CODEWITHSUNDEEP
eclipsedeploymentazure
user1687210
user1687210

Reputation: 41

Microsoft azure deploy error 40 %

I´m deploying a simple application in the cloud. I'm using Eclipse for this, but the deploy fail.

In the console the error is:

09/16/2012 09:40:46 - Configuring Remote Desktop
09/16/2012 09:40:50 - Uploading Deployment Package
09/16/2012 09:44:58 - Failed uploading deployment package (.cspkg).

The deploy is only completed until 40%.

In the log of Eclipse says:

!ENTRY WAEclipsePlugin 4 0 2012-09-16 09:42:57.026 !MESSAGE Error !STACK 0 com.gigaspaces.azure.util.CommandLineException: Timeout at com.gigaspaces.azure.rest.WindowsAzureRestUtils.execute(WindowsAzureRestUtils.java:301) at com.gigaspaces.azure.rest.WindowsAzureRestUtils.execute(WindowsAzureRestUtils.java:338) at com.gigaspaces.azure.rest.WindowsAzureRestUtils.runStorage(WindowsAzureRestUtils.java:393) at com.gigaspaces.azure.rest.WindowsAzureStorageServices.putBlock(WindowsAzureStorageServices.java:358) at com.gigaspaces.azure.rest.WindowsAzureStorageServices.access$0(WindowsAzureStorageServices.java:348) at com.gigaspaces.azure.rest.WindowsAzureStorageServices$UploadingTask.call(WindowsAzureStorageServices.java:79) at com.gigaspaces.azure.rest.WindowsAzureStorageServices$UploadingTask.call(WindowsAzureStorageServices.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

Could you help me please?

Upvotes: 4

Views: 371

Answers (2)

Eli Polonsky
Eli Polonsky

Reputation: 601

the error seems to indicate a problem with your connection (Timeout)

is this consistent? may i ask what version are you using of the eclipse plugin?

Upvotes: 0

AvkashChauhan
AvkashChauhan

Reputation: 20576

I am sure the size if the main issue here because I have seen such issue. To ensure it just try deploying the small less functional version of same app under 30 MB and see if that has any issue. Also even when your package size is still under the limit however 130MB package size is not practical and requires application architecture changes.

You can try keeping the over all size smaller by using:

  1. Startup Task to automate the runtime download/install
  2. Use other Java Management api to download the application and other component in later phase

Upvotes: 1

Related Questions