Java.Net.BindException: Address Already In Use While Starting Oc4j Process

(Doc ID 786992.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version and later
Information in this document applies to any platform.
***Checked for relevance on 05-Feb-2013 ***
Checked for relevancy on 13-Aug-2014


When recovering from a process failure for an OPMN managed OC4J process, it was not possible for OPMN to restart the OC4J instance.  opmnctl status will show the process as being down and attempts to start it up will fail.

Reported in the OPMN log file is the following message :-

ERROR 01.03.09 23:01:43 [cz.itsys.gtsrps.view.listener.BootstrapLoader 172] rps_viewcontroler - contextInitialized error Port already in use: 3251; nested exception is: Address already in use
java.rmi.server.ExportException: Port already in use: 3251; nested exception is: Address already in use

Caused by: Address already in use
        at Method)
        at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(
        at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(
        at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(
        at sun.rmi.transport.tcp.TCPTransport.listen(

09/03/01 23:01:45 WARNING: OC4J will not send ONS ProcReadyPort messages to opmn for service: OC4JServiceInfo id: null protocol: jms hostname: null port: 12604 description: null
09/03/01 23:01:45 null hostname was null
09/03/01 23:01:45 Oracle Containers for J2EE 10g (  initialized


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