It seems that debugging portlets using the Portal 5.1 Test Environment is no
t so easy. All of our developers experience an issue where a Servlet.Engine.
Transports thread gets paused. The only way to recover from this is to selec
t each of these threads and
click the pause button. Interestingly, the debugger does not know these thre
ads are paused - this would make the process of recovering a bit easier as w
e would see the stack in our little debug window. Unfortunately, this is not
 so.

Had anyone else experienced this?

[ Post a follow-up to this message ]