This content has been marked as final. Show 6 replies
WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
This will be useful to make shutdown of servers without any problem.
Note: block=false will always works it should not be the problem.
Thank you for responding. I'm failing to understand what the TMP directory has to do with the blocking/non-blocking of the WLST calls. Are you saying that, if I overwrite the TMP directory or providide all users with the proper permissions on the TMP directory, then non-blocking will work? If that's the case, then why does non-blocking work while connected to the Admin Server and not the managed servers? I assume they're all using the same TMP directory anyway.
I totally agree with you but I dont see any issues with block=false option.
It should work.
you can try once to change the tmp folder and let me know.
I edited my wlst.cmd script to include the JVM arg for the temp directory. I also echo the JVM_ARGS after they're set:
JVM_ARGS=-Dprod.props.file="C:\Oracle\MIDDLE~1\WLSERV~1.3\.product.properties" -Djava.io.tmpdir=C:/Users/Michael/TempWLST -Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning
I then re-launched WLST, connected to my managed server (not the admin server) and issued this command:
Unfortunately, WLST still blocked user interaction. I could not issue any further WLST commands until my managed server completely shut down.
FYI, I'm running WebLogic Server 10.3.6 on a Windows 7 Ultimate x64 environment.
Kal, are you saying you can connect to a managed server (not admin) and issue shutdown commands without blocking? What version of WebLogic and what OS are you running?
You can use that option to connecting managed server and go for shutdown call.
Thank you for the hopes that this is supposed to work. So my question is, given the WLST configuration and the commands I'm issuing, why is it not working in our environment? Any other thoughts on why non-blocking is not working for us via our managed servers?