Sorry, but notion of "Wicket quickstart" for this issue has no sense.
Look, I shown you a opened bug report. I also shown how I force the java2d thread creation. Note, I create no threads myself, and AFAIR, even some (do not remember what) Wicket code triggered the java2d thread creation.
As a mater of java2d thread creation, it will got any inheritable thread local. That's not theory, it's fact!
So why I said it's not about quickstart, you must them open something (jvisualvm?) and monitor threads. Or you may also play with classloader and a not-small application and verify a leak.
Adriano On 25/05/2010 10:32, Alex Objelean wrote:
Hi Adriano again! I know you have no time for creating the quickstart. That is why I am trying to reproduce it. I want to make a quickstart to prove if the problem reported by you is true or false and will publish it when it is ready. I need some help from you. Could you give a simple example of how you create the thread in your application which handles the java2d and any other code you may find useful. Thanks! Alex
