|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Lennart Petersson
|Sent: Friday, July 06, 2001 4:21 AM
|To: [EMAIL PROTECTED]
|Subject: SV: [JBoss-dev] Any problems vith the cache in 2.4?
|
|
|Hi! Problem 1 solved by you Vincent - that was the missing
|toString() method in the PK class (Should that really matter, why
|are JBoss using it in the cache?).
that is not correct, we create a "safe" cache key so something is really
spooky
marcf
|
|Problem 2 was no problem, it was the old EJBDoclet passivate bug.
|The erroneous component was not regenerated with a corrected
|EJBDoclet (it was not my component :)
|
|So that mean that all you guys can keep on with 3.0 :-)
|
|THANKS!
|
|/Lennart
|
|----- Original Message -----
|From: Vincent Harcq <[EMAIL PROTECTED]>
|To: <[EMAIL PROTECTED]>
|Sent: Friday, July 06, 2001 9:05 AM
|Subject: RE: [JBoss-dev] Any problems vith the cache in 2.4?
|
|
|> Can you try this:
|> 1. Solution 1
|> Add a toString to your PK (hack entitypk.j).
|> Also put your Cache size very high.
|> And your overager periods very high as well.
|> 2. Solution 2.
|> Set your cache size to 1/1 (min/max)
|>
|> Let us know please.
|> Vincent.
|>
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
