Request status in Fail over

          Process to Find request status if fail over happen in middle of some request at
          application level, because I need this to do control at application level. Some
          will help me in this issue.

failover is automatic. you only failover for idempotent method invocations.
 there is no control that you can use in the application. except when the
 failover also fails and returns an exception to the application for the
 application to handle.
 sree
 "srouthu" <[email protected]> wrote in message
 news:40bec785$1@mktnews1...
 >
 > Process to Find request status if fail over happen in middle of some
 request at
 > application level, because I need this to do control at application level.
 Some
 > will help me in this issue.

Similar Messages

DAG Sporadic Entire Server DB Fail Over

Hi,
I have been having this issues for a while now, I have two physical exchange servers in a DAG, both on Exchange 2013 CU1. Randomly, every few days and various times, Server1 will fail all of it's databases over to Server2. I'll redistribute them, and again,
say Server2 will fail all databases to Server1. In short, both servers at times have failed their databases over.
I started with this: http://technet.microsoft.com/en-us/library/dd351258(v=exchg.150).aspx which led me to setup monitoring of the Microsoft-Exchange-ManagedAvailability logs. I can tell you that replication tests work fine, and the health of all the
databases are fine.
My monitoring turned up the following errors, in this example "EX0001" was the server that failed all of it's databases over to "EX0002". It seems pretty clear to me, that Exchange Managed Availability, is finding an issue with
EWS, attempting to restart the MSExchangeServicesApp pool and cannot due to "Throttling" so ti fails the DB's over, that's my best guess...the problem is I dont know how to fix this...I've run through troubleshooting EWS Healthset, nothing
really turns up... http://technet.microsoft.com/en-us/library/ms.exch.scom.ews.protocol(v=exchg.150).aspx
EX0001
1011
Microsoft-Exchange-ManagedAvailability
Recovery
Microsoft-Exchange-ManagedAvailability/RecoveryActionLogs
5/22/2014 7:06:43 AM
Warning (Info)
1520183
NT AUTHORITY\SYSTEM
RecycleApplicationPool-MSExchangeServicesAppPool-EWSSelfTestRestart: Throttling rejected the operation
EX0001
4
Microsoft-Exchange-ManagedAvailability
Monitoring
Microsoft-Exchange-ManagedAvailability/Monitoring
5/22/2014 7:17:27 AM
Error (Info)
8287
NT AUTHORITY\SYSTEM
The EWS.Protocol health set has detected a problem on EX0001 beginning at 5/22/2014 10:55:12 AM (UTC). The health manager is reporting that recycling the MSExchangeServicesAppPool
app pool has failed to restore health and it has tried to fail over active copies of local databases to a healthy server. Attempts to auto-recover from this condition have failed and requires Administrator attention. Details below: MachineName:
EX0001 ServiceName: EWS.Protocol ResultName: EWSSelfTestProbe/MSExchangeServicesAppPool Error: System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) Exception: System.Exception: System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.ThrowError(Object key, Object exceptiondata, String logDetails) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.DoWorkInternal(CancellationToken
cancellationToken) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.RunEWSGenericProbe(CancellationToken cancellationToken) at Microsoft.Exchange.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken) at Microsoft.Exchange.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute() ExecutionContext: EWSGenericProbeError:Exception=System.Exception: System.Exception: >>> PRIMARY ENDPOINT VERIFICATION EwsUrl=https://localhost:444/ews/exchange.asmx
UserName/Password=HealthMailbox663889950a344102878cede289222a46@domain.local/xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt AuthMethod=CAFE ConvertId (Attempt #0) Status=The
request failed. The operation has timed out ConvertId (Attempt #0) Latency=59521.1327 ConvertId (Attempt #1) Status=iteration 1; 55.427003 seconds elapsed ConvertId (Attempt #1) Latency=55427.003 at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSCommon.RetrySoapActionAndThrow(Action
operation, String soapAction, ExchangeServiceBase service) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon.ExecuteEWSCall(String endPoint, String operation, Boolean verifyAffinity) at Microsoft.Exchange.Monitoring.ActiveMonitoring.Ews.Probes.EWSGenericProbeCommon
FailureContext: ResultType: Failed IsNotified: False DeploymentId: 0 RetryCount: 0 ExtensionXml: Version: StateAttribute1:
EWS StateAttribute2: Unknown StateAttribute3: StateAttribute4: StateAttribute5: StateAttribute6: 0 StateAttribute7: 0 StateAttribute8:
0 StateAttribute9: 0 StateAttribute10: 0 StateAttribute11: StateAttribute12: StateAttribute13: StateAttribute14: StateAttribute14:
StateAttribute16: 0 StateAttribute17: 0 StateAttribute18: 0 StateAttribute19: 0 StateAttribute20: 120011 StateAttribute21: [000.000] EWSCommon
start: 5/22/2014 11:13:13 AM [000.000] Configuring EWScommon [000.000] Probe time limit: 120000ms, HTTP timeout: 59500ms, RetryCount: 1 [000.047] using authN: CAFE
[email protected] xGAVmP[^jn{qGgOx0Jtx:4X+-j@?d%XM?@7yErsoFF[_#u[%LcX=0hPzMln#1PiQ/7z?14rJJs8Dc)AYLi0F9mU)bMpL_gj{Q3*[Yt1:UgX=:CkQc=[Xuagz%Od=|@tt
[000.047] using HTTP request timeout: 59500 ms [000.047] action iteration 0 [000.047] starting (total time left 119954 ms) [059.568] action threw Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The operation has timed out [064.584]
action iteration 1 [064.584] starting (total time left 55416 ms) [120.011] action wait timed out [120.011] action threw System.TimeoutException: iteration 1; 55.427003 seconds elapsed StateAttribute22: StateAttribute23:
StateAttribute24: StateAttribute25: PoisonedCount: 0 ExecutionId: 32395373 ExecutionStartTime: 5/22/2014 11:13:13 AM ExecutionEndTime: 5/22/2014
11:15:13 AM ResultId: 253233015 SampleValue: 0 ------------------------------------------------------------------------------- States of all monitors within the health set: Note: Data may be stale. To get current data,
run: Get-ServerHealth -Identity 'EX0001' -HealthSet 'EWS.Protocol' State Name TargetResource HealthSet AlertValue ServerComponent ----- ---- -------------- --------- ---------- --------------- NotApplicable EWSSelfTestMonitor MSExchangeServicesAppPool EWS.Protocol
Unhealthy None NotApplicable EWSDeepTestMonitor DG01DB15 EWS.Protocol Unhealthy None NotApplicable PrivateWorkingSetWarningThresholdExc... msexchangeservicesapppool EWS.Protocol Healthy None NotApplicable ProcessProcessorTimeErrorThresholdEx... msexchangeservicesapppool
EWS.Protocol Healthy None NotApplicable ExchangeCrashEventErrorThresholdExce... msexchangeservicesapppool EWS.Protocol Healthy None States of all health sets: Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX0001' State HealthSet
AlertValue LastTransitionTime MonitorCount ----- --------- ---------- ------------------ ------------ NotApplicable Autodiscover.Protocol Healthy 3/8/2014 12:46:17 AM 4 NotApplicable ActiveSync.Protocol Healthy 3/8/2014 1:15:35 AM 7 NotApplicable ActiveSync
Healthy 3/8/2014 2:08:15 AM 3 NotApplicable EDS Healthy 5/22/2014 5:19:41 AM 13 NotApplicable ECP Healthy 3/8/2014 1:15:27 AM 3 NotApplicable EventAssistants Healthy 5/22/2014 5:48:56 AM 28 NotApplicable EWS.Protocol Unhealthy 5/22/2014 7:07:12 AM 5 NotApplicable
FIPS Healthy 5/21/2014 10:24:01 PM 18 NotApplicable AD Healthy 2/23/2014 10:42:29 PM 10 NotApplicable OWA.Protocol.Dep Healthy 5/22/2014 5:19:40 AM 1 NotApplicable Monitoring Unhealthy 5/22/2014 5:35:31 AM 9 Online HubTransport Unhealthy 5/22/2014 5:19:43
AM 138 NotApplicable DataProtection Healthy 5/22/2014 7:08:02 AM 201 NotApplicable AntiSpam Healthy 5/22/2014 5:19:40 AM 4 NotApplicable Network Healthy 5/21/2014 10:36:54 PM 1 NotApplicable OWA.Protocol Healthy 3/8/2014 1:15:34 AM 5 NotApplicable MailboxMigration
Healthy 3/8/2014 12:46:18 AM 4 NotApplicable MRS Healthy 3/8/2014 12:44:35 AM 9 NotApplicable MailboxTransport Healthy 5/22/2014 5:19:41 AM 57 NotApplicable PublicFolders Healthy 5/21/2014 10:44:15 PM 4 NotApplicable RPS Healthy 2/23/2014 11:38:33 PM 1 NotApplicable
Outlook.Protocol Healthy 4/22/2014 11:04:18 AM 3 NotApplicable UserThrottling Healthy 5/22/2014 5:51:13 AM 7 NotApplicable SiteMailbox Healthy 3/8/2014 2:10:53 AM 3 NotApplicable UM.Protocol Healthy 5/22/2014 5:19:41 AM 17 NotApplicable Store Healthy 5/22/2014
5:19:43 AM 225 NotApplicable MSExchangeCertificateDeplo... Disabled 1/1/0001 12:00:00 AM 2 NotApplicable DAL Healthy 8/2/2013 12:59:03 AM 16 NotApplicable Search Healthy 5/22/2014 5:37:18 AM 269 Online EWS.Proxy Healthy 5/5/2014 1:34:08 AM 1 Online RPS.Proxy
Healthy 5/5/2014 1:34:38 AM 13 Online OAB.Proxy Healthy 5/5/2014 1:34:37 AM 1 Online ECP.Proxy Healthy 5/5/2014 1:34:17 AM 4 Online OWA.Proxy Healthy 5/5/2014 1:34:25 AM 2 Online Outlook.Proxy Healthy 5/5/2014 1:34:08 AM 1 Online Autodiscover.Proxy Healthy
5/5/2014 1:34:08 AM 1 Online ActiveSync.Proxy Healthy 5/5/2014 1:34:35 AM 1 Online RWS.Proxy Healthy 5/5/2014 1:34:18 AM 10 NotApplicable Autodiscover Healthy 5/21/2014 10:24:01 PM 2 Online FrontendTransport Healthy 5/15/2014 12:49:31 AM 11 NotApplicable EWS
Unhealthy 5/22/2014 7:06:01 AM 2 NotApplicable OWA Healthy 2/23/2014 11:37:56 PM 1 NotApplicable Outlook Healthy 3/8/2014 12:45:14 AM 5 Online UM.CallRouter Healthy 5/22/2014 5:19:41 AM 7 NotApplicable RemoteMonitoring Healthy 8/2/2013 12:58:03 AM 1 NotApplicable
POP.Protocol Healthy 5/20/2014 9:22:12 AM 5 NotApplicable IMAP.Protocol Healthy 5/20/2014 9:22:21 AM 5 Online POP.Proxy Healthy 3/7/2014 1:31:10 PM 1 Online IMAP.Proxy Healthy 3/7/2014 1:31:10 PM 1 NotApplicable IMAP Healthy 5/20/2014 9:23:32 AM 2 NotApplicable
POP Healthy 5/20/2014 9:17:18 AM 2 NotApplicable Antimalware Healthy 5/15/2014 8:33:13 AM 8 NotApplicable FfoQuarantine Healthy 8/2/2013 12:58:20 AM 1 Online Transport Healthy 5/22/2014 5:38:00 AM 9 NotApplicable Security Healthy 3/8/2014 12:46:09 AM 3 NotApplicable
Datamining Healthy 3/8/2014 12:45:44 AM 3 NotApplicable Provisioning Healthy 3/8/2014 12:45:40 AM 3 NotApplicable ProcessIsolation Healthy 3/8/2014 12:47:05 AM 12 NotApplicable TransportSync Healthy 3/8/2014 12:45:37 AM 3 NotApplicable MessageTracing Healthy
3/8/2014 12:44:56 AM 3 NotApplicable CentralAdmin Healthy 3/8/2014 12:45:12 AM 3 NotApplicable OAB Healthy 8/2/2013 1:02:27 AM 3 NotApplicable Calendaring Healthy 8/2/2013 1:02:07 AM 3 NotApplicable PushNotifications.Protocol Healthy 2/23/2014 10:46:17 PM
3 NotApplicable Ediscovery.Protocol Healthy 5/21/2014 10:38:16 PM 1 NotApplicable HDPhoto Healthy 5/6/2014 9:36:25 AM 1 NotApplicable Clustering Healthy 3/8/2014 12:45:34 AM 4 NotApplicable DiskController Healthy 4/22/2014 2:51:30 AM 1 NotApplicable MailboxSpace
Healthy 5/22/2014 6:16:51 AM 96 NotApplicable FreeBusy Healthy 5/22/2014 5:32:54 AM 1 Note: Subsequent detected alerts are suppressed until the health set is healthy again.

Hi,
Based on the error message, throttling rejected the operation. I recommend you use the Get-ThrottlingPolicy | fl cmdlet to view EWS settings in throttling policy.
You can modify the default throttling policy and set the basic settings for EWS. Then restart the Microsoft Exchange Throttling service and recycle the MSExchangeServicesAppPool to check the result.
For more information about the EWS throttling, you can refer to the following articles.
EWS throttling in Exchange
http://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx
EWS Best Practices: Understand Throttling Policies
http://blogs.msdn.com/b/mstehle/archive/2010/11/09/ews-best-practices-understand-throttling-policies.aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Servlet fail-over problem

 I'm testing WebLogic clustering of servlets with in-memory-replication in Sun platform
 (wls 5.1 sp9) and using Apache plug-in.
 I did this test:
 - I configured a cluster of two servers
 - I simulate a situation of hang, in one of the two servers, filling all execution
 threads with servlets doing Thread.sleep()
 - I tried to launch a request to the cluster (a JSP request) but my request timed
 out
 after ConnectTimeoutSecs.
 Looking at the wlproxy.log it seems that the cluster attempts to failover to
 the
 secondary server (after HungServerRecoverSecs) but it doesn't respond, then it
 retries
 with the primary server and so on ( waiting every time HungServerRecoverSecs for
 a
 response) until the timeout "ConnectTimeoutSecs" is reached.
 This is very strange because the secondary server is not hung; if I launch a request
 directly to it (specifying in the URL host:port) it responds to me.
 I have also tried to specify the parameter Idempotent ON, even if the default
 is ON, but
 with no result.
 Can anyone help me?


 I solved the problem setting the parameter weblogic.system.servletThreadCount
 in the cluster properties file.
 Now another problem raised.
 When one of server of the cluster is in a status of hang the cluster
 carry out fail-over to the second server but session information is lost.
 Can anyone help me?
 "Mike Reiche" <[email protected]> wrote:
 >
 >Don't take this as absolute gospel - it is just my understanding of how
 >things
 >work.
 >
 >Since the WL server is still alive, it will accept connections. This
 >takes ConnectTimeOutSecs
 >out of the picture.
 >
 >Now you're just left with HungRecoverSeconds. If the response takes longer
 >than
 >HungRecoverSeconds, then wlproxy will deem the request to have 'timed
 >out'. If
 >it is not Idempotent, that's it, you're done. If it is Idempotent, wlproxy
 >will
 >retry - on the other wl instance. From what you describe, the second
 >one should
 >work - unless of course the second WL is also backed up with Thread.sleep()
 >-
 >then after HungRecoverSeconds, the request will be resent to an available
 >WL instance.
 >
 >"Lucia Giraldo" <[email protected]> wrote:
 >>
 >>I'm testing WebLogic clustering of servlets with in-memory-replication
 >>in Sun platform
 >>(wls 5.1 sp9) and using Apache plug-in.
 >>I did this test:
 >>- I configured a cluster of two servers
 >>- I simulate a situation of hang, in one of the two servers, filling
 >>all execution
 >>threads with servlets doing Thread.sleep()
 >>- I tried to launch a request to the cluster (a JSP request) but my
 >request
 >>timed
 >>out
 >>after ConnectTimeoutSecs.
 >>Looking at the wlproxy.log it seems that the cluster attempts to failover
 >>to
 >>the
 >>secondary server (after HungServerRecoverSecs) but it doesn't respond,
 >>then it
 >>retries
 >>with the primary server and so on ( waiting every time HungServerRecoverSecs
 >>for
 >>a
 >>response) until the timeout "ConnectTimeoutSecs" is reached.
 >>This is very strange because the secondary server is not hung; if I
 >launch
 >>a request
 >>directly to it (specifying in the URL host:port) it responds to me.
 >>I have also tried to specify the parameter Idempotent ON, even if the
 >>default
 >>is ON, but
 >>with no result.
 >>Can anyone help me?
 >

SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
Keegan

Hi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

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

Failing over after WRITE_ERROR_TO_SERVER exception in sendRequest()

Hi
I am getting below error in my issproxy.log file. I wanted to see the source of this URL.cpp file to find out why it is failing. I am not able to open them using DLL decompiler as well.
Could anyone tell me where can I get the source code for iisproxy.dll and iisforward.dll ?
This request is failing only when the request is routed from IIS.
================New Request: [/GLMS/index.jsp.wlforward] =================
Mon Nov 24 14:19:48 2014 <503614168189882> SSL must be used
Mon Nov 24 14:19:48 2014 <503614168189882> Initializing SSL
Mon Nov 24 14:19:48 2014 <503614168189881> INFO: Initializing SSL library
Mon Nov 24 14:19:48 2014 <503614168189881> timer thread starting
Mon Nov 24 14:19:48 2014 <503614168189881> Loaded 1 trusted CA's
Mon Nov 24 14:19:48 2014 <503614168189881> sysMkdirs() on 'C:\windows\TEMP\_wl_proxy':
Mon Nov 24 14:19:48 2014 <503614168189881> getWLFilePath: Complete File name = [C:\windows\TEMP\_wl_proxy\orbrandom.txt]
Mon Nov 24 14:19:48 2014 <503614168189881> INFO: Successfully initialized SSL
Mon Nov 24 14:19:48 2014 <503614168189882> SSL configured successfully
Mon Nov 24 14:19:48 2014 <503614168189882> resolveRequest: wlforward: /TEST/index.jsp
Mon Nov 24 14:19:48 2014 <503614168189882> URI is /GLMS/index.jsp, len=15
Mon Nov 24 14:19:48 2014 <503614168189882> Request URI = [/TEST/index.jsp]
Mon Nov 24 14:19:48 2014 <503614168189882> attempt #0 out of a max of 50
Mon Nov 24 14:19:48 2014 <503614168189882> Trying a pooled connection for 'XX.XX.XX.XX/7002/7002'
Mon Nov 24 14:19:48 2014 <503614168189882> getPooledConn: No more connections in the pool for Host[XX.XX.XX.XX] Port[7002] SecurePort[7002]
Mon Nov 24 14:19:48 2014 <503614168189882> general list: trying connect to '192.168.17.180'/7002/7002 at line 1306 for '/GLMS/index.jsp'
Mon Nov 24 14:19:48 2014 <503614168189882> New SSL URL: match = 0 oid = 22
Mon Nov 24 14:19:48 2014 <503614168189882> Connect returns -1, and error no set to 10035, msg 'Unknown error'
Mon Nov 24 14:19:48 2014 <503614168189882> EINPROGRESS in connect() - selecting
Mon Nov 24 14:19:48 2014 <503614168189882> Setting peerID for new SSL connection
Mon Nov 24 14:19:48 2014 <503614168189882> c0a8 11b4 5a1b 0000 ....Z...
Mon Nov 24 14:19:48 2014 <503614168189882> Local Port of the socket is 57397
Mon Nov 24 14:19:48 2014 <503614168189882> Remote Host xx.xx.xx.xx Remote Port 7002
Mon Nov 24 14:19:48 2014 <503614168189882> general list: created a new connection to 'XX.XX.XX.XX'/7002 for '/GLMS/index.jsp', Local port: 57397
Mon Nov 24 14:19:48 2014 <503614168189882> WLS info in sendRequest: XX.XX.XX.XX:7002 recycled? 0
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs from client:[Accept]=[application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs from client:[Accept-Encoding]=[gzip, deflate]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs from client:[Accept-Language]=[en-IN]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs from client:[Cookie]=[ADMINCONSOLESESSION=9fTkJypQ229r1ZHx6cQZG8cwHb0T0ssW8TkM7zyzzCVvNzjzDsf2!1779325670; JSESSIONID=GcZVJyXT8WMyv9pT8xGNzndSPCbBCcy1tfm5yRG1DSv8PhT97gv9!1779325670; _WL_AUTHCOOKIE_ADMINCONSOLESESSION=WcL9RbOJFiDqn3LiZO0g]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs from client:[Host]=[localhost]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs from client:[User-Agent]=[Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)]
Mon Nov 24 14:19:48 2014 <503614168189882> URL::sendHeaders(): meth='GET' file='/GLMS/index.jsp' protocol='HTTP/1.1'
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[Accept]=[application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[Accept-Encoding]=[gzip, deflate]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[Accept-Language]=[en-IN]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[Cookie]=[ADMINCONSOLESESSION=9fTkJypQ229r1ZHx6cQZG8cwHb0T0ssW8TkM7zyzzCVvNzjzDsf2!1779325670; JSESSIONID=GcZVJyXT8WMyv9pT8xGNzndSPCbBCcy1tfm5yRG1DSv8PhT97gv9!1779325670; _WL_AUTHCOOKIE_ADMINCONSOLESESSION=WcL9RbOJFiDqn3LiZO0g]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[Host]=[localhost]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[User-Agent]=[Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[Connection]=[Keep-Alive]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[WL-Proxy-Client-IP]=[::1]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[Proxy-Client-IP]=[::1]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[X-Forwarded-For]=[::1]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[WL-Proxy-Client-Keysize]=[128]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[X-WebLogic-Force-JVMID]=[unset]
Mon Nov 24 14:19:48 2014 <503614168189882> Hdrs to WLS:[WL-Proxy-SSL]=[true]
Mon Nov 24 14:19:48 2014 <503614168189881> WARN: GetSessionCallback: No session match found
Mon Nov 24 14:19:48 2014 <503614168189881> WARN: DeleteSessionCallback: No match found!!
Mon Nov 24 14:19:48 2014 <503614168189882> ERROR: SSLWrite failed
Mon Nov 24 14:19:48 2014 <503614168189882> SEND failed (ret=-1) at 805 of file ..\nsapi\.\URL.cpp
Mon Nov 24 14:19:48 2014 <503614168189882> *******Exception type [WRITE_ERROR_TO_SERVER] raised at line 806 of ..\nsapi\.\URL.cpp
Mon Nov 24 14:19:48 2014 <503614168189882> Marking xx.xx.xx.xx:7002 as bad
Mon Nov 24 14:19:48 2014 <503614168189882> Exception occurred for backend host 'XX.XX.XX.XX/7002/0' while sending request : 'WRITE_ERROR_TO_SERVER [os error=0, line 806 of ..\nsapi\.\URL.cpp]: '
Mon Nov 24 14:19:48 2014 <503614168189882> got exception in sendRequest phase: WRITE_ERROR_TO_SERVER [os error=0, line 806 of ..\nsapi\.\URL.cpp]: at line 1019; last_error 0
Mon Nov 24 14:19:48 2014 <503614168189882> INFO: Closing SSL context
Mon Nov 24 14:19:48 2014 <503614168189882> Failing over after WRITE_ERROR_TO_SERVER exception in sendRequest()

yes that is right.
Essentially you should be doing one of the following on weblogic side:
1) Installed Certs on weblogic that were obtained from a commercial CA. (like verisign, thawte etc)
In this case, you will receive rootCA crt along with the other bundled certs and private key.
these rootCA certs are publicly available (your browser will be already using them)
2) Using certs signed by your company. (companies can maintain their own CA)
In this case you should be having a rootCA cert from your company.
3) using demo certs that were shipped with weblogic.
In this case, the rootca cert can be obtained from DemoTrust.jks
this is documented at http://e-docs.bea.com/wls/docs90/plugins/isapi.html#114851 (should be same for any plugins)
Apache plug-in can understand .crt extension.
-Vijay

Http cluster servlet not failing over when no answer received from server

          I am using weblogic 510 sp9. I have a weblogic server proxying all requests to
          a weblogic cluster using the httpclusterservlet.
          When I kill the weblogic process servicing my request, I see the next request
          get failed over to the secondary server and all my session information has been
          replicated. In short I see the behavior I expect.
          r.troon
          However, when I either disconnect the primary server from the network or just
          switch this server off, I just get a message back
          to the browser - "unable to connect to servers".
          I don't really understand why the behaviour should be different . I would expect
          both to failover in the same manner. Does the cluster servlet only handle tcp
          reset failures?
          Has anybody else experience this or have any ideas.
          Thanks


I think I might have found the answer......
The AD objects for the clusters had been moved from the Computers OU into a newly created OU. I'm suspecting that the cluster node computer objects didn't have perms to the cluster object within that OU and that was causing the issue. I know I've seen cluster
object issues before when moving to a new OU.
All has started working again for the moment so I now just need to investigate what permissions I need on the new OU so that I can move the cluster object in.

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

GSLB Zone-Based DNS Payment Gw - Config Active-Active: Not Failing Over

Hello All:
Currently having a bit of a problem, have exhausted all resources and brain power dwindling.
Brief:
Two geographically diverse sites. Different AS's, different front ends. Migrated from one site with two CSS 11506's to two sites with one 11506 each.
Flow of connection is as follows:
Client --> FW Public Destination NAT --> CSS Private content VIP/destination NAT --> server/service --> CSS Source VIP/NAT --> FW Public Source NAT --> client.
Using Load Balancers as DNS servers, authoritative for zones due to the requirement for second level Domain DNS load balancing (i.e xxxx.com, AND FQDNs http://www.xxxx.com). Thus, CSS is configured to respond as authoritative for xxxx.com, http://www.xxxx.com, postxx.xxxx.com, tmx.xxxx.com, etc..., but of course cannot do MX records, so is also configured with dns-forwarders which consequently were the original DNS servers for the domains. Those DNS servers have had their zone files changed to reflect that the new DNS servers are in fact the CSS'. Domain records (i.e. NS records in the zone file), and the records at the registrar (i.e. tucows, which I believe resells .com, .net and .org for netsol) have been changed to reflect the same. That part of the equation has already been tested and is true to DNS Workings. The reason for the forwarders is of course for things such as non load balanced Domain Names, as well as MX records, etc...
Due to design, which unfortunately cannot be changed, dns-record configuration uses kal-ap, example:
dns-record a http://www.xxxx.com 0 111.222.333.444 multiple kal-ap 10.xx.1.xx 254 sticky-enabled weightedrr 10
So, to explain so we're absolutely clear:
- 111.222.333.444 is the public address returned to the client.
- multiple is configured so we return both site addresses for redundancy (unless I'm misunderstanding that configuration option)
- kal-ap and the 10.xx.1.xx address because due to the configuration we have no other way of knowing the content rule/service is down and to stop advertising the address for said server/rule
- sticky-enabled because we don't want to lose a payment and have it go through twice or something crazy like that
- weighterr 10 (and on the other side weightedrr 1) because we want to keep most of the traffic on the site that is closer to where the bulk of the clients are
So, now, the problem becomes, that the clients (i.e. something like an interac machine, RFID tags...) need to be able to fail over almost instantly to either of the sites should one lose connectivity and/or servers/services. However, this does not happen. The CSS changes it's advertisement, and this has been confirmed by running "nslookups/digs" directly against the CSSs... however, the client does not recognize this and ends up returning a "DNS Error/Page not found".
Thinking this may have something to do with the "sticky-enabled" and/or the fact that DNS doesn't necessarily react very well to a TTL of "0".
Any thoughts... comments... suggestions... experiences???
Much appreciated in advance for any responses!!!
Oh... should probably add:
nslookups to some DNS servers consistently - ALWAYS the same ones - take 3 lookups before getting a reply. Other DNS servers are instant....
Cheers,
Ben Shellrude
Sr. Network Analyst
MTS AllStream Inc

Hi Ben,
if I got your posting right the CSSes are doing their job and do advertise the correct IP for a DNS-query right?
If some of your clients are having a problem this might be related to DNS-caching. Some clients are caching the DNS-response and do not do a refresh until they fail or this timeout is gone.
Even worse if the request fails you sometimes have to reset the clients DNS-demon so that they are requesting IP-addresses from scratch. I had this issue with some Unixboxes. If I remeber it corretly you can configure the DNS behaviour for unix boxes and can forbidd them to cache DNS responsed.
Kind Regards,
joerg

JDBC - Fail over connection

Hello Group,
I ´m currently working on the follwing szenario in XI (NW2004, SP19):
Via the jdbc adapter I send a sql statement to a database (db1) and get the response. This works fine.
Because it´s a very important request, I have a second database (db2) with exactly the same data as in db1. When the db1 is not reachable, the adapter should connect automatically the db2.
Can I handle this with the jdbc adapter (fail over connection)? Or with another configuration in the XI.
Thanks in advance.
Kind regards,
Martin

hi
you can use a bpm with an exception brach where you specify if first db fail try to connect to db2
it a useful solution

Replication fail-over and reconfiguration

I would like to get a conversation going on the topic of Replication, I have
setup replication on several sites using the Netscape / iPlanet 4.x server
and all has worked fine so far. I now need to produce some documentation and
testing for replication fail-over for the master. I would like to hear from
anyone with some experience on promoting a consumer to a supplier. I'm
looking for the best practice on this issue. Here is what I am thinking,
please feel free to correct me or add input.
Disaster recovery plan:
1.) Select a consumer from the group of read-only replicas
2.) Change the database from Read-Only to Read-Write
3.) Delete the replication agreement (in my case I am using a SIR)
4.) Create a new agreement to reflect the supplier status of the chosen
replica (again a SIR for me)
5.) Reinitialize the consumers (Online or LDIF depending on your number of
entries)
That is the general plan so far. Other questions and topics might include:
1.) What to do when the original master comes back online
2.) DNS round-robin strategies (Hardware assistance, Dynamic DNS, etc)
3.) General backup and recovery procedures when: 1.) Directory is corrupted
2.) Link is down / network is partitioned 3.) Disk / server corruption /
destruction
Well I hope that is a good basis for getting a discussion going. Feel free
to email me if you have questions or I can help you with one of your issues.
Best regards,
Ray Cormier

There is no failover in Meta-Directory 5.1, you can implement manual failover on the metaview by using multi-master replication with Directory Server. There are limitations and this is a manual process.
- Paul

VIP is not failed over to surviving nodes in oracle 11.2.0.2 grid infra

Hi ,
It is a 8 node 11.2.0.2 grid infra.
While pulling both cables from public nic the VIP is not failed over to surviving nodes in 2 nodes but remainng nodes VIP is failed over to surviving node in the same cluster. Please help me on this.
If we will remove the power from these servers VIP is failed over to surviving nodes
Public nic's are in bonding.
grdoradr105:/apps/grid/grdhome/sh:+ASM5> ./crsstat.sh |grep -i vip |grep -i 101
ora.grdoradr101.vip ONLINE OFFLINE
grdoradr101:/apps/grid/grdhome:+ASM1> cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.4.0-1 (October 7, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 84:2b:2b:51:3f:1e
Slave Interface: eth1
MII Status: up
Speed: 100 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 84:2b:2b:51:3f:20
Thanks
Bala

Please check below MOS note for this issue.
1276737.1
HTH
Edited by: krishan on Jul 28, 2011 2:49 AM

Fail-over Recovery ?

Hi All,
can anyone help me out to know if "Fail-Over Recovery" concept is avaliable in Hyperion Essbase 11.1.1.3.
If possible, please explain me how it ca be done.
Regards

Rajesh Kumar wrote:
Hi
I am working on data base fail over recovery mechanism. I am working on weblogic6.1Sp1 server installed on a unix machine. We are using J2EE architecture in our application. We have used Entity beans for dase base transactions.
My main objective is to allow my applictaion to switch over to secondry data base in case of failure of primary data base.
I have already developed a prototype which is working fine for a client application's request.But i can't use it for entity beans with container managed persistance.
So what i want to ask you is as follows:
Is there a way to switch between data bases for container managed entity beans.If yes then how to implement it?
Thank you
RajeshEasy. Define a multipool to tap a pool to the regular database first, and in cases when that DBMS is down,
tap a second pool to the fallback DBMS. Define a TxDataSource for the multipool, and have the beans
use that DataSource.
Joe

InfoPackage error message "Subsequent update (requests) : Status unknown "

After running an InfoPackage the status is set to green, but when you look at the Details tab you see an error message "Subsequent update (requests) : Status unknown " and "With DTP in InfoProvider ZHRPYO00 : Further processed " under it. We did not used to get this error message and don't quite understand why are we getting it now. Could someone explain, please?
Thanks!
Luda

Hi,
Usually this error could be while loading the DSO or loading DSO first and then to other infoprovider.
Error message tab at the monitor should give you clear error message where it went wrong. check this tab.
some time while activating the data this may fail for the DSO object. or some time due to authorization problem to load the data automatically from the DSO to infocubes.
If possible let me know what is error message.
Regards,
Vishwa.

Sun Identity Manger 8.0 and fail over..

We are setting up a fail/recovery site for our Sun Identity Manager solution, I had pictured a seem less fail over, but that looks near impossible to do with oracle database. I had pictured load balanced Appserver, with load balanced data bases, sort of a multi-master like LDAP allows..
Curious what others are using for a fail over site / setup.
Thanks

We're using 7.0. For us failover is basically mulitple servers all using the same DB repository, with a "smart" loadbalancer in front of them (smart meaning, able to detect which back end servers are responsive).
IdM doesn't use any inter-server temp-data synchronization, all the servers running off the same repository communicate by committing changes to the database.
So if a specific IdM instance dies, on the next page load the user will be redirected to a new server. That server will redirect to the login page and ask the user to re-auth, with the desired page placed after login.jsp as a "nextPage" argument. After (re-)logging in, the user's returned to the page they were trying to get to. However, in-progress edits that had not been committed back to the database will be lost.
We looked at high availability arrangements where valid sessions are shared across a new server, but fundamentally the limitation is that the app servers still don't sync in-progress edits, so the only difference between an HA environment and a more passive fail-over environment (like ours) is that in an HA environment the user doesn't have to re-login on a server failure; they still lose in-progress edits. So HA didn't seem like it added value to us.
If you are literally talking about an off-site, completely standby, seamless failover site, I agree I don't see how you would do that. I'd expect that you'd need the offsite setup to be a cold-standby site; configured to use the replicated database, but with the apps powered down until you actually need them. Otherwise, I think you'd have problems with the standby site servers not wanting to "standby". You could ensure no users end up on the standby servers, but background processes are likely to be run across both the primary and the standby services; I don't think you can enforce an "idle but running" status for the standby servers.
Edited by: etech on Feb 4, 2009 7:37 PM

Request status in Fail over

Similar Messages

Maybe you are looking for