Unable to deploy code - Metadata Container is not deleted

[Hagai Shatz]

On one of my dev orgs I am no longer able to deploy files on save - the deploy process starts and hangs for several minutes until I get an error message: 'Could not send Message.' When trying to deploy several files together, the process get stuck on: deleting Metadata Container.

Using: IntelliJ IDEA 2016.3.4, Build #IU-163.12024.16, built on January 31, 2017, JRE: 1.8.0_112-release-408-b6 x86_64, JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o

See attached IDE log.

[Scott Wells]

Hi, Hagai. It looks like the call to the Salesforce API ToolingApi.delete() timed out:

Caused by: java.net.SocketTimeoutException: SocketTimeoutException invoking https://sirenum-dev-hagai-dev-ed.my.salesforce.com/services/Soap/T/39.0/00D0Y000000rIBL: Read timed out

I've heard from serveral users that some pods are having VERY slow performance right now, though the one that comes up the most is NA35. Your org appears to be in EU11 and I'm not sure about its state. What happens if you try to make changes from Developer Console? Note that I'm not steering you to do that, but since that also uses the Tooling API, I'd like to verify whether this slow behavior is consistent across tools or not. If it's fast there, would you mind retrying from Illuminated Cloud to see if it was a short-lived/transient issue?

Please let me know your findings.

[Hagai Shatz]

Trying to edit and save code using the Developer Console result in similar hang on save. When I eventually closed the window I got the following message: Failed to create deployment: This container has a save in progress with deploymentId=1dr0Y000000WpmG. You may not enqueue a request until this completes.: Metadata Container ID

And here is the deployment log:

Notice that another org on the same pod eu11, works just fine.

[Scott Wells]

Hagai, what happens if in Developer Console under the Progress tab you click Cancel All Deployments? Does that get the org back into a good state?

[Hagai Shatz]

It found and cancelled one item: Cancelling deployment 1dr0Y000000WpmGQAS. But still hang when I save the Apex class in Developer Console.

[Scott Wells]

That hang is almost certainly the same hang that you were seeing from Illuminated Cloud. I'm not sure if there's something wrong in that particular org, especially since you said you have another org in the same pod that's just fine. But if the Developer Console is also hanging, that's a pretty clear sign that something is wrong there. I can think of two options: 1) open a support case with Salesforce since the issue is reproducible in Developer Console; 2) I can provide some guidance on how to try to clean out the Tooling API objects that are created by Illuminated Cloud when deploying, but my guess is that the Cancel All Deployments button has probably already purged the ones that would come into play here. I think option 1 probably makes the most sense.

[Hagai Shatz]

Thanks, will contact SF support.

Don't know if this is related to upgrading to version 1.7.8.3, but this started minutes after upgrading this morning. Even thought I have no issues working with other orgs.

[Scott Wells]

It's always possible but my guess is that it's not related. The only change in 1.7.8.3 was an update to the WSDL-generated SOAP API clients for Spring '17 based on WSDLs I got directly from Salesforce. As I think I mentioned, I've heard about some issues with tooling API deployment from other users over the last day or so that Salesforce is looking into.

Having said that, if after you speak with Salesforce they think this is something IC did to the org, just let me know or have them contact me and I'll take whatever that is into account.

Let me know what you hear if you don't mind.

[Hagai Shatz]

Still have no clue on what create the problem to begin with. However, the problem disappeared after a few hours.

[Scott Wells]

Okay, I'll resolve this for now but feel free to reopen with details if you see it happen again.