jxtps opened a new issue, #1708:
URL: https://github.com/apache/pekko/issues/1708
I'm seeing the following occasional stack trace in production:
```
java.lang.IllegalArgumentException: requirement failed
at scala.Predef$.require(Predef.scala:324)
at
org.apache.pekko.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:105)
at
org.apache.pekko.dispatch.TaskInvocation.run(AbstractDispatcher.scala:59)
at
org.apache.pekko.dispatch.ForkJoinExecutorConfigurator$PekkoForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:57)
at
java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at
java.base/java.util.concurrent.ForkJoinPool.helpJoin(ForkJoinPool.java:2076)
at
java.base/java.util.concurrent.ForkJoinTask.awaitDone(ForkJoinTask.java:423)
at
java.base/java.util.concurrent.ForkJoinTask.invokeAll(ForkJoinTask.java:750)
...
```
The `...` is my client code, and it does `ForkJoinTask.invokeAll(tasks)`
with an array of `RecursiveAction`s.
This happens during heavily parallelized calls to my client code. Think a
bunch of concurrent web requests all needing to issue parallel sub-tasks.
As this is happening based on live traffic I don't have a neatly packaged up
reproducible test case immediately available.
Does pekko have multi-threaded stress tests with tasks being invoked in
parallel?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org
For additional commands, e-mail: notifications-h...@pekko.apache.org
