December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4980) Calling a message endpoint twice from different transactions makes MessageInflowLocalProxy confuse the two transactions

by Marcus Nilsson (JIRA)

Calling a message endpoint twice from different transactions makes MessageInflowLocalProxy confuse the two transactions ----------------------------------------------------------------------------------------------------------------------- Key: JBAS-4980 URL: http://jira.jboss.com/jira/browse/JBAS-4980 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.0.GA Reporter: Marcus Nilsson Assigned To: Carlo de Wolf We have a resource adapter where we call an endpoint (a MessageInflowLocalProxy) twice from two different transactions. This caused the endpoint to fail in endTransaction with Current transaction TransactionImple < ac, BasicAction: -3f57fcde:b392:473d5904:ab status: ActionStatus.RUNNING > is not the expected transaction We tracked this problem down to the member variable "transaction" in MessageInflowLocalProxy.java, which is not set to null in endTransaction. When the endpoint is called again during a transaction, startTransaction will leave it alone, making transaction point to the old one. http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_2_0_GA/ejb3/src/main/... Suggested fix: Set transaction=null at end of transaction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1834) Entering registration information is confusing

by Chris Laprun (JIRA)

Entering registration information is confusing ---------------------------------------------- Key: JBPORTAL-1834 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1834 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun Assigned To: Chris Laprun -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5021) org.jboss.test.jca.test.XADSUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.jca.test.XADSUnitTestCase ---------------------------------------- Key: JBAS-5021 URL: http://jira.jboss.com/jira/browse/JBAS-5021 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assigned To: Shelly McGowan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-435) Re-release maven-jboss-deploy-plugin

by Paul Gier (JIRA)

Re-release maven-jboss-deploy-plugin ------------------------------------ Key: JBBUILD-435 URL: http://jira.jboss.com/jira/browse/JBBUILD-435 Project: JBoss Build System Issue Type: Task Components: maven-jboss-deploy-plugin Reporter: Paul Gier Assigned To: Paul Gier Fix For: maven-jboss-deploy-plugin-1.5 An issue came up with the released version of the plugin. Version 1.5 will be re-released since the project is small, and an update of the release should not negatively affect anyone. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-434) maven-jboss-deploy-plugin leaves version number in export

by Carlo de Wolf (JIRA)

maven-jboss-deploy-plugin leaves version number in export --------------------------------------------------------- Key: JBBUILD-434 URL: http://jira.jboss.com/jira/browse/JBBUILD-434 Project: JBoss Build System Issue Type: Bug Affects Versions: maven-jboss-deploy-plugin-1.5 Reporter: Carlo de Wolf Assigned To: Paul Gier Priority: Critical <?xml version="1.0" encoding="UTF-8"?> <project name="jboss/jboss-ejb3-ext-api-component-info"> <component id="jboss/jboss-ejb3-ext-api" licenseType="lgpl" version="0.1.2-SNAPSHOT" description="JBoss EJB 3 API for Bean Providers" scm="svn:http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/" > <artifact id="jboss-ejb3-ext-api-sources.jar"/> <artifact id="jboss-ejb3-ext-api.jar"/> <export> <include input="jboss-ejb3-ext-api-0.1.2-SNAPSHOT.jar"/> </export> </component> </project> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-856) Release 2.2.2.GA_CP02

by Ron Sigal (JIRA)

Release 2.2.2.GA_CP02 --------------------- Key: JBREM-856 URL: http://jira.jboss.com/jira/browse/JBREM-856 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal For EAP 4.2 and 4.3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1823) fix udp collision with cms tests

by Prabhat Jha (JIRA)

fix udp collision with cms tests -------------------------------- Key: JBPORTAL-1823 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1823 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.3 Final Reporter: Prabhat Jha Assigned To: Prabhat Jha CMS tests fail when on two or more more testsuite run at the same time because udp traffic collision. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5042) forceClearOnShutdown

by Adrian Brock (JIRA)

forceClearOnShutdown -------------------- Key: JBAS-5042 URL: http://jira.jboss.com/jira/browse/JBAS-5042 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.3.GA Reporter: Adrian Brock An undocmentated feature has been added to the jms rar in 4.2.3 "forceClearOnShutdown". Sadly it doesn't work properly. This needs fixing, documentating and testing. It should also be made the default since we don't want to wait forever when we stop an MDB. If an MDB doesn't shutdown in the time then we should log a warning. Discussion from the mailing list: " c) forceClearOnShutdown, et. al. The idea looks good, but the implementation is rubbish. It shows a fundamental misunderstooding on how the pool works. The notification happens once for each session that ends (and hence so does your loop). In practice with the default config, it will leave the loop after the first session ends (almost immediately) when in the default config there are still 14 other sessions to go. A 1 second default wait is also unrealistic. Many people have MDBs that take longer than this to process something. In fact, this should be the default behaviour (but with different configuration). Nothing should wait forever! :-) The defaults should be specified in conf/standardjboss.xml and the ejb3 equivalent aop interceptors file such that users can easily change them. " -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5040) Locked entities won't be released correctly after transaction timeout

by Christian Michels (JIRA)

Locked entities won't be released correctly after transaction timeout --------------------------------------------------------------------- Key: JBAS-5040 URL: http://jira.jboss.com/jira/browse/JBAS-5040 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Manager Affects Versions: JBossAS-4.2.2.GA Reporter: Christian Michels Assigned To: Adrian Brock When locking an entity in a (outer) user transaction and trying to lock the same entitity in a inner transaction (with a smaller txTimeout), the entity will not be released, if the inner transaction timed out. The entity won't be released until the outer transaction timed out. With JBoss 4.0.4, the inner transaction rollback will be resolved after a short while: 18:56:14,237 WARN [TransactionImpl] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=PCTR694/17, BranchQual=, localId=17] timed out. status=STATUS_ACTIVE 18:56:17,237 ERROR [BeanLock] Thread[RMI TCP Connection(2)-172.22.6.85,5,RMI Runtime]Saw rolled back tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=PCTR694/17, BranchQual=, localId=17] waiting for txLock 18:56:17,237 ERROR [LogInterceptor] TransactionRolledbackException in method: public abstract void kam.jbosstest.transactionlocking.LockedEntityEJBRemote.loadIntoTransaction() throws java.rmi.RemoteException, causedBy: java.lang.RuntimeException: Transaction marked for rollback, possibly a timeout ... e.g. EntityLockingEJBHome entityLockingHome = (EntityLockingEJBHome) ctx.lookup("EntityLockingEJB"); kam.jbosstest.transactionlocking.EntityLockingEJBRemote entityLockingRemote = entityLockingHome.create(); LockedEntityEJBHome lockedEntityHome = (LockedEntityEJBHome) ctx.lookup("LockedEntityEJB"); LockedEntityEJBRemote entity = null; try { entity = lockedEntityHome.findByPrimaryKey(1); } catch (FinderException e) { throw new Exception(e); } UserTransaction ut = (UserTransaction) ctx.lookup("UserTransaction"); ut.setTransactionTimeout(10); System.out.println("Starting transaction (timeout=10s)..."); Date start = new Date(System.currentTimeMillis()); ut.begin(); System.out.println("Date:" + start); System.out.println("...locking entity in client context..."); entity.loadIntoTransaction(); try{ System.out.println("...trying to lock the same entity in a new transaction with 2s txTimeout..."); entityLockingRemote.lockResource(1, 2); }catch(Exception e){ e.printStackTrace(); } Date end = new Date(System.currentTimeMillis()); System.out.println("Application was locked for: " + (end.getTime() - start.getTime()) + "ms instead of about 2s"); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5038) Create separate deployer for setting webapp clustering defaults

by Brian Stansberry (JIRA)

Create separate deployer for setting webapp clustering defaults ---------------------------------------------------------------- Key: JBAS-5038 URL: http://jira.jboss.com/jira/browse/JBAS-5038 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 Initial approach for beta3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007