cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CXF-3170) NullPointerException in StaxUtils.java:961
Date Fri, 21 Jan 2011 17:35:43 GMT

     [ https://issues.apache.org/jira/browse/CXF-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp updated CXF-3170:
-----------------------------

    Fix Version/s: NeedMoreInfo

> NullPointerException in StaxUtils.java:961
> ------------------------------------------
>
>                 Key: CXF-3170
>                 URL: https://issues.apache.org/jira/browse/CXF-3170
>             Project: CXF
>          Issue Type: Improvement
>    Affects Versions: 2.3.1
>         Environment: Java version: 1.6.0_21
> Java home: C:\Program Files\Java\jdk1.6.0_21\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
>            Reporter: Gary Gregory
>             Fix For: NeedMoreInfo
>
>
> We get the following NPE:
> {noformat}
> java.lang.NullPointerException
> 	at org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:961)
> 	at org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:949)
> 	at org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:185)
> 	at org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInInterceptor.java:73)
> 	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:247)
> 	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
> 	at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:97)
> 	at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:458)
> 	at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:146)
> 	at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:148)
> 	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179)
> 	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:108)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
> 	at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159)
> 	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:527)
> 	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:423)
> 	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:930)
> 	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:358)
> 	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:866)
> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
> 	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245)
> 	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
> 	at org.eclipse.jetty.server.Server.handle(Server.java:351)
> 	at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:594)
> 	at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1042)
> 	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:549)
> 	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:211)
> 	at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:424)
> 	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:506)
> 	at org.eclipse.jetty.util.thread.OldQueuedThreadPool$PoolThread.run(OldQueuedThreadPool.java:524)
> {noformat}
> This is due to the way we configure Jetty and CXF in a jetty.xml file, so it our fault
so to speak.
> BUT, it would be nice to either get: a civilized error message or some default fall through
behavior (that does not blow up in an NPE)
> But still

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message