activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Green <james.mk.gr...@gmail.com>
Subject Re: Fusesource PHP Stomp bug
Date Wed, 21 Nov 2012 11:41:42 GMT
Dejan,

The Fusesource Stomp website makes no reference to the Github project (that
I can see), leaving people to download a possibly very old release.

Using the 1.0.0-dev branch the large messages bug is still present.

The author of the PECL library has issued me a test release which does at
least resolve the performance problems so I have a route forward for now.

Thanks,

James


On 21 November 2012 10:07, Dejan Bosanac <dejan@nighttale.net> wrote:

> Hi James,
>
> most of the development is moved to github
> https://github.com/dejanb/stomp-php
>
> You might want to check the code and issues filed there. This library
> is not officially support by FuseSource/RedHat, so it's a community
> maintained.
>
> Regards
> --
> Dejan Bosanac
> ----------------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> dbosanac@redhat.com
> Twitter: @dejanb
> Blog: http://sensatic.net
> ActiveMQ in Action: http://www.manning.com/snyder/
>
>
> On Tue, Nov 20, 2012 at 3:57 PM, James Green <james.mk.green@gmail.com>
> wrote:
> > If I try and send a large, multi-megabyte (base64 encoded), message to a
> > queue my script issues the following notice then "hangs" consuming all
> > available CPU:
> >
> > Notice: fwrite(): send of 8192 bytes failed with errno=104 Connection
> reset
> > by peer in /home/jamesg/Stomp.php on line 495
> >
> > Is this library being maintained at all? The JIRA issues are around two
> > years old..!
> >
> > Incidently in my tests of sending 10,000 1024 byte messages via the
> > Fusesource library and by the PECL Stomp library with receipts on but
> > persistence off, the Fusesource library appears 400x faster than the PECL
> > library. In fact, the Fusesource library is "only" 3-4x slower with
> > receipts on and off.
> >
> > James
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message