Project and Portfolio Management Practitioners Forum
cancel

Logon via HTTPS - Custom and OOTB JSP Reports Are Not Running/Failing

Highlighted
ErwinTazelaar
Regular Contributor.

Logon via HTTPS - Custom and OOTB JSP Reports Are Not Running/Failing

Hello,

On our test environment we have installed IIS 7.5
According to the admin guide, however we use webport 8080 that directs to two nodes with the ports 9000 (user node) and 10000 (background node).  Because we have a VIP/Loadbalancer with port 8080.

We are able to login via HTTPS.
However when I want to run a custom or OOTB JSP report, the report fails with the following message.

---------------------------------------------
Running report/web/knta/achmea/APSC_Rapportage_v5_60.jsp
Posting report request tohttp://145.219.238.177:9000/itg/servlet/RunJspReport
Post data= 'REPORT_JSP=%2Fweb%2Fknta%2Fachmea%2FAPSC_Rapportage_v5_60.jsp&OUT_BASEFILE=rep_57090&USER_ID=113034&REPORT_ID=57090&SUBMISSION_LANGUAGE=AMERICAN&KEYID=196142&KEY=105886819'
Error running report.
Unexpected end of file from server
java.net.SocketException: Unexpected end of file from server
at com.kintana.rpt.server.KSCRunJspReportCommand.logError(KSCRunJspReportCommand.java:310)
at com.kintana.rpt.server.KSCRunJspReportCommand.execute(KSCRunJspReportCommand.java:254)
at com.kintana.core.server.execution.CommandRunner.run(CommandRunner.java:118)
at java.lang.Thread.run(Unknown Source)

------------------------------

The report command line is:
------------------------------
ksc_run_jsp_report /web/knta/achmea/APSC_Rapportage_v5_60.jsp
REPORT_ID=[RP.REPORT_SUBMISSION_ID]
USER_ID=[RP.CREATED_BY]
OUT_BASEFILE=[RP.FILENAME]
ksc_end_report_parameters
------------------------------

One thing to mention, when I login on our second background node via HTTP, the custom and OOTB JSP reports are running succesfull. 
 

Can this due to some wrong settings in IIS 7.5, or that some specific PPMC files are not updated correctly? 
Or related that our VIP/Loadbalancer is configured with port 8080... and directs to the usernode with port 9000

-> Posting report request to  http://145.219.238.177:9000/itg/servlet/RunJspReport

Attached you can find the zip file with the server.conf settings.

 

L.S. After every kUpdateHtml.sh I need to update the AJP port in the file ppm-bindings.xml to 9000 otherwise I can't login.

 

Best Regards,

Erwin

3 REPLIES
Jim Esler
Acclaimed Contributor.

Re: Logon via HTTPS - Custom and OOTB JSP Reports Are Not Running/Failing

The directive com.kintana.core.server.BASE_URL should appear in server.conf only once, not once per node. It should be set to the value used by users to connect to the application.

randull
Micro Focus Expert

Re: Logon via HTTPS - Custom and OOTB JSP Reports Are Not Running/Failing

Did you make sure that the ports you use are available?

Thanks,
Randall
Best regards,
Randall

-- Remember to give Kudos to answers! (click the KUDOS star)
"If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
ErwinTazelaar
Regular Contributor.

Re: Logon via HTTPS - Custom and OOTB JSP Reports Are Not Running/Failing

Hi Jim and Randull,

 

The ports we use are available.

When I remove the Base_URL below the second node it's still not working.

Furthermore I am not able to generate the report via the second/background node, due to removing the base_url.

 

Do you know any solution?

 

Best Regards,

Erwin