409 Conflict, when deploying in Azure about windowsazuretoolkitforeclipsewithjava HOT 5 CLOSED

I tried deploying to staging slot when there is existing deployment in production slot.
It worked for me without any issues.

I need more details from you to understand the issue you are facing.
If you are deploying to a slot (production or staging) and if that slot has existing deployment then 409 error is expected.
(We are planning new features which handles 409 conflicts errors in a better way - more details on this will be available publicly soon).

Can you please give me your exact repo steps? What is the service name and target environment you are selecting in eclipse publish wizard in both the cases?

from windowsazuretoolkitforeclipsewithjava.

Hi,

the exact steps I did was:

1. create an application in eclipse with a windows azure deployment project.
2. deploy this to a new cloud service (with new storage) - in staging environment
3. in the cloud service, swap the deployed from staging to production
4. deploy again to the same cloud service - to the staging environment (there aren't any instances now in the staging environment, because I swapped it to production) --> here I got the 409 conflict

is this the expected behavior?
if it is not the expected behavior, please tell me and I will provide information about the used cloud services.

from windowsazuretoolkitforeclipsewithjava.

I got the 409 conflict too.

from windowsazuretoolkitforeclipsewithjava.

@Hannu-Daniel , Thanks for reporting with exact repo steps. We are now tracking the issue and will update the status of issue#3 once the fix is available for public.

from windowsazuretoolkitforeclipsewithjava.

Try with the latest Eclipse plugin update (October release - v2.2.0) - there is now a checkbox in the publish wizard letting you override the existing deployment.

from windowsazuretoolkitforeclipsewithjava.