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 [EMAIL PROTECTED] 2006-05-04 00:56 ------- In step 3, thread-B initialized parameterClasses as an array of null. Then in step 4, thread-A couldn't find validateId method because parameterClasses was incorrect. If you thought that this problem was depends on the configuration, I say "No". Like I said, this exception didn't occur when I accessed with a browser. In other words, configuration was correct and this problem didn't occur when ValidatorAction was accessed by single thread. I putted a whole stack trace. The information was chipped off at line 627. But we can suppose the real reason by followings. A) ValidatorException was thrown because NoSuchMethodException was catched at line 626. B) NoSuchMethodException was thrown because parameterClasses was incorrect. We can see it in the stack trace. "FieldChecks.validateId(java.lang.Object, null, null, null, null, null)" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Regards, -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
