JMS Server Going Into Failed State With Error "Caused By: weblogic.store.io.jdbc.OwnershipException"
(Doc ID 2747037.1)
Last updated on JUNE 10, 2022
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
WebLogic domain with two managed servers, MS1 and MS2.
JMS server pointing to MS1 is working fine until MS2 is started. Once MS2 is started, JMS server pointing to MS1 is going into failed state and JMS server pointing to MS2 is looking fine. Managed servers are coming up in OK state, but JMS servers of MS1 is in a failed state.
Errors in logs:
The issue is caused by changing migration policy from either exactly-once or failure-recovery back to manual and still keeping the database leasing enabled.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document