[ 
https://issues.apache.org/jira/browse/CMIS-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170881#comment-13170881
 ] 

Dilip MD commented on CMIS-416:
-------------------------------

Hi,

0.6.0 version version still has buffer set to (2 * 1024 * 1024). 

After changing this to less than 64 KB, it solves problem with AtomPub 
connection. But not with Webservices type and it throws up error like below. 

java.lang.ArrayIndexOutOfBoundsException: -1
        at 
weblogic.utils.http.HttpChunkOutputStream.writeChunkHeader(HttpChunkOutputStream.java:177)
        at 
weblogic.utils.http.HttpChunkOutputStream.flush(HttpChunkOutputStream.java:197)
        at 
weblogic.utils.http.HttpChunkOutputStream.close(HttpChunkOutputStream.java:160)
        at 
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:347)
        at 
weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
        at 
weblogic.net.http.HttpURLConnection.getHeaderFields(HttpURLConnection.java:718)
        at 
com.sun.xml.ws.transport.http.client.HttpClientTransport.getHeaders(HttpClientTransport.java:179)
        at 
com.sun.xml.ws.transport.http.client.HttpResponseProperties.getResponseHeaders(HttpResponseProperties.java:62)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
com.sun.xml.ws.api.PropertySet$MethodAccessor.get(PropertySet.java:283)
        at com.sun.xml.ws.api.PropertySet.get(PropertySet.java:335)
        at 
com.sun.xml.ws.api.DistributedPropertySet.get(DistributedPropertySet.java:126)
        at com.sun.xml.ws.client.ResponseContext.get(ResponseContext.java:109)
        at 
org.apache.chemistry.opencmis.client.bindings.spi.webservices.AbstractPortProvider.endCall(AbstractPortProvider.java:152)
        at 
org.apache.chemistry.opencmis.client.bindings.spi.webservices.ObjectServiceImpl.createDocument(ObjectServiceImpl.java:90)

Here I'm using Weblogic 10.3.3. Also tried with increasing the 
"-Dweblogic.Chunksize" value which did not work. Any idea on this? 
 
                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to