The integration server XPath cache size might become a performance bottleneck for customers who use many XPath expressions. Altering the size of the XPath cache might improve message flow performance.
An integration server (or 'execution group' in WebSphere® Message Broker Version 8.0 and earlier versions) keeps a cache of compiled XPath expressions to help reduce the processor usage of parsing and re-creating XPath expressions that are used repeatedly during message flow execution. This cache is shared by all message flows within an integration server. The default size of this cache is 10000 elements, and this is expected to be sufficient for most customer configurations.
mqsireportproperties <INode> -e default -o ComIbmXPathCache -r
where <INode> is your integration node. The following output is an example of that returned from the command:ComIbmXPathCache
uuid='ComIbmXPathCache'
userTraceLevel=''
traceLevel=''
userTraceFilter=''
traceFilter=''
vrmfIntroducedAt=''
resourceGroup=''
maximumSize='10000'
minimumSize='6000'
currentSize='0'
mqsireportproperties <INode> -e default -o ComIbmXPathCache -n maximumSize -v 20000.
mqsireportproperties <INode> -e default -o ComIbmXPathCache -n minimumSize -v 1000.
The currentSize property reports the number of compiled XPath expressions that are stored in the XPath cache. This property is read-only, and must not be set with the mqsichangeproperties command.