DipatchPolicy

Question

I am trying to use the dipatchPolicy option for my ejb's in order to improve performance. Here is the scenario that I am trying to execute:
A java client app (started from its own jvm) invokes an EJB on my wl-server. This EJB in turn uses a bunch of other EJB's and some regular java classes (helper classes) to do the task. The starting point into the wl-server is a java class, followed by a session-EJB, and then a couple of session-EJB's and helper classes, and some CMP Entity-EJBs.
I have compiled all my session-EJB's that come in the execution-path with "-dispatchPolicy myExecuteQ" flag. The entity beans however go against the default execute Q. When I run the client, I notice that all the work is getting done by the default Q threads, and myExecuteQ threads never get used.
Can someone tell what am I doing wrong.
Thanks,
Praveen.

Answer 1

I think that request is assigned to an execute queue when it first arrives - it
will not be changed after that.
Praveen Verma <[email protected]> wrote:
I am trying to use the dipatchPolicy option for my ejb's in order to improve performance. Here is the scenario that I am trying to execute:
A java client app (started from its own jvm) invokes an EJB on my wl-server. This EJB in turn uses a bunch of other EJB's and some regular java classes (helper classes) to do the task. The starting point into the wl-server is a java class, followed by a session-EJB, and then a couple of session-EJB's and helper classes, and some CMP Entity-EJBs.
I have compiled all my session-EJB's that come in the execution-path with "-dispatchPolicy myExecuteQ" flag. The entity beans however go against the default execute Q. When I run the client, I notice that all the work is getting done by the default Q threads, and myExecuteQ threads never get used.
Can someone tell what am I doing wrong.
Thanks,
Praveen.--
Dimitri