Clovertech

Sending huge file to a webservice

› Clovertech Forums › Read Only Archives › Intelligent Health Broker › Intelligent Health Broker › Sending huge file to a webservice

  • Creator
    Topic
  • February 26, 2014 at 3:39 am #54065
    SREEKANTH CHANDIKA
    Participant

      I am trying to send a large file to a webservice client and IB server rejects as it cannot handle. Any help on how to change the server settings to enable it send huge data is highly appreciated

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • February 26, 2014 at 5:01 am #80053
        Charlie Bursell
        Participant

          What version of Cloverleaf?  For 5.8.5+  The new web services is much better (CAA-WS)

        • February 27, 2014 at 1:12 am #80054
          Richard Hart
          Participant

            Hi Sreekanth.

            How huge is huge?

            There is an internal timeout and if you are validating the message before ACKing this could be an issue.

            We have had 10mb files and  I’m pretty sure a 30mb file, although this was in error!

          • March 1, 2014 at 12:02 pm #80055
            SREEKANTH CHANDIKA
            Participant

              We are using 5.8 and file size is around 50 MB.

            • March 7, 2014 at 3:11 am #80056
              Elisha Gould
              Participant

                There is an issue with the grm xml processor in 5.8 if you try reading the data from the document, and is 5-10 times slower than 5.6.

                It appears to do all the processing on the disk and it does not support grabbing just the next entry, but instead parses the xml document to that entry again.

                The result is that for a 50MB xml document it could take 1/2 hour to an hour to process.

                Our workaround was to use a different basic xml parser that did not perform xsd validate, and to also increase the timeouts in the tomcat configuration:

                platform/apps/conf/reg.xml

                platform/apps/conf/server.xml

                If you do not perform any processing on the document, you may be able to get away with just increasing the timeouts in the tomcat configuration.

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Intelligent Health Broker’ is closed to new topics and replies.