[
https://issues.jboss.org/browse/JBTM-1217?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1217:
-------------------------------------
This happens when using the "Servlet 3.0" protocol with Arquillian. Switching to
the default (JMX) causes just one test to fail, rather than all of the tests failing with
"Servlet 3.0".
Modify the arquillian.xml to the following to observe:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<arquillian
xmlns="http://jboss.org/schema/arquillian"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jboss.org/schema/arquillian
http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
<!-- Example configuration for a remote JBoss AS 7 instance -->
<!-- Must use Servlet 3.0 for interop tests to pass in IPv6 mode -->
<!--defaultProtocol type="Servlet 3.0" /-->
<container qualifier="jboss-as" default="true">
<!--protocol type="jmx-as7">
<property
name="executionType">REMOTE</property>
</protocol-->
<configuration>
<property
name="javaVmArguments">${server.jvm.args}</property>
<property
name="serverConfig">standalone-xts.xml</property>
<property
name="managementAddress">${node.address}</property>
</configuration>
</container>
</arquillian>
{code}
For the WSTFSC07 tests only the following failure occurs, when using JMX:
{code}
test3_10(com.jboss.transaction.wstf.interop.Sc007Test)
{code}
It seems to be a JMX related issue as the following appears in the test log:
{code}
Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING
at
org.jboss.remotingjmx.protocol.v1.ClientConnection$TheConnection.invoke(ClientConnection.java:1225)
at
org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:522)
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305)
... 83 more
{code}
WSTX11-interop & WSTFSC07 IPv6 tests fail: Error launching test
---------------------------------------------------------------
Key: JBTM-1217
URL:
https://issues.jboss.org/browse/JBTM-1217
Project: JBoss Transaction Manager
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: XTS
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.17.0, 5.0.0.M2
See:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/narayana-java6-ipv6-...
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