I'll see what I can do my code uses a lot of abstract behaviour but
I'll see I can find other similar test cases and adapt.
At work we have Websphere MQ so today I'll be able to compare behaviors.
On Sep 15, 2009, at 8:50 AM, Rob Davies wrote:
Can we have a test case please ? :)
On 15 Sep 20
Can we have a test case please ? :)
On 15 Sep 2009, at 14:41, Robert Nicholson wrote:
I just tried my app with the 5.3 SNAPSHOT and when I run it I see my
process is consuming messages but every single one of them is always
left on the queue. This even when my JMS Session is AUTO_ACKNOWLEDGE
I just tried my app with the 5.3 SNAPSHOT and when I run it I see my
process is consuming messages but every single one of them is always
left on the queue. This even when my JMS Session is AUTO_ACKNOWLEDGE
On Sep 15, 2009, at 2:40 AM, Rob Davies wrote:
On 15 Sep 2009, at 07:33, Robert Nic
What has changed in the 5.3 SNAPSHOT since Hermes gives me the
following error now when performing discovery
Has anything changed in regards to how you setup Hermes discovery with
5.3 SNAPSHOT vs 5.20?
hermes.HermesException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavaila
On 15 Sep 2009, at 07:33, Robert Nicholson wrote:
On each occasion when I notice messages are no longer being
delivered. If I restart my app after restarting the broker the
messages begin to deliver.
On Sep 15, 2009, at 12:56 AM, Rob Davies wrote:
On 15 Sep 2009, at 06:42, Robert Nichol
On each occasion when I notice messages are no longer being delivered.
If I restart my app after restarting the broker the messages begin to
deliver.
On Sep 15, 2009, at 12:56 AM, Rob Davies wrote:
On 15 Sep 2009, at 06:42, Robert Nicholson wrote:
So, I have a pretty standard JMS message
I have a multi threaded consumer setup... all message consumption is
asynchronous
the consumers both the dispatch consumer and the "child" consumers are
setup like this
public synchronized void startJMS() throws JMSException {
try {
connection = createQueueConnection(qu
On 15 Sep 2009, at 06:42, Robert Nicholson wrote:
So, I have a pretty standard JMS message listener but when using
ActiveMQ it often just doesn't receive any messages even when there
are messages on the queue. The Session is a transacted one with
AUTO_ACKNOWLEDGE but for some reason the me
So, I have a pretty standard JMS message listener but when using
ActiveMQ it often just doesn't receive any messages even when there
are messages on the queue. The Session is a transacted one with
AUTO_ACKNOWLEDGE but for some reason the messages are never taken off
the queue.
I believe A
