commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39393] - [validator] ValidatorAction needs thread-safe
Date Wed, 03 May 2006 17:02:44 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39393>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39393





------- Additional Comments From martinc@apache.org  2006-05-03 17:02 -------
Your description doesn't explain why an exception would be thrown, though. Yes,
in step 4, thread-A will be using the parameterClasses value that was set by
thread-B in step 3, but so what? That's not going to hurt anything.

We really do need to see an accurate stack trace. The one you have posted is
actually not possible. There is no way that loadValidationMethod is going to
call FieldChecks.validateId, which is what your stack trace shows. The trace
also shows that the *real* problem is happening in what is presumably your own
code - the package name is com.example.validator, which isn't part of Commons
Validator.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message