Hi Patrik! Indeed it was very strange! Before we added the println to the shutdown-hook of the the Actorsystem the only thing we found in the log was some shutdown info of reactive mongo.
04:12:24.094 DEBUG Cluster Node [akka.tcp://[email protected]:3552] - Heartbeat to [akka.tcp://[email protected]:3552] 04:12:24.094 DEBUG Cluster Node [akka.tcp://[email protected]:3552] - Heartbeat to [akka.tcp://[email protected]:3552] 04:12:24.096 DEBUG Cluster Node [akka.tcp://[email protected]:3552] - Heartbeat response from [akka.tcp://[email protected]:3552] 04:12:24.098 DEBUG Cluster Node [akka.tcp://[email protected]:3552] - Heartbeat response from [akka.tcp://[email protected]:3552] ... 04:12:24.833 DEBUG Associated [akka.tcp://[email protected]:3552] <- [akka.tcp://GatlingSystem@gatlinghostname:9044] 04:12:25.115 DEBUG Netty says all channels are closed. 04:12:25.115 DEBUG Netty says all channels are closed. 04:12:25.119 WARN MongoDBSystem Actor[akka://OurProgramm/user/MongoDB_default#1699070059] stopped. 04:12:25.119 WARN MongoDBSystem Actor[akka://OurProgramm/user/MongoDB_meta#-2087698689] stopped. Thats it! No exception nothing. Regards Wolfgang Am Montag, 9. Februar 2015 13:04:25 UTC+1 schrieb Patrik Nordwall: > > Hi Wolfgang, > > This sounds very strange. > > Can you share your configuration? > > I'm thinking about one setting. > akka.jvm-exit-on-fatal-error > If you have configured that to off the jvm might still be running but the > ActorSystem is shutdown because of a fatal error. > > What is shown in the logs? Nothing? Can you run with debug log level, then > you should see a steady stream of log messages (e.g. form cluster > heartbeating) and we might be able to see what happend before the magical > shutdown. > > /Patrik > > On Mon, Feb 9, 2015 at 11:51 AM, Wolfgang Friedl <[email protected] > <javascript:>> wrote: > >> Hi Roland! >> >> I was out on vacation, so sorry for may delayed response. >> Its exactly happed like I described. The JVM was still running but the >> actorsystem was gone of course with all its actors. >> >> Sometimes the problem occurred after a few minutes sometimes it happed >> after a few hours. Before the incident happened our system behaved like it >> should. >> >> Due to unknown reason sometimes the actorsystem stopped to work. In the >> log files we did not find any log-entries from our postStop() functions of >> our actors. Thats why we added a println() to the shutdown hook of the >> actorsystem, and this lines we did find at our console after the incident >> happened again. >> >> As I mentioned above after we switched back to akka 2.3.7 (which is also >> used by all systems who are remotly talking to us) the problem did not >> occur again. >> >> Regards >> >> Wolfgang >> >> >> Am Freitag, 30. Januar 2015 09:04:25 UTC+1 schrieb rkuhn: >>> >>> Hi Wolfgang, >>> >>> thinking about this for a bit I am very confused: the ActorSystem cannot >>> “vanish” while the JVM keeps running. You mention postStop hooks that are >>> not executed. Can you be a bit more specific about how you know that >>> >>> - there is only exactly one JVM ever started >>> - there is an ActorSystem successfully running within that JVM >>> - then somehow that very same JVM suddenly has no ActorSystem >>> anymore without stopping its Actors >>> >>> >>> Sorry for sounding skeptical, I’d just like to exclude other >>> possibilities (like a new JVM coming up and failing to start its >>> ActorSystem while an old JVM silently disappears in its entirety, e.g. by >>> using ømq and encountering a failure). >>> >>> Regards, >>> >>> Roland >>> >>> 29 jan 2015 kl. 14:58 skrev Wolfgang Friedl <[email protected]>: >>> >>> Update >>> >>> After switching back to Akka 2.3.7 the problem did not occur anymore (so >>> far). >>> >>> So its either a problem of Akka 2.3.8 (2.3.9) or there is a problem in >>> certain circumstances to connect systems (with akka.remote) running >>> with different akka versions, in our case 2.3.7 with akka 2.3.8 (2.3.9) >>> >>> >>> Regards >>> >>> Wolfgang >>> >>> -- >>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>> >>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/ >>> current/additional/faq.html >>> >>>>>>>>>> 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 [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/akka-user. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> >>> *Dr. Roland Kuhn* >>> *Akka Tech Lead* >>> Typesafe <http://typesafe.com/> – Reactive apps on the JVM. >>> twitter: @rolandkuhn >>> <http://twitter.com/#!/rolandkuhn> >>> >>> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> >>>>>>>>>> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > Patrik Nordwall > Typesafe <http://typesafe.com/> - Reactive apps on the JVM > Twitter: @patriknw > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
