Multihomed cluster
I need to set up weblogic cluster in a single machine. let us assume i need to run two wls in the cluster and i have done the following
1. set up two ip address for the machine (ip1 and ip2)
2. able to run two instances of wls, server1 bind to ip1 and server2 to ip2.
My question is how to set up multicast ip address for the cluster in the machine. I am using a standalone machine running NT workstation
Thanks
Asit,
In Sun Solaris, using ifconfig to config 2 ip with 1 NIC in one machine as:
> ifconfig le0 192.168.0.1 inet plumb up
> ifconfig le0:1 192.168.1.2 inet plumb up
Brian
Asit N Bhattacharya <[email protected]> wrote:
>What is the equivalent procedure for solaris?
>Thanks.
>
>Cameron Purdy wrote:
>
>> On NT all you have to do is pick a legal multicast address. The one used
>in
>> the WL examples will even work! Use the multicast test to verify.
>>
>> To multi-home (have multiple IP addresses per host) then you will have
>to
>> use the NT configuration for network TCP/IP properties and add those IP
>> addresses to the adapter.
>>
>> Peace,
>>
>> --
>> Cameron Purdy
>> Tangosol, Inc.
>> http://www.tangosol.com
>> +1.617.623.5782
>> WebLogic Consulting Available
>>
>> "sakthi" <[email protected]> wrote in message
>> news:[email protected]...
>> >
>> > I need to set up weblogic cluster in a single machine. let us assume
>i
>> need to run two wls in the cluster and i have done the following
>> > 1. set up two ip address for the machine (ip1 and ip2)
>> > 2. able to run two instances of wls, server1 bind to ip1 and server2
>to
>> ip2.
>> >
>> > My question is how to set up multicast ip address for the cluster in
>the
>> machine. I am using a standalone machine running NT workstation
>> >
>> > Thanks
>
>--
>------------------------------
> ||| Asit N Bhattacharya
> ooooo [email protected]
> ||| (925)787-0780
>------------------------------
>
>
>
Similar Messages
-
hi!,
I have 2 WLS 5.1 instances running in cluster mode in WinNT.
Both WLS instances are running the same 2 RMI Services implementations that
were compiled with -clusterable flag.
In client code I have:
Calculator c = (Calculator)
aming.lookup( "t3://127.0.0.10,127.0.0.11:9999/CalculatorService");
When Both WLS instances are running there's no problem, but when I shutdown
one of them!
this errror comes:
RemoteException
weblogic.rmi.ConnectException: Failed to create socket to:
969903448053945584S12
7.0.0.11:[9999,9999,9002,9002,9999,-1] using protocol t3
Why? or it's OK?
And some times when Both WLS are running, the next error apears.
RemoteException
weblogic.rjvm.PeerGoneException: Peer requested connection shutdown
thanks in advance!
Mauricio
I could not start up the cluster from the console, but instead I start each
instances of WLS with
startscripts. When servers start the next messages is shown at the end.
Server 1:
Mon Jul 10 14:06:35 GMT-05:00 2000:<I> <SSLListenThread> Listening on port:
9002
address: 127.0.0.10
Mon Jul 10 14:06:35 GMT-05:00 2000:<I> <ListenThread> Listening on port:
9999 ad
dress: 127.0.0.10
<NT Performance Pack> NATIVE: created IoCompletionPort successfully.
IoPort=0x00
000248
Mon Jul 10 14:06:41 GMT-05:00 2000:<I> <WebLogicServer> WebLogic Server
started
Mon Jul 10 14:09:11 GMT-05:00 2000:<I> <ListenThread> Adding address:
server1/12
7.0.0.10 to licensed client list
Mon Jul 10 14:09:12 GMT-05:00 2000:<I> <NT Performance Pack> Allocating: '2'
NT
reader threads
Server2:
Mon Jul 10 14:08:47 GMT-05:00 2000:<I> <ListenThread> Listening on port:
9999 ad
dress: 127.0.0.11
Mon Jul 10 14:08:47 GMT-05:00 2000:<I> <SSLListenThread> Listening on port:
9002
address: 127.0.0.11
<NT Performance Pack> NATIVE: created IoCompletionPort successfully.
IoPort=0x00
00026c
Mon Jul 10 14:08:55 GMT-05:00 2000:<I> <WebLogicServer> WebLogic Server
started
Mon Jul 10 14:09:12 GMT-05:00 2000:<I> <NT Performance Pack> Allocating: '2'
NT
reader threads
and then I start the console and attach it to the cluster.
So, I could see the tree view and both servers and services like EJB's and
RMI, this showing that my servers are in cluster isn't?.
What information do you need to help me with this issue?
"Prasad Peddada" <[email protected]> wrote in message
news:[email protected]...
> Things to note are.
>
> When you did the lookup where both the servers are up and running? Are
they
> warmed up..
>
> Are you sure that the servers are running in cluster. You can check this
from
> console.
>
> Prasad
>
> Mauricio Del Moral wrote:
>
> > hi!,
> > I have 2 WLS 5.1 instances running in cluster mode in WinNT.
> > Both WLS instances are running the same 2 RMI Services implementations
that
> > were compiled with -clusterable flag.
> >
> > In client code I have:
> > Calculator c = (Calculator)
> > Naming.lookup( "t3://127.0.0.10,127.0.0.11:9999/CalculatorService");
> >
> > When Both WLS instances are running there's no problem, but when I
shutdown
> > one of them!
> > this errror comes:
> >
> > RemoteException
> > weblogic.rmi.ConnectException: Failed to create socket to:
> > 969903448053945584S12
> > 7.0.0.11:[9999,9999,9002,9002,9999,-1] using protocol t3
> >
> > Why? or it's OK?
> >
> > And some times when Both WLS are running, the next error apears.
> >
> > RemoteException
> > weblogic.rjvm.PeerGoneException: Peer requested connection shutdown
> >
> > thanks in advance!
> > Mauricio
>
-
Start managed server in multihomed machine with cluster?
Hi,
I have problems with starting a remote managed server.
I have a cluster configured with 2 managed servers in the same machine. I added a new managed server but assigned to other machine.
MachineA:
-AdminServer:7001,
-ManagedServerA1: 7004, ManagedServerA2:7006
-Cluster
MachineB:
-ManagedServerB: 7003
I tried to start ManagedServerB in Machine A but I have got this error:
startManagedWeblogic.cmd ManagedServerB http://MachineA:7001
<Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address “IP of MachineB that I am using†might be incorrect or another process is using port 7003: java.net.BindException: Cannot assign requested address: JVM_Bind.>
<Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
But the port is not used by any other process or server.
Other question: is it necessary to start all managed servers, local and remote in the server where my application is deployed?
Is it the correct way for using a cluster in multihomed machine?
Is there any documentation for configuring a cluster specifically for this case?
By the way, I am using Weblogic 91.
Regards,
HicyoHi,
I am also having the same problem below.Can someone suggest a solution to my problem?
I have a cluster configured with 2 managed servers in the same machine. I added a new managed server but assigned to other machine.
MachineA:
-AdminServer:7001,
-ManagedServerA1: 7004, ManagedServerA2:7006
-Cluster
MachineB:
-ManagedServerB: 7003
I tried to start ManagedServerB in Machine A but I have got this error:
startManagedWeblogic.cmd ManagedServerB http://MachineA:7001
<Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address “IP of MachineB that I am using†might be incorrect or another process is using port 7003: java.net.BindException: Cannot assign requested address: JVM_Bind.>
<Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
But the port is not used by any other process or server. -
Cluster mgmt of off-network (multihomed) addresses
I'm currently in the process of configuring an HA cluster to replace a single machine. The original machine had virtual interfaces plumbed for several different networks, which remote sites connect to for FTP and other data. I'd like to know how to do the same using the cluster (3.1 on Solaris 9 atm).
Part of the problem is when I attempt to define the Logical Hostname resource, I get the error "specified hostname(s) cannot be hosted by any adapter on xxx". I tried configuring a different (permanent) address on both cluster nodes that was on the same network, which allowed the initial configuration; however, when the resource was stopped, it partially unconfigured the permanent interface and brough the entire cluster to its knees.
Does anyone know how I can do this? In detail, I have interface ce3 with a network like 192.1.110, and virtual addresses that need to be failover resources in the cluster on 192.1.33, 192.1.34, etc.I've managed to succeed in getting the multiple networks managed by the cluster, it appears. Essentially, I did an ifconfig addif to add the network, and explicitly set an appropriate netmask. I also put an entry in /etc/hosts, though I haven't done anything with IPMP. The cluster in question doesn't have multiple public interfaces (two private, one sunray, one public).
I suspect the netmask may have been the cause of my earlier troubles. Since we didn't have an entry for these networks in /etc/netmasks, it probably defaulted to 255.0.0.0, somehow making it such that when the cluster software unconfigured the managed address, it somehow partially unconfigured the permanent address and made things go pretty nuts.
I'm still interested in hearing what you've done to get it to work, however, in case I've missed something. -
Multihomed, unicast cluster question
I'm trying to direct a unicast cache cluster to run on a different IP then the server default by using the following java command line options:
-Dtangosol.coherence.localhost=192.168.202.xxx -Dtangosol.coherence.localport=20000
I'm able to tell the jvms how to connect to the cluster over the non-default IP address on the box. All 6 jvms (2 jvms per server - 3 servers) cluster in, but it seems that something is missing because when we kick off the script to load the cache files, it doesn't load successfully - it seems stalled. There are no error messages anywhere and no indicator that anything is wrong. When I remove all the references to the IP I want to use and use the defaults instead, the jvms cluster fine and when we kick off the script to load the cache, it runs normally. I'm not modifying the tangosol-coherence-override.xml file - I'm just doing the above options on the java command line. Shouldn't this be enough? Or do I need to make modifications to the override xml too?Sorry for taking so long to respond, the past couple weeks were pretty busy. I've found that the cache loading script does work, but instead of taking 10-15 minutes, it's taking about an hour and 15 minutes to load cache over hipersocket. Over ethernet, the load time is normal. We've found out about a bug for the hipersocket driver that exists in SuSE z/OS linux, and we think it also exists in Redhat RHEL4.0 z/OS linux. I'm going to do some more research into server / network tuning on hipersockets before I open a ticket with you guys. Thanks for the prompt response though ...
- Jim -
Hi,
I'm running two WLS 6 in a multihomed machine. Do I need to install to instances
of WLS or can I install one instance and use the same file, but starting with
different scripts. Are there any negatives or positives about using one install,
but two scripts? These instances will be clustered.
Thanks for your help.
But do I have to have the same installation or I can have different
installations?
Should the clusters use the same config.xml files?
Also, am I correct to assume that the admin server can also be a cluster?
I have only two machines and I want one of them to be the admin, as well as
to be one of the nodes in the cluster. Is there anything wrong with this
configuration?
Thanks.
Andre Mendonca
[email protected]
"Kaye Wilcox" <[email protected]> wrote in message
news:[email protected]...
> You'll need to create your cluster and add your server instances to the
> cluster via the console (see
> http://edocs.bea.com/wls/docs60/adminguide/config.html#1024476).
>
> You'll need only one WLS 6.0 installation on your machine. You will need a
> start up script for each server instance that you want to boot up. So if
you have
> an admin server and a cluster of two managed servers you will need three
start up
> scripts for your servers (see
<WL_HOME>/wlserver6.0/config/mydomain/startWebLogic.sh
>
> and startManagedWebLogic.sh for example start up scripts).
>
> wwen wrote:
>
> > Hi,
> >
> > I'm running two WLS 6 in a multihomed machine. Do I need to install to
instances
> > of WLS or can I install one instance and use the same file, but starting
with
> > different scripts. Are there any negatives or positives about using one
install,
> > but two scripts? These instances will be clustered.
> >
> > Thanks for your help.
>
-
Setting up a cluster for the first time: newbie questions
Any help appreciated with this situation:
I'm trying to set up a cluster for the first time and running into
issues (no big surprise). I'll outline my situation and pose questions
as they arise. If/when I get things to work I'll post a step-by-step
summary of what it took to get a simple cluster going.
Here's what I have:
machines:
1 Windows 2000 machines with WL 6.1
2 RedHat Linux machines with WL 6.1
All machines are on the same Home LAN, can see each other, etc.
IP addresses are:
Windows box: 192.168.1.100
Linux box 1: 192.168.1.102
Linux box 2: 192.168.1.103
servers:
I've set up the Windows machine as my admin server, and set up
a managed server on each Linux machine. I created a cluster that consists
of the 2 Linux machines and deployed the web app and EJB to the cluster.
The Windows machine is acting as a Proxy using ClusterServlet.
The web application has been set as the Default Web Application on the
two Linux machines. All 3 machines are listening on ports 80/443. I also
set up session memory replication through the console.
Application:
I have an application that I package as an EAR file. I'm using it as a
"reference" application designed to mimic a real world app as much as possible.
The EAR file contains a web application that uses Struts. It also consists
of a single Stateless Session Bean. The WAR file and EJB Jar are all
packaged up into the EAR file. I've been able to run this application just
fine on a single managed server on all 3 machines.
The web application works fine, and it can invoke the EJB. I can also
invoke the EJB from Java stand-alone clients. Struts works great. All is
well with the world. Now I'm trying to "cluster-ize" this app using
the environment described above and encountering issues.
I've read the docs and followed the instructions according to the
"Weblogic Bible" book. I can bring up all 3 servers and the Linux
managed servers connect to the cluster just fine. I can also
see the Struts messages in their logs which normally happens and tells me
the webapp is initialized properly. The console tells me that the managed
servers are running. I get no error messages starting up any of the serves.
Here are the problems I am encountering.
When I try to access the Web Application (through a browser on the
Windows machine using http://localhost) I get the following error message:
<Nov 19, 2002 6:44:33 AM EST> <Error> <HTTP> <HttpServer(1754841,null default ct
x,admin) found no context for "/". This request does not match the context path
for any installed web applications and there is no default web application confi
gured.>
Also, when I try to invoke the EJB through a stand-alone Java client,
I get a JNDI lookup error on the EJB's home interface.
Questions:
Question1: I noticed when setting up the machines that console lets you
define a "Machine" or a "Unix Machine". What's the difference? Should I
define the Linux machines as Unix machines or machines, and what are the
consequences of either choice?
Question2:
I'm not totally clear on how my web.xml should look to set up Struts,
the ClusterServlet, and a servlet filter I'm using to test Servlet filters.
Here is what I had before I tried to cluster and which works fine:
<filter>
<filter-name>MainFilter</filter-name>
<filter-class>com.refapp.servlets.MainFilter</filter-class>
<init-param>
<param-name>myAttribute</param-name>
<param-value>Foo</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>MainFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping
<!-- Struts ActionServlet Configuration -->
<servlet>
<servlet-name>action</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
<init-param>
<param-name>application</param-name>
<param-value>refappstruts</param-value>
</init-param>
<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>
<init-param>
<param-name>debug</param-name>
<param-value>2</param-value>
</init-param>
<init-param>
<param-name>mapping</param-name>
<param-value>org.apache.struts.action.RequestActionMapping</param-value>
</init-param>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.do</welcome-file>
<welcome-file>index.jsp</welcome-file>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
(I have set up a "dummy" 0-length file called index.do that triggers
Struts to go into its ActionServlet when first accessing the web site).
Here is how I added ClusterServlet to web.xml:
servlet>
<servlet-name>ClusterServlet</servlet-name>
<servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
<load-on-startup>0</load-on-startup>
<init-param>
<param-name>defaultServers</param-name>
<param-value>192.168.1.102:80:443|192.168.1.103:80:443</param-value>
</init-param>
<init-param>
<param-name>DebugConfigInfo</param-name>
<param-value>ON</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>InitServlet</servlet-name>
<url-pattern>/servlet/InitServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>action</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ClusterServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ClusterServlet</servlet-name>
<url-pattern>*.html</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ClusterServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ClusterServlet</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>
Clearly there is a problem with the Default Web application not being
seen/mapped properly. Any chances my URL mappings for the filter servlet,
Struts, and ClusterServlet are stepping on each other?
With respect to the EJB, here is what my weblogic-ejb-jar looks like:
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>Hello</ejb-name>
<stateless-session-descriptor>
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
<stateless-clustering>
<stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
<stateless-bean-load-algorithm>
round-robin
</stateless-bean-load-algorithm>
<stateless-bean-methods-are-idempotent>
true
</stateless-bean-methods-are-idempotent>
</stateless-clustering>
</stateless-session-descriptor>
<jndi-name>Hello.Home</jndi-name>
</weblogic-enterprise-bean>
I run this through ejbc and package everything up into the EAR file.
However, I get a JNDI lookup failure when I try to access the Bean from
a standalone Java client running on the Windows machine.
Here is the jndi.properties file that I am using:
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://localhost:80
Any ideas what I'm doing wrong here? I can post config.xml also if needed.
Thanks in advance!
Let me try to answer :)....
A1> No need to name diff machines by default weblogic
considers the servers are physically located in diff boxes.
The names are used to differtiate the mang servers which are in
multihomed
Some things to chk
1> Did u targeted the ear file Target as cluster.
2> Can u see on the Admin console that both the man servers
are participated in the cluster( u can see by clicking the monitoring
tab on the Cluster node).
3>Is the URL:PORT for the default web app correct?
the reason: is I dont see the port# on the link u mentioned
4> probably ur ejb might not been deployed on the target thats the
reason u cant access thru java client. If u correct the targets that
will probably fix it.
Hope this helps
Please post the result
Thanks
Sudhir
[email protected] (Chris) wrote in message news:<[email protected]>...
> Any help appreciated with this situation:
> I'm trying to set up a cluster for the first time and running into
> issues (no big surprise). I'll outline my situation and pose questions
> as they arise. If/when I get things to work I'll post a step-by-step
> summary of what it took to get a simple cluster going.
> Here's what I have:
>
> machines:
> 1 Windows 2000 machines with WL 6.1
> 2 RedHat Linux machines with WL 6.1
> All machines are on the same Home LAN, can see each other, etc.
> IP addresses are:
> Windows box: 192.168.1.100
> Linux box 1: 192.168.1.102
> Linux box 2: 192.168.1.103
>
> servers:
> I've set up the Windows machine as my admin server, and set up
> a managed server on each Linux machine. I created a cluster that consists
> of the 2 Linux machines and deployed the web app and EJB to the cluster.
> The Windows machine is acting as a Proxy using ClusterServlet.
> The web application has been set as the Default Web Application on the
> two Linux machines. All 3 machines are listening on ports 80/443. I also
> set up session memory replication through the console.
>
> Application:
> I have an application that I package as an EAR file. I'm using it as a
> "reference" application designed to mimic a real world app as much as possible.
> The EAR file contains a web application that uses Struts. It also consists
> of a single Stateless Session Bean. The WAR file and EJB Jar are all
> packaged up into the EAR file. I've been able to run this application just
> fine on a single managed server on all 3 machines.
> The web application works fine, and it can invoke the EJB. I can also
> invoke the EJB from Java stand-alone clients. Struts works great. All is
> well with the world. Now I'm trying to "cluster-ize" this app using
> the environment described above and encountering issues.
>
> I've read the docs and followed the instructions according to the
> "Weblogic Bible" book. I can bring up all 3 servers and the Linux
> managed servers connect to the cluster just fine. I can also
> see the Struts messages in their logs which normally happens and tells me
> the webapp is initialized properly. The console tells me that the managed
> servers are running. I get no error messages starting up any of the serves.
>
> Here are the problems I am encountering.
>
> When I try to access the Web Application (through a browser on the
> Windows machine using http://localhost) I get the following error message:
>
> <Nov 19, 2002 6:44:33 AM EST> <Error> <HTTP> <HttpServer(1754841,null default ct
> x,admin) found no context for "/". This request does not match the context path
> for any installed web applications and there is no default web application confi
> gured.>
>
> Also, when I try to invoke the EJB through a stand-alone Java client,
> I get a JNDI lookup error on the EJB's home interface.
>
> Questions:
> Question1: I noticed when setting up the machines that console lets you
> define a "Machine" or a "Unix Machine". What's the difference? Should I
> define the Linux machines as Unix machines or machines, and what are the
> consequences of either choice?
>
> Question2:
> I'm not totally clear on how my web.xml should look to set up Struts,
> the ClusterServlet, and a servlet filter I'm using to test Servlet filters.
> Here is what I had before I tried to cluster and which works fine:
>
> <filter>
> <filter-name>MainFilter</filter-name>
> <filter-class>com.refapp.servlets.MainFilter</filter-class>
> <init-param>
> <param-name>myAttribute</param-name>
> <param-value>Foo</param-value>
> </init-param>
> </filter>
>
> <filter-mapping>
> <filter-name>MainFilter</filter-name>
> <url-pattern>/*</url-pattern>
> </filter-mapping
>
>
> <!-- Struts ActionServlet Configuration -->
> <servlet>
> <servlet-name>action</servlet-name>
> <servlet-class>org.apache.struts.action.ActionServlet</servlet-class>
>
> <init-param>
> <param-name>application</param-name>
> <param-value>refappstruts</param-value>
> </init-param>
>
> <init-param>
> <param-name>config</param-name>
> <param-value>/WEB-INF/struts-config.xml</param-value>
> </init-param>
>
> <init-param>
> <param-name>debug</param-name>
> <param-value>2</param-value>
> </init-param>
>
> <init-param>
> <param-name>mapping</param-name>
> <param-value>org.apache.struts.action.RequestActionMapping</param-value>
> </init-param>
> <load-on-startup>2</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>action</servlet-name>
> <url-pattern>*.do</url-pattern>
> </servlet-mapping>
>
> <welcome-file-list>
> <welcome-file>index.do</welcome-file>
> <welcome-file>index.jsp</welcome-file>
> <welcome-file>index.html</welcome-file>
> </welcome-file-list>
>
> (I have set up a "dummy" 0-length file called index.do that triggers
> Struts to go into its ActionServlet when first accessing the web site).
>
> Here is how I added ClusterServlet to web.xml:
>
> servlet>
> <servlet-name>ClusterServlet</servlet-name>
> <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
> <load-on-startup>0</load-on-startup>
> <init-param>
> <param-name>defaultServers</param-name>
> <param-value>192.168.1.102:80:443|192.168.1.103:80:443</param-value>
> </init-param>
> <init-param>
> <param-name>DebugConfigInfo</param-name>
> <param-value>ON</param-value>
> </init-param>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>InitServlet</servlet-name>
> <url-pattern>/servlet/InitServlet</url-pattern>
> </servlet-mapping>
>
> <servlet-mapping>
> <servlet-name>action</servlet-name>
> <url-pattern>*.do</url-pattern>
> </servlet-mapping>
>
> <servlet-mapping>
> <servlet-name>ClusterServlet</servlet-name>
> <url-pattern>/</url-pattern>
> </servlet-mapping>
>
> <servlet-mapping>
> <servlet-name>ClusterServlet</servlet-name>
> <url-pattern>*.html</url-pattern>
> </servlet-mapping>
>
> <servlet-mapping>
> <servlet-name>ClusterServlet</servlet-name>
> <url-pattern>*.jsp</url-pattern>
> </servlet-mapping>
>
> <servlet-mapping>
> <servlet-name>ClusterServlet</servlet-name>
> <url-pattern>*.do</url-pattern>
> </servlet-mapping>
>
>
> Clearly there is a problem with the Default Web application not being
> seen/mapped properly. Any chances my URL mappings for the filter servlet,
> Struts, and ClusterServlet are stepping on each other?
>
> With respect to the EJB, here is what my weblogic-ejb-jar looks like:
>
> <weblogic-ejb-jar>
> <weblogic-enterprise-bean>
> <ejb-name>Hello</ejb-name>
> <stateless-session-descriptor>
> <pool>
> <max-beans-in-free-pool>100</max-beans-in-free-pool>
> </pool>
> <stateless-clustering>
> <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
> <stateless-bean-load-algorithm>
> round-robin
> </stateless-bean-load-algorithm>
> <stateless-bean-methods-are-idempotent>
> true
> </stateless-bean-methods-are-idempotent>
> </stateless-clustering>
> </stateless-session-descriptor>
> <jndi-name>Hello.Home</jndi-name>
> </weblogic-enterprise-bean>
>
> I run this through ejbc and package everything up into the EAR file.
> However, I get a JNDI lookup failure when I try to access the Bean from
> a standalone Java client running on the Windows machine.
> Here is the jndi.properties file that I am using:
>
> java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
> java.naming.provider.url=t3://localhost:80
>
> Any ideas what I'm doing wrong here? I can post config.xml also if needed.
>
> Thanks in advance!
-
WebLogic 5.1 sp6 .. session in cluster not working properly
It seems like there is a problem in Weblogic 5.1 with sessions in a
clustered environment. The problem is immediately visible with sp3 but
also appears in different form with sp6 . I discovered the problem is
actually with session while testing the cluster with a Session servlet
given with the Weblogic 5.1 kit.
I regiestered the servlet as servlet/session.
The environment is briefly as follows:
Solaris 2.6
Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
machine with two multihome addreses like home1:7001 and home2:7001
Cluster properties in mycluster/weblogic.properties are set as,
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
and also started with required cluster properties in startup.
iPlanet 4.0 webserver - obj.conf has entries like
WebLogicCluster="home1:7001,home2:7001"
All requests are made as http://<host>/servlet/session
sp3 ) After both members are booted up, the first call to session
servlet from any new browser session throws a NullException in server,
but subsequent calls work fine. Single server works fine.
After looking at sp6 release notes it appeared to me that it was a known
problem with cluster.
sp6 ) After both members are booted up, all calls to session servlet do
not complete and eventually it times out. Other servlets work fine.
It only works if we do these steps,
- one of the member is booted up and then session servlet is called and
response comes back.
- second member is booted up and it works well if session servlet is
called. Subsequent requests to both members work fine.
Another strange behaviour:
While running a snoop servlet in cluster subsequent requests show,
Requested url :
either http://<host>/servlet/snoop
or http://<host>:7001/servlet/snoop alternatively
which is strange.
You are not using the same service pack on both the servers. let try do that and see how it goes.
1. Also, if you are doing testing why do you so many threads.
2. The servers are unable to open sockets to each other. Could be network related. Please check into that also, but first start the servers with the same service pack.
- Prasad
Sutanu Ghosh wrote:
> Here are the thread dumps from both members of the cluster. I took the dumps
> about 5 times in 10 secs interval. It will be helpful for us if you can give
> some insight about this problem.
> Also about the snoop servlet, can you explain why the requested url is
> different (one with weblogic port another without it) in every alternate
> requests ?
> thanks
>
> Prasad Peddada wrote:
>
> > Sutanu Ghosh wrote:
> >
> > > It seems like there is a problem in Weblogic 5.1 with sessions in a
> > > clustered environment. The problem is immediately visible with sp3 but
> > > also appears in different form with sp6 . I discovered the problem is
> > > actually with session while testing the cluster with a Session servlet
> > > given with the Weblogic 5.1 kit.
> > > I regiestered the servlet as servlet/session.
> > >
> > > The environment is briefly as follows:
> > > Solaris 2.6
> > > Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
> > > machine with two multihome addreses like home1:7001 and home2:7001
> > > Cluster properties in mycluster/weblogic.properties are set as,
> > > weblogic.httpd.clustering.enable=true
> > > weblogic.httpd.session.enable=true
> > > weblogic.httpd.session.persistence=true
> > > weblogic.httpd.session.persistentStoreType=replicated
> > > and also started with required cluster properties in startup.
> > >
> > > iPlanet 4.0 webserver - obj.conf has entries like
> > > WebLogicCluster="home1:7001,home2:7001"
> > >
> > > All requests are made as http://<host>/servlet/session
> > >
> > > sp3 ) After both members are booted up, the first call to session
> > > servlet from any new browser session throws a NullException in server,
> > > but subsequent calls work fine. Single server works fine.
> > > After looking at sp6 release notes it appeared to me that it was a known
> > > problem with cluster.
> > >
> > > sp6 ) After both members are booted up, all calls to session servlet do
> > > not complete and eventually it times out. Other servlets work fine.
> > > It only works if we do these steps,
> >
> > Take thread dumps in intervals of 10 seconds and post them again.
> >
> > > - one of the member is booted up and then session servlet is called and
> > > response comes back.
> > > - second member is booted up and it works well if session servlet is
> > > called. Subsequent requests to both members work fine.
> > >
> > > Another strange behaviour:
> > > While running a snoop servlet in cluster subsequent requests show,
> > > Requested url :
> > > either http://<host>/servlet/snoop
> > > or http://<host>:7001/servlet/snoop alternatively
> > > which is strange.
>
> ------------------------------------------------------------------------
> SIGQUIT
> A SIGQUIT has been received. Do you want to:
> [ 0 ] continue program
> [ 1 ] check & print one deadlock
> [ 2 ] check & print all deadlocks
> [ 3 ] dump thread stacks
> [ 4 ] dump lock registry
> [ 5 ] heap inspection
> [ 6 ] terminate program
> Type number corresponding to selected action: Found 0 deadlock
>
> Full thread dump:
> "HighPriority TimeEventGenerator" (TID:0xe7f658, sys_thread_t:0xe7f590, state:CW, thread_t: t@90, threadID:0xc9751dd8, stack_bottom:0xc9752000, stack_size:0x20000) prio=9
>
> [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
> [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
> [3] java.lang.Thread.run(Thread.java:479)
> -------------------
> "SSLListenThread" (TID:0xe4e270, sys_thread_t:0xe4e1a8, state:R, thread_t: t@89, threadID:0xc9841dd8, stack_bottom:0xc9842000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
> [4] java.net.ServerSocket.accept(ServerSocket.java:224)
> [5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
> [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
> [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "ListenThread" (TID:0xe247f0, sys_thread_t:0xe24728, state:R, thread_t: t@88, threadID:0xc9801dd8, stack_bottom:0xc9802000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
> [4] java.net.ServerSocket.accept(ServerSocket.java:223)
> [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "NBExecuteThread-1" (TID:0xa9b748, sys_thread_t:0xa9b680, state:CW, thread_t: t@84, threadID:0xc9891dd8, stack_bottom:0xc9892000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "NBExecuteThread-0" (TID:0xa9a388, sys_thread_t:0xa9a2c0, state:CW, thread_t: t@83, threadID:0xc98c1dd8, stack_bottom:0xc98c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-69" (TID:0xa98fc8, sys_thread_t:0xa98f00, state:R, thread_t: t@82, threadID:0xc9911dd8, stack_bottom:0xc9912000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
> [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
> [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
> [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
> [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-68" (TID:0xa97be8, sys_thread_t:0xa97b20, state:R, thread_t: t@81, threadID:0xc9941dd8, stack_bottom:0xc9942000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
> [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-67" (TID:0xa96828, sys_thread_t:0xa96760, state:MW, thread_t: t@80, threadID:0xc9991dd8, stack_bottom:0xc9992000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-66" (TID:0xa95468, sys_thread_t:0xa953a0, state:MW, thread_t: t@79, threadID:0xc99c1dd8, stack_bottom:0xc99c2000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-65" (TID:0xa940a8, sys_thread_t:0xa93fe0, state:CW, thread_t: t@78, threadID:0xc9a11dd8, stack_bottom:0xc9a12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-64" (TID:0xa92ce8, sys_thread_t:0xa92c20, state:CW, thread_t: t@77, threadID:0xc9a41dd8, stack_bottom:0xc9a42000, stack_size:0x20000) prio=5
>
> [1] weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:43)
> [2] weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:58)
> [3] weblogic.rmi.extensions.BasicResponse.getThrowable(BasicResponse.java:13)
> [4] weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:74)
> [5] weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
> [6] weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
> [7] weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:224)
> [8] weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:164)
> [9] weblogic.jndi.Environment.getContext(Environment.java:122)
> [10] weblogic.jndi.Environment.getInitialContext(Environment.java:104)
> [11] weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:362)
> [12] weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:406)
> [13] weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:585)
> [14] weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
> [15] weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
> [16] weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:331)
> [17] weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1215)
> [18] weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1118)
> [19] examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
> [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> [22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
> [23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
> [24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
> [25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
> [26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
> [27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
> [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-63" (TID:0xa91b10, sys_thread_t:0xa91a48, state:CW, thread_t: t@76, threadID:0xc9a91dd8, stack_bottom:0xc9a92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-62" (TID:0xa90750, sys_thread_t:0xa90688, state:CW, thread_t: t@75, threadID:0xc9ac1dd8, stack_bottom:0xc9ac2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-61" (TID:0xa8f390, sys_thread_t:0xa8f2c8, state:CW, thread_t: t@74, threadID:0xc9b11dd8, stack_bottom:0xc9b12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-60" (TID:0xa8dfd0, sys_thread_t:0xa8df08, state:CW, thread_t: t@73, threadID:0xc9b41dd8, stack_bottom:0xc9b42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-59" (TID:0xa8cc10, sys_thread_t:0xa8cb48, state:CW, thread_t: t@72, threadID:0xc9b91dd8, stack_bottom:0xc9b92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-58" (TID:0xa8ba38, sys_thread_t:0xa8b970, state:CW, thread_t: t@71, threadID:0xc9bc1dd8, stack_bottom:0xc9bc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-57" (TID:0xa89670, sys_thread_t:0xa895a8, state:CW, thread_t: t@70, threadID:0xc9c11dd8, stack_bottom:0xc9c12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-56" (TID:0xa882b0, sys_thread_t:0xa881e8, state:CW, thread_t: t@69, threadID:0xc9c41dd8, stack_bottom:0xc9c42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-55" (TID:0xa86ef0, sys_thread_t:0xa86e28, state:CW, thread_t: t@68, threadID:0xc9c91dd8, stack_bottom:0xc9c92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-54" (TID:0xa85b30, sys_thread_t:0xa85a68, state:CW, thread_t: t@67, threadID:0xc9cc1dd8, stack_bottom:0xc9cc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-53" (TID:0xa84958, sys_thread_t:0xa84890, state:CW, thread_t: t@66, threadID:0xc9d11dd8, stack_bottom:0xc9d12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-52" (TID:0xa83598, sys_thread_t:0xa834d0, state:CW, thread_t: t@65, threadID:0xc9d41dd8, stack_bottom:0xc9d42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-51" (TID:0xa821d8, sys_thread_t:0xa82110, state:CW, thread_t: t@64, threadID:0xc9d91dd8, stack_bottom:0xc9d92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-50" (TID:0xa80a10, sys_thread_t:0xa80948, state:CW, thread_t: t@63, threadID:0xc9dc1dd8, stack_bottom:0xc9dc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-49" (TID:0xa7f650, sys_thread_t:0xa7f588, state:CW, thread_t: t@62, threadID:0xc9e11dd8, stack_bottom:0xc9e12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-48" (TID:0xa7e478, sys_thread_t:0xa7e3b0, state:CW, thread_t: t@61, threadID:0xc9e41dd8, stack_bottom:0xc9e42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-47" (TID:0xa7d0b8, sys_thread_t:0xa7cff0, state:CW, thread_t: t@60, threadID:0xc9e91dd8, stack_bottom:0xc9e92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-46" (TID:0xa7bcf8, sys_thread_t:0xa7bc30, state:CW, thread_t: t@59, threadID:0xc9ec1dd8, stack_bottom:0xc9ec2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-45" (TID:0xa7a938, sys_thread_t:0xa7a870, state:CW, thread_t: t@58, threadID:0xc9f11dd8, stack_bottom:0xc9f12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-44" (TID:0xa79578, sys_thread_t:0xa794b0, state:CW, thread_t: t@57, threadID:0xc9f41dd8, stack_bottom:0xc9f42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-43" (TID:0xa783a0, sys_thread_t:0xa782d8, state:CW, thread_t: t@56, threadID:0xc9f91dd8, stack_bottom:0xc9f92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-42" (TID:0xa76fe0, sys_thread_t:0xa76f18, state:CW, thread_t: t@55, threadID:0xc9fc1dd8, stack_bottom:0xc9fc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-41" (TID:0xa74c18, sys_thread_t:0xa74b50, state:CW, thread_t: t@54, threadID:0xca011dd8, stack_bottom:0xca012000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-40" (TID:0xa73858, sys_thread_t:0xa73790, state:CW, thread_t: t@53, threadID:0xca041dd8, stack_bottom:0xca042000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-39" (TID:0xa72498, sys_thread_t:0xa723d0, state:CW, thread_t: t@52, threadID:0xca091dd8, stack_bottom:0xca092000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-38" (TID:0xa712c0, sys_thread_t:0xa711f8, state:CW, thread_t: t@51, threadID:0xca0c1dd8, stack_bottom:0xca0c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-37" (TID:0xa6ff00, sys_thread_t:0xa6fe38, state:CW, thread_t: t@50, threadID:0xca111dd8, stack_bottom:0xca112000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-36" (TID:0xa6eb40, sys_thread_t:0xa6ea78, state:CW, thread_t: t@49, threadID:0xca141dd8, stack_bottom:0xca142000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-35" (TID:0xa6d780, sys_thread_t:0xa6d6b8, state:CW, thread_t: t@48, threadID:0xca191dd8, stack_bottom:0xca192000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-34" (TID:0xa3c940, sys_thread_t:0xa3c878, state:CW, thread_t: t@47, threadID:0xca1c1dd8, stack_bottom:0xca1c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-33" (TID:0xa3c720, sys_thread_t:0xa3c658, state:CW, thread_t: t@46, threadID:0xca211dd8, stack_bottom:0xca212000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-32" (TID:0xa3aa60, sys_thread_t:0xa3a998, state:CW, thread_t: t@45, threadID:0xca241dd8, stack_bottom:0xca242000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-31" (TID:0xa3a658, sys_thread_t:0xa3a590, state:CW, thread_t: t@44, threadID:0xca291dd8, stack_bottom:0xca292000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-30" (TID:0xa45828, sys_thread_t:0xa45760, state:CW, thread_t: t@43, threadID:0xca2c1dd8, stack_bottom:0xca2c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-29" (TID:0xa23d00, sys_thread_t:0xa23c38, state:CW, thread_t: t@42, threadID:0xca311dd8, stack_bottom:0xca312000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-28" (TID:0xa14fe8, sys_thread_t:0xa14f20, state:CW, thread_t: t@41, threadID:0xca341dd8, stack_bottom:0xca342000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-27" (TID:0xa21eb0, sys_thread_t:0xa21de8, state:CW, thread_t: t@40, threadID:0xca391dd8, stack_bottom:0xca392000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-26" (TID:0xa0fee0, sys_thread_t:0xa0fe18, state:CW, thread_t: t@39, threadID:0xca3c1dd8, stack_bottom:0xca3c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-25" (TID:0x9c54c8, sys_thread_t:0x9c5400, state:CW, thread_t: t@38, threadID:0xca411dd8, stack_bottom:0xca412000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-24" (TID:0x9c7cc8, sys_thread_t:0x9c7c00, state:CW, thread_t: t@37, threadID:0xca441dd8, stack_bottom:0xca442000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-23" (TID:0xa0acc8, sys_thread_t:0xa0ac00, state:CW, thread_t: t@36, threadID:0xca491dd8, stack_bottom:0xca492000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-22" (TID:0xa17b08, sys_thread_t:0xa17a40, state:CW, thread_t: t@35, threadID:0xca4c1dd8, stack_bottom:0xca4c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-21" (TID:0x9c8498, sys_thread_t:0x9c83d0, state:CW, thread_t: t@34, threadID:0xca511dd8, stack_bottom:0xca512000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-20" (TID:0x9fb8f8, sys_thread_t:0x9fb830, state:CW, thread_t: t@33, threadID:0xca541dd8, stack_bottom:0xca542000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-19" (TID:0x9fd4f8, sys_thread_t:0x9fd430, state:CW, thread_t: t@32, threadID:0xca591dd8, stack_bottom:0xca592000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-18" (TID:0xa0f628, sys_thread_t:0xa0f560, state:CW, thread_t: t@31, threadID:0xca5c1dd8, stack_bottom:0xca5c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-17" (TID:0x9c0cf8, sys_thread_t:0x9c0c30, state:CW, thread_t: t@30, threadID:0xca611dd8, stack_bottom:0xca612000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-16" (TID:0x9bc4f8, sys_thread_t:0x9bc430, state:CW, thread_t: t@29, threadID:0xca641dd8, stack_bottom:0xca642000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-15" (TID:0x9b38f8, sys_thread_t:0x9b3830, state:CW, thread_t: t@28, threadID:0xca691dd8, stack_bottom:0xca692000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-14" (TID:0x9b3cf8, sys_thread_t:0x9b3c30, state:CW, thread_t: t@27, threadID:0xca6c1dd8, stack_bottom:0xca6c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-13" (TID:0x9c94f8, sys_thread_t:0x9c9430, state:CW, thread_t: t@26, threadID:0xca711dd8, stack_bottom:0xca712000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.ke -
Need some advice with indexing and search server in multihomed environment.
Hi,
I want to introduce the JISS (java indexing and search server). We have an multihomed environment with two frontends for convergence and imap/pop proxy service and two mail stores in a cluster HA environment
(Sun cluster 3.2, messaging server 7u3-15.01, convergence 1.0-12.01 running on glassfish 2.1.1). The directory servers (multimaster) are on speperated servers.
I viewed the jiss deployment pages in the wiki (http://wikis.sun.com/display/CommSuite/Indexing+and+Search+Service+Deployment+Planning), but they are more confusing than helpful.
My questions are as follows:
Can I put the jiss web service on the convergence server (to share the same glassfish server?
Is it better to put the indexing part of JISS on a seperate server or on the convergence server or better on the mail store servers?
Can I run the JMQ broker in an HA environment on the cluster? Is it possible to run JMQ together with messaging server in the same cluster group?
Can JISS index two mail stores (I didn't find anything in the config guide)?
Best Regards,
Ruedigerruediger_kunze wrote:
I want to introduce the JISS (java indexing and search server). We have an multihomed environment with two frontends for convergence and imap/pop proxy service and two mail stores in a cluster HA environmentI would recommend holding off until the next release (Communication Suite 7 update 1) as ISS update 1 provides a large number of useful enhancement.
I viewed the jiss deployment pages in the wiki (http://wikis.sun.com/display/CommSuite/Indexing+and+Search+Service+Deployment+Planning), but they are more confusing than helpful.
My questions are as follows:
Can I put the jiss web service on the convergence server (to share the same glassfish server?Yes. This is the scenario used in the single-host-install guide:
http://wikis.sun.com/display/CommSuite7/Sun+Java+Communications+Suite+7+on+a+Single+Host
Is it better to put the indexing part of JISS on a seperate server or on the convergence server or better on the mail store servers?This is answered in the Deployment Planning guide:
"Indexing requires significant CPU resources, thus, it is best to install the indexing service on a separate host dedicated to an ISS single server installation. If this is not an option, then install ISS on the back-end host as a single server installation, and install GlassFish Server as well for ISS."
Can I run the JMQ broker in an HA environment on the cluster? Is it possible to run JMQ together with messaging server in the same cluster group?This article may help:
http://wikis.sun.com/display/CommSuite/Deploying+GlassFish+Message+Queue+in+a+Highly+Available+Environment
Can JISS index two mail stores (I didn't find anything in the config guide)?When you Bootstrap the account you point at the mailhost that the account resides on:
http://wikis.sun.com/display/CommSuite/Administering+Indexing+and+Search+Service
"Creating New ISS Accounts"
Regards,
Shane. -
Hi,
I have a cluster running on a multihomed Solaris Server. It is made of two
servers running on IP1 and IP2 (both using port 7001). It says in the
documentation that I can put in the IPs of the two servers separated by a
comma for the cluster address. So the address that I put in was
"IP1:7001,IP2:7001" instead of a DNS name.
How do I connect to the cluster. If I connect to IP1:7001 then I am
connecting to the server and not the cluster, correct?
I would appreciate any help,
Mohammad
Sorry for the delay, I have been extremely busy...
There are several alternatives -- DNS round-robin, hardware load balancers
(e.g., Cisco LocalDirector), etc.
Mica Cooper wrote:
> Robert,
>
> WLBS is Windows Load Balancing Service. It was designed to only use 1 IP per
> box. It comes on the server editions. Do you know of something else? Linux
> or Solaris maybe?
>
> Mica
>
> "Robert Patrick" <[email protected]> wrote in message
> news:[email protected]...
> > Hi,
> >
> > I'm not sure what WLBS is but I guess my question is does it really need
> to know
> > that the IP addresses happen to point to the same machine? What happens
> if you
> > just tell it that there are twice as many machines as there really are?
> >
> > Robert
> >
> > Mica Cooper wrote:
> >
> > > Currently,
> > > I am using WLBS to do the load balancing and it will only handle one IP
> per
> > > box. Do you know of any other software to do this?
> > > Mica
> > >
> > > "Robert Patrick" <[email protected]> wrote in message
> > > news:[email protected]...
> > > > The real answer here is that the "cluster" is virtual -- it only
> exists
> > > because
> > > > there are one or more server instances running. Regardless of how you
> > > attain
> > > > it, you are going to connect to one or more of the server instances.
> > > There are
> > > > several ways to do this as has been previously discussed (e.g., DNS
> alias
> > > that
> > > > does DNS round-robin-style load-balancing, a comma-separated list of
> IP
> > > > addresses, etc.).
> > > >
> > > > Mica, as for your question, you need to teach your "load-balancing IP"
> > > about all
> > > > of the IP addresses for the servers in the cluster and not just "one
> IP
> > > per
> > > > physical machine".
> > > >
> > > > Hope this helps,
> > > > Robert
> > > >
> > > > Mica Cooper wrote:
> > > >
> > > > > Tao,
> > > > >
> > > > > Thats not what he is asking.
> > > > >
> > > > > He's asking how to call MyServerClusterName instead of trying to
> call
> > > > > different instances by IP. I would like to know how to do this also.
> > > > > Currently we are calling a load balancing IP and it proxies to each
> > > instance
> > > > > but it only works for 1 instance per box and I need 2 instances per
> box.
> > > > >
> > > > > Mica Cooper
> > > > >
> > > > > "Tao Zhang" <[email protected]> wrote in message
> > > > > news:[email protected]...
> > > > > > If you don't use DNS, you can write the IP1:7001,IP2:7001 in your
> > > > > > PROVIDER_URL, and then transfer it to InitialContext.
> > > > > >
> > > > > >
> > > > > > Mohammad Khan <[email protected]> wrote in message
> > > > > > news:[email protected]...
> > > > > > > Hi,
> > > > > > >
> > > > > > > I have a cluster running on a multihomed Solaris Server. It is
> made
> > > of
> > > > > two
> > > > > > > servers running on IP1 and IP2 (both using port 7001). It says
> in
> > > the
> > > > > > > documentation that I can put in the IPs of the two servers
> separated
> > > by
> > > > > a
> > > > > > > comma for the cluster address. So the address that I put in was
> > > > > > > "IP1:7001,IP2:7001" instead of a DNS name.
> > > > > > >
> > > > > > > How do I connect to the cluster. If I connect to IP1:7001 then I
> am
> > > > > > > connecting to the server and not the cluster, correct?
> > > > > > >
> > > > > > > I would appreciate any help,
> > > > > > > Mohammad
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > >
> >
-
Hi,
I have a configuration where a single Apache running the WLS-plugin
fronts two WLS instances executing on the same, multihomed Solaris
machine. The cluster specific weblogic.properties file contains the
following:
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
Static pages and servlets not depending on HTTP session state work fine
but when I try to run the example session servlet
(examples.servlets.SessionServlet) the web browser never gets any
response. I can't find anything suspicous in the log files.
Does anybody have any idea of what could be wrong? Is there a simple way
to verify that the clustering config, the multicast address etc is okay?
Thank you
Patrik
Yep, that definately made a difference. It works now - thanks!
Cheers
Patrik
Wei Guan skrev:
> What is your SP? Could you try SP4?
>
> --
> Cheers - Wei
>
> Patrik Gottfridsson <[email protected]> wrote in message
> news:[email protected]...
> >
> > The weblogic.httpd.clustering.enable is set on the command line in the
> startup
> > script. Also, I ran the multicastTest utility after shutting down the
> > application server. So neither of these should cause any problems. The
> strange
> > thing is that everything looks normal. I get some nice messages in the
> > weblogic.log saying that both WLS instances join the cluster and so on.
> >
> > To debug I tried set this property in the cluster-wide config file:
> >
> > weblogic.debug.replication=2
> >
> > and this resulted in the following message in the weblogic.log of the
> primary
> > WLS:
> >
> > Thu Aug 17 16:36:35 GMT+02:00 2000:<I> <RepMan> Trying to create secondary
> for
> > 5449997915261938767 on new host
> > 5557948761125425783S192.168.1.235:[7001,7001,7002,7002,7001,-1]
> >
> > and then nothing more (browser hung). Should the trace contain something
> more,
> > e.g. "Secondary created ok .."? I guess this would imply that the
> replication
> > fails in some way.
> >
> > Cheers
> >
> > Patrik
> >
> >
> >
> > Wei Guan skrev:
> >
> > > weblogic.httpd.clustering.enable=true must be set in startup script.
> > >
> > > --
> > > Cheers - Wei
> > >
> > > Vincent Wong <[email protected]> wrote in message
> > > news:[email protected]...
> > > >
> > > > Hi,
> > > >
> > > > I have a configuration where a single Apache running the WLS-plugin
> > > > fronts two WLS instances executing on the same, multihomed Solaris
> > > > machine. The cluster specific weblogic.properties file contains the
> > > > following:
> > > >
> > > > weblogic.httpd.clustering.enable=true
> > > > weblogic.httpd.session.persistence=true
> > > > weblogic.httpd.session.persistentStoreType=replicated
> > > >
> > > > Static pages and servlets not depending on HTTP session state work
> fine
> > > > but when I try to run the example session servlet
> > > > (examples.servlets.SessionServlet) the web browser never gets any
> > > > response. I can't find anything suspicous in the log files.
> > > >
> > > > Does anybody have any idea of what could be wrong? Is there a simple
> way
> > > > to verify that the clustering config, the multicast address etc is
> okay?
> > > >
> > > > Thank you
> > > >
> > > > Patrik
> > > >
> >
-
Hello,
We are using Weblogic 5.1.0 SP11 on windows 2000. We have setup multihoming with
different IP addresses to run two instances of WL server.
Instead of maintaining the same static files under each servers document root can
we maintain the files under one server and share with the other server ?
You can have these files at per-cluster directory level.
for e.g. /home/kumara/weblogic510/mycluster/public_html
This folder is read by all clustered nodes...
L Pusapaty wrote:
> Hello,
>
> We are using Weblogic 5.1.0 SP11 on windows 2000. We have setup multihoming with
> different IP addresses to run two instances of WL server.
>
> Instead of maintaining the same static files under each servers document root can
> we maintain the files under one server and share with the other server ?
>
-
Lets say setup1 has 2 solaris boxes each having one instance of wl
server and in a cluster.
In setup2 we multihome each box to have 3 wl instaces and put the 6
instances(total) in cluster.
Lets assume all boxes are identical and run only weblogic + same
application code..
a) Is setup2 more advantageous than setup1?
b) I know there is the problem of having replicated session data on the
same m/c if they are multihomed. In which version/release this is
solved? Is this feature
supported on 4.5.1 and 4.5.2 through service packs?
shivu wrote:
> Lets say setup1 has 2 solaris boxes each having one instance of wl
> server and in a cluster.
>
> In setup2 we multihome each box to have 3 wl instaces and put the 6
> instances(total) in cluster.
>
> Lets assume all boxes are identical and run only weblogic + same
> application code..
>
> a) Is setup2 more advantageous than setup1?
This depends on how "big" the solaris boxes are. In our tests, we have seen
that most JVMs cannot effectively utilize more than a few CPUs. Therefore,
if you have a box with 8 CPUs, you probably need to run more than one copy
of the server to effectively utilize the box. Of course, the disadvantage
(which will be addressed with WLS 5.1.1) is that, if you are using our
in-memory replication, you have no control over where the primary/secondary
copies of the objects are located (so they might be on two different WLS
servers that are running on the same physical machine).
> b) I know there is the problem of having replicated session data on the
> same m/c if they are multihomed. In which version/release this is
> solved? Is this feature
> supported on 4.5.1 and 4.5.2 through service packs?
WLS 5.1.1 (not sure what the plans are for the 4.5.x line).
Hope this helps,
Robert
-
Session lost problem in Weblogic cluster and Iplanet proxy
We have an environment like this
Iplanet 4.1--> Two Weblogic servers.(WLS 6.1 sp1)
The Weblogic servers are not really clusterd, but we are using the Weblogic Cluster
attribute in the obj.conf to configure the proxy (The Weblogic servers are really
independant servers with the same application deployed).
This is working fine in our development environment. No problem with session and
load balancing. Although this architecture is not documented in Weblogic docs,
I have seen several references to this type of architecture in the web and it
seems to be working.
Now we are into our pre-production environment. The same archictecture exists.
Only the following differences
1. Both the weblogic servers run on multihomed machines. We have bound the Weblogic
servers to specific IP addresses using the Listen address option.
2. The same IP addresses are there in the proxy plug-in conf file.
3. There is a firewall between the Iplanet and Weblogic.
Now if only one weblogic is running, the application works fine. The moment we
turn the other weblogic on, the application starts misbehaving. The session seems
to get lost and proxy forwards requests randomly.
What could be the reason?
Regards
Anup
Hi
The problem got solved. There was an older version of libproxy.so in the Iplanet
proxy
Regards
Anup
Yeshwant Kamat <[email protected]> wrote:
>Anup,
>
>Is there a reason you are not clustering the WLS instances? Remove the
>firewall in your
>prod environment and see if that makes a difference.
>
>Anup wrote:
>
>> Hi Mike
>> 1. As per the documentation WebLogic Server is set up to handle session
>tracking
>> by default. So we are not doing anything special. Since the application
>works
>> fine with one Weblogic and multiple clients connecting to it through
>Iplanet ,
>> I think there is no problem with Session tracking as such.
>>
>> 2.We are using the default cookie name for session (JSESSIONID). So
>we haven't
>> done anything extra in the proxy set up or weblogic.xml
>>
>> 3. I have watched the cookie that comes on the browser
>> PAACk3iviDm4ZuMPIbB9TpTTw9slk40IEC02MKjpu14EZ9ayzqaP!-1196227542!gmbpds054!7015!7016.
>>
>> gmbpds054 is the DNS name of one of the weblogic servers. So that is
>also fine.
>>
>> What else could be the problem.
>> Regards
>> Anup
>>
>> "Mike Reiche" <[email protected]> wrote:
>> >
>> >If you have session tracking turned on in weblogic, creating a session
>> >will write
>> >a cookie back to the browser. iPlanet does sticky load balancing
>based
>> >on the
>> >IP address in this cookie. So -
>> >
>> >1) do you have session tracking turned on?
>> >
>> >2) is the cookie getting written to your browser?
>> >
>> >3) are iPlanet and WebLogic using the same cookie? (same name)
>> >
>> >Mike
>> >
>> >"Anup Maliyackel" <[email protected]> wrote:
>> >>
>> >>We have an environment like this
>> >>
>> >>Iplanet 4.1--> Two Weblogic servers.(WLS 6.1 sp1)
>> >>
>> >>The Weblogic servers are not really clusterd, but we are using the
>Weblogic
>> >>Cluster
>> >>attribute in the obj.conf to configure the proxy (The Weblogic servers
>> >>are really
>> >>independant servers with the same application deployed).
>> >>
>> >>This is working fine in our development environment. No problem with
>> >>session and
>> >>load balancing. Although this architecture is not documented in Weblogic
>> >>docs,
>> >>I have seen several references to this type of architecture in the
>web
>> >>and it
>> >>seems to be working.
>> >>
>> >>Now we are into our pre-production environment. The same archictecture
>> >>exists.
>> >>Only the following differences
>> >>1. Both the weblogic servers run on multihomed machines. We have
>bound
>> >>the Weblogic
>> >>servers to specific IP addresses using the Listen address option.
>> >>
>> >>2. The same IP addresses are there in the proxy plug-in conf file.
>> >>
>> >>3. There is a firewall between the Iplanet and Weblogic.
>> >>
>> >>Now if only one weblogic is running, the application works fine.
>The
>> >>moment we
>> >>turn the other weblogic on, the application starts misbehaving. The
>> >session
>> >>seems
>> >>to get lost and proxy forwards requests randomly.
>> >>
>> >>What could be the reason?
>> >>
>> >>Regards
>> >>Anup
>> >
>
-
Greetings,
I'm still very ignorant about setting up clusters - I'm actually a coder that
wants to use MBeans to do some things with clustered servers, so forgive what
is probably a very basic question.
The question is this:
When a server is being configured to belong to a cluster in the console, is it
required that the Listen Adress be filled in for proper operation? One would
think so (and I hope so, because I need to user ServerMBean.getListenAddress()).
However, I noticed that I can remove this value and the console will still see
the server as existing in the cluster (I'm guessing via the Listen Port). My
algorithm relies on being able to get the Listen Address. Am I safe, or do I have
trouble?
Mike
I meant to say " ServerRuntimeMBean.getListenAddress( )"
you could try this
java weblogic.Admin -url t3://localhost:7001 -username system -password weblogic GET
-pretty -type ServerRuntime
Michael Watt wrote:
> Kumar,
>
> Thank you for your initial answer.
>
> I have indeed tried ServerMBean.getListenAddress() and found that when the Listen
> Address has not been filled in via the console, I do not get any value from this
> method. This is in fact, the crux of my problem. When I asked if I were "in
> trouble", I was trying to find out administrators can leave the Listen Address
> field blank and still have a functioning cluster. So.... if this field IS left
> blank, is there any other way that I can find out the listening address, since
> ServerMBean.getListenAddress() seems to be tied only to this field value?
>
> BTW, you asked if my machine is multihomed... well, kinda. The admin machine
> (which also has a clustered server instance on it - not recommended I know) that
> I develop on has 3 network cards, but only 2 are plugged in.
>
> Mike
>
> However, I noticed that I can remove this value and the console willstill see
> the server as existing in the cluster (I'm guessing via the ListenPort). My
> algorithm relies on being able to get the Listen Address. Am I safe,or do I have
> trouble?
>
> I don't see any trouble here.
> BTW, is your machine multihomed?
Maybe you are looking for
-
Save Web Page to String or File
Hi, I'm trying to save a web page to a file or preferably to a String. I need the html coding from it. I tried with the next code: public static String saveURL(URL url){ try{ URLConnection uc = url.openConnection(); Inp
-
My iPhone 4 has been disabled and it went to the "Connect to iTunes screen." At first, iTunes told me to unlock the phone before I could use it in iTunes. Until, I turned the phone off, pressed and held home while plugging the USB cord back into my d
-
Project Online with Project Pro for Office 365
Hi, I have several licences for Project Online with Project Pro for Office 365. Project Web App is working fine, as well as Excel Web App, Word Web App... I just miss Project Pro for Office 365. I don't know were to find it, how to activate it :-( T
-
How can i create a query where it prompts me for the incoming Pmt number and it will tell me the Deposit number . I need to know when Incoming payments were deposited. thanks
-
Premiere Elements 8: Splash Screen Fail
I am running my Premiere Elements 8 on Windows 7 64 bit, latest Nvidia drivers. The splash screen where you launch the actual program loads fine and my projects open from the OPEN PROJECT menu the first time, but if I close the program and try to onc