How to Resolve RMI, JMS and HTTP Port Conflicts for Standalone OC4J or JDeveloper (Doc ID 247740.1)

Last updated on OCTOBER 02, 2017

Applies to:

Oracle Containers for J2EE - Version 10.1.2.0.0 to 10.1.3.4.0 [Release AS10gR2 to AS10gR3]
Oracle JDeveloper - Version 10.1.2.0.0 to 10.1.3.4.0 [Release Oracle10g]
Information in this document applies to any platform.
***Checked for relevance on 07-Jul-2013***


Symptoms

The information in this article applies to:

Standalone OC4J and OC4J embedded in JDeveloper 10.1.2.x.x up to 10.1.3.4.0

Starting a second instance of standalone OC4J, but it fails with errors similar to these:


Error starting JMS-Server: Unable to bind socket: Address in use: JVM_Bind

Error starting ORMI-Server. Unable to bind socket: Address in use: JVM_Bind

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