That's an interesting find; I've never seen that before. Does it happen
consistently?
That being said, it's highly unlikely we can reproduce it without some
insight into what modules you are using and (a guess from what I'm seeing
in the stack trace) whats in your @Startup module methods.
On Thu
Found one Java-level deadlock:
=
"Tapestry PeriodicExecutor":
waiting for ownable synchronizer 0x0007569066f8, (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync),
which is held by "main"
"main":
waiting to lock monitor 0x7fd8fc004188 (object
