You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2004/11/05 04:44:32 UTC
[jira] Created: (GERONIMO-440) Installing package in offline mode should fail if server is running
Installing package in offline mode should fail if server is running
-------------------------------------------------------------------
Key: GERONIMO-440
URL: http://nagoya.apache.org/jira/browse/GERONIMO-440
Project: Apache Geronimo
Type: Improvement
Components: deployment
Versions: 1.0-M2
Reporter: Aaron Mulder
The deployment feature of building an executable package and installing it into the server's configuration store should not work if the server is running. We don't want to allow the deploy tool and the server to make conflicting changes, etc.
The easy way to detect if the server is running would be to try to connect to its JMX remoting interface, but this throws a security exception. Probably it would be good enough to detect the security exception as opposed to a "nothing listening on that port" or "whatever's there isn't Geronimo". But none of that will help if the server is running and listening on a nonstandard port.
Perhaps the server should have a lock file while running or something like that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-440) Installing package in offline mode
should fail if server is running
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-440?page=all ]
Aaron Mulder closed GERONIMO-440:
---------------------------------
Fix Version: 1.1
(was: 1.x)
Resolution: Invalid
Assign To: Aaron Mulder
There's no long an offline mode per se
> Installing package in offline mode should fail if server is running
> -------------------------------------------------------------------
>
> Key: GERONIMO-440
> URL: http://issues.apache.org/jira/browse/GERONIMO-440
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M2
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Fix For: 1.1
>
> The deployment feature of building an executable package and installing it into the server's configuration store should not work if the server is running. We don't want to allow the deploy tool and the server to make conflicting changes, etc.
> The easy way to detect if the server is running would be to try to connect to its JMX remoting interface, but this throws a security exception. Probably it would be good enough to detect the security exception as opposed to a "nothing listening on that port" or "whatever's there isn't Geronimo". But none of that will help if the server is running and listening on a nonstandard port.
> Perhaps the server should have a lock file while running or something like that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-440) Installing package in offline mode should fail if server is running
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-440?page=all ]
Matt Hogstrom updated GERONIMO-440:
-----------------------------------
Fix Version: 1.x
(was: 1.0)
Moving to 1.x
> Installing package in offline mode should fail if server is running
> -------------------------------------------------------------------
>
> Key: GERONIMO-440
> URL: http://issues.apache.org/jira/browse/GERONIMO-440
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M2
> Reporter: Aaron Mulder
> Fix For: 1.x
>
> The deployment feature of building an executable package and installing it into the server's configuration store should not work if the server is running. We don't want to allow the deploy tool and the server to make conflicting changes, etc.
> The easy way to detect if the server is running would be to try to connect to its JMX remoting interface, but this throws a security exception. Probably it would be good enough to detect the security exception as opposed to a "nothing listening on that port" or "whatever's there isn't Geronimo". But none of that will help if the server is running and listening on a nonstandard port.
> Perhaps the server should have a lock file while running or something like that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-440) Installing package in offline mode should fail if server is running
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-440?page=all ]
Aaron Mulder updated GERONIMO-440:
----------------------------------
Fix Version: 1.0
Description:
The deployment feature of building an executable package and installing it into the server's configuration store should not work if the server is running. We don't want to allow the deploy tool and the server to make conflicting changes, etc.
The easy way to detect if the server is running would be to try to connect to its JMX remoting interface, but this throws a security exception. Probably it would be good enough to detect the security exception as opposed to a "nothing listening on that port" or "whatever's there isn't Geronimo". But none of that will help if the server is running and listening on a nonstandard port.
Perhaps the server should have a lock file while running or something like that.
was:
The deployment feature of building an executable package and installing it into the server's configuration store should not work if the server is running. We don't want to allow the deploy tool and the server to make conflicting changes, etc.
The easy way to detect if the server is running would be to try to connect to its JMX remoting interface, but this throws a security exception. Probably it would be good enough to detect the security exception as opposed to a "nothing listening on that port" or "whatever's there isn't Geronimo". But none of that will help if the server is running and listening on a nonstandard port.
Perhaps the server should have a lock file while running or something like that.
Environment:
The problem with a lock file is that it's still there if the machine crashes and Geronimo isn't restarted.
Perhaps the "lock file" could point to the JMX listen port, or the deploy tool could inspect the configuration database content to figure that out. Perhaps this issue is overengineering.
> Installing package in offline mode should fail if server is running
> -------------------------------------------------------------------
>
> Key: GERONIMO-440
> URL: http://issues.apache.org/jira/browse/GERONIMO-440
> Project: Geronimo
> Type: Improvement
> Components: deployment
> Versions: 1.0-M2
> Reporter: Aaron Mulder
> Fix For: 1.0
>
> The deployment feature of building an executable package and installing it into the server's configuration store should not work if the server is running. We don't want to allow the deploy tool and the server to make conflicting changes, etc.
> The easy way to detect if the server is running would be to try to connect to its JMX remoting interface, but this throws a security exception. Probably it would be good enough to detect the security exception as opposed to a "nothing listening on that port" or "whatever's there isn't Geronimo". But none of that will help if the server is running and listening on a nonstandard port.
> Perhaps the server should have a lock file while running or something like that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira