We are implementing a WebSphere Message Broker v8 solution on AIX environment. Our issue is that whenever a request comes to the mapping node, mapping node takes a lot of time to process the request. Please note that this happens for the first request only. After that it processes the request very fast.
Kindly note that each time when a execution group is reloaded and / or a new deployment takes place, this issue occurs for the first request.
This is very critical as we will be integrating channels like ATM and POS machines where this might cause a SLA failure.
Would appreciate your help in this regards.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-02-05T00:03:49Z by email@example.com
Pinned topic WebSphere Message Broker v8 issue with mapping node
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-05T00:03:49Z at 2013-02-05T00:03:49Z by firstname.lastname@example.org
email@example.com 120000CJSH515 PostsACCEPTED ANSWER
Re: WebSphere Message Broker v8 issue with mapping node2013-02-05T00:03:49Z in response to FurqanBaqaiI think this is 'working as designed'. One obvious solution is push a few messages through the flow(s) after deploying them. You could put it into the scripts that do the deployment.