Back in October, my team first encountered the following exception using
Struts 1.1 and WebLogic 6.1 SP2:
java.net.BindException: Address in use: JVM_Bind Perhaps another process is
using port <xxxxx>
Well, after several months, we have finally solved the problem. The problem
was due to an error in our version of the Struts "validation.xml" file.
Specifically, for the "publicId" value in the DOCTYPE section, we had the
following (2nd line contains error):
<!DOCTYPE form-validation PUBLIC
"-//Apache Software Foundation//DTD Struts Validation Configuration
1.1//EN"
"http://jakarta.apache.org/commons/dtds/validator_1_0.dtd";>
In the latest version of Struts 1.1 (beta 3), the "publicID" should be:
<!DOCTYPE form-validation PUBLIC
"-//Apache Software Foundation//DTD Commons Validator Rules
Configuration 1.0//EN"
"http://jakarta.apache.org/commons/dtds/validator_1_0.dtd";>
Does anyone understand why having the incorrect ID would cause this socket
"still in use" error for up to 5 or 10 minutes? Furhtermore, the expected
ID must have changed from the earliest Struts 1.1 beta release. Does anyone
know the history here?
Thanks,
JOHN
P.S. Our original post for describing this problem was:
http://www.mail-archive.com/struts-user@jakarta.apache.org/msg45187.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
