ad(BufferedInputStream.java:280)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:295)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:287)
             at allaire.jrun.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:305)
             at
allaire.jrun.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:173)
             at
allaire.jrun.jrpp.ProxyService.swapRunnable(ProxyService.java:48)
             at allaire.jrun.ThreadPool.swapRunnable(ThreadPool.java:223)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:77)
     
     "jcp-74" prio=5 tid=0x7f18b0 nid=0x133 runnable [0xccdc0000..0xccdc09e0]
             at java.net.SocketInputStream.socketRead(Native Method)
             at java.net.SocketInputStream.read(SocketInputStream.java:86)
             at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
             at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
             at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:295)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:287)
             at allaire.jrun.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:305)
             at
allaire.jrun.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:173)
             at
allaire.jrun.jrpp.ProxyService.swapRunnable(ProxyService.java:48)
             at allaire.jrun.ThreadPool.swapRunnable(ThreadPool.java:223)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:77)
     
     "jcp-73" prio=5 tid=0x96120 nid=0x132 runnable [0xcce80000..0xcce809e0]
             at java.net.SocketInputStream.socketRead(Native Method)
             at java.net.SocketInputStream.read(SocketInputStream.java:86)
             at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
             at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
             at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:295)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:287)
             at allaire.jrun.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:305)
             at
allaire.jrun.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:173)
             at
allaire.jrun.jrpp.ProxyService.swapRunnable(ProxyService.java:48)
             at allaire.jrun.ThreadPool.swapRunnable(ThreadPool.java:223)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:77)
     
     "jcp-72" prio=5 tid=0x4bb3e0 nid=0x131 runnable [0xcd6bf000..0xcd6c09e0]
     #
     # HotSpot Virtual Machine Error, Internal Error
     # Please report this error at
     # http://java.sun.com/cgi-bin/bugreport.cgi
     #
     # Error happened during: print threads
     #
     # Error ID: 4E4D4554484F440E4350500166 01
     #
     # Problematic Thread: prio=5 tid=0xe0430 nid=0x4 runnable
(Review ID: 144484)
======================================================================

Name: rmT116609 Date: 04/16/2002


 DESCRIPTION OF THE PROBLEM :

We run our application server (BEA Weblogic 6.1) using the Sun JVM.

While doing a thread dump during debugging, the jvm running Weblogic crashed and gave us the following output:


# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E4350500166 01
#
# Problematic Thread: prio=5 tid=0xec098 nid=0x4 runnable

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Start BEA WEblogic 6.1 under a heavy webload test
2. issue kill -3 pidnum where pidnum is the pid of the jvm running Weblogic
3. Crash.

EXPECTED VERSUS ACTUAL BEHAVIOR :
I was expecting a thread dump of the JVM in the error log,
and instead the JVM crashed totally.


(Review ID: 145489)
======================================================================

Name: rmT116609 Date: 04/23/2002


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Start Weblogic 5.1 with the -server option
2. Start Apache Jmeter with a small (15 steps) test plan
which fetches servlets from the server.
3. Procude some full thread dumps (kill -QUIT pid).
4. Repeat to 3 and wait.

EXPECTED VERSUS ACTUAL BEHAVIOR :
Expected: The JVM server shouldn't crash.

Actual: JVM died.



ERROR MESSAGES/STACK TRACES THAT OCCUR :
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E435050015E 01
#
# Problematic Thread: prio=5 tid=0x1612f8 nid=0x4 runnable
#
Abort

"VM Thread" prio=5 tid=0x1612f8 nid=0x4 runnable

(Review ID: 145678)
======================================================================


Name: stC104175 Date: 07/31/2000


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-beta)
Java HotSpot(TM) Client VM (build 1.3-beta, mixed mode)


While using kill -e <pid> to generate stack trace, the following message
occurred:

----------------------------------------------------
Full thread dump:

"RV Event Dispatch" prio=5 tid=0x578d10 nid=0x32 waiting on monitor
[0xd240f000..0xd240fa58]
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:420)
        at COM.TIBCO.rv.RvQ.waitEvent(RvQ.java:79)
        at COM.TIBCO.rv.RvDataDispatch.run(RvDataDispatch.java:36)

"Thread-11" prio=5 tid=0x569250 nid=0x30 waiting on monitor
[0xd6e03000..0xd6e03a58]
        at java.lang.Thread.sleep(Native Method)
        at com.gs.ficc.freedom.rv.RvPubSubCenter$1.run(RvPubSubCenter.java:56)
        at java.lang.Thread.run(Thread.java:484)

"RV Event Dispatch" prio=5 tid=0x568cc8 nid=0x2f waiting on monitor
[0xd7901000..0xd7901a58]
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E4350500166 01
#
# Problematic Thread: prio=5 tid=0xa8008 nid=0x4 runnable
#
(Review ID: 107818)
======================================================================

Name: krC82822 Date: 02/03/2001


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Server VM (build 2.0fcs-E, mixed mode)

1a) run ORBacus 4.0.4-based server application in console window
1b) hit Ctrl-Break to get thread dump
2) source code n/a - repeatable
3)
Full thread dump:

"ORBacus:Server:ReceiverThread" prio=5 tid=0x7b0210 nid=0x87 runnable
[0xea8f000..0xea8fdc0]
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E4350500166
#
# Problematic Thread: prio=5 tid=0x77c1b0 nid=0x6e runnable
#
4) can't get trace information!
5) NT 4.0 Service Pack 4, Intel x86 Pentium II 400 MHz 128 MB RAM
   Thread/monitor dump works ok with following on same computer:
java version "1.2.2"
Classic VM (build JDK-1.2.2-004, native threads, symcjit)
(Review ID: 116340)
======================================================================

Name: rmT116609 Date: 12/05/2001


$ /app/java/jdk1.3.1/bin/../bin/sparc/native_threads/java - version
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)


$ uname -a
SunOS pdcecm06 5.7 Generic_106541-14 sun4u sparc SUNW,Ultra-80

Though we've kill -QUITed our JVM running weblogic server 5.1.0SP9 several
times, this time produced the following output. This problem seems to have been
reported for earlier versions of the JVM. I open a new bug because it looks
like this is claimed to be fixed in the version I'm using. Perhaps there is
another problem still lurking:

Full thread dump:

"Screen Updater" daemon prio=5 tid=0x568dd8 nid=0x3e waiting on monitor
[0x75981000..0x75981a28]
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:420)
        at sun.awt.ScreenUpdater.nextEntry(ScreenUpdater.java:76)
        at sun.awt.ScreenUpdater.run(ScreenUpdater.java:95)

"AWT-Motif" daemon prio=6 tid=0x2f0080 nid=0x3c runnable
[0x75b81000..0x75b81a28]
        at sun.awt.motif.MToolkit.run(Native Method)
        at java.lang.Thread.run(Thread.java:484)

"SunToolkit.PostEventQueue-0" daemon prio=6 tid=0x291048 nid=0x3b waiting on
monitor [0x75c81000..0x75c81a28]
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:420)
        at sun.awt.PostEventQueue.run(SunToolkit.java:491)

      .
      .
      .
"ExecuteThread-11" daemon prio=5 tid=0x9bd580 nid=0x1a runnable
[0x77181000..0x77181a28]
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E4350500166 01
#
# Problematic Thread: prio=5 tid=0x18f6d8 nid=0x4 runnable
#

There was no thread tid=0x18f6d8 in the output I shortened above.
(Review ID: 131944)
======================================================================

Name: rmT116609 Date: 12/05/2001


java version "1.3.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_01)
Java HotSpot(TM) Client VM (build 1.3.1_01, mixed mode)


J2EE application running in Weblogic Server 5.1sp10.

thread dump, either through SIGQUIT, or weblogic.platform.SunVM.dump(),
regularly causes:

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E4350500166 01
#
# Problematic Thread: prio=5 tid=0x1350f0 nid=0x4 runnable

this issue was NOT RESOLVED in closed issue 4357866.

problem is NOT reproducible with either -Xint or -Xfuture flags signifying a
problem with HotSpot.

Other java options in use are: -server -Xnoclassgc -ms -mx -XX:New/Max/Survivor
(Review ID: 136535)
======================================================================

Name: rmT116609 Date: 12/12/2001


java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)


We use KILL -QUIT to produce a thread dump when our jvm is freeze but when we
use the options "-server -ms1024m -mx1024m -XX:+UseISM -Xconcurrentio", it
doesn't works dans the dump crash at the middle and produce this error. I have
made some tests and it seem the "-Xconcurrentio" is the problem.
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E4350500166 01
#
# Problematic Thread: prio=5 tid=0x104810 nid=0x4 runnable
#
(Review ID: 137232)
======================================================================

Name: rmT116609 Date: 03/11/2002


DESCRIPTION OF THE PROBLEM :
When pressing ^\ to get thread dump on an application running in JBoss, the JVM core dumps with this message:

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error happened during: print threads
#
# Error ID: 4E4D4554484F440E4350500166 01
#
# Problematic Thread: prio=5 tid=0xdae38 nid=0x2 runnable
#
Abort

EXTRA RELEVANT SYSTEM CONFIGURATION :
This problem occurs when running in one-to-one threading model (/usr/lib/lwp is first in LD_LIBRARY_PATH). This occurs when running an application in JBoss.

(Review ID: 144032)
======================================================================

Name: rmT116609 Date: 03/24/2002


DESCRIPTION OF THE PROBLEM :
This bug sounds very similar to 4339224 except that we use kill -3 to get our thread dumps instead of ctrl brk sequence. And I see despite that bug report being closed that users are still seeing it on even newer versions of jdk than we are using.

Every core file we get has the same stack trace shown below
from a where command in dbx on java core file:
(l@4) dbx: warning: cannot get thread count -- generic
libthread_db.so error
terminated by signal ABRT (Abort)
(/opt/SUNWspro/bin/../WS6/bin/sparcv9/dbx) where
=>[1] get_sig(0xff36c28c, 0x0, 0x0, 0xfee0bd78, 0xff37e000,
0x0), at 0xff369a04
  [2] _reaper_create(0xfee0bd78, 0xff385980, 0x6,
0xfee0a20c, 0xfee0bd78, 0xfee0
a250), at 0xff35dbf8
  [3] __thr_sigsetmask(0x0, 0x4, 0x6, 0xff37e000, 0x4,
0xff2bc4a8), at 0xff360c0c
  [4] putspent(0x6, 0x0, 0x0, 0xffffffff, 0xff2bc414,
0xfee0a360), at 0xff24afe0
  [5] _xftw(0xff2b8018, 0xfee0a360, 0x0, 0xfffffff8, 0x4,
0xfee0a381), at 0xff2357bc
  [6] os::abort(0x1, 0xfe492000, 0x1, 0xfee0a, 0xfe492000,
0xfee0a37c), at 0xfe3a019c
  [7] report_error(0xea, 0xfee0abf6, 0x166, 0xfe428208,
0xfe4ffddc, 0xfe492000), at 0xfe30f904
  [8] report_fatal(0x166, 0xfe492000, 0xfe475e30,
0x7387ffe8, 0x0, 0x121e), at 0xfe30f1d4
  [9] nmethod::scope_desc_at(0xfe492000, 0xfac489e0, 0x1,
0xfac488ff, 0xfac48828, 0x10), at 0xfe1655a4
  [10] vframe::new_vframe(0xfac48790, 0xfe492000, 0x958598,
0xfee0b86c, 0xfee0b854, 0xfee0b7cc), at 0xfe11f5a0
  [11] JavaThread::print_stack(0x0, 0xfe447718, 0xfe492000,
0x958598, 0xfe492000, 0xfee0ba4c), at 0xfe3b5f10
  [12] Threads::print(0x1, 0x0, 0x958598, 0xfe4ffddc,
0xfe4479b8, 0xfe492000), at 0xfe3b6d20
  [13] VM_Operation::evaluate(0xfde81c20, 0xfe4a9890, 0x164,
0xfee0b, 0xfe492000, 0xfee0bb3c), at 0xfe190a30
  [14] VMThread::evaluate_operation(0x1944e0, 0xfde81c20,
0xfe492000, 0xfe4a6cc4, 0xfe4a33dc, 0xfe492000), at
0xfe190ad4
  [15] VMThread::loop(0x1944e0, 0xfde81c20, 0x8, 0xfe4ae1bc,
0xfe4ae1b0, 0xfe4ae1c0), at 0xfe2cb8a8
  [16] VMThread::run(0xfe492000, 0x1944e0, 0x0, 0x0, 0x0,
0x0), at 0xfe2cb234
  [17] _start(0xfe492000, 0xff37f690, 0x1, 0x1, 0xff37e000,
0x0), at 0xfe20d410
(/opt/SUNWspro/bin/../WS6/bin/sparcv9/dbx)

And the thread dump in each case is interrupted by the same HotSpot Virtual Machine Internal Error shown below with the same Error ID each time. And the tid is always the "VM Thread" So would it be possible to at least get some information on exactly what can cause this particular error id?

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. As usual mainly occurs on our production servers and have not been able to pin down exact steps to reproduce.


EXPECTED VERSUS ACTUAL BEHAVIOR :
We expected a full thread dump which happens normally, not the core dump that we get when this VM Internal Error occurs.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Full thread dump:
     
     "jcp-80" prio=5 tid=0x4bb210 nid=0x143 runnable [0xcc640000..0xcc6409e0]
             at java.net.PlainSocketImpl.socketAccept(Native Method)
             at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
             at java.net.ServerSocket.implAccept(ServerSocket.java:243)
             at java.net.ServerSocket.accept(ServerSocket.java:222)
             at allaire.jrun.NetworkService.accept(NetworkService.java:213)
             at
allaire.jrun.jrpp.ProxyService.createRunnable(ProxyService.java:31)
             at allaire.jrun.ThreadPool.createRunnable(ThreadPool.java:175)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:72)
     
     "jcp-79" prio=5 tid=0x53ca30 nid=0x142 runnable [0xcc940000..0xcc9409e0]
             at java.net.SocketInputStream.socketRead(Native Method)
             at java.net.SocketInputStream.read(SocketInputStream.java:86)
             at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
             at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
             at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:295)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:287)
             at allaire.jrun.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:305)
             at
allaire.jrun.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:173)
             at
allaire.jrun.jrpp.ProxyService.swapRunnable(ProxyService.java:48)
             at allaire.jrun.ThreadPool.swapRunnable(ThreadPool.java:223)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:77)
     
     "jcp-78" prio=5 tid=0x2570d0 nid=0x141 runnable [0xcd780000..0xcd7809e0]
             at java.net.SocketInputStream.socketRead(Native Method)
             at java.net.SocketInputStream.read(SocketInputStream.java:86)
             at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
             at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
             at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:295)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:287)
             at allaire.jrun.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:305)
             at
allaire.jrun.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:173)
             at
allaire.jrun.jrpp.ProxyService.swapRunnable(ProxyService.java:48)
             at allaire.jrun.ThreadPool.swapRunnable(ThreadPool.java:223)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:77)
     
     "jcp-77" prio=5 tid=0x33c820 nid=0x136 runnable [0xcca00000..0xcca009e0]
             at java.net.SocketInputStream.socketRead(Native Method)
             at java.net.SocketInputStream.read(SocketInputStream.java:86)
             at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
             at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
             at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:295)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:287)
             at allaire.jrun.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:305)
             at
allaire.jrun.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:173)
             at
allaire.jrun.jrpp.ProxyService.swapRunnable(ProxyService.java:48)
             at allaire.jrun.ThreadPool.swapRunnable(ThreadPool.java:223)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:77)
     
     "jcp-76" prio=5 tid=0x801c90 nid=0x135 runnable [0xccc40000..0xccc409e0]
             at java.net.SocketInputStream.socketRead(Native Method)
             at java.net.SocketInputStream.read(SocketInputStream.java:86)
             at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
             at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
             at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:295)
             at
allaire.jrun.jrpp.ProxyEndpoint.readFully(ProxyEndpoint.java:287)
             at allaire.jrun.jrpp.ProxyEndpoint.readInt(ProxyEndpoint.java:305)
             at
allaire.jrun.jrpp.ProxyEndpoint.readRequest(ProxyEndpoint.java:173)
             at
allaire.jrun.jrpp.ProxyService.swapRunnable(ProxyService.java:48)
             at allaire.jrun.ThreadPool.swapRunnable(ThreadPool.java:223)
             at allaire.jrun.WorkerThread.run(WorkerThread.java:77)
     
     "jcp-75" prio=5 tid=0x326b28 nid=0x134 runnable [0xccd00000..0xccd009e0]
             at java.net.SocketInputStream.socketRead(Native Method)
             at java.net.SocketInputStream.read(SocketInputStream.java:86)
             at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
             at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
             at java.io.BufferedInputStream.re