| Author |
Message
|
| DaeMoohn |
 Posted: Tue Nov 16, 2010 6:47 am Post subject: What are the requirements for message listeners? |
 |
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
Hi,
We are using XMS 2.0.0.2 on client side with MQ client 7.0.1.3. On server side we 6.0.2.7. Until recently, on an "identically configured server" (MQ administration statement), we were receiving notifications on the client whenever a new message arrived in the queue. Now, we are not notified when messages are received on the queue. We still can access the queue to read already existing messages.
Is there any required configuration necesary on the server side to enable this functionality? I would like to help the admins to help us make this work in this environment too. We didn't change anything in our app so I consider this a server side issue.
Can you please offer me some hints or even documented arguments? (I don't have proper admin knowledge about MQ, only gained some through programming). |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Nov 16, 2010 7:35 am Post subject: Re: What are the requirements for message listeners? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| DaeMoohn wrote: |
| we were receiving notifications on the client whenever a new message arrived in the queue. |
How? Your application using Callback, your application being started on the arrivial of a new message, what?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 16, 2010 7:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Are the new messages committed? |
|
| Back to top |
|
|
| DaeMoohn |
| Posted: Tue Nov 16, 2010 7:38 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
Sorry if I wasn't clear. We are using what is standard called in ia9h.pdf "message listener". We have some components built upon these message listeners.
Basically, our apps, win services, read the existing messages from the queues, they process them, then they register those listeners.
Now, we don't receive any notification whenever a new message appears. I don't understand why, since MQ admins say the config is identical. |
|
| Back to top |
|
|
| DaeMoohn |
| Posted: Tue Nov 16, 2010 7:39 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
| mqjeff wrote: |
| Are the new messages committed? |
Well, I don't have access to the application that puts messages in the queue, we are only working with the application that reads messages from the queue. We are attempting transactional operations, so we commit the messages after we process them. |
|
| Back to top |
|
|
| shashikanth_in |
| Posted: Tue Nov 16, 2010 10:01 am Post subject: |
|
|
Centurion
Joined: 26 Feb 2009
Posts: 123
|
| DaeMoohn wrote: |
Sorry if I wasn't clear. We are using what is standard called in ia9h.pdf "message listener". We have some components built upon these message listeners.
Basically, our apps, win services, read the existing messages from the queues, they process them, then they register those listeners.
Now, we don't receive any notification whenever a new message appears. I don't understand why, since MQ admins say the config is identical. |
Message listeners are registered to receive messages asynchronously. It is not clear as to why your Windows service is reading messages first and then registering message listeners. Any reason?
Does it work if you connect again to "identically configured server"? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 16, 2010 8:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Define
| Quote: |
| XMS 2.0.0.2 on client side with MQ client 7.0.1.3. |
.
Does that mean you are using an XMS version you downloaded as support pack, or the XMS version packaged with the MQ client?
You need to use the XMS version packaged with the MQ Client. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| DaeMoohn |
| Posted: Wed Nov 17, 2010 12:07 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
The application that puts messages (that we read) can't be switched back to the old environment because of politics (they let us test the live environment only 2 weeks before live).
| shashikanth_in wrote: |
| DaeMoohn wrote: |
Sorry if I wasn't clear. We are using what is standard called in ia9h.pdf "message listener". We have some components built upon these message listeners.
Basically, our apps, win services, read the existing messages from the queues, they process them, then they register those listeners.
Now, we don't receive any notification whenever a new message appears. I don't understand why, since MQ admins say the config is identical. |
Message listeners are registered to receive messages asynchronously. It is not clear as to why your Windows service is reading messages first and then registering message listeners. Any reason?
Does it work if you connect again to "identically configured server"? |
The reason why I read the messages that exist in the queue is to allow those messages be processed if, for any reason, the service or the host machine where the service (or other cases too) fail. |
|
| Back to top |
|
|
| DaeMoohn |
| Posted: Wed Nov 17, 2010 12:23 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
| fjb_saper wrote: |
Define
| Quote: |
| XMS 2.0.0.2 on client side with MQ client 7.0.1.3. |
.
Does that mean you are using an XMS version you downloaded as support pack, or the XMS version packaged with the MQ client?
You need to use the XMS version packaged with the MQ Client. |
I think they installed a new client without reinstalling the client. |
|
| Back to top |
|
|
| DaeMoohn |
| Posted: Wed Nov 17, 2010 1:51 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
| DaeMoohn wrote: |
| fjb_saper wrote: |
Define
| Quote: |
| XMS 2.0.0.2 on client side with MQ client 7.0.1.3. |
.
Does that mean you are using an XMS version you downloaded as support pack, or the XMS version packaged with the MQ client?
You need to use the XMS version packaged with the MQ Client. |
I think they installed a new client without reinstalling the client. |
we reinstalled XMS because it wasn't properly installed there. Still we don't receive notifications. |
|
| Back to top |
|
|
| DaeMoohn |
| Posted: Wed Nov 17, 2010 6:45 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
| Now things started to work a bit, but, with wireshark, we see that at some point MQBACK and after several of those it cracks. What is with SYSTEM.JMS.REPORT.QUEUE? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 17, 2010 1:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| DaeMoohn wrote: |
I think they installed a new client without reinstalling the client.
we reinstalled XMS because it wasn't properly installed there. Still we don't receive notifications. |
With V7 XMS is part of the distribution. You should no longer be using the fix pack. Make sure also you're up to the latest level (7.0.1.3). You might still need an APAR for XMS at that level. If you hit a problem open a PMR.
_________________
MQ & Broker admin
Last edited by fjb_saper on Thu Nov 18, 2010 7:09 am; edited 1 time in total |
|
| Back to top |
|
|
| DaeMoohn |
| Posted: Thu Nov 18, 2010 5:58 am Post subject: |
|
|
Apprentice
Joined: 04 Jun 2010
Posts: 26
|
| We reverted to 7.0.1.2 client and XMS 2.0.0.2. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 18, 2010 6:09 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| DaeMoohn wrote: |
| We reverted to 7.0.1.2 client and XMS 2.0.0.2. |
| fjb_saper wrote: |
| With V7 XMS is part of the distribution. You should no longer be using the fix pack. |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 18, 2010 6:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The supportPac and the product are "the same release", at least at current levels... there have been previous posts from someone who appears to be on the XMS team that indicate this.
I don't think playing around with software levels in general is going to do a lot to resolve this particular issue. As a troubleshooting point, it is a usual reasonable approach to confirm that the issue still occurs at the current level.
Other general troubleshooting points are
- Compare the working and the non-working system at a very high level of detail
- Take MQ client level traces on both the working and non-working system and compare the results
- improve the amount of logging that the application does to provide a very fine grain of detail about steps taking and results given
- Open a PMR and work with IBM and XMS support.
|
|
| Back to top |
|
|
|
|
