| Author |
Message
|
| jacobjonz |
 Posted: Wed Feb 18, 2009 4:56 am Post subject: Need help. Data not available in the reciever queue |
 |
|
Novice
Joined: 18 Feb 2009
Posts: 21
|
Hi all,
I am new to MQ. Please help me out.
I added the queue managers and added queues.
Added Cluster receiver and cluster sender channels.
shared the channels and queues iin a new cluster.
but i dont receive the data placed in the sender queue in the receiver queue.
i dot get any error |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Feb 18, 2009 5:16 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
where is that message now....?
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 18, 2009 5:18 am Post subject: Re: Need help. Data not available in the reciever queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jacobjonz wrote: |
| i dot get any error |
Not when you put the message, but I bet there's an error in a log somewhere!
Check that -
- you have 2 full repositories and all the cluster senders point to one or other of them
- all the cluster channels (sender and receiver) are running
- all the relevant objects are in the same cluster (i.e. spelt the same way and in the same case)
- there are no relevant messages in any of the queue manager logs
If this doesn't help, post more details of your topology and the version of WMQ you're using.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 18, 2009 5:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to correct section
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Feb 18, 2009 5:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There is no such thing as a "sender" queue or a "receiver" queue.
There are qlocals and qremotes and qclusters and qaliases and qmodels.
Messages put on qlocals do not get removed unless some application removes them.
Channels do not remove messages from any queue unless it has a usage of XMITQ and is associated with a channel.
Normal applications *NEVER* write to XMITQs.
Also look up CLWLUSEQ in the documentation. |
|
| Back to top |
|
|
| jacobjonz |
| Posted: Wed Feb 18, 2009 5:49 am Post subject: |
|
|
Novice
Joined: 18 Feb 2009
Posts: 21
|
That message is still available in the first queue.
I have two full repositories.
Both the cluster senders are pointing to the corresponding cluster receivers and are shared in the cluster.
I din understand what u meant by ' all the relevant objects are in the same cluster (i.e. spelt the same way and in the same case) '.
Everything is spelt correct.
now, i found in the log these error messages:
EXPLANATION:
An internal error has occurred with identifier FBF. This message is issued in
association with other messages.
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3412.
----- amqxfdcp.c : 818 --------------------------------------------------------
2/18/2009 14:14:33 - Process(3852.1) User(johnsonjacob_c) Program(endmqm.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20806070. This message is
issued in association with other messages.
ACTION:
----- amqxfdcp.c : 774 --------------------------------------------------------
2/18/2009 14:14:33 - Process(3852.1) User(johnsonjacob_c) Program(endmqm.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QM1.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3852.
----- amqxfdcp.c : 812 --------------------------------------------------------
2/18/2009 14:14:47 - Process(428.1) User(johnsonjacob_c) Program(strmqm.exe)
-------------------------------------------------------------------------------
2/18/2009 17:26:18 - Process(5288.1) User(johnsonjacob_c) Program(endmqm.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 20806070. This message is
issued in association with other messages.
----- amqxfdcp.c : 774 --------------------------------------------------------
2/18/2009 17:26:19 - Process(5288.1) User(johnsonjacob_c) Program(endmqm.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager QM2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 5288.
-------------------------------------------------------------------------------
2/18/2009 18:13:30 - Process(5184.2314) User(johnsonjacob_c) Program(javaw.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier FC5. This message is issued in
association with other messages.
----- amqxfdcp.c : 774 --------------------------------------------------------
2/18/2009 18:13:30 - Process(5184.2314) User(johnsonjacob_c) Program(javaw.exe)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 5184.
----- amqxfdcp.c : 818 --------------------------------------------------------
2/18/2009 18:28:24 - Process(3384.40) User(johnsonjacob_c) Program(javaw.exe)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier FC5. This message is issued in
association with other messages.
----- amqxfdcp.c : 774 --------------------------------------------------------
2/18/2009 18:28:24 - Process(3384.40) User(johnsonjacob_c) Program(javaw.exe)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 3384.
----- amqxfdcp.c : 818 -------------------------------------------------------- |
|
| Back to top |
|
|
| jacobjonz |
| Posted: Wed Feb 18, 2009 5:53 am Post subject: |
|
|
Novice
Joined: 18 Feb 2009
Posts: 21
|
| What i meant by sender and receiver queue was the queue to which i moved data and the queue from which i tried to read data [since they were both shared on a same cluster] |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Feb 18, 2009 5:56 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| mqjeff wrote: |
| Normal applications *NEVER* write to XMITQs. . |
I don't understand this.
If an application opens a remote queue definition then it does open in fact the underlying xmit queue for output (and this will show as an open count on the xmit queue).
All messages destined for another queue manager are written to xmit queues initially and this is done by the application.
The queue usage handles will show the application in question has the xmit queue open for output (and not some MQ system thread). |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 18, 2009 5:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| mqjeff wrote: |
| Normal applications *NEVER* write to XMITQs. . |
I don't understand this.
If an application opens a remote queue definition then it does open in fact the underlying xmit queue for output (and this will show as an open count on the xmit queue). |
I think the point here is that applications never write directly to the xmitq.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 18, 2009 6:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jacobjonz wrote: |
now, i found in the log these error messages:
|
You're not trying to run the WMQ processes under your own id are you?
You might also want to offer us a clue about WMQ version & OS.
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Wed Feb 18, 2009 6:02 am; edited 1 time in total |
|
| Back to top |
|
|
| jacobjonz |
| Posted: Wed Feb 18, 2009 6:01 am Post subject: |
|
|
Novice
Joined: 18 Feb 2009
Posts: 21
|
| Yeah, is there a problem with that? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 18, 2009 6:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jacobjonz wrote: |
| Yeah, is there a problem with that? |
Yes - it doesn't work.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jacobjonz |
| Posted: Wed Feb 18, 2009 6:04 am Post subject: |
|
|
Novice
Joined: 18 Feb 2009
Posts: 21
|
| is it ok if i give another id on the network which is not currently logged on from this machine? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 18, 2009 6:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jacobjonz wrote: |
| is it ok if i give another id on the network which is not currently logged on from this machine? |
No. WMQ must run as the mqm user. Check the installation guide for the OS you're using (which you've still not mentioned). From "network" I'll guess you're on Windows, in which case WMQ must run as a local user.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jacobjonz |
| Posted: Wed Feb 18, 2009 6:13 am Post subject: |
|
|
Novice
Joined: 18 Feb 2009
Posts: 21
|
yeah, i am on a windows network.
but, i have a doubt:
if it uses a local user, wont there be any issue while sending messages over the network? |
|
| Back to top |
|
|
|
|
