| Author |
Message
|
| svla |
 Posted: Thu Jan 12, 2006 7:35 am Post subject: problem with receiver chanell |
 |
|
Novice
Joined: 12 Jan 2006
Posts: 10
Location: Italy
|
Hello!
I'm working on a virtual machine (Windows 2003 server) and I'd installed WebSphere MQ v5.3 (CSD 10). I comunicate with a Linux Red Hat throw MQ via TCP. I've created a QM for the transmission with the follows objects:
- 1 Local Queue for receiving
- 1 Trasmission Queue and 1 Remote Queue Definition for sending
- 1 Sender Chanell
- 1 Receiver Chanell
- 1 Listner on 1414 port via TCP
In the past the comunication with the other QM goes on the right way; but now I've restarted the Windows2003 server machine and deleted the QM. When I've re-created the QM, I meet this problem: the receiver chanell is inactive and the errors on logs are:
- AMQ9202 (..\Program Files\IBM\WebSphere MQ\Errors) with TCP return code 10061
- AMQ9001 and AMQ9002 (..\Program Files\IBM\WebSphere MQ\Qmgrs\HIT0\errors)
I can not do anything on the receiver layer cause it's a closed system.
Could anyone help me? By. |
|
| Back to top |
|
 |
| mvic |
| Posted: Thu Jan 12, 2006 7:56 am Post subject: Re: problem with receiver chanell |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| svla wrote: |
- AMQ9202 (..\Program Files\IBM\WebSphere MQ\Errors) with TCP return code 10061
- AMQ9001 and AMQ9002 (..\Program Files\IBM\WebSphere MQ\Qmgrs\HIT0\errors) |
An error lookup for 10061 gives "No connection could be made because the target machine actively refused it."
Is there a firewall between the two? Have you started the listener on the receiving machine? |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Jan 12, 2006 8:20 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Can you look at the amqerr01 log on the receiver machine? If not you, can someone else?
_________________
-wayne |
|
| Back to top |
|
|
| svla |
| Posted: Thu Jan 12, 2006 8:21 am Post subject: |
|
|
Novice
Joined: 12 Jan 2006
Posts: 10
Location: Italy
|
| There is no firewall on 1414 and the listner is started on that port. |
|
| Back to top |
|
|
| svla |
| Posted: Thu Jan 12, 2006 8:29 am Post subject: |
|
|
Novice
Joined: 12 Jan 2006
Posts: 10
Location: Italy
|
| In the amqerr01 log (receiver machine) there is an error for the default QM: AMQ7880 with error code 20. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Jan 12, 2006 8:35 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| svla wrote: |
| In the amqerr01 log (receiver machine) there is an error for the default QM: AMQ7880 with error code 20. |
Is it possible to paste the whole error message into the forum please? |
|
| Back to top |
|
|
| svla |
| Posted: Thu Jan 12, 2006 8:55 am Post subject: |
|
|
Novice
Joined: 12 Jan 2006
Posts: 10
Location: Italy
|
11/01/2006 15:08:56
AMQ7880: Codice di errore 20 durante l'avvio del servizio
QM_rfiwapeor02tst/Command Server WebSphere MQ.
SPIEGAZIONE:
Il servizio non è riuscito ad avviare QM_rfiwapeor02tst/Command Server. Il
messaggio di errore notificato era il seguente: Process could not be started -
return code 20
AZIONE:
Utilizzare i servizi di WebSphere MQ per individuare i motivi che hanno
impedito l'avvio del servizio. Se il recupero per questo servizio è attivo, MQ
tenterà di eseguirlo.
If you don't understand italian language the english message translate by me is:
AMQ7880: error code 20 during the start of QM_rfiwapeor02tst/Command Server WebSphere MQ service.
PROBLEM DESCRIPTION:
The service was not able to start QM_rfiwapeor02tst/Command Server.
The error message notified was: Process could not be started -
return code 20
SOLUTION:
Use WebSphere MQ services to find the reason of non starting service. If the recovery of this service is active, MQ try to do it. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Jan 12, 2006 9:09 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
Thanks, OK the command server is having a problem starting, which is bad, and may make life difficult in other ways. But I can't think of how this could be related to a TCP/IP error from the channels.
You said port 1414 was open in the firewall. I suggest trying to connect to 1414 on the target machine using telnet, to check whether there really is connectivity. If there is, your telnet session should get connected, and perhaps you can send some data (tap some keys on the keyboard) but the connection to the target machine will get closed by MQ and you will probably get an error log entry and/or an FDC on the target machine.
If this pattern is not observed, please report on what exactly you do see. |
|
| Back to top |
|
|
|
|
