网络传输扩展-connect方法未生效
- Dominant language
- CSS
- Stars
- 491
- Forks
- 809
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 6
Description
使用自定义的扩展,connect方法仍然执行的是NettyTransporter中的connect。
dubbo版本:3.2.10
在META-INF/dubbo/org.apache.dubbo.remoting.Transporter配置了自定义扩展信息
在配置文件中配置了dubbo.protocol.transporter的值为custom
代码如下:
```
public class CustomTransporter implements Transporter {
public static final String NAME = "custom";
@Override
public RemotingServer bind(URL url, ChannelHandler handler) throws RemotingException {
System.out.println("CustomTransporter:server "+url);
RemotingServer server = new NettyServer(url, handler);
return server;
}
@Override
public Client connect(URL url, ChannelHandler handler) throws RemotingException {
System.out.println("CustomTransporter:client "+url);
Client client = new NettyClient(url, handler);
return client;
}
}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the report with Dubbo 3.2.10, the META-INF/dubbo/org.apache.dubbo.remoting.Transporter registration, and dubbo.protocol.transporter=custom. Trace Transporter.connect resolution against the shown CustomTransporter and NettyTransporter implementations; the issue is done when the configured custom connect method is invoked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100