[cmcintos]

Hi,

We run bulk plan just fine and then all of a sudden we get the following errors. Can't find where this limit of 50 active beans is at to change it. Any clue from the group?

2008-06-16 14:19:01.279 41732 Error Exception Generic_Remote_Exception
weblogic.ejb20.cache.CacheFullException: Cache 'ejb.BulkPlan(Application:
GC3App, EJBComponent: BulkPlan.jar)' is at its limit of: 50 *active*
beans.

weblogic.ejb20.cache.CacheFullException: Cache 'ejb.BulkPlan(Application: GC3App, EJBComponent: BulkPlan.jar)' is at its limit
of: 50 *active* beans.
at weblogic.ejb20.cache.NRUCache.getFreeNode(NRUCache .java:242)
at weblogic.ejb20.cache.NRUCache.put(NRUCache.java:33 2)
at weblogic.ejb20.manager.ExclusiveEntityManager.getR eadyBean(ExclusiveEntityManage
r.java:300)
at weblogic.ejb20.manager.ExclusiveEntityManager.preI nvoke(ExclusiveEntityManager.j
ava:246)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(Ba seEJBObject.java:137)
at weblogic.ejb20.internal.EntityEJBObject.preInvoke( EntityEJBObject.java:89)
at glog.ejb.bulkplan.ejb_BulkPlan_odnke0_EOImpl.getBu lkPlanGid(ejb_BulkPlan_odnke0_
EOImpl.java:72
at glog.server.workflow.adhoc.BulkPlanResultsCleanup. execute(BulkPlanResultsCleanup
.java:52)
at glog.server.workflow.SimpleWorkflow.execute(Simple Workflow.java:23)
at glog.server.workflow.WorkflowSessionBean.execute(W orkflowSessionBean.java:64)
at
glog.server.workflow.WorkflowSessionServerSideEJBW rapper.execute(WorkflowSession
ServerSideEJBWrapper.java:32)
at glog.server.workflow.WorkflowSessionServerSideEJBW rapper_61kh96_EOImpl.execute(W
orkflowSessionServerSideEJBWrapper_61kh96_EOImpl.j ava:20
at glog.server.workflow.WorkflowManager.execute(Workf lowManager.java:341)
at glog.server.workflow.Trigger.trigger(Trigger.java: 123)
at glog.util.event.MemoryEventQueueRunnable.processEv ent(MemoryEventQueueRunnable.j
ava:141)
at glog.util.event.MemoryEventQueueRunnable.run(Memor yEventQueueRunnable.java:96)
at glog.util.event.EventThread.run(EventThread.java:8 2)
at java.lang.Thread.run()V(Unknown Source)
[batch - 1]

[Srivathsana]

Hi,

I hope this creeps up when the number of BPs are more.Seems that your BeanCache for BulkPlan has a maximum capacity of 50.Increasing the capacity of the cache should help here.Please try this and repost if you still face issues..

[cmcintos]

Yes I did that already and we don't see that error anymore. Another odd thing we do see is
We get no errors yet bulk plan fails to plan logged in to domain B.
Then I login to domain A plan the exact same order releases from domain B, use the parameter set defined in domain B and we get a shipment built. Then I delete the shipment built while logged into domain A and redo the same thing in domain B. Bulk plan works as expected.

When bulk plan stops working in domain B, I run bulk plan in any other domain, then I can go back to the right domain (B) and plan shipments again. I'm stumped on this one.
Still seams a caching issue out there somewhere

[Srivathsana]

If your workflow involves setting some constraints in the OR through an agent of different data query type using data type association before it is sent for a BulkPlan,this scenario is very much possible.We have also had such an instance where our Bulkplan required more than an iteration to plan our ORs..
The workaround we did was,we moved all the related updates into an OrderRelease agent which was previuosly done by an agent of a different data query type using data type association and we were able to overcome the cache issue to enable our BulkPlan plan the ORs in the first go itself..
Please let me know it this relates to you..

[cmcintos]

First suggestion didn't work cause then we hit the max of 5000 and I didn't attempt any change to agents. It mysteriously isn't being encountered anymore.