Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Oops 500 Sorry, we had some technical problems during your last operation.

hsieh yiyu March 1, 2018

Hi,

I meet a problem that GUI display Oops 500 message.

Sorry, we had some technical problems during your last operation.

I capture the log (logs/atlassian-jira.log) display below:

Could you help me how to solve it? 

2018-03-01 19:14:15,790 http-nio-8080-exec-1 ERROR - [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet action threw exception
java.lang.NoClassDefFoundError: Could not initialize class webwork.dispatcher.GenericDispatcher
at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.prepareDispatcher(JiraWebworkActionDispatcher.java:196)
at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:133)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)
... 86 filtered
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)

 

 

2 answers

2 accepted

0 votes
Answer accepted
hsieh yiyu March 4, 2018

The issue happened on reboot JIRA.

The JIRA version is JIRA v7.4.3.

No help to restart.

Use JRASERVER 62486 can be solved this issue. Ths.

0 votes
Answer accepted
somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 2, 2018

Hi hsieh,

  • When do you experience this issue, e.g. when creating an issue, at setup, etc?
  • What version of JIRA are you on?
  • Does a restart help?

There is an older bug that was fixed in 7.3.9 that may match what you're seeing.  You can find it at JRASERVER - 62486: Accessing a non-existent url in JIRA during startup will break access to the instance until a restart is performed.

Let me know if that helps.  If not please provide the answers to the above questions and we'll go from there.

Cheers,

Branden

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events