My Oracle Support Banner

Incorrect JNDI Property for Foreign JMS Server After Executing updateDomain() in the WLST Offline Mode (Doc ID 1344001.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Weblogic Server - Version: 9.2 to 10.3.1
Oracle Weblogic Server - Version: 9.2 to 10.3.1]
Information in this document applies to any platform.


When we use WLST's updateDomain() command in offline mode, the JMS configuration files get corrupted which is causing the server start-up to fail due to configuration parsing.

Here are the WLST commands that would reproduce the issue:

  1. First read the domain using the below command:
    wls:/offline> readDomain('D:\WLS_Installation\WLS10.3\user_projects\domains\MQ7_domain')
  2. Now just invoke updateDomain
    wls:/offline> updateDomain()
  3. Then if we try to look up the JNDI credentials in offline mode, they are either null or corrupted
    -rw- Key null
    -rw- Value null
  4. When we try to look up the same in online mode, everything works:
    wls:/MQ7_domain/serverConfig/JMSSystemResources/MySystemModule1/JMSResource/MySystemModule1/ForeignServers/MyForeignServer1/JNDIProperties/> ls()
    -r-- Key
    -r-- Value jmsid
  5. After we implement updateDomain() in WLST offline mode, we can also observe that the JMS config.xml changes like the following:


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.