Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: JiBX/WS 0.9
-
Component/s: JiBX/WS
-
Labels:None
-
Testcase included:yes
-
Number of attachments :
Description
Seismic example fails when run with "ant run-xbis" and "ant run-pox-xbis".
Server side error is:
java.lang.IllegalArgumentException: Unknown node type 1
[java] org.xbis.JibxReader.nextToken(JibxReader.java:609)
[java] org.xbis.JibxReader.next(JibxReader.java:158)
[java] org.jibx.runtime.impl.UnmarshallingContext.toStart(UnmarshallingContext.java:451)
[java] org.jibx.ws.io.PayloadUnmarshaller.invoke(PayloadUnmarshaller.java:117)
[java] org.jibx.ws.context.InContext.internalInvokeInHandlers(InContext.java:125)
[java] org.jibx.ws.context.InContext.invokeInHandlers(InContext.java:87)
[java] org.jibx.ws.pox.PoxProcessor.receiveMessage(PoxProcessor.java:140)
[java] org.jibx.ws.server.Service.processRequest(Service.java:206)
[java] org.jibx.ws.server.http.WsServletDelegate.doPost(WsServletDelegate.java:147)
[java] org.jibx.ws.server.http.WsServlet.doPost(WsServlet.java:76)
[java] javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
[java] javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
When run with SOAP, this error is wrapped in a SOAP Fault. The client also receives a similar error since it cannot unmarshal the SOAP Fault.
On subsequent requests, different exceptions are returned. The exception shown above is always returned on the first request after restarting Tomcat.
It's best to try this with the latest code to pick up the exception handling changes.
XBIS over TCP works fine.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] | |
| Fix Version/s | JiBX/WS 0.9 [ 15270 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Fixed the code so that the XBIS reader and writer will be reset for each operation when using HTTP, while still keeping state as long as the connection is held for TCP.