Updating JSP Report In 11g Does Not Work On-The-Fly Unless WLS_REPORTS Is Restarted (Doc ID 1162025.1)

Last updated on NOVEMBER 23, 2015

Applies to:

Oracle Reports Developer - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

On Fusion Middleware Reports Services version 11.1, when replacing the JSP report with a newly updated JSP report, the report output will not display the new updates unless WLS_REPORTS is restarted.

That was not the case in Application Server OC4J (10gR1 and 10gR2); everytime a new JSP report is uploaded, the new jsp report is executed and get the new result without restarting the server/OC4J_BI_Forms.

Steps to Reproduce

The issue can be reproduced at will with the following steps:

1. The symptoms when WLS_REPORTS managed server is not restarted:

Save the jsp report in DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/reports_11.1.1.2.0/uqanoi/war/chenk/

old.jsp (report result: old)
new.jsp (report result: new)

(a) Make copy the old report and name it with a different name

mv old.jsp pk.jsp

(b) Run the report

https://hostname.domain/reports/chenk/pk.jsp?

The report will display the old output

(c) Now copy the new modified report and use the same name as in step (a)

mv new.jsp pk.jsp

(d) Run the new modified report

https://hostname.domain/reports/chenk/pk.jsp?

The report will display the old output instead of the new output

The issue is not reproduced when restarting the WLS_REPORTS managed server between steps (c) and (d)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms