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: R2dbcExecutorSpec #476

Open
johanandren opened this issue Nov 1, 2023 · 0 comments
Open

Failed: R2dbcExecutorSpec #476

johanandren opened this issue Nov 1, 2023 · 0 comments
Labels
failed Test failure

Comments

@johanandren
Copy link
Member

https://github.com/akka/akka-persistence-r2dbc/actions/runs/6701159366/job/18208163693#step:6:443

--> [akka.persistence.r2dbc.internal.R2dbcExecutorSpec: R2dbcExecutor should close connection when no response from update] Start of log messages of test that [Failed(org.scalatest.exceptions.TestFailedException: The future returned an exception of type: io.r2dbc.postgresql.client.ReactorNettyClient$PostgresConnectionClosedException, with message: Connection closed.)]
[2023-10-31 02:13:55,428] [INFO] [akka.event.slf4j.Slf4jLogger] [] [] [R2dbcExecutorSpec-akka.actor.default-dispatcher-3] - Slf4jLogger started
[2023-10-31 02:14:00,443] [INFO] [akka.persistence.r2dbc.internal.R2dbcExecutorSpec] [] [] [parallel-2] - beforeAll delete - getConnection took [5000660] µs
[2023-10-31 02:14:00,451] [INFO] [akka.actor.testkit.typed.scaladsl.LogCapturing] [] [] [pool-1-thread-1-ScalaTest-running-R2dbcExecutorSpec] - Logging started for test [akka.persistence.r2dbc.internal.R2dbcExecutorSpec: R2dbcExecutor should close connection when no response from update]
[2023-10-31 02:14:03,465] [WARN] [akka.persistence.r2dbc.internal.R2dbcExecutorSpec] [] [] [R2dbcExecutorSpec-akka.actor.default-dispatcher-5] - Timeout after [3 seconds], will try to close connection
[2023-10-31 02:14:03,466] [DEBUG] [akka.persistence.r2dbc.internal.R2dbcExecutorSpec] [] [] [R2dbcExecutorSpec-akka.actor.default-dispatcher-3] - test - DB call failed: io.r2dbc.postgresql.client.ReactorNettyClient$PostgresConnectionClosedException: [08006] Connection closed
[2023-10-31 02:14:03,467] [DEBUG] [akka.persistence.r2dbc.internal.R2dbcExecutorSpec] [] [] [R2dbcExecutorSpec-akka.actor.default-dispatcher-5] - test - Select failed: {}
io.r2dbc.postgresql.client.ReactorNettyClient$PostgresConnectionClosedException: Connection closed
	at io.r2dbc.postgresql.client.ReactorNettyClient.lambda$static$1(ReactorNettyClient.java:102)
	at io.r2dbc.postgresql.client.ReactorNettyClient$BackendMessageSubscriber.close(ReactorNettyClient.java:968)
	at io.r2dbc.postgresql.client.ReactorNettyClient.drainError(ReactorNettyClient.java:527)
	at io.r2dbc.postgresql.client.ReactorNettyClient.lambda$close$7(ReactorNettyClient.java:190)
	at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:45)
	at reactor.core.publisher.Mono.subscribe(Mono.java:4495)
	at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.subscribeNext(MonoIgnoreThen.java:263)
	at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:51)
	at reactor.core.publisher.Mono.subscribe(Mono.java:4495)
	at reactor.core.publisher.Mono.subscribeWith(Mono.java:4561)
	at reactor.core.publisher.Mono.toFuture(Mono.java:5073)
	at akka.persistence.r2dbc.internal.R2dbcExecutor$PublisherOps$.asFutureDone$extension(R2dbcExecutor.scala:47)
	at akka.persistence.r2dbc.internal.R2dbcExecutor.closeAfterTimeout(R2dbcExecutor.scala:367)
	at akka.persistence.r2dbc.internal.R2dbcExecutor.$anonfun$withConnection$4(R2dbcExecutor.scala:273)
	at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:49)
	at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:48)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
[2023-10-31 02:14:03,470] [INFO] [akka.actor.testkit.typed.scaladsl.LogCapturing] [] [] [pool-1-thread-1-ScalaTest-running-R2dbcExecutorSpec] - Logging finished for test [akka.persistence.r2dbc.internal.R2dbcExecutorSpec: R2dbcExecutor should close connection when no response from update] that [Failed(org.scalatest.exceptions.TestFailedException: The future returned an exception of type: io.r2dbc.postgresql.client.ReactorNettyClient$PostgresConnectionClosedException, with message: Connection closed.)]
[2023-10-31 02:14:03,470] [DEBUG] [akka.persistence.r2dbc.internal.R2dbcExecutorSpec] [] [] [R2dbcExecutorSpec-akka.actor.default-dispatcher-3] - Connection closed after timeout
<-- [akka.persistence.r2dbc.internal.R2dbcExecutorSpec: R2dbcExecutor should close connection when no response from update] End of log messages of test that [Failed(org.scalatest.exceptions.TestFailedException: The future returned an exception of type: io.r2dbc.postgresql.client.ReactorNettyClient$PostgresConnectionClosedException, with message: Connection closed.)]
[info] - should close connection when no response from update *** FAILED *** (3 seconds, 22 milliseconds)
[info]   The future returned an exception of type: io.r2dbc.postgresql.client.ReactorNettyClient$PostgresConnectionClosedException, with message: Connection closed. (R2dbcExecutorSpec.scala:103)
[info]   org.scalatest.exceptions.TestFailedException:
[info]   at org.scalatest.concurrent.ScalaFutures$$anon$1.futureValueImpl(ScalaFutures.scala:333)
[info]   at org.scalatest.concurrent.Futures$FutureConcept.futureValue(Futures.scala:476)
[info]   at org.scalatest.concurrent.Futures$FutureConcept.futureValue$(Futures.scala:475)
[info]   at org.scalatest.concurrent.ScalaFutures$$anon$1.futureValue(ScalaFutures.scala:281)
[info]   at akka.persistence.r2dbc.internal.R2dbcExecutorSpec.$anonfun$new$2(R2dbcExecutorSpec.scala:103)
@johanandren johanandren added the failed Test failure label Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed Test failure
Projects
None yet
Development

No branches or pull requests

1 participant