This is a known problem with the 2.4-CR3 release of Portal when run with MySQL. You can either go back to the CR2 release or wait for the fix in CR4. See here for details:
Thanks, I didn't see that post. Has it been fixed in cvs yet?
Well, I am not sure that this is the final word here.
I am running portal 2.6.2-GA on JBoss AS 4.2.1-GA and I get exactly the same in the server log, plus plenty of trouble in consequence.