[CXF-6250] WebSocket conduit fails to process String based responses and throws NPE

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.3
• Fix Version/s: 3.0.4, 3.1
• Component/s: Transports
• Estimated Complexity: Unknown
• Assignee: Akitoshi Yoshida
• Reporter: Akitoshi Yoshida
• Created: 10/Feb/15 16:33
• Updated: 16/Feb/15 16:09
• Resolved: 10/Feb/15 18:00

Description

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
...