It seems that debugging portlets using the Portal 5.1 Test Environment is not 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 select each of these threads and click the pause button. Interestingly, the debugger does not know these threads are paused - this would make the process of recovering a bit easier as we would see the stack in our little debug window. Unfortunately, this is not so.

Had anyone else experienced this?