Hello,

I have a simple Web application that implements EJB Web services. My application throws an IllegalArgumentException at runtime. This is an expected behaviour. The client (SOAPUI in this case) never sees a soap fault message from WebSphere. Further, upon inspecting log files I do not seem to find any indication of the exception. It is almost as if WebSphere did not bubble up the exception back to the client. Instead, it seems that WebSphere chewed up the exception never to be seen again.

How can I get WebSphere to report back the exception back to the client? I am using WebSphere 9.5.0.12

Any ideas or thougths are appreciated.

Hello,

I have a simple Web application that implements EJB Web services. My application throws an IllegalArgumentException at runtime. This is an expected behaviour. The client (SOAPUI in this case) never sees a soap fault message from WebSphere. Further, upon inspecting log files I do not seem to find any indication of the exception. It is almost as if WebSphere did not bubble up the exception back to the client. Instead, it seems that WebSphere chewed up the exception never to be seen again.

How can I get WebSphere to report back the exception back to the client? I am using WebSphere 9.5.0.12

Any ideas or thougths are appreciated.

Hi Octavio,

I'm assuming that you can see that your application is throwing the IllegalArgumentException on the WebSphere provider side and therefore it was actually invoked.  That would rule out any errors that might have occurred before the web services engine was invoked.

Set this trace spec to see you can find anything amiss in the trace.log file:

*=info:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.*=all

Hello,

I have a simple Web application that implements EJB Web services. My application throws an IllegalArgumentException at runtime. This is an expected behaviour. The client (SOAPUI in this case) never sees a soap fault message from WebSphere. Further, upon inspecting log files I do not seem to find any indication of the exception. It is almost as if WebSphere did not bubble up the exception back to the client. Instead, it seems that WebSphere chewed up the exception never to be seen again.

How can I get WebSphere to report back the exception back to the client? I am using WebSphere 9.5.0.12

Any ideas or thougths are appreciated.

Hi Barbara,

I set the trace spec as you suggested.  I can see both the Inbound and Outbound HTTP SOAP messages in the trace.log file. I also see System.out.println() statements that I put right before I throw the exception. So I am pretty confident the exception is taking place.However, I do not see any indications that the web services engine is processing any sort of exception. 
Is it possible that I need to configure/enable the engine to actually do something when the exception occurrs? 

Hi Octavio,

I'm assuming that you can see that your application is throwing the IllegalArgumentException on the WebSphere provider side and therefore it was actually invoked.  That would rule out any errors that might have occurred before the web services engine was invoked.

Set this trace spec to see you can find anything amiss in the trace.log file:

*=info:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.*=all

Hello,

I have a simple Web application that implements EJB Web services. My application throws an IllegalArgumentException at runtime. This is an expected behaviour. The client (SOAPUI in this case) never sees a soap fault message from WebSphere. Further, upon inspecting log files I do not seem to find any indication of the exception. It is almost as if WebSphere did not bubble up the exception back to the client. Instead, it seems that WebSphere chewed up the exception never to be seen again.

How can I get WebSphere to report back the exception back to the client? I am using WebSphere 9.5.0.12

Any ideas or thougths are appreciated.

Hi Octavio,

Does your Outtbound message have a SOAPFault in it, or something else?  An error in a web service is supposed to result in a SOAPFault.

Hi Barbara,

I set the trace spec as you suggested.  I can see both the Inbound and Outbound HTTP SOAP messages in the trace.log file. I also see System.out.println() statements that I put right before I throw the exception. So I am pretty confident the exception is taking place.However, I do not see any indications that the web services engine is processing any sort of exception. 
Is it possible that I need to configure/enable the engine to actually do something when the exception occurrs? 

Hi Octavio,

I'm assuming that you can see that your application is throwing the IllegalArgumentException on the WebSphere provider side and therefore it was actually invoked.  That would rule out any errors that might have occurred before the web services engine was invoked.

Set this trace spec to see you can find anything amiss in the trace.log file:

*=info:com.ibm.ws.webservices.*=all:org.apache.*=all:com.ibm.ws.websvcs.*=all:com.ibm.ws.metadata.*=all

Hello,

I have a simple Web application that implements EJB Web services. My application throws an IllegalArgumentException at runtime. This is an expected behaviour. The client (SOAPUI in this case) never sees a soap fault message from WebSphere. Further, upon inspecting log files I do not seem to find any indication of the exception. It is almost as if WebSphere did not bubble up the exception back to the client. Instead, it seems that WebSphere chewed up the exception never to be seen again.

How can I get WebSphere to report back the exception back to the client? I am using WebSphere 9.5.0.12

Any ideas or thougths are appreciated.

Hello,

I have a simple Web application that implements EJB Web services. My application throws an IllegalArgumentException at runtime. This is an expected behaviour. The client (SOAPUI in this case) never sees a soap fault message from WebSphere. Further, upon inspecting log files I do not seem to find any indication of the exception. It is almost as if WebSphere did not bubble up the exception back to the client. Instead, it seems that WebSphere chewed up the exception never to be seen again.

How can I get WebSphere to report back the exception back to the client? I am using WebSphere 9.5.0.12

Any ideas or thougths are appreciated.