Frank Sauer wrote:
>
> According to the EJB 1.1 spec the container is *supposed* to
> throw an exception on the 2nd-Nth re-entrant call. Apparently
> not all vendors are compliant yet.
>
> We ran into this problem (Gemstone is compliant and throws the exception)
> and solved it by creating a session pool on the client side.
Thoughts:
- isn't this adding complexity?
- your connection pool is exactly what we did for JDBC connection pooling
prior to appserver managed DB pooling.
- my threaded (pre-existing) client needs serveral 100 handles to mySBObject.
Without concurrent access, I need to myHome.create("myName"); in each
thread's startup. This is very expensive and big hit on the server.
What's a better pattern for performance?
Thanks
curt
Curt Smith
[EMAIL PROTECTED]
(w) 404-237-1166 x182
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
