Production/Consumption Paused State of JMSServer is not Properly Set on Startup or Migration

(Doc ID 1511757.1)

Last updated on MAY 24, 2017

Applies to:

Oracle Weblogic Server - Version 10.3.4 to 12.1.1.0
Information in this document applies to any platform.

Symptoms

Below are the steps that need to be followed to observe this kind of an inconsistency.
  
 1) Create a domain which consists of one Admin Server and two managed servers namely MS1 and MS2. AdminServer is running on 7001 port. MS1 running on 7003  and MS1 running on 7005.
 
 2) Put MS1 and MS2 in a cluster say "mycluster".
 
 3) Create a JMS Server say "JMSServer1" and target it to MS1 (Migratable).
 
 4) Create a FileStore or JDBCStore. Here we created FileStore say "FileStore1" and target it to MS1 (Migratable).
 
 5) Create a JMS Server say "JMSServer2" and target it to MS2 (Migratable).
 
 6) Create a FileStore or JDBCStore. Here we created FileStore say "FileStore2" and target it to MS2 (Migratable).
 
 7) Create a JMS Module say "SystemModule" and target it to  "mycluster".
 
 8) Create a subdeployment say "mysubdeployment" and target it to  "JMSServer1".
 
 9) Create a queue namely "SampleQueue" with a jndi name "SampleQueue" and target it to the subdeployment namely "mysubdeployment" which was created above.
 
 10) Create a Connection factory with name "QCF" with a jndi name "QCF" and deploy  to "mycluster".
 
 11) Start both the servers MS1 and MS2.
 
 12) Now execute the attached QueueSend.java file so that messages will be send to the queue.
 
 13) Now explicitly trigger a pause in the Queue namely "SampleQueue".

 (Select  Services->Messaging->JMS Module->SystemModule->SampleQueue->Control->Click on Production and click on Pause).
 
 14) Now change the setting of Paused Production/Consumption at startup of the  Queue namely "SampleQueue" in Advanced settings and restart the module.

(Select  Services->Messaging->JMS Module->SystemModule->SampleQueue->under  Configuration -> General Tab click on Advanced and select Pause Message Production at Startup, Pause Message Consumption at Startup, Pause Message Insertion at Startup).
 
 15) Now explicitly trigger a pause for JMSServer namely "JMSServer1".

(Select  Services->Messaging->JMS Servers->JMSServer1->Control->Click on Production  and click on Pause).

16) Now change the setting of Paused Production/Consumption at startup of the JMSServer namely "JMSServer1" in Advanced settings.

(Select  Services->Messaging->JMS Servers->JMSServer1->under Configuration -> General Tab click on Advanced and select Production Paused At Startup, Consumption Paused At Startup).
 
 17) At this point in time the Production Paused state in the Control tab for  JMS Server and the Queue is true which is as expected.
 
 18) Now manually migrate from the migratable targets

(Select  Environment->Migratable Targets->MS1 (migratable)->Control-> Click on Migrate and Migrate to MS2).
 
 19) Now we can observe that the state of the Production Paused for JMS Server is false (ideally should be true) whereas for Queue is true (as expected).
 
 20) In config.xml for JMSServer1 even though the value for <production-paused-at-startup> is true but in Admin Console we see the value as false Which is not the expected behaviour.

 

This issue was reproduced on WLS 10.3.4, 10.3.5 , 10.3.6 and 12.1.1

Cause

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