Hi everyone,

I have a ticket with a long history and many merges, but it shows fine under 
/rt/Ticket/History.html?id=$ID. RT also gives me its history without problems 
when I use the REST-API with the short format /rt/REST/1.0/ticket/$ID/history ->

RT/4.2.12 200 Ok

# 642/642 (/total)


But when I use the long format /rt/REST/1.0/ticket/$ID/history?format=l the CPU 
usage on my RT process spikes and becomes unresponsive. Which leads to 
supervisord restarting the process after a while.

Were on RT 4.2.12 and our stack is nginx -> nginx -> supervisord -> 
rt-server.fcgi -> postgresql

It looks like a bug in RT to me, or could it be some misconfiguration on my 

Vinzenz Sinapius
Information Technology | Informationstechnik

tracetronic GmbH
Stuttgarter Str. 3

Phone: +49 351 205768-167
Fax: +49 351 205768-999
E-mail: vinzenz.sinap...@tracetronic.de<mailto:vinzenz.sinap...@tracetronic.de>

Head Office | Hauptsitz: Stuttgarter Str. 3, 01189 DRESDEN, GERMANY
Managing Directors | Geschäftsführer: Dr.-Ing. Rocco Deutschmann, Dr.-Ing. 
Peter Strähle
Registration Court | Registergericht: Amtsgericht Dresden, HRB 23 086

Reply via email to