SourceForge.net
2005-06-08 14:17:41 UTC
Bugs item #1028860, was opened at 2004-09-16 08:01
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1028860&group_id=54559
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: client
Group: v0.7.6.1
Submitted By: Bill (wmoore2242)
Initial Comment:
I have run into a situation where the client does not
receive a message. I do see the message is on the
queue using the Admin tool.
It also appears that once a message is missed that my
client will never get a message.
----------------------------------------------------------------------
Message:
Logged In: YES
user_id=557161
You don't state what connector you are using. If you're using the
http connector from behind a firewall, then the blocking receive()
won't be able to receive a notification that a message is available
for it.
This limitation has been fixed for the 0.7.7 release.
----------------------------------------------------------------------
Comment By: Bill (wmoore2242)
Date: 2004-09-17 04:45
Message:
Logged In: YES
user_id=1122604
After some trail and error, I found that if I used the receive
method with a timeout, that my app is now able to get all
messages. I would expect the receive with no arguments to
return immediately if there is a message already on the queue
when it is invoked, but this is not the case.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1028860&group_id=54559
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1028860&group_id=54559
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: client
Group: v0.7.6.1
Status: Closed
Resolution: Fixed
Priority: 5Resolution: Fixed
Submitted By: Bill (wmoore2242)
Assigned to: Tim Anderson (tanderson)
Summary: Client does not receive messageInitial Comment:
I have run into a situation where the client does not
receive a message. I do see the message is on the
queue using the Admin tool.
It also appears that once a message is missed that my
client will never get a message.
----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2005-06-09 00:17Message:
Logged In: YES
user_id=557161
You don't state what connector you are using. If you're using the
http connector from behind a firewall, then the blocking receive()
won't be able to receive a notification that a message is available
for it.
This limitation has been fixed for the 0.7.7 release.
----------------------------------------------------------------------
Comment By: Bill (wmoore2242)
Date: 2004-09-17 04:45
Message:
Logged In: YES
user_id=1122604
After some trail and error, I found that if I used the receive
method with a timeout, that my app is now able to get all
messages. I would expect the receive with no arguments to
return immediately if there is a message already on the queue
when it is invoked, but this is not the case.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=1028860&group_id=54559