yeah, i just figured that out. i'll just patch our wicket for now. but we
should add this for wicket 1.4 (in a nicer way than this (generic utility
method), of course):
final StringBuilder builder =
new StringBuilder();
StackTraceElement[] elements =
t.getStackTrace();
for (int i = 0; i <
elements.length; i++) {
builder.append(elements[i]);
}
throw new
WicketRuntimeException("After " + timeout + " the Pagemap "
+ pageMapName +
" is still locked by: " + t
+ ", giving up
trying to get the page for path: " + path + "\nStack
Trace: " + builder.toString());
Eelco Hillenius wrote:
>
>> makes sense all right. is there any way we could print out a stack trace
>> of
>> the thread that's holding the monitor we're trying to grab? maybe via
>> JMX?
>> this would be extremely useful when this exception is thrown!
>
> We've had a thread about that, and the conclusion was that this is
> possible (I believe Johan built it) but only with Java 5.
>
> Eelco
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>
--
View this message in context:
http://www.nabble.com/pagemap-locking-tf3996742.html#a11351736
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
