You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Alex Romayev <ro...@yahoo.com> on 2004/03/02 21:33:44 UTC
[XConfToolTask] java.net.ConnectException: Connection timed out: connect
Hi,
Most of the time when I run XConfToolTask, it works
fine, but sometimes I get the following error:
IOException: java.net.ConnectException: Connection
timed out: connect
Any idea what's the problem here?
Thanks,
-Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Joerg Heinicke <jo...@gmx.de>.
On 02.03.2004 22:51, Geoff Howard wrote:
>> The problem after an upgrade is the remaining of the xerces JAR at
>> tools/lib. The JARs are only copied on demand to that place, i.e. if
>> no xerces JAR exists at that place at all. If there is already a 2.6.0
>> JAR it won't be replaced if you have updated only lib/endorsed. This
>> is at least true for build.bat. build.sh copies the endorsed libs
>> always to tools/lib, but does not remove old versions.
>>
>> Is that explanation helpful?
>>
>> Why are these three files copied at all? When the java.endorsed.dirs
>> property is set (which is to lib/endorsed) the JARs are on the
>> classpath. If we need to copy them the build script should probably
>> made a bit more intelligent on this issue.
>
>
> No fair, I figured that out on my own but now you won't believe me... :)
>
> I have no idea why the build copies those files, and I think no one
> does. Anyone? In fact, the batch file spits out bogus file not found
> warnings at the beginning of every build which has confused newbies.
Yes, the windows build tests for many locations where to find the JARs.
> Anyone against stopping the copy from lib/endorsed to toos/lib, and
> pointing the ant/jetty endorsed dir to lib/endorsed directly?
The java.endorsed.dirs already point to lib/endorsed.
> If not,
> then we need to fix the build scripts so that we are not shielded from
> endorsed lib updates in the build.
It's just an issue of the build. I tried it without the libs at
tools/lib and it does not work:
BUILD FAILED
java.lang.IllegalArgumentException: No attributes are implemented
at
org.apache.crimson.jaxp.DocumentBuilderFactoryImpl.setAttribute(Docum
entBuilderFactoryImpl.java:93)
at XConfToolTask.execute(Unknown Source)
Hmm, don't know why it falls back to Crimson (from JDK I guess) though
endorsed dirs are set and Ant works without the JARs in tools/lib.
Joerg
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Geoff Howard <co...@leverageweb.com>.
Joerg Heinicke wrote:
> On 02.03.2004 22:08, Geoff Howard wrote:
>
>>>>> Hi,
>>>>>
>>>>> Most of the time when I run XConfToolTask, it works
>>>>> fine, but sometimes I get the following error:
>>>>>
>>>>> IOException: java.net.ConnectException: Connection
>>>>> timed out: connect
>>>>>
>>>>> Any idea what's the problem here?
>>>>
>>>>
>>>>
>>>>
>>>> Which version of Cocoon? The xpatch task is supposed to disable
>>>> resolving of remote dtds but the underlying xalan/xerces feature
>>>> was broken. To be honest, I don't remember where it left off, when
>>>> it broke or if/when it was fixed.
>>>
>>>
>>>
>>>
>>> It was Xerces 2.6.0, but fixed for Cocoon 2.1.4.
>>
>>
>> Thanks, Joerg. I had it in my head that it was "fixed" but the
>> problem didn't go away. Am I loonier than I thought?
>
>
> The problem after an upgrade is the remaining of the xerces JAR at
> tools/lib. The JARs are only copied on demand to that place, i.e. if
> no xerces JAR exists at that place at all. If there is already a 2.6.0
> JAR it won't be replaced if you have updated only lib/endorsed. This
> is at least true for build.bat. build.sh copies the endorsed libs
> always to tools/lib, but does not remove old versions.
>
> Is that explanation helpful?
>
> Why are these three files copied at all? When the java.endorsed.dirs
> property is set (which is to lib/endorsed) the JARs are on the
> classpath. If we need to copy them the build script should probably
> made a bit more intelligent on this issue.
No fair, I figured that out on my own but now you won't believe me... :)
I have no idea why the build copies those files, and I think no one
does. Anyone? In fact, the batch file spits out bogus file not found
warnings at the beginning of every build which has confused newbies.
Anyone against stopping the copy from lib/endorsed to toos/lib, and
pointing the ant/jetty endorsed dir to lib/endorsed directly? If not,
then we need to fix the build scripts so that we are not shielded from
endorsed lib updates in the build.
Geoff
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Joerg Heinicke <jo...@gmx.de>.
On 02.03.2004 22:08, Geoff Howard wrote:
>>>> Hi,
>>>>
>>>> Most of the time when I run XConfToolTask, it works
>>>> fine, but sometimes I get the following error:
>>>>
>>>> IOException: java.net.ConnectException: Connection
>>>> timed out: connect
>>>>
>>>> Any idea what's the problem here?
>>>
>>>
>>>
>>> Which version of Cocoon? The xpatch task is supposed to disable
>>> resolving of remote dtds but the underlying xalan/xerces feature was
>>> broken. To be honest, I don't remember where it left off, when it
>>> broke or if/when it was fixed.
>>
>>
>>
>> It was Xerces 2.6.0, but fixed for Cocoon 2.1.4.
>
> Thanks, Joerg. I had it in my head that it was "fixed" but the problem
> didn't go away. Am I loonier than I thought?
The problem after an upgrade is the remaining of the xerces JAR at
tools/lib. The JARs are only copied on demand to that place, i.e. if no
xerces JAR exists at that place at all. If there is already a 2.6.0 JAR
it won't be replaced if you have updated only lib/endorsed. This is at
least true for build.bat. build.sh copies the endorsed libs always to
tools/lib, but does not remove old versions.
Is that explanation helpful?
Why are these three files copied at all? When the java.endorsed.dirs
property is set (which is to lib/endorsed) the JARs are on the
classpath. If we need to copy them the build script should probably made
a bit more intelligent on this issue.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Joerg Heinicke <jo...@gmx.de>.
On 02.03.2004 22:08, Geoff Howard wrote:
>>>> Hi,
>>>>
>>>> Most of the time when I run XConfToolTask, it works
>>>> fine, but sometimes I get the following error:
>>>>
>>>> IOException: java.net.ConnectException: Connection
>>>> timed out: connect
>>>>
>>>> Any idea what's the problem here?
>>>
>>>
>>>
>>> Which version of Cocoon? The xpatch task is supposed to disable
>>> resolving of remote dtds but the underlying xalan/xerces feature was
>>> broken. To be honest, I don't remember where it left off, when it
>>> broke or if/when it was fixed.
>>
>>
>>
>> It was Xerces 2.6.0, but fixed for Cocoon 2.1.4.
>
> Thanks, Joerg. I had it in my head that it was "fixed" but the problem
> didn't go away. Am I loonier than I thought?
The problem after an upgrade is the remaining of the xerces JAR at
tools/lib. The JARs are only copied on demand to that place, i.e. if no
xerces JAR exists at that place at all. If there is already a 2.6.0 JAR
it won't be replaced if you have updated only lib/endorsed. This is at
least true for build.bat. build.sh copies the endorsed libs always to
tools/lib, but does not remove old versions.
Is that explanation helpful?
Why are these three files copied at all? When the java.endorsed.dirs
property is set (which is to lib/endorsed) the JARs are on the
classpath. If we need to copy them the build script should probably made
a bit more intelligent on this issue.
Joerg
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Geoff Howard <co...@leverageweb.com>.
Joerg Heinicke wrote:
> On 02.03.2004 21:48, Geoff Howard wrote:
>
>> Alex Romayev wrote:
>>
>>> Hi,
>>>
>>> Most of the time when I run XConfToolTask, it works
>>> fine, but sometimes I get the following error:
>>>
>>> IOException: java.net.ConnectException: Connection
>>> timed out: connect
>>>
>>> Any idea what's the problem here?
>>
>>
>> Which version of Cocoon? The xpatch task is supposed to disable
>> resolving of remote dtds but the underlying xalan/xerces feature was
>> broken. To be honest, I don't remember where it left off, when it
>> broke or if/when it was fixed.
>
>
> It was Xerces 2.6.0, but fixed for Cocoon 2.1.4.
Thanks, Joerg. I had it in my head that it was "fixed" but the problem
didn't go away. Am I loonier than I thought?
Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Joerg Heinicke <jo...@gmx.de>.
On 02.03.2004 21:48, Geoff Howard wrote:
> Alex Romayev wrote:
>
>> Hi,
>>
>> Most of the time when I run XConfToolTask, it works
>> fine, but sometimes I get the following error:
>>
>> IOException: java.net.ConnectException: Connection
>> timed out: connect
>>
>> Any idea what's the problem here?
>
> Which version of Cocoon? The xpatch task is supposed to disable
> resolving of remote dtds but the underlying xalan/xerces feature was
> broken. To be honest, I don't remember where it left off, when it broke
> or if/when it was fixed.
It was Xerces 2.6.0, but fixed for Cocoon 2.1.4.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [XConfToolTask] java.net.ConnectException: Connection timed out: connect
Posted by Alex Romayev <ro...@yahoo.com>.
I've replaced my ant/lib (since I'm calling the task
from my own build script) with xercesImpl-2.6.1.jar
and it worked. Thanks for your help guys.
--- Geoff Howard <co...@leverageweb.com> wrote:
> Alex Romayev wrote:
>
> >I have 2.1.4 label. My internet connection is fine
> >(proved by this email ;-)). I suppose the server
> it's
> >trying to look up is down...
> >
> >
>
> if web.xml is the culprit (you should see which file
> is being patched in
> the console) that'd be sun's site.
>
> >Do you think if I CVS HEAD, it'll fix it?
> >
> >
>
> Maybe - we did upgrade to Xerces 2.6.2 from 2.6.1
> about six days ago.
> You may just try upgrading Xerces (I think Xpatch
> will use the version
> in tools/lib??)
>
> Geoff
>
> >Thanks,
> >-Alex
> >
> >--- Geoff Howard <co...@leverageweb.com> wrote:
> >
> >
> >>Alex Romayev wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>Most of the time when I run XConfToolTask, it
> works
> >>>fine, but sometimes I get the following error:
> >>>
> >>>IOException: java.net.ConnectException:
> Connection
> >>>timed out: connect
> >>>
> >>>Any idea what's the problem here?
> >>>
> >>>
> >>>
> >>>
> >>Which version of Cocoon? The xpatch task is
> >>supposed to disable
> >>resolving of remote dtds but the underlying
> >>xalan/xerces feature was
> >>broken. To be honest, I don't remember where it
> >>left off, when it broke
> >>or if/when it was fixed. But that's probably the
> >>issue. While the
> >>problem exists, it is impossible to run the xpatch
> >>task against an xml
> >>file with a dtd reference (web.xml for example) if
> >>no interet connection
> >>is present, and probably if the dtd request fails.
> >>
> >>Geoff
> >>
> >>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail:
> users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Geoff Howard <co...@leverageweb.com>.
Alex Romayev wrote:
>I have 2.1.4 label. My internet connection is fine
>(proved by this email ;-)). I suppose the server it's
>trying to look up is down...
>
>
if web.xml is the culprit (you should see which file is being patched in
the console) that'd be sun's site.
>Do you think if I CVS HEAD, it'll fix it?
>
>
Maybe - we did upgrade to Xerces 2.6.2 from 2.6.1 about six days ago.
You may just try upgrading Xerces (I think Xpatch will use the version
in tools/lib??)
Geoff
>Thanks,
>-Alex
>
>--- Geoff Howard <co...@leverageweb.com> wrote:
>
>
>>Alex Romayev wrote:
>>
>>
>>
>>>Hi,
>>>
>>>Most of the time when I run XConfToolTask, it works
>>>fine, but sometimes I get the following error:
>>>
>>>IOException: java.net.ConnectException: Connection
>>>timed out: connect
>>>
>>>Any idea what's the problem here?
>>>
>>>
>>>
>>>
>>Which version of Cocoon? The xpatch task is
>>supposed to disable
>>resolving of remote dtds but the underlying
>>xalan/xerces feature was
>>broken. To be honest, I don't remember where it
>>left off, when it broke
>>or if/when it was fixed. But that's probably the
>>issue. While the
>>problem exists, it is impossible to run the xpatch
>>task against an xml
>>file with a dtd reference (web.xml for example) if
>>no interet connection
>>is present, and probably if the dtd request fails.
>>
>>Geoff
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [XConfToolTask] java.net.ConnectException: Connection timed out: connect
Posted by Alex Romayev <ro...@yahoo.com>.
I have 2.1.4 label. My internet connection is fine
(proved by this email ;-)). I suppose the server it's
trying to look up is down...
Do you think if I CVS HEAD, it'll fix it?
Thanks,
-Alex
--- Geoff Howard <co...@leverageweb.com> wrote:
> Alex Romayev wrote:
>
> >Hi,
> >
> >Most of the time when I run XConfToolTask, it works
> >fine, but sometimes I get the following error:
> >
> >IOException: java.net.ConnectException: Connection
> >timed out: connect
> >
> >Any idea what's the problem here?
> >
> >
>
> Which version of Cocoon? The xpatch task is
> supposed to disable
> resolving of remote dtds but the underlying
> xalan/xerces feature was
> broken. To be honest, I don't remember where it
> left off, when it broke
> or if/when it was fixed. But that's probably the
> issue. While the
> problem exists, it is impossible to run the xpatch
> task against an xml
> file with a dtd reference (web.xml for example) if
> no interet connection
> is present, and probably if the dtd request fails.
>
> Geoff
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail:
> users-help@cocoon.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: [XConfToolTask] java.net.ConnectException: Connection timed out:
connect
Posted by Geoff Howard <co...@leverageweb.com>.
Alex Romayev wrote:
>Hi,
>
>Most of the time when I run XConfToolTask, it works
>fine, but sometimes I get the following error:
>
>IOException: java.net.ConnectException: Connection
>timed out: connect
>
>Any idea what's the problem here?
>
>
Which version of Cocoon? The xpatch task is supposed to disable
resolving of remote dtds but the underlying xalan/xerces feature was
broken. To be honest, I don't remember where it left off, when it broke
or if/when it was fixed. But that's probably the issue. While the
problem exists, it is impossible to run the xpatch task against an xml
file with a dtd reference (web.xml for example) if no interet connection
is present, and probably if the dtd request fails.
Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org