|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (CARGO-723) cargo:stop doesn't work with JBoss EAP 5cargo:stop doesn't work with JBoss EAP 5
---------------------------------------- Key: CARGO-723 URL: http://jira.codehaus.org/browse/CARGO-723 Project: Cargo Issue Type: Bug Components: JBoss Environment: JBoss EAP 5 branch Reporter: Ondrej Zizka Priority: Minor The server actually stops, but cargo doesn't find about it and waits until the timeout. Note that this is different from CARGO-708 - that concerns cargo:start. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-723) cargo:stop doesn't work with JBoss EAP 5[ http://jira.codehaus.org/browse/CARGO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186059#action_186059 ] Matt Wringe commented on CARGO-723: ----------------------------------- the server will usually stop after the timeout since the thread that started the server will be killed. What exact version of JBoss EAP is this? The title says 5, but the environment says the branch. Please note that cargo may not work with unreleased application servers, its too time consuming to be tracking fresh code in a source repository. I will see if I have time to look into this issue, we also would accept patches if applicable > cargo:stop doesn't work with JBoss EAP 5 > ---------------------------------------- > > Key: CARGO-723 > URL: http://jira.codehaus.org/browse/CARGO-723 > Project: Cargo > Issue Type: Bug > Components: JBoss > Environment: JBoss EAP 5 branch > Reporter: Ondrej Zizka > Priority: Minor > > The server actually stops, but cargo doesn't find about it and waits until the timeout. > Note that this is different from CARGO-708 - that concerns cargo:start. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-723) cargo:stop doesn't work with JBoss EAP 5[ http://jira.codehaus.org/browse/CARGO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186274#action_186274 ] Ondrej Zizka commented on CARGO-723: ------------------------------------ It's the EAP 5 branch. It's not of much importance - just that the tests take few minutes longer on Hudson (and other jobs have to wait), and that it causes the job run to be considered as errorneous. The EAP 5 code shouldn't be changing much now. Thanks if you find a time for it. > cargo:stop doesn't work with JBoss EAP 5 > ---------------------------------------- > > Key: CARGO-723 > URL: http://jira.codehaus.org/browse/CARGO-723 > Project: Cargo > Issue Type: Bug > Components: JBoss > Environment: JBoss EAP 5 branch > Reporter: Ondrej Zizka > Priority: Minor > > The server actually stops, but cargo doesn't find about it and waits until the timeout. > Note that this is different from CARGO-708 - that concerns cargo:start. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
[jira] Commented: (CARGO-723) cargo:stop doesn't work with JBoss EAP 5[ http://jira.codehaus.org/browse/CARGO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186275#action_186275 ] Ondrej Zizka commented on CARGO-723: ------------------------------------ On the other hand, if CARGO-713 Separate container.timeout to start and stop timeouts was done, this wouldn't be even less important as the hudson delays is the bigger problem. > cargo:stop doesn't work with JBoss EAP 5 > ---------------------------------------- > > Key: CARGO-723 > URL: http://jira.codehaus.org/browse/CARGO-723 > Project: Cargo > Issue Type: Bug > Components: JBoss > Environment: JBoss EAP 5 branch > Reporter: Ondrej Zizka > Priority: Minor > > The server actually stops, but cargo doesn't find about it and waits until the timeout. > Note that this is different from CARGO-708 - that concerns cargo:start. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Free embeddable forum powered by Nabble | Forum Help |