Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Sun, 31 Mar 2013 15:03:15 +0000 (UTC)
From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: <JIRA.12613573.1351201548958.82582.1364742195486@arcas>
In-Reply-To: <JIRA.12613573.1351201548958@arcas>
References: <JIRA.12613573.1351201548958@arcas>
Subject: [jira] [Updated] (IVYDE-329) Disable DTD external fetching for
 matching ivy/ivy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/IVYDE-329?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lalev=C3=A9e updated IVYDE-329:
----------------------------------

    Labels: patch  (was: )
   =20
> Disable DTD external fetching for matching ivy/ivy
> --------------------------------------------------
>
>                 Key: IVYDE-329
>                 URL: https://issues.apache.org/jira/browse/IVYDE-329
>             Project: IvyDE
>          Issue Type: Improvement
>         Environment: Ivy 2.4.0.alpha/IvyDE 2.2.0.beta2
>            Reporter: Stephen Haberman
>              Labels: patch
>         Attachments: ivyde-xml-dtd-hung.txt, optionalExternalDtds.diff, o=
ptionalExternalDtds-ivyde.diff
>
>
> Our team uses Ivy/IvyDE, and noticed Eclipse hanging today/yesterday, to =
the point of being unusable.
> I tracked it down to Eclipse asking IvyDE "is this your file?", which  Iv=
yDE's IvySettingsContentDescriber used XMLHelper.parse to answer, but then =
Xerces hung while trying to load the XML file's DTD.
> So, the problem was the DTD being unavailable, but it seems like XMLHelpe=
r should turn this off, especially if the schema parameter is null, and it'=
s in non-validating mode.
> The attached patch turns off external DTD fetching when XMLHelper is alre=
ady in non-validating mode.
> This avoids the wire call, which speeds up the XMLHelper.parse by at leas=
t 100%, ~250-300ms when fetching the DTD, to ~100-150ms when not. (And this=
 is the happy case, in the worst case, waiting for the timeout if the DTD i=
s unavailable, takes ~20s).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira