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

Failure: JmsConnector connection status should reflect connection status on connection retries #1306

Open
2m opened this issue Nov 6, 2018 · 5 comments

Comments

@2m
Copy link
Member

2m commented Nov 6, 2018

[info] - should reflect connection status on connection retries *** FAILED *** (16 seconds, 792 milliseconds)
[info]   The code passed to eventually never returned normally. Attempted 16 times over 10.034311338 seconds. Last failure message: Published connection state Disconnected was not Connected. (JmsConnectionStatusSpec.scala:349)
[info]   org.scalatest.exceptions.TestFailedDueToTimeoutException:
[info]   at org.scalatest.concurrent.Eventually.tryTryAgain$1(Eventually.scala:432)
[info]   at org.scalatest.concurrent.Eventually.eventually(Eventually.scala:439)
[info]   at org.scalatest.concurrent.Eventually.eventually$(Eventually.scala:391)
[info]   at akka.stream.alpakka.jms.JmsSpec.eventually(JmsSpec.scala:18)
[info]   at akka.stream.alpakka.jms.JmsConnectionStatusSpec.$anonfun$new$43(JmsConnectionStatusSpec.scala:349)
[info]   at scala.collection.immutable.Range.foreach$mVc$sp(Range.scala:155)
[info]   at akka.stream.alpakka.jms.JmsConnectionStatusSpec.$anonfun$new$42(JmsConnectionStatusSpec.scala:348)
[info]   at akka.stream.alpakka.jms.JmsConnectionStatusSpec.$anonfun$new$42$adapted(JmsConnectionStatusSpec.scala:313)
[info]   at akka.stream.alpakka.jms.JmsSpec.withServer(JmsSpec.scala:54)
[info]   at akka.stream.alpakka.jms.JmsConnectionStatusSpec.$anonfun$new$41(JmsConnectionStatusSpec.scala:313)

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

andreas-schroeder pushed a commit to andreas-schroeder/alpakka that referenced this issue Nov 25, 2018
Allow for infinite send retries. It was possible to reproduce the error
partially under heavy CPU over-utilization and unfair scheduling: it
can happen that 10 send tries are performed before reconnection is
scheduled.

Fixes akka#1306
ennru pushed a commit that referenced this issue Nov 27, 2018
Allow for infinite send retries. It was possible to reproduce the error
partially under heavy CPU over-utilization and unfair scheduling: it
can happen that 10 send tries are performed before reconnection is
scheduled.

Fixes #1306
@ennru ennru added this to the 1.0-M2 milestone Nov 27, 2018
@ennru
Copy link
Member

ennru commented Feb 14, 2019

A different variant in the same test:

[info] JmsConnectionStatusSpec:
[info] JmsConnector connection status
[info] - should reflect connection status on connection retries *** FAILED *** (3 seconds, 916 milliseconds)
[info]   java.io.IOException: VMTransportServer already bound at: vm://brokerName-a6671ba7-3b6c-4aca-a52e-b1dc55936cc9?create=false

https://travis-ci.org/akka/alpakka/jobs/492957863#L706

@ennru ennru reopened this Feb 14, 2019
@ennru ennru removed this from the 1.0-M2 milestone Feb 14, 2019
@2m
Copy link
Member Author

2m commented Apr 16, 2019

[info] - should reflect connection status on connection retries *** FAILED *** (2 seconds, 133 milliseconds)
[info]   java.io.IOException: VMTransportServer already bound at: vm://brokerName-f83bdfce-c8c3-49af-bafc-5eb4da36b8e5?create=false
[info]   at org.apache.activemq.transport.vm.VMTransportFactory.bind(VMTransportFactory.java:237)
[info]   at org.apache.activemq.transport.vm.VMTransportFactory.doBind(VMTransportFactory.java:223)
[info]   at org.apache.activemq.transport.TransportFactorySupport.bind(TransportFactorySupport.java:40)
[info]   at org.apache.activemq.broker.TransportConnector.createTransportServer(TransportConnector.java:318)
[info]   at org.apache.activemq.broker.TransportConnector.getServer(TransportConnector.java:141)

https://travis-ci.com/akka/alpakka/jobs/192800923

@2m 2m mentioned this issue Apr 16, 2019
@2m
Copy link
Member Author

2m commented Jun 19, 2019

@2m
Copy link
Member Author

2m commented Aug 19, 2019

@ennru
Copy link
Member

ennru commented Nov 27, 2019

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