Jaspersoft report is giving 502 error somtime

[Legacy User]

All,

When we ran jaspersoft report in immediate mode (not in scheduled mode), sometime reporting server is throwing the error below.

"HTML response error code: 502, error.

Error 502!!!

Oops something went wrong there"

 

But, when we ran the report in scheduled mode, this issue wont come and will get the output without any issue?

 

Could you please help me to understand why this issue happens / how to solve it.

 

Thanks,

Agin A Vadath

[goosr02]

Hi Agin,

Can you please let us know on what version of clarity are you on ?

How many pages is your report fetching ?

Also, Are both (Schedule/Immediate) requests going to the same Jasper server ?

 

Do you see any errors in the logs ?

 

 

Regards,

Srikanth G

[Legacy User]

Hi Srikanth,

We are using 14.3 version of clarity and 6.2.1 version of jaspersoft.

Report is fetching more than 500 pages.

This error comes only in immediate mode(sometime), not in scheduled mode.

We are capturing 'error' logs only in jaspersoft. But, couldn't see any error logs captured for the same.

 

Thanks,

Agin

[goosr02]

Hi Agin,

 

Thanks for the details.

Any report which is having more than 500 pages needs to be scheduled, if we try to get making use of immediate option it will fail. You are seeing HTTP error may be because reverse proxy is blocking it.

 

Please refer below community post , which has got similar issue reference:

Jaspersoft issues after upgrading to 15.1 Jasper 6.2.1 and servers moved to AWS 

 

Also refer:

Reference:  Advanced Reporting with Jaspersoft - CA PPM SaaS - 14.3 - CA Technologies Documentation 

 

 

Hope it helps.

 

Regards,

Srikanth G

[Legacy User]

Thanks Srikanth for your quick response and sharing this information.

In Immediate mode, if our report (custom report) is fetching more than 500 pages of data, it will throw this error. correct me, if my understanding is wrong.

 

Thanks,

Agin

[goosr02]

Yes Agin, if a report is fetching more than 500 pages of data it will give us error. To verify, you can quickly try running a report which fetches less data.

 

Note:

CA PPM 14.3 is soon reaching EOS - December 31, 2017. Please consider upgrading your environment with CA PPM latest release.

 

 

Regards,

Srikanth G

[Legacy User]

Thanks Srikanth for clarifying the same.

 

Yeah. Plan is on for the upgrade and will do shortly.

 

Thanks,

Agin 

[Legacy User]

Hi Srikanth,

 

I have ran a custom report with page limitation as 5k(<property name="net.sf.jasperreports.governor.max.pages" value="5000"/>).However am getting more than 900+ pages without any error. Please find the screen below.

 

 

Sometime when user is running this report in immediate mode, they are getting the error what i mentioned earlier.

 

Thanks,

Agin

[Suman Pramanik]

502 error doesn;t give detailed information. The generic error means Bad Gateway, so we need to co relate with network tracing and jaspersoft and ppm logs to see what error is getting captured.