AnsweredAssumed Answered

Migration of IBM MQ Series (deprecated) VSI to IBM MQ Native - not working

Question asked by DevTestUser on Aug 9, 2016
Latest reply on Aug 12, 2016 by Kevin.Bowman

Hi  Kevin.Bowman, we are migrating MQ virtual service from IBM MQ Series (Deprecated) to IBM MQ Native.. I am successfully able to develop MQ VS in native method and it works fine.. integrated with SOAP based client and tested too. However, we also need to migrate the existing  MQ VSI (old mq vsi) which was created in previous mq method (i.e., IBM MQ Series) to work with latest new MQ model..  what I have done is pointed to old vsi from new model and copied all data filters which were added in previous model listen step to new model listen step.. Whenever I test it through my soap call, mq service fails and this is the error description I could see in DevTest Server console..

 

2 AE6E69395A2511E6ACC9E22C20524153 5D62E4815E5211E6A94C005056803F17 5D51F4755E5211E6A94C005056803F17 MQ1 [VS_MQ1_Run] local 1 0 0 1 /home/lisa/lisatmp_8.3.0/lads/5D51F4755E5211E6A94C005056803F17/IBMMQ_native/Configs/LISA4-QUEUE-ST.config     1470761852847 2016-08-09 17:57:32 1470761857339 2016-08-09 17:57:37 false         abort     AE6E693F5A2511E6ACC9E22C20524153     1470761857339     2016-08-09 17:57:37     5D51F4755E5211E6A94C005056803F17     Test Aborted     5D62E4815E5211E6A94C005056803F17     2     0     0                     S         lisa.abort.rsp.time         0         1470761857339                                           Respond     null     1470761857330     2016-08-09 17:57:37     5D51F4755E5211E6A94C005056803F17     IBM MQ Native VSE Respond     5D62E4815E5211E6A94C005056803F17     2     8     0                     S         lisa.Respond.rsp         ============================================================================ | Exception: ============================================================================ | Message:     Value for Sender was null ---------------------------------------------------------------------------- ============================================================================         1470761857338                       S         lisa.Respond.rsp.time         8         1470761857338                                      62         1470761857339         17:57:37         Finished transaction processing         Ending         5D51F4755E5211E6A94C005056803F17                                      Respond : ============================================================================ | Value for Sender was null ============================================================================ | Step:        Respond ---------------------------------------------------------------------------- | Message:     Value for Sender was null ---------------------------------------------------------------------------- | Trapped Exception: Value for Sender was null | Trapped Message:   ============================================================================ | Exception: ============================================================================ | Message:     Value for Sender was null ---------------------------------------------------------------------------- ============================================================================ ---------------------------------------------------------------------------- STACK TRACE ============================================================================ | Exception: ============================================================================ | Message:     Value for Sender was null ---------------------------------------------------------------------------- ============================================================================ at com.itko.lisa.asset.spec.SpecStringPayload.getValueInstance(SpecStringPayload.java:84) at com.itko.lisa.asset.spec.SpecStringPayload.getValueInstance(SpecStringPayload.java:33) at com.itko.lisa.messaging.builder.AbstractMultiSendOperation.getSendOperations(AbstractMultiSendOperation.java:318) at com.itko.lisa.messaging.builder.AbstractMultiSendOperation.doPreEvaluate(AbstractMultiSendOperation.java:360) at com.itko.lisa.asset.operation.AbstractRuntimeOperation.evaluate(AbstractRuntimeOperation.java:80) at com.itko.lisa.asset.operation.AbstractOperationStep.execute(AbstractOperationStep.java:146) at com.itko.lisa.asset.operation.AbstractOperationStep.execute(AbstractOperationStep.java:109) at com.itko.lisa.messaging.vse.AbstractVseRespondStep.execute(AbstractVseRespondStep.java:87) at com.itko.lisa.test.TestNode.executeNode(TestNode.java:981) at com.itko.lisa.test.TestCase.execute(TestCase.java:1280) at com.itko.lisa.test.TestCase.execute(TestCase.java:1195) at com.itko.lisa.test.TestCase.executeNextNode(TestCase.java:1180) at com.itko.lisa.test.TestCase.executeTest(TestCase.java:1124) at com.itko.lisa.coordinator.Instance.run(Instance.java:204) ============================================================================          E          5D51F4755E5211E6A94C005056803F17          1470761857338               

 

  I think the issue is because of request meta data or response meta data ? but not getting exactly which parameter is causing this issue.. there are close to 50 parameters in meta data section so not sure.. I have attached new MQ VSM, new MQ VSI , old MQ VSI.. You can see new MQ VSI and old MQ VSI responses are 100% same apart from metadata section which is something new mq model generated..

 

thanks for help

Outcomes