Hello,
One way we launch our eclipse is in a headless mode (no UI) for command
line execution support. Shortly after process startup we experience
OutOfMemoryError. This is running on Windows 7. The relevant stack trace
for the current thread is shown below. Any ideas why this is happening?
Thanks,
Kevin
0SECTION THREADS subcomponent dump routine
NULL =================================
NULL
1XMPOOLINFO Thread pool info:
2XMPOOLTOTAL Current total number of threads: 56
NULL
1XMCURTHDINFO Current thread
NULL ----------------------
3XMTHREADINFO "qtp879320118-90" J9VMThread:0x90D0EB00,
j9thread_t:0x90D084DC, java/lang/Thread:0x9AE3D9D8, state:R, prio=5
3XMTHREADINFO1 (native thread ID:0x6239, native priority:0x5,
native policy:UNKNOWN)
3XMTHREADINFO2 (native stack address range from:0x90C7E000,
to:0x90CBF000, size:0x41000)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at
java/util/concurrent/locks/AbstractQueuedSynchronizer
$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1868)
4XESTACKTRACE at
java/util/concurrent/locks/AbstractQueuedSynchronizer
$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2084)
4XESTACKTRACE at
org/eclipse/jetty/util/BlockingArrayQueue.poll(BlockingArrayQueue.java:337)
4XESTACKTRACE at
org/eclipse/jetty/util/thread/QueuedThreadPool.idleJobPoll
(QueuedThreadPool.java:517)
4XESTACKTRACE at
org/eclipse/jetty/util/thread/QueuedThreadPool.access$600
(QueuedThreadPool.java:39)
4XESTACKTRACE at
org/eclipse/jetty/util/thread/QueuedThreadPool$3.run
(QueuedThreadPool.java:563)
4XESTACKTRACE at java/lang/Thread.run(Thread.java:777)
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users
