You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jason Warner <ja...@gmail.com> on 2008/02/21 19:16:54 UTC
Questions about using Gshell on a remote server instance
I was working with gshell in trunk and noticed something that I thought was
odd. I had used deploy/connect to connect to a remote instance of
geronimo. I then went to issue a geronimo/stop-server command but I didn't
provide the hostname or port for the remote server. The command attempted
to shutdown a local instance of geronimo. I was confused as to why this
would be the case. My expectation would be that if I were connected to a
remote instance, then any commands sent to a geronimo server would be
directed at that instance. I think this behavior might confuse users. Is
there a reason things are working the way they currently are? Is it
technically feasible to accomplish this with the way the command is written
or is it just not worth the effort? I'd like to see what other think about
this, but I'm definitely going to document it in the wiki.
Thanks,
--
~Jason Warner
Re: Questions about using Gshell on a remote server instance
Posted by Jason Dillon <ja...@planet57.com>.
Hrm.... Too bad there isn't an anonymous user that can only check if the server was started or not... Since that is all that start-server does.
--jason
-----Original Message-----
From: "Jarek Gawor" <jg...@gmail.com>
Date: Thu, 21 Feb 2008 15:57:23
To:dev@geronimo.apache.org
Subject: Re: Questions about using Gshell on a remote server instance
On Thu, Feb 21, 2008 at 2:35 PM, Jason Warner <ja...@gmail.com> wrote:
>
>
> On Thu, Feb 21, 2008 at 1:36 PM, Jarek Gawor <jg...@gmail.com> 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
Re: Questions about using Gshell on a remote server instance
Posted by Jason Dillon <ja...@planet57.com>.
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 <ja...@gmail.com>
> wrote:
>>
>>
>> On Thu, Feb 21, 2008 at 1:36 PM, Jarek Gawor <jg...@gmail.com>
>> 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
Re: Questions about using Gshell on a remote server instance
Posted by Jarek Gawor <jg...@gmail.com>.
On Thu, Feb 21, 2008 at 2:35 PM, Jason Warner <ja...@gmail.com> wrote:
>
>
> On Thu, Feb 21, 2008 at 1:36 PM, Jarek Gawor <jg...@gmail.com> 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
Re: Questions about using Gshell on a remote server instance
Posted by Jason Warner <ja...@gmail.com>.
On Thu, Feb 21, 2008 at 1:36 PM, Jarek Gawor <jg...@gmail.com> 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.
>
> On Thu, Feb 21, 2008 at 1:16 PM, Jason Warner <ja...@gmail.com> wrote:
> > I was working with gshell in trunk and noticed something that I thought
> was
> > odd. I had used deploy/connect to connect to a remote instance of
> geronimo.
> > I then went to issue a geronimo/stop-server command but I didn't provide
> the
> > hostname or port for the remote server. The command attempted to
> shutdown a
> > local instance of geronimo. I was confused as to why this would be the
> > case. My expectation would be that if I were connected to a remote
> > instance, then any commands sent to a geronimo server would be directed
> at
> > that instance. I think this behavior might confuse users. Is there a
> > reason things are working the way they currently are? Is it technically
> > feasible to accomplish this with the way the command is written or is it
> > just not worth the effort? I'd like to see what other think about this,
> but
> > I'm definitely going to document it in the wiki.
> >
> > Thanks,
> >
> > --
> > ~Jason Warner
>
--
~Jason Warner
Re: Questions about using Gshell on a remote server instance
Posted by Jarek Gawor <jg...@gmail.com>.
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
On Thu, Feb 21, 2008 at 1:16 PM, Jason Warner <ja...@gmail.com> wrote:
> I was working with gshell in trunk and noticed something that I thought was
> odd. I had used deploy/connect to connect to a remote instance of geronimo.
> I then went to issue a geronimo/stop-server command but I didn't provide the
> hostname or port for the remote server. The command attempted to shutdown a
> local instance of geronimo. I was confused as to why this would be the
> case. My expectation would be that if I were connected to a remote
> instance, then any commands sent to a geronimo server would be directed at
> that instance. I think this behavior might confuse users. Is there a
> reason things are working the way they currently are? Is it technically
> feasible to accomplish this with the way the command is written or is it
> just not worth the effort? I'd like to see what other think about this, but
> I'm definitely going to document it in the wiki.
>
> Thanks,
>
> --
> ~Jason Warner
Re: Questions about using Gshell on a remote server instance
Posted by "Erik B. Craig" <ec...@apache.org>.
Jason,
I'm not sure how it's *supposed* to be by design, but my expectations
would be the same as yours - it would shutdown the the instance that
you are remotely connected to and not the local instance. As such, I
agree that it may confuse users.
Perhaps this behavior should be changed?
Thanks,
Erik B. Craig
ecraig@apache.org
On Feb 21, 2008, at 12:16 PM, Jason Warner wrote:
> I was working with gshell in trunk and noticed something that I
> thought was odd. I had used deploy/connect to connect to a remote
> instance of geronimo. I then went to issue a geronimo/stop-server
> command but I didn't provide the hostname or port for the remote
> server. The command attempted to shutdown a local instance of
> geronimo. I was confused as to why this would be the case. My
> expectation would be that if I were connected to a remote instance,
> then any commands sent to a geronimo server would be directed at
> that instance. I think this behavior might confuse users. Is there
> a reason things are working the way they currently are? Is it
> technically feasible to accomplish this with the way the command is
> written or is it just not worth the effort? I'd like to see what
> other think about this, but I'm definitely going to document it in
> the wiki.
>
> Thanks,
>
> --
> ~Jason Warner
Re: Questions about using Gshell on a remote server instance
Posted by Jason Dillon <ja...@planet57.com>.
stop-server was created before the deploy/connect bits so its not
using the same framework. But I don't see why it can't... and it
probably should.
--jason
On Feb 21, 2008, at 10:16 AM, Jason Warner wrote:
> I was working with gshell in trunk and noticed something that I
> thought was odd. I had used deploy/connect to connect to a remote
> instance of geronimo. I then went to issue a geronimo/stop-server
> command but I didn't provide the hostname or port for the remote
> server. The command attempted to shutdown a local instance of
> geronimo. I was confused as to why this would be the case. My
> expectation would be that if I were connected to a remote instance,
> then any commands sent to a geronimo server would be directed at
> that instance. I think this behavior might confuse users. Is there
> a reason things are working the way they currently are? Is it
> technically feasible to accomplish this with the way the command is
> written or is it just not worth the effort? I'd like to see what
> other think about this, but I'm definitely going to document it in
> the wiki.
>
> Thanks,
>
> --
> ~Jason Warner