topic Re: SAS Environment Manager does not properly shutdown in Administration and Deployment

SAS Environment Manager does not properly shutdown

ScottBass — Sun, 15 Mar 2015 23:59:47 GMT

Hi,

SAS9.4/Windows Server 2012

I'm getting this message in my SAS Environment Manager wrapper.log:

STATUS | wrapper | 2015/03/13 23:02:49 | The SAS [Config-Lev1] SAS Environment Manager Service is not installed.

STATUS | wrapper | 2015/03/13 23:02:49 | SAS [Config-Lev1] SAS Environment Manager service installed.

STATUS | wrapper | 2015/03/13 23:02:49 | Starting the SAS [Config-Lev1] SAS Environment Manager service...

STATUS | wrapper | 2015/03/13 23:02:49 | --> Wrapper Started as Service

STATUS | wrapper | 2015/03/13 23:02:49 | Java Service Wrapper Community Edition 32-bit 3.5.6

STATUS | wrapper | 2015/03/13 23:02:49 | http://wrapper.tanukisoftware.com

STATUS | wrapper | 2015/03/13 23:02:49 |

STATUS | wrapper | 2015/03/13 23:02:50 | Launching a JVM...

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: Initializing...

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager:

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: WARNING - Unable to load the Wrapper's native library because none of the

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: following files:

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: wrapper-windows-x86-64.dll

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: wrapper.dll

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: could be located on the following java.library.path:

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\%LD_LIBRARY_PATH%

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\%LIBPATH%

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\%SHLIB_PATH%

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\..\..\wrapper\lib

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\..\lib

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: Please see the documentation for the wrapper.java.library.path

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: configuration property.

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager: System signals will not be handled correctly.

INFO | jvm 1 | 2015/03/13 23:02:50 | WrapperManager:

STATUS | wrapper | 2015/03/13 23:02:53 | SAS [Config-Lev1] SAS Environment Manager started.

INFO | jvm 1 | 2015/03/13 23:02:53 | Mar 13, 2015 11:02:53 PM org.apache.tomcat.jdbc.pool.ConnectionPool init

INFO | jvm 1 | 2015/03/13 23:02:53 | WARNING: maxIdle is larger than maxActive, setting maxIdle to: 100

Is this a bug in the SAS installation? There is no wrapper-windows-x86-64.dll nor wrapper.dll under E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE. There is, however, E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\lib\wrapper-windows-x86-32.dll. There are also wrapper.dll files under the agent and hq-engine directories, but with varying sizes.

I assume I can copy wrapper-windows-x86-32.dll as wrapper.dll and copy it into a directory in the java.library.path. But I'm wondering 1) if this is correct, and 2) why I would need to do this?

SAS Environment Manager is also not shutting down properly, I assume because of the above issue:

INFO | jvm 1 | 2015/03/14 10:26:04 | [HQServer.main(stop)]: Shutdown of type 'NormalStop' was request

ERROR | wrapper | 2015/03/14 10:27:39 | Shutdown failed: Timed out waiting for signal from JVM.

It times out in the Windows Services snapin, and a java process remains running. I have to manually kill that process to free handles on the logs and restart the service.

The installation of SAS and the Environment Manager had no errors and was relatively uneventful.

Re: SAS Environment Manager does not properly shutdown

ScottBass — Mon, 16 Mar 2015 00:23:39 GMT

So I copied E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\lib\wrapper-windows-x86-32.dll as E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\lib\wrapper.dll but now get this:

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: The file is located on the path at the following location but

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: could not be loaded:

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\..\..\wrapper\lib\wrapper.dll

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: Please verify that the file is both readable and executable by the

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: current user and that the file has not been corrupted in any way.

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: One common cause of this problem is running a 32-bit version

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: of the Wrapper with a 64-bit version of Java, or vica versa.

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: This is a 64-bit JVM.

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: Reported cause:

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: E:\SAS\Config\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform

INFO | jvm 1 | 2015/03/16 11:15:51 | WrapperManager: System signals will not be handled correctly.

Re: SAS Environment Manager does not properly shutdown

SASKiwi — Mon, 16 Mar 2015 00:51:33 GMT

Scott, this is a documented issue. Environment Manager has to be stopped and started via a BAT file not simply by stopping and starting services:

52668 - A SAS® Environment Manager agent either fails to start or it starts and does not send data

There are a few other SAS notes you might want to check out too.

Re: SAS Environment Manager does not properly shutdown

ScottBass — Mon, 16 Mar 2015 01:37:04 GMT

Thanks @SASKiwi, but that KB article is about the Environment Manager Agent, not the Environment Manager. And I don't get from that article where starting and stopping the service via the Services snapin (and by extension the Start-Service and Stop-Service Powershell cmdlets) are prohibited. It even states "3. Start the SAS Environment Manager agent how you normally start it".

Re: SAS Environment Manager does not properly shutdown

SASKiwi — Mon, 16 Mar 2015 01:56:54 GMT

Yes, its the Environment Manager Agent I was talking about sorry. We found if we didn't start and stop this way then our SAS Web Server became overloaded with EMA errors and kept using 100% of its CPU! It was also a recommendation from SAS Tech Support.

I do suggest you check out the other EM notes however.

Re: SAS Environment Manager does not properly shutdown

ScottBass — Mon, 16 Mar 2015 01:58:35 GMT

And here are the results when I use the BAT file in my Lev9 environment:

cmd console output:

E:\SAS\Config\Lev9\Web\SASEnvironmentManager\server-5.8.0-EE\bin>hq-server.bat start

wrapper | Starting the SAS [Config-Lev9] SAS Environment Manager service...

wrapper | SAS [Config-Lev9] SAS Environment Manager started.

E:\SAS\Config\Lev9\Web\SASEnvironmentManager\server-5.8.0-EE\bin>hq-server.bat stop

wrapper | Stopping the SAS [Config-Lev9] SAS Environment Manager service...

wrapper | Waiting to stop...

wrapper | SAS [Config-Lev9] SAS Environment Manager stopped.

wrapper.log:

STATUS | wrapper | 2015/03/16 12:47:26 | Starting the SAS [Config-Lev9] SAS Environment Manager service...

STATUS | wrapper | 2015/03/16 12:47:26 | --> Wrapper Started as Service

STATUS | wrapper | 2015/03/16 12:47:26 | Java Service Wrapper Community Edition 32-bit 3.5.6

STATUS | wrapper | 2015/03/16 12:47:26 | http://wrapper.tanukisoftware.com

STATUS | wrapper | 2015/03/16 12:47:26 |

STATUS | wrapper | 2015/03/16 12:47:26 | Launching a JVM...

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: Initializing...

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager:

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: WARNING - Unable to load the Wrapper's native library because none of the

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: following files:

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: wrapper-windows-x86-64.dll

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: wrapper.dll

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: could be located on the following java.library.path:

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: E:\SAS\Config\Lev9\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\%LD_LIBRARY_PATH%

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: E:\SAS\Config\Lev9\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\%LIBPATH%

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: E:\SAS\Config\Lev9\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\%SHLIB_PATH%

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: E:\SAS\Config\Lev9\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\..\..\wrapper\lib

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: E:\SAS\Config\Lev9\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\sbin\..\lib

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: Please see the documentation for the wrapper.java.library.path

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: configuration property.

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager: System signals will not be handled correctly.

INFO | jvm 1 | 2015/03/16 12:47:27 | WrapperManager:

STATUS | wrapper | 2015/03/16 12:47:31 | SAS [Config-Lev9] SAS Environment Manager started.

INFO | jvm 1 | 2015/03/16 12:47:34 | Mar 16, 2015 12:47:34 PM org.apache.tomcat.jdbc.pool.ConnectionPool init

INFO | jvm 1 | 2015/03/16 12:47:34 | WARNING: maxIdle is larger than maxActive, setting maxIdle to: 100

STATUS | wrapper | 2015/03/16 12:48:35 | Stopping the SAS [Config-Lev9] SAS Environment Manager service...

INFO | jvm 1 | 2015/03/16 12:48:35 | [HQServer.main(stop)]: Shutdown of type 'NormalStop' was request

INFO | wrapper | 2015/03/16 12:48:40 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:48:45 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:48:50 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:02 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:07 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:12 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:22 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:27 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:33 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:38 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:43 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:48 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:53 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:49:58 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:50:03 | Waiting to stop...

INFO | wrapper | 2015/03/16 12:50:08 | Waiting to stop...

ERROR | wrapper | 2015/03/16 12:50:10 | Shutdown failed: Timed out waiting for signal from JVM.

STATUS | wrapper | 2015/03/16 12:50:10 | Dumping JVM state.

INFO | jvm 1 | 2015/03/16 12:50:10 | 2015-03-16 12:50:10

INFO | jvm 1 | 2015/03/16 12:50:10 | Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.51-b03 mixed mode):

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "WrapperListener_stop_runner" prio=6 tid=0x000000000769a000 nid=0x63fc waiting on condition [0x000000000a91f000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: TIMED_WAITING (sleeping)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.sleep(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.tanukisoftware.wrapper.WrapperStartStopApp.stop(WrapperStartStopApp.java:466)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.tanukisoftware.wrapper.WrapperManager$13.run(WrapperManager.java:4214)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Thread-4" daemon prio=6 tid=0x0000000007695800 nid=0x82fc runnable [0x000000000a81f000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.FileInputStream.readBytes(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.FileInputStream.read(FileInputStream.java:243)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.util.exec.StreamPumper.run(StreamPumper.java:124)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.run(Thread.java:744)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Thread-3" daemon prio=6 tid=0x0000000007694000 nid=0x5144 runnable [0x000000000969f000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.FileInputStream.readBytes(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.FileInputStream.read(FileInputStream.java:272)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.BufferedInputStream.read(BufferedInputStream.java:334)

INFO | jvm 1 | 2015/03/16 12:50:10 | - locked <0x00000000fd9c0418> (a java.io.BufferedInputStream)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.io.FilterInputStream.read(FilterInputStream.java:107)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.util.exec.StreamPumper.run(StreamPumper.java:124)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.run(Thread.java:744)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "[Pool-Cleaner]:Tomcat Connection Pool[1-1857196397]" daemon prio=6 tid=0x0000000007695000 nid=0x8a48 waiting on condition [0x000000000959f000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: TIMED_WAITING (sleeping)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.sleep(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.apache.tomcat.jdbc.pool.ConnectionPool$PoolCleaner.run(ConnectionPool.java:1172)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "WrapperStartStopAppMain" prio=6 tid=0x0000000007698000 nid=0x8ff8 runnable [0x00000000084ce000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.ProcessImpl.waitForInterruptibly(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.ProcessImpl.waitFor(ProcessImpl.java:448)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.util.exec.Execute.waitFor(Execute.java:362)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.util.exec.Execute.execute(Execute.java:333)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.bootstrap.ProcessManagerImpl.executeProcess(ProcessManagerImpl.java:110)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.bootstrap.ProcessManagerImpl.executeProcess(ProcessManagerImpl.java:84)

INFO | jvm 1 | 2015/03/16 12:50:10 | at com.hyperic.bootstrap.TcServerEngineController.start(TcServerEngineController.java:90)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.bootstrap.HQServer.start(HQServer.java:152)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.hyperic.bootstrap.HQServer.main(HQServer.java:272)

INFO | jvm 1 | 2015/03/16 12:50:10 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

INFO | jvm 1 | 2015/03/16 12:50:10 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.reflect.Method.invoke(Method.java:606)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.tanukisoftware.wrapper.WrapperStartStopApp.run(WrapperStartStopApp.java:245)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.run(Thread.java:744)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "DestroyJavaVM" prio=6 tid=0x0000000007697000 nid=0x65a4 waiting on condition [0x0000000000000000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Wrapper-Connection" daemon prio=6 tid=0x0000000007693800 nid=0x7fa0 in Object.wait() [0x00000000082cf000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: WAITING (on object monitor)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Object.wait(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | - waiting on <0x00000000fd732560> (a org.tanukisoftware.wrapper.WrapperManager$13)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.join(Thread.java:1280)

INFO | jvm 1 | 2015/03/16 12:50:10 | - locked <0x00000000fd732560> (a org.tanukisoftware.wrapper.WrapperManager$13)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.join(Thread.java:1354)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.tanukisoftware.wrapper.WrapperManager.privilegedStopInner(WrapperManager.java:4246)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.tanukisoftware.wrapper.WrapperManager.handleSocket(WrapperManager.java:4977)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:5327)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.run(Thread.java:744)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Wrapper-Control-Event-Monitor" daemon prio=6 tid=0x0000000007696800 nid=0x5bc8 waiting on condition [0x00000000080cf000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: TIMED_WAITING (sleeping)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Thread.sleep(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | at org.tanukisoftware.wrapper.WrapperManager$3.run(WrapperManager.java:908)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Service Thread" daemon prio=6 tid=0x000000000578c800 nid=0x1c34 runnable [0x0000000000000000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "C2 CompilerThread1" daemon prio=10 tid=0x000000000578a800 nid=0x8e44 waiting on condition [0x0000000000000000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "C2 CompilerThread0" daemon prio=10 tid=0x0000000005787000 nid=0x83e4 waiting on condition [0x0000000000000000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Attach Listener" daemon prio=10 tid=0x0000000005786000 nid=0x143c runnable [0x0000000000000000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Signal Dispatcher" daemon prio=10 tid=0x0000000001a9b800 nid=0x8898 waiting on condition [0x0000000000000000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: RUNNABLE

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Finalizer" daemon prio=8 tid=0x0000000005764800 nid=0x760c in Object.wait() [0x0000000006aef000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: WAITING (on object monitor)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Object.wait(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | - waiting on <0x00000000ff608b40> (a java.lang.ref.ReferenceQueue$Lock)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)

INFO | jvm 1 | 2015/03/16 12:50:10 | - locked <0x00000000ff608b40> (a java.lang.ref.ReferenceQueue$Lock)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "Reference Handler" daemon prio=10 tid=0x0000000005763000 nid=0x8764 in Object.wait() [0x00000000069ee000]

INFO | jvm 1 | 2015/03/16 12:50:10 | java.lang.Thread.State: WAITING (on object monitor)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Object.wait(Native Method)

INFO | jvm 1 | 2015/03/16 12:50:10 | - waiting on <0x00000000ff608cc8> (a java.lang.ref.Reference$Lock)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.Object.wait(Object.java:503)

INFO | jvm 1 | 2015/03/16 12:50:10 | at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)

INFO | jvm 1 | 2015/03/16 12:50:10 | - locked <0x00000000ff608cc8> (a java.lang.ref.Reference$Lock)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "VM Thread" prio=10 tid=0x0000000005761000 nid=0x3324 runnable

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "GC task thread#0 (ParallelGC)" prio=6 tid=0x00000000019ba000 nid=0x4ad4 runnable

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "GC task thread#1 (ParallelGC)" prio=6 tid=0x00000000019bb800 nid=0x1e7c runnable

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "GC task thread#2 (ParallelGC)" prio=6 tid=0x00000000019bd000 nid=0x43e4 runnable

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "GC task thread#3 (ParallelGC)" prio=6 tid=0x00000000019bf000 nid=0x1a44 runnable

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | "VM Periodic Task Thread" prio=10 tid=0x00000000057d6000 nid=0x75fc waiting on condition

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | JNI global references: 216

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | jvm 1 | 2015/03/16 12:50:10 | Heap

INFO | jvm 1 | 2015/03/16 12:50:10 | PSYoungGen total 38912K, used 17716K [0x00000000fd500000, 0x0000000100000000, 0x0000000100000000)

INFO | jvm 1 | 2015/03/16 12:50:10 | eden space 33792K, 37% used [0x00000000fd500000,0x00000000fe1540d8,0x00000000ff600000)

INFO | jvm 1 | 2015/03/16 12:50:10 | from space 5120K, 99% used [0x00000000ff600000,0x00000000ffaf9208,0x00000000ffb00000)

INFO | jvm 1 | 2015/03/16 12:50:10 | to space 5120K, 0% used [0x00000000ffb00000,0x00000000ffb00000,0x0000000100000000)

INFO | jvm 1 | 2015/03/16 12:50:10 | ParOldGen total 87040K, used 1826K [0x00000000f8000000, 0x00000000fd500000, 0x00000000fd500000)

INFO | jvm 1 | 2015/03/16 12:50:10 | object space 87040K, 2% used [0x00000000f8000000,0x00000000f81c8ad0,0x00000000fd500000)

INFO | jvm 1 | 2015/03/16 12:50:10 | PSPermGen total 21504K, used 16941K [0x00000000f2e00000, 0x00000000f4300000, 0x00000000f8000000)

INFO | jvm 1 | 2015/03/16 12:50:10 | object space 21504K, 78% used [0x00000000f2e00000,0x00000000f3e8b4e8,0x00000000f4300000)

INFO | jvm 1 | 2015/03/16 12:50:10 |

INFO | wrapper | 2015/03/16 12:50:13 | Waiting to stop...

ERROR | wrapper | 2015/03/16 12:50:14 | JVM did not exit on request, terminated

STATUS | wrapper | 2015/03/16 12:50:15 | <-- Wrapper Stopped

STATUS | wrapper | 2015/03/16 12:50:17 | SAS [Config-Lev9] SAS Environment Manager stopped.

Re: SAS Environment Manager does not properly shutdown

santzufe — Thu, 23 Sep 2021 15:29:42 GMT

Hi Scott,

could you solve the issue? I have the same issue and I can't find information to solve it. Thanks.

Re: SAS Environment Manager does not properly shutdown

Sajid01 — Mon, 27 Sep 2021 11:57:14 GMT

Under this situation I would stop SAS, leaving environment manager as it it.
Then reboot the machine.
Remove any lock files (.lck) in the environment manager server logs.

Then try restarting and stopping SAS again to see if the environment manager stops properly.
If this does not work, approach SAS Tech Support.

Re: SAS Environment Manager does not properly shutdown

santzufe — Mon, 27 Sep 2021 15:04:54 GMT

Hello, thank you very much for the reply. The problem I have is that although the SAS Environment and SAS Environment Agent windows services are apparently running, I can't access the application. In the wrapper.log I see the same error that it can't find the .dll.

Re: SAS Environment Manager does not properly shutdown

Sajid01 — Mon, 27 Sep 2021 16:57:08 GMT

Hello
As pointed out by you I also see the following file only
[SASCONCFIG]/\Lev1\Web\SASEnvironmentManager\server-5.8.0-EE\wrapper\lib\wrapper-windows-x86-32.dll.

Nothing with -x86-64 at least in that folder. And the server runs fine.

The error could be an outcome of error at some other location or may be a faulty install.

(Remember if we miss a semi colon after data somefile in a data step, SAS points that SET is not allowed in data statement and not about missing semicolon ).
As the thread is old, I presume you are able to maintain desired functionality. Just curios is the error persistent since the time of install OR crept in later on?
However it is better to take this with SAS Tech Support.

Re: SAS Environment Manager does not properly shutdown

ronf_sas — Mon, 27 Sep 2021 17:01:03 GMT

The messages about not being able to load the wrapper's native library are informational and do not indicate a problem. You will see these messages in a functioning EV wrapper.log.

Re: SAS Environment Manager does not properly shutdown

santzufe — Mon, 27 Sep 2021 17:42:01 GMT

Checking the log, the error has always been. Apparently that's not the problem. Thanks for the reply.

Re: SAS Environment Manager does not properly shutdown

santzufe — Mon, 27 Sep 2021 17:44:20 GMT

Hi. Thanks for your reply. I thought that was the problem, but it seems that it is not.