[JBoss JIRA] Created: (JBTM-289) remove use of Synchronizations for lock storage in jboss integration
by Jonathan Halliday (JIRA)
remove use of Synchronizations for lock storage in jboss integration
--------------------------------------------------------------------
Key: JBTM-289
URL: http://jira.jboss.com/jira/browse/JBTM-289
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTA Implementation
Affects Versions: 4.2.3.SP5
Reporter: Jonathan Halliday
Assigned To: Jonathan Halliday
Fix For: 4.2.3.SP6
JBossAS needs to be able to lock transactions regardless of their state. Since the current integration implementation uses Synchronizations to store lock state, locking is possible only during transactions lifecycle phases where Synchronization registration is permitted. Relax this by changing the integration so that locks are stored using the general object storage mechanism added to TransactionImple to support JTA 1.1.
--
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
16 years, 6 months
[JBoss JIRA] Created: (JBTM-253) Listen address of JBossTS ports not configurable
by Arto Huusko (JIRA)
Listen address of JBossTS ports not configurable
------------------------------------------------
Key: JBTM-253
URL: http://jira.jboss.com/jira/browse/JBTM-253
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Transaction Core
Affects Versions: 4.2.3.SP3
Environment: JBoss AS 4.2.0 GA
Reporter: Arto Huusko
Assigned To: Mark Little
JBossTS integrated in JBoss AS 4.2.0 GA always binds some tcp ports to listen on all addresses. jboss.bind.address has no effect on the listen address, nor is it otherwise configurable.
Looking at source code (for example ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/recovery/TransactionStatusManager.java in jbossts-jta-4.2.3.SP3-src.zip) confirms that there is no kind of support for binding the listen address, only the port can be freely selected.
The listen address should be configurable, so that it can be limited to localhost, for example.
In addition, if possible, it would be nice to be able to disable listening on any ports. I'm not sure if the TransactionStatusManager really needs to listen on any port in a simple JBoss AS installation.
--
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
16 years, 7 months