“500 Internal Server Error” while accessing BPEL worklist
There are Active and Stand-by production sites in our architecture which has IDM and SOA nodes independent of each other. The BPEL worklist is integrated with OSSO, in turn with OAM and is working fine in Active production site. As discussed in the previous post for setting up Disaster Recovery of Oracle Application Server, we have just replicated the DB and copied the Oracle App server folder completely from Active to Stand-by sites.
We followed the metalink note 753087.1 for integrating BPEL worklist with OSSO. The osso.conf file generated in Active production site is used for configuring the BPEL worklist. We used the same osso.conf file to configure BPEL worklist in Stand-By site. Once configuration is completed, we accessed the BPEL worklist using the URL http://soa.oracle.com:7777/integration/worklistapp/Login and encountered with 500 Internal Server Error as shown in below screenshot.
We found the below error in SOA Apache logs.
[Wed Jun 15 17:30:02 2011] [error] [client 192.168.123.22] [ecid: 1308139202:10.200.37.36:929850:0:68,0] mod_oc4j: request toOC4J NIC-PSOABP1A-AR:12502 failed: unknown
[Wed Jun 15 17:36:58 2011] [error] [client 192.168.123.4] [ecid: 1308139618:10.200.37.36:598030:0:29,0] mod_oc4j: Failed to f
ind a failover oc4j process for session request for destination: application://ascontrol (no island or jgroup).
[Wed Jun 15 17:38:56 2011] [error] [client 192.168.123.4] [ecid: 1308139736:10.200.37.36:671912:0:57,0] mod_oc4j: Response st
atus=499 and reason=Oracle SSO, but failed to get mod_osso global context.
[Wed Jun 15 17:38:56 2011] [error] [client 192.168.123.4] [ecid: 1308139736:10.200.37.36:671912:0:57,0] mod_oc4j: request to
OC4J NIC-PSOABP1A-AR:12502 failed: Connect failed
Troubleshooting process: The solution is very simple that same hostnames were used for IDM nodes in both Active and Stand-by sites. The hostname were configured incorrectly in Stand-by environment and due to which the request from BPEL to OSSO (IDM) is not transferring and resulting in 500 Server error.
After rectifying the hostnames in SOA servers, we are able to login to BPEL worklist as shown below.
About the Author Mahendra
I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com