It would be ideal to create a test case using simple Java API
http://activemq.apache.org/stomp.html#Stomp-JavaAPI
and add it to the
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/transport/stomp/StompTest.java?view=markup
If Perl is easier for you,
Hi,
can you raise a Jira issue with this test attached, so we can handle it
later?
Thanks
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Fri, Jan 23, 2009 at 6:03 PM, Jagath
Thanks Dejan. Here's the JIRA issue link.
https://issues.apache.org/activemq/browse/AMQ-2084 ActiveMQ - XPATH
Selectors - Unable to make it work
Thanks and Regards,
Jagath
Dejan Bosanac wrote:
Hi,
can you raise a Jira issue with this test attached, so we can handle it
later?
Hi Frank,
it is great to have a test case. Could you create a jira issue[1] for
this and attach your tests case with the ASF license grant. In that
way we can use your test case in the activemq test suite to ensure
this issue stays fixed when it is resolved.
Thanks,
Gary.
[1]
Sending to a topic that has no subscribers won't by default hold the
message until someone subscribes. You could use retroactive consumers,
or durable consumers to solve this, or switch to using a queue if that
would meet your needs.
You may want to read the JMS tutorial to get a feel for when
First thx for quick reply. I'm already using durableconsumers. My
subscribition Client is written in .net and I'm using NMS. Can anyone send
me a sample code how to let it work. The problem is that the message isn't
send to durable consumer, if the consumer subscribes first time after a
message
Are you using a fixed clientID and subscriberName?
2009/1/26 zunrise de...@artkontrast.de:
First thx for quick reply. I'm already using durableconsumers. My
subscribition Client is written in .net and I'm using NMS. Can anyone send
me a sample code how to let it work. The problem is that the
A durable consumer won't receive messagew sent before it was started if
it has never subscribed to the broker before. The purpose of a durable
consumer is to allow a consumer to disconnect and then reconnect and
receive any messages sent since the last time it was connected. So if
you are
Hi,
I tried all this without success.
The more messages are in the queue the slower it gets. My system was running
during the whole weekend now. The first hour I had about 900 messages per
second (JMS sending took about 0ms). Then after about 1-2 hours JMS sending
suddently takes 1 ore more
I'll also express strong interest in AMQP and I'll take the liberty of saying
that most people using stomp for cross platform integration with ActiveMQ
should be expressing interest. With the influx of enterprise apps being
written in dynamic languages, AMQP offers high end messaging features in
Thanks. This approach worked. I guess uzipping the tar in windows and ftp ing
to solaris also works. But you need to remove the dos characters from the sh
file.
Filip Hanik - Dev Lists wrote:
this is because the build tool, Maven, that is used to create the
distros for ActiveMQ, doesn't
Hello,
I just made another test:
What happens, if the Queue is full. Will the performance grow again?
I Changed my Queue size to GB (storeUsage limit=2gb store=#store/ ).
Now I restarted my test, having 900 JMS Producers sending messages into the
Queue.
The first few minutes it is very fast.
The AMQP reality is that only new message brokers will implement it -
simply because you'd have to re-write the message broker to
accommodate it. Which is why you won't see any of the traditional
messaging platforms like Webshpere MQ, SonicMQ or Tibco EMS, RV
implementing any time soon.
13 matches
Mail list logo