ibm-mq

Use of Public key in the certificate signing request ( CSR )

|▌冷眼眸甩不掉的悲伤 提交于 2021-01-28 01:49:19
问题 Public and private-key pair will be generated during the creation of CSR on our server. We will send the CSR and public key to CA by holding private key with us. CA will validate our public key before signing it with private key of CA's root certificate. We are having our own CA team to certify the CSR requests. My queries are as follows: Will CSR itself includes public key or do we need to provide public key separately to CA ? Will CSR be signed by our public key before sending it to CA (or)

An unexpected error (2063) occurs when I connect to my queue manager

强颜欢笑 提交于 2021-01-27 20:32:52
问题 I'm looking to setup a Queue Manager Using WebSphere MQ V7 MQ Explorer. After Creating my Queue Manager, normally I expect that some sub directories are automatically generated under it, "Queues", "Topics", "Channels" .. as illustrated in the photo below. In my case, no sub directories are generated, as illustrated below in the second snapshot. PS : the status of my Queue manager is : Running but disconnected from WebSphere MQ Explorer. When I right-click on the QMgr Name and choose Connect,

Websphere MQ C++ client crashes in VS2013- library/linker issues?

六眼飞鱼酱① 提交于 2021-01-27 16:32:04
问题 I just upgraded a project to VS2013 from VS2010 and now it crashes whenever I send a message via MQ, yet it worked fine under VS2010. I suspected it was something to do with VS2013, so I built one of the demo apps that comes with MQ - imqwrld.cpp which is a simple "hello world" app. This code alone is enough for the debug runtime library to throw an exception: #include <imqi.hpp> // WebSphere MQ C++ int main ( int argc, char * * argv ) { ImqQueue * p = new ImqQueue(); delete p; return 0 }

Websphere MQ C++ client crashes in VS2013- library/linker issues?

帅比萌擦擦* 提交于 2021-01-27 16:31:40
问题 I just upgraded a project to VS2013 from VS2010 and now it crashes whenever I send a message via MQ, yet it worked fine under VS2010. I suspected it was something to do with VS2013, so I built one of the demo apps that comes with MQ - imqwrld.cpp which is a simple "hello world" app. This code alone is enough for the debug runtime library to throw an exception: #include <imqi.hpp> // WebSphere MQ C++ int main ( int argc, char * * argv ) { ImqQueue * p = new ImqQueue(); delete p; return 0 }

Websphere MQ C++ client crashes in VS2013- library/linker issues?

主宰稳场 提交于 2021-01-27 16:31:09
问题 I just upgraded a project to VS2013 from VS2010 and now it crashes whenever I send a message via MQ, yet it worked fine under VS2010. I suspected it was something to do with VS2013, so I built one of the demo apps that comes with MQ - imqwrld.cpp which is a simple "hello world" app. This code alone is enough for the debug runtime library to throw an exception: #include <imqi.hpp> // WebSphere MQ C++ int main ( int argc, char * * argv ) { ImqQueue * p = new ImqQueue(); delete p; return 0 }

How to create durable subscription to ibm mq amqp topic from java program?

你。 提交于 2021-01-20 12:36:28
问题 We have programmatically created subscriber to IBM MQ AMQP TOPIC with createDurableSubscriber by providing clientId and subscriber name. We start the program so it subscribes to TOPIC and stop the program. Then send the msgs to topic and again start the receiver program again but we cannot receive the msgs sent and loose the messages which should not happen in case of durable subscription.. We can see amqp topic and its durable subscription when subscriber is connected using mqsc commands

MQ Input/Output count increasing when Datapower client is connect using MQ front side handler

坚强是说给别人听的谎言 提交于 2020-12-16 07:33:39
问题 I am using MQ 7.5.0.2 and Datapower client IDG7 When MQ send messages to Datapower, Datapower receive those messages using MQ front side handlers and also same way it do send messages using Backend URL But the problem I am facing it when ever Datapower connects to MQ, Queue Input/Output count increases to (10 ~20) and remains same and the Handle state is INACTIVE. When I see queue details using below commands it is displaying as below display qstatus(******) type(handle) QUEUE(********) TYPE