tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christofer Dutz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TOMEE-1364) When using the tomee-maven-plugins stop goal tomee seems to hang forever
Date Fri, 26 Sep 2014 11:25:34 GMT

    [ https://issues.apache.org/jira/browse/TOMEE-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149034#comment-14149034
] 

Christofer Dutz commented on TOMEE-1364:
----------------------------------------

Did you also apply any change to the logic? As this would still result in a 60 second break
at the end of every stop execution as the original code isn't actually doing what it's probably
intended to do: It checks until it is able to connect instead of trying to connect until it
doesn't work anymore.


> When using the tomee-maven-plugins stop goal tomee seems to hang forever
> ------------------------------------------------------------------------
>
>                 Key: TOMEE-1364
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1364
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Maven Plugin
>    Affects Versions: 1.7.0, 2.0.0, 1.7.1
>            Reporter: Christofer Dutz
>            Assignee: Andy Gumbrecht
>             Fix For: 2.0.0, 2.0.0-Milestone-1, 1.7.2
>
>         Attachments: TOMEE-1364-2.0.0-SNAPSHOT.diff
>
>
> When running Tomee in a setup for UI tests (separate start and stop executions) the stop
seems to hang forever. 
> When looking through the code, it seems Tomee is correctly shut down (At least the ports
it opened closed and the processes are killed), but the maven plugin seems to try to get a
connection to the shutdown port for MAXINT times, waiting a second between each try. As far
as I understood the code, there is no way not to wait for 78 years in order to gracefully
shut down Tomee.
> As I already investigated the problem in detail, I'll whip up a patch and attach that
to this issue later this day (Will create one for 1.7.x and one for HEAD)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message