[JBoss JIRA] Created: (JBAS-7285) Lazy initialization fix for wrong use case.
by Vicky Kak (JIRA)
Lazy initialization fix for wrong use case.
-------------------------------------------
Key: JBAS-7285
URL: https://jira.jboss.org/jira/browse/JBAS-7285
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCA service
Reporter: Vicky Kak
Assignee: Vicky Kak
Fix For: JBossAS-5.2.0.GA, JBossAS-Branch_4_2
The JCA lazy initialization does not work in the following sceanrio
*********************************************************************
DataSource ds = ...
Connection c = ds.getConnection();
UserTransaction ut = ...
ut.begin();
// Do work
c = ds.getConnection(); // This should be avoided and looks antipattern.
ut.commit();
ut.begin();
*********************************************************************
Getting the connection again in the TX context causes the issue, the subsequent
ds.getConnection() leads to multiple enlistment of the local XAResources
and thus causing this warning
http://www.jboss.org/community/wiki/Multiple1pc
The application developers should not follow the above coding pattern, however we should fix the issue cropping due to this coding practice as it could lead some misbehaviour in container, there are no evidences about the misbehaviour but it had been reported by our customers.
--
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
13 years, 9 months
[JBoss JIRA] Created: (JBAS-7924) smoke-tests build SUCCESS despite FAILURE
by Thomas Diesler (JIRA)
smoke-tests build SUCCESS despite FAILURE
-----------------------------------------
Key: JBAS-7924
URL: https://jira.jboss.org/jira/browse/JBAS-7924
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Reporter: Thomas Diesler
Assignee: Shelly McGowan
Fix For: JBossAS-6.0.0.M3
[tdiesler@tdvaio testsuite]$ ./build.sh clean jars smoke-tests
smoke-tests:
[server:start] Starting server "all", with command (start timeout is 120 seconds ):
[server:start] /usr/java/jdk1.6.0_17/bin/java -cp /home/tdiesler/git/jbossas/build/target/jboss-6.0.0-SNAPSHOT/bin/run.jar:/usr/java/jdk1.6/lib/tools.jar -Xms128m -Xmx512m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -XX:-UseGCOverheadLimit -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/home/tdiesler/git/jbossas/build/target/jboss-6.0.0-SNAPSHOT/lib/endorsed -Djgroups.udp.ip_ttl=0 -Djboss.server.log.threshold=DEBUG -Djava.endorsed.dirs=/home/tdiesler/git/jbossas/build/target/jboss-6.0.0-SNAPSHOT/lib/endorsed/ -Dxb.builder.useUnorderedSequence=true org.jboss.Main -c all -b localhost -g DefaultPartition
[server:start] Server started.
...
smoke-tests-raw:
[echo]
[echo] junit.timeout: 300000
[echo] jbosstest.iterationcount: 10
[echo] jbosstest.threadcount: 5
[echo] jbosstest.beancount: 5
[echo]
[mkdir] Created dir: /home/tdiesler/git/jbossas/testsuite/output/log
...
[junit] Running org.jboss.test.jmsra.test.RaJMSSessionUnitTestCase
[junit] javax.ejb.EJBException: javax.jms.JMSException: Could not create a session: Unable to get managed connection for JmsXA)
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.423 sec
[junit] Test org.jboss.test.jmsra.test.RaJMSSessionUnitTestCase FAILED
...
[server:stop] Shutting down server: all
[server:stop] log4j:WARN No appenders could be found for logger (org.jnp.interfaces.TimedSocketFactory).
[server:stop] log4j:WARN Please initialize the log4j system properly.
[server:stop] shutdownTimeout will be=45
[server:stop] Server stopped.
BUILD SUCCESSFUL
Total time: 6 minutes 3 seconds
--
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
13 years, 9 months