Lydia
New Contributor II
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Error management on JMS Consumer
Hi ptaylor, Thank you very much for this answer ! You gave me a better insight on how things work. And yeah it actually makes a lot of sense that i’m not catching this error. Yet at the same time being able to handle an error path and stop the pipeline instead of failing is quite different. Basically : For the JMS snap I want to be able to direct any issue with MQ directly to MQ team cause i have no hand in it. Most issue these days are actually about a down with the MQ but i was doing quick testing on my side only so i tried with an auth failure instead. I’ll contact the MQ dev team for integrated testing to see if i can reproduce the exact error and check how snaplogic responds to that. Regardless of the error/snap having an issue and of what kind, I wanted to be able to STOP the pipeline after sending a notification / logging the issue, instead of ending in a FAILURE (which is also a stop but abrupt). That’s because of how my organisation poorly deals with failures in Snaplogic i guess. Since we’re a big org with several teams using Snaplogic, right now it takes several hours for my team to be made aware of the failure of one of our pipeline in production and then i need to dig in the dashboard to find more info and it’s really not an efficent process. With an error path i can make us aware directly and with more specific info depending on where a problems occurs.2.5KViews1like2CommentsRe: Can we hyperlink inside a mapper snap?
If you clic in the F2 cell and then press enter does the formula gets calculated then ? I’d think this is because the output printed is “text” so it shows the text until you click it and it understand it’s a formula instead. I’m not sure how you could fix this, this has probably to do with excel settings too…2.4KViews0likes1CommentRe: Can we hyperlink inside a mapper snap?
Hum… I’m using a french version of Excel so symbols might be different… But i tried it on my side and it worked Testing For Excel Link_2022_04_29.slp (6.5 KB) Maybe try using double quotes "=HYPERLINK(\"https://www.google.com/\",\""+ $ID +"\")"2.4KViews1like0CommentsRe: Error management on JMS Consumer
Hi ptaylor, Here is the error i got. In this case i was specifically using the wrong password to trigger an authentication error. An error occurred while creating the consumer Resolution: Please verify if the provided properties like destination, message selector and subscription name are valid Reason: JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). Hide Details... SnapCompletionService com.snaplogic.api.ConfigurationException: An error occurred while creating the consumer at com.snaplogic.snaps.jms.JMSConsumer.executeForSuggest(JMSConsumer.java:635) at com.snaplogic.cc.snap.common.SnapRunnableImpl.executeSnap(SnapRunnableImpl.java:798) at com.snaplogic.cc.snap.common.SnapRunnableImpl.executeForSuggest(SnapRunnableImpl.java:647) at com.snaplogic.cc.snap.common.SnapRunnableImpl.doRun(SnapRunnableImpl.java:856) at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:435) at com.snaplogic.cc.snap.common.SnapRunnableImpl.call(SnapRunnableImpl.java:117) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: com.snaplogic.snap.api.SnapDataException: An error occurred while creating the connection from the connection factory (Name: CDP_MQ_APP1) at com.snaplogic.snaps.jms.JMSAccount.createConnection(JMSAccount.java:376) at com.snaplogic.snaps.jms.JMSAccount.createSessionRequest(JMSAccount.java:308) at com.snaplogic.snaps.jms.JMSAccount.connect(JMSAccount.java:223) at com.snaplogic.snaps.jms.JMSAccount.connect(JMSAccount.java:75) at com.snaplogic.snaps.jms.JMSConsumer.initSessionsForValidate(JMSConsumer.java:310) at com.snaplogic.snaps.jms.JMSConsumer.lambda$executeForSuggest$3(JMSConsumer.java:611) at net.jodah.failsafe.Functions.lambda$toSupplier$10(Functions.java:262) at net.jodah.failsafe.Functions.lambda$get$0(Functions.java:48) at net.jodah.failsafe.RetryPolicyExecutor.lambda$supply$0(RetryPolicyExecutor.java:66) at net.jodah.failsafe.Execution.executeSync(Execution.java:128) at net.jodah.failsafe.FailsafeExecutor.call(FailsafeExecutor.java:379) at net.jodah.failsafe.FailsafeExecutor.run(FailsafeExecutor.java:212) at com.snaplogic.snaps.jms.JMSConsumer.executeForSuggest(JMSConsumer.java:604) ... 11 more Caused by: com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for queue manager 'TAAPP1' with connection mode 'Client' and host name 'CTAMQS1.LACAISSE.COM(1417)'. Please check if the supplied username and password are correct on the queue manager to which you are connecting. For further information, review the queue manager error logs and the Securing IBM MQ topic within IBM Knowledge Center. at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:531) at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:215) at com.ibm.msg.client.wmq.internal.WMQConnection.<init>(WMQConnection.java:439) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:8475) at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:7815) at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl._createConnection(JmsConnectionFactoryImpl.java:303) at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:236) at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConnectionFactory.java:6005) at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:136) at com.ibm.mq.jms.MQQueueConnectionFactory.createConnection(MQQueueConnectionFactory.java:209) at com.snaplogic.snaps.jms.JMSAccount.createConnection(JMSAccount.java:374) ... 23 more Caused by: com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:203) ... 32 more Reason: JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). Resolution: Please verify if the provided properties like destination, message selector and subscription name are valid Error Fingerprint[0] = efp:com.snaplogic.snaps.jms.jP6OsCuR Error Fingerprint[1] = efp:com.snaplogic.snaps.jms.WukNlqv9 Error Fingerprint[2] = efp:com.ibm.msg.client.wmq.common.internal.w7ghFJBL Error Fingerprint[3] = efp:com.ibm.msg.client.wmq.common.internal._mz1O6W-2.1KViews1like1CommentRe: Error management on JMS Consumer
Hum… sorry but i feel we are not focussing on the issue i’m having. I’ve updated my first answer to make it more clear (also english is not my first language sorry if i’m confusing). My issue is not with Execute Pipeline failing or such, it’s that the JMS Consumer Snap don’t go to that error path. The Audit after works just fine if i use the good SQL password, i was juste trying to show quickly a similar issue having a different consequence but i have no issue with either the SQL or Execute Pipeline. So are there some errors type that won’t trigger an error path ? Is this maybe on some snaps only ?2.3KViews1like1CommentRe: Error management on JMS Consumer
Hi @darshthakkar, thanks for the comeback ! The snap works just fine usually, I was currently trying to trigger an error by using the wrong password to see if the error path was working correctly, because error caused on MQ issues needed to be foward to a different team than the team managing the rest of the pipeline in production. My issue is not the error itself but the fact that it doesnt go to the error path and instead fails right there. In comparaison when i use the wrong SQL password on the SQL snap it triggers the error path correctly : (dont mind the fail on the error box itself cause it’s using the same sql account 😅 )4KViews1like6CommentsError management on JMS Consumer
Hello everyone, We are currently trying to improve our pipelines by adding error paths and are having problems with the JMS Consumer snap. Unlike other snaps, like the SQL Server snaps, where a connection failure is routed to the error path, a connection error on our JMS snap does not trigger the error path and fails (see attached image). Is there a way for us to catch those errors without ending with a failure ? Please note we do not use ultra pipeline/ultra tasks, but a regular schedule task to run this pipeline. Edit for clarity : Error is not triggering error path Here same type of error (connexion error) is triggering error path (don’t mine the failure on the next box it was expected here)Solved