I am evaluating Jira 6.2.7 on our staging server. When creating an issue, the create issue popup does not close, but the issues get created... Problem occurs with IE9, Firefox and Chrome.
No error is logged in atlassian-jira.log, but in firefox web-console a HTTP 500 error is shown:
[16:28:59.556] POST http://xxx.xxx/secure/QuickCreateIssue.jspa?decorator=none
[HTTP/1.1 500 Internal Server Error 370ms]
Details:
Request-URL:
http://xxx.xxx/secure/QuickCreateIssue.jspa?decorator=none
Request-Methode:
POST
Status-Code:
HTTP/1.1 500 Internal Server Error
Request-Header
16:28:59.000
X-Requested-With:XMLHttpRequestX-AUSERNAME:adminUser-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0Referer:http://xxx.xxx/secure/Dashboard.jspa Pragma:no-cacheHost:xxx.xxxContent-Type:application/x-www-form-urlencoded; charset=UTF-8Content-Length:620Connection:keep-aliveCache-Control:no-cacheAccept-Language:de-de,de;q=0.8,en-us;q=0.5,en;q=0.3Accept-Encoding:gzip, deflateAccept:*/*
Gesendetes Cookie
JSESSIONID:26215EE2533DBFB7557DB0E4C3711A53atlassian.xsrf.token:BG0Z-TTHO-B8UJ-5139|57e5408fd7a5bd48982248e8f583dc2755efa0e9|lin__utmz:1.1408543605.1.1.utmcsr__utmc:1__utmb:1.4.10.1408630707__utma:1.1799610962.1408543605.1408627649.1408630707.5
Response-Header
Δ350ms
X-Seraph-LoginReason:OKX-Content-Type-Options:nosniffX-AUSERNAME:adminX-ASESSIONID:1ok83blX-ASEN:SEN-L2809694X-AREQUESTID:988x7701x1Transfer-Encoding:chunkedServer:Apache-Coyote/1.1Pragma:no-cacheExpires:Thu, 01 Jan 1970 00:00:00 GMTDate:Thu, 21 Aug 2014 14:28:59 GMTContent-Type:text/html;charset=UTF-8Connection:closeCache-Control:no-cache, no-store, must-revalidate
[16:28:59.883] ajax[59339480] error : {
successful : false,
status : 500,
statusText : error,
hasData : true,
readyState : 4,
requestId : 59339480,
aborted : undefined,
}
Community moderators have prevented the ability to post new answers.
Ok, I got it. The Listener mentioned in the StackTrace was still active. After delete creating issues is working... Thank you Alexey for pointing me to the solution!
Try to use something like firebug to rerun the request - and get more details from 500 error. Error was found - it was undeleted listener - so the tickets were created normally but failed when events were fired.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With Firebug I can see the following error:
java.lang.NoClassDefFoundError: com/atlassian/jira/security/JiraAuthenticationContext</pre><blockquote id="stacktrace" style="overflow-x: auto;"><pre>java.lang.NoClassDefFoundError: com/atlassian/jira/security/JiraAuthenticationContext at de.polscheit.jira.listener.GanttPlanningDatesSync.issueCreated(GanttPlanningDatesSync.java:343) at com.atlassian.jira.event.issue.AbstractIssueEventListener.workflowEvent(AbstractIssueEventListener.java:100) at com.atlassian.jira.event.issue.IssueEventListenerHandler$IssueEventInvoker.invoke(IssueEventListenerHandler.java:51) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$2.run(AsynchronousAbleEventDispatcher.java:66) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1.execute(AsynchronousAbleEventDispatcher.java:32) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:60) at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160) at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79) at com.atlassian.jira.event.issue.DefaultIssueEventManager.publishEvent(DefaultIssueEventManager.java:124) ...
We had installed "JIRA Gantt-Chart Plugin" before, but it got deinstalled... Is that an artifact of this plugin? How do I get rid of that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.