Solution for sender channel status retrying
Scenario 1: My window machine installed with IBM WebSphere MQ 7.5 version and z/OS machine installed with IBM WebSphere MQ 7.0. I have one remote queue on my window
machine which sends messages to z/OS machines local Queue. I am able to send messages from my remote queue to z/OS local queue using sender channel, Receiver Channel and Transmission Queue. Some network interruption happened on my window machine and lost connection with Z/OS machine. At the time of network interruption, my sender channel and Z/OS receiver channel was running. when connection restored with these two machine my sender channel status becomes "Retrying" and receiver channel status still showing running. When I looked on error log AMQERR01.LOG for sender channel, this look like below.
I tried with lots of option like stop and start Sender Queue Manager, Sender channel, checked MAX instance defined on both machine but nothing worked. I also applied fix pack of 7.5.0.5 on MQ7.5 by reading below article. IT02422: WMQ V7.5 JAVA APPLICATION FAILS WITH REASON CODE 2025 (MQRC_MAX_CONNS_LIMIT_REACHED) AFTER NETWORK OUTAGES(http://www-01.ibm.com/support/docview.wss?doc=aimwmq&rs=171&uid=swg21110505) but this also not worked.
Solution: Finally I got one solution. forcefully stopped sender channel and receiver channel(STOP CHL(rcvr chl name) MODE(FORCE)), both channel status should be STOPPED now. start receiver channel.Stop and start Queue manager of sender channel. Than, finally start sender channel. In my case this worked :)
Scenario 2: I configured my remote Queue and local Queue on window machine. Through java application, I am trying to put messages on remote Queue and try to get those messages on my local queue, but my messages got stuck on transmission Queue and sender channel goes into Retrying state.
Note: Earlier my sender channel connected with other system's IP and able to send and receive messages, when I changed IP with my local system than messages got stuck in transmission queue and sender channel goes into Retrying state.
Solution: I found one temporary solution. Deleted old transmission Queue and created new one and given reference to sender channel and Remote queue.
In above 2 scenario, difference in 1st scenario is, sender channel goes in retrying state when one system lost connection with other system where as in 2nd scenario, changed IP address in sender channel.
Related Topic:
Scenario 2: I configured my remote Queue and local Queue on window machine. Through java application, I am trying to put messages on remote Queue and try to get those messages on my local queue, but my messages got stuck on transmission Queue and sender channel goes into Retrying state.
Note: Earlier my sender channel connected with other system's IP and able to send and receive messages, when I changed IP with my local system than messages got stuck in transmission queue and sender channel goes into Retrying state.
Solution: I found one temporary solution. Deleted old transmission Queue and created new one and given reference to sender channel and Remote queue.
In above 2 scenario, difference in 1st scenario is, sender channel goes in retrying state when one system lost connection with other system where as in 2nd scenario, changed IP address in sender channel.
Related Topic:
