[JBoss JIRA] (JBTM-1216) XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1216?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1216:
--------------------------------
Fix Version/s: 5.0.0.Final
(was: 5.0.0.M2)
> XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1216
> URL: https://issues.jboss.org/browse/JBTM-1216
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Amos Feng
> Assignee: Paul Robinson
> Priority: Trivial
> Labels: assign
> Fix For: 4.17.4, 5.0.0.Final
>
> Original Estimate: 1 hour
> Time Spent: 5 minutes
> Remaining Estimate: 0 minutes
>
> see http://172.17.131.2/job/narayana-java6/1285/artifact/XTS/localjunit/crash...
> {code}
> 13:26:49,610 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:95)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:357)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:70)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:246)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:525)
> at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:119)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:68)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:134)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:112)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:93)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.apache.cxf.common.jaxb.JAXBUtils.generateJaxbSchemas(JAXBUtils.java:765)
> at org.apache.cxf.jaxb.JAXBDataBinding.generateJaxbSchemas(JAXBDataBinding.java:431)
> at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:354)
> at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:474)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:685)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:536)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:248)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:205)
> at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:207)
> at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:442)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:329)
> ... 15 more
> {code}
> and the service failed
> {code}
> 13:26:57,492 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> {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-1216) XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1216?page=com.atlassian.jira.plugin.... ]
Paul Robinson reopened JBTM-1216:
---------------------------------
> XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1216
> URL: https://issues.jboss.org/browse/JBTM-1216
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Amos Feng
> Assignee: Paul Robinson
> Priority: Trivial
> Labels: assign
> Fix For: 4.17.4, 5.0.0.Final
>
> Original Estimate: 1 hour
> Time Spent: 5 minutes
> Remaining Estimate: 0 minutes
>
> see http://172.17.131.2/job/narayana-java6/1285/artifact/XTS/localjunit/crash...
> {code}
> 13:26:49,610 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:95)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:357)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:70)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:246)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:525)
> at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:119)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:68)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:134)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:112)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:93)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.apache.cxf.common.jaxb.JAXBUtils.generateJaxbSchemas(JAXBUtils.java:765)
> at org.apache.cxf.jaxb.JAXBDataBinding.generateJaxbSchemas(JAXBDataBinding.java:431)
> at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:354)
> at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:474)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:685)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:536)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:248)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:205)
> at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:207)
> at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:442)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:329)
> ... 15 more
> {code}
> and the service failed
> {code}
> 13:26:57,492 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> {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-1216) XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1216?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1216:
-------------------------------------
Happened again:
http://172.17.131.2/job/btny-pulls-narayana/323/artifact/XTS/localjunit/c...
> XTS Rec test fail with NPE when start service jboss.ws.endpoint-publish.ws-t11-client during booting the jboss-as
> ------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1216
> URL: https://issues.jboss.org/browse/JBTM-1216
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, XTS
> Reporter: Amos Feng
> Assignee: Paul Robinson
> Priority: Trivial
> Labels: assign
> Fix For: 4.17.4, 5.0.0.M2
>
> Original Estimate: 1 hour
> Time Spent: 5 minutes
> Remaining Estimate: 0 minutes
>
> see http://172.17.131.2/job/narayana-java6/1285/artifact/XTS/localjunit/crash...
> {code}
> 13:26:49,610 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:95)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:357)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:70)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:246)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:525)
> at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:119)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:68)
> at org.jboss.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:134)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:112)
> at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:95)
> at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:93)
> ... 5 more
> Caused by: java.lang.NullPointerException
> at org.apache.cxf.common.jaxb.JAXBUtils.generateJaxbSchemas(JAXBUtils.java:765)
> at org.apache.cxf.jaxb.JAXBDataBinding.generateJaxbSchemas(JAXBDataBinding.java:431)
> at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:354)
> at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:474)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:685)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:536)
> at org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:248)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:205)
> at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:101)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:207)
> at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:442)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:329)
> ... 15 more
> {code}
> and the service failed
> {code}
> 13:26:57,492 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.ws.endpoint-publish.ws-t11-client: org.jboss.msc.service.StartException in service jboss.ws.endpoint-publish.ws-t11-client: javax.xml.ws.WebServiceException: java.lang.NullPointerException
> {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-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris logged work on JBTM-1407:
-----------------------------------------
Author: Gytis Trikleris
Created on: 15/Jan/13 3:40 PM
Start Date: 15/Jan/13 11:00 AM
Worklog Time Spent: 3 hours, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 1 hour (was: 0 minutes)
Time Spent: 6 hours, 40 minutes (was: 3 hours, 10 minutes)
Worklog Id: (was: 12428404)
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
> Key: JBTM-1407
> URL: https://issues.jboss.org/browse/JBTM-1407
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 4.17.3
> Reporter: Mark Little
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M2
>
> Time Spent: 6 hours, 40 minutes
> Remaining Estimate: 1 hour
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj
--
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-1293) ATBridgeTest#testSimple counter isn't incremented
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1293?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1293:
--------------------------------
Git Pull Request: https://github.com/jbosstm/narayana/pull/204 (was: https://github.com/jbosstm/narayana/pull/191)
> ATBridgeTest#testSimple counter isn't incremented
> -------------------------------------------------
>
> Key: JBTM-1293
> URL: https://issues.jboss.org/browse/JBTM-1293
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 3 days
> Time Spent: 6 hours
> Remaining Estimate: 2 days, 2 hours
>
> See:
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/21/...
> {code}
> @Test
> public void testSimple() throws Exception
> {
> ut.begin();
> client.incrementCounter(1);
> ut.commit();
> ut.begin();
> int counter = client.getCounter();
> ut.commit();
> Assert.assertEquals(1, counter);
> }
> {code}
> Even though the first transaction should have committed an update to the counter, it is still set to zero in the second transaction.
> This happens intermittently (once so far). It also happened on Beacon which is notorious for test failures caused by things going slowly. I would suspect that the bridged JTA transaction in the first transaction hasn't quite finished the commit when the second transaction is begun.
> If the WS-AT coordinator sends an async commit to the participants and an async committed to the client, then this problem could happen if the client's 'committed' is received before the participant's 'commit' message.
> To verify this we need to check that the coordinator sends an async (@OneWay) commit message to the participant. In which case the simplest solution is to add a 3sec delay between the two transactions. We should also look for other tests that may be affected.
--
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-1293) ATBridgeTest#testSimple counter isn't incremented
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1293?page=com.atlassian.jira.plugin.... ]
Paul Robinson logged work on JBTM-1293:
---------------------------------------
Author: Paul Robinson
Created on: 15/Jan/13 11:19 AM
Start Date: 15/Jan/13 11:19 AM
Worklog Time Spent: 1 hour, 30 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 2 days, 30 minutes (was: 2 days, 2 hours)
Time Spent: 7 hours, 30 minutes (was: 6 hours)
Worklog Id: (was: 12428403)
> ATBridgeTest#testSimple counter isn't incremented
> -------------------------------------------------
>
> Key: JBTM-1293
> URL: https://issues.jboss.org/browse/JBTM-1293
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 3 days
> Time Spent: 7 hours, 30 minutes
> Remaining Estimate: 2 days, 30 minutes
>
> See:
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/21/...
> {code}
> @Test
> public void testSimple() throws Exception
> {
> ut.begin();
> client.incrementCounter(1);
> ut.commit();
> ut.begin();
> int counter = client.getCounter();
> ut.commit();
> Assert.assertEquals(1, counter);
> }
> {code}
> Even though the first transaction should have committed an update to the counter, it is still set to zero in the second transaction.
> This happens intermittently (once so far). It also happened on Beacon which is notorious for test failures caused by things going slowly. I would suspect that the bridged JTA transaction in the first transaction hasn't quite finished the commit when the second transaction is begun.
> If the WS-AT coordinator sends an async commit to the participants and an async committed to the client, then this problem could happen if the client's 'committed' is received before the participant's 'commit' message.
> To verify this we need to check that the coordinator sends an async (@OneWay) commit message to the participant. In which case the simplest solution is to add a 3sec delay between the two transactions. We should also look for other tests that may be affected.
--
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-1293) ATBridgeTest#testSimple counter isn't incremented
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1293?page=com.atlassian.jira.plugin.... ]
Paul Robinson commented on JBTM-1293:
-------------------------------------
Current thinking is that it's not caused by JBTM-1303. I think it's actually due to the way the test uses JPA and @GeneratedValue. I've made the fix; we'll have to see if it happens again after the pull is merged.
> ATBridgeTest#testSimple counter isn't incremented
> -------------------------------------------------
>
> Key: JBTM-1293
> URL: https://issues.jboss.org/browse/JBTM-1293
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing, TXFramework
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 5.0.0.M2
>
> Original Estimate: 3 days
> Time Spent: 6 hours
> Remaining Estimate: 2 days, 2 hours
>
> See:
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/21/...
> {code}
> @Test
> public void testSimple() throws Exception
> {
> ut.begin();
> client.incrementCounter(1);
> ut.commit();
> ut.begin();
> int counter = client.getCounter();
> ut.commit();
> Assert.assertEquals(1, counter);
> }
> {code}
> Even though the first transaction should have committed an update to the counter, it is still set to zero in the second transaction.
> This happens intermittently (once so far). It also happened on Beacon which is notorious for test failures caused by things going slowly. I would suspect that the bridged JTA transaction in the first transaction hasn't quite finished the commit when the second transaction is begun.
> If the WS-AT coordinator sends an async commit to the participants and an async committed to the client, then this problem could happen if the client's 'committed' is received before the participant's 'commit' message.
> To verify this we need to check that the coordinator sends an async (@OneWay) commit message to the participant. In which case the simplest solution is to add a 3sec delay between the two transactions. We should also look for other tests that may be affected.
--
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