I couldn't actually read the attached file - can you attach again
without the formatting ?
On 13 Jun 2008, at 22:30, drjava wrote:
I am (still) in the process of testing a JmsMessenger class called
JmsLogMessenger. One of my test cases scenario is as follows:
* start the JMS broker (Active
On 14 Jun 2008, at 00:17, grndvl1 wrote:
To showcase the ActiveMQ possibilities the demos should work. They
don't...
I just got the latest version and wow does the demos blow. Can
someone
please update these for something with a little more flash and that
actually
work? The Chat demo
On 14 Jun 2008, at 01:50, Joshua Smith wrote:
All-
I'm reading a number of references on JMS written some time between
2001 and
now. The challenge that comes with that is knowing which things are
still
true today and which things were describing the state of affairs at
that
time. I found
All-
I'm reading a number of references on JMS written some time between 2001 and
now. The challenge that comes with that is knowing which things are still
true today and which things were describing the state of affairs at that
time. I found the following paragraph in the O'reilly Java Message Se
I was using 'PERSISTENT' mode on publisher side, which causes the dead loop
of 'SHUTDOWN message not acked --> redelivery of SHUTDOWN message upon
subscriber start'.
eaglepointe wrote:
>
> Yes, I'm running 5.1.0 and using default activemq.xml. I've found out the
> cause! It is a bug subscriber
Yes, I'm running 5.1.0 and using default activemq.xml. I've found out the
cause! It is a bug subscriber code, it closes the connection in 'onMessage'
upon receiving 'SHUTDOWN' message while using 'session.AUTO_ACKNOWLEDGE', so
'SHUTDOWN' message never gets acknowledged, which results in everybody
To showcase the ActiveMQ possibilities the demos should work. They don't...
I just got the latest version and wow does the demos blow. Can someone
please update these for something with a little more flash and that actually
work? The Chat demo doesn't run, the send / receive doesn't work. The
I am (still) in the process of testing a JmsMessenger class called
JmsLogMessenger. One of my test cases scenario is as follows:
* start the JMS broker (Active Mq 5.1.0, embedded)
* start a thread that sends messages at a given interval.
* after a while (n seconds) shut the broker down
* after an
Not that it helps much, I tried it with a 5.x release and your code works
fine. I see the subscription is durable across consumer and broker restarts.
Have you modified your activemq.xml, are you running with 5.1.0?
/Dave
On Fri, Jun 13, 2008 at 1:05 PM, eaglepointe <[EMAIL PROTECTED]> wrote:
>
>
Forgot to mention that I also restarted message broker before start durable
subscriber again.
eaglepointe wrote:
>
> Ok, here is what I did,
>
> 1) start message broker
> 2) start a durable subscriber which subscribes "topictest.messages" as the
> attached code
> 3) start publisher, which send
Ok, here is what I did,
1) start message broker
2) start a durable subscriber which subscribes "topictest.messages" as the
attached code
3) start publisher, which sends some messages to "topictest.messages" in
'persistent' mode, and the subscriber receives the messages
4) stop the subscriber and
Your not running this from within a thread by any chance? I don't
believe connection.start() is going to block, so try and create the
connection outside the thread and pass it in by reference to the thread
instance.
HTH
/Dave
On Thu, Jun 12, 2008 at 10:30 PM, eaglepointe <[EMAIL PROTECTED]> wrot
It looks that there is a problem in activemq journal wich is used by default
amqPersistenceAdapter. I have tested this also on amq 4.1.1 journaledJDBC
adapter with same bug.
When jdbcPersistenceAdapter with 4.1.1(non-journal) or
kahaPersistenceAdapter with 5.1 are used with 2 durable topic subscri
13 matches
Mail list logo
