Sunday, October 19, 2014

WLST No domain or domain template has been read

Error: No domain or domain template has been read


If you have just recently started to get your hands dirty with weblogic & wlst, you’ll may not be aware of all the wlst commands and scenarios in which those commands can be used. The documentation for wlst, and weblogic in general, is so huge that it is OK for anyone to have missed out such niti-grities.

During a similar situation, I faced below error when I was trying to execute “getNodeManagerHome()” command on wlst using node manager connection.

“Error: No domain or domain template has been read.”

Ø  WLST command & error message

Welcome to WebLogic Server Administration Scripting Shell


Type help() for help on available commands


wls:/offline> getNodeManagerHome()

Error: No domain or domain template has been read.



At first I thought this may be because of my not being connected to the node manager. But as you can see below, soon that assumption turned out to be wrong.

wls:/offline> nmConnect('weblogic', 'xxxxxxxx', '10.xx.xx.xx', '5556','poc_domain', '/opt/app/oracle/middleware/user_projects/domains/poc_domain','plain')

Connecting to Node Manager ...

Successfully Connected to Node Manager.

wls:/nm/poc_domain> getNodeManagerHome()

Error: No domain or domain template has been read.



Ø  Solution

To execute several commands, you must first read the domain template using readDomain(), and then you can execute those commands.

wls:/offline> readDomain('/opt/app/oracle/middleware/user_projects/domains/poc_domain')




Note that readDomain() is used on offline mode, i.e. without actually connecting using the weblogic/node manager credentials.

The other commands, which impose that you first read the domain using readDomain() are: updateDomain(), addTemplate(), etc.


Ø  Reference


Continue to to SeeITwithSanjay for more blogs on FMW.


Saturday, January 4, 2014

Unable to create an instance of Java Virtual Machine, jvm.dll

Unable to create an instance of Java Virtual Machine, jvm.dll


At the end of installation for Oracle JDevloper Studio 12c, you get option to launch the studio. For me, the launch of Jdev studio failed with below error.


Unable to create an instance of the Java Virtual Machine Located at Path <<JDK_HOME>>\hre\bin\client\jvm.dll










On some research, the cause was suspected to be one to the following two-

1.       Low Max Heap Size i.e. Xmx

2.       High Max Perm Size i.e. -XX:MaxPermSize


The above parameters are defined in JDEV_HOME\bin location in jdev.conf file- C:\Oracle\Middleware\Oracle_Home\jdeveloper\jdev\bin\jdev.conf


In my case, the Xmx parameter was not even present in my jdev.conf, hence I decided to try reducing the PermSize to see if it works.


Ø  Original PermSize:

AddVMOptionHotspot -XX:MaxPermSize=320M


Ø  New modified PermSize:

AddVMOptionHotspot -XX:MaxPermSize=128M


Voila!.. JDev studio launched successfully.

Continue to SeeITwithSanjay.


Updated on 14th Jan 2014.


Recently I saw post on regarding the same issue wherein Arik, based on inputs from oracle sales person, has mentioned that reducing Xmx may rather causes issue. Hence you should only try to reduce permsize before taking any other action, to resolve the problem.