[
https://issues.apache.org/jira/browse/NIFI-14207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933966#comment-17933966
]
Marc Pellmann commented on NIFI-14207:
--------------------------------------
There are three Nullpointers in the JettyWebSocketSession, in the Methods
{code:java}
public InetSocketAddress getRemoteAddress()
public InetSocketAddress getLocalAddress()
public boolean isSecure() {code}
I assume there are changes in the Jetty 12 implementation.
session.getLocalSocketAddress() now gives null back sometimes and there is
Nullpointer Exception in the call to session.isSecure(). I testet it now with
the actual snapshot.
[~ijokarumawak] - are you still work on this component?
> Web Socket Connection does not work in 2.x
> ------------------------------------------
>
> Key: NIFI-14207
> URL: https://issues.apache.org/jira/browse/NIFI-14207
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Marc Pellmann
> Priority: Critical
> Attachments: Web+Sockets.json
>
>
> I have a simple Web Socket example where there is a ListenWebSocket processor
> with a JettyWebSocketServer service without SSL and on the same system a
> ConnectWebSocket processor with a JettyWebSocketClient accessing the server.
>
> Before 2.0, a run of the ConnectWebSocket resulted in a connect on the client
> side and the connected relation was also run on the ListenWebSocket.
>
> Now there is a connect on the client side and directly a disconnect and on
> the server side no relation is run at all and there is no error.
>
> I have attached the flow as JSON.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
