djsiders

I am in the process of attempting an update to JasperServer 5.6 I have successfully configured and built the application and got it to start on my machine. I built a simple report and setup a scheduled job for that report, and all worked fine (emailed report, created report in repository, etc.) After running, I went to the repository folder where the report output files were stored (CSV and PDF) and tried to delete, but no option is given. When I select those files, the buttons at the top stay greyed out. Note that since I was just testing, I used the same folder for the Jasper Report and the report output files, not sure if that matters. When I select the Jasper Report in the same folder, I get the delete option (button enabled). I have played with permissions on the folder as well, no luck. I am working as user jasperadmin, and have not made any server config changes via the UI (permissions, etc.) other than as noted above.

All I have ever had to change is the values in the js.jdbc.properties file. Mine is under the config folder, just below where the startup files are. I put in the QA servers URL, UID, password, driver, etc. and run export. Then change to the Prod server values and run the import.

Issue was with the maven build not get resources into the database for themes. Cleared DB completely and started over, and found the several images were being created and inserted. Once this occurred, the pages began displaying correctly. Thanks mwoinoskibt for the hint on stylesheets, that pointed me in the direction of looking at themes.

Also, don't think this has anything to do with this, but I had to change the following two lines in the sessionFactory bean in applicationContext.xml <value>/com/jaspersoft/jasperserver/api/metadata/common/service/impl/hibernate/persistent /RepoMondrianConnection.hbm.xml</value> <!--value>${property.hbm.RepoMondrianXMLADefinition}</value--> Without this change, I would get an error creating the bean and the app wouldn't even start.

Tried in FireFox 11 and IE 7 CSS view enabled

Can you run Subreport 1 directly from iReports. If so, does it print results from subreport2? Does the main report run correctly (showing both subreports) in iReports (basically eliminating server as the issue)

Adding screenshot and jasperserver log file. I downloaded the server war file from this site, replaced the context and go same results.

After finally getting JS 4.5 to build, when deploying, the application starts, but the pages are just overlapping garbage. You can make out various portions of the page, even enough to login, but nothing really displays right. Several overlapping windows, the text is all overlapping, etc. Any ideas appreciated. As noted, the application itself seems to be somewhat working, as it appears to log me in, just can't get a good screen to display.

The factory method that produces the datasource needs to be static. If not, the source will test OK, but you get the error noted when trying to actually run.

I am using Sun JVM 1.6.0_18, but that is not where the issue lies directly. Not sure what tracker is or how it is used, but the issue is in the method named setParameter(JRParameter param) in class com.jaspersoft.ireport.designer.compiler.prompt.PromptDialog The method starts at line 113 of the 3.7.6 Source code. In that method, the first if statement determines if the param (defined in the report) is of type java.util.Date. If it is, the next few lines initi a var called datePicker. That var is defined at the top of the code, line 53 as a Class level private JXDatePicker, with an initial value of null. Searching for usage of that variable, it is not initialized anywhere in the class except for line 124 of this method. After the datePicker var is initialized to a new JXDatePicker, the code goes on set a format on line 128, however, that line references the var datetimePicker not datePicker. Just like datePicker, the only place datetimePicker is initialized to a non null is in this method, but at line 147, which is a different if condition. Therefore, when line 128 tries to use datetimePicker, it is still null, and throws the NPException. Don't think so, but it could be possible that some jvm version return a different Value class name from the param, but don't see how. Even if that is the case, the code is wrong and is trying to use an unititialize variable every time a format string is set. No two ways about that. If you fall into the first IF clause and you have a format string that is not empty, you will get an NPE on any JVM known to the java world. The fix is to use the datePicker on the set format line, as that is what was supposed to be used, as that is what is referenced by the rest of that portion of the IF statement.

Something I have found useful to have to keep from having to flip back and forth between the repository name and the local file path when working in iReports and the deployed server version of a report. Create a Parameter IS_RUNNING_LOCAL - type Boolean - default value false - use for prompt Create another Parameter SUB_REP_LOCATION - type String - do not use for prompt - set default to code below: $P{IS_RUNNING_LOCAL}.booleanValue() ? "SubReportName.jasper" : "repo:SubRepReposName" Then set your SubReport Expression property to: $P{SUB_REP_LOCATION} Of course change the two report names to match your sub report names. When deploying to the server do not use either of these params as input, just the boolean when running iReports. When you run in iReports, answer true to the IS_RUNNING_LOCAL prompt. This will cause iReports to use the local name/path. When running on the server with no prompt, it will default to false and use the repository name for the subreport. If you are doing a lot of dev work, you can temporarily change the default value to true so you can use the default of the prompt. An added benefit is that iReport will then find and compile the sub-report (at least in later iReport versions) as well.

A few things I have done for odd SQL like this: $P!{PARM_NAME} put the literal text of the param into the SQL (the ! is the key) instead of using it like a parameter value In your case, since your param is a colletion, possibly something like $P!{PARM_NAME}.get(0) If you don't know the number of items in your collection ahead of time, you can use a Scriptlet to create the actual SQL. In that case, create a param with a default value like: $P{REPORT_SCRIPTLET}.createSQL($P{YOUR_COLL_PARAM}) and then in your reports query definition, simply use $P!{PARM_NAME} as your entire query. At runtime, the query will be the text the Scriptlet code generates. The scriptlet code would accept your collection param as an argument, and step through creating the dynamic SQL as required.

Looking for feedback regarding user experience of the paid version of JS vs. the CE freeware version. Specifically quality of support, but any other comments welcome. I just can't seem to find much info and support for CE except in this forum and wonder if the paid version is much better. We are have severe problems with scheudling, and the investment in the paid version would be well worth it if we felt it would solve our issues. Just don't have that confidence right now, as it seems whenever something is fixed in JasperServer (and or iReports), something new pops up as an issue.

I am having an issue with scheduled reports running reliably in JS 3.7.0. When checking the schedule instance after the report should have run, the schedule shows last run date at the correct time, however no report is received in Email, and no report is produced and saved in the repository folder. I checked the view->messages log in jasper server, the jasperserver.log file, and the catalina.out log file and none show an error or any kind. We had a similar issue prior to upgrading from JS 3.0 to 3.7. In 3.0, we would get failed scheduled reports with a "NoSuchMethod" exception in the Scriptlet class. However, the same report would often run successfully in automated mode, and would always run successfully in manual mode. In the 3.0 case, at least we got some indication of the failure, in this case, we only know when someone complains of not receiving the report.

Found the issue in class com.jaspersoft.ireport.designer.compiler.prompt.PromptDialog Lines 120 - 144 The original code was getting a null pointer on line 128 becaue datetimePicker was never initialized for a java.util.Date Object. All other references in that area of the code pointed to datePicker instead. I changed line 128 to use datePicker and the method setFormats (rather than setDateFormat method of datetimePicker), rebuilt the project and got a new com-jaspersoft-ireport.jar, dropped that jar in my iReport-3.7.5\ireport\modules directory and restarted iReports. All works fine now. Snippets of code change attached.