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.

Additional info from iReports console I didn't initially see: java.lang.reflect.InvocationTargetException at java.awt.EventQueue.invokeAndWait(EventQueue.java:998) at javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1320) at com.jaspersoft.ireport.designer.compiler.prompt.Prompter.promptForParameters(Prompter.java:263) at com.jaspersoft.ireport.designer.compiler.IReportCompiler.run(IReportCompiler.java:706) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997) Caused by: java.lang.NullPointerException at com.jaspersoft.ireport.designer.compiler.prompt.PromptDialog.setParameter(PromptDialog.java:128) at com.jaspersoft.ireport.designer.compiler.prompt.Prompter$1.run(Prompter.java:68) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:104) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

Using iReports 3.7.5 I add a paramater to my report of type java.util.Date and check the "Use as Prompt" box I am not prompted for that parameter, or any paramaters that follow it in the list. I have moved the param around and the problem always follows the Date param. It doesn't matter how complex or simple the report. Example 3 params in a report P1 type String P2 type String P3 type Date When I run the report, I get prompted for P1 and P2, but not P3. Then change to P1 type String P2 type Date P3 type String Run this report, and I get prompted for P1, but not P2 OR P3 This only seems to happen when the type is java.util.Date. Change the type of the offending paramater, and it all works. Unforturnately, I require the Date type (which has worked fine until now)

I did delete the jaspersoft ji-jpivot directories in my local repository, and it somehow found the required jar after that.

sample settings.xml uploaded. I changed the local path to just say userid (this is from a win xp machine) I changed our internal repository location to just read ourRepo The main change that made it work for me was by setting the below values to false in both the standard and JasperServerDevProfile profiles <repository> <id>JasperForge Maven Repository</id> <url>http://www.jasperforge.org/maven2</url> <snapshots> <enabled>false</enabled> </snapshots> <releases> <enabled>false</enabled> </releases> </repository> I build by running mvn -PJasperServerDevProfile install

Found this solution on the JasperReports forum. http://jasperforge.org/plugins/espforum/view.php?group_id=102&forumid=103&topicid=80434 I just disabled the Jasper repository and didn't add the mirror, and my build is now working. Still something that needs fixed on the JF side I beilieve, but this at least go me around it.

The problem to me, seems to be with JasperServer Maven repository, or something related. My maven-metadata-JasperForge Maven Repository.xml file doesn't contain valid Maven data, but rather an html web page. See attached file. Also see a forum posting that jasperforge was down for updates on 10/20/2010. My guess is this broke something major.

I am having what appears to be a similar issue with building 3.7. I get the following reason for my error: Project ID: jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot Reason: Error getting POM for 'jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot' from th e repository: Unable to read local copy of metadata: Cannot read metadata from ' C:Documents and Settingsuserid.m2repositoryjaspersoftji-proji-jpivot-ui ji-jpivot3.7.0-SNAPSHOTmaven-metadata-JasperForge Maven Repository.xml': end tag name </td> must match start tag name <span> from line 263 (position: END_TAG seen ...</span></span></td>... @267:173) jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot:pom:3.7.0-SNAPSHOT for project jaspersoft.ji-pro.ji-jpivot-ui:ji-jpivot When I go to my local maven repository, it has file maven-metadata-JasperForge Maven Repository.xml, however that file is actually the HTML of a Jasper web page. My thought is that there is something wrong with their Maven/POM setup. Note: I do not use the Buildomatic scripts as they do not work for my application, however, I have built this successfully several times last week during some testing, and now when ready to deploy to production, I can't get a production build. Nothing has changed from my setup that worked last week.

My first thought would be use sub-reports for the detail. Make each subreport the correct size and place on the report next to each other. Not sure without trying if you will have to something to make the appear side by side instead of 1 under the other...

I am trying to understand the full build and install process for jasper server 3.5.0 CE, but am having dificulty with the final install. If I use the js-ant scripts described through the steps in the Source Build Guide, I get a running version on my local machine. If I remove the jasperserver directory from tomcat's webapps directory, and drop in the WAR file from jasperserver-war/target, it deploys, but will not run. Am seeing the following in the logs. org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'defaultWebDeploymentInformation' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Could not resolve placeholder 'quartz.web.deployment.uri' All of our deployments to date for 3.0 have been via dropping in a new WAR file, and I don't want to change from that.

Still no luck on this, but noticed one other clue to the issue. We use the Scriptlet to calculate some report params, like start and ending dates, and also use the Scriptlet to fill fields directly on the report. When calculating a parameter value, the default for the parameter is a Scriptlet function call that results in the default value. When filling the field on the report, the operation is the same, just the output field box is getting it's value from a Scriptlet function call rather than a datasource field. What I have noticed is that the parameter calls on the report always work, however the field fill intermittently fail. As noted in earlier posts, the field fill finds the Scriptlet method fine when run later manually, and often when run automatically. This condition seems to happen when: 1) The report is run as a scheduled report 2) The report is fill a field with data from a Scriptlet function call 3) Error is not Scriptlet method specific, just the first method encounted in the report fill