Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-16252

[camel-azure-storage-blob] Stream caching bug due to unsupported InputStream mark operation

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.7.0
    • 3.7.3, 3.9.0
    • camel-azure
    • None
    • Unknown

    Description

      Already asked the question in the mailing list. Claus Ibsen stated that this is actually a bug: 

      Ad 1)
      Yes that seems like a little bug. You are welcome to create a JIRA ticket.

      Here is my description of the bug:
      <dependency>
          <groupId>org.apache.camel.springboot</groupId>
          <artifactId>camel-azure-storage-blob-starter</artifactId>
          <version>3.7.0</version>
      </dependency>

      We are currently trying to integrate azure cloud by using the camel-azure-storage-blob component. Everything works fine until we activate stream caching and camel starts to spool the payload. In this case we get the following error:

      Caused by: java.lang.IllegalArgumentException: InputStream of body exchange does not support mark/rest operations.

                  at org.apache.camel.component.azure.storage.blob.BlobStreamAndLength.createBlobStreamAndLengthFromExchangeBody(BlobStreamAndLength.java:52)

                  at org.apache.camel.component.azure.storage.blob.operations.BlobOperations.uploadBlockBlob(BlobOperations.java:181)

      I have looked into the source and think that the component does not load the stream properly from the FileInputStreamCache object. 

      Attachments

        1. azuredsl.txt
          0.7 kB
          Christian Müller

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            omarsmak Omar Al-Safi
            mueller110 Christian Müller
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment