Closed wxbty closed 12 months ago
After I use the command "docker-compose -p docker-apisix restart" to restart, the following error occurs:
error log:
This is also very similar to #3725
Refer to the hello
function here https://github.com/apache/apisix/tree/master/t/lib/dubbo-backend to implement sayHello
.
I think your sayHello
is not fully implemented.
Added several other methods, it seems that there is no difference. The problem now is 502:
error_log: 2022/11/24 03:47:14 [error] 48#48: 9611 multi: connect failed 0000FFFFA0828D20 2022/11/24 03:47:14 [warn] 48#48: 9611 multi: multi connection detach not empty 0000FFFFA0828D20
Added several other methods, it seems that there is no difference. The problem now is 502:
I noticed you are using M1 mac, I don't have a corresponding machine to reproduce it.
I suggest you perform the same operation on an amd64 machine to determine if the problem is on a different platform or on your operation.
@tzssangglass I reproduced this problem on a centos7 server, the steps are as issue #8382. In addition, the issue of #https://github.com/apache/apisix-docker/issues/373 should be caused by the wrong configuration of m1, It has been solved now. The current 502 problem can be reproduced on different platforms. I can't understand the error msg of “multi connection detach not empty”, and even I can't find it in the source code
I can't understand the error msg of “multi connection detach not empty”, and even I can't find it in the source code
Can you display the error logs as text instead of images?
and even I can't find it in the source code
if (!ngx_queue_empty(&multi_c->data)) {
ngx_log_error(NGX_LOG_WARN, c->log,
0, "multi: multi connection detach not empty %p", c);
}
The problem now is 502
the steps are as issue #8382.
You need to close this issue and open a new issue to describe the new 502 problems and giving full details of the steps to reproduce it.
Cross-referencing issues and describing new problems in old issues confuse me.
@tzssangglass Put it on hold for now, I'll bring it up next time
This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions.
Description
I encountered the same error as issue #3725, but I used the dubbo provider exported by java, and the consumer can call it normally.
error:
curl http://127.0.0.1:9080/demo -H "Host: 127.0.0.1" -X POST --data '{"name": "hello"}'
error log:
route cmd:
curl http://127.0.0.1:9180/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
java provider:
generated nginx.conf not exist var dubbo_service_name:
Environment
apisix version
): 3.0.0uname -a
): mac m1openresty -V
ornginx -V
): openresty/1.21.4.1;built by gcc 10.2.1 20210110 (Debian 10.2.1-6);built with OpenSSL 1.1.1n 15 Mar 2022curl http://127.0.0.1:9090/v1/server_info
):luarocks --version
):