Hello All,
Can some one help me in understanding around this issue?
Issue: We have stubbed one MQ service but during testing , testing team found that they are getting responses or traffic from Lisa even after MQ service is down in Lisa server.
I am not able to understand is it Lisa issue or some thing else. Quick reply is much appreciated.
Thanks..
Shivam Garg
I know of no reason why this would happen. Since your Think Time is 0, responses should go immediately. That should rule out a response message staying on an internal DevTest response queue after the service is stopped.
This is likely a support ticket question at this point; however, the DevTest version your team is running is out of support now.
Try diagnosing this way:
1) Stop the service
2) Ask an MQ Admin if they see a DevTest connection on the queue manager (how many connections do they see)
3) Start the service
4) Ask an MQ Admin if they see a DevTest connection on the Queue Manager (how many connections do they see)
5) Stop the service
6) Ask the MQ Admin if they see a DevTest connection on the Queue Manager (may take a few seconds) (how many connections do they see)
Ideally, the connections should go from 0 and back down to 0. If other connections are open, I would try to find what they might be. If no connections, I don't see how DevTest could be sending data after the service is stopped since no connection exists.
If you can get a server Admin to provide you with a copy of the log files it might be helpful.
The concept of assets was introduced circa DevTest 7.5. When I asked the question of Scope, I was referring to the Connection Assets that sit underneath Project Config. I presume you are not using these in your instance. If you are using these assets to manage the connection and queues, you will see information that looks something like this. If you are using the assets, review and set the Scope to "Model", redeploy, and try the test shutdown again to see if you get a different result.