Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] Integrations with Azure Blob Storagemajorrandom2021-08-30 11:312021-09-15 14:40
Reportersebastien_lironView Statuspublic 
Assigned Tojarmendariz 
PriorityurgentResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.50
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Regression introduced in release

0047606: Missing timeout on Azure Blob Storage operations

DescriptionIn our use of the Azure JDK we are not defining timeouts on any of the upload/download/delete file operations.

If there is any problem when working with that API and the server does not respond, the thread executing that code will get stack, and its database transaction will remain open.

an import entry was blocked by this request for at least 4 hours :

Relevant stack trace:

Import Entry - 5" 0000884 daemon prio=5 os_prio=0 cpu=1105246.52ms elapsed=810940.05s tid=0x00007f27d404b000 nid=0x3720 waiting on condition [0x00007f271498b000]
java.lang.Thread.State: WAITING (parking)

at jdk.internal.misc.Unsafe.park(java.base@11.0.11/Native Method)

parking to wait for <0x000000009a1fab18> (a java.util.concurrent.CountDownLatch$Sync)
        at java.util.concurrent.locks.locksupport.park(java.base@11.0.11/
        at java.util.concurrent.locks.abstractqueuedsynchronizer.parkandcheckinterrupt(java.base@11.0.11/
        at java.util.concurrent.locks.abstractqueuedsynchronizer.doacquiresharedinterruptibly(java.base@11.0.11/
        at java.util.concurrent.locks.abstractqueuedsynchronizer.acquiresharedinterruptibly(java.base@11.0.11/
        at java.util.concurrent.countdownlatch.await(java.base@11.0.11/
        at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(
        at reactor.core.publisher.Mono.block(
        at$Proxy$_$$_WeldClientProxy.uploadFile(Unknown Source)
        at org.openbravo.client.application.attachment.AttachImplementationManager.upload(
        at com.openbravo.norauto.order.integration.processes.ProcessPendingItem.attachFileToOrder(
        at com.openbravo.norauto.order.integration.processes.ProcessPendingItem.processPendingItem(
        at com.openbravo.norauto.order.integration.integration.NOROrdSynchronization.saveRecord(
        at org.openbravo.service.importprocess.ImportEntryProcessor$ImportEntryProcessRunnable.doRunCycle(
        at org.openbravo.service.importprocess.ImportEntryProcessor$
        at java.util.concurrent.executors$
        at java.util.concurrent.threadpoolexecutor.runworker(java.base@11.0.11/
        at java.util.concurrent.threadpoolexecutor$
Steps To ReproduceThere are still no steps to reproduce, the problem with the Azure server seems to be random so far.

But looking at the APIs that are being used on the AzureStorageClient class, it is clear that no timeouts are being defined.
Proposed Solutionthere are 2 options to check:
- Close the connection before start the upload
- Add a timeout so if the upload takes long (5 hours is a lot) interrupt the process
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0047649 closedjarmendariz cannot overwrite attachemnt in Azure 
related to defect 0047650 closedjarmendariz missing timeout for Amazon S3 upload 

-  Notes
hgbot (developer)
2021-09-06 12:18

Merge Request created: [^]
hgbot (developer)
2021-09-08 09:17

Directly closing issue as related merge request is already approved.

Repository: [^]
Changeset: 3b48046e6f792366bc082d19cfa905139539a690
Author: Javier Armendáriz <>
Date: 2021-09-08T09:13:32+02:00
URL: [^]

Fixed ISSUE-47606: Setting a timeout value for all azure operations

Adding a timeout field to azure configuration tab with a default value of 60 seconds. This timeout will
be used by all azure operations. This also adds a timeout exception used to display a descriptive message
to the user when the operation times out.

A src/org/openbravo/service/integration/azure/storage/exception/
M src-db/database/model/tables/OBAZS_CONFIGURATION.xml
M src-db/database/sourcedata/AD_COLUMN.xml
M src-db/database/sourcedata/AD_ELEMENT.xml
M src-db/database/sourcedata/AD_FIELD.xml
M src-db/database/sourcedata/AD_MESSAGE.xml
M src/org/openbravo/service/integration/azure/storage/
M src/org/openbravo/service/integration/azure/storage/attachments/
M src/org/openbravo/service/integration/azure/storage/process/
hgbot (developer)
2021-09-08 09:17

Merge request merged: [^]

- Issue History
Date Modified Username Field Change
2021-08-30 11:31 sebastien_liron New Issue
2021-08-30 11:31 sebastien_liron Assigned To => AugustoMauch
2021-09-01 16:15 AugustoMauch version 2.50 =>
2021-09-01 16:15 AugustoMauch Summary lock on import entry using azure attachments => Missing timeout on Azule Blob Storage operations
2021-09-01 16:15 AugustoMauch Description Updated View Revisions
2021-09-01 16:15 AugustoMauch Steps to Reproduce Updated View Revisions
2021-09-06 09:17 AugustoMauch Assigned To AugustoMauch => jarmendariz
2021-09-06 09:18 AugustoMauch Status new => scheduled
2021-09-06 12:18 hgbot Note Added: 0131574
2021-09-08 08:35 alostale Summary Missing timeout on Azule Blob Storage operations => Missing timeout on Azure Blob Storage operations
2021-09-08 08:59 alostale Relationship added related to 0047649
2021-09-08 09:01 alostale Relationship added related to 0047650
2021-09-08 09:17 hgbot Resolution open => fixed
2021-09-08 09:17 hgbot Status scheduled => closed
2021-09-08 09:17 hgbot Note Added: 0131641
2021-09-08 09:17 hgbot Note Added: 0131642
2021-09-15 14:40 rafaroda Tag Attached: NOR

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker