Service Virtualization

  • Private Community

  • 1.  MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 09:25 AM

    Hi ,

     

    I had created MQ virtual service using Request/Response pair. I am getting same error with different reasons for same Virtual Service.

     

    1. No Response Found and Timed out. Not able to access Virtual service as Txn Count didn't increased. Workstation log Error "MQJE001: Completion Code '2', Reason '2019'.

    2. No Response Found Timed out. Able to access Virtual Service . Vse log has warning "com.itko.lisa.jms.mq.MQJavaEngine - A property key was used for the MQ Security exit, but LISA found no object to use in state so skipped it."

     

    Thanks,

    -Ankush



  • 2.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 11:01 AM

    I'm a little bit confused.  You are running an IBM MQ VSE service, but you are seeing the 2019 error in Workstation when you run a test case against the VS?  When does the timeout happen?  Where exactly do you see 'No response found'?  Is the 2019 error something that pops up immediately when you run the test case in workstation or are you just noticing it in the log?  Can you provide more details on the sequence of events?  What exactly what you are doing and where exactly do you see each message or behavior happen?

     

    MQ 2019 is usually preceded by an MQ 2009 error; it typically happens when something bad happens to the socket connection to the MQ server.  The actual cause can be any number of things.

     

    "A property key was used for the MQ Security exit, but LISA found no object to use in state so skipped it.": This you can safely ignore; it's a harmless warning.



  • 3.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 11:30 AM

    Sorry For confusion.

     

    When i executed the MQ step in workstation it will give me step error with below exception.

     

    Exception Executing Messaging/ESB Step: com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2019'.

     

    Workstation.log

    2015-12-30 16:19:37,752Z (11:19) [ControlBar-Monitor] TRACE com.itko.util.AutoRefreshObject - (getObject) object=false

    2015-12-30 16:19:37,848Z (11:19) [Finalizer] ERROR System.err                     - MQJE001: Completion Code '2', Reason '2019'.

    2015-12-30 16:19:37,849Z (11:19) [Finalizer] ERROR System.err                     - MQJE001: Completion Code '2', Reason '2019'.

     

    and their is not transaction count in Virtual Service.

     

     

    Regards,

    -Ankush



  • 4.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 12:01 PM

    Does it do this every time?  Do you see any errors other than 2019 in the log?  Can you give me the full stack trace that you see in the Workstation UI, *not* the log?  Are you sure the test step is using the same connection and queue information as the virtual service? 

     

    Can you try reconfiguring your test case so it both sends to and receives from the response queue, taking the VS out of the picture temporarily?  Does that give you the same error?



  • 5.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 11:59 AM

    Hi Kevin,

     

    I had restarted the Queue Manager and Deployed Virtual service. when i had executed my MQ test Step from Workstation getting "No Response found " but in VSE server i am getting Transaction count and Transaction Id which is matched with my request values.

     

     

    MQ_Error.png

     

    VSE :-

     

    MQ_Vse.png

     

     

     

    2015-12-30 16:42:24,315Z (11:42) [PAM_Virtualization [VS_PAM_Virtualization_Run]/1] WARN  com.itko.lisa.jms.mq.MQJavaEngine - A property key was used for the MQ Receive exit, but LISA found no object to use in state so skipped it.

    2015-12-30 16:42:24,315Z (11:42) [PAM_Virtualization [VS_PAM_Virtualization_Run]/1] WARN  com.itko.lisa.jms.mq.MQJavaEngine - A property key was used for the MQ Send exit, but LISA found no object to use in state so skipped it.

    2015-12-30 16:42:24,315Z (11:42) [PAM_Virtualization [VS_PAM_Virtualization_Run]/1] WARN  com.itko.lisa.jms.mq.MQJavaEngine - A property key was used for the MQ Security exit, but LISA found no object to use in state so skipped it.

    2015-12-30 16:42:35,080Z (11:42) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Memory used 179mb, allocated 511mb, max 910mb (19%) Our cpu usage 0%, system cpu used 15% GC time 0%

    2015-12-30 16:42:35,080Z (11:42) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:42:35,080Z (11:42) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - | Name

    2015-12-30 16:42:35,080Z (11:42) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:42:35,080Z (11:42) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Virtualization: status=running, capacity=1 current tx/sec: 0 peak tx/sec: 1 errors: 0

    2015-12-30 16:42:35,080Z (11:42) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - --------------------------------------------------------------------------------------------------

    2015-12-30 16:43:05,199Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Memory used 192mb, allocated 511mb, max 910mb (21%) Our cpu usage 0%, system cpu used 18% GC time 0%

    2015-12-30 16:43:05,199Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:43:05,199Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - | Name

    2015-12-30 16:43:05,199Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:43:05,199Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Virtualization: status=running, capacity=1 current tx/sec: 0 peak tx/sec: 1 errors: 0

    2015-12-30 16:43:05,199Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - --------------------------------------------------------------------------------------------------

    2015-12-30 16:43:35,283Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Memory used 207mb, allocated 511mb, max 910mb (22%) Our cpu usage 0%, system cpu used 16% GC time 0%

    2015-12-30 16:43:35,283Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:43:35,283Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - | Name

    2015-12-30 16:43:35,283Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:43:35,283Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Virtualization: status=running, capacity=1 current tx/sec: 0 peak tx/sec: 1 errors: 0

    2015-12-30 16:43:35,283Z (11:43) [Event Sink Thread Pool Thread 3] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - --------------------------------------------------------------------------------------------------

    2015-12-30 16:44:05,372Z (11:44) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Memory used 222mb, allocated 511mb, max 910mb (24%) Our cpu usage 0%, system cpu used 15% GC time 0%

    2015-12-30 16:44:05,372Z (11:44) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:44:05,372Z (11:44) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - | Name

    2015-12-30 16:44:05,372Z (11:44) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:44:05,372Z (11:44) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Virtualization: status=running, capacity=1 current tx/sec: 0 peak tx/sec: 1 errors: 0

    2015-12-30 16:44:05,372Z (11:44) [Event Sink Thread Pool Thread 2] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - --------------------------------------------------------------------------------------------------

    2015-12-30 16:44:35,536Z (11:44) [Event Sink Thread Pool Thread 4] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Memory used 236mb, allocated 511mb, max 910mb (25%) Our cpu usage 0%, system cpu used 10% GC time 0%

    2015-12-30 16:44:35,536Z (11:44) [Event Sink Thread Pool Thread 4] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:44:35,536Z (11:44) [Event Sink Thread Pool Thread 4] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - | Name

    2015-12-30 16:44:35,536Z (11:44) [Event Sink Thread Pool Thread 4] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - ==================================================================================================

    2015-12-30 16:44:35,536Z (11:44) [Event Sink Thread Pool Thread 4] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Virtualization: status=running, capacity=1 current tx/sec: 0 peak tx/sec: 1 errors: 0

    2015-12-30 16:44:35,536Z (11:44) [Event Sink Thread Pool Thread 4] INFO  com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - --------------------------------------------------------------------------------------------------

     

     

    Regards,

    -Ankush



  • 6.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 12:02 PM

    Okay, I'm confused again.  Were you getting the 2019 error before you restarted the queue manager and VSE server?  Are you still getting it now?



  • 7.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 12:12 PM

    After restarting i am not getting error 2019.



  • 8.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 12:26 PM

    Okay.  So your problem is that the VSE service appears to be responding but your test case is not receiving the response?

     

    So, from your first screenshot it doesn't look like the test case is actually timing out.  Its response time is given as 1123ms, so unless you changed the timeout to 1 second then it's receiving *something*.  However, the 'Step Response' event is set to 'null'.  It looks like the test case is receiving a response message with an empty message body.  Sometimes the old IBM MQ step simply treats that the same as a timeout.  From your second screenshot it looks like the VSE service found a match for the request.

     

    Are you sure the VSE actually contains a non-empty response for that request?  If you go into the test case and uncheck 'Use payload as last response' (not sure of the exact wording), then does that remove the 'no response' error?

     

    Have you tried running just the receive side of the test case over and over until it actually *does* time out, just to make sure that the response queue is empty before you send your request?



  • 9.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 12:22 PM

    Hi Kevin,

     

    After 5-10 tries i am start getting this error in my MQ test Step.

     

    ============================================================================

    | Exception Executing Messaging/ESB Step: com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2085'.

    ============================================================================

    | Step:        MQ SOURCEs publish

    ----------------------------------------------------------------------------

    | Message:     MQJE001: Completion Code '2', Reason '2085'.

    ----------------------------------------------------------------------------

    | Trapped Exception: MQJE001: Completion Code '2', Reason '2085'.

    | Trapped Message:   com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2085'.

    ----------------------------------------------------------------------------

    STACK TRACE

    com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2085'.

      at com.ibm.mq.MQDestination.open(MQDestination.java:335)

      at com.ibm.mq.MQQueue.<init>(MQQueue.java:251)

      at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:2786)

      at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:2813)

      at com.itko.lisa.jms.mq.MQJavaEngine.accessQueue(MQJavaEngine.java:595)

      at com.itko.lisa.jms.mq.MQJavaEngine.getPublishQueue(MQJavaEngine.java:539)

      at com.itko.lisa.jms.mq.MQJavaEngine.commonPrepare(MQJavaEngine.java:214)

      at com.itko.lisa.jms.mq.MQJavaEngine.prepare(MQJavaEngine.java:155)

      at com.itko.lisa.jms.JMSNode.openExec(JMSNode.java:1634)

      at com.itko.lisa.jms.JMSNode.execute(JMSNode.java:1897)

      at com.itko.lisa.test.TestNode.executeNode(TestNode.java:973)

      at com.itko.lisa.test.TestCase.execute(TestCase.java:1230)

      at com.itko.lisa.test.TestCase.execute(TestCase.java:1145)

      at com.itko.lisa.test.TestCase.executeNextNode(TestCase.java:1130)

      at com.itko.lisa.editor.WalkThruPanel.prepAndExecNode(WalkThruPanel.java:1048)

      at com.itko.lisa.editor.WalkThruPanel.access$900(WalkThruPanel.java:68)

      at com.itko.lisa.editor.WalkThruPanel$10.doCallback(WalkThruPanel.java:961)

      at com.itko.util.swing.panels.ProcessingDialog$2.run(ProcessingDialog.java:194)

      at java.lang.Thread.run(Unknown Source)

    ============================================================================

     

     

    Regards,

    -Ankush



  • 10.  Re: MQ Virtualization Error "MQJE001: Completion Code '2', Reason '2019'"

    Posted Dec 30, 2015 12:28 PM

    MQ 2085 usually means you have specified a queue name that does not exist in the MQ server.  I don't know why this would suddenly fail if you haven't changed anything.  Are you sure your MQ server is stable?