[Missing 'Link an Existing Input Control' iR-nb]

sad, can't update JS without that :(

[Objects permissions]

I installed the new JS 3.1, migrated the old 2.x database and upgraded with the scripts included in 3.1. But the user permissions haven't migrated properly! And now with the new gui I don't know how to assign user permissions to a specific report. There is a button to assign permissions to the folder selected, but how to do that to a report????

I'm trying to discover why the object permissions on JS 2.x aren't working in the same way on JS 3.x. I've two installations (with both versions). On the first (2.x) I try to change an user role, and when I relogin the folder assigned to that role appears. Doing the same on JS 3.x doesn't work. In 3.x release notes I can't view nothing about changes on object permissions...

Now I've only two solutions: stay on 2.x branch or migrate to OpenReports :(

[Missing 'Link an Existing Input Control' iR-nb]

no? :(

[Request: Speedup permissions]

It would be great :)

 

The permission screens are going very very slow yet, they aren't usable. I've created a PHP application/web that does the same but more easy and more more fast. It works direct with the jasperserver mysql tables. If there is someone interested tell me.

[Permissions on JS 3.1 (URGENT !!)]

Hi!

I installed the new JS 3.1, migrated the old 2.x database and upgraded with the scripts included in 3.1. But the user permissions haven't migrated properly! And now with the new gui I don't know how to assign user permissions to a specific report. There is a button to assign permissions to the folder selected, but how to do that to a report????

 

Thx

[Which JS version I have?]

Thx Lucianc!

[Which JS version I have?]

No 'releasenote' file or similar exist in JS folder. I installed JS over a existing Tomcat, not a bundled version.

 

Anandharaj, it's a good idea... When I could know my version I will put it in the title :)

 

Some developer can help? ;(

[jasperserver3.0 ubuntu 8.04 not work after reboot]

Why you start mysql in safe mode? Otherwise that's not seems to be the problem...

 

Look at Catalina (/usr/local/tomcat/logs in my case) and Jasperserver (/usr/local/tomcat/webapps/jasperserver/WEB-INF/logs/jasperserver.log in my case) logs, any suspicious error?

[Request: Speedup permissions]

I updated to JS 3.1 and the problem persists! :( 30 or more seconds wating on each screen of the permission page :(

[Missing 'Link an Existing Input Control' iR-nb]

Hi,

I'm trying the new JasperServer 3.1 with the new iReport 3.1.2-nb. I've created a new input control in the repository and I want to link it to a Report Unit. In previous iReports (no Net Beans based) I had the option 'Link an Existing Input Control' inside the folder 'Input controls' of the Report Unit. Now I can't see this option, it's not possible yet? Can I work with iReport 3.0 classic or is there compatibily errors with JS 3.1?

 

Thx

[Which JS version I have?]

Simple question, I guess...

I've an installation of JS on a GNU Linux host but I don't remember which version it is, 3.0 or 3.1. How can I discover the version I've installed?

[JasperServer 3.1.0 Released]

Solved my last problem, new one posted on: http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=48943&res=5

[Error upgrading to JS 3.1]

Problem solved.. I haven't read the Upgrade Guide: js.quartz.properties, js.mail.properties and js.scheduler.properties now are in one file: js.quartz.properties Seems like no connection with my MySQL database:  In my context.xml I've changed 'root' with 'jasperdb' but when I restart tomcat the logs continue with 'root' access denied. Some idea? Thx :(

Code:

SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateRepositoryService' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'schedulingReportDeleteListener' while setting bean property 'repositoryListeners' with key [2]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulingReportDeleteListener' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportSchedulingService' while setting bean property 'schedulingService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingService': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingFacade' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportQuartzScheduler' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportQuartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulingReportDeleteListener' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportSchedulingService' while setting bean property 'schedulingService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingService': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingFacade' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportQuartzScheduler' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportQuartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingService': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingFacade' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportQuartzScheduler' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportQuartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingFacade' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportQuartzScheduler' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportQuartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportQuartzScheduler' while setting bean property 'target'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportQuartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportQuartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]] Caused by: org.quartz.SchedulerConfigException: Failure occured during job recovery. [see nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.JasperServerScheduler': org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES)) [see nested exception: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))]]



Post Edited by Dimas at 11/26/08 11:52

[Error deploying WAR on Tomcat6]

Thx to all. Finally I had to uninstall the tomcat6 package from the Ubuntu repositories and make a new and manual install. That worked for JasperServer 3.0.

[Error upgrading to JS 3.1]

I upgraded and have that error when starting:

Nov 26, 2008 10:16:09 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'reportSchedulerMailSender' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Could not resolve placeholder 'report.scheduler.mail.sender.host'

Nov 26, 2008 10:16:09 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.jaspersoft.jasperserver.war.util.SpringBeanServletContextPlublisher
org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'reportSchedulerMailSender' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Could not resolve placeholder 'report.scheduler.mail.sender.host'

I've deployed the new war and restored my configuration files, including 'js.mail.properties'. That contains:

report.scheduler.mail.sender.host=localhost
report.scheduler.mail.sender.username=
report.scheduler.mail.sender.password=
report.scheduler.mail.sender.from=informatica@htrueta.scs.es
report.scheduler.mail.sender.protocol=smtp
report.scheduler.mail.sender.port=25

I've seen that on the original 3.1 WAR file there isn't any js.mail.properties. That's normal?

[JasperServer 3.1.0 Released]

I upgraded and have that error when starting:

Nov 26, 2008 10:16:09 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'reportSchedulerMailSender' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Could not resolve placeholder 'report.scheduler.mail.sender.host'

Nov 26, 2008 10:16:09 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class com.jaspersoft.jasperserver.war.util.SpringBeanServletContextPlublisher
org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'reportSchedulerMailSender' defined in ServletContext resource [/WEB-INF/applicationContext-report-scheduling.xml]: Could not resolve placeholder 'report.scheduler.mail.sender.host'

I've deployed the new war and restored my configuration files, including 'js.mail.properties'. That contains:

report.scheduler.mail.sender.host=localhost
report.scheduler.mail.sender.username=
report.scheduler.mail.sender.password=
report.scheduler.mail.sender.from=informatica@htrueta.scs.es
report.scheduler.mail.sender.protocol=smtp
report.scheduler.mail.sender.port=25

I've seen that on the original 3.1 WAR file there isn't any js.mail.properties. That's normal?

[Error deploying WAR on Tomcat6]

Thx for the blog reference. I've done the installation similar to the blog instructions, but with mysql. At the first time I start the tomcat with the jasperserver deployed the errors appear on log.

I tried to attach the logs with the forum, but it not seems to work. I uploaded it to this location: http://www.dimas.cat/logs.zip

 

Thx! :)

[Error deploying WAR on Tomcat6]

Hi!

I've installed an Ubuntu Server 8.10 with the Tomcat6 packages. Tomcat6 is running ok, as well as the manager, but I can't deploy the JasperServer 3.0. I followed the instructions from the JasperServer Install Guide but it don't start. I attach the logs with the errors, I can't understand it. Someone can help? Thx

The logs: http://www.dimas.cat/logs.zip

Post Edited by Dimas at 11/07/08 14:59

["Access denied" on Exit]

I use LDAP authentication, the users can login normally but they can't logout ;(

["Access denied" on Exit]

When a user press the Exit button to logout appears an error page saying:

 

HTTP Status 403 - Access is denied

type: Status report

message: Access is denied

description: Access to the specified resource (Access is denied) has been forbidden.

 

The URL is: http://10.80.167.205:8080/jasperserver/exituser.html?curlnk=4

 

With admin users (like jasperadmin or a ldap root) it doesn't happens.

 

Any ideas?

[Daylight saving (Date not updated)]

I solved that. The problem was from Java, not JasperServer or tomcat.

 

I've updated the time zone information in both server (ubuntu) and java. To update the java time zone information I've used the tzupdater utility (free on sun webpage).

[Daylight saving (Date not updated)]

Hi,

 

In Europe the last saturday we advance one hour: from 2AM to 3AM.

 

We have a Linux server with tomcat+jasperserver. The date from the server is ok (date command returns a correct date) but in tomcat and jasperserver there is the old time (one hour later).

 

Can someone help me with that?

 

Thx !!!

[Request: Speedup permissions]

The problem is in permissions editing screen, the rest of operations work fine and fast.

[Request: Speedup permissions]

I've configured JasperServer to integrate with our LDAP directory, importing automatically all the users and their rols when they login to the Jasper.

 

Now, when we are managing the reports permissions and we make a change it goes very very slow to save it, and to change the listing page.

 

Can you optimize that for a next version?

 

Thx and congrats for the work.

[Decode on Where clause (Oralce) give empty report]

I've detected that using decode inside a where clause JasperServer don't recognize it and returns an empty report. I can run the same select with Toad and iReports and they give me results, but not with JasperServer. It's a recognized bug?

 

If I cut this code from the sql JasperServer works ok:

 

where dcp072 = decode(to_char(sysdate,'D'),'5',to_date(to_char(sysdate + 3,'dd/mm/yyyy'),'dd/mm/yyyy'),to_date(to_char(sysdate + 1,'dd/mm/yyyy'),'dd/mm/yyyy'))