[JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1838?focusedWorklogId=12429505&page=... ]
Paul Robinson logged work on JBTM-1838:
---------------------------------------
Author: Paul Robinson
Created on: 22/Jul/13 12:19 PM
Start Date: 22/Jul/13 12:19 PM
Worklog Time Spent: 1 day
Issue Time Tracking
-------------------
Remaining Estimate: 4 hours (was: 1 day)
Time Spent: 1 day
Worklog Id: (was: 12429505)
> Document how to configure XTS to use SSL
> ----------------------------------------
>
> Key: JBTM-1838
> URL: https://issues.jboss.org/browse/JBTM-1838
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, Documentation
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4
>
> Original Estimate: 1 day
> Time Spent: 1 day
> Remaining Estimate: 4 hours
>
> The documentation should show how to use 'https' for all communications.
> I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS.
> We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart.
> Other options are a community wiki page or blog posting.
--
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
12 years, 8 months
[JBoss JIRA] (JBTM-1838) Document how to configure XTS to use SSL
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1838?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1838:
--------------------------------
Description:
The documentation should show how to use 'https' for all communications.
I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS.
We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart.
Other options are a community wiki page or blog posting.
was:The documentation should show how to use 'https' for all communications in the example.
> Document how to configure XTS to use SSL
> ----------------------------------------
>
> Key: JBTM-1838
> URL: https://issues.jboss.org/browse/JBTM-1838
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, Documentation
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M4
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> The documentation should show how to use 'https' for all communications.
> I'm not sure what form the documentation should take. Given that the majority of configuration is actually related to enabling SSL for Web Services in general, I don't think it should all live in the XTS docs. Maybe we just add the XTS specific stuff there and link to the docs on how to enable SSL for WS.
> We could also provide a JDF quickstart. However, the docs comprise of many bash commands, so this may not fit in well with a quickstart.
> Other options are a community wiki page or blog posting.
--
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
12 years, 8 months
[JBoss JIRA] (JBTM-1857) TestBASubordinateCrashDuringComplete hangs
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1857:
-------------------------------------
Summary: TestBASubordinateCrashDuringComplete hangs
Key: JBTM-1857
URL: https://issues.jboss.org/browse/JBTM-1857
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing, XTS
Reporter: Gytis Trikleris
Assignee: Paul Robinson
Priority: Minor
Fix For: 4.17.8
http://172.17.131.2/job/jbossts-EAP61-jdbcobjectstore/DB_TYPE=oracle,jdk=...
{code}
Running com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete
2013-07-22 07:07:16
Full thread dump Java HotSpot(TM) 64-Bit Server VM (20.12-b01 mixed mode):
"Thread-104" prio=10 tid=0x00007fcab126c000 nid=0x487f runnable [0x00007fcaaeb46000]
java.lang.Thread.State: RUNNABLE
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:220)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
- locked <0x00000000dd968c88> (a java.io.InputStreamReader)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
- locked <0x00000000dd968c88> (a java.io.InputStreamReader)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:129)
"Thread-103" prio=10 tid=0x00007fcab0823800 nid=0x487d runnable [0x00007fcaaed48000]
java.lang.Thread.State: RUNNABLE
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:220)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
- locked <0x00000000dd96ada0> (a java.io.BufferedInputStream)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
- locked <0x00000000dd96adf8> (a java.io.InputStreamReader)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
- locked <0x00000000dd96adf8> (a java.io.InputStreamReader)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:129)
"process reaper" daemon prio=10 tid=0x00007fcab106f000 nid=0x487b runnable [0x00007fcaaec47000]
java.lang.Thread.State: RUNNABLE
at java.lang.UNIXProcess.waitForProcessExit(Native Method)
at java.lang.UNIXProcess.access$900(UNIXProcess.java:20)
at java.lang.UNIXProcess$1$1.run(UNIXProcess.java:132)
"ThreadedStreamConsumer" prio=10 tid=0x00007fcab030f000 nid=0x487a waiting on condition [0x00007fcaaee49000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000dd9c4688> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at org.apache.maven.surefire.util.internal.Java15BlockingQueue.take(Java15BlockingQueue.java:40)
at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:68)
at java.lang.Thread.run(Thread.java:662)
"resolver-5" daemon prio=10 tid=0x00007fcab0f86000 nid=0x45fc waiting on condition [0x00007fcaaef4a000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000dab57588> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"resolver-4" daemon prio=10 tid=0x00007fcab0c05800 nid=0x44a1 waiting on condition [0x00007fcaaf04b000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000dab57588> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"resolver-3" daemon prio=10 tid=0x00007fcab0c11800 nid=0x44a0 waiting on condition [0x00007fcaaf14c000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000dab57588> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"resolver-2" daemon prio=10 tid=0x00007fcab0981800 nid=0x449f waiting on condition [0x00007fcaaf24d000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000dab57588> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"resolver-1" daemon prio=10 tid=0x00007fcab0dff800 nid=0x449e waiting on condition [0x00007fcaaf65f000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000dab57588> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:662)
"Low Memory Detector" daemon prio=10 tid=0x00007fcab0088000 nid=0x449a runnable [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"C2 CompilerThread1" daemon prio=10 tid=0x00007fcab0085800 nid=0x4499 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"C2 CompilerThread0" daemon prio=10 tid=0x00007fcab0083800 nid=0x4498 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Signal Dispatcher" daemon prio=10 tid=0x00007fcab0081000 nid=0x4497 waiting on condition [0x0000000000000000]
java.lang.Thread.State: RUNNABLE
"Finalizer" daemon prio=10 tid=0x00007fcab0064800 nid=0x4496 in Object.wait() [0x00007fcaafc65000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000daaa0460> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
- locked <0x00000000daaa0460> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x00007fcab0062800 nid=0x4495 in Object.wait() [0x00007fcaafd66000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000daaa0500> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:485)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x00000000daaa0500> (a java.lang.ref.Reference$Lock)
"main" prio=10 tid=0x00007fcab0007000 nid=0x4493 in Object.wait() [0x00007fcab7e58000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000000dd96aeb8> (a java.lang.UNIXProcess)
at java.lang.Object.wait(Object.java:485)
at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165)
- locked <0x00000000dd96aeb8> (a java.lang.UNIXProcess)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:151)
at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:88)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:191)
at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:98)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:199)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:176)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:134)
at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:97)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
"VM Thread" prio=10 tid=0x00007fcab005c000 nid=0x4494 runnable
"VM Periodic Task Thread" prio=10 tid=0x00007fcab0093000 nid=0x449b waiting on condition
JNI global references: 1080
{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
12 years, 8 months
[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ]
Michael Musgrove commented on JBTM-1855:
----------------------------------------
The problem is that there may be no JTS transaction. The RTS transaction could be started on any server and is most likely just a standard JTA (non JTS) transaction - this originating server is where the (RTS) coordinator for the transaction resides. When the RTS transaction propagates to another server (via XATMI) and if we want to enlist JTA resources (such as JMS connections) then these resources must be enlisted with the coordinator. But RTS does not know about JTA so the bridge enlists itself with the coordinator, starts a JTA transaction and keeps a record of which JTA resources enlist with this subsidiary JTA transaction. When the coordinator tells the bridge (acting as an RTS participant) to prepare and commit, the bridge forwards these requests to any JTA resources that have enlisted with the JTA transaction. The bridge is the only component capable of fulfilling these requirements so there is no other way.
To use the bridge we will have to make sure that the blacktie-stompconnect subsystem has a dependency on the bridge. If you track what gytis is doing with JBTM-1364 and his associated quickstart (or ping the team) then I think it will be clear what needs to be done to enable the bridge for use by the stompconnect subsystem.
> No unit tests for queue with RTS transport
> ------------------------------------------
>
> Key: JBTM-1855
> URL: https://issues.jboss.org/browse/JBTM-1855
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: BlackTie, REST, Testing
> Reporter: Crispin Boylan
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml.
> When TXN_CFG is manually added to the btconfig.xml the tests actually fail with error:
> 15:15:44,584 ERROR [jacorb.orb] (StompConnect Transport: tcp:///127.0.0.1:49804) Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><coordinator><status>TransactionActive</status><created>1970-01-01T01:00:00.060+01:00</created><timeout>300</timeout><txnURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</volatileParticipantEnlistmentURI></coordinator>
> at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:484) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:486) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.jacorb.orb.ParsedIOR.<init>(ParsedIOR.java:225) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.jacorb.orb.ORB.string_to_object(ORB.java:1961) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.createControlWrapper(ProtocolConverter.java:110) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.controlToTx(ProtocolConverter.java:98) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.onStompReceive(ProtocolConverter.java:310) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:172) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06-icedtea]
--
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
12 years, 8 months
[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1855:
---------------------------------
Thanks Mike to take a look. The StompConnect code will be moved to wildfly-blacktie subsystem with JBTM-1568, I just wonder it is any problem to use the bridge or maybe another way to associated JTS transaction ?
> No unit tests for queue with RTS transport
> ------------------------------------------
>
> Key: JBTM-1855
> URL: https://issues.jboss.org/browse/JBTM-1855
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: BlackTie, REST, Testing
> Reporter: Crispin Boylan
> Assignee: Amos Feng
> Fix For: 5.0.0.M4
>
>
> There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml.
> When TXN_CFG is manually added to the btconfig.xml the tests actually fail with error:
> 15:15:44,584 ERROR [jacorb.orb] (StompConnect Transport: tcp:///127.0.0.1:49804) Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><coordinator><status>TransactionActive</status><created>1970-01-01T01:00:00.060+01:00</created><timeout>300</timeout><txnURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</volatileParticipantEnlistmentURI></coordinator>
> at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:484) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:486) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.jacorb.orb.ParsedIOR.<init>(ParsedIOR.java:225) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.jacorb.orb.ORB.string_to_object(ORB.java:1961) [jacorb-2.3.2.jbossorg-4.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.createControlWrapper(ProtocolConverter.java:110) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.controlToTx(ProtocolConverter.java:98) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.onStompReceive(ProtocolConverter.java:310) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:172) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06-icedtea]
--
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
12 years, 8 months
[JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1854:
-----------------------------------
Description:
The first CI job link includes:
CurrentTests01_Test036
jtsremote JTSRemote_ImplicitPropagationTest
crashrecovery02_2 CrashRecovery02_2 - all of them
crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
The second CI job link includes:
JTSRemote_ImplicitPropagationTest failure
CrashRecovery02_2_Test46 hang
was:
There were quite a few failures so I am simply listing them here and referencing the job for further investigation:
CurrentTests01_Test036
jtsremote JTSRemote_ImplicitPropagationTest
crashrecovery02_2 CrashRecovery02_2 - all of them
crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
> Hornetq failures in CI test suite
> ---------------------------------
>
> Key: JBTM-1854
> URL: https://issues.jboss.org/browse/JBTM-1854
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M4
>
> Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz
>
>
> The first CI job link includes:
> CurrentTests01_Test036
> jtsremote JTSRemote_ImplicitPropagationTest
> crashrecovery02_2 CrashRecovery02_2 - all of them
> crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
> crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
> The second CI job link includes:
> JTSRemote_ImplicitPropagationTest failure
> CrashRecovery02_2_Test46 hang
--
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
12 years, 8 months
[JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1854:
-----------------------------------
Attachment: testoutput.idlj.tar.run4.gz
testoutput for the CI job hang (2nd link)
> Hornetq failures in CI test suite
> ---------------------------------
>
> Key: JBTM-1854
> URL: https://issues.jboss.org/browse/JBTM-1854
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M4
>
> Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz
>
>
> There were quite a few failures so I am simply listing them here and referencing the job for further investigation:
> CurrentTests01_Test036
> jtsremote JTSRemote_ImplicitPropagationTest
> crashrecovery02_2 CrashRecovery02_2 - all of them
> crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
> crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
--
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
12 years, 8 months
[JBoss JIRA] (JBTM-1856) Provide a transactional driver quickstart
by Gytis Trikleris (JIRA)
Gytis Trikleris created JBTM-1856:
-------------------------------------
Summary: Provide a transactional driver quickstart
Key: JBTM-1856
URL: https://issues.jboss.org/browse/JBTM-1856
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Demonstrator
Reporter: Gytis Trikleris
Assignee: Gytis Trikleris
Priority: Minor
Fix For: 5.0.0.Final
Provide a simple example of a standalone application using Narayana with Transactional Driver.
--
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
12 years, 8 months