|
»
« Return to Thread: query timeout bug
Re: query timeout bug
by Michael Sokolov-2
::
Rate this Message:
I had a similar issue (1.3-dev version on linux). Queries would randomly
die immediately, with the message that they had taken too long: sorry don't
have the details, but it really did sound like they had been killed
explicitly by the watchdog. I had set the watchdog timer to 30 seconds.
-Mike
> -----Original Message-----
> From: Andrew Hart CEMS Staff [mailto:Andrew2.Hart@...]
> Sent: Tuesday, June 30, 2009 6:03 AM
> To: exist
> Subject: [Exist-open] query timeout bug
>
> I recently tried to use
> - query-timeout
> this attribute sets the maximum amount of
> time (expressed in
> milliseconds) that the query can take before
> it is killed..
> from conf.xml to limit queries to 5 minutes or less. This
> was because some of our scripts get data from an external
> source through a proxy, either of which can take forever to
> respond...Anyway it worked well apart from the fact that it
> randomly kills xqueries immediately (and gives the query
> timed out error).
>
> Anyone else get this? I am on Solaris 10 java 1.5.0_01 eXist says
> 8849-20090416 but this may be wrong as I have to remember to
> type it in before build.sh
>
> I am asking because it could be something local - like our
> http proxy - causing the problem.
>
>
> This email was independently scanned for viruses by McAfee
> anti-virus software and none were found
> --------------------------------------------------------------
> ----------------
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
------------------------------------------------------------------------------
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open
die immediately, with the message that they had taken too long: sorry don't
have the details, but it really did sound like they had been killed
explicitly by the watchdog. I had set the watchdog timer to 30 seconds.
-Mike
> -----Original Message-----
> From: Andrew Hart CEMS Staff [mailto:Andrew2.Hart@...]
> Sent: Tuesday, June 30, 2009 6:03 AM
> To: exist
> Subject: [Exist-open] query timeout bug
>
> I recently tried to use
> - query-timeout
> this attribute sets the maximum amount of
> time (expressed in
> milliseconds) that the query can take before
> it is killed..
> from conf.xml to limit queries to 5 minutes or less. This
> was because some of our scripts get data from an external
> source through a proxy, either of which can take forever to
> respond...Anyway it worked well apart from the fact that it
> randomly kills xqueries immediately (and gives the query
> timed out error).
>
> Anyone else get this? I am on Solaris 10 java 1.5.0_01 eXist says
> 8849-20090416 but this may be wrong as I have to remember to
> type it in before build.sh
>
> I am asking because it could be something local - like our
> http proxy - causing the problem.
>
>
> This email was independently scanned for viruses by McAfee
> anti-virus software and none were found
> --------------------------------------------------------------
> ----------------
> _______________________________________________
> Exist-open mailing list
> Exist-open@...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>
------------------------------------------------------------------------------
_______________________________________________
Exist-open mailing list
Exist-open@...
https://lists.sourceforge.net/lists/listinfo/exist-open
« Return to Thread: query timeout bug
| Free embeddable forum powered by Nabble | Forum Help |
