Weblogic Clustering Problem

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

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

Similar Messages

Weblogic clustering problem (4.0.4)

We currently have two Weblogic servers setup in a clustered configuration.
          The cluster seems to operate fine and the clients can use both servers. The
          only problem I have seen is that if the client is not shutdown gracefully then
          it's connections to the Primary Weblogic server get closed but the ones that
          are on the second server in the cluster remain open. Is there a timeout I can
          specify in the server to automatically kill those client connections?
          Robert


I found answer to my question.
Yes it is available.
It is now “Oracle Communications Converged Application Server”

Clustering problems and load balancing question

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


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

OIM installation on RAC DB and Weblogic clusters

I understand its a very broad question but tell me the links/resource/metalink documents references for installing OIM 9.1.0.1 on Weblogic clusters and Oracle RAC DB clusters ? (either or both)
Is OIM 9.1.0.1 compatible with Oracle RAC DB 10gR2 ? I have checked the configuration matrix but still not sure on it. Can anybody confirm this ?
I have gone through the basic installation guide for the same but I still find loopholes in it. If anybody has made any document for his/her purpose, please let me know, very appreciative!
It does not give information about the schema design needed for OIM on Oracle RAC DB like -
1.) During installation of OIM, we need to specify the "User Name" and "Password" of the database account that is created for Oracle Identity Manager.
So is that user needed to be created with all the necessary privileges in RAC DB before starting this installation ?
Thanks in advance,
- oidm.
Edited by: oidm on Aug 3, 2009 12:06 AM

Hey there,
I have checked the certification matrix but still just wanted to specifically know about compatibility of OIM 9.1.0.1 with Oracle RAC DB 10.2.0.2 ? Do they go hand in hand ?
Thanks,
- oidm.
Edited by: oidm on Aug 3, 2009 7:52 PM

Calrification for Weblogic Clustering

Our J2EE application is multitiered where JSPs&Servlets(Frontend) runs in a weblogic instance and EJBs(Backend) runs in two weblogic instances which are clustered. Here the Frontend weblogic instance and one of the clustered Backend weblogic instance are running in a same machine A and the other clustered Backend weblogic instance is running in another machine B. We had tested the following cases for Failover
Note :
please consider "JSPs&Servlets" as Frontend and "EJBs" as Backend.
Weblogic 9.2 and stateless session beans are used.
Frontend is not clustered.
Case 1:
We are doing a transaction where the request from frontend goes to one of the of the Clustered Backend weblogic instance. Before the transaction gets completed this backend weblogic instance is made to shutdown. The transaction has failed over to the another available Clustered Backend weblogic instance . The transaction had completed successfully and the Failover is working fine.
Case 2:
We are doing a transaction where the request from frontend(running in Machine A) goes to the Clustered Backend weblogic instance running in the Machine A itself. Before the transaction gets completed, the machine A is made to shutdown (i.e. both frontend and backend weblogic instance shuts down at the same time). Here the transaction has failed and could not able failover to the other available Backend weblogic instance .
Please clarify whether weblogic cluster supports the Backend failover when both the Frontend and Backend are brought down at the same time?
Any weblogic CLustering experts, please clarify...

Hi Jayesh,
Thanks very much for your reply.
I understood that your reply "You might want to consider collapsing front end (servlet & JSP) and back end (EJB) servers into a single WebLogic server for better fail over support." means that JSP&Servlet and EJB should be combined to form a single archive(EAR) which has to be deployed in single weblogic instance.
Please check whether my assumptions are correct for your suggestion on better failover.
1.The cluster configuration of JSPs&Servlet(web.xml) and EJBs(ejb-jar.xml) running in single weblogic instance will be similar to the cluster configuration of JSPs&Servlet(web.xml) and EJBs(ejb-jar.xml) running in separate weblogic instances. i.e All the configurations are same, but instead of the application running in separate weblogic instances, it will run in single weblogic instance.
2.In the URL for specifying the EJB connection from the JSP&Servlet, the cluster IP address should be used.
You have mentioned that if EJB client is not alive, the failover will not work. Please clarify how the failover will work in this case only(JSP&Servlet and EJB running in single weblogic instance and clustered).
Thanks,
Thiyagu

Weblogic clustering with IIS as web server

          Hi,
          I have two IIS servers and two machines for weblogic. I am planning to have
          a weblogic clustering. I have seen the documentation online. But has some questions
          for which dint find any answers.
          Somewhere on the newsgroup I read , if we will be having IIS proxy-plug in we
          do not need the DNS setup. Is that true ?
          How many IPs and other things I need to do this setup ? What is admin server &
          its role ? configuration how to do it is not avaliable in the documentation.
          Could someone help ?
          Thanks and Regards,
          Sheetal


Hi
          you can find the ore information in the following link
          http://bernal.bea.com/stage/wls/docs70/plugins/isapi.html
          Regards,
          Prasanna Yalam

Can we configure webserver to loaedbalance multiple weblogic clusters?

Can we configure webserver to loadbalance to multiple weblogic clusters?
E.g. Web server X -> Cluster Y & Cluster Z
In the plugin documentation it is not explicit that you can or can't do so.

Refer:- http://download.oracle.com/docs/cd/E17904_01/web.1111/e16435/apache.htm#CDEHDGJG
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13709/failover.htm#i1040344
-Akshay

Weblogic clustering steps

Hi Everybody, I'm new to weblogic so I need your help to know each and every steps that are involved in setting up the weblogic on two different boxes and cluster it finally this cluster should be load balanced with apache server.
I would like to explain little more about the infrastructure that i want to have.
1) Two weblogic servers runs on two different machines (on Linux box).
2) I'll have apache in one server.
3) Each weblogic will have its own adminserver.
4) Both the weblgic servers will connect to same DB
5) Client will connect to the Loadbalancer which is apache server(On windows box).
6) Apache server has to load balance the requests coming from client between the two weblogic servers.
7) I've weblogic12c installed in the servers.
Please let me know if any info that you need for clarifications.
Thanks in advance.
Karthik S

Hi,
Please follow the below link for clustering on two boxes
http://middlewaremagic.com/weblogic/?p=971
and follow the below link for apache to communicate with the weblogic clustered boxes,
http://middlewaremagic.com/weblogic/?p=1311
Regards,
Fabian

Weblogic clustering - Non session objects

Hi,
I have an app that doesn't have any HttpSession object or EJBs. We have only one servlet for entire application that works as a controller and we store all the information regarding the user in the servlet instance variable as cache. None of our objects are Serializable. Can i deploy my application on weblogic cluster. Will weblogic support clustering for thsi kind of applications. We have only one servlet and all other classes are normal java classes. No JSP, EJB etc. No HttpSession or ApplicationContext of servlets are being used.
thanks,
webbie.

Hi,
The There are basically two reasons ...for which we want Clustering:
<h3><font color=maroon>Reason - 1): Failover</font></h3>
This feature needs HttpSession replication...Failover means if a Userhas Logged in to our application and accessing some pages ...then his HttpSession Replica will be available in a Secondary WebLogic Server so...even if his Promary WebLogic Server Goes Down ...His Session data will not be lost...and client can interact with the Application without any Interruption. To Enable Failover in your Clustered Application you need to provide the <persistent-store-type>Tag inside your "<Application>/WEB-INF/weblogic.xml"
   <session-descriptor>
      <persistent-store-type>replicated</persistent-store-type>
   </session-descriptor>
<font color=red><b>NOTE:</b> until u dont put <persistent-store-type> Tag inside your "weblogic.xml" file...by default HttpSession replication will be disabled....because it's default value is "inMemory" means even If your Application has HttpSession ... it wont be replicated on Secondary Server.</font>
<h3><font color=maroon>Reason - 2): LoadBalancing</font></h3>
This feature has NOTHING TO DO with HttpSession replication (in general). It means simply different clients request will be processed by different WebLogic Server Instances in a Round-Robin fashion. I Think this is what you want to implement. Because your application is not using any HttpSession .So thet Application willl not have any Failover. But LoadBalancing is the Default Feature of WebLogic Cluster. U need not to do anything additionally to Achieve it.
<font color=green><b>Note:</b>Means Without Having HttpSession Objects in your Application Still u can have WebLogic Clustering Feature to get the benifit of LoadBalancing.</font>
To know more about Session Replication and it's related issues : http://weblogic-wonders.com/weblogic/2009/12/08/session-replication-issues/
Thanks
Jay SenSharma

WebLogic clustering within the box

          Folks,
          Is it possible to do weblogic clustering within a single UNIX box?
          For example,
          UNIX Machine A(10.9.44.25) have two domains mydomain1 and mydomain2.
          mydomain1 - AdminServer7001 - ManagedServer8001
          mydomain2 - ManagedServer9001
          Is it possible to clustering for ManagedServer8001 and ManagedServer9001?
          Thanks
          - Robot


          "Majic Robot" <[email protected]> wrote:
          >
          >Folks,
          >
          >Is it possible to do weblogic clustering within a single UNIX box?
          >
          >For example,
          >
          >UNIX Machine A(10.9.44.25) have two domains mydomain1 and mydomain2.
          >
          >mydomain1 - AdminServer7001 - ManagedServer8001
          >mydomain2 - ManagedServer9001
          >
          >Is it possible to clustering for ManagedServer8001 and ManagedServer9001?
          >
          >Thanks
          >
          >- Robot
          You can create a clustered environment on a single machine; limits to the numbers
          of managed servers within the cluster is a variable based on available machine
          resources (memory, file handles, kernel limits, etc.).
          You cannot create a cluster though as you suggest above. Recall that clusters
          are defined within a single domain, and you cannot create a cluster that spans
          (is split) between domains.
          To create a cluster on a single machine, you just need to keep the rule that each
          managed server has a unique ipaddress:port combination for its listening address.
          On a single machine you have the option of multi-homing the machine (eg multiple
          IP addresses on a single NIC) or use a single address, but use different ports;
          or use a combination of both.

Weblogic Clustering Advantages + Disadvantages

Hi All,
I have a query about Weblogic clustering concept. First of all I would like to explain my environment architecture.We have SOA and ADF domain configured with High Availability mode in weblogic level.
ie SOA is installed in two servers ( primary & secondary ) and ADF respectively. So total 4 servers.
My Query is : Just want to know about advantages and disadvantages if we configured both Primary and
Secondary in Cluster mode and Stand alone mode in Weblogic.

Hi,
There are no disadvantages as such with the clustering feature.
But you can go through the basic advantages that a clustering feature provides:
http://docs.oracle.com/cd/E11035_01/wls100/cluster/overview.html#wp1011562
Thanks,
Sharmela

Replicated DB & WebLogic Clustering

Hi All,
          In the documentation I've seen on WebLogic clustering, the individual application servers always connect to a single DB back-end. My
          distributed application is connecting to a replicated DB and I would like each of the application servers to connect to a different DB instance. Is
          this possible with WebLogic? How would I set upt the connection pool/data source to achieve this?
          Thanks.
          Kris


Hi,
It is depend on what kind of Load Balancer you are using.
Many H/W Load Balancer has their own server fail detect method.
Most of them are checking the port is reachable.
If the port is not reachable, then the L4 send the request to another port.
Some L7 switchs can detect the URI. and check the index page or other web page.
You don't need too much care how to set the H/W load balaner exactly act like a plug-in module.
Best Regards,
Luke Ham
Edited by: user2088723 on 2008. 9. 6 오전 1:31

Problems with weblogic clustering in 6.1 sp3

We have spent a lot of time trying to get our application deployed to
          a cluster using weblogic 6.1 sp3 and we consistently receive a failure
          when we attempt to start the managed server. This was not a problem
          with weblogic sp1--we got our application to deploy to the cluster
          successfully; although there was another weblogic bug there with
          clients accessing EJB clusters--we won't go into that here...
          We have tried this on both a Windows 2000 machine and an HP machine
          running weblogic sp3. The same error occurs on both platforms.
          The error in deploying our application to the cluster against weblogic
          sp3 looks to have to do with our custom security realm. Inside our
          custom realm we make use of a configurable providerUrl which we set to
          the cluster address/port. The custom realm makes a call where it
          passes in the providerUrl to:
               weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
          When we have our providerUrl set to the cluster address/port--e.g.,
               t3://clustermember1:7001
          and attempt to start the managed server we get the error:
          Starting WebLogic Server ....
          Connecting to http://adminserver:7117...
          The WebLogic Server did not start up properly.
          Exception raised:
          weblogic.management.configuration.ConfigurationException:
          clustermember1 not found
               at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
               at weblogic.management.Admin.initialize(Admin.java:340)
               at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
               at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          When we have our providerUrl set to the admin server address--e.g.,
               t3://adminserver:7117
          everything starts up fine.
          Does anyone know why this would work on sp1 and not sp3 of weblogic
          6.1?
          We verified that all passwords are correct and everything else we
          could determine--any ideas would be helpful.
          We don't want the providerUrl to point at our admin server, we want it
          to point at the cluster address/port.
          When we get the managed server error, we received this error on the
          AdminServer:
          2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
          'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
          Caught naming exception null; throwing RuntimeException.
          javax.naming.CommunicationException. Root exception is
          java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
          unreachable; nested exception is:
               java.net.ConnectException: Connection refused; No available router to
          destination
               at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
               at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
               at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
               at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
               at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
               at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
               at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
               at javax.naming.InitialContext.init(InitialContext.java:222)
               at javax.naming.InitialContext.<init>(InitialContext.java:198)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
               at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
               at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
               at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
               at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
               at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
               at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
          <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
          Servlet failed with Exception
          java.lang.RuntimeException
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
               at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
               at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
               at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
               at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
               at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Thanks for any help.
          Rich


Bottom line:
          In our custom realm we were not handling user guest correctly. Even if you
          have guest user disabled, Weblogic seems to have hard-coded guest to
          send messages to the cluster every-so-often. Not sure there--couldn't get
          an answer out of bea as to exactly why we see guest still being used...
          It seems that with sp3, the user guest interaction started happening earlier
          than it did with sp1, consequently making our realm code fail when trying to
          retrieve the guest user like someone we knew about in our system.
          Hence, our getUser and authUserPassword methods now return null for both
          users guest and system, making the secondary realm (file realm) be used to
          authenticate and resolve guest & system. BEA helped get our code fixed;
          however, we still don't have a lot of depth in understanding Weblogic
          server's use of guest...
          Apparently, in 7.x the guest & system user behavior and configuration is
          different also... We'll see when we start digging into that migration.
          Rich
          [email protected] (Rich Koch) wrote in message news:<[email protected]>...
          > Thanks for the responses--we're working with weblogic support now. We
          > think that the custom realm that we have [the developer that wrote it
          > left the company] is the problem.
          >
          > The original developer was told by someone to check:
          > weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
          >
          > In order to determine if the JNDI was available/ready for the whole
          > cluster.
          >
          > It seems that the meaning/setting of THE_ONE changed with this respect
          > from
          > sp1 to sp3--i.e., this is no longer a valid test to tell us if the
          > JNDI is
          > ready for the cluster.
          >
          > We believe this was used because the 'system' user has to be
          > authenticated before the custom realm is up. Originally, before this
          > check was in place, an exception was received when authenticating
          > 'system'. This appears to be a weblogic limitation/issue. Support
          > has told us that this is different in weblogic 7.0. Unfortunately, we
          > can't upgrade from 6.1 yet.
          >
          > We'll post the solution when this gets figured out.
          >
          > Rak
          >
          > "Sabha" <[email protected]> wrote in message news:<[email protected]>...
          > > There was a security restriction enforced from sp2/sp3 onwards in terms of
          > > looking up mbeans from admin server.
          > >
          > > This might cause things to fail if you are attempting to lookup Mbeans with
          > > guest priviliges from admin server. Also, can you try doing the following:
          > >
          > > Run " java weblogic.Admin -url adminServer -username system -password
          > > .... -GET -pretty -type Server" and check whether the named clustermember1
          > > is available in the list or not.
          > >
          > > Also you seem to be getting some security exception - can you check that.
          > >
          > > t3://tomtate.msais.com:7119: Destination
          > > unreachable; nested exception is:
          > >
          > > --- Try running weblogic.Admin PING on this one and see whether you are
          > > able to reach this server upon the error message.
          > >
          > > --Sabha
          > >
          > > "Rich Koch" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > We have spent a lot of time trying to get our application deployed to
          > > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
          > > > when we attempt to start the managed server. This was not a problem
          > > > with weblogic sp1--we got our application to deploy to the cluster
          > > > successfully; although there was another weblogic bug there with
          > > > clients accessing EJB clusters--we won't go into that here...
          > > >
          > > > We have tried this on both a Windows 2000 machine and an HP machine
          > > > running weblogic sp3. The same error occurs on both platforms.
          > > >
          > > > The error in deploying our application to the cluster against weblogic
          > > > sp3 looks to have to do with our custom security realm. Inside our
          > > > custom realm we make use of a configurable providerUrl which we set to
          > > > the cluster address/port. The custom realm makes a call where it
          > > > passes in the providerUrl to:
          > > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
          > > >
          > > > When we have our providerUrl set to the cluster address/port--e.g.,
          > > > t3://clustermember1:7001
          > > >
          > > > and attempt to start the managed server we get the error:
          > > >
          > > > Starting WebLogic Server ....
          > > > Connecting to http://adminserver:7117...
          > > >
          > ***************************************************************************
          > > > The WebLogic Server did not start up properly.
          > > > Exception raised:
          > > > weblogic.management.configuration.ConfigurationException:
          > > > clustermember1 not found
          > > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
          > > > at weblogic.management.Admin.initialize(Admin.java:340)
          > > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          > > > at weblogic.Server.main(Server.java:35)
          > > > Reason: Fatal initialization exception
          > > >
          > ***************************************************************************
          > > >
          > > > When we have our providerUrl set to the admin server address--e.g.,
          > > > t3://adminserver:7117
          > > >
          > > > everything starts up fine.
          > > >
          > > > Does anyone know why this would work on sp1 and not sp3 of weblogic
          > > > 6.1?
          > > > We verified that all passwords are correct and everything else we
          > > > could determine--any ideas would be helpful.
          > > >
          > > > We don't want the providerUrl to point at our admin server, we want it
          > > > to point at the cluster address/port.
          > > >
          > > > When we get the managed server error, we received this error on the
          > > > AdminServer:
          > > >
          > > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
          > > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
          > > > Caught naming exception null; throwing RuntimeException.
          > > > javax.naming.CommunicationException. Root exception is
          > > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
          > > > unreachable; nested exception is:
          > > > java.net.ConnectException: Connection refused; No available router to
          > > > destination
          > > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          > > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          > > > at
          > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:307)
          > > > at
          > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:211)
          > > > at
          > > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          > > ory.java:149)
          > > > at
          > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
          > > > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
          > > > at javax.naming.InitialContext.init(InitialContext.java:222)
          > > > at javax.naming.InitialContext.<init>(InitialContext.java:198)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
          > > Realm.java:416)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
          > > lm.java:347)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
          > > java:51)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
          > > 225)
          > > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
          > > Realm.java:578)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
          > > a:221)
          > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
          > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
          > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
          > > > at
          > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
          > > ava:356)
          > > > at
          > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
          > > tSecurityManager.java:205)
          > > > at
          > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          > > ntext.java:2518)
          > > > at
          > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          > > :2260)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
          > > >
          > > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
          > > al2)]
          > > > Servlet failed with Exception
          > > > java.lang.RuntimeException
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
          > > a:260)
          > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
          > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
          > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
          > > > at
          > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
          > > ava:356)
          > > > at
          > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
          > > tSecurityManager.java:205)
          > > > at
          > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          > > ntext.java:2518)
          > > > at
          > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          > > :2260)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > >
          > > >
          > > > Thanks for any help.
          > > >
          > > > Rich

Problems with weblogic clustering setup

Hi all, I'm having problems extending a weblogic 9.2 cluster from vertical to orizontal. The environment is composed by two physical servers A and B. On A it's running the node manager, the admin console and two nodes, on B I've just installed weblogic 9.2, registered the licence.
I'm reading this guide: http://egeneration.beasys.com/wls/docs103/cluster/setup.html#wp742559 but I think this guide is non clear.
1) I added the new machine into the admin console
2) I added the new server to the configuration (environmnent -> cluster)
3) I created a new node on the new server and I associate it to the cluster and machine.
moreover I checked the ports so that it should be set correctly.
After I start the nodemanager into B and after adminconsole from A tries to connect to B I get this into the console
[root@engtest4 bea]# /opt/bea/weblogic92/server/bin/startNodeManager.sh
+ CLASSPATH=/opt/bea/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit90_150_10/lib/tools.jar:/opt/bea/weblogic92/server/lib/weblogic_sp.jar:/opt/bea/weblogic92/server/lib/weblogic.jar:/opt/bea/weblogic92/server/lib/webservices.jar:/opt/bea/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit90_150_10/lib/tools.jar:/opt/bea/weblogic92/server/lib/weblogic_sp.jar:/opt/bea/weblogic92/server/lib/weblogic.jar:/opt/bea/weblogic92/server/lib/webservices.jar::/opt/bea
+ export CLASSPATH
+ export PATH
+ cd /opt/bea/weblogic92/common/nodemanager
+ set -x
+ '[' '' '!=' '' ']'
+ '[' '' '!=' '' ']'
+ /opt/bea/jrockit90_150_10/bin/java -jrockit -Xms128m -Xmx256m -Xverify:none -Djava.security.policy=/opt/bea/weblogic92/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/opt/bea/jrockit90_150_10 weblogic.NodeManager -v
<Jan 14, 2009 5:10:22 PM> <INFO> <Loading domains file: /opt/bea/weblogic92/common/nodemanager/nodemanager.domains>
<Jan 14, 2009 5:10:23 PM> <INFO> <Loading identity key store: FileName=/opt/bea/weblogic92/server/lib/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Jan 14, 2009 5:10:23 PM> <INFO> <Loaded node manager configuration properties from '/opt/bea/weblogic92/common/nodemanager/nodemanager.properties'>
Node manager v9.2.2.0
Configuration settings:
NodeManagerHome=/opt/bea/weblogic92/common/nodemanager
ListenAddress=
ListenPort=5556
ListenBacklog=50
SecureListener=true
AuthenticationEnabled=true
NativeVersionEnabled=true
CrashRecoveryEnabled=false
JavaHome=/opt/bea/jrockit90_150_10/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/opt/bea/weblogic92/common/nodemanager/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1
LogAppend=true
LogToStderr=true
LogFormatter=weblogic.nodemanager.server.LogFormatter
DomainsFile=/opt/bea/weblogic92/common/nodemanager/nodemanager.domains
DomainsFileEnabled=true
StateCheckInterval=500
Domain name mappings:
wl_server -> /opt/bea/weblogic92/samples/domains/wl_server
base_domain -> /opt/bea/user_projects/domains/base_domain
<Jan 14, 2009 5:10:24 PM> <INFO> <Secure socket listener started on port 5556>
<Jan 14, 2009 5:10:38 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
     at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
     at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
     at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
     at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:595)
<Jan 14, 2009 5:11:54 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
     at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
     at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
     at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
     at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:595)
<Jan 14, 2009 5:11:54 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
     at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
     at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
     at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
     at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:595)
should server A and B have the same domain configuration? (same files)
Regards
Marco

Yes, you must have the same domain configuration on the server B. Usually I copy the domain directory on the server B to have the same configuration. the directory with "salt file" should be the "<domain_dir>/security"...
Hope this helps...
Mariano

Weblogic clustered server instance failed in less than 30 hours with no load/utilization

system description: hpux 11, jdk 1.2.2_03, weblogic 5.1 sp1, two clustered
instances on one box, fail over to second box on shared file system.
problem:
in our custom weblogic monitoring scripts, we run the weblogic ping command
every ten seconds with the following command:
java weblogic.Admin t3://10.7.192.103:7001 PING 10 56 system weblogic
this weekend, both of our instances failed at one point and returned this
error message multiple times:
Exception in thread "main" java.lang.NullPointerException
at
weblogic.common.internal.BootServicesStub.findOrCreateClientContext(BootServ
icesStub.java:112)
at weblogic.common.T3Client.connect(T3Client.java:384)
at weblogic.Admin.connect(Admin.java:133)
at weblogic.Admin.main(Admin.java:216)
our monitoring scripts successfull revived the instances, but there is a
problem with this.
problem: there was no load or utlization of the weblogic server instances
at the time of the failure. both instances had only been up for about 30
hours when they failed. is this due to weblogic instability? i hope not.
a max uptime of 30 hours doesn't say much for the reliability of the product
especially since there was zero utilization...
andrew park

This looks to be a bug (obviously). I will have someone take a look and
let you know.
Cheers
Mark g
In article <8gbj2d$m9m$[email protected]>, [email protected] says...
system description: hpux 11, jdk 1.2.2_03, weblogic 5.1 sp1, two clustered
instances on one box, fail over to second box on shared file system.
problem:
in our custom weblogic monitoring scripts, we run the weblogic ping command
every ten seconds with the following command:
java weblogic.Admin t3://10.7.192.103:7001 PING 10 56 system weblogic
this weekend, both of our instances failed at one point and returned this
error message multiple times:
Exception in thread "main" java.lang.NullPointerException
at
weblogic.common.internal.BootServicesStub.findOrCreateClientContext(BootServ
icesStub.java:112)
at weblogic.common.T3Client.connect(T3Client.java:384)
at weblogic.Admin.connect(Admin.java:133)
at weblogic.Admin.main(Admin.java:216)
our monitoring scripts successfull revived the instances, but there is a
problem with this.
problem: there was no load or utlization of the weblogic server instances
at the time of the failure. both instances had only been up for about 30
hours when they failed. is this due to weblogic instability? i hope not.
a max uptime of 30 hours doesn't say much for the reliability of the product
especially since there was zero utilization...
andrew park
==================================================
NewsGroup Rant
==================================================
Rant 1.
The less info you provide about your problem means
the less we can help you. Try to look at the
problem from an external perspective and provide
all the data necessary to put your problem in
perspective.

Weblogic Clustering Problem

Similar Messages

Maybe you are looking for