Clustering problem WLS 5.1

Hi,
we have an environment with 2 clusters ( 1 JSP & 1 EJB)
both cluster consist each of 2 nodes, where 1 JSP and 1 EJB are running on a machine.
although both clusters seem to act correctly at runtime ( and are also visible
in the console as clusters), we get an exception at startup - only at th JSP tier
which is rather confusing:
Do Aug 08 06:11:15 CEST 2002:<E> <WebLogicServer> Unable to bind cluster MO as
"WebLogic" into JNDI tree
javax.naming.NameAlreadyBoundException; remaining name 'weblogic.cluster.WebLogic'
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at weblogic.jndi.toolkit.BasicWLContext_WLStub.bind(BasicWLContext_WLStub.java:1261)
at weblogic.jndi.toolkit.WLContextStub.bind(WLContextStub.java:484)
at weblogic.cluster.ClusterMain.start(ClusterMain.java:290)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1447)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:869)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
None of our clusters is named MO !
Does anybody have a clue ?!

Similar Messages

Clustering Problem on WLS 5.1 sp 2/3

I've set up a multihomed machine running four instances of WLS 5.1 sp2 on
 solaris 7. When I initially added them to a cluster and tested them for
 serving JSPs everything seemed fine. I've since tried deploying an EJB
 (which works in a non clustered server) and I'm suddenly getting the
 following errors:
 stdout:
 ... <E> <MutlicastSocket> Multicast socket receive error:
 java.lang.runtimeException: I/O error opening JAR file from
 file:/export/home0/weblogic/cluster1/serverclasses
 stderr:
 java.util.zip.ZipException: error in opening zip file
 at java.util.zip.ZipFile.open(Native Method)
 at java.util.zip.ZipFile.open(Compiled Code)
 at java.util.zip.ZipFile.<init>(Compiled Code)
 at java.util.zip.ZipFile.<init>(Compiled Code)
 at
 weblogic.boot.ServerClassLoader.deploy(ServerClassLoader.java:141)
 at
 weblogic.cluster.AnnotatedServiceOffer.expandClassPath(AnnotatedServiceOffer
 .java:74)
 at weblogic.cluster.AnnotatedServiceOffer.readObject(Compiled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
 iled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
 Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readArrayList(Compiled
 Code)
 at weblogic.cluster.Announcement.readObject(Announcement.java:73)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
 iled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
 Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled Code)
 at
 weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
 at weblogic.cluster.TMSocket.execute(Compiled Code)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)
 (My EJB is deployed it its expanded directory form, which worked in a single
 server, this error happens repeatedly, regardless of accessing the EJB. The
 weblogic log says that the EJB deployed successfully)
 I've also tried upgrading to sp3, now it cannot even serve jsps, I get the
 following error:
 Wed Jun 14 10:36:06 GMT+01:00 2000: <ServletContext-General> file: init
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: init
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: param
 verbose initialized to: true
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: param
 packagePrefix initialized to: jsp_servlet
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: param
 compileCommand initialized to: /usr/java1.2/bin/javac
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: param
 srcCompiler initialized to weblogic.jspc
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: param
 superclass initialized to null
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: param
 workingDir initialized to: /export/home0/weblogic/cluster1/classfiles
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp: param
 pageCheckSeconds initialized to: 1
 Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 initialization complete
 Wed Jun 14 10:36:24 GMT+01:00 2000:<E> <ServletContext-General> Servlet
 failed with Exception
 java.lang.NullPointerException
 at
 weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
 eplicatedSession.java:339)
 at
 weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
 onContext.java:322)
 at
 weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
 l.java:1104)
 at
 weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
 ava:1007)
 at
 weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
 ava:981)
 at
 weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
 at
 weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
 at
 weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
 at jsp_servlet.simpleSession._jspService(simpleSession.java:64)
 at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :123)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :141)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:744)
 at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:692)
 at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
 Manager.java:251)
 at
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 at
 weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)
 Thanks in advance, tell me if you need more info
 Loz (ECsoft/MyNet)


I got that working. Never mind.
 Amit Bhutra <[email protected]> wrote in message
 news:[email protected]...
 > I am getting same error. How did you resolved it?
 > Weblogic creates a jar file in mycluster/tmp_deployment directory.
 >
 > Do i need to include this jar file in my weblogic.properties?
 >
 > Loz <[email protected]> wrote in message
 > news:[email protected]...
 > > OK, I got rid of the EJB problem by deploying as a jar, how about the
 sp3
 > > problem?
 > >
 > > Loz
 > >
 > > "Loz" <[email protected]> wrote in message
 > > news:[email protected]...
 > > > I've set up a multihomed machine running four instances of WLS 5.1 sp2
 > on
 > > > solaris 7. When I initially added them to a cluster and tested them
 for
 > > > serving JSPs everything seemed fine. I've since tried deploying an EJB
 > > > (which works in a non clustered server) and I'm suddenly getting the
 > > > following errors:
 > > >
 > > > stdout:
 > > > ... <E> <MutlicastSocket> Multicast socket receive error:
 > > > java.lang.runtimeException: I/O error opening JAR file from
 > > > file:/export/home0/weblogic/cluster1/serverclasses
 > > >
 > > > stderr:
 > > > java.util.zip.ZipException: error in opening zip file
 > > > at java.util.zip.ZipFile.open(Native Method)
 > > > at java.util.zip.ZipFile.open(Compiled Code)
 > > > at java.util.zip.ZipFile.<init>(Compiled Code)
 > > > at java.util.zip.ZipFile.<init>(Compiled Code)
 > > > at
 > > > weblogic.boot.ServerClassLoader.deploy(ServerClassLoader.java:141)
 > > > at
 > > >
 > >
 >
 weblogic.cluster.AnnotatedServiceOffer.expandClassPath(AnnotatedServiceOffer
 > > > .java:74)
 > > > at weblogic.cluster.AnnotatedServiceOffer.readObject(Compiled
 > > Code)
 > > > at
 > > >
 > >
 >
 weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
 > > > iled Code)
 > > > at
 > > > weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled
 > > Code)
 > > > at
 > > >
 weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
 > > > Code)
 > > > at
 > > > weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
 > Code)
 > > > at
 > > > weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled
 > > Code)
 > > > at
 > > >
 weblogic.common.internal.WLObjectInputStreamBase.readArrayList(Compiled
 > > > Code)
 > > > at
 > weblogic.cluster.Announcement.readObject(Announcement.java:73)
 > > > at
 > > >
 > >
 >
 weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
 > > > iled Code)
 > > > at
 > > > weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled
 > > Code)
 > > > at
 > > >
 weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
 > > > Code)
 > > > at
 > > > weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
 > Code)
 > > > at
 > > > weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled
 > > Code)
 > > > at weblogic.cluster.TMSocket.execute(Compiled Code)
 > > > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 > > >
 > > > (My EJB is deployed it its expanded directory form, which worked in a
 > > single
 > > > server, this error happens repeatedly, regardless of accessing the
 EJB.
 > > The
 > > > weblogic log says that the EJB deployed successfully)
 > > >
 > > > I've also tried upgrading to sp3, now it cannot even serve jsps, I get
 > the
 > > > following error:
 > > >
 > > > Wed Jun 14 10:36:06 GMT+01:00 2000: <ServletContext-General> file:
 > init
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > init
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > param
 > > > verbose initialized to: true
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > param
 > > > packagePrefix initialized to: jsp_servlet
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > param
 > > > compileCommand initialized to: /usr/java1.2/bin/javac
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > param
 > > > srcCompiler initialized to weblogic.jspc
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > param
 > > > superclass initialized to null
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > param
 > > > workingDir initialized to: /export/home0/weblogic/cluster1/classfiles
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > param
 > > > pageCheckSeconds initialized to: 1
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000: <ServletContext-General> *.jsp:
 > > > initialization complete
 > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<E> <ServletContext-General>
 Servlet
 > > > failed with Exception
 > > > java.lang.NullPointerException
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
 > > > eplicatedSession.java:339)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
 > > > onContext.java:322)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
 > > > l.java:1104)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
 > > > ava:1007)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
 > > > ava:981)
 > > > at
 > > >
 weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
 > > > at
 > > > weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
 > > > at
 > > >
 > weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
 > > > at
 jsp_servlet.simpleSession._jspService(simpleSession.java:64)
 > > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 > > > :123)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 > > > :141)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 > > > l.java:744)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 > > > l.java:692)
 > > > at
 > > >
 > >
 >
 weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
 > > > Manager.java:251)
 > > > at
 > > >
 > >
 >
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 > > > at
 > > > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 > > > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 > > >
 > > > Thanks in advance, tell me if you need more info
 > > >
 > > > Loz (ECsoft/MyNet)
 > > >
 > > >
 > >
 > >
 >
 >

Clustering Problems with WLS 4.5.1

Hi!
          I'm trying to configure a WebLogic 4.5.1 cluster (named "cluster1", on two
          WinNT4 SP5 servers (instances WLS "server A" and "server B")
          When I start each WLS instance in each server, both create a cluster where I
          can only find one WLS server, not two! So I have on each NT server, one
          cluster which contain one WLS server!!!
          To see that, I use the WLS console on the 2 servers, and I see that in each
          server, there is a cluster "cluster1" and only one server ("server A" in the
          first NT Server, and "server B" in the second one).
          The two server are identical, same OS, same SP, same WLS version, same WLS
          Service Pack, same IP Multicast address, same TCP port (7001), and there is
          no multihoming.
          I can't see how to put the two WLS servers in the same cluster!
          Do someone have a clue?
          Best regards,
          Jean-Michel Gautreau
          [email protected]


Here is a console screendump, taken after the two WLS servers' boot.
          I forgot to tell we have installed WLBS on both NT servers, before
          installing WebLogic 4.5.1. Is there a problem in the communication between
          the two servers? I'm not sure but I feel it is a network problem, the two NT
          servers don't seem to communicate correctly through WLBS with the WLS
          cluster?
          Any hint?
          [dump.bmp]

WLS 5.1 SP8 Clustering problems

Hi all,
 I am trying to create a cluster with 2 instances of WLS and third WLS
 instance to be used as a proxy. The two servers in the cluster have joined
 the Multicast Address correctly (I hope, because thats what the log file
 says). Now the proxy also started succesfully. But when I make a request
 for a JSP page, it is going into an infinite loop. The request is not going
 beyond the proxy i think, because, on the proxy, it says *.jsp:init.
 Then i tried to use ISAPI plug-in to call this JSP, but i am getting an
 ISAPI error (I don't know why it is looking for localhost:7001 when I have
 specified
 WebLogicCluster=192.200.1.251:7001,192.200.1.252:7001,192.200.1.253:7001
 in the iisproxy.ini File:
 Internal Server Error
 Reason:Cannot connect to WebLogic: timed out after 10 seconds. Cluster list:
 localhost:7001
 Line 427 of iisproxy.cpp
 Can Some one help ?
 Thank You in advance.
 Ramesh


Seems ISAPI plugin could not locate iisproxy.ini.
 Here is the search order:
 - current directory (same as the dll)
 - WebLogic installation directory (finds it from the regirstry) -
 c:\weblogic
 Try to save iisproxy.ini at the same location of the dll.
 "ramesh" <[email protected]> wrote in message
 news:[email protected]...
 > Hi all,
 >
 > I am trying to create a cluster with 2 instances of WLS and third WLS
 > instance to be used as a proxy. The two servers in the cluster have
 joined
 > the Multicast Address correctly (I hope, because thats what the log file
 > says). Now the proxy also started succesfully. But when I make a request
 > for a JSP page, it is going into an infinite loop. The request is not
 going
 > beyond the proxy i think, because, on the proxy, it says *.jsp:init.
 >
 > Then i tried to use ISAPI plug-in to call this JSP, but i am getting an
 > ISAPI error (I don't know why it is looking for localhost:7001 when I have
 > specified
 > WebLogicCluster=192.200.1.251:7001,192.200.1.252:7001,192.200.1.253:7001
 > in the iisproxy.ini File:
 >
 > Internal Server Error
 > Reason:Cannot connect to WebLogic: timed out after 10 seconds. Cluster
 list:
 > localhost:7001
 > Line 427 of iisproxy.cpp
 >
 > Can Some one help ?
 >
 > Thank You in advance.
 >
 > Ramesh
 >
 >
 >

Communication between Clusters Problem

Hi all
 1. Is it possible for a bean, being hosted in a cluster to call a bean which is hosted in another cluster?
 We have a problem with the role information, which gets wrong at every second call.
 We have the following setup:
 - A cluster called "web-cluster" consists of two machines with one weblogic 9.2 server per machine.
 - We have another cluster called "ID-Cluster" with the same setup (2 Machines, 2 WLS).
 - In the "Web-Cluster" we have a bean deployed called "SecurityProxy".
 - In the "Web-Cluster" we have a Web-Application ("WebApp") deployed which use the "SecurityProxy"
 - In the ID-Cluster we have a Bean called "SecurityBean". - The SecurityProxy makes a login to the ID-Cluster with a technical user, role "techSecurityProxy".
 - Calls from SecurityProxy to SecurityBean alternate with each call.
 Problem:
 User logs in to the "WebApp" and gets role "customer" associated.
 First call from SecurityProxy to SecurityBean: call is done with the correct role "techSecurityProxy" second call is done with the role "customer" !?! It seams as if the security context gets propageted...
 We have no trust defined between the clusters and we have no runas configured in den deployment descriptors. Can anyone help?

Frank, the security context is propagted between the JVM's. I have asked BEA support to specify if this can be configured or turned off to resolve another issue I have but to date I have not had a response.
 In your case can you not add the new principle like -useProxy to authenticated users which allows them to use the proxy once they are authenticated?
 
 Hussein Badakhchani
 London Middleware

Problems - WLS 10.0 web service client

I'm having a few issues with WLS 10.0 web service client.
 I generated a service control from the WSDL. The service is provided by a 3rd party (non-WLS) at another company. I generated the control within my web project and it's deployed as part of the web application. I experience the following problems with the service control API:
 1) The methods setKeyStore(), setTrustStore(), setClientCert() all seem to be ignored - the server always uses the values set in the server's environment definition. Note - the setEndpointAddress() seems to work.
 2) The client request does not set the 'Content-Type' HTTP header correctly (it's set to text/html) - I have no way to override this via the service control API (that I can see).
 3) I don't see any way/place to turn on more detailed tracing of what's going on internally with the service control invocation - is there a way to enable a detailed trace log of what is happening within the service control?
 Note: I'm able to call the web service via the test client (after importing the 3rd party server cert into my local cacerts).
 Thanks,
 [email protected]

Thank you for the reply..
But im still geting the same error. I have tried to include all the libraries in JWSDP pack but still.. I have managed to narrow down the place where the error occures.. It actually happens when I try to get the WebService Client Servant which is located in the package LSC:
---> LSC.LWServiceGenClient.LWS_Impl service = new LSC.LWServiceGenClient.LWS_Impl();
LSC.LWServiceGenClient.LWSServantInterface lagerServiceServant = LSC.LWServiceGenClient.LWSServantInterface_Stub)service.getLWSServantInterfacePort();
return lagerServiceServant;
Could something be wrong with the way I package the Jar? I'm using Sun One Studio and have tried including the 5 packages the application consists of; I have tried including just the files; moving the main class to <root>.. Still same problem..
Or could there be some different fundemental thingy I have forgotten ??
thanks
Aqoi

Clustering Problem

 Hi Guys ,
 How should scaling of Weblogic applications being accessed by t3 protocol to be
 done .
 Consider the following scenario :
 Weblogic server A hosts an application which in turn uses t3 protocol to contact
 applications hosting in Weblogic Server B. Web Client talks to Weblogic Server
 A using IIS Proxy dll. While scaling this set up we can Cluster applications running
 on Weblogic Server A .IIS Proxy dll is able to route the requests to Weblogic
 Server A clusters.
 How should the Weblogic Server B cluster setup to be done ?
 Any thoughts on this is welcome.
 Thanks & Regards,
 Kumar


 Actually architecture is such that we need to have Server B separately as it may
 host some common functionalities used by multiple applications . So we cannot
 merge those two. I am using iisproxy.dll to point to my cluster address for Server
 A (Comma separated address) and it is working fine.
 Now my Server B is being used by Server A (it is a configuration XML file) where
 we specify server B's IP and port number , use t3 protocol to contact Server B.
 I am not having a DNS Server to resolve the DNS Name to multiple IP addresses
 of cluster. So I am not sure as to how to specify the cluster address for Server
 B.
 Note: As we have an option of specifying comma separated IP address values in
 iisproxy.ini file . Is there any way to specify the cluster address for Server
 B.
 "Wenjin Zhang" <[email protected]> wrote:
 >
 >My suggestion is, add your server A to your cluster B. Your IIS proxy
 >plugin will
 >point to your cluster and you configure iisproxy.ini with your cluster
 >address.
 >You shouldn't have problem to use comma seperated address.
 >
 >
 >
 >"Kumar" <[email protected]> wrote:
 >>
 >>Thanks a lot.
 >>Firstly I may be having JSP/Servlets also in Server B.
 >>
 >>Secondly If I don't have an DNS Server to resolve the Cluster Address
 >>to multiple
 >>IP should I be using comma separated IP address as Cluster Address.
 >>
 >>Let me try further and get back to you.
 >>
 >>
 >>
 >>
 >>"Wenjin Zhang" <[email protected]> wrote:
 >>>
 >>>Simply speaking, if cluster B is used to host applications like your
 >>>EJB and JMS,
 >>>no special configuration on cluster B is required. The only thing you
 >>>need take
 >>>care is, cluster A should use cluster address of cluster B to contact
 >>>cluster
 >>>B. I am not sure if you also use B to host servlets/JSPs.
 >>>
 >>>
 >>>"Kumar" <[email protected]> wrote:
 >>>>
 >>>>Hi Guys ,
 >>>>
 >>>>How should scaling of Weblogic applications being accessed by t3 protocol
 >>>>to be
 >>>>done .
 >>>>
 >>>>Consider the following scenario :
 >>>>Weblogic server A hosts an application which in turn uses t3 protocol
 >>>>to contact
 >>>>applications hosting in Weblogic Server B. Web Client talks to Weblogic
 >>>>Server
 >>>>A using IIS Proxy dll. While scaling this set up we can Cluster applications
 >>>>running
 >>>>on Weblogic Server A .IIS Proxy dll is able to route the requests
 >to
 >>>>Weblogic
 >>>>Server A clusters.
 >>>>
 >>>>How should the Weblogic Server B cluster setup to be done ?
 >>>>
 >>>>Any thoughts on this is welcome.
 >>>>
 >>>>Thanks & Regards,
 >>>>Kumar
 >>>>
 >>>
 >>
 >

Clustering problems and load balancing question

          I am using Weblogic 6.1. My Windows NT environment consists of 10 web client-simulator
          machines, 2 App. Server machines and one database server machine. I have defined
          one cluster on each app. server. Each cluster is running 3 Weblogic instances, or
          so it should be when I fix my problems!
          My questions/problems are the following:
          1. Can I use a software dispatcher to perform workload balancing between the 2 weblogic
          clusters? That is, the client-simulator machines send the requests to the software
          dispatcher which performs workload balancing between the 2 Weblogic clusters. The
          clusters perform round-robin amongst all instances. Note that the documentation only
          talks about Hardware Balancing.
          2. I am having problems with my multicast IP addresses. For instance, on one App.
          Server machine, I am using the multicast IP address: 239.0.0.1 for MyCluster. When
          I start the Admin Server, I get a JDBC error: "... multicast socket error: Request
          Time Out". I have used the utils.MulticastTest utility which shows the packets not
          being received:
          I (S1) sent message num 1
          I (S1) sent message num 2
          I (S1) sent message num 3
          I (S1) sent message num 4
          What am I doing wrong?
          3. Re. the cluster configuration:
          NOTE: I have executed my workload using 2 independent App. Server machines with a
          software dispatcher - no clustering. Each App. Server used a jdbc connection pool
          of 84 database connections. The db connections happened to become my bottleneck.
          When I tried to increase the number of connections in the jdbc pool, throughput decreased
          dramatically. Thus, I decided to add a cluster of Weblogic instances to each one
          of my 8 x 900Mhz machines in order to scale up. Unfortunatly, adding clusters have
          not been that simple a task - probably because I am totally new to the Web Application
          Server world!
          Here is what I've got so far:
          I have obtained 3 static IP addresses for the 3 instances of Weblogic instances that
          I wish to run within the cluster. All servers in the cluster use port number 80.
          There is a corresponding DNS entry for each IP address. My base assumption is that
          one of these instances will double up as the Administration Server... Is it true,
          or do I need to define a separate Admin server if I wish to run 3 Weblogic instances
          (each with a connection pool of 84 database connections for a total of 252 database
          connections)?
          Do I need to re-deploy my applications for the cluster? And if so, would this explain
          why I am having problem starting my Admin Server?
          I think this is it for now. Any help will be greatly appreciated!
          Thanks in advance,
          Guylaine.


          Guylaine Cantin wrote:
          > I am using Weblogic 6.1. My Windows NT environment consists of 10 web client-simulator
          > machines, 2 App. Server machines and one database server machine. I have defined
          > one cluster on each app. server. Each cluster is running 3 Weblogic instances, or
          > so it should be when I fix my problems!
          >
          > My questions/problems are the following:
          >
          > 1. Can I use a software dispatcher to perform workload balancing between the 2 weblogic
          > clusters? That is, the client-simulator machines send the requests to the software
          > dispatcher which performs workload balancing between the 2 Weblogic clusters. The
          > clusters perform round-robin amongst all instances. Note that the documentation only
          > talks about Hardware Balancing.
          >
          We also support software load balancers (for e.g. resonate)
          The software dispatcher should be intelligent enough to decode the
          cookie and route the request to the appropriate servers. This is
          necessary to maintain sticky load balancing.
          > 2. I am having problems with my multicast IP addresses. For instance, on one App.
          > Server machine, I am using the multicast IP address: 239.0.0.1 for MyCluster. When
          > I start the Admin Server, I get a JDBC error: "... multicast socket error: Request
          > Time Out". I have used the utils.MulticastTest utility which shows the packets not
          > being received:
          >
          > I (S1) sent message num 1
          > I (S1) sent message num 2
          > I (S1) sent message num 3
          > I (S1) sent message num 4
          > ...
          >
          > What am I doing wrong?
          >
          You should run the above utility from multiple windows and see if each
          of them being recognized or not.
          i.e. java utils.MulticastTest -N S1 -A 239.0.0.1
          java utils.MulticastTest -N S1 -A 239.0.0.1
          > 3. Re. the cluster configuration:
          >
          > NOTE: I have executed my workload using 2 independent App. Server machines with a
          > software dispatcher - no clustering. Each App. Server used a jdbc connection pool
          > of 84 database connections. The db connections happened to become my bottleneck.
          > When I tried to increase the number of connections in the jdbc pool, throughput decreased
          > dramatically. Thus, I decided to add a cluster of Weblogic instances to each one
          > of my 8 x 900Mhz machines in order to scale up. Unfortunatly, adding clusters have
          > not been that simple a task - probably because I am totally new to the Web Application
          > Server world!
          >
          You have to stress test your application several times and set
          maxCapacity of the conn pool accordingly.
          > Here is what I've got so far:
          >
          > I have obtained 3 static IP addresses for the 3 instances of Weblogic instances that
          > I wish to run within the cluster. All servers in the cluster use port number 80.
          > There is a corresponding DNS entry for each IP address. My base assumption is that
          > one of these instances will double up as the Administration Server... Is it true,
          > or do I need to define a separate Admin server if I wish to run 3 Weblogic instances
          > (each with a connection pool of 84 database connections for a total of 252 database
          > connections)?
          BEA recommends to use Admin server for administrative tasks only
          like configuring new deployments, jdbc conn pools, adding users etc..
          It's not a good idea to have admin server part of cluster.
          >
          > Do I need to re-deploy my applications for the cluster? And if so, would this explain
          > why I am having problem starting my Admin Server?
          >
          You have to target all your apps to the Cluster.
          > I think this is it for now. Any help will be greatly appreciated!
          >
          > Thanks in advance,
          >
          > Guylaine.
          >

Unclosed files problem:WLS 7.0 on HP-UX

We are running WLS 7.0 on HP-UX. As the load increases we are facing problems.
The symptoms are
1. The number of threads for the process doest no increase. But for every unit
of load the number of open files increases
2. At some point it reaches max number of open files
3. After that our application can not proceed, since we creat some oracle , socket
connections. Since the number of open files reaches limit no other files/socket
can be opened
4. Our application uses pool. We have monitored our application pools and we are
not creating these unclosed file descriptors
Would be of great help if someone could provide us help
Thnx

lsof will help you to find all the open files and from that you can come to
understanding of what files are opened.
"Siva" <[email protected]> wrote in message
news:[email protected]..
>
We are running WLS 7.0 on HP-UX. As the load increases we are facingproblems.
The symptoms are
1. The number of threads for the process doest no increase. But for everyunit
of load the number of open files increases
2. At some point it reaches max number of open files
3. After that our application can not proceed, since we creat some oracle, socket
connections. Since the number of open files reaches limit no otherfiles/socket
can be opened
4. Our application uses pool. We have monitored our application pools andwe are
not creating these unclosed file descriptors
Would be of great help if someone could provide us help
Thnx

BPM Clustering on WLS

Does anyone have a decent cookbook for setting up a BPM cluster in WLS? We are deploying this configuration and have no problems on the WLS side but major problems with BPM. Unfortunately the documentation for this is rather thin and not too intuitive. Any help would be greatly appreciated.
TIA,
IGS

You need to increase the JTA timeout value in WLS to something higher (like 300). Some of the BPM engine transactions take longer than Weblogic's default.
Please refer to the following document in MetaLink for details:
Doc ID: 780946.1

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

Multi-tiers clustering problem: NameNotFoundException

Hi All
          I am trying multi-tier clustering when I encounter an unexpected naming
          exception. Following is the scenario.
          1) There are two clusters: [webcluster] and [servercluster]. They are
          in the same administration domain.
          2) Each of them has only one server: [cscweb] and [cscserver].
          3) Cluster addresses are [node177.truetel.com.tw:7001] and
          [node177.truetel.com.tw:7003] respectively.
          4) war files are deployed to [webcluster] while ejb jars are
          deployed to [servercluster], supposedly.
          My problem is that, if all the war files and jar files are deployed on
          BOTH clusters, then the application runs smoothly. However,
          if they are deployed as in step 4, then the unexpected
          javax.naming.NameNotFoundException will be thrown.
          If I also deployed SOME of the ejb jars to the [webcluster], then the
          application can run until it fails to locate the ejbs not deployed on
          the [webcluster]. A javax.naming.NameNotFoundException will be
          thrown then.
          It seems to be a JNDI problem where ejbs not in the same cluster
          could not be located. Can this be fixed?
          Any help will be appreciated,
          Lynch


Hi All
          I am trying multi-tier clustering when I encounter an unexpected naming
          exception. Following is the scenario.
          1) There are two clusters: [webcluster] and [servercluster]. They are
          in the same administration domain.
          2) Each of them has only one server: [cscweb] and [cscserver].
          3) Cluster addresses are [node177.truetel.com.tw:7001] and
          [node177.truetel.com.tw:7003] respectively.
          4) war files are deployed to [webcluster] while ejb jars are
          deployed to [servercluster], supposedly.
          My problem is that, if all the war files and jar files are deployed on
          BOTH clusters, then the application runs smoothly. However,
          if they are deployed as in step 4, then the unexpected
          javax.naming.NameNotFoundException will be thrown.
          If I also deployed SOME of the ejb jars to the [webcluster], then the
          application can run until it fails to locate the ejbs not deployed on
          the [webcluster]. A javax.naming.NameNotFoundException will be
          thrown then.
          It seems to be a JNDI problem where ejbs not in the same cluster
          could not be located. Can this be fixed?
          Any help will be appreciated,
          Lynch

Weblogic Clustering Problem

Hi,
I am tring to set up clustering on my laptop(Windows XP home OS) using Medrec Tutorials for Weblogic SP4.Its giving me SocketException.Same had worked when tried on Win2000 OS.I tried with SP2 also but its giving the same exception.
Please let me know if anyone encountered similar pbm and resolved it.Thanks in advance.
Please find the log below:
<Jul 29, 2006 11:22:01 PM IST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "MedRec2" for domain "clusterdomain">
<Jul 29, 2006 11:22:03 PM IST> <Error> <Cluster> <BEA-000116> <Failed to join cluster MedRecCluster at address 230.0.0.1 due to: java.net.SocketException: error setting options.
java.net.SocketException: error setting options
at java.net.PlainDatagramSocketImpl.join(Native Method)
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:172)
at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:43)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:924)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
>
<Jul 29, 2006 11:22:03 PM IST> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.server.ServerLifecycleException: Failed to listen on multicast address
weblogic.server.ServerLifecycleException: Failed to listen on multicast address
at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:48)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:924)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Caused by: java.net.SocketException: error setting options
at java.net.PlainDatagramSocketImpl.join(Native Method)
at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:172)
at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:43)
... 4 more
>
<Jul 29, 2006 11:22:03 PM IST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.server.ServerLifecycleException: Failed to listen on multicast addresserror setting options>
The WebLogic Server did not start up properly.
Exception raised: 'java.net.SocketException: error setting options'
Reason: weblogic.server.ServerLifecycleException: Failed to listen on multicast addresserror setting options
Thanks
Raju

Hi,
Actually i tried with Weblogic 8.1 sp2 and sp4 but same problem.I just tried setting up clusters on Windows 2000 it works fine.Seems to be a problem with windows XP home.
Any idea if same problem occurs with Win XP professional?
Anyway thanx for the reply.
Thanks
Raju

JMX over t3 problem (WLS 10.0)

Has anyone attempted to retrieve JMX data from a WebLogic 10 instance and succeeded? I am attempting to connect to a out-of-the-box installation of Weblogic Server. I am using the sample code at http://e-docs.bea.com/wls/docs100/jmx/accessWLS.html#wp1112969, yet whenever I connect I get the exception pasted below. Nothing shows up in the servers logs, but I have verified with TCPdump that the connection is occurring.
If I connect via iiop instead of t3 and set a default name/password on the iiop config page, it works. Doing so is rather insecure so I'd like to avoid that.
The exception is:
Exception in thread "main" java.io.IOException
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:156)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
at MyConnection.initConnection(MyConnection.java:55)
at MyConnection.main(MyConnection.java:123)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.io.EOFException]
at weblogic.jrmp.Context.lookup(Context.java:189)
at weblogic.jrmp.Context.lookup(Context.java:195)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:144)
... 5 more
Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.io.EOFException
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:273)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
at weblogic.jrmp.RegistryImpl_Stub.lookup(Unknown Source)
at weblogic.jrmp.Context.lookup(Context.java:185)
... 8 more
Caused by: java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:243)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
... 13 more

It turned out my problem was my classpath. I pared it down to just wlclient.jar and wljxmclient.jar and that did it.

Clustering 5 wls

Hello,
 I set up a cluster of 5 wls (451) with the default values, on
 a LAN, on 5 computers, same config.
 They joined the cluster together without any problem.
 But, when calling mulitple methods on a Stateless session bean,
 the time between calls were really slow: 4 to 10 seconds.
 I tested with 2 Wls only in a cluster. It does work, really fast.
 1. What did I miss?
 2. How to configure wls so that it does not renew contacts to
 other wls too often?
 Thierry


The short answer to #1 is to set the following tuneables on the client
 side:
 java -Dweblogic.system.executeThreadCount=10
 -Dweblogic.system.percentSocketReaders=50 <your client program>
 The default settings are 5 and 33. Thus the number of socket reading
 threads on the client was restricted to a maximum of 2 (33% of 5). As
 you discovered, this can cause problems when there are > 3 servers in
 the cluster.
 This has been documented in the tuning guide which is part of the WL5.1
 docs.
 Srikant, [email protected], http://www.weblogic.com/, etc.
 Thierry Janaudy wrote:
 > Hello,
 >
 > I set up a cluster of 5 wls (451) with the default values, on
 > a LAN, on 5 computers, same config.
 >
 > They joined the cluster together without any problem.
 >
 > But, when calling mulitple methods on a Stateless session bean,
 > the time between calls were really slow: 4 to 10 seconds.
 >
 > I tested with 2 Wls only in a cluster. It does work, really fast.
 >
 > 1. What did I miss?
 >
 > 2. How to configure wls so that it does not renew contacts to
 > other wls too often?
 >
 > Thierry

Clustering problem WLS 5.1

Similar Messages

Maybe you are looking for