Skip to main content

admin-thread-pool idle timeout

5 replies [Last post]
apostle
Offline
Joined: 2006-05-05
Points: 0

Could anyone please tell me what the following message in Glassfish log states for?

WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=25;_ThreadName=Thread-2;|GRIZZLY0023: Interrupting idle Thread: admin-thread-pool-4848(3).|#

I'm having this warning when an application deployment takes more than 15 minutes on ubuntu OS.
It prevents application to be deployed successfully. However it works on windows platform.

I tried to put -1 for idle-thread-timeout-seconds property of the admin-thread-pool in the Glassfish config file, but it gave no effect.

I tried it with different glassfish and jdk versions in different combinations (GF v3.2.1, v3.1.2.2, jdk 1.7, 1.6) it works for windows for all combinations and it does not for ubuntu.

Is it a bug in the Application Server? Is there any way to find the problem source? Could anyone suggest from where to start? I'm having this issue on production, is it really a time to think about moving to another application server?

Thanks

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
rlubke
Offline
Joined: 2003-08-21
Points: 0

You'd want to set the request-timeout-seconds property to -1. By
default it is 900 (15 minutes).

I do have a couple of follow up questions.

1) How long does the deployment take on Windows?
2) What is the nature of the application you're deploying (EJBs, CDI,
size of the archive, etc.)?

It also may be useful to gather thread dumps during the deployment
process to gain insight into the issue.
I would recommend using jstack or visualvm for this task.

> forums@java.net
> November 2, 2012 10:59 AM
> Could anyone please tell me what the following message in Glassfish log
> states for?
> WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=25;_ThreadName=Thread-2;|GRIZZLY0023:
>
> Interrupting idle Thread: admin-thread-pool-4848(3).|# I'm having this
> warning when an application deployment takes more than 15 minutes on
> ubuntu
> OS. It prevents application to be deployed successfully. However it
> works on
> windows platform. I tried to put -1 for idle-thread-timeout-seconds
> property
> of the admin-thread-pool in the Glassfish config file, but it gave no
> effect.
> I tried it with different glassfish and jdk versions in different
> combinations (GF v3.2.1, v3.1.2.2, jdk 1.7, 1.6) it works for windows
> for all
> combinations and it does not for ubuntu. Is it a bug in the Application
> Server? Is there any way to find the problem source? Could anyone suggest
> from where to start? I'm having this issue on production, is it really
> a time
> to think about moving to another application server? Thanks
>
> --
>
> [Message sent by forum member 'apostle']
>
> View Post: http://forums.java.net/node/891937
>
>

apostle
Offline
Joined: 2006-05-05
Points: 0

Do you mean this property?

asadmin set server-config.network-config.protocols.protocol.http-listener-1.http.request-timeout-seconds=-1

1) How long does the deployment take on Windows?
The deployment on windows takes more than 90 minutes. It is more than the time for deployment on ubuntu. This is something that I cannot understand.

2) What is the nature of the application you're deploying (EJBs, CDI,
size of the archive, etc.)?
It is an .ear file with several modules: an EJB module and three web applications. The most time is consumed by a singleton. Could the change of request-timeout-seconds property help in this case?

I would recommend using jstack or visualvm for this task.

I'm not familiar with any of this tool unfortunately. I looked through short howto for jstack here http://www.herongyang.com/Java-Tools/jstack-JVM-Thread-Dump-Stack-Strace... and I have a question: If the deployment process takes about 70 minutes should I run jstack periodically during the deployment process?
BTW I tried to deploy the application several times on ubuntu server and this message appears at different time after the deployment process started. It may appear from 15mins till 50 mins after the process start.

Thank you for helping me out.

rlubke
Offline
Joined: 2003-08-21
Points: 0

apostle wrote:
Do you mean this property?

asadmin set server-config.network-config.protocols.protocol.http-listener-1.http.request-timeout-seconds=-1

1) How long does the deployment take on Windows?
The deployment on windows takes more than 90 minutes. It is more than the time for deployment on ubuntu. This is something that I cannot understand.

That is strange. I recall that there are/were some issues with deployment taking a long time.
I'm not sure which issues those are yet - I'll check.

2) What is the nature of the application you're deploying (EJBs, CDI,
size of the archive, etc.)?
It is an .ear file with several modules: an EJB module and three web applications. The most time is consumed by a singleton. Could the change of request-timeout-seconds property help in this case?

It should prevent the timeout.

I would recommend using jstack or visualvm for this task.

I'm not familiar with any of this tool unfortunately. I looked through short howto for jstack here http://www.herongyang.com/Java-Tools/jstack-JVM-Thread-Dump-Stack-Strace... and I have a question: If the deployment process takes about 70 minutes should I run jstack periodically during the deployment process?
BTW I tried to deploy the application several times on ubuntu server and this message appears at different time after the deployment process started. It may appear from 15mins till 50 mins after the process start.

I would take several snapshots of the thread state.

Thank you for helping me out.

apostle
Offline
Joined: 2006-05-05
Points: 0

It really prevents timeout. Thank you very much for all your help.

The only thing that I cannot understand is how http request is involved here? Is there any http request issued for a singleton @PostConstruct method that is called during an application start?

Could you please suggest any documentation that could help me to understand GF configuration setting in details.

Many thanks.

rlubke
Offline
Joined: 2003-08-21
Points: 0

I believe the deployment is initiated over HTTP, so if the deployment
process takes too long, well, then you know what happens.

> forums@java.net
> November 6, 2012 6:47 AM
> It really prevents timeout. Thank you very much for all your help. The
> only
> thing that I cannot understand is how http request is involved here?
> Is there
> any http request issued for a singleton @PostConstruct method that is
> called
> during an application start? Could you please suggest any
> documentation that
> could help me to understand GF configuration setting in details. Many
> thanks.
>
> --
>
> [Message sent by forum member 'apostle']
>
> View Post: http://forums.java.net/node/891937
>
>
> forums@java.net
> November 4, 2012 1:56 PM
>

apostle wrote:
Do you mean this property? asadmin set
> server-config.network-config.protocols.protocol.http-listener-1.http.request-timeout-seconds=-1
>
> /1) How long does the deployment take on Windows?/ The deployment on
> windows
> takes more than 90 minutes. It is more than the time for deployment on
> ubuntu. This is something that I cannot understand. That is strange. I
> recall
> that there are/were some issues with deployment taking a long time.
> I'm not
> sure which issues those are yet - I'll check. /2) What is the nature
> of the
> application you're deploying (EJBs, CDI,/ /size of the archive,
> etc.)?/ It is
> an .ear file with several modules: an EJB module and three web
> applications.
> The most time is consumed by a singleton. Could the change of
> request-timeout-seconds property help in this case? It should prevent the
> timeout. /I would recommend using jstack or visualvm for this task. /
> I'm not
> familiar with any of this tool unfortunately. I looked through short
> howto
> for jstack here
> http://www.herongyang.com/Java-Tools/jstack-JVM-Thread-Dump-Stack-Strace...
>
> and I have a question: If the deployment process takes about 70 minutes
> should I run jstack periodically during the deployment process? BTW I
> tried
> to deploy the application several times on ubuntu server and this message
> appears at different time after the deployment process started. It may
> appear
> from 15mins till 50 mins after the process start. I would take several
> snapshots of the thread state. Thank you for helping me out.

>
> --
>
> [Message sent by forum member 'rlubke']
>
> View Post: http://forums.java.net/node/891937
>
>