|
|
|
[
Permlink
| « Hide
]
Eugene Zhuravlev - 14 Mar 07 16:21
Please check in task manager that after the debug session is stopped, the Tomcat's process actually exites.
I'm facing this problem too.
The only way I found to get rid of this bug is to change the debugging mode from socket to shared memory. Nima,
Can your problem be described by my post above? Eugene,
I checked all the processes in the task manager, tomcat is stopped but the debugger cannot be started for the second time. I think IDEA cannot close the opened socket connection with the server. Are there any error messages in console or exceptions in idea.log?
No, nothing
It just open the popup window to compile java files and rebuild the project (this phase goes well), then the popup window is closed and nothing happens. I'd proposed one if that was reproducible here.... Still I think this is not the thing we can influence on. IDEA uses debugging engine provided by JDK and all connections are controlled by this engine, not our code. With application servers it sometimes happens that the server process does not quit and occupies the port, hence the problem with successive attempts to connect.
Could you please take a thread dump of the state when debugger doe not start? To do this you either need to run IDEA with console enabled or use the tool http://www.adaptj.com/root/main/download |
|||||||||||||||||||||||||||||||||||||||||||