WRT the last message - could multithreading on the client side be
the problem?  I have several session beans that execute lengthy database
queries.  I kick off searches on 3 of them in different threads.  When the
first returns (others are still running), I call another method on it, and
it blows up (that is, the Method parameter is null on the server side as
per my last message).  I know multithreading is a no-no in the EJBs
themselves.  Is there a problem with a multithreaded client?

Thanks,
        Aaron


Reply via email to