Jump to content

Problem with caching of SQL data in Input Control


jme14

Recommended Posts

I have created an input control to select a specific error-code for an error-report. This input control selects also the error-messages and the number of times a specific error occurs (with count(*)).

select vme.id
,      left(vme.code,3) as code
,      concat(vme.ernst
             ,lpad(vme.id,3,'0')
             ,' - '
             ,vme.message
             ,' ('
             ,count(*)
             ,')'
             ) as message
from hls_verwerking_melding vme
     join hls_verwerking_verslag vve
       on vve.id_vme = vme.id
and (vme.ernst = $P{p_error_code} or $P{p_error_code} = '0')
group by vme.id

This works fine, but.... Jasperserver does not (always) refresh the selected data. When I use the input control, I get the same data as yesterday. (Yes, I am sure the data has been modified in the database)

How can I instruct JasperServer not to cache the data in this input control?

I use JasperServer CE 3.7.0

Regards,

Jan

Link to comment
Share on other sites

  • Replies 5
  • Created
  • Last Reply

Top Posters In This Topic

  • 4 weeks later...

We are seeing this behaviour too- our input controls cache from the previous day's data. In fact, if you rerun the report, on the third time the cache is abandoned and it starts working.

But then, when you choose the report from the list of reports subsequently, it goes back to the previous day's cache despite having abandoned it earlier!

Why would clearing the ad-hoc cache have any effect? This is not an ad-hoc report, it is an iReport with an input control.

If we have to clear the ad-hoc cache every day then this is not a solution.

Link to comment
Share on other sites

  • 1 month later...
  • 8 months later...

Is this solved in JasperServer 4.0.0 ?

We also have the problem of the cached inputcontrols.
It looks like this is a user - dependent cache. For one user the list is cashed and not refreshed and for another user everything works fine.

Is there a solution or work-around for this in 3.7.0?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...