Hi,
I have a WAS 3.5.6 clustered architecture. Two HTTP Servers (A & B) have remote OSE connections to two WAS servers (C & D) . Everything works fine when both the WAS servers are up. But, we recently found that if a request is made after shutting down one of the WAS servers (say, D), the request takes a long long time .. home page doesn't come up .. IE just keeps on doing slow processing .. possibly, it might time out later.
Then I found out on the IBM site a fix (PQ60039) for including a timeout directive in bootstrap.properties. This will enable a timeout eventually getting a failover response from the remote shutdown server (server D) .
If this fix works, I will get a page not found or some other response in the timeout period specified. Thats fine. But, my issue is its not clear with this fix or any other related document, whether this request or the subsequent requests will then be routed to WAS server C ( which is up and running).
Can anyone please help by answering this ASAP.
Thanks in advance.
Regards,
anuptosh
I have a WAS 3.5.6 clustered architecture. Two HTTP Servers (A & B) have remote OSE connections to two WAS servers (C & D) . Everything works fine when both the WAS servers are up. But, we recently found that if a request is made after shutting down one of the WAS servers (say, D), the request takes a long long time .. home page doesn't come up .. IE just keeps on doing slow processing .. possibly, it might time out later.
Then I found out on the IBM site a fix (PQ60039) for including a timeout directive in bootstrap.properties. This will enable a timeout eventually getting a failover response from the remote shutdown server (server D) .
If this fix works, I will get a page not found or some other response in the timeout period specified. Thats fine. But, my issue is its not clear with this fix or any other related document, whether this request or the subsequent requests will then be routed to WAS server C ( which is up and running).
Can anyone please help by answering this ASAP.
Thanks in advance.
Regards,
anuptosh