Home > An Internal > An Internal Server Error Occurred When Requesting Resource /rest/gadget/1.0/admin

An Internal Server Error Occurred When Requesting Resource /rest/gadget/1.0/admin

By azhdanov on Tue, 29 Nov 2011 12:54:19 -0800 2013-01-08T13:17:17+00:00 Andriy Zhdanov reporter Sorry, where do I find the logs in which stack trace would be expected? The http/https-difference COULD be a further lead - parallel to the installation of the plugin, we have been working on implementing https on the server. Sorry! Initially, it was giving an error of 'Internal server error' while trying to add any custom field but after indexing, it worked perfectly fine. Source

The view should show the projectid for the chosen project. Later that night I reindexed when no one was using JIRA.Flavio BeckOct 16, 2014Hi Mohin, are your dashboard gadgets pointing to a FILTER where do you have "issueFunction in dateCompare..." I Do not post bug reports, feature or support requests! Thanks MohinjiraCommentSameera Shaakunthala [inactive]Feb 06, 2014When this happens, the first thing you should do is saving the web page into a text file.

Refer to screenshot DateFormat.png AttachmentsOptionsSort By NameSort By DateAscendingDescendingThumbnailsListAttachments1.png2 kB12/Apr/2013 3:36 AMDateFormat.png266 kB31/Jul/2012 9:19 AMDueDate.png268 kB31/Jul/2012 9:19 AMPeriod.png206 kB31/Jul/2012 9:19 AMTimeSinceChart.png31 kB31/Jul/2012 9:19 AMIssue Links mentioned in Page Loading... clicking the link shows: {code:title=An internal error occurred when requesting resource /rest/gadget/1.0/admin.|borderStyle=solid} 500 java.lang.IllegalArgumentException: The datetime zone id is not recognised: GMT+01:00 {code} The error in the What happens if you refresh the page? Stack Trace: [hide] com.atlassian.jira.util.dbc.Assertions$NullArgumentException: user should not be null!

Could be all sorts of things. Please contact your JIRA instance administrator with the error that you have encountered. We have the same behaviour on our production system. By w.rutten on Thu, 15 Dec 2011 00:13:55 -0800 2013-01-08T13:17:25+00:00 Log in to comment Assignee Andriy Zhdanov Type bug Priority major Status invalid Component – Version – Votes 0 Watchers 1

Cheers,CommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software Printed by Atlassian Confluence 5.7.3, Team Collaboration Software. AttachmentsOptionsSort By NameSort By DateAscendingDescendingThumbnailsListAttachmentsJiraBug.png57 kB07/Sep/2011 11:27 AMJiraBug.png57 kB07/Sep/2011 11:23 AMActivity People Assignee: Unassigned Reporter: Wessel de Roode Votes: 0 Vote for this issue Watchers: 2 Start watching this issue Dates Maybe there is a delay before user information is propagated, but there is a bug if one tracker login page tells me there is an internal server error and another lists https://answers.atlassian.com/questions/6741/an-internal-server-error-occurred-when-requesting-resource-httphostname8080restgadget1.0login. board.jspa that then takes me to http://tracker.phpbb.com/login.jsp that fills the screen with the following.

Andriy Zhdanov jiratimesheet Issues Issues Issue #196 invalid [TIME-196] An internal server error occurred when requesting resource /rest/timesheet-gadget/1.0/timesheet.json Andriy Zhdanov repo owner created an issue 2013-01-08 Using Timesheet portlet from Timesheet ThanksCommentAdd your comment...10-1Andre Quadros PetryJul 29, 2014Check in your server.xml file if the context path is properly set. I do custom MODs. From catalina.out: 28.10.2010 10:46:43 com.sun.jersey.server.impl.application.WebApplicationImpl onException SEVERE: Internal server error java.lang.IllegalArgumentException: repeated interface: java.util.List at java.lang.reflect.Proxy.getProxyClass(Proxy.java:370) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:98) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at $Proxy37.getProjects(Unknown Source) at com.atlassian.jira.issue.search.parameters.lucene.DefaultPermissionQueryFactory.getQuery(DefaultPermissionQueryFactory.java:62) at com.atlassian.jira.jql.query.PermissionClauseQueryFactory.getPermissionQuery(PermissionClauseQueryFactory.java:102) at com.atlassian.jira.jql.query.PermissionClauseQueryFactory.getQuery(PermissionClauseQueryFactory.java:86)

By w.rutten/Walter Rutten on Mon, 28 Nov 2011 06:01:08 -0800 Comments (6) Andriy Zhdanov reporter Following the link in the message: {"html":"