[jboss-jira] [JBoss JIRA] (AS7-4070) CLONE - Arquillian should wait until a port is free after AS JVM process ends to prevent "port in use".

Fri Mar 23 03:41:47 EDT 2012

     [ https://issues.jboss.org/browse/AS7-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Rubinger updated AS7-4070:
---------------------------------

    Assignee: Ondrej Zizka  (was: Andrew Rubinger)

Ondrej:

I have a patch to enable this feature here:

  https://github.com/ALRubinger/jboss-as/commit/57e452fb83e9492bddf6fb2c65ce0c006616961b

I'm bypassing the typical pull request process for AS due to the nature of this feature; from what I can tell, we don't have the hooks necessary to simulate a taken port before the container fires up, then release it during hang.

Manually I receive this output when we configure a port wait timeout, then I release the port:

{code}Mar 23, 2012 12:40:03 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer waitOnPorts
WARNING: Waiting on port 2222 to become available for 14s
Mar 23, 2012 12:40:03 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer waitOnPorts
WARNING: Waiting on port 2222 to become available for 13s
Mar 23, 2012 12:40:03 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
INFO: Starting container with: [/opt/oracle/java/jdk6/bin/java, -Xmx512m, -XX:MaxPermSize=128m, -ea, -Djboss.home.dir=target/jbossas, -Dorg.jboss.boot.log.file=target/jbossas/standalone/log/boot.log, -Dlogging.configuration=file:target/jbossas/standalone/configuration/logging.properties, -Djboss.modules.dir=/home/alr/business/jboss/git/jbossas/jboss-as/build/target/jboss-as-7.1.2.Final-SNAPSHOT/modules, -Djboss.bundles.dir=target/jbossas/bundles, -jar, /home/alr/business/jboss/git/jbossas/jboss-as/arquillian/container-managed/target/jbossas/jboss-modules.jar, -mp, /home/alr/business/jboss/git/jbossas/jboss-as/build/target/jboss-as-7.1.2.Final-SNAPSHOT/modules, -jaxpmodule, javax.xml.jaxp-provider, org.jboss.as.standalone, -server-config, standalone.xml]
00:40:03,872 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
00:40:04,010 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA{code}

Recommend using this patch/branch of mine as a base, running on the QE systems which have been problematic, and determining if this solves the issue for you.  Remember to simply configure arquillian.xml as I've done in the example in jbossas/arquillian/container-managed/src/test/resources.

> CLONE - Arquillian should wait until a port is free after AS JVM process ends to prevent "port in use".
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4070
>                 URL: https://issues.jboss.org/browse/AS7-4070
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 7.1.0.CR1
>            Reporter: Ondrej Zizka
>            Assignee: Ondrej Zizka
>            Priority: Blocker
>              Labels: arq_qe_blocker
>             Fix For: 7.1.2.Final
>
>
> (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use
> (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one
> (05:54:35) dmlloyd: which may also be causing other issues
> (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too,
> (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there?
> (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such
> (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate
> (05:57:07) ozizka: which is ugly
> (05:57:14) dmlloyd: I mean arq should
> (05:59:17) ozizka: dmlloyd:  Do you have it somewhere on hudson?
> (05:59:24) ozizka: dmlloyd: It never happened to me actually
> (05:59:49) ozizka: Send me a log if you have one handy
> (06:01:35) dmlloyd: ozizka: no, try running with this command though: 
> {code}
> mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \
>                    -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"
> {code}
> (06:13:56) ozizka: dmlloyd: That's on linux?
> (06:14:03) dmlloyd: yes

--
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