Today I updated ictime. After this operation ictime stopped to work making some pages (such as project details) unusable.
I have to disable it to continue to use JIRA (without ictime)
I've tried to uninstall/reinstall the plugin, unsuccessfully
The trace log is very long.. these are some lines
2013-03-28 18:36:25,307 ajp-bio-8109-exec-24 ERROR torriani 1116x1704x2 4eqfex 172.27.1.182 /rest/ictime/1.0/rest/checkPermission [atlassian.plugin.servlet.DefaultServletModuleManager] Unable to create filter
com.atlassian.util.concurrent.LazyReference$InitializationException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'de.iconcept.ictime.rest.RestResource': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [de.iconcept.ictime.rest.RestResource]: Constructor threw exception; nested exception is java.lang.NullPointerException
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'de.iconcept.ictime.rest.RestResource': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [de.iconcept.ictime.rest.RestResource]: Constructor threw exception; nested exception is java.lang.NullPointerException
Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [de.iconcept.ictime.rest.RestResource]: Constructor threw exception; nested exception is java.lang.NullPointerException
at de.iconcept.ictime.services.DefaultReportService.initSQLProcessor(DefaultReportService.java:160)
at de.iconcept.ictime.services.DefaultReportService.<init>(DefaultReportService.java:96)
at de.iconcept.ictime.rest.RestResource.<init>(RestResource.java:230)
After analyzing the logs I found the problem and was able to fix it. There will be a new release in the next days with some more bugfixes. Thank you very much for the information you gave us.
The new release 2.3.7 is available now. The problem you had was caused by a missing attribute in your dbconfig.xml (probably the "schema-name" tag), which has no influence on JIRA but was causing a null pointer exception in our plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For the moment I would recommend you to try to get back to the last version that worked for you, i.e. you uninstall the plugin and re-install the version you had before. Please provide the complete stacktrace to jiraplugins@interconcept.de, together with the following information:
- database you are using (MySQL, PostgreSQL, Oracle, ...)
- your JIRA version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another question, you updated from which ictime version to which ictime version?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
unfortunately I hav trouble with my backup
I sent you an email to your address
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.