[JBoss JIRA] (JBTM-1469) Move TXBridge quickstart into JDF
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1469?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1469:
--------------------------------
Original Estimate: 2 days
Remaining Estimate: 2 days
Assignee: Paul Robinson
> Move TXBridge quickstart into JDF
> ---------------------------------
>
> Key: JBTM-1469
> URL: https://issues.jboss.org/browse/JBTM-1469
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: TxBridge, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M3
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> TXBridge is now supported, so we can move one or more of the quickstarts across to JDF. We should first run this by Pete and get a JDF Jira created, then link this one through.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1460) TXBridge test hangs when Arquillian starts the container
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1460?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1460:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M3)
> TXBridge test hangs when Arquillian starts the container
> --------------------------------------------------------
>
> Key: JBTM-1460
> URL: https://issues.jboss.org/browse/JBTM-1460
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: AS7 master as of 2013-02-05
> Arquillian core: 1.0.0.Final
> Arquillian osgi: 1.0.2.Final
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.Final
>
> Attachments: client.log, server.log
>
>
> See: 172.17.131.2/job/btny-pulls-narayana/345/ where the job has hung for about 16hrs.
> From looking at the stack trace in client.log (attached):
> {code}
> at org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:107)
> at org.jboss.jbossts.txbridge.tests.inbound.junit.InboundBasicTests.setUp(InboundBasicTests.java:75)
> {code}
> The hang is happening on this line:
> {code}
> controller.start(CONTAINER);
> {code}
> Which is starting the container 'jboss', which is described in the arquillian.xml as:
> {code}
> <container qualifier="jboss" default="true" mode="manual">
> <configuration>
> <property name="javaVmArguments">${server.jvm.args}</property>
> <property name="serverConfig">standalone-xts.xml</property>
> <property name="managementAddress">${node.address}</property>
> </configuration>
> </container>
> {code}
> From looking at server.log (attached) it looks like the server has started and deployed the deployments:
> First of two deployments:
> {code}
> 18:36:32,013 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "txbridge-inbound-tests-service.war" (runtime-name : "txbridge-inbound-tests-service.war")
> {code}
> Second of two deployments:
> {code}
> 18:36:32,975 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "txbridge-inbound-tests-client.war" (runtime-name : "txbridge-inbound-tests-client.war")
> {code}
> Notice that the output above is that last line of output on the server.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1509) Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror:
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1509?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-1509.
---------------------------------
Resolution: Done
> Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror:
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1509
> URL: https://issues.jboss.org/browse/JBTM-1509
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Affects Versions: 4.6.1.CP12
> Environment: JBoss EAP 5.1.2
> Reporter: Tom Ross
> Assignee: Tom Jenkinson
> Fix For: 4.6.1.CP14
>
>
> JBoss TM prints a warning
> 17/01/13 09:18:48.672 WARN com.arjuna.ats.jta.logging.loggerI18N 5952 Thread-63 (Horn a9f5517:e5ec:50f6e612:14491 Can't find resource for bundle java.util.PropertyResourceBundle, key com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror: [key='com.arjuna.ats.internal.jta.transaction.arjunacore.timeouterror']TransactionImple.enlistResource, XAException.XAER_RMERR, < 131075, 41, 27, 80798279834849954953484848459757102535349555810153101995853481025410154495058495252574997571025353495558101531019958534810254101544950584952529850 >
> due to corrupted resource string
--
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
11 years, 9 months
[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:
--------------------------------
Fix Version/s: 5.0.0.M3
(was: 5.0.0.Final)
> 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: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M3
>
> Attachments: test-ds.xml, transaction.xml
>
> Original Estimate: 3 days
> Time Spent: 6 hours
> Remaining Estimate: 2 days, 2 hours
>
> 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
> }
> }
> Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar.
--
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
11 years, 9 months
[JBoss JIRA] (JBTM-1330) Support Last Logging Resource
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1330?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1330:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M3)
> Support Last Logging Resource
> -----------------------------
>
> Key: JBTM-1330
> URL: https://issues.jboss.org/browse/JBTM-1330
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
> LLR
> ===
> xar1::prepare(); // sync 1
> ds1::insert(tmLog) ds1::commit() // sync 2
> xar1::commit(); // sync 3
> lazily remove (tmLog) // sync 4
> XA
> ==
> xar1::prepare(); // sync 1
> xar2::prepare(); // sync 2
> tm::log() // sync 3
> xar1::commit() // sync 4
> xar2::commit() // sync 5
> (potentally lazily) remove (tmLog) // sync 6
--
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
11 years, 9 months