java - MQ queue manager closed channel immediately during connect -

i have read many articles according issue, stiil have no solution.

when try create connection websperemq

mqje001: mqexception occurred: completion code 2, reason 2009 mqje016: mq queue manager closed channel during connect closure reason = 2009 

after reading different articles tried change ccsid doing

mqenvironment.properties.put(mqc.ccsid_property, 1208);  // tried other ccsids 1200,819,500 

but had no success. read idea @ mq log files find out if there process wich interrupt connection. not able investigate log files since encoded , don't how read them.

questions: 1) know how read mq logs? how make them readable? 2) know else cause kind of problem?

logs file amqerr01.txt :

----- amqxfdcp.c : 773 -------------------------------------------------------- 04.07.2013 10:41:01 - process(2880.3) user(anton.kasianchuk) program(javaw.exe) amq6118: internal websphere mq error has occurred (20806211)  explanation: error has been detected, , mq error recording routine has been called. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 735 -------------------------------------------------------- 04.07.2013 10:41:01 - process(2880.3) user(anton.kasianchuk) program(javaw.exe) amq6184: internal websphere mq error has occurred on queue manager mmsg01q2.  explanation: error has been detected, , websphere mq error recording routine has been called. failing process process 2880. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 773 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6118: internal websphere mq error has occurred (20806211)  explanation: error has been detected, , mq error recording routine has been called. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 735 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6184: internal websphere mq error has occurred on queue manager mmsg01q2.  explanation: error has been detected, , websphere mq error recording routine has been called. failing process process 2880. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 773 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6118: internal websphere mq error has occurred (20806211)  explanation: error has been detected, , mq error recording routine has been called. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 735 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6184: internal websphere mq error has occurred on queue manager mmsg01q2.  explanation: error has been detected, , websphere mq error recording routine has been called. failing process process 2880. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 773 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6118: internal websphere mq error has occurred (20806211)  explanation: error has been detected, , mq error recording routine has been called. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 735 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6184: internal websphere mq error has occurred on queue manager mmsg01q2.  explanation: error has been detected, , websphere mq error recording routine has been called. failing process process 2880. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 773 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6118: internal websphere mq error has occurred (20806211)  explanation: error has been detected, , mq error recording routine has been called. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 735 -------------------------------------------------------- 04.07.2013 10:41:05 - process(2880.1) user(anton.kasianchuk) program(javaw.exe) amq6184: internal websphere mq error has occurred on queue manager mmsg01q2.  explanation: error has been detected, , websphere mq error recording routine has been called. failing process process 2880. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 773 -------------------------------------------------------- 04.07.2013 10:45:41 - process(3192.1) user(anton.kasianchuk) program(crtmqm.exe) amq6119: internal websphere mq error has occurred (failed create mapped memory segment: [rc=536895769 errorcode=5])  explanation: mq detected unexpected error when calling operating system. mq error recording routine has been called. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 735 -------------------------------------------------------- 04.07.2013 10:45:41 - process(3192.1) user(anton.kasianchuk) program(crtmqm.exe) amq6183: internal websphere mq error has occurred.  explanation: error has been detected, , websphere mq error recording routine has been called. failing process process 3192. action: use standard facilities supplied system record problem identifier, , save generated output files. contact ibm support center.  not discard these files until problem has been resolved.  ----- amqxfdcp.c : 779 -- 

logs file 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 queuemanager(1), cc:2 - rc:2058  10:45:42 connect 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 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 threads terminated  10:45:48 disconnect queuemanager (1), cc:2 - rc:2018  10:45:48 disconnect 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 mts packages, ok  10:45:52 ending queue manager...  10:45:52 deleting queue manager...  10:45:53 ready. 

logs \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 action requested.  explanation: operation requested cannot performed on channel 'cloud.mmsg01q2.s1'. operations valid channel types. example, can ping channel end sending message. action: check whether channel name specified correctly.  if check 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: @ previous error messages channel program 'cloud.mmsg01q2.s1' in error files determine cause of failure.  ----- amqrmrsa.c : 468 -------------------------------------------------------- 

what logs referring to? mq error logs not in binary. can find them under (on windows) websphere mq installation folder. error logs specific queue manager under \qmgrs\"qmgr"\ folder. please @ these error logs, may have information regarding problem.

check if port using in application 1 queue manager listening on. have ssl enabled on queue manager port , application not use ssl?