Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.4.2
-
3.04
-
Description
It looks like we have a bug where Velocity isn't initialized correctly. This is from a customer's logs:
2006-01-17 22:12:17,028 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Professional Edition, Version: 3.4.2-#108^M 2006-01-17 22:12:17,028 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Configured to use database: mssql^M 2006-01-17 22:12:17,121 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] ^M ^M *******************************************************************************************************^M JIRA 3.4.2 build: 108 (Professional Edition) started. You can now access JIRA through your web browser.^M *******************************************************************************************************^M ^M [Filter: profiling] Using parameter [jira_profile]^M [Filter: profiling] defaulting to off [autostart=false]^M [Filter: profiling] Turning filter off [jira_profile=off]^M 2006-01-17 22:12:19,215 [webwork.dispatcher.ServletDispatcher] Unable to find 'webwork.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir^M Jan 17, 2006 10:12:19 PM org.apache.coyote.http11.Http11Protocol start^M INFO: Starting Coyote HTTP/1.1 on http-9090^M Jan 17, 2006 10:12:19 PM org.apache.catalina.storeconfig.StoreLoader load^M INFO: Find registry server-registry.xml at classpath resource^M Jan 17, 2006 10:12:20 PM org.apache.catalina.startup.Catalina start^M INFO: Server startup in 15140 ms^M 2006-01-17 22:12:27,590 ERROR [com.atlassian.velocity.DefaultVelocityManager] Exception getting message body from Velocity: java.lang.NullPointerException^M java.lang.NullPointerException^M at org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:294)^M at org.apache.velocity.runtime.RuntimeInstance.getTemplate(RuntimeInstance.java:831)^M at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:440)^M at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:76)^M at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:60)^M at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:55)^M at com.atlassian.jira.plugin.JiraResourcedModuleDescriptor.getHtml(JiraResourcedModuleDescriptor.java:88)^M at com.atlassian.jira.plugin.renderer.JiraRendererModuleDescriptor.getCss(JiraRendererModuleDescriptor.java:63)^M at org.apache.jsp.styles.global_005fprintable_005fcss_jsp._jspService(org.apache.jsp.styles.global_005fprintable_005fcss_jsp:2036)^M at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)^M at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)^M at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)^M
The correct version of Velocity (1.4) can be checked out with svn co http://svn.apache.org/repos/asf/jakarta/velocity/engine/tags/VEL_1_4 velocity. At ResourceManagerImpl.java:294 we find:
Resource resource = globalCache.get(resourceName);
Where globalCache would have been set when initialize() is called. Apparently it isn't called when Velocity is used from a plugin.
Attachments
Issue Links
- duplicates
-
JRASERVER-8517 NPE from Velocity during data backup importing.
- Closed