On 9/12/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> Can you post a thread dump? I think you can get one by hitting
> control-shift-|, although I always end up hitting two or three things
> before getting it.
Thanks, I didn't know how to do that on my Mac.
Below is the stack for each thread:
^\Full thread dump Java HotSpot(TM) Client VM (1.5.0_07-87 mixed mode, sharing):
"Low Memory Detector" daemon prio=5 tid=0x00509190 nid=0x1814c00
runnable [0x00000000..0x00000000]
"CompilerThread0" daemon prio=9 tid=0x00508790 nid=0x1814800 waiting
on condition [0x00000000..0xb0b0674c]
"Signal Dispatcher" daemon prio=9 tid=0x00508280 nid=0x1803e00 waiting
on condition [0x00000000..0x00000000]
"Finalizer" daemon prio=8 tid=0x005079c0 nid=0x1810c00 in
Object.wait() [0xb0a04000..0xb0a04d10]
at java.lang.Object.wait(Native Method)
- waiting on <0x0ccfadd8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0x0ccfadd8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x005075c0 nid=0x180fe00 in
Object.wait() [0xb0983000..0xb0983d10]
at java.lang.Object.wait(Native Method)
- waiting on <0x0ccfae58> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x0ccfae58> (a java.lang.ref.Reference$Lock)
"main" prio=5 tid=0x00501650 nid=0x1804a00 runnable [0xb07ff000..0xb08000dc]
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at serp.util.Strings.toClass(Strings.java:162)
at serp.util.Strings.toClass(Strings.java:108)
at serp.bytecode.TypedInstruction.getType(TypedInstruction.java:76)
at serp.bytecode.LoadInstruction.isThis(LoadInstruction.java:164)
at org.apache.openjpa.enhance.PCEnhancer.findField(PCEnhancer.java:718)
at
org.apache.openjpa.enhance.PCEnhancer.getAssignedField(PCEnhancer.java:675)
at
org.apache.openjpa.enhance.PCEnhancer.validateProperties(PCEnhancer.java:593)
at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:444)
at org.apache.openjpa.enhance.PCEnhancer.run(PCEnhancer.java:4342)
at
org.apache.openjpa.ant.PCEnhancerTask.executeOn(PCEnhancerTask.java:89)
at
org.apache.openjpa.lib.ant.AbstractTask.execute(AbstractTask.java:172)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.Main.runBuild(Main.java:698)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
"VM Thread" prio=9 tid=0x00506db0 nid=0x180fa00 runnable
"VM Periodic Task Thread" prio=9 tid=0x00509cf0 nid=0x1815000 waiting
on condition
"Exception Catcher Thread" prio=10 tid=0x005018a0 nid=0x1804e00 runnable
>
> -Patrick
>
> On 9/11/07, Dave <[EMAIL PROTECTED]> wrote:
> > I'm trying to upgrade the Roller 4.0 code base from OpenJPA 0.9.7 to
> > OpenJPA 1.0 but I'm running into a blocking issue.
> >
> > The <openjpac> task that we use to enhance our POJOs is locking up
> > during the build process. There are no error messages or stack traces,
> > but the CPU goes to about 98% (on my core duo MacBook pro) and Ant
> > just hangs.
> >
> > Any hints on how I could debug this problem?
> >
> > - Dave
