[JAVA-2851] Decrease logging spam for ObjectId when JMX is unavailable Created: 03/May/18 Updated: 28/Oct/23 Resolved: 21/May/18 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Monitoring |
| Affects Version/s: | None |
| Fix Version/s: | 3.8.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Currently the ObjectId class logs a warning with a stack trace when it's unable to get a process id from JMX. The driver should log this at DEBUG and not include the stack trace. This will help reduce log spam in environments where JMX is unavailable, e.g. Android. |
| Comments |
| Comment by Jeffrey Yemin [ 21/May/18 ] |
|
Note: wrong issue mentioned in the commit. |
| Comment by Jeffrey Yemin [ 21/May/18 ] |
|
Author: {'username': 'jyemin', 'name': 'Jeff Yemin', 'email': 'jeff.yemin@10gen.com'}Message: The ObjectId class logs its failure to get either the machine identifer, This is annoying for applications running on platforms where this occurs This commit removes the stack trace from the log message and changes the |