Re: [akka-user] Critical bug: akka 2.1-M1 SILENTLY fails on object unmarshalling when type is not available in classpath

[√iktor Ҡlang]

Hi,

Set "akka.remote.log-remote-lifecycle-events" to "on" in your config.

These outputs were suppressed because people didn't want to get drowned in remote logging.

I will clarify the description that property and add this to the FAQ.

Cheers,

√

On Fri, Aug 17, 2012 at 8:33 AM, wolfy <pshi...@gmail.com> wrote:

I've wasted two days before I've found one mysterious problem.

Let we have two independent applications using akka-remote.
One on them has some private enum, containing private field (it's important!).  And this application send instance of enum mentioned to another one.

Another application tries to unmarshal message and akka SILENTLY fails. So, programmer are in doubt: no log messages, no exceptions, not any visible problem, but target application doesn't receive anything.

This problem doesn't occure when type of passed instance is available in classpath of the second app, OR then it's enum which doesn't contain any fields.

Please find full demo attached (full sources, buildable by maven).

To reproduce the problem you should compile application, then run DummyServerBad, then run DummyClient. You will not see anything in stdout/stderr of DummyServerBad, and will see timeout exception in stdout of DummyClient.

Then try to do the same with DummyServerGood (same code, but located in classpath of DummyClient). In this case message will be received by server and client will receive answer.

I think that Akka MUST do some verbose logging on ANY unmarshalling fail, current behavior is the way to the hell of very-hard-to-debug errors.

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://akka.io/faq/
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user?hl=en.
 
 

--
Viktor Klang

Akka Tech Lead

Typesafe - The software stack for applications that scale

Twitter: @viktorklang

[wolfy]

Thank you very much for you help, this option made everything clear.

But I think that such option MUST be turned on by default or described in the first lines of the akka-remoting docs.

It's very easy to produce situation like this and it's very hard to debug such issues.

[√iktor Ҡlang]

On Fri, Aug 17, 2012 at 10:14 AM, wolfy <pshi...@gmail.com> wrote:

Thank you very much for you help, this option made everything clear.

But I think that such option MUST be turned on by default or described in the first lines of the akka-remoting docs.

It's very easy to produce situation like this and it's very hard to debug such issues.

You're right, this thing is new for 2.1-M1, Roland is on the case.

Cheers,

√

[√iktor Ҡlang]

On Wed, Sep 26, 2012 at 10:50 AM, Johan Nystrom <jtny...@gmail.com> wrote:

+1. 

I am just starting out with Akka and remoting and I think I was bitten by this. It seems that NotSerializableExceptions were not showing up until I turned on this flag, and as a result messages were silently dropped.

It wasn't fixed in M2?

[√iktor Ҡlang]

So we're cool?

On Fri, Sep 28, 2012 at 5:03 AM, Johan Nystrom <jtny...@gmail.com> wrote:

Actually, please disregard the comment I just posted, I was using M1, not M2. Thanks.

Johan

[√iktor Ҡlang]

On Mon, Oct 1, 2012 at 2:52 AM, Johan Nystrom <jtny...@gmail.com> wrote:

It seems so. I don't have these problems with M2. Sorry to raise a false alarm.

Np. Happy hAkking!