For the purely stateless stuff I would tend to agree.
it is the entity that was the problem.
marcf
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Wednesday, September 19, 2001 1:15 PM
|To: [EMAIL PROTECTED]
|Subject: [JBoss-dev] Re: [JBoss-user] How does JBoss do Stateless
|Session Beans?
|
|
|We should restore pooling of stateless session beans and message driven
|beans. If such beans perform any non-trivial initialization during
|ejbCreate
|for use across stateless methods we are killing the performance of the bean
|and wasting these resources.
|
|----- Original Message -----
|From: "Sacha Labourey" <[EMAIL PROTECTED]>
|To: <[EMAIL PROTECTED]>; "Jboss-Dev"
|<[EMAIL PROTECTED]>
|Sent: Wednesday, September 19, 2001 7:23 AM
|Subject: RE: [JBoss-user] How does JBoss do Stateless Session Beans?
|
|
|> Hello Olivier,
|>
|> For various reason, mainly the highly added complexity when synchronising
|> entity beans, the pool has been modified by ... not pooling i.e. the
|> pool.free method instead pushes a new fresh instance on the pool stack.
|> Consequently, the current code will call ejbRemove *only* when
|your server
|> is under high load and it needs to free instances that cannot fit on the
|> stack size. In this case, discard(ctx) is called and make appropriate
|calls.
|>
|> But I agree that the code sould be modified to either:
|> - really pool SLSB (and only SLSB)
|> - or correctly call ejbRemove on the SLSB
|>
|> Any opinion?
|>
|> Cheers,
|>
|>
|>
|> Sacha
|>
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
