-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] StacklessClosedChannelException on Blob Downloads in Windows Azure Functions on Version 12.25.4 #40106
Comments
Thank you for your feedback. Tagging and routing to the team member best able to assist. |
I just ran the function locally on my mac. I could not reproduce the error there. It has to do with the Windows Function environment in combination with the new library... |
Update: I noticed that the HTTP download of the blob simply does not progress. So the blob storage closes the TCP/HTTP connection after ~45s thus the exception. Please tell me if I can provide any useful information or tests. |
Is someone working on this? Azure Functions seem like a common use case for blob downloads. It would be bad if this issue persists in the newer versions. |
Hi @SoulKa |
Thank you for investigating this issue! I can provide further details where needed |
Hi @SoulKa Wanted to confirm, have you used either of these guides when trying to develop with Storage and Azure Functions? |
Hi @ibrahimrabab, I have not used these guides yet. Are they relevant when I do not have a netty dependency in my project? These are my dependencies: pom.xml <dependencies>
<dependency>
<groupId>com.microsoft.azure.functions</groupId>
<artifactId>azure-functions-java-library</artifactId>
<version>3.1.0</version>
</dependency>
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-storage-blob</artifactId>
</dependency>
<!-- Test -->
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter</artifactId>
<version>5.10.2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>5.11.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-junit-jupiter</artifactId>
<version>5.11.0</version>
<scope>test</scope>
</dependency>
<!-- Lombok as QoL Dependency -->
<dependency>
<artifactId>lombok</artifactId>
<groupId>org.projectlombok</groupId>
<scope>provided</scope>
<version>1.18.32</version>
</dependency>
<dependency>
<artifactId>jackson-databind</artifactId>
<groupId>com.fasterxml.jackson.core</groupId>
<version>2.17.1</version>
</dependency>
<dependency>
<artifactId>jackson-datatype-jsr310</artifactId>
<groupId>com.fasterxml.jackson.datatype</groupId>
<version>2.17.1</version>
</dependency>
<dependency>
<artifactId>annotations</artifactId>
<groupId>org.jetbrains</groupId>
<scope>provided</scope>
<version>24.1.0</version>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-sdk-bom</artifactId>
<version>1.2.22</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement> |
Describe the bug
I am getting
io.netty.channel.StacklessClosedChannelException
exceptions when downloading blobs usingdownloadToFile()
in version 12.25.4. The same code works using version 12.25.3. It is running in an Azure Function. The download link is valid and the blob storage is available. I can reproduce the error. Probably an issue due to the netty upgrade in version 12.25.4?Exception or Stack Trace
To Reproduce
Steps to reproduce the behavior:
new BlobClientBuilder().endpoint(blobSasUrl).buildClient()
and a valid download URL to a blob with a valid SAS URL. Version 12.25.4 of the storage library has to be used.client.downloadToFile(destinationPath, true)
StacklessClosedChannelException
Code Snippet
Expected behavior
The blob gets successfully downloaded as it was in version 12.25.3
Setup (please complete the following information):
4.33.1.22394
and App Service Plan EP2 and EP3, both getting the same issueInformation Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: