IS Windows Service suddenly stopped without evidence


Our customer has the problem of IS 8.0 SP1 Windows service suddenly stopped.
I just investigated the stats.log, server.log, error.log and gc.log (they set) but there
are no evidence of thecause like out of memory, etc.

I am referring the following document and suppose only that the hard disk might have no space.

Please sincerely give any advice about,

  • Other possible cause
  • Which file we should investigate for this time.
  • Which setting they should set for the next time.

Best regards,

Hi Shogo,

can you check the event viewer log of windows?

There should be an entry for the stop of the service.


Dear Holger-san,

Thanks for the reply and the advice.
I already received the 2 screen shots including the message like below
And I am asking them if there are other events.

  1. 2016/11/16 13:31:30
    Software AG webMethods Integration Server 8.0 (5555) service stopped because
    of the unexpected cause. This is the 1st failure.
    The following alternative operation will be executed within 900000 mill seconds:
    Restart the service.

  2. 2016/11/16/ 13:46:30
    Software AG webMethods Integration Server 8.0 (5555) service is started.

I just found the difference in the IS server.log being debug mode.
IS service stop this time might happen before “wmMQTransactionalConnection.begin() entered”.
Please sincerely give any advice.

2016-11-16 13:31:29 JST [ADA.0600.1002D] wmMQConnectionFactory:cleanConnectioncache() exit 2016-11-16 13:31:30 JST [ISP.0090.0003C] XXXXXX (from Application) 2016-11-16 13:46:32 JST [ISS.0025.0001C] Integration Server build 209 2016-11-16 12:30:44 JST [ADA.0600.1002D] wmMQConnectionFactory:cleanConnectioncache() exit 2016-11-16 12:30:45 JST [ISP.0090.0003C] XXXXXX (from Application) 2016-11-16 12:30:45 JST [ADA.0600.1001D] wmMQTransactionalConnection.begin() entered 2016-11-16 12:30:45 JST [ADA.0600.1003D] begin _inTransaction=true 2016-11-16 12:30:45 JST [ADA.0600.1002D] wmMQTransactionalConnection.begin() exit

Best regards,


Are you on a 32bit JVM?

I once had a problem when the 32bit JVM on Windows tried to cross the 32bit process’ RAM size limit.

The windows process of the IS would suddenly die, without warnings or errors…

Try to reduce the max memory of the IS or changing to a 64bit JVM (I think there is a fix for the 8.0 for that but I’m not too sure).

Best Regards,

Gerardo Lisboa-san,

Thanks for the reply very much.
Their IS 8.0 SP1 is 64bit on Windows 2008 R2.
I just got the “hs_err_pid9204.log” of JVM error as the attached.

Could you provide with any idea about data in this file?

(The following is the part of the file.“db2jdbc.dll” is the somewhat cause?)

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000018000c786, pid=9204, tid=7800

JRE version: 6.0_19-b04

Java VM: Java HotSpot™ 64-Bit Server VM (16.2-b04 mixed mode windows-amd64 )

Problematic frame:

C [db2jdbc64.dll+0xc786]

If you would like to submit a bug report, please visit:

Bug Report

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

Best regards,
hs_err_pid9204.log (51.1 KB)

Hi Shogo,

looks like an issue with your database connectivity to IBMs DB2.

Can you share some informations about db version, driver version and connection config?

If possible try to switch connection mode to plain JDBC Type 4 (Thin) driver, which is pure java and does not need to rely on the dll.

You can obtain this driver from IBM developer network fro free.


Dear Holger-san,

Thanks for the reply very much.
I am confirming to the customer about the configuration of IS, JDBC Apdapter and DB2 (or DB2Connect).

When I got them from him, please sincerely let me get back to you

Best regards,