Java Solaris Communities Sun Store Join SDN My Profile Why Join?
» search tips 
Sun Developer Network
Developers Home > Products & Technologies > Java Technology > Community > Bug Database >
Join SDNWhy Join
 
Bug Database
Bug Detail
Quick Lists
-  Top 25 Bugs
-  Top 25 RFE's
-  Recently Closed Bugs
Printable Page Printable Page


Bug Database
Welcome
 
»  Login
»  Report a Bug
»  FAQs
  Bug Watch List:
» Watch this Bug
 Bug Votes:
 This bug is Closed.You cannot Vote for it.
Bug ID: 4479571
Votes 3
Synopsis JVM core dumps after receiving out of memory messages
Category hotspot:runtime_system
Reported Against 1.3.0_03
Release Fixed
State 11-Closed, duplicate of 4503832, bug
Priority: 2-High
Related Bugs 4484290 , 4490177 , 4503832 , 4788015
Submit Date 13-JUL-2001
Description 
This problem is present in both 1.3.0_02 1.3.0_03 and 1.3.1

Changing the time-stamp of a servlet deployed in WebLogic 6's
public_html/WEB-INF/classes/ directory triggers the OutOfMemory errors and
the eventual HotSpot crash.

When a servlet is changed, WebLogic 6's code destroys its current class
loader  customer  and instantiates a new one.  This requires any session objects
in memory to be serialized before the class loader is destroyed, then
deserialized and reinstantiated for the new class loader.  (This is
documented at
http://e-docs.bea.com/wls/docs60////servlet/progtasks.html#143031 under the
"ClassCastException and HTTP Sessions" header).

There is a lot of serialization/deserialization happening all at once, which
is what we suspect is causing the problem.

This problem happens with any of the flags -client, -server or -hotspot

java.lang.OutOfMemoryError
	<<no stack trace available>>
<Jul 9, 2001 9:51: customer  AM EDT> <Error> <HTTP> <[WebAppServletContext(2378821,public_html)] Servlet failed with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
java.lang.OutOfMemoryError
	<<no stack trace available>>
<Jul 9, 2001 9:51: customer  AM EDT> <Error> <HTTP> <[WebAppServletContext(2378821,public_html)] Servlet failed with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4349254E560E43505000F4 01
#
# Problematic Thread: prio=5 tid=0x100ae0 nid=0xb runnable 
#

========
dbx output of thread
current thread:   xxxxx@xxxxx  
=>[1] __sigprocmask(0x0, 0xfea01f38, 0x0, 0xffffffff, 0xffffffff, 0x0), at 0xff379cf0
  [2] _resetsig(0xff38c984, 0x0, 0xfea03dc0, 0x0, 0x0, 0xfea03e40), at 0xff36f31c
  [3] _sigon(0xff3943d8, 0xff394278, 0xfea03e38, 0xfea0200c, 0x6, 0xff2cd0ac), at 0xff36ea40
  [4] _thrp_kill(0x0, 0xb, 0x6, 0xff38c984, 0xfea03dc0, 0xff393bf4), at 0xff371944
  [5] abort(0xff333bb0, 0xfea02100, 0x0, 0xfffffff8, 0x0, 0xfea02121), at 0xff2b9468
  [6] os::abort(0x1, 0xfe78c000, 0x1, 0xfea02, 0xfe78c000, 0xfea0211c), at 0xfe6e28ac
  [7] report_error(0xee, 0xfea02992, 0xf4, 0xfe73eca4, 0xfe7c6df8, 0xfe78c000), at 0xfe650ae0
  [8] report_fatal(0xf4, 0xfe78c000, 0xfe762218, 0xfea03344, 0x100ae0, 0x2), at 0xfe6503b0
  [9] ciEnv::get_constant_by_index_impl(0x0, 0x100ae0, 0xfea03b78, 0x2, 0xfe78c000, 0xfea033b0), at 0xfe5d7880
  [10] ciEnv::get_constant_by_index(0xfe79f8ec, 0x100ae0, 0xfea03438, 0x2, 0xfe78c000, 0x1f5f08), at 0xfe5d75ec
  [11] ciBytecodeStream::get_constant(0x1f5f08, 0xfea03b78, 0xfe78c000, 0xfea034b0, 0xfea03550, 0x2), at 0xfe5d74d
4
  [12] GraphBuilder::load_constant(0xfe78c000, 0x100fa0, 0xfea035d4, 0x100f98, 0x100f94, 0x100f90), at 0xfe5d6f84
  [13] GraphBuilder::connect_to_end(0xfe7b8fac, 0xfe7b8fb0, 0xfe7b8fb4, 0xfe7b8fb8, 0xfe7b8fbc, 0xfe78c000), at 0x
fe5acf54
  [14] GraphBuilder::handle_exception(0xda9d78, 0xdaa8b0, 0xdaa99c, 0xfe78c000, 0xffffffff, 0xfe7b0c3c), at 0xfe5d
477c
  [15] GraphBuilder::connect_to_end(0xfe7b8fac, 0xfe7b8fb0, 0xfe7b8fb4, 0xfe7b8fb8, 0xfe7b8fbc, 0xfe78c000), at 0x
fe5ac300
  [16] GraphBuilder::GraphBuilder(0xda9ea0, 0xfea03a98, 0x100fd0, 0xda9cd4, 0xda9de4, 0xfea03770), at 0xfe5abbc0
  [17] IRScope::build_graph(0xda9e50, 0xfea03a98, 0xffffffff, 0x1f4f60, 0xfe78c000, 0xfe78c000), at 0xfe5aa970
  [18] IR::IR(0xda9ccc, 0xfea03a98, 0x1f5ec0, 0xda9cb8, 0x100fd0, 0x100dd0), at 0xfe5a9ba4
  [19] Compilation::build_hir(0x100f7c, 0xfe78c000, 0xfea03a98, 0xfea03ba4, 0x400, 0xfffffffc), at 0xfe5a9984
  [20] Compilation::compile_java_method(0xfea03a98, 0xfea03a1c, 0xfea03a98, 0x100ae0, 0xfea03ba4, 0xfea039cc), at 
0xfe5a8a18
  [21] Compilation::Compilation(0x100ca0, 0xfea03b78, 0x1f5ec0, 0xffffffff, 0x100c84, 0xfe78c000), at 0xfe5a8440
  [22] Compiler::compile_method(0x100c84, 0x100c18, 0xfe78c000, 0x1f5ec0, 0xffffffff, 0x1f5ec0), at 0xfe5a81a0
  [23] CompileBroker::invoke_compiler_on_method(0x1f5ec0, 0x0, 0xfe7ab604, 0x0, 0x0, 0xa48), at 0xfe5a3a98
  [24] CompileBroker::compiler_thread_loop(0x29128, 0x100ae0, 0xfe78c000, 0xfea03d60, 0xfe78c000, 0xf9cf5130), at 
0xfe59df70
  [25] JavaThread::run(0xfe904000, 0xfe795d3c, 0xfe78c000, 0x100000, 0x100ae0, 0x100000), at 0xfe58e040
  [26] _start(0xfe78c000, 0xff255d60, 0x0, 0xb8681e50, 0x1, 0xfe401000), at 0xfe57dea4



All info (java_g core file and dbx output(newdbxout) and error logs) are contained in
/net/cores.east/cores/62553685
Work Around 
N/A
Evaluation 
Not enough info to reproduce this. I do not use WebLogic 6 product, and I have no idea where to find such servlet stuff.  Downloaded 6.0 and installed it.
Started up fine, waiting for servlet info.  Please provide a demo
servlet to use and steps to get it up and running. 
  xxxxx@xxxxx   2001-08-01

Picked up from Ireland. Looking for causes of OutOfMemory.
Requested that customer add -verbosegc and provide
the output.

  xxxxx@xxxxx   2001-09-21

After applying fixes for bugs 4490177,4484290 and 4503832, the customer
no longer sees a SEGV. The problem is now a hang. If we don't see this
problem again, I am closing the bug as a dup of 4503832.

  xxxxx@xxxxx   2001-10-17
Comments
  
  Include a link with my name & email   

Submitted On 22-AUG-2001
raniwala 
I feel that bug 4395735 may be the reason of this crash.


Submitted On 22-AUG-2001
raniwala 
I got same error:
<Aug 22, 2001 10:34:38 AM PDT> <Error> <HTTP> <
[WebAppServletContext(6529454,sta
ging)] Servlet failed with Exception
java.lang.OutOfMemoryError
        <<no stack trace available>>
>
<Aug 22, 2001 10:35:10 AM PDT> <Error> <HTTP> <
[WebAppServletContext(6529454,sta
ging)] Servlet failed with Exception
java.lang.OutOfMemoryError
        <<no stack trace available>>
>
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4349254E560E43505000F4 01
#
# Problematic Thread: prio=5 tid=0x988a0 nid=0xa runnable
#
Abort

This error happened on Weblogic6.0/Apache running on 
solaris. This happened twice in two days with our 
application, which runs fine on Tomcat, Weblogic 5.1, with 
JDK 1.3.0. I don't know the cause of problem but I observe 
that if I restart Weblogic after modifying JSPs it works 
fine. Any more info, mail at raniwala@flashmail.com


Submitted On 22-AUG-2001
sutanu_g 
It has happened in one environment and of course does not 
happen everywhere and everytime with weblogic 6.x with jdk 
1.3.x. Is not the core and dbx output helping ?

A note on the original description of the bug.
- this is actually triggered when a servlet class is 
changed and server tries to reload the class.
- OutOfMemory occured followed by crash when the jvm was 
started as -mx1024m without any min size.
- OutOfMemory did not occur but the crash happened when jvm 
started as -ms1024m -mx1024m


Submitted On 07-MAR-2002
Karthik9277 
We have encountered problems on Windows 2000 and NT when 
using the -hotspot option with the JVM. 

This is due to a Sun bug 
(http://developer.java.sun.com/developer/bugParade/bugs/4479
571.html) 

and results in intermittent crashes of the server. To work 
around this problem, try setting:

-XX:MaxPermSize=128m

This option allows you to increase the size of the area 
HotSpot uses for class representations.
===============================================
Due to a Sun bug, a java lang.OutOfMemory error my occur 
when starting WebLogic Server if the 

number of classes being loaded is too high. 

As a workaround, increase the value of the JVM option -
XXMaxPermSize when initializing WebLogic 

Server, using this syntax:

java -XX:MaxPermSize=<value>K

where <value> is some number of kilobytes. The JVM uses a 
default maximum value of 32 MB.

This problem has been reported to Sun.


Submitted On 05-JUN-2002
zjshang 
i got folloring error sometimes without OutOfMemory #

# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4349254E560E43505000F4
#
# Problematic Thread: prio=1 tid=0x808e1d8 nid=0x29db 
runnable
#


is it same bug ?


Submitted On 18-AUG-2002
mechlife 
is this a related problem.....i am sorry if this is not the right 
place to put it...


<Aug 17, 2002 2:30:06 PM EDT> <Error> <HTTP> <
[WebAppServletContext
(3477601,gmacretailhome,/gmacretailhome)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:30:29 PM EDT> <Error> <HTTP> <
[WebAppServletContext
(3477601,gmacretailhome,/gmacretailhome)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:30:40 PM EDT> <Error> <Posix Performance 
Pack> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:30:58 PM EDT> <Error> <HTTP> <
[WebAppServletContext
(3477601,gmacretailhome,/gmacretailhome)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:31:29 PM EDT> <Error> <HTTP> <
[WebAppServletContext
(3477601,gmacretailhome,/gmacretailhome)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:31:46 PM EDT> <Error> <Posix Performance 
Pack> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:32:26 PM EDT> <Error> <HTTP> <
[WebAppServletContext
(3477601,gmacretailhome,/gmacretailhome)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:32:36 PM EDT> <Error> <HTTP> <
[WebAppServletContext
(3477601,gmacretailhome,/gmacretailhome)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:32:43 PM EDT> <Error> <HTTP> <
[WebAppServletContext
(3477601,gmacretailhome,/gmacretailhome)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:33:01 PM EDT> <Error> <HTTP> <
[WebAppServletContext(2503741,gmac,/gmac)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:33:24 PM EDT> <Error> <HTTP> <
[WebAppServletContext(2503741,gmac,/gmac)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:33:28 PM EDT> <Error> <HTTP> <
[WebAppServletContext(2503741,gmac,/gmac)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:33:34 PM EDT> <Error> <Kernel> 
<ExecuteRequest failed
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:38:15 PM EDT> <Error> <Posix Performance 
Pack> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4349254E560E43505000F4 01
#
# Problematic Thread: prio=5 tid=0xab8f8 nid=0xb runnable 
#
Abort - core dumped
LD_LIBRARY_PATH=/app/bea/wls6.1-
gmacretail/lib/solaris:/app/bea/wls6.1-
gmacretail/lib/solaris/oci816_8


Submitted On 18-AUG-2002
mechlife 
is this a related problem.....i am sorry if this is not the right 
place to put it...

<Aug 17, 2002 2:33:24 PM EDT> <Error> <HTTP> <
[WebAppServletContext(2503741,gmac,/gmac)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:33:28 PM EDT> <Error> <HTTP> <
[WebAppServletContext(2503741,gmac,/gmac)] Servlet failed 
with Exception
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:33:34 PM EDT> <Error> <Kernel> 
<ExecuteRequest failed
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
<Aug 17, 2002 2:38:15 PM EDT> <Error> <Posix Performance 
Pack> <Uncaught Throwable in processSockets
java.lang.OutOfMemoryError
	<<no stack trace available>>
> 
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4349254E560E43505000F4 01
#
# Problematic Thread: prio=5 tid=0xab8f8 nid=0xb runnable 
#
Abort - core dumped
LD_LIBRARY_PATH=/app/bea/wls6.1-
gmacretail/lib/solaris:/app/bea/wls6.1-
gmacretail/lib/solaris/oci816_8


Submitted On 14-SEP-2002
mlabib2000 
I am facing the three flavours of the problem here, That is :

---------------------------------------
1- java.lang.OutOfMemoryError
	<<no stack trace available>>

2- Server Hang, or

3- # HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4349254E560E43505000F4 01

------------------------------------------------
This is wheather applying the -XX:MaxPermSize=128m 
parameter or not!. Has you been able to find a geniune cause 
of the problem and a fix for it?


Submitted On 12-DEC-2002
jraibeck 
I am running Weblogic 6.1 with the latest jdk 1.3.1 version on 
Windows 2000.  I only get this error (see below) when trying 
to use OptimizeIt 4.2.  The suggestion by Karthik9277 to 
add "-XX:MaxPermSize=128m" seems to have fix my problem 
so far.

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Error ID: 4349254E560E43505000F4
#
# Problematic Thread: prio=5 tid=0x24c41678 nid=0x838


Submitted On 24-JUL-2003
developersjava 
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.0_01-b03 mixed 
mode)
#
# Error happened during: generation collection for allocation
#
# Error ID: 4F4F502D41500E4350500190
#
# Problematic Thread: prio=1 tid=0x0x8203240 nid=0x178f 
waiting on monitor

albolle@yahoo.fr


Submitted On 28-AUG-2003
clayuser 
i have reproduced this error with the following steps: 
1. simple webapp with 2 jsp's
2. every time the first jsp is invoked: dump the context
(parent)classloader id's
3. make a second jsp which changes the default timezone to 
another and invoke it once
4. now if you check (do a request to the first jsp again) the 
id's of the first jsp you will see that that the classloaders 
have changed 
5. as consequence you get ClassCastExceptions and 
OutofMemory depending on your application

used wl 7.0/red hat



PLEASE NOTE: JDK6 is formerly known as Project Mustang





About Sun  |  About This Site  |  Newsletters  |  Contact Us  |  Employment
How to Buy  |  Licensing  |  Terms of Use  |  Privacy  |  Trademarks
 

 
Copyright 1994-2008 Sun Microsystems, Inc.
A Sun Developer Network Site

Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License.
 
XML Content Feeds