C:\Apache\geronimo\trunk>java -version java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing)
Paul discovered that it has to do with our EjbRefBuilder http://www.nabble.com/forum/ViewPost.jtp?post=8890983&framed=y And then on IRC, Dain had a comment for the above mail- (see transcript at19:25) http://servlet.uwyn.com/drone/log/bevinbot/geronimo/20070209 Cheers Prasad On 2/10/07, Kevan Miller <[EMAIL PROTECTED]> wrote:
On Feb 9, 2007, at 5:09 PM, Prasad Kashyap wrote: > On 2/9/07, Jacek Laskowski <[EMAIL PROTECTED]> wrote: >> On 2/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> > Author: prasad >> > Date: Fri Feb 9 13:52:23 2007 >> > New Revision: 505518 >> > >> > URL: http://svn.apache.org/viewvc?view=rev&rev=505518 >> > Log: >> > * removed persistence-context-type. transaction is implied >> >> Did it cause any troubles? I wonder whether it could or not and don't >> mind it's removed. > > Well, I got a deployment exception when it was there. Apparently, in > the new schema, "Transactional" is not one of the enumeration > elements. Also, if the value is not "extended", then transaction is > implied. > > So after I removed it, the deployment went further ahead. It failed > later with the OutOfMemoryError, a different problem all together. A general note about OOME's. Sun's JRE had a problem with leaking ClassLoaders. The problem is fixed in the 1.5.0_10 version of the JRE. In versions prior to this, you'll leak a ClassLoader and associated Classes on every undeploy. Eventually, you'll run out of PermGen space. --kevan
