Skip to content
This repository has been archived by the owner on Jan 10, 2019. It is now read-only.

Job won't get picked up on the first submit but on the second. #28

Open
wpoosanguansit opened this issue Feb 21, 2013 · 1 comment
Open

Comments

@wpoosanguansit
Copy link

Hi,

I am not sure if there is any other settings that dictate the behavior of the job queue being picked up. The queue picks up jobs for processing after the second submit, every time. I am not sure if this is relevant. From the document, job will use put function but in the example code publish is used. However, I tried both and they behave the same way.

Firs time:

info: (Job module) Add process id 638f7617-c544-45dd-8b25-040f70af06aa to Queue system

If I submit again:

info: (Job module) Add process id 07718909-53a0-4de9-bc87-f92550f0b078 to Queue system
Job get 07718909-53a0-4de9-bc87-f92550f0b078
process item 512690b85095ae9754000007
info: (Job module) done

Any help is appreciated.

@wpoosanguansit
Copy link
Author

Hi,

Just like to add that this behavior happens when I point the db connection to the remote host. When I install redis locally to debug, things seem to work fine again. Any help in pointing to how to debug this issue is appreciated.

Thanks for your help.

Watt Poosanguansit

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

No branches or pull requests

1 participant