EAI JMS Transport BS- Cache flag set to N
Hi,
We have a couple of JMS inbound request (no outbound services). We have to restart JMS components everytime middleware was restarted. To avoid this, we were suggested to unset the Cache flag on the EAI JMS Transport service. With this change, connectin issue is resolved. I mean, we no more need to restart JMS components when middleware system restarts.
Question: What will be the impact in removing the cache on EAI JMS Transport business service on the JMS inbound service calls? will there be any performance impact since its not cached anymore, everytime request has to look for JMS parameters etc. How can I verify the behavior (is there any phrase to lookup in logs).. please suggest.