I noticed the following messages in my console after keeping the server idle for a day or so
[4/30/13 7:28:55:045 CDT] 0000002c AlarmThreadMo W UTLS0008W: The return of alarm thread "Deferrable Alarm : 3" (0000002a) to the alarm thread pool has been delayed for 10281 milliseconds. This may be preventing normal alarm function within the application server. The alarm listener stack trace is as follows:
at java.io.WinNTFileSystem.getLastModifiedTime(Native Method)
at java.io.File.lastModified(File.java:837)
at com.ibm.ws.classloader.ReloadableClassLoader.checkForUpdate(ReloadableClassLoader.java:241)
at com.ibm.ws.classloader.ClassLoaderManager.checkAndNotify(ClassLoaderManager.java:543)
at com.ibm.ws.classloader.ClassLoaderManager.access$000(ClassLoaderManager.java:82)
at com.ibm.ws.classloader.ClassLoaderManager$ReloadTimerTask.alarm(ClassLoaderManager.java:586)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:133)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659).
Here is what I found from IBM
http://www-01.ibm.com/support/docview.wss?uid=swg21623512
Adding
http://stackoverflow.com/questions/18860737/alarm-thread-warning-every-60-seconds
How to set JVM args on server
Application Server
[4/30/13 7:28:55:045 CDT] 0000002c AlarmThreadMo W UTLS0008W: The return of alarm thread "Deferrable Alarm : 3" (0000002a) to the alarm thread pool has been delayed for 10281 milliseconds. This may be preventing normal alarm function within the application server. The alarm listener stack trace is as follows:
at java.io.WinNTFileSystem.getLastModifiedTime(Native Method)
at java.io.File.lastModified(File.java:837)
at com.ibm.ws.classloader.ReloadableClassLoader.checkForUpdate(ReloadableClassLoader.java:241)
at com.ibm.ws.classloader.ClassLoaderManager.checkAndNotify(ClassLoaderManager.java:543)
at com.ibm.ws.classloader.ClassLoaderManager.access$000(ClassLoaderManager.java:82)
at com.ibm.ws.classloader.ClassLoaderManager$ReloadTimerTask.alarm(ClassLoaderManager.java:586)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:133)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659).
Here is what I found from IBM
http://www-01.ibm.com/support/docview.wss?uid=swg21623512
Adding
-Dcom.ibm.websphere.alarmthreadmonitor.threshold.millis=140000
to JVM args suppresses the warning successfully.http://stackoverflow.com/questions/18860737/alarm-thread-warning-every-60-seconds
How to set JVM args on server
Application Server
- In the Administration Console select Servers
- Expand Server Type and select WebSphere application servers
- Click on the name of your server
- Expand Java and Process Management and select Process Definition.
- Under the Additional Properties section, click Java Virtual Machine.
- Scroll down and locate the textbox for Generic JVM arguments.
1 comment:
-Dcom.ibm.websphere.alarmthreadmonitor.enabled=false it works for me.
Post a Comment