Applications Login Page Ends In 500 Internal Server Error After Start Of Services (Doc ID 1910999.1)

Last updated on JULY 25, 2017

Applies to:

Oracle Applications Manager - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

After a fresh clone of production, a "500 Internal Server Error" occurs on the login page:

500 Internal Server Error
Servlet error: An exception occurred.
The current application deployment descriptors do not allow for including it in this response.
Please consult the application log for details.


The issue is only resolved with a manual OACORE restart from "adoacorectl.sh". However, when the login page comes up, the error won't occur again until the next restart of the services.

One may have already tried the following steps to resolve it permanently, but it does not help:
 - Compiling all JSP files.
 - Force regeneration of all JAR files.

An error stack in log files when the issue occurs looks like: application.log.  For the first page access:

14/06/26 12:13:55.972 html: LeakSetting:
  global:true,session:false,aggressive:false,stderr:false,appslog:false,corelog:false
  ignoring:null
14/06/26 12:14:12.481 html: Servlet error
java.lang.ExceptionInInitializerError
  at oracle.apps.fnd.sso.AppsLoginRedirect.doGet(AppsLoginRedirect.java:909)


For all subsequent page accesses, the following results:

14/06/26 12:18:08.701 html: Servlet error
java.lang.NoClassDefFoundError: Could not initialize class oracle.apps.fnd.sso.SSOManager
  at oracle.apps.fnd.sso.AppsLoginRedirect.doGet(AppsLoginRedirect.java:909)


Currently, no permanent fix is available. The only workaround is to restart the oacore manually until it works fine.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms