Exception Appeared in JNEP Diag When Connection To The Network Element Lost

(Doc ID 1173683.1)

Last updated on MARCH 21, 2018

Applies to:

Oracle Communications ASAP - Version 5.2.4 and later
Information in this document applies to any platform.
***Checked for relevance on 31-JUL-2012***


When the NE itself disconnects (due to a restart) , the following exception is thrown in the JNEP.diag by the JInterp's ConnectionHandler:

150959.110:Connection handler osm-des-46699:PROG:com.mslv.activation.jinterpreter.JInterpConnection:
com.mslv.activation.jinterpreter.ConnectionException: Connection to the network element lost.
at com.mslv.activation.jinterpreter.JInterpConnection.runClassMethod(JInterpConnection.java:217)
at com.mslv.activation.jinterpreter.JInterpConnection.handleMessage(JInterpConnection.java:131)
at com.mslv.activation.server.ConnectionHandler.run(ConnectionHandler.java:251)

The login and disconnect methods are overridden in the cartridge and the Exceptions are handled in the cartridge itself.

Since this is generated by ASAP's JInterp class , we are not able to handle this exception inside the cartridge and it is being logged in the JNEP diag file.

Can you please update whether we can prevent this exception log?


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms