Warning thread warning every 60 seconds

I am running a local WAS 7.0 server for development purposes. My machine is Win 7, and I am using Java 1.6. Specific version of WAS:

IBM WebSphere Application Server, 7.0.0.25 Build Number: cf251235.04 Build Date: 8/30/12 

The version of Eclipse I am using is

 Eclipse Java EE IDE for Web Developers Version: Juno Service Release 2 Build id: 20130225-0426 

And the WebSphere Application Server 7.0 Eclipse plug-in

 com.ibm.websphere.v7.core (7.0.101.v20121205_2240) "WebSphere Application Server v7.0 Core Runtime Jars" [Active] 

The problem that I have, every two minutes or so, I get the following warning printed in the SystemOut.log file:

 [9/17/13 16:54:47:812 CDT] 00000025 AlarmThreadMo W UTLS0008W: The return of alarm thread "Non-deferrable Alarm : 2" (0000001f) to the alarm thread pool has been delayed for 40106 milliseconds. This may be preventing normal alarm function within the application server. The alarm listener stack trace is as follows: at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:196) at com.ibm.io.async.AbstractAsyncFuture.waitForCompletion(AbstractAsyncFuture.java:334) at com.ibm.io.async.AsyncFuture.getByteCount(AsyncFuture.java:218) at com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.readAIOSync(AioSocketIOChannel.java:215) at com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.processSyncReadRequest(AioTCPReadRequestContextImpl.java:182) at com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPReadRequestContextImpl.java:111) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext.read(SSLReadServiceContext.java:265) at com.ibm.ws.management.connector.ipc.ClientAccessor.clientReadMoreData(ClientAccessor.java:264) at com.ibm.ws.management.connector.ipc.ClientAccessor.request(ClientAccessor.java:169) at com.ibm.ws.management.connector.ipc.IPCConnectorClient.sendReceive(IPCConnectorClient.java:452) at com.ibm.ws.management.connector.ipc.IPCConnectorClient.pullNotifications(IPCConnectorClient.java:2167) at com.ibm.ws.management.event.PullRemoteReceiver.getNotifications(PullRemoteReceiver.java:222) at com.ibm.ws.management.event.PullRemoteReceiver.alarm(PullRemoteReceiver.java:183) at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:133) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646). [9/17/13 16:56:07:712 CDT] 0000001f AlarmThreadMo W UTLS0009W: Alarm Thread "Non-deferrable Alarm : 2" (0000001f) previously reported to be delayed has now completed. It was active for approximately 120007 milliseconds. 

This happens sequentially; since I get a “delay” warning, and after 2 minutes I get a “completed” warning. Then it takes about 60 seconds, and again I get the warning “delay”, after which the warning is “completed” again after about 2 minutes ... To infinity.

Besides ridiculous irritation; everything seems to be working fine ... I can publish / start / stop the server. My application is working fine.

I just want this warning to stop populating my SystemOut.log ... any suggestions?

PS I have the following set as my "general JVM arguments" in my server definition:

 -Xquickstart -Dcom.ibm.websphere.alarmthreadmonitor.threshold.millis=140000 -Dlog4j.debug-XX:+HeapDumpOnOutOfMemoryError-XX:HeapDumpPath=D:/temp 

The idea that setting "-Dcom.ibm.websphere.alarmthreadmonitor.threshold.millis = 140000" should increase the warning threshold to 140,000 ms instead of the default value of 40,000 ms (found from here )

+4
source share
3 answers

Turns out I had a typo in my JVM arguments regarding the com.ibm.websphere.alarmthreadmonitor.threshold.millis property.

Adding -Dcom.ibm.websphere.alarmthreadmonitor.threshold.millis=140000 to my arguments the JVM successfully suppresses the warning.

+4
source

In WAS8 and WAS85 there is a problem with false warnings:

http://www-01.ibm.com/support/docview.wss?uid=swg1PM85931

You can disable it with the following system property:

-Dcom.ibm.websphere.alarmthreadmonitor.hung_alarm_mute = 1

You must also enable diagnostic tracing to determine what is happening on your system. Use the following trace line: = info: com.ibm.ws.management.connector.ipc. = all

+1
source

I believe this is PM85931 . If you need a fix, I recommend opening PMR with IBM.

+1
source

Source: https://habr.com/ru/post/1502694/


All Articles