MQ gestionnaire de file d'attente canal fermé immédiatement lors de connecter

J'ai lu de nombreux articles selon mon problème, mais je stiil ont pas de solution.

Lorsque j'essaie de créer une connexion à WebSpereMQ-je obtenir

MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009

Après la lecture de différents articles que j'ai essayé de changer CCSID en faisant

MQEnvironment.properties.put(MQC.CCSID_PROPERTY, 1208); 
//also tried other CCSIDs like 1200,819,500

mais je n'ai eu aucun succès. Que j'ai lu qu'une bonne idée est de regarder MQ fichiers journaux pour savoir si il y a un autre processus qui interrompre la connexion. Mais je ne suis pas en mesure d'enquêter sur que les fichiers journaux depuis qu'ils sont codés et je ne sais pas comment les lire.

Questions:
1) savez-vous comment lire MQ journaux? Comment rendre lisible?
2) vous savez quoi d'autre pourrait causer ce genre de problème?

Journaux à partir d'un fichier AMQERR01.txt :

----- amqxfdcp.c : 773 --------------------------------------------------------
04.07.2013 10:41:01 - Process(2880.3) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6118: An internal WebSphere MQ error has occurred (20806211)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 735 --------------------------------------------------------
04.07.2013 10:41:01 - Process(2880.3) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager MMSG01Q2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2880.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 773 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6118: An internal WebSphere MQ error has occurred (20806211)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 735 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager MMSG01Q2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2880.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 773 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6118: An internal WebSphere MQ error has occurred (20806211)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 735 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager MMSG01Q2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2880.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 773 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6118: An internal WebSphere MQ error has occurred (20806211)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 735 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager MMSG01Q2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2880.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 773 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6118: An internal WebSphere MQ error has occurred (20806211)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 735 --------------------------------------------------------
04.07.2013 10:41:05 - Process(2880.1) User(Anton.Kasianchuk) Program(javaw.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager MMSG01Q2.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2880.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 773 --------------------------------------------------------
04.07.2013 10:45:41 - Process(3192.1) User(Anton.Kasianchuk) Program(crtmqm.exe)
AMQ6119: An internal WebSphere MQ error has occurred (Failed to create mapped
memory segment: [rc=536895769 errorCode=5])
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 735 --------------------------------------------------------
04.07.2013 10:45:41 - Process(3192.1) User(Anton.Kasianchuk) Program(crtmqm.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 3192.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center.  Do not discard these files until the problem has been resolved. 
----- amqxfdcp.c : 779 --

journaux à partir d'un fichier amqtsivt.txt

10:45:39 IVT Started
10:45:41 Setup IVT Environment...
10:45:41 Creating Queue Manager...
10:45:42 Starting Queue Manager...
10:45:42 Ready.
10:45:42 Connect to QueueManager(1), CC:2 - RC:2058
10:45:42 Connect to QueueManager(2), CC:2 - RC:2058
10:45:42 Open queue, CC:2 - RC:2018
10:45:42 Put Message, CC:2 - RC:2018
10:45:42 Message Put: AMQMTSIVT
10:45:42 Get Message, CC:2 - RC:2018
10:45:42 Message Returned: 
10:45:42 Close queue, CC:2 - RC:2018
10:45:42 Started thread 01
10:45:42 MQOpen in Child Thread, CC:2 - RC:2018
10:45:42 MQPut in Child Thread, CC:2 - RC:2018
10:45:42 MQGet in Child Thread, CC:2 - RC:2018
10:45:42 MQClose in Child Thread, CC:2 - RC:2018
10:45:42 Child Thread finished 43 cycles
10:45:43 Started thread 02
10:45:43 MQOpen in Child Thread, CC:2 - RC:2018
10:45:43 MQPut in Child Thread, CC:2 - RC:2018
10:45:43 MQGet in Child Thread, CC:2 - RC:2018
10:45:43 MQClose in Child Thread, CC:2 - RC:2018
10:45:43 Child Thread finished 46 cycles
10:45:44 Started thread 03
10:45:44 MQOpen in Child Thread, CC:2 - RC:2018
10:45:44 MQPut in Child Thread, CC:2 - RC:2018
10:45:44 MQGet in Child Thread, CC:2 - RC:2018
10:45:44 MQClose in Child Thread, CC:2 - RC:2018
10:45:44 Child Thread finished 49 cycles
10:45:45 Started thread 04
10:45:45 MQOpen in Child Thread, CC:2 - RC:2018
10:45:45 MQPut in Child Thread, CC:2 - RC:2018
10:45:45 MQGet in Child Thread, CC:2 - RC:2018
10:45:45 MQClose in Child Thread, CC:2 - RC:2018
10:45:45 Child Thread finished 3 cycles
10:45:45 Started thread 05
10:45:45 MQOpen in Child Thread, CC:2 - RC:2018
10:45:45 MQPut in Child Thread, CC:2 - RC:2018
10:45:45 MQGet in Child Thread, CC:2 - RC:2018
10:45:45 MQClose in Child Thread, CC:2 - RC:2018
10:45:45 Child Thread finished 3 cycles
10:45:45 Started thread 06
10:45:45 MQOpen in Child Thread, CC:2 - RC:2018
10:45:45 MQPut in Child Thread, CC:2 - RC:2018
10:45:45 MQGet in Child Thread, CC:2 - RC:2018
10:45:45 MQClose in Child Thread, CC:2 - RC:2018
10:45:45 Child Thread finished 3 cycles
10:45:45 Started thread 07
10:45:45 MQOpen in Child Thread, CC:2 - RC:2018
10:45:45 MQPut in Child Thread, CC:2 - RC:2018
10:45:45 MQGet in Child Thread, CC:2 - RC:2018
10:45:45 MQClose in Child Thread, CC:2 - RC:2018
10:45:45 Child Thread finished 3 cycles
10:45:45 Started thread 08
10:45:45 MQOpen in Child Thread, CC:2 - RC:2018
10:45:45 MQPut in Child Thread, CC:2 - RC:2018
10:45:45 MQGet in Child Thread, CC:2 - RC:2018
10:45:45 MQClose in Child Thread, CC:2 - RC:2018
10:45:45 Child Thread finished 3 cycles
10:45:46 Started thread 09
10:45:46 MQOpen in Child Thread, CC:2 - RC:2018
10:45:46 MQPut in Child Thread, CC:2 - RC:2018
10:45:46 MQGet in Child Thread, CC:2 - RC:2018
10:45:46 MQClose in Child Thread, CC:2 - RC:2018
10:45:46 Child Thread finished 6 cycles
10:45:47 User cancelled action
10:45:47 Started thread 10
10:45:47 MQOpen in Child Thread, CC:2 - RC:2018
10:45:47 MQPut in Child Thread, CC:2 - RC:2018
10:45:47 MQGet in Child Thread, CC:2 - RC:2018
10:45:47 MQClose in Child Thread, CC:2 - RC:2018
10:45:47 Child Thread finished 9 cycles
10:45:48 Error(s) encountered during thread execution
10:45:48 All threads terminated
10:45:48 Disconnect from QueueManager (1), CC:2 - RC:2018
10:45:48 Disconnect from QueueManager (2), CC:2 - RC:2018
10:45:48 Ready.
10:45:49 Cleaning Up...
10:45:49 Deleting MTS Package
10:45:49 Access MTS Admin Catalog, OK
10:45:52 Get MTS Packages, OK
10:45:52 Ending Queue Manager...
10:45:52 Deleting Queue Manager...
10:45:53 Ready.

journaux à partir de \Qmgrs\MMSG01Q2\errors\AMQERR01.txt

----- amqrmrsa.c : 468 --------------------------------------------------------
05.07.2013 09:41:10 - Process(6004.21) User(j2mquser) Program(amqrmppa.exe)
AMQ9502: Type of channel not suitable for action requested.
EXPLANATION:
The operation requested cannot be performed on channel 'CLOUD.MMSG01Q2.S1'.
Some operations are only valid for certain channel types. For example, you can
only ping a channel from the end sending the message.
ACTION:
Check whether the channel name is specified correctly.  If it is check that the
channel has been defined correctly. 
----- amqrmsaa.c : 1072 -------------------------------------------------------
05.07.2013 09:41:10 - Process(6004.21) User(j2mquser) Program(amqrmppa.exe)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'CLOUD.MMSG01Q2.S1' ended abnormally.
ACTION:
Look at previous error messages for channel program 'CLOUD.MMSG01Q2.S1' in the
error files to determine the cause of the failure. 
----- amqrmrsa.c : 468 --------------------------------------------------------

InformationsquelleAutor Anton Kasianchuk | 2013-07-03

ibm-mq java

1

Journaux qui faites-vous allusion? MQ journaux d'Erreurs ne sont pas en binaire. Vous pouvez les trouver sous (sur Windows) WebSphere MQ dossier d'installation. Les journaux d'erreur spécifiques au gestionnaire de file d'attente sera sous \Qmgrs\"qmgr"\ dossier. Veuillez regarder ces journaux d'erreurs, ils peuvent avoir de l'information au sujet de votre problème.

Vérifier si le port que vous utilisez dans l'application est un gestionnaire de file d'attente est à l'écoute sur. Avez-vous des SSL activé sur le gestionnaire de file d'attente du port et de votre application n'utilise pas SSL?
- Vous aviez raison au sujet de journaux. Maintenant, j'ai ajouté les journaux d'erreur à ma question. Mais comme pour moi, ils n'ont pas beaucoup d'information. Pouvez-vous regarder? Vous parliez de ce genre de journaux, de droite?
- Et oui, le port que j'utilise dans mon application est le même que celui du gestionnaire de file d'attente.
- Peut-être que le problème est dans l'OS, j'ai utilisé? Nous avons deux machines (Windows7 et WindowsXP) avec le même logiciel en et nous utilisons le même logiciel de configuration. Mais quand il fonctionne très bien sur XP, c'est un échec sur Windows 7.
- MQRC 2058 signifie que le gestionnaire de file d'attente nom fourni n'est pas valide. MQRC 2018 signifie MQRC_HCONN_ERROR est suivi d'erreur parce que le précédent appel pour créer une connexion a échoué avec 2058.
- MQRC 2058 signifie que le gestionnaire de file d'attente nom fourni n'est pas valide. MQRC 2018 signifie MQRC_HCONN_ERROR est suivi d'erreur parce que le précédent appel pour créer une connexion a échoué avec 2058. Est MMSG01Q2 le gestionnaire de file d'attente, vous essayez de vous connecter? Avez-vous précisé le gestionnaire de file d'attente le nom correct de l'affaire?
- Je peux vous assurer que je suis en train d'essayer de se connecter à MMSG01Q2 et d'ailleurs il est commencé très bien. Encore une chose: je me suis trompé sur le fonctionnement des systèmes de question - on ne peut pas créer de connexion ni dans WindowsXP, ni dans Windows7.
- Il semble que certaines informations utiles sont dans le \Qmgrs\MMSG01Q2\errors\AMQERR01.txt. On dirait que je suis le mauvais type de canal. (Cette des journaux ont été ajoutés à ma question)
InformationsquelleAutor Shashi
1

- Je l'utiliser pour le client de connexion en mode
MQEnvironment.les propriétés.mettre(MQConstants.TRANSPORT_PROPERTY, MQConstants.TRANSPORT_MQSERIES);

InformationsquelleAutor JakesIV
0

Pour résoudre ce problème, j'ai ajouté le code suivant:
```
MQEnvironment.properties.put(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES_BINDINGS);
```
- Bonne trouvaille. Ce code permet à votre application pour utiliser la mémoire partagée pour communiquer avec le gestionnaire de file d'attente. Cela fonctionne tant que l'application et le gestionnaire de file d'attente sont de la même machine. Pour l'application à se connecter via le canal, le canal doit être de SVRCONN (Serveur de connexion) de type. Veuillez donc vérifier si le canal que vous utilisez est de SVRCONN type.
InformationsquelleAutor Anton Kasianchuk

Vous devez vous connecter pour publier un commentaire.