Last updated on DECEMBER 05, 2016
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On WebLogic Server 220.127.116.11.0 and higher, JMS clients can be blocked from sending messages for four minutes or more after a restart. For example, here is the order of events on the WebLogic side:
12:12:00 all servers are stopped
12:12:00 starting admin server
12:13:00 admin server running
12:14:00 starting all 4 clustered managed servers
12:20:00 all 4 managed servers running
12:24:00 JMS clients processing messages again
JMS clients were blocked for several minutes even though at least one or more managed servers were in the RUNNING state. During the blockage, many BEA-000128 (Cluster Member update) events were seen.
The 4+ minutes delay between the servers reaching RUNNING state and the JMS messages flowing is unexpected: JMS messages should flow immediately once the server is running.
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