Thread Stuck When Starting Up OSM Managed Server <BEA-003107> <Lost 2 unicast message(s).>

(Doc ID 1616150.1)

Last updated on FEBRUARY 27, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
****Currency checked on 16-sep-2015****
****Currency checked on 27-Feb-2017****


For OSM Performance testing customer has been recommended to use 18 managed server OSM COM and 3 managed server SOM. However, customer found that after starting up more than 15-16 managed server OSM COM thread stuck on one of the managed server and whole cluster became unresponsive. The remaining managed servers are not able to startup when this issue was observed.

Error found on Managed Server 10 where there is a stuck thread :


<Jan 9, 2014 7:01:36 PM MYT> <Info> <Cluster> <BEA-003107> <Lost 2 unicast message(s).>
<Jan 9, 2014 7:01:45 PM MYT> <Info> <Cluster> <BEA-003107> <Lost 2 unicast message(s).>
<Jan 9, 2014 7:01:45 PM MYT> <Info> <Cluster> <BEA-000111> <Adding BOSMCOMPFT_MS18 with ID -1109516540817879619S:[8127,8127,-1,-1,-1,-1,-1]:,,,,,,,,,,,,,,,,, to cluster: COM_CLUSTER view.>
<Jan 9, 2014 7:01:45 PM MYT> <Info> <Cluster> <BEA-000128> <Updating -1109516540817879619S:[8127,8127,-1,-1,-1,-1,-1]:,,,,,,,,,,,,,,,,, in the cluster.>


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