cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Connected (Issue: Instrumentation is not available

Ramesh_Nadar
Advisor

Hello All,

From few days we are facing issue with agent connections. Connection state --> Connected (Issue: Instrumentation is not available.)

Agent log: 
2019-01-11 07:38:46 [00000002] severe [native] Exception while connecting to Server/Collector 172.xx.xx.xx, info:<connect()/apr_socket_connect(), 70007, Connection timed out>
2019-01-11 07:38:46 [00000002] warning [native] Unable to register with Server/Collector 172.xx.xx.xx, CONTINUING WITHOUT INSTRUMENTATION.

To reconnect agent we have to restart JVM multiple time. Which is heavenly impacting business.

Need permanent solution for this. Kindly suggest for solutions.

Thanks

Ramesh


5 REPLIES 5

Hello, how looks network architecture between agent and collector? Is there any firewall between them that can affect performance of the connection?

Sebastian


Hello Sebastian,

Connection between agent & collector server is clear. No firewall between.

For past 3-4 years no issue were observed in similar way.

Thank

Ramesh


As Radek said, collector logs has to be checked as well. Maybe there is some problems with class cache. It has to be checked

Sebastian


@Ramesh N. could you send logs from collector?


Babar_Qayyum
Leader

Hello @Ramesh N.

If there is no firewall in between agent and collector (not recommended) and even though you are facing the same situation then use the DT_WAIT (e.g. wait=30) with the environment variable to increase the connection establishment time.

This is the registry key 'wait'. It is the maximum time in seconds (default: 20; was 60 until 5.5) an Agent waits for a connection to an AppMon Collector. If the connection cannot be established within this time-frame, the application continues uninstrumented.

Regards,

Babar