Re: [akka-user] akka-sample-remote not working

1,008 views
Skip to first unread message

Rich Dougherty

unread,
Jan 14, 2013, 10:34:24 PM1/14/13
to akka...@googlegroups.com
Hi David

The sample apps in release-2.1 work OK for me. Are you sure you're not accidentally running against master? 

In the last 24 hours there have been reported issues of the sample apps not working in master:

Also, if I remember correctly, the new remote protocol wasn't released in 2.1.

Cheers
Rich


On Tue, Jan 15, 2013 at 12:08 PM, David Riley <che...@gmail.com> wrote:
Hi,

I am trying to run the sample project akka-sample-remote from release-2.1 but I get the following error:

[INFO] [01/14/2013 23:05:11.908] [run-main] [Remoting] Starting remoting
[error] (run-main) akka.remote.RemoteTransportException: No transport is loaded
for protocol: akka, available protocols: tcp.akka
akka.remote.RemoteTransportException: No transport is loaded for protocol: akka,
 available protocols: tcp.akka
        at akka.remote.Remoting$.localAddressForRemote(Remoting.scala:109)

Is this a known problem? 

I tried changing all references of akka with tcp.akka and the LookupApp works, but not the CreationApp, where there is a similar error.

Thanks

David

--
>>>>>>>>>> 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.
 
 

Akka Team

unread,
Jan 15, 2013, 2:55:45 AM1/15/13
to akka...@googlegroups.com
Hi David!

Looking at the log, you are running master and not 2.1 which is the
current stable version.

-Endre

√iktor Ҡlang

unread,
Jun 12, 2013, 10:41:44 AM6/12/13
to Akka User List
Hi Alberto,

have you gone through the migration guide?


Cheers,


On Wed, Jun 12, 2013 at 10:20 AM, Alberto Andreotti <albertoa...@gmail.com> wrote:
Hi guys,

I'm experiencing the same problem. Here's what I get,

[ERROR] [06/12/2013 14:12:29.774] [main] [RemoteActorRefProvider] Error while looking up address [akka://BE...@127.0.0.1:2552]
akka.remote.RemoteTransportException: No transport is loaded for protocol: [akka], available protocols: [akka.tcp]
        at akka.remote.Remoting$.localAddressForRemote(Remoting.scala:79)
        at akka.remote.Remoting.localAddressForRemote(Remoting.scala:116)

I downloaded a tar file, akka-2.2.0-RC1.tgz. Any ideas on what could be going wrong?

thks!

On Monday, January 14, 2013 8:08:42 PM UTC-3, David Riley wrote:
Hi,

I am trying to run the sample project akka-sample-remote from release-2.1 but I get the following error:

[INFO] [01/14/2013 23:05:11.908] [run-main] [Remoting] Starting remoting
[error] (run-main) akka.remote.RemoteTransportException: No transport is loaded
for protocol: akka, available protocols: tcp.akka
akka.remote.RemoteTransportException: No transport is loaded for protocol: akka,
 available protocols: tcp.akka
        at akka.remote.Remoting$.localAddressForRemote(Remoting.scala:109)

Is this a known problem? 

I tried changing all references of akka with tcp.akka and the LookupApp works, but not the CreationApp, where there is a similar error.

Thanks

David

--
>>>>>>>>>> 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 unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.

To post to this group, send email to akka...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Viktor Klang
Director of Engineering

Twitter: @viktorklang

√iktor Ҡlang

unread,
Jun 12, 2013, 11:29:06 AM6/12/13
to Akka User List
Hi Alberto,


On Wed, Jun 12, 2013 at 11:24 AM, Alberto Andreotti <albertoa...@gmail.com> wrote:
Hi Viktor,

thanks for your answer, I did not follow the guide, but I switched to the correct version instead, and that fixed the problem. It was my mistake :-).
Now, another question can I use this microkernel stuff to run my app as a daemon? In that case, how would I go about it?

An in-JVM daemon or a process daemon?

Cheers,
 

thanks again,

Alberto.

√iktor Ҡlang

unread,
Jun 12, 2013, 12:49:14 PM6/12/13
to Akka User List


On Wed, Jun 12, 2013 at 11:38 AM, Alberto Andreotti <albertoa...@gmail.com> wrote:
Hey!, what I'm trying to do is to have my app split in two parts, on one side all my actors that perform the heavy work, I would like to put this part in a daemon process. On the other side, I would like to have one or more apps(like clients) that will interact with the daemon by talking to actors in the actorSystem of the daemon.
I  tried running,

akka package.MyServerBootableClass &

it works, but when the console dies, so does the process.

Alberto.

√iktor Ҡlang

unread,
Jun 12, 2013, 1:43:10 PM6/12/13
to Akka User List
Hi Alberto,


On Wed, Jun 12, 2013 at 1:40 PM, Alberto Andreotti <albertoa...@gmail.com> wrote:
Hi Viktor,

thanks for the answer. I was really expecting the microkernel layer to handle it for me.

How so?
 
Otherwise I don't find the value added by the microkernel, besides an standard deployment method.

You don't see the value of getting a single distributable that can be deployed in one piece?
 
I had tried(unsuccessfully) the options in the link you provided, but with sbt. Now using the microkernel + nohup did the trick. Just in case it help others, that's what I run to have the app running as daemon,

A single, platform specific, command isn't that bad of an overhead, right?

Cheers,
 

nohup akka mypackage.MyBootableClass &

Alberto.

Alberto Andreotti

unread,
Jun 14, 2013, 10:09:04 AM6/14/13
to akka...@googlegroups.com
Hi again,

hello I'm having problems again with this. First of all, I would like to explain what I'm trying to do, to be sure I'm following the right pattern. I would like to have my app split up into parts with independent lifecycles(startup, shutdown, etc),

1. A daemon from where all my actors are instantiated. This should almost never be stopped. 
2. A client app, like a web interface, that talks to the daemon. This could be stopped and restarted many times.

I want to have these two parts living in the same machine, using some sort of "IPC" between each other.
What I did is to have the client referencing actors from the daemon(running with microkernel), which worked at some point, but is not working now. The funny thing is that when I run the same code in the REPL everything works fine.
I verified that the conf file is within the jar, and changed ips from localhost(127.0.0.1) to the external machine's IP, with no success. Any ideas on where I could be wrong?

Thanks again!

Alberto.



On Wednesday, June 12, 2013 2:55:53 PM UTC-3, Alberto Andreotti wrote:
Hi, I definitely see the value, but I was hoping for the extra feature. Seems I woke up lazy today :-).

Cheers,

Alberto.

Patrik Nordwall

unread,
Jun 14, 2013, 11:36:41 AM6/14/13
to akka...@googlegroups.com
Is the problem that you can't send messages between the two actor systems? 
I need more information to be able to help.

Try to log the settings.
akka.log-config-on-start=on



For more options, visit https://groups.google.com/groups/opt_out.
 
 



--

Patrik Nordwall
Typesafe The software stack for applications that scale
Twitter: @patriknw

Alberto Andreotti

unread,
Jun 14, 2013, 3:02:22 PM6/14/13
to akka...@googlegroups.com
Hi Patrik,

thanks for the suggestion, I attached a file with a diff(mercurial) between the config output for both the kernel and no kernel versions. The kernel version seems to have more stuff.

Alberto.
KB_3_to_2.diff

Patrik Nordwall

unread,
Jun 14, 2013, 3:12:53 PM6/14/13
to akka...@googlegroups.com
I can't see anything wrong in the diff. You have more jar files in the classpath when running the microkernel and that is why you see diffs in reference conf.

What code are you trying to run? Anything in the logs?

Alberto Andreotti

unread,
Jun 14, 2013, 3:19:34 PM6/14/13
to akka...@googlegroups.com
I'm just creating a couple of actors, and then I try to talk to them from other process through references in the actor system. I instantiate the exact same thing from the REPL with no problems. Weird, right?

Akka Team

unread,
Jun 24, 2013, 3:00:11 AM6/24/13
to Akka User List
Hi Alberto,

without saying what exactly does not work you make it quite hard to help you.

Regards,

Roland
Akka Team
Typesafe - The software stack for applications that scale
Blog: letitcrash.com
Twitter: @akkateam

Alberto Andreotti

unread,
Jun 28, 2013, 9:16:22 PM6/28/13
to akka...@googlegroups.com
Hi Roland,

thanks for keeping an eye on the post. I couldn't isolate the problem that's why I wasn't more specific. Fortunately I got closer, and I'll explain what I learnt in case others find it useful.
After tinkering a while with configuration, I started seeing an java.io.OptionalDataException. After googling for it, I realized that it was something related with serialization of lists in messages. It seems that when the application is run inside the microkernel the serialization happens in a different way.
I was sending a list of strings, among other things, to my actors living in the microkernel, the message could never make it to the final actors due to the serialization problem. I tried with simple messages(no members in them) and bingo! they can reach the remote actor system.
The weird part is that I spent a lot of time without seeing the exception, that's why I started playing with my firewall cofiguration, netstat and the like. You can see a user having a similar problem using Akka + Apache James here.
I couldn't solve my particular problem, mainly because lack of time, I turned a couple of message members into serializables, changed the configuration to choose a serializer explicitly, and the exception went away. I still have to take a closer look, and verify configuration, but I think I'm closer. I'll keep you posted :-).

thanks!

Alberto.

c wanek

unread,
Nov 22, 2013, 4:44:28 PM11/22/13
to akka...@googlegroups.com
Alberto,

Were you able to resolve this issue? 

I've run into precisely the same thing with serializing lists.  In my particular case, I'm trying to send from a Play Framework application to a remote akka actor in a cluster (though for my test purposes, it's just a single node).  My lists are members of the objects I'm trying to serialize, so I'm not able to choose a different serializer for just the lists.

Can you share some details about the config changes you made?

Thanks,
Charlie
Reply all
Reply to author
Forward
0 new messages