-
Notifications
You must be signed in to change notification settings - Fork 6
DefaultRPCSender - Possible race condition between sending and registering the listener #41
Comments
Can you do me a favor and take a look at the code in the messageoverhaul branch? I've got a complete rework of jWAMP underway that resolves a lot of these sorts of issues. Thanks,
|
Will do. Must be a drop down for branch selection here somewhere .... :-) Chuck Marcotte On Monday, August 4, 2014 12:59 PM, trumpetinc notifications@github.com wrote:
|
On the home page, just above the last commit label on the left, there is a green button next to it. Thks for your interest in JWamp. |
FYI. The Call ERROR json parser does not match the spec and a parsing error is occurring. Note, the spec says that the 4th argument is a dictionary, but the examples show a list of strings. Call ERROR On , Charles Marcotte chuckmarcotte@yahoo.com wrote:
|
Hmm... The Promise class needs the get() method to check to see if the value has already been set BEFORE calling wait(). I sometimes see an RPC call that waits forever because the response comes back faster than the client thread can call enter get() and call wait(). ghetolay/jwamp Chuck Marcotte On Monday, August 4, 2014 2:38 PM, ghetolay notifications@github.com wrote:
|
Chuck - I have created a separate Issue for the Promise race condition you identified ( #42 ). I have it fixed and will push that in a second. Can you please do me a favor and open a new Issue for the ERROR call parameters? |
In the class DefaultRPCSender, in method call():
public String call(String procId, ResultListener listener, long timeout, Object... args)
the line for:
Is invoked before the listener is registered
The text was updated successfully, but these errors were encountered: