please discuss it on the list kai
On Jan 6, 2008, at 9:26 PM, khudalla wrote:
Hi, Chris, James!
I have put some time into this issue and already have commented on
it in
JIRA. I think I have found the problem and already have hacked up a
solution
which I would like to elaborate on. However
I'm a little closer now...
After reading that the message type is toggled on whether or not the
content-length header is included,
http://activemq.apache.org/stomp.html, I dug in to the stomp gem and
found that it is hard coded to always send the content-length header.
def _transmit(s, comman
Hi, Chris, James!
I have put some time into this issue and already have commented on it in
JIRA. I think I have found the problem and already have hacked up a solution
which I would like to elaborate on. However, James, in JIRA the issue is not
assigned to anyone and I would like to discuss some
Hello,
Using the latest AMQ 5.0.0 release and the ruby stomp-1.0.5 gem, I'm
trying to send some messages via the example catstomp.rb script and
receive the messages using the example javascript from
http://activemq.apache.org/ajax.html. However, it doesn't appear that
the message body is making it
I dont think so, I doubt youll get much help there.does it ALWAYS happen
or just sometimes? The reason I mention that is that we have gotten this
exception before with a spring based JMS listeners trying to connect to a
TCP AMQ broker URL and both were AMQ 4.1.1 out of the box. However, it was
I'll assume all the clients are active at the same time - and that you
don't require durable subscribers. In which case there will be the
destination itself - which is a relatively small object and queued
messages for each subscriber to a destination.
The trade of is one of performance agains
Hi,
I am planning a system which will involve one broker and many clients (about
40) that will use it.
calculating the usage, i will have to hold about 700 topics per client,
total of 28000.
That seems pretty large . I am considering making some topics shared for
different usages, using message f
