Timeline for Connection pooling in the CIL
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 20, 2017 at 8:49 | comment | added | Quirijn | I added an issue just now. | |
| Jan 11, 2017 at 12:39 | vote | accept | Quirijn | ||
| Jan 9, 2017 at 21:30 | answer | added | Quirijn | timeline score: 5 | |
| Jan 9, 2017 at 14:43 | comment | added | Bengineer | In addition, we use the client connection provided by our OData library - so you could submit an enhancement direct to that repository. See: github.com/sdl/odata/blob/… | |
| Jan 9, 2017 at 14:41 | comment | added | Bengineer |
I will add to the backlog as an enhancement. In the meantime you may wish to try configuring Tomcat's server.tomcat.max-threads which specifies the maximum number of request processing threads that the connector can handle. The default is 200. This can be modified by creating (or modifying) a file named application.properties in the config folder, and setting a value, such as: server.tomcat.max-threads=400
|
|
| Jan 9, 2017 at 14:38 | history | tweeted | twitter.com/StackTridion/status/818466921880424449 | ||
| Jan 9, 2017 at 14:25 | comment | added | Quirijn | Thanks, Ben. Is this on the roadmap at all, to your knowledge? | |
| Jan 9, 2017 at 14:23 | comment | added | Bengineer | We only support the pooled connection manager in our Transport Service client. Not in the CIL Java library. | |
| Jan 9, 2017 at 12:08 | history | asked | Quirijn | CC BY-SA 3.0 |