Random Ports Used for Distributed Java Object Caching, Even When Setting s_fnd_cache_port_range in the Autoconfig Context File
(Doc ID 471276.1)
Last updated on OCTOBER 04, 2016
Applies to:Oracle Applications Technology Stack - Version 11.5.9 to 18.104.22.168 [Release 11.5 to 11.5.10]
Information in this document applies to any platform.
What is Java Object Caching (JOC)
Caching provides a powerful, flexible, easy to use mechanism for storing database results and other Java objects in-memory for repeated usage. This minimizes expensive object initializations and database round-trips, thereby improving application tier performance.
1st JVM in instance starts and LONG_RUNNING_JVM=true is enabled in Jserv.properties. This enables JOC and sets the search for
Master JOC JVM looks for other JVMs using this port (12345)
OTHER JVM's join
Once connected, the JVM's communicate with each other over a random port range.
How to Restrict the port range used by Distributed JOC
Update the 's_fnd_cache_port_range' in your autoconfig context file and run autoconfig.
But JOC is still using Random Ports
The autoconfig changes for the 's_fnd_cache_port_range' variable came in the TXK patchsets (unpublished bug:4483646).
However the code to add the profile option "FND_CACHE_PORT_RANGE" was added in a different patch (unpublished bug:4555120). This code is distributed in 11i.ATG_PF.H Rollup 3.
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
|What is Java Object Caching (JOC)|
|How to Restrict the port range used by Distributed JOC|
|But JOC is still using Random Ports|