Port Conflicts In EBS - Address already in use
Last updated on FEBRUARY 01, 2018
Applies to:Oracle Mobile Application Server - Version 126.96.36.199 to 12.2.4 [Release 11.5 to 12.2]
Oracle Concurrent Processing - Version 188.8.131.52 to 12.2.4 [Release 11.5 to 12.2]
Oracle Applications Technology Stack - Version 184.108.40.206 to 12.2.4 [Release 11.5 to 12.2]
Information in this document applies to any platform.
Some times starting MWA services you may get following error:
[user@node] $ sh mwactl.sh start 10208
MWA Telnet Server Release: 220.127.116.11 [December 12th 2002]
[user@node] $ Couldn't create server socket : Address already in use
When we checked port 10208 at OS level it is occupied by concurrent manager process.
[user@node] $ netstat -nape |grep 10208
tcp 0 0 ::ffff:10.131.64.10:10208 ::ffff:10.131.64.10:31288 ESTABLISHED 502 64085 19765/java
[user@node] $ ps -ef | grep 19765
user 19765 19617 0 Sep08 ? 00:04:59 /u01/oracle/SID/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=19765 -server -Xmx384m -XX:NewRatio=2 -XX:+UseSerialGC -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -mx1024m -Ddbcfile=/u01/oracle/SID/inst/apps/SID_host/appl/fnd/12.0.0/secure/SID.dbc -Dcpid=9731 -Dconc_queue_id=6269 -Dqueue_appl_id=0 -Dlogfile=/u01/oracle/SID/inst/apps/SID_host/logs/appl/conc/log/FNDOPP9731.txt -DLONG_RUNNING_JVM=true -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.fnd.cp.gsf.GSMServiceController
Also sometimes while staring the services, one will get following error in error_log:
[Tue Oct 7 00:10:33 2014] [crit] (98)Address already in use: make_sock: could not bind to port 4473
user@node:/u01/oracle/SID/inst/apps/SID_host/logs/ora/10.1.3/Apache #sudo netstat -patun | grep 4473
tcp 0 0 10.129.11.77:4473 10.129.11.75:1561 ESTABLISHED 31618/FNDLIBR
Also if customer has multiple EBS installation on the same box, it is likely that one of the random port used by OS may clash with a port used by EBS.
This leads to fs_clone and similar utilities to fail.
Some times you may also get following error while starting JOC in javacache.log-
Cache not initialized
The port 12345 should be free on each host running the JVMs
If you check port 12345 at OS level it may be occupied by OPP/Workflow processes. You can check that with netstat command as shown in Scenario 1.
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