Closed lakshmanpython closed 5 years ago
@lakshmanpython I cannot see any details of your problem in this issue. Can you tell me what your setup is and what issue you are seeing?
2019-02-20 03:35:59,849] ERROR JMS exception {} (com.ibm.eventstreams.connect.mqsink.JMSWriter:230) com.ibm.msg.client.jms.DetailedJMSRuntimeException: JMSWMQ2007: Failed to send a message to destination 'XXXXXX.REMOTE'. JMS attempted to perform an MQPUT or MQPUT1; however IBM MQ reported an error. Use the linked exception to determine the cause of this error. at com.ibm.msg.client.jms.DetailedJMSException.getUnchecked(DetailedJMSException.java:267) at com.ibm.msg.client.jms.internal.JmsErrorUtils.convertJMSException(JmsErrorUtils.java:173) at com.ibm.msg.client.jms.internal.JmsProducerImpl.send(JmsProducerImpl.java:633) at com.ibm.eventstreams.connect.mqsink.JMSWriter.send(JMSWriter.java:227) at com.ibm.eventstreams.connect.mqsink.MQSinkTask.put(MQSinkTask.java:90) at org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:564) at org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:322) at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:225) at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:193) at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:175) at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:219) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: com.ibm.mq.MQException: JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2009' ('### MQRC_CONNECTION_BROKEN'). at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:203) at com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1263) at com.ibm.msg.client.wmq.internal.WMQMessageProducer.checkJmqiCallSuccess(WMQMessageProducer.java:1220) at com.ibm.msg.client.wmq.internal.WMQMessageProducer.access$800(WMQMessageProducer.java:75) at com.ibm.msg.client.wmq.internal.WMQMessageProducer$SpiUnidentifiedProducerShadow.sendInternal(WMQMessageProducer.java:1032) at com.ibm.msg.client.wmq.internal.WMQMessageProducer$ProducerShadow.send(WMQMessageProducer.java:548) at com.ibm.msg.client.wmq.internal.WMQMessageProducer.send(WM
Regards Lakshman
@lakshmanpython Thanks for the stack trace, it sounds like the connector was at least able to find your MQ install, which indicates your connector configuration is correct. Can you review this IBM support documentation and see if following those steps resolves your problem? http://www-01.ibm.com/support/docview.wss?uid=swg21226703
Thanks Katheris Issue solved.
we keep the task set 500 ms , now removed.
Hi Andrew
facing below issue after send couple of messages.