21 PM, Rajika Kumarasiri wrote:
> Sure, let me have some time.
>
> Rajika
>
>
> On Tue, Apr 6, 2010 at 6:52 PM, Gary Tully wrote:
>
>> can you open a jira issue and attach your test case or something that can
>> reproduce in junit? It looks like there is an outst
rver, but all client side
> context
> should be removed on a rollback.
> A junit test case is the best way to help reproduce and diagnose.
>
> On 6 April 2010 13:58, Rajika Kumarasiri wrote:
>
> > I tested with 5.1.3 but end up with the same result. Anybody has any
&
I tested with 5.1.3 but end up with the same result. Anybody has any clue?
Thanks,
Rajika
On Tue, Apr 6, 2010 at 3:14 PM, Rajika Kumarasiri wrote:
> Thanks Gary. I'll give a try and let you know.
>
> Rajika
>
>
> On Tue, Apr 6, 2010 at 3:05 PM, Gary Tully wrote:
>
Thanks Gary. I'll give a try and let you know.
Rajika
On Tue, Apr 6, 2010 at 3:05 PM, Gary Tully wrote:
> There has been a lot of work in this area, I would advise upgrading to
> version 5.3.1 <http://activemq.apache.org/activemq-531-release.html>
>
> On 6 April 2010 1
hi,
I am using the activemq broker 5.2 ( on Fedora 11) as the JMS provider.
Using a JMS consumer I am connecting to this broker. The client uses JMS
transacted session. I am getting the following exception and the stack
trace[1] when client tries to call session.rollback(). It works fine when
calli
