Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: web service bug
-
Labels:None
-
Mantis ID:13136
Description
WebService.log.error(message) doesn't seem to be being reported - even though error message is passed to clients. Specific case is :
catch (Exception e) {
log.error(IMPLCLASS+": Couldn't write input sequences to "+inseqs.getAbsolutePath(), e);
throw new Exception("Server error: failed to write input sequence set\n");
}
where client receives the Server error message, but the logs do not contain log.error message.
****** ADDITIONAL INFORMATION ******
Reviewing code suggests that full disks may also cause untrapped exceptions in client code.
catch (Exception e) {
log.error(IMPLCLASS+": Couldn't write input sequences to "+inseqs.getAbsolutePath(), e);
throw new Exception("Server error: failed to write input sequence set\n");
}
where client receives the Server error message, but the logs do not contain log.error message.
****** ADDITIONAL INFORMATION ******
Reviewing code suggests that full disks may also cause untrapped exceptions in client code.