Issues with multiple cartridges
edited Feb 11, 2012 5:13PM in Order and Service Management (Communications Industry) (MOSC) 2 commentsAnswered
If we do not undeploy the old cartridges due to wanting to retain the old orders, then we are accumulating a lot of Ear files from every version of deployment in weblogic. This is creating a huge JNDI tree in the managed server. this could be consuming a lot of memory as well as making restarts of server even longer.
could you advise how we can avoid this situation whereby we have frequent deployments of new code baselines but we need to retain orders for a long duration in the past.
we cannot undeploy the old cartridge versions as we will lose the old orders but then again we are accumulating so many .ear files in the weblogic deployments which we fill is impacting the JVM and memory.
could you advise how we can avoid this situation whereby we have frequent deployments of new code baselines but we need to retain orders for a long duration in the past.
we cannot undeploy the old cartridge versions as we will lose the old orders but then again we are accumulating so many .ear files in the weblogic deployments which we fill is impacting the JVM and memory.
0