We might be able to open a port on localhost during startup, which
would only be used to provide status (like starting, started, shutting
down). Then we wouldn't need to make a JMX connection to the server
at all. Though if possible, a special anonymous system account with
limited proviledges for remote JMX would be more ideal... though I've
no idea if that is possible asis or if it would be easy to implement
if its not there.
Anyone have any other ideas?
--jason
On Feb 21, 2008, at 12:57 PM, Jarek Gawor wrote:
On Thu, Feb 21, 2008 at 2:35 PM, Jason Warner <[EMAIL PROTECTED]>
wrote:
On Thu, Feb 21, 2008 at 1:36 PM, Jarek Gawor <[EMAIL PROTECTED]>
wrote:
Yes, I've noticed that too. The deploy/* commands are not
'integrated'
with the geronimo/* commands. Looks like the JMX connection is not
being shared between these groups of commands. We should be able to
fix that. Please open a bug. Also, I just noticed that if an user
changes the default user/password the geronimo/start-server command
might fail with an error.
Jarek
I just opened a jira for that original issue I mentioned.
https://issues.apache.org/jira/browse/GERONIMO-3869
I'm not sure I understand that second issue you mentioned.
The start-server command has hardcoded username/password combination
and it cannot be specified on the command line. So if the password is
changed and if you start the server let's say with:
geronimo/start-server --background --timeout 60
You will see something like:
.....
Geronimo Application Server started
<after <60 seconds>
ERROR Exception: Failed to start: Geronimo Server
Even though the server started up fine but then becuase of the
exception it will be killed.
Jarek
