You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2011/08/04 11:49:27 UTC

[jira] [Resolved] (CMIS-416) Can't execute org.apache.chemistry.opencmis.client.api.Session.query() method under WL 10.x app server because HTTP POST chunking value is set to > 64k in size

     [ https://issues.apache.org/jira/browse/CMIS-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Müller resolved CMIS-416.
---------------------------------

    Resolution: Fixed
      Assignee: Florian Müller

Reduced chunk size to 64k.

> Can't execute org.apache.chemistry.opencmis.client.api.Session.query()  method under WL 10.x app server because HTTP POST chunking value is set to > 64k in size
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CMIS-416
>                 URL: https://issues.apache.org/jira/browse/CMIS-416
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-client-bindings
>    Affects Versions: OpenCMIS 0.4.0
>         Environment: WebLogic 10.3 running under Windows Server 2008
>            Reporter: George Florentine
>            Assignee: Florian Müller
>             Fix For: OpenCMIS 0.5.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> On WebLogic 10.3, the HTTP chunking size for keep-alive sessions must be < 64k size or an HTTP POST command will fail. In the 0.4.0 version of HttpUtils the BUFFER_SIZE constant is set to a pretty large value (2 * 1024 * 1024 bytes), set on line 54 of HttpsUtils.java . With this setting, HTTP POST methods that go through the HttpUtils.invoke() method fail with an error on WL 10.3.x servers. On line 166, this statement:
> conn.setChunkedStreamingMode(BUFFER_SIZE);
> sets the buffer size and the subsequent write of the buffer fails. Reducing the  size of BUFFER_SIZE to < 64k solves this issue. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira