| Numéro d’ID de bogue |
BUG-000128534 |
| Envoi | February 10, 2020 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS GeoEvent Server |
| Version trouvée | 10.7.1 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 2016 64 Bit |
| Statut | Known Limit
Après examen par l’équipe de développement, il a été déterminé que ce problème est lié à une limitation connue du logiciel sur laquelle Esri n’a aucun contrôle. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
This behavior is by design. GeoEvent Server allows administrators granular control over the type/level of messages requested from specific loggers. Administrators can leave ROOT logging set to WARN or ERROR while requesting DEBUG messages from specific loggers. Once requested, DEBUG logging must be turned of for those specific loggers; requesting ROOT "return" to WARN or ERROR does not do this.
Administrators who have forgotten which loggers they have requested specific levels of logged messages from can edit the org.ops4j.pax.logging.cfg file located beneath \GeoEvent\etc and scroll to the end of the file to review their settings. Deleting lines for specific loggers with specific logging levels effectively delegates logging control to whatever has been specified for the ROOT logger.
Solution de contournement
To reset multiple configured loggers to the default settings, delete a series of line items out of the following file:
"C:\Program Files\ArcGIS\Server\GeoEvent\etc\org.ops4j.pax.logging.cfg"
Étapes pour reproduire
ID de bogue: BUG-000128534
Logiciel: