Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-557

jbossas-managed-6 hangs with JBoss AS 6.1.0.Final

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: jbossas_1.0.0.CR1
    • Fix Version/s: None
    • Component/s: JBoss AS Containers
    • Labels:
      None
    • Environment:
      Fedora 14 64bit
      java version "1.6.0_24"
      Apache Maven 3.0.3
    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      In arquillian.xml specify URL of the logging.properties file e.g.:

      <configuration>
      <property name="javaVmArguments">-Dlogging.configuration=file:///opt/sw/jboss/jboss-6.1.0.Final/bin/logging.properties</property>
      </configuration>

      Show
      In arquillian.xml specify URL of the logging.properties file e.g.: <configuration> <property name="javaVmArguments">-Dlogging.configuration= file:///opt/sw/jboss/jboss-6.1.0.Final/bin/logging.properties </property> </configuration>

      Description

      To reproduce:

      1. Use the arquillian-showcase project
      2. Apply the attached patch to add arq-jbossas-managed-6 profile to the CDI module. (The patch also modifies the bom file slightly)
      3. Set JBOSS_HOME to point to local JBoss AS 6.1.0 installation
      4. 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
      

      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.

        Gliffy Diagrams

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              jharting Jozef Hartinger
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development