Transaction logging - cannot modify the truncation size of the payload

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Transaction logging - cannot modify the truncation size of the payload

Using an older version of Connect (4.2.1).

I'm trying to increase the truncation size of the web services transaction logging, but I cannot get it to change.
Has anyone done this successfully?

For example:
FINE: Invoking handleMessage on interceptor org.apache.cxf.interceptor.LoggingInInterceptor@172a1780
Mar 31, 2017 4:13:26 PM
INFO: Inbound Message
ID: 16
Response-Code: 200
......<<removed logging>>
Message (saved to tmp file):
Filename: /apps/connectfx/gateway/temp/cxf-tmp-652156/cos2287423267104147031tmp
(message truncated to 65536 bytes)

It is truncating to 64K (64*1024).

I set a Java property named "" to a higher value (for the class).  This did not take, as I believe an interceptor is setting the value at a higher level.
Apache CXF debug logging indicates the following interceptors:

ar 31, 2017 4:13:26 PM org.apache.cxf.phase.PhaseInterceptorChain outputChainToLog
FINE: Chain org.apache.cxf.phase.PhaseInterceptorChain@6c315447 was created. Current flow:
  receive [PolicyInInterceptor, LoggingInInterceptor, AttachmentInInterceptor]
  post-stream [StaxInInterceptor]
  read [WSDLGetInterceptor, ReadHeadersInterceptor, SoapActionInInterceptor, StartBodyInterceptor]
  pre-protocol [MAPCodec, MustUnderstandInterceptor]
  user-protocol [SoapResponseInInterceptor]
  post-protocol [CheckFaultInterceptor, JAXBAttachmentSchemaValidationHack]
  unmarshal [DocLiteralInInterceptor, SoapHeaderInterceptor]
  pre-logical [MAPAggregatorImpl]
  post-logical [WrapperClassInInterceptor]
  pre-invoke [SwAInInterceptor, HolderInInterceptor]

There is probably some way to configure the LoggingInInterceptor - under WEB-INF\classes, there are webservices.xml files for PD, QD and RD.   However, the only interceptor that is registered for retrieve documents is:
            <ref bean="securityConfigInInterceptor" />

Any suggestions?  Does anyone know how the interceptors are configured/registered?  It does not look like I am finding all configuration settings, as there are many more interceptors according to the logging above.