#3556
  • Created on
    2013-08-22 15:26
  • Reported by
    Patrik Nordwall
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    rkuhn
  • Milestone
    2.3.0-RC3
  • Plan Level
    -
  • Due Date
    -

Attachments

DOC: clarify that TestActorRef can't be used with Stash

Also, improve the error handling for this case, since it throws NPE at Stash.mailbox
case other ⇒ throw ActorInitializationException(self, s"DequeBasedMailbox required, got: ${other.getClass.getName}\n"

context.asInstanceOf[ActorCell].mailbox.messageQueue is null for CallingThreadMailbox
User picture
  on 2013-09-24 14:18 *
By rkuhn
Milestone set to Rollins
User picture
  on 2013-11-05 13:41 *
By rkuhn
Milestone changed from Rollins to -none-
User picture
  on 2013-11-05 14:42 *
By rkuhn
Milestone set to Rollins
User picture
  on 2013-11-05 19:38 *
By viktorklang
Milestone changed from Rollins to Current
User picture
  on 2013-11-05 19:50 *
By rkuhn
Milestone changed from Current to Rollins
User picture
  on 2013-11-28 13:57 *
By bjorn.antonsson@typesafe.com
What would happen if the CallingThreadMailbox exposed the underlying queue? I guess stash and unstash would just wreck havoc with all the orderings and locks, since they would bypass them completely.
User picture
  on 2013-11-29 12:40 *
By bjorn.antonsson@typesafe.com
One solution proposed on the akka user list is to define the stash methods abstract in the FSM actor and mix in Stash at runtime, or a TestStash for testing.

I was thinking that the TestStash could use normal tell operations to unstash things (yes it's not perfect).
User picture
  on 2014-02-04 15:58 *
By Patrik Nordwall
Assigned to set to rkuhn
Status changed from New to Fixed
This was fixed in 2.3.0-RC1. Stash and TestActorRef can now be used together.
User picture
  on 2014-02-14 13:16 *
By rkuhn
Milestone changed from Current to 2.3.0-RC3