Hi PIKU, XU connection manager is full issue occurs usually when the ruleset is too large and the threads are overloaded, essentially usage is greater than CPU allocated. Below changing the allocated value to a extremely lower amount , you can generate this error in the ra.xml file from the DecisionService.war
Inside the ra.xml, these are the parameters you should be concerned about:
<config-property>
<config-property-name>defaultConnectionManagerProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>pool.maxSize=480,pool.waitTimeout=-1</config-property-value>
</config-property>
<config-property>
<config-property-name>documentBuilderPoolProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>pool.maxSize=120,pool.waitTimeout=-1</config-property-value>
</config-property>
<config-property>
<config-property-name>transformerPoolProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>pool.maxSize=120,pool.waitTimeout=-1</config-property-value>
</config-property>
You can also check how much CPU, you have available and adjust accordingly too:
The interesting part is the "Cache" tab in the XU dump.
So you
- Open the RES Console => "Server Info" tab.
- You set the "Log Level" to "Debug" in "Server Info"
- You click on the corresponding server in the "Execution Unit(s)" list.
- You click on the "View" in the "Execution Unit Dump"
------------------------------
Aaron Chen
------------------------------
Original Message:
Sent: Fri December 16, 2022 12:37 AM
From: PIKU Queen
Subject: Xu Connection manager is full
Hi ,
is there a way we can generate. XU connection manager is full issue , how we can produce this error to occur ? What are the changes required ??
Thanks
Piku
------------------------------
PIKU Queen
------------------------------