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 -

Pentaho BI Platform Tracking | Meelan Laxman | 1 year ago
  1. 0

    Allow for any valid DNS characters for the hostname in the IBM Websphere URL. This is for the IBM Websphere Consumer / Producer steps Currently if you have the following valid hostname: mq://thisIs-AHostName:1434/Test It will throw the following error because of the dash (-): 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Unable to make connection to mq://thisIs-AHostName:1434/Test 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : 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 - 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.mq.d.f(SourceFile:103) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.mq.a.b(SourceFile:53) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.a.init(SourceFile:82) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.c.init(SourceFile:109) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at java.lang.Thread.run(Thread.java:745) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Error initializing step [IBM Websphere MQ Consumer - QUEUE] 2015/10/21 14:35:07 - MQ Consumer - QUEUE - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Step [IBM Websphere MQ Consumer - QUEUE.0] failed to initialize!

    Pentaho BI Platform Tracking | 1 year ago | Meelan Laxman
    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 -
  2. 0

    Allow for any valid DNS characters for the hostname in the IBM Websphere URL. This is for the IBM Websphere Consumer / Producer steps Currently if you have the following valid hostname: mq://thisIs-AHostName:1434/Test It will throw the following error because of the dash (-): 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Unable to make connection to mq://thisIs-AHostName:1434/Test 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : 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 - 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.mq.d.f(SourceFile:103) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.mq.a.b(SourceFile:53) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.a.init(SourceFile:82) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.steps.jms.c.init(SourceFile:109) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - at java.lang.Thread.run(Thread.java:745) 2015/10/21 14:35:07 - IBM Websphere MQ Consumer - QUEUE.0 - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Error initializing step [IBM Websphere MQ Consumer - QUEUE] 2015/10/21 14:35:07 - MQ Consumer - QUEUE - ERROR (version 5.4.0.1-130, build 1 from 2015-06-14_12-34-55 by buildguy) : Step [IBM Websphere MQ Consumer - QUEUE.0] failed to initialize!

    Pentaho BI Platform Tracking | 1 year ago | Meelan Laxman
    org.pentaho.di.core.exception.KettleException: Unable to parse JMS url. Check the syntax of the JMS url for this MQ connection. It should resemble mq://host:port/queue_manager_name?optional_channel_name
  3. 0

    The simple mapping step requires an input. It shouldnt really; The normal mapping doesnt. See error: 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - ERROR (version 5.0.1, build 1 from 2013-10-30_19-53-32 by buildguy) : Unable to load the mapping transformation because of an error : org.pentaho.di.core.exception.KettleException: 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - The simple mapping step needs one Mapping Input step to write to in the sub-transformation 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - ERROR (version 5.0.1, build 1 from 2013-10-30_19-53-32 by buildguy) : org.pentaho.di.core.exception.KettleException: 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - The simple mapping step needs one Mapping Input step to write to in the sub-transformation 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - at org.pentaho.di.trans.steps.simplemapping.SimpleMapping.prepareMappingExecution(SimpleMapping.java:225) 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - at org.pentaho.di.trans.steps.simplemapping.SimpleMapping.init(SimpleMapping.java:286) 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:65) 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - at java.lang.Thread.run(Unknown Source) 2013/11/08 15:31:06 - Simple Mapping (sub-transformation).0 - ERROR (version 5.0.1, build 1 from 2013-10-30_19-53-32 by buildguy) : Error initializing step [Simple Mapping (sub-transformation)] And attached files.

    Pentaho BI Platform Tracking | 3 years ago | Dan Keeley (codek)
    org.pentaho.di.core.exception.KettleException: The simple mapping step needs one Mapping Input step to write to in the sub-transformation
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    When placing a parameter/variable for the URL in the IBM Websphere Consumer / Producer step I receive the following error: {quote} 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - ERROR (version 6.0.0.0-353, build 1 from 2015-10-07 13.27.43 by buildguy) : Unable to make connection to ${WebsphereURL} 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - ERROR (version 6.0.0.0-353, build 1 from 2015-10-07 13.27.43 by buildguy) : org.pentaho.di.core.exception.KettleException: *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 - 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - at org.pentaho.di.trans.steps.jms.mq.d.f(SourceFile:103) 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - at org.pentaho.di.trans.steps.jms.mq.a.b(SourceFile:53) 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - at org.pentaho.di.trans.steps.jms.a.init(SourceFile:82) 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - at org.pentaho.di.trans.steps.jms.c.init(SourceFile:109) 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69) 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - at java.lang.Thread.run(Unknown Source) 2015/12/16 15:19:50 - IBM Websphere MQ Consumer.0 - ERROR (version 6.0.0.0-353, build 1 from 2015-10-07 13.27.43 by buildguy) : Error initializing step [IBM Websphere MQ Consumer] 2015/12/16 15:19:50 - WebsphereTEST - ERROR (version 6.0.0.0-353, build 1 from 2015-10-07 13.27.43 by buildguy) : Step [IBM Websphere MQ Consumer.0] failed to initialize! {quote} EXPECTED RESULTS: The transformation should run fine and retrieve the message from the queue ACTUAL RESULTS: It fails with the stack trace above. Note that if you hardcode the URL, the transformation will run as expected.

    Pentaho BI Platform Tracking | 12 months ago | Meelan Laxman
    org.pentaho.di.core.exception.KettleException: *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*
  6. 0

    When using a Mapping (Sub-transformation) step where you specify to use a transformation from a repository; If you use a variable name for the transformation name it is resolved no problem. When also using a variable for the directory of the transformation, the directory variable does not get resolved and therefore the transformation cannot be found. 2010/05/11 11:10:59 - Set Variables.0 - Set variable CURRENT_TRANSFER to value [SINGLE] . . . 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : Unable to load the mapping transformation because of an error : org.pentaho.di.core.exception.KettleException: 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : Unable to load transformation [WORKORDER] : can't find directory /MX/${CURRENT_TRANSFER} 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : org.pentaho.di.core.exception.KettleException: 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : Unable to load transformation [WORKORDER] : can't find directory /MX/${CURRENT_TRANSFER} 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : at org.pentaho.di.trans.steps.mapping.MappingMeta.loadMappingMeta(MappingMeta.java:518) 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : at org.pentaho.di.trans.steps.mapping.Mapping.init(Mapping.java:342) 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : at org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:48) 2010/05/11 11:11:13 - Mapping (sub-transformation).0 - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : at java.lang.Thread.run(Unknown Source) 2010/05/11 11:11:13 - Mapping (sub-transformation) - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : Error initializing step [Mapping (sub-transformation)] 2010/05/11 11:11:13 - MX - Get Each Row - ERROR (version 3.2.5, build 1 from 2010-05-11 10.46.59 by bill.wallace) : Step [Mapping (sub-transformation).0] failed to initialize! As you can see above, the variable with WORKORDER in is resolved btu the CURRENT_TRANSFER is not. I have tested this in 3.2.4,3.2.5 and 4.0.0Preview. It works in 4.0.0Preview but not in 3.2.4/5 best Regards Bill

    Pentaho BI Platform Tracking | 7 years ago | Bill Wallace
    org.pentaho.di.core.exception.KettleException: Unable to load transformation [WORKORDER] : can't find directory /MX/${CURRENT_TRANSFER}

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. 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()
    2. org.pentaho.di
      StepInitThread.run
      1. org.pentaho.di.trans.steps.jms.mq.d.f(SourceFile:103)
      2. org.pentaho.di.trans.steps.jms.mq.a.b(SourceFile:53)
      3. org.pentaho.di.trans.steps.jms.a.init(SourceFile:82)
      4. org.pentaho.di.trans.steps.jms.c.init(SourceFile:109)
      5. org.pentaho.di.trans.step.StepInitThread.run(StepInitThread.java:69)
      5 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:745)
      1 frame