search

yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
0 stars 0 forks source link

Netty issue: "Target not found" #36

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
If we try to address a particular client in the "send" method the server 
returns "target not found" - although the target is surely registered. Hints: A 
plug-In can obtain a reference to a certain connector by calling 
getConnector(<target-id>). The getConnector method is implemented in BaseServer 
and just wrapped for the plug-in. We suspect the Netty connectors do not return 
their ID properly, so that they can't be identified by the getConnector method. 
This can be tested e.g. with the RRPC call or simply by using the Web Client 
sendToken method.

Original issue reported on code.google.com by fivefeetfurther@gmail.com on 9 Aug 2010 at 2:28

GoogleCodeExporter commented 8 years ago 
i couldn't replicate this the getId method in BaseConnector uses getRemotePort 
method which is implemented in NettyConnector. 

But i am using the client id that is displayed on the top in the target 
field... i am assuming that's what you meant by the target.

Original comment by mailtopu...@gmail.com on 29 Aug 2010 at 7:40

GoogleCodeExporter commented 8 years ago 
hi alex can you put the exact step to reproduce it.. i couldn't reproduce it 
using rpc client or any.

Original comment by mailtopu...@gmail.com on 14 Oct 2010 at 1:33

GoogleCodeExporter commented 8 years ago

Original comment by fivefeetfurther@gmail.com on 14 Oct 2010 at 2:28

GoogleCodeExporter commented 8 years ago 
Seems to be automagically fixed, updated chat demo to check to send message to 
target only and it worked. Will have to be approved again in v0.11 rollout test.

Original comment by fivefeetfurther@gmail.com on 14 Oct 2010 at 4:29