March 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-651) Mavenize JBoss Transactional File IO project

by jaikiran pai (JIRA)

Mavenize JBoss Transactional File IO project -------------------------------------------- Key: JBTM-651 URL: https://jira.jboss.org/jira/browse/JBTM-651 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: jaikiran pai JBoss Transactional File IO project http://www.jboss.org/jbosstm/fileio/ currently is not available in the Maven repo. Making it available in the Maven repo would help other (Maven based) projects to easily consume it. -- 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

11 years, 6 months

5
16
0 / 0

[JBoss JIRA] (JBTM-957) NullPointerException found in com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple

by David Lloyd (Created) (JIRA)

NullPointerException found in com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple -------------------------------------------------------------------------------------------------------- Key: JBTM-957 URL: https://issues.jboss.org/browse/JBTM-957 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.15.3 Reporter: David Lloyd Priority: Minor com.arjuna.ats.internal.jts.orbspecific.coordinator.ArjunaTransactionImple's doBeforeCompletion() method assumes that the "controlHandle" field is initialized to a non-null value. However, com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl does not do said initialization despite the fact that the apparent contract published in com.arjuna.ats.internal.jts.orbspecific.ControlImple specifies that "The derived classes are responsible for setting everything up, including adding the control to the list of controls...". -- 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

11 years, 6 months

8
11
0 / 0

[JBoss JIRA] (JBTM-993) update HornetQ journal array value handling

by Jonathan Halliday (Created) (JIRA)

update HornetQ journal array value handling ------------------------------------------- Key: JBTM-993 URL: https://issues.jboss.org/browse/JBTM-993 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 4.15.3 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.16.0.Beta1 Fix possible race condition in data array handling. -- 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

11 years, 6 months

4
5
0 / 0

[JBoss JIRA] (JBTM-1064) The coordinator can throw a ConcurrentModificationException during transaction termination

by Radesh Rao (JIRA)

Radesh Rao created JBTM-1064: -------------------------------- Summary: The coordinator can throw a ConcurrentModificationException during transaction termination Key: JBTM-1064 URL: https://issues.jboss.org/browse/JBTM-1064 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M1 Reporter: Radesh Rao Assignee: Michael Musgrove Throws the following exception: java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$KeyIterator.next(HashMap.java:828) at org.jboss.jbossts.star.service.Coordinator.terminateTransaction(Coordinator.java:331) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) -- 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

11 years, 6 months

3
5
0 / 0

[JBoss JIRA] (JBTM-960) Change "ARJUNA12140: Adding multiple last resources is disallowed" warning and show underlying resource instead of LastResourceRecord

by Scott Marlow (Created) (JIRA)

Change "ARJUNA12140: Adding multiple last resources is disallowed" warning and show underlying resource instead of LastResourceRecord ------------------------------------------------------------------------------------------------------------------------------------- Key: JBTM-960 URL: https://issues.jboss.org/browse/JBTM-960 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 4.15.3 Reporter: Scott Marlow Assignee: Jonathan Halliday As discussed on IRC, change the ARJUNA12140 warning from the current: " ARJUNA12140: Adding multiple last resources is disallowed. Current resource is com.arjuna.ats.internal.arjuna.abstractrecords.LastResourceRecord@xxxxx " To: " Enlisting multiple non-XA resources into transaction is not allowed. Tried to enlist resource %s when resource %s is already enlisted. " Instead of showing the LastResourceRecord, it would help reduce the time it takes to locate the root cause, if we showed the underlying resources in the warning message. -- 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

11 years, 6 months

4
5
0 / 0

[JBoss JIRA] (JBTM-991) update arjunacore EnvironmentBeans

by Jonathan Halliday (Created) (JIRA)

update arjunacore EnvironmentBeans ---------------------------------- Key: JBTM-991 URL: https://issues.jboss.org/browse/JBTM-991 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Transaction Core Affects Versions: 4.15.3 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.16.0.Beta1 Update config beans to reflect obsolete and modified properties -- 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

11 years, 6 months

4
5
0 / 0

[JBoss JIRA] (JBTM-924) recovery leaks xaresources

by Jonathan Halliday (Created) (JIRA)

recovery leaks xaresources -------------------------- Key: JBTM-924 URL: https://issues.jboss.org/browse/JBTM-924 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 5.0.0.M1, 4.15.3, 4.6.1.CP12 Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.6.1.CP13, 4.15.4, 5.0.0.M2 XARecoveryModule._xidScans may grow without limit in cases where an xa recovery plugin is both a) returning new XAResources rather than validiating and reusing the previous one and b) the isSameRM implementation provided by the driver is unable to recognize the equivalence of two such XAResources. To prevent such leakage we should remove any scan entries that have not been updated recently, thus ensuring expiration of entries that are not refreshed by the refreshXidScansForEquivalentXAResourceImpl correlation mechanism. -- 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

11 years, 6 months

3
4
0 / 0

[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

11 years, 6 months

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

11 years, 6 months

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

11 years, 6 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2012