Hey
"Lahooti, Hamid" wrote:
> > >Which EJB-server does this? I would consider this to be buggy behaviour.
> >> This behaviour is exhibited by WebLogic Server 4.5.1 but I don't agree
> >> it is necessarily a bug as the ejb spec does not require the server
> >> to maintain the association between ejb object and the bean instance
> >> other than for the duration of a transaction. At least, that's my
> >> understanding.
>
> >It is not "a bug" perhaps, but it would be rather dumb.
> It's not that dumb. The container cannot afford to keep every
> bean instance that it creates, active. It's easy keeping the
> ejb objects, they do not have state.
It should be able to afford to keep a specified number of instances
alive in a so-called active pool. In WLS 4.5.1 you can set the size of
this pool with the "maxBeansInCache" setting.
If a server does not have this functionality the performance would be
rather bad because unnecessary activation/passivation would occur.
> >And no, WLS 4.5.1 does not behave like this.
> I can produce the above behaviour with WLS 4.5.1 by making
> consecutive calls to findByPrimaryKey with different keys
> in separate transactions. The same bean instance will be
> associated with different primary keys (i.e. ejb objects)
Not sure what you mean here. The issue was if instances were passivated
after each transaction or not. Your above use-case does not show this.
Can you give an exact sequence of calls, and where the corresponding
activation/passivation occurs?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
