[JBoss JIRA] (JBTM-1217) WSTX11-interop tests fail on pure IPv6 nodes
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1217:
-----------------------------------
Summary: WSTX11-interop tests fail on pure IPv6 nodes
Key: JBTM-1217
URL: https://issues.jboss.org/browse/JBTM-1217
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.17.0, 5.0.0.M2
You can see the failure for the job here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/narayana-java6-ipv6/...
Although, this is now the job configured to test just the WSTX11-interop tests: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/narayana-java6-ipv6-...
This can be reproduced by taking a test node, such as vmg36, offline. These are the commands I ran to reproduce. However, you may need to change the wget command to clone an appropriate workspace. Notice the comment that tells you to remove a dependency from a pom.xml. The build will fail if you miss this step out.
{code}
ssh probinso(a)dev89.mw.lab.eng.bos.redhat.com
ssh probinso(a)vmg36.mw.lab.eng.bos.redhat.com
wget http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/narayana-java6-ipv6/w...
unzip narayana-java6-ipv6.zip
cd narayana-java6-ipv6
export MAVEN_OPTS="-DproxySet=true -DproxyHost=proxy-01-ipv6.mw.lab.eng.bos.redhat.com -DproxyPort=3128"
export IPV6_OPTS="-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.bind.address=[::1] -Djboss.bind.address.management=[::1] -Djboss.bind.address.unsecure=[::1]"
export IPV6_OPTS="$IPV6_OPTS $MAVEN_OPTS"
export WSTX_MODULES="WSTX11-interop"
export ARQ_PROF=arqIPv6
export PATH=/usr/lib/jvm/java-1.6.0/bin/:$PATH
export JAVA_HOME=/usr/lib/jvm/java-1.6.0/
export JBOSS_HOME=~/narayana-java6-ipv6/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/
#Now Remove rest-at javadoc dep from narayana-full/pom.xml
./build.sh install -DskipTests=true $IPV6_OPTS -Dmaven.javadoc.skip=true
cd jboss-as
./build.sh install -DskipTests -Dts.smoke=false $IPV6_OPTS
cp ./build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/docs/examples/configs/standalone-xts.xml ./build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/configuration/
cd ..
./build.sh -f XTS/localjunit/pom.xml --projects "$WSTX_MODULES" -P$ARQ_PROF "$@" $IPV6_OPTS clean install
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months
[JBoss JIRA] (JBTM-1268) Test timeout for com.jboss.transaction.wstf.interop.Sc007Test#test3_10
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1268:
-----------------------------------
Summary: Test timeout for com.jboss.transaction.wstf.interop.Sc007Test#test3_10
Key: JBTM-1268
URL: https://issues.jboss.org/browse/JBTM-1268
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.5, 4.17.0, 5.0.0.M2
The test took longer than the 120s default of the jmx Arquillian runner. The interop tests can be quite intensive, running the same operation many times. It's possible that on slow machines that this would take longer than 120s.
It could also be caused by a legitimate bug, but it's hard to tell from the log as these tests produce a lot of expected exceptions as they also test correct behavior under erroneous conditions.
We should increase the test timeout to 5mins to resolve this issue. We can re-open if we see it happen again.
--
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, 6 months
[JBoss JIRA] (JBTM-1267) JBossAS7ServerKillProcessor should wait for defunct java process to disappear
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1267:
-----------------------------------
Summary: JBossAS7ServerKillProcessor should wait for defunct java process to disappear
Key: JBTM-1267
URL: https://issues.jboss.org/browse/JBTM-1267
Project: JBoss Transaction Manager
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: TxBridge, XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.16.5, 4.17.0, 5.0.0.M2
It's possible that this is what is causing JBTM-1259 as Arquillian may be detecting the defunct process.
Remember to apply the fix to the Kill Procesor in TXBridge too.
--
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, 6 months
[JBoss JIRA] (JBTM-1258) QA build does not archive JTS remote test output for both ORBs
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-1258:
--------------------------------------
Summary: QA build does not archive JTS remote test output for both ORBs
Key: JBTM-1258
URL: https://issues.jboss.org/browse/JBTM-1258
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: 5.0.0.M1
Reporter: Michael Musgrove
Assignee: Tom Jenkinson
Fix For: 5.0.0.M1
The QA test suite runs the remote JTS tests against JacORB and the JDK orb but only the last run is archived.
The fix should save the first run in an archive:
testoutput/tests-jtsremote.zip
The results from the second run will be in testoutput/jtsremote as normal
--
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, 6 months
[JBoss JIRA] (JBTM-1224) XTS Rec test fail with NPE when starting service jboss.remoting.endpoint.managemen
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1224:
-----------------------------------
Summary: XTS Rec test fail with NPE when starting service jboss.remoting.endpoint.managemen
Key: JBTM-1224
URL: https://issues.jboss.org/browse/JBTM-1224
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 5.0.0.M1
Reporter: Paul Robinson
Assignee: Amos Feng
Fix For: 4.17.0, 5.0.0.M2
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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 6 months