[Koha] recursion problem with requests.pl

[LAURENT Henri-Damien]

Chris Nighswonger a écrit :
> Hi Bryan,
>
> On Fri, Jan 22, 2010 at 8:04 AM, Bryan Lakatos
> <Bryan.Lakatos at mvschool.com> wrote:
>   
>> Greetings,
>>
>> I just upgraded from 3.0.0 to 3.0.5 today (running ondebian linux "lenny" that is up to date), and all went well, except oneinfinite recursion loop when giving requests.pl a biblionumber query.
>>
>> Forexample, in the admin interface (:8080), having searched the catalog,the list of books includes a link to see any holds on each book. Thisis the link:
>>
>> server:8080/cgi-bin/koha/reserve/request.pl?biblionumber=33769 (with the number changing with each book, of course)
>>
>> Clickingone of these links starts a request.pl process that maxes out the CPUand never returns a response to the browser. I've waited 30 mins onthis (as I went to grab dinner) and it never finished; I had to killthe request.pl process to end it.
>>
>> In the apache error.log, these two lines appear for every time I trigger the problem:
>>
>> [ThuJan 21 21:33:22 2010] Digit.pl: Deep recursion on subroutine"utf8::SWASHNEW" at /usr/share/perl/5.10/utf8_heavy.pl line 251, line 275.
>> [Thu Jan 21 21:33:22 2010] Digit.pl: Deeprecursion on subroutine "CGI::Carp::die" at/usr/share/perl/5.10/utf8_heavy.pl line 198,  line 275.
>>
>> If anyone has any tip or advice for me, I'd greatly appreciate it. THANKS!
>>     
>
> I can confirm that this bug exists in 3.00.05, but has been fixed in
> the current 3.0.x HEAD. You can grab the latest code by cloning the
> main git repo. See this link for how to:
> http://wiki.koha.org/doku.php?id=en:development:git_usage
>
> Also feel free to jump back on IRC if you get stuck.
>
> Kind Regards,
> Chris
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>   
Hi
The bug you ask for is because you set DebugLevel to 2.
Set it to 1 and it will go away.

We experienced also such problems with this level.
But it would be a real nighmare to fix that better.
You have to know it : DebugLevel 2 breaks more things.

Hope that helps.
-- 
Henri-Damien LAURENT
BibLibre