Replicating router partitions for Fail/Over ?

Hi everyone,
Is it really worth the value to replicate a router partition on the same
node ?
In other words, has anyone ever seen a router partition failing on its
own (eg due
to an out of memory), ie not because of the node failure ?
What I am looking for is to avoid wasting system resources for unneeded
replicates.
Thanks.
Vincent Figari

You will use Active/Standby failover method to keep your fail-over configuration in secondary firewall (PIX).
Active/Standby Failover lets you use a standby security appliance to take over the functionality of a failed unit. When the active unit fails, it changes to the standby state while the standby unit changes to the active state. The unit that becomes active assumes the IP addresses (or, for a transparent firewall, the management IP address) and MAC addresses of the failed unit and begins to pass traffic. The unit that is now in standby state takes over the standby IP addresses and MAC addresses. Because network devices see no change in the MAC to IP address pairing, no ARP entries change or time out anywhere on the network. PIX Security Appliance with 7.x version and above supports failover.
For further information click this link.
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml#regu

Similar Messages

Support for fail over/clustering?

Is there any support for fail over/clustering Oracle on a two-node Linux cluster? Is it even possible to run Oracle on a two-node Linux cluster?

To add more, I'm unsure whether an HA product is even needed once Oracle Releases Parallel Server. Also, is it possible to run Oracle w/o Parallel Server on a cluster? If so, what does that buy you?

ACE MIB Value for Fail over

Hi,
May I know the MIB value ACE (Application Contril Engine )will be generating while a fail over occurs. Is the value same for contetx fail over as well ??
Regards
Jithesh

Hi,
I think this is the error code your looking for;
727012
Error Message %ACE-2-727012: HA: FT Group group ID changed state to NewState. Reason:
reason str.
Table 2-2 NewState Values and Descriptions
NewState Value
Description
FSM_FT_STATE_INIT
The initial state. Visible only when the configuration for the FT group exists but it is not in service.
FSM_FT_STATE_ELECT
After you enter the inservice command when you are configuring an FT group, the ACE enters the ELECT state. The redundancy state machine negotiates with its peer context in the FT group to determine the redundancy role (active or standby)
FSM_FT_STATE_ACTIVE
The active member of the FT group.
FSM_FT_STATE_STANDBY_COLD
This state can be entered if:
•FT VLAN is down but the peer device is still alive.
•Configuration or application state synchronization failure have occurred.
FSM_FT_STATE_STANDBY_CONFIG
The standby context is waiting to receive configuration information. Upon entering this state, the active context will be notified to send a copy of the running configuration.
FSM_FT_STATE_STANDBY_BULK
The standby context is waiting to receive state information. Upon entering this state, the active context will be notified to send a copy of the current states information for all applications.
FSM_FT_STATE_STANDBY_HOT
The standby context is ready to become active in a failover situation.
Values returned for the reason str variable can be one of the following:
•FSM_FT_EV_PEER_DOWN
•FSM_FT_EV_PEER_FT_VLAN_DOWN
•FSM_FT_EV_PEER_SOFT_RESET
•FSM_FT_EV_STATE
•FSM_FT_EV_TIMEOUT
•FSM_FT_EV_CFG_SYNC_STATUS
•FSM_FT_EV_BULK_SYNC_STATUS
•FSM_FT_EV_COUP
•FSM_FT_EV_RELINQUISH
•FSM_FT_EV_TRACK_STATUS
•FSM_FT_EV_UPDATE
•FSM_FT_EV_ENABLE_INSERVICE
•FSM_FT_EV_DISABLE_INSERVICE
•FSM_FT_EV_SWITCHOVER
•FSM_FT_EV_PEER_COMPATIBLE
•FSM_FT_EV_MAINT_MODE_OFF
•FSM_FT_EV_MAINT_MODE_PARTIAL
•FSM_FT_EV_MAINT_MODE_FULL
Check from the above ID onwards for more details around ft status.
Cheers
Scott

Exception while testing for Fail over

Hi
 I have the web tier architecture away from cluster. All ejbs are in cluster
 running in two seperate machines say server1 and server2 . We have a
 factory class running in
 webtier(we use servlet in this tier) which obtains home interface only once
 and stores it for future reference. When ever we need the remoteobject stub,
 we ask the factory class and which in turn uses the stored home interface to
 get the same.
 In the webtier, I list all the servers in the cluster as a part of url as
 t3://server1,server2:8000
 I started the web tier as well as Object tier cluster. I could see the
 request coming in both the machines in the cluster for the ejb. But When I
 bring down one the server say server1 in the cluster, I get the following
 exception.
 java.lang.NullPointerException
 at weblogic.rjvm.RJVMFinder.isThisHost(RJVMFinder.java:340)
 at weblogic.rjvm.RJVMFinder.isHostedByLocalRJVM(RJVMFinder.java:314)
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:151)
 at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
 at
 weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
 textFactoryDelegate.java:195)
 at weblogic.jndi.Environment.getContext(Environment.java:122)
 at weblogic.jndi.Environment.getInitialContext(Environment.java:105)
 at
 weblogic.service.BasicReplicaList.forceRefresh(BasicReplicaList.java:196)
 at weblogic.service.BasicReplicaList.refresh(BasicReplicaList.java:182)
 at
 weblogic.service.BasicReplicaHandler.refreshReplicaList(BasicReplicaHandler.
 java:331)
 at
 weblogic.service.BasicReplicaHandler.failOver(BasicReplicaHandler.java:123)
 at weblogic.service.BasicServiceStub._wl_failOver(BasicServiceStub.java:91)
 at
 weblogic.service.BasicServiceStub._wl_autoFailOver(BasicServiceStub.java:118
 at
 com.mportal.server.device.CommEndPointImplHomeImpl_ServiceStub.findByDeviceN
 umber(CommEndPointImplHomeImpl_ServiceStub.java:169)
 at
 com.mportal.router.servlet.mPortalServlet.processRequest(mPortalServlet.java
 :241)
 at
 com.mportal.router.servlet.mPortalServlet.handleRequest(mPortalServlet.java:
 184)
 at com.mportal.router.servlet.mPortalServlet.doGet(mPortalServlet.java:93)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
 at
 weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
 :124)
 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(ExecuteThread.java:120)
 Then I bring up the Server1 (Which was the one I brought it down), I get the
 same message in the web-tier and the following in the
 Server 1 machine(which is in cluster).
 Mon May 21 23:11:38 EDT 2001:<E> <NT Performance Pack> failure in
 processSockets() loop: GetData: fd=1324 numBytes=87
 java.lang.NullPointerException
 at
 weblogic.rjvm.ConnectionManager.gotExceptionSending(ConnectionManager.java:7
 53)
 at
 weblogic.rjvm.ConnectionManager.gotExceptionSending(ConnectionManager.java:7
 46)
 at weblogic.socket.JVMAbbrevSocket.sendOutMsg(JVMAbbrevSocket.java:362)
 at weblogic.socket.JVMAbbrevSocket.sendMsg(JVMAbbrevSocket.java:237)
 at weblogic.socket.JVMAbbrevSocket.sendMsg(JVMAbbrevSocket.java:170)
 at
 weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
 a:103)
 at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:630)
 at weblogic.socket.JVMAbbrevSocket.dispatch(JVMAbbrevSocket.java:393)
 at weblogic.socket.JVMSocketT3.dispatch(JVMSocketT3.java:355)
 at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:424)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
 Any one's help is appreciated.
 Thanks
 Suresh


You're not giving us much to go on, you know.
There's code that results in this exception.
There's a full stack trace somewhere.
What does your client look like?
How was it generated?
Which particular framework are you using (Axis? JWS? Something else?)...

Configuring Fail Over Clustering

I was assigned to configure the New DIA Line for our Data Center for Fail over (Back Up)
My Existing Line is - ISP ==} Router 2811 ==} Juniper SSG320 ==} Cisco Core Switch 6500
For Back Up We get additional line.
How can I configure the Fail Over Clustering the new DIA Lines?
Please see attached my Network Diagram.
Thank you,
Michael

Dear All,
My problem is solved by disabling antivirus.
thanks for the support
Sunil
SUNIL PATEL SYSTEM ADMINISTRATOR

Active/active Fail over monitoring

Guys,
I have a small concern for my Active active FO. Below are the details of setup.
1)- I have two pairs of ASA 5520 each carrying three contexts. (CTXT 1-3 in 1st ASA, CTXT 4-6 in 2nd ASA).
2)- I have created two fail over group in each ASA for active active FO. FO group 1&2 in primary ASA and 3&4 FO group in 2nd ASA.
3)- I have assigned two contexts (CTXT1-2) to FO group 1 and rest Context (CTXT-3) to FO group 2 in primary ASA.
4)- Same in the 2nd ASA.
My question is
1)- how can i configure my monitor for fail over.
2)- Is it based on the Interfaces of Contexts or the no of contexts ?
Thanks
swap

Hi Felipe,
Yes, it could be the NAT configuration. But I've tried creating a back-up NAT rule before, but that wasn't successful either.
nat (inside,outside) source static NETWORK_OBJ_10.80.1.0_24 NETWORK_OBJ_10.80.1.0_24 destination static DM_INLINE_NETWORK_5 DM_INLINE_NETWORK_5 no-proxy-arp route-lookup
nat (inside,outside) source static Branch_Inside Branch_Inside destination static DM_INLINE_NETWORK_4 DM_INLINE_NETWORK_4 no-proxy-arp route-lookup
nat (inside,outside) source static Branch_Inside Branch_Inside destination static Roswell Roswell no-proxy-arp route-lookup
object network inside-net
nat (inside,outside) dynamic interface
nat (inside,outside) after-auto source dynamic any interface
access-group outside_access_in_1 in interface outside control-plane
access-group outside_access_in in interface outside
access-group outside_access_out out interface outside
access-group outside_access_ipv6_in in interface outside
access-group outside_access_ipv6_out out interface outside
access-group outside_access_in in interface inside
access-group outside_access_out out interface inside
access-group outside_access_ipv6_in in interface inside
access-group outside_access_ipv6_out out interface inside
access-group outside_p_access_in in interface outside_p
access-group outside_p_access_out out interface outside_p
access-group global_access global
access-group global_access_ipv6 global
route outside_p 0.0.0.0 0.0.0.0 y.y.y.y 1 track 1
route outside 0.0.0.0 0.0.0.0 x.x.x.x 255
Before I was really lookign at the license being Base as I may need to upgrade to Security Plus.

WLC 4400 and 5500 Fail-over

Can we do the same thing with WCL 4400 and 5500 series for failover? We have 1 existing 4400 WLC and we wanted to purchase another 1 for fail-over as well as backup. But right now, 4400 is EOL already. The only option is to have the 5500 WLC.
So if you do have previous set-up like this, so I would need your inputs.. Otherwise, same as usual, will gonna test to work this out.

You can have both in a primary and backup, but make sure they are on the same code version. I'm assuming that you also have the configuration correct for the two wlc to communicate.
I would put them both on the 7.0.220.0.
Sent from Cisco Technical Support iPhone App

2960 and fail over

I am going to hook a 2960 to a wireless antenna and have a backup T-1 to use for fail-over. Can a 2960 do this function?
Shannon

It could if any of the 2960 have a WAN interface such as T1 but it does not and since it's a switch.

Problems with LDAP Server fail-over

Our Xsan installed with 12 FCP, 2 MDC Xserve and 2 LDAP Xserver for fail-over.
The 2 MDC fail-over runs well but the 2 LDAP fail-over got problems.
The first time we up-plug the powercode of 1 xserve and the other LDAP takes over successfully but FCP users re-login takes 15 minutes. That's unacceptable.
The fail-over never succeed after that.
That means once the LDAP down and the backup LDAP will not take the job, we will lose everything related to user login.
Anybody can help? Thanks a lot.

I believe you can enter both LDAP servers in the client configuration for LDAP access. (Even though you shouldn't have to)
IP failover is not the issue, your LDAP configuration is.
Start at page 90 and work throught this document to make sure you have the clients setup properly.
http://manuals.info.apple.com/en/MacOSXSrvr10.3_OpenDirectoryAdmin.pdf

NFS fail-over

Hello all
We are planning to use remote home directories for our non-system user accounts on our Solaris boxes.
We have two servers to use for fail over.
Is it possible to set up NFS to fail over between both servers?
Cheers
--Andreas

If they can't be on the same subnet, then they can't fail each other over directly. You'd have to have client support, and there's no NFS client I'm aware of that will do that on read/write filesystems.
You could make it work if you could force unmount the clients after a server failure, but that would be annoying.
If the servers had a presence on the same subnet, they could each host a virtual IP address that clients would connect to.
Darren

First call attempt fails with 12000; reason="Routes available for this request but no available gateway at this point"

We've installed a new Audiocodes Mediant 1000B gateway for our customer. They only have about 6 users enabled for Enterprise voice and using Lync for all calls. They have an intermittent problem whereby the first call attempt to a number on the
PSTN fails with 12000; reason="Routes available for this request but no available gateway at this point". There is only one PSTN gateway installed. All routes point to this gateway. What I found initially is that the calls
were failing after 10 seconds which is the default "failovertimeout" in the OutboundRouting.exe.config. I found this post http://voipnorm.blogspot.co.uk/2012/06/lync-2010-gateway-timeout-call-failures.html and
changed the value to 20 seconds. Subsequent failures failed after 20 seconds (the new value). The interesting thing is that the second attempt even a couple of seconds later succeeds. My Lync server event log has 46046 "A call to a PSTN
number failed due to non availability of gateways." for the failed call and 46047 "A PBX gateway is now responding to requests after some failures." for the successful call moments later.
My environment is Lync 2010. A single enterprise edition Front End with collocated mediation. The server is virtual and in a different physical location to the gateway. The two sites are connected via a LES1000. The RTT between the
sites is very low so it isn't necessarily networking.
In the Syslog output on the Audiocodes we don't see the call even reach the gateway. It's likely that Lync has simply marked the gateway as down and doesn't route the first call. Then it wakes up and marks it as up and routes the next call.
Update wise I'm on 4.0.7577.183, 199 and 217 for those that are up to date and the only components that are behind say that 223 is available. Those being Core Components, Lync Server, Conferencing Server and Web Components.
As I said, this is intermittent, apparently doesn't happen for every user (which I don't buy), but is easily replicated on request.
I definitely think changing the failovertimeout value has reduced the number of failures. But realistically I don't want users sitting there for 20 seconds before their call fails. Or 19 seconds for the call to route.
I've found a few posts on this and similar issues. I don't get the 25051 or 25052 errors.
Any help gratefully appreciated.
Regards
Randy Chapman
Best Regards Randy Chapman

Try to change the value of Failovertimeout to 1000.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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

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

Multiple j-sessions for IOP fail-over?

Weblogic has the ability to support multiple j-sessions to allow fail-over of the connection.
My understanding is that this is not currently supported in IOP.
When will IOP support multiple j-sessions?
Is it possible to get a patch for this in the current version 11 of IOP?
Thank you.

That is part of the product roadmap to support multiple j-sessions for IOP fail over using Weblogic. That way, if the primary IOP server fails, the user can be re-routed to the backup server in a high-availability fashion. However, that is not supported currently, but will be over the next couple of releases.

Is Replica aware stubs are in infinite loop when fail over????

 Hi
 Any help on this Appreciated
 See in this senario, where there is four weblogic instance runs in the cluster
 and a replica aware stub(stateless bean with idempodent methods) finds a particular
 method fails on a server and it redircets the request to another one server but the
 same method fails on all the server, then what is goin to happen?? is it going to
 throw some exception or gonna be in a loop to keep on redirecting the method request
 to all servers in Round???
 Regards
 Aruna


 Aruna,
 A stateless session bean whose methods have been declared idempotent will automatically
 retry on another service provider in a fail-over situation. When a fail-over situation
 occurs, the stub refreshes its list of service providers. Note: Just because your
 method call fails, doesn't mean it's a fail-over situation.
 Jane
 "Aruna" <[email protected]> wrote:
 >
 >Hi
 >
 > Any help on this Appreciated
 >
 > See in this senario, where there is four weblogic instance runs in
 >the cluster
 >and a replica aware stub(stateless bean with idempodent methods) finds a
 >particular
 >method fails on a server and it redircets the request to another one server
 >but the
 >same method fails on all the server, then what is goin to happen?? is it
 >going to
 >throw some exception or gonna be in a loop to keep on redirecting the method
 >request
 >to all servers in Round???
 >
 >
 >Regards
 >Aruna

Replicating router partitions for Fail/Over ?

Similar Messages

Maybe you are looking for