[JBoss JIRA] (JBTM-1211) Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1211?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris commented on JBTM-1211:
---------------------------------------
http://172.17.131.2/job/jbossts-EAP61/1540
> Fix qa suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
> ------------------------------------------------------------------------------
>
> Key: JBTM-1211
> URL: https://issues.jboss.org/browse/JBTM-1211
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTS, Testing, Transaction Core
> Affects Versions: 4.16.4
> Reporter: Paul Robinson
> Assignee: Michael Musgrove
> Fix For: 4.17.4, 5.0.0.M2
>
> Attachments: jbossts-narayana-java6-ipv6-dualstack.57.tar, jtsremote(1).zip, jtsremote.zip
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> See: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java6/232
> {code}
> Running org.jboss.jbossts.qa.junit.testgroup.TestGroup_jtsremote
> [junit] Tests run: 9, Failures: 1, Errors: 0, Time elapsed: 169.235 sec
> {code}
--
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, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Remaining Estimate: 3 days (was: 3 hours)
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 1 day, 5 hours
> Remaining Estimate: 3 days
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
>
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h5. TXF
> * Weld -> EJB3 -> Transactions
> * JBossWS. Might be able to remove by putting the WS specific stuff into the XTS subsystem.
> h2. Subsystem Breakdown
> Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
> h5. Transactions
> * All current stuff
> * STM
> * TXF (Unlikely to work due to dependency on Weld for loading a portable extension)
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)
--
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, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h5. TXF
* Weld -> EJB3 -> Transactions
* JBossWS. Might be able to remove by putting the WS specific stuff into the XTS subsystem.
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF (Unlikely to work due to dependency on Weld for loading a portable extension)
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
was:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h5. TXF
* Weld -> EJB3 -> Transactions
* JBossWS
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF (Unlikely to work due to dependency on Weld for loading a portable extension)
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
>
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h5. TXF
> * Weld -> EJB3 -> Transactions
> * JBossWS. Might be able to remove by putting the WS specific stuff into the XTS subsystem.
> h2. Subsystem Breakdown
> Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
> h5. Transactions
> * All current stuff
> * STM
> * TXF (Unlikely to work due to dependency on Weld for loading a portable extension)
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)
--
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, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h5. TXF
* Weld -> EJB3 -> Transactions
* JBossWS
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF (Unlikely to work due to dependency on Weld for loading a portable extension)
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
was:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h5. TXF
* Weld -> EJB3 -> Transactions
* JBossWS
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
>
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h5. TXF
> * Weld -> EJB3 -> Transactions
> * JBossWS
> h2. Subsystem Breakdown
> Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
> h5. Transactions
> * All current stuff
> * STM
> * TXF (Unlikely to work due to dependency on Weld for loading a portable extension)
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)
--
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, 2 months
[JBoss JIRA] (JBTM-1398) Review subsystem usage across Narayana
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1398?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1398:
--------------------------------
Description:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h5. TXF
* Weld -> EJB3 -> Transactions
* JBossWS
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
was:
h2. Components and their subsystem requirements:
h5. Transactions
* To Investigate
h5. XTS
* Bootstrap coordinator
* Setup WS endpoints for coordinator
* Setup WS endpoints for the participants
* Respond to configuration from standalone-xts.xml
h5. REST-TX
* Boostrap the coordinator
* Setup a REST endpoint for the coordinator
* Setup a REST endpoint for the participants
h5. Blacktie
* Register MDB
* Register MBean
h5. STM
* To Investigate
h5. TXF
* Modify the WS handler chain on application deployment
* Registers a CDI extension
h2. Notable Dependencies
h5. TXF
* Weld
* JBossWS
h2. Subsystem Breakdown
Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
h5. Transactions
* All current stuff
* STM
* TXF
h5. XTS
* All Current Stuff
h5. RTS (new)
h5. Blacktie (new)
> Review subsystem usage across Narayana
> --------------------------------------
>
> Key: JBTM-1398
> URL: https://issues.jboss.org/browse/JBTM-1398
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 2 days
> Time Spent: 6 hours
> Remaining Estimate: 1 day, 2 hours
>
> h2. Components and their subsystem requirements:
> h5. Transactions
> * To Investigate
>
> h5. XTS
> * Bootstrap coordinator
> * Setup WS endpoints for coordinator
> * Setup WS endpoints for the participants
> * Respond to configuration from standalone-xts.xml
> h5. REST-TX
> * Boostrap the coordinator
> * Setup a REST endpoint for the coordinator
> * Setup a REST endpoint for the participants
> h5. Blacktie
> * Register MDB
> * Register MBean
> h5. STM
> * To Investigate
> h5. TXF
> * Modify the WS handler chain on application deployment
> * Registers a CDI extension
> h2. Notable Dependencies
> h5. TXF
> * Weld -> EJB3 -> Transactions
> * JBossWS
> h2. Subsystem Breakdown
> Providing we can have 'soft' dependencies it would seem favourable to have all the core features in the transactions subsystem and the optional 'transports' in additional subsystems.
> h5. Transactions
> * All current stuff
> * STM
> * TXF
> h5. XTS
> * All Current Stuff
> h5. RTS (new)
> h5. Blacktie (new)
--
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, 2 months