Jeff, What aspect of OPENJPA-258 are you experiencing? The OOME? Does your scenario mimic the scenario in 258, or something similar? Or, is there some other aspect of 258 that you are referring to?
It's interesting that the scenario described in 258 was not resolved until 1.0.2. And, since you just moved to 1.0.2 and are now experiencing the "same problem" that was supposedly fixed in 1.0.2, then I wonder whether we are talking about the same problem. You mention the IBM JDK. Are you indicating that the problem does not surface with the Sun JDK? That should be a relatively simple verification. I switch back and forth between the IBM and Sun JDK's all the time. If you can provide more details on the specific problem and environment for your scenario, then we can hopefully help narrow down the problem and get it resolved. Thanks. Kevin On Tue, Mar 4, 2008 at 11:42 AM, Jeff Melching <[EMAIL PROTECTED]> wrote: > I tried to upgrade my application to the 1.0.2 release from 1.0.1 and I am > now seeing the exact behavior listed in > https://issues.apache.org/jira/browse/OPENJPA-258. > > I am however using an ibm jvm not sun. I ran the main method from the > sample attached to the jira item using 1.0.2 and my ibm jvm and received > matching behavior to my application. Could we get this fixed for ibm's > jvm as well? > > I tried 2 different ibm jvm's. > > java version "1.5.0" > > Java(TM) 2 Runtime Environment, Standard Edition (build > pxi32devifx-20070806 (SR5a)) > > IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 > j9vmxi3223-20070426 (JIT enabled) > > J9VM - 20070420_12448_lHdSMR > > JIT - 20070419_1806_r8 > > GC - 200704_19) > > JCL - 20070725 > > java version "1.5.0" > > Java(TM) 2 Runtime Environment, Standard Edition (build > pxi32devifx-20071025a (SR6b)) > > IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 > j9vmxi3223-20071005 (JIT enabled) > > J9VM - 20071004_14218_lHdSMR > > JIT - 20070820_1846ifx1_r8 > > GC - 200708_10) > > JCL - 20071025 > > > >
