[erlang-questions] Jinterface receiveRPC bug?

[David Welton]

Hi,

Did you ever figure this out?  We're observing some similar behavior
that's a bit odd.  I'm not the one following the Java code, so I will
have to ask for some details, but our Java guy is complaining about
getting null back as well.

It's likely to have something to do with having both receiveRPC and
other code that also does a receive... at least that's my intuition.

Any guidance on this?

On Fri, Sep 7, 2012 at 12:33 PM, Damian Dobroczyński <qoocku@REDACTED> wrote:
> Hi list!
>
> We've found irritating problem with jinterface (R15B01): from time to time
> "receiveRPC()" method returns "null" instead of
> sensible value. After short digging we've found such scenario:
>
> ... sendRPC/receiveRPC
> [java] erlang Jinterface says: I got: '{rex,['node102@REDACTED']}'
>
> ... sendRPC/receiveRPC
> [java] erlang Jinterface says: I got: '{rex,{jpg,#Bin<32162>}}'
>
> ... sendRPC/receiveRPC
> [java] erlang Jinterface says: I got: '{rex,['node102@REDACTED']}'
>
> ... sendRPC/receiveRPC
> [java] erlang Jinterface says: I got:
> '{'$gen_call',{#Pid<node106@REDACTED>,#Ref<node106@REDACTED>},{is_auth,'node106@REDACTED'}}'
>
> ...
>
> (we've changed "receiveRPC" method to produce log entries)
>
> "{rex, ...} messages are OK. The last one is suprising. Is it proper
> behavior? I mean, does a Java node receive occasionally "is_auth" messages
> (I think they are related somehow to net_kernel module) ? "node6" IS the
> node we're connected to.
>
> -- D.
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>



-- 
David N. Welton

http://www.welton.it/davidw/

http://www.dedasys.com/