OPMN and WebLogic AdminServer Port Conflicts When Configuring PFRD and IDM (OID) 11g on Same Host Machine
(Doc ID 1133653.1)
Last updated on JULY 01, 2024
Applies to:
Oracle Fusion Middleware - Version 11.1.1.2.0 to 11.1.1.9.0 [Release Oracle11g]Information in this document applies to any platform.
Symptoms
Example Scenario:
Portal/Forms/Reports/Discoverer (PFRD) 11g and Oracle Identity Management (OID/DIP) 11g have been configured on the same machine.
Important to Note:
Installing PFRD and IDM in the same MIDDLEWARE_HOME (MW_HOME) is not recommended. This is stated in the Release Notes located in the 11.1.1.2 Documentation Library e.g.
Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86
2.2.1 Installing Oracle SOA Suite and Oracle Portal, Forms, Reports and Discoverer in the Same Middleware Home
Co-location is not recommended for the following reasons:
This means that other products, such as IDM, cannot consume a later patchset (e.g. 11.1.1.5) if they reside in the same MW_HOME as PFRD. Why? Because the patchset level is restricted by the WebLogic Server version required by PFRD.
PFRD and IDM 11g solutions can reside on the same machine, but they must be built in separate Middleware Homes. If two Middleware Homes on the same machine are used, the issue discussed in this support document may be seen as port conflicts arise at an operating system level.
Installing PFRD and IDM in the same MIDDLEWARE_HOME (MW_HOME) is not recommended. This is stated in the Release Notes located in the 11.1.1.2 Documentation Library e.g.
Oracle Fusion Middleware Release Notes 11g Release 1 (11.1.1) for Linux x86
2.2.1 Installing Oracle SOA Suite and Oracle Portal, Forms, Reports and Discoverer in the Same Middleware Home
Co-location is not recommended for the following reasons:
- patchset version and WebLogic Server version compatibility
- the patching story for PFRD being out of sync with other Fusion Middleware products.
This means that other products, such as IDM, cannot consume a later patchset (e.g. 11.1.1.5) if they reside in the same MW_HOME as PFRD. Why? Because the patchset level is restricted by the WebLogic Server version required by PFRD.
PFRD and IDM 11g solutions can reside on the same machine, but they must be built in separate Middleware Homes. If two Middleware Homes on the same machine are used, the issue discussed in this support document may be seen as port conflicts arise at an operating system level.
At configuration time, the 'Auto Port' option was chosen in the Configuration Assistant.
Post configuration an attempt is made to start up the two configurations - (Portal/Forms/Reports/Discoverer and Identity Management (OID/DIP) concurrently. All components in the first configuration (e.g PFRD) start up fine. The components in the second configuration do not start successfully e.g
- OPMN fails to start - the following error is thrown
RCV: No such file or directory
Communication error with the OPMN server local port.
Check the OPMN log files - Weblogic AdminServer fails to start - the following error is thrown
.. <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
.. <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[1]". The address IP might be incorrect or another process is using port 7001: java.net.BindException: Address already in use: JVM_Bind.>
.. <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[3]". The address 127.0.0.1 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use: JVM_Bind.>
..
.. <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
..
.. <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
.. <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
.. <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |