This content has been marked as final. Show 2 replies
The potential difference I could see is ojdbc jar version - would this problem solve if we upgrade/downgrade this jar in JBoss-2?
You should first test if JBOSS-2 can successfully failover.
The test you performed was with both JBoss services running and you found that service #1 failed over but service #2 did not.l
So shutdown service #1, leave service #2 running and test the failover. Either service #2 will fail over or the system will die.
If service #2 fails over then you can run out the ojdbc jar version being an issue. If service #2 doesn't fail over then you should just leave service #1 offline while you research and resolve the problem with service #2.
I would definitely want to try what you have suggested. But the problem we are facing is on production systems. We couldn't replicate this issue in lower environments because we don't have RAC set up. We have got only one server running in lower env.
So I posted here to know if this is already known problem.