-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
2.4.1
-
2.04
-
10-sep-2003 12:39:24 org.enhydra.jdbc.util.Logger info
INFO: GenericPool:cleanUp done min=2 max=50 count=2
10-sep-2003 12:41:45 webwork.dispatcher.ServletDispatcher service
SEVERE: Could not execute action
java.lang.NullPointerException
at com.atlassian.jira.web.action.issue.EditIssue.doDefault(EditIssue.jav
a:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:413)
at webwork.action.ActionSupport.execute(ActionSupport.java:142)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport
.java:44)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.
java:131)
[JRASERVER-2311] Java error: Could not execute action (webwork.dispatcher)
Milo van der Linden
added a comment - I have upgraded my database to Oracle. JIRA's speed went up four times! And the strange crashes seem to have ended.
Is there a limit to the ammount of issues that can be held by the hsql version?
Thanks anyway, I consider this incident closed.
Kind regards.
Milo van der Linden
added a comment - I have upgraded my database to Oracle. JIRA's speed went up four times! And the strange crashes seem to have ended.
Is there a limit to the ammount of issues that can be held by the hsql version?
Thanks anyway, I consider this incident closed.
Kind regards. 
Jeff Turner
added a comment - The stacktrace you posted came from the Edit Issue page. It wouldn't cause the dashboard to go blank. Is it possible these are two unrelated problems?
Could you send a zipped copy of logs/catalina.out to support@atlassian.com? That will contain more relevant information than atlassian-jira.log
If you don't mind sending us (support@atlassian.com) your data, that would also help us replicate the problem(s). It can be done in the Administration section of JIRA, in the 'Support Request' page listed on the left.
I'm not aware of any problems directly attributable to hsqldb, but migrating to an enterprise database certainly wouldn't hurt. Docs on this process available at
http://www.atlassian.com/software/jira/docs/latest/standalone-dbconfig.html
Cheers,
--Jeff
Jeff Turner
added a comment - The stacktrace you posted came from the Edit Issue page. It wouldn't cause the dashboard to go blank. Is it possible these are two unrelated problems?
Could you send a zipped copy of logs/catalina.out to support@atlassian.com? That will contain more relevant information than atlassian-jira.log
If you don't mind sending us (support@atlassian.com) your data, that would also help us replicate the problem(s). It can be done in the Administration section of JIRA, in the 'Support Request' page listed on the left.
I'm not aware of any problems directly attributable to hsqldb, but migrating to an enterprise database certainly wouldn't hurt. Docs on this process available at
http://www.atlassian.com/software/jira/docs/latest/standalone-dbconfig.html
Cheers,
--Jeff Milo van der Linden
added a comment - I am getting fed up with this! The last two weeks I have been restarting JIRA daily!
Could you guys please look into my problem more seriously?
Do I need to step away from the hsql database?
What database do you suggest then and can I connect it to the standalone version?
Will the problem really be solved once I select a more solid database?
Milo van der Linden
added a comment - I am getting fed up with this! The last two weeks I have been restarting JIRA daily!
Could you guys please look into my problem more seriously?
Do I need to step away from the hsql database?
What database do you suggest then and can I connect it to the standalone version?
Will the problem really be solved once I select a more solid database? Milo van der Linden
added a comment - This morning JIRA crashed again. I managed to pick up the log and added it to provide more information on our crashes. I will continu to do this in order for you guys to get a better overview on the issue.
Milo van der Linden
added a comment - This morning JIRA crashed again. I managed to pick up the log and added it to provide more information on our crashes. I will continu to do this in order for you guys to get a better overview on the issue. Milo van der Linden
added a comment - We use the JIRA standalone 2.4.1 #55. This problem occurs twice a day. All of a sudden the dashboards go blank and no one can log in anymore.
Milo van der Linden
added a comment - We use the JIRA standalone 2.4.1 #55. This problem occurs twice a day. All of a sudden the dashboards go blank and no one can log in anymore.
Mike Cannon-Brookes
added a comment - Milo,
Could you give us a little more context about the error?
What application server are you using? What database / JDK?
What were you doing when it occurred? Does it always happen?
Cheers,
Mike
Mike Cannon-Brookes
added a comment - Milo,
Could you give us a little more context about the error?
What application server are you using? What database / JDK?
What were you doing when it occurred? Does it always happen?
Cheers,
Mike 
hsql data is limited by the amount of JVM memory available. If you didn't have a particularly massive amount of data, I'm not sure why it would be slow. Anyway, glad the problem is solved for you. I'll close the bug.