Cloud Debugger API will be shutdown May 31, 2023

[timcobra]

Hi,

I noticed that Cloud Debugger API will be shutdown May 31, 2023, so I went to the console and disabled the API for my Google Appengine. No surprise, but I now get an error in my logs. I don't use the Cloud debugger (that I'm aware of), so what is causing the error:

java.io.IOException: Server returned HTTP response code: 403 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1924)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1520)
	at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:250)
	at com.google.devtools.cdbg.debuglets.java.GcpHubClient.registerDebuggee(Unknown Source)

None of my Java 11 code or POM, Appengine-web.xml or web.xml reference the API, so not sure what is calling the API. Hope you can help.

Thanks
Tim

[Marramirez]

Hi @timcobra,

Welcome to the Google Cloud Community!

You can try the following troubleshooting options:

• Look for any reference that uses the Cloud Debugger API in your Java code.
• If you are using a library or framework that uses the Cloud Debugger API, you can update that library or update its version so that it is not depending on Cloud Debugger API.

There may be a bug in the application that causes it to call the Cloud Debugger API. You can also get in touch with Google Cloud Support for assistance.

Let me know if it helped, thanks!

[timcobra]

Thanks Marramirez.

From looking deeper into the logs and also here: console.cloud.google.com/debug?project=XXX It looks like Bitbucket is making the API request. My gmail account is the same for bitbucket and GCP, and somehow they are linked. Any idea how to disconnect them?

[timcobra]

Hi,

I think the Atlassian/BitBucket isn't the problem. I have removed all references to .git etc. in the .war file and even set the source code in my appengine project to be local files - So I don't think it is this. 

However, I did notice that I only get the problem/error in my Appengine projects that I have recently migrated to Java 11. For Java 8, I don't get the issue, I even switched one of my projects back to java 8 and no problem when the Cloud Debugger API is turned off.

When migrating to Java 11, I am still using the "Legacy bundled services", so I still have my appengine-web.xml  and have to add: <app-engine-apis> true </app-engine-apis>. So why does adding this kick off the clouddebugger.googleapis.com errors every few seconds.

For now I have turned the Cloud Debugger API back on, even though it says it has been deprecated - is this a bug on my side or one Google has missed. Any more help would really be appreciated, as I am now going to pause the rest of my Java 8 to 11 migrations 😞

Thanks!

[timcobra · Accepted solution]

It appears to be fixed. I'm guess that Google has done something on their side to stop these error. The API was due to be Deprecated on May 31st, and yesterday I noticed that it has finally been marked as such in the API list. So now when I disable it from my list of APIs in Google Cloud Console GUI, I no longer get the error mentioned above. Strange, but I'm happy as I can now continue to migrate my projects to Java 11.