CODEWITHSUNDEEP
ibm-mqxms
Bilgehan
Bilgehan

Reputation: 1227

IBM XMS.Net Listener Hangs Out when connection is closed forbiddenly

Hi I use webpshere mq client 8.0.0.8 and I set my listener at once and start to listen mq,but something went wrong and and myconnection is closed but it throws no error and mylistener hang out and cant listen message.If its throws error I have a mechanism to catch and restart it but that time I failed.Is there any property set to avoid this issue?

I have exceptionlistener and reconnect options in my connectionproperties.But this is not directly work,I have a autoresetevent (receiveCompleteEvent)mechanism,only solution I can find set signal in exceptionlistener,and kill connection.In exception listener I can log connection error notifications but no automatic connection set,

 connectionfactory.SetIntProperty(IBM.XMS.XMSC.WMQ_CLIENT_RECONNECT_OPTIONS, IBM.XMS.XMSC.WMQ_CLIENT_RECONNECT);
            connectionfactory.SetIntProperty(IBM.XMS.XMSC.WMQ_CLIENT_RECONNECT_TIMEOUT, 150);

private void OnException(Exception ex)
        {
            QueueStatuslog.Error(String.Format("Unexpected error occured to connection:{0}", ex.ToString()));
            try
            {
                if (receiveCompleteEvent != null)
                {
                    QueueStatuslog.Error(String.Format("Due to connection error send stop signal:{0}", ex.ToString()));
                    receiveCompleteEvent.Set();
                }

Upvotes: 2

Views: 663

Answers (1)

Shashi
Shashi

Reputation: 15263

Exception, like connection related, will be thrown to application when application makes synchronous MQ API call, like consumer.receive or producer.send. If you are using message listener to receive messages, the message delivery is an asynchronous operation and messages are delivered on the message listener thread. So XMS can not throw exceptions on that thread. Hence it requires another thread, i.e. ExceptionListener to let the application know about any connection related issues.

You will need to setup ExceptionListener on connection and catch any exception thrown. When an exception is thrown, issue Connection.Stop, clean up and reinitialize message receive.

You can also look at using automatic client reconnection and this.

Upvotes: 2

Related Questions