Hi we have the following set up.
MQ Work flow server is running on an AIX system. We have configured a work flow client on a Win2K system which uses queue manager to connect to the work flow server. The work flow server is running on the queue manager FMCQM and the Work flow client is configured on a queue manager FMCWAS1. FMCQM is the repository manager for the cluster FMCGRP and FMCWAS1 is also a part of the cluster.
Connectivity is tested and normally we are able to connect to the workflow server using this client. But if the client is disconnected for a long time, and we try to connect again, SOMETIMES it gives fmc time out error. What I observed is that at this moment both the cluster sender and receiver channels on the client(FMCWAS1) queue manager had become inactive. But as soon as we start the WF client the sender channel becomes active immediately. But the receiver channel does not become active for a long time and the WF client gives time out error.
But if we refresh the cluster by this command
refresh cluster(fmcgrp)
then this receiver channel becomes active and the client connects now.
I assume that the channels becoming inactive is quite normal after the disconnect interval has passed, but they are expected to become active as soon as a message arrives.
Also is there any setting where we can alter the time out period before which the Work Flow client gives the time out error?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum