Home > Unable To > Jira Unable To Retrieve Gadget Xml Http Error 404

Jira Unable To Retrieve Gadget Xml Http Error 404

Contents

HTTP error 504 when adding Confluence gadget to JIRA dashboard Resolved mentioned in Page Loading... See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright © The problem is caused by running out of memory.Increase your memory allocationto 768MB or higher. Atlassian Documentation  Log in JIRA Knowledge Base Missing gadget , Error occurred while retrieving gadget spec for rest/gadgets/1.0/g/com.atlassian.jira.gadgets Symptoms A dashboard is not able to load a gadget. http://quiddityweb.com/unable-to/jira-unable-to-retrieve-gadget-xml-http-error-504.html

Enable the Text (text-gadget) module in the Gadgets Plugin - OR - related plugin which is missing Was this helpful? HTTP error 500 -- url: /admin/addgadget.action | userName: aj | referer: http://confluence-URL/admin/addgadget.action | action: addgadget Around the same time, the following appears in theatlassian-jira.logJIRA log: 2012-10-02 08:01:03,381 http-8080-11 ERROR [500ErrorPage.jsp] Exception HTTP error 500 What reason to lead to this problem? Why was this unhelpful?

Error Occurred While Retrieving Gadget Spec

Report a bug Atlassian News Atlassian Atlassian Documentation  Log in JIRA Knowledge Base Gadgets do not display when failing to access XML specification Symptom When integrating JIRA with a proxy However, none of the gadget will show up in theMacro Browser. Cause JIRA Gadgets use the extensible REST Plugin Module framework, which provides access to resources via URI paths. Was this helpful?

Was this helpful? Do note that JIRA is required to perform a full re-index upon removing the indexes directory. Specify scheme/proxyName/proxyPort attributes in JIRA Connector, e.g.

Cause TheAtlassian JIRA - Plugins - Gadgets Plugin is disabled. HTTP error 404 Plus the Road Map gadget no longer appears as an option for adding to the dashboard. The gadget is displaying the error so by removing it there shouldn't be an error message. Yes No Thanks for your feedback!

You will need a .p7b and .jks file: keytool -import -trustcacerts -alias server -file .p7b -keystore .jks Add the following line to iptables: iptables -t nat -A OUTPUT -p tcp -d Unfortunately for Jira OnDemand version I can't execute a SQL query for database.Ivar SønstabøApr 28, 2014I know Alexey, it was more information to Mauro :) But I assume that, if the Shutdown JIRA, remove the plugin from theinstalled-pluginsfolder, restart JIRA. Edit /conf/server.xml (Standalone), or /conf/server.xml for Ear-War deployment.

Jira This Gadget Cannot Be Displayed On Your Dashboard

Best regards,Mauro CommentAlexey LitvishkoApr 27, 2014Thank you, Mauro. HTTP error 504 at com.atlassian.gadgets.directory.internal.impl.ConfigurableExternalGadgetSpecDirectoryEntryProvider.validateGadgetSpec(ConfigurableExternalGadgetSpecDirectoryEntryProvider.java:140) at com.atlassian.gadgets.directory.internal.impl.ConfigurableExternalGadgetSpecDirectoryEntryProvider.access$100(ConfigurableExternalGadgetSpecDirectoryEntryProvider.java:32) at com.atlassian.gadgets.directory.internal.impl.ConfigurableExternalGadgetSpecDirectoryEntryProvider$1.doInTransaction(ConfigurableExternalGadgetSpecDirectoryEntryProvider.java:77) at com.atlassian.sal.co re.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25) at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:34) <+2> (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129) at com.sun.proxy.$Proxy98.doInTransaction(Unknown Source) <+2> (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) at com.sun.proxy.$Proxy98.doInTransaction(Unknown Error Occurred While Retrieving Gadget Spec JIRA or GreenHopper gadget): 2012-10-02 08:01:03,432 WARN [http-8090-6] [gadgets.renderer.internal.GadgetSpecFactoryImpl] getGadgetSpec Error occurred while retrieving gadget spec for http://jira-URL/rest/gadgets/1.0/g/com.pyxis.greenhopper.jira:greenhopper-gadget-project-dashboard/gadgets/greenhopper-project-dashboard.xml -- url: /admin/addgadget.action | userName: aj | referer: http://confluence-URL/admin/addgadget.action | action: addgadget 2012-10-02 Unable To Retrieve Gadget Xml. Http Error 500 Why was this unhelpful?

The JIRA self-generated outgoing URL fails to access the requested spec XML. Check This Out The following error is present where the gadget should be: Error loading gadget from rest/gadgets/1.0/g/com.atlassian.jira.gadgets/gadgets/login.xml: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. HTTP error 504 at org.apache.shindig.gadgets.DefaultGadgetSpecFactory.fetchObjectAndCache(DefaultGadgetSpecFactory.java:127) at org.apache.shindig.gadgets.DefaultGadgetSpecFactory.getGadgetSpec(DefaultGadgetSpecFactory.java:90) at com.atlassian.gadgets.renderer.internal.local.LocalGadgetSpecFactory.getGadgetSpec(LocalGadgetSpecFactory.java:82) at com.atlassian.gadgets.renderer.internal.local.LocalGadgetSpecFactory.getGadgetSpec(LocalGadgetSpecFactory.java:64) at com.atlassian.gadgets.renderer.internal.GadgetSpecFactoryImpl.getGadgetSpec(GadgetSpecFactoryImpl.java:140) Steps to reproduce the problem Setup 2 JIRA instances Turn on "Use gzip compression" setting in first JIRA scheme="your_request_scheme" proxyName="your_proxy_name" proxyPort="your_proxy_port" /> notes: scheme should be either http or https, which's consistent with the request scheme used to access proxy (instead of JIRA application server). Jira Not All Gadgets Have Loaded

Thanks for the help.jirajira-cloudcloudCommentCommentAdd your comment...1 answer10-1Mauro Fernandez Badii [Atlassian]Mar 19, 2014Hi Norbert, This message is appearing on newly created instances and was reported on issue: https://jira.atlassian.com/browse/JRA-37524 feel free to watch As a workaround, the gadget can be removed from the System Dashboard Regards,Mauro CommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software Test if the domain name of proxy server can be detected on JIRA application server; for example wget https://support.atlassian.com:443/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:assigned-to-me-gadget/gadgets/assigned-to-me-gadget.xml If the proxy's domain can't be detected on JIRA application server, adjust Source See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright ©

Resolution Go to JIRA Administration > Add-ons > Manage Add-ons > Change search option to System > Search for Atlassian JIRA - Plugins - Gadgets Plugin Click on the plugin. If nothing above helps, Please make a backup of your database and then try the workaround from this bug : JSW-9991 - JIRA Agile hangs on installation Resolved Was this helpful? It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article?

Page Loading...

If the gadget relies on data from a plugin, make sure that the plugin is operating properly, is not removed, and is not out of date. Note it's different than JIRA Mobile Connect plugin (com.atlassian.jconnect.jconnect-plugin). For example the Atlassian JMX Monitoring Plugin has been known to cause issues. AttachmentsOptionsSort By NameSort By DateAscendingDescendingThumbnailsListAttachmentscannot_add_gadget_error.jpeg52 kB30/Apr/2014 10:18 AMIssue Links relates to CONF-28226 Confluence Page Gadget leads to an internal server error Open JRA-29795 Gadgets can't be added or saved in Confluence

Resolution Make sure you are using a real certified secure certificate, not a self-signed one Reimport the certificate using the following command. Yes No Thanks for your feedback! At least the error message and all seems very much the same. have a peek here How can I slove this problem?jira-cloudCommentCommentAdd your comment...1 answer10-1Michiel NieuwstratenAug 29, 2013Missing add-on: https://marketplace.atlassian.com/plugins/com.atlassian.jira.ext.calendarCommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software

It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? AttachmentsIssue Links is related to JRA-35317 EAP Feedback - JIRA 6.2 Open was cloned as JDEV-27075 Loading... Activity People Assignee: Unassigned Reporter: Matt Hass Participants: Matt Hass, Michael Andreacchio, Piotr Stefan Stefaniak [Atlassian] Votes: 0 Vote for this issue Watchers: 5 Start watching this issue Dates Created: 07/Jan/2014 Show 1 more links (1 mentioned in) Activity People Assignee: Oswaldo Hernandez [Atlassian] Reporter: John Chin Kim Loong Votes: 8 Vote for this issue Watchers: 13 Start watching this issue Dates

Why was this unhelpful? You have JIRA Mobile plugin (com.atlassian.mobile.jira-mobile) installed in JIRA. The following appears in the atlassian-confluence.logwhen trying to register individual external gadget (e.g. So it might be a bit more difficult to execute the same SQL there (again, assuming the problem have the same cause :))CommentAdd your comment...210Colin WhootenApr 28, 2014same here.

It could also be necessary to flush browser cache. I believe that if the Gadget with the error is removed from the Dashboard by Configuring the Default Dashboard or any other Dashboard that has the Gadget, then the error will HTTP error 404 What I will need do to resolve the problem?jirajira-cloudcloudCommentCommentAdd your comment...5 answers10-1Mauro Fernandez Badii [Atlassian]Apr 27, 2014Hi Alexey, I just created the bug https://jira.atlassian.com/browse/JRA-38051 The error is similar Page Loading...