So I figured out what the problem was. I had http dump option enabled on my application server which was causing the LoggingInInterceptor to be invoked before the WSS4JInInterceptor. The logging interceptor was streaming in the file right at the beginning of the chain, so by the time it was done, the timestamp was expired. Glad that was just a configuration problem...
-- View this message in context: http://cxf.547215.n5.nabble.com/WSS4J-Timestamp-expiring-before-large-file-transfer-finishes-tp5717348p5717367.html Sent from the cxf-user mailing list archive at Nabble.com.
