-
Notifications
You must be signed in to change notification settings - Fork 56
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
On ios getting connected and then error #27
Comments
I have the same problem. I reported it over a month ago but I didn't receive any solution. I see that the problem occurs when the queue has some arguments set for example: x-message-ttl, x-queue-mode, x-expires.... |
Do you have any solution? I have the same problem and my application does not work because There is some Bug. Is there author od this? Can you solve this issue? |
I am very busy at the moment, when i have time i wil check this problem. @mrozkosz What is youre problem exactly |
let connection = new Connection(config)
connection.connect()
let queue;
let exchange;
connection.on('connected', (event) => {
console.log("connected")
queue = new Queue(connection, {
name:
${userId}
,passive: false,
durable: true,
exclusive: false,
consumer_arguments: {'x-priority': 1}
},{"x-queue-mode" : "lazy"});
keys.forEach( key=> { queue.bind(exchange,
${key}
); })queue.on('message', (data) => {
This code is working on android but on ios its call giving connected first and then {"code": "5", "description": "Cannot use channel after it has been closed.", "name": "error", "type": "channel"}
The text was updated successfully, but these errors were encountered: