session which resulted in the session being shared across threads, obviously
a no-no as sessions need to be in a single thread context. The simple
solution was to make these class instance variables and that solved the
problem.
Thanks Gary.
frank_at_zynga wrote:
>
> Hi Gary,
>
> I
Hi Gary,
I've entered this in JIRA under Test Cases. The title is "Transacted
Messages not Committed".
Thanks,
-Frank
Gary Tully wrote:
>
> 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 tha
Hmmm, one of the files didn't get uploaded. Let me try again...
http://www.nabble.com/file/p21632866/TestCase.java TestCase.java
frank_at_zynga wrote:
>
> Hi Gary,
>
> I was able to create a test case and reproduce this behavior on a
> consistent basis. The source cod
nabble.com/file/p21632842/AMQWorkerTest.java
AMQWorkerTest.java
Gary Tully wrote:
>
> Hi Frank,
> do you think you can produce a test case for the behavior you describe.
> Thanks,
> Gary.
>
> 2009/1/22 frank_at_zynga :
>>
>> Hi,
>>
>> We're just st
Hi,
We're just starting to phase in the use of AMQ 5.2.0 in a high volume
environment and I've run into some strange behavior with transacted
sessions. The basic architecture of the consumer is a java daemon that
spawns a configurable number of single threaded consumers that implement
MessageLis
