Hi,
Many times we see that the JVM arguments And Classpath settings applied by us in server StartScripts …. are not being picked up by the Managed Servers which we start Using NodeManagers….like HeapSize, PermSize…etc. For more information : http://forums.oracle.com/forums/thread.jspa?threadID=1038345&tstart=0
To Debug this kind of issues first of all we need to look up in the Server Logs/Stdout that which values are being picked up by the Managed Servers. If it is not the one which we wanted there…then please follow the steps:
If you are starting your Managed Server using NodeManager then First of all try the following options as well..
Option-1).
Login to AdminConsole–>Environments—.Servers—>YourManagedServer—>Configuration (TAB)—>ServerStart (SubTab)—> Arguments:(TextArea)
-Xms1024m -Xmx1024m -XX:MaxPermSize=256m –Duser.dir=E:/MyDirectory
Specify the your own Heap & MaxPermSize setting here.. in the TextArea …Then start your Server.
NOTE: Similarly in the same Page you will see the CLASSPATH variable which you can use to set the Managed Server ClassPath…
————————————–
If option-1 doesn’t work then….
Option-2). If above also didn’t work then please try to add the following 2 entry in the “nodemanager.properties” file and in startWebLogic.cmd please add the JAVA_OPTION=-Xms1024m -Xmx1024m -XX:MaxPermSize=256m –Duser.dir=E:/MyDirectory
StartScriptName=startWebLogic.sh
StartScriptEnabled=true
Then try to start your Managed Server. (here u can give your Custom Script name as well, But that should be available inside Domain_home/bin)
====================================
Alternative Of Setting CLASSPATH:
Step-1). start the Server using start Scripts …and then copy the classpath from the STDOUT of the Server… (Make sure there is no line breaks in that)
Step-2). open admin console and then add the same classpath in the “Server Start” tab …now in the same classpath you can append your Jars as well..
NOTE: setting classpath through AdminConsole will take effect only when you start your Server using NodeManager for which you are planning to set the classpath.
Alternative:
if the Jar precedence does not matter much in your case then …as an alternative putting the Jars in “<DOMAIN_HOME>lib” directory will help much…because the Jars present in this directory will be automatically appended at the end of the CLASSPATH…(it happens on the fly so you wont be able to see it)
.
.
Thanks
Jay SenSharma
March 27th, 2010 on 9:12 am
Managed Server ServerStart Arguments:(TextArea)
-Xms1024m -Xmx1024m -XX:MaxPermSize=256m
MEM_ARGS in setDomainEnv.sh.
MEM_ARGS=”-Xms256m -Xmx512m”
export MEM_ARGS
When I start the managed server using NodeManager then try the option-1.
But I find the parms {MEM_ARGS} and {JAVA_OPTIONS} at the starting WLS with line.
/opt/java1.5/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dweblogic.system.BootIdentityFile=/bea/user_projects/domains/base_domain/servers/apServer/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -da -Dplatform.home=/bea/weblogic92 -Dwls.home=/bea/weblogic92/server -Dwli.home=/bea/weblogic92/integration -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/bea/patch_weblogic923/profiles/default/sysext_manifest_classpath -Dweblogic.Name=apServer -Djava.security.policy=/bea/weblogic92/server/lib/weblogic.policy weblogic.Server
Can you please suggest what else we need to change?
March 27th, 2010 on 11:48 am
Hi Neski,
It’s OK … Actually currently your Managed Server actually running with -Xms1024m -Xmx1024m -XX:MaxPermSize=256m memory setting only.
Reason:
/opt/java1.5/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -Dweblogic.system.BootIdentityFile=/bea/user_projects/domains/base_domain/servers/apServer/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -da -Dplatform.home=/bea/weblogic92 -Dwls.home=/bea/weblogic92/server -Dwli.home=/bea/weblogic92/integration -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/bea/patch_weblogic923/profiles/default/sysext_manifest_classpath -Dweblogic.Name=apServer -Djava.security.policy=/bea/weblogic92/server/lib/weblogic.policy weblogic.Server
In the above Output of your ServerLog/OUT file you will see the Heap and MaxPerm Setting twice….because on setting you have defined in “setDomainEnv.sh” and second setting you have defined in “serverStart” tab ….Remember that always the Second Setting Takes Preference over the First one….
It means If we have defined More than one Heap Settings in the JAVA_OPTIONS then you will always see that the Final (Last) Value of the JAVA_OPTION will override the previous value.
Still if you dont want to see two values in your STDOUT then please remove the MEM_ARGS values from “setDomainEnv.sh”….This is the Default Behavior of WebLogic….
Why we have provided this feature …because suppose if u have 4 Managed Servers out of them if you want to assign a Specific Heap Setting only to one managed Server then u need to use “ServerStart” option….rest all 3 Managed Server will still be able to take the Memory settings from setDomainEnv.sh…
So nothing to worry….Your Managed Server is actually running with the Highlighted Heap Settings only.
Keep Posting 🙂
Thanks
Jay SenSharma
August 12th, 2010 on 9:06 pm
Hello Jen ,
I need to get the attachment part ( ie an XML for me ). I need to read that to a String variable is that possible ?
Thanks In Advance
-Shyam
August 12th, 2010 on 11:33 pm
Hi Skoiloth,
Please try the Sample which i uploaded in the following Link: http://www.4shared.com/file/0eBpfhnS/_2__SOAP-Attachment-Test.html
U need to change only two things …..
Change 1). In the build.xml file Provide your Own File which u want to read inside the WebService…
Example:
<arg line=”http://${wls.hostname}:${wls.port}/attach/AttachWSService C:DELbuild.xml” />
Change 2). Inside the WebService class “.java” Give the Location and the File name where you want to write the Data of the XML file Sent by the WebService Client…
try {
int readBytes;
System.out.println(“AttachWSService t Reading File…”);
claimForm.writeTo(new FileOutputStream(filename+”.CREATED”));
System.out.println(“nnt Data Written In the File: “+filename+”.CREATED”);
}
catch (Exception e)
{
System.out.println (“I/O exception, ” + e.getMessage());
}
.
.
Keep Posting 🙂
Thanks
Jay SenSharma
September 28th, 2010 on 11:37 am
HI ,
I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
Below is the error in the managed server log,
startWebLogic.sh: grep: not found
startWebLogic.sh: uname: not found
startWebLogic.sh: test: argument expected
can you help me to solve the problem please. i am using weblogic 10.3.3
thanks
Arun
September 29th, 2010 on 1:36 pm
Hi Jay, As requested sent the logs to weblogicwonders@yahoo.in .
FYI ,i am using the startscriptEnabled=true here
October 6th, 2010 on 1:12 pm
Hi Jay,
This is Madhu and I am learning weblogic 10.3 by reading Oracle weblogic Documentation.
I am facing the same issue as above.
Environment : Solaris10
Weblogic Version:10.3
Java Vendor :Sun
Weblogic domain is starting sucessfully when I ran startWebLogic.sh and I am able to login to weblogic admin console
bash-3.00# ./startWebLogic.sh
.
.
JAVA Memory arguments: -Xms1024m -Xmx1024m -XX:MaxPermSize=512m
.
WLS Start Mode=Production
When I am starting, weblogic Admin Server using WLST
startServer(‘AdminServer’,’testdom’,’t3://localhost:7001′,’weblogic’,’weblogic’,’/usr/bea/user_projects/domains/testdom’,’true’,60000,’false’)
server started
WLST-WLS-1286350583901:
WLST-WLS-1286350583901:
Server started successfully.
‘WLST-WLS-1286350583901’
and when I am trying to login to admin console Out of Memory permgenspace Error is coming…
As Mentioned above I have added JAVA_OPTION=-Xms1024m -Xmx1024m -XX:MaxPermSize=512m in Managed Server configuration.
Still I am getting Out of Memory errors.
Kindly guide me on this.
October 6th, 2010 on 3:11 pm
Hi Jay,
Small progress in issue…
I have verified the heap space & PermGen Space using visualvm.
When I am starting using startWebLogic.sh,
-Xms1024m -Xmx1024m -XX:MaxPermSize=512m these values are utilised by Weblogic instance.
But,When I am starting using WLST
HeapSpace Max value is 256m and PermGen Max Value is 68m
Can you plz tell me where to update to get -Xms1024m -Xmx1024m -XX:MaxPermSize=512m when I am starting using WLST.
Regards,
Madhu
October 6th, 2010 on 9:33 pm
Hi Madhu,
While starting your server using WLST function “startServer” please use the following syntax….to make sure your own Memory settings will take effect:
startServer(‘demoServer’,,’testdom’,’t3://localhost:7001′,’weblogic’,’weblogic’,’/usr/bea/user_projects/domains/testdom’,’true’,60000,’false’, jvmArgs=’-XX:MaxPermSize=512m, -Xmx1024m, -Xms1024m, -XX:+UseParallelGC’)
.
.
Keep Posting 🙂
Thanks
Jay SenSharma
October 7th, 2010 on 12:17 pm
Hi Jay,
Thanks for the response and now server instance started as required.
The root cause for the issue is,
weblogic environmental variables are not setting on solaris10 even with execution of setWLSEnv.sh/setDomainEnv.sh.
Below is the output from terminal
bash-3.00# export CLASSPATH=
bash-3.00# export PATH=/usr/bin:/usr/sbin
bash-3.00# /usr/bea/wlserver_10.3/server/bin/setWLSEnv.sh
JAVA_OPTIONS=-Xms1024m -Xmx1024m -XX:MaxPermSize=512m
CLASSPATH=/usr/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/jdk/jdk1.6.0_18/lib/tools.jar:/usr/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/usr/bea/wlserver_10.3/server/lib/weblogic.jar:/usr/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/usr/bea/wlserver_10.3/server/lib/webservices.jar:/usr/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/usr/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:
PATH=/usr/bea/wlserver_10.3/server/bin:/usr/bea/modules/org.apache.ant_1.6.5/bin:/usr/jdk/jdk1.6.0_18/jre/bin:/usr/jdk/jdk1.6.0_18/bin:/usr/bin:/usr/sbin
Your environment has been set.
bash-3.00# echo $CLASSPATH
bash-3.00# echo $PATH
/usr/bin:/usr/sbin
bash-3.00#
As I am unable to start wlst using java weblogic.WLST, I set the jar files in classpath in soaris /etc/profile and then I am able to start wlst.
But I am not setting JVM Memory values explicitly,thats why Heapspace/PermGenspace errors are coming.
Setting weblogic environmental variables issue is coming on solaris and the same is working fine on Windows.
Please guide me to fix this..
Thanks,
Madhu.
October 7th, 2010 on 9:58 pm
Hi Madhu,
Make Sure that u run the step3). Very Carefully with the given instructions …..below
The Following 5 Steps u need to perform as Pre-Work before Running the actual WLST codes…
Step1). Open a Shell Prompt.
Step2). echo $CLASSPATH … Just to see what is the current CLASSPATH value.
Step3). run the “setWLSEnv.sh” by adding two DOTs separated by a single space …..before the actual script like following : (use ‘cd’ command to move inside the /wlserver_10.3/server/bin) then run the following command….
. ./setWLSEnv.sh
Note: The first DOT represents that set the Environment in the current Shell, AND the second ./ represents execute the script from the current directory.
Step4). Verify that the Classpath is Set properly or not:
echo $CLASSPATH
Step5). Now u can run your command
.
.
Keep Posting 🙂
Thanks
Jay SenSharma
October 8th, 2010 on 1:03 pm
Hi Jay,
As per your reply,the environmental variables are setting for the terminal and wlst is starting up.
bash-3.00# echo $JAVA_OPTIONS
-Xms1024m -Xmx1024m -XX:MaxPermSize=512m
But, if we start server instance using wlst still JVM HeapSpace/PermGenSpace not allocated as expected.
SO I am passing JVM arguments explicitly as you mentioned in previous replies.
startServer(‘AdminServer’,’testdom’,’t3://localhost:7001′,’weblogic’,’weblogic’,’/usr/bea/user_projects/domains/testdom’,’true’,60000,’false’, jvmArgs=’-XX:MaxPermSize=512m, -Xmx1024m, -Xms1024m, -XX:+UseParallelGC’)
Thanks for your support.
Madhu.
October 11th, 2010 on 5:53 pm
Jay,
firstly congratulations for making such a elaborate portal..
jay i have a request if you could post on how to start managed servers without Admin server and also how to start without nodemanager and Admin server and How this stuff works..
December 9th, 2010 on 12:05 am
Hey Jay,
Really nice post, thanks for that.
I am struggling to find out how to start each managed severs with different heap size considering both the managed servers are residing in the same domain.
I know explicitly I can mention the min and max heap as command line argument, is there any other way to do the same.
I also know that 😉 I can edit the startManagedweblogic.cmd and mention the desired size in JAVA_OPTIONS, but how I will do that for two different managed.
Thanks.
Keep posting 😉
Regards,
Sohel.
December 9th, 2010 on 12:45 am
Hi Sohel,
If you have 2 Managed Servers in the same Box belonging to the same domain As Well As if you want to assign them Different Memory Settings/Classpath As Well As you want to start The Managed Servers without the help of NodeMaanger (It means want to start them using startScripts)
Then you must have to create your own startManagedServer.sh scripts ….Which is very simple as well…
Example: Just copy and paste the “startManagedWebLogic.sh” twice with name “startManagedWebLogic_MS1.sh” and “startManagedWebLogic_MS2.sh” now you can specify write variables CLASSPATH and JAVA_OPTIONS in these files.
But if you want use NodeManager (through AdminConsole) to start those Managed Servers then you can follow the Way mentioned in the above Post.
.
.
Keep Posting 🙂
Thanks
Jay SenSharma
December 9th, 2010 on 12:49 am
Hi Sohel,
If you want to give different heap size to each server that can be achieved by two methods
Method-1
If you are using Node Manager then follow the option-1 in the above post for and do the same for every server you want to do.
Server-1
Login to AdminConsole–>Environments—.Servers—> ManagedServer-1 —>Configuration (TAB)—>ServerStart (SubTab)—> Arguments:(TextArea)
-Xms1024m -Xmx1024m
Server-2
Login to AdminConsole–>Environments—.Servers—> ManagedServer-2 —>Configuration (TAB)—>ServerStart (SubTab)—> Arguments:(TextArea)
-Xms512m -Xmx512m
Method-2
If you are not using Node Manager then make two diffrent startup scripts having diffrent heap sizes for each server like
startManagedweblogic-1.cmd
set MEM_ARGS=-Xms1024m -Xmx1024m
startManagedweblogic-2.cmd
set MEM_ARGS=-Xms512m -Xmx512m
Hope this would help you
Regards,
Ravish Mody
December 9th, 2010 on 1:03 am
Thank you very much.
Much appreciated.
Cheers,
Sohel.
July 13th, 2011 on 5:57 pm
Hi Jay,
I used the option 1 since i need to set the memory arguments for a particular managed server.
Please see the below logs:
.
.
JAVA Memory arguments: -Xms512m -Xmx1024m
.
WLS Start Mode=Development
.
CLASSPATH=;G:OracleMIDDLE~1patch_wlw1030profilesdefaultsys_manifest_classpathweblogic_patch.jar;G:OracleMIDDLE~1patch_wls1030profilesdefaultsys_manifest_classpathweblogic_patch.jar;G:OracleMIDDLE~1patch_cie660profilesdefaultsys_manifest_classpathweblogic_patch.jar;G:OracleMIDDLE~1JROCKI~1libtools.jar;G:OracleMIDDLE~1WLSERV~1.3serverlibweblogic_sp.jar;G:OracleMIDDLE~1WLSERV~1.3serverlibweblogic.jar;G:OracleMIDDLE~1modulesfeaturesweblogic.server.modules_10.3.0.0.jar;G:OracleMIDDLE~1WLSERV~1.3serverlibwebservices.jar;G:OracleMIDDLE~1modulesORGAPA~1.5/lib/ant-all.jar;G:OracleMIDDLE~1modulesNETSFA~1.0_1/lib/ant-contrib.jar;G:OracleMiddlewaredomainsBpmUATDomainelfconfig;G:OracleMIDDLE~1WLSERV~1.3commonevalpointbaselibpbclient57.jar;G:OracleMIDDLE~1WLSERV~1.3serverlibxqrl.jar;;
.
PATH=G:OracleMIDDLE~1patch_wlw1030profilesdefaultnative;G:OracleMIDDLE~1patch_wls1030profilesdefaultnative;G:OracleMIDDLE~1patch_cie660profilesdefaultnative;G:OracleMIDDLE~1WLSERV~1.3servernativewin32;G:OracleMIDDLE~1WLSERV~1.3serverbin;G:OracleMIDDLE~1modulesORGAPA~1.5bin;G:OracleMIDDLE~1JROCKI~1jrebin;G:OracleMIDDLE~1JROCKI~1bin;G:OracleMIDDLE~1WLSERV~1.3servernativewin32;G:OracleMIDDLE~1WLSERV~1.3serverbin;G:OracleMIDDLE~1JROCKI~1jrebin;G:OracleMIDDLE~1JROCKI~1bin;G:OracleMIDDLE~1WLSERV~1.3servernativewin32oci920_8;C:coreutilPerlbin;C:WINNTsystem32;C:WINNT;C:WINNTSystem32Wbem;c:coreutilwinzip;C:COREUTILntreskit;C:COREUTILsfreskit;c:usrOVbinOpC;c:usrOVbin;D:coreutilOmniBackbin;;G:OracleMIDDLE~1WLSERV~1.3servernativewin32oci920_8
.
***************************************************
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\hostname:portconsole *
***************************************************
starting weblogic with Java version:
java version “1.6.0_05”
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
BEA JRockit(R) (build R27.6.0-50_o-100423-1.6.0_05-20080626-2105-windows-ia32, compiled mode)
Starting WLS with line:
C:beaJROCKI~1binjava -jrockit -Xms512m -Xmx1024m -Dweblogic.system.BootIdentityFile=C:beadomainsXXDomainserversC6MS2Udatanodemanagerboot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xms256m -Xmx1536m -Djavax.net.ssl.trustPassword=changeit -Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol -Xverify:none -da -Dplatform.home=C:beaWLSERV~1.3 -Dwls.home=C:beaWLSERV~1.3server -Dweblogic.home=C:beaWLSERV~1.3server -Dweblogic.management.discover=false -Dweblogic.management.server=t3://192.44.190.137:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=C:beapatch_wlw1030profilesdefaultsysext_manifest_classpath;C:beapatch_wls1030profilesdefaultsysext_manifest_classpath;C:beapatch_cie660profilesdefaultsysext_manifest_classpath -Dweblogic.Name=C6MS2U -Djava.security.policy=C:beaWLSERV~1.3serverlibweblogic.policy weblogic.Server
The memory arguments I added in arguments is shown in nodemanger java_options initially. Can you check whether the memory args I mentioned is refected. I added
-Xms256m -Xmx1536m in server start argument.
Thanks and Regards,
Charan
July 14th, 2011 on 1:52 am
Hi Charan,
Yes, the memory argument is reflected properly. As in the JAVA_OPTS i can see that first it is “-Xms512m -Xmx1024m” and later in the same line it is “-Xms256m -Xmx1536m”
If any duplicate JAVA_OPTS appears in the consiguration then the JVM always picks up the JAVA_OPTS which appears at the end …. It means your Server is running using the Memory Setting “-Xms256m -Xmx1536m” so you need not to worry if there are duplicate JAVA_OPTS appearing in the output because the Last JAVA_OPTS will be used by the JVM.
.
.
Keep Posting 🙂
Thanks
Jay SenSharma
July 14th, 2011 on 6:09 pm
Thanks Jay 🙂
Thanks and Regards,
Charan
August 7th, 2011 on 9:23 am
Hi Jay,
If i use admin console-server startup tab to modify the memory setting where exactly the configuration is getting modified.I want to know which file is getting modified.
The 2nd option of setting the memory setting in startWebLogic.sh and nodemanager.properties-Here how will i set indivual memory setting for each managed server. Can you explain the 2nd option. Thank for your help!
August 7th, 2011 on 4:01 pm
Hi sudheshpn,
When you give the memory arguments from the admin-console that arguments are been saved in the config.xml file.
The best option to start managed servers with different memory arguments when starting them using the admin-console would be given the arguments to there respective server-startup tabs which should do the trick as these arguments should override the arguments given in the start-up scripts.
Regards,
Ravish Mody
August 12th, 2011 on 3:28 pm
Thank you Ravish!!You are great!
November 25th, 2011 on 3:55 pm
i took the first script and when i run that script according to the guidelines it is showing the following
C:>java weblogic.WLST application_status.py
Initializing WebLogic Scripting Tool (WLST) …
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Problem invoking WLST – java.io.FileNotFoundException: C:\application_status.py (The system cannot find the file specified)
Can you please tell how to overcome this issue.
Thanks in advance ….
February 10th, 2012 on 1:02 pm
hi.. I am using Windows XP version ,Weblogic 10.3.2 in the test environment. After deploying the application onto the weblogic ,for launching the Oracle FCDB application,I am facing the problem;services.ear is getting started and is taking the classpaths and arguments proeprly. It says
Error 500–Internal Server Error
java.lang.Exception: Undefined System property : fcat.basedir
at com.iflex.fcat.infra.JFProperties.getBasePath(JFProperties.java:1106)
at com.iflex.fcat.infra.JFProperties.getFileFromHome(JFProperties.java:1094)
at com.iflex.fcat.gui.InternetServletConfig.getConfig(InternetServletConfig.java:292)
at com.iflex.fcat.gui.InternetServlet.init(InternetServlet.java:137)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:235)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Please help!!!!!!!!!!
February 22nd, 2012 on 12:14 am
Hi, I am new to MM and this is my first comment, first of all, hats off to your work.
I want to know all the Memory Arguments and other options/settings/attributes we can set for a server when running from command line. This could very helpful for a starter like me.
Thanking you.
February 22nd, 2012 on 2:19 am
Hi WL_Prasad,
Usually what all parameters need to be set while starting your server can be determined only after performing various test on your server like Load testing, so that the Heap utilization matrix and the request/response time statistics can be seen. Just to run a server does not require any additional settings or tuning parameters. So it all depends on What kind of applications you are going to deploy on your server, what kind of load you are extecting, what is your estimated request/response statistics and how much are you getting actually also it depends on What kind of application frameworks are you using, what kind of JVM (32-bit or 64-bit), RAM size, Operating System, Number of Cores present in your hardware…etc.
So basically there is no standard rule which can be used to add some parameters in your server, So let us know if you are facing any issue so that accordingly we can suggest something.
.
.
Keep Posting 🙂
Thanks
Jay SenSharma
February 27th, 2012 on 11:49 am
Hi, my last comment has been awaiting moderation for the last 5 days, could u please reply so that I can ask another questions. If anything is wrong with my question, let me know.
Thanking you
December 2nd, 2012 on 5:28 pm
Hi Jay/Ravish,
I am facing problem with my nodemanager i configured as a service.Below is the scenario :-
I configured one admin server ,2 managed server which are configured in a same machine named machine 1 .Now everything is working fine.
Admin server,managed servers and Node manager is starting normally.
Now to see if node manager starts up a failed server i tried killing the process of one of my manager server through task manager after which the particular server went into Unknown state but still even after waiting 500 seconds seems like the nodemanager is not contacting the particular server or somewhere i am missing some configuration.Below is my nodemanager.properties file content :
#Sun Dec 02 14:05:50 IST 2012
DomainsFile=F:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=F:\oracle\MIDDLE~1\JDK160~1
AuthenticationEnabled=true
NodeManagerHome=F:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager
JavaHome=F:\oracle\MIDDLE~1\JDK160~1\jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.cmd
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=false
SecureListener=false
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
StartScriptEnabled=false
LogFile=F:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
Kindly help me out where am i going wrong.
December 5th, 2012 on 3:51 pm
I started it as a windows service.First i started admin then node manager the manage server services.All are getting started properly and even manage server state and health is showing as Running and OK respectively.
Is it something to do with the sequence or if it is can you tell me how to start when it is configured as a service.
December 8th, 2012 on 5:41 pm
Hi Rene,
Below is the details of my nodemanager startup.properties #Server startup properties
#Sun Dec 02 17:45:46 IST 2012
SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false
RestartMax=2
RestartDelaySeconds=0
RestartInterval=3600
AdminURL=http://[2001:0:4137:9e76:385f:1ed6:3f57:fefc]:7001
AutoRestart=true
AutoKillIfFailed=false
I checked in admin console too under health monitoring in configuration tab of managed server but there also the auto restart is checked. Wondering whether node manager can start up a manage server whose process is killed force fully or not because might be if manager server health is not ok or in hung mode then there will be a trigger to node manager to auto restart that particular server.
Can you please clear out this curious doubt of mine 🙂 ?