Issue description from customer:

We are seeing errors when using the OutputChart component and having multiple browser windows or tasb from the same browser view the same page. The application is configured with "com.icesoft.faces.concurrentDOMViews" set to true and "com.icesoft.faces.synchronousUpdate" set to false.

I have reproduced this with a simple web app with two charts on it that are being updated by a background thread once per second. With two browser windows looking at the same page, the chart images swap places, become unavailable, etc.

Also I have noticed severe memory leaks with this type of application. Looking at the source, I see that the image resource is registered but is never released until the session expires. With a long running session, this will chew through memory.

See file "com.icesoft.faces.webapp.http.core.ResourceDispatcher". The "registered" property (an ArrayList) is always added to, but only cleared when the session expires.

Also see "com.icesoft.faces.webapp.http.common.standard.pathDispatcherServer". It maintains two ArrayList properties, "matchers" and "servers" that also grow without bounds in the situation.

I understand that the requirement to have dynamic resource stay available, but in this case, the chart component is being updated. So maybe the when the chart is updated, the resource for the previous image should replace the resource or the resource name should be the constant, so that for a chart component the resource URL would remain constant but the content would change. Obviously the would require the proper caching and expiration meta data to force the browser to refetch the image.