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

Bug: Nats heap space error #340

Open
deinelieblings opened this issue Feb 13, 2019 · 0 comments
Open

Bug: Nats heap space error #340

deinelieblings opened this issue Feb 13, 2019 · 0 comments
Labels

Comments

@deinelieblings
Copy link
Member

Error:

[ERROR] [02/11/2019 10:32:15.578] [application-akka.actor.default-dispatcher-68051] [ActorSystem(application)] Uncaught fatal error from thread [application-akka.actor.default-dispatcher-68051] shutting down ActorSystem [application]
java.lang.OutOfMemoryError: Java heap space
    at org.nats.common.NatsUtil.<init>(NatsUtil.java:34)
    at org.nats.Connection.<init>(Connection.java:169)
    at org.nats.Conn.<init>(Conn.scala:28)
    at org.nats.Conn$.connect(Conn.scala:115)
    at utils.Nats.publishLogout(Nats.scala:22)
    at services.UserService$$anonfun$logout$1.apply(UserService.scala:70)
    at services.UserService$$anonfun$logout$1.apply(UserService.scala:69)
    at scala.util.Success$$anonfun$map$1.apply(Try.scala:237)
    at scala.util.Try$.apply(Try.scala:192)
    at scala.util.Success.map(Try.scala:237)
    at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:237)
    at scala.concurrent.Future$$anonfun$map$1.apply(Future.scala:237)
    at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)
    at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
    at akka.dispatch.BatchingExecutor$BlockableBatch$$anonfun$run$1.apply$mcV$sp(BatchingExecutor.scala:91)
    at akka.dispatch.BatchingExecutor$BlockableBatch$$anonfun$run$1.apply(BatchingExecutor.scala:91)
    at akka.dispatch.BatchingExecutor$BlockableBatch$$anonfun$run$1.apply(BatchingExecutor.scala:91)
    at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:72)
    at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:90)
    at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:40)
    at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)
    at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
    at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
    at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
    at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

If a memory problem, it must be tested whether we write the memory unnecessarily full or if the currently available memory is insufficient.

deinelieblings added a commit that referenced this issue Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant