Last updated on AUGUST 13, 2013
Applies to:Oracle Communications Order and Service Management - Version: 2.5.2 to 6.3.1 - Release: 2.5 to 6.3
Information in this document applies to any platform.
Currency Check Completed on 04/09/2012
When investigating an OSM performance problem, JVM thread dumps provide useful diagnostic information.
This note provides sample code, which can be used in your plugin code so that order id and history id will be displayed as part of thread name. Details are provided as the default thread dump does not tell what the order id and history id the plugin was working on. This makes it difficult to determine if the plugin was stuck with the same task.
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