Integration Server does not start as startup service schedule:init hangs: After migrate to wM10.1

,
1

Hi Guys,

We migrated webMethods97 to webMethods10.1 version with latest fix and now our Integration Server start up hang at below step:

[ISS.0028.0012I] WmRoot: Startup service (wm.server.schedule:init)

At the same time the database table IS_USER_TASKS is also locked and could not be accessed .

we did try to delete dispatch.cnf and restart the server but same issue.
This is happening only when we are putting IS in cluster. without clustering IS start without any issue.

Could you please help me ?

Thanks
Miki

2

Please check the JDBC pools function name “ISCoreAudit” pointing to same db schema on both the IS nodes.

Also, provide details about the cluster setup.

This a known issue in version 9.7, there is a fix as below, but you need to check if similar fixes are available for version 10.1

IS_8.2_SP2_Core_Fix19
IS_9.6_Core_Fix9
IS_9.7_Core_Fix7
IS_9.8_Core_Fix4
IS_9.9_Core_Fix2

The readme for the solution is following :

PIE-37898

Integration Server becomes unresponsive during startup.

Integration Server sometimes became unresponsive at startup when initializing the scheduler. This occurred because of a database deadlock.

This issue is now resolved and the deadlock will no longer occur.

3

Hi Mahesh,
yes both the server pointing to same JDBC pools function name “ISCoreAudit” and it is happening even 2 node is down.
we are using terracotta for cluster setup.
watt.server.cluster.aliasList=server-a,server-b
watt.server.cluster.aware=true
watt.server.cluster.name=abc

we could see this is included in webMethods 10.1 readme but still having issue.

Thanks
Miki

4

Hi Mahesh,
yes both the server pointing to same JDBC pools function name “ISCoreAudit” and it is happening even 2nd node is down.
we are using terracotta for cluster setup.
watt.server.cluster.aliasList=server-a,server-b
watt.server.cluster.aware=true
watt.server.cluster.name=abc

we could see this is included in webMethods 10.1 readme but still having issue.

Thanks
Miki

5

can you try bringing one of node up and then bring the second one to see if that helps

Else, you have to capture the diagnostic logs when this issue occurs to see what is really happening.

6

Hi Mahesh,
Problem is even one node is not getting up and to make them up I need to request DB team to clear the locking from IS_User_task table but if we will restart the server again we will face slimier issue

No error found in diagnostic logs

Thanks
Miki