[jboss-jira] [JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

[Aslak Knutsen (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660069#comment-12660069 ] 

Aslak Knutsen commented on AS7-3128:
------------------------------------

As far as I can tell, the Arquillian AS7 Managed Container does wait for the Process it spawns to end.

{code}
process.destroy()
process.waitFor()
{code}

Unless there is some other waitFor that should be called as well, I'm not sure why that would leave the process with open ports.. 


Ondrej; the test you are refering to is not using Arquillian it self, but I assume Arquillian has been running previously.. ?
                
> Arquillian doesn't wait for the process to really end, causes problems like "port in use".
> ------------------------------------------------------------------------------------------
>
>                 Key: AS7-3128
>                 URL: https://issues.jboss.org/browse/AS7-3128
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 7.1.0.CR1
>            Reporter: Ondrej Zizka
>            Assignee: Aslak Knutsen
>            Priority: Blocker
>              Labels: arq_qe_blocker
>
> (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