I was able to track down the source of our problem and I did create a
https://issues.apache.org/jira/browse/WICKET-2534 JIRA issue which was
patched in Wicket 1.4.4. It boiled down to a resource leak in the
URLResourceStream which is used by wicket to get access to the
lastModifiedTime of jar fi
t/msg20951.html
here
Adam
igor.vaynberg wrote:
>
> we had to revert a part of that patch in 1.4.5 to fix a resource
> streaming problem. please check with that.
>
> -igor
>
> On Wed, Dec 30, 2009 at 8:02 AM, adamatmagpie wrote:
>>
>> I was able to track down t
