Last updated on JANUARY 24, 2017
Applies to:Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.
JNEP cartridge code seems to be hung and did not receive the NE response.
Based on the thread dump info in ASAP.Console file , the thread is in a RUNNABLE state, so it seems to be actively running at the point where the thread dump was taken.
The custom cartridge action processor (GetDeviceCustomerProcessor) has called a 3rd party library, and the 3rd party library is trying to get a response code from the NE.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms