Facing rabbitmq connectivity issue from Jboss server. #3830
Replies: 3 comments
-
Below is the Error from server log: |
Beta Was this translation helpful? Give feedback.
-
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
The trace only says there was a null (JNDI resource?) pointer from a Qpid client. We don't have much else to work with. This seems to be a client configuration issue. We don't use Qpid client in any of the tests. If it implements AMQP 1.0, that plugin must be enabled. For AMQP 0-9-1 or RabbitMQ streams, there are clients provided by our team. RabbitMQ logs all connection events as long as there is at least one byte sent on the connection. There are also guides that |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Thank you for using RabbitMQ.
STOP NOW AND READ THIS BEFORE OPENING A NEW ISSUE ON GITHUB
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
have a specific, actionable suggestion for our team, you must first ask
your question or discuss your suspected issue on the mailing list:
https://groups.google.com/forum/#!forum/rabbitmq-users
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
cause analysis and so on.
Please take the time to read the CONTRIBUTING.md document for instructions on
how to effectively ask a question or report a suspected issue:
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
Following these rules will save time for both you and RabbitMQ's maintainers.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions