Mystery Connections from Concurrent Manager Server to Online Server

Hi,

It has been quite sometime since i posted my last "AppsDBATechStuff" blog. I was held up with certain "time-bound" activities, that occupied most of my time.

Now, i would like to share with you an interesting problem that i got to work on. We were working on certain memory management issues with Jserv in our environment and it was discovered that there were connections between the Online Servers and the Concurrent Manager server. Though it was not the likely culprit in the "memory" issue that we were chasing, it caught our attention and i started working on this.

Upon my investigation, i was able to determine that the connections were originating from the concurrent manager box and terminating on the Online Servers. I tied the ports and the processess together and determined that "Workflow Java Deferred Agent Listener" process was where the connections were originating and the "OA Core Group" Jserv was where the connection was terminating.

Looking at the logs (javacache.log), i was able to determine that Workflow Java Deferred Agent Listener was making these connections to all the Jservs on the online servers. Further analysis revealed that these connections were being made as part of the "Distributed mode Java Caching" framework. The "Database Invalidation" mechanism in which the WF Java Deferred Agent Listener processes the events relating to the data objects caching invalidation, is also responsible for notifying the Jserv that the data objects that were cached are now invalid.

This is the reason we saw the connections. Though we do not rely/leverage on the component cache mechanism, the above connections were seen as part of the framework being available and enabled. We continue to rely on "time based invalidation".


- Aravind Kamath