[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
Bridging stuff
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-BA
> 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: Documentation, XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> 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
> Bridging stuff
--
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
10 years, 9 months
[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:
--------------------------------
Assignee: Gytis Trikleris (was: Paul Robinson)
> 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: Documentation, XTS
> Reporter: Paul Robinson
> Assignee: Gytis Trikleris
> 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
10 years, 9 months
[JBoss JIRA] (JBTM-1967) TXFramework tests do not work with remote container
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1967?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1967:
--------------------------------
Assignee: Gytis Trikleris (was: Paul Robinson)
> TXFramework tests do not work with remote container
> ---------------------------------------------------
>
> Key: JBTM-1967
> URL: https://issues.jboss.org/browse/JBTM-1967
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: XTS
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Priority: Minor
> Fix For: 5.0.0.Final
>
>
> TXFramework tests fail to add and remove byteman script to/from remote server.
> Here is the output after executing the following line:
> {code}mvn clean test -Dtest=CompensatableTest#testDefaultNoExistingTX -Parq-remote{code}
> {code}
> Running org.jboss.narayana.compensations.functional.compensatable.CompensatableTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 6.167 sec <<< FAILURE!
> org.jboss.narayana.compensations.functional.compensatable.CompensatableTest Time elapsed: 6.166 sec <<< ERROR!
> java.lang.RuntimeException: Failed to submit Byteman script
> at org.jboss.jbossts.xts.bytemanSupport.BMScript.submit(BMScript.java:24)
> at org.jboss.narayana.compensations.functional.compensatable.CompensatableTest.submitBytemanScript(CompensatableTest.java:86)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:242)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:579)
> at java.net.Socket.connect(Socket.java:528)
> at java.net.Socket.<init>(Socket.java:425)
> at java.net.Socket.<init>(Socket.java:208)
> at org.jboss.byteman.agent.submit.Submit$Comm.<init>(Submit.java:871)
> at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:777)
> at org.jboss.byteman.agent.submit.Submit.addScripts(Submit.java:595)
> at org.jboss.byteman.agent.submit.Submit.addRulesFromResources(Submit.java:568)
> at org.jboss.jbossts.xts.bytemanSupport.BMScript.submit(BMScript.java:22)
> ... 54 more
> org.jboss.narayana.compensations.functional.compensatable.CompensatableTest Time elapsed: 6.167 sec <<< ERROR!
> java.lang.RuntimeException: Failed to remove Byteman script
> at org.jboss.jbossts.xts.bytemanSupport.BMScript.remove(BMScript.java:34)
> at org.jboss.narayana.compensations.functional.compensatable.CompensatableTest.removeBytemanScript(CompensatableTest.java:91)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36)
> at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99)
> at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87)
> at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:242)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:579)
> at java.net.Socket.connect(Socket.java:528)
> at java.net.Socket.<init>(Socket.java:425)
> at java.net.Socket.<init>(Socket.java:208)
> at org.jboss.byteman.agent.submit.Submit$Comm.<init>(Submit.java:871)
> at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:777)
> at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:688)
> at org.jboss.byteman.agent.submit.Submit.deleteRulesFromResources(Submit.java:661)
> at org.jboss.jbossts.xts.bytemanSupport.BMScript.remove(BMScript.java:32)
> ... 54 more
> Results :
> Tests in error:
> org.jboss.narayana.compensations.functional.compensatable.CompensatableTest: Failed to submit Byteman script
> org.jboss.narayana.compensations.functional.compensatable.CompensatableTest: Failed to remove Byteman script
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {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
10 years, 9 months
[JBoss JIRA] (JBTM-1963) Automatically added TXBridge handler should be optional
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1963?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1963:
--------------------------------
Assignee: Gytis Trikleris (was: Paul Robinson)
> Automatically added TXBridge handler should be optional
> -------------------------------------------------------
>
> Key: JBTM-1963
> URL: https://issues.jboss.org/browse/JBTM-1963
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Application Server Integration, TxBridge
> Reporter: Gytis Trikleris
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.Final
>
>
> XTS subsystem automatically adds XTS and TXBridge handlers if the deployment has a class annotated with @WebService and @Transactional. However, TXBridge handler required the WS-AT transaction to be available for every request. If the transaction is not present, it fails to handle the message with com.arjuna.wst.UnknownTransactionException.
> The problem arises when @Transactional annotation has a type such as SUPPORTED, in which case WS-AT transaction should not be mandatory.
> We could write a wrapper for the current handler, which will delegate the call only if the transaction is available.
--
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
10 years, 9 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:
--------------------------------
Component/s: (was: Documentation)
> 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
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.Final
>
> 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
10 years, 9 months