Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Technology Stack - EBS (MOSC)

Java Cache Port Conflict could not be resolved

Nov 30, 2015 1:06AM 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

Reserve the port ("Java Object Cache Port">12346) in the sysctl.conf.
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:

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month