Two Managed Servers non-clustered problem

I have two managed servers each exactly the same just listening on different
          port in the same domain. When I start the second server I get a "Child
          exited " message reported in the first server's logs. This does not seem to
          affect the running of the server. Does anyone know why this happens. Note
          that both servers define the same jndi name for a stateless session bean.
          Could this be a problem>

Solaris 8. There is no information in any log relating to the message "Child
          Exited". Note that sometimes the message appears twice.
          "Kumar Allamraju" <[email protected]> wrote in message
          news:[email protected]..
          > what OS is this on?
          > This message may not be coming from WLS?
          > Can you post the error message or stacktrace?
          >
          > --
          > Kumar
          >
          > Paul
          >
          > > I have two managed servers each exactly the same just listening on
          different
          > > port in the same domain. When I start the second server I get a "Child
          > > exited " message reported in the first server's logs. This does not seem
          to
          > > affect the running of the server. Does anyone know why this happens.
          Note
          > > that both servers define the same jndi name for a stateless session
          bean.
          > > Could this be a problem>
          > >
          > >
          >

Similar Messages

Transaction span two WLS managed servers (non-clustering)

(Weblogic 6.1 - non-clustering version)
I have two managed servers configured on a single machine on different
ports, and I am not using clustering weblogic. Assuming I have EJB A
deployed on managed server 1, and EJB B deployed on managed server 2.
I want to have EJB A to invoke EJB B. In EJB A, I guess I will
probably create the InitialContext with the URL of managed server 2,
then do the JNDI look up and call EJB B.
My questions are:
- Can weblogic handle transaction that spans two managed servers
(non-clustering setting)?
- Does weblogic use XA to handle transaction between managed servers?
- Do I need to do any JTA code in order to achieve that (instead of
just letting the EJB container to handle the transaction for me)?
Thanks in advance!
B.L.

Hi,
"benson" <[email protected]> wrote in message
news:[email protected]..
(Weblogic 6.1 - non-clustering version)
I have two managed servers configured on a single machine on different
ports, and I am not using clustering weblogic. Assuming I have EJB A
deployed on managed server 1, and EJB B deployed on managed server 2.
I want to have EJB A to invoke EJB B. In EJB A, I guess I will
probably create the InitialContext with the URL of managed server 2,
then do the JNDI look up and call EJB B.
My questions are:
- Can weblogic handle transaction that spans two managed servers
(non-clustering setting)?Yes, it can.
- Does weblogic use XA to handle transaction between managed servers?Yes, it does. Make sure you use TX DataSources. If the servers are connected
to different databases, TX DataSources should be based on connection pools
used XA drivers.
- Do I need to do any JTA code in order to achieve that (instead of
just letting the EJB container to handle the transaction for me)?No, you don't. WebLogic will take care about handling
distributed TXs.
Regards,
Slava Imeshev

Bridge already registered when using two managed servers

I have defined a messaging bridge with a target of my cluster in Weblogic 9.0 (upgraded from 7.0). My cluster has two managed servers. The bridge and resource adapter also have targets of the cluster. When I start the first managed server, everything works fine. The bridge works. When I bring up the second managed server, I repeatedly get the following:
          javax.jms.JMSException: SJMSBridge is already registered
          Is there something new that I need to define in the config to make this work?

Here is the full error. I can understand what you are saying about the cluster, but I get this message even when only one server of the cluster is running. That doesn't make sense to me.
          ####<Nov 15, 2005 2:30:36 PM PST> <Info> <MessagingBridge> <PFRIMER> <ManagedServer2> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1132093836274> <BEA-200030> <Bridge "SJMSBridge" is configured to work in "Exactly-once" mode, and it is actually working in "Duplicate-okay" mode.>
          ####<Nov 15, 2005 2:30:36 PM PST> <Info> <MessagingBridge> <PFRIMER> <ManagedServer2> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1132093836805> <BEA-200028> <The bridge "SJMSBridge" has started transferring messages.>
          ####<Nov 15, 2005 2:30:38 PM PST> <Warning> <MessagingBridge> <PFRIMER> <ManagedServer2> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1132093838008> <BEA-200026> <Bridge "SJMSBridge" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: javax.resource.ResourceException: Error setting message listener
               at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1457)
               at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1437)
               at weblogic.jms.adapter.JMSBaseConnection.setMessageListener(JMSBaseConnection.java:1201)
               at weblogic.jms.adapter.JMSConnectionHandle.setMessageListener(JMSConnectionHandle.java:134)
               at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:951)
               at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1038)
               at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
          -------------- Linked Exception ------------
          javax.resource.ResourceException: Error creating asynchronous consumer
               at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1457)
               at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1437)
               at weblogic.jms.adapter.JMSBaseConnection.createConsumer(JMSBaseConnection.java:1299)
               at weblogic.jms.adapter.JMSBaseConnection.access$400(JMSBaseConnection.java:84)
               at weblogic.jms.adapter.JMSBaseConnection$11.run(JMSBaseConnection.java:1183)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
               at weblogic.jms.adapter.JMSBaseConnection.setMessageListener(JMSBaseConnection.java:1180)
               at weblogic.jms.adapter.JMSConnectionHandle.setMessageListener(JMSConnectionHandle.java:134)
               at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:951)
               at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1038)
               at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
          -------------- Linked Exception 2 ------------
          javax.jms.JMSException: SJMSBridge is already registered
               at org.exolab.jms.messagemgr.ConsumerManager.createDurableConsumerEndpoint(ConsumerManager.java:404)
               at org.exolab.jms.server.JmsServerSession.createSubscriber(JmsServerSession.java:771)
               at org.exolab.jms.server.mipc.IpcJmsSessionConnection.createSubscriber(IpcJmsSessionConnection.java:588)
               at org.exolab.jms.server.mipc.IpcJmsSessionConnection.notify(IpcJmsSessionConnection.java:165)
               at org.exolab.jms.server.mipc.IpcJmsReceiver.notify(IpcJmsReceiver.java:100)
               at org.exolab.jms.server.mipc.IpcServerChannel.run(IpcServerChannel.java:161)
          .)>

Wlw-runtime-config.xml & two managed servers

I have a problem with WSDL generation and WebLogic workshop in a
cluster.
I'm using a wlw-runtime-config.xml file to ensure that my web service
generates the correct url for it's endpoint.
The problem I have is that I have two managed servers on one physical
box, one listening on port 7010, the other on port 7030.
The wlw-runtime-config.xml file is placed in the domain root, and I
only seem to be able to specify a single port/dns name in the config
file.
My web service request will come in through the IIS plugin, hit one of
the servers, generate the WSDL containing the port information, which
may or may not be correct for the WLS instance that it has actually
been proxied to.
If that is correct, how do I handle the fact that the web service is
deployed across all cluster members, two of which are hosted on one
single machine.
Am I missing something?
Pete

Hi Pete,
I'm assuming you have seen the "how do i" on this topic [3], plus the
information on how to setup a cluster [1].
Your missing link may be the way your DNS entry is configured for the
cluster. See the docs [2] on this topic, but you will need to specify
the multiple nodes something like this:
DNSName1:port1,DNSName1:port2,DNSName1:port3
Note the folks in our super support group will be best suited to assist
your efforts.
Regards,
Bruce
[1]
http://e-docs.bea.com/wls/docs81/cluster/setup.html#684345
[2]
http://e-docs.bea.com/wls/docs81/cluster/setup.html#714310
[3]
http://edocs.bea.com/workshop/docs81/doc/en/workshop/guide/deployment/howClusterDeployment.html
Pete wrote:
>
I have a problem with WSDL generation and WebLogic workshop in a
cluster.
I'm using a wlw-runtime-config.xml file to ensure that my web service
generates the correct url for it's endpoint.
The problem I have is that I have two managed servers on one physical
box, one listening on port 7010, the other on port 7030.
The wlw-runtime-config.xml file is placed in the domain root, and I
only seem to be able to specify a single port/dns name in the config
file.
My web service request will come in through the IIS plugin, hit one of
the servers, generate the WSDL containing the port information, which
may or may not be correct for the WLS instance that it has actually
been proxied to.
If that is correct, how do I handle the fact that the web service is
deployed across all cluster members, two of which are hosted on one
single machine.
Am I missing something?
Pete

Linking JMS Queues between two managed servers

I have an environment setup with an AdminServer and multiple managed servers all under the same domain and on the same cluster. They are all running under the same Instance of weblogic on one Windows Server.
          I have two different applications on two managed servers that need to have a JMS Queue be linked between them. Essentially have Server1's 'inbox' link to Server2's 'outbox' and Server2's 'inbox' link to Server2's 'outbox'. Each has their own name for their inbox or outbox.
          Server1(inbox)=Server2(outbox)
          Server2(inbox)=Server1(outbox)
          I've tried using Foreign JNDI Providers, however it doesn't allow me to input two addresses (Server1 and Server2).
          Is there another function that would do the same thing?
          Thanks!

You can make use of Message Bridges between any 3th party JMS provider or SAF (store & forward) if both jms servers are weblogic servers.
          Schelstraete Bart
          [email protected]
          http://www.schelstraete.org
          http://www.linkedin.com/in/bschelst
          Edited by bschelst at 04/07/2008 1:27 PM

Need recommendation - iis with two physical servers and clusters

Hello,
I was hoping to get a recommendation/opinion or two on the configuration I've inherited. I'm looking
at the following configuration using weblogic 8.1 sp4 server (to be upgraded to sp6) running on two physical machines:
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7001
ManagedServer2:7010
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:7001
ManagedServer4:7010
On MachineA: IIS Proxy Plugin with parameter in .ini file
WeblogicCluster: MachineA:7001, MachineA:7010, MachineB:7001,MachineB7010
Naturally, the IIS is acting as a round robin load balancer..
The domains were created using the wizard on both machines and basic domain template..
For proper failover to be taken advantage of, does something different need to be configured? Or is it fine?
And if so, does group replication have something to do with it?
Should either of the clusters be Managed Servers across physical machines?
or should this just be one cluster of 4 managed servers across two machines?
I really am not sure on any of this, even though i've read through much of the documentation for clustering..twice.
I should mention that there is only a .war file deployed with 4 connection pools and 4 Data Sources..No EJBs or JMS
Would really appreciate any feedback or opinions/advice..
Thanks

This is what I'd do
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7010
ManagedServer2:7020
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:8010
ManagedServer4:8020
I just changed the port numbers so they flow and have a pattern - 70* port numbers belong to cluster 1, 80* port numbers belong to cluster 2. No technical benefit apart from it makes it tidier in my opinion.
Port 9001 for the admin server is normally the domain wide admin port - you could be using that, so that's fine, but my admin server is running 7001.
You also only need one admin server per domain, this can run on MachineA
Replication groups are used to help WLS figure out where to place the secondary http session. It will try servers on a different machine/replication group first, if none available, it will create secondary on the same machine.
What you will end up with is a domain with 4 managed servers in it. The admin server will run on machineA, say using port 7001, each of the managed servers will contact the admin server to download it's config.
The cluster1 will contain 2 managed servers and the same for cluster2.
providing you have your cluster multicast addresses set up and the cluster is working, that should be all you need to do for the session failover.
There's some BEA sample code somewhere which will deploy a web-app and show which managed server you've attached to. If you find that and then connect through IIS, shut down the server that the JSP tells you, you should be able to see the session fail-over nicely.
Hope that helps,
Pete

Two Managed servers in the same apahce.

Hi,
I did not have too much experience with WLS, I have two manged servers which listened on diff port, and I tried to configure them in one apache instance..
do u know how to do it? I have tried this:
<Location /weblogic>
SetHandler weblogic-handler
PathTrim /weblogic
</Location>
<IfModule mod_weblogic.c>
MatchExpression app1 WebLogicHost=192.1.1.87|WebLogicPort=7100|Debug=ON
MatchExpression app2 WebLogicHost=192.1.1.87|WebLogicPort=7200|Debug=ON
</IfModule>
And got the following error:
[Mon Jun 23 15:43:41 2003] [error] CONFIG_ERROR [line 1309 of ap_proxy.cpp]: Neither 'WebLogicCluster' nor 'WebLogicHost' specified in parameters
My WLS: 7 sp2 and apache is 2.0.45.
Appreciate your advice...
Regards
Leo

You can have more number of soa servers in a SOA domain. You can create mutiple managed servers using config wizard. But when you create more than one soa servers, then all the servers should exist in the same cluster.
You can not have the soa servers outside the soa cluster.

Two managed servers in one apache.

Hi,
I do not have too much experience with WLS, now I have two or more managed servers,
each one run different apps, but I want to use the same apache server for the
Front End(proxy). How to do it? I have tried this:
in httpd.conf:
<Location /weblogic>
SetHandler weblogic-handler
PathTrim /weblogic
</Location>
<IfModule mod_weblogic.c>
MatchExpression abc WebLogicHost=192.1.1.2|WebLogicPort=7100|Debug=ON
MatchExpression xyz WebLogicHost=192.1.1.2|WebLogicPort=7200|Debug=ON
</IfModule>
And got the following error:
[Mon Jun 23 15:43:41 2003] [error] CONFIG_ERROR [line 1309 of ap_proxy.cpp]: Neither
'WebLogicCluster' nor 'WebLogicHost' specified in parameters
Any suggestion are welcome...
Thanks
Leo

Hi,
The SAP Business One workstations read the name of the license service to which they connect from the SLIC table in the SBO-Common database. All Company databases sharing an SBO-Common database use the same license file. In addition, several SBO-Common databases can direct to the same license service.
For more information please refer to:
[License Guide 2007A|https://service.sap.com/~sapidb/011000358700000359212007E.pdf]
hope it helps,
Regards,
Ladislav
SAP Business One Forum Team

Performance of Clustered Managed Servers

WLS 10.3.5 on Solaris10
we have the clustered weblogic10.3.5 domain with two managed servers, which a web app deployed.
we use proxy server (an ohs server) as the frontend host.
we tested for the app login, if both managed servers are started, the login takes about 2 mins.
however if only one managed server is started, the login only takes less 1/2 min.
There is no problem to support two managed servers in the ram and cpu on the server
Why?
where should we start to look into the issue?

Hi,
According to the info you sent, there are 71GB of swap area in use and 7GB of real memory free.
This is not conclusive, as we don't know what is in the swap area. It could be part or the entire JVM for your application. Also, we have to take into consideration shared memory.
I believe you are running many applications in that server, and possible multiple environments.
In order to avoid spending too much time investigating other config issues that might not exist, I think you should try to eliminate the swap to see if this is the issue. I believe that this could be the main issue, based on the info I have so far.
Would be possible for you to stop all or some of the applications running in that server? Then you should check the available RAM (make sure that there are at least 10GB available before starting both managed servers) and restart both managed servers which you have your application running.
Regarding the response times for the login, does it always take the same time to login? You mentioned about 30 seconds, this also seems very high to me. Are your discarding the first login after the server restart? Depending on which framework you are using, it might be interpreting some artifacts or compiling the JSPs in the first execution.
Regards,
Fabio Douek

Problem in running Managed Servers

Hi,
I used the configuration wizard and tried creating a domain ( admin server , 2 managed servers ('new_Server_1' , 'new_Server_2' )) . Admin server listens to the port 7003.
Set up details :
Managed Servers - IP's - Port
new_Server_1 - 1.1.1.10 - 7011
new_Server_2 - 1.1.1.11 - 7011
Node Manager - 1.1.1.10 - 5555
I login into the admin console after the whole set up, node manager was running , admin server wa s running and tried starting the managed servers ,But they failed to start giving the error message -
<Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_05-b04 from Sun Microsystems Inc.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://1.1.1.10:7003 to check if there exists a running admin server at this URL.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jan 9, 2010 11:29:57 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jan 9, 2010 11:29:57 AM CET> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://1.1.1.10:7003 to retrieve the initial configuration.>
<Jan 9, 2010 11:29:58 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\new_Server_1\new_Server_1.log is opened. All server side log events will be written to this file.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\weblogic81\server\lib\DemoTrust.jks.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\bea\jdk142_05\jre\lib\security\cacerts.>
<Jan 9, 2010 11:30:00 AM CET> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "new_Server_1" for domain "integration">
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster new_Cluster on 237.0.0.1:7011.>
<Jan 9, 2010 11:30:03 AM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of new_Cluster.>
<Jan 9, 2010 11:30:36 AM CET> <Error> <Deployer> <BEA-149601> <The deployment framework was unable to resume accepting requests.>
<Jan 9, 2010 11:30:36 AM CET> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup>
The WebLogic Server did not start up properly.
weblogic.management.AbortDeploymentException: weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
at weblogic.t3.srvr.StartupClassService.addDeployment(StartupClassService.java:92)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
Reason: Deployer:149601The deployment framework was unable to resume accepting requests.weblogic.t3.srvr.FatalStartupException: Can't start server due to startup class failure WLI Startup Class - with nested exception:
java.lang.ClassNotFoundException: com.bea.wli.init.BPMStartup
Is this due to the WLI Start up classes set to both admin and managed servers caused this problem / jars missed out while creating a domain ,, ? any pointers to solve this issue.
thank you in advance.
colonel

Hi,
<font color=red>OPTION-A)</font>
If you are able to start the Managed Server using ...the Start Scripts then it means that the Missing class gets included in the Server Classpath ....when we use StartScripts to Start the Server.
If above one works fine...then Just try the following..
Step1). Open the "nodemanager.properties" file and then "startScriptEnabled=true" and "startScriptName=startWebLogic.cmd" ....provide these two entries there....remember if you are using any custom scripts to start your managed server ...then give that scriptname in "startScriptName" parameter..
Step2). restart the Node Manager and then try to start the Managed Server from Admin Console.
for more informations Please refer to "nodemanager.properties" details:
http://download-llnw.oracle.com/docs/cd/E15051_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
<font color=red>OPTION-B)</font>
Start the ManagedServer using the StartScripts and then open the server OUT file....
Find the value of CLASSPATH in that OUT File ...copy the CLASSPATH Value and then Login to Admin Console....
Servers--->Click on ServerName (Example MS1)---> configuration Page ---> ServerStart (TAB)
In this page Paste the CLASSPATH Value which u have copied....in the CLASSPATH Test Field...
Now restart your Server using AdminConsole.
Thanks
Jay SenSharma
Edited by: Jay SenSharma on Jan 30, 2010 6:42 PM
Edited by: Jay SenSharma on Jan 30, 2010 10:57 PM

Creation of Managed servers using WLST on two different machines

Hello,
I am looking for a use case, where i need to create two managed servers to running admin servers
condition 1: Adminserver and managed_server1 will be in same machine.
codition 2: managed_server2 will be in other machine.
Example: AdminSever and managed_server1 will be in the 10.10.10.101 and Managed_server2 will be in 10.10.10.102
I have a code which will create two managed servers in a same machine. How can i modify this code???
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.*;
import weblogic.management.scripting.utils.WLSTInterpreter;
import org.python.util.InteractiveInterpreter;
public class EmbeddedWLST
static InteractiveInterpreter interpreter = null;
EmbeddedWLST()
System.out.println(“Inside the constructor()”);
interpreter = new WLSTInterpreter();
private static void connect()
System.out.println(“Inside the Connect method()”);
StringBuffer buffer = new StringBuffer();
buffer.append(“connect(‘weblogic’,’1qaz2wsx’,'t3://localhost:7001′)”);
System.out.println(“After Connect method()”);
interpreter.exec(buffer.toString());
System.out.println(“at the end of conenct method”);
private static void createServers()
System.out.println(“Inside the CreateServer method()”);
StringBuffer buf = new StringBuffer();
buf.append(startTransaction());
buf.append(“man1=create(‘msEmbedded1′,’Server’)\n”);
buf.append(“man2=create(‘msEmbedded2′,’Server’)\n”);
buf.append(“mach=create(‘machineEmbedded’,'Machine’)\n”);
buf.append(“clus=create(‘clusterEmbedded’,'Cluster’)\n”);
buf.append(“man1.setListenPort(8001)\n”);
buf.append(“man2.setListenPort(9001)\n”);
buf.append(“man1.setCluster(clus)\n”);
buf.append(“man2.setCluster(clus)\n”);
buf.append(“man1.setMachine(mach)\n”);
buf.append(“man2.setMachine(mach)\n”);
buf.append(endTransaction());
//buf.append(“print Script ran successfully … \n”);
interpreter.exec(buf.toString());
private static String startTransaction() {
StringBuffer buf = new StringBuffer();
buf.append(“edit()\n”);
buf.append(“startEdit()\n”);
return buf.toString();
private static String endTransaction() {
StringBuffer buf = new StringBuffer();
buf.append(“save()\n”);
buf.append(“activate(block=’true’)\n”);
return buf.toString();
public static void main(String[] args) throws IOException
System.out.println(“inside the main “);
Runtime rt2 = Runtime.getRuntime();
Process pr2 = rt2.exec(“cmd /c C:\\Oracle\\Middleware\\wlserver_10.3\\server\\bin\\setWLSEnv.cmd “);
BufferedReader br = new BufferedReader(new InputStreamReader(pr2.getInputStream()));
String line = “”;
while ((line = br.readLine()) != null)
System.out.println(line);
new EmbeddedWLST();
connect();
createServers();
Help me out please.
Thanks,
Alok

Hi Shane --
Yes, they were installed from the same disk (I'm pretty sure I did a software update on both but will double-check tonight).
When I try to Import the project, it is grayed out in the 'Choose a File' window. If I double-click the project from the Finder, I get "General Error (41)" -- which is a different one than when I tried it yesterday (when I had no other sequences active).
Also something weird today -- although the edited footage is all linked fine & plays properly, in the timeline most of the footage shows the red "Media Offline" frame for its thumbnail.
Any ideas?
Many thanks!!
-- Sean

Multiple managed servers, Multiple machines and Multiple clusters

Hi,
I have couple of applications to be deployed in high availabliity. I
have been a Tomcat/Apache guy so far. Yesterday night I read the whole admin doc
and tried some installations on the boxes. But have some confusion here.
Since our application is getting commercialised and I like to have 12 managed
serves on each of the three big linux servers and one windows machine as admin
server port 9002. 18 for each application in clustered environment. cluster of
18 for each application.
FIRST CONFUSION is
I want to use only one domain name. So I install weblogic81
on win box and call it dls and then I find out that I need to install weblogic81
as good as the one on win box on linux servers, not surpised, but during the installation
when it asked me for a domain name I was confused. No option to join the existing
domain that I created on my winbox.
Why??? So I type dls again.
Is there a way not to do all this as it may be creatign another domain and just
start nodemanager and not install domain at all ?
SECOND CONFUSION is
When I was installing weblogic on win machine as admin server. I was given
options of adding managed servers and clusters amd machines. So do we need to
have all the managed servers already running before I add them here or I can do
it later.
Thanks n Advance.
Vivke

http://www.rittmanmead.com/2010/07/obiee-11gr1-scaleout-clustering-and-high-availability/
hope it helps

Howto Programatically discover clusters, admin server, managed servers

Hi,
          I'm want to programatically discover what clusters, admins servers, and managed servers exist in my domain.
          I've tried using get MBeanHome, but in order to get that I must know the location of the admin server.
          I'd like to be able to discover from within my program the host name and port of the admin server,and then from there to be able to discover the managed servers and clusters that are running and on what machines/ ports they are running on.
          Is this possible.
          Cheers,
          Keith

Keith Hyland <> writes:
          > I'm want to programatically discover what clusters, admins servers, and managed servers exist in my domain.
          >
          > I've tried using get MBeanHome, but in order to get that I must know the location of the admin server.
          >
          > I'd like to be able to discover from within my program the host name and port of the admin server,and then from there to be able to discover the managed servers and clusters that are running and on what machines/ ports they are running on.
          >
          > Is this possible.
          Its possible, but there are no public APIs for directly doing this. I
          guess you could try looking up the local server's MBean and navigating
          to the admin server's MBean from there.
          You could probably also deduce it from the system property
          weblogic.management.host that you would have set to boot the managed
          server.
          andy
          --

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
          >>>>
          >>>
          >>
          >

Managed servers dies regularly

Hello,
we have two managed servers on two different machines (not
running in a cluster) and both of them die regularly, i.e.
they simply stop. There is nothing in the log files at all
that hints at any problems. Both managed servers are started
via node manager. The admin servers on both machines work fine.
We use WLServer 6.1 sp1 running under Win NT 4. Any ideas?
Cheers

Holger Dewes wrote:
Kumar Allamraju <[email protected]> wrote:
pls clarify whether the process has died or servers are hung?
Hello Kumar,
that's actually a very good question. Does every managed server
run in its own process?Yes.
I will have to investigate this. All I
can say at the moment is that the web console shows the server
as not running. There's a known issue in 61 sp2 that admin console loosing the discovery
of managed servers under load. May be this is what you are seeing.
Then I start it again, and it runs fine... for aRegardless i want you to check the process id of that managed server and
see if it exists or not...
Kumar
while.
Cheers

Two Managed Servers non-clustered problem

Similar Messages

Maybe you are looking for