Hi, On Wed, Oct 21, 2015 at 3:43 PM, Muhui Jiang <[email protected]> wrote: > I see. I fixed this by changing the source code to disable the check whether > the number of concurrent streams is exceed. But anyway thanks a lot. > > BTW: do you think client can send max_concurrent_streams in the settings > frame to tell the server to change this value? Nginx support it while h2o > doesn't support it. > > A question related to this: > I tried to make 500 concurrent streams using a for loop. And when the file I > request is big, it may come out such a exception below: > > 2015-10-21 21:33:03.397:DBUG:oejh.HTTP2Session:qtp1360875712-10: Removed > HTTP2Stream@61009542#999{sendWindow=2147483647,recvWindow=65525,reset=false,CLOSED} > > 2015-10-21 21:33:03.397:WARN:oeju.Promise$Adapter:qtp1360875712-10: > > java.lang.OutOfMemoryError: Java heap space > > > when the client make a request for a small file, this exception may not be > raised I am wondering is it because Jetty has some constraints on it.
There are no constraints in Jetty. You just started the JVM with a heap too small. -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
