id summary reporter owner description type status priority milestone component version resolution keywords cc drp_resources i_links o_links remaining_time sprint 591 Impossible to correlate service log output jamoore jamoore "With multiple users, it is impossible to correlate the various statements related to a single call: {{{ 13:42:25,717 INFO [ServiceHandler] Meth: foo 13:42:25,717 INFO [ServiceHandler] Args: [[B@28b24ebd] 13:42:25,769 INFO [EventHandler] Auth: user=1,group=2,event=381(User) 13:42:25,788 INFO [ServiceHandler] Rslt: true }}} could just as easily be: {{{ 13:42:25,717 INFO [ServiceHandler] Meth: foo 13:42:25,717 INFO [ServiceHandler] Meth: bar 13:42:25,717 INFO [ServiceHandler] Args: [[B@28b24ebd] 13:42:25,717 INFO [ServiceHandler] Args: [[B@28b24ebd] 13:42:25,769 INFO [EventHandler] Auth: user=1,group=2,event=381(User) 13:42:25,769 INFO [EventHandler] Auth: user=2,group=2,event=381(User) 13:42:25,788 INFO [ServiceHandler] Rslt: true 13:42:25,788 INFO [ServiceHandler] Rslt: false }}} Options: 1. Add security context to each exception 1. Add a correlation ID Problems with (1): * Requires adding a serializable field which implies a serialVersionUID bump. (The field is necessary because by the time that some logging occurs, the user has already been logged out.) Adding the security context is not a bad idea, but should be done in concert with further exceptin changes. Problems with (2): * This needs to be enforced on all logging statements which should be done in concert with #169 and other logging restructuring. Probably add a correlation ID to the output mentioned above. Further changes can be made." task new major Unscheduled Services 3.0-Beta1 logging, cleanup