dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Robin,

I think this is caused by the reverse proxy (nginx) timing out before
Tomcat can actually return a response. You might need to have a smaller (or
less complex) table , increase the speed of the machine or database server,
or have a look at how to increase the timeout for nginx, for instance here (
http://howtounix.info/howto/110-connection-timed-out-error-in-nginx)

Best regards,
Jason


On Fri, Mar 27, 2015 at 10:17 AM, Robin Martens <martens@xxxxxxx> wrote:

>  For your info, this is the error from the nginx error log:
>
>
>
> 2015/03/27 11:15:55 [error] 1445#0: *109012 upstream timed out (110:
> Connection timed out) while reading response header from upstream, client:
> 41.74.166.253, server: , request: "GET
> /fmis/api/analytics.json?dimension=BJKhSzfBKmv:Ae4qxiqGIfG;CpmfQtBkyz1;DVwxeJ0Xb7I;Ic8vhxrAzoh;MEUrnLoL6XN;NVMJAZYKU5z;NiRivr4ler1;Q6iENGCcTuC;WViHkMizFb9;YTkehaWmzR0;ahc5rJrzMX1;iucW8LchIct;p597QYRZ53h;pnzcAhEZPri;sXydEIf4G1w;uRpDTRApgcP;v0PApklkBX7;z15lLraL5Hc&dimension=IdABfQSGt1m:JEPCGjls8dZ;S1synIzr3Ew;boch7cMML3Q&dimension=UHynmMv2aLn:Kj3XoSFbfup;RoMyDiCiPBK;YGSu51Ps7XJ;opkSFostfHa&dimension=dx:V4ul2HVfbiw;eLMKH6NDAGf&dimension=e1yBdvZPgCq:B6Ww9EbkbPL;F1R4dnundcI;TyUeDhqCEXc;b7fJfWTcMeZ;jEpTjDQ43wH;xYZ6Rl6nWQW&dimension=ou:LEVEL-3;l01au4APkBP&filter=pe:LAST_YEAR&displayProperty=NAME
> HTTP/1.1", upstream: "
> http://127.0.0.1:8080/fmis/api/analytics.json?dimension=BJKhSzfBKmv:Ae4qxiqGIfG;CpmfQtBkyz1;DVwxeJ0Xb7I;Ic8vhxrAzoh;MEUrnLoL6XN;NVMJAZYKU5z;NiRivr4ler1;Q6iENGCcTuC;WViHkMizFb9;YTkehaWmzR0;ahc5rJrzMX1;iucW8LchIct;p597QYRZ53h;pnzcAhEZPri;sXydEIf4G1w;uRpDTRApgcP;v0PApklkBX7;z15lLraL5Hc&dimension=IdABfQSGt1m:JEPCGjls8dZ;S1synIzr3Ew;boch7cMML3Q&dimension=UHynmMv2aLn:Kj3XoSFbfup;RoMyDiCiPBK;YGSu51Ps7XJ;opkSFostfHa&dimension=dx:V4ul2HVfbiw;eLMKH6NDAGf&dimension=e1yBdvZPgCq:B6Ww9EbkbPL;F1R4dnundcI;TyUeDhqCEXc;b7fJfWTcMeZ;jEpTjDQ43wH;xYZ6Rl6nWQW&dimension=ou:LEVEL-3;l01au4APkBP&filter=pe:LAST_YEAR&displayProperty=NAME";,
> host: "197.243.47.210", referrer: "
> https://197.243.47.210/fmis/dhis-web-pivot/index.html";
>
>
>
>
>
> *From:* Dhis2-users [mailto:dhis2-users-bounces+martens=
> sher.be@xxxxxxxxxxxxxxxxxxx] *On Behalf Of *Robin Martens
> *Sent:* 26 March 2015 16:46
> *To:* DHIS 2 Users list; DHIS 2 Developers list
> *Subject:* [Dhis2-users] DHIS2 - Communication error "0" when generating
> pivot table
>
>
>
> Hi devs,
>
>
>
> Is there a limit on the pivot table size that can be generated in DHIS2?
> We’re having an extremely large table (in this case used for exporting
> structured data to excel) with indicators that gives a communication error
> after generating. When applied for a different period with less data, the
> table generates normally.
>
>
>
> The table contains 1 indicator and 1 data element. When reporting only the
> data element it’s fine, when reporting only the indicator, it gives an
> error, which leads me to think there’s a limit to the calculations
> somewhere.
>
>
>
> Any quick ways to fix this?
>
>
>
> Kind regards,
>
>
>
> Robin
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+46764147049