I find that if I use jencks to receive message, use a client to send some messages and then sleep for a while then send some messages again, the non-deliverd messages of the first time sending will always stay in the queue and not be delived any more.
Waves wrote: > > Have you seen my reply? After update the Activemq4.1.0 with your patch, > there are some non-delivered messages in the queue. Now the problem is > critical for us, so I hope you to help me to find the answer quickly. > Thank you very much! > > > Waves wrote: >> >> I update ActiveMQSessionExecutor.class in >> apache-activemq-4.1.0-incubator\apache-activemq-4.1.0-incubator\lib\activemq-core-4.1.0-incubator.jar >> and >> apache-activemq-4.1.0-incubator\apache-activemq-4.1.0-incubator\apache-activemq-4.1.0-incubator.jar, >> I also update ActiveMQSessionExecutor.class in client dependented >> activemq-core-4.1.0-incubator.jar, >> the problem still existed. >> >> >> Christopher G. Stach II wrote: >>> >>> Guillaume Nodet wrote: >>>> Is this related to http://issues.apache.org/activemq/browse/AMQ-1078 ? >>>> >>>> On 1/26/07, Waves <[EMAIL PROTECTED]> wrote: >>>>> >>>>> ActiveMQ:4.1.0, spring2.0, jencks1.3. We used jencks2.0 later, the >>>>> problem >>>>> still existed. >>> >>> That's my guess. :) >>> >>> -- >>> Christopher G. Stach II >>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Use-jencks-to-async-receive-message%2C-there-are-always-some-messages-are-left-in-the-queue-tf3120301.html#a8723890 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
