[JBoss JIRA] Created: (JBTM-693) Object Store Browser mbean does not initialise properly
by Michael Musgrove (JIRA)
Object Store Browser mbean does not initialise properly
-------------------------------------------------------
Key: JBTM-693
URL: https://jira.jboss.org/jira/browse/JBTM-693
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Tooling
Affects Versions: 4.9.0
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Minor
Fix For: 4.10.0
The default com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBean does not initialise itself properly when running in the AS causing a null pointer reference when displaying the bean in a JMX client.
Also the need for the jmxEnabled property of ObjectStoreEnvironmentBean is superfluous.
See workaround for how to initialise the bean via transaction-jboss-beans.xml.
--
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
14 years, 10 months
[JBoss JIRA] Created: (JBTM-679) Enable use of maven to import external lib jars into XTS
by Andrew Dinn (JIRA)
Enable use of maven to import external lib jars into XTS
--------------------------------------------------------
Key: JBTM-679
URL: https://jira.jboss.org/jira/browse/JBTM-679
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 4.9.0
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.10.0
The XTS build process employs a variety of external jars:
JBossTS jars
JBossWS jars (including Java EE API jars, JBossWS native jars and CXF jars)
JBossAS jars (including Java EE API jars)
other java jars (junit)
The build process should normally employ the JBossTS jars produced by building JBossTS in the source tree containing XTS as a subtree. However, in the case of the other sets of jars it should be possible to build XTS with a guarantee that the build employs known versions of each of the required jars.
This should be achieved using maven to resolve dependencies and download the required jars. In the case of the AS and WS jars the versions should be derived from the component-matrix pom associated with a specific version of the AS to which the XTS and TS tree is matched.
--
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
14 years, 10 months
[JBoss JIRA] Created: (JBTM-377) XAResourceRecord save/restore state insufficiently paranoid
by Jonathan Halliday (JIRA)
XAResourceRecord save/restore state insufficiently paranoid
-----------------------------------------------------------
Key: JBTM-377
URL: http://jira.jboss.com/jira/browse/JBTM-377
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.0.GA
Reporter: Jonathan Halliday
Fix For: 4.4.CR2
The XAResourceRecord save state method writes meta-data into the objectstore before attempting to Serialize and write the actual bytes for an XAResource that it believes, on the basis of it implementing the market interface, is Serializable. If the serialization fails at runtime, the objectstore record is left in an invalid state and can cause the recovery pass to blow up in horrible ways.
We should obtain the byte[] representing the serialized resource before writing anything to the record so that this does not occur. If serialization fails, the record will therefore be useless but at least not otherwise broken.
--
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
14 years, 10 months