Morning,
I had gone through testing in development and test to finally putting 4.4.5 and greenhopper 5.8.7 on our production system. With production for some reason, I am getting some errors not seen dev/test.
The errors a I seen in catalina.out:
012-03-19 05:15:55,184 TP-Processor10 INFO anonymous 315x3725x1 lv8ahw 130.96.202.53 /s/588/15/1/_/download/resources/jira.webresources:global-static/global.css atlassian.plugin.webresource.PluginResourceLocatorImpl Unable to find resource for plugin: jira.webresources:global-static and path: global.css
Mar 19, 2012 5:28:27 AM org.apache.tomcat.util.http.Parameters processParameters
WARNING: Parameters: Invalid chunk '' ignored.
Mar 19, 2012 5:28:28 AM org.apache.tomcat.util.http.Parameters processParameters
WARNING: Parameters: Invalid chunk '' ignored.
Is there some setting I am missing? Is this some procxy related thing? I am not sure what this is about.
Um, the thing I notice also is that Jira is really fast. Note that with test and dev I had to backup with xml backup export and restore the data to get it from the 4.2.1-b588 standalone to the new new 4.4.5 system. However, with production, I just started up the new JIra pointing at the old data and let it do its upgrade. I am wondering now if something that was removed before that is referenced in the database used the global-static.css and global.css styles, but now they are not needed. I do see that the old 4.2.1 had a lot more css files, but the new 4.4.5 has very few in the styles directory. Using the last backup xml from 4.2.1 now would be a real hassle as users are working on the new system now. Is there something in the database I can manually remove or some other step I can use to stop the whining messages for things apparently not needed now?
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.