Too many open cursers for osm rule engine
edited Feb 16, 2012 5:41AM in Order and Service Management (Communications Industry) (MOSC) 3 commentsAnswered
Hi,
Problem with many open cursors happened after customer increased oms_pool Initial Capacity to 50 connections and EC_OM_Datasource value to 30. Earlier they were 15 ( default ) and 1 respectively.
The reason for customer changed the values was, in coming months they were expecting a lot of order volume through OSM and they planned to increase oms.web and oms.automation thread counts. Since they faced some issues they increased the Initial Capacity.
The customer question is why on increasing the Initial Capacity the cursors were not closing even though it is possible that not all connections were active.
After the connection pools were decreased again everything works as usual.
Problem with many open cursors happened after customer increased oms_pool Initial Capacity to 50 connections and EC_OM_Datasource value to 30. Earlier they were 15 ( default ) and 1 respectively.
The reason for customer changed the values was, in coming months they were expecting a lot of order volume through OSM and they planned to increase oms.web and oms.automation thread counts. Since they faced some issues they increased the Initial Capacity.
The customer question is why on increasing the Initial Capacity the cursors were not closing even though it is possible that not all connections were active.
After the connection pools were decreased again everything works as usual.
0