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

Similar Messages

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>Reason - 1): Failover</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>
NOTE: 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.
<h3>Reason - 2): LoadBalancing</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.
Note:Means Without Having HttpSession Objects in your Application Still u can have WebLogic Clustering Feature to get the benifit of LoadBalancing.
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

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

Weblogic Clustering Replica Session not Recovering

Dear All,
Have One domains with WLS 10.3.4 on two physical machines, each machine hosting one managed server, cluster of the two servers, node manager on both servers and admin server on one of the servers. Using unicast and in-memory replication with replicate if clustered set in the weblogic.xml.
Apache balancing between the two and selected options to allow proxy plugin in the domain.
Question is I bring both servers up,
Log the user into test application.
In the console I can see from Cluster Monitoring that a single user connects on Managed Server 1 and that the session is correctly replicated onto Managed Server 2.
I then fail Managed Server 1 which is hosting the primary session, on manual page refresh the users request goes to the Managed Server 2 with the user staying logged in (as expected).
However when I return the failed Managed Server 1 to service I expected the current session now on Managed Server 2 to be replicated back to the Managed Server 1 (in case Managed Server 2 that is now hosting the primary session fails).
No matter how long I wait this replication does not take place, HOWEVER if after the Managed Server 1 is returned to service I manually refresh the Web Page which connects to Managed Server 2 this kicks the replication into action and creates a session replica back on Managed Server 1.
I don't think this is exected behaviour so any idea what is going wrong?
In the oracle docs it says
"In a two-server cluster, the client would transparently fail over to the server hosting the secondary session state. However, replication of the client’s session state would not continue unless another WebLogic Server became available and joined the cluster. For example, if the original primary server was restarted or reconnected to the network, it would be used to host the secondary session state. "
but in this case the second bit does not seem to host the secondary state unless the web page is actually used again (at which point you see the replica state created, it's almost like it will replicate going forwards but ignores the current state and does not re-sync between the managed servers, leading to a user being logging out if a flip-flop server failure test is carried out.
Thanks
Edited by: user10645195 on 18-Feb-2011 08:46
Edited by: user10645195 on 18-Feb-2011 08:52

HI,
The HttpSession replication happens Only when WebLogic creates a New HttpSession or Container encounters "session.setAttribute(obj,obj)" method...It means the Data is replicated to the Secondary JVM HttpSession only when application calls the setAttribute method of HttpSession. And in this case only the modified part of data is replicated NOT the complete HttpSession data.
So i think u can try adding a Simple temporary attribute in the HttpSession like
session.setAttribute("dummyData",""+new java.util.Date());
Now make sure that the above code is placed in each and every page of your application...sothat whenever a client will request the because of setAttribute() the Session modified data (dummyData) will be replicated...and if there are more setAttribute() on that page then all the those also will be replicated...
Example:
Map map = new HashMap();
session.setAttribute("map", map); -------> Here Session data Will be replicated to Node-2 (bcoz of setAttribute()) 
map.put("one", "aaa"); No Replication (Means No Session data Refresh...bcoz setAttribute is not called...)
then from page1.jsp I go to page2.jsp and I do this:
Map map = (Map)session.getAttribute("map");
map.put("two", "bbb"); No Replication (Means No Session data Refresh...bcoz setAttribute is not called...)
and then from page2.jsp I go to page3.jsp and I do this:
Map map = (Map)session.getAttribute("map");
map.put("three", "ccc"); No Replication (Means No Session data Refresh...bcoz setAttribute is not called...)
Now you will see On The node2 the sessioncontains an EMPTY map ! (That is Correct) because when you executed 
Map map = new HashMap();
session.setAttribute("map", map);

At that time The Map was not containing any data in it.

You need to try this:
Map map = new HashMap();
session.setAttribute("map", map);
map.put("one", "aaa"); ----> Now session.setAttribute("map", map); here session data will be refreshed in Node-2
then from page1.jsp I go to page2.jsp and I do this:
Map map = (Map)session.getAttribute("map");
map.put("two", "bbb"); ----> Now session.setAttribute("map", map); here session data will be refreshed in Node-2
and then from page2.jsp I go to page3.jsp and I do this:
Map map = (Map)session.getAttribute("map");
map.put("three", "ccc"); ----> Now session.setAttribute("map", map); here session data will be refreshed in Node-2
It means until u don't call session.setAttribute(---, ---)...The Session Data is not replicated (refreshed) to the Second Node(Secondary JVM).
Thanks
Jay SenSharma
http://middlewaremagic.com/ (Middleware magic Is Here)

Special consideration for coding clients while using weblogic clustering

 Hi.
 I wanted to know whether there are any special consdirations to
 be taken while coding clients(servlets in our case) for EJBs when
 we are using clustering of App servers.
 In our setup, we are following the recommended 2-tier architecture
 for Weblogic5.1
 thanks and regards,
 Amol


Amol wrote:
 > Hi,
 > adding a couple of points to the previous mail:
 > 1. In case of servlet failure after doXXX() method has been
 > called and before the method returns, if the app server
 > fails, will doXXX() be called again on the servlet in the
 > secondary server?
 > 2. How much time does it take for the servlet session on
 > one machine to be replicated on the second machine when
 > using in-memory replication.
 It depends on the size of the object and complexity.
 -- Prasad
 >
 > Thanks,
 > Amol
 >
 > "Amol" <[email protected]> wrote:
 > >
 > >Hi kumar (and everybody),
 > >
 > >Your opinion resolves the doubt i had in mind, since even
 > >WebLogic
 > >docs do not say anything about clustering affecting the
 > >coding
 > >of bean clients.
 > >
 > >However may I request you to please evaluate the same
 > >query with
 > >respect to the following conditions:
 > >1. The Session bean calls a stored proc on the db. After
 > >the call
 > >to stored proc and before the stored proc returns with
 > >the results,
 > >the app server fails.
 > >Here there could be two cases of interest, a) Stored proc
 > >does
 > >a write on db -OR- b) Stored proc does only a read on
 > >db
 > >2. The Session bean calls an Entity bean which "writes"
 > >to the
 > >db. The db write is successful, but before the entire
 > >call to the
 > >session bean is completed(that is before user gets his
 > >results)
 > >the Server fails. Now permanent changes have been made
 > >to the db,
 > >but client doesnt get the results.
 > >
 > >Please note the fact that we are using recommended 2-tier
 > >architecture
 > >and in this case server failure would imply failure of
 > >Servlet
 > >as well as the beans.
 > >
 > >Regards,
 > >Amol
 > >--------------------------
 > >
 > >Kumar Allamraju <[email protected]> wrote:
 > >>Absolutely not. Make sure the objects you are putting
 > >>in the session are
 > >>serializable.
 > >>
 > >>
 > >>
 > >>Amol wrote:
 > >>
 > >>> Hi.
 > >>> I wanted to know whether there are any special consdirations
 > >>to
 > >>> be taken while coding clients(servlets in our case)
 > >>for EJBs when
 > >>> we are using clustering of App servers.
 > >>>
 > >>> In our setup, we are following the recommended 2-tier
 > >>architecture
 > >>> for Weblogic5.1
 > >>>
 > >>> thanks and regards,
 > >>> Amol
 > >>
 > >
 Cheers
 - Prasad

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.

Issue with Distributed Queue and WebLogic Clustering

Hi, When a message is received by distributed queue, MDB is processing the message on two managed servers. There seems to be issue with clustering and the physical queues present on both the managed servers are receving the message.
Our environment configuration details are as below:
One Web logic Cluster with 2 nodes (2 managed web logic servers).
One MDB deployed on the cluster listening to a queue with JNDI name “xng/jms/CODEventsQueue”
One Distributed queue with two members on the two nodes of the cluster, and with JNDI name “xng/jms/CODEventsQueue”
Two members of the distributed queue deployed on two JMS servers, which are separately deployed on each managed server .
And the distributed queue is deployed on the cluster.
Any help is appreciated.
Thanks
Sampath

It is not clear to me how you concluded that "both the managed servers are receiving the message". Did you monitor the queues' statistics, or did you see both MDB instances received the same message?
It looks like that you using a weighted distributed queue. Do the two physical queues that compose the distributed queue have their own JNDI names? If so, what are they?
Have you tried to use a uniform distributed queue and see if the same behavior shows up?
You can find more about uniform distributed destination at
http://edocs.bea.com/wls/docs103/jms/dds.html#wp1313713
BTW, which WebLogic Server releases are you using? Could you provide the distributed queue configuration?
Thanks,
Dongbo

Using weblogic clustering to improve permance in J2EE applications

I'm wondering if someone can help me to figure out a solution to some performance issues already existing in my Weblogic-based application.
          - Current configuration: 2 weblogic domains where each domain contains it's own weblogic instance and each instance is running different applications and all running in the same computer. I'm not using clustering.
          Configuration described above have performance issues, so I would like to receive tipical recommendations to improve performance including a change of the configuration of weblogic servers. One of my ideas is to use clustering as follows:
          Have each J2EE app described above running on their own computer, where each computer includes one weblogic domain with two instances of the same application with clustering enabled for fail-over and load-balancing. This idea is makes some sense, or I'm suggesting a very bad idea ?
          thanks for your help

I'd first need to understand what is causing the performance issues. ie what is the factor limiting your performance? Are you at 100% CPU? Are you waiting for a database to respond etc? Once we have that analysis, we can probably give you better advice on how to fix it.
          -- Rob
          WLS Blog http://dev2dev.bea.com/blog/rwoollen/

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

Replicated DB & WebLogic Clustering

Similar Messages

Maybe you are looking for