[
https://issues.apache.org/jira/browse/KNOX-2993?focusedWorklogId=895874&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-895874
]
ASF GitHub Bot logged work on KNOX-2993:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Dec/23 15:58
Start Date: 15/Dec/23 15:58
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request, #827:
URL: https://github.com/apache/knox/pull/827
## What changes were proposed in this pull request?
This is a very small, but even more imprtant change because it helps us a
lof during the troubleshooting of service discovery or simple descriptor
handler issues: related error stack traces are displayed on `INFO` level.
## How was this patch tested?
Manually tested:
```
2023-12-15 16:57:35,494 ERROR knox.gateway
(DescriptorsMonitor.java:onFileChange(123)) - An error occurred while
processing dt.json : java.lang.IllegalArgumentException: Unresolved provider
configuration reference: kerberos-providers
java.lang.IllegalArgumentException: Unresolved provider configuration
reference: kerberos-providers
at
org.apache.knox.gateway.topology.simple.SimpleDescriptorHandler.handleProviderConfiguration(SimpleDescriptorHandler.java:266)
~[gateway-topology-simple-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
at
org.apache.knox.gateway.topology.simple.SimpleDescriptorHandler.generateTopology(SimpleDescriptorHandler.java:416)
~[gateway-topology-simple-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
at
org.apache.knox.gateway.topology.simple.SimpleDescriptorHandler.handle(SimpleDescriptorHandler.java:199)
~[gateway-topology-simple-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
at
org.apache.knox.gateway.topology.simple.SimpleDescriptorHandler.handle(SimpleDescriptorHandler.java:97)
~[gateway-topology-simple-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
at
org.apache.knox.gateway.services.topology.monitor.DescriptorsMonitor.onFileChange(DescriptorsMonitor.java:97)
[gateway-server-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
at
org.apache.knox.gateway.services.topology.monitor.DescriptorsMonitor.onFileCreate(DescriptorsMonitor.java:64)
[gateway-server-2.1.0-SNAPSHOT.jar:2.1.0-SNAPSHOT]
at
org.apache.commons.io.monitor.FileAlterationObserver.doCreate(FileAlterationObserver.java:391)
[commons-io-2.8.0.jar:2.8.0]
at
org.apache.commons.io.monitor.FileAlterationObserver.checkAndNotify(FileAlterationObserver.java:346)
[commons-io-2.8.0.jar:2.8.0]
at
org.apache.commons.io.monitor.FileAlterationObserver.checkAndNotify(FileAlterationObserver.java:305)
[commons-io-2.8.0.jar:2.8.0]
at
org.apache.commons.io.monitor.FileAlterationMonitor.run(FileAlterationMonitor.java:184)
[commons-io-2.8.0.jar:2.8.0]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_282]
```
Issue Time Tracking
-------------------
Worklog Id: (was: 895874)
Remaining Estimate: 0h
Time Spent: 10m
> Show error stack trace when simple descriptor handler fails to parse a
> descriptor
> ---------------------------------------------------------------------------------
>
> Key: KNOX-2993
> URL: https://issues.apache.org/jira/browse/KNOX-2993
> Project: Apache Knox
> Issue Type: Task
> Components: Server
> Affects Versions: 2.0.0, 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the error stack trace is shown in gateway.log only, if the
> {{org.apache.knox.gateway}} log level is set to {{DEBUG}}:
> {noformat}
> @Message( level = MessageLevel.ERROR, text = "An error occurred while
> processing {0} : {1}" )
> void simpleDescriptorHandlingError(String simpleDesc,
> @StackTrace(level = MessageLevel.DEBUG)
> Exception e);
> {noformat}
> This makes our lives hard when dealing with errors related to events coming
> from CM configuration monitoring.
> I recommend showing this information even on {{INFO}} level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
