You'll need to explain your setup, and I'd strongly suggest reading your log file, as that will tell you where the "null" is coming from. Even if it's a techy thing and you can't read it, we can't help you with just "Error" or "null" - we need to know what it's reporting in the background
Your log files will contain errors telling us what is happening when you get this error on-screen. The logs will be a lot more detailed and technical. I'm afraid just saying "error" without explaining what you are doing, what you have set up or anything else you are seeing is not going to get you far, you need to look at the resources you have to help you - logs, repeating the problem, examining the configuration and seeing what it *might* be
2014-05-11 20:40:38,779 FelixDispatchQueue ERROR [osgi.container.felix.FelixOsgiContainerManager] Framework error in bundle com.atlassian.plugins.atlassian-whitelist-api-plugin
org.osgi.framework.BundleException: Unresolved constraint in bundle com.atlassian.plugins.atlassian-whitelist-api-plugin : Unable to resolve 111.0: missing requirement [111.0] package; (package=com.atlassian.activeobjects.external) [caused by: Unable to resolve 26.0: missing requirement [26.0] package; (&(package=com.atlassian.plugin.osgi.bridge.external)(version>=2.6.5)) [caused by: Unable to resolve 5.0: missing requirement [5.0] package; (package=org.springframework.beans) [caused by: Unable to resolve 2.0: missing requirement [2.0] package; (&(package=org.apache.commons.logging)(version>=1.0.4)(!(version>=2.0.0))) [caused by: Unable to resolve 9.0: missing requirement [9.0] package; (&(package=org.slf4j)(version>=1.6.4))]]]]
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:54) <+5> (StandardContext.java:4939) (StandardContext.java:5434) (LifecycleBase.java:150) (ContainerBase.java:1559) (ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
You have an idea where is the problem?
You've probably got a broken plugin (what plugins have you installed? Are you 100% sure the versions you've installed are compatible with your version of Jira?).
Or you've amended something in the installation that has broken it - have you made any tweaks? How did you install it? Have a look at the system information page and check the classpath, version of Java, and that the "modified files" list is nice and short.
But, first, try clearing the plugin cache - https://confluence.atlassian.com/display/CONFKB/How+to+Clear+Confluence+Plugins+Cache
I have these add-ons:
Gantt-Chart Project for JIRA - Free
Analytics Client Plugin
Atlassian Universal Plugin Manager Plugin
HipChat Core Plugin
HipChat for JIRA
InProduct translation for JIRA
JIRA GitHub Issue Importer
JIRA iCalendar Plugin
JIRA Importers Plugin (JIM)
JIRA Polish (Poland) Language Pack
JIRA Service Desk
JIRA Service Desk Polish (Poland) Language Pack
JIRA Toolkit Plugin
JIRA Working Hours Plugin
Redmine Importers Plugin for JIM
Support Tools Plugin
Has the error message in the log changed though?
I think we need to look at your overall installation though. How was this instance created? What have you changed? What does the system information page say about "modified files", your version of Java, your version of Jira and the versions of the plugins you have?
Instance was created by my host company on my server.
Everything is working properly and than problems come from nowhere. I have a information to chance HSL DB for MySQL and we did it yesterday. Everything is working but without Service Desk.
- modified files: [Instalation type: Standalone] jira-application.properties
Wersja Java 1.7.0_25
Dostawca Java Oracle Corporation
Wersja JVM 1.7
Dostawca JVM Oracle Corporation
Wersja implementacji JVM 23.25-b01
Java Runtime Java(TM) SE Runtime Environment
Java VM Java HotSpot(TM) 64-Bit Server VM
Sterownik bazy danych MySQL Connector Java mysql-connector-java-5.1.30 ( Revision: email@example.com)
Numer wersji 6260
So "I don't change anything in my setup. That error comes from nowhere..." is wildly inaccruate and we could have been chasing completely the wrong thing. You've made an infrastructural change and not considered that could be part of the problem?
It's the right thing to do - HSQL is not suitable for production, but the migration is the FIRST thing you should have said, not said you haven't change anything.
So. How did you do the migration? What did you change as part of the migration?
I've checked the integrity in http://IP_adress:8080/secure/admin/IntegrityChecker.jspaand there is a problem with:
Check workflow integrity <input type="checkbox" name="integrity_check_4_6" value="6" checked="checked"/> Check you have entered are correct workflow statuses
ERROR: XX-84 - workflow entry with id 10229 has an incorrect status. (JRA-4241)
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot