[erlang-questions] Jinterface receiveRPC bug?

[Damian Dobroczyński]

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
<mailto: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
<mailto:node102@REDACTED>']}'

... sendRPC/receiveRPC
[java] erlang Jinterface says: I got:
'{'$gen_call',{#Pid<node106@REDACTED>,#Ref<node106@REDACTED>},{is_auth,'node106@REDACTED
<mailto: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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120907/a876584f/attachment.htm>