April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1594) Implementation-Version manifest entry contains scm revision

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1594?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1594: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Implementation-Version manifest entry contains scm revision > ----------------------------------------------------------- > > Key: JBTM-1594 > URL: https://issues.jboss.org/browse/JBTM-1594 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.4, 5.0.0.M3 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1600) narayana.sh continually attempts to rebase despite non in progress

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1600?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1600: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > narayana.sh continually attempts to rebase despite non in progress > ------------------------------------------------------------------ > > Key: JBTM-1600 > URL: https://issues.jboss.org/browse/JBTM-1600 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > > See "No rebase in progress?" lines in: > http://172.17.131.2/job/btny-pulls-narayana/417/ > I think this can happen if you merge the last commit. The rebase is then complete, so "rebase --continue" fails, causing the script to continue it's loop. This is from memory, not had chance to check properly. > Also, it could be due to an upgrade in the CI nodes bringing a new version of git. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1644) Thoroughly document how to recover a local JTA object store from a different node (perhaps with quickstart?)

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1644: ----------------------------------- Summary: Thoroughly document how to recover a local JTA object store from a different node (perhaps with quickstart?) Key: JBTM-1644 URL: https://issues.jboss.org/browse/JBTM-1644 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Demonstrator, Documentation Reporter: Tom Jenkinson Assignee: Michael Musgrove Priority: Critical Fix For: 5.0.0.M3 Please can you document any restrictions (stating none if there are none). How to configure the recovery manager (e.g. specific node id, not *). Considerations a user should have (not to connect more than one recovery manager to the same store at once, suggestions for how to restrict that - maybe object store specific?) Object store specific information, e.g. if you are using filesystem/hornetq/jdbc do any of them ensure that only one process is accessing at the same time? A simple quickstart demonstrating how to use (maybe JDBC object store inside AS7 would be most appropriate) would be useful. Does IP address play a role, are there any other restrictions? -- 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, 5 months

1
0
0 / 0

[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: ------------------------------------- Next time we see this, let me know and I'll raise it with the JBossWS team. I'd rather not raise it with them now, as the last time we saw it was nearly 1month ago. I'd rather give them a failure in a current code base. > 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: 1 day > > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1418) TxBridgeDemoTest timed out

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1418?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1418. --------------------------------- Resolution: Incomplete Description Logs are both empty and we've only seen it once. Closing as we don't have enough info to resolve. > TxBridgeDemoTest timed out > -------------------------- > > Key: JBTM-1418 > URL: https://issues.jboss.org/browse/JBTM-1418 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TxBridge > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.4 > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/btny-EAP61-quickstarts-tac... > {noformat} > Running org.jboss.jbossts.txbridge.demotest.TxBridgeDemoTest > Build timed out (after 10 minutes). Marking the build as failed. > {noformat} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1418) TxBridgeDemoTest timed out

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1418?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1418: -------------------------------- Description: See: http://172.17.131.2/view/Narayana+BlackTie/job/btny-EAP61-quickstarts-tac... {noformat} Running org.jboss.jbossts.txbridge.demotest.TxBridgeDemoTest Build timed out (after 10 minutes). Marking the build as failed. {noformat} was: See: http://172.17.131.2/job/btny-EAP61-quickstarts/615 {noformat} Running org.jboss.jbossts.txbridge.demotest.TxBridgeDemoTest Build timed out (after 10 minutes). Marking the build as failed. {noformat} > TxBridgeDemoTest timed out > -------------------------- > > Key: JBTM-1418 > URL: https://issues.jboss.org/browse/JBTM-1418 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, TxBridge > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 4.17.4 > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/btny-EAP61-quickstarts-tac... > {noformat} > Running org.jboss.jbossts.txbridge.demotest.TxBridgeDemoTest > Build timed out (after 10 minutes). Marking the build as failed. > {noformat} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1475) TXBridge InboundCrashRecoveryTests failure - could not start container

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1475?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1475. --------------------------------- Resolution: Cannot Reproduce Bug > TXBridge InboundCrashRecoveryTests failure - could not start container > ---------------------------------------------------------------------- > > Key: JBTM-1475 > URL: https://issues.jboss.org/browse/JBTM-1475 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > See: http://172.17.131.2/job/narayana-dualstack/83 > {noformat} > Tests in error: > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Could not start container > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Deployment with name txbridge-inbound-tests-client could not be undeployed. Container jboss must be still running. > {noformat} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1475) TXBridge InboundCrashRecoveryTests failure - could not start container

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1475?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1475: ------------------------------------- Probably. Closing as we only saw it once. > TXBridge InboundCrashRecoveryTests failure - could not start container > ---------------------------------------------------------------------- > > Key: JBTM-1475 > URL: https://issues.jboss.org/browse/JBTM-1475 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TxBridge > Reporter: Gytis Trikleris > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > See: http://172.17.131.2/job/narayana-dualstack/83 > {noformat} > Tests in error: > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Could not start container > testCrashOneLog(org.jboss.jbossts.txbridge.tests.inbound.junit.InboundCrashRecoveryTests): Deployment with name txbridge-inbound-tests-client could not be undeployed. Container jboss must be still running. > {noformat} -- 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, 5 months

1
0
0 / 0

[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: -------------------------------- Remaining Estimate: 1 day > 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: 1 day > > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1643) Need a qa test suite ant target to skip jts tests

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1643?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1643: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/276 > Need a qa test suite ant target to skip jts tests > ------------------------------------------------- > > Key: JBTM-1643 > URL: https://issues.jboss.org/browse/JBTM-1643 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 5.0.0.M3 > > > Useful for testing everything apart from JTS -- 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, 5 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 April 2013