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.

Sign up for GitHub

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

Jump to bottom

Channel::BasicConsumeMessage timeout not ms #13

Closed
noldus opened this issue Jun 19, 2012 · 4 comments
Closed

Channel::BasicConsumeMessage timeout not ms #13

noldus opened this issue Jun 19, 2012 · 4 comments
Assignees
@alanxz
Labels
Bug

Comments

@noldus
Copy link

noldus commented Jun 19, 2012

As described in the headerfile for the Channel class, the overloaded function 'BasicConsumeMessage' accepts a timeout parameter. The timeout must be specified in ms (milliseconds), but this turns out not to be correct. The value is treated as having the unit 'seconds', thus the actual timeout value calculated in 'BasicConsumeMessage' is factor 1000 times higher.
@alanxz
Copy link
Owner

alanxz commented Jun 19, 2012

What platform are you seeing this behavior on?

@ghost ghost assigned alanxz Jun 19, 2012
@noldus
Copy link
Author

noldus commented Jun 19, 2012

I forgot to mention that. I am running Windows 7 32-bit and building with Visual Studio 2010.

alanxz added a commit that referenced this issue Jun 22, 2012
@alanxz
Timeout should be in ms and not seconds
3cdf94d 
Fix for issue #13
@alanxz alanxz mentioned this issue Jun 22, 2012
Merged
@alanxz
Copy link
Owner

alanxz commented Jun 22, 2012

Ok, this should be fixed in #14.

@alanxz alanxz closed this as completed Jun 22, 2012
@noldus
Copy link
Author

noldus commented Jun 25, 2012

Thank you for the fast response and the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alanxz alanxz

Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alanxz @noldus