[JBossWS] - Suppressing SoapFault Stack trace
by zurchman
It looks like this code in SOAPFaultExceptionHandler (1.0.4.GA) will always log an ugly stack trace for Exceptions thrown by the Endpoint.
Is there some way to supress the stack trace?
In many cases, the Exception is expected, and all we're really interested in logging at the Endpoint is the fault message.
| /** Translate the request exception into a SOAPFault message.
| */
| public static SOAPMessage exceptionToFaultMessage(Exception reqEx)
| {
| // Get or create the SOAPFaultException
| SOAPFaultException faultEx;
| if (reqEx instanceof SOAPFaultException)
| {
| faultEx = (SOAPFaultException)reqEx;
| }
| else
| {
| QName faultCode = Constants.SOAP11_FAULT_CODE_CLIENT;
| String faultString = (reqEx.getMessage() != null ? reqEx.getMessage() : reqEx.toString());
| faultEx = new SOAPFaultException(faultCode, faultString, null, null);
| faultEx.initCause(reqEx);
| }
|
| Throwable faultCause = faultEx.getCause();
| log.error("SOAP request exception", faultCause != null ? faultCause : faultEx);
|
| ...
| }
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993187#3993187
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993187
17 years, 9 months
[JBossWS] - Re: Issue with .NET ws clients
by maeste
"heiko.braun(a)jboss.com" wrote : Looking at it more carefully doesn't reveal anything at JBossWS processing level. That piece of code prepares the SOAPMessageContext upon receiving the HTTPRequest InputStream.
|
Yes, it seems the HTTPRequest InputStream is already closed when jbossws try to use it. One more thing to clarify the situation: it happens with unpredictable frequency...it seems a problem with server overload or concurrency (just a smell of them, I'm not sure, but a lot of tests in test environment can't reproduce error)
"heiko.braun(a)jboss.com" wrote :
| My 2 cents:
| In this case i'd say that the servlet engine probably has written something back to .NET client without notice.
|
and closes the connection.
"heiko.braun(a)jboss.com" wrote :
| Do you have any HTTP logs available at the client side?
|
No of course.........it's a .NET client :)
"heiko.braun(a)jboss.com" wrote :
| A look at the jboss-tomcat logs might help as well.
Some classes suspected? We can't enable all jboss-tomcat logs in production environment processing many requests per second.
A little OT: please take a look to my last post in Design Forum ;)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993094#3993094
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993094
17 years, 9 months
[JBossWS] - Re: NullPointerException in WSDL11Reader
by NicoSchl
Hi Thomas,
This occurred with jbossws 1.0.0.GA shipped with JBoss 4.0.4.GA.
I have also tried upgrading to jbossws 1.0.4 GA, but the exception is still there.
| java.lang.NullPointerException
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processOperationInput(WSDL11Reader.java:487)
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processPortTypeOperations(WSDL11Reader.java:473)
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processPortType(WSDL11Reader.java:459)
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processBinding(WSDL11Reader.java:741)
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processPort(WSDL11Reader.java:1110)
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processPorts(WSDL11Reader.java:1093)
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processServices(WSDL11Reader.java:1066)
| at org.jboss.ws.metadata.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:128)
| at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:145)
| at org.jboss.ws.metadata.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:263)
| at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:90)
| at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:85)
| at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
| at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy42.create(Unknown Source)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
| at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
|
Nico
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993070#3993070
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993070
17 years, 9 months