MQSeries connection error

[Steve Carter]

Our MQ Admins recently made some changes to the security settings within MQ.  Before these changes, the MQ threads would connect in a matter of seconds.  After the changes, the connection reports the following error every 60 seconds for up to 8 or 9 minutes:

$ more mqMsgDist0.err

[mqs :init:ERR /0:     mqStatus:04/26/2009 13:39:23] No reply msg, make sure command server is started (strmqcsv qmgr-name)

[mqs :init:ERR /0:     mqStatus:04/26/2009 13:40:23] No reply msg, make sure command server is started (strmqcsv qmgr-name)

[mqs :init:ERR /0:     mqStatus:04/26/2009 13:41:23] No reply msg, make sure command server is started (strmqcsv qmgr-name)

[mqs :init:ERR /0:     mqStatus:04/26/2009 13:42:23] No reply msg, make sure command server is started (strmqcsv qmgr-name)

[mqs :init:ERR /0:     mqStatus:04/26/2009 13:43:23] No reply msg, make sure command server is started (strmqcsv qmgr-name)

[mqs :init:ERR /0:     mqStatus:04/26/2009 13:44:23] No reply msg, make sure command server is started (strmqcsv qmgr-name)

[mqs :init:ERR /0:     mqStatus:04/26/2009 13:45:23] No reply msg, make sure command server is started (strmqcsv qmgr-name)

I’m waiting to hear back from the MQ Admin as to what was changed.  It appears that Cloverleaf is expecting some kind of reply message that it never receives.  After a period of time, it seems to give up on the reply message and simply connects.  However, it blocks all other threads in the process from starting until the MQ connection(s) are established.

Has anyone seen this type of error before or know specifically what Cloverleaf is expecting?

I’ve already contacted Healthvision support for their input.

Thanks.

Steve

Topic