Glassfish gem -- shutting down

[Paul Blair-3]

We've been using the following command to shut down the Glassfish gem (0.9.5):

kill -INT `cat /path/to/rails/publish/shared/pids/capistrano-publish`

On one of our Solaris environments we've been noticing Glassfish being reluctant to shut down. Is there a different command we should be using, or something else we should be doing to prep for shutdown?

Thanks,

--
Paul Blair
pblair@...

Cyrus Innovation LLC
200 Varick, Suite 902
New York, NY 10014
phone: [phone]
fax: [phone]
http://cyrusinnovation.com

[Vivek Pandey]

I assume you are running glassfish gem as daemon and yes this is the
right command you are using. It is tested to work on solaris and linux
flavors.

Is this intermittent problem or glassfish gem never shutdown on
receiving SIGINT? Also before you decide to to kill it, is the
application deployed on this is accessible? Also can you send the output
of `pmap -x <pid>` on solaris machine?

-vivek.

Paul Blair wrote:

> We've been using the following command to shut down the Glassfish gem
> (0.9.5):
>
> kill -INT `cat /path/to/rails/publish/shared/pids/capistrano-publish`
>
> On one of our Solaris environments we've been noticing Glassfish being
> reluctant to shut down. Is there a different command we should be
> using, or something else we should be doing to prep for shutdown?
>
> Thanks,
>
> --
> Paul Blair
> pblair@... <mailto:pblair@...>
>
> Cyrus Innovation LLC
> 200 Varick, Suite 902
> New York, NY 10014
> phone: [phone]
> fax: [phone]
> http://cyrusinnovation.com
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Paul Blair-3]

We've determined that this turned out to be the result of SIGINT being trapped in that environment; it had nothing to do with Glassfish at all. Sorry for the false alarm.

On Thu, Oct 29, 2009 at 7:17 PM, Vivek Pandey <Vivek.Pandey@...> wrote:

I assume you are running glassfish gem as daemon and yes this is the right command you are using. It is tested to work on solaris and linux flavors.

Is this intermittent problem or glassfish gem never shutdown on receiving SIGINT? Also before you decide to to kill it, is the application deployed on this is accessible? Also can you send the output of `pmap -x <pid>` on solaris machine?

-vivek.

Paul Blair wrote:

We've been using the following command to shut down the Glassfish gem (0.9.5):

kill -INT `cat /path/to/rails/publish/shared/pids/capistrano-publish`

On one of our Solaris environments we've been noticing Glassfish being reluctant to shut down. Is there a different command we should be using, or something else we should be doing to prep for shutdown?

Thanks,

--
Paul Blair

pblair@... <mailto:pblair@...>

Cyrus Innovation LLC
200 Varick, Suite 902
New York, NY 10014
phone: [phone]
fax: [phone]
http://cyrusinnovation.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...