Closed running-g closed 4 years ago
The plugin tried to fetch some socket information and the returned value was einval
, meaning the socket was "invalid" (most likely already closed) in the middle of a login operation.
FTR, here is the line in question which does not handle such scenarios. I'm not really sure how it should since if the socket is already closed or otherwise cannot be used, the connection cannot send any meaningful information to the client. It could avoid the exception but I struggle to come up with an error message that would be actually useful.
thks
I have an error in rabbitmq
OS:Windows Server 2019 RabbitMQ version:3.7.23 Erlang version 22.0 RabbitMQ server and client application log
rabbitmq-plugins list: [ ] rabbitmq_amqp1_0 3.7.23 [E] rabbitmq_auth_backend_cache 3.7.23 [E] rabbitmq_auth_backend_http 3.7.23 [ ] rabbitmq_auth_backend_ldap 3.7.23 [ ] rabbitmq_auth_mechanism_ssl 3.7.23 [ ] rabbitmq_consistent_hash_exchange 3.7.23 [E] rabbitmq_event_exchange 3.7.23 [ ] rabbitmq_federation 3.7.23 [ ] rabbitmq_federation_management 3.7.23 [ ] rabbitmq_jms_topic_exchange 3.7.23 [E] rabbitmq_management 3.7.23 [e] rabbitmq_management_agent 3.7.23 [E] rabbitmq_mqtt 3.7.23 [ ] rabbitmq_peer_discovery_aws 3.7.23 [ ] rabbitmq_peer_discovery_common 3.7.23 [ ] rabbitmq_peer_discovery_consul 3.7.23 [ ] rabbitmq_peer_discovery_etcd 3.7.23 [ ] rabbitmq_peer_discovery_k8s 3.7.23 [ ] rabbitmq_random_exchange 3.7.23 [ ] rabbitmq_recent_history_exchange 3.7.23 [ ] rabbitmq_sharding 3.7.23 [ ] rabbitmq_shovel 3.7.23 [ ] rabbitmq_shovel_management 3.7.23 [ ] rabbitmq_stomp 3.7.23 [ ] rabbitmq_top 3.7.23 [ ] rabbitmq_tracing 3.7.23 [ ] rabbitmq_trust_store 3.7.23 [e] rabbitmq_web_dispatch 3.7.23 [E] rabbitmq_web_mqtt 3.7.23 [ ] rabbitmq_web_mqtt_examples 3.7.23 [ ] rabbitmq_web_stomp 3.7.23 [ ] rabbitmq_web_stomp_examples 3.7.23
Client library: Java,C#,Node,more....