activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Namrata Patel <>
Subject Re: Apollo 1.6 + Perl client errors where ActiveMQ didn't
Date Sun, 01 Sep 2013 06:37:35 GMT

We are too moved on from Apollo 1.6 from ActiveMQ. But we are using PHP
Stomp client.
Looks like for you if you send too many messages simultaneously, it is
failing. I tried a simple test in php, that Connects -> loops and sends
5000 messages to a queue -> disconnect. (attached is the php example, u can
modify it for perl)

This simple send works for me. Is it the issue with just Topics as I was
trying using Queue. I just had trouble sending too many messages as a part
of transaction with queue though.


On Sat, Aug 31, 2013 at 2:23 AM, Jens Kristian Søgaard <> wrote:

> Hi,
> For several years I have been using ActiveMQ together with the Perl STOMP
> library Net::Stomp - without any problems.
> Now I tried setting up Apollo 1.6 to replace ActiveMQ and I run into an
> odd problem:
> My test client is a simple loop that will send messages to a topic. The
> client works fine for a period of time, and then unexpectedly fails with an
> error like this:
>   "only wrote xxx characters out of the xxx character frame"
> The exact number of characters vary from run to run.
> After this message is printed, the client is no longer able to send
> messages.
> I assumed this was showing the age of Net::Stomp and decided to
> reimplement the client using the newer Net::STOMP::Client. However I see
> the exact same problem with this new script - the error reads:
>   "could not send all data!"
> After getting this error, the script is no longer able to send new
> messages.
> I was able to let the script disconnect and reconnect by forcibly dropping
> the Net::STOMP::Client object and instantiating a new object, as the
> disconnect() and connect() methods doesn't do anything useful after the
> error occurs.
> My main concern is that this shouldn't be happening. The error occurs up
> to ~20 times per hour, requiring reconnection every time.
> If I keep the volume of messages low, the error doesn't occur - or at
> least it occurs very infrequently. As soon as I increase it to a few
> messages per second, the errors pops up frequently.
> When I try the same script on ActiveMQ it just keeps running for weeks
> without requiring reconnects.
> Anyone seen behaviour like this, or have an idea what could be done?
> Thanks in advance,
> --
> Jens Kristian Søgaard, Mermaid Consulting ApS,
> http://www.mermaidconsulting.**com/ <>


*Namrata Patel** *| Software Engineer
Synergy Technology Services

t+91-22-407-51999 | f +91-22-2925-1003 | m +91-9967585155
**<>| <>

701 Acropolis, Military Road, Marol, Andheri (East), Mumbai - 400 059


*Disclaimer: The information contained in this electronic message and any 
attachments to this message are intended for the exclusive use of the 
addressee(s) and may contain confidential or privileged information.  If 
you are not the intended recipient or have received this email in error you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.*

View raw message