Automatic failover for message consumers

I'm trying to evaluate the failover capabilities of a message consumer when the JMS service is migrated either manually or because of a server failure. I've tried setting the reconnect policy to "all" on both the client and the connection factory, but my consumer will not receive messages after the migration occurs unless I restart it. I've seen some references in the documentation about a special license needed for using the JMS clustering capabilities. I'm using the default license that comes with the download so I suspect this may be the problem. Can anyone confirm this?

Hi
          Thanks for the immediate response. We are okie for the messages lost before the subscriber created.
          Messages are not coming even after the subscibers are created successfully..
          When i publish a message Topic Server throws a error in the server side for the particular reconnected subscriber.
          I attached the error log
          <20-Mar-2007 00:41:08 o'clock GMT+04:00> <Warning> <JMS> <BEA-040499> <An error occurred while pushing messages to a JMS
          client: weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException:
          Could not establish a connection with 3695118781574910662C:57.12.45.181R:8457695624056246393S:10.12.88.82:[7010,-1,-1,-1
          ,-1,-1,-1]:JawaDomain:ManagedServer_1, java.rmi.ConnectException: Destination is not a server; No available router to de
          stination; nested exception is:
          java.rmi.ConnectException: Destination is not a server; No available router to destination; nested exception is:
          java.rmi.ConnectException: Could not establish a connection with 3695118781574910662C:57.12.45.181R:845769562405
          6246393S:10.12.88.82:[7010,-1,-1,-1,-1,-1,-1]:JawaDomain:ManagedServer_1, java.rmi.ConnectException: Destination is not
          a server; No available router to destination; nested exception is:
          java.rmi.ConnectException: Destination is not a server; No available router to destination
          weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not
          establish a connection with 3695118781574910662C:57.12.45.181R:8457695624056246393S:10.12.88.82:[7010,-1,-1,-1,-1,-1,-1
          ]:JawaDomain:ManagedServer_1, java.rmi.ConnectException: Destination is not a server; No available router to destination
          ; nested exception is:
          java.rmi.ConnectException: Destination is not a server; No available router to destination; nested exception is:
          java.rmi.ConnectException: Could not establish a connection with 3695118781574910662C:57.12.45.181R:845769562405
          6246393S:10.12.88.82:[7010,-1,-1,-1,-1,-1,-1]:JawaDomain:ManagedServer_1, java.rmi.ConnectException: Destination is not
          a server; No available router to destination; nested exception is:
          java.rmi.ConnectException: Destination is not a server; No available router to destination
          at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:116)
          at weblogic.jms.dispatcher.DispatcherAdapter.dispatchNoReply(DispatcherAdapter.java:29)
          at weblogic.jms.frontend.FESession.pushMessage(FESession.java:2759)
          at weblogic.jms.common.Sequencer.deliverMessages(Sequencer.java:274)
          at weblogic.jms.common.Sequencer.pushMessage(Sequencer.java:171)
          Truncated. see log file for complete stacktrace
          Thanks

Similar Messages

Weblogic7/examples/clustering/ejb Automatic failover for idempotent methods ?

This one should be easy since it is from the examples folder of bea 7 about
          clustering.
          Ref : \bea7\weblogic007\samples\server\src\examples\cluster\ejb
          I am referring to the cluster example provided with the weblogic server 7.0
          on windows 2000.
          I deployed Admin server and 2 managed server as described in document.
          Everything works fine as shown by the example. I get load balancing and
          failover both. Too Good.
          Client.java is using the while loop to manage the failover. So on exception
          it will go thru the loop again.
          I understand from the documentation that the stateless session EJB will
          provide the automatic failover for Idempotent stateless bean
          Case Failover Idempotent : ( Automatic )
          If methods are written in such a way that repeated calls to the same method
          do not cause duplicate updates, the method is said to be "idempotent." For
          idempotent methods, WebLogic Server provides the
          stateless-bean-methods-are-idempotent deployment property. If you set this
          property to "true" in weblogic-ejb-jar.xml, WebLogic Server assumes that the
          method is idempotent and will provide failover services for the EJB method,
          even if a failure occurs during a method call.
          Now I made 2 changes to the code.
          1 . I added as follows to the weblogic-ejb-jar.xml of teller stateless EJB
          <stateless-clustering>
          <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
          <stateless-bean-load-algorithm>random</stateless-bean-load-algorithm>
          <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
          potent>
          </stateless-clustering>
          So I should get the automatic failover .............
          2. Also I added the break statement in the catch on line around 230 in
          Client .java
          catch (RemoteException re) {
          System.out.println(" Error: " + re);
          // Replace teller, in case that's the problem
          teller = null;
          invoke = false;
          break;
          So that the client program does not loop again and again.
          Now I compile and restart all my three servers and redeploy application (
          just to be sure )
          I start my client and I get a automatic load balancing between the server
          which makes me happy.
          But Failover ....?
          I kill one of the managed application server in cluster at any particular
          test fail point.
          I expect the exception to be taken care automatically by error/failover
          handler in the home/remote stub
          But the client program fails and terminates.
          1. What is wrong with the code ?
          2. Does the automatic failover with the indempotent methods also has to be
          taken care by coding the similar while loop for stateless ejb ?
          Your help will be appreciated ASAP.
          Let me know if you need any thing more from my system. But I am sure this
          will be very easy as it is from the sample code.........
          Thanks


Sorry I meant to send this to the ejb newsgroup.
          dan
          dan benanav wrote:
          > Do any vendors provide for clustering with automatic failover of entity
          > beans? I know that WLS does not. How about Gemstone? If not is there
          > a reason why it is not possible?
          >
          > It seems to me that EJB servers should be capable of automatic failover
          > of entity beans.
          >
          > dan

Configuring Automatic Failover for EPM Planning Cluster

We are trying to test automatic failover using a Planning(11.1.2.2)/weblogic cluster containing 2 physical servers and a Weblogic proxy plug-in for OHS.
I understand that to enable this we must configure in-memory replication of HTTP session states and to do this, (according to various sources including ID 779350.1) the weblogic.xml file must include a descriptor set up as follows:
<session-descriptor>
   <session-param>
    <param-name>PersistentStoreType</param-name>
    <param-value>replicated</param-value>
</session-param>
</session-descriptio>
Where should weblogic.xml be created or amended (if it already exists) for a Planning cluster in a standard scaled out EPM deployment in order to effect failover between the two servers.
Thanks

yes, it can be load balanced in hyperion registry i believe, seen it once only drawback is ,if a JVM goes down while processing a request it needs to be manually started, however the url will switch automatically

How can I get gmail to automatically check for messages every 5 minutes on my 4S?

I am new to my Iphone 4s. I use gmail for my mail application. One special from address is urgent when I get a message. I have flagged this address as a VIP and assigned loud tones and notifications in the notifications function but a message was sent to me but nothing "arrived and nothing happened" until I opened mail again. I need this message and the notification to be intrusive!

There is no option to Fetch email every 5 minutes.
The options are:
Every 15 Minutes
Every 30 Minutes
Hourly
Manually
These settings are in Settings > Mail, Contacts, Calendars > Fetch New Data
The only other option is to set the email account up as Exchange so that as new emails arrive they are pushed to the device.

Can I prevent automatic failover for a period of time?

We have two Exchange 2013 servers (and a witness server) in a DAG. They are all VMWare virtual. We have recently migrated our 500 users from Ex2007 to Ex2013, so there is a bit of a learning curve for us. One of the servers "A"
is has a better hardware situation than the other "B" server that is offsite. They both have the same memory and hard drive sizes. We would like to keep the databases active on the better A server. There was a situation with our
primary A server the night before that caused the databases to be activated on the B server which in turn caused B to run all the resources up to 100% and be very. I was able to move the active databases back to A and put B in maintenance mode so
that it won't fail over to B for right now until we can get B a better hardware situation.
Question is: Is it possible for B to keep getting the logs played to the server so that if there were a catastrophic failure on A, we could essentially activate the databases on B we would be fine. I don't want it to be activating on B on
its own. I don't want to break the DAG because we want it to be able to eventually be used as designed, but it may be a month or two. Essentially, can we put the DAG in a manual mode?
Thanks.
Sally

Hi,
Just for more reference:
How To Block A Mailbox Database Copy From Activation…
http://theucguy.net/how-to-block-mailbox-database-copy-from/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Thanks,
Simon Wu
TechNet Community Support

DataGuard automatic failover

Say an automatic failover has happened.
The former primary DB is down.
The former standby DB is now the primary DB and is up and running.
I assume the clients have to reconnect to the second DB.
Now, how can we make the automatic failover for the clients?
(At least that you do not have to manually change the clients' tnsnames.ora to the new DB.)

Take a look into the NET8 manual. The simple way is to define multiple addresses in the address list. That way you get a connect time failover: if the first instance isn't reachable the scond one will be used and so on.
DB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.2)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = ORCL)
)

Replicating simple Java objects for automatic failover

Is there a way to replicate a simple java object that is bound from JNDI
          across all servers so that if the primary server fails, it will
          automatically failover?
          We have a java client that uses JNDI to access EJBs on WLS5.1 SP8. In order
          to determine client information, the client currently binds a simple java
          class in the JNDI tree. The Entity and Session beans use the caller
          principal to locate the object in order to access client-information for
          such things as record locking, logging, etc..
          We have to move this architecture to a cluster environment and we are
          wondering how we can replicate this object across cluster servers so that
          failover is handled automatically, and that it is still accessible through
          JNDI.
          An RMI replicated stub is not enough, since it only works as long as the
          server hosting the RMI object is alive.
          I'd like to add that the object is created and bound at client start-up and
          destroyed at client exit.
          Thank you for any advice or information,
          Dania Kodeih.


A: Replicating simple Java objects for automatic failover

That's what I figured. I guess the only solution in this case is to persist
          the object during client sessions. I was hoping for something simpler, but I
          guess I'll have to create an Entity Bean and everything else that comes with
          it.
          Thanks,
          Dania.
          Cameron Purdy wrote in message <[email protected]>...
          >Unfortunately, when the originating server goes down, the replicated object
          >disappears.
          >
          >Peace,
          >
          >--
          >Cameron Purdy
          >Tangosol, Inc.
          >http://www.tangosol.com
          >+1.617.623.5782
          >WebLogic Consulting Available
          >
          >
          >"Don Ferguson" <[email protected]> wrote in message
          >news:[email protected]..
          >> If I am not mistaken, any serializable object will automatically be
          >replicated
          >> across the tree.
          >>
          >> Dania Kodeih wrote:
          >>
          >> > Is there a way to replicate a simple java object that is bound from
          JNDI
          >> > across all servers so that if the primary server fails, it will
          >> > automatically failover?
          >> >
          >> > We have a java client that uses JNDI to access EJBs on WLS5.1 SP8. In
          >order
          >> > to determine client information, the client currently binds a simple
          >java
          >> > class in the JNDI tree. The Entity and Session beans use the caller
          >> > principal to locate the object in order to access client-information
    �... [Show more]
Read other 4 answers

JSF error message: Automatic prompting for file download

This is a weird problem. I have a JSF application wherin I popup a new window on a submit button.
The window opens a test.jsf page that redirects the output to a servlet1.
Servlet then based on some parameters does a sendRedirectI() to different servlets out of context.
Now the issue is that when the output is redirected to out of context servlet, that returns a file download.
If in IE browser, if one does not do a setting of "Automatic prompting for file download", this window that I had opened on submit buttton vanishes in a jiffy. If the IE setting is done, it shows the file download correctly.
I would want to show the user some kind of message by which he/she understands that this IE setting has to be done.
I have tried several ways:
1. Javascript: window.onbeforeunload on the test.jsf so that when the window unloads i can show some message. But since test.jsf forwards to servlet1, the html page generated does not show my script.
2. I also tried checking if some windows registry can help me understand the setting.
3. I tried writing in response object the javascript and then redirecting it to servlet out of context. But I guess sendRedirect() does a new request, so this did not help.
Can anyone help? I am not sure if I am able to explain my problem correctly.
Yani

Here is the result.I used your code and it worked fine with IE setting Enabled. But when I tried to access the download servlet after opening a new window, it doesnt download the file.

HACMP Clustering Script for SAP ECC 6.0 (SR1) - Automatic Failover

Hello,
I have installed the SAP ECC 6.0 (SR1) under AIX 5.3 / DB2 V8 FP12 with HACMP Clustering environment. Manual Failover is working fine. Central System has been installed in share drive with Virtual IP and Virtual name inNode A. Dialog Instance is loaded locally in Node B. I want to get HACMP Clustering script(automatic failover script) for Automation. Please help me if you have. It is single package clustering. If Node A fails, Node B will take care ( Central System and Dialog instance will run in Node B)
Thanks
Gautam Poddar

this post is duplicated at Upgrade to ERP 2005/ECC 6.0 from R/3 4.72/Basis 640 on Z/OS 1.4 DB2 8.1

HACMP Clustering Script for SAP ECC 6.0 (SR1) - Automatic Failover-Oracle10

Hello,
I have installed the SAP ECC 6.0 (SR1) under AIX 5.3 / Oracle 10g with HACMP Clustering environment. Manual Failover is working fine. ASCS and Database instances are loaded in share drive with Virtual IP and Virtual name. Central Instance and Dialog Instance are loaded locally in Node A and Node B. I want to get HACMP Clustering script(automatic failover script) for Automation. Please help me if you have.
Thanks
Gautam Poddar

Here are HA stop & start scripts that you should be able adapt for your particular circumstances. Based on earlier versions of SAP / Oracle but assume should be a reasonable guide
Script to start SAP is start_sap_prd
#!/bin/ksh
Script:         /usr/local/bin/cluster/start_sap_prd
Comments:       HACMP Application START script for PRD
Show me obvious information in hacmp.out
banner "Starting"
banner "PRD SAP"
Set the oracle and sap owner.
ORASID="PRD"
SAPADM="prdadm"
ORAUSR="oraprd"
VIRTUALHOST="vhost"
DEVHOST="vhostdev"
Get the volume groups for this resource group
RG=$( /usr/es/sbin/cluster/utilities/cllsgrp | grep -i $ )
VG_LIST=$( /usr/es/sbin/cluster/utilities/cllsres -g $ | \
        grep "VOLUME_GROUP=" | \
        awk -F\" '{ print $2 }' )
Check the transport directory is mounted.
if mount | grep -w "/usr/sap/trans"
then
        print "Transport directory is already mounted."
else
        cd /tmp
        print "Attempting a background mount of the transport directory."
        nohup mount -o intr,bg,soft :/usr/sap/trans1 /usr/sap/trans &
fi
#Start SAP and Oracle
#Start listener
su - $ -c /rprd/oracle/PRD/920_64/bin/lsnrctl start
rc=$?
if [ $? != 0 ]
then
        echo "ERROR: Listener failed to start\n"
fi
#Start Database
su - $ -c "/rprd/oracle/PRD/bin/start_database_PRD.sh"
sleep 20
Standard sapstart script
su - $ -c startsap $
Script:       /usr/local/bin/cluster/stop_sap_prd
Dated:        01/11/06
Application: Oracle/SAP
Comments:     HACMP Application STOP script for SAP / Oracle PRD
Show me obvious information in hacmp.out
Set the oracle and sap owner.
rc=$?
if [ $? != 0 ]
then
        echo "ERROR: Failed to start SAP\n"
fi
exit 0
Script to stop SAP is stop_sap_prd
#!/bin/ksh
set -x
banner "stopping"
banner "PRD SAP"
ORASID="PRD"
SAPADM="prdadm"
ORAUSR="oraprd"
VIRTUALHOST="vhost"
#Stop SAP/Oracle
su - $ -c stopsap $
rc=$?
if [ $? != 0 ]
then
        echo "ERROR: Failed to stop SAP and Oracle\n"
        break
fi
Stop SAP collector and Oracle listener.
su - $ -c /usr/sap/PRD/SYS/exe/run/saposcol -k
rc=$?
if [ $? != 0 ]
then
        echo "ERROR: Failed to stop SAPOSCOL \n"
fi
su - $ -c /rprd/oracle/PRD/920_64/bin/lsnrctl stop
rc=$?
if [ $? != 0 ]
then
        echo "ERROR: Listener failed to stop\n"
fi
if mount | grep -w "/usr/sap/trans"
then
        print "Transport directory is mounted."
        /usr/es/sbin/cluster/events/utils/cl_nfskill -k -u /usr/sap/trans
        sleep 1
        /usr/es/sbin/cluster/events/utils/cl_nfskill -k -u /usr/sap/trans
        sleep 1
        umount -f /usr/sap/trans &
else
        print "Transport directory is not mounted."
fi
exit 0

Retry interval and no of retry for messages with status Automatic Retry

Hi,
Can anyone explain how is the retry interval determined for messages which went into Automatic Retry mode?
Also can we define retry interval and no. of retry for such messages? if yes where?
Thanks in advance.
Regards,
Bharat

Hi Bharat,
the CSS note -
[#1298448 XI runtime: No automatic retry for EO message|http://service.sap.com/sap/support/notes/1298448]e
may be useful.
Regards
Kenny

How do I get Apple Mail to NOT automatically check for new messages?

Under General, I have it set to Manually, under each Gmail account (2) I have UNchecked the "include when automatically checking for new messages" under "Advanced", but it still checks automatically. Are there other settings that effect this behavior? I want it to ONLY check manually.

It seems to be impossible to stop the automatic push - I found another email client that permits me to access gmail via pop3, and that permits several things that Apple Mail is deficient in (as far as I'm concerned) - permits delete of email on Gmail without having it deleted on my laptop, and does not permit autpmatic push. I need access sto ALL my email under MY organization structure on my laptop, even when I do not have internet access, and Apple mail does not permit me to manage things my way (neither does gmail).

Automatic failover doesn't failback to the first server if the second server is lost.

Hi Everybody,
We use the database mirroring a lot in our product solutions and we have recently experienced a strange behaviour in our failover tests with SQL2008R2.
We have 2 servers running Windows 2008 R2 standard and SQL 2008 R2 standard SP2. (let's call them DB1 and DB2)
We also have a Witness workstation running SQL 2008 Express on a Windows 7
A database from DB1 is mirrored to DB2 in "safety full" mode, with witness. At this stage, the database is principal on DB1 and mirror on DB2
To test the automatic failover, we first restart the DB1 server which has the database in principal mode
After a few seconds, the database on DB2 becomes principal, which is normal , that's exactly what we want.
After a few minutes, DB1 comes back online and its database takes the mirror role (still OK). At this stage then, the database is principal on DB2 and mirror on DB1
when the monitoring application shows that the mirror is synchronized and that both servers are connected to the witness, we restart DB2 to trigger an automatic failover to DB1.
What we see is that DB1 never takes the principal role and the database stays in mirror.
In the DB1 Errorlog, I only see these 2 lines when DB2 disappears, no other message related to the mirroring session.
2014-01-22 08:57:26.91 spid43s Starting up database 'Test123'.
2014-01-22 08:57:26.95 spid43s Bypassing recovery for database 'Test123' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
When DB2 comes back online, the database on DB2 keeps its principal status and the database on DB1 stays mirror.
And what is really really strange is that, if I restart DB2 once again, directly after that, DB1 failover normally and the database on DB1 takes the principal role after a few seconds. without any configuration changes between the 2 restarts.
DB1 errorlog shows then :
2014-01-22 09:00:37.53 spid29s Error: 1474, Severity: 16, State: 1.
2014-01-22 09:00:37.53 spid29s Database mirroring connection error 4 'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://DB2:5022'.
2014-01-22 09:00:37.53 spid18s Database mirroring is inactive for database 'Test123'. This is an informational message only. No user action is required.
2014-01-22 09:00:42.37 spid32s The mirrored database "Test123" is changing roles from "MIRROR" to "PRINCIPAL" due to Auto Failover.
2014-01-22 09:00:42.39 spid32s Recovery is writing a checkpoint in database 'Test123' (7). This is an informational message only. No user action is required.
2014-01-22 09:00:42.39 spid32s Recovery completed for database Test123 (database ID 7) in 78 second(s) (analysis 0 ms, redo 0 ms, undo 7 ms.) This is an informational message only. No user action is required.
So, if I summarize,
- a first failover from DB1 to DB2 always work
- then, a restart of DB2 never failover to DB1
- a second restart of DB2 always failover to DB1
This is pretty much systematic on one our server couple.
Any explanation for this or any idea where I can search to find the reason of this strange behavior ?
Thanks a lot for your help
Seb

Thank you Tom
But I have already checked that and reported the Errorlog abstracts in my original post.
When DB01 disapears for the first time, nothing in the DB01 ERRORLOG (it is restarting :-) )
AND no particular error message in the DB02 ERRORLOG (nothing related to the fact that DB01 is not reachable anymore !!! )
Only these two lines
2014-01-22 08:57:26.91 spid43s Starting
up database 'Test123'.
2014-01-22 08:57:26.95 spid43s Bypassing recovery
for database 'Test123' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required.
So my main question remains Why DB02 doesn't detect that DB01 disapears (and the first time only) and why the failover mechanism doesn't trigger the failover ?
Thank you
Seb

SQL 2005 mirroring : Abrupt Automatic failover

hi All,
We have a SQL 2005 SP4 mirroring setup of 15 DBs with Principal(P), Mirror(M) & Witness (W).
We have now seen abrupt DB failovers for some of the databases (yest it was 4 out of 15) from P to M.
Errors were seen on Witness server as follows for all Dbs that failed over:
Date 07/01/2015 11:07:48 PM
Log SQL Server (Current - 08/01/2015 12:00:00 AM)
Source spid19s
Message
The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response. Check the service and network connections.
Actions taken:
1. Network and Firewall team reverted that no error detected and no network traffic between the witness server and db server during the db auto failover period.
2. On the system side, we have verified that no hardware error found on either VM or SAN storage, and no Symantec SQL backup jobs running nor anti virus scanning during the db auto failover period too.
3. We did see some high amount of IO activity on P server around failover time. Some IO errors similar to below were seen, however point to note is these errors were not only for the DBs that failed over, but for others including TEMPDB:
Date 07/01/2015 11:07:38 PM
Log SQL Server (Current - 08/01/2015 4:06:00 AM)
Source spid2s
Message
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [R:\SQLDATA\MSSQL.1\MSSQL\Data\<DBName>.mdf] in database [DBName] (5). The OS file handle is 0x000000000000095C. The offset of the
latest long I/O is: 0x0000054ff22000
Questions:
1. I assumed that the Witness keeps polling P & M on DB mirroring endpoints (in our case 5022) to check that the DBs are online, but Network team says there is no activity on that port, is my understanding correct?
2. Is there any other reason for DB failover ?
Link referred:
http://dba.stackexchange.com/questions/22402/what-can-cause-a-mirroring-session-to-timeout-then-failover-sql-server-2005
http://msdn.microsoft.com/en-us/library/ms179344(v=sql.90).aspx
Any help is highly appreciated!!!
Regards,
Mandar

This is common with Mirroring server it is not as resilient to changes as log shipping. Are you aware about
below fact although not directly related to your question
If you plan to use high-safety mode with automatic failover, the normal load on each failover partner should be less than 50 percent of the CPU. If your work load overloads the CPU, a failover partner might be unable to ping the other server instances in
the mirroring session. This causes a unnecessary failover. If you cannot keep the CPU usage under 50 percent, we recommend that you use either high-safety mode without automatic failover or high-performance mode.
Now to your problem
The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response. Check the service and network connections.
I would say there was network dip for more than 10 seconds and since default failover time is 10 seconds and for few databases witness thought principal cannot be reached it initiated failover.
Network team is incorrect to say there was no dip (its common with NOC team not to take responsibility)
This Support Article is worth reading specially the network part
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Automatic failover to an alternate Directory Server

We have two messaging server (Server A and Server B) running with independent LDAP server and replication is enabled between two.
In order to use automatic failover to an alternate Directory Server, I configured like this on Server A
configutil -o local.ugldaphost -v �serverA serverB�
Now to test the configuration I stopped the LDAP server on server A and run[b] imsimta test �rewrite-debug, it worked fine. But when I tried the authenticate user from pop3 or HTTP it came out with an error �Authentication Server is temporarily unavailable�
Any reason why it�s not doing the failover for HTTP, POP3 and IMAP authentication?

sorry I forget this
Sun Java(tm) System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004)
libimta.so 6.1 HotFix 0.01 (built 17:31:31, Jun 24 2004)
SunOS test.abc.com 5.9 Generic_112234-03 i86pc i386 i86pc

Automatic failover for message consumers

Similar Messages

Maybe you are looking for