OGG JAGENT is failing to start after node reboot and getting below error in the ogg_agent.log file — oracle-mosc

GoldenGate, Streams and Distributed Database (MOSC)

MOSC Banner

OGG JAGENT is failing to start after node reboot and getting below error in the ogg_agent.log file

in GoldenGate, Streams and Distributed Database (MOSC) 1 commentAnswered

OGG JAGENT is failing to start after node reboot and getting below error in the ogg_agent.log file


[2022-04-02T14:47:27.787+02:00] [JAGENT] [ERROR] [OGGMON-20274] [com.goldengate.monitor.jagent.jmx.MBeansContainerImpl] [tid: main] [ecid: 0000NzeKF941baP5qfg8yY1YI4NV000001,0] [[

JAgent is unable to launch at JMX port: 6959.JAgent JMX port is not available.

Please change 'jagent.jmx.port' property in Config.properties file to an available port number.,

java.io.IOException: Cannot bind to URL [rmi://oggapp-martip-dm16.oneadr.net:6959/jmxrmi]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: oggapp-martip-dm16.oneadr.net; nested exception is:

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