Work Orders Are Stuck Due to an Intermittent JNEP JVM Crash - SIGSEGV
Last updated on NOVEMBER 29, 2013
Applies to:Oracle Communications ASAP - Version 7.0.2 to 7.0.2 [Release 7.0.0]
Information in this document applies to any platform.
On ASAP Release R7_0_2/B154.
Work orders were stuck for one NE. Because of this, there was a high pending queue for that NE.
After investigating with our network prime, they mentioned there was no maintenance occuring on the NE from their side as well. Normally, as is seen whenever Network Element has any maintenance. Telnet to the IP was also working fine. In order to resolve this issue, the NEP was recycled and it was resolved.
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