You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I access the file service's api document address (http://localhost:8000/file/v3/api-docs) through the gateway, I will find that success and failure alternate. If I directly use the file service's ip:port to access the document address (http://localhost:11002/v3/api-docs), there will be no error.
success:
fail:
file-service is a dubbo provider. If you remove all the provider's @ DubboServices, no error will be reported.
stacktrace:
2025-01-10 08:26:54.435 INFO 8000 --- [erverWorker-7-1] .r.p.t.h.AbstractServerTransportListener : [] [DUBBO] An error occurred while processing the http request with DefaultHttp11ServerTransportListener, Http1Request{method='GET', path='/v3/api-docs', contentType='null'}, dubbo version: 3.3.2, current host: 172.19.0.1
org.apache.dubbo.remoting.http12.exception.HttpStatusException: Invoker not found
at org.apache.dubbo.rpc.protocol.tri.h12.AbstractServerTransportListener.doRoute(AbstractServerTransportListener.java:128)
at org.apache.dubbo.rpc.protocol.tri.h12.AbstractServerTransportListener.onBeforeMetadata(AbstractServerTransportListener.java:122)
at org.apache.dubbo.rpc.protocol.tri.h12.AbstractServerTransportListener.onMetadata(AbstractServerTransportListener.java:89)
at org.apache.dubbo.rpc.protocol.tri.h12.AbstractServerTransportListener.onMetadata(AbstractServerTransportListener.java:54)
at org.apache.dubbo.remoting.http12.netty4.h1.NettyHttp1ConnectionHandler.channelRead0(NettyHttp1ConnectionHandler.java:56)
at org.apache.dubbo.remoting.http12.netty4.h1.NettyHttp1ConnectionHandler.channelRead0(NettyHttp1ConnectionHandler.java:29)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:93)
at org.apache.dubbo.remoting.http12.netty4.h1.NettyHttp1Codec.channelRead(NettyHttp1Codec.java:49)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
at io.
What you expected to happen
There is no exception when requesting /v3/api-docs
Anything else
I guess the problem is caused by the adaptation of triple protocol to spring, but I am not very familiar with triple protocol. I would like to ask the developer to help me troubleshoot it.
Are you willing to submit a pull request to fix on your own?
Yes I am willing to submit a pull request on my own!
Pre-check
Search before asking
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
dubbo version: 3.3.2
springboot: 3.2.5
jdk: 21
Steps to reproduce this issue
dependency:
spring-gateway:
application.yml:
openapi config:
v-file-service-impl:
application.yml
If I access the file service's api document address (http://localhost:8000/file/v3/api-docs) through the gateway, I will find that success and failure alternate. If I directly use the file service's ip:port to access the document address (http://localhost:11002/v3/api-docs), there will be no error.
success:
fail:
file-service is a dubbo provider. If you remove all the provider's @ DubboServices, no error will be reported.
stacktrace:
What you expected to happen
There is no exception when requesting /v3/api-docs
Anything else
I guess the problem is caused by the adaptation of triple protocol to spring, but I am not very familiar with triple protocol. I would like to ask the developer to help me troubleshoot it.
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: