|
| > Hi, I think you are confused on how synchronization
> works. The Deployment Manager synchronizes with the
> node agents. Please see:
> http://www-1.ibm.com/support/docview.wss?uid=swg211084
> 07
>
> You can force a synchronization with the nodes from
> the console or using wsadmin.sh, as long as the nodes
> are managed. Please see the following for the
> wsadmin commands:
> http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rx
> mx/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/a
> e/txml_sync.html
>
> The Application Servers are ready to process requests
> as soon as startup is completed.
>
> Brian
Thank you for your reply! My question is based on the following background.
When a cluster member,say A, is suspended, other cluster members are busy withing handling the requests. So the state kept in A can be significantly different with the state of other cluster members. So when A is resumed, requests that belong to some sess
ion can be routed to A if the session owner cluster member fails. In this case, can A still handle the requests correctly?
Can A get the session information itself from the session backup cluster member(when using peer-to-peer)? If not, A would start a new session for the request,which would cause errors.
|
|