Technology Stack - EBS (MOSC)

MOSC Banner

Java Cache Port Conflict could not be resolved

edited Feb 2, 2016 4:03AM in Technology Stack - EBS (MOSC) 1 commentAnswered

My customer has encounterred the similar issue as documented below.

Port Conflicts In EBS - Address already in use (Doc ID 1940314.1)

We suggest him to

  1. Reserve the port ("Java Object Cache Port">12346) in the sysctl.conf.
  2. net.ipv4.ip_local_reserved_ports = 12346
    1. Set net.ipv4.ip_local_port_range in sysctl.conf to outside of port
    2. net.ipv4.ip_local_port_range = 30000 65500

However, after starting adcmctl.sh and adalnctl.sh, 12346 is still used by

The following concurrent manger process.

------

  • oracle.apps.fnd.cp.gsm.GSMSvcComponentContainer

------

Further more, this issue could be reproduced at will in the customer’s instance.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS TechStack Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center