Abhishek reported this error:
Internal Server Error
The Server encountered an internal error or misconfiguration and was unable to complete your request
Please contact the server administrator, applmgr@justanexample.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
192.168.1.32 - - [28/Jan/2009:09:23:46 -0500] "GET /oa_servlets/AppsSSOServlet/?urlc=v1.2~64B471D0DE31B9ABC28F471BB5DCF74F6583C912573EFBE43AE8001F4F33C31CE4
C01658BEF2F5DE748E13B748BA0CD3EC9B272181AC9A939DB5D75D6C9DA03435445B79EC48BC0B1CCD0764201C93309A2B3C77B1870912D4220B82FF987AF091E9576ABDF0FEA035EC8572556A19B
DB78035965C12BBB63B58E420C3FD37BB86BE2101B5C74879BBF26BEB55C1317BF9FFF6ADB234E480AF57B7156ED45E161D19D36C3D7435BD577E67F96866026C43B3D7AAAD980FDFD9D68576F99A
230B030B435000F61003EEC92225B7FD8DFCB8C34835A41E3CC6EDC7BFD09A9BAF563D7E284A75AD0785AA189D1E21F7BD0A99266AE3DD97EC4FED32AE6A867F81B25F93E5564561A76E348836B54
8F6B06184CBB963A67A28D6 HTTP/1.1" 500 543 0
mod_jserv.log:
[28/01/2009 09:39:24:897] (ERROR) an error returned handling request via protocol "ajpv12"
[28/01/2009 09:39:24:897] (ERROR) balance: 1775 internal servlet error in server dev14.justanexample.com:16220
[28/01/2009 09:39:24:897] (ERROR) an error returned handling request via protocol "balance"
[28/01/2009 09:52:12:600] (ERROR) ajp12: Servlet Error: java.lang.NoSuchMethodError: oracle.apps.fnd.sso.SessionMgr.setLang(Loracle/apps/fnd/common/WebAppsContext;Ljavax/servlet/http/HttpServletRequest;Ljava/lang/String;)V: oracle.apps.fnd.sso.SessionMgr.setLang(Loracle/apps/fnd/common/WebAppsContext;Ljavax/servlet/http/HttpServletRequest;Ljava/lang/String;)V
$IAS_CONFIG_HOME/Apache/Jserv/logs/jvm/OACoreGroup.0.stderr
java.lang.NoSuchMethodError: oracle.apps.fnd.sso.SessionMgr.setLang(Loracle/apps/fnd/common/WebAppsContext;Ljavax/servlet/http/HttpServletRequest;Ljava/lang/String;)V
at org.apache.jserv.JServConnection.processRequest(JServConnection.java:462)
at org.apache.jserv.JServConnection.run(JServConnection.java:294)
at java.lang.Thread.run(Thread.java:534)
Cause: Un-synchronized data in APPLSYS.WF_LOCAL_USER_ROLES:HZ_PARTY
Solution:
For non-OATM instances:
sql>
begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
P_PARALLEL_PROCESSES=>2,
P_LOGGING=>'LOGGING', P_RAISEERRORS=>TRUE,
P_TEMPTABLESPACE=>'APPLSYSX');
END;
/
For OATM instances:
sql>
begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
P_PARALLEL_PROCESSES=>2,
P_LOGGING=>'LOGGING', P_RAISEERRORS=>TRUE,
P_TEMPTABLESPACE=>'APPS_TS_TX_DATA'); END; /
Since we were on an OATM instance, we ran this pl/sql block after logging in as apps:
SQL> begin apps.wf_local_synch.BULKSYNCHRONIZATION(P_ORIG_SYSTEM=>'ALL',
2 P_PARALLEL_PROCESSES=>2,
3 P_LOGGING=>'LOGGING', P_RAISEERRORS=>TRUE,
4 P_TEMPTABLESPACE=>'APPS_TS_TX_DATA');
5 END;
6 /
PL/SQL procedure successfully completed.
SQL>
There was no need to bounce Apache. After running the above query, we were able to login without issues.
No comments:
Post a Comment