I found out that the error below was caused by wrong configuration of the security provider of the application opm-public. When we changed jazn.xml in $ORACLE_HOME/j2ee/[oc4j_container]/config directory with the correct settings and that solved this problem.
[Thu Aug 13 16:09:08 2009] [error] [client 10.8.192.155] [ecid: 1250172548:10.9.8.44:23073:0:7,0] mod_oc4j: Failed to find a failover oc4j process for session request for destination: application://opm-public (no island or jgroup).
[Thu Aug 13 16:09:08 2009] [error] [client [ip_address]] [ecid: 1250172548:10.9.8.44:23073:0:7,0] mod_oc4j: request to OC4J [hostname]:[port] failed: Connect failed
Did this post help you in any way can you please leave a comment? This will motivate me writing more posts.
![[Valid Atom 1.0]](http://4.bp.blogspot.com/_1DZkSxdocDo/SeRZqmezMfI/AAAAAAAAAI4/fkoNVB7dsv0/s400/valid-atom.png "Validate my Atom 1.0 feed")
Posts
5 reactions:
Can you please provide a bit more details about how you changed the jazb.xml?
Hi Sir,
I am interested in your article and your experience in OAS/IDM/SSO technology.
How can I contact you ? (my email is : xtanto@hotmail.com)
Thank you,
xtanto
When we changed jazn.xml in $ORACLE_HOME/j2ee/[oc4j_container]/config directory with the correct settings...
What were the correct settings?
That depends on your LDAP/OID. Normally in the $ORACLE_HOME/j2ee/home/config/jazn.xml the correct settings are set when you configure the Security Provider in Enterprise manager.
Thanks for the quick response.
I have one more question.
Before you updated the jazn.xml configuration file, was the problem an intermittent thing?
We are getting the same error, but it is not a consistent thing, it only happens sometimes. When it happens the oc4j instance has to be recycled to get the application responsive again. Is this the behavior you were seeing before you made the configuration changes for the security provider?
Post a Comment
comment