[Mika Koistinen]

Actually we were tracing another problem with our limited production environment and it required tracking those results and we didn’t consider that possibility to that some uses our api without paging . We have removed that log message, because issue is solved and we will try to remove long messages in future.
But anyway, if there would be some solution to prevent long delays, that would be awesome.

thanks,
mika

• This reply was modified 5 years, 3 months ago by Mika Koistinen.

[Mika Koistinen]

Hi Ray,
I’ll send sample file soon.
Msg is send by codesite.send(‘SOmetitle’, s);
Actually i dont know exactly how long that is .. but I have configured that File Size LImit is 20M. so when most of files are 40M i assume that message is 10M 🙂

49 710 905 file_30.csl
40 474 293 file_31.csl
40 597 025 file_32.csl
40 140 651 file_33.csl
57 753 417 file_34.csl
59 570 272 file_35.csl
41 600 168 file_36.csl
39 692 905 file_37.csl
57 148 799 file_38.csl
43 182 131 file_39.csl
I go to that entry by going to end of file (Ctrl-End) or many many page downs.

BUt i’ll send that file soon.

[Mika Koistinen]

Hi,
For 3. I might have a simple brute-force solution, which I use in my centralized codesite liveviewer machine: Just add a scheduled task to kill all live viewers. I do it during midnight

[Author]

Posts