cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <>
Subject [jira] [Created] (CXF-6250) WebSocket conduit fails to process String based responses and throws NPE
Date Tue, 10 Feb 2015 16:34:11 GMT
Akitoshi Yoshida created CXF-6250:

             Summary: WebSocket conduit fails to process String based responses and throws
                 Key: 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

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
	at java.util.concurrent.ConcurrentHashMap.hash([:1.7.0_75]
	at java.util.concurrent.ConcurrentHashMap.get([:1.7.0_75]
	at org.apache.cxf.transport.websocket.ahc.AhcWebSocketConduit$AhcWebSocketListener.onMessage([146:org.apache.cxf.cxf-rt-transports-websocket:3.1.0.SNAPSHOT]
	at com.ning.http.client.providers.netty.NettyWebSocket.onTextFragment([147:com.ning.async-http-client:1.8.5]
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider$WebSocketProtocol.handle([147:com.ning.async-http-client:1.8.5]
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.messageReceived(

This message was sent by Atlassian JIRA

View raw message