Issue with deployment (Clojure/Java)

i like this post (click again to cancel)
0
i dont like this post (click again to cancel)

For the past few days I have been getting the following error from dotcloud push when attempting to push my Clojure app to the dotCloud Java service:

sent 156 bytes  received 20 bytes  50.29 bytes/sec
total size is 5.33M  speedup is 30272.57
13:44:33 ---> Deploy of "xxx" scheduled for revision rsync-1328622272610 at 2012-02-07 13:44:33
13:44:33 ---> Building the application...
13:44:33 [www] Build started for revision rsync-1328622272610 (clean build)
13:44:41 [www] Build completed successfully. Compiled image size is 5MB
13:44:41 ---> Initializing new services... (This may take a few minutes)
13:44:41 ---> No new services found
13:44:41 ---> All services have been initialized. Deploying code...
13:44:41 [www.0] Deploying build revision rsync-1328622272610...
13:44:46 [www.0] Running postinstall script...
13:44:48 [www.0] Launching...
13:45:02 [www.0] Waiting for the service to become responsive...
13:45:32 [www.0] -- Failed to deploy: Service "http" (port: 8080) failed to respond within 30 seconds
13:45:32 ---> Deploy finished

In other words, everything goes fine until we hit "Failed to deploy".

The only change made to the application code was a modified text string in a template so I'm pretty confident that I haven't broken anything, also the app works perfectly in a local jetty container.

I have tried restarting my app's www service and also destroying and pushing the app again. To no avail.

Have there been any changes to the Java service recently? Has anyone else experienced a similar deploy failure or can anyone throw any light on this?

Much appreciated.

asked Feb 07 '12

peeb gravatar image peeb
1 1 1
i like this answer (click again to cancel)
0
i dont like this answer (click again to cancel)

We changed the way we build applications and we now check if the build is successful, by trying to connect to the application. If we can't connect to the application the deploy fails.

In the case of the Java service, Jetty can be very slow to start which can illegitimately cause the build to fail. We are going to make that timeout configurable and maybe higher by default for the Java service.

In the meantime, please contact us at support@dotcloud.com with the name of the affected application and we will revert it to the old build method.

link

answered Feb 07 '12

lopter gravatar image lopter
962 2 5

Your answer

Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
[hide preview]

Question tools

Tags:

Stats:

Asked: Feb 07 '12

Seen: 86 times

Last updated: Feb 07 '12

Powered by Askbot version 0.7.23

Copyright DotCloud, 2011. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.