You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling azure-storage-datalake:cameltesting?operation=listFileSystem causes the following flood of requests:
2021-03-02 14:04:55,301 INFO [com.azu.sto.blo.imp.Ser.listBlobContainersSegment] (parallel-3) --> GET https://cqaccpeterpalagap1.blob.core.windows.net?comp=REDACTED(empty body)--> END GET
2021-03-02 14:04:55,363 INFO [com.azu.sto.blo.imp.Ser.listBlobContainersSegment] (reactor-http-epoll-1) <-- 200 https://cqaccpeterpalagap1.blob.core.windows.net?comp=REDACTED (61 ms, unknown-length body)(body content not logged)<-- END HTTP
2021-03-02 14:04:55,418 INFO [com.azu.sto.blo.imp.Ser.listBlobContainersSegment] (parallel-5) --> GET https://cqaccpeterpalagap1.blob.core.windows.net?marker=REDACTED&comp=REDACTED(empty body)--> END GET
2021-03-02 14:04:55,487 INFO [com.azu.sto.blo.imp.Ser.listBlobContainersSegment] (reactor-http-epoll-1) <-- 200 https://cqaccpeterpalagap1.blob.core.windows.net?marker=REDACTED&comp=REDACTED (69 ms, unknown-length body)(body content not logged)<-- END HTTP
2021-03-02 14:04:55,493 INFO [com.azu.sto.blo.imp.Ser.listBlobContainersSegment] (parallel-7) --> GET https://cqaccpeterpalagap1.blob.core.windows.net?marker=REDACTED&comp=REDACTED(empty body)--> END GET
...
Steps to reproduce:
Open AzureStorageDatalakeTest
Find the two occurrences of the URL of this issue, uncomment the blocks below
Expected: the test should pass
Actual: the above sequence of messages is repeated in the log until one cancels the Maven execution on the command line
The text was updated successfully, but these errors were encountered:
Rel. #2289
Calling
azure-storage-datalake:cameltesting?operation=listFileSystem
causes the following flood of requests:Steps to reproduce:
AzureStorageDatalakeTest
Expected: the test should pass
Actual: the above sequence of messages is repeated in the log until one cancels the Maven execution on the command line
The text was updated successfully, but these errors were encountered: