Start Admin Server using NodeManager without 'boot.properties'
Hi All,
I am trying to stat Admin Server using nodemanager through below code.
public static void main(String args[]) {
try{
System.out.println("Starting...");
InteractiveInterpreter interpreter = new WLSTInterpreter();
interpreter.exec("nmConnect('weblogic', 'weblogic123', '10.0.0.100', '5556', 'domain1','D:/oracle/MiddleWare/user_projects/domains/domain1','ssl')");
interpreter.exec("nmServerStatus('AdminServer')");
interpreter.exec("nmStart('AdminServer')");
interpreter.exec("nmDisconnect()");
System.out.println("End.");
}catch(Exception ex){
System.out.println("Hello...");
ex.printStackTrace();
}Everything is working fine but we need a property file 'boot.properties' under location 'Bea Home/user_projects/domain/domain1/servers/AdminServer/data/nodemanager' having username and password.
Please let me know if there is any way to start Admin Server using nodemanager without using 'boot.properties' file.
Is there any way to provide username and password directly to 'nmStart()' method.
Please let me know...
Edited by: Rajesh Panchal on Jun 14, 2011 1:56 AM
Hi Rajesh,
Maybe you are looking for something like:
wls:/nm/IDMDomain> pr=makePropertiesObject("username=weblogic;password=weblogic0");
wls:/nm/IDMDomain> nmStart('AdminServer',props=pr);
Then, in your source code it should be something like:
interpreter.exec("pr=makePropertiesObject('username=weblogic;password=weblogic0')");
interpreter.exec("nmStart('AdminServer',props=pr)");
Hope it works.
-Cris
Similar Messages
-
Errors while starting admin server using WLST and NodeManager
Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
thanks
manohar
C:\oracle\Middleware\wlserver_10.3\server\bin>
C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
Connecting to Node Manager ...
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
loading of the trusted certificate list raised a certificate parsing exception
PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
0.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
of the trusted certificate list raised a certificate parsing exception PKIX: Un
supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : I/O error while reading domain directory
Use dumpStack() to view the full stacktrace
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline> dumpStack()
This Exception occurred at Tue May 03 10:45:03 EDT 2011.
weblogic.nodemanager.NMException: I/O error while reading domain directory
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:299)
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:312)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
a:248)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:205)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
java:52)
at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
eManagerService.java:179)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
rService.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
at org.python.pycode._pyx2.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.pycode._pyx16.f$0(<console>:1)
at org.python.pycode._pyx16.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
weblogic.nodemanager.NMException: I/O error while reading domain directory
wls:/offline>
wls:/offline>Hi manohar,
Please try the following article... (With Node Manager Communication type as "Plain" because it looks like you are getting PKIX security certificate chain message ) Just to isolate the issue
Topic: Start AdminServer And NodeManager Using WLST
http://middlewaremagic.com/weblogic/?p=6580
Thanks
Ravish Mody -
Starting admin server using WLST and NodeManager
Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
thanks
manohar
C:\oracle\Middleware\wlserver_10.3\server\bin>
C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
Connecting to Node Manager ...
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
loading of the trusted certificate list raised a certificate parsing exception
PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
0.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
of the trusted certificate list raised a certificate parsing exception PKIX: Un
supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : I/O error while reading domain directory
Use dumpStack() to view the full stacktrace
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline> dumpStack()
This Exception occurred at Tue May 03 10:45:03 EDT 2011.
weblogic.nodemanager.NMException: I/O error while reading domain directory
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:299)
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:312)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
a:248)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:205)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
java:52)
at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
eManagerService.java:179)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
rService.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
at org.python.pycode._pyx2.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.pycode._pyx16.f$0(<console>:1)
at org.python.pycode._pyx16.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
weblogic.nodemanager.NMException: I/O error while reading domain directory
wls:/offline>
wls:/offline>Hi manohar,
Thank you, Pierluigi for encouraging Middleware Magic Team :)
manohar, apart from what *"Pierluigi"* has suggested, additionally please notice the following messsage in your StackTrace (whih is basically a NOTICE message but does not look good)
The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object:In your case it looks like the actual issue is your Certificate which comes by default with JDK. As mentioned in this BUG.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6803022
Additionally please refer to the following Thread:
http://forums.oracle.com/forums/message.jspa?messageID=3958098#3958098
I am suspecting that you need to do the following in order to get rid of Certificate Errors which is the ROOT cause of your issue
Do the following: After taking a backup of *"$JAVA_HOME/jre/lib/security/cacerts"* file
cd $JAVA_HOME/jre/lib/security
cp -p cacerts cacerts.original
chmod 644 cacerts
keytool -delete -alias ttelesecglobalrootclass2ca -keystore cacerts
keytool -delete -alias ttelesecglobalrootclass3ca -keystore cacertsAlso try with Node Manager Communication type as "*Plain*" because it looks like you are getting PKIX security certificate chain message, just to isolate the issue.
Regards,
Ravish Mody -
Failes to start Managed server using Nodemanager from admin console
Hi
I have created the cluster using Weblogic version 9.2 MP3 with
Machine 1 --> Admin (AS) + Managed server (MS1)
Machine 2 --> Managed server(MS2)
All the servers(AS,MS1,MS2) are SSL configured to run in production mode.
Machine is associated with each managed server and node manager is up and running.
I have made Host name verification as "None"
When i start the MS 1 from admin console it comes up in running.However MS2 is not coming in running mode.
The server logs states that "Could not connect to admin server"
Cannot decrypt the password ,username and TrustKeyStorePrivatepassphrase.
Even when i write the clear text password and username in Server_Name/data/nodemanager/boot.properties,then also it throws the same error.
Node manager is not configured to SSL.
Any Clue what i am missing????Is your Machine #2 shown as "Reachable" in the admin console ( Machines -> Machine2 -> Monitoring )?
Does your managed server #2 have the same userid and password on its Server -> Configuration -> Server Start page ( UserName & Password fields ) as managed server #1?
Your boot.properties only needs 2 lines, like:
password=your plain text password
username=your plain text username -
Problem starting Admin Server using Node Manager
I have configured the Node Manager to run as a windows service. I want it to start the Admin Server when it is started. This is not working. The Node Manager starts without problem but does not appear to even attempt to start the Admin Server. No error message is written to the nodemanager.log. I have configured the following properties as described in the documentation:
StartScriptEnabled=true
StartScriptName=startWebLogic.cmd
Starting the Admin Server using wlst works. As does starting and stopping a Managed server using the Admin console. This leads me to conclude that the Node Manager configuration is ok.
WLS version is 9.2.
All suggestions as to what could be the issue here would be greatly appreciated.
Cheers!Ok, I just wasted a whole day before I found the tricks.
First, you don't need to do that StartScriptEnabled stuff, unless you have important things to add there.
Ok, and now what I found:
- You must make sure you have installed the NodeManager as a service
- Next, make sure the admin server is assigned to the right machine. Since you can do the WLST trick, that should be fine. If not, tough luck, because the docs say you cannot re-assign an admin server.
- In nodemanager.properties (...\weblogic92\common\nodemanager) make sure CrashRecoveryEnabled is set to true
- In nodemanager.domains (same dir) make sure your domain is mentioned with its path
- For each of the servers to be auto-started, make sure that a startup.properties (in <your-domain-dir> \servers\<server-name> \data\nodemanager) contains Arguments=-Xnohup (for JRockit, for Sun JDK its -Xrs)
Make sure they are started through the nodemanager, et voila, they'll be restarted after a reboot.
Why this works? At reboot, the OS ask all processes to die, nicely. Those that don't, get killed forcibly. Without the -Xnohup/rs, the WebLogic servers respond to the nice request, and the nodemanager immediately tries to restart them. Unfortunately, the OS refuses to do that, and the server process is marked as failed, and won't be restarted after reboot. With the option given, the servers ignore mr nice guy, and get killed after the nodemanager has disappeared.
What can go wrong? A lot. I was playing with the nodemanager username and password, and that took some time to clean up. I probably have to redo the entire setup just to make sure I have a repeatable experience now...
Cheers,
Bert -
Problem while starting managed server using nodemanager
Hi everyone,
I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
Is there a way to check whether the nodemanager(of X) is already running.
If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.1. yes you can check if the nodemanage is running using the following ways.
For linux env:-
a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
c. use nm() command with WLST
Example:
wls:/mydomain/serverConfig> nm()
Currently connected to Node Manager that is monitoring the domain "mydomain"
wls:/mydomain/serverConfig> nm()
Not connected to any Node Manager
wls:/mydomain/serverConfig>
To see if WLST connects to nodemanager or not?
help('nmLog') --> to check the nm logs
2. To start the nodemanager using WLST here are the commands
Example:
For single managed Server
wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
Starting server 'myserver' ...
The server 'myserver' started successfully.
wls:/mydomain/serverConfig>
For Cluster
wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
All servers in the cluster mycluster are started successfully.
wls:/mydomain/serverConfig> -
Managed servers are started/stopped from admin console using NodeManager
Hi,
I have weblogic cluster and it has 4 managed servers on two different machines with each machine having 2 managed servers.
I have node manager setup on the two machines. I use admin console to start/stop managed servers.
Now there is a requirement to add TIBCO lib and bin path to weblogic managed server path. I have added the entries in LD_LIBARY_PATH but on starting the server using admin console the TIBCO lib/bin paths are not appended to weblogic server path.
I noticed that in nodemanager.properties we have set StartScriptEnabled=false and so it doesn't use startWebLogic.sh,which internally use other configuration files.
I'm wondering as how to add these entries in WebLogic server path. Also, how the nodemanager is able to start the managed server without using startWebLogic.sh script.
In general, what happens when I click the start button in Admin console to start the managed servers which calls NodeManager internally.
Your inputs are highly appreciated.
Thanks in advance.
BR,
AjmalHi Ajmal,
For your issue there are two solution's as shown below:
Solution-1
You can add the TIBCO lib with the complete path where the TIBCO lib file is kept from console in Class Path
Console Path:
Servers > Configuration > Server Start
However this has to be done with all the managed serves.
Solution-2
If you don't want the burden to add the TIBCO lib files on every server from console then you can add the same lib files in the classpath of startWebLogic.sh and in nodemanager.properties we have set StartScriptEnabled=true. This will make sure that all the settings would be taken from the startWebLogic.sh.
This way whenever you start any of you managed servers from console it would pick up that lib files.
In both the solution you can check the managed servers *.out* files that the lib files would be present in there classpath.
Hope this would help you.
Regards,
Ravish Mody -
Unable to start Admin server by using weblogic.admin utility
Hi,
I stoped the admin server by using weblogic.admin utility command as bellow.
java weblogic.Admin -url http://server1:8008 -username adminuser -password weblogic SHUTDOWN myserver
It stopped successfully. But while starting as below i am getting error. Kindly help me out.
java weblogic.Admin -url http://172.27.72.70:8008 -username adminuser -password weblogic START myserver
<Warning> <Net> <BEA-000905> <Could not open connection with host: server1 and port: 8008.>
Failed to connect to http://172.27.72.70:8008: Destination unreachable; nested exception is:
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'star', port: '8008'; No available router to destination
Any suggestion is appreciated.
Thanks,Hi,
Thanks for your reply.
Yes, Node Manager has configured on Managed Server's host machine.
So can't we start admin server by using weblogic.admin utility if admin server is stopped?
Thanks, -
Unable to start Manager server using Node Manager
Hi,
I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
Managed server log: -
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
[root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
Nodemanager log:
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
<Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
<Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
<Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)You can start a managed server as follows:
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');
print 'CONNECT TO ADMIN SERVER';
connect(adminusername, adminpassword);
print 'START MANAGED SERVER';
start('VideotheekWebServer','Server');
nmServerStatus('VideotheekWebServer');
print 'START CLUSTER';
start('VideotheekCluster','Cluster');
nmServerStatus('VideotheekServer1');
nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager. -
Not able to start Managed server using nohup command and failed to authenticate weblogic user
Hi,
I stopped weblogic Admin server, managed server and opmnctl. and restarted Admin server successfully but I'm able to start managed start without nohup command. if I use nohup command then it's not able to get authenticate and faild to start managed server. I created boot.property file with weblogic user name and password still not working. is there anyother way to suppy login credentials for managed server?
how can I supply login credentials in below command?
nohup ./startManagedWebLogic.sh bi_server1 t3://machine:7001 > bis1_startup.log &
Appreciate you for your help
Thanks
Jay./app/obiee_11g/Oracle_BI1/jdk/bin/java -server -Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:-UseSSE42Intrinsics -Dweblogic.Name=bi_server1 -Djava.security.policy=/app/obiee_11g/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/app/obiee_11g/wlserver_10.3/server/lib/cacerts -da -Dplatform.home=/app/obiee_11g/wlserver_10.3 -Dwls.home=/app/obiee_11g/wlserver_10.3/server -Dweblogic.home=/app/obiee_11g/wlserver_10.3/server -Dcommon.components.home=/app/obiee_11g/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/app/obiee_11g/user_projects/domains/bifoundation_domain -Djrockit.optfile=/app/obiee_11g/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/servers/bi_server1 -Doracle.domain.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/carml -Digf.arisidstack.home=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/app/obiee_11g/oracle_common/modules/oracle.ossoiap_11.1.1,/app/obiee_11g/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dbi.oracle.home=/app/obiee_11g/Oracle_BI1 -DEPM_ORACLE_HOME=/app/obiee_11g/Oracle_BI1 -Dweblogic.MaxMessageSize=50000000 -DEPM_ORACLE_HOME=/app/obiee_11g/Oracle_BI1 -DHYPERION_HOME=/app/obiee_11g/Oracle_BI1 -DEPM_ORACLE_INSTANCE=novalue -Dhyperion.home=/app/obiee_11g/Oracle_BI1 -DEPM_REG_PROPERTIES_PATH=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig -Depm.useApplicationContextId=false -Doracle.biee.search.bisearchproperties=/app/obiee_11g/Oracle_BI1/bifoundation/jee/BISearchConfig.properties -Dweblogic.management.clearTextCredentialAccessEnabled=true -Doracle.notification.filewatching.interval=2000 -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.SSL.enableJSSE=true -Dfile.encoding=utf-8 -Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.search.services.BISearchServiceConfiguration -Dxdo.server.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/bipublisher -DXDO_FONT_DIR=/app/obiee_11g/Oracle_BI1/common/fonts -Drtd.instanceName=RTD_bi_server1 -Dem.oracle.home=/app/obiee_11g/oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=01scqabi01.natusmed.natus.com:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/obiee_11g/patch_wls1035/profiles/default/sysext_manifest_classpath weblogic.Server
<Nov 17, 2013 12:24:00 AM PST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Nov 17, 2013 12:24:00 AM PST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Nov 17, 2013 12:24:01 AM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
<Nov 17, 2013 12:24:07 AM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:Error: Failed to get value from Standard Input
Enter password to boot WebLogic server:
<Nov 17, 2013 12:24:07 AM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Nov 17, 2013 12:24:09 AM PST> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user starting the managed server. The reason for the error is .>
<Nov 17, 2013 12:24:09 AM PST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://01scqabi01.natusmed.natus.com:7001.>
<Nov 17, 2013 12:24:09 AM PST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Nov 17, 2013 12:24:09 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Nov 17, 2013 12:24:09 AM PST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Nov 17, 2013 12:24:09 AM PST> <Notice> <Log Management> <BEA-170019> <The server log file /app/obiee_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/bi_server1.log is opened. All server side log events will be written to this file.>
<Nov 17, 2013 12:24:19 AM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Nov 17, 2013 12:24:20 AM PST> <Critical> <Security> <BEA-090403> <Authentication for user denied>
<Nov 17, 2013 12:24:20 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Nov 17, 2013 12:24:20 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Nov 17, 2013 12:24:20 AM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Nov 17, 2013 12:24:20 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN> -
Error starting remote server w. nodemanager
All,
Here is the error I am getting trying to start the remote server using nodemanager.
http://172.24.0.81:8001 (admin)
SATEST server does not exits on the remote server. Thank you for your help, appricate it. Let me know if you need further information.
ERROR----
<Sep 22, 2008 4:46:20 PM> <Info> <NodeManager> <Starting WebLogic server with command line: /opt/bea/jrockit90_150_06/jre/bin/java -Dweblogic.Name=SATEST2 -Dj
ava.security.policy=/opt/bea/wlserver_10.0/server/lib/weblogic.policy -Dweblogic.management.server=http://172.24.0.81:8001 -Djava.library.path=/opt/bea/jrocki
t90_150_06/jre/lib/i386/jrockit:/opt/bea/jrockit90_150_06/jre/lib/i386:/opt/bea/jrockit90_150_06/jre/../lib/i386::/opt/bea/wlserver_10.0/server/native/linux/i
686:/opt/bea/wlserver_10.0/server/native/linux/i686/oci920_8 -Djava.class.path=/opt/bea/patch_wls1000/profiles/default/sys_manifest_classpath/weblogic_patch.j
ar:/opt/bea/jrockit90_150_06/lib/tools.jar:/opt/bea/wlserver_10.0/server/lib/weblogic_sp.jar:/opt/bea/wlserver_10.0/server/lib/weblogic.jar:/opt/bea/modules/f
eatures/weblogic.server.modules_10.0.0.0.jar:/opt/bea/modules/features/com.bea.cie.common-plugin.launch_2.1.0.0.jar:/opt/bea/wlserver_10.0/server/lib/webservi
ces.jar:/opt/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/opt/bea/modules/net.sf.antcontrib_1.0b2.0/lib/ant-contrib.jar::/opt/bea -Dweblogic.system.BootI
dentityFile=/opt/bea/user_projects/domains/qa_domain/servers/SATEST2/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.se
curity.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false weblogic.Server >
<Sep 22, 2008 4:46:20 PM> <Info> <NodeManager> <Working directory is "/opt/bea/user_projects/domains/qa_domain">
<Sep 22, 2008 4:46:20 PM> <Info> <NodeManager> <Server output log file is "/opt/bea/user_projects/domains/qa_domain/servers/SATEST2/logs/SATEST2.out">
<Sep 22, 2008 4:46:21 PM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/opt/bea/wlserver_10.0/platform/lib/p13n/p13n-schemas.jar:/opt/bea/wlserver_10.0/platform/lib/p13n/p13n_common.jar:/opt/bea/wlserver_10.0/platform/lib/p13n/p1
3n_system.jar:/opt/bea/wlserver_10.0/platform/lib/wlp/netuix_common.jar:/opt/bea/wlserver_10.0/platform/lib/wlp/netuix_schemas.jar:/opt/bea/wlserver_10.0/plat
form/lib/wlp/netuix_system.jar:/opt/bea/wlserver_10.0/platform/lib/wlp/wsrp-client.jar:/opt/bea/wlserver_10.0/platform/lib/wlp/wsrp-common.jar>
<Sep 22, 2008 4:46:22 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R26.4.0-63_CR302700-72606-1.5.0_06-20
061127-1104-linux-ia32 from BEA Systems, Inc.>
<Sep 22, 2008 4:46:24 PM EDT> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {3DES}/Q0Ui/e8S9ILKA67csL+8g== from the fi
le /opt/bea/user_projects/domains/qa_domain/servers/SATEST2/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties f
rom another domain into /opt/bea/user_projects/domains/qa_domain/servers/SATEST2/data/nodemanager/boot.properties, change the encrypted attribute to its clear
text value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the s
erver. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceExcept
ion: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
<Sep 22, 2008 4:46:24 PM EDT> <Critical> <Security> <BEA-090518> <Could not decrypt the password attribute value of {3DES}/Q0Ui/e8S9ILKA67csL+8g== from the fi
le /opt/bea/user_projects/domains/qa_domain/servers/SATEST2/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties f
rom another domain into /opt/bea/user_projects/domains/qa_domain/servers/SATEST2/data/nodemanager/boot.properties, change the encrypted attribute to its clear
text value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the s
erver. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceExcept
ion: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
Enter username to boot WebLogic server:<Sep 22, 2008 4:46:24 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 Wed May 9 18:10:27 EDT 2
007 933139 >
<Sep 22, 2008 4:46:26 PM EDT> <Info> <Management> <BEA-141223> <The server name SATEST2 specified with -Dweblogic.Name does not exist. The configuration inclu
des the following servers {AdminServer}.>
<Sep 22, 2008 4:46:26 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name SATEST2 specified with -Dweblogic.Name does not exist. The configuration includes
the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:148)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:38)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:378)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:125)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:647)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:419)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:377)
at weblogic.Server.main(Server.java:67)
>
<Sep 22, 2008 4:46:26 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 22, 2008 4:46:26 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 22, 2008 4:46:26 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Sep 22, 2008 4:46:27 PM> <Debug> <NodeManager> <Waiting for the process to die: 7590>
<Sep 22, 2008 4:46:27 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 22, 2008 4:46:27 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>Thanks. I just reinstall the software and did not have issue. Maybe the issue was caused since I was trying to configure Weblogic running on Window 2003 as admin server and Linux as my remote server.
Here is how I got it to work. I reinstalled software on the Linux box and used Linux box as my primary server with admin console running on that and window 2003 as my remote node.
Thanks for you help. I appreciate it -
Starting Manage Server using node manager
Hi,
Hi,
I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
but not able to start Managed server using node manager
its giving exception as below;
error:- wls:/nm/webdomain> nmStart('ms1')
Starting server ms1 ...
Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
plz help me out in this
Thanks in advanceAn example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
"By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped." -
HANDSHAKE_FAILURE problem when starting managed server via NOdeManager
hi all, i am trying to start a managed server using nodeManager, but i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command start for
server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
to negotiate an acceptable set of security parameters.. Please ensure that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try to start
the managed server via adminserver console, i got the exception mentioned in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver, and
nodemanager is supposed to run at localhost:5555 (and indeed it does, because
ihave started it successfully).
thanx in advance and regards marcoMarco.
Sorry, this is not a solution to your problem but i am trying to solve the same
problem for a week now.
I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
same error. I know that the default certificate installed provides a hostname
verification of weblogic.com. I turned the hostname verification off, i put in
the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
error when starting the managed server. I went ahead and created my own certificate
for machine called mallik, created my own passphrase, created a new keystore,
made the admin server view the keystore, used the same certificate for both the
admin server and the node manager. It still fails with the same error. I went
ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
totally confused now what needs to be done.
My nodeManger.hosts looks like this:
mallik 10.100.10.130
managedServer1 10.100.10.130
managedServer2 10.100.10.13
Below is the startNodeManager.cmd.
@echo off
@rem *************************************************************************
@rem This script can be used to start the WebLogic NodeManager
@rem
@rem This script sets the following variables before starting the NodeManager:
@rem
@rem WL_HOME - The root directory of your WebLogic installation.
@rem NODEMGR_HOME - The home directory for this NodeManager instance.
@rem JAVA_HOME - Location of the version of Java used to start WebLogic
@rem Server. This variable must point to the root directory of
@rem a JDK installation and will be set for you by the
@rem installer. See the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
list of
@rem supported JVMs on Windows NT.
@rem PATH - Adds the JDK and WebLogic directories to the system path.
@rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
@rem JAVA_OPTIONS - Java command-line options for running the server. (These
@rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
@rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
@rem -client, etc.)
@rem MEM_ARGS - The variable to override the standard memory arguments
@rem passed to java
@rem
@rem *************************************************************************
SETLOCAL
set WL_HOME=C:\bea7.0\weblogic700
set NODEMGR_HOME=%WL_HOME%\common\nodemanager
set JAVA_HOME=C:\bea7.0\jdk131_06
Call %WL_HOME%\common\bin\commEnv.cmd
@rem If NODEMGR_HOME does not exist, create it
:checkNodeManagerHome
if exist %NODEMGR_HOME% goto checkJava
echo.
echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
mkdir %NODEMGR_HOME%
@rem Check that java is where we expect it to be
:checkJava
if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
echo The JDK wasn't found in directory %JAVA_HOME%.
echo Please edit this script so that the JAVA_HOME
echo variable points to the location of your JDK.
goto finish
:runNodeManager
if not "%JAVA_VM%" == "" goto noResetJavaVM
rem set JAVA_VM=-hotspot
set JAVA_VM=%COMM_VM%
:noResetJavaVM
if not "%MEM_ARGS%" == "" goto noResetMemArgs
set MEM_ARGS=-Xms32m -Xmx200m
:noResetMemArgs
@echo on
set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
cd %NODEMGR_HOME%
#"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
"-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
"-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
"-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
"-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
"-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
"-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
"-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
goto finish
:finish
ENDLOCAL
I would appreciate if anybody can help me.
Mallik.
"Marco" <[email protected]> wrote:
>
hi all, i am trying to start a managed server using nodeManager, but
i keep on
getting following exception:
weblogic.nodemanager.NodeManagerException: [Could not execute command
start for
server managedServer via the Node Manager - reason: [CommandInvoker:
Failed to
send command: 'online to server 'managedServer' to NodeManager at host:
'localhost:5555'
with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
was unable
to negotiate an acceptable set of security parameters.. Please ensure
that the
NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
at
java.lang.reflect.Method.invoke(Native Method) at
here is my script for starting nodemanager
set JAVA_HOME=c:\bea\jdk131
set WL_HOME=c:\bea\weblogic700
set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
-Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
-Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
-Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
-Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
-Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
weblogic.nodemanager.NodeManager
i have created an admin server, called adminserver
then i have created in the same domain a server called managedserver
both servers run on the same machine,at different port number.
i have created a machine, and associated managedserver to it.
in the machine/configuration/nodemanager i have set listenaddress localhost
and
listenport 5555.
my nodemanager starts automatically at htat port. however, when i try
to start
the managed server via adminserver console, i got the exception mentioned
in
the subject.
can anyone help?
regards
marco
can anyone point me to the right direction for solving this problem?
in the adminserver console i have defined a machine for teh managedserver,
and
nodemanager is supposed to run at localhost:5555 (and indeed it does,
because
ihave started it successfully).
thanx in advance and regards marco -
Starting Admin Server with nohup from Node Manager
We are using WebLogic 9.1 on Windows 2003. I am able to start the Admin Server from the Node Manager using WLST but when the user logs off the server the Admin Server exits.
The documentation says to use the -Xrs or -Xnohup options for Sun Jvm or JRockit Jvm. Where should this option be invoked?
I have placed the option in the Arguments field of the 'Server Start' tab in the Admin Console. And I have also placed the option on the command line when invoking the WLST The Admin Server still exits when the user logs off the server.
Can this option be used with the WLST command that starts the Admin Server? If so, does anyone know the syntax?
Your help would be appreciated.
ThanksCan you explain how are you doing this. Are starting the server using WLST nmStart()?
If you are using nmStart(), then is your nodemanager running as a windows service.
Also, the option you are referring to should be used for the JVM running as a Windows service. If you start nodemanager as a service (which you typically should do in your case), then you can place the -XnoHup option on the Java command line for the Nodemanager service..
Venkat -
Not able to start admin server
I am getting this error when ever i am trying to start weblogic server
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=
48m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=D:\app\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sys_manifest_cla
sspath\weblogic_patch.jar;D:\app\Oracle\MIDDLE~1\patch_oepe1032\profiles\default
\sys_manifest_classpath\weblogic_patch.jar;D:\app\Oracle\MIDDLE~1\JDK160~1.5-3\l
ib\tools.jar;D:\app\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar;D:\app\O
racle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\app\Oracle\MIDDLE~1\WLSE
RV~1.3\server\lib\weblogic.jar;D:\app\Oracle\MIDDLE~1\modules\features\weblogic.
server.modules_10.3.2.0.jar;D:\app\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webserv
ices.jar;D:\app\Oracle\MIDDLE~1\modules\ORGAPA~1.0/lib/ant-all.jar;D:\app\Oracle
\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;D:\app\Oracle\MIDDLE~1\WLSERV
~1.3\common\eval\pointbase\lib\pbclient57.jar;D:\app\Oracle\MIDDLE~1\WLSERV~1.3\
server\lib\xqrl.jar
PATH=D:\app\Oracle\MIDDLE~1\patch_wls1032\profiles\default\native;D:\app\Oracle\
MIDDLE~1\patch_oepe1032\profiles\default\native;D:\app\Oracle\MIDDLE~1\WLSERV~1.
3\server\native\win\32;D:\app\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;D:\app\Oracl
e\MIDDLE~1\modules\ORGAPA~1.0\bin;D:\app\Oracle\MIDDLE~1\JDK160~1.5-3\jre\bin;D:
\app\Oracle\MIDDLE~1\JDK160~1.5-3\bin;D:\app\291188\product\11.2.0\dbhome_1\bin;
C:\Program Files\CA\SC\CAWIN\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32
\Wbem;C:\Program Files\Intel\DMIX;C:\PROGRA~1\CA\SC\CAM\bin;C:\Program Files\CA\
DSM\bin;D:\app\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_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:port\console *
starting weblogic with Java version:
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode)
Starting WLS with line:
D:\app\Oracle\MIDDLE~1\JDK160~1.5-3\bin\java -client -Xms256m -Xmx512m -XX:Com
pileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dweblogic.Name=AdminS
erver -Djava.security.policy=D:\app\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblog
ic.policy -Xverify:none -da -Dplatform.home=D:\app\Oracle\MIDDLE~1\WLSERV~1.3
-Dwls.home=D:\app\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\app\Oracl
e\MIDDLE~1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterat
iveDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\app\
Oracle\MIDDLE~1\patch_wls1032\profiles\default\sysext_manifest_classpath;D:\app\
Oracle\MIDDLE~1\patch_oepe1032\profiles\default\sysext_manifest_classpath weblo
gic.Server
<Oct 13, 2010 10:53:42 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting We
bLogic Server with Java HotSpot(TM) Client VM Version 14.0-b16 from Sun Microsys
tems Inc.>
<Oct 13, 2010 10:53:47 AM IST> <Info> <Management> <BEA-141107> <Version: WebLog
ic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
<Oct 13, 2010 10:53:49 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to STARTING>
<Oct 13, 2010 10:53:49 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing s
elf-tuning thread pool>
<Oct 13, 2010 10:53:49 AM IST> <Notice> <LoggingService> <BEA-320400> <The log f
ile D:\app\Oracle\Middleware\user_projects\domains\domain1\servers\AdminServer\l
ogs\AdminServer.log will be rotated. Reopen the log file if tailing has stopped.
This can happen on some platforms like Windows.>
<Oct 13, 2010 10:53:49 AM IST> <Notice> <LoggingService> <BEA-320401> <The log f
ile has been rotated to D:\app\Oracle\Middleware\user_projects\domains\domain1\s
ervers\AdminServer\logs\AdminServer.log00003. Log messages will continue to be l
ogged in D:\app\Oracle\Middleware\user_projects\domains\domain1\servers\AdminSer
ver\logs\AdminServer.log.>
<Oct 13, 2010 10:53:49 AM IST> <Notice> <Log Management> <BEA-170019> <The serve
r log file D:\app\Oracle\Middleware\user_projects\domains\domain1\servers\AdminS
erver\logs\AdminServer.log is opened. All server side log events will be written
to this file.>
<Oct 13, 2010 10:53:55 AM IST> <Error> <Security> <BEA-090870> <The realm "myrea
lm" failed to be loaded: weblogic.security.service.SecurityServiceException: com
.bea.common.engine.ServiceInitializationException: weblogic.security.spi.Provide
rInitializationException: A failure occurred attempting to load LDIF for provide
r Authorizer from file D:\app\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\XACMLAuthori
zerInit.ldift..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.Servic
eInitializationException: weblogic.security.spi.ProviderInitializationException:
A failure occurred attempting to load LDIF for provider Authorizer from file D:
\app\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\XACMLAuthorizerInit.ldift.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itializeRealm(CommonSecurityServiceManagerDelegateImpl.java:465)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.lo
adRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:875)
Truncated. see log file for complete stacktrace
Caused By: com.bea.common.engine.ServiceInitializationException: weblogic.securi
ty.spi.ProviderInitializationException: A failure occurred attempting to load LD
IF for provider Authorizer from file D:\app\Oracle\MIDDLE~1\WLSERV~1.3\server\li
b\XACMLAuthorizerInit.ldift.
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(S
erviceEngineImpl.java:365)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(S
erviceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(Servic
eEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.j
ava:72)
at weblogic.security.service.CSSWLSDelegateImpl.getService(CSSWLSDelegat
eImpl.java:156)
Truncated. see log file for complete stacktrace
Caused By: weblogic.security.spi.ProviderInitializationException: A failure occu
rred attempting to load LDIF for provider Authorizer from file D:\app\Oracle\MID
DLE~1\WLSERV~1.3\server\lib\XACMLAuthorizerInit.ldift.
at com.bea.common.store.bootstrap.BootStrapServiceImpl.loadFullLDIFTempl
ate(BootStrapServiceImpl.java:900)
at com.bea.common.store.bootstrap.BootStrapServiceImpl.loadLDIFTemplate(
BootStrapServiceImpl.java:678)
at com.bea.common.store.bootstrap.BootStrapServiceImpl.loadLDIFXACMLAuth
orizerTemplate(BootStrapServiceImpl.java:173)
at com.bea.common.store.bootstrap.BootStrapServiceImpl.loadLDIFXACMLAuth
orizerTemplate(BootStrapServiceImpl.java:157)
at com.bea.common.security.internal.service.BootStrapServiceImpl.loadLDI
FXACMLAuthorizerTemplate(BootStrapServiceImpl.java:106)
Truncated. see log file for complete stacktrace
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal store error> kodo.jdo.Fa
talDataStoreException: The transaction has been rolled back. See the nested exc
eptions for details on the errors that occurred.
at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.jav
a:2170)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2017)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1915)
at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java
:1833)
at org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRunt
ime.java:81)
Truncated. see log file for complete stacktrace
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 nonfatal store error> kodo.jdo
.DataStoreException: ORA-00942: table or view does not exist
{prepstmnt 25551189 INSERT INTO BEAXACMLAP (DOMN, REALMN, TYPEN, CN, XVER, CTS,
WCN, WCI, WXF, XD, XS, MTS) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [params
=(String) domain1, (String) myrealm, (String) Policies, (String) urn:bea:xacml:2
.0:entitlement:resource:type@E@Fjndi@G@M@Oapplication..., (String) 1.0, (null) n
ull, (null) null, (null) null, (Blob) oracle.sql.BLOB@18ed284, (InputStream) jav
a.io.ByteArrayInputStream@19eef79, (String) 3, (Timestamp) 2010-10-13 10:53:55.7
15] [reused=0]} [code=942, state=42000]
FailedObject: [email protected]a
3
at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:420
7)
at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictiona
ry.java:4171)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java
:102)
at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java
:72)
at kodo.jdbc.kernel.BatchingPreparedStatementManager.flushInternal(Batch
ingPreparedStatementManager.java:214)
Truncated. see log file for complete stacktrace
Caused By: org.apache.openjpa.lib.jdbc.ReportingSQLException: ORA-00942: table o
r view does not exist
{prepstmnt 25551189 INSERT INTO BEAXACMLAP (DOMN, REALMN, TYPEN, CN, XVER, CTS,
WCN, WCI, WXF, XD, XS, MTS) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [params
=(String) domain1, (String) myrealm, (String) Policies, (String) urn:bea:xacml:2
.0:entitlement:resource:type@E@Fjndi@G@M@Oapplication..., (String) 1.0, (null) n
ull, (null) null, (null) null, (Blob) oracle.sql.BLOB@18ed284, (InputStream) jav
a.io.ByteArrayInputStream@19eef79, (String) 3, (Timestamp) 2010-10-13 10:53:55.7
15] [reused=0]} [code=942, state=42000]
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingCo
nnectionDecorator.java:192)
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(Log
gingConnectionDecorator.java:57)
at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnect
ion$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866)
at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate
(DelegatingPreparedStatement.java:269)
at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStateme
nt.executeUpdate(JDBCStoreManager.java:1398)
Truncated. see log file for complete stacktrace
>
<Oct 13, 2010 10:53:55 AM IST> <Notice> <Security> <BEA-090082> <Security initia
lizing using security realm myrealm.>
<Oct 13, 2010 10:53:55 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server
failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Secu
rity Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Oct 13, 2010 10:53:55 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to FAILED>
<Oct 13, 2010 10:53:55 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical
service failed. The server will shut itself down>
<Oct 13, 2010 10:53:55 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server st
ate changed to FORCE_SHUTTING_DOWN>Oracle WebLogic Server 11g uses a built in production quality (limited in capacity) LDAP server to store user authorization information such as roles, credentials etc. You can also use an external RDBMS instead of the built in LDAP server. Using the RDBMS security store is highly recommended by Oracle in some situations, especially in a cluster environment (for using SAML 2.0 services).
If you choose to use the RDBMS Security Store, you can configure the security store either through the Configuration Wizard or through WLST at the command line.
The problem arises because the underlying database has not been configured (or not configured correctly). If you're going to use the RDMBS security store (instead of the default LDAP server), please do the following:
1. First, make sure you test the database connection on the Configuration Wizard page (Look at the right hand top corner for the button that tests the connection).
2. Create necessary RDBMS tables in the Security Datastore. I understand others in this thread have suggested this option. However, I want to emphasize that you must log in as the same user you've used as the user name to test your RDBMS connection (I used system as the user name) in Step 1 and run the following script:
$ @WL_HOME\server\lib\rdbms_security_store_oracle.sql (I'm using Oracle as an example - there are similar scripts for DB2, MS SQL Server).
The script will create about 30 or so tables. You can log out of the DB at this point.
3. Start up the Admin Server. It should start correctly now.
Hope this helps!
Thanks! Sam
sam alapati
[email protected]
Edited by: user10463043 on Nov 9, 2010 4:38 PM
Edited by: user10463043 on Nov 9, 2010 4:39 PM
Edited by: user10463043 on Nov 9, 2010 4:40 PM
Maybe you are looking for
-
i need help with what i posted in the title
-
I have a panel class with a slider on it . pseudocode: public class MyJSlider extends JPanel{ private JSlider myjslider; private Color mycolor; public Color getColor(){return mycolor;} the action taken by the JSlider is to set mycolor to a new Color(
-
Hi all i have installed developersuit10g release2 and configured the webutil according to webutil_demo. but when i run the demo form wu_test_106 it gives me error ORA-06508. i checked avaerything its according to the demo document. i also download th
-
How to use WebDav in CQ5 on Window7 64 bit?
Setting up webdev for windows ,when I am adding a new network while giving the crx.default link, it is asking for the Username & Password. After entering Username & Password(I tried admin/admin), one pop-up is coming:-The folder you entered does not
-
I am a computer idiot. HELP
My house has wireless through a Linksys router. Everything was working fine until this Christmas. I bought my sons new laptops (WiFi enabled). We can't seem to hook them up to the wireless network. I know our security password, but I think the se