My Oracle Support Banner

Unable to Start OC4J_Portal container in AS Portal 10g (Doc ID 2506785.1)

Last updated on JULY 16, 2019

Applies to:

Portal - Version to [Release 10gR2]
Information in this document applies to any platform.


OC4J Container does not start even though it is shown in stop status in the application server console and via OPMN script.

$ ./opmnctl status

Processes in Instance:
ias-component | process-type | pid | status
DSA | DSA | N/A | Down
LogLoader | logloaderd | N/A | Down
dcm-daemon | dcm-daemon | N/A | Down
OC4J | home | 30063 | Alive
OC4J | OC4J_Portal | 30064 | STOP
WebCache | WebCache | 29988 | Alive
WebCache | WebCacheAdmin | 29974 | Alive
HTTP_Server | HTTP_Server | 29975 | Alive


Error reported in the log (OC4J~OC4J_Portal~default_island~1) is as follows:

19/02/10 00:21:58 Stop process
Error: Could not connect to the remote server. Please check if the server is down or the client is using invalid host, ORMI port or password to connect: Connection refused



Most likely the service was killed instead of a gracious stop. 


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.