Java Message Services (JMS) Connector

RE: Java Message Services (JMS) Connector

superonion — Thu, 12 Sep 2024 02:03:48 GMT

I have also had the same problem.

2024-09-12 00:46:53,056 [ActiveMQ VMTransport: vm://localBroker#1-1] DEBUG org.apache.activemq.broker.region.AbstractRegion - localBroker adding destination: topic://ActiveMQ.Advisory.Connection
2024-09-12 00:46:53,061 [ActiveMQ VMTransport: vm://localBroker#1-1] DEBUG org.apache.activemq.broker.region.AbstractRegion - localBroker adding consumer: ID:swjpto4201tv-58836-1726102012812-4:1:-1:1 for destination: ActiveMQ.Advisory.TempQueue,ActiveMQ.Advisory.TempTopic
Exception in thread "HandshakeCompletedNotify-Thread" java.lang.UnsupportedOperationException: This method is deprecated and marked for removal. Use the getPeerCertificates() method instead.
at java.base/javax.net.ssl.SSLSession.getPeerCertificateChain(SSLSession.java:295)
at java.base/javax.net.ssl.HandshakeCompletedEvent.getPeerCertificateChain(HandshakeCompletedEvent.java:173)
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.handshakeCompleted(RemoteTCPConnection.java:2187)
at java.base/sun.security.ssl.TransportContext$NotifyHandshake$1.run(TransportContext.java:701)
at java.base/sun.security.ssl.TransportContext$NotifyHandshake$1.run(TransportContext.java:698)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/sun.security.ssl.TransportContext$NotifyHandshake.run(TransportContext.java:698)
at java.base/java.lang.Thread.run(Thread.java:842)

RE: Java Message Services (JMS) Connector

mikelGran — Mon, 12 Aug 2024 08:18:34 GMT

[mention:85da3ad2b1884075bab04aad006ee23b:e9ed411860ed4f2ba0265705b8793d05] Hi! This plugin does not work in the new 24.2 Appian Version due JAVA 17. Other plugins like Advance Call WebService have been updated to solve this, could it be possible with this one too, thanks!

RE: Java Message Services (JMS) Connector

manpreetm0001 — Thu, 23 Jul 2020 12:40:42 GMT

[mention:85da3ad2b1884075bab04aad006ee23b:e9ed411860ed4f2ba0265705b8793d05]Please help me with tibco topic connection for messaging system

RE: Java Message Services (JMS) Connector

manpreetm0001 — Tue, 21 Jul 2020 13:33:51 GMT

Please help me with tibco connection for messaging system

RE: Java Message Services (JMS) Connector

pooja.sudarshan — Wed, 01 Jul 2020 11:27:06 GMT

[mention:85da3ad2b1884075bab04aad006ee23b:e9ed411860ed4f2ba0265705b8793d05] The plugin is working good for me. Currently I have hardcode the connection string in "Que Config" node of "JMS Message Producer". To generalize it, I am trying to use Constant to store the connection string, and make this this constant environment specific.

When I pass this connection string to the plug-in using constant, it throws below error .

"com.appiancorp.plugins.typetransformer.AppianPrimitive cannot be cast to com.appiancorp.plugins.typetransformer.AppianObject"

Can you please help if this can be reoslved?

RE: Java Message Services (JMS) Connector

pooja.sudarshan — Wed, 20 May 2020 14:35:47 GMT

Can we use this plugin for MQ version 9.1.0.3?

Where can I find documentation for IBM MQ setup in Appian?

Thanks,

Pooja

RE: Java Message Services (JMS) Connector

jesusa583 — Thu, 14 Feb 2019 12:53:25 GMT

The previous Problem was solved by restarting the Server. Now we have a Problem reading the message but we are going to try to solve it through the professional Services team

RE: Java Message Services (JMS) Connector

jesusa583 — Mon, 11 Feb 2019 15:45:30 GMT

Hi there,

We are using the plugin jms-2.0.0.jar to send a message to an IBM MQ Queue in the way described in the documentation. However we always see the following error message in the log:

2019-02-11 15:13:48,256 [Appian Work Item - 8674 - execution01 : UnattendedJavaActivityRequest] WARN com.appiancorp.process.engine.UnattendedJavaActivityRequest - An error occurred while executing activity: id=268451385, classname=com.appiancorp.ps.jms.smartservice.MessageProducerSmartService. This action will be retried until it succeeds or the maximum retry period is reached. Details: com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ0018: Failed to connect to queue manager 'BA74' with connection mode 'Client' and host name 'blbmq-ba74(19074)'.

We have checked with the MQ Team that the Queue Connection Settings are correct:

[host=blbmq-ba74, port=19074, queueManager=BA74, channel=JAVA.BPMS.BA74.1, cipherSuite=, clientId=, queue=MQBP0001.APPIAN.REQUEST.TO.IB, topic=, subscriptionName=]

Any idea about why it could fail? The MQ Team says that the channel Name is incorrect, with an extra blank space " JAVA.BPMS.BA74.1" which was a Problem at the beginning but the model was corrected and published. Old instances have been deleted but still we cant connect.

Any idea would be highly appreciated!