Mqseries Error Codes 2195
Contents |
Java testing Databases Java development in cloud Java DevOps Modular code EJB specification Modular containers Modular troubleshooting Programming code http://www.theserverside.com/discussions/thread.tss?thread_id=10438 App servers Modular tools Java in the cloud Java Web services WS* specs Architecture Java middleware Spring Hibernate Servlets JSP Java client platforms Framework JSF Web https://www.mail-archive.com/mqseries@akh-wien.ac.at/msg12298.html portals UI Enterprise Java development JSRs and APIs Languages JVM languages DSLs Java app deployment Java tools Java performance Java performance Cloud platforms JVM tuning code 2 Java HPC Web dev tools Development tools Open source strategy IDEs Java platforms Java testing Development hardware Mobile app dev Mobile development and deployment Mobile cloud apps Mobile platforms Mobile ALM Mobile app testing SEARCH this site and the web Site Index Home>Discussions>TSS feedback>Urgent: A error in MQSeries "Queue Manager not reason 2195 mqrc support CCSID" Email This Discussions TSS feedback: Urgent: A error in MQSeries "Queue Manager not support CCSID" Get thread feed Urgent: A error in MQSeries "Queue Manager not support CCSID" (1 messages) Posted by: Liu Haoyang Posted on: November 27 2001 01:24 EST Hi,guys When I run MQSeries Demo Applet the java console report a error like this: init complete starting............ New Qmanager.......... MQJE020: 队列管理器不支持 CCSID(Queue Manager not support CCSID) MQJE001: 完成码 2,原因 2195 An MQ error occurred : Completion code 2 Reason code 2195 End of start!!!!!!! the source code is: qMgr = new MQQueueManager(qManager); Any help is appreciate! Reply to this Threaded Messages (1) Urgent: A error in MQSeries "Queue Manager not support CCSID" by David Hanna on December 06 2001 01:28 EST Urgent: A error in MQSeries "Queue Manager not support CCSID"[ Go to top ] Posted by: David Hanna Posted on: December 06 2001 01:28 EST in r
I'll tell you how to find out. On a distributed platform, you should be able to type... mqrc 2195 ...on the command line and it will return the description for the reason code. Failing that, you can always pull up the WMQ Messages manual at... http://publibfp.boulder.ibm.com/epubs/html/amqzao04/amqzao04tfrm.htm ...and look in "Chapter 8. API completion and reason codes". Now you should be able to find out just about any reason or completion code that WMQ can throw at you! By the way, 2195 means "Unexpected Error". These usually cut an FDC record which has additional info. -- T.Rob -----Original Message----- From: Meital Geron-Issers [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 8:06 AM To: [EMAIL PROTECTED] Subject: Re: failed to connect queue manager Hello, Sorry, but I've just noticed the link exception which is MQJE001: Completion Code 2, Reason 2195. Do you know what does it mean? Thanks Meital -----Original Message----- From: Arvind Chaudhary [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2003 10:02 AM To: [EMAIL PROTECTED] Subject: Re: failed to connect queue manager Meital, there would be a linked exception to the JMS exception that you are getting which would give the real (MQSeries) reason why the MQClient could not connect to server. It will give more information, if you could print the linked exception or the complete exception stack. -Arvind. Meital Geron-Issers <[EMAIL PROTECTED] To: [EMAIL PROTECTED] LLPAY.BIZ> cc: (bcc: arvind.chaudhary/Polaris) Sent by: MQSeries List Subject: Re: failed to conncet queue manager <[EMAIL PROTECTED] T> 12/01/03 01:11 PM Please respond to MQSeries List Thanks. I will check those issues. The exception I got was : javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for Regards Meital -----Original Message----- From: Carroll, Y. (Yvette) [mailto:[EMAIL PROTECTED] Sent: Monday, December 01, 2003 9:22 AM To: [EMAIL PROTECTED] Subject: Re: failed to conncet queue manager I'm not even sure what the JMS is, but I found this in the manuals: MQJMS2005 Failed to create MQQueueManager for {0}. Explanation: JMS could not connect to a queue manager. {0} gives the name of the queue manager. User Response: Use the linked exception to determine the cause of this error. Check the queue manager is running and, if using client attach, that the listener is running and the channel, port and hostname are set correctly. If no queue manager name has been specified, check that the default queue manager has been defined. Is there a linked exception? -----Original Message----- From: Meital Ger