users@glassfish.java.net

Re: Interrupting idle thread

From: Korbinian Bachl <korbinian.bachl_at_googlemail.com>
Date: Tue, 15 May 2012 20:36:08 +0200

CPU usage goes up, interrupt Messages fill logs - i bet a pizza and a beer that its related ;)

Von meinem iPhone gesendet

Am 15.05.2012 um 19:58 schrieb Oleksiy Stashok <oleksiy.stashok_at_oracle.com>:

> On 05/15/2012 07:45 PM, Korbinian Bachl wrote:
>>
>> Very bad idea!
>> Turning it off will clean your logs, but the server will die anyway.
> That's not true, depends on usecase and thread-pool settings.
> If long-lasting HTTP request processing is something we expect - then possible solution is to change default thread-pool configuration and increase max threads number.
>
>> Best chance is to disable the gzip compression in Glassfish, do a server restart and you should be good. Its a bug in it, see more details here:
>>
>> http://java.net/jira/browse/GLASSFISH-18705
> This might not be related.
>
> WBR,
> Alexey.
>
>
>
>
>>
>> In case you dont want to loose gzip use a filter solution like EHCache's gzip-filter;
>>
>> Regards,
>>
>> K.B.
>>
>> 2012/5/15 Oleksiy Stashok <oleksiy.stashok_at_oracle.com>
>> Hi,
>>
>> most probably you see this problem because servlet/webapp processes request longer than 15mins (by default), if it's ok - pls. disable the request-timeout using asadmin like:
>>
>> asadmin set server-config.network-config.protocols.protocol.http-listener-1.http.request-timeout-seconds=-1
>>
>> Change the "http-listener-1" in the command above w/ the real name of the listener, which listens on port 8009.
>>
>> Thanks.
>>
>> WBR,
>> Alexey.
>>
>> On 05/10/2012 10:06 PM, Cam Bazz wrote:
>>>
>>> All of a sudden my cpu usage goes 100% and I get bunch of these in the
>>> server log. Could that be some sort of attack? Best regards,
>>> C.B.
>>>
>>> [#|2012-05-08T17:27:20.932+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(1).|#]
>>>
>>> [#|2012-05-08T17:27:20.932+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(3).|#]
>>>
>>> [#|2012-05-08T17:27:20.932+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(5).|#]
>>>
>>> [#|2012-05-08T17:27:20.932+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(4).|#]
>>>
>>> [#|2012-05-08T17:27:22.207+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(1).|#]
>>>
>>> [#|2012-05-08T17:27:22.207+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(3).|#]
>>>
>>> [#|2012-05-08T17:27:22.207+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(5).|#]
>>>
>>> [#|2012-05-08T17:27:22.207+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(4).|#]
>>>
>>> [#|2012-05-08T17:27:23.319+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(1).|#]
>>>
>>> [#|2012-05-08T17:27:23.320+0300|WARNING|glassfish3.1.2|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=12;_ThreadName=Thread-2;|GRIZZLY0023:
>>> Interrupting idle Thread: http-thread-pool-8009(3).|#]
>>
>>
>