Managed Servers Hang in a ALSB 3.0 Cluster if Using Unicast
(Doc ID 943767.1)
Last updated on MAY 12, 2023
Applies to:
Oracle Service Bus - Version 3.0 to 3.0 [Release Aqualogic Service Bus]Information in this document applies to any platform.
Symptoms
While running a OSB cluster across a LAN, managed servers are found in a hung state with the following stack trace:
Holding lock: weblogic/cluster/messaging/internal/GroupMemberImpl@0xc066628 [thin lock]
at weblogic/cluster/messaging/internal/GroupImpl.forward(GroupImpl.java:354)[optimized]
at weblogic/cluster/messaging/internal/GroupMemberImpl.receive(GroupMemberImpl.java:67)[inlined]
at weblogic/cluster/messaging/internal/GroupManagerImpl.handleMessage(GroupManagerImpl.java:165)
at weblogic/cluster/messaging/internal/GroupImpl.forward(GroupImpl.java:354)[optimized]
at weblogic/cluster/messaging/internal/GroupMemberImpl.receive(GroupMemberImpl.java:67)[inlined]
at weblogic/cluster/messaging/internal/GroupManagerImpl.handleMessage(GroupManagerImpl.java:165)
Changes
The ALSB cluster is configured with the messaging mode <Unicast>.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |