Databases
StackOverflow2013
Postsdbo
POAkka Actor not terminating if an exception is thrown
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAkka Actor not terminating if an exception is thrown
    primarykey
    data
    text
    <p>I am currently trying to get started with Akka and I am facing a weird problem. I've got the following code for my Actor:</p> <pre><code>class AkkaWorkerFT extends Actor { def receive = { case Work(n, c) if n &lt; 0 =&gt; throw new Exception("Negative number") case Work(n, c) =&gt; self reply n.isProbablePrime(c); } } </code></pre> <p>And this is how I start my workers:</p> <pre><code>val workers = Vector.fill(nrOfWorkers)(actorOf[AkkaWorkerFT].start()); val router = Routing.loadBalancerActor(SmallestMailboxFirstIterator(workers)).start() </code></pre> <p>And this is how I shut everything down:</p> <pre><code>futures.foreach( _.await ) router ! Broadcast(PoisonPill) router ! PoisonPill </code></pre> <p>Now what happens is if I send the workers messages with n > 0 (no exception is thrown), everything works fine and the application shuts down properly. However, as soon as I send it a single message which results in an exception, the application does not terminate because there is still an actor running, but I can't figure out where it comes from.</p> <p>In case it helps, this is the stack of the thread in question:</p> <pre><code> Thread [akka:event-driven:dispatcher:event:handler-6] (Suspended) Unsafe.park(boolean, long) line: not available [native method] LockSupport.park(Object) line: 158 AbstractQueuedSynchronizer$ConditionObject.await() line: 1987 LinkedBlockingQueue&lt;E&gt;.take() line: 399 ThreadPoolExecutor.getTask() line: 947 ThreadPoolExecutor$Worker.run() line: 907 MonitorableThread(Thread).run() line: 680 MonitorableThread.run() line: 182 </code></pre> <p>PS: The thread which is not terminating isn't any of the worker threads, because I've added a postStop callback, every one of them stops properly.</p> <p>PPS: <code>Actors.registry.shutdownAll</code> workarounds the problem, but I think shutdownAll should only be used as a last resort, shouldn't it?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USfresskoma
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAkka Actor not terminating if an exception is thrown
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAkka Actor not terminating if an exception is thrown
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAkka Actor not terminating if an exception is thrown
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI suspect the actor that remains is the EventHandler actor.
      singulars
      1. POAkka Actor not terminating if an exception is thrown
      1. USViktor Klang
    2. CO@ViktorKlang: But why does it remain, and how do I stop it properly? :)
      singulars
      1. POAkka Actor not terminating if an exception is thrown
      1. USfresskoma
    3. COWhen should it be stopped? See the shutdown method here: http://akka.io/api/akka/1.1.2/#akka.event.EventHandler$
      singulars
      1. POAkka Actor not terminating if an exception is thrown
      1. USViktor Klang
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload