RakeshRay writes:
> Thanks for the suggestions, I tried, but does not help.
> It could be the problem with the Stomp protocol!.
> Anyone using Stomp to Connect to use Active MQ?
I'm using STOMP with perl Net::Stomp and it is working reasonably good
for simple use. 5.3.SNAPSHOT is buggy once you
RakeshRay wrote:
>
> Thanks for the suggestions, I tried, but does not help.
> It could be the problem with the Stomp protocol!.
> Anyone using Stomp to Connect to use Active MQ?
>
>
You could use the Stomp client tools on my web site. The download includes a
ProducerTool and a ConsumerTool w
Thanks for the suggestions, I tried, but does not help.
It could be the problem with the Stomp protocol!.
Anyone using Stomp to Connect to use Active MQ?
mjustin wrote:
>
> If it depends on message number / message size, maybe the broker needs
> more buffer space, you can try increasing the mem
If it depends on message number / message size, maybe the broker needs more
buffer space, you can try increasing the memoryLimit in the activemq.xml
file. It helped with a similar problem where the producer stopped after a
small number of messages until I increased the value to 50mb.
I tried with 1000 messsages or 800 byte/each, that is small enough.
I removed can_read before read_frame and seems behaving okay. Reading more
to figure out if can_read is really required in my case or not!
Thanks for the other suggestions, though.
mjustin wrote:
>
> I am using 5.2 and 5.3-Snaps
I am using 5.2 and 5.3-Snapshot. Have you tried to test it with a smaller
number of messages, and without transactions?
RakeshRay wrote:
>
>
> Hi,
> We have written a wrapper around and internally it is using using timeout
> feature.
> What version of Active MQ are you using?
>
>
-
-
Hi,
We have written a wrapper around and internally it is using using timeout
feature.
What version of Active MQ are you using?
sub read {
my ($self) = @_;
# after reading, we also need to acknoledge the read, but keep them
both as
part of the same transaction
Hi, Hoover.
We have written a wrapper around and internally it is using
receive_frame()...Here is the wrapper code.
sub read {
my ($self) = @_;
# after reading, we also need to acknoledge the read, but keep them
both as
part of the same transaction
# still need
Maybe you meant to call $stomp->receive_frame() in the while loop instead?
On Wed, Jul 1, 2009 at 1:15 PM, RakeshRay wrote:
>
> Just installed Active MQ 5.2.
> Using Stomp, inserted 5000 msgs and try to read the same with
> while ( my $msg = $stomp->read() ) {
>$stomp->commit();
>
I don't know the PHP Stomp client very well (but a Delphi implementation).
$stomp->read() seems to return immediately without waiting for the next
message.
There might be a different method $stomp->read(receivetimeout), which waits
for the given time (in milliseconds) before it gives up.
Michael
10 matches
Mail list logo
