October 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1121) XTS recovery: UnknownTransactionException when enlisting participant

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1121?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1121: -------------------------------- Fix Version/s: (was: 4.16.4) > XTS recovery: UnknownTransactionException when enlisting participant > -------------------------------------------------------------------- > > Key: JBTM-1121 > URL: https://issues.jboss.org/browse/JBTM-1121 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Affects Versions: 4.16.3 > Reporter: Paul Robinson > Assignee: Paul Robinson > > See: > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java7/125 > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java7/124 > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch416-java7/123 > {code} > 22:06:21,092 ERROR [org.jboss.ws.common.invocation.InvocationHandlerJAXWS] (http--127.0.0.1-8080-2) Method invocation failed with exception: null: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_03] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_03] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_03] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_03] > at org.jboss.ws.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:111) > at org.jboss.wsf.stack.cxf.JBossWSInvoker._invokeInternal(JBossWSInvoker.java:181) > at org.jboss.wsf.stack.cxf.JBossWSInvoker.invoke(JBossWSInvoker.java:127) > at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) [cxf-rt-core-2.4.6.jar:2.4.6] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_03] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_03] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_03] > at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) [cxf-rt-core-2.4.6.jar:2.4.6] > at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106) [cxf-rt-core-2.4.6.jar:2.4.6] > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263) [cxf-api-2.4.6.jar:2.4.6] > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-rt-core-2.4.6.jar:2.4.6] > at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:207) [cxf-rt-transports-http-2.4.6.jar:2.4.6] > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:91) > at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169) > at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87) > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185) [cxf-rt-transports-http-2.4.6.jar:2.4.6] > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:108) [cxf-rt-transports-http-2.4.6.jar:2.4.6] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final] > at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) > at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.0.3.GA.jar:2.0.3.GA] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.14.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.14.Final.jar:] > at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.7.Final.jar:2012-04-09 10:12] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.14.Final.jar:] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.14.Final.jar:] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.14.Final.jar:] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.14.Final.jar:] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.14.Final.jar:] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.14.Final.jar:] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.14.Final.jar:] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.14.Final.jar:] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.14.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.14.Final.jar:] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.14.Final.jar:] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] > Caused by: javax.xml.ws.WebServiceException: enlistDurable failed > at org.jboss.jbossts.xts.servicetests.service.XTSServiceTestInterpreter.processCommands(XTSServiceTestInterpreter.java:235) [classes:] > at org.jboss.jbossts.xts.servicetests.service.XTSServiceTestInterpreter.processCommands(XTSServiceTestInterpreter.java:166) [classes:] > at org.jboss.jbossts.xts.servicetests.service.XTSServiceTestPortTypeImpl.serve(XTSServiceTestPortTypeImpl.java:87) [classes:] > ... 41 more > Caused by: com.arjuna.wst.UnknownTransactionException > at com.arjuna.mwlabs.wst11.at.remote.TransactionManagerImple.enlistForDurableTwoPhase(TransactionManagerImple.java:56) [jbossxts-4.16.4.Final-SNAPSHOT.jar:] > at org.jboss.jbossts.xts.servicetests.service.XTSServiceTestInterpreter.processCommands(XTSServiceTestInterpreter.java:233) [classes:] > ... 43 more > {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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-314) JDBCStore.getJDBCClass does not work for some JDBC drivers

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-314?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-314: ------------------------------- Fix Version/s: (was: 4.17.0) > JDBCStore.getJDBCClass does not work for some JDBC drivers > ---------------------------------------------------------- > > Key: JBTM-314 > URL: https://issues.jboss.org/browse/JBTM-314 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Jeremy Stone > Assignee: Tom Jenkinson > > Implementation of com.arjuna.ats.internal.arjuna.objectstore.JDBCStore getJDBCClass(Connection) breaks if JDBC driver DatabaseMetaData getDriverName() is not consistent between driver releases or driver implementations (e.g. SQLServer), and tries to load illegally named classes if first word of reported driver name contains illegal characters (e.g. MySql). > Maybe a pluggable strategy for determination of the class should be used instead. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1005) IllegalStateException when deploying TXBridge demo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1005?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1005: -------------------------------- Fix Version/s: (was: 4.16.0.Final) (was: 4.17.0) > IllegalStateException when deploying TXBridge demo > -------------------------------------------------- > > Key: JBTM-1005 > URL: https://issues.jboss.org/browse/JBTM-1005 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, TxBridge > Affects Versions: 4.16.0.Beta1, 5.0.0.M1 > Reporter: Paul Robinson > Assignee: Paul Robinson > > To reproduce, build the TXBridge demo and deploy to jboss-as-7.1.0.Beta1b. Observe the following exception during deployment: > {code} > 13:15:07,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "txbridge_demo.war" > 13:15:07,641 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."txbridge_demo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."txbridge_demo.war".PARSE: Failed to process phase PARSE of deployment "txbridge_demo.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Beta1.jar:] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] > Caused by: java.lang.IllegalStateException > at org.jboss.as.webservices.util.ASHelper.getRequiredAttachment(ASHelper.java:164) > at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:55) > at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:87) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Beta1.jar:] > ... 5 more > 13:15:07,644 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "txbridge_demo.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"txbridge_demo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"txbridge_demo.war\".PARSE: Failed to process phase PARSE of deployment \"txbridge_demo.war\""}} > 13:15:07,650 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Stopped deployment txbridge_demo.war in 5ms > 13:15:07,650 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report > JBAS014777: Services which failed to start: service jboss.deployment.unit."txbridge_demo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."txbridge_demo.war".PARSE: Failed to process phase PARSE of deployment "txbridge_demo.war" > 13:15:07,651 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"txbridge_demo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"txbridge_demo.war\".PARSE: Failed to process phase PARSE of deployment \"txbridge_demo.war\""}}}} > {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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-891) Port XTS interop tests to JBoss AS 7.x

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-891?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-891: ------------------------------- Fix Version/s: (was: 4.17.0) > Port XTS interop tests to JBoss AS 7.x > -------------------------------------- > > Key: JBTM-891 > URL: https://issues.jboss.org/browse/JBTM-891 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1949) QA suite failure: RawResources02_3_Test112

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1949?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1949: -------------------------------- Fix Version/s: (was: 4.17.12) > QA suite failure: RawResources02_3_Test112 > ------------------------------------------ > > Key: JBTM-1949 > URL: https://issues.jboss.org/browse/JBTM-1949 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.11 > Environment: db2 > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Attachments: jbossts-EAP61-jdbcobjectstore_28_db2_RawResources02_3_Test112.zip > > > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61-jdbcobjectst... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1325) Second bridged JTA transaction doesn't seem to commit if running on same server as first

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1325?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1325: -------------------------------- Fix Version/s: (was: 5.0.0.M2) (was: 4.17.3) > Second bridged JTA transaction doesn't seem to commit if running on same server as first > ---------------------------------------------------------------------------------------- > > Key: JBTM-1325 > URL: https://issues.jboss.org/browse/JBTM-1325 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Paul Robinson > Assignee: Paul Robinson > > See here for code to reproduce (follow steps in README.md): https://github.com/paulrobinson/quickstart-1/tree/master-JBTM-1324_Create... > Scenario: > * 1 JTA Client > * Invokes two WS-AT services in same JTA transaction > * Each service bridges to a JTA transaction which update a DB > > The tests succeed if the client and service one are on the first server and the second service is on a second server. The problem occurs when the client, first and second service all run on the same 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1446) Prepare Quickstarts for Release

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1446?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1446: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Prepare Quickstarts for Release > ------------------------------- > > Key: JBTM-1446 > URL: https://issues.jboss.org/browse/JBTM-1446 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Paul Robinson > Assignee: Paul Robinson > Original Estimate: 4 hours > Time Spent: 5 minutes > Remaining Estimate: 0 minutes > > * The tag should reference the latest release, rather than a snapshot > * General check over looking for things that won't work with a tagged/released AS7+Narayana. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1443) Track AS 7.2.0.Alpha1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1443?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1443: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Track AS 7.2.0.Alpha1 > --------------------- > > Key: JBTM-1443 > URL: https://issues.jboss.org/browse/JBTM-1443 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > > https://issues.jboss.org/browse/AS7/fixforversion/12318469#selectedTab=co... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1329) test(com.hp.mwtests.ts.jts.local.orbsetup.ORBSetupTest): Error: org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 208 completed: No

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1329?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1329: -------------------------------- Fix Version/s: (was: 5.0.0.M2) (was: 4.17.3) > test(com.hp.mwtests.ts.jts.local.orbsetup.ORBSetupTest): Error: org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 208 completed: No > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1329 > URL: https://issues.jboss.org/browse/JBTM-1329 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > http://172.17.131.2/job/jbossts-branch417-EAP61-ipv6-dualstack/107/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1059) Deploy the TXFramework module as part of Arquillian testing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1059?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1059: -------------------------------- Fix Version/s: (was: 5.0.0.M2) > Deploy the TXFramework module as part of Arquillian testing > ----------------------------------------------------------- > > Key: JBTM-1059 > URL: https://issues.jboss.org/browse/JBTM-1059 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > > See: https://community.jboss.org/message/718048 -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2013