quality@glassfish.java.net

WS error on GF 2.1.1

From: Wouter van Reeven <wouter_at_van.reeven.nl>
Date: Tue, 15 Feb 2011 14:45:47 +0100

Hi all,


Would someone of the GlassFish team be able to help me please? We are
running Sun GlassFish Enterprise Server v2.1.1 ((v2.1 Patch06)(9.1_02
Patch12)) (build b31g-fcs) and have several Web Services running on it
for two months now. Yesterday and today we had one service failing
occasionally with the stacktrace

          <ns2:cause class="java.lang.NullPointerException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
            <ns2:stackTrace>
              <ns2:frame class="com.sun.xml.stream.buffer.AbstractProcessor" file="AbstractProcessor.java" line="177" method="readFromNextStructure"/>
              <ns2:frame class="com.sun.xml.stream.buffer.AbstractProcessor" file="AbstractProcessor.java" line="163" method="readStructure"/>
              <ns2:frame class="com.sun.xml.stream.buffer.AbstractProcessor" file="AbstractProcessor.java" line="167" method="readEiiState"/>
              <ns2:frame class="com.sun.xml.stream.buffer.stax.StreamReaderBufferProcessor" file="StreamReaderBufferProcessor.java" line="213" method="next"/>
              <ns2:frame class="com.sun.xml.ws.streaming.XMLStreamReaderUtil" file="XMLStreamReaderUtil.java" line="67" method="readRest"/>
              <ns2:frame class="com.sun.xml.ws.message.stream.StreamMessage" file="StreamMessage.java" line="371" method="writePayloadTo"/>
              <ns2:frame class="com.sun.xml.ws.message.stream.StreamMessage" file="StreamMessage.java" line="459" method="writeTo"/>
              <ns2:frame class="com.sun.xml.ws.message.AbstractMessageImpl" file="AbstractMessageImpl.java" line="193" method="readAsSOAPMessage"/>
              <ns2:frame class="com.sun.xml.ws.handler.SOAPMessageContextImpl" file="SOAPMessageContextImpl.java" line="79" method="getMessage"/>

I have investigated the incoming XML but cannot find anything wrong with
it. The payload is similar to other XML messages that get through just
fine. No weird characters or strange encoding or whatsoever.

When I take the incoming message and use it to call the failing web
service using soapUI, the message gets handled correctly! I *guess*
something must be wrong with the original XML message but I am not able
to find anything.

Does anyone have any experience with this and know how to solve it?


Thanks, Wouter

-- 
Blackholes are where God is dividing by zero.
[Unknown Source]
Skype: wvreeven
Facebook: wvreeven
Twitter: wvreeven