Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample link returns "Application Error" #11

Open
MemberSense opened this issue Dec 27, 2013 · 3 comments
Open

Sample link returns "Application Error" #11

MemberSense opened this issue Dec 27, 2013 · 3 comments

Comments

@MemberSense
Copy link

http://docpad-syte.herokuapp.com/

Worked briefly yesterday. Gave up meat, milk and eggs.

@balupton
Copy link
Member

balupton commented Jan 8, 2014

I rebooted the website with the latest deps and that seem to have solved the problem.

However, it seems that generations keep taking longer and longer until heroku crashes it.

downtime

There are two problems here:

  1. Generations shouldn't take longer and longer
  2. Generations shouldn't keep responsiveness, requests should still go through to the old cached file from the last generation, rather than halting

Will look into them now.

Gave up meat, milk and eggs.

That's awesome to hear. Happy to have a more personal discussion about this if you'd like :) (skype username balupton)

@RobLoach
Copy link

RobLoach commented Jan 8, 2014

I could be very wrong here, but I believe Heroku will close an application if it's not used/pinged after 30 minutes or so. Don't take my word for it, though. I've run into something similar.

@balupton
Copy link
Member

balupton commented Jan 9, 2014

This is very true... I'll check the logs to check if that is the cause. However, wouldn't port monitor's checks every minute prevent that from kicking in? Will check either-way, thanks for the heads up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants