通过SOAPHandler启用日志记录时,mtom服务中的JAX-WS故障更改
问题描述:
我在独立服务器应用程序中发布了jax-ws服务。该服务使用MTOM接收文件通过SOAPHandler启用日志记录时,mtom服务中的JAX-WS故障更改
正如答案建议对这个问题:
Tracing XML request/responses with JAX-WS
我使用SOAP消息日志记录如下服务的处理程序:
public boolean handleMessage(SOAPMessageContext smc){
performLoggingActions(smc);
return true;
}
记录器方法如下:
private void performLoggingActions(SOAPMessageContext smc) {
ByteArrayOutputStream bout = null;
try {
Boolean isOutBound = (Boolean) smc.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);
SOAPMessage message = smc.getMessage();
//More stuff
} catch (Exception e) {
logger.error(String.format("Error in logSoapMessage! Error: %s ", e.getMessage()), e);
} finally {
IOUtils.closeQuietly(bout);
}
}
当客户端发送有效的请求时,记录中没有问题。一切都按预期记录。但是,如果通过SOAP UI在请求中发送了无效的内容标识,那么在SOAPMessage消息= smc.getMessage()中记录失败。我有以下错误:
Error in logSoapMessage! Error: No such MIME Part: Part=5
java.lang.IllegalStateException: No such MIME Part: Part=5
at com.sun.xml.internal.org.jvnet.mimepull.DataHead.read(DataHead.java:138)
at com.sun.xml.internal.org.jvnet.mimepull.MIMEPart.read(MIMEPart.java:85)
的问题是,当这种情况发生时,该消息不传播到服务水平和服务给客户端的响应与以下故障:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Server</faultcode>
<faultstring>unexpected XML tag. expected: somenamespace but found: {http://www.w3.org/2004/08/xop/include}Include</faultstring>
</S:Fault>
</S:Body>
</S:Envelope>
当我禁用肥皂日志记录并发送故障请求,消息会传播到服务级别,传播到@WebService批注的类,并且在尝试读取mtom内容时收到类似的期望。 然而,在这种情况下,该错误反映在响应的故障字符串:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
<faultcode>S:Server</faultcode>
<faultstring>No such MIME Part: Part=5</faultstring>
</S:Fault>
</S:Body>
</S:Envelope>
我希望同样的故障,无论记录处理程序的存在。如您所见,我正在捕获日志处理程序中的所有异常,但服务响应会根据日志处理程序的存在而发生变化。
我做错了什么?我的要求是有和没有日志处理程序相同的错误。
问候
编辑:错误的整个堆栈跟踪补充说:
Error in logSoapMessage! Error: No such MIME Part: Part=5
java.lang.IllegalStateException: No such MIME Part: Part=5
at com.sun.xml.internal.org.jvnet.mimepull.DataHead.read(DataHead.java:138)
at com.sun.xml.internal.org.jvnet.mimepull.MIMEPart.read(MIMEPart.java:85)
at com.sun.xml.internal.ws.encoding.MIMEPartStreamingDataHandler$StreamingDataSource.getInputStream(MIMEPartStreamingDataHandler.java:98)
at com.sun.xml.internal.org.jvnet.staxex.Base64Data.get(Base64Data.java:315)
at com.sun.xml.internal.org.jvnet.staxex.Base64Data.length(Base64Data.java:357)
at com.sun.xml.internal.ws.encoding.MtomCodec$MtomXMLStreamReaderEx.getTextCharacters(MtomCodec.java:533)
at com.sun.istack.internal.XMLStreamReaderToContentHandler.handleCharacters(XMLStreamReaderToContentHandler.java:244)
at com.sun.istack.internal.XMLStreamReaderToContentHandler.bridge(XMLStreamReaderToContentHandler.java:155)
at com.sun.xml.internal.ws.message.stream.StreamMessage.writePayloadTo(StreamMessage.java:375)
at com.sun.xml.internal.ws.message.stream.StreamMessage.writeTo(StreamMessage.java:460)
at com.sun.xml.internal.ws.message.AbstractMessageImpl.readAsSOAPMessage(AbstractMessageImpl.java:196)
at com.sun.xml.internal.ws.handler.SOAPMessageContextImpl.getMessage(SOAPMessageContextImpl.java:82)
at com.ibtech.smg.esb.jaxws.handler.JAXWSSOAPLoggingHandler.performLoggingActions(JAXWSSOAPLoggingHandler.java:54)
at com.ibtech.smg.esb.jaxws.handler.JAXWSSOAPLoggingHandler.handleMessage(JAXWSSOAPLoggingHandler.java:36)
at com.ibtech.smg.esb.jaxws.handler.JAXWSSOAPLoggingHandler.handleMessage(JAXWSSOAPLoggingHandler.java:1)
at com.sun.xml.internal.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:295)
at com.sun.xml.internal.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:138)
at com.sun.xml.internal.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:136)
at com.sun.xml.internal.ws.handler.HandlerTube.processRequest(HandlerTube.java:118)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:639)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:598)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:583)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:480)
at com.sun.xml.internal.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:312)
at com.sun.xml.internal.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:606)
at com.sun.xml.internal.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:257)
at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handleExchange(WSHttpHandler.java:108)
at com.sun.xml.internal.ws.transport.http.server.WSHttpHandler.handle(WSHttpHandler.java:93)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:90)
at sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:96)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:93)
at sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:690)
at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:90)
at sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:662)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:809)
答
能否请您粘贴到您的SOAP处理整个堆栈跟踪和代码?这行是否打印在您的日志中? logger.error(String.format("Error in logSoapMessage! Error: %s ", e.getMessage()), e);
我已经添加了整个堆栈跟踪。正如你可以看到你提到的那一行是打印的。行SOAPMessage message = smc.getMessage();发生异常。 – simpleusr
只需将'throw e'加入你的catch块并看看。这应该将原来的异常退回给客户端。 – Gautam
嗨,我已经认为该选项,但在javax.xml.ws.handler.Handler公共布尔handleMessage(C上下文)方法接口不允许抛出异常... –
simpleusr