Resequencer Instances Remain in Running State and Mediator Group in locked state 7 after Server Restart
Last updated on OCTOBER 30, 2017
Applies to:Oracle SOA Suite - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 12c]
Information in this document applies to any platform.
On : 220.127.116.11.170418 version, Mediator Service Engine
Instances created by Mediator services (running in a cluster) that use either FIFO or BestEffort resequencing strategy are stuck in running state after restarting servers. MEDIATOR_GROUP_STATUS table shows locked state of 7.
Instances should not remain in running state and should get completed after server restart.
The issue can be reproduced at will with the following steps:
1) Deploy Mediator composites that use FIFO and/or BestEffort sequencing strategy.
2) Generate instances.
3) Stop a server in the cluster mid processing.
4) Run the following database query to monitor the composites' Mediator group status, message status and instance count:
5) Bring up one server.
6) Rerun query.
Query shows the status of resequencers in MEDIATOR_GROUP_STATUS are locked (state 7). Also, the EM Console shows instances for both services are stuck in Running state.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms