[
https://issues.apache.org/jira/browse/CAMEL-14172?focusedWorklogId=342280&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-342280
]
ASF GitHub Bot logged work on CAMEL-14172:
------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Nov/19 23:37
Start Date: 12/Nov/19 23:37
Worklog Time Spent: 10m
Work Description: dschlenk commented on pull request #3332: CAMEL-14172:
when loggingSizeLimit is -1 it should do what the docs say it does
URL: https://github.com/apache/camel/pull/3332
I was able to manually verify this fix works against 2.25.0-SNAPSHOT but
couldn't figure out how to write a unit test. Happy to do that if given some
hints on how to (successfully) get at log output in a unit test or access the
underlying CXF LoggingFeature from a CxfEndpoint.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 342280)
Remaining Estimate: 0h
Time Spent: 10m
> setting loggingSizeLimit to -1 when using CXF components does not disable the
> size limit as the docs say
> --------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-14172
> URL: https://issues.apache.org/jira/browse/CAMEL-14172
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.24.2
> Reporter: David Schlenk
> Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The docs for the CXF component claim that setting the value of option
> *loggingSizeLimit* to -1 will disable the size limit. This is not the case -
> when using -1, the default size limit is still in place. CAMEL-9102
> theoretically fixes this issue, but seems to have been closed without merging
> the PR. Happy to provide a new PR that does similar against current, but it
> would be nice if either the docs were changed or the bug gets fixed to do
> what the docs say.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
