Closed GoogleCodeExporter closed 8 years ago
Hi Wilson,
I looked at the code again for any issues and there are no issues with this
stack trace. In fact, this error needs to be thrown up the stack so that this
socket session can be cleaned up. However, I did notice that all the Network
errors are being logged twice. Once in the ServerHandler and another in the
ErrorHandler. This doubles up the logs which can be of significant size
considering your scale.
Taking that into account, I am attaching a new dataService-2.4-M2.jar file with
reduced logging. I hope this helps you cut down on some logging.
All you need to do is copy the attached jar file to the deploy/openmobster.last
directory. For safety, backup the existing dataService-2.4-M2.jar file
somewhere else before you overwrite it.
I hope this new jar file helps you. Also, I am assuming your dataService debug
level is turned off (ships like this by default). If not, you can cut down on
logging tremendously by turning off the debug level logging in the dataService.
Anyways, Good Luck
Original comment by openmobs...@gmail.com
on 25 Sep 2013 at 3:21
Attachments:
I will filter this particular exception from the logs in the next
release...Just this exception will be removed since there are no functional
side effects with this error
Original comment by openmobs...@gmail.com
on 25 Sep 2013 at 3:48
Original comment by openmobs...@gmail.com
on 25 Sep 2013 at 3:49
Original comment by openmobs...@gmail.com
on 24 Dec 2013 at 5:11
Original issue reported on code.google.com by
wilson.t...@gmail.com
on 10 Sep 2013 at 3:08Attachments: