Hello all,
I have a GlassFish app-server server with lots of classes which
takes quite long to properly shut down. It has self-registered
with SMF as a service instance (domain1), and that includes no
forced timeout for starts and stops (value is 0), but the method
script somehow enforces a
On 2013-03-26 14:09, Michael Stapleton wrote:
Hi Jim,
Your SMF method is likely running asadmin.
Have you tried using the asadmin command directly to stop the domain?
It sounds like it could be the default 60 second socket timeout when
asadmin attempts to contact glassfish.
Network issues?
There are a number of environmental variables used by asadmin, but I did
not find anything that looked promising.
As a last resort hack, you could you wrap the asadmin command in a
script.
I would also try to find out why my app takes over 60 seconds to stop.
We might be trying to cure the
On 2013-03-26 14:44, Michael Stapleton wrote:
There are a number of environmental variables used by asadmin, but I did
not find anything that looked promising.
As a last resort hack, you could you wrap the asadmin command in a
script.
I thought of changing the SMF method to something like
Well, regarding the glassfish part of the problem, the 60sec timeout
is hardcoded unconfigurable in the admin-cli part of the project.
http://java.net/projects/glassfish/sources/svn/content/tags/3.1.1-b12/admin/cli/src/main/java/com/sun/enterprise/admin/cli/StopDomainCommand.java?rev=60828
Grep
Could these be of use?
startd/critical_failure_count
startd/critical_failure_period
The critical_failure_count and critical_failure_period
properties together specify the maximum number of ser-
vice failures allowed in a given time interval before
On Mar 26, 2013, at 9:15 AM, Jim Klimov wrote:
Well, regarding the glassfish part of the problem, the 60sec timeout
is hardcoded unconfigurable in the admin-cli part of the project.
