| Author |
Message
|
| brgmo |
 Posted: Tue Jul 30, 2002 8:11 pm Post subject: message is not put on transmission queue |
 |
|
Master
Joined: 03 Jun 2002
Posts: 227
|
| Quote: |
Dear All
I have written a java program which is used for putting message on a remote queue. However the message reaches the transmission queue but after that it remains there only and is not passed further to remote queue. Ihave defined al necessary sender as well as reciever channels. i have put only output options to the queue. i am not getting any errors also in my error logs. please help me as it is very-very urgent.
thanks in advance
prabhat
|
[/url] |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Jul 30, 2002 8:36 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Sounds like the channel associated with the XMIT queue is not started. Either manually start it or set up triggering for the channel so that it starts automatically when a message lands on the XMIT queue.
Oh, and if the channel is started or triggered to start, and the message still sits there, make sure the app that put the message does a commit or disconnect if the message was done under syncpoint. Uncommitted messages put to remote queues wait in the XMIT queue till committed.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| brgmo |
| Posted: Tue Jul 30, 2002 8:49 pm Post subject: |
|
|
Master
Joined: 03 Jun 2002
Posts: 227
|
| no the channel is starting but it shows a status of retrying. can you guide me further peter as this is a very critical point for me bcz we have to deliver it today to our client. i am really in great tension. |
|
| Back to top |
|
|
| bduncan |
| Posted: Wed Jul 31, 2002 8:58 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
brgmo... There are hundreds of reasons why the channel is retrying. We'll need lot's more information before we can diagnose this. It sounds like either a network problem, or a queue manager misconfiguration, but definitely not a problem with your java application. Here's what I'd do:
1) use ping to make sure there is network connectivity between the two machines
2) use the PING CHANNEL command within runmqsc to see if you can get a better idea why the channel is retrying
3) check the MQSeries queue manager logs to see if it says why the channel isn't starting
4) run the channel manually using the runmqchl command. If you start this in the foreground, you'll be able to see a more verbose error message if it is unable to start
5) If the sender channel is configured for port 1414, make sure the destination machine has port 1414 available (not behind a firewall) and if a unix machine, the appropriate entry in /etc/services
6) confirm the channel listener is running on the destination queue manager. This is amqsbcg and is normally started in /etc/inetd.conf on unix, and as a service on windows
7) check the queue manager logs on the destination machine. See if the sender channel is actually making a connection and then failing. If you see no error entries in these logs, it probably means the sending side isn't even getting over here - which points to a network problem or misconfiguration on the sending side.
Do all this, and it should point to the problem. If it still isn't working, post the results of all these steps and we should be able to diagnose at that point.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| brgmo |
| Posted: Wed Jul 31, 2002 9:20 pm Post subject: |
|
|
Master
Joined: 03 Jun 2002
Posts: 227
|
thanks a lot brandon for giving such a good guidance. But both qmgrs lie in the same machine and on the same server. anyway i will try all the points given by you and get back to you.
prabhat. |
|
| Back to top |
|
|
| bduncan |
| Posted: Thu Aug 01, 2002 9:59 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
prabhat,
Your problem could definitely be stemming from the fact that you have both queue managers on the same physical machine. In these instances, the channel listeners for each queue manager must be listening on different ports, i.e., 1414 and 1415. If they are both on the same port, this would explain your problems..
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
|
|
