[From nobody Fri Aug 6 17:08:10 2004 Return-Path: <dave@lumos.com> Received: from relay3.firstlink.com ([66.37.143.30]) by pickering.mail.mindspring.net (Earthlink Mail Service) with ESMTP id 18cqgj6Eg3Nl3p20 for <servlets@mindspring.com>; Thu, 14 Nov 2002 15:06:51 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by relay3.firstlink.com (Postfix) with ESMTP id 2044CB45E3 for <servlets@mindspring.com>; Thu, 14 Nov 2002 13:06:51 -0700 (MST) Received: from gleam.lumos.com (unknown [216.4.9.35]) by relay3.firstlink.com (Postfix) with ESMTP id DC277B45DE for <jhunter@servlets.com>; Thu, 14 Nov 2002 13:06:46 -0700 (MST) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C28C19.5BE43A68" Subject: javasoft bug report that shows up in using JDOM X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Date: Thu, 14 Nov 2002 12:06:46 -0800 Message-ID: <728DA21B8941A843A7C496F1ACF4851801E2E17A@gleam.lumos.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: javasoft bug report that shows up in using JDOM Thread-Index: AcKMGVvVU2yU/novRlq74sEB7ZZeEw== From: "Spencer, Dave" <dave@lumos.com> To: <jhunter@servlets.com> X-Virus-Scanned: by First Link Technology, Inc. X-Razor-id: 0ebec9982f7b0ac673159f88c41cedddadbb5ab4 X-Mozilla-Status2: 00000000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C28C19.5BE43A68 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Jason - I'm not on the jdom lists and hope I'm not breaking a rule by mailing you directly, but anyway some of the discussion on this thread: =20 http://lists.denveronline.net/lists/jdom-interest/2002-October/011522.ht ml =20 May be related to a javasoft bug in StringBuffer in jdk1.4.1. =20 http://developer.java.sun.com/developer/bugParade/bugs/4724129.html =20 It causes amazing pathalogical memory behavior. JDK1.4.0 is fine. =20 thx for listening, Dave =20 ------_=_NextPart_001_01C28C19.5BE43A68 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4915.500" name=3DGENERATOR></HEAD> <BODY> <DIV><SPAN class=3D918380420-14112002><FONT size=3D2>Jason - I'm not on = the jdom=20 lists and hope I'm not breaking a rule</FONT></SPAN></DIV> <DIV><SPAN class=3D918380420-14112002><FONT size=3D2>by mailing you = directly, but=20 anyway some of the discussion on this thread:</FONT></SPAN></DIV> <DIV><FONT size=3D2></FONT>&nbsp;</DIV> <DIV><FONT size=3D2><A=20 href=3D"http://lists.denveronline.net/lists/jdom-interest/2002-October/01= 1522.html">http://lists.denveronline.net/lists/jdom-interest/2002-October= /011522.html</A></FONT></DIV> <DIV><FONT size=3D2></FONT>&nbsp;</DIV> <DIV><SPAN class=3D918380420-14112002><FONT size=3D2>May be related to a = javasoft=20 bug in StringBuffer in jdk1.4.1.</FONT></SPAN></DIV> <DIV><FONT size=3D2></FONT>&nbsp;</DIV> <DIV><FONT size=3D2><A=20 href=3D"http://developer.java.sun.com/developer/bugParade/bugs/4724129.ht= ml">http://developer.java.sun.com/developer/bugParade/bugs/4724129.html</= A></FONT></DIV> <DIV><FONT size=3D2></FONT>&nbsp;</DIV> <DIV><SPAN class=3D918380420-14112002><FONT size=3D2>It causes amazing = pathalogical=20 memory behavior.</FONT></SPAN></DIV> <DIV><SPAN class=3D918380420-14112002><FONT size=3D2>JDK1.4.0 is=20 fine.</FONT></SPAN></DIV> <DIV><SPAN class=3D918380420-14112002><FONT = size=3D2></FONT></SPAN>&nbsp;</DIV> <DIV><SPAN class=3D918380420-14112002><FONT size=3D2>thx for=20 listening,</FONT></SPAN></DIV> <DIV><SPAN class=3D918380420-14112002><FONT size=3D2>&nbsp; = Dave</FONT></SPAN></DIV> <DIV><SPAN class=3D918380420-14112002></SPAN>&nbsp;</DIV></BODY></HTML> ------_=_NextPart_001_01C28C19.5BE43A68-- ]