-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed: JMS Connectors should sink disconnect exceptional completion #1231
Comments
This was referenced Oct 1, 2018
Merged
Merged
andreas-schroeder
pushed a commit
to andreas-schroeder/alpakka
that referenced
this issue
Oct 17, 2018
Stream-based connection status Connection status is now exposed as stream of updates. For the Java interface, a Java enum is exposed, for the Scala interface, a sealed trait with case objects and a case class is used. Fix reconnect attempts Now also retry to connect (for a limited amount of times and after delay) if creating sessions, consumers, producers or destinations fail Fix flaky 'disconnect exceptional completion' test Fixes akka#1231 Fixes akka#1031
andreas-schroeder
pushed a commit
to andreas-schroeder/alpakka
that referenced
this issue
Oct 17, 2018
Stream-based connection status Connection status is now exposed as stream of updates. For the Java interface, a Java enum is exposed, for the Scala interface, a sealed trait with case objects and a case class is used. Fix reconnect attempts Now also retry to connect (for a limited amount of times and after delay) if creating sessions, consumers, producers or destinations fail Fix flaky 'disconnect exceptional completion' test Fixes akka#1231 Fixes akka#1031
andreas-schroeder
pushed a commit
to andreas-schroeder/alpakka
that referenced
this issue
Oct 27, 2018
Stream-based connection status Connection status is now exposed as stream of updates. For the Java interface, a Java enum is exposed, for the Scala interface, a sealed trait with case objects and a case class is used. Fix reconnect attempts Now also retry to connect (for a limited amount of times and after delay) if creating sessions, consumers, producers or destinations fail Fix flaky 'disconnect exceptional completion' test Fixes akka#1231 Fixes akka#1031
Merged
Fixed with #1252 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://travis-ci.org/akka/alpakka/jobs/432357452
The text was updated successfully, but these errors were encountered: