issue with fetching js

  • Problem
  • Updated 5 years ago
Fetching of the js seems frequently a bit slow and right now really slow. Is there a know issue or outage ?
Photo of Robert Williams

Robert Williams

  • 4 Posts
  • 0 Likes

Posted 5 years ago

  • 6
Photo of gpmelendezG

gpmelendez

  • 3 Posts
  • 0 Likes
The solution I found is to set timeouts to http replies.
Photo of cgbystrom

cgbystrom, Product Manager

  • 331 Posts
  • 17 Likes
Could you please elaborate on your problem?
I'm not sure what you mean with "fetching of the js".

Is it serving of the client.js file or the REST API calls that are causing your slow downs?
Photo of Dominik Rask

Dominik Rask

  • 2 Posts
  • 0 Likes
It seems like it's the REST API that doesn't work, examples on http://www.beaconpush.com/account/tes... gives "504 Gateway Time-out".
Photo of cgbystrom

cgbystrom, Product Manager

  • 331 Posts
  • 17 Likes
Dominik, yes, you're absolutely right. Overlooked that. Working on a fix right now.
Photo of jim jonesJJ

jim jones

  • 17 Posts
  • 0 Likes
I'm getting the same issue. Gateway timeout issues from the REST API
Photo of cgbystrom

cgbystrom, Product Manager

  • 331 Posts
  • 17 Likes
Problem solved. Sorry about this "hiccup". There were some problems with our REST API server.

As you all know, we are still in beta and some stability issues like this arise from time to time but we will try to fix them as soon as possible.
Measurements have also been taken to alert us even quicker when things like this happen.

Thanks for reporting all, keep it coming. We love feedback! :)
Photo of jim jonesJJ

jim jones

  • 17 Posts
  • 0 Likes
Thanks Carl. What the best method to contact you guys when there is an issue like this? Also, can we sign up for paid accounts while you are in beta? I just want to ensure that if I sign up for a paid account, that any issues like this can be addressed in a reasonable time frame and that I have some way to get in touch. Great job, keep it up. Thanks.

Jim
Photo of cgbystrom

cgbystrom, Product Manager

  • 331 Posts
  • 17 Likes
In this beta period we offer only free accounts.
With free accounts, we've chosen to handle our support requests through Get Satisfaction. Probably not our final and only choice, mind you, but it's quite easy to use for everyone involved.

Regarding paid accounts, we haven't yet decided what difference in level of support there will be between paid and free.

Do you have any specific ideas in mind for communication? Except for this Get Satisfaction forum.
Photo of jim jonesJJ

jim jones

  • 17 Posts
  • 0 Likes
Thanks Carl. This forum will work. I guess I was thinking something more on the lines of a ticket tracking system with a support @ email address for submitting issues.

Just a few more questions if you don't mind:
1) Do you have any info on your hosting infrastructure (ie. data center locations, or anything else you could share)? Is the system EC2 hosted?
2) Do you recommend using your service for a production app today? Or would you advise we wait.

I really like the service and am just trying to weigh the risks of integrating it into my app. Thanks.
Photo of cgbystrom

cgbystrom, Product Manager

  • 331 Posts
  • 17 Likes
Glad you like it!

Sure, that'd be possible for paid accounts. At ESN (the company behind Beacon), we use Zendesk for another product, providing support for paying customers. Works quite well.

Since our focus has been on bringing stability and compatibility during this phase, details regarding SLAs and ways of handling premium support has not been worked out yet.
While waiting for issues like this to be settled internally, we try to be as transparent as possible.

Now to your questions,
1) Yes, we're hosted on Amazon EC2 in their east coast data center. As you might know, they're a respected cloud-hosting provider and we're currently very pleased with them.

2) It depends. Will sending messages be a core part of your app? Put in other words, if Beacon for some reason would be unavailable during beta, would the user experience of your app come crashing down? As an example, some of our customers rely only on Beacon to provide additional real-time capabilities on top of what they already have. This inherently makes those sites/apps immune to worst case scenarios.

Otherwise, we're planning to get out of beta in early September.

I'm interested in hearing more of what you are building. If you don't mind, drop me a mail at
carl(at)esn.me and we could discuss things further.
Photo of Robert Williams

Robert Williams

  • 4 Posts
  • 0 Likes
Sorry for the delayed update. For the last couple of weeks Beacon has been very reliable. Moving the script load above some other large script loads that we were doing also helped improve things.
Photo of cgbystrom

cgbystrom, Product Manager

  • 331 Posts
  • 17 Likes
Glad to hear that!
Photo of service.g2100S

service.g2100

  • 2 Posts
  • 0 Likes
I got Networking error with "504 Gateway Time-out" by firefox 3.6.9.
Ok in IE8.
Photo of cgbystrom

cgbystrom, Product Manager

  • 331 Posts
  • 17 Likes
You may see such timeouts if you have a long idle connection or a proxy between you and Beacon.

The client should reconnect and resume where it left off.