J2EE App Server startup error in VM

When I am re-starting a proprietary J2EE app server (which requires Java 1.4.x). I periodically get this critical Java VM error:

# 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.2_03-b02 mixed mode)
#
# Error ID: 43113F32554E54494D45110E4350500308
#
# Problematic Thread: prio=2 tid=0x00a59768 nid=0x590 runnable
#

Heap at VM Abort:
Heap
 def new generation   total 36480K, used 31516K [0x10010000, 0x127a0000, 0x14ed0000)
  eden space 32448K,  971244656sed [0x10010000, 0x11ed7240, 0x11fc0000)
  from space 4032K,   01244656sed [0x11fc0000, 0x11fc0000, 0x123b0000)
  to   space 4032K,   01244656sed [0x123b0000, 0x123b0000, 0x127a0000)
 tenured generation   total 483968K, used 43490K [0x14ed0000, 0x32770000, 0x50010000)
   the space 483968K,   81244656sed [0x14ed0000, 0x17948a20, 0x17948c00, 0x32770000)
 compacting perm gen  total 35072K, used 34831K [0x50010000, 0x52250000, 0x56010000)
   the space 35072K,  991244656sed [0x50010000, 0x52213e60, 0x52214000, 0x52250000)
Dynamo exited abnormally.  For troubleshooting information go to the URL:
  http://www.atg.com/support
Press any key to continue . . .

I can get it very consistently when I restart the application multiple times rapidly. This is running under Windows 2003 Enterprise Server SP2. Googling for "Error ID: 43113F32554E54494D45110E435050030" gives me nothing. I read something about array initialization being a place to check. Since this is not 100% consistent, I am sure it will be a nightmare to really determine the actual cause and create a fix for it. Thankfully I don't think there is a problem with the 2007.1 release of the ATG Service platform, because they have moved away from the Dynamo Application Server and just use JBOSS, or WEBLOGIC as the app server. Also I think you can use Java 1.5 rather that 1.4. I suspect this is a problem in the DAS code (or the Java 1.4 VM) that only seems to occur when restarting DAS frequently. Some businesses heavily use the legacy 2006.3 version with the DAS app server, so it will continue to be an issue whenever I need to work in this environment and restart the app server.

I get impatient with these app servers, it takes long enough to start without having to wait a little extra time between restarts, just to ensure the app server does not crash.