Question

Procedure to update Rule-Connect-MQ ValidateInfrastructure activity residing in pega-procom Ruleset

I have edited the Rule-Connect-MQ ValidateInfrastructure activity with following information. But when i had checked in the rule now it is appearing in my RuleSet BankingMLG. It was part of under pega-procom. I had tested the Connect-MQ but it was not logging the debug statement that i had put in. Hence, need your help to know whether i had edited the Rule-Connect-MQ ValidateInfrastructure activity correctly as it the latest version now moved under my app rule set instead of Pega-Procom before.

The below code was added:-

com.ibm.mq.MQEnvironment.sslCipherSuite = "TLS_RSA_WITH_AES_256_CBC_SHA256";
com.ibm.mq.MQEnvironment.hostname= "xxxx.com";
com.ibm.mq.MQEnvironment.port = 1414;
com.ibm.mq.MQEnvironment.channel = "GMXXXX.PEGA.CLT";
com.ibm.mq.MQEnvironment.iserID = "XXXXX";
com.ibm.mq.MQEnvironment.password = "XXXX"

STEPS TO REPRODUCE
Following the edit and checked in the Rule-Connect-MQ ValidateInfrastructure activity .

Selected Integration-resources

Ran MQ Server -> MoFMQServer

The below is the error that i am getting when i had tested the MQ connectivity.

com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2397'.
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:247)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:588)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:630)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:107)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:205)
at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:911)
at com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:799)
at com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:750)
at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:157)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:681)
at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.connectQueueMananger(MQListener.java:1793)
at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.initializeConnection(MQListener.java:803)
at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.run_(MQListener.java:640)
at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:442)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9204: Connection to host '<hostname>' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2397;AMQ9641: Remote CipherSpec error for channel 'GMFTLX04.PEGA.CLT' to host ''. [3=GMFTLX04.PEGA.CLT]],3=<hostname>(1414),5=RemoteConnection.analyseErrorSegment]
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:2053)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1226)
at com.ibm.mq.ese.jmqi.InterceptedJmqiImpl.jmqiConnect(InterceptedJmqiImpl.java:311)
at com.ibm.mq.ese.jmqi.ESEJMQI.jmqiConnect(ESEJMQI.java:337)
at com.ibm.mq.MQSESSION.MQCONNX_j(MQSESSION.java:924)
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:236)
... 14 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9641: Remote CipherSpec error for channel 'GMFTLX04.PEGA.CLT' to host ''. [3=GMFTLX04.PEGA.CLT]
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.analyseErrorSegment(RemoteConnection.java:3839)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.receiveTSH(RemoteConnection.java:2746)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.initSess(RemoteConnection.java:1034)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConnection.java:727)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:400)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:299)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:164)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1598)
... 19 more
2019-06-20 13:16:37,240 [ MQ-Thread-8] [ STANDARD] [ ] ( services.mq.MQListener) ERROR MQ.MoFListenerWoS.MoFMQServer - Caught MQException in listener MoFMQServer.MoFListenerWoS
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2397'.
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:247)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:588)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:630)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:107)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:205)
at com.ibm.mq.MQQueueManagerFactory.obtainBaseMQQueueManager(MQQueueManagerFactory.java:911)
at com.ibm.mq.MQQueueManagerFactory.procure(MQQueueManagerFactory.java:799)
at com.ibm.mq.MQQueueManagerFactory.constructQueueManager(MQQueueManagerFactory.java:750)
at com.ibm.mq.MQQueueManagerFactory.createQueueManager(MQQueueManagerFactory.java:157)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:681)
at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.connectQueueMananger(MQListener.java:1793)
at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.initializeConnection(MQListener.java:803)
at com.pega.pegarules.integration.engine.internal.services.mq.MQListener.run_(MQListener.java:640)
at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:442)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9204: Connection to host '<hostname>' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2397;AMQ9641: Remote CipherSpec error for channel 'GMFTLX04.PEGA.CLT' to host ''. [3=GMFTLX04.PEGA.CLT]],3=<hostname>,5=RemoteConnection.analyseErrorSegment]
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:2053)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1226)
at com.ibm.mq.ese.jmqi.InterceptedJmqiImpl.jmqiConnect(InterceptedJmqiImpl.java:311)
at com.ibm.mq.ese.jmqi.ESEJMQI.jmqiConnect(ESEJMQI.java:337)
at com.ibm.mq.MQSESSION.MQCONNX_j(MQSESSION.java:924)
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:236)
... 14 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9641: Remote CipherSpec error for channel 'GMFTLX04.PEGA.CLT' to host ''. [3=GMFTLX04.PEGA.CLT]
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.analyseErrorSegment(RemoteConnection.java:3839)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.receiveTSH(RemoteConnection.java:2746)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.initSess(RemoteConnection.java:1034)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConnection.java:727)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:400)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:299)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:164)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1598)
... 19 more
2019-06-20 13:16:37,335 [ ] [ STANDARD] [ ] (ternal.async.PassivationDaemon) INFO - PegaRULES Passivation Daemon initialized in web-tier.
2019-06-20 13:16:37,360 [ ] [ STANDARD] [ ] (al.async.AsyncServicesExecutor) INFO - PegaRULES Async service executor (thread pool) initialized in web-tier.
2019-06-20 13:16:37,413 [ [ STANDARD] [ ] (base.PassivationStorageManager) INFO - Passivation data will be written to file.
2019-06-20 13:16:38,338 [ ] [ STANDARD] [ ] ( etier.impl.EngineStartup) INFO - PegaRULES engine successfully started. Server: <server name> System: pega Description: <server name> pega 2019-05-21 13:56:36.199 GMT URL: http://<server name>:20110/prweb/PRSOAPServlet
2019-06-20 13:16:38,361 [ ] [ STANDARD] [ ] (ervlet.WebAppLifeCycleListener) INFO - MBean registered via WebAppLifeCycle: a83b2ef56c93a46bbfb2a7f2fb728f76
2019-06-20 13:16:38,373 [ ] [ STANDARD] [ ] ( priv.management.MBeanSecurity) INFO - The following MBean security configuration has been applied:
2019-06-20 13:16:38,374 [ ] [ STANDARD] [ ] ( priv.management.MBeanSecurity) INFO - deny.RequestorManagement.Clipboard=true
2019-06-20 13:16:38,374 [ ] [ STANDARD] [ ] ( priv.management.MBeanSecurity) INFO - deny.RequestorManagement.RequestorDetails=true
2019-06-20 13:16:38,374 [ ] [ STANDARD] [ ] ( priv.management.MBeanSecurity) INFO - deny.DatabaseManagement.DatabaseConnectionDetails=true
2019-06-20 13:16:38,626 [ ] [ STANDARD] [ ] (riv.management.MBeanManagement) INFO - MBean Management (Web) initialized for DefaultDomain
2019-06-20 13:16:38,634 [ ] [ STANDARD] [ ] (ervlet.WebAppLifeCycleListener) INFO - Web Tier initialization is complete.

***Edited by Moderator: Lochan to mask proprietary information***

***Moderator Edit-Vidyaranjan: Updated SR details***

Group Tags

Comments

Keep up to date on this post and subscribe to comments

July 10, 2019 - 4:27am

Hi Team,

Could someone pelase hep me on this issue?

Thanks,

Kumar

August 30, 2019 - 12:34am

Hi Team,

      Could you please help on the above issue? I am also facing the similar issue.

Thanks

Madhan