-
1. Re: MDB instansiation...
pra Sep 14, 2001 2:42 AM (in response to lolsson)It would be interesting to see the results if you increase the number of times you send a message. 100 happends to equals the default instance pool size, so what you might see is the instance pool filling up.
//Peter -
2. Re: MDB instansiation...
lolsson Sep 14, 2001 10:05 AM (in response to lolsson)I let the client send 1000 messages with a two second
delay between each messsage, This led to:
1) 1001 calls to ejbCreate()
2) 1000 calls to onMessage()
3) Zero calls to ejbRemove()
In a similar experiment the client sent 2460 messages
with a one second delay between messages.
This led to:
1) 2461 calls to ejbCreate()
2) 2460 calls to onMessage()
3) Zero calls to ejbRemove()
Lars -
3. Re: MDB instansiation...
pra Sep 17, 2001 2:53 PM (in response to lolsson)Hi,
I have checked it somewhat more and I am now inclined to consider this a bug. It was introduced between 2.4.0 and 2..4.1 by some changes to the instance pool code where instances should actually never be pooled.
There seems to not be total agreement if this is a bug or not on the dev mailinglist, so we will see how this will end.
//Peter -
4. Re: MDB instansiation...
pra Sep 21, 2001 3:09 AM (in response to lolsson)It should be fixed now in the 2.4.1 cvs tree.
//Peter