Fail over is not happening in Weblogic JSP Server

Hi..
We have 6 Weblogic instances running as application server (EJB) and 4 Weblogic
instances running as web server (JSP). We have configured one cluster for EJB
servers and one cluster for JSP servers. In front-end we are using four Apache
servers to proxy the request to Weblogic JSP cluster. In my httpd.conf file I
have configured with the Weblogic cluster. I can see the requests are going in
all the servers and believe the cluster is working fine in terms of load balancing
(round-robin). The clients are accessing the servers using CSS (Cisco Load Balancer).
But when we test the fail-over in the cluster, we are facing problems. Let me
explain the scenarios of the fail-over test:
1. The load was generated by the Load Generator
2. When the load is there, we shut down one Apache server, even though there was
some failed transaction, immedialty the servers become stable. So fail-over is
happening in this stage.
3. When I shutdown one EJB instance, again after some failed transactions, the
transactions become stable
4. But, when I shutdown one JSP instance, immediately the transaction failed and
it is not able to fail over to another JSP server and the number of failed transactions
increased.
So I guess, there is some problem in the proxy plug-in configuration, so that
when I shutdown one JSP server, still the requests are being send to the JSP server
by the Apache proxy plug-in.
I have read various queries posted in the News Groups and found some information
about configuring session and cookie information in the Weblogic.xml file. Also
I’m not sure what are all the configurations needs to be done in the Weblogic.xml
and httpd.conf file. Kindly help me to resolve the problem. I would appreciate
your response.
===============================================================
My httpd.conf file plug-in configuration:
###WebLogic Proxy Directives. If proxying to a WebLogic Cluster see WebLogic
Documentation.
<IfModule mod_weblogic.c>
WebLogicCluster X.X.X.X1:7001,X.X.X.X2:7001,X.X.X.X3:7001,X.X.X.X4:7001
MatchExpression *.jsp
</IfModule>
<Location /apollo>
SetHandler weblogic-handler
DynamicServerList ON
HungServerRecoverSecs 600
ConnectTimeoutSecs 40
ConnectRetrySecs 2
</Location>
==============================================================
Thanks in advance,
Siva.

Hi,
I can see that bug 13703600 is already got fixed in 12.1.2 but still you same problem please raise ticket with oracle support.
Regrds,
Kal

Similar Messages

Firefox Proxy Fail-over is not working correctly

I am in a corporate environment, where we must use a complex auto-proxy, by configuring an automatic proxy configuration of http://proxyconf/proxy.pac. I am seeing an intermittent failure with Firefox 3.6.13, where the same site will load after a delay in IE (e.g. it works for half an hour, then fails for a while, etc.).
By using Wireshark and tracing the packets, I have identified that a proxy server is intermittently failing, and Firefox is failing to try the second proxy. The auto proxy rule that is being invoked is:
if (!isResolvable(host)) return "PROXY 172.16.39.201:8080; PROXY 10.241.32.28:8080";
The problem is that Firefox is never failing over - it tries the 172 address 6 times in a row, then gives up and displays the "The proxy server is refusing connections" "Firefox is configured to use a proxy server that is refusing connections." "* Check the proxy settings to make sure that they are correct." "* Contact your network administrator to make sure the proxy server is working." error message. It continues with this behavior regardless of how many attempts, reloads, restarts are tried.
IE on the other hand will try and fail with the 172 address, and then start using the 10. address (which works correctly). Several other applications also work correctly, such as IRC clients.
Obviously the corporate proxy that is failing must be fixed, however Firefox is failing to utilitize the 2nd proxy after the first one fails.
Seems like a bug.
Is there some easy way for me to replace the proxy file with my own file? E.g. replace http://http://proxyconf/proxy.pac with file://c:\..., or use some add-on?
It must be an autoproxy script, as there is no single proxy that I can use for all addresses.

You can correct this issue by forcing the file blocklist.xml to update or wait until Firefox updates the file. 
That update will remove the severity="0" flags in the file that cause the problem.
See:
* [/questions/832793?page=2#answer-198407]
* http://forums.mozillazine.org/viewtopic.php?p=10899869#p10899869
*[https://bugzilla.mozilla.org/show_bug.cgi?id=663722 Bug 663722] - The blocklist output is including severity="0" where it shouldn't be

Load balancing not happening on UDQ in weblogic 11g

Hi Team,
I have a 2 clusters with two managed servers each on different machines
Cluster A(On machine 1)
Managed server A (on machine 1)
Managed server B(on machine 2)
I have created 2 JMS servers
JMS Server A on Managed server A
JMS Server Bon Managed server B
and a JMS module on Cluster A
and JMS connection factory targeted on Cluster A and a uniform distributed queue targeted on JMS server A and JMS Server B
But load balancing is not happening only one managed server is loaded at a time.. Using weblogic 11(aka 10.2.3)
Tried disabling server affinity but it did not help ...Can any one please let me know how to fix this?

Hi,
When you say load is not balanced and reaching only one managed server.
I assume both the UDD's targets are reachable and are visible in JNDI tree ?
also , what kind of application is it - i,e is it clustered app that would be seen as consumers on each UDQ ?
take a look at the app and check if its clusterred . along with that also take a look at the number of consumers on UDQ instances.
Let me know what you find.
Sri

Exception while failing over to 2nd RAC Node

We are using Weblogic 10.3.4. Our setup is that we have a Web Application (A tapestry front end Web UI) and EJb 2.1 back-end talking to the Oracle database. The EJB’s are CMP. Our product always was just stand alone and it wasn’t until this release we needed to make it work with RAC. To get this to work we followed the model of having a Multidatasource with datasources pointing to our RAC nodes. We have two types of datasources that we use persistent and non-persistent. And we are using the Oracle thin driver – non-XA for RAC Service Instances, supporting global transactions.
When we do failover to the 2nd node we get a nasty exception in our GUI but after logging out and logging back it we are fine.
My question is that I assumed I shouldn't have to restart our web-application and it should have stayed up ?? Or is there something wrong with our setup ?
Thanks,
Ian

Showing us the exception and/or the error messages at the server might help...
Note that failing over does not save any ongoing connection or transaction that
had been to the dead RAC node... Does your web-app get-use-close JDBC
connections on a per-user-invoke basis, or does it hold onto connections?
Joe

How can WLS use JSP pages in a Web Application witth just a JRE [Web Application, WAR, JSP, weblogic.jsp.pageCheckSeconds and JRE]

 How can WLS use JSP pages in a Web Application (either a .war file or a war directory structure) without a java compiler?
 I suspect either the JSP specification is flawed (i.e. it doesn't take account of servers using just a JRE), or BEA's implementation is broken.
 Production servers do not have a JDK installed. They only have a JRE. Therfore a java compiler is not present on the machine that the Web Application is deployed onto.
 On the development machine, when the server is requested to load the JSP it creates a tmpwar directory within the Web Application directory structure. This is then included in the resultant .war file thus:
 D:\war>jar -tf gmi.war
 META-INF/
 META-INF/MANIFEST.MF
 gmiService.jsp
 WEB-INF/
 WEB-INF/classes/
 WEB-INF/classes/com/
 WEB-INF/classes/com/bt/
 WEB-INF/classes/com/bt/gmi/
 WEB-INF/classes/com/bt/gmi/gmiService.class
 WEB-INF/getList.xsl
 WEB-INF/getListByConnection.xsl
 WEB-INF/getListByDistrict.xsl
 WEB-INF/getListByDistrictConnection.xsl
 WEB-INF/lib/
 WEB-INF/source/
 WEB-INF/source/build.bat
 WEB-INF/source/gmiService.java
 WEB-INF/web.xml
 WEB-INF/weblogic.xml
 tmpwar/
 tmpwar/jsp_servlet/
 tmpwar/jsp_servlet/_gmiservice.class
 tmpwar/jsp_servlet/_gmiservice.java
 When deployed on the production server with the web.xml file set to use the following values (note XML stripped):
 weblogic.jsp.pageCheckSeconds
 -1
 weblogic.jsp.precompile
 false
 weblogic.jsp.compileCommand
 javac
 weblogic.jsp.verbose
 true
 weblogic.jsp.packagePrefix
 jsp_servlet
 weblogic.jsp.keepgenerated
 false
 And in the weblogic.properties file:
 weblogic.httpd.webApp.gmi=war/gmi
 I've also tried with the .war file, but that insists on creating another tmpwar directory outside of the .war file.
 Then, although I have set pageCheckSeconds to -1 (don't check and don't recompile) ter production server still attempts to recompile the JSP's:
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: init
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param verbose initialized to: true
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param packagePrefix initialized to: jsp_servlet
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param compileCommand initialized to: javac
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param srcCompiler initialized to weblogic.jspc
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param superclass initialized to null
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param workingDir initialized to: /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param pageCheckSeconds initialized to: -1
 Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: initialization complete
 Mon Sep 25 11:40:12 BST 2000: <WebAppServletContext-gmi> Generated java file: /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.java
 Mon Sep 25 11:40:14 BST 2000:<E> <WebAppServletContext-gmi> Compilation of /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.java failed: Exception in thread "main" java.lang.NoClassDefFoundError: sun/tools/javac/Main
 java.io.IOException: Compiler failed executable.exec([Ljava.lang.String;[javac, -classpath, /opt/Solaris_JRE_1.2.1_04/lib/rt.jar:/opt/Solaris_JRE_1.2.1_04/lib/i18n.jar:/opt/Solaris_JRE_1.2.1_04/classes:/var/wls/5.1/weblogic/lib/weblogic510sp4boot.jar:/var/wls/5.1/weblogic/classes/boot:/var/wls/5.1/weblogic/eval/cloudscape/lib/cloudscape.jar:/var/wls/5.1/weblogic/lib/wleorb.jar:/var/wls/5.1/weblogic/lib/wlepool.jar:/var/wls/5.1/weblogic/lib/weblogic510sp4.jar:/var/wls/5.1/weblogic/license:/var/wls/5.1/weblogic/classes:/var/wls/5.1/weblogic/lib/weblogicaux.jar:/opt/wls-servers/gmiServer/weblogic/gmiServer/serverclasses:/opt/wls-servers/gmiServer/weblogic/lotusxsl.jar:/opt/wls-servers/gmiServer/weblogic/xerces.jar:/opt/wls-servers/gmiServer/weblogic/logging.jar::/opt/wls-servers/gmiServer/weblogic/war/gmi/WEB-INF/classes:/opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war, -d, /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war, /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.java])
 at java.lang.Throwable.fillInStackTrace(Native Method)
 at java.lang.Throwable.fillInStackTrace(Compiled Code)
 at java.lang.Throwable.<init>(Compiled Code)
 at java.lang.Exception.<init>(Compiled Code)
 at java.io.IOException.<init>(Compiled Code)
 at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(Compiled Code)
 at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
 at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code)
 at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
 at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:187)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:142)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:744)
 at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:692)
 at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:251)
 at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 at weblogic.kernel.ExecuteThread.run(Compiled Code)


The default Java compiler from sun lives in the tools.jar that comes with
 the JDK. Just add that to your set of JARs which are deployed in production
 and you should be fine. No need to install the full JDK - just make the
 tools.jar available to WebLogic.
 Regards
 James
 James Strachan
 =============
 email: [email protected]
 web: http://www.metastuff.com
 "Martin Webb" <[email protected]> wrote in message
 news:[email protected]...
 >
 > How can WLS use JSP pages in a Web Application (either a .war file or a
 war directory structure) without a java compiler?
 >
 > I suspect either the JSP specification is flawed (i.e. it doesn't take
 account of servers using just a JRE), or BEA's implementation is broken.
 >
 > Production servers do not have a JDK installed. They only have a JRE.
 Therfore a java compiler is not present on the machine that the Web
 Application is deployed onto.
 >
 > On the development machine, when the server is requested to load the JSP
 it creates a tmpwar directory within the Web Application directory
 structure. This is then included in the resultant .war file thus:
 >
 > D:\war>jar -tf gmi.war
 > META-INF/
 > META-INF/MANIFEST.MF
 > gmiService.jsp
 > WEB-INF/
 > WEB-INF/classes/
 > WEB-INF/classes/com/
 > WEB-INF/classes/com/bt/
 > WEB-INF/classes/com/bt/gmi/
 > WEB-INF/classes/com/bt/gmi/gmiService.class
 > WEB-INF/getList.xsl
 > WEB-INF/getListByConnection.xsl
 > WEB-INF/getListByDistrict.xsl
 > WEB-INF/getListByDistrictConnection.xsl
 > WEB-INF/lib/
 > WEB-INF/source/
 > WEB-INF/source/build.bat
 > WEB-INF/source/gmiService.java
 > WEB-INF/web.xml
 > WEB-INF/weblogic.xml
 > tmpwar/
 > tmpwar/jsp_servlet/
 > tmpwar/jsp_servlet/_gmiservice.class
 > tmpwar/jsp_servlet/_gmiservice.java
 >
 > When deployed on the production server with the web.xml file set to use
 the following values (note XML stripped):
 >
 > weblogic.jsp.pageCheckSeconds
 > -1
 >
 > weblogic.jsp.precompile
 > false
 >
 > weblogic.jsp.compileCommand
 > javac
 >
 > weblogic.jsp.verbose
 > true
 >
 > weblogic.jsp.packagePrefix
 > jsp_servlet
 >
 > weblogic.jsp.keepgenerated
 > false
 >
 >
 > And in the weblogic.properties file:
 >
 > weblogic.httpd.webApp.gmi=war/gmi
 >
 > I've also tried with the .war file, but that insists on creating another
 tmpwar directory outside of the .war file.
 >
 >
 > Then, although I have set pageCheckSeconds to -1 (don't check and don't
 recompile) ter production server still attempts to recompile the JSP's:
 >
 >
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: init
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param
 verbose initialized to: true
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param
 packagePrefix initialized to: jsp_servlet
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param
 compileCommand initialized to: javac
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param
 srcCompiler initialized to weblogic.jspc
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param
 superclass initialized to null
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param
 workingDir initialized to:
 /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp: param
 pageCheckSeconds initialized to: -1
 > Mon Sep 25 11:40:11 BST 2000: <WebAppServletContext-gmi> *.jsp:
 initialization complete
 > Mon Sep 25 11:40:12 BST 2000: <WebAppServletContext-gmi> Generated java
 file:
 /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.
 java
 > Mon Sep 25 11:40:14 BST 2000:<E> <WebAppServletContext-gmi> Compilation of
 /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.
 java failed: Exception in thread "main" java.lang.NoClassDefFoundError:
 sun/tools/javac/Main
 >
 > java.io.IOException: Compiler failed
 executable.exec([Ljava.lang.String;[javac, -classpath,
 /opt/Solaris_JRE_1.2.1_04/lib/rt.jar:/opt/Solaris_JRE_1.2.1_04/lib/i18n.jar:
 /opt/Solaris_JRE_1.2.1_04/classes:/var/wls/5.1/weblogic/lib/weblogic510sp4bo
 ot.jar:/var/wls/5.1/weblogic/classes/boot:/var/wls/5.1/weblogic/eval/cloudsc
 ape/lib/cloudscape.jar:/var/wls/5.1/weblogic/lib/wleorb.jar:/var/wls/5.1/web
 logic/lib/wlepool.jar:/var/wls/5.1/weblogic/lib/weblogic510sp4.jar:/var/wls/
 5.1/weblogic/license:/var/wls/5.1/weblogic/classes:/var/wls/5.1/weblogic/lib
 /weblogicaux.jar:/opt/wls-servers/gmiServer/weblogic/gmiServer/serverclasses
 :/opt/wls-servers/gmiServer/weblogic/lotusxsl.jar:/opt/wls-servers/gmiServer
 /weblogic/xerces.jar:/opt/wls-servers/gmiServer/weblogic/logging.jar::/opt/w
 ls-servers/gmiServer/weblogic/war/gmi/WEB-INF/classes:/opt/wls-servers/gmiSe
 rver/weblogic/war/gmi/_tmp_war, -d,
 /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war,
 /opt/wls-servers/gmiServer/weblogic/war/gmi/_tmp_war/jsp_servlet/gmiService.
 java])
 > at java.lang.Throwable.fillInStackTrace(Native Method)
 > at java.lang.Throwable.fillInStackTrace(Compiled Code)
 > at java.lang.Throwable.<init>(Compiled Code)
 > at java.lang.Exception.<init>(Compiled Code)
 > at java.io.IOException.<init>(Compiled Code)
 > at
 weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(Compiled Code)
 > at
 weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:200)
 > at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code)
 > at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:173)
 > at
 weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:18
 7)
 > at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :118)
 > at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :142)
 > at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:744)
 > at
 weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
 l.java:692)
 > at
 weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
 Manager.java:251)
 > at
 weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
 > at
 weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
 > at weblogic.kernel.ExecuteThread.run(Compiled Code)
 >
 >
 >

Automatic Site Fail Over

Hi
Here is my setup
2 Mail box servers cluster with one dag in Toronto. 1 Cas server in Toronto.
My question is if I setup another mailbox Cas server in vancouver. Can I acheieve automatic site fail over to Vancouver if Toronto goes down?
Is it recommended to do so? or what would be a better site failover strategy?

In simple words Automatic failover won't happen if Toronto goes down.
First let us read Exchange 2010 DAG Misconceptions
here
For multi-site DAG, you need to enable DAC (Datacenter Activation coordination), that will require to contact each DAG member to seek permission if it can mount databases. Since Toronto is down or there is network problem, Remote site would not be able to
mount databases.
Failover to Local Site is always automatic (preferred) and to remote site manual (preferred again). Because, Exchange has no knowledge of your Infrastructure and can't make smart decision whether to mount databases.
Exchange does support mounting of databases, and requires careful steps for failover and fallback. As explained below -
http://smtpport25.wordpress.com/2010/12/10/exchange-2010-dag-local-and-site-drfailover-and-fail-back/
Hope this helps.
Regards,
Sarvesh Goel
MCP, MCITP, MCTS, MCSA - Directory Services and Microsoft Exchange
Ok but what is the reason automatic site fail over will not occur?
The reason why I'm asking is because another admins believes if Vancouver is added to the DAG then the databases should mount automatically when the other nodes fail.

Why sever-side state saving doesn't support fail over?

Hi all,
In my previous thread "ADF server-side state saving method" Frank said that it doesn't support fail over.
Re: ADF server-side state saving method
My customer is wondering the reason.
If anyone has a clear statement about it, could you share it?
Any help will be much appreciated.
Atsushi

Timo,
As I wrote in my previous thread, my customer adopted multi-windows application design because they didn't know it caused viewExpiredException frequently.
Now I'm looking for the best setting for avoiding the exception and need ADF guru's help.
Frank said that ADF is on Sun's RI. And it seems that the state-saving parameters of Mojarra are working correctly in my environment. However any ADF docs don't mention the behavior of server-side state saving clearly. When I set state-saving method "server", view states are managed per logical view (≒ window). And it seems better for multi-window application than using client-token based state management from the perspective of preventing viewExpiredException.
Because fail over is not their requirement, if we could make sure that server-side state saving doesn't have other side-effects they might adopt it.
So I'd like to know in more detail about the behavior.
Thanks,
Atsushi

Initialization of the JSF runtime either failed or did not occurr

Hi, i am newby to Jdev. While working the online tutorial i have the error below. I was about creating a JSF page this error occurs.
Could someone help me please ?
Thanks
Oct 6, 2010 10:31:49 AM javax.faces.webapp
SEVERE: Initialization of the JSF runtime either failed or did not occurr. Review the server''s log for details.
java.lang.InstantiationException: org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl
     at java.lang.Class.newInstance0(Class.java:340)
     at java.lang.Class.newInstance(Class.java:308)
     at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:537)
     at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:386)
     at javax.faces.FactoryFinder.access$400(FactoryFinder.java:135)
     at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:717)
     at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)
     at javax.faces.webapp.FacesServlet.init(FacesServlet.java:164)
     at oracle.jdevimpl.webapp.design.support.http.DesignTimeServletInfo._init(DesignTimeServletInfo.java:304)
     at oracle.jdevimpl.webapp.design.support.http.DesignTimeServletInfo.init(DesignTimeServletInfo.java:193)
     at oracle.jdevimpl.webapp.design.support.http.DesignTimeServletContainerContext.initializeLoadOnStartupServlets(DesignTimeServletContainerContext.java:313)
     at oracle.jdevimpl.webapp.design.DesignTimeWebApp._initializeLoadOnStartupServlets(DesignTimeWebApp.java:2661)
     at oracle.jdevimpl.webapp.design.DesignTimeWebApp._initServletContainer(DesignTimeWebApp.java:804)
     at oracle.jdevimpl.webapp.design.DesignTimeWebApp.access$000(DesignTimeWebApp.java:106)
     at oracle.jdevimpl.webapp.design.DesignTimeWebApp$1.run(DesignTimeWebApp.java:712)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:619)

The error show up at the time creating brand new jsf page.
SEVERE: Initialization of the JSF runtime either failed or did not occurr. Review the server''s log for details.
java.lang.InstantiationException: org.apache.myfaces.portlet.faces.context.FacesContextFactoryImpl
     at java.lang.Class.newInstance0(Class.java:340)
     at java.lang.Class.newInstance(Class.java:308)
oracle.jdevimpl.webapp.design.support.http.DesignTimeServletContainerContext.initializeLoadOnStartupServlets(DesignTimeServletContainerContext.java:313)
     at oracle.jdevimpl.webapp.design.DesignTimeWebApp._initializeLoadOnStartupServlets(DesignTimeWebApp.java:2661)
     at oracle.jdevimpl.webapp.design.DesignTimeWebApp._initServletContainer(DesignTimeWebApp.java:804)

ACE 4710 - 'reverse proxy' infront of serverfarm - fail-over/sorry server design issue

Hi All,
I'm working on a specific config and have an issue in the backup farm/fail-over/sorry server area.
The customer wants the following:
They have an existing serverfarm with X web servers, they want a single server to act as a reverse-proxy in front of the farm.
So that all traffic goes trough that server, that server then forwards the request to the original serverfarm.
The problem in my design is in the fail-over, if i configure the reverse-proxy server in a new serverfarm and use the original (web servers) farm as backup it has fail-over, but if the reverse-proxy AND the original serverfarm fail, there is no nice way to get the users on a sorry server.
I could give the original serverfarms rservers a 'backup standby' server but that won't give the desired effect either.
For maintance they first take 50% of the servers offline and switch to the other 50% after that, so then users would see a sorry page even if there where operational servers in the farm left.
The 4710's are running routed mode, and the farms use Sticky Cookie, and also some http URL & Cookie matching is done.
Anyone have an idea how to build this?

Hi,
It need additional testing but as per my understanding if you put the back up in this order then the last backup server will be choosen first.
In your case it will be like " RSERVER1 >> backup sorry server >> backup web content
As per the below example:
I put test 2 as first backup server and test1 as second backup server but if you look at the first part it took rserver test1 as first backup.
serverfarm host 1313-GIN-GWAP-SDC-80
rserver RSERVER1
    backup-rserver test1
    inservice
rserver test1
    inservice standby
rserver test2
    inservice standby
regards,
Ajay Kumar

Could not execute command "getState" for server server01 using nodemanager

Hi,
I have built a weblogic 9.1 env with 2 managed servers running on different boxes from the admin server.
I am having problems in starting the managed servers using the nodemanager. I get the following error message in the Admin server log:
<Error> <NodeManager> <BEA-300034> <Could not execute command "getState" for server "******" using the node manager. Reason: I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found).>
I get the following message on the admin console:
For server ******, the Node Manager associated with machine ******-machine is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
I can start the managed server using the "startMangedWeblogic.sh" without any issues.
Any help on this would be greatly appreciated.
Thanks

one more thing to add:
I get the following error in the Managed server log:
<I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic91/common/nodemanager' invalid (domain salt file not found)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:74)
at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:46)
at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:239)
at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:170)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:104)
at weblogic.nodemanager.server.Handler.run(Handler.java:64)
at java.lang.Thread.run(Thread.java:595)

Bea weblogic 6.1 does not oracle Database fail over

Hi We had Concurrency Strategy:excusive . Now we change that to Database for performace
reasons. Since we change that now when we do oracle database fail over weblogic
6.1 does not detect database fail over and it need restart.
how we can resolve this ??

mt wrote:
Hi We had Concurrency Strategy:excusive . Now we change that to Database for performace
reasons. Since we change that now when we do oracle database fail over weblogic
6.1 does not detect database fail over and it need restart.
how we can resolve this ??Are your pools set to test connections at reserve time?
Joe

Weblogic not failing over correctly

Hi,
          I've got two weblogic servers in a cluster recieving requests from a
          weblogic proxy server. To demonstrate and test failover I've written
          three servlets: Login, Logout, and Test2. They perform session
          tracking ie. Login creates a session, Test2 tests it and Logout kills
          the session. The failover is very inconsistent at best. Shutting down
          one of the servers in the cluster causes the other one to failover OK
          but turning it back on and shutting down the second one doesn't work.
          Also the Test2 servlet doesn't see the session when it is loaded for the
          first time. Reloading causes it to work properly. Why?
          Could you look through these weblogic.properties files and see if they
          are configured correctly? One is from the cluster servers and the other
          is from the proxy server.
          These are in the weblogic root directory. I don't have any properties
          files in the cluster - wide or server specific directories. I am not
          using a shared file system.
          I am using weblogic 5.1 sp1 on NT and jdk1.2.2.
          Thank you
          Timur M.
          [weblogic.properties]
          [weblogic.properties]


The mistakes I found so far are the following.
          You have to register HttpClusterServlet to proxy all the servlet/jsp requests to weblogic
          cluster.
          ** PROXY PROPERTIES **
          weblogic.httpd.register.cluster=weblogic.servlet.internal.HttpClusterServlet
          weblogic.httpd.initArgs.cluster=defaultServers=jer:7001|tmaltaric:7001
          weblogic.httpd.defaultServlet=cluster
          ** WEBLOGIC SERVER PROPERTIES **
          weblogic.httpd.register.Login=Login
          weblogic.httpd.register.Logout=Logout
          blah blah blah
          Hope this helps.
          - Prasad
          Timur Maltaric wrote:
          > Hi,
          >
          > I've got two weblogic servers in a cluster recieving requests from a
          > weblogic proxy server. To demonstrate and test failover I've written
          > three servlets: Login, Logout, and Test2. They perform session
          > tracking ie. Login creates a session, Test2 tests it and Logout kills
          > the session. The failover is very inconsistent at best. Shutting down
          > one of the servers in the cluster causes the other one to failover OK
          > but turning it back on and shutting down the second one doesn't work.
          > Also the Test2 servlet doesn't see the session when it is loaded for the
          > first time. Reloading causes it to work properly. Why?
          >
          > Could you look through these weblogic.properties files and see if they
          > are configured correctly? One is from the cluster servers and the other
          > is from the proxy server.
          >
          > These are in the weblogic root directory. I don't have any properties
          > files in the cluster - wide or server specific directories. I am not
          > using a shared file system.
          > I am using weblogic 5.1 sp1 on NT and jdk1.2.2.
          >
          > Thank you
          > Timur M.
          >
          > ------------------------------------------------------------------------
          > Name: weblogic.properties
          > weblogic.properties Type: application/x-unknown-content-type-properties_auto_file
          > Encoding: base64
          >
          > Name: weblogic.properties
          > weblogic.properties Type: application/x-unknown-content-type-properties_auto_file
          > Encoding: base64
          Cheers
          - Prasad

Load balancing not happending but fail over is for Read only Entity beans

 The following are the configuration.
 Two NT servers with WL5.1 sp9 having only EJBs(Read only entity beans)
 One Client with WL5.1 sp9 having servlet/java application as
 EJB client.
 I am trying to make a call like findbyprimarykey in one of the
 entity bean. I could see the request is being directed only to the one of the
 server always. When I bring that server, fail over is happening to the other server.
 Here are the settings I have in the ejb-jar.xml :
 <entity>
 <ejb-name>device.StartHome</ejb-name>
 <home>com.wl.api.device.StartHome</home>
 <remote>com.wl.api.device.StartRemote</remote>
 <ejb-class>com.wl.server.device.StartImpl</ejb-class>
 <persistence-type>Bean</persistence-type>
 <prim-key-class>java.lang.Long</prim-key-class>
 <reentrant>False</reentrant>
 <resource-ref>
 <res-ref-name>jdbc/wlPool</res-ref-name>
 <res-type>javax.sql.DataSource</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
 </entity>
 Here are the settings I have in the weblogic-ejb-jar.xml.
 <weblogic-enterprise-bean>
 <ejb-name>device.StartHome</ejb-name>
 <caching-descriptor>
 <max-beans-in-cache>50</max-beans-in-cache>
 <cache-strategy>Read-Only</cache-strategy>
 <read-timeout-seconds>900</read-timeout-seconds>
 </caching-descriptor>
 <reference-descriptor>
 <resource-description>
 <res-ref-name>jdbc/wlPool</res-ref-name>
 <jndi-name>weblogic.jdbc.pool.wlPool</jndi-name>
 </resource-description>
 </reference-descriptor>
 <enable-call-by-reference>False</enable-call-by-reference>
 <jndi-name>device.StartHome</jndi-name>
 </weblogic-enterprise-bean>
 Am I doin any mistake in this?
 Any one's help is appreciated.
 Thanks
 Suresh


we are using 5.1
 "Gene Chuang" <[email protected]> wrote in message
 news:[email protected]...
 > Colocation optimization occurs if your client resides in the same
 container (and also in the same
 > EAR for 6.0) as your ejbs.
 >
 > Gene
 >
 > "Suresh" <[email protected]> wrote in message
 news:[email protected]...
 > > Ok....the ejb-call-by-reference set to true is making the call to one
 server
 > > only. i am not sure why it is. I removed the property name and it
 works.
 > > Also I have one question, in our prduct environment, when i cache the
 ejb
 > > home it is not doing the load balancing. can any one help me for that.
 > > thanks
 > >
 > > Mike,
 > > From the sample pgm I sent, even from single client calls get load
 > > balanced.
 > >
 > > Suresh
 > >
 > >
 > > "Gene Chuang" <[email protected]> wrote in message
 > > news:[email protected]...
 > > > In WL, LoadBalancing will ONLY WORK if you reuse your EJBHome! Take
 your
 > > StartEndPointHome lookup
 > > > out of your for loop and see if this fixes your problem.
 > > >
 > > > I've seen this discussion in ejb-interest, and some other vendor
 (Borland,
 > > I believe it is), brings
 > > > up an interesting point: Clustering and LoadBalance is not in the
 J2EE
 > > specs, hence implementation
 > > > is totally up to the vendor. Weblogic loadbalances from the remote
 > > interfaces (EJBObject, EJBHome,
 > > > etc..), while Borland loadbalances from JNDI Context lookup.
 > > >
 > > > Let me suggest a third implmentation: loadbalance from BOTH Context
 > > lookup as well as stub method
 > > > invocation! Or create a smart replica-aware list manager which
 persists
 > > on the client thread
 > > > (ThreadLocal) and is aware of lookup/evocation history. Hence if I do
 the
 > > following in a client
 > > > hitting a 3 node cluster, I'll still get perfect round-robining
 regardless
 > > of what I do on the
 > > > client side:
 > > >
 > > > InitialContext ctxt = new InitialContext();
 > > > EJBHome myHome = ctxt.lookup(MY_BEAN);
 > > > myHome.findByPrimaryKey(pk); <== hits Node #1
 > > > myHome = ctxt.lookup(MY_BEAN);
 > > > myHome.findByPrimaryKey(pk); <== hits Node #2
 > > > myHome.findByPrimaryKey(pk); <== hits Node #3
 > > > myHome = ctxt.lookup(MY_BEAN);
 > > > myHome.findByPrimaryKey(pk); <== hits Node #1
 > > > ...
 > > >
 > > >
 > > > Gene
 > > >
 > > > "Suresh" <[email protected]> wrote in message
 > > news:[email protected]...
 > > > > Mike ,
 > > > >
 > > > > Do you have any reasons for the total number of machines to be 10.
 > > > >
 > > > > I tried with 7 machines.
 > > > >
 > > > >
 > > > > Here is my sample client java application running individual in the
 > > seven
 > > > > machines.
 > > > >
 > > > > StartEndPointHome =
 > > > > (StartEndPointHome)ctx.lookup("dev.StartEndPointHome");
 > > > > for(;;)
 > > > > {
 > > > > // logMsg(" --in loop "+currentTime);
 > > > > if (currentTime > nextRefereshTime)
 > > > > {
 > > > > logMsg("****- going to call");
 > > > > currentTime=getSystemTime();
 > > > > nextRefereshTime=currentTime+timeInterval;
 > > > > StartEndPointHome =
 > > > > (StartEndPointHome)ctx.lookup("dev.StartEndPointHome");
 > > > > long rndno=(long)(Math.random()*10)+range;
 > > > > logMsg(" going to call remotestub"+rndno);
 > > > > retVal =
 > > > >
 > >
 ((StartEndPointHome)getStartHome()).findByNumber("pe"+rndno+"_mportal_dsk36.
 > > > > mportal.com");
 > > > >
 > > > > logMsg("**++- called stub");
 > > > > }
 > > > >
 > > > >
 > > > >
 > > > > The range value is different for each of the machines in the
 cluster.
 > > > >
 > > > > If the first request starts at srv1, all request starts hitting the
 same
 > > > > server.
 > > > > If the first request starts at srv2, all request starts hitting the
 same
 > > > > server.
 > > > >
 > > > > I have the following for the url , user and pwd values for the
 context
 > > .
 > > > >
 > > > > public static String url="t3://10.11.12.14,10.11.12.117:8000";
 > > > > public static String user="guest";
 > > > > public static String password="guest";
 > > > >
 > > > >
 > > > >
 > > > > It would be great if you could help me.
 > > > >
 > > > > Thanks
 > > > > suresh
 > > > >
 > > > >
 > > > > "Mike Reiche" <[email protected]> wrote in message
 > > > > news:[email protected]...
 > > > > >
 > > > > > If you have only one client don't be surprised if you only hit one
 > > server.
 > > > > Try
 > > > > > running ten different clients and see if the hit the same server.
 > > > > >
 > > > > > Mike
 > > > > >
 > > > > >
 > > > > > "suresh" <[email protected]> wrote:
 > > > > > >
 > > > > > >The following are the configuration.
 > > > > > >
 > > > > > > Two NT servers with WL5.1 sp9 having only EJBs(Read only entity
 > > beans)
 > > > > > >
 > > > > > > One Client with WL5.1 sp9 having servlet/java application as
 > > > > > > EJB client.
 > > > > > >
 > > > > > >
 > > > > > >I am trying to make a call like findbyprimarykey in one of the
 > > > > > >entity bean. I could see the request is being directed only to
 the
 > > one
 > > > > > >of the
 > > > > > >server always. When I bring that server, fail over is happening
 to
 > > the
 > > > > > >other server.
 > > > > > >
 > > > > > >
 > > > > > >Here are the settings I have in the ejb-jar.xml :
 > > > > > > <entity>
 > > > > > > <ejb-name>device.StartHome</ejb-name>
 > > > > > > <home>com.wl.api.device.StartHome</home>
 > > > > > > <remote>com.wl.api.device.StartRemote</remote>
 > > > > > > <ejb-class>com.wl.server.device.StartImpl</ejb-class>
 > > > > > > <persistence-type>Bean</persistence-type>
 > > > > > > <prim-key-class>java.lang.Long</prim-key-class>
 > > > > > > <reentrant>False</reentrant>
 > > > > > > <resource-ref>
 > > > > > > <res-ref-name>jdbc/wlPool</res-ref-name>
 > > > > > > <res-type>javax.sql.DataSource</res-type>
 > > > > > > <res-auth>Container</res-auth>
 > > > > > > </resource-ref>
 > > > > > > </entity>
 > > > > > >
 > > > > > >
 > > > > > >Here are the settings I have in the weblogic-ejb-jar.xml.
 > > > > > >
 > > > > > ><weblogic-enterprise-bean>
 > > > > > > <ejb-name>device.StartHome</ejb-name>
 > > > > > >
 > > > > > > <caching-descriptor>
 > > > > > > <max-beans-in-cache>50</max-beans-in-cache>
 > > > > > > <cache-strategy>Read-Only</cache-strategy>
 > > > > > > <read-timeout-seconds>900</read-timeout-seconds>
 > > > > > > </caching-descriptor>
 > > > > > >
 > > > > > > <reference-descriptor>
 > > > > > > <resource-description>
 > > > > > > <res-ref-name>jdbc/wlPool</res-ref-name>
 > > > > > > <jndi-name>weblogic.jdbc.pool.wlPool</jndi-name>
 > > > > > > </resource-description>
 > > > > > > </reference-descriptor>
 > > > > > > <enable-call-by-reference>False</enable-call-by-reference>
 > > > > > > <jndi-name>device.StartHome</jndi-name>
 > > > > > > </weblogic-enterprise-bean>
 > > > > > >
 > > > > > >
 > > > > > >Am I doin any mistake in this?
 > > > > > >
 > > > > > >Any one's help is appreciated.
 > > > > > >Thanks
 > > > > > >Suresh
 > > > > >
 > > > >
 > > > >
 > > >
 > > >
 > >
 > >
 >
 >

Failed over to a Aysnc Replica and now previous primary replica(Now Secondary) is in NOT SYNC state

Hello All,
Here is my situation :
3 Nodes in an AG configuration, and its a multi-site cluster. Sync commit between 2 nodes in one DC and Async commit to a node in the DR DC.
AG is failed over to the Async Replica which is the DR site and all the databases comes up fine and application also can connect using the listener.
When checked the state of secondary databases, its in NOT SYNC mode. Data is suspended automatically. I can resume data movement to fix the problem, but was curious why this will be in NOT SYNC mode?
Thanks in advance.
Thank you,
Anup
<div> Anup | Database Consultant Blog: <a href="www.sqlsailor.com/">www.sqlsailor.com</a> Twitter: <a href="https://twitter.com/#!/AnupWarrier"> Follow me !</a>
 Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful. </div>

Hello Anup,
The reason this happens is because of the forced failover needed to be used when moving to an Async replica. It will cause all other replicas to become suspended due to the fact that it is never known if data loss will occur or not.
It might not make sense right now, but think about a situation where the databases are not synchronized and failover is forced (it has to work in all situations). There may be a good bit of data on the primary replica that has not yet made it (or partially)
to the async secondary. It wouldn't make sense to negotiate the primary back down (after all, it's the async one) and undo valid transactions. It also allows for a database snapshot or other method to be done on the old sync primary which could be used for
DR purposes to get those valid transactions and data out.
BOL Doc:
http://msdn.microsoft.com/en-us/library/hh213151.aspx#ForcedFailover
Sean Gallardy | Blog |
Twitter

Stateful bean not failing over

          I have a cluster of two servers and a Admin server. Both servers are running NT
          4 sp6 and WLS6 sp1.
          When I stop one of the servers, the client does n't automatically failover to
          the other server, instead it fails unable to contact server that has failed.
          My bean is configured to have its home clusterable and is a stateful bean. My
          client holds onto the remote interface, and makes calls through this. If Server
          B fails then it should automatically fail over to server A.
          I have tested my multicast address and all seems to be working fine between servers,
          my stateless bean work well, load balancing between servers nicely.
          Does anybody have any ideas, regarding what could be causing the stateful bean
          remote interface not to be providing failover info.
          Also is it true that you can have only one JMS destination queue/topic per cluster..The
          JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
          servers?
          Thanks


Did you enable stateful session bean replication in the
          weblogic-ejb-jar.xml?
          -- Rob
          Wayne Highland wrote:
          >
          > I have a cluster of two servers and a Admin server. Both servers are running NT
          > 4 sp6 and WLS6 sp1.
          > When I stop one of the servers, the client does n't automatically failover to
          > the other server, instead it fails unable to contact server that has failed.
          >
          > My bean is configured to have its home clusterable and is a stateful bean. My
          > client holds onto the remote interface, and makes calls through this. If Server
          > B fails then it should automatically fail over to server A.
          >
          > I have tested my multicast address and all seems to be working fine between servers,
          > my stateless bean work well, load balancing between servers nicely.
          >
          > Does anybody have any ideas, regarding what could be causing the stateful bean
          > remote interface not to be providing failover info.
          >
          > Also is it true that you can have only one JMS destination queue/topic per cluster..The
          > JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
          > servers?
          >
          > Thanks
          Coming Soon: Building J2EE Applications & BEA WebLogic Server
          by Michael Girdley, Rob Woollen, and Sandra Emerson
          http://learnweblogic.com

Fail over is not happening in Weblogic JSP Server

Similar Messages

Maybe you are looking for