I have faced issue on WM 9.7 Integration server installed on OS Window where as we have trying to identify how WM server was auto or manually restart?
I have attached WM server logs for your reference can some one have a look and let me know if they find any pointer why this server was restarted, Was it due to any other component issue or any manual interaction.
Manual restart : While i have checked in my security logs and didn’t notice any kind of manual restart so trying to identify How come this server got auto restart.
Integration server shut down and restart was graceful and even i can see all start/stop entries in server logs as well as we never encounter low memory or any kind of db space issue.
Adding to that we don’t have any window scheduled job but have normal window services for software ag integration server where start up type is automatic.
I would be more interested in how and why it restarted. Unless you have some auto-restart code in the batch file (server.bat)(or some job scheduling/monitoring application restarts it) , the IS should not restart itself as describe.
IS is started and monitored by separate process called Tanuki wrapper.
This wrapper is configured to detect whether IS JVM is not responsive (like Loop consuming CPU) or has OOM (Out Of Memory). In such cases the wrapper will restart IS.
To analyze - you can open Global Support ticket.
You can also inspect /profiles/IS_default/logs/wrapper.log for restart initiated by the wrapper.
Look for string “Launching JVM” for IS restart, and preceding lines for the reason.
After analysis - configuration can be done using /profiles/IS-Default/configuration/custom_wrapper.conf…
Rajiv – As per me, its done manually as I can see there is a difference of 2 minutes b/w shutdown and re-start as per your logs. If it is done by system then we might not have that much time gap. Can you check.
I believe as per the logs its some how IS is malfunctioning or not responded with process auto restart by its own and it could also be http port itself not reaching some hiccups as the logs Holger mentioning above for some reason.
Is this happening since after install or can you redo install and configure the Insance IS_Default setting up the custom_wrapper and wrapper config’s as Shmuel suggests?
I have pulled my WM server OS window wrapper.log can you provide any further pointers which need to analyse?
sure after doing few more analysis will approach sag support team till then gathering reqd info
MR as173d@ If server get restart by system itself will it not take more than 2 mins, how to identify that restart was perform via manual action not by system itself < nothing has capture in security logs>
Holger@
Check the HTTP-Port as the shutdown sequence mentions a port 9400 which is not opened again after restart.
I slightly modify my server logs so that by mistake i should not be posting client info in public forum
so by mistake this line got deleted 2015-12-11 07:27:40 CST [ISP.0046.0012I] Enabling HTTP Listener on
Can you pls past line or statement from server log which suggest below your analysis will be helpful in future
Shutdown was incomplete.
Shutdown was triggered from console (shutdown.sh) or wrapper.
@RMG we are using this server from couple of years and it has been used by business so can’t go for reinstall
The wrapper.log is truncated at the top.
As I mentioned - you look for 1) and 2) below
Lines like these with eye catcher “Launching a JVM” - which mean wrapper start the server:
STATUS | wrapper | 2015/12/11 07:23:02 | Base configuration file is D:\webMethods\profiles\IS_XYZ\configuration\wrapper.conf
STATUS | wrapper | 2015/12/11 07:23:02 | Found #include file in D:\webMethods\profiles\IS_XYZ\configuration\wrapper.conf: D:\webMethods\profiles\IS_XYZ/configuration/wrapper-license.conf
STATUS | wrapper | 2015/12/11 07:23:02 | Reading included configuration file, D:\webMethods\profiles\IS_XYZ\configuration\wrapper-license.conf
STATUS | wrapper | 2015/12/11 07:23:02 | Found #include file in D:\webMethods\profiles\IS_XYZ\configuration\wrapper.conf: D:\webMethods\profiles\IS_XYZ/configuration/custom_wrapper.conf
STATUS | wrapper | 2015/12/11 07:23:02 | Reading included configuration file, D:\webMethods\profiles\IS_XYZ\configuration\custom_wrapper.conf
STATUS | wrapper | 2015/12/11 07:23:02 | → Wrapper Started as Service
STATUS | wrapper | 2015/12/11 07:23:02 | Java Service Wrapper Standard Edition 64-bit 3.5.25
STATUS | wrapper | 2015/12/11 07:23:02 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2015/12/11 07:23:02 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2015/12/11 07:23:02 | Licensed to Software AG for Software AG Integration Server
STATUS | wrapper | 2015/12/11 07:23:02 |
STATUS | wrapper | 2015/12/11 07:23:03 | Launching a JVM…
INFO | jvm 1 | 2015/12/11 07:23:09 | WrapperManager: Initializing…
Look at preceding lines why it was closed. Here the file is truncated. Cannot be analyzed.
In other words, lines before these are missing/truncated:
STATUS | wrapper | 2015/12/11 07:21:52 | Machine is shutting down.
INFO | jvm 1 | 2015/12/11 07:21:53 | Bootstrap: Remote shutdown is disabled.
INFO | jvm 1 | 2015/12/11 07:21:57 | MapiCommunication.destroy() called
one reason for incomplete shutdown might be that it took to long and wrapper killed the IS JVM process.
Usually the Common.CDS portion is shutdown at the end of shutdown sequence.
This would also explain the FS Full Data checks (FSData full consistency check is being performed.) in the startup sequence.
