Home > Unable To > Gadget Exception Unable To Retrieve Gadget Xml. Http Error 404

Gadget Exception Unable To Retrieve Gadget Xml. Http Error 404

Contents

This problem comes from a wrong parser. HTTP error 40410-1NWIMar 19, 2014I ordered JIRA Agile OnDemand. Hide Permalink Zhang, Zhen-Yu added a comment - 03/Nov/10 8:20 AM Can you tell the root cause of the issue? E.G: The plugin is working but when i add any of this components: Obviously changing the class for the components i use, the gadgets that previously worked fine, now have dissapeared http://blogeurope.net/unable-to/frontend-exception-error-1066-unable-to-open-iterator-for-alias.php

The problem is caused by running JIRA on a system that is not part of theSupported Platforms. Atlassian Documentation  Log in JIRA Knowledge Base Gadgets do not display when failing to access XML specification Symptom When integrating JIRA with a proxy server, the Dashboard Gadget can't be Report a bug Atlassian News Atlassian Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence The exception thrown in the console is: 2010-10-18 11:40:16,458 INFO [org.apache.shindig.gadgets.render.Renderer] (http-0.0.0.0-8380-8) Failed to render gadget http://:/rest-ecmdemo/jcr/repository/portal-system/production/app:gadgets/app:helloworld/app:data/app:resources/helloworld.xml: Unable to retrieve gadget xml.

Error Occurred While Retrieving Gadget Spec

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 JIRA Home directory should be different than the installation directory, or where the webapp is deployed. Resolution Shutdown JIRA Remove the content within the following directory: /caches/indexes/ /plugins/.bundled-plugins/ /plugins/.osgi-plugins/ /work/ Start JIRA again Re-index your JIRA instance Other Causes and Solutions An incompatible plugin in JIRA causes Resolution Make sure you are using a real certified secure certificate, not a self-signed one Reimport the certificate using the following command.

Do note that JIRA is required to perform a full re-index upon removing the indexes directory. 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 Why was this unhelpful? Jira Gadgets Make sure that your OS, database, Java version, web browser, and application server are supported.

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 504 at com.atlassian.gadgets.renderer.internal.GadgetSpecFactoryImpl.getGadgetSpec(GadgetSpecFactoryImpl.java:169) at com.atlassian.gadgets.renderer.internal.GadgetSpecFactoryImpl.getGadgetSpec(GadgetSpecFactoryImpl.java:86) at sun.reflect.GeneratedMethodAccessor326.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58) at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56) at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:39) at Cause 4 The problem is caused to outdated indexes/corrupted work directory. you can try this out People Assignee: Le Thanh Hai (Inactive) Reporter: Gary Hu Votes: 0 Vote for this issue Watchers: 0 Start watching this issue Dates Created: 27/Oct/10 2:49 PM Updated: 13/Apr/11 8:52 AM Resolved:

However, none of the gadget will show up in theMacro Browser. Was this helpful? HTTP error 50010-1AndrewAug 02, 2012 In My DashBoard´╝îit appear this notice: Error loading gadget from rest/gadgets/1.0/g/com.atlassian.jira.ext.calendar:issuescalendar-gadget/templates/plugins/jira/portlets/calendar/gadget/calendar-gadget.xml: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. https://marketplace.atlassian.com/plugins/jira-timesheet-plugin If yes, the plugin installed seems to be having difficulties to connect to external site to extract information, you could check out the documentation below to see if you encountered

Unable To Retrieve Gadget Xml. Http Error 500

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 It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? Error Occurred While Retrieving Gadget Spec Was this helpful? Jira This Gadget Cannot Be Displayed On Your Dashboard HTTP error 404What's wrong with it?

Report a bug Atlassian News Atlassian Atlassian Documentation  Log in Confluence Knowledge Base Unable to Register External Gadgets Due to Invalid gadget URL or 500 Error Response Symptoms When trying this content Hide Permalink Minh Dang (Inactive) added a comment - 10/Nov/10 5:32 AM We cannot reproduce this problem in current version of WCM. It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? Get the following error message: Finding: Tested in JIRA 6.2.4 Temporary Workaround: Please try the following steps and see you able to get any results: Go to JIRA instance serving gadget Jira Not All Gadgets Have Loaded

Skip to content Skip to breadcrumbs Skip to header menu Skip to action menu Skip to quick search Linked ApplicationsLoading… Quick Search Help About Confluence Log in Sign up QuestionsTopicsLeaderboardRewardsUnable Try JIRA - bug tracking software for your team. Page Loading... weblink Yes No Thanks for your feedback!

Thanks, Minh Hide Permalink Minh Dang (Inactive) added a comment - 12/Nov/10 9:16 AM - edited @Gary Hu: Please see my comment. HTTP error 504 when adding Confluence gadget to JIRA dashboardLog In ExportXMLWordPrintableDetails Type: Bug Status: Resolved (View Workflow) Priority: Low Resolution: Fixed Affects Version/s: 6.1, 6.1.5, 6.2.4 Fix Version/s: 6.2.5, 6.3-OD-5 See Gadgets do not display correctly after upgrade to JIRA 4.0 A firewall restriction for JIRA self-generated outgoing request A mismatched domain and port in JIRA self-generated outgoing request A mismatched

Local Gadget can be added, but after adding it to the dashboard it can NOT be displayed well.

The problem is caused by running out of memory.Increase your memory allocationto 768MB or higher. Resolution Shutdown JIRA Follow Setting your JIRA Home Directory to change the JIRA Home Directory. 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 © Because we now using WCM2.0.0-tp, and can not update it to WCM2.1.x for project reason for this moment.

Right after the first login the System Dashboard shows the following "Gadget Error":Error loading gadget from rest/gadgets/1.0/g/com.atlassian.studio.theme.jira:admin-gadget/com/atlassian/studio/jira/gadgets/admin-gadget.xml: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. Atlassian Cause JIRA Gadgets use the extensible REST Plugin Module framework, which provides access to resources via URI paths. http://blogeurope.net/unable-to/git-reset-error-unable-to-unlink-old.php Thank you very much.

Thanks, Minh Show Minh Dang (Inactive) added a comment - 10/Nov/10 5:32 AM We cannot reproduce this problem in current version of WCM. Show 1 more links (1 mentioned in) Activity People Assignee: Oswaldo Hernandez [Atlassian] Reporter: Chin Kim Loong Votes: 8 Vote for this issue Watchers: 13 Start watching this issue Dates Created: Note it's different than JIRA Mobile Connect plugin (com.atlassian.jconnect.jconnect-plugin). 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

Shutdown JIRA, remove the plugin from theinstalled-pluginsfolder, restart JIRA. HTTP error 500. Restart JIRA Cause 2 The problem is caused by SSL misconfiguration. I will mark this issue as resolved with resolution is cannot reproduce.

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 Page Loading... Show Zhang, Zhen-Yu added a comment - 03/Nov/10 8:20 AM Can you tell the root cause of the issue? 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

If updating some configuration could solve the problem, maybe we could fix the issue in our WCM2.0.0-tp version. I will mark this issue as resolved with resolution is cannot reproduce. It could also be necessary to flush browser cache. Show Minh Dang (Inactive) added a comment - 12/Nov/10 9:16 AM - edited @Gary Hu: Please see my comment.

Resolution Disable JIRA Mobileplugin in JIRA. You have JIRA Mobile plugin (com.atlassian.mobile.jira-mobile) installed in JIRA. Local Gadget can be added and displayed finely. 2.b) While visit the portal under "/ecmdemo/". Yes No Thanks for your feedback!

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 Error loading gadget from rest/gadgets/1.0/g/jira-timesheet-plugin:timesheet-gadget/gadget.xml: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. 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 HTTP error 404gadgetsCommentCommentAdd your comment...1 answer10-1Richie Gee [Atlassian]Mar 31, 2013Hi there, It appears to be pointing at the timesheet plugin that you have installed, can you verify whether you have the