October 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-738) Remove log4j.properties from jbossjts.jar

by Jesper Pedersen (JIRA)

Remove log4j.properties from jbossjts.jar ----------------------------------------- Key: JBTM-738 URL: https://jira.jboss.org/jira/browse/JBTM-738 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.9.0 Reporter: Jesper Pedersen Priority: Minor The archive jbossjts.jar contains a log4j.properties file, which creates a transaction.log file. It can be disabled by specifying -Dlog4j.defaultInitOverride=true, but that is not always possible for some Ant tasks, like checkstyle. Hence an empty file is created. It would nice to have the logging configuration outside of the archive. -- 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, 2 months

5
10
0 / 0

[JBoss JIRA] Created: (JBTM-248) Generic compensation annotations

by Mark Little (JIRA)

Generic compensation annotations -------------------------------- Key: JBTM-248 URL: http://jira.jboss.com/jira/browse/JBTM-248 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Implementation Affects Versions: 4.2.3.SP5 Reporter: Mark Little Assigned To: Mark Little We're working on WS-BA based compensation annotations. That's great, but can we refactor so that we can support compensations outside of WS-BA? ArjunaCore can support compensations without Web Services. Maybe the WS-BA annotations vanish entirely, or collapse down to a subset of what currently exists to support what is truly unique about WS-BA? -- 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, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBTM-869) Document XTS standalone

by Tom Jenkinson (JIRA)

Document XTS standalone ----------------------- Key: JBTM-869 URL: https://issues.jboss.org/browse/JBTM-869 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Paul Robinson The documentation goes in ROOT/XTS/docs/installation_and_administratio.../ The docs are docbook, check other docs for details Update narayana/trunk/narayana-full/readme.txt to not link to the forum posting You can consult this community thread for raw data: http://community.jboss.org/message/554385#554385 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBTM-838) get.drivers task in qa/build.xml is failing due to "java.net.UnknownHostException: reports.qa.atl.jboss.com

by Ivo Studensky (JIRA)

get.drivers task in qa/build.xml is failing due to "java.net.UnknownHostException: reports.qa.atl.jboss.com ----------------------------------------------------------------------------------------------------------- Key: JBTM-838 URL: https://issues.jboss.org/browse/JBTM-838 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6.1.CP11, 4.15.0 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.6.1.CP12, 4.15.1 There has been a change in a lot of domain names recently and all the atl.jboss.com domains have been decommissioned. Hence, the get.drivers target in qa/build.xml needs to be updated with a new domain name. The domain name corresponding to the reports.qa.atl.jboss.com is now www.qa.jboss.com. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

6
11
0 / 0

[JBoss JIRA] (JBTM-934) Ensure that Narayana (trunk) can build a JTS that works with the JDK ORB

by Tom Jenkinson (Created) (JIRA)

Ensure that Narayana (trunk) can build a JTS that works with the JDK ORB ------------------------------------------------------------------------ Key: JBTM-934 URL: https://issues.jboss.org/browse/JBTM-934 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson It is suggested to make use of *maven profiles* that determine which ORB to test against and potentially build against. -- 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, 2 months

8
22
0 / 0

[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

12 years, 2 months

5
16
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

12 years, 2 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

12 years, 2 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

12 years, 2 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

12 years, 2 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 October 2011