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

When I tried to pick up this issue after implementation of https, it appeared to work correctly. You should test more to see if it's just one *type* of gadget, or if it's constant (every time you go to your dashboard) or intermittent. 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? I do custom MODs. this content

Top bonelifer Moderator Team Posts: 101 Joined: Mon Jan 31, 2005 10:41 am Re: Cannot login in Tracker Quote Post by bonelifer » Mon Dec 10, 2012 3:42 am If you Thanks for replying though Top bonelifer Moderator Team Posts: 101 Joined: Mon Jan 31, 2005 10:41 am Re: Cannot login in Tracker Quote Post by bonelifer » Mon Jul 09, 2012 Atlassian Summit is Oct 10 - 13 in San Jose, CA – Register soon before tickets sell out. What happens if you refresh the page? https://jira.atlassian.com/browse/JRA-25602

JVM Version : 1.0 JVM Vendor : Sun Microsystems Inc. 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. After retrying&retrying it suddenly started to work! Top Finn Skovgaard Registered User Posts: 1 Joined: Fri Nov 23, 2012 9:34 pm Re: Cannot login in Tracker Quote Post by Finn Skovgaard » Fri Nov 23, 2012 9:48 pm

I don't know what was the problem earlier. I wanted to create a ticket. The user name is "Finn Skovgaard" so not null, contrary to what the error message says. at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:26) at com.atlassian.jira.security.login.LoginManagerImpl.authorise(LoginManagerImpl.java:135) at com.atlassian.jira.security.JiraRoleMapper.canLogin(JiraRoleMapper.java:46) at com.atlassian.seraph.auth.DefaultAuthenticator.isAuthorised(DefaultAuthenticator.java:229) at com.atlassian.seraph.auth.DefaultAuthenticator.authoriseUserAndEstablishSession(DefaultAuthenticator.java:197) at com.atlassian.seraph.auth.DefaultAuthenticator.login(DefaultAuthenticator.java:102) at com.atlassian.crowd.integration.seraph.v22.CrowdAuthenticator.login(CrowdAuthenticator.java:133) at com.atlassian.seraph.filter.PasswordBasedLoginFilter.runAuthentication(PasswordBasedLoginFilter.java:127) at com.atlassian.seraph.filter.PasswordBasedLoginFilter.login(PasswordBasedLoginFilter.java:72) at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:130) at com.atlassian.jira.web.filters.JiraLoginFilter.doFilter(JiraLoginFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:46) at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66) at

But if I click under Administration -> Logging & Profiling -> Profiling -> "Enable Profiling" and return to Dashboard then I see error An internal server error occurred when requesting resource If possible, try a re-index. (It may take some time to complete and users will not be able to access JIRA during re-index)Kentaro ParsonsAug 28, 2014Just in case this helps someone, 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 https://answers.atlassian.com/questions/6741/an-internal-server-error-occurred-when-requesting-resource-httphostname8080restgadget1.0login. posting here won't increase your post count (or shouldn't!).

In my perception, no measure has been executed that directly caused the plugin to start working. Can anyone help me? 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 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)

Forum rules Please do not post any "phpBB" specific topics here unless they do not fit into the category above. Sorry! Do not post bug reports, feature or support requests! The view should show the projectid for the chosen project.

But after picking the project I receive the error. news Do not post bug reports, feature or support requests! If I didn't look for that specifc option (filter was: [customfield] IN (option1, option2, etc), everything was fine. Top ira88 Registered User Posts: 0 Joined: Sat Dec 08, 2012 2:45 pm Contact: Contact ira88 Website Re: Cannot login in Tracker Quote Post by ira88 » Sat Dec 08, 2012

If this problem persists, please contact your JIRA administrators. Memory Information: Total Memory: 2730 MB Free Memory: 2012 MB Used Memory: 718 MB Total PermGen Memory: 256 MB Free PermGen Memory: 100 MB Used PermGen Memory: 155 MB System Information: Here my atlassian-plugin.xml: and here the gadget.xml: I don't have access to the log. have a peek at these guys JVM Implementation Version : 20.1-b02 Java Runtime : Java(TM) SE Runtime Environment Java VM : Java HotSpot(TM) 64-Bit Server VM User Name : jira User Timezone : Europe/London User Locale :

at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:26) at com.atlassian.jira.security.login.LoginManagerImpl.authorise(LoginManagerImpl.java:135) at com.atlassian.jira.security.JiraRoleMapper.canLogin(JiraRoleMapper.java:46) at com.atlassian.seraph.auth.DefaultAuthenticator.isAuthorised(DefaultAuthenticator.java:229) at com.atlassian.seraph.auth.DefaultAuthenticator.authoriseUserAndEstablishSession(DefaultAuthenticator.java:197) at com.atlassian.seraph.auth.DefaultAuthenticator.login(DefaultAuthenticator.java:102) at com.atlassian.crowd.integration.seraph.v22.CrowdAuthenticator.login(CrowdAuthenticator.java:133) at com.atlassian.seraph.filter.PasswordBasedLoginFilter.runAuthentication(PasswordBasedLoginFilter.java:127) at com.atlassian.seraph.filter.PasswordBasedLoginFilter.login(PasswordBasedLoginFilter.java:72) at com.atlassian.seraph.filter.BaseLoginFilter.doFilter(BaseLoginFilter.java:130) at com.atlassian.jira.web.filters.JiraLoginFilter.doFilter(JiraLoginFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:46) at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66) at If I disable profiling, then it is working again. Otherwise, please create a support issue on our support system at http://support.atlassian.com with the following information: a description of your problem cut & paste the error and system information found below

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":"