Home > Unable To > Error Occurred While Retrieving Gadget Spec

Error Occurred While Retrieving Gadget Spec


It works!CommentAdd 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. My AccountSearchMapsYouTubePlayGmailDriveCalendarGoogle+TranslatePhotosMoreShoppingDocsBooksBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages Linked ApplicationsLoading… DashboardsProjectsIssuesAgileCaptureGetting started Help Online Help JIRA Agile Help Keyboard Shortcuts About JIRA JIRA Credits Log In Export Tools 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. 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. Check This Out

The problem is caused by running out of memory.Increase your memory allocationto 768MB or higher. Restart JIRA Cause 2 The problem is caused by SSL misconfiguration. 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 HTTP error 404What's wrong with it?

Error Occurred While Retrieving Gadget Spec

As I tried to re-add it to the Dashboard, I could not find the gadget anymore. Make sure that your OS, database, Java version, web browser, and application server are supported. 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 500 What reason to lead to this problem?
  • HTTP error 404 Causes and Resolutions This issue could be caused by any number of reasons - please review each cause and solution in turn: Cause 1 The problem is caused
  • 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
  • The exception thrown in the console is: 2010-10-18 11:40:16,458 INFO [org.apache.shindig.gadgets.render.Renderer] (http- 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.
  • We hope atlassian team can resolve this issue a soon as possible )Ivar SønstabøApr 28, 2014Can this be linked to the same issue here: https://answers.atlassian.com/questions/287832/after-an-upgrade-to-jira-6-2-3-jira-agile-6-3-12-agile-gadgets-are-no-longer-available-on-the-dashboard.
  • The local gadget is created by Application Registry->Gadget->Create a new gadget.
  • The problem is caused by running JIRA on a system that is not part of theSupported Platforms.
  • 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

HTTP error 404 I guess some part of URL was hard coded. Cause JIRA Gadgets use the extensible REST Plugin Module framework, which provides access to resources via URI paths. 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 Jira Gadgets Cause 4 The problem is caused to outdated indexes/corrupted work directory.

Local Gadget can be added and displayed finely. 2.b) While visit the portal under "/ecmdemo/". Jira This Gadget Cannot Be Displayed On Your Dashboard Reproduce steps: 1) Deploy pure EPP 5.0.0 and visit the portal under "/portal/". 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). Can somebody please verify if this is the case ?

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 Hide Permalink Minh Dang (Inactive) added a comment - 10/Nov/10 5:32 AM We cannot reproduce this problem in current version of WCM. Atlassian HTTP error 40410-1NWIMar 19, 2014I ordered JIRA Agile OnDemand.

Jira This Gadget Cannot Be Displayed On Your Dashboard

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 get redirected here Gliffy Diagrams Sort Name Modify Date Ascending Descending Activity All Comments Work Log History Activity Transitions Summary Ascending order - Click to sort in descending order Hide Permalink Minh Dang (Inactive) Error Occurred While Retrieving Gadget Spec So, if you cannot upgrade to newer version of WCM then could you try to remove pull-parser-2.jar inside gatein-ecmdemo-extension-2.0.0-GA.ear\lib and try again? Jira Not All Gadgets Have Loaded If updating some configuration could solve the problem, maybe we could fix the issue in our WCM2.0.0-tp version.

HTTP error 404 Plus the Road Map gadget no longer appears as an option for adding to the dashboard. http://fullflash.net/unable-to/unable-to-display-document-error-retrieving-page-1-unspecified-error.html HTTP error 404" is received when access local gadget created from the Portlet UI in ecmdemoAgile Board ExportXMLWordPrintable Details Type: Bug Status: Closed (View Workflow) Priority: Minor Resolution: Cannot Reproduce Affects HTTP error 500. Resolution If the gadget relies on data from another system (E.G. Unable To Retrieve Gadget Xml. Http Error 500

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. https://jira.atlassian.com/browse/JRA-37524 Error loading gadget from rest/gadgets/1.0/g/com.atlassian.jira.gadgets:road-map-gadget/gadgets/roadmap-gadget.xml: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. Local Gadget can be added, but after adding it to the dashboard it can NOT be displayed well. http://fullflash.net/unable-to/unable-to-display-document-error-retrieving-page.html 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

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. 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 QuestionsTopicsLeaderboardRewardsorg.apache.shindig.gadgets.GadgetException: 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

It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article?

Local Gadget can be added and displayed finely. 2) Deploy exo-wcm-2.0.0-tech-preview-for-epp-5.0.0.GA.zip following the guide. 2.a) While visit the portal under "/porta/". Hide Permalink Zhang, Zhen-Yu added a comment - 03/Nov/10 8:20 AM Can you tell the root cause of the issue? 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 Edit /conf/server.xml (Standalone), or /conf/server.xml for Ear-War deployment.

This problem comes from a wrong parser. The JIRA self-generated outgoing URL fails to access the requested spec XML. Specify scheme/proxyName/proxyPort attributes in JIRA Connector, e.g. navigate here Report a bug Atlassian News Atlassian Linked ApplicationsLoading…DashboardsProjectsIssuesCaptureGetting Started Give feedback to Atlassian Help JIRA Core help Keyboard Shortcuts About JIRA JIRA Credits Log In JIRA (including JIRA Core)JRA-35223Get exception Unable

Therefore, we highly suggest to perform this suggestion during off office hours, as it needs a down time for JIRA to rebuild the indexes. Why was this unhelpful? Resolution Make sure you are using a real certified secure certificate, not a self-signed one Reimport the certificate using the following command. Resolution Shutdown JIRA Follow Setting your JIRA Home Directory to change the JIRA Home Directory.

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: For example the Atlassian JMX Monitoring Plugin has been known to cause issues.