JSR-160 connection pooling

Description

As a Jolokia User
I want to have an effective usage and re-usage of JSR-160 connections
because this save resources on the Jolokia proxy server.

Environment

None

Acceptance Criteria

* Performance tests using proxies with pooling enabled must be significantly faster than without * Size of the agents must not increase more than 50k * Heap-Memory Usage must not increase unbounded (verify with performance test)

Balsamiq Wireframes

Activity

Show:

Roland Huss April 8, 2011 at 8:33 PM

Since all routing information comes from outside (i.e. within the request), it might get tricky to structure the cache properly, since various targets and hence various different JSR-160 connections needs to be handled.

Taken into consideration the size restrictions of the agents, it's questionable whether a full blown cache library can be included or whether one should stick to the means that the JDK provides (the later possibly).

Details

Assignee

Reporter

Components

Fix versions

Priority

Created April 8, 2011 at 6:42 PM
Updated February 29, 2012 at 5:52 PM