I have problems debugging a servlet-based application
which seems to stumble upon a bug within a debugging
environment (Kawa, an IDE, a wrapper around JDK,
including Java Debugger, jdb). When this happens,
the only way out is to kill the Kawa process from
task manager.
After reloading Kawa, and trying to restart debugging
session, what happens is that my servlet is unable to
bind itself, and throws the following:
java.rmi.server.ExportException: Port already in use: 1109; nested
exception is:
java.net.BindException: Address in use: bind
and is unable to start debugging session.
The only cure I have found so far is to log in once again
(regardless of the OS - Win95/98/NT, the result is the same).
Only in this manner can I bind to the socket previously
allocated by the dead Kawa (my servlet, that is).
Is there some other way to continue debug without having to
log in again?
Is there some other JDK wrapper that offers (bug-free?)
debugging?
Thanks for reading this last line. (;
--
shone | [EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
