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.…
[View More]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
[View Less]
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'…
[View More]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
[View Less]
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-…
[View More]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
[View Less]
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.…
[View More]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
[View Less]
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 …
[View More]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
[View Less]
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 …
[View More]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
[View Less]
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
…
[View More]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
[View Less]
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 …
[View More]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
[View Less]
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
…
[View More]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
[View Less]
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)
…
[View More]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
[View Less]