title: Mysterious error in SOAP when JAX-WS receives the response
body: <p>I receive the following error when I'm trying to send a SOAP message. 
  The thing that has me confused, is that it seems like </p>
  
  <ul>
  <li>Something fails in the C layer, the message <em>"Object reference not set to an instance of an object."</em> is a typical .net message if I recall.</li>
  <li>It happens deep in the SOAP handler.</li>
  <li>It happens when it receives the response.</li>
  <li>It looks to me that it actually fails, trying to create an error message.</li>
  </ul>
  
  <p>I'm using Glassfish 3.1.2.2, with its default SOAP framework (JAX-WS if I recall)</p>
  
  <p>Any pointers on how to trace this error, and possibly get the actual received SOAP response, to see if it is the one to blame?</p>
  
  <p>I have to add that I'm NOT a SOAP expert by any means of the definition. I just have to figure our why this fails. Unfortunately.</p>
  
  <p>Stack trace:</p>
  
  <pre><code>com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Object reference not set to an instance of an object. Please see the server log to find more detail regarding exact cuase of the failure.
      at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:193)
      at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:134)
      at com.sun.xml.ws.client.sei.StubHandler.readResponse(StubHandler.java:247)
      at com.sun.xml.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:177)
      at com.sun.xml.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:256)
      at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:128)
      at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:102)
      at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:151)
  </code></pre>