----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56034/#review163371 -----------------------------------------------------------
geode-core/src/main/java/org/apache/geode/cache/client/internal/OpExecutorImpl.java (line 794) <https://reviews.apache.org/r/56034/#comment234783> Shouldn't you just uncomment the 'e' parameter in this logger.debug message? e.printStackTrace will just do to system out. - Dan Smith On Jan. 28, 2017, 12:49 a.m., nabarun nag wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/56034/ > ----------------------------------------------------------- > > (Updated Jan. 28, 2017, 12:49 a.m.) > > > Review request for geode, Barry Oglesby, Jason Huynh, Dan Smith, and xiaojian > zhou. > > > Repository: geode > > > Description > ------- > > Issue: > During an exception we just get an loggger.warn message with a custom > message. We have no clue what caused the execution. > > Solution: > When debug is enabled, It will print the stacktrace > > > Diffs > ----- > > > geode-core/src/main/java/org/apache/geode/cache/client/internal/OpExecutorImpl.java > 54f8e39 > > Diff: https://reviews.apache.org/r/56034/diff/ > > > Testing > ------- > > > Thanks, > > nabarun nag > >
