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

Akitoshi Yoshida resolved CXF-6250.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.1.0

> WebSocket conduit fails to process String based responses and throws NPE
> ------------------------------------------------------------------------
>
>                 Key: CXF-6250
>                 URL: https://issues.apache.org/jira/browse/CXF-6250
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.0.3
>            Reporter: Akitoshi Yoshida
>            Assignee: Akitoshi Yoshida
>             Fix For: 3.0.4, 3.1.0
>
>
> When the response message is typed as String, the response message is not 
> correctly processed and this symptom is shown in the following exception.
> 2015-02-10 17:24:11,808 | ERROR | w I/O worker #18 | AhcWebSocketConduit      
>         | 146 - org.apache.cxf.cxf-rt-transports-websocket - 3.1.0.SNAPSHOT | 
> [ws] onError
> java.lang.NullPointerException
>       at 
> java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:333)[:1.7.0_75]
>       at 
> java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:988)[:1.7.0_75]
>       at 
> org.apache.cxf.transport.websocket.ahc.AhcWebSocketConduit$AhcWebSocketListener.onMessage(AhcWebSocketConduit.java:353)[146:org.apache.cxf.cxf-rt-transports-websocket:3.1.0.SNAPSHOT]
>       at 
> com.ning.http.client.providers.netty.NettyWebSocket.onTextFragment(NettyWebSocket.java:202)[147:com.ning.async-http-client:1.8.5]
>       at 
> com.ning.http.client.providers.netty.NettyAsyncHttpProvider$WebSocketProtocol.handle(NettyAsyncHttpProvider.java:2380)[147:com.ning.async-http-client:1.8.5]
>       at 
> com.ning.http.client.providers.netty.NettyAsyncHttpProvider.messageReceived(NettyAsyncHttpProvider.java:1
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to