cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (Commented) (JIRA)" <>
Subject [jira] [Commented] (CXF-4023) invalid ProtocolVariant causes NullPointerException in RMSoapInterceptor
Date Thu, 16 Feb 2012 20:06:59 GMT


Aki Yoshida commented on CXF-4023:

Hi Michael,

We will be fixing the code so that no NPE will be thrown under this condition.
But we would like to know if there is a combination of namespace usage which you expect CXF
to support. 

We don't think that it makes sense to support an arbitrary combination. However, if some existing
implementation generates a message having a particular combination that is not currently supported
by CXF, we will consider supporting that combination.

Let us know.

Regards, Aki
> invalid ProtocolVariant causes NullPointerException in RMSoapInterceptor
> ------------------------------------------------------------------------
>                 Key: CXF-4023
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.5.1
>         Environment: Windows XP
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing)
>            Reporter: Michael Heß
> If a WS-RM request contains a mixture of Protocol Variants (for WS-A and WS-RM) that
is unknown to, the following NPE is raised. 
> Interceptor for {}ReloadAccountService#{}ReloadAccount
has thrown exception, unwinding now
> java.lang.NullPointerException
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
> 	at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(
> 	at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(
> 	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
> 	at org.eclipse.jetty.server.handler.ContextHandler.doScope(
> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(
> 	at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
> 	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
> 	at org.eclipse.jetty.server.Server.handle(
> 	at org.eclipse.jetty.server.HttpConnection.handleRequest(
> 	at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(
> 	at org.eclipse.jetty.http.HttpParser.parseNext(
> 	at org.eclipse.jetty.http.HttpParser.parseAvailable(
> 	at org.eclipse.jetty.server.AsyncHttpConnection.handle(
> 	at
> 	at$
> 	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
> 	at org.eclipse.jetty.util.thread.QueuedThreadPool$
> 	at
> This can probably be handled more gracefully?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message