Ops Center (MOSC)

MOSC Banner

Changing java mediator setting breaks agent communication

edited Jun 16, 2016 5:47AM in Ops Center (MOSC) 2 commentsAnswered

Would anyone know why changing the default java from 1.8 to 1.7 (using pkg set-mediator) would break agent communication for that asset?  At first we thought we were running into the well known bug which requires running OCDoctor --troubleshoot --fix to fix but that wasn't it.

Changing the default java back to 1.8 (and rebooting) fixes the problem.  I find this odd when it appears the agents explicitly execute java 1.8 anyway.  Does anyone know of a work-around?  We need to use java 1.7 temporarily until a 3rd party application can be upgraded.

Thanks

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

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