-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NullPointerException #723
Comments
That implies the underlying rabbit connection returned no channel, which should not be possible. Please show your configuration. the code that exhibits this behavior, together with version information for all libraries. |
Not clear, what you show to us, @jayzch . Indeed, Framework should not throw NPE, but you see your comment is not readable and we can't understand that stack trace properly. If you could format it the standard console output way, that would be helpful. Anyway +1 for some code to reproduce. Otherwise neither we can help you, nor you for us to fix the problem if it is there. Thank you for understanding. |
This problem occurs when the number of RabbitMQ Server channels exceeds the limit maxChannel |
OK! Let it be. But how to reproduce, please? |
It's a bit odd that the client returns null in this case rather than throwing an exception. I think the assertion should be made regardless of whether a transaction is being used. |
It is odd, indeed, but clear in the javadocs...
|
Fixes spring-projects#723 To avoid an `NPE` when connection returns `null` for the `createChannel()` in case of `channelMax` is reached, throw newly introduced `AmqpResourceNotAvailableException`. This exception can be used in the `RetryPolicy` to retry the original operation after some back-off - the channel permit may be released in between **Cherry-pick to 2.0.x and 1.7.x**
* GH-723: Add AmqpResourceNotAvailableException Fixes #723 To avoid an `NPE` when connection returns `null` for the `createChannel()` in case of `channelMax` is reached, throw newly introduced `AmqpResourceNotAvailableException`. This exception can be used in the `RetryPolicy` to retry the original operation after some back-off - the channel permit may be released in between **Cherry-pick to 2.0.x and 1.7.x** * * Fix `AbstractConnectionFactoryTests` for proper mock * Fix `amqp.adoc` according PR comments
* GH-723: Add AmqpResourceNotAvailableException Fixes #723 To avoid an `NPE` when connection returns `null` for the `createChannel()` in case of `channelMax` is reached, throw newly introduced `AmqpResourceNotAvailableException`. This exception can be used in the `RetryPolicy` to retry the original operation after some back-off - the channel permit may be released in between **Cherry-pick to 2.0.x and 1.7.x** * * Fix `AbstractConnectionFactoryTests` for proper mock * Fix `amqp.adoc` according PR comments
* GH-723: Add AmqpResourceNotAvailableException Fixes #723 To avoid an `NPE` when connection returns `null` for the `createChannel()` in case of `channelMax` is reached, throw newly introduced `AmqpResourceNotAvailableException`. This exception can be used in the `RetryPolicy` to retry the original operation after some back-off - the channel permit may be released in between **Cherry-pick to 2.0.x and 1.7.x** * * Fix `AbstractConnectionFactoryTests` for proper mock * Fix `amqp.adoc` according PR comments
The text was updated successfully, but these errors were encountered: