Domain Created: Failed Restarting Managed Servers in a cluster
Hi,
I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
Admin Server - adminServer - 1.1.1.19 - on port 7001
Managed servers - machines:ip's - port
1. mgndServer1 - 1.1.1.19 - 7011
2. mgndServer2 - 1.1.1.20 - 7011
mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
node manager ; - 1.1.1.19 - 5555
In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
Log :
<Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
<Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
<Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
<Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
<Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
Please help me in understand what went wrong here ? can anyone quickly guide me ..
thanks
patrick
Hi Revanth,
The issue seems to be with the JMX URL value defined in the 'server URL' property.
Apparently I ran into the same issue as I was unable to access the Admin Server URL from the SMA.
Changing the Host and Port value properly resolved the issue for me.
Regards,
Anandraj
Similar Messages
-
Not able to restart managed servers after password change in console
im doin the following steps,am i doin anything wrong?
1)shutdown all managed servers
2)change pwd in admin console
3)edit boot.properties file with new pwd in admin server
4)copy these boot file to every managed server
5)now restart admin server.(able to do it succesfully)
6)not able to restart managed servers (im getting the following error.
Can any help me out plz very urgent?
<Critical> <WebLogicServer> <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)
Truncated. see log file for complete stacktrace
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>Hi,
*1)In order to export the user data on to the server,do we have to create a specific directory to save this data into the server.*
Yes ....you can give any Existing Directory Path in the AdminConsole Export Page.... Any Directory in your File System.
*2)Is there any other way by not exporting or importing the data?*
That is the only way to prevent the Data Loss....There are some other ways to do it without using Admin Console like Using WLST or Using JMX you can export the Data but all these techniques will exactly do the same thing ... The AdminConsole is the easiest way to do it.
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic/ (Middleware Magic Is Here) -
Deployment failed: No managed servers to service request: how to recover
I am unable to deploy applications, instead get error:
2013-05-14 05:27:53 CDT: Starting action "Deploy Application"
2013-05-14 05:27:53 CDT: Deploy Application started
2013-05-14 05:27:53 CDT: Deployment failed: No managed servers to service request
2013-05-14 05:27:53 CDT: Application deployment failed.
2013-05-14 05:27:53 CDT: "Deploy Application" complete: status FAILED
The error occurs both from Jdeveloper and UI deployment. Is there a way to recover from this ? This did work earlier today..I am experiencing the same stuck job on my java cloud instance - can Oracle support reset my job
If I try to start/stop/redeploy or add an application I get the following error
"Information
The operation cannot be invoked because the service is running Java Cloud Service Job 170371. Wait for the job to complete, then re-run the operation."
https://forums.oracle.com/thread/2548962
https://forums.oracle.com/thread/2501942?tstart=30
thank you
/michael -
Error while starting managed servers in a cluster
Hi,
I have Weblogic 8.1.3 deployed on my system. We've have a Ant script that set's up the project domain etc. We have an admin server and two other managed servers which are part of a cluster. I am able to start the admin server and access the admin console without any errors. However when I start any of the managed servers in the cluster, using the following command (startManagedWebLogic.cmd Reactor-1 http://localhost:80 OR startManagedWebLogic.cmd Reactor-2 http://localhost:80)
I get the error listed below. The same Ant script was used to setup the project on another system and it worked but I haven't been able to set it up on my system.
The error says that it could be due to servers having duplicate names in the cluster but thats not the case here, the managed servers are named Reactor-1 and 2.
Also, the IP address being accessed, 192.168.141.50:81 is not my system, its another system on the network. I've done a full text search for the IP address but I've not been able to find it in ANY file under c:\bea.
Can someone please tell me if I've missed something? I'd appreciated any help with this.
Thanks
Ameeth
<Mar 21, 2005 4:52:43 PM GMT+05:30> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server Reactor-1
.>
<Mar 21, 2005 4:52:44 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 81.>
<Mar 21, 2005 4:52:44 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
r HTTP from Reactor-1.
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '81'
at weblogic.net.http.HttpClient.openServer(Ljava.lang.String;I)V(HttpClient.java:275)
at weblogic.net.http.HttpClient.openServer()V(HttpClient.java:329)
at weblogic.net.http.HttpClient.<init>(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSoc
ketFactory;I)V(HttpClient.java:128)
at weblogic.net.http.HttpClient.New(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSocket
Factory;I)Lweblogic.net.http.HttpClient;(HttpClient.java:196)
at weblogic.net.http.HttpURLConnection.connect()V(HttpURLConnection.java:119)
at weblogic.cluster.MemberManager.waitForSync(J)V(MemberManager.java:213)
at weblogic.cluster.MemberManager.waitToSyncWithCurrentMembers()V(MemberManager.java:160)
at weblogic.cluster.ClusterCommunicationService.initialize()V(ClusterCommunicationService.java:58)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:924)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String)V(Server.java:32)
>
<Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdenti
ty from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias D
emoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Mar 21, 2005 4:52:47 PM GMT+05:30> <Warning> <WebLogicServer> <BEA-000311> <Attempting to use low strength (exportable) certif
icates with a full strength (domestic) license.>
<Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
:\bea\JROCKI~1\jre\lib\security\cacerts.>
<Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port
7002, ip address 127.0.0.1>
<Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 81,
ip address 127.0.0.1>
<Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <Cluster> <BEA-000102> <Joining cluster ReactorCluster on 237.0.0.1:7001>
<Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "Reactor-1" for dom
ain "ReactorAdminServer" running in Development Mode>
<Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 21, 2005 4:52:51 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 82.>
<Mar 21, 2005 4:52:52 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
r HTTP from 8288749592481618145S:localhost:[81,81,-1,-1,81,-1,-1,0,0]:192.168.141.50:81,192.168.141.50:82:ReactorAdminServer:Re
actor-1.
java.io.IOException: Reference to server no longer exists.
Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuratio
n for this error.
at weblogic.rmi.cluster.ServerInfoManager.updateServerInfo(Lweblogic.rmi.cluster.ServerInfo)V(ServerInfoManager.java:1
11)
at weblogic.rmi.cluster.ServerInfoManager.readUpdate(Ljava.lang.Object)V(ServerInfoManager.java:95)
at weblogic.cluster.MemberAttributes.readExternal(Ljava.io.ObjectInput)V(MemberAttributes.java:103)
at java.io.ObjectInputStream.readExternalData(Ljava.io.Externalizable;Ljava.io.ObjectStreamClass)V(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
at weblogic.cluster.HTTPExecuteRequest.execute(Lweblogic.kernel.ExecuteThread)V(HTTPExecuteRequest.java:91)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread)V(Unknown Source)make sure you use a unique cluster multicast ip address. are you sure that your etc/hosts file has proper entries for localhost?
-
Status of managed servers in a cluster
i have an environment with multiple clusters . I want to deploy code using WLST to a specific cluster. Before deploying i want to check if the managed servers in that cluster are running ...
how to check only managed servers in a specific cluster ... and not all managed servers in that domain ..
connect("weblogic","xyz",admin:port)
deploy ("abc","xyz.war","mycluster")
where mycluster has 2 managed servers. My domain has several clusters
thanksimport sys
import time
url = sys.argv[ 1 ]
username = sys.argv[ 2 ]
password = sys.argv[ 3 ]
try:
connect( username, password, url )
except WLSTException:
print 'Administration server not running.'
exit()
print 'Shutting down servers for domain at url ' + url + '...'
adminServer = cmo.getAdminServerName()
cd( 'Servers' )
servers = cmo.getServers()
domainRuntime()
for s in servers:
serverName = s.getName()
if serverName != adminServer:
try:
serverRuntime = getMBean( '/ServerRuntimes/' + serverName )
serverState = serverRuntime.getState()
if serverState == 'RUNNING':
shutdown( name = serverName, entityType = 'Server', force = 'true', block = 'true', timeOut = 60000 )
print 'Server ' + serverName + ' shut down.'
except AttributeError:
print 'Server ' + serverName + ' is not currently running.'
continue
try:
shutdown( name = adminServer, entityType = 'Server', force = 'true', block = 'false', timeOut = 60000)
except WLSTException:
print 'WARNING: Error occurred while attempting to shut down server ' + adminServer + ' .'
print 'Server ' + adminServer + ' shutting down.'
exit() -
What should be the client url for managed servers in a cluster
Hi guys,
I have created a cluster(cluster_1) having 4 managed servers. 2 managed servers on my machine(IP1) and 2 managed servers on other machine(IP2).
I am able to deploy a xxx.war file on my admin server
also
I am able to deploy the same war file on my cluster
When I try to hit the client url, it gives me back the correct data, but it creates the session on the admin server and not the cluster.
If I remove the xxx.war file from the deployment(deployed on admin server) and redeploy the xxx,war file on the cluster, it gets deployed successfully , but the client url gives me a 404 error.
What should I do, so that after hitting the client url, it creates the session on the managed servers in the cluster ?
My admin server is not the part of this cluster.
cluster ip:127.0.0.1
ip1: 10.25.63.130
ip2: 10.25.63.131
please help
SalilHi Salil
This is exactly what I mentioned in my earlier post. You CANNOT and should NOT expose the managed server url (host, port) to the end users. Because as you already figured out, you can specify only one. Or they cannot try one at a time like that.
This is where, the Load Balancer will come into picture like Apache Web Server. After installing Apache web server, usually it runs at default port 80. So you just expose the apache host to outside world. Also most companies will have Firewalls and Apache is outside of Firewall and all weblogic servers are inside the Firewall. In apache, you configure the weblogic cluster details like the host names and ports of each managed server etc in httpd.conf file etc.
Ex: For outside users, they may try like http://apachehost/myWeb/myHello.jsp -> apachehost is the host name where Apache web server is running at port 80. NOW Apache is smart enough to do Load Balancing and Failover. If 100 users access the site with 4 managed servers, ideally each managed server will get 25 requests (load balancing). Also if 2 servers are killed, automatically, request will NOT go to them, but to other 2 live servers etc etc. Apache takes care of this.
Bottom line, please see my earlier post, and you need to have some sort of Web Server like Apache for your cluster setup.
Thanks
Ravi Jegga -
Error : Running Managed Servers in a cluster
Hi,
I tried creating a new domain from my local pc - by using the configuration wizard provided by weblogic.. the configuration used is like this -
Admin Server - adminServer - 1.1.1.19 - on port 7001
Managed servers - machines:ip's - port
1. mgndServer1 - 1.1.1.19 - 7011
2. mgndServer2 - 1.1.1.20 - 7011
mgndCluster defined as - mgndServer1:7011, mgndServer2:7011
node manager ; - 1.1.1.19 - 5555
In the last step i didnt check ( select box ) the WLI Start up , WLI Shutdown classes for the managed cluster , but Set the WLI Start up , shut down classes for admin server.
Started the admin server and from the admin console, state of the node manager was running , I tried starting the managed servers, but it failed with the below error - and managed servers never come into running state..
Log :
<Jan 29, 2010 10:36:26 AM CET> <Info> <NodeManager@*.*:5555> <Starting Server adminServer ::mgndServer1 ...>
<Jan 29, 2010 10:36:26 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.19:7001 to check if there exists a running admin server at this URL.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 29, 2010 10:36:26 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 29, 2010 10:36:26 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.19:7001 to retrieve the initial configuration.>
<Jan 29, 2010 10:36:27 AM CET> <Info> <NodeManager@*.*:5555> <Server myDomain::mgndServer1 started, process id = 6,888>
<Jan 29, 2010 10:36:28 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\mgndServer2\mgndServer2.log is opened. All server side log events will be written to this file.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 29, 2010 10:36:29 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 29, 2010 10:36:30 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "mgndServer1" for domain "myDomain">
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster mgndCluster on 237.0.0.13:7011.>
<Jan 29, 2010 10:36:57 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of mgndCluster.>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.0000.tlog].>
<Jan 29, 2010 10:37:27 AM CET> <Notice> <JTA> <BEA-110025> <Creating new transaction log file [.\mgndServer1\./mgndServer1.heur.0000.tlog].>
<Jan 29, 2010 10:37:35 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI Worklist due to error weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean].
java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:480)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:182)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:224)
at weblogic.ejb20.deployer.EJBModule.setupEJBToImplClassDependencies(EJBModule.java:1030)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:481)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.ManagementException: [Deployer:149233]An unexpected error was encountered during the deployment process. - with nested exception:
[java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/SLSBContainerBean]
at weblogic.management.deploy.slave.SlaveDeployer.convertThrowable(SlaveDeployer.java:1017)
at weblogic.management.deploy.slave.SlaveDeployer.access$500(SlaveDeployer.java:124)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3034)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
<Jan 29, 2010 10:37:38 AM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application WLI System EJBs due to error weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for WLI Process Tracking
Module Name: WLI Process Tracking, Error: Exception preparing module: EJBModule(WLI Process Tracking,status=NEW)
Unable to deploy EJB: .\mgndServer2\stage\WLI System EJBs\tracking from tracking:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.bea.wli.management.tracking.ProcessTrackingBean
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:550)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1604)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:823)
at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3026)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:967)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:349)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>
Please help me in understand what went wrong here ? can anyone quickly guide me ..
thanks
patrickHi,
<font color=red>OPTION-A)</font>
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
<font color=red>OPTION-B)</font>
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 10:55 PM -
How to install Window service for Managed Servers of a Cluster
Dear All,
I am preparing a production setup consist of three machines A,B and C. Machines A is the Admin Server which hosts a cluster consist of two managed nodes. I intend to schedule both these nodes, targeted to two different machines (machines B node-b and machine C host node-c), as startup task on daily basis. I have no Node Manager running on machine A, but on machine B and machine C.
I am only interested to schedule started task for node-b and node-c only. I need to know how to install the Windows services for the node-b and node-c since there are targeted on remote machines. Starting managed server as Win sevice works in the case of standalone managed servers but not sure when it comes to cluster setup.I appreciate if you can throw some light on this question.
Thanks
KrisKrish,
>Let say I gracefully shutdown both managed servers while >Admin is running. Do you think both these nodes while be >brought up ? I dont think they will come up.
If you require an automatic restart when the managed server did not enter a failed state you can use the weblogic.Admin utility to ping the servers and kick off a server startup in the normal way with nodemanger see:
http://e-docs.bea.com/wls/docs81/admin_ref/cli.html
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html
If your servers entered a failed state you can use weblogics self health monitoring.
>Can we use JMX MBean to start managed servers ?
Yes.
As long as the nodemanagers are running you can start the managed servers using scripted commands using the weblogic.Admin class or your own java app using JMX.
I think you may also be able to use WLST
http://dev.bea.com/codelibrary/code/wlst.jsp
hope this helps
cheers
Please see the
Hussein Badakhchani
www.orbism.com -
Concurrent startup managed servers in a cluster
I'm using WLS 6.1 sp3 on Solaris 8. I configured 24 instances in a cluster.
I tried to startup all managed servers at the same time. Some of the
instance failed. Due to the WLS startup time (half hour to start an instance
cause we have many ejbs), I didn't try to start servers one by one. Here is
the log file I got from one of the failed servers. Any help will be
appreciated.
Thanks!
Wenji
/bea/jdk131/bin/java -server -ms512m -mx512m -XX:NewSize=128m -XX:MaxNewSize
=128m -verbosegc -classpath
.:/appdata/wls/cbfe1b/config/prod/properties:/appdata/wls/cbfe1b/config/prod
/properties/srv34:/oracle/product/8.1.7/jdbc/lib/classes12.zip:/appdata/wls/
cbfe1b/config/prod/lib/externalAPIs/iioprt.jar:/appdata/wls/cbfe1b/config/pr
od/lib/externalAPIs/xerces.jar:/appdata/wls/cbfe1b/config/prod/lib/externalA
PIs/jdom.jar:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/log4j-1.2.5.ja
r:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/xalan.jar:/oracle/product
/8.1.7/jdbc/lib/nls_charset12.zip:/bea/wlserver6.1:/bea/wlserver6.1/lib/webl
ogic.jar:/appdata/wls/cbfe1b/config/prod/classes:/appdata/wls/cbfe1b/config/
prod/lib/eontec/eontec_custom_user_realm.jar:/appdata/wls/cbfe1b/config/prod
/lib/ibm/mqccf.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/ccf.jar:/appdata/
wls/cbfe1b/config/prod/lib/ibm/eablib.jar:/appdata/wls/cbfe1b/config/prod/li
b/ibm/imsconn.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/recjava.jar -Dwebl
ogic.Domain=prod -Dweblogic.Name=prod-srv34 -Dbea.home=/bea -Dweblogic.manag
ement.server=milkyway:8100 -Djava.security.policy=/bea/wlserver6.1/lib/weblo
gic.policy -Dweblogic.management.password=eontec00 -Dweblogic.RootDirectory=
/appdata/wls/cbfe1b weblogic.Server
Starting WebLogic Server ....
MBean Info preloading problem:
java.lang.NullPointerException
at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
at
weblogic.management.tools.AttributeInfo.readObject(AttributeInfo.java:151)
at java.lang.reflect.Method.invoke(Native Method)
at
java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2209)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1406)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1137)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2258)
at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
at weblogic.management.internal.Helper.getMBeanInfo(Helper.java:205)
at weblogic.management.internal.Helper.preloadMBeanInfos(Helper.java:232)
at weblogic.management.Admin.initialize(Admin.java:226)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
at weblogic.Server.main(Server.java:35)
Connecting to http://milkyway:8100...
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NullPointerException
<<no stack trace available>>
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: connecting to
http://milkyway:8100/wl_management_internal2/Bootstrap - with nested
exception:
[java.lang.NullPointerException]
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1164)
at weblogic.management.Admin.initialize(Admin.java:340)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Admin server is not a member of a cluster.
Wenji
Wenji Tong wrote:
> I'm using WLS 6.1 sp3 on Solaris 8. I configured 24 instances in a cluster.
> I tried to startup all managed servers at the same time. Some of the
> instance failed. Due to the WLS startup time (half hour to start an instance
> cause we have many ejbs), I didn't try to start servers one by one. Here is
> the log file I got from one of the failed servers. Any help will be
> appreciated.
>
> Thanks!
> Wenji
>
>
>
> /bea/jdk131/bin/java -server -ms512m -mx512m -XX:NewSize=128m -XX:MaxNewSize
> =128m -verbosegc -classpath
> .:/appdata/wls/cbfe1b/config/prod/properties:/appdata/wls/cbfe1b/config/prod
> /properties/srv34:/oracle/product/8.1.7/jdbc/lib/classes12.zip:/appdata/wls/
> cbfe1b/config/prod/lib/externalAPIs/iioprt.jar:/appdata/wls/cbfe1b/config/pr
> od/lib/externalAPIs/xerces.jar:/appdata/wls/cbfe1b/config/prod/lib/externalA
> PIs/jdom.jar:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/log4j-1.2.5.ja
> r:/appdata/wls/cbfe1b/config/prod/lib/externalAPIs/xalan.jar:/oracle/product
> /8.1.7/jdbc/lib/nls_charset12.zip:/bea/wlserver6.1:/bea/wlserver6.1/lib/webl
> ogic.jar:/appdata/wls/cbfe1b/config/prod/classes:/appdata/wls/cbfe1b/config/
> prod/lib/eontec/eontec_custom_user_realm.jar:/appdata/wls/cbfe1b/config/prod
> /lib/ibm/mqccf.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/ccf.jar:/appdata/
> wls/cbfe1b/config/prod/lib/ibm/eablib.jar:/appdata/wls/cbfe1b/config/prod/li
> b/ibm/imsconn.jar:/appdata/wls/cbfe1b/config/prod/lib/ibm/recjava.jar -Dwebl
> ogic.Domain=prod -Dweblogic.Name=prod-srv34 -Dbea.home=/bea -Dweblogic.manag
> ement.server=milkyway:8100 -Djava.security.policy=/bea/wlserver6.1/lib/weblo
> gic.policy -Dweblogic.management.password=eontec00 -Dweblogic.RootDirectory=
> /appdata/wls/cbfe1b weblogic.Server
> Starting WebLogic Server ....
> MBean Info preloading problem:
> java.lang.NullPointerException
> at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2266)
> at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
> at
> weblogic.management.tools.AttributeInfo.readObject(AttributeInfo.java:151)
> at java.lang.reflect.Method.invoke(Native Method)
> at
> java.io.ObjectInputStream.invokeObjectReader(ObjectInputStream.java:2209)
> at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1406)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
> at java.io.ObjectInputStream.inputArray(ObjectInputStream.java:1137)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
> at java.io.ObjectInputStream.inputClassFields(ObjectInputStream.java:2258)
> at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:514)
> at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1407)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:381)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:231)
> at weblogic.management.internal.Helper.getMBeanInfo(Helper.java:205)
> at weblogic.management.internal.Helper.preloadMBeanInfos(Helper.java:232)
> at weblogic.management.Admin.initialize(Admin.java:226)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
> at weblogic.Server.main(Server.java:35)
> Connecting to http://milkyway:8100...
> ***************************************************************************
> The WebLogic Server did not start up properly.
> Exception raised:
> java.lang.NullPointerException
> <<no stack trace available>>
> --------------- nested within: ------------------
> weblogic.management.configuration.ConfigurationException: connecting to
> http://milkyway:8100/wl_management_internal2/Bootstrap - with nested
> exception:
> [java.lang.NullPointerException]
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1164)
> at weblogic.management.Admin.initialize(Admin.java:340)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
> ***************************************************************************
>
>
>
-
Problems with deploying file to one of the managed servers on a cluster
We are running Weblogic 10.3.
When I start both managed servers from the Admin Console, one fails with the error below and in Admin state, but the other managed server starts up correctly.
The only difference from when it was first working is that the managed server ServerBox1 was imaged and loaded onto new hardware and all network/os properties configured the same as the old box.
####<Timestamp> <Info> <Deployer> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292425> <BEA-149059> <Module DocFile.war of application DocFile is transitioning from STATE_NEW to STATE_PREPARED on server ServerBox1.>
####<Mar 29, 2012 3:11:32 PM EDT> <Error> <HTTP> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292488> <BEA-101064> <[WebAppModule(DocFile:DocFile.war)] Error parsing descriptor in Web appplication "/domainPath/servers/ServerBox1/stage/DocFile/DocFile.war"
java.lang.NullPointerException
at com.bea.xbean.regex.RangeToken.match(RangeToken.java:485)
at com.bea.xbean.regex.RegularExpression.matchString(RegularExpression.java:1673)
at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1432)
at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1370)
at com.bea.xbean.schema.SchemaTypeImpl.matchPatternFacet(SchemaTypeImpl.java:1362)
at com.bea.xbean.values.JavaDecimalHolderEx.validateLexical(JavaDecimalHolderEx.java:71)
at com.bea.xbean.validator.Validator.validateAtomicType(Validator.java:1296)
at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1259)
at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1195)
at com.bea.xbean.validator.Validator.handleText(Validator.java:835)
at com.bea.xbean.validator.Validator.textEvent(Validator.java:820)
at com.bea.xbean.validator.Validator.nextEvent(Validator.java:250)
at com.bea.xbean.validator.ValidatingXMLStreamReader.validate_event(ValidatingXMLStreamReader.java:654)
at com.bea.xbean.validator.ValidatingXMLStreamReader.next(ValidatingXMLStreamReader.java:544)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl.next(XMLStreamReaderExtImpl.java:1122)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.fillBuffer(XMLStreamReaderExtImpl.java:804)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.reload(XMLStreamReaderExtImpl.java:755)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getBigIntegerValue(XMLStreamReaderExtImpl.java:155)
at com.bea.staxb.runtime.internal.UnmarshalResult.getBigIntegerValue(UnmarshalResult.java:467)
at com.bea.staxb.runtime.internal.IntegerToIntTypeConverter.getObject(IntegerToIntTypeConverter.java:34)
at com.bea.staxb.runtime.internal.BaseSimpleTypeConverter.unmarshal(BaseSimpleTypeConverter.java:39)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:167)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:164)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:159)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1193)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:350)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
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)
>
####<Timestamp> <Info> <Deployer> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292506> <BEA-149061> <Module DocFile.war of application DocFile failed to transition from STATE_NEW to STATE_PREPARED on server ServerBox1.>
####<Mar 29, 2012 3:11:32 PM EDT> <Error> <Deployer> <box1> <ServerBox1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1333048292727> <BEA-149205> <Failed to initialize the application 'DocFile' due to error weblogic.application.ModuleException: [HTTP:101064][WebAppModule(DocFile:DocFile.war)] Error parsing descriptor in Web appplication "/domainPath/servers/ServerBox1/stage/DocFile/DocFile.war"
java.lang.NullPointerException
at com.bea.xbean.regex.RangeToken.match(RangeToken.java:485)
at com.bea.xbean.regex.RegularExpression.matchString(RegularExpression.java:1673)
at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1432)
at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1370)
at com.bea.xbean.schema.SchemaTypeImpl.matchPatternFacet(SchemaTypeImpl.java:1362)
at com.bea.xbean.values.JavaDecimalHolderEx.validateLexical(JavaDecimalHolderEx.java:71)
at com.bea.xbean.validator.Validator.validateAtomicType(Validator.java:1296)
at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1259)
at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1195)
at com.bea.xbean.validator.Validator.handleText(Validator.java:835)
at com.bea.xbean.validator.Validator.textEvent(Validator.java:820)
at com.bea.xbean.validator.Validator.nextEvent(Validator.java:250)
at com.bea.xbean.validator.ValidatingXMLStreamReader.validate_event(ValidatingXMLStreamReader.java:654)
at com.bea.xbean.validator.ValidatingXMLStreamReader.next(ValidatingXMLStreamReader.java:544)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl.next(XMLStreamReaderExtImpl.java:1122)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.fillBuffer(XMLStreamReaderExtImpl.java:804)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.reload(XMLStreamReaderExtImpl.java:755)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getBigIntegerValue(XMLStreamReaderExtImpl.java:155)
at com.bea.staxb.runtime.internal.UnmarshalResult.getBigIntegerValue(UnmarshalResult.java:467)
at com.bea.staxb.runtime.internal.IntegerToIntTypeConverter.getObject(IntegerToIntTypeConverter.java:34)
at com.bea.staxb.runtime.internal.BaseSimpleTypeConverter.unmarshal(BaseSimpleTypeConverter.java:39)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:167)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:164)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:159)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1193)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:350)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
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)
null.
weblogic.application.ModuleException: [HTTP:101064][WebAppModule(DocFile:DocFile.war)] Error parsing descriptor in Web appplication "/domainPath/servers/ServerBox1/stage/DocFile/DocFile.war"
java.lang.NullPointerException
at com.bea.xbean.regex.RangeToken.match(RangeToken.java:485)
at com.bea.xbean.regex.RegularExpression.matchString(RegularExpression.java:1673)
at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1432)
at com.bea.xbean.regex.RegularExpression.matches(RegularExpression.java:1370)
at com.bea.xbean.schema.SchemaTypeImpl.matchPatternFacet(SchemaTypeImpl.java:1362)
at com.bea.xbean.values.JavaDecimalHolderEx.validateLexical(JavaDecimalHolderEx.java:71)
at com.bea.xbean.validator.Validator.validateAtomicType(Validator.java:1296)
at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1259)
at com.bea.xbean.validator.Validator.validateSimpleType(Validator.java:1195)
at com.bea.xbean.validator.Validator.handleText(Validator.java:835)
at com.bea.xbean.validator.Validator.textEvent(Validator.java:820)
at com.bea.xbean.validator.Validator.nextEvent(Validator.java:250)
at com.bea.xbean.validator.ValidatingXMLStreamReader.validate_event(ValidatingXMLStreamReader.java:654)
at com.bea.xbean.validator.ValidatingXMLStreamReader.next(ValidatingXMLStreamReader.java:544)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl.next(XMLStreamReaderExtImpl.java:1122)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.fillBuffer(XMLStreamReaderExtImpl.java:804)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl$CharSeqTrimWS.reload(XMLStreamReaderExtImpl.java:755)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getBigIntegerValue(XMLStreamReaderExtImpl.java:155)
at com.bea.staxb.runtime.internal.UnmarshalResult.getBigIntegerValue(UnmarshalResult.java:467)
at com.bea.staxb.runtime.internal.IntegerToIntTypeConverter.getObject(IntegerToIntTypeConverter.java:34)
at com.bea.staxb.runtime.internal.BaseSimpleTypeConverter.unmarshal(BaseSimpleTypeConverter.java:39)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:167)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:164)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:136)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:159)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1193)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:350)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
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)
null
I also noticed that the DocFile directory inside the stage directory is deleted once the ServerBox1 is started completely.
Thanks for the assistance.Hi Partha. Did you get a solution to your problem with high connection delay times on your server? I'm having a similar problem and saw your post.
Thanks,
Mark -
Limit on number of Managed Servers in a cluster
Hi All,
Do you know if there is any limit on number of managed servers I can have in a
cluster.
If there is a limit then how many?
If not, is there a recommended limit from BEA?
We are using Weblogic 6.1 SP2 and we have 16 managed servers running in the cluster.
Under heavy load (through put about 600-800) the console is not responding fast.
Also when we try to monitor the Weblogic Servers from the console under Monitoring->performance
, the screen is not getting refreshed faster(which makes me think the monitoring
info I see on the console is not completely correct).
I have a heap size of 96m for admin and 768m for Managed Servers.
Did anyone see this problem before.
Are there any command line arguments that I can add to make my console respond
faster?
If not, do we have any patch from BEA that makes console work faster?
Please suggest.
Thanks for your attention,
Kiran
Hi Vineet,
In Latest version of SAP MDM which is 7.1 we have the liberty to use multiple Main tables so answer to your question is yes we can use 20-30 main tables, now the question is that what type of data model you are prepairing this question is just to understand your entire structure and may be suggest some thing at higher level on which you can think and then take corrective action as per your thoughts.
Generally even if you are integrating Customer/Products in single repository and then designing the main table you wont have to prepare such huge number of main tables you can have these two main tables and then rest of then as sub tables and refer it to each other also you need to know what imapct it will have on system performance becuase they would be referring to each other and also if you are creating some thousands of records in each repository then it is more advisable to use limited number of main tables and use MDM to it's fullest capability by designing such model that we have best utlisation of server performance.
Hope it helped a bit.
Let me know if you need any further information on same.
Thanks and Regards
Praful. -
Creating new Managed Servers on remote machines
Hi,
We have a multi-machine domain already in place. Nodemanager is configured and we're using the architecture suggested in Oracle SOA Enterprise Deployment Guide, where we have one domain home for the AdminServer and one domain home for the Managed servers. Right now what we need to know is how to add new managed servers in the easiest and fastest way possible on the mserver home on both the adminserver local machine and on the remote machine, this is a development environment and we need to be able to quickly create and delete these servers for developers to work.
We know that the standard way of doing it is doing a pack (for the managed servers only), and then an unpack on the mserver home both on local and remote machine after changing the root directory of these servers to match those homes. Here is were we have our first doubts. Do the unpack command command has to be run with the already running servers down? Does this pack and unpack process affects what we already have deployed on the running managed servers? And last but not least, is there any way to automate this process? Because we need to give the developers the ability to create clusters on the environment through the admin server console, but without giving them access to the underlying operating system.
If this seems like a newbie question is because we are, we're just in the process of migrating oas 10g to weblogic 11g and there are tons of basic administration stuff that seem pretty strange for us, we've looked through the Oracle manuals and metalink but even though some show you how to create the domain with remote managed servers for the first time, we couldn't find any mention on how to add the mserver efficiently after that.
Thanks!Cris,
Thanks again for your help, we're trying to figure out how to present this procedure to our customer, just one thought though, we were thinking about moving away from the architecture presented by de SOA Enterprise Deployment guide, and using a single domain home located on the shared storage, that way we could create the managed servers from the admin console without having to use pack/unpack and deciding where to run the servers just by configuring machines and nodemanager. However, we haven't seen this kind of configuration anywhere on Oracle manuals, is there any other problem you are aware of in this idea? We're using a storage with multipath for the shared disk so we're not very concerned about availability (and if the storage went down the weblogic domain would be the least of our problems).
Regards, Franco. -
Problem in running Managed Servers
Hi,
I used the configuration wizard and tried creating a domain ( admin server , 2 managed servers ('new_Server_1' , 'new_Server_2' )) . Admin server listens to the port 7003.
Set up details :
Managed Servers - IP's - Port
new_Server_1 - 1.1.1.10 - 7011
new_Server_2 - 1.1.1.11 - 7011
Node Manager - 1.1.1.10 - 5555
I login into the admin console after the whole set up, node manager was running , admin server wa s running and tried starting the managed servers ,But they failed to start giving the error message -
<Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.10:7003 to check if there exists a running admin server at this URL.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.10:7003 to retrieve the initial configuration.>
<Jan 9, 2010 11:29:58 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\new_Server_1\new_Server_1.log is opened. All server side log events will be written to this file.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "new_Server_1" for domain "integration">
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster new_Cluster on 237.0.0.1:7011.>
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of new_Cluster.>
<Jan 9, 2010 11:30:36 AM CET> <Error> <Deployer> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
<Jan 9, 2010 11:30:36 AM CET> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup>
The WebLogic Server did not start up properly.
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
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:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Reason: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
Is this due to the WLI Start up classes set to both admin and managed servers caused this problem / jars missed out while creating a domain ,, ? any pointers to solve this issue.
thank you in advance.
colonelHi,
<font color=red>OPTION-A)</font>
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
<font color=red>OPTION-B)</font>
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 6:42 PM
Edited by: Jay SenSharma on Jan 30, 2010 10:57 PM -
How to start managed servers in parallel?
Hello everyone,
I am developing a wlst script that would start all managed servers on a particular machine (machine_name should be provided) from the admin server side. The script works fine. However, since there were some domains that have 25+ managed servers for a single machine, it takes some time to start all of them in sequence. Is there a way to trigger a start command for each of the managed servers that I need to start just like what the node manager does when i start them through admin console? Something like triggering parallel processes running on background. Here is my code snippet:
#It focuses only on all managed servers defined within the listen address provided
if (server_listenaddress == managed_server) and (server_name != admin_name):
if (execute_command == "start"):
print 'About to start',server_name,'on',server_listenaddress,'...'
print
try:
start(server_name)
print
state(server_name,'Server')
print
nmDisconnect()
except WLSTException:
print 'Server instance',server_name,'could not be started. Skipping this server..'
print
state(server_name,'Server')
else:
print 'About to stop',server_name,'on',server_listenaddress,'...'
print
try:
shutdown(server_name,force='true')
print
state(server_name,'Server')
print
except WLSTException:
print 'Server instance',server_name,'could not be stopped. Skipping this server..'
print
state(server_name,'Server')
elif (server_name == admin_name):
#It skips to restart the admin server since this script it only to restart managed servers.
print 'Server',server_name,'is the admin server. Skipping...'
print
else:
print 'Managed server',server_name,'is not configured with',managed_server,'listen address. Skipping this server..'
Thanks in advance for all your help!!
regards,
RustanWorks perfectly, thanks!!!
In summary, I just modified this line:
start(server_name)
and changed it to:
start(server_name, block='false')
In Admin Console, it is set to false but in WLST, it is defaulted to true so we need to explicitly set it to false.
"Oracle Fusion Middleware Oracle WebLogic Scripting Tool, block is always set to true." -
Use Admin Server to Manage multiple managed servers through Nodemanager
hi guys,
Iam trying to simulate the production environment for a Weblogic based application.
I want to use one Admin Server(adminServer) to control 2 managed servers(weblogic,Bizarro).
adminServer & weblogic sit on windows machine (prod1) and Bizarro sits on OakStage(unix
machine).
I have nodeManagers running on both machines. They were started using the default
start scripts that were provided.
I can sucessfully start&stop instance weblogic (the instance that resides on the
same machine as adminServer). When I try to start Bizarro i get the following
error in the console
<Oct 18, 2002 7:59:22 AM PDT> <Error> <NodeManager> <Could not start server 'Bizarro'
via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to
the NodeManager running on host '192.168.0.97:5555' to execute command 'online
Bizarro', reason: Operation timed out: connect. Ensure that the NodeManager on
host '192.168.0.97' is configured to listen on port '5555' and that it is actively
listening]'>
but iam sure node manager is running on port 5555 on that box.
Here is my config.xml file. Is there something Iam missing?
I have also modified the hosts file to only have the ip address of the admin server.
<?xml version="1.0" encoding="UTF-8"?>
<!--If your domain is active, please do not edit the config.xml file. Any changes
made to that file while the domain is active will not have any effect on the domain's
configuration and are likely to be lost. If your domain is inactive, you may edit
this file with an XML editor. If you do so, please refer to the BEA Weblogic Server
Configuration Reference documentation available from http://edocs.bea.com/wls/docs61/reference.html.
In general, we recommend that changes to your configuration file be made through
the Administration Console.-->
<Domain Name="adminDomain">
<Security Name="adminDomain" PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<FileRealm Name="wl_default_file_realm"/>
<StartupClass ClassName="com.ias.hub.weblogic.WeblogicStartup" Name="hubStartup"
Targets="weblogic"/>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
o=beasys.com;server.principal=uid=admin, ou=Administrators, ou=TopologyManagement,
o=NetscapeRoot;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
o=beasys.com" Name="defaultLDAPRealmForNetscapeDirectoryServer" Notes="This is
provided as an example. Before enabling this Realm, you must edit the configuration
parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<Server ListenPort="9000" Machine="Prod1" Name="weblogic" StdoutDebugEnabled="true"
StdoutSeverityLevel="64">
<ServerStart ClassPath="my correct claspath" Name="weblogic" OutputFile="weblogic.log"/>
<SSL ListenPort="9001" Name="weblogic"/>
<ServerDebug Name="weblogic"/>
<KernelDebug Name="weblogic"/>
<Log FileName="weblogic.log" Name="weblogic"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<WebServer LogFileName="./config/adminDomain/logs/access.log" LoggingEnabled="true"
Name="weblogic"/>
</Server>
<JDBCConnectionPool CapacityIncrement="2" DriverName="weblogic.jdbc.oci.Driver"
InitialCapacity="15" LoginDelaySeconds="1" MaxCapacity="15" Name="IasPool" Properties="user=stage2;password=******;server=ORCL_STAGE.INTERASSET.COM"
RefreshMinutes="25" Targets="weblogic" TestTableName="DUAL" URL="jdbc:weblogic
racle"/>
<SNMPAgent Name="adminDomain"/>
<Application Deployed="true" Name="certificate" Path=".\config\adminDomain\applications">
<WebAppComponent Name="certificate" Targets="adminServer" URI="certificate.war"/>
</Application>
<JDBCDataSource JNDIName="IAS_DATA_SOURCE" Name="IasDataSource" PoolName="IasPool"
Targets="weblogic"/>
<Application Deployed="true" Name="DefaultWebApp" Path=".\config\adminDomain\applications">
<WebAppComponent Name="DefaultWebApp" Targets="adminServer" URI="DefaultWebApp"/>
</Application>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
dc=example, dc=com;server.principal=cn=Manager, dc=example, dc=com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
dc=example, c=com" Name="defaultLDAPRealmForOpenLDAPDirectoryServices" Notes="This
is provided as an example. Before enabling this Realm, you must edit the configuration
parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<Machine Name="Prod1">
<NodeManager Name="Prod1"/>
</Machine>
<Application Deployed="true" Name="entity" Path=".\config\adminDomain\applications">
<EJBComponent Name="entity" Targets="weblogic" URI="entity.jar"/>
</Application>
<Application Deployed="true" Name="hub" Path=".\config\adminDomain\applications">
<WebAppComponent Name="hub" Targets="weblogic" URI="hub"/>
</Application>
<Server ListenAddress="192.168.0.97" ListenPort="7000" Machine="OakStage" Name="Bizarro">
<ServerStart ClassPath="my correct classpath" Name="Bizarro" OutputFile="bizarro.log"/>
<SSL Name="Bizarro"/>
<ServerDebug Name="Bizarro"/>
<KernelDebug Name="Bizarro"/>
<Log Name="Bizarro"/>
<WebServer Name="Bizarro"/>
</Server>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<ApplicationManager Name="adminDomain"/>
<CustomRealm ConfigurationData="server.host=ldapserver.example.com;membership.scope.depth=1;microsoft.membership.scope=sub;membership.filter=(|(&(memberobject=%M)(objectclass=memberof))(&(groupobject=%M)(objectclass=groupmemberof)));group.dn=ou=Groups,
o=ExampleMembershipDir;group.filter=(&(cn=%g)(objectclass=mgroup));server.principal=cn=Administrator,
ou=Members, o=ExampleMembershipDir;user.dn=ou=Members, o=ExampleMembershipDir;user.filter=(&(cn=%u)(objectclass=member))"
Name="defaultLDAPRealmForMicrosoftSiteServer" Notes="This is provided as an example.
Before enabling this Realm, you must edit the configuration parameters as appropriate
for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<JTA Name="adminDomain"/>
<Server ListenPort="7000" Name="adminServer" NativeIOEnabled="true" TransactionLogFilePrefix="config/adminDomain/logs/">
<ServerStart Name="adminServer"/>
<Log FileName="config/adminDomain/logs/weblogic.log" Name="adminServer"/>
<ServerDebug Name="adminServer"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<KernelDebug Name="adminServer"/>
<WebServer DefaultWebApp="DefaultWebApp" LogFileName="./config/adminDomain/logs/access.log"
LoggingEnabled="true" Name="adminServer"/>
<SSL Enabled="true" ListenPort="7005" Name="adminServer" ServerCertificateChainFileName="config/adminDomain/ca.pem"
ServerCertificateFileName="config/adminDomain/democert.pem" ServerKeyFileName="config/adminDomain/demokey.pem"/>
</Server>
<UnixMachine Name="OakStage">
<NodeManager ListenAddress="192.168.0.97" Name="OakStage"/>
</UnixMachine>
<Log FileName="adminDomain.log" Name="adminDomain"/>
</Domain>
Thanks guys
regards
sydCan this be done when you set up your domain along with admin and managed servers the very first time ? Even if you set up a domain with bunch of managed servers why does the library still get installed on admin server??? Also, for the method you described dont we have to update targets for statup and shutdown classes and work managers?
Also, what is the other method to do it from the console?
METHOD 2 (Other than the one you described- Please tell me if this is correct method and if we need to go to till level)
Step1:
I went to deployments base_domain (in admin console) > deployments chose each library and changed targets manually and activate the changes
Step2
Go to Startup and shutdown classes and change targets there
Step 3
Go to work managers and change targets there.
Please let me know
Edited by: user9021545 on May 12, 2011 10:18 AM
Maybe you are looking for
-
Can I add more than one horizontal separator to the PanelUI (the new panel menu)
Steps: 1. Click the new panel menu button (hamburger) 2. Click Customize 3. On the left, drag "Separator (for panel menu)" from "Additional Tools and Features" to the panel on the right. A horizontal separator appears. "Separator (for panel menu)" no
-
Everyone has the same problems. My iPod has been plugged in properly, I have followed all the support suggestions but nothing works. HELP PLEASE!
-
How to install Lion on a MacBook Pro without disks
I have a mbp from 2010 and it came shipped with snow leopard. Now i have a new ssd in my macbook and want to install lion. The sl discs are not working anymore and when I use Internet recovery it want's to install mountain lion. Can't do that becaus
-
Finder crashes when right clicking on a file
I'm new to Tiger/Apple and don't know how to make heads nor tails of this Finder.Crash.Log. Finder crashes more often than not when I right click on a file. Please help. Here is the log file: Host Name: xxxxxx-computer Date/Time: 2007-01-24 06:05:36.
-
Why can't i open PDF files inside of firefox without downloading them?
None of the suggestions are working but i used to be able to do this. Please help! Thank you