Installing weblogic without node manager

Hi
I installed weblogic 9.2 on windows 64 bit env. My machine is a VM.
I installed the admin server and managed server on different ports both on the same machine.
So i dont think there is a need for node manager in this context since there are no multiple machines involved.
I start the admin server and then try to start the managed server from the admin console . This is the error its giving me
The server dev_01 does not have a machine associated with it.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
where dev_01 is the name of the managed server.
However, i am able to start the managed server thorugh script
startManagedWebLogic.cmd dev_01 http://localhost:7001
I would not prefer to have the node manager . so how would i start the managed server from the admin console?
Any help much appreciated

Hi,
Starting a ManagedServer from AdminConsole requires Nodemnager should be associated with the ManagedServer.
NodeManager is a Utility which is used to remotely start, stop Servers. If you try to start a ManagedServer from AdminConsole , in this case also it is called as *"Remote Start"* even if the ManagedServer is located in the Same Physical Box.

It means without associating the NodeManager to your ManagedServer you cannot start that ManagedServer from the AdminConsole. Because as soon as u try to start the ManagedServer from AdminConsole the AdminServer tries to pass the Start Instructions to the NodeManager Associated with That ManagedServer. If NiodeManager is associated with the ManagedServer then it performs all the prework before starting the Server and then issues the ManagedServer Start command.
 
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

Similar Messages

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

WLST without Node Manager

We are not using node manager to start|stop the servers. But we are monitoring the servers, getting the runtime values of the servers remotely using WLST. Can we also use WLST to automatically start and stop the managed servers without node manager, when the server status is failed. Also, can we do that remotely?
Please advise me where I can find the documentation on it.

No, you cannot start and stop servers via WLST without a Node Manager running.
-satya
BEA Blog: http://dev2dev.bea.com/blog/sghattu/

To manage coherence JVM's from weblogic server node manager

we have configured weblogic server node managers on weblogic admin console and want to add multiple coherence JVM on node manager to manage multiple coherence server JVM's. we have configured mode manager on each computer that hosts the Coherence server instance that we want to control with Node Manager. Is it possible to spawn multiple JVM's using the node manager which has been installed on each weblogic machines.

I was able to start the server but while passing the tangosol parameters as arguments we are getting below errors.
Console encountered the following error weblogic.management.provider.UpdateException: [Management:141191]The prepare phase of the configuration update failed with an exception: at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:670) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:28) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:112) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52) at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211) at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:457) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:178) Caused by: weblogic.management.ManagementException: Must import new custom cluster configuration file for Coherence-1. at weblogic.management.mbeans.custom.CoherenceClusterSystemResource.setUsingCustomClusterConfigurationFile(CoherenceClusterSystemResource.java:149) at weblogic.management.configuration.CoherenceClusterSystemResourceMBeanImpl.setUsingCustomClusterConfigurationFile(CoherenceClusterSystemResourceMBeanImpl.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48) at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:539) at com.bea.staxb.runtime.internal.MultiIntermediary.setValue(MultiIntermediary.java:82) at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType$ElementQNameProperty.fill(ByNameRuntimeBindingType.java:348) at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:159) at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51) at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:48) at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184) at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156) at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51) at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:48) at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199) at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169) at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65) at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150) at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleConfigTreeLoad(RuntimeAccessDeploymentReceiverService.java:967) at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:599) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:29) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:114) at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52) at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211) at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:458)
Please let me know if anyone has come across this error and got any solution for it.

Starting manged server without node manager

Hi All
I know that we can start managed servers from admin console but for that we have to have node manager on that machine running.
But I want to know,if I dont want to use node manager,can i start some how managed servers from admin console.That is if my node manager is not running,can i start the managed servers using admin console.
Please let me know if it is possible or not.
Thanks in advance.
DJ

Without the node manager running, you cannot start the managed servers from the admin console.
There are other options you can use to start the managed servers though, which i guess you might be aware of.
Just in case you don't, it's nicely documented by Atul @ http://onlineappsdba.com/index.php/2008/08/03/oracle-weblogic-server-startupshutdown/
Hope this helps.
Thanks,
Patrick

Can i use single node manager with two weblogic domain?

I am very new to weblogic and node manager.
i had created two domains in weblogic. (single node manger).
Can i connect both domains with same nodemanger?
How to do this?

The node manager uses a nodemanager.domains file to determine which domains it manages, for example,
domain_name=/path_to_domain/domain_name
other_domain_name=/path_to_other_domain/other_domain_name
This file can be found in the NODEMANAGER_HOME, that you specified when starting the node manager (startNodeManager - NODEMGR_HOME="${WL_HOME}/../oracle_common/common/nodemanager")
When you are running the domain on multiple machines you have to enroll the node manager into the domain (http://docs.oracle.com/cd/E23943_01/web.1111/e13813/reference.htm#i1065827)
A scripted example can be found here: Middleware Snippets: Automate WebLogic Installation and Configuration. The Node Manager administration guide can be found here: Oracle&reg; Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server 11g Release 1 (10.3.6) -….

Unable to start SOA server through Node Manager

Hi All,
I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
I am getting an error while trying to start soa server with nmStart() command, below is the error message...
"Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
I executed the dumpStack() command, and i am getting the output as "No stack trace available"
If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
I followed some of the blogs like...
http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
Experts, please give your advice.
Many Thanks,
N

Hi Narsing,
I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
Regards,
Neeraj Sehgal
Hi Neeraj,
I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
I have made sure the property StartScriptEnabled= true.
I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to FAILED_NOT_RESTARTABLE status.
If i see the log messages in the nodemanager.log, this is the below message...
<Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
<Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
 at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
 at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
 at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
 at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
 at weblogic.nodemanager.server.Handler.run(Handler.java:71)
 at java.lang.Thread.run(Thread.java:662)
The log message in the soa_server1.out file is as below...
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
<Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
Many Thanks.

OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

Hi,
Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
To get it activated I bounced services and when I try to start Node Manager it gives below error --
<Aug 30, 2011 2:02:42 PM CDT> <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>
<Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
+ set +x
I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
Cherrish Vaidiyan
Edited by: Cherrish on Aug 30, 2011 3:14 PM

Hi,
There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
Cherrish Vaidiyan

Picking list generation without Warehouse management

Hi all,
I have requirement for my client to generate picking list genereation without wm. so i assigned EK00 condition type, transmission medium, Language, send time & picking confirmation in shipping point. Also created condition record in VP01SHP tcode but still unable to generate output for picking in VL70.
Please suggest !
Thanks & Regards,
Shakti

Following 2 recently discussed SDN thread will be help to you:
- Re: We use picking option without warehouse management installed
- picking without warehouse management
Regards
JP

Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

Hello,
I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
Can someone help me resolve this issue?
<Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

Can you see what listen address you have given to Node Manager in console or in config.xml?
<machine xsi:type="unix-machineType">
<name>Servername</name>
<node-manager>
<name>Servername</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
Another way to start Managed server is to use startManaged.sh script.

Node Manager installed as service does not start managed servers. WLS 10.3

Hi All,
I have installed the node manager as a windows service. When the service starts up it does start the managed servers.
In the nodemanager.log file it shows that the node manager is reading the startup.properties file for all of the managed servers.
<Jul 24, 2009 6:38:13 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\NODEMA~1\nodemanager.domains>
<Jul 24, 2009 6:38:13 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <IntegrationServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\IntegrationServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <ProdBackupServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\ProdBackupServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <QAServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\QAServer\data\nodemanager\startup.properties">
<Jul 24, 2009 6:38:13 AM> <INFO> <Plain socket listener started on port 5556, host localhost>
The node manager properties file contains the following
#Mon Apr 20 10:54:45 PDT 2009
DomainsFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
JavaHome=C\:\\bea\\JROCKI~1
AuthenticationEnabled=false
NodeManagerHome=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1
LogLevel=INFO
DomainsFileEnabled=true
StartScriptEnabled=false
StartScriptName=startWebLogic.cmd
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=true
LogFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
The managed servers' boot.properties file and startup file are below
boot.properties:
#Thu Jul 23 13:48:26 PDT 2009
CustomTrustKeyStoreFileName=C\:\\bea\\wlserver_10.3\\common\\ssl\\supportTrust2008.jks
TrustKeyStore=CustomTrust
password={3DES}mvtUK8oB8JEiQoVES4AQIQ\=\=
CustomTrustKeyStorePassPhrase={3DES}34+15HRlP6qqpZX3bTPp+Q\=\=
CustomTrustKeyStoreType=JKS
username={3DES}P5mMHiWLnf2UtssZbQtezkDtIS0COiHW
startup.properties:
#Server startup properties
#Thu Jul 23 13:48:27 PDT 2009
Arguments=-Xms1024m -Xmx1024m -Xnohup
JavaHome=C\:\\bea\\jrockit_160_05
SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
RestartMax=2
RestartDelaySeconds=0
RestartInterval=3600
BeaHome=C\:\\bea
ClassPath=C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\lib\\itext\\WEB-INF\\lib\\itext.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic_sp.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic.jar;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\massmutual\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\assuritylife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\minnesotalife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\lib\\ltclibrary\\WEB-INF\\classes\\
AdminURL=http\://localhost\:7001
JavaVendor=BEA
AutoRestart=true
AutoKillIfFailed=false
I am wondering if I left out a parameter some where.
Any help would be greatly appreciated.
Thanks,
Greg

First of all, I assume you mean "... up it does NOT start ..."?
It might be helpful to point out that the purpose of the NodeManager is not to start the servers, but to "control" the servers through remote commands. When the NodeManager starts back up, it tries to reset the servers to the last known state it set them to, based on remote commands.
For instance, if your system was running and you stopped the servers through the admin console and then restarted the machine, the NodeManager would not start the servers on machine startup, because the last controlled state of the servers was down. If all of your WebLogic servers were running as a result of NodeManager commands, and you pulled the plug on the box, when you restarted the machine, the NodeManager probably would restart the servers.

Weblogic 10.3.6 update node manager error.

After installing 10.3.5 I did the installation on WebLogic 10.3.6 upgrade. (wls1036_upgrade_generic.jar). Domain installation does not work if I did, and then I saw when I ran the node manager.
Error
C:\oracle\Middleware\wlserver_10.3\server\bin>set CLASSPATH=.;C:\oracle\MIDDLE~1
\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\ora
cle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpath\weblogic_patch
.jar;C:\oracle\MIDDLE~1\patch_jdev1112\profiles\default\sys_manifest_classpath\w
eblogic_patch.jar;C:\PROGRA~1\Java\JDK17~1.0_0\lib\tools.jar;C:\oracle\MIDDLE~1\
WLSERV~1.3\server\lib\weblogic_sp.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\w
eblogic.jar;C:\oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.6.0
.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\oracle\MIDDLE~1
\modules\ORGAPA~1.1/lib/ant-all.jar;C:\oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/
ant-contrib.jar;
C:\oracle\Middleware\wlserver_10.3\server\bin>if not "" == "" set CLASSPATH=;.;C
:\oracle\MIDDLE~1\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic
patch.jar;C:\oracle\MIDDLE~1\patchocp371\profiles\default\sys_manifest_classpa
th\weblogic_patch.jar;C:\oracle\MIDDLE~1\patch_jdev1112\profiles\default\sys_man
ifest_classpath\weblogic_patch.jar;C:\PROGRA~1\Java\JDK17~1.0_0\lib\tools.jar;C:
\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\oracle\MIDDLE~1\WLSERV
~1.3\server\lib\weblogic.jar;C:\oracle\MIDDLE~1\modules\features\weblogic.server
.modules_10.3.6.0.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C
:\oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\oracle\MIDDLE~1\modules\
NETSFA~1.0_1/lib/ant-contrib.jar;
C:\oracle\Middleware\wlserver_10.3\server\bin>if not "" == "" set CLASSPATH=.;C:
\oracle\MIDDLE~1\patch_wls1036\profiles\default\sys_manifest_classpath\weblogic_
patch.jar;C:\oracle\MIDDLE~1\patch_ocp371\profiles\default\sys_manifest_classpat
h\weblogic_patch.jar;C:\oracle\MIDDLE~1\patch_jdev1112\profiles\default\sys_mani
fest_classpath\weblogic_patch.jar;C:\PROGRA~1\Java\JDK17~1.0_0\lib\tools.jar;C:\
oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\oracle\MIDDLE~1\WLSERV~
1.3\server\lib\weblogic.jar;C:\oracle\MIDDLE~1\modules\features\weblogic.server.
modules_10.3.6.0.jar;C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:
\oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\oracle\MIDDLE~1\modules\N
ETSFA~1.0_1/lib/ant-contrib.jar;;
C:\oracle\Middleware\wlserver_10.3\server\bin>cd C:\oracle\MIDDLE~1\WLSERV~1.3\c
ommon\NODEMA~1
C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>if not "" == "" if not "" == "" go
to runNMWithListenAddressAndPort
C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
enAddress
C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>if not "" == "" goto runNMWithList
enPort
C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>"C:\PROGRA~1\Java\JDK17~1.0_0\bin\
java.exe" -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Dcoher
ence.home=C:\oracle\MIDDLE~1\COHERE~1.7 -Dbea.home=C:\oracle\MIDDLE~1 -Xverify:
none "-Djava.security.policy=C:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.p
olicy" "-Dweblogic.nodemanager.javaHome=C:\PROGRA~1\Java\JDK17~1.0_0" weblogic.N
odeManager -v
<Jan 4, 2012 4:22:31 PM> <INFO> <Loading domains file: C:\oracle\MIDDLE~1\WLSERV
~1.3\common\NODEMA~1\nodemanager.domains>
Jan 04, 2012 4:22:31 PM weblogic.nodemanager.server.NMServerConfig initDomainsMa
p
INFO: Loading domains file: C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1\nodema
nager.domains
<Jan 4, 2012 4:22:36 PM> <INFO> <Loading identity key store: FileName=C:/oracle/
MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
Jan 04, 2012 4:22:36 PM weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig
INFO: Loading identity key store: FileName=C:/oracle/MIDDLE~1/WLSERV~1.3/server\
lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true
<Jan 4, 2012 4:22:36 PM> <SEVERE> <Fatal error in node manager server>
weblogic.nodemanager.common.ConfigException: Unknown key store identity alias or
not a key entry alias: DemoIdentity
at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
va:177)
at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
at weblogic.NodeManager.main(NodeManager.java:31)
Jan 04, 2012 4:22:36 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
weblogic.nodemanager.common.ConfigException: Unknown key store identity alias or
not a key entry alias: DemoIdentity
at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.ja
va:177)
at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:102)
at weblogic.nodemanager.server.NMServer.init(NMServer.java:186)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:148)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:380)
at weblogic.NodeManager.main(NodeManager.java:31)
C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>goto finish
C:\oracle\MIDDLE~1\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
Correction would be how.

Hi,
You should check admin server's logs found under ${DOMAIN_HOME}/servers/AdminServer/logs.
Regards,
Mohab

Unable to start node manager of WebLogic 12c on OEL 5.9 64 bit

Hi,
I have WLS 12 running on OEL 5.9 64 bit.
The installation ise JDK instead of the default JRockit.
The version of Java that has been installed is from rpm: jdk-7u25-linux-x64.rpm
I have created a domain.
I am unable to start the Node Manager the first time, and thus unable to create the file nodemanager.properties.
I get an error:
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
I have added JAVA_USE_64BIT=true in the commEnv.sh, but it seems not to help.
Does someone know how to get the nodde manager runing on a Linux x86 64 bit?
Thanks by advance for any tip.

Hello, try this:
1. Set the environment to use the 64 bit WLS library:
export LD_LIBRARY_PATH=
/u01/Middleware/wlserver_10.3/server/native/linux/x86_64/:/u01/Middleware/wlserver_10.3/server/native/linux/i686/
2. Retry the domain configuration:
/u01/Middleware/Oracle_PFRD/bin/config.sh

How to install Oracle BPEL Process Manager with the BEA WebLogic

Hi ,
I will install Oracle BPEL Process Manager with BEA WebLogic 9.2(MP2). I have download orabpel_10133_WebLogic.zip ,then Modify the following mandatory installation properties in the orabpel_10133_WebLogic\bpelDomain.properties file:
# BEA_HOME is the path where Weblogic is Installed
BEA_HOME=/opt/bea
# JAVA_HOME is the path of jdk folder inside your weblogic
JAVA_HOME=/opt/bea/jrockit90_150_10
# DOMAIN_HOME is the path where you wish to create your domain called BPELDomain
DOMAIN_HOME=/opt/bea/user_projects/domains
# APPS_HOME is the path where you wish to copy your applications and adapters that are required for oracleBPELServer
APPS_HOME=/opt/bea/user_projects/apps
# BEA_HOME is the path where BPEL PM is Installed
BPEL_HOME=/home/oracle/bpel/product/10.1.3.1/OraBPEL_1/bpel
# DRIVER_TYPE is the datasource class that installable use to create a datasources for oracleBPELServer
DRIVER_TYPE=oracle.jdbc.xa.client.OracleXADataSource
# DB_URL is the url to connect to orabpel schema
DB_URL=jdbc:oracle:thin:@16.157.134.17:1521:orcl
# DB_USER is the user Id for orabpel shema in database
DB_USER=ORABPEL
#DB_PASSWORD is the password for orabpel schema in database
DB_PASSWORD=bpel
#BPEL_SERVER_NAME is the server i.e. to be created under BPELDomain
BPEL_SERVER_NAME=oracleBPELServer
#PROXY_HOST is the Host name of the proxy server
PROXY_HOST=www-proxy.us.oracle.com
#PROXY_HOST=
#PROXY_PORT is the Port where the proxy server is running
PROXY_PORT=80
#PROXY_PORT=
#NON_PROXY_HOST is the list of non proxy hosts that are divided by a | symbol
#NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com
NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com|16.157.134.135
When I run the setup.sh , it will report
BUILD FAILED
/opt/software/WL_Installables/build.xml:131: Traceback (innermost last):
File "./wl_scripts/bpelDomain.py", line 22, in ?
File "./wl_scripts/createGroupsAndUsers.py", line 4, in ?
weblogic.management.utils.AlreadyExistsException: [Security:090267]Group BpelGroup
Actully ,there is no BpelGroup in Weblogic. Does anybody know how to solve it ?

MAke sure you have not set ANY environment variable related to Oracle / BEA / Java / LD_library path. Use the following script to unset / set the initial settings:
#!/bin/sh
unset ORACLE_BASE ORACLE_HOME ORACLE_SID ORACLE_TERM
unset LD_LIBRARY_PATH LD_LIBRARY_PATH_64
unset CLASSPATH JAVA_HOME
export PATH=.:/usr/sbin:/usr/bin:/usr/local/bin:/opt/VRTS/bin
export BEA_HOME=/appl/oracle/products/9.2/weblogic
Marc
http://orasoa.blogspot.com

While i m starting node manager in weblogic

Dear All,
my weblogic server was working fine after restarted the windows server, when i am trying to start the node manager i m getting below error, please guide me please, this is production
<Sep 22, 2013 12:58:07 AM> <WARNING> <There was a problem initializing the domain 'weblogic_domain' at 'D:\Oracle\Middleware\u
_domain'. Please make sure that this domainName: 'weblogic_domain' is registered and is fully enrolled for this nodemanager at
projects\domains\weblogic_domain'.>
Sep 22, 2013 12:58:07 AM weblogic.nodemanager.server.NMServer findOrCreateDomainManager
WARNING: There was a problem initializing the domain 'weblogic_domain' at 'D:\Oracle\Middleware\user_projects\domains\weblogic
at this domainName: 'weblogic_domain' is registered and is fully enrolled for this nodemanager at: 'D:\Oracle\Middleware\user_
ain'.
<Sep 22, 2013 12:58:07 AM> <WARNING> <I/O error while reading domain directory>
java.io.IOException: Invalid state file format. State file contents:
 at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
 at weblogic.nodemanager.server.AbstractServerMonitor.loadStateInfo(AbstractServerMonitor.java:497)
 at weblogic.nodemanager.server.AbstractServerMonitor.isCleanupAfterCrashNeeded(AbstractServerMonitor.java:156)
 at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:25)
 at weblogic.nodemanager.server.AbstractServerManager.recoverServer(AbstractServerManager.java:147)
 at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:23)
 at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:105)
 at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:60)
 at weblogic.nodemanager.server.NMServer.findOrCreateDomainManager(NMServer.java:284)
 at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:273)
 at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
 at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
 at weblogic.nodemanager.server.Handler.run(Handler.java:71)
 at java.lang.Thread.run(Thread.java:662)
Sep 22, 2013 12:58:07 AM weblogic.nodemanager.server.Handler handleDomain
WARNING: I/O error while reading domain directory
java.io.IOException: Invalid state file format. State file contents:
 at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
 at weblogic.nodemanager.server.AbstractServerMonitor.loadStateInfo(AbstractServerMonitor.java:497)
 at weblogic.nodemanager.server.AbstractServerMonitor.isCleanupAfterCrashNeeded(AbstractServerMonitor.java:156)
 at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:25)
 at weblogic.nodemanager.server.AbstractServerManager.recoverServer(AbstractServerManager.java:147)
 at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:23)
 at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:105)
 at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:60)
 at weblogic.nodemanager.server.NMServer.findOrCreateDomainManager(NMServer.java:284)
 at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:273)
 at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:227)
 at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:109)
 at weblogic.nodemanager.server.Handler.run(Handler.java:71)
 at java.lang.Thread.run(Thread.java:662)
thanks

why do you mis-post this problem in an Oracle database forum when root cause & fix are external to any Oracle database?

Installing weblogic without node manager

Similar Messages

Maybe you are looking for