Skip to main content

Posts

Showing posts from June, 2012

IBM WebSphere MQ JMS exception messages - Middleware News

JMS exception messages This section lists most common exceptions that can be generated by WebSphere MQ JMS. It does  not  include all messages that can be written to a trace file. If you receive an exception message not in this list (except in a trace file), or if the cause seems to be an error in WebSphere MQ JMS, please contact your IBM service representative. MQJMS0000 Method {0} has been invoked at an illegal or inappropriate time or if the provider is not in an appropriate state for the requested operation. Explanation:  The normal reason for this exception is that the SSL certificate stores have not been defined. {0} identifies the method that has caused the problem.  User Response:  See  Using Secure Sockets Layer (SSL)  for more information. MQJMS0002 JMS Client attempted to set invalid clientId on a connection. Explanation:  An application attempted to set the clientId property of a valid connection to null, or attempted to set the clientId property of an invalid

adsrerrapop