Skip to content
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

Closed
ennru opened this issue Sep 24, 2018 · 3 comments
Closed

Failed: JMS Connectors should sink disconnect exceptional completion #1231

ennru opened this issue Sep 24, 2018 · 3 comments

Comments

@ennru
Copy link
Member

ennru commented Sep 24, 2018

https://travis-ci.org/akka/alpakka/jobs/432357452

[info] JmsConnectorsSpec:
[info] The JMS Connectors
[info] - should sink disconnect exceptional completion *** FAILED *** (90 milliseconds)
[info]   javax.jms.JMSException: Cannot send, channel has already failed: tcp://127.0.0.1:44374 was not an instance of akka.stream.alpakka.jms.ConnectionRetryException, but an instance of javax.jms.JMSException (JmsConnectorsSpec.scala:598)
This was referenced Oct 1, 2018
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
@ennru
Copy link
Member Author

ennru commented Oct 19, 2018

@2m
Copy link
Member

2m commented Oct 26, 2018

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
@2m 2m mentioned this issue Oct 28, 2018
@ennru
Copy link
Member Author

ennru commented Oct 31, 2018

Fixed with #1252

@ennru ennru closed this as completed Oct 31, 2018
@ennru ennru added this to the 1.0-M2 milestone Oct 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants