Alpakka JMS is bouncing ActiveMQ connections on temp DestinationDoesNotExist

What is the rationale behind not handling the SUBJ exception smarter (check .isTemporary() on it and based on that decide whether to ignore it or not)?

What would be the best way to implement such behavior change?

Hi @mrbald

Possibly nobody else had this problem with temporary destinations.
I suggest you try to find a solution in the Alpakka JMS code and submit a PR with those changes.