StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGracefully terminating a Scala program after using Actor.self
primarykey
Id
10400412
data
AcceptedAnswerId
0
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-05-01T15:59:29.343
FavoriteCount
0
LastActivityDate
2012-05-02T11:51:07.583
LastEditDate
2012-05-01T16:10:28.870
LastEditorUserId
18078
OwnerUserId
18078
ParentId
0
PostTypeId
1
Score
2
ViewCount
430
LastEditorDisplayName
text
Body
Using scala.actors.Actor.self creates a ForkJoinScheduler, which sticks around and keeps the program from terminating normally. I'd like to use Scala actors within a program that is written in Java, and currently uses a thread pool which shuts down gracefully. It would be ideal if I could coerce Actor to use a DaemonScheduler, but if need be I'd be happy to issue an explicit termination command. Here's some sample code: <pre><code>object EchoActor extends DaemonActor { def act() { loop { react { case (x: Any, respondTo: Actor) => { println("echoActor Got message " + x) respondTo ! "Echoing: " + x } case msg => println("Can't handle message " + msg) } } } } object TestRunner extends App { EchoActor.start() for (n <- 1 to 3) { EchoActor !("Time to echo", self) println(self.receiveWithin(1000) { case x => x}) Actor.clearSelf() // <<-- This doesn't allow for graceful shutdown } Actor.resetProxy() // <<-- Neither does this println("Done.") } </code></pre> This program doesn't terminate, even though there are no threads left that could use Actor.self. I've tried calling Actor.exit(), which just throws an InterruptedException, and I'm just about to give up completely on Actor.self. Am I missing something? Update Just discovered: <pre><code>scala.actorsScheduler.shutdown() </code></pre> which works for global termination, and will get the job done for now. I would prefer to change the default scheduler to be a DaemonScheduler, so please post an answer if you know how.
Tags
<scala><actor>
Title
Gracefully terminating a Scala program after using Actor.self
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USDavid Leppik
UserOwnerUserId
1. USDavid Leppik
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POGracefully terminating a Scala program after using Actor.self
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POGracefully terminating a Scala program after using Actor.self
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.