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
> ***************************************************************************
>
>
>
Similar Messages
-
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 -
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 -
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
patrickHi 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 -
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 -
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. -
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 -
Startup.properties settings for managed servers
We are using WLS 9.2 MP3 on Solaris 10 (SPARC).
I have built a few test systems in an attempt to document configurations and noticed my managed servers on the systems start up with a different "weblogic.management.server" setting in the log files. This setting appears in the <domain>/servers/<server name>/data/nodemanager/start.properties file as "AdminURL=http:\://xxx.xxx.xxx.xxx\:7001"
Each system was built and rebuilt using the same settings. Each system has multiple interfaces. One system has an entry of AdminURL=http:\://192.168.100.100\:7001 and another system has an entry of AdminURL=http:\://10.10.10.100\:7001 even though each system was built just like the other.
Every time I manually change the adminURL setting it gets reset on each server restart (which I expected). I have not specified (that I know of) the IP address or interface of the admin server anywhere in the "server start" settings. I also notice the admin server is starting on all interfaces on the system (not sure if this is good/bad/indifferent).
Can anyone tell me where the startup.properties file entries are pulled from?
As a followup: I just noticed (after my post) a slight difference between my systems. One has a fiber connection whereas the others do not. When I execute 'ifconfig -a' I see the interfaces/IP's in different orders (because the interfaces are named differently). I also noticed a wlsifconfig.sh script in one of the startup files. It almost appears as though the wlsifconfig.sh script is setting the AdminURL value and is pulling it from the last interface it finds in the ifconfig listing?????
Thanks for any assistanceTo diagnose problems with Thunderbird, try one of the following:
*Restart Thunderbird with add-ons disabled (Thunderbird Safe Mode). On the Help menu, click on "Restart with Add-ons Disabled". If Thunderbird works like normal, there is an Add-on or Theme interfering with normal operations. You will need to re-enable add-ons one at a time until you locate the offender.
*Restart the operating system in '''[http://en.wikipedia.org/wiki/Safe_mode safe mode with Networking]'''. This loads only the very basics needed to start your computer while enabling an Internet connection. Click on your operating system for instructions on how to start in safe mode: [http://windows.microsoft.com/en-us/windows-8/windows-startup-settings-including-safe-mode Windows 8], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7 Windows 7], [http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-vista Windows Vista], [http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/boot_failsafe.mspx?mfr=true" Windows XP], [http://support.apple.com/kb/ht1564 OSX]
; If safe mode for the operating system fixes the issue, there's other software in your computer that's causing problems. Possibilities include but not limited to: AV scanning, virus/malware, background downloads such as program updates. -
Cluster Monitoring didn't show all the managed servers in cluster .
Hi
We have below configuration :
domain :- 6 clusters
each cluster :- 3 managed servers (managed servers are on different physical boxes)
when monitoring the cluster we can see
for ms1 it shows : ms1,ms2 but not ms3
for ms2 it shows : ms1,ms2 but not ms3
for ms3 it shows : ms1,ms2,ms3
ms3 is Running.
Why ms1 and ms2 are not able to see ms3? This is happening with all the clusters.ms1 and ms2 are not able to see ms3.
Is the reason that heart beat messages are not received by ms1 and ms2 even though ms3 is running?
Is this because network issue?
Is it that if JVM is busy doing full Gc then it ignores Hearbeat messages. ?
Please correct me if i ma wrong.
Thanks in advance.. :)Hi,
Did u check if the server MS3 was running .. also did u see any exception/error/warn message in the system.out log.
regards,
Zeno -
Weblogic managed servers connecting to the servers in different cluster
Hi All,
We have a weired problem going on for a while. We have a cluster configuration
with an admin server and two managed servers. We have the similar configuration
in DEV, TEST and PROD. The problem is that the managed server members in DEV cluster
are making connections to managed servers which are member of PROD cluster for
session replication. The same way TEST servers are trying to connect to PROD and
DEV.
Has anyone seen this kind of problem before. BEA seems to be cluless so far.
Thanks in adavnce for your input.
Udit
Venkat,
Thats a good suggestion but these things are too obvious to ignore. We have different
multicast address in DEV and PROD and also hosts are on different sub net. I do
not know if cluster name will make any differene though.
Thanks for your input anyway,
Udit
"venkat" <[email protected]> wrote:
>
>Udit,
> You can check the sub net, multicast address and the cluster name.
>If the dev
>and prod servers are in the same sub net with same multicast address,
>then change
>the multicast and try.
>
>Venkat
>"venkat" <[email protected]> wrote:
>>
>>Udit,
>>
>>
>>"Udit Singh" <[email protected]> wrote:
>>>
>>>Kumar,
>>>Thanks for the reply.
>>>The situation is that managed server in DEV try to replicate the session
>>>to a
>>>managed server in PROD and TEST and vice versa.
>>>Let us say our dev managed servers are running on abc01 and abc02 and
>>>prod managed
>>>servers are running on xyz01 and xyz02. All the managed servers are
>>running
>>>on
>>>port 7005.
>>>If I do the netstat on abc01 or abc02 I could the see established connections
>>>between abc01/02 and xyz01/02.
>>>Why is that happening? We are running 6.1SP2.
>>>
>>>Udit
>>>
>>>Kumar Allamraju <[email protected]> wrote:
>>>>We do not restrict intercluster communication as of 61 SP3.
>>>>Once we get the IP from the cookie, we can safely make a
>>>>connection to the other clustered node. We were not checking
>>>>if the server is part of the same cluster or not. This is
>>>>already fixed in 7.x and 61 SP4(not yet released) If you are
>>>>on 61 Sp2 or SP3 then you should contact support and
>>>>reference CR # CR089798 to get a one off patch.
>>>>
>>>>Regardless, are you traversing from DEV to PROD cluster and
>>>>vice-versa. If not then this problem shouldn't happen unless
>>>>plugin is routing the request to wrong cluster.
>>>>
>>>>--
>>>>Kumar
>>>>
>>>>Udit Singh wrote:
>>>>> Hi All,
>>>>> We have a weired problem going on for a while. We have a cluster
>>configuration
>>>>> with an admin server and two managed servers. We have the similar
>>>configuration
>>>>> in DEV, TEST and PROD. The problem is that the managed server members
>>>>in DEV cluster
>>>>> are making connections to managed servers which are member of PROD
>>>>cluster for
>>>>> session replication. The same way TEST servers are trying to connect
>>>>to PROD and
>>>>> DEV.
>>>>> Has anyone seen this kind of problem before. BEA seems to be cluless
>>>>so far.
>>>>>
>>>>> Thanks in adavnce for your input.
>>>>> Udit
>>>>
>>>
>>
>
-
OSB Managed Servers - How to add one to the OSB Cluster
Hi,
I have an OSB Cluster of two managed servers. There is an Admin Server that controls the two.
On the Admin Server I see that there are about 137 odd Applications and a list of Libraries installed.
However on the Managed Servers I see there is not a single application.
Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?
If I create a new Managed Server that I want to Add to the Cluster there is no option to deploy those applications to the newly created Managed server in one shot. The only time it can get those applications is if the Applications were deployed to the OSB Cluster and not to the managed servers.
Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well?Does Managed Server show only the Custom applications? I feel not. Applications like AQAdapter, MQ Adapter, ALSB Routing, etc. should they all not be present on the Managed Servers?Your understanding is correct. Managed server should have libraries and adapters targetted to it.
Is there a way (apart from extending the domains again and having those applications deployed to the OSB cluster) to have all these applications running on the Managed servers as well? Yes, manually you have to target each and every application to the cluster but it may not be an effective process. The basic funda of cluster is to make applications independent of managed server, so that if you add/remove a managed server then it does not affect the existing configuration. I think you should follow the standard practice and always create a clustered domain where all applications are targetted to cluster and NOT to the managed server. You may like to refer -
http://download.oracle.com/docs/cd/E17904_01/doc.1111/e15022/config.htm#i1531648
Regards,
Anuj -
Weblogic.Admin command for stopping all Managed Servers in cluster
Hello All,
I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
I am looking for a way to do that using java weblogic.Admin utility
Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
Thanks
Weblogic Consultanthi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM -
Singleton deployed in cluster runs in both managed servers
Hi,
I have deployed a singleton service in a Weblogic (9.2) cluster. This cluster has two managed servers.
Recently we saw instances of this singleton services running on both these managed servers, which resulted in a lot of duplicate data in our system.
Is this a bug in the system? How can we prevent this?Hi,
Could you please refer the following links and confirm me if you had defined and configured the singleton service as mentioned in the links:
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/clusters/ConfigureSingletonService.html
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/clusters/DefineSingletonService.html
regards,
Zeno
Maybe you are looking for
-
Historic and Current data for Master data bearing objects
Hi All, We are trying to implement type 2 dimensions for all the master data bearing characteristics, where we require historic and current data available for reporting. the master data can have a number of attributes and all of them can be time depe
-
Error while loading heirarchy for a standard infoobject
HI, When I try to run a infopackage for loading a hierarchy for a standard info object 0RPM_BUGU, I'm getting an error that states that there are no PSA tables for the selection criteria. Both the communication and the transfer structure are active.
-
Getting time_out Error in report bcos of SQL Statement!
Hi Experts, I am getting Time_out error in my big program because of Select statement.I have checked in SQL Trace AND fuond the message "SQL0104N An unexpected token "vakey" was found following "umh kschl". Expected tokens may include: ",". S
-
hi everybody, when i try to build a midlet which imports from bouncycastle (import org.bouncycastle.crypto.CryptoException; for example) i get an error message: package org.bouncycastle.crypto does not exist i tried placing the java and org folders o
-
I click the + button to open a new tab and it doesn't do anything, not even open a new tab. I try to right click and open a new tab and still don't work. But if I right click a link and click open in new tab it will work. How do I get to open my tabs