AniRamadoss commented on issue #4084:
URL: https://github.com/apache/jena/issues/4084#issuecomment-5052707185

   I haven't tried reproducing with Jena6, but I took a brief look at the code 
and the same assumptions seem to hold.
   
   Jetty Server object is instantiated here -
   
https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-main/src/main/java/org/apache/jena/fuseki/main/JettyHttps.java#L93
   
   Creates a server with just a threadpool passed in -
   
https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-main/src/main/java/org/apache/jena/fuseki/main/JettyServer.java#L476
   
   The default Server initialization still initializes an ArrayByteBufferPool -
   
https://github.com/jetty/jetty.project/blob/jetty-12.1.x/jetty-core/jetty-server/src/main/java/org/eclipse/jetty/server/Server.java#L155
   
   ArrayByteBufferPool still defaults to 64 KB for its maxCapacity -
   
https://github.com/jetty/jetty.project/blob/jetty-12.1.x/jetty-core/jetty-io/src/main/java/org/eclipse/jetty/io/ArrayByteBufferPool.java#L154
   
   The HttpConfiguration Fuseki passes to Jetty via the ServerConnectors is 
created here -
   
https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-main/src/main/java/org/apache/jena/fuseki/main/sys/JettyLib.java#L96
   
   Where it sets an outputBufferSize of 5 MB - 
   
https://github.com/apache/jena/blob/main/jena-fuseki2/jena-fuseki-main/src/main/java/org/apache/jena/fuseki/main/sys/FusekiSystemConstants.java#L58
   
   The Jetty team has indicated that the behavior of their BufferPools 
provisioning buffers over the maxCapacity but not retaining them is an 
intentional feature, not a bug. I would expect the same scenario to be 
reproducible with Jena6 (and probably Jena5 too).  
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to