There is an option to replace the sub-report for a report by replacing the existing one under controls & resources. Clicking on sub-report name should open a new page asking for uploading a local file or select from repository. As shown below:
But instead of that it keeps on waiting & after some time throws following exception.
org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 90 seconds
I have seen this and this happens when the report is not properly published. Can you please try the same for out of box report and see or you can copy the report again to repository and see if this helps
It is happening in our Test & Stage environment only. In Dev, it is working fine. I deleted & redeployed all reports using Import Settings.
But, the issue still persists.
Even, all environments are same. So, not able to identify the exact cause.
Try to delete the organization in your Dev box and import the out of box content and then try to import one report and test. I know its tiresome but I am trying to find out what is causing.
I re-installed Jasper server & re-deployed all reports one by one. This time, I was able to edit sub-reports successfully. As per my analysis, the sub-report editing functionality works fine till there are limited number of users in Japser Server.
But, once I assigned “Advanced Reporting” rights to group “Role: Team Member” in Clarity & ran “Create and Update Jasper Users” job, the number of users increased to 17000+ in Jasper Server & sub-report editing feature stopped working. This seems to be some memory related issue only which occurs when number of users increases.
Would you be able to suggest any resolution related to this?
Please see the technical document for sizing http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1114126.aspx
You may also consider setting up a jaspersoft cluster
I've already tried this, but no success. Thanks for your support. I'm going to raise a case now.
Sure we will work via case
This is the caseid: 00305718
just to let you know:
We had exactly the same exception "org.springframework.webflow.conversation.impl.LockTimeoutException" and found your thread:
By changing the parameter <property name="lockTimeoutSeconds" value="90"/> in the file webapps/reportservice/WEB-INF/jasperserver-servlet.xml, we could buy the more time to finish.
The real problem was simply that the query was not efficient and took longer than 90 secs to finish.
I will test this and update.
This particular property change helps running report for long. But, the issue I'm facing is to replace sub-report under control & resources with a new version of sub-report.