topic The return of alarm of thread “Non-deferrable Alarm :0” websphere application server while stopping in Administration and Deployment

The return of alarm of thread “Non-deferrable Alarm :0” websphere application server while stopping

MG18 — Mon, 21 Jan 2019 16:28:16 GMT

Hi All,

I am trying stop the WebSphere server(SASServer8 ) using was admin console and getting below mentioned error :-

Error :-

[1/20/19 18:57:19:312 AST] 00000028 AdminHelper A ADMN1021I: An attempt is made to stop the SASServer8 server. [1/20/19 18:57:24:453 AST] 00000004 ApplicationMg A WSVR0217I: Stopping application: ibmasyncrsp [1/20/19 18:58:08:863 AST] 0000002c AlarmThreadMo W UTLS0008W: The return of alarm thread "Non-deferrable Alarm : 0" (00000004) to the alarm thread pool has been delayed for 49440 milliseconds. This may be preventing normal alarm function within the application server. The alarm listener stack trace is as follows: at com.ibm.ws.webcontainer.component.WebContainerImpl.stop(WebContainerImpl.java:679) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stop(ApplicationMgrImpl.java:1151) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStop(DeployedApplicationImpl.java:1324) at com.ibm.ws.runtime.component.DeployedModuleImpl.stop(DeployedModuleImpl.java:646) at com.ibm.ws.runtime.component.DeployedApplicationImpl.stop(DeployedApplicationImpl.java:1098) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stopApplication(ApplicationMgrImpl.java:922) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stop(ApplicationMgrImpl.java:875) at com.ibm.ws.runtime.component.ContainerHelper.stopComponent(ContainerHelper.java:475) at com.ibm.ws.runtime.component.ContainerHelper.stopComponents(ContainerHelper.java:459) at com.ibm.ws.runtime.component.ContainerImpl.stopComponents(ContainerImpl.java:650) at com.ibm.ws.runtime.component.ContainerImpl.stop(ContainerImpl.java:638) at com.ibm.ws.runtime.component.ApplicationServerImpl.stop(ApplicationServerImpl.java:257) at com.ibm.ws.runtime.component.ContainerHelper.stopComponent(ContainerHelper.java:475) at com.ibm.ws.runtime.component.ContainerHelper.stopComponents(ContainerHelper.java:459) at com.ibm.ws.runtime.component.ContainerImpl.stopComponents(ContainerImpl.java:650) at com.ibm.ws.runtime.component.ContainerImpl.stop(ContainerImpl.java:638) at com.ibm.ws.runtime.component.ServerImpl.stop(ServerImpl.java:615) at com.ibm.ws.runtime.component.ServerCollaborator$ShutdownHook$1.run(ServerCollaborator.java:738) at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5305) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5483) at com.ibm.ws.runtime.component.ServerCollaborator$ShutdownHook.run(ServerCollaborator.java:728) at com.ibm.ws.runtime.component.ServerCollaborator$StopAction.alarm(ServerCollaborator.java:692) at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:133) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1656).

had any one faced this issue before and found the solution ?

Is there any workaround for it?

Why this error is coming ? Will there be problem from SAS Application side or no ?

Will SAS support team help in it ?

Re: The return of alarm of thread “Non-deferrable Alarm :0” websphere application server while stopp

SimonDawson — Tue, 22 Jan 2019 09:40:59 GMT

Not sure that this is a SAS application problem since there are no SAS functions in any frame on that stack.

Does the container stop? If it does then is this a problem?

Re: The return of alarm of thread “Non-deferrable Alarm :0” websphere application server while stopp

MG18 — Sun, 10 Feb 2019 13:32:43 GMT

Does anyone know how to enable to trace option for SASServer in IBM WebSphere ?

Re: The return of alarm of thread “Non-deferrable Alarm :0” websphere application server while stopp

JuanS_OCS — Tue, 12 Feb 2019 15:23:14 GMT

Hello @MG18 ,

great question. This is an error related to WebSphere, however, due only to the fact that WebSphere versions are way too old, as per SAS requirements. For 9.3:

https://support.sas.com/en/documentation/third-party-software-reference/9-3/support-web-servers/ibm-websphere.html hence for SAS 9.3 the greatest version of WebSphere is 8.5.0.1.

What's going on is the fact that, probably, the memory if the SASServer8 is full of objects and the garbage collector is not working fast enough. Hence, giving a timeout. Then, Websphere raises what they call, an Alarm, and those versions cannot handle the alarm well.

Please see this IBM Note, it should explain more in detail and, hopefully, help:

https://www-01.ibm.com/support/docview.wss?uid=swg1PM71282

I would recommend to enable JMX monitoring of every WebSphere server https://www.ibm.com/support/knowledgecenter/en/SSYMRC_5.0.2/com.ibm.jazz.repository.web.admin.doc/topics/c_server_mon_was.html

This will give you a better overview of the JVMs Heap Sizes and the behaviour of the Garbage Colllectors.

In any case, as the note says, the solution is:

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.27, 8.0.0.5 and 8.5.0.1.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Re: The return of alarm of thread “Non-deferrable Alarm :0” websphere application server while stopp

JuanS_OCS — Tue, 12 Feb 2019 15:19:21 GMT

Does anyone know how to enable to trace option for SASServer in IBM WebSphere ?

For this question, Google is your friend:

https://www.google.nl/search?rlz=1C1GCEU_nlNL823NL827&ei=OeJiXLTNE82NkwWK7bO4DQ&q=WebSphere+enable+trace&oq=WebSphere+enable+trace&gs_l=psy-ab.3..0i203l2j0i22i30l8.404343.410629..411121...1.0..3.1227.9450.5j8j3j2j6-2j4......0....1..gws-wiz.....6..35i39j0j0i67j0i10j0i10i203.uMrtW0f8VNg