weblogic12c - Weblogic 12c setting PermSize when using NodeManager -
we have windows server 2012 64bit + weblogic 12c setup. adminserver requires higher permsize when being used 64bit os, need modify "setdomainenv.cmd" (as described in other questions here on stackoverflow).
when starting adminserver through usual "startweblogic.cmd" script, uses settings in "setdomainenv.cmd" sets permsize etc. successfully, when using nodemanager "startserver()" command, not.
i read in documentation fact 1 can control parameters loaded on startup of managed server (with nodemanager), did not find right way it.
i hope can achieve consistent behaviour when starting managed server (and adminserver) through nodemanager or manually.
any ideas?
update:
i checked what's going on when starting managed server and(!) in comparison what's going on when starting adminserver. result: adminserver process (it starts 'javaw.exe' instance in contrast 'java.exe' instance managed server) never get's passed parameters set in setdomainenv.cmd script.. it's full of oracle internal parameters.
to me looks messed , inconsistent. in addition found issue reported oracle mystically talks setting environment variables when running on 64bit os (see headline "developer zip distribution fails on windows 64-bit , linux 64-bit"):
https://docs.oracle.com/cd/e24329_01/doc.1211/e26593/issues.htm#wlsrn238
i have idea if applies version or not, since version downloaded not "developer" version, primary weblogic download latest release.
the question comes mind this: expected way of starting adminserver if not using "startserver"? there bug nobody cares about, since done differently? disappointed how confusing rather simple topic evolves when starting read oracle documentation: not @ all.
command line triggered when starting adminserver through "startserver()" command:
c:\progra~1\java\jdk17~1.0_6\jre\bin\javaw.exe -classpath "c:\progra~1\java\jdk17~1.0_6\jre\lib\rt.jar;c:\progra~1\java\jdk17~1.0_6\jre\lib\i18n.jar;c:\progra~1\java\jdk17~1.0_6\lib\tools.jar;d:\oracle\middleware\wlserver\server\lib\weblogic_sp.jar;d:\oracle\middleware\wlserver\server\lib\weblogic.jar;d:\oracle\middleware\oracle_common\modules\net.sf.antcontrib_1.1.0.0_1-0b3\lib\ant-contrib.jar;d:\oracle\middleware\wlserver\modules\features\oracle.wls.common.nodemanager_2.0.0.0.jar;d:\oracle\middleware\oracle_common\modules\com.oracle.cie.config-wls-online_8.1.0.0.jar;d:\oracle\middleware\wlserver\common\derby\lib\derbyclient.jar;d:\oracle\middleware\wlserver\common\derby\lib\derby.jar;d:\oracle\middleware\wlserver\server\lib\xqrl.jar" "-djava.runtime.name=java(tm) se runtime environment" -dpython.cachedir=c:\users\admini~1\appdata\local\temp\2\wlsttempadministrator -djava.protocol.handler.pkgs=weblogic.utils|weblogic.utils|weblogic.utils -djava.vm.version=24.65-b04 "-djava.vm.vendor=oracle corporation" -djava.vendor.url=http://java.oracle.com/ -dpath.separator=; "-djava.vm.name=java hotspot(tm) 64-bit server vm" -dweblogic.rootdirectory=d:\oracle\middleware\user_projects\domains\test1234\. "-djava.vm.specification.name=java virtual machine specification" -djava.runtime.version=1.7.0_67-b01 -djavax.rmi.corba.utilclass=weblogic.iiop.utildelegateimpl -djava.awt.graphicsenv=sun.awt.win32graphicsenvironment -djava.endorsed.dirs=c:\progra~1\java\jdk17~1.0_6\jre\lib\endorsed -dos.arch=amd64 -djava.io.tmpdir=c:\users\admini~1\appdata\local\temp\2\ -dline.separator= "-djava.vm.specification.vendor=oracle corporation" -djava.naming.factory.url.pkgs=weblogic.jndi.factories:weblogic.corba.j2ee.naming.url "-dos.name=windows server 2012 r2" -dprod.props.file=d:\oracle\middleware\wlserver\.product.properties -dorg.omg.corba.orbsingletonclass=weblogic.corba.orb.orb -djava.library.path=c:\progra~1\java\jdk17~1.0_6\jre\bin;c:\windows\sun\java\bin;c:\windows\system32;c:\windows;;d:\oracle\middleware\wlserver\server\native\win\x64;d:\oracle\middleware\wlserver\server\bin;d:\oracle\middleware\oracle_common\modules\org.apache.ant_1.9.2\bin;c:\progra~1\java\jdk17~1.0_6\jre\bin;c:\progra~1\java\jdk17~1.0_6\bin;d:\oracle\product\12.1.0\dbhome_1\bin;c:\windows\system32;c:\windows;c:\windows\system32\wbem;c:\windows\system32\window~1\v1.0\;c:\progra~2\visual~1\bin;c:\progra~1\doxygen\bin;c:\progra~1\tortoi~1\bin;c:\progra~2\window~4\8.0\window~1\;c:\progra~1\micros~1\110\tools\binn\;d:\oracle\middleware\wlserver\server\native\win\x64\oci920_8;. "-djava.specification.name=java platform api specification" -djava.class.version=51.0 -dorg.omg.corba.orbclass=weblogic.corba.orb.orb -dos.version=6.3 -djavax.rmi.corba.portableremoteobjectclass=weblogic.iiop.portableremoteobjectdelegateimpl -djava.awt.printerjob=sun.awt.windows.wprinterjob -djava.specification.version=1.7 -djava.class.path=c:\progra~1\java\jdk17~1.0_6\lib\tools.jar;d:\oracle\middleware\wlserver\server\lib\weblogic_sp.jar;d:\oracle\middleware\wlserver\server\lib\weblogic.jar;d:\oracle\middleware\oracle_common\modules\net.sf.antcontrib_1.1.0.0_1-0b3\lib\ant-contrib.jar;d:\oracle\middleware\wlserver\modules\features\oracle.wls.common.nodemanager_2.0.0.0.jar;d:\oracle\middleware\oracle_common\modules\com.oracle.cie.config-wls-online_8.1.0.0.jar;d:\oracle\middleware\wlserver\common\derby\lib\derbyclient.jar;d:\oracle\middleware\wlserver\common\derby\lib\derby.jar;d:\oracle\middleware\wlserver\server\lib\xqrl.jar -djava.vm.specification.version=1.7 -dweblogic.management.generatedefaultconfig=false -djava.home=c:\progra~1\java\jdk17~1.0_6\jre "-djava.specification.vendor=oracle corporation" -dawt.toolkit=sun.awt.windows.wtoolkit "-djava.vm.info=mixed mode" -djava.version=1.7.0_67 -djava.ext.dirs=c:\progra~1\java\jdk17~1.0_6\jre\lib\ext;c:\windows\sun\java\lib\ext "-djava.vendor=oracle corporation" -djava.vendor.url.bug=http://bugreport.sun.com/bugreport/ -dweblogic.store.disablediskscheduler=true -dpython.verbose=warning weblogic.server
update 2:
start adminserver through node manager (nmstart('adminserver')) creates usual "java.exe" process , starts adminserver correct memory settings. more confusing: why "startserver()" creating separate process (javaw.exe) entirely different settings? why settings totally different adminserver? "correct" way of starting adminserver (development/production?). 2 thumbs down on environment.
update 3:
after repeating further tests solution of getting "startserver()" work follows: not worry node manager settings @ all, edit "startweblogic" script directly adding additional java options inside of (as usual adding -d start parameters). reason global settings (as used node manager) ignored completely, see pasted command line output.
check nodemanager.properties
file in oracle install ( e.g. /opt/ora/mw/wlserver_10.3/common/nodemanager/nodemanager.properties ) , verify these options set:
startscriptname=startmanagedweblogic.sh startscriptenabled=true
so nodemanager starting servers appropriate scripts. have option of setting server specific start attributes via admin console - go to:
servers -> server name -> server start tab -> arguments
you can fill in server specific jvm args, -xx:maxpermsize=4096m
in field used nodemanager. may better/easier idea hard coding in setdomainenv script.
update
attempt issuing nmstart()
command rather startserver()
command adminserver.
startserver
allows start server without nodemanager. uses javaw.exe background process
nmstart
allows start server nodemanager - why correct memory settings. because process started via service, more or less automatically backgrounded, why see normal java.exe
Comments
Post a Comment