Implement tests for WS-AT subordinate transaction recovery
----------------------------------------------------------
Key: JBTM-447
URL: https://jira.jboss.org/jira/browse/JBTM-447
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: WS-T Implementation
Affects Versions: 4.5
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.6
--
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
Implement test suite for WS-BA coordinator and participant recovery
-------------------------------------------------------------------
Key: JBTM-431
URL: https://jira.jboss.org/jira/browse/JBTM-431
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: WS-T Implementation
Affects Versions: 4.5
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.6
Now that WS-BA recovery is available it needs to be tested thoroughly, preferably via an automated process.
--
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
Implement test suite for WS-AT coordinator and participant recovery
-------------------------------------------------------------------
Key: JBTM-387
URL: https://jira.jboss.org/jira/browse/JBTM-387
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.4.CR2
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Now that WS-AT recovery is available it needs to be tested thoroughly, preferably via an automated process.
--
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
Socket process id binds to the wrong interface
----------------------------------------------
Key: JBTM-412
URL: https://jira.jboss.org/jira/browse/JBTM-412
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Application Server Integration
Affects Versions: 4.4.0.GA, 4.4.CR2, 4.4.CR1, 4.5
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 4.5
If working offline, i.e. no eth0/network, and jboss is started on localhost then the server doesn't boot because SocketProcessId is binding to the wrong interface - InetAddress getByName(null) should be used instead of InetAddress.getLocalHost()
--
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
WS-BA coordinator interposition support
---------------------------------------
Key: JBTM-409
URL: https://jira.jboss.org/jira/browse/JBTM-409
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.4.0.GA
Reporter: Jonathan Halliday
Assignee: Andrew Dinn
Fix For: 4.5
--
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
admin guide shows wrong class name for Facility Codes
-----------------------------------------------------
Key: JBTM-458
URL: https://jira.jboss.org/jira/browse/JBTM-458
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: John Mazzitelli
Priority: Minor
In the Administrators Guide:
http://www.jboss.org/jbosstm/docs/4.2.3/manuals/html/core/AdministrationG...
it says this:
"Facility Code - JBossTS uses the following values defined in the class com.arjuna.common.util.logging.VisibilityLevel"
It then lists the several FAC_xxx facility codes like FAC_ATOMIC_ACTION and others.
These are not defined in the VisibilityLevel class. I think the full class name specified here should be:
com.arjuna.ats.arjuna.logging.FacilityCode
--
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
Fix labs text
-------------
Key: JBTM-315
URL: http://jira.jboss.com/jira/browse/JBTM-315
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.3.0.BETA2
Reporter: Mark Little
Assigned To: Mark Little
Priority: Trivial
"JBoss Transactions is founded on industry proven technology and an 18 year history as a leader in distributed transactions."
Was true 2 years ago. Needs to say 20+ now.
--
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
Make sure JDBC text is clear that it should only be used outside of application servers
---------------------------------------------------------------------------------------
Key: JBTM-283
URL: http://jira.jboss.com/jira/browse/JBTM-283
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP5
Reporter: Mark Little
Assigned To: Mark Little
--
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
Make sure it is clear that JBossTS can be used outside of an application server
-------------------------------------------------------------------------------
Key: JBTM-332
URL: http://jira.jboss.com/jira/browse/JBTM-332
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: Mark Little
Assigned To: Mark Little
--
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
documentation issue: wrong name for cachestore in JBoss_TS_Programmers_Guide
----------------------------------------------------------------------------
Key: JBTM-445
URL: https://jira.jboss.org/jira/browse/JBTM-445
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Reporter: John Mazzitelli
Priority: Minor
http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4....
"The cached store
...
If overriding the object store implementation, the type of this object store is CachedStore."
That's the wrong name of the type. I got a warning in the logs saying it can't find the class for "CachedStore"
Server started up fine and started using the cache store when I used "CacheStore" instead (notice - without the 'd').
--
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