Actually, I think it was just a listener method. There wasn't a =
deadlock, maybe it should have been sync'd. However, the question came =
up about listeners in general. And I think the real question is =
shouldn't listeners and submits by design, only allow one click of each? =
Should Tapestry by default disable links and buttons until it returns?
-----Original Message-----
From: Ivano Pagano [mailto:i.pagano@mclink.it]
Sent: Fri 6/23/2006 4:00 AM
To: Tapestry users
Subject: Re: Tapestry making Java use 99% cpu?
=20
Are you using code which should be synchronized... maybe your code is=20
stuck in a deadlock? or does the service still runs?
Mark Stang wrote:
>At one point, I noticed my machine going a bit crazy. I believe it =
happened when I clicked on a link and then clicked it again...
>
>hth,
>
>Mark
>
>
>
>-----Original Message-----
>From: sgendler@gmail.com on behalf of Sam Gendler
>Sent: Thu 6/22/2006 2:10 PM
>To: Tapestry users
>Subject: Re: Tapestry making Java use 99% cpu?
>=20
> =20
>
>>it is possible to get Tomcat to unload the WebappClassloader
>>cleanly (I did it), but this is beyond the scope of one email. :-(
>>
>> =20
>>
>
>But it isn't beyond the scope of a wiki page (nudge nudge, wink wink)
>
>--sam
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
> =20
>
--
Ivano Pagano
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
|