[
https://issues.jboss.org/browse/ARQ-557?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger updated ARQ-557:
--------------------------------
Description:
To reproduce:
# Use the arquillian-showcase project
# Apply the attached patch to add arq-jbossas-managed-6 profile to the CDI module. (The
patch also modifies the bom file slightly)
# Set JBOSS_HOME to point to local JBoss AS 6.1.0 installation
# In the "cdi" folder run "mvn clean install -Parq-jbossas-managed-6"
The execution hangs after the following line and does not continue after 120 seconds:
{noformat}
Running com.acme.cdi.translate.TextTranslatorServiceTestCase
Aug 23, 2011 9:13:40 AM
org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator
getActivatedConfiguration
INFO: Could not read active container configuration: null
Starting server "default", with command (start timeout is 120 seconds ):
/opt/sw/jboss/jdk/jdk1.6.0_24/bin/java -cp
/opt/sw/jboss/jboss-6.1.0.Final/bin/run.jar:/home/jharting/jboss/sw/jdk/jdk1.6.0_24/lib/tools.jar
-Xmx512m -XX:MaxPermSize=128m -Djbosstest.udp.ip_ttl=0
-Djava.endorsed.dirs=/opt/sw/jboss/jboss-6.1.0.Final/lib/endorsed
-Djboss.server.log.threshold=DEBUG
-Djava.endorsed.dirs=/opt/sw/jboss/jboss-6.1.0.Final/lib/endorsed/
-Dxb.builder.useUnorderedSequence=true org.jboss.Main -c default -b localhost -g
131f57cc4f7
{noformat}
Note that the tests pass if JBoss AS 6.0.0.Final is used. I tried upgrading
jboss-server-manager to 1.0.4.Final and jboss-as-profileservice-client to 6.1.0.Final in
the bom file with no success.
The remote container works as expected with both 6.0.0.Final and 6.1.0.Final.
was:
To reproduce:
# Use the arquillian-showcase project
# Apply the attached patch to add arq-jbossas-managed-6 profile to the CDI module. (The
patch also modifies the bom file slightly)
# Set JBOSS_HOME to point to local JBoss AS 6.1.0 installation
# In the "cdi" folder run "mvn clean install -Parq-jbossas-managed-6"
The execution hangs after the following line and does not continue after 120 seconds:
Running com.acme.cdi.translate.TextTranslatorServiceTestCase
Aug 23, 2011 9:13:40 AM
org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator
getActivatedConfiguration
INFO: Could not read active container configuration: null
Starting server "default", with command (start timeout is 120 seconds ):
/opt/sw/jboss/jdk/jdk1.6.0_24/bin/java -cp
/opt/sw/jboss/jboss-6.1.0.Final/bin/run.jar:/home/jharting/jboss/sw/jdk/jdk1.6.0_24/lib/tools.jar
-Xmx512m -XX:MaxPermSize=128m -Djbosstest.udp.ip_ttl=0
-Djava.endorsed.dirs=/opt/sw/jboss/jboss-6.1.0.Final/lib/endorsed
-Djboss.server.log.threshold=DEBUG
-Djava.endorsed.dirs=/opt/sw/jboss/jboss-6.1.0.Final/lib/endorsed/
-Dxb.builder.useUnorderedSequence=true org.jboss.Main -c default -b localhost -g
131f57cc4f7
jbossas-managed-6 hangs with JBoss AS 6.1.0.Final
-------------------------------------------------
Key: ARQ-557
URL:
https://issues.jboss.org/browse/ARQ-557
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JBoss Containers
Affects Versions: jbossas_1.0.0.CR1
Environment: Fedora 14 64bit
java version "1.6.0_24"
Apache Maven 3.0.3
Reporter: Jozef Hartinger
Priority: Critical
Attachments: ARQ-557.patch
To reproduce:
# Use the arquillian-showcase project
# Apply the attached patch to add arq-jbossas-managed-6 profile to the CDI module. (The
patch also modifies the bom file slightly)
# Set JBOSS_HOME to point to local JBoss AS 6.1.0 installation
# In the "cdi" folder run "mvn clean install
-Parq-jbossas-managed-6"
The execution hangs after the following line and does not continue after 120 seconds:
{noformat}
Running com.acme.cdi.translate.TextTranslatorServiceTestCase
Aug 23, 2011 9:13:40 AM
org.jboss.arquillian.container.impl.client.container.ContainerRegistryCreator
getActivatedConfiguration
INFO: Could not read active container configuration: null
Starting server "default", with command (start timeout is 120 seconds ):
/opt/sw/jboss/jdk/jdk1.6.0_24/bin/java -cp
/opt/sw/jboss/jboss-6.1.0.Final/bin/run.jar:/home/jharting/jboss/sw/jdk/jdk1.6.0_24/lib/tools.jar
-Xmx512m -XX:MaxPermSize=128m -Djbosstest.udp.ip_ttl=0
-Djava.endorsed.dirs=/opt/sw/jboss/jboss-6.1.0.Final/lib/endorsed
-Djboss.server.log.threshold=DEBUG
-Djava.endorsed.dirs=/opt/sw/jboss/jboss-6.1.0.Final/lib/endorsed/
-Dxb.builder.useUnorderedSequence=true org.jboss.Main -c default -b localhost -g
131f57cc4f7
{noformat}
Note that the tests pass if JBoss AS 6.0.0.Final is used. I tried upgrading
jboss-server-manager to 1.0.4.Final and jboss-as-profileservice-client to 6.1.0.Final in
the bom file with no success.
The remote container works as expected with both 6.0.0.Final and 6.1.0.Final.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira