[jboss-jira] [JBoss JIRA] Created: (JBAS-6394) CachedConnectionManager start transaction for all connection in cache.
Nattapong Triammeerit (JIRA)
jira-events at lists.jboss.org
Mon Jan 19 06:23:04 EST 2009
CachedConnectionManager start transaction for all connection in cache.
----------------------------------------------------------------------
Key: JBAS-6394
URL: https://jira.jboss.org/jira/browse/JBAS-6394
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transaction Manager (Arjuna)
Environment: JBossAS-4.2.2.GA, jdk1.5_14, windows XP SP2, spring framework 2.5.1
Reporter: Nattapong Triammeerit
Assignee: Jonathan Halliday
I use spring to implement database dao leyer and transaction management. I got a error "Trying to start a new tx when old is not complete! ..." when I try to create the transaction after directly getting database connection from datasource.
The scenario is
1. Firstly get database connection from datasource. The connection is added to CachedConnectionManager.
2. Start the transaction, the connection in CachedConnectionManager is started.
3. Get database connection from datasource again. It throw "org.jboss.resource.connectionmanager.JBossLocalXAException: Trying to start a new tx when old is not complete! ..."
I think, It raise an error becuase it start the first connection in CachedConnectionManager but JBoss transaction manager unknown it and cannot suspense it before inner transaction started. Does it is correct to start transaction to all connection of CachedConnectionManager?
Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list