Skip to content
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

(Optinally) prevent execution abort when trying to send to non-existing topic #24

Closed
hhamalai opened this issue Aug 27, 2014 · 1 comment
Labels

Comments

@hhamalai
Copy link

Stompest client can try write to temporary topic, but the client listening that topic might already be disconnected. AMQ will response with an error. stompest.async.client will call onError handlers in method _onError, one of which disconnects the client.

@nikipore
Copy link
Owner

If you wish to override the default behavior of the handler of ERROR frames you could implement your own ErrorListener, cf. the documentation.

To that end, inject a custom listenersFactory when you create an async.Stomp instance. I would suggest that you subclass async.listener.ErrorListener and create a copy of async.listener.defaultListeners in which you replace the async.listener.ErrorListener class by your customized subclass.

You could just as well monkey patch async.listener.ErrorListener directly, but that's the dirty way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants