cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4103
Views
0
Helpful
0
Comments
cdnadmin
Level 11
Level 11
This document was generated from CDN thread

Created by: Daniel Schimmer on 07-02-2012 10:18:09 AM
Hi There,

I have a web server that hosts several gadgets.  Sometimes when I update that server, and log into finesse I receive the following error:

There were issues rendering this gadget.
Unable to retrieve spec for http://xxx.xxx.xxx.xxx:xxxx/gadget/tasks. HTTP error 504
 
The finesse web server seems to be stuck in this state for sometime (10-20 minutes at times), on occasion when it does recover I can no longer set the ready state of my phone, nor log out of finesse.
 
Has anybody else encountered this? when checking the urls on my server during the time finesse has this error, everything seems to respond properly.
 
Thanks,
 
Daniel

Subject: RE: HTTP 504 Error
Replied by: Arul Selvan on 21-03-2013 04:44:20 AM
Hi.
i am also facing simillar issue anybody help for this its happening randomly for few minutes after some referesh automatically resolved.
i am using Agent team based Gadget
 
Error Details:
There were issues rendering this gadget.
Unable to retrieve spec for http://172.16.12.119/FGadget/portalGadget.xml. HTTP error 504
http://172.16.12.119/FGadget/portalGadget.xml

Note:while showing error xml file is accessable from my browser

Subject: RE: HTTP 504 Error
Replied by: Kevin Pickard on 21-03-2013 02:57:38 PM
We have been seeing this issue for quite a while on and off. We noticed that it seems to have gotten worse (ie. more frequent) with Finesse 9.1. It seems to be related to the response time of the web server hosting the gadget although we don't know that for sure yet (and the response times are very fast). When we use a fast web server with SSDs the problem does not seem to appear (but we have only tried that with Finesse 9.0). I think there might be a timing issue in the Finesse server (just a guess).

Subject: RE: HTTP 504 Error
Replied by: Kevin Pickard on 27-03-2013 12:56:13 PM
Is anyone from the Cisco Finesse team going to comment on this?
We have now switched our Finesse 9.1 system to point to our gadgets on the faster IIS Server (with SSDs) and so far things look better with fewer 504s. Can someone from the Finesse team let us know what the timing requirements Finesse has with regards to gadget retrieval? As I said before this got worse with 9.1. Were any of the changes made from 9.0 to 9.1 related to timing with regards to retireval? I believe these are retrieved via MakeRequest right?

Subject: RE: HTTP 504 Error
Replied by: Chuck Smith on 27-03-2013 01:01:35 PM
In Finesse 9.1.1 you can host the gadget on the Finesse server itself and point all your gadgets URLs to localhost. Have you given that a try?

Subject: RE: HTTP 504 Error
Replied by: Gary Olmsted on 27-03-2013 09:23:36 PM
Hello all...

This is in response to the question about timing requirements.  Shindig (the part of Finesse Server responsible for handling MakeRequest and rendering Gadgets) has a requirement that the request made from it to the external webserver must respond within 5 seconds.  This goes for any general REST requests as well.  If you are getting a HTTP 504, it means that the request to render the gadget from your webserver is not responding in that 5 seconds.  Are you certain the connectivity between the Finesse Server and your external Web Server is solid?
 
For 9.1.1 we added the ability to host the gadgets in the Finesse Server itself.  Have you tried this instead?  Is there definitely a requirement that they are hosted on your external webserver?

Subject: RE: HTTP 504 Error
Replied by: Arul Selvan on 28-03-2013 06:49:02 AM
Normal
  0
 
 
 
 
  false
  false
  false
 
  EN-IN
  X-NONE
  X-NONE
 
  
  
  
  
  
  
  
  
  
 
 
  
  
  
  
  
  
  
  
  
  
  
 


 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 



/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-fareast-language:EN-US;}


 Hi Gary,
 I understand, this problem is entirely due to slow IP communication. even it’s happening some time while I am sending request to my external webpage using  gadgets.io.makeRequest method.
 Is it any option is there avoid this problem, like increase my waiting time before give the request for external webpage and settings for render my gadget.

Subject: RE: HTTP 504 Error
Replied by: Arul Selvan on 28-03-2013 06:51:03 AM
 Hello Gary,
 I understand, this problem is entirely due to slow IP communication. even it’s happening some time while I am sending request to my external webpage using  gadgets.io.makeRequest method.  
Is it any option is there avoid this problem, like increase my waiting time before give the request for external webpage and settings for render my gadget.

Subject: RE: HTTP 504 Error
Replied by: Arul Selvan on 28-03-2013 07:03:34 AM
 Hi Gary,
 
 I understand, this problem is entirely due to slow IP communication. even it’s happening some time while I am sending request to my external webpage using  gadgets.io.makeRequest method. 
 
 Is it any option is there avoid this problem, like increase my waiting time before give the request for external webpage and settings for render my gadget.

Subject: RE: HTTP 504 Error
Replied by: Kevin Pickard on 28-03-2013 07:36:52 AM
Well I think there might be something wrong with the 5 second timing as our webserver is responding in less than 1 or 2 seconds. Putting the gadgets on the Finesse server itself will be an issue that would take some work as they use .Net code.

Subject: RE: HTTP 504 Error
Replied by: Kevin Pickard on 28-03-2013 07:51:38 AM
As a further follow-up on this. Perhaps the time is .5 seconds? (an incorrect decimal place). And I believe this timing would be per request (ie. per gadget) or is it 5 seconds to fetch *all* gadgets and render them?

Subject: RE: HTTP 504 Error
Replied by: Gary Olmsted on 28-03-2013 08:57:36 AM
Nope.  Shindig has a 5 (FIVE) second timeout per request.   Looks sorta like this:

Browser -> Finesse (Shindig) -> External Web Server

If the External Web Server does not start responding within 5 seconds then Shindig will respond with a 504.  You mention that the webserver is responding within 1 to 2 seconds.  The quesion I have is whether that is where you tested that?  Is the webserver responding 1 to 2 seconds to the Finesse Server?  Are you certain there are no network hinderences between Finesse (Shindig) -> External Web Server??
 

Subject: RE: HTTP 504 Error
Replied by: Kevin Pickard on 28-03-2013 10:04:29 AM
The Finesse server and the web server are both located on the same network (subnet) and both are connected to the same physical switch. We have measured the response times from the web server when it is actually accessed from a completely different subnet through multiple switches (which would slow things down) and the response times are still sub 1 or 2 seconds.
An additional question I have is that since it is 5 seconds per request then the initial XML (in our case) for the gadget would be one request. Then any additional components loaded by that would again be individual requests. In our case the total rendering (involving multiple requests) of each of the individual gadgets is still well under the 5 second timeout. But given that all this timing is happening at the browser end (in Shindig) and it is trying to load multiple gadgets on multiple tabs, could it be timing out simply because the browser itself is very busy? Although that would not explain why changing to a web server with SSDs would improve things.

Subject: RE: HTTP 504 Error
Replied by: Christopher Vadnais on 28-03-2013 03:11:54 PM
Shindig also has to proxy included javascript within this time that Gary mentioned so it can build the iframe for the rendered gadget.  If you are including files that are not hosted by your webserver, make sure finesse can resolve those hosts (when not using an ip address) or host them on your own web server in addition to the gadget xml. 

Subject: RE: HTTP 504 Error
Replied by: Kevin Pickard on 28-03-2013 03:42:49 PM
All the included files are hosted on our web server and all that works fine. Most of the time everything loads up fine and our gadgets function properly. And as I said earlier, the complete gadget renders (so all included javascript is pulled as well) in under 1-2 seconds.
The 504 only happens *sometimes* although with Finesse 9.1 it happens much more frequently than it did with Finesse 9.0.
It seems that every once in a while Finesse gets into a funny state were we are getting 504 on all our gadgets despite our webserver serving them in under 5 seconds. If we log out and wait for 10-15 minutes and try logging in again things sometimes sort themselves out and everything works again.

Subject: RE: HTTP 504 Error
Replied by: Christopher Vadnais on 28-03-2013 03:53:04 PM
Are you using ip or hostname for your gadget urls?  It would be good to rule out DNS lookups taking a long time.
Also, have you disabled LRO on your ESXi host? 
See:http://docwiki.cisco.com/wiki/Disable_LRO
The LRO settings if wrong can cause Finesse to occasionally have terrible network performance, which sounds like what you may be experiencing.  How may agents are typically logged into your system.  The LRO problems often happen more often when the traffic is lower or sporadic.
It is important to make sure the host is rebooted after making these changes.

Subject: RE: HTTP 504 Error
Replied by: Arul Selvan on 08-04-2013 01:16:48 AM
Gary Olmsted:
Hello all...

This is in response to the question about timing requirements.  Shindig (the part of Finesse Server responsible for handling MakeRequest and rendering Gadgets) has a requirement that the request made from it to the external webserver must respond within 5 seconds.  This goes for any general REST requests as well.  If you are getting a HTTP 504, it means that the request to render the gadget from your webserver is not responding in that 5 seconds.  Are you certain the connectivity between the Finesse Server and your external Web Server is solid?
 
For 9.1.1 we added the ability to host the gadgets in the Finesse Server itself.  Have you tried this instead?  Is there definitely a requirement that they are hosted on your external webserver?
 
 
 can you share the doument link for host gadget in the finesse server itself?
 
 
 

Subject: RE: HTTP 504 Error
Replied by: Arul Selvan on 08-04-2013 01:42:58 AM
Gary Olmsted:
Hello all...

This is in response to the question about timing requirements.  Shindig (the part of Finesse Server responsible for handling MakeRequest and rendering Gadgets) has a requirement that the request made from it to the external webserver must respond within 5 seconds.  This goes for any general REST requests as well.  If you are getting a HTTP 504, it means that the request to render the gadget from your webserver is not responding in that 5 seconds.  Are you certain the connectivity between the Finesse Server and your external Web Server is solid?
 
For 9.1.1 we added the ability to host the gadgets in the Finesse Server itself.  Have you tried this instead?  Is there definitely a requirement that they are hosted on your external webserver?
 
 
 can you share the document link or procedure to host the gadget inside finesse server itself?
 


 


 
 
 

Subject: RE: HTTP 504 Error
Replied by: Theodore Phipps on 08-04-2013 09:18:32 AM
Instructions should be in the Finesse Admin Guide and Developer Guide.
 
Instructions to manage 3rd party gadget account to get access to upload gadgets:
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_911/user/guide/CFIN_BK_F271B138_00_finesse-admin-and-serviceability-911.pdf
 
instructions to upload gadgets are in the developer guide in Chapter 10:
http://developer.cisco.com/documents/2382082/2401619/Cisco+Finesse+Web+Services+Guide+for+Release+9.1%281%29/688f8efa-b86e-48e7-bfce-3aeff5a34745
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links