Jasper Server 5.5 Home Page Recently Viewed Items

For some reason the Recently Viewed Items on the Jasper Server home page is not working. It use to work and just stopped one day. Cannot figure out why? It is working on our test environment. How is the Recently Viewed Items displayed and how can I fix this. Did a datasource or server report get deleted? Currently it is alway empty and our users liked when it would show their specific results. Just looking for some guidance to test fixes.

scott.thibodeau's picture
Joined: Feb 18 2014 - 7:22am
Last seen: 3 years 10 months ago

4 Answers:

It's probably getting data from jiaccessevent table. The resource_id corresponds to id in the jiresource table.

hozawa's picture
Joined: Apr 24 2010 - 4:31pm
Last seen: 3 years 9 months ago

Thank you for your answer. Do you know what configuration changes I should look at on the server to ensure this is running. The data does appear in the jiresources table but is not showing on screen.

scott.thibodeau - 9 years 1 week ago

Recently Viewed Items (RVI) works through REST API, so it's very strange that they stoped to work.

I have a few question to try to undestans what's going on:

  1. How do you deply JRS in production (Do you use proxy ? or deployng JRS as ROOT web app)
  2. Any javascript errors in browser's console ?

Also if you detected that RVI stoped to work, could you checj View->Search Results

Select "Viewed by Me" and type  Report or Adhoc. It should show the same results as RVI because underhood they use the same services.





nesterone's picture
Joined: May 4 2011 - 5:04am
Last seen: 8 years 4 months ago
nesterone, We installed using the bundled apache-tomcat server. There are no javascript errors in the browser. The search results "Viewed by Me" did not stop working, and still works now. By inspecting the HTML of the RVI on our test server, we see it's drawn into a table. On Prod, the element is written, but it has no child elements inside it. Stranger yet is that this DID work in Prod, and one day we all noticed it was no longer there.
peter.larabell's picture
Joined: Mar 11 2014 - 6:57am
Last seen: 9 months 3 weeks ago

I encountered the same issue. It ended up being to do with the server JRS was being run on, specifically the hostname routing.
When Jasper performs the HTTP request for the content to be displayed on the home page, a port number was put into the URL which was causing a time out.
Ask the server guy to help you out. It could also explain why it happened "out of the blue" because changes to the server's routing could have been made separately.

tyler_5's picture
Joined: Sep 4 2017 - 8:30pm
Last seen: 5 years 4 months ago