WebLogic Cluster 2 Managed Servers
Hi all,
Description: 2 virtual machines configured in cluster:
ManagedServer1: 172.31.10.76 on port 7780 (here is also AdminServer on port 7001)
ManagedServer2: 172.31.10.77 on port 7780
Everything seems to be working. I was able to deploy a war file which could tell me the ip address of the server. Everything seems to be all right. However I have some questions:
On a third machine I have Oracle 11g and I want to deploy application through the AdminServer to both of my ManagedServers but to use the db of the third server 172.31.10.78. Well I managed to do this however I can not log in through the login page of my web application. I get the following error:
<Aug 30, 2011 11:13:13 AM PDT> <Error> <HTTP> <BEA-101020> <[ServletContext@1072316483[app:manager module:manager.war path:/manager spec-version:2.5]] Servlet failed with Exception
org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: Exception [EclipseLink-28013] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Attempted to deploy PersistenceUnit [ApplicationEntityManager] while being in the wrong state [DeployFailed]. Close all factories for this PersistenceUnit.
at org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:375)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:374)
at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:263)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:101)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
Truncated. see log file for complete stacktrace
Caused By: javax.persistence.PersistenceException: Exception [EclipseLink-28013] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Attempted to deploy PersistenceUnit [ApplicationEntityManager] while being in the wrong state [DeployFailed]. Close all factories for this PersistenceUnit.
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:307)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:151)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:207)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:195)
at org.springframework.orm.jpa.JpaTransactionManager.createEntityManagerForTransaction(JpaTransactionManager.java:392)
Truncated. see log file for complete stacktrace
Caused By: Exception [EclipseLink-28013] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Attempted to deploy PersistenceUnit [ApplicationEntityManager] while being in the wrong state [DeployFailed]. Close all factories for this PersistenceUnit.
at org.eclipse.persistence.exceptions.EntityManagerSetupException.cannotDeployWithoutPredeploy(EntityManagerSetupException.java:170)
at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:307)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:151)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:207)
at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:195)
Truncated. see log file for complete stacktrace
I have also setup a DataSources with the appropriet settings - from tests I see I am able to connect to the db however I can not log in so I think there is something with the db. I`m not sure if I have Cluster with 2 Managed Servers which option I need to use DataSources or MultiData Sources. I may be wrong I do not know I`m new to clusters and weblogic but I`m very happy that after 2 days I was able to do all this :).
Any help is much appreciated.
Thank you.
Do you have any rewrites configured in Apache?
This (Middleware Snippets: Session Management Using WebLogic 12c) includes some examples to configure the WebLogic plug-in.
LoadModule weblogic_module modules/mod_wl.so
<IfModule weblogic_module>
ConnectTimeoutSecs 10
ConnectRetrySecs 2
DebugConfigInfo ON
WLSocketTimeoutSecs 2
WLIOTimeoutSecs 300
Idempotent ON
FileCaching ON
KeepAliveSecs 20
KeepAliveEnabled ON
DynamicServerList ON
WLProxySSL OFF
</IfModule>
<Location /SessionTest>
SetHandler weblogic-handler
WebLogicCluster <%= @WEBLOGIC_CLUSTER_ADDRESS %>
</Location>
<Location /SpringHibernate>
SetHandler weblogic-handler
WebLogicCluster <%= @WEBLOGIC_CLUSTER_ADDRESS %>
</Location>
Similar Messages
-
Automating start / restart of WebLogic Admin and managed servers on MS Windows
Hi All,
Please help me to do the automation of start and stop scrip of Oracle Weblogic 10.3.6 and Forms and Reports 11.1.2.2.0(Managed Servers) On Windows server 2008.
Here are two options for automating start / stop of WebLogic Admin and managed servers on MS Windows. Please suggesst which one is standrad procedure.
Use NodeManager (installed as a MS Windows Service)
or
Create Windows Service(s) for the server(s) - no NodeManager
Following Document : 1060058.1
Please suggest me the best practice. Many thanks in advance.
Kind Regards,
MohanHi Borys,
Thank you for quick reply...
If we use the first option "Create Windows Service(s) for the server(s) - no NodeManager" then we will be facing issue Like "Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running"
In the document : 1060058.1 : Mentioned as Important Note: The second option has a limitations.
Limitaion is below when we use first option : "Create Windows Service(s) for the server(s) - no NodeManager" -
Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases. If a server is started using NodeManager, NodeManager would recognize such a state and restart the process accordingly. Furthermore, if you start up managed servers via a MS Windows Service, you cannot monitor and/ or stop the managed server via the Weblogic Admin Console and/or Fusion Middleware ( Enterprise Manager ) Control.
I have implemented the second option "Use NodeManager starting admin and manged servers via WLST script" - Python script. Its working well without issue...No Limitation...
Script Contains Below :
print "================== Start scripts of Managed servers and Admin server ======================"
nmConnect(userConfigFile='D:/myFiles/myuserconfigfile.secure',userKeyFile='D:/myFiles/myuserkeyfile.secure',host='00.0.00.00',port='5556',domainName='ClassicDomain',domainDir='D:\Oracle\Middleware\user_projects\domains\ClassicDomain',nmType='ssl')
print "================== Adminserver Starting ================================================"
nmStart('AdminServer')
connect('weblogic','Password1','10.4.93.117:7001')
print "================== MANAGED SERVER (FROMS) Starting ====================================="
start('WLS_FORMS','Server')
print "================== MANAGED SERVER (REPORTS) Starting ==================================="
start('WLS_REPORTS','Server')
exit()
HOPE WE WILL MEET AGAIN AND AGAIN...
Many thanks for your comments!
Kind Regards,
Mohan -
Starting cluster fails, managed servers can't seem to connect to admin serv
I have been trying to run the WebLogic JPA example from,
http://wiki.eclipse.org/EclipseLink/Examples/JPA/CacheCoordination
but not having much luck on three different Linux machines,
The first issue I found was if you did not set the memory options just right, the JVM would just hang,
I am now using,
<jvmarg value="-XX:PermSize=512m"/>
<jvmarg value="-XX:MaxPermSize=960m"/>
with JDK 1.7_17, not sure if there are better options...
The 3 servers are started using (each with different port, all server run on the same machine, as with the admin server),
<java classname="weblogic.Server"
fork="true"
failonerror="true">
<jvmarg value="-server"/>
<!--jvmarg value="-Xms512m"/>
<jvmarg value="-Xmx960m"/-->
<jvmarg value="-XX:PermSize=512m"/>
<jvmarg value="-XX:MaxPermSize=960m"/>
<env key="PATH" value="${env.JAVA_HOME}/bin:${env.PATH}"/>
<sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
<sysproperty key="weblogic.Name" value="server1"/>
<sysproperty key="bea.home" value="${JEE_HOME}"/>
<sysproperty key="weblogic.management.server" value="${JEE_HOST}:7001"/>
<sysproperty key="weblogic.management.username" value="${JEE_USER}"/>
<sysproperty key="weblogic.management.password" value="${JEE_PASSWORD}"/>
<sysproperty key="java.security.police" value='"${JEE_SERVER}/lib/weblogic.policy"'/>
<sysproperty key="weblogic.RootDirectory" value="${JEE_DOMAIN}"/>
<sysproperty key="weblogic.Stdout" value="server1.log"/>
<sysproperty key="weblogic.Stderr" value="server1.err"/>
<classpath>
<fileset dir="${JEE_SERVER}/lib" includes="weblogic.jar,weblogic_sp.jar"/>
<pathelement location="${env.JAVA_HOME}/lib/tools.jar"/>
</classpath>
</java>
I found that the start-up would sometimes fail on some of the machines unless I used,
<sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
But on once machine this does not help either,
I also tried using unicast, but still does not start,
the admin server starts, then the managed servers start and seem to try to connect to the admin server and just never do, never get past STARTING (to STARTED in the log).
Another have any other ideas?How are you starting the managed servers. try running the command
from /MW_HOME/user_projects/domains/bifoundation_domain/bin
nohup sh ./startManagedWebLogic.sh bi_server1 http://localhost:7001> start_bi_server1.log &
and see how it goes. make sure you have set the boot.properties files under security folder so that it wont get failed looking for username and password.
hope it helps -
Weblogic server and managed servers sudden shutdown
Hi,
when trying to restart both the admin and managed osb servers. after some time the admin and managed servers are getting shut down. This is what the information i got from logs. Appreciate your help in this regard
####<Aug 18, 2011 12:51:44 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686304697> <BEA-310002> <38% of the total memory in the server is free>
####<Aug 18, 2011 12:52:06 PM EDT> <Error> <JDBC> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000109> <1313686326579> <BEA-001112> <Test "SELECT 1 FROM DUAL" set up for pool "GLTOdatasource" failed with exception: "oracle.jdbc.xa.OracleXAException".>
####<Aug 18, 2011 12:52:06 PM EDT> <Info> <JDBC> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000109> <1313686326580> <BEA-001128> <Connection for pool "GLTOdatasource" closed.>
####<Aug 18, 2011 12:52:44 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686364766> <BEA-310002> <61% of the total memory in the server is free>
####<Aug 18, 2011 12:56:45 PM EDT> <Info> <Health> <weblogic.GCMonitor> <<anonymous>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000011> <1313686605051> <BEA-310002> <44% of the total memory in the server is free>
####<Aug 18, 2011 12:58:18 PM EDT> <Info> <Security> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000111> <1313686698580> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
####<Aug 18, 2011 1:02:23 PM EDT> <Notice> <WebLogicServer> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686943979> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Aug 18, 2011 1:02:23 PM EDT> <Alert> <gifosb_admin> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686943996> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Aug 18, 2011 1:02:24 PM EDT> <Notice> <WebLogicServer> <Thread-1> <<WLS Kernel>> <> <8beb4c4d69347bb8:6c6553af:131ddaf5db4:-7ff7-0000000000000117> <1313686944005> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
Thanks,
Bharath<JVM called WLS shutdown hook. The server will force shutdown now>This is your JVM process which is getting killed and hence server is forced to shutdown. On which OS, servers are running? How are you starting the server? If you are on windows, DO NOT close the command prompt through which you started the server.
Regards,
Anuj -
How create one cluster whit managed servers in diferent hosts?
in the same domain
Have you created a domain using the config tool ( which gives you just an admin server and no managed servers )?
Start your admin server & login.
Create a session in the Change Center
Create 1 machine within the admin console for each host: ( Domains -> Environment -> Machines - > New ). Use the actual host name for the value of Machine Name.
So create a machine named "myhost1.yourcompany.com" and a machine named "myhost2.yourcompany.com".
You can also do this within the configuration tool:
http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/custom.html#wp1071071 -
Weblogic Cluster recovery of servers declared dead
Hi
1)When the HungServerRecoverSecs time is over and the server is declared dead,
why does the server not behave as a part of the cluster even when it is brought
up?
2)What steps need to be taken to make sure that the server beahaves as a part
of the cluster once it is brought back up?
3)Is there a way by which we can restart any one of the boxes clustered together
without affecting the other ones behaviour as a part of the cluster and then puch
into this cluster the one we started lately?
Thanks
Mausam
Mausam wrote:
> Hi
> 1)When the HungServerRecoverSecs time is over and the server is declared dead,
> why does the server not behave as a part of the cluster even when it is brought
> up?
This is not true, when hungserverrecoversecs time is over, we just assume that server
is hung and not responding. We do failover to 2ndry server at this time. When you
recycle such server, it should become part of dynamic list of servers used by proxy
to load balance. if this is not the behavior you are seeing, it could be a bug.
Follow with [email protected]
>
> 2)What steps need to be taken to make sure that the server beahaves as a part
> of the cluster once it is brought back up?
none at your end. With the next HTTP request we will rewrite the list of servers HTTP
header that will be parsed by proxy.
>
> 3)Is there a way by which we can restart any one of the boxes clustered together
> without affecting the other ones behaviour
yes, you can!
> as a part of the cluster and then puch
> into this cluster the one we started lately?
yes you can add or delete as many servers as you want any time in cluster.
>
>
> Thanks
> Mausam
Viresh Garg
Principal Developer Relations Engineer
BEA Systems
-
Weblogic managed servers question
Hi all,
I'm trying to set up a 3 machines , one having weblogic admin
server and two machines having managed weblogic servers.what i'm not
undersatnding is :
1. Do i have to install the weblogic software on all machines with the same
domain name .?
2. Do i have to deploy my components/web applications on all machines?
3. Do i have to put the above machines in a cluster to achieve load
balancing etc.
4. How will i access my manage servers considering that they will have 2
different ips (since they are installed on 2 different
machines)?
5.Does anyone know any dosc online which explains these matters.I have gone
through the weblogic server administrator
guide , but could not find the information i'm looking for (or have i
missed any section)?
Thanks in advance
PrashantHi.
My answers are embedded:
Prashant S wrote:
Hi all,
I'm trying to set up a 3 machines , one having weblogic admin
server and two machines having managed weblogic servers.what i'm not
undersatnding is :
1. Do i have to install the weblogic software on all machines with the same
domain name .?I'm not sure what you mean. The managed servers need to be in the same
weblogic domain (ie directory under config) if you are using clustering. Also
if you are using clustering the cluster members (managed servers) need to be on
the same LAN/subnet.
>
2. Do i have to deploy my components/web applications on all machines?You do not have to deploy your applications on your admin server. Typically I
install a webapp (or whatever) on the admin server then select the targets for
deployment to the managed servers.
>
3. Do i have to put the above machines in a cluster to achieve loadbalancing
etc.Yes.
>
4. How will i access my manage servers considering that they will have 2
different ips (since they are installed on 2 different machines)?For web applications the standard practice is to use a proxy front-end to the
cluster. We offer plugin's for Netscape, Apache and IIS that handle
loadbalancing and failover for weblogic clusters. We also offer the
HttpClusterServlet if you prefer to use an instance of WLS to proxy to your
cluster. Use your browser to hit the proxy, which will pass your request on to
a cluster member. See the following link for details:
http://edocs.bea.com/wls/docs61/adminguide/http_proxy_cluster.html
>
5.Does anyone know any dosc online which explains these matters.I have gone
through the weblogic server administrator
guide , but could not find the information i'm looking for (or have i
missed any section)?
Thanks in advance
Prashantnot sure if you have seen this but
http://edocs.bea.com/wls/docs61/cluster/index.html contains links to docs
discussing most cluster administration issues.
Hope this helps.
Michael Young
Developer Relations Engineer
BEA Support -
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 -
SAML2 between Managed Servers in same Weblogic
Hi,
I need to configure SAML V2 between 2 or more applications deployed in WebLogic 10.3.6 server.
My problem occurs when I try to use application in same weblogic, different managed server.
* App1 call App2 within an iframe.
* When I access App1, logon page works.
* When I access App2 within iframe, credentials was transfered perfectly from App1 to App2.
* When I return to App1, session is ended.
Deploying apps on diferent weblogic all works fine and I can access App1 and App2 normally.
Deploying apps on same weblogic, same managed server, credentials are sharing automatically even SAML not configured.
I can't understand why App1's session was killed when I access App2 in same weblogic and different managed servers.
Does someone can help me?
RegardsI am setting a different cookie for each application. First app show login form and authenticate correctly but when I open second app, credentials was not recnognized.
-
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 -
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
>>>>
>>>
>>
>
-
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?
-
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 -
I am unable to start Managed Servers through Weblogic AdminConsole
Hi,
We are using Weblogic 10.3.1.0 version.
Totaly 4 Managed Severs
1 Admin Server
with Nodemanger.
In Admin Console When ever we going to Stop the Manged Servers.
1. Environment ----- > Servers ---- > Control ----------- > Mananged Server 1 -----------> Force shutdown
2. Then click refresh button ---- showing "FAILED_NOT_RESTARTABLE"
3. after that when ever we going to start the Managed Server in Admin console
First its Showing ----- Starting
and next its showing ----- FAILED_NOT_RESTARTABLE
4. its not coming to Running State.
In Logs
Domain log
-----------> <1273141345460> <BEA-000450> <Socket 8 internal data record unavailable (probable closure due idle timeout), event received 17>
####<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280738> <BEA-000396> <Server shutdown has been requested by weblogic>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280771> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
####<06-May-2010 11:54:40 o'clock BST> <Notice> <Cluster> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280844> <BEA-000163> <Stopping "async" replication service>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281061> <BEA-000365> <Server state changed to ADMIN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281064> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<06-May-2010 11:54:41 o'clock BST> <Notice> <Server> <ukirt156> <twpserver1> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1273143281113> <BEA-002607> <Channel "Default" listening on 172.21.149.168:7003 was shutdown.>
####<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <ukirt156> <AdminServer> <[ACTIVE] ExecuteThread: '45' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273143390016> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
AdminServer log
<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 11:57:33 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
<06-May-2010 12:07:02 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
ManagedServer Log
<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler pause
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
<06-May-2010 11:54:54> <Debug> <NodeManager> <Waiting for the process to die: 19316>
<06-May-2010 11:54:54> <Info> <NodeManager> <Server was shut down normally>
<06-May-2010 11:54:54> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
NodeManager Log
<06-May-2010 11:54:54> <Info> <twp_domain> <twpserver1> <Server was shut down normally>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Boot identity properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Startup configuration properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/startup.properties">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00020">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Starting WebLogic server with command line: /appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/bin/java -Dweblogic.Name=twpserver1 -Djava.security.policy=/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.management.server=http://ukirt156:7001 -Djava.library.path="/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386/jrockit:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/../lib/i386::/appl/nsm/CA/UnicenterNSM/lib:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386/client:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386:/appl/nsm/CA/SharedComponents/ccs/dia/dna/lib:/appl/nsm/CA/SharedComponents/ccs/dia/lib:/usr/lib:/opt/CA/CAlib:/appl/nsm/CA/SharedComponents/lib:/appl/nsm/CA/SharedComponents/Csam/SockAdapter/lib:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/data/share/package/twp/WEB-INF/lib/ojdbc14.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.system.BootIdentityFile=/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xmanagement:port=7091,ssl=false,authenticate=false -Xms=1200m -Xmx=1200m -Xverbose:gc,gcpause -Dreflexis.scheduler=true -Dreflexis.server=twpserver1 -Djava.awt.headless=true -Dclient.encoding.override=UTF-8 -Doracle.jdbc.V8Compatible=true weblogic.Server >
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Working directory is "/appl/weblogic/scripts">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00021">
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
<06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
<06-May-2010 11:56:29> <Info> <twp_domain> <twpserver1> <Server failed during startup so will not be restarted>
<06-May-2010 11:56:29> <Warning> <Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:332)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Server logs
<06-May-2010 12:06:57> <Info> <NodeManager> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
[JRockit] Management server started on port 7091, ssl=false, authenticate=false.
<06-May-2010 12:06:59 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.2-20_o-108500-1.6.0_05-20090120-1115-linux-ia32 from BEA Systems, Inc.>
<06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}xvFgPysVi5b89pYwaAppoqPXQ5wFVW13yoFhzhKmuQo= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception <06-May-2010 12:07:01 o'clock BST> <Info> <Management> <BEA-141223> <The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the
<06-May-2010 12:07:01 o'clock BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
at weblogic.Server.main(Server.java:67)
>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<06-May-2010 12:07:01 o'clock BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<06-May-2010 12:07:02> <Debug> <NodeManager> <Waiting for the process to die: 19443>
<06-May-2010 12:07:02> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<06-May-2010 12:07:02> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Note: if i start the manged servers through WLST script its working fine.
[twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
nmStart('twpserver1')
Please provide the solution, how to solve this issue.
Thanks
SRKJust at first glance, it seems as though you have one or more configuration issues, perhaps inconsistencies between the node manager server configuration files and the domain's config.xml
nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
nmStart('twpserver1')
implies that tmp_domain is configured in /appl/weblogic/oracle/middleware/user_projects/domains, (which is the default from the configuration wizard). However, the node manager and server output logs make it seem like it's trying to use a domain in the directory /appl/weblogic/scripts. Not sure how that happened, perhaps you had two domains? Perhaps copied or moved the domain files? Something else?
In any case, start by checking out your nodemanager.domains file and ensure that it reflects your intended domain directory.
Maybe you are looking for
-
Insert statement does not insert all records from a partitioned table
Hi I need to insert records in to a table from a partitioned table.I set up a job and to my surprise i found that the insert statement is not inserting all the records on the partitioned table. for example when i am using select statement on to a par
-
The company I work for use AVI videos for Nuendo and I have recently installed my Adobe CC to test efficiency in creating video files for our clients. making QT is a piece of cake but cannot seem to find an option to create AVI anywhere. Would this o
-
Ask about PF-STATUS in ALV LIST DISPLAY
Hi gurus, I have a code like below : REPORT zmm_qi_un2. TABLES : zqi01. TYPE-POOLS: slis. data : itab like table of zqi01 with header line. CONSTANTS : sym_checkbox VALUE '9', sym_large_square VALUE 'W', sym_locked VALUE 'H'.
-
How to install Windows 8 on Boot Camp?
I am wondering if the Retina MacBook Pro now supports Windows 8? Is this the one I should buy if I want to install Windows on my Mac? http://www.amazon.com/Microsoft-Windows-8-Pro-Upgrade/dp/B008H3SW4I/ref=sr_1_2?i e=UTF8&qid=1365657884&sr=8-2&keywor
-
Hello everybody, does anybody know how I can read from CAR Area network with [c]FP 2020. I want to use a modul from softing witch converts CAN 11898 to USB. From there I want to use a USB -> RS232 converter to read the CAN message with the [c]FP seri