org.pentaho.di.core.exception.KettleException

2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - Unable to parse JMS url. Check the syntax of the JMS url for this MQ connection. 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - It should resemble mq://host:port/queue_manager_name?optional_channel_name 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 -

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web396

  • via Pentaho BI Platform Tracking by Meelan Laxman, 9 months ago
    2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - Unable to parse JMS url. Check the syntax of the JMS url for this MQ connection. 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - It should resemble mq://host:port/queue_manager_name?optional_channel_name 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 -
  • via Pentaho BI Platform Tracking by Meelan Laxman, 7 months ago
    *2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - Unable to parse JMS url. Check the syntax of the JMS url for this MQ connection.* *2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - It should resemble mq://host:port/queue_manager_name?channel=optional_channel_name* 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 -
  • via Pentaho BI Platform Tracking by Meelan Laxman, 1 year ago
    *2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - Unable to parse JMS url. Check the syntax of the JMS url for this MQ connection.* *2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - It should resemble mq://host:port/queue_manager_name?channel=optional_channel_name*
  • Stack trace

    • org.pentaho.di.core.exception.KettleException: 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - Unable to parse JMS url. Check the syntax of the JMS url for this MQ connection. 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - It should resemble mq://host:port/queue_manager_name?optional_channel_name 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.mq.d.f(SourceFile:103) at org.pentaho.di.trans.steps.jms.mq.a.b(SourceFile:53) at org.pentaho.di.trans.steps.jms.a.init(SourceFile:82) at org.pentaho.di.trans.steps.jms.c.init(SourceFile:109) at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.