Hello,

We are experiencing a very strange issue. Every now and then the Integration Server gets restarted even though nobody from our team runs the restart script or restarts it from the admin page. When looking into the server.log we always notice that it looks as if the Integration Server suddenly restarts itself and there are no errors found in the log before the standard IS start log entries. Do you happen to know if on 9.9 servers the IS can get restarted by itself?
The issue is kinda urgent as it happens on our productive servers.

Our IS settings:

Version:9.9.0.0
Fix level: IS_9.9_Core_Fix11

Thank you in advance,
n23

Hi,

please have a look at the profiles/IS/logs/wrapper.log for the affected instance.

Looks like the jvm crashes for some reasons and wrapper is detecting this and restarts the server.

Regards,
Holger

Hi Holger,

Indeed this is the cause. I can see following log entries:

STATUS | wrapper | 2017/08/02 01:31:16 | JVM received a signal SIGKILL (9).
STATUS | wrapper | 2017/08/02 01:31:16 | JVM process is gone.
ERROR | wrapper | 2017/08/02 01:31:16 | JVM exited unexpectedly.
STATUS | wrapper | 2017/08/02 01:31:20 | Launching a JVM…
INFO | jvm 3 | 2017/08/02 01:31:21 | Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
INFO | jvm 3 | 2017/08/02 01:31:21 | WrapperManager: Initializing…

INFO | jvm 1 | 2017/08/01 15:38:06 | Java HotSpot™ 64-Bit Server VM warning: INFO: os::commit_memory(0x000000050eb00000, 1221591040, 0) failed; error=‘Cannot allocate memory’ (errno=12)
INFO | jvm 1 | 2017/08/01 15:38:06 | #
INFO | jvm 1 | 2017/08/01 15:38:06 | # There is insufficient memory for the Java Runtime Environment to continue.
INFO | jvm 1 | 2017/08/01 15:38:06 | # Native memory allocation (mmap) failed to map 1221591040 bytes for committing reserved memory.
INFO | jvm 1 | 2017/08/01 15:38:06 | # An error report file with more information is saved as:
INFO | jvm 1 | 2017/08/01 15:38:06 | # /IS/99/IntegrationServer/instances/default/hs_err_pid11041.log
ERROR | wrapper | 2017/08/01 15:38:08 | JVM exited unexpectedly.
STATUS | wrapper | 2017/08/01 15:38:13 | Launching a JVM…
INFO | jvm 2 | 2017/08/01 15:38:13 | Java HotSpot™ 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0

Can you please tell us what should be done to avoid this issue in the future?

Thanks,
n23

Hi,

please check your setenv.sh for memory setings and increase the max heap size.

Regards,
Holger

Ok. Thank you for your support!

Best regards,
n23