Conflicting managed server names or machine names

Are there any problems if two different domains use the same managed server name? eg. ms1. I am hoping the managed servers are independent of each other.
How about machine names? E.g. two domains refer to app_server_1. However, in this case, I am hoping they refer to the same thing.

I think there is no problem. because weblogic server managed configuration file based on domain. So, a domain doesn't know other domain's configuration including server & machine names.

Similar Messages

How to get managed server name in Weblogic10.2 ?

Hi
I want to get managed server name from a cluster in a servlet or util project class whom that one is called by ?
Do I have to implement any interface or I have to extends a class ? Please help me to resolved.
Thanks

Here is a snippet of code that I use in WL10 MP1 that works fine:
import javax.management.MBeanServer;
import javax.management.ObjectName;
import javax.naming.InitialContext;
String managedServerName = null;
InitialContext ctx = null;
try {
//fetch managed server name by accessing the
//RuntimeServerMBean using the
//MBeanServer interface
ctx = new InitialContext();
MBeanServer server = (MBeanServer) ctx.lookup("java:comp/env/jmx/runtime");
ObjectName service = new ObjectName("com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean");
managedServerName = (String) server.getAttribute(service, "ServerName");
} catch (Exception ex) {
//error occurred
} finally {
if (ctx != null) {
try {
ctx.close();
} catch (Exception dontCare) {

Not able to startup managed server on remote machine -- Please advice

Hi All,
We have one admin server and two managed server in one domain. The admin server and a managed server are in one machine(say machineA) and another managed server is on a different machine(say machineB). I changed the weblogic admin console password and in boot.properties file also. Now when i am restarting the managed server on machineB, i am getting below error message.
<May 12, 2009 12:26:37 PM PDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://123.23.4.56:7071 to retrieve th
e initial configuration.>
<May 12, 2009 12:26:38 PM PDT> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user weblogic star
ting the managed server. The reason for the error is .>
<May 12, 2009 12:26:38 PM PDT> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through UR
L: http://123.23.4.56:7071/wl_management_internal2/Bootstrap, user: weblogic
weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the identity of the user we
blogic starting the managed server. The reason for the error is .
at weblogic.management.ManagedServerAdmin.retrieveMBeansFromAdminServer(ManagedServerAdmin.java:513)
at weblogic.management.ManagedServerAdmin.initialize(ManagedServerAdmin.java:150)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:753)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the iden
tity of the user weblogic starting the managed server. The reason for the error is .'
Reason: weblogic.management.configuration.ConfigurationException: [Configuration Management:150021]The admin server failed to authenticate the identity of the
user weblogic starting the managed server. The reason for the error is .
Kindly help me on this.
Any suggestion is appreciated.
Thanks & Regards,
Raj

Hi Raj,
Which version of weblogic are you using? Try to delete the cache directory of the managed server and try to restart it again and see if the problem goes away.
From Weblogic 9 version onwards by default when Managed server starts for the first time it will read boot.properties file inside domain directory and makes a copy of it inside its cache directory domain/servers/ManagedServername/Security folder. I think boot.properties file inside cache directory of managed server might be using old credentials.
The best way is to delete cache directory of managed server inside domain/servers you will see directory by managed server name, delete it and restart the managed server.
Hope this helps!!
- - Tarun

How to create managed server in remote machine ?

Hi,
I have a cluster. It has 2 managed servers
one managed server runs on machine A
I want to run another managed server on machine B
How do i do that.
I have weblogic installed on both machines A and B
Problem:
a.) how to create domain in machine B ? should i use pack/unpack commands or can i create a new domain from scratch in the machine B ?
Machine A has the domain directory created. Machine A also has admin server
b.) if i create a domian from scratch in machine B, then how does synchroniziation happens ?
say in machine A ( initially where the domain is created ). I add some entries in setDomainenv.sh, how will it reflect in machine B ?
Regards,
Harsha

There are many ways to achieve this, this is one of the method that might help you get started...
http://download.oracle.com/docs/cd/E12839_01/web.1111/e14144/toc.htm
Hope this helps.
.raja

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

Finding out a Managed Server Name/Port

Hi all,
Hope I have the relevant newsgroup....
Does anyone know how I might be able to find out the name of the managed server (or its port) that I am currently running on?
We have a clustered environment (1 admin, 2 managed servers) but I need to get the name of the managed server/port so I can generate some unique information for the server.
I was reading about JMX and it seems I can return a list of ALL servers configured to run on a cluster. It doesn't really help though as I need to find out the specific server details within the cluster.
Any help would really be appreciated.
Cheers,
Jay.

Yes, you can use WLST tool :-
domainConfig()
cmo.getServers()
Link : [http://edocs.bea.com/wls/docs100/config_scripting/monitoring.html]
I hope this helps :)
Edited by: Manish Chellappan on Jul 22, 2009 9:23 PM

LiveCycle rights management server name

In Acrobate, The name of LiveCycle rights management server needs for security. I also wish to know port. Please help

Rights Management is a product that you can purchase from Adobe to be installed and configured in a company's infrastructure. Adobe does not have a public facing Rights Management server that you could connect to.
Also, you only need to configure Acrobat if you are going to apply a policy to a PDF document. If you are trying to open a doccument with a Rights Management policy applied to it, you do not need to configure anything in Reader or Acrobat.
Regards
Steve

How to find manage server name in weblogic server?

I have two managed server in weblogic server. I need to find out which managed server serving my request. Please let me know if any body knows about this.

You do not need to do anything, if your Report server is on the same machine as the Forms server (which is usually the case) you simply use the url as
/reports/rwservlet?report=myreport' and the server will automatically use the default report server.
then you simply use
web.show_document('/reports/rwservlet?userid=scott/tiger@orcl&report=myreport&desformat=htmlcss&desname=test.html'Tony
Try it now
Edited by: Tony Garabedian on Nov 5, 2008 2:00 PM

How to oracle manager server name

for connecting OEM it asking
username
password
oracle manager server
so how can i get this name

hint: read docu "Oracle Enterprise Manager Configuration Guide" (chapter 4)

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

Starting Admin and Managed Server on Same Machine

Has anyone come across a method of running both their admin server and managed
servers as a Service and on the same machine. As you can see, when the OS comes
up both Services for the servers will be started. I can put in a dependency on
the managed server saying that the admin server needs to be started but that doesn't
guarantee that admin server will be ready for "prime time."
I have seen somewhere in a support message something about a "depend" and "delay"
flag for the beasvc.exe program but the one I'm using doesn't seem to support
this.
Here is my setup:
Windows 2000 Pro
Weblogic Server 6.1 SP1
Any assistance is appreciated,
Rich

John Hufnagle wrote:
          > Is it possible to run cluster admin server and one of the managed servers on the
          > same machine...(just preserving machine resources for in-house testing).
          As Kumar said, it is possible to run the admin server and one (or more) managed servers
          on the same machine.
          >
          >
          > If the admin listens on 7001/7002 can I just set up the managed server to 7003/7004
          > or will I also run into problems with the multicast address?
          Since the admin server is not part of the cluster, it is perfectly fine to use a
          different set of ports for the managed servers as long as all servers in the same
          cluster use the same ports...
          Hope this helps,
          Robert

Admin and Managed Server on same machine

          Is it possible to run cluster admin server and one of the managed servers on the
          same machine...(just preserving machine resources for in-house testing).
          If the admin listens on 7001/7002 can I just set up the managed server to 7003/7004
          or will I also run into problems with the multicast address?


John Hufnagle wrote:
          > Is it possible to run cluster admin server and one of the managed servers on the
          > same machine...(just preserving machine resources for in-house testing).
          As Kumar said, it is possible to run the admin server and one (or more) managed servers
          on the same machine.
          >
          >
          > If the admin listens on 7001/7002 can I just set up the managed server to 7003/7004
          > or will I also run into problems with the multicast address?
          Since the admin server is not part of the cluster, it is perfectly fine to use a
          different set of ports for the managed servers as long as all servers in the same
          cluster use the same ports...
          Hope this helps,
          Robert

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.

Conflicting managed server names or machine names

Similar Messages

Maybe you are looking for