Thanks Chris,
Very helpful advice. I can't help but feel a little out of my depth
with this one :-\
On 19 February 2010 16:46, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chris,
>
> On 2/19/2010 11:08 AM, Chris Mannion wrote:
>&
UAoIOk6Bm5CLCNWBb1g/jXy9p8hDZ8
> =6wCb
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
m/blog/2007/09/10/urlopenstream-might-leave-you-hanging/
> as its first hit.
>
> In essence: the timeout is controlled by setTimeout on UrlConnection.
>
> On 12 February 2010 11:59, Chris Mannion wrote:
>> Hi all
>>
>> Hoping someone can shed some light on a little puzzle I hav
t java.net.URL.openStream(URL.java:1007)
at ep.ext.outputUrl(ext.java:446)
So it's the attempt to open the input stream on the URL that is timing
out, what governs that timeout?
--
Chris Mannion
iCasework and LocalAlert imp
cat setting that was causing the problem.
2008/11/27 André Warnier <[EMAIL PROTECTED]>:
> Chris Mannion wrote:
>>
>> Hi All
>>
>> I've recently started having a problem with one of the servlets I'm
>> running on a Tomcat 5.5 system. The code of t
as the XML data often contains characters like &
which have to remain encoded to keep the XML valid.
As I said, this problem started without the servlet code having
changed at all so is there any Tomcat setting that could be
responsible for this?
--
Chris Mannion
iCasework and LocalAlert
bapp) with
those from Tomcat
5.5 but that didn't make any difference. Has anyone got any more ideas?
--
Chris Mannion
iCasework and LocalAlert implementation team
0208 144 4416