Professional Documents
Culture Documents
The HTTP Response status codes beginning with the digit "5" indicates cases in
which the server is aware that it has encountered an error or is otherwise
incapable of performing the request. Any client (e.g. the Web browser ) goes
through the following cycle when it communicates with Web server:
The error '500 Internal Server Error' is a very generic error message. This error
can only be resolved by fixes to the Web server end and generally not a client-side
problem. Hence it is important to locate and analyse the logs which should give
further information about the error.
Error Block:
Check each of the error blocks for the complete error details. If it is matching
the error details what is observed at your instance then refer the suggested
solution.
Symptom:1
Browser Error : If You receive following error while accessing E-Business R12
instance
Application.log:
Solution:1
Make sure your System Profile "JTF_DIST_CACHE_PORT" has the same port specified as
the value mentioned for variable: s_java_object_cache_port in context file. You can
check the sytem profile value by running following sql
For any issues with Guest user password mismatch, please refer the following note
Note 443353.1 -- How To Successfully Change The Guest Password In E-Business Suite
11.5.10 and R12
Symptom:2
Application.log
Exception in static block of jtf.cache.CacheManager. Stack trace is:
oracle.apps.jtf.base.resources.FrameworkException: IAS Cache initialization failed.
The Distributed
Caching System failed to initialize on port: 12345. The list of hosts in the
distributed cac
hing system is: . The port 12345 should be free on each host running the JVMs. The
default port 12345 can be overridden
using -Doracle.apps.jtf.cache.IASCacheProvidercacheProvider.port=
The Java object Controller issue are generally specific to AIX platform. This
failure was a result of the Applications JDK missing required java.security updates
specific to the applications server and a port specific code issue within
cache.jar.
Solution:2
Alternative Solution
Incase the above solutions doesnot solve the issue, then following steps can also
be carried out after taking proper backup of the system
1. Remove any *.lock files in $ORA_CONFIG_HOME/10.1.3/j2ee//persistence//
3. Ensure that all the middle tier services are running fine with following command
$ adopmnctl.sh status -l
You are running adopmnctl.sh version 120.4.12000000.3
Checking status of OPMN managed processes...
5. If the instance has been created by cloning another instance or any issues with
listener configuration is suspected then create a clean autoconfig envrionment and
rerun autoconfig. Refer the following note
7. Compile all JSP files after sourcing the environment. Run the command
cd $FND_TOP/patch/115/bin
ojspCompile.pl --compile --flush
8. If feasible, completely reboot the instance. Stop all middle tier services and
stop database services as well OS services. Then restart all those services.
1. Access the following URL and complete all tests. Upload the result output to the
associated metalink SR
http://host.domain:port/OA_HTML/jsp/fnd/aoljtest.jsp
(Replace the host, domain, port value with your instance details )
2. Upload the debug log files instance after reproducing the issue. You may refer
following note for the same
Note 422419.1 -- R12 - How To Enable and Collect Debug for HTTP, OC4J and OPMN