[JBoss JIRA] (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-622?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson commented on JBTM-622:
------------------------------------
Brain dump: Can we use the EIS name along with XID to guarantee uniqueness?
> Support for crash recovery of tx-inflow with multiple resource managers
> -----------------------------------------------------------------------
>
> Key: JBTM-622
> URL: https://issues.jboss.org/browse/JBTM-622
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JCA, Recovery, Transaction Core
> Affects Versions: 4.2.3.CP06
> Reporter: Toshiya Kobayashi
> Priority: Minor
>
> JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs.
> In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBTM-622) Support for crash recovery of tx-inflow with multiple resource managers
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-622?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson commented on JBTM-622:
------------------------------------
We might want to raise a Jira here: http://java.net/jira/browse/CONNECTOR_SPEC
> Support for crash recovery of tx-inflow with multiple resource managers
> -----------------------------------------------------------------------
>
> Key: JBTM-622
> URL: https://issues.jboss.org/browse/JBTM-622
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JCA, Recovery, Transaction Core
> Affects Versions: 4.2.3.CP06
> Reporter: Toshiya Kobayashi
> Priority: Minor
>
> JCA tx-inflow spec allows the external EIS to provide the Xid for the inflowed transaction. The TM handling the inflowed (i.e. subordinate) transaction uses this Xid verbatim when talking to RMs.
> In current implementation, each RM enlisted in the subordinate tx will see the same Xid as originally provided by the EIS. This screws recovery where multiple resources are involved, since a given Xid no longer belongs to exactly one RM, but may be shared by several. We can no longer return a single XAResource to drive the recovery for a given Xid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1479:
--------------------------------
Description:
See JBTM-809 for the algorithm
You might want to put the startup in the context listener:
public class MyServletContextListener implements ServletContextListener {
public void contextInitialized(ServletContextEvent sce) {
// Initialize RecoveryManager
// Initialize TransactionManager
// Initialize IronJacamar
}
@Override
public void contextDestroyed(ServletContextEvent sce) {
// Clean IronJacamar
// Clean TransactionManager
// Clean RecoveryManager
}
}
was:See JBTM-809 for the algorithm
> Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
> -------------------------------------------------------------------------
>
> Key: JBTM-1479
> URL: https://issues.jboss.org/browse/JBTM-1479
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Attachments: test-ds.xml, transaction.xml
>
>
> See JBTM-809 for the algorithm
> You might want to put the startup in the context listener:
> public class MyServletContextListener implements ServletContextListener {
> public void contextInitialized(ServletContextEvent sce) {
> // Initialize RecoveryManager
> // Initialize TransactionManager
> // Initialize IronJacamar
> }
>
> @Override
> public void contextDestroyed(ServletContextEvent sce) {
> // Clean IronJacamar
> // Clean TransactionManager
> // Clean RecoveryManager
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBTM-809) Replace transactional driver with ironjacamar
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-809?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated JBTM-809:
-------------------------------
Description:
The general approach would be along the lines of:
Startup
======
Embedded embedded = EmbeddedFactory.create();
embedded.startup();
embedded.deploy(new File("my-rar.rar").toURI().toURL());
embedded.deploy(new File("my-ds.xml").toURI().toURL());
In use
=====
InitialContext initialContext = new InitialContext();
UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
Shutdown
=======
embedded.undeploy(new File("my-ds.xml").toURI().toURL());
embedded.undeploy(new File("my-rar.rar").toURI().toURL());
embedded.shutdown(); // does not work - some threads don't stop
Problems?
=========
JCA transitive dependencies?
Accessing ds files from war?
Accessing rar from war?
May have to provide these both upfront.
was:Evaluate JCA replacement for transactional jdbc driver and do the work
> Replace transactional driver with ironjacamar
> ---------------------------------------------
>
> Key: JBTM-809
> URL: https://issues.jboss.org/browse/JBTM-809
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Resource Manager
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> The general approach would be along the lines of:
> Startup
> ======
> Embedded embedded = EmbeddedFactory.create();
> embedded.startup();
> embedded.deploy(new File("my-rar.rar").toURI().toURL());
> embedded.deploy(new File("my-ds.xml").toURI().toURL());
> In use
> =====
> InitialContext initialContext = new InitialContext();
> UserTransaction ut = (UserTransaction)initialContext.lookup("UserTransaction");
> DataSource dataSource = (DataSource)initialContext.lookup("java:/"+"TestDS");
> Shutdown
> =======
> embedded.undeploy(new File("my-ds.xml").toURI().toURL());
> embedded.undeploy(new File("my-rar.rar").toURI().toURL());
> embedded.shutdown(); // does not work - some threads don't stop
> Problems?
> =========
> JCA transitive dependencies?
> Accessing ds files from war?
> Accessing rar from war?
> May have to provide these both upfront.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBTM-1476) Document new XTS Features
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1476?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1476:
--------------------------------
Description:
Plan for new XTS features and docs:
# Implement new feature
# Release a milestone of 5.0.0
# Publish a blog post shortly after release
# Refine the feature based on community feedback
# Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item)
Here's a list of features that need documenting, so far:
JBTM-986 Automatically setup the client side handler chain
JBTM-1447 Create WebserviceFeature for TXBridge
New API for WS-AT (JTA) and WS-AB
was:
Plan for new XTS features and docs:
# Implement new feature
# Release a milestone of 5.0.0
# Publish a blog post shortly after release
# Refine the feature based on community feedback
# Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item)
Here's a list of features that need documenting, so far:
JBTM-986 Automatically setup the client side handler chain
JBTM-1447 Create WebserviceFeature for TXBridge
> Document new XTS Features
> -------------------------
>
> Key: JBTM-1476
> URL: https://issues.jboss.org/browse/JBTM-1476
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Fix For: 5.0.0.Final
>
>
> Plan for new XTS features and docs:
> # Implement new feature
> # Release a milestone of 5.0.0
> # Publish a blog post shortly after release
> # Refine the feature based on community feedback
> # Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item)
> Here's a list of features that need documenting, so far:
> JBTM-986 Automatically setup the client side handler chain
> JBTM-1447 Create WebserviceFeature for TXBridge
> New API for WS-AT (JTA) and WS-AB
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBTM-1476) Document new XTS Features
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1476?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1476:
--------------------------------
Description:
Plan for new XTS features and docs:
# Implement new feature
# Release a milestone of 5.0.0
# Publish a blog post shortly after release
# Refine the feature based on community feedback
# Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item)
Here's a list of features that need documenting, so far:
JBTM-986 Automatically setup the client side handler chain
JBTM-1447 Create WebserviceFeature for TXBridge
New API for WS-AT (JTA) and WS-BA
was:
Plan for new XTS features and docs:
# Implement new feature
# Release a milestone of 5.0.0
# Publish a blog post shortly after release
# Refine the feature based on community feedback
# Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item)
Here's a list of features that need documenting, so far:
JBTM-986 Automatically setup the client side handler chain
JBTM-1447 Create WebserviceFeature for TXBridge
New API for WS-AT (JTA) and WS-AB
> Document new XTS Features
> -------------------------
>
> Key: JBTM-1476
> URL: https://issues.jboss.org/browse/JBTM-1476
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Paul Robinson
> Fix For: 5.0.0.Final
>
>
> Plan for new XTS features and docs:
> # Implement new feature
> # Release a milestone of 5.0.0
> # Publish a blog post shortly after release
> # Refine the feature based on community feedback
> # Document the feature in the XTS xts_administration_and_development_guide before the 5.0.0.Final release (this issue is to do this item)
> Here's a list of features that need documenting, so far:
> JBTM-986 Automatically setup the client side handler chain
> JBTM-1447 Create WebserviceFeature for TXBridge
> New API for WS-AT (JTA) and WS-BA
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] (JBTM-1478) Squash all 5_BRANCH commits into logical groups
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1478:
-----------------------------------
Summary: Squash all 5_BRANCH commits into logical groups
Key: JBTM-1478
URL: https://issues.jboss.org/browse/JBTM-1478
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Application Server Integration
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
Before we raise a pull request for our AS changes to M2, we need to reduce the number of commits. To do this we should squash them into logical groups. E.g. TXFramework, artefact name changes and version numbers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month