Clarity

  • Private Community
Back to discussions
Expand all | Collapse all

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

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

    Posted Mar 23, 2017 12:03 PM

    I  have below two issues with Jaspersoft, was trying in all avenues but could not resolve.

     

    We were on Clarity 14.2 and Jasper 5.6.1 On premise. Migrating to Clarity 15.1 and Jasper 6.2.1 and also migrating servers to AWS.  having below issue any inputs are really appreciated.

     

    1. Very few reports are throwing this error, while running the report from UI. when scheduled running fine. also the CA PPM BEAN and CA PPM DWH BEAN are showing as test failed when i login to direct url (/reportservice). There is nothing getting logged in the Jasperlogs.

     

    Error Details
    HTML response error code: 502, error

    HTML response was: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

    Proxy Error

    The proxy server received an invalid response from an upstream server.
    The proxy server could not handle the request POST /reportservice/flow.html.

    Reason: Error reading from remote server

     

    2. Output to Host File system option not working | Jaspersoft Community

    Output to Host File System option which used to work in 5.6.1 Even after doing this as suggested in Jasper documents it is not working.
     .../WEB-INF/applicationContext.xml enableSaveToHostFS Set the value from "false" (the default) to "true".
    Also uncommented the code in these files: ./webapps/reportservice/optimized-scripts/bower_components/jrs-ui/src/scheduler/template/editor/outputTabTemplate.htm ./webapps/reportservice/scripts/bower_components/jrs-ui/src/scheduler/template/editor/outputTabTemplate.htm
    Any help is appreciated!


  • 2.  Re: Jaspersoft issues after upgrading to 15.1 Jasper 6.2.1 and servers moved to AWS

    Broadcom Employee
    Posted Mar 23, 2017 01:58 PM

    Hi Venu,

     

    The reason you are getting this error is because your reverse proxy is blocking the error codes, some reports which are big and more than 500 pages its getting blocked and rather than showing the error code its shows the error. To fix the same you need to work with network team and turn off ProxyErrorOverride  to off

     

    Example

     

    This is the recommend setting after change...

    <IfModule proxy_module>
    ProxyErrorOverride On
    .......
    .......
    </IfModule>

    <VirtualHost *:8081>
    ProxyErrorOverride Off
    .......
    .......

    </VirtualHost>


    <VirtualHost *:8082>
    ProxyErrorOverride Off
    .......
    .......

    </VirtualHost>

     

     

    You can see the request is getting blocked when you do a fiddler trace or browser trace.

     

    Regards

    Suman Pramanik