Activity

log was harmless, it is expected behavior. The big problem was that there are two places where this could happen in the same try/catch block, this particular message was expected and the other is an error that is handled gracefully.

Scott Feldstein
added a comment - 25/Jul/11 12:32 PM log was harmless, it is expected behavior. The big problem was that there are two places where this could happen in the same try/catch block, this particular message was expected and the other is an error that is handled gracefully.