November 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-918) TXBridge Demo: SynchronizationImple.afterCompletion failed due to IllegalStateException

by Paul Robinson (Created) (JIRA)

TXBridge Demo: SynchronizationImple.afterCompletion failed due to IllegalStateException --------------------------------------------------------------------------------------- Key: JBTM-918 URL: https://issues.jboss.org/browse/JBTM-918 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.15.3 Environment: AS 7 master @ 2011-10-06 15:00:00 Reporter: Paul Robinson Fix For: 4.15.4, 5.0.0.M2 To reproduce: 1. Deploy TXBridge demo client and service 2. Visit: http://localhost:8080/txbridge-demo-client/ 3. Click "Submit Booking" Observe: {code} 14:58:12,899 WARN [com.arjuna.ats.jta] (TaskWorker-3) ARJUNA16029: SynchronizationImple.afterCompletion - failed for org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@259f1b1d with exception: java.lang.IllegalStateException at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionImple(TransactionSynchronizationRegistryImple.java:225) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.putResource(TransactionSynchronizationRegistryImple.java:103) [jbossjts-4.15.3.Final.jar:] at org.jboss.as.jpa.transaction.TransactionUtil.putEntityManagerInTransactionRegistry(TransactionUtil.java:195) at org.jboss.as.jpa.transaction.TransactionUtil.access$100(TransactionUtil.java:48) at org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization.afterCompletion(TransactionUtil.java:220) at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:117) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:403) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:335) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.SubordinateAtomicAction.doCommit(SubordinateAtomicAction.java:176) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.TransactionImple.doCommit(TransactionImple.java:158) [jbossjts-4.15.3.Final.jar:] at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.commit(XATerminatorImple.java:87) [jbossjts-4.15.3.Final.jar:] at org.jboss.jbossts.txbridge.inbound.BridgeDurableParticipant.commit(BridgeDurableParticipant.java:204) [jbosstxbridge-4.15.3.Final.jar:] at com.arjuna.wst11.messaging.engines.ParticipantEngine.executeCommit(ParticipantEngine.java:577) [jbossxts-4.15.3.Final.jar:] at com.arjuna.wst11.messaging.engines.ParticipantEngine.commit(ParticipantEngine.java:149) [jbossxts-4.15.3.Final.jar:] at com.arjuna.wst11.messaging.ParticipantProcessorImpl.commit(ParticipantProcessorImpl.java:99) [jbossxts-4.15.3.Final.jar:] at com.arjuna.webservices11.wsat.sei.ParticipantPortTypeImpl$2.executeTask(ParticipantPortTypeImpl.java:84) [jbossxts-4.15.3.Final.jar:] at com.arjuna.services.framework.task.TaskWorker.run(TaskWorker.java:63) [jbossxts-4.15.3.Final.jar:] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] {code} Full server.log is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
13
0 / 0

[JBoss JIRA] (JBTM-920) remove PropertyPrefix requirement for EnvironmentBean classes

by Jonathan Halliday (Created) (JIRA)

remove PropertyPrefix requirement for EnvironmentBean classes ------------------------------------------------------------- Key: JBTM-920 URL: https://issues.jboss.org/browse/JBTM-920 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Common, Configuration Affects Versions: 5.0.0.M1, 4.15.3 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.15.4, 5.0.0.M2 BeanPopulator enforces the requirement that EnvironmentBean classes have a PropertyPrefix annotation, in order to ensure that all properties existing prior to beanification still function using their legacy representation post-beanification. However, this requirement is too stringent - new properties added in the post-beanification era neither have, nor should be required to have, a legacy representation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-907) fix timing in RecoveryDriver

by Jonathan Halliday (JIRA)

fix timing in RecoveryDriver ---------------------------- Key: JBTM-907 URL: https://issues.jboss.org/browse/JBTM-907 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 5.0.0.M1, 4.15.3 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.15.4, 5.0.0.M2 Default client timeout for sync scan requests is incorrect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-906) stub new jdbc methods for build on jdk7

by Jonathan Halliday (JIRA)

stub new jdbc methods for build on jdk7 --------------------------------------- Key: JBTM-906 URL: https://issues.jboss.org/browse/JBTM-906 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1, 4.15.3 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.15.4, 5.0.0.M2 The JDBC classes in Java 7 have some new methods. These need stubbing out in our transactional driver and test harness so we can build on jdk7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (JBTM-770) incorrect cleanup registration causes memory leak

by Jonathan Halliday (JIRA)

incorrect cleanup registration causes memory leak ------------------------------------------------- Key: JBTM-770 URL: https://jira.jboss.org/browse/JBTM-770 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.6.1.CP06, 4.12.0 Reporter: Jonathan Halliday Assignee: Mark Little Fix For: 4.13.0, 4.6.1.CP08 jts.TransactionImple constructors attempt to optimize the cleanup callback needed to remove entries from _transactions, bypassing the ORB for interposition scenarios: theTx = (TwoPhaseCoordinator) BasicAction.Current(); if (theTx != null) { theTx.addSynchronization(new LocalCleanupSynchronization(this)); } else { registerSynchronization(new CleanupSynchronization(this)); } Unfortunately this does not work and leads to memory leaks on _transactions in certain cases. Specifically, where theTx is a ServerTransaction (i.e. extends ArjunaTransactionImple, which extends TwoPhaseCoordinator), the callbacks run (by ArjunaTransactionImple.do[Before|After]Completion()) are those in ArjunaTransactionImple._syncs, not the masked ones in TwoPhaseCoordinator._syncs. Thus using TwoPhaseCoordinator.addSynchronization registers a callback which is never invoked. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

9
15
0 / 0

[JBoss JIRA] Created: (JBTM-852) Setting SettingVolatile store still creates an ObjectStore directory on the disk

by Mircea Markus (JIRA)

Setting SettingVolatile store still creates an ObjectStore directory on the disk --------------------------------------------------------------------------------- Key: JBTM-852 URL: https://issues.jboss.org/browse/JBTM-852 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.15.0 Reporter: Mircea Markus Priority: Minor Even when configuring {code:java} arjPropertyManager.getObjectStoreEnvironmentBean().setObjectStoreType(VolatileStore.class.getName()) {code} an "ObjectStore" directory is created on the disk. After discussing with JTM team this doesn't cause any real problem in the sense that nothing is written to the disk, but this is annoying and might create confusion between the users. A workaround would be to add the following configuration together with the previously mentioned one: {code:java} BeanPopulator.getNamedInstance(ObjectStoreEnvironmentBean.class, "communicationStore").setObjectStoreType(VolatileStore.class.getName()) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
21
0 / 0

[JBoss JIRA] Created: (JBTM-847) Look into how AssumedComplete works for ArjunaJTA (and jtax)

by Mark Little (JIRA)

Look into how AssumedComplete works for ArjunaJTA (and jtax) ------------------------------------------------------------ Key: JBTM-847 URL: https://issues.jboss.org/browse/JBTM-847 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Reporter: Mark Little Assignee: Tom Jenkinson When a transaction cannot be completed over a long period of time, a scanner is supposed to kick in and move the log elsewhere. Those scanners exist in ArjunaCore and ArjunaJTS, but do not appear to be there in ArjunaJTA. It should be straightforward to add them by using the base class in ArjunaCore, but investigate whether they are present already and just not obvious. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBTM-247) Update (if necessary) the new integration layer SPIs

by Mark Little (JIRA)

Update (if necessary) the new integration layer SPIs ---------------------------------------------------- Key: JBTM-247 URL: http://jira.jboss.com/jira/browse/JBTM-247 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Jonathan Halliday http://anonsvn.jboss.org/repos/jbossas/projects/integration/ -- 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

12 years, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-892) Document the usage of the shipped maven installation in the build instructions

by Tom Jenkinson (JIRA)

Document the usage of the shipped maven installation in the build instructions ------------------------------------------------------------------------------ Key: JBTM-892 URL: https://issues.jboss.org/browse/JBTM-892 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M2 Include info such as txmvn -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
12
0 / 0

[JBoss JIRA] Created: (JBTM-520) Include distribution information in MANIFEST.MF

by Jesper Pedersen (JIRA)

Include distribution information in MANIFEST.MF ----------------------------------------------- Key: JBTM-520 URL: https://jira.jboss.org/jira/browse/JBTM-520 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6.0 Reporter: Jesper Pedersen Priority: Minor It would be nice if the jar files contain information inside the MANIFEST.MF files - like Implementation-Title Implementation-Vendor Implementation-Vendor-Id Implementation-Version -- 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

12 years, 1 month

4
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2011