efpaz

Hi, I've been having all sorts of broken pipe / connection timeout problems with a group of reports that uses a jdbc oracle connection (ojdbc5.jar) as datasource. I've tried increasing the value assigned to property name="poolTimeout" value="900" and set org.quartz.jobStore.misfireThreshold=180000 I've attached log excerpts from two of the errors i'm mentionning, it has been recomended in previous posts to use a dummy query setting like this: datasource.extra.params=validationQuery="select 1" to keep the connection pool alive or create a new one. Is it possible to implement that code in such way that'd only affect the oracle jdbc connection?, the reason i'm asking that is due to having multiple data sources to different dbms and that query would fail if run in mssql server probably generating noice in the log. Any help will be greatly appreciated. Thank you, Emanuel Code: Post Edited by emanuelfpaz at 08/09/2010 14:46 Post Edited by emanuelfpaz at 08/09/2010 14:48

Hi, we are having the exact same problem with jasperserver 3.1. After reviewing the source code we found out that the problem actually, doesn't appear to be a bug, dashboards do not support multi-value input controls or anything that has a collection data type. We've changed a method in the AdhocHelperImpl class to enable multi-value support, but we are missing something because the parameter still doesn't appear after adding the report that contains it to the dashboard. Any ideas or help about this would be greatly appreciated. Emanuel

We are experiencing exactly the same problem. We are using JServer 3.5.1. It worked perfectly before updating firefox from version 3.0.11 to 3.5 Best Regards, Emanuel

Hi, Thanks for your reply. That could be a possible way to do it, but the user wouldn't be able to see the history of schedules in the scheduled jobs page. And the ultimate goal for this is to also be able to track all the subscriptions history for monitoring and admininstration. I've read that by supposedly adding the line org.quartz.scheduler.isDurable = true in the js.quartz.base.properties file this issue should be addressed. But after a few tests there is no change in behavior. http://www.opensymphony.com/quartz/api/org/quartz/JobDetail.html Maybe quartz is not handling the life cycle of all the records in the JIReportJob* tables and QRTZ_ tables. My guess is that there must be a parameter in one of those config files that allows us to set the volatility to false and then the records in those tables won't be deleted. Thanks again, Emanuel

Hi All, I have detected that when you create a scheduled job, it is deleted immediately from the database after runs, making it impossible to keep a schedule history for admininstration and monitoring purposes. Is there a known way to address this? Are there any configuration files either native JasperServer or Quartz where I should change a flag, or something like this? Thanks in advance

Hi Matt, I'm currently in a development stage with Jasper Server Professional Version: 3.1.0 and I'm experiencing the same issues mentioned by zerglicious. I wonder if there already is a workaround for this and if it involves some type of configuration change that I'm missing. Thanks in advance, Emanuel

Hi, I've noticed that all input controls become mandatory regardless of the mandatory property setting. This happens when trying to use a report as a topic for an ad-hoc report, otherwise it works perfectly fine. Is there a way to override this? Thanks in advance.

Hi, I've noticed that all input controls become mandatory regardless of the mandatory property setting. This happens when trying to use a report as template for an ad-hoc report, otherwise it works perfectly fine. Is there a way to override this? Thanks in advance.