Hehe, you cannot afford our rates so you expect us to answer your question for free :-)
I'd suggest you write some stress tests. RequiresNew and select for update
sounds like a deadlock situation in the database under load to me.
Actually, we had done the load testing so we were very confident it wasn't a true locking issue. As it turns out it was something about the fact that the db was UNIX. The whole setup works fine if the DB is simply switched to a Windows server. Maybe it's time for me to move over to an Oracle forum, but does anyone here know if there would be different Oracle drivers required when talking to an Oracle db on HPUX?
Why is every bean's ejb transaction attribute set to "RequiresNew"? If one bean calls another bean you now have two DB transactions open - increasing the potential for a deadlock. Are you sure a "Required" transaction setting is not enough?