activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (AMQ-2346) in managed environment, 2 connections/session, UserTransaction, transaction management gets confused
Date Mon, 31 Aug 2009 17:02:48 GMT


David Jencks commented on AMQ-2346:

Making ENDED_XA_TRANSACTION_CONTEXTS static in TransactionContext makes the test pass for
me.  This variable doesn't make any sense unless it's static, as otherwise the only possible
TransactionContext in the list is "this".

I'm not thrilled with introducing a static, in an osgi environment it would be better to have
a service, but it seems like the best solution in a non-osgi environment.

Unfortunately I'm seeing a new problem, apparently a race condition between closing a connection
and starting a new connection and setting clientId.  Adding a Thread.sleep(10) to JmsTransactionTestSupport
reconnect sidesteps this problem...

Tests run: 17, Failures: 0, Errors: 15, Skipped: 0, Time elapsed: 2.022 sec <<< FAILURE!
 Time elapsed: 1.124 sec  <<< ERROR!
javax.jms.InvalidClientIDException: Broker: localhost - Client: org.apache.activemq.test.JmsResourceProvider
already connected from vm://localhost#8
	at org.apache.activemq.advisory.AdvisoryBroker.addConnection(
	at org.apache.activemq.command.ConnectionInfo.visit(
	at org.apache.activemq.transport.ResponseCorrelator.onCommand(
	at org.apache.activemq.transport.TransportFilter.onCommand(
	at org.apache.activemq.transport.vm.VMTransport.iterate(
	at org.apache.activemq.thread.PooledTaskRunner.runTask(
	at org.apache.activemq.thread.PooledTaskRunner$
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

> in managed environment, 2 connections/session, UserTransaction, transaction management
gets confused
> ----------------------------------------------------------------------------------------------------
>                 Key: AMQ-2346
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JCA Container
>    Affects Versions: 5.3.0
>            Reporter: David Jencks
>            Assignee: Gary Tully
>             Fix For: 5.3.0
> In geronimo we're seeing an intermittent tck problem that seems to relate to a situation
where there are:
> -- a BMT stateless session ejb
> -- two connections (I think these get shared to the same ManagedConnection)
> -- two sessions
> -- tx control through UT
> -- send a message in one tx
> -- receive message in a tx that is rolled back
> -- receive message in a tx that is committed
> In a public test case I'm seeing that the session proxies get confused about whether
there is an active transaction.  This doesn't happen all the time but with a few repititions
it happens consistently.
> See GERONIMO-4784

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message