java.lang.IllegalArgumentException at java.nio.Buffer.limit(Unknown Source)

Charles Moulliard added a comment - 18/Mar/10 9:33 AM - edited I see in the class SslHttpChannelEndPoint that we don't check if the size of the buffer is not negative or bigger than the buffer's capacity version : 6.1.14 int c=(header!= null && buffer!= null )?wrap(header,buffer):wrap(header); version : 6.1.22 if (header!= null && header.length()>0) { if (buffer!= null && buffer.length()>0) c=wrap(header,buffer); else c=wrap(header); } else c=wrap(buffer); This is why we get this error in Buffer class of NIO The code should be adapted

Greg Wilkins added a comment - 22/Mar/10 5:12 PM also raised as https://bugs.eclipse.org/bugs/show_bug.cgi?id=306376

Greg Wilkins added a comment - 22/Mar/10 5:13 PM I've tested both jetty-6 and jetty-7 with large (>100k) writes to both response streams and response writers, without any problem. It is true that the endpoint is not handling the large buffers, but it is handled in layers above. Can you tell me how you are calling the SSL endpoint so that it is passed these large NIO buffers?

Charles Moulliard added a comment - 23/Mar/10 1:29 AM Hi Greg, Many thanks for your help. In fact, the servicemix-http component of ServiceMix (2009-01) uses Jetty underneath to connect through SSL. Here is the class used : http://svn.apache.org/repos/asf/servicemix/components/bindings/servicemix-http/trunk/src/main/java/org/apache/servicemix/http/endpoints/HttpProviderEndpoint.java . In our particular case, we have extended a marshaller class which in charge to send the request to a WebMethod HTTP server. Here is the snaphot of the code : Could it be possible that we have a side effect (negative) with NIO because we use here a ByteBufferArray (org.mortbay.io) for the content that we send to the HTTP request ? import java.io.ByteArrayOutputStream; import java.net.URI; import java.net.URLEncoder; import java.text.DateFormat; import java.text.SimpleDateFormat; import java.util.Date; import javax.jbi.messaging.MessageExchange; import javax.jbi.messaging.NormalizedMessage; import javax.xml.transform.stream.StreamResult; import org.apache.servicemix.http.endpoints.DefaultHttpProviderMarshaler; import org.apache.servicemix.http.jetty.SmxHttpExchange; import org.apache.servicemix.jbi.jaxp.StAXSourceTransformer; import org.mortbay.io.ByteArrayBuffer; import org.mortbay.jetty.HttpHeaders; public class ExdiHttpProviderMarshaller extends DefaultHttpProviderMarshaler { public void createRequest( final MessageExchange exchange, final NormalizedMessage inMsg, final SmxHttpExchange httpExchange) throws Exception { ... // Get the content of the message and transform it to a string ByteArrayOutputStream messageContentAsBaos = new ByteArrayOutputStream(); if (inMsg.getContent() != null ) { transformer.toResult(inMsg.getContent(), new StreamResult(messageContentAsBaos)); } ... httpExchange.setRequestHeader(HttpHeaders.CONTENT_TYPE, ExdiMarshallerConstants.CONTENT_TYPE); httpExchange.setRequestHeader(HttpHeaders.AUTHORIZATION, "Basic " + credentials); httpExchange.setRequestHeader(HttpHeaders.CONTENT_LENGTH, sb.length() + ""); httpExchange.setRequestContent( new ByteArrayBuffer(sb.toString()));

Greg Wilkins added a comment - 20/Apr/10 4:22 PM Ah! client side!

Greg Wilkins added a comment - 21/Apr/10 5:26 AM If the buffer is non NIO, get the array and wrap it with a ByteBuffer.