Process goes over 4GB RAM occupation and then crashes, because of Product Promotion caching.
We experienced in a couple of Siebel implementation the following behaviour:
We have a root product and lots of different promotions the user can select and apply. The object manager involved in the process ( either EAI or Remote Configurator ) save in the cache the selected promotions improving performances in the subsequents selections but causing also the increase of his RAM occupation.
If it is not restarted after a while the RAM occupation goes up the 4GB limit and the process crash.
Now we need to accomplish a new requirement where the number of promotions could be very high. How we can avoid then a daily crash of the components?
We have a root product and lots of different promotions the user can select and apply. The object manager involved in the process ( either EAI or Remote Configurator ) save in the cache the selected promotions improving performances in the subsequents selections but causing also the increase of his RAM occupation.
If it is not restarted after a while the RAM occupation goes up the 4GB limit and the process crash.
Now we need to accomplish a new requirement where the number of promotions could be very high. How we can avoid then a daily crash of the components?
0