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
>>>>
>>>
>>
>
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:<I> <ServletContext-General> file: init
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: init
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
verbose initialized to: true
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
packagePrefix initialized to: jsp_servlet
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
compileCommand initialized to: /usr/java1.2/bin/javac
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
srcCompiler initialized to weblogic.jspc
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
superclass initialized to null
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
workingDir initialized to: /export/home0/weblogic/cluster1/classfiles
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
pageCheckSeconds initialized to: 1
Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <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:<I> <ServletContext-General> file:
> init
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > init
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > param
> > > verbose initialized to: true
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > param
> > > packagePrefix initialized to: jsp_servlet
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > param
> > > compileCommand initialized to: /usr/java1.2/bin/javac
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > param
> > > srcCompiler initialized to weblogic.jspc
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > param
> > > superclass initialized to null
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > param
> > > workingDir initialized to: /export/home0/weblogic/cluster1/classfiles
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
> > param
> > > pageCheckSeconds initialized to: 1
> > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <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 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.
>
-
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?<p>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.</p>
<p>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?</p>
<p>
Hussein Badakhchani
London Middleware
</p> -
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
-
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
RajuHi,
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 -
Weblogic6.0 clustering problem
Hi All
I need to test clustering features in weblogic6.0 using
WindowsNT machine.I downloaded the wl6.0 and installed on my NT
machine.I added one sever like MSever in the ADMIN console.I started
StartManagedWebLogic with severname and admin host address.I am gettin
these errors.can any body help how to solve this problem.I appreciate
early reply.
D:\weblogic6\wlserver6.0\config\NAMDomain>startManagedWebLogic MServer
http://137.168.67.164:7001
D:\weblogic6\wlserver6.0>set
PATH=.\bin;D:\weblogic6\wlserver6.0\bin;D:\weblogic6\jdk130\bin;C:\Program
Files\Oracle\jre\1.1.7\bin;D:\jdk1.2.2\bin;D:\j2sdkee1.2.2\bin;D:\weblogic\bin;D:\OraHome1\bin;C:\WINNT\sys
D:\weblogic6\wlserver6.0>set
CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
D:\weblogic6\wlserver6.0>"D:\weblogic6\jdk130\bin\java" -hotspot -ms64m
-mx64m -classpath .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
-Dweblogic.Domain=NAMDomain -Dweblogic.Name=MServer
"-Dbea.home=D:\weblogic6"
Starting WebLogic Server ....
<Feb 20, 2001 11:21:47 AM EST> <Notice> <Management> <Loading
configuration file .\config\NAMDomain\config.xml ...>
<Feb 20, 2001 11:21:50 AM EST> <Info> <Logging> <Only log messages of
severity "Error" or worse will be displayed in this window. This can be
changed at Admin Console> NAMDomain> Servers> MServer> Logging> Debug
Starting Cluster Service ....
<Feb 20, 2001 11:21:58 AM EST> <Notice> <WebLogicServer> <WebLogic
Server started>
<Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <Unable to
create a server socket for: FA2880/137.168.67.112, port: 7001.
java.net.BindException: Address in use: JVM_Bind Perhaps the address
FA2880/1
<Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <The
WebLogic Server is no longer listening for connections. You should
probably restart it.>
<Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <The shutdown
sequence has been initiated.>
<Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Disconnecting from
cluster MCluster>
<Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Multicast socket
receive error: java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:392)
at
weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:128)
at
weblogic.cluster.MulticastManager.execute(MulticastManager.java:290)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks in advance
Nagesh
Hi All
I need to test clustering features in weblogic6.0 using
WindowsNT machine.I downloaded the wl6.0 and installed on my NT
machine.I added one sever like MSever in the ADMIN console.I started
StartManagedWebLogic with severname and admin host address.I am gettin
these errors.can any body help how to solve this problem.I appreciate
early reply.
D:\weblogic6\wlserver6.0\config\NAMDomain>startManagedWebLogic MServer
http://137.168.67.164:7001
D:\weblogic6\wlserver6.0>set
PATH=.\bin;D:\weblogic6\wlserver6.0\bin;D:\weblogic6\jdk130\bin;C:\Program
Files\Oracle\jre\1.1.7\bin;D:\jdk1.2.2\bin;D:\j2sdkee1.2.2\bin;D:\weblogic\bin;D:\OraHome1\bin;C:\WINNT\sys
D:\weblogic6\wlserver6.0>set
CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
D:\weblogic6\wlserver6.0>"D:\weblogic6\jdk130\bin\java" -hotspot -ms64m
-mx64m -classpath .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
-Dweblogic.Domain=NAMDomain -Dweblogic.Name=MServer
"-Dbea.home=D:\weblogic6"
Starting WebLogic Server ....
<Feb 20, 2001 11:21:47 AM EST> <Notice> <Management> <Loading
configuration file .\config\NAMDomain\config.xml ...>
<Feb 20, 2001 11:21:50 AM EST> <Info> <Logging> <Only log messages of
severity "Error" or worse will be displayed in this window. This can be
changed at Admin Console> NAMDomain> Servers> MServer> Logging> Debug
Starting Cluster Service ....
<Feb 20, 2001 11:21:58 AM EST> <Notice> <WebLogicServer> <WebLogic
Server started>
<Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <Unable to
create a server socket for: FA2880/137.168.67.112, port: 7001.
java.net.BindException: Address in use: JVM_Bind Perhaps the address
FA2880/1
<Feb 20, 2001 11:21:58 AM EST> <Emergency> <WebLogicServer> <The
WebLogic Server is no longer listening for connections. You should
probably restart it.>
<Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Feb 20, 2001 11:21:58 AM EST> <Alert> <WebLogicServer> <The shutdown
sequence has been initiated.>
<Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Disconnecting from
cluster MCluster>
<Feb 20, 2001 11:21:59 AM EST> <Error> <Cluster> <Multicast socket
receive error: java.net.SocketException: socket closed
java.net.SocketException: socket closed
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(DatagramSocket.java:392)
at
weblogic.cluster.FragmentSocket.receive(FragmentSocket.java:128)
at
weblogic.cluster.MulticastManager.execute(MulticastManager.java:290)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks in advance
Nagesh
-
HTTPSession clustering problem
Can anyone help with my problems with HTTP session clustering?
We have 2 clustered weblogic servers to which we are proxying jsp
requests. Ideally I would like the jsp requests to be serviced by either
server in the cluster, but if they go to a server other than that on
which the session was created i get a message 'Cookie Error : Primary !=
me'.
If i set up one of the servers as the primary, so all requests go to
this unless it is offline in which case they go to the secondary, then i
can get the session information to failover correctly - but when the
primary comes back up and requests are routed though it again i get the
same 'primary != me' message.
Is it possible to configure weblogic such that jsp requests can be
serviced by any server in the cluster regardless of on which server the
session was created? and if so how?
We are using WL451 SP7 on solaris, with Understudy proxying the jsp
requests.
Thanks,
Steve
Correct, Understudy isn't smart enough to direct requests in the same
session to the same server. If you are intent on using Understudy as a
proxy, you can use JDBC Session persistence instead of in memory session
replication. That way, all nodes in the cluster have equal access to
session state. However, this is a much slower solution.
I would recommend switching to Weblogic, NES, or IIS as your proxy,
with an appropriate plugin. See:
http://www.weblogic.com/docs45/admindocs/cluster.html for more
information.
Rich Nill wrote:
>
> Matt,
>
> I believe the problem here is that you are not using Weblogic itself, or a
> Weblogic web server plug-in, to proxy requests to your cluster. You must use
> Weblogic or a plug-in to forward the HTTP requests to the cluster as these
> proxies are smart enough to handle Weblogic HttpSession stickiness.
> Understudy won't do this for you.
>
> Rich
>
> Matt Holland wrote:
>
> > Can anyone help with my problems with HTTP session clustering?
> >
> > We have 2 clustered weblogic servers to which we are proxying jsp
> > requests. Ideally I would like the jsp requests to be serviced by either
> > server in the cluster, but if they go to a server other than that on
> > which the session was created i get a message 'Cookie Error : Primary !=
> > me'.
> > If i set up one of the servers as the primary, so all requests go to
> > this unless it is offline in which case they go to the secondary, then i
> > can get the session information to failover correctly - but when the
> > primary comes back up and requests are routed though it again i get the
> > same 'primary != me' message.
> >
> > Is it possible to configure weblogic such that jsp requests can be
> > serviced by any server in the cluster regardless of on which server the
> > session was created? and if so how?
> >
> > We are using WL451 SP7 on solaris, with Understudy proxying the jsp
> > requests.
> >
> > Thanks,
> > Steve
-
Weblogic clustering problem (4.0.4)
We currently have two Weblogic servers setup in a clustered configuration.
The cluster seems to operate fine and the clients can use both servers. The
only problem I have seen is that if the client is not shutdown gracefully then
it's connections to the Primary Weblogic server get closed but the ones that
are on the second server in the cluster remain open. Is there a timeout I can
specify in the server to automatically kill those client connections?
Robert
I found answer to my question.
Yes it is available.
It is now “Oracle Communications Converged Application Server” -
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]
-
I am not sure if this issue belongs to this forum. If not, please let me know and I will post it in the appropriate forum.
My application has clustered remote SLSBs with "FirstAvaliable" policy.
The BMP Entity Beans are set for cache invalidation as they exist at local level only. They is no clustering of entity beans.
I am using Commit Option A.
I want cache to invalidate bean on all nodes except the node it was accessed from.
Here the cache is being cleared even on the node it was last accessed from.
I executed a business method on the same node (due to FirstAvailable) and here is the list of methods encountered.
setEntityContext
ejbFindByPrimaryKey
ejbActivate
ejbLoad
getAllAccounts
ejbStore
setEntityContext
ejbActivate
ejbLoad
getAllAccounts
ejbStore
setEntityContext
ejbActivate
ejbLoad
getAllAccounts
ejbStore
My expectation is that second and third time, in addition to my business method, only ejbLoad and ejbStore should be executed.
After info from guides and forum topics, I have configured as under :
cluster-service.xml
============
I am using the default behaviour of JBoss-Cluster based bridge
jboss.cache:service=InvalidationManager
${jboss.partition.name:DefaultPartition}
DefaultJGBridge
jboss:service=${jboss.partition.name:DefaultPartition}
jboss.cache:service=InvalidationManager
standardjboss.xml
============
Container Configuration is defined as under : (Commit Option is A)
<container-configuration>
<container-name>Standard BMP 2.x EntityBean with cache invalidation</container-name>
<call-logging>false</call-logging>
<invoker-proxy-binding-name>entity-rmi-invoker</invoker-proxy-binding-name>
<sync-on-commit-only>true</sync-on-commit-only>
<insert-after-ejb-post-create>false</insert-after-ejb-post-create>
<container-interceptors>
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor
org.jboss.ejb.plugins.LogInterceptor
org.jboss.ejb.plugins.SecurityInterceptor
org.jboss.ejb.plugins.TxInterceptorCMT
org.jboss.ejb.plugins.EntityCreationInterceptor
org.jboss.ejb.plugins.EntityLockInterceptor
org.jboss.ejb.plugins.EntityInstanceInterceptor
org.jboss.ejb.plugins.EntityReentranceInterceptor
org.jboss.resource.connectionmanager.CachedConnectionInterceptor
org.jboss.ejb.plugins.EntitySynchronizationInterceptor
org.jboss.cache.invalidation.triggers.EntityBeanCacheBatchInvalidatorInterceptor
org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor
</container-interceptors>
<instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
<instance-cache>org.jboss.ejb.plugins.InvalidableEntityInstanceCache</instance-cache>
<persistence-manager>org.jboss.ejb.plugins.BMPPersistenceManager</persistence-manager>
<locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
<container-cache-conf>
<cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
<cache-policy-conf>
<min-capacity>50</min-capacity>
<max-capacity>1000000</max-capacity>
<overager-period>300</overager-period>
<max-bean-age>600</max-bean-age>
<resizer-period>400</resizer-period>
<max-cache-miss-period>60</max-cache-miss-period>
<min-cache-miss-period>1</min-cache-miss-period>
<cache-load-factor>0.75</cache-load-factor>
</cache-policy-conf>
</container-cache-conf>
<container-pool-conf>
100
</container-pool-conf>
<commit-option>A</commit-option>
</container-configuration>
jboss.xml
======
<?xml version="1.0"?>
<security-domain>java:/jaas/defaultLdap</security-domain>
<enterprise-beans>
<ejb-name>ejb/ApplicationService</ejb-name>
<security-domain>java:/jaas/defaultLdap</security-domain>
<resource-ref>
<res-ref-name>jdbc/OracleDS</res-ref-name>
<jndi-name>java:/jdbc/OracleDS</jndi-name>
</resource-ref>
True
<cluster-config>
<home-load-balance-policy>
org.jboss.ha.framework.interfaces.FirstAvailable
</home-load-balance-policy>
<bean-load-balance-policy>
org.jboss.ha.framework.interfaces.FirstAvailable
</bean-load-balance-policy>
</cluster-config>
<ejb-name>ejb/ApplicationEntity</ejb-name>
<security-domain>java:/jaas/defaultLdap</security-domain>
<resource-ref>
<res-ref-name>jdbc/OracleDS</res-ref-name>
<jndi-name>java:/jdbc/OracleDS</jndi-name>
</resource-ref>
<configuration-name>Standard BMP 2.x EntityBean with cache invalidation</configuration-name>
<cache-invalidation>True</cache-invalidation>
cache-invalidation.xml (No Change)
==============
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server>
<!-- $Id: cache-invalidation-service.xml,v 1.4 2003/08/27 04:31:54 patriot1burke Exp $ -->
<!-- ===================================================================== -->
<!-- -->
<!-- Cache Invalidation Service -->
<!-- -->
<!-- ===================================================================== -->
<!--
Uncomment if you want to activate the cache invalidation mechanism accross
nodes using the JMS bridge
PropagationMode can be : IN_OUT = 1, IN_ONLY = 2, OUT_ONLY = 3
You can also set the ProviderUrl attribute to another IP:port setting if you
must lookup your JMS information in other JMS trees i.e.
MyOtherNode:1099
-->
<!--
<depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
<depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager
jboss.cache:service=InvalidationManager
jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge
jboss.cache:service=InvalidationManager
java:/ConnectionFactory
topic/JMSCacheInvalidationBridge
1
-->
Thanks.hi ,
In this scenario u can use the load balancer instead of fail over clustering .
I would suggest u to create apache proxy for redirect the request for many jboss instance.
Rgds
kathir -
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 ?!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 ?! -
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>
> >
> >
>
-
Hi All,
I have to clarify regarding DB Clustering, existing system is an EP6 SP6 with Oracle 9i on Solaris platform. It has to be clustered with MS SQL Server on Win2k.
Thanks in advance for the kind help!!!
Cheers
Nithin
Message was edited by: Nithin S JCan you run the following and check the output:
db2mscs -f <path>\db2mscs.cfg -d <path>\debug.txt
I suspect you may see the following error in the debug.txt:
Create_IP_Resource fnc_errcode 5045
If you see the fnc_errcode 5045
In that case, error 5045 which is a windows error, means
ERROR_CLUSTER_NETWORK_NOT_FOUND. This error is occuring because windows
couldn't find the "public network" as indicated by IP_NETWORK.
Windows couldn't find the MSCS network called "public network". The
IP_NETWORK parameter must be set to an MSCS Network., so running the
Cluster Admin GUI and expanding the Cluster Configuration->Network to
view all MSCS networks that were available and if "public network" was
one of them.
However, the parameter IP_NETWORK is optional and you could be commented
out. In that case the first MSCS network detected by the system was
used. You may already have the instruction for how to set up a
microsoft cluster. Nevertheless, you may find the following web link
useful:
http://www.microsoft.com/windows2000/techinfo/planning/server/clusterste
ps.asp
I think is caused by the fact that they are specifying an IP Address
that is already used by one of the resources. This needs to be a third,
seperate IP Address.
If you do not see the fnc_errcode 5045 please paste the debug output.
Regards,
Adam -
Clusters problem solved - turned off networking...
Howdy...
For several months my single MacPro (8 core) had no issues running a quick cluster with 4 instances. Then, for some reason, it the cluster would not show up in compressor. Sometimes it would show up after a reboot, or after waiting for a time, and then go away again when I submitted a 2nd job. The instability has become very unnerving...
Then, after reading many posts, I tried making my Ethernet connection inactive.
Oddly enough, this seems to have completely solved my problem. If I turn off my network connection, the cluster shows up immediately and I can submit my jobs with glee. If I reactivate my network connection, the cluster disappears from Compressor and Batch Monitor once again...
I've tried reinstalling FCS2 with no luck, but this is a good temporary work around...
Anyone have any idea why this is happening, or if there is a better fix?
Thanks!
-Ben Freedmananyone ever figure out why this works or what to do to fix the problem?
Maybe you are looking for
-
I can't say I'm thrilled about the new update (2014 model), in fact I'm disappointed. However, it still may be able to cater for my needs. At the minute I'm using a PC with Win 7. My main usage is browsing the 'net, downloading music and running a fe
-
Why can I not get Instagram on my iPad Air?
I Have an iPad Air and I cannot get Instagram but on other iPads you can. I'm really confused on why.
-
Is apple still supporting mac pro
It seems as if Apple has forgotten about the Mac Pro. Are they still going to support and update this machine?
-
Windows XP 32-bit Virtual Memory Tuning.
For our PXI racks we "tune" the virtual memory under Windows XP 32-bit (standard NI installation), as a couple of our applications process vast volumes of data , as follows: Open boot.ini Find the line beginning with 'multi' Add the following to the
-
Use wscompile to set properties in generated client.
It seems to me that there should be an easy way to set properties in generated code. My client code generates properly, for instance: try { stub._initialize(super.internalTypeRegistry); } catch (JAXRPCException e) {