geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-3869) geronimo/stop-server doesn't use connection established by deploy/connect in gshell
Date Mon, 25 Feb 2008 20:48:51 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572221#action_12572221
] 

Jarek Gawor commented on GERONIMO-3869:
---------------------------------------

Committed changes to trunk (revision 630982) that enable the geronimo/stop-server command
to reuse the connection from the deploy/connect command. These changes also included the following
fixes:
1) The deploy/connect command will now automatically disconnect the previous cached connection.
2) The deploy/disconnect command will remove the connection from cache even if connection.close()
fails.


> geronimo/stop-server doesn't use connection established by deploy/connect in gshell
> -----------------------------------------------------------------------------------
>
>                 Key: GERONIMO-3869
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3869
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: startup/shutdown
>    Affects Versions: 2.1, 2.1.1, 2.2
>            Reporter: Jason Warner
>            Assignee: Jarek Gawor
>             Fix For: 2.1.1, 2.2
>
>
> When using the gshell command line to work with geronimo, hostname and possibly port
(depending on geronimo configuration) must be provided to geronimo/stop-server even if the
gshell session is already connected to that remote server via deploy/connect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message