Jump to content
JasperReports 7.0 is now available ×

Empty reports on fresh installation of JasperServer?


richard.legendi

Recommended Posts

  • Replies 10
  • Created
  • Last Reply

Top Posters In This Topic

I am guessing that you are talking about the sample reports.  Can you tell if there is any data in the tables that it is trying to pull the data from?  Maybe something went wrong with the load of the sample data.  Is this specific to the library view?  Do the reports work from other views, such as the repository view?  I have not seen this before - empty database tables would be my best guess.

Link to comment
Share on other sites

Yes, about the sample reports (as you can see the name of the query on the screenshot is Accounts Reports). I believe the data import was successful because both demo tables (*sugarcrm, foodmart*) is populated, I can use them in the embedded JPivot tool. The import showed some errors for the *foodmart* table, but since all the sample reports are empty I suspect an other problem here. It seems the reports do not work from the repository view.
Link to comment
Share on other sites

Here's some of the things that I do when I'm having trouble with tomcat. Shutdown tomcat, delete files: 

tomcat/conf/Catalina/Localhost/*.xml (if there are any jrs related datasource files in here) (tomcat will recreate them)

tomcat/logs/*.*

tomcat/work/Catalina/localhost

tomcat/temp/*.*

It looks to me that there is some sort of display error. Because the report unit is present - and you obviously clicked on it to try and display the report. 

So, the trick I think is to try and get some error information in the logs:

tomcat/logs/catalina.out

tomcat/webapps/jasperserver/WEB-INF/logs/jasperserver.log 

And hopefully there is some info after the cleanup

Link to comment
Share on other sites

To try to get more information, one thing to try would be to edit tomcat/webapps/jasperserver/WEB-INF/log4j.properties and change "log4j.rootLogger=ERROR, stdout, fileout" to "log4j.rootLogger=DEBUG, stdout, fileout" (this puts the jasperserver logger in "spew mode").  Restart tomcat (or at least restart jasperserver webapp) and monitor tomcat/webapps/jasperserver/WEB-INF/logs/jasperserver.log (if it doesn't exist, you'll want to "touch" the file to create one -- for some reason Jasper Server won't create a log if the file doesn't exist...no clue why).

HTH...

Link to comment
Share on other sites

  • 4 weeks later...

Well, sort of. Actually, I wanted put JasperServer into a Liferay bundled Tomcat. I wasn't succesful in integrating these tools, but as the Server Admin Guide suggested in the docs folder of JasperServer, the official way to do this is to use **two** Tomcat installations. That was the best solution I was able to come up with.

 

However, a hint that might help you out: I got a warning on the logs about the *Context is read-only*. I tried to merge the `conf/context.xml` file of Tomcat and the JasperServer but then even the first page of JasperServer didn't load. I might have misconfigured something else too (I was trying recklessly to put things together and installed several other webapps and configured everything I found, etc.), but maybe you'll have a bit more luck with this. Hope this helps.

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...