Unexpected CPU Spike After April 23 and “Invalid URI hostname could not be parsed” Error in Azure Container App(Function)(java)

Since April 23, our CPU usage suddenly increased by dozens of times. The average CPU went from around 0.05% to roughly 1%, and total CPU usage jumped from about 60% to 600%, where it has remained consistently high. Our application is written in Java 17 and deployed on Azure Container Apps (using the Azure Functions runtime / Java worker). No code changes or configuration modifications were made during this period.

On May 29, after investigation, we discovered that the AzureWebJobsStorage setting was configured to use local storage (e.g., UseDevelopmentStorage=true). This caused the background process to continuously poll the remote storage endpoint, leading to the CPU spike. After correcting AzureWebJobsStorage to point to a valid storage account, CPU usage dropped significantly but is still sitting at about twice the level it was before April 23.

Additionally, we are now encountering the same issue described here: Azure Container Apps - Invalid URI: hostname could not be parsed.

Could you please confirm whether there was a platform upgrade around April 23 that might have caused this behavior? Why did the AzureWebJobsStorage setting suddenly affect CPU usage. Also, when can we expect a fix for the “Invalid URI hostname could not be parsed” error, or what steps can we take to mitigate it in the meantime?