It has been shown many times why this change was a bad idea.
Nevermind the theoretical nature of the initial objections, which have
also been shown to be true concerns (see
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6489540). It has
been shown that this change doesn't really solve
Hi All,
I am facing a problem with wicket i.e.
There are few links on my page. On Clicking any link for first time, page
just refreshes, but attached listener is not called. For later clicks, it
works correctly.
It has been observed that, for first click it invokes wicket's
'newRequestCycle'
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
You don't create the thread yourself. Java does!
On Tue, May 25, 2010 at 9:32 AM, Alex Objelean alex.objel...@gmail.com 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
OK, then just give me whatever code you use which causes the memory leak...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/vote-Revert-WICKET-2846-tp2226987p2230020.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Just try using something like JFreeChart
On Tue, May 25, 2010 at 9:36 AM, Alex Objelean alex.objel...@gmail.com wrote:
OK, then just give me whatever code you use which causes the memory leak...
--
View this message in context:
Or draw something yourself if you want to skip the dependency
On Tue, May 25, 2010 at 9:38 AM, James Carman
ja...@carmanconsulting.com wrote:
Just try using something like JFreeChart
On Tue, May 25, 2010 at 9:36 AM, Alex Objelean alex.objel...@gmail.com
wrote:
OK, then just give me
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
That is exactly what I am trying to do. To make a simple example that cause
the leak and monitor it... By quickstart I mean the simplest project which
helps to cause the leak.
--
View this message in context:
On 25/05/2010 10:47, Alex Objelean wrote:
That is exactly what I am trying to do. To make a simple example that cause
the leak and monitor it... By quickstart I mean the simplest project which
helps to cause the leak.
package mm.util.app;
import java.awt.GraphicsEnvironment;
public class
Here's an example page that you can plug into a quickstart to show the bug:
public class HomePage extends WebPage
{
private static final long serialVersionUID = 1L;
static
{
System.out.println(I'm being initialized within the context
of thread +
I ran this page and then fired up jvisualvm and took a heap dump.
Go to the Classes view. Find the java.lang.Thread class. Click on
it and it will bring up a list of instances. Go through them until
you find one with the name Java2D Disposer (#13 for me). Then, look
for the field called
On Sat, May 22, 2010 at 2:22 AM, Jeremy Thomerson jer...@wickettraining.com
wrote:
As you may have noticed over the past couple of days (ha), there has been
quite a bit of discussion over what seemed at the time like a very trivial
change in WICKET-2846 [*]. The end result is that it does
Please create a quickstart.
On Tue, May 25, 2010 at 6:57 AM, AChahal ak...@qasource.com wrote:
Hi All,
I am facing a problem with wicket i.e.
There are few links on my page. On Clicking any link for first time, page
just refreshes, but attached listener is not called. For later clicks, it
I'm searching for a way to make our website more manageable, and I've
heard that svnpubsub will allow us to quickly update our website
(faster than currently). The snag is that the files need to be in a
svn repo.
As I hate xml for editing documents, I was looking for a decent
replacement. Having
The github project I mentioned is:
http://github.com/dashorst/wicket-site/
Of course this will be folded back into ASF svn should we decide to use Jekyll.
I'll let this discussion/vote/decision making process run for about a
week and continue to tweak the project.
Martijn
On Tue, May 25, 2010
James, thank you very much for such a detailed description. I appreciate your
effort and I'm sure this experience helped me to learn a lot of new things.
Nevertheless, I would like to clarify few things:
Here is a definition of memory leak: If a program holds a reference to a
heap chunk that
On Tue, May 25, 2010 at 4:57 PM, Alex Objelean alex.objel...@gmail.comwrote:
James, thank you very much for such a detailed description. I appreciate
your
effort and I'm sure this experience helped me to learn a lot of new things.
Nevertheless, I would like to clarify few things:
Here is
It seems that this memory leak happens only once. I guess the first deploy
(the one which will force the creation of the background Java2D thread) will
hang around forever, but subsequent redeploys will be correctly cleaned-up.
Also, what leaks is the classloader. Only static variables and class
-1
Stefan
On Tue, May 25, 2010 at 5:13 PM, Stefan Lindner lind...@visionet.de wrote:
-1
Stefan
Voting has ended, it's already reverted.
--
Jeremy Thomerson
http://www.wickettraining.com
Jeremy, I've tried with redeploy... same story. I'm not insisting on bringing
the issue back. If is the willing of the majority, I'm ok. It is just to
help me understand something that I'm not find that obvious.
Alex
--
View this message in context:
I've done some playing with Tomcat undeploy and it does appear that
the ITL reference is cleared (perhaps Sun/Oracle/Sunacle should close
the bug?). However, this does not make the ITL implementation
valid, IMHO. It doesn't work (out of the box) for the preferred
method of executing asynchronous
I'm glad we finally came to a conclusion. Do you think it would be useful to
update the task description in JIRA? Even if it will remain 'WONT FIX', I
don't care, at least we have a proof and learn a little bit more from this
experience.
Thanks!
Alex
--
View this message in context:
On Wed, May 26, 2010 at 12:07 AM, Alex Objelean alex.objel...@gmail.comwrote:
I'm glad we finally came to a conclusion. Do you think it would be useful
to
update the task description in JIRA? Even if it will remain 'WONT FIX', I
don't care, at least we have a proof and learn a little bit
The newest tomcat has improved permgen cleanup which they backported
from tomcat 7 iiuc.
Martijn
On Wed, May 26, 2010 at 3:10 AM, James Carman
ja...@carmanconsulting.com wrote:
I've done some playing with Tomcat undeploy and it does appear that
the ITL reference is cleared (perhaps
26 matches
Mail list logo