Start managed server in multihomed machine with cluster?

Hi,
 I have problems with starting a remote managed server.
 I have a cluster configured with 2 managed servers in the same machine. I added a new managed server but assigned to other machine.
 MachineA:
 -AdminServer:7001,
 -ManagedServerA1: 7004, ManagedServerA2:7006
 -Cluster
 MachineB:
 -ManagedServerB: 7003
 I tried to start ManagedServerB in Machine A but I have got this error:
 startManagedWeblogic.cmd ManagedServerB http://MachineA:7001
 <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address â€œIP of MachineB that I am usingâ€ might be incorrect or another process is using port 7003: java.net.BindException: Cannot assign requested address: JVM_Bind.>
 <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
 But the port is not used by any other process or server.
 Other question: is it necessary to start all managed servers, local and remote in the server where my application is deployed?
 Is it the correct way for using a cluster in multihomed machine?
 Is there any documentation for configuring a cluster specifically for this case?
 By the way, I am using Weblogic 91.
 Regards,
 Hicyo

Hi,
 I am also having the same problem below.Can someone suggest a solution to my problem?
 I have a cluster configured with 2 managed servers in the same machine. I added a new managed server but assigned to other machine.
 MachineA:
 -AdminServer:7001,
 -ManagedServerA1: 7004, ManagedServerA2:7006
 -Cluster
 MachineB:
 -ManagedServerB: 7003
 I tried to start ManagedServerB in Machine A but I have got this error:
 startManagedWeblogic.cmd ManagedServerB http://MachineA:7001
 <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address â€œIP of MachineB that I am usingâ€ might be incorrect or another process is using port 7003: java.net.BindException: Cannot assign requested address: JVM_Bind.>
 <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
 But the port is not used by any other process or server.

Similar Messages

Start Managed Server from Another Machine

 Hello,
 In a two machines cluster starting a managed on the secondary machine not the
 one hosting the admin server, I keep getting the following error:
 Managed server log error:
 The WebLogic Server did not start up properly.
 Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
 not found for MBean orsus:Name=orsus,Type=Domain'
 Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
 not found for MBean orsus:Name=orsus,Type=Domain
 Admin Server log:
 <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error
 occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain.
 Method: null. Exception: javax.management.AttributeNotFoundException: Attribute
 AdministrationMBeanAuditingEnabled
 not found for MBean orsus:Name=orsus,Type=Domain.
 javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
 not found for MBean orsus:Name=orsus,Type=Domain
 at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
 at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
 at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
 at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
 at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
 at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
 Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed
 Server orsusClusterNode_2 is disconnected from the admin server. This may be either
 due to a managed server getting temporarily partitioned or the managed server
 process exiting.>
 <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest
 failed
 weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
 exception:
 [weblogic.rjvm.PeerGoneException: ; nested exception is:
 weblogic.utils.net.SocketResetException].
 weblogic.rjvm.PeerGoneException: ; nested exception is:
 weblogic.utils.net.SocketResetException
 at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
 at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
 at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
 Source)
 at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
 at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
 at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 Caused by: weblogic.utils.net.SocketResetException
 at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
 ... 2 more
 --------------- nested within: ------------------
 weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
 exception:
 [weblogic.rjvm.PeerGoneException: ; nested exception is:
 weblogic.utils.net.SocketResetException]
 at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
 Source)
 at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
 at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
 at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 Any ideas?
 Regards.
 Eran
 [wlerrlog.txt]


Do both the machines have the same weblogic server installation? Looks
 like there is a conflict, the machine where the managed server is
 running has a weblogic server version lesser than the admin server.
 Check the versions on both machines.
 java weblogic.version
 should print the version information.
 Thanks,
 -satya
 eran wrote:
 >
 > Hello,
 >
 > In a two machines cluster starting a managed on the secondary machine not the
 > one hosting the admin server, I keep getting the following error:
 >
 > Managed server log error:
 > ***************************************************************************
 > The WebLogic Server did not start up properly.
 > Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
 > not found for MBean orsus:Name=orsus,Type=Domain'
 > Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
 > not found for MBean orsus:Name=orsus,Type=Domain
 >
 >
 > Admin Server log:
 > <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error
 > occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain.
 > Method: null. Exception: javax.management.AttributeNotFoundException: Attribute
 > AdministrationMBeanAuditingEnabled
 > not found for MBean orsus:Name=orsus,Type=Domain.
 > javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
 > not found for MBean orsus:Name=orsus,Type=Domain
 > at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
 > at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
 > at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
 > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
 > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
 > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
 > at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
 > Source)
 > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
 > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
 > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
 > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
 > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
 > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed
 > Server orsusClusterNode_2 is disconnected from the admin server. This may be either
 > due to a managed server getting temporarily partitioned or the managed server
 > process exiting.>
 > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest
 > failed
 > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
 > exception:
 > [weblogic.rjvm.PeerGoneException: ; nested exception is:
 > weblogic.utils.net.SocketResetException].
 > weblogic.rjvm.PeerGoneException: ; nested exception is:
 > weblogic.utils.net.SocketResetException
 > at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
 > at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
 > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
 > Source)
 > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
 > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
 > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 > Caused by: weblogic.utils.net.SocketResetException
 > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
 > ... 2 more
 > --------------- nested within: ------------------
 > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested
 > exception:
 > [weblogic.rjvm.PeerGoneException: ; nested exception is:
 > weblogic.utils.net.SocketResetException]
 > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown
 > Source)
 > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
 > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
 > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 >
 > Any ideas?
 >
 > Regards.
 > Eran
 >
 >
 >
 >
 > ------------------------------------------------------------------------
 >
 > Managed server log error:
 > ***************************************************************************
 > The WebLogic Server did not start up properly.
 > Exception raised: 'javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain'
 > Reason: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain
 > ***************************************************************************
 >
 >
 > Admin Server log:
 > <Feb 5, 2004 9:20:17 AM GMT+02:00> <Error> <Management> <BEA-140001> <An error occurred while getting attribute AdministrationMBeanAuditingEnabled on MBean orsus:Name=orsus,Type=Domain. Method: null. Exception: javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled
 > not found for MBean orsus:Name=orsus,Type=Domain.
 > javax.management.AttributeNotFoundException: Attribute AdministrationMBeanAuditingEnabled not found for MBean orsus:Name=orsus,Type=Domain
 > at weblogic.management.internal.DynamicMBeanImpl.getXAttributeInfo(DynamicMBeanImpl.java:1917)
 > at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java:585)
 > at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java:177)
 > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1183)
 > at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1153)
 > at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java:284)
 > at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
 > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
 > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
 > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
 > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
 > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
 > at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 >
 > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Warning> <Management> <BEA-141138> <Managed Server orsusClusterNode_2 is disconnected from the admin server. This may be either due to a managed server getting temporarily partitioned or the managed server process exiting.>
 > <Feb 5, 2004 9:20:18 AM GMT+02:00> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
 > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
 > [weblogic.rjvm.PeerGoneException: ; nested exception is:
 > weblogic.utils.net.SocketResetException].
 > weblogic.rjvm.PeerGoneException: ; nested exception is:
 > weblogic.utils.net.SocketResetException
 > at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
 > at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
 > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown Source)
 > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
 > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
 > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 > Caused by: weblogic.utils.net.SocketResetException
 > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:111)
 > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
 > ... 2 more
 > --------------- nested within: ------------------
 > weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
 > [weblogic.rjvm.PeerGoneException: ; nested exception is:
 > weblogic.utils.net.SocketResetException]
 > at weblogic.management.internal.RemoteMBeanServerImpl_812_WLStub.addNotificationListener(Unknown Source)
 > at weblogic.management.internal.BaseNotificationListenerImpl.addFilterAndHandback(BaseNotificationListenerImpl.java:48)
 > at weblogic.management.internal.MBeanProxy.addNotificationListener(MBeanProxy.java:350)
 > at weblogic.server.ServerLifeCycleRuntime$1.execute(ServerLifeCycleRuntime.java:523)
 > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 >

OSB 10gR3 - Starting Managed server on remote machine

I have 2 Windows 2003 Enterprise machines.
I have OSB 10gR3 installed on both with Node Manager running on default port, on both.
I create the servicebustutorial domain and start the admin server on the first machine.
On the second machine, I use the WLST to
<ul><li>connect('weblogic','password','t3://xxx.xxx.xxx.xxx:7001') # connect to admin server on first machine
</li>
<li>nmEnroll('c:/bea/wlserver_10.3/common/nodemanager') # make node manager visible
</li>
<li>nmEnroll('c:/bea/user_projects/domains/servicebustutorial') # enroll in the servicebustutorial</li>
</ul>
Now, I don't know if this is the correct thing to do.
Back on the first machine, I create a new machine to represent the second Windows box.
I can see the node manager on the second machine using the machine monitoring page.
I then create a new server that is assigned to the new machine.
I can attempt to start the new server on the second machine.
The Server directory appears in the servers directory on the second windows box.
Log files appear on the second box but the config.xml is not there, and thus, the server fails to start.
I would have thought that the server config would have propogated from the admin server, is this a wrong assumption?
What am I doing wrong?
Thanks, in advance.
...Lyall

Thanks for replying.
I login as a local administrator on the machine that WebLogic runs. All operations are performed using that login (starting admin server, starting node manager).
I changed permissions on C:\BEA, all the way down, localadmin group has full control, everywhere.
I tried changing nodemanager C:\bea\wlserver_10.3\common\nodemanager\nodemanager.properties LogLevel to DEBUG but then NodeManager refuses to start, so I returned it back to INFO.
I set debug on the Managed Server I am trying to setup, as you suggested.
I even updated the NodeManager and Server boot.properties files to be cleartext and Deleted the LDAP directory within the Managed Server (as I assume it's re-created if it does not exist)
Wow, heaps comes out, but the following may be relevant.
In particular, this single line, causes concern.
bq. ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE \\ ExecuteThread: '0' for queue: 'weblogic.kernel.Default \\ (self-tuning)'> <<WLS Kernel>> <> <> \\ <1236334820297> <BEA-000000> <[Security:090295 |http://forums.oracle.com//]caught unexpected exception>
It's an unexpected exception but it's not an Error and only reported as a Debug! I could be climbing up the wrong tree, but the following log output is what immediately precedes the login failure.
bq. ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.wrap ClassLoader=java.net.URLClassLoader@1f0e58> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.wrap ControlFlag=LoginModuleControlFlag: required> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.JAASLoginServiceImpl.login created LoginContext> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.JAASLoginServiceImpl.login ThreadContext ClassLoader Current=sun.misc.Launcher$AppClassLoader@124dfc> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize LoginModuleClassName=weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize ClassLoader=java.net.URLClassLoader@1f0e58> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize created delegate login module> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <LDAP ATN LoginModule initialized> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize delegated> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.login> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <LDAP Atn Login> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will be delegated> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will use NameCallback to retrieve name> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[1] will be delegated> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle will delegate all callbacks> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle delegated callbacks> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle got username from callbacks[0], UserName=weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <LDAP Atn Login username: weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820281> <BEA-000000> <new LDAP connection to host 134.251.218.157 port 7001 use local connection is true> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820281> <BEA-000000> <created new LDAP connection LDAPConnection { ldapVersion:2 bindDN:""}> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <connection succeeded> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <getConnection return conn:LDAPConnection { ldapVersion:2 bindDN:""}> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <authenticate user:weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <getDNForUser search("ou=people,ou=myrealm,dc=Tester", "(&(uid=weblogic)(objectclass=person))", base DN & below)> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <[Security:090295|http://forums.oracle.com/forums/]caught unexpected exception> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <LDAP Atn Abort> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit delegated, returning false> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.authenticate authenticate failed for user weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.isLocked(weblogic)> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic)> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) UserLockout Login failure for user in realm myrealm> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.getInvaliLoginUsersHighCount()> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) User weblogic has 1 failures in realm myrealm> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImplUserLockout InvalidLogin Record GC not needed> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) UserLockout About to multicast login failure for user SecurityMessage realm:myrealm record:SecurityMulticastRecord: origin: Strategic realmName: myrealm seqnum: 1 timestamp: Mar 6, 2009 8:50:20 PM username: weblogic nextSeqNo:1> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImplUserLockout Can't create multicastSession because ClusterServices are unavailable> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Critical> <Security> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Critical> <WebLogicServer> <osb-strat> <Strategic> <Main Thread> <<WLS Kernel>> <> <> <1236334820312> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. \\ weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. \\ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source) \\ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source) \\ at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source) \\ 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) \\ >

Can't start manager server on other machine from admin console

hi, m fredzh
i have weblogic 10.3.2 where i created a cluster named cluster1 on production mode
the machines and servers list as follow:
cluster1 192.168.1.100
--machine1
--server1 192.168.1.100
--machine2
-server2 192.168.1.101
i create nodemanager on machine2, and set the type as ssl, the listener address 192.168.1.101,
then login on 192.168.1.101, and run wlst.sh , nmEnroll and then start startNodemanaged.sh ..
start server2 on the admin console(on 192.168.1.100), failed and the log as follow:
can anbody help me, thank you..
==============================================================================
<Critical> <WebLogicServer> <localhost.localdomain> <managerServer2> <main> <<WLS Kernel>> <> <> <1286788326928> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
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)
Caused By: java.lang.reflect.InvocationTargetException
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 weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
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)
Caused By: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:125)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:173)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
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 weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
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)
Edited by: fredzh on 2010-10-12 下午6:54

hi,Jay
i followed the steps as follow:
1、change prod mode to dev
2、modified the config.xml entrys on the all two servers:
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<credential-encrypted>test</credential-encrypted>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
3、enrolled the node, then started the two adminservers, started server2's nodemanager..server2 can be started from the cluster admin console.
4、change the dev mode to prod mode on admin console, it failed throw error:
"in production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean"
i checked the config.xml ,the entrys i had changed were not aotomatically encrypted,may i manually encryp the clear text value? ..follow is the config.xml :
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>cluster_domain</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>cluster_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<anonymous-admin-lookup-enabled>false</anonymous-admin-lookup-enabled>
<credential-encrypted>test</credential-encrypted>
<web-app-files-case-insensitive>false</web-app-files-case-insensitive>
<compatibility-connection-filters-enabled>false</compatibility-connection-filters-enabled>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<principal-equals-case-insensitive>false</principal-equals-case-insensitive>
<principal-equals-compare-dn-and-guid>false</principal-equals-compare-dn-and-guid>
<downgrade-untrusted-principals>false</downgrade-untrusted-principals>
<enforce-strict-url-pattern>true</enforce-strict-url-pattern>
<cross-domain-security-enabled>false</cross-domain-security-enabled>
</security-configuration>
<jta>
<security-interop-mode>default</security-interop-mode>
</jta>
<server>
<name>AdminServer</name>
<ssl>
<hostname-verifier xsi:nil="true"></hostname-verifier>
<hostname-verification-ignored>true</hostname-verification-ignored>
<export-key-lifespan>500</export-key-lifespan>
<client-certificate-enforced>false</client-certificate-enforced>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<inbound-certificate-validation>BuiltinSSLValidationOnly</inbound-certificate-validation>
<outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
<allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
<use-server-certs>false</use-server-certs>
</ssl>
<listen-port>7110</listen-port>
<listen-address></listen-address>
</server>
<server>
<name>server2</name>
<machine>machine2</machine>
<listen-port>7110</listen-port>
<listen-address>192.168.1.101</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>/opt/jdk1.6.0_21</java-home>
<bea-home>/root/Oracle/Middleware</bea-home>
<root-directory>/root/Oracle/Middleware/user_projects/domains/cluster_domain</root-directory>
<username>weblogic</username>
<password-encrypted>{AES}xhSI75AxXtXdMrCXRgA2uY5pfcxUGE9X4YXTjfe1XEY=</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>machine2</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>192.168.1.101</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<admin-server-name>AdminServer</admin-server-name>
</domain>
Edited by: fredzh on 2010-10-13 下午7:57

How to install managed server on another machine

Can anybody point me where I can find related installation doc?
Thanks in advance

I want to configure the manages servers in a windows 2000 environment......
to do eastblish this environment, I do not want to install the weblogic on client machine(I mean developer machine). I wanted to install weblogic on one server and on a remote machines, i want to map the server(WLS) machine and do work from there.....I wonder with out installing the WLS on client machine(developer machine),..is this possible to start managed server from client machines with out installing wls on that tmachines......?, with wls installed on client machine, its working perfecr........ but can I start/stop managed servers with out wls installation on client machine ....?if so ...how..? what scripts to modify........?
Thanks

How to start managed server from admin server both running on separate machines

 I have an admin server on one machine and created a managed server on different
 machine, I am not able to start managed server from either machine. When I used
 the admin server machine to start the managed server remotely I got this message
 Connecting to http://fkeita:7001...
 <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
 ng using realm myrealm.>
 <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
 ogic Managed Server "managedserver3" for domain "admindomain">
 <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
 create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
 java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
 a
 ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
 <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
 to
 bind to any port such that it is not reachable from the console.>
 <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
 initialize the server: Fatal initialization exception>
 When I tried to connect managed server from its machine to admin server (running
 on separate machine ) I got this error
 Starting WebLogic Server...
 Connecting to http://fkeita:7001...
 <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
 ng using realm myrealm.>
 <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
 ed during initialization. Exception:java.lang.SecurityException: Authentication
 for user system denied
 java.lang.SecurityException: Authentication for user system denied
 at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 SecurityServiceManager.java:978)
 at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 erviceManager.java:1116)
 at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 at weblogic.Server.main(Server.java:31)
 >
 <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
 initialize the server: Fatal initialization exception
 Throwable: java.lang.SecurityException: Authentication for user system denied
 java.lang.SecurityException: Authentication for user system denied
 at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 SecurityServiceManager.java:978)
 at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 erviceManager.java:1116)
 at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 at weblogic.Server.main(Server.java:31)
 >
 The WebLogic Server did not start up properly.
 Exception raised:
 java.lang.SecurityException: Authentication for user system denied
 at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 SecurityServiceManager.java:978)
 at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 erviceManager.java:1116)
 at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 at weblogic.Server.main(Server.java:31)
 Reason: Fatal initialization exception
 Throwable: java.lang.SecurityException: Authentication for user system denied
 java.lang.SecurityException: Authentication for user system denied
 at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 SecurityServiceManager.java:978)
 at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 erviceManager.java:1116)
 at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 at weblogic.Server.main(Server.java:31)
 Thanks.


 I used startmanagedweblogic managedserver1 http://fkeita:7001 to try to start managed
 server, but it did not work, and got error messages. Error messages are posted
 on my first posting.
 "pankaj" <[email protected]> wrote:
 >Use the startManagedWeblogic.cmd / .sh script to start your
 >Managed/Clustered servers
 >
 >
 >"fkeita" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> I have an admin server on one machine and created a managed server
 >on
 >different
 >> machine, I am not able to start managed server from either machine.
 >When I
 >used
 >> the admin server machine to start the managed server remotely I got
 >this
 >message
 >>
 >> Connecting to http://fkeita:7001...
 >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security
 >initializi
 >> ng using realm myrealm.>
 >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328>
 ><Starting WebL
 >> ogic Managed Server "managedserver3" for domain "admindomain">
 >> <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350>
 ><Unable to
 >> create a server socket on Channel Default for: BFINKELMAN/90.0.0.25,
 >port:
 >8002.
 >> java.net.BindException: Cannot assign requested address: JVM_Bind
 >Perhaps
 >the
 >> a
 >> ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using
 >port
 >8002.>
 >>
 >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server
 >failed
 >> to
 >> bind to any port such that it is not reachable from the console.>
 >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342>
 ><Unable to
 >> initialize the server: Fatal initialization exception>
 >>
 >> When I tried to connect managed server from its machine to admin server
 >(running
 >> on separate machine ) I got this error
 >>
 >> Starting WebLogic Server...
 >> Connecting to http://fkeita:7001...
 >> <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security
 >initializi
 >> ng using realm myrealm.>
 >> <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364>
 ><Server fail
 >> ed during initialization. Exception:java.lang.SecurityException:
 >Authentication
 >> for user system denied
 >> java.lang.SecurityException: Authentication for user system denied
 >> at
 >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 >> SecurityServiceManager.java:978)
 >> at
 >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 >> erviceManager.java:1116)
 >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 >> at weblogic.Server.main(Server.java:31)
 >> >
 >> <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342>
 ><Unable to
 >> initialize the server: Fatal initialization exception
 >> Throwable: java.lang.SecurityException: Authentication for user system
 >denied
 >> java.lang.SecurityException: Authentication for user system denied
 >> at
 >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 >> SecurityServiceManager.java:978)
 >> at
 >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 >> erviceManager.java:1116)
 >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 >> at weblogic.Server.main(Server.java:31)
 >> >
 >>
 >***************************************************************************
 >> The WebLogic Server did not start up properly.
 >> Exception raised:
 >> java.lang.SecurityException: Authentication for user system denied
 >> at
 >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 >> SecurityServiceManager.java:978)
 >> at
 >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 >> erviceManager.java:1116)
 >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 >> at weblogic.Server.main(Server.java:31)
 >> Reason: Fatal initialization exception
 >> Throwable: java.lang.SecurityException: Authentication for user system
 >denied
 >> java.lang.SecurityException: Authentication for user system denied
 >> at
 >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
 >> SecurityServiceManager.java:978)
 >> at
 >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
 >> erviceManager.java:1116)
 >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
 >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
 >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
 >> at weblogic.Server.main(Server.java:31)
 >>
 >> Thanks.
 >
 >

How to start managed server from admin server both running

I have an admin server on one machine and created a managed server on different
machine, I am not able to start managed server from either machine. When I used
the admin server machine to start the managed server remotely I got this message
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server (running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
ed during initialization. Exception:java.lang.SecurityException: Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
<Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Reason: Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
Thanks.

"fkeita" <[email protected]> wrote in message
news:[email protected]...
>
I have an admin server on one machine and created a managed server ondifferent
machine, I am not able to start managed server from either machine. When Iused
the admin server machine to start the managed server remotely I got thismessage
>
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328><Starting WebL
ogic Managed Server "managedserver3" for domain "admindomain">
<Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350><Unable to
create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port:8002.
java.net.BindException: Cannot assign requested address: JVM_Bind Perhapsthe
a
ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port8002.>
>
Try running netstat to see whether another process is actually running at
the given address/port.
Also check using ifconfig/ipconfig or directly checking /etc/hosts file of
the box to see whether the ips addreses are correct.
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Serverfailed
to
bind to any port such that it is not reachable from the console.>
<Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342><Unable to
initialize the server: Fatal initialization exception>
When I tried to connect managed server from its machine to admin server(running
on separate machine ) I got this error
Starting WebLogic Server...
Connecting to http://fkeita:7001...
<Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Securityinitializi
ng using realm myrealm.>
<Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364><Server fail
ed during initialization. Exception:java.lang.SecurityException:Authentication
for user system denied
java.lang.SecurityException: Authentication for user system denied
atweblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:978)
atweblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>Seems to be some issue with security credentials.
Try running the manageed server directly (as sort of admin) by not passing
the admin server url and bringing it just like an admin server.
See if this works. If it works, then soemthing wrong in the way the admin
server is receiving the request/security credentials from managed server.
Also make sure both managed and admin servers are on the same patch/service
pack level.
-Sabha

A lot of problem for an error: Cannot start Managed Server through NM

Hi, all. Thank for coming here.
My main problem is cannot start Manager server through Node Manager. I've configured with the same way on my friend's network and It's works but It's wrong with mine.
my weblogic domain:
Machine 1: Administration Server + 1 Managed server
Machine 2: 1 Managed server
all of these servers communicate through SSL protocol. When I try to start Managed Server on remote machine:
output from console which was invoked startWebLogic.sh
+<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
+<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
And this is MS01 log:
starting weblogic with Java version:
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]+
The application has requested the JVM to exit with an fatal error from JNI. Error message:
JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Starting WLS with line:
+/opt/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=MS01 -Djava.security.policy=/opt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xrs -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/opt/Oracle/Middleware/wlserver_10.3 -Dwls.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.35:7001 -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/opt/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/patch_wlp1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/wlportal_10.3/p13n/lib/system:/opt/Oracle/Middleware/wlportal_10.3/light-portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/lib/system:/opt/Oracle/Middleware/wlportal_10.3/analytics/lib/system:/opt/Oracle/Middleware/wlportal_10.3/apps/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/Oracle/Middleware/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/Oracle/Middleware/wlportal_10.3/portal/lib/security weblogic.Server+
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]+
The application has requested the JVM to exit with an fatal error from JNI. Error message:
JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Stopping PointBase server...
PointBase server stopped.
And this is output from console which node manager runs on:
+<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
+<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
I tried to start Managed server some times again, but I face up to strange issue, this is output from console which Admin Server runs on (these exception messages throws continuously):
+<Sep 9, 2010 12:42:53 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "p13nDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
+<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceAlwaysXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
I can ensure that all of these connection pool has configured to run on 9093 port already. Then I view the DOMAIN_NAME/pointbase.log, it said:
Unable to start the server. start server error: java.net.BindException: Address already in use
I cannot understand what's run on pointbase address ?
All of these error make me angry, because I've configured with the same way on other system and It's work. I've spent all of week to fix these bug, but I'm having nothing :((
Please help me.

Thank Jay SenSharma.
I've looked for these JAVA_OPTION values you said, but I cant found them. That value is content of JAVA_DEBUG option, not JAVA_OPTION. In my situation, JAVA_DEBUG=" " (it's not set by default).
Please re-view my error log:
Node Manager output:
+<Sep 9, 2010 11:32:44 PM> <WARNING> <Exception while starting server 'MS01'>+
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Sep 9, 2010 11:32:44 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'MS01'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:541)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:619)
Managed server MS01's log:
+<Sep 9, 2010 11:45:05 PM> <INFO> <NodeManager> <Server output log file is '/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.out'>+
+<Sep 9, 2010 11:45:07 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>+
+<Sep 9, 2010 11:45:09 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010+
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
+<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://xmlns.oracle.com/weblogic/domain>+
+<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - /opt/Oracle/Middleware/user_projects/domains/devdomain/<unknown>:11:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>+
+<Sep 9, 2010 11:45:14 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320400> <The log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log00002. Log messages will continue to be logged in /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log.>+
+<Sep 9, 2010 11:45:14 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log is opened. All server side log events will be written to this file.>+
+<Sep 9, 2010 11:45:17 PM EDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details..+
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+ at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)+
+ at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
+ Truncated. see log file for complete stacktrace+
Caused By: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
+ at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
+ at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
+ Truncated. see log file for complete stacktrace+
Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
+ at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
+ at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
+ Truncated. see log file for complete stacktrace+
Caused By: java.lang.RuntimeException: There were errors initializing your configuration: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal store error> org.apache.openjpa.util.StoreException: com.pointbase.jdbc.jdbcUniversalDriver
+ at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:123)+
+ at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.createConnectionFactory(JDBCConfigurationImpl.java:776)+
+ at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:683)+
+ 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 org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:288)+
+ at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
+ at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
+ 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 org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)+
+ at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
+ at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
+ at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
+ at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
+ at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
+ at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
+ at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)+
+ at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)+
+ at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.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)+
Caused by: java.lang.ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
+ at java.lang.Class.forName0(Native Method)+
+ at java.lang.Class.forName(Class.java:169)+
+ at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:85)+
+ ... 38 more+
+ at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:302)+
+ at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
+ at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
+ at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
+ Truncated. see log file for complete stacktrace+
+>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>+
+<Sep 9, 2010 11:45:17 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:+
There are 1 nested errors:
+weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)+
+ at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.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)+
+>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>+
+<Sep 9, 2010 11:45:17 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>+
+<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>+
+<Sep 9, 2010 11:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 16443>+
+<Sep 9, 2010 11:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>+
+<Sep 9, 2010 11:45:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>+
ps:
I've come your weblog and found alot of tips for debugging WebLogic Server exceptions. It's really helpful. Thanks.
Edited by: Doubt_Man on Sep 10, 2010 10:49 AM
Edited by: Doubt_Man on Sep 10, 2010 3:54 PM

Starting managed server with nodemanager

Hi there,
Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
(1) set up the main server and able to run the server successfully.
(2) set up one managed server, set up one machine on same server as main server.
(3) assign machine to created managed server.
(4) after that i've tried to run that managed server and error giving as below:
Error from main server terminal
===================
<NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
Error from Node Manager Termal
====================
<Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
<Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Thanks in advance,
Tim

Sorry , i forgot to mention that the OS i am using is Solaris.
Thx

Problem with starting managed server

In a domain , I have one admin server and one managed server. When im trying to start managed server , the message says,
Message icon - Warning For server Server-0, the Node Manager associated with machine Machine-0 is not reachable.
Message icon - Warning 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 or you are not authorized to perform the action requested. No action will be performed.
Already i started the node manager , i checked with node manager's log files, and I found these error in log files,
<Jul 30, 2010 12:54:32 PM> <Warning> <Uncaught exception in server handler: javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from 127.0.0.1 - 127.0.0.1. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.
 at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
 at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertReceived(Unknown Source)
 at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
 at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
 at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
 at com.certicom.tls.record.ReadHandler.processRecord(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:66)
 at java.lang.Thread.run(Thread.java:619)
Can any one help me to troubleshoot this.

Hi Jose,
To Disable SSL communication for NodeManager do the following:
Step1). Open the *"nodeManager.properties"* file from *<WL_HOME>\common\nodemenager* (Example Location : C:\bea103\wlserver_10.3\common\nodemanager ) directory and change the value of SecureListener property to false:
SecureListener=false
Step2). Login to AdminConsole and then
AdminConsoleHome--->Machines --><Your_MachineName> (Click here)--->NodeManager (Tab)---> Select the type as "Plain" from the combo box (by default it will be SSL)
Step3). Restart the NodeManager ....better if you follow Step4) as well...
Step4). Please Enroll your NodeManager as described in the Step8) of the following Link: http://weblogic-wonders.com/weblogic/2010/04/28/weblogic-clustering-in-remote-boxes/
Thanks
Jay SenSharma

Error starting managed server with JRockit VM

I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace

I found the solution . The reason for this is that JRockit's High Performance Thread
System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
The two asynchronous I/O systems clash and the result is the error you see.
There are two ways around this problem. Either disable JRockit's High Performance
Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
disable Weblogic's Native I/O.
For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
and change this to NativeIOEnabled="false".
For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
to
weblogic.system.nativeIO.enable=false
"Manoj jayadevan" <[email protected]> wrote:
>
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during
i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed
and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace

Start managed server with the node manager???

Hello,
I have one admin server and one managed server for my domain. Can i Start the amdin and managed server from the node manager and not just the admin server. Currently with the install of node manager only the admin server starts and not the managed server. I need to log in to the admin server to start my managed server which is very cumbersome.
Edited by: user9021545 on Mar 11, 2011 1:58 PM

hi,
In order to start Managed server from the console itself,then u have to enroll your node manager.
Step1). Start the AdminServer...using startScript "startWebLogic.sh/cmd"
step2)start ur node manager using stat node manager scripts,
step3)Login to adminConsole and then see the NodeManager is Reachable or not
If reachanble
then run "setWLSEnv.sh/cmd".
Then run wlst.sh file
Step3)connect('weblogic','weblogic','t3://localhost:7001')
Step4)nmEnroll('C:/bea103/user_projects/domains/7001_Domain','C:/bea103/wlserver_10.3/common/nodemanager')
After this u will be able to start and stop managed server from console itself
Note:even after dis your managed server doesnt starts then please check under <DOMAIN_ROOT>\servers\<SERVER_NAME> whether you have a folder name as security and inside it whether you have file called as boot.properties
if no then follow these below steps
Please create a directory "security" inside your
<DOMAIN_ROOT>\servers\<SERVER_NAME>
inside "<DOMAIN_ROOT>\servers\<SERVER_NAME>\security" ( Example Location:
WLS103/user_projects/domains/Test_Domain/servers/AdminServer/security )
directory create a file with exactly same name as "boot.properties" and with
following 2 lines inside it:
username=weblogic
password=weblogic
NOTE: Here "weblogic" is the Administrator username & password...
if you want dont want to run Admin server from foreground then try runnin it as a background process
This link wi; b helpful for that
http://middlewareforum.com/weblogic/?cat=23
any further help in this den do let me know
Regards
Fabian

Starting Managed Server: bi_server1 with error

I am installing OBIEE 11.1.1.7, but at configuration time the error occurred below.
The console weblogic start correctly, but is bi_server1 as ADMIN status.
Stopping Derby Server...
Starting AdminServer
Starting the domain ...
progress in calculate progress1
Executing Task: Starting Managed Server: bi_server1
oracle.as.install.bi.wls.ServerLifeCycleException: Failed to achieve state RUNNING in 3600seconds.   The server is currently in state ADMIN
        at oracle.as.install.bi.wls.ServerLifeCycle.waitForManagedWLSServerState(ServerLifeCycle.java:119)
        at oracle.as.install.bi.wls.ServerLifeCycle.startServerSynchronous(ServerLifeCycle.java:59)
        at oracle.as.install.bi.biconfig.standard.StartStopManagedServer.doExecute(StartStopManagedServer.java:55)
        at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
        at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
        at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
        at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
        at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
        at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
        at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
        at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
        at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
        at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
        at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
        at java.lang.Thread.run(Thread.java:662)

I had same issue while installing OBIEE 11.1.1.7.0
Check your data Sources are connecting. To do that
1. Login to console, go to Data Sources
2. Click on mds-owsm
3. Click on Monitoring --> Testing on second line below Monitoring
4. Select bi_server1 and click Test Data Source.
If this fails, check your tnsnames.ora file and verify you are able to connect to the database server from the obiee installation server.
If this is working fine, then follow these steps:
1. Login to console, go to servers
2. Click on control on Summary of Servers
3. Click on Lock & Edit in the left pane
4. Select bi_server1 and click resume.
This should work. Sometimes during new installation the weblogic sever times out from connecting to database. So resuming will do the work. DO NOT FORCE SHUT DOWN
Thanks,
Preet Shah

NodeManager not able to start second managed server in same machine

Hi,
I am facing an issue, I am not able start a second ManagedServer(MG2) using nodemanager (through AdminConsole)
My setup is as below:
Server 1
1) Admin Server + ManagedServer (MG1) (INSTALL LOCATION: /opt/web/MyServer1)
2) Second Managed Server (MG2) (INSTALL LOCATION: /opt/web/MyServer2)
Both belong a same Domain (MyDomain) and NodeManager runs from /opt/web/MyServer1
I can start MG1, but not MG2.
I did
1) nmEnroll for (1) nmEnroll('/opt/web/MyServer1/domains/MyDomain','/opt/web/MyServer1/wlserver_10.3/common/nodemanager')
2) nmEnroll for (2) nmEnroll('/opt/web/MyServer2/domains/MyDomain','/opt/web/MyServer2/wlserver_10.3/common/nodemanager')
I see following error in nodemanager.log,
The domain 'MyDomain' at '/opt/web/MyServer2/domains/MyDomain' was not registered in the nodemanager.domains file and dy
namic domain registration is not supported. Please register the domain in the nodemanager.domains file.
I can start the MG2 if I manually edit nodemanager.domains to point /opt/web/MyServer2/domains/MyDomain.
Is there a way to configure multiple domains locations in nodemanager.domains, so Nodemanger can start managed server installed in different location?

Your nmEnroll shows 2 different domain path values supplied - which means you have told NM to try to connect to 2 different domains
1) nmEnroll for (1) nmEnroll('/opt/web/MyServer1/domains/MyDomain','/opt/web/MyServer1/wlserver_10.3/common/nodemanager')
2) nmEnroll for (2) nmEnroll('/opt/web/MyServer2/domains/MyDomain','/opt/web/MyServer2/wlserver_10.3/common/nodemanager')
You also show 2 distinct node managers you are trying to configure.
nmEnroll enrolls a domain, not an individual server. If you have only 1 installation of nodemanager, and only 1 domain, then you would only need one nmEnroll command.

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.

Start managed server in multihomed machine with cluster?

Similar Messages

Maybe you are looking for