Clustering newbie WLS6.1

Okay, so my first attempts at clustering aren't going too well...
          I have a single Sun box with WLS 6.1 SP3 installed.
          On the box I have:
          One Admin server listening on 7001
          One Managed server listening on 7002
          One Managed server listening on 7003
          Firstly is this okay?
          Then I have a cluster with just the two managed servers inside it.
          I have a stateless session EJB. I have configured the .xml to
          indicate clusterable and deployed it to the two managed servers, and
          also the cluster...
          So when I send requests to the server it doesnt seem to round-robin
          the requests. I thought that even if I sent all requests to 7002 the
          cluster aware stub should round robin to 7003?
          I monitor whether it was load balanced by looking at the console under
          the EJB, 'monitor all stateless EJBRuntimes'. Here I can see that the
          EJB appears on both managed servers with correct number of idle beans
          on each server, but the transactions commited only goes up on one of
          the servers(7002).
          I know I must be missing something obvious here but just cant find any
          docs/postings that help.
          Any sugestions?
          Thanks
          Peter

Hi Peter,
 See comments inline.
 Jane
 BEA Support
 "Peter" <[email protected]> wrote in message
 news:[email protected]...
 > Okay, so my first attempts at clustering aren't going too well...
 >
 > I have a single Sun box with WLS 6.1 SP3 installed.
 > On the box I have:
 > One Admin server listening on 7001
 > One Managed server listening on 7002
 > One Managed server listening on 7003
 >
 > Firstly is this okay?
 No, in 6.x, you managed servers must be listening on the same port. Also,
 typically 7002 is the default SSL port, so make sure you haven't used the
 same port for both ListenPort and SSLListenPort.
 Make sure that each managed server is listening on a different IP address.
 In WLS7.0 you can use different ports.
 >
 > Then I have a cluster with just the two managed servers inside it.
 >
 > I have a stateless session EJB. I have configured the .xml to
 > indicate clusterable and deployed it to the two managed servers, and
 > also the cluster...
 Only need to deploy to the cluster.
 >
 > So when I send requests to the server it doesnt seem to round-robin
 > the requests. I thought that even if I sent all requests to 7002 the
 > cluster aware stub should round robin to 7003?
 Use a DNS name in your ClusterAddress that maps to both IP addresses for
 your managed servers. In the URL for your remote client, you should use
 t3://<clusterDNSname>:<port> - e.g., if my managed servers are listening on
 port 8000 and my ClusterAddress is "mycluster" then I would use
 t3://mycluster:8000 in my URL.
 >
 > I monitor whether it was load balanced by looking at the console under
 > the EJB, 'monitor all stateless EJBRuntimes'. Here I can see that the
 > EJB appears on both managed servers with correct number of idle beans
 > on each server, but the transactions commited only goes up on one of
 > the servers(7002).
 >
 > I know I must be missing something obvious here but just cant find any
 > docs/postings that help.
 >
 > Any sugestions?
 >
 > Thanks
 >
 > Peter

Similar Messages

Clustering newbie questions

 Pls forgive some naivete as am new to clusters ... we have WLS 6.0 running an app
 clustered on 3 servers and we have problems crashing every other day and slow
 performance all the time. Platform is Win NT 4.0 SP4 with 640 MB RAM, using IIS
 as HTTP server, with BigIP F5 load balancer in front. This is a strange configuration
 to me and WLS 6.0/NT is pretty old I think ... but it's hard to know where to
 start looking for source of problems !!
 Can anybody pls help with general thoughts ? appreciate it ...
 thans in advance ...


Do you get any stack trace at the time of crash?
 For performance related issues - you will have to profile the application
 and understand where the most time is being spent. If its too slow , then
 may be even threaddumps can help identify what is happening. Generally you
 should have a test setup and some way of simulating the normal load on the
 application and thats where you should profile the application with some
 profiling tools.
 Yes, WLS6.0 is now retired.
 sree
 "Ethan Allen" <[email protected]> wrote in message
 news:[email protected]..
 >
 > Pls forgive some naivete as am new to clusters ... we have WLS 6.0 running
 an app
 > clustered on 3 servers and we have problems crashing every other day and
 slow
 > performance all the time. Platform is Win NT 4.0 SP4 with 640 MB RAM,
 using IIS
 > as HTTP server, with BigIP F5 load balancer in front. This is a strange
 configuration
 > to me and WLS 6.0/NT is pretty old I think ... but it's hard to know where
 to
 > start looking for source of problems !!
 >
 > Can anybody pls help with general thoughts ? appreciate it ...
 >
 > thans in advance ...

Clustering newbie error while starting managed server

 I'm getting an authorization exception while starting a managed server (see attached
 trace). I'm running WLS 6.1 on three Redhat Linux servers. I've configured an
 admin server on Machine1, which starts fine. When I attempt to start the first
 managed server on M2 (an identical installation: same default values used on both
 machines), and supplying the admin server machine's IP and listen port, I get
 an error message which includes the line:
 The reported error was: < null > This condition generally results when the managed
 and admin servers are using the same listen address and port.
 While the port is the same (which I understand they must be), the listen addresses
 are definitely different. Any suggestions?
 Thanks,
 [trace.txt]


 Thanks for the ideas, Mark. As it turned out, I discovered while reading the security
 newsgroup that WLS 6.1 "has issues with" Java 1.4.0, which I happened to be running
 the managed server under. After regressing to 1.3.1, it seems to work. Funny
 how I could have missed that....:-)
 "Mark Vaughn" <[email protected]> wrote:
 >
 >Here are a few things I have run into in this area. IF you are on UNIX,
 >make sure
 >your DNS settings and /etc/hosts files are all identicle between
 >these servers. I would recommend using IP's instead of names that
 >have to be resolved. Also, there is a line in your cluster settings
 >that is mis-formatted:
 >
 ><Cluster ClusterAddress="reaper1,reaper2:7001" Name="TestCluster" />
 >
 >"reaper1" has no port defined.
 >
 >Try adding the port for reaper1. If that fixes it I will be shocked,
 >
 >but you will be fixed. If it does not, try using IP's instead of
 >server names. If that fixes, you know the problem was in the network
 >configurations on the machines.
 >
 >Hope that helps,
 >--Mark Vaughn
 >
 >
 >"Martin Zaidel" <[email protected]> wrote:
 >>
 >>
 >>
 >>Right: the error message implies the problem is that the admin and managed
 >>server
 >>have the same IP, while I know they don't: that's what's confusing me.
 >> (My config.xml
 >>is attached.)
 >>
 >>Just to clarify:
 >>
 >>I've installed the WLS 6.1 with examples (with the 6.1 cluster license)
 >>on three
 >>machines (each with their own filesystems). On skylla, I've created
 >a
 >>server named
 >>'Admin' in the examples domain, as well as a cluster with two machines,
 >>reaper1
 >>and reaper2, all using the default ports and settings. Admin starts
 >>fine on skylla.
 >> When I invoke the managed server on reaper1 with
 >>
 >>java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=examples
 >-Dweblogic.Name=reaper1
 >>-Dweblogic.management.server=skylla:7001 -Dweblogic.management.password=$WLS_PW
 >>-Dbea.home=/opt/bea -Dcloudscape.system.home=./samples/eval/cloudscape/data
 >>-Djava.security.policy==$WL_HOME/lib/weblogic.policy
 >>weblogic.Server
 >>
 >>then I get the error (see attachment of my original post). Note that
 >>all these
 >>installations are straight out of the box.
 >>
 >>Thanks,
 >>
 >>Martin
 >>
 >>
 >>
 >>Kumar Allamraju <[email protected]> wrote:
 >>><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 >>><html>
 >>>Looking at the error message , it appears that your admin & managed
 >>>server are configured
 >>> to have the same IP ? It doesn't look like that's the case from
 >>your
 >>>email.
 >>>Can you clarify?
 >>> Also post your config.xml , i will take a look at it.
 >>>--
 >>> Kumar
 >>>Martin Zaidel wrote:
 >>><blockquote TYPE=CITE>I'm getting an authorization exception while
 >starting
 >>>a managed server (see attached
 >>> trace). I'm running WLS 6.1 on three Redhat Linux servers.
 >>>I've configured an
 >>> admin server on Machine1, which starts fine. When I attempt
 >>>to
 >>>start the first
 >>> managed server on M2 (an identical installation: same default values
 >>>used on both
 >>> machines), and supplying the admin server machine's IP and listen
 >>>port,
 >>>I get
 >>> an error message which includes the line:
 >>>The reported error was: < null > This condition generally results
 >>>when the managed
 >>> and admin servers are using the same listen address and port.
 >>>While the port is the same (which I understand they must be),
 >the
 >>>listen addresses
 >>> are definitely different. Any suggestions?
 >>>Thanks,
 >>> ----------------------------------------
 >>> 
 >>>Name: trace.txt
 >>> trace.txt Type: Plain Text (text/plain)
 >>> 
 >>>Encoding: base64</blockquote>
 >>></html>
 >>>
 >>
 >

The Local Object can be clustered?

 I hava two EJB in one jar file.One EJB is a Local Interface Entity Bean,another
 is a remote Interface Session Bean.The Session Bean calls the Entity Bean.I deploy
 the jar file into weblogic 6.1 cluster.I want to know the jar file can be clustered.I
 seem to see that Local Interface cann't be clustered in some documents.
 Thanks for answer!


 I'm sorry for not providing you the document.In fact all the documents I ever saw
 say that the local object can't be clustered in WLS6.1 .But I really test a situation
 that can be clustered.I was also every puzzled.The situation is depicted as followed.But
 the situation can only implement the load balance while the Fail-over failed.
 "Shan" <[email protected]> wrote:
 >
 >Could you tell me the url to the document about
 >clustering local entity bean?
 >thanks!
 >Shan
 >"Sunrise" <[email protected]> wrote:
 >>
 >>Yes!I found that Local Object such as Local Entity Bean can also be
 >clustered!
 >>Thanks!
 >>
 >>"Sabha" <[email protected]> wrote:
 >>>Local interface is only accessible within the same application -- so,
 >>>its
 >>>client can only be local to the server and again within the same
 >>>application -- so , it does not matter whether its deployed in a cluster
 >>>or
 >>>not. Only the other related ejb who is looking it up needs to be deployed
 >>>wherever the localinterface Bean object is deployed.
 >>>
 >>>- Sabha
 >>>
 >>>"Sunrise" <[email protected]> wrote in message
 >>>news:[email protected]...
 >>>>
 >>>> I hava two EJB in one jar file.One EJB is a Local Interface Entity
 >>>Bean,another
 >>>> is a remote Interface Session Bean.The Session Bean calls the Entity
 >>>Bean.I deploy
 >>>> the jar file into weblogic 6.1 cluster.I want to know the jar file
 >>>can be
 >>>clustered.I
 >>>> seem to see that Local Interface cann't be clustered in some documents.
 >>>> Thanks for answer!
 >>>
 >>>
 >>
 >

Error when starting managed server Message Too Long

 Hi,
 I'm trying to setup clustering with WLS6.1sp2.
 I use the jdk include with wls
 2 servers in the cluster OS=AIX
 1 Adminserver running on Solaris 8
 When I start a managed server on one of the clustered machines
 I see the following error.
 Starting Cluster Service ....
 <Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread listening
 on port 7001, ip address 10.160.3.74>
 <Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast message:
 java.io.IOException: Message too long
 java.io.IOException: Message too long
 at java.net.PlainDatagramSocketImpl.send(Native Method)
 at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
 at java.net.DatagramSocket.send(DatagramSocket.java:341)
 at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
 at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
 at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
 Code))
 at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
 at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
 at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
 at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
 at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
 at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
 at weblogic.Server.main(Server.java:35)
 >
 <Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast messages
 (cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
 <Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic Managed
 Server "s01ap007" for domain "axa" running in Production Mode>
 Also deploying doesn't seem to succeed could this be coused by this error
 I hope someone can help me.
 Best regards,
 Peter Van der Goten


 Because I found the answer via Mr. yunyee who also had this problem on an AIX machine
 I will post this also here.
 The problem was that the upd_sendspace variable was set on
 a mutch to low value (9126) or something in this range
 It had to be set on 32769.
 this was done with no -o udp_sendspace=32769
 Best regards,
 Peter
 "Peter Van der Goten" <[email protected]> wrote:
 >
 >Hi,
 >I'm trying to setup clustering with WLS6.1sp2.
 >I use the jdk include with wls
 >2 servers in the cluster OS=AIX
 >1 Adminserver running on Solaris 8
 >
 >When I start a managed server on one of the clustered machines
 >I see the following error.
 >Starting Cluster Service ....
 ><Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread
 >listening
 >on port 7001, ip address 10.160.3.74>
 ><Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast
 >message:
 >java.io.IOException: Message too long
 >java.io.IOException: Message too long
 > at java.net.PlainDatagramSocketImpl.send(Native Method)
 > at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
 > at java.net.DatagramSocket.send(DatagramSocket.java:341)
 > at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
 > at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
 > at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
 >Code))
 > at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
 > at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
 > at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
 > at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
 > at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
 > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
 > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
 > at weblogic.Server.main(Server.java:35)
 >>
 ><Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast
 >messages
 >(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
 ><Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic
 >Managed
 >Server "s01ap007" for domain "axa" running in Production Mode>
 >
 >Also deploying doesn't seem to succeed could this be coused by this error
 >
 >I hope someone can help me.
 >Best regards,
 >Peter Van der Goten
 >

Newbie Labview Question: Array of clusters

1: i am a student
2: this is not homework or a graded project
3: I'm a pretty capable programmer, but that's in text-based languages. ;-)
I have a sensor feed which contains 4 channels. I need to leave all 4 channels active, but I want to select one of them to graph at any given time. The data from the NI driver for the hardware comes as a 1x4 array of 2-element clusters.
Normally, I'd just index to the desired element in the 1x4 array, and feed that cluster to the appropriate graphing tool, but I'm missing something. I swiped a display element from the NI driver example VI's, but any time I insert blocks between the data feed and the graph I get "bad connection" errors.
I've been googling and book-looking for several days now, to no avail, I'd appreciate any help in this question.
in the image at ( http://dl.dropbox.com/u/4286123/LabviewHelp.jpg ), what block do i need to insert into the highlighted wire to be able to select and graph only one of the 4 data channels, controlled by an integer source?
Many thanks.
Solved!
Go to Solution.

Use the Index Array funtion found in the Array palette. Wire in the index number of the waveform you wish to display.
- tbob
Inventor of the WORM Global

Clustering wls6.0 and wls5.1

Hi,
 Does anybody know if it is possible to cluster a wls6.0 and a wls5.1 servers
 Thanks for your help,
 Olivier


No, that's not possible.
 All servers in a cluster must be using the same version of WLS as well as on
 the same version of the Service Packs.
 "Olivier Demin" <[email protected]> wrote in message
 news:[email protected]..
 > Hi,
 >
 > Does anybody know if it is possible to cluster a wls6.0 and a wls5.1
 servers
 > ?
 >
 > Thanks for your help,
 > Olivier
 >
 >

Help: newbie of iplanet clustering & loading balancing

As l went through the sample app, "bank" coming along with iplanet. l have a few questions in mind. It is highly appreciated somebody can give a helping hand to me by answering below questions
1) In ias-web.xml and web.xml, the app is set as "distributable" and session is synchronized by "dsync". Also, all servlets are set "sticky". My question is why the JSP don't need to be set as "sticky". If l have a web site made up of serveral ten of thousand of JSP pages, it will be a big trouble
2) Let's say, if the sample include a stateful session bean, do l have to set that stateful session bean to "sticky". If so,
does it mean the invocation from servlet to stateful session bean will take place in same JVM process.
3) Is there any latency if session is synchronized by "dsync" process. If the application is set as "distributable" (support load-balancing), but the servlet is NOT set as sticky. Will it cause any trouble due to latency of synchronization of session among iplanet server
regards
Danny

Hi
Firstly, Thanks for your reply. it would very thankful if you can provide me more detailed information on below questions
1) As a stateful session bean is set sticky. Does it mean all requests from same session will be directed from web-tier to the same jvm initializing that stateful session bean. Also, all invocation to entity bean/other sesson beans from that sticky stateful session bean will take place within same jvm as this stateful session bean is, am l correct ?
2) Is there a latency for "dsync" to do replication of state of HTTPsession and stateful session bean ? If so, there is chance that state of HTTPSession / stateful session bean will be lost if the crash of jvm happen in-between the replication, am l correct ? Is there any way to avoid it ?
regards
Danny

Newbie clustering question / multicasting

Hi,
 Wondering if anybody can point me in the right direction. I want to run
 Weblogic in a cluster. My sticking point seems to be the multicasting
 aspect. I have three boxes with 192.168.1.xxx address. They connect to a
 Netopia SDSL router so I can connect to the Internet. I have 1 WAN IP and 2
 useable public IPs so I can map each of the three IPs to each of my three
 boxes. Been trying to read up on multicasting. From weblogic documentation
 I need a multicast address. Is it correct that this address would be the
 address of my router? But I don't think my router supports multicasting
 since it's just a cheap dsl router. Is there anything I can do to get
 around this problem?
 Thanks.


Correction to my previous post. The multicast addresses can only be in the
 range 224.0.0.1 to 239.255.255.255. The 192.168.1.xxx addresses are fine for
 the machines.
 Giri
 "Giri Alwar" <[email protected]> wrote in message
 news:[email protected]...
 > The multicast address is not the address of the router - rather it is a
 > separate address that is reserved exclusively for the servers in the
 cluster
 > to talk to each other to send out heartbeats, announce JNDI bindings etc.
 > Pick an address (a 192.168.1.xxx address will do fine) that is not used
 for
 > any other purpose and assign it as the multicast address. There is also a
 > utility from weblogic to test if multicast is working correctly before you
 > start the individual servers in the cluster. Refer to the documentation.
 > Giri
 >
 > "Tinou" <[email protected]> wrote in message
 > news:[email protected]...
 > > Hi,
 > >
 > > Wondering if anybody can point me in the right direction. I want to run
 > > Weblogic in a cluster. My sticking point seems to be the multicasting
 > > aspect. I have three boxes with 192.168.1.xxx address. They connect to
 a
 > > Netopia SDSL router so I can connect to the Internet. I have 1 WAN IP
 and
 > 2
 > > useable public IPs so I can map each of the three IPs to each of my
 three
 > > boxes. Been trying to read up on multicasting. From weblogic
 > documentation
 > > I need a multicast address. Is it correct that this address would be
 the
 > > address of my router? But I don't think my router supports multicasting
 > > since it's just a cheap dsl router. Is there anything I can do to get
 > > around this problem?
 > >
 > > Thanks.
 > >
 > >
 > >
 >
 >

Load balancing with multiple clusters (HTTPProxyServlet)

 Hello!
 I'm newbie in Weblogic. I would like to have clustering and load balancing in
 development environment. I've created 2 clusters, with one managed server each.
 I've created a web application for deploying the http proxy servlet and put it
 under another managed server without clustering. Below is my configuration:
 managed server without cluster (as proxy) - Port 8002
 admin server - Port 8001
 cluster_1 - multicast address 237.0.0.11, multicast port 8004, cluster address
 - t3://localhost:8006, t3://localhost:8007
 cluster_2 - multicast address 237.0.0.10, multicast port 8014, cluster address
 - t3://localhost:8006, t3://localhost:8007
 managed_cluster1 - under cluster_1, port 8006
 managed_cluster2 - under cluster_2, port 8007
 in the web.xml of the proxy, i put the following parameters:
 <param-name>WebLogicCluster</param-name>
 <param-value>localhost:8006|localhost:8007</param-value>
 However, when i send the requests to http://localhost:8002/sms, the requests always
 go to the same server, for eg: managed_cluster2?
 If i configure using single cluster, the load balancing will be in proper. What's
 the cause fo the problem? and any solution?
 Thanx in advance.
 Regards,
 joey


You have 2 options here Jordi, either you can use BGP loadbalancing, this requires multipath as BGP by default would only install one route from the BGP table to the RIB hence FIB.
But this may result in excessive IRL (inter rack link) usage in the cluster when traffic coming in on rack0 wants to take the bGP path out on rack1
You could also use ABF (access-list based forwarding) to forcelly push traffic received on rack0 out on the link on rack0 and use an ipsla tracker to fallback to rack1 in case the uplink is gone.
Alternatively to extend this by IGP signaling to redirect traffic preferably to rack1 to start with to minimize the IRL usage.
And then you also have the ability to use RPL in the uplink path to make one link more preferred on teh internet then the other in case you want to control a bit which link is preferably used on rack0 or rack1
regards
xander

Fail over JMS in clustering

Hi ,
          I'm newbies to weblogic.
          Currently I need to use JMS to asychronous messaging.
          version I used is weblogic 705.
          The environment is clustering. There is one Admin server, and 2 managed servers by multicasting.
          Let's say, there have managed server#1 and managed server#2.
          I set up JMS servers in each instance of managed Servers by using distributed Queue.
          And used MDB to consume the message from queue and deploy to each server.
          used persistance store in DB by JDBC connection Pools which is deploy multipools to cluster.
          when firing hte message using distributed queue, messages keep in persistance store according to load balancing.
          - Is there any work around to support failover?
          Lets say, there fired 20 messages and according to the load balancing, each queue in server server got 10 records. but their persistance is in DB.
          - After firing messages, I intentionally shut down the 2nd server, and restart again. Then MDB consume message which is already send to him. But There have a problem, when restarting the 2nd server, the message in queue( persistance in DB) which is related by 1st serer is wipe out from DB persistance.
          Why can't identify why this one happen.
          Anybody can help me.
          Best regards,

I'm not sure what is your question? Why are the messages stored in the DB wiped out?
          I don't remember WebLogic 7.0 too much, is there a way to setup for JMS migration? If so, you can then migrate from 1 server to another so the messages can be processed even if the server goes down.

Error starting Server with Clustering License

          Hello
          I was using WebLogic Application server ver 6.0 evaluation copy
          and everything was working fine. When I have updated the license
          to use the clustering capabilities of Weblogice server , I was
          not able to start the weblogic server and the server was throwing
          following exception.
          Throwable: weblogic.server.ServiceFailureException: Cluster service
          - with nestd exception:
          [java.net.SocketException: Unknown error]
          weblogic.server.ServiceFailureException: Cluster service - with
          nested exception:
          [java.net.SocketException: Unknown error]
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:446)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
          at weblogic.Server.main(Server.java:35)
          '>
          I haven't configured any cluster on my server.
          Do I have to do anything beside running upgradeLicense command
          using the new locense. Is there anything I am missing here.
          Thanks in Advance
          Sunil


Just to be clear, the WLS 6.0 software downloaded from the web site is
          the full product and supports clustering, in-memory replication, etc.
          The evaluation license packaged with the software does not provide keys
          to enable these features. To evaluate these features, you need to
          contact your BEA sales person to get a license to turn these features
          on.
          Kent Kong wrote:
          > hi ,
          > If your wls6.0 is downloaded from the website of bea, it doesnot
          > support cluster service.
          > You should ask our sales for a complete one.
          >
          > Otherwise ,maybe the version of the server in your cluster
          > is not the same.
          >
          > Kent Kong

ShutDown problem in wls6.0

Hi
we are using wls6.0 sp1 on a unix machine. when trying to stop the server by the command
java weblogic.Admin -url <url> -username system -password <password> SHUTDOWN
we get the following exception even if the server is running, and are not able to stop the server from a different session.
Exception in thread "main" java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'class java.rmi.ConnectException'
at weblogic.common.T3Client.sendRecv(T3Client.java:724)
at weblogic.common.AdminServicesImpl.shut(AdminServicesImpl.java:97)
at weblogic.Admin.main(Admin.java:425)
Can anyone give a pointer to the problem.
Thanx
Amit

Generally use kill -9 against the pid.
Peace,
Cameron Purdy
Tangosol Inc.
Tangosol Coherence: Clustered Coherent Cache for J2EE
Information at http://www.tangosol.com/
"Amit Chopra" <[email protected]> wrote in message
news:3c3b22b6$[email protected]..
Hi
we are using wls6.0 sp1 on a unix machine. when trying to stop the serverby the command
java weblogic.Admin -url <url> -username system -password <password>SHUTDOWN
>
we get the following exception even if the server is running, and are notable to stop the server from a different session.
>
Exception in thread "main" java.lang.ClassCastException: ExpectedRemoteException, RuntimeException, or Error but received: 'class
java.rmi.ConnectException'
at weblogic.common.T3Client.sendRecv(T3Client.java:724)
atweblogic.common.AdminServicesImpl.shut(AdminServicesImpl.java:97)
at weblogic.Admin.main(Admin.java:425)
Can anyone give a pointer to the problem.
Thanx
Amit

WLS Clustering: beginner's question..

 Hi,
 Im just about to start get my hands dirty with WLS clustering. As I understand,
 it is not available in the WLS6.0/6.1 eval version downloadable from the web.
 [1] Do I need to purchase a web Logic licence to experiment with clustering..?
 [2] If not, how and where could I obtain the cluster option for the WLS..?
 Thanks in advance,
 -hari


 thanks very much for the info. So I shall attempt to use the eval version on experimenting
 cluster support.
 cheers,
 -hari
 "Lynch" <[email protected]> wrote:
 >Yes that's true.
 >
 >We try our clustering on the basis of the downloaded eval version.
 >
 >"Mike Reiche" <[email protected]> ¼¶¼g©ó¶l¥ó
 >news:3b950be7$[email protected]..
 >>
 >> I believe that clustering is included with the demo license.
 >>
 >> There is a 'cluster' entry in the demo license file.
 >>
 >> Mike
 >
 >
 >

How to restart clustered message store

Hello all,
I'm sure this is a newbie question, but what is the recommended procedure for making configuration changes to a clustered deployment of message store?
I've inherited admin duties for two servers running iMS 6.2. Each server is assigned a portion of the user population with fail-over to the other server. I have some experience with iMS but not with cluster.
If I wanted to make a configuration change (e.g. change the http port), I would normally use the configutil command, then stop and restart iMS to activate the changes.
But what is the proper way to do this when you have multiple servers in a cluster?
Thank you,
BJ

Messaging 6 is FAR better to work with in Cluster than 5.x was. In cluster, to do what you need:
run configutil to make the change.
stop-msg http
start-msg http
done.
yes, even in cluster, this is all you have to do. the start/stop script actually works with the Watcher process, and it's watcher that tells cluste when failover is needed. Since Watcher is doing the stop/start stuff, it knows it means to do that, and doesn't bother the Cluster with it.

Clustering newbie WLS6.1

Similar Messages

Maybe you are looking for