Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm guessing the problem (or at least <em>a</em> problem) is here:</p> <pre><code>MQQueue mqQueue = new MQQueueManager(queueName, props); </code></pre> <p>This should be </p> <pre><code>queueManager = new MQQueueManager(queueManagerName, properties); </code></pre> <p>If you have installed the WebSphere MQ client to the default location, there are many sample programs under the following directory:</p> <pre><code>C:\Program Files (x86)\IBM\WebSphere MQ\tools\dotnet\samples\cs\base\ </code></pre> <p>There are a number of sample programs there for various tasks. If you have the latest V7.1 client installed then you will see the following programs:</p> <pre><code>SimpleAsyncPut SimpleClientAutoReconnectGet SimpleClientAutoReconnectPut SimpleGet SimpleMessageProperties SimplePublish SimplePut SimpleReadAhead SimpleSharingConversation SimpleSubscribe SimpleXAGet SimpleXAPut </code></pre> <p>There are also WCF and XMS samples.</p> <p>If you need the client code, please see my response to another SO question <a href="https://stackoverflow.com/questions/10957612/what-is-the-latest-websphere-mq-client-version/10957643#10957643">here</a> for links.</p> <p><strong>Update:</strong> </p> <p>Here's the normal diagnostic process.</p> <ol> <li>If the WMQ components were installed by relocating libraries or classes from somewhere else, perform an install using the full vendor-supplied client media. This includes troubleshooting utilities such as trace, dspmqver, etc. It also resolves any library or class mismatch issues.</li> <li>Use the pre-compiled client programs to test the connection. The <code>amqsputc</code>, <code>amqsgetc</code> and <code>amqsbcgc</code> programs require the <code>MQSERVER</code> environment variable <a href="http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/cs12280_.htm" rel="nofollow noreferrer">as described here</a>. The Q program from <a href="http://ibm.co/SupptPacMA01" rel="nofollow noreferrer">SupportPac MA01</a> is a separate download but has the advantage of NOT requiring any environment variables, CCDT files or other dependencies.</li> <li>If the sample programs fail, check the QMgr's error logs at <code>[WMQ install]/qmgrs/[QMgr name]/errors/AMQERR01.LOG</code> for messages. Also check for FDC files and errors in <code>[WMQ install]/errors</code>.</li> <li>If no errors on the QMgr side, attempt the connection again while using a client-side trace as described <a href="http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.msc.doc/xms_ctrouble_trace_net.html" rel="nofollow noreferrer">here</a> and <a href="http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/cs12880_.htm" rel="nofollow noreferrer">here</a>.</li> </ol> <p>Most client problems are resolved through installation of the full WMQ client as supplied by IBM. (Conversely that implies most people are installing by grabbing DLL or JAR files.) If the problem persists, error log inspection on the QMgr and client side usually reveals the underlying cause. If these do not work then tracing usually diagnoses the remaining issues.</p> <p><strong>UPDATE 2:</strong><br> Per the error messages <a href="http://www.mqseries.net/phpBB2/viewtopic.php?p=332547#332547" rel="nofollow noreferrer">posted at MQSeries.net</a>, the channel has a security exit set. A security exit is external code that the channel calls out to when starting a channel. There is no way to know what the exit expects or does without having access to the code or docs of the exit. If the exit is written in-house, you'll need to talk to the programmer to figure out what it requires. If the exit is a commercial product then you will need to get the documentation for it. </p> <p>Alternatively, alter the channel so that <code>SCYEXIT</code> is blank to disable the exit.</p> <p>The data posted at MQSeries.net was as follows:</p> <pre><code>MQ9575: DCE Security: failed to get the user's login name. EXPLANATION: System call 192.168.50.55 to get the login name of the user running WebSphere MQ client application process 5 failed with error value -1. This occurred in security exit function create_cred. The exit will now attempt to open channel using the DCE default login context. ACTION: If you wish to run using the DCE default login context take no action. If you wish to run using the user's login name as the DCE security exit principal examine the documentation for the operating system on which you are running MQ clients and reconfigure the operating system as necessary to allow the 192.168.50.55 call to succeed. </code></pre> <p>Note that it states the call is failing in the security exit.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload