reactivemongo play 2.3 0.11.7 to 0.11.11 upgrade raises ExceptionInInitializerError

Question

[I am re-editing this question to reflect on my last tests]

I am trying to upgrade my akka / play 2.3 application from

"org.reactivemongo" %% "play2-reactivemongo" % "0.11.7.play23"

to

"org.reactivemongo" %% "play2-reactivemongo" % "0.11.11-play23"

Compilation goes fine but at run-time I get the following error:

[ERROR] -- NettyTransport(akka://reactivemongo)
failed to bind to /127.0.0.1:2552, shutting down Netty transport

...

Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to: /127.0.0.1:2552

The Akka part of application.conf reads as follows:

akka {
    loggers = ["akka.event.slf4j.Slf4jLogger"]
    loglevel = "DEBUG"
    actor {
        provider = "akka.remote.RemoteActorRefProvider"
        mailbox {
            requirements {
                "akka.dispatch.BoundedMessageQueueSemantics" = bounded-mailbox
            }
        }
    }
    remote {
        enabled-transports = ["akka.remote.netty.tcp"]
        netty.tcp {
            hostname = "127.0.0.1"
            port = 2552
        }
    }
}

The exception is raised when trying to instantiate the reactivemongo driver

val driver = new reactivemongo.api.MongoDriver()

This suggests that the mongodriver is using Akka under the hood and is binding to the same address that my main application. And indeed, if I edit my application.conf and change the akka.remote.netty.tcp.port from 2552 to 2553, I get the following exception:

[ERROR] -- NettyTransport(akka://reactivemongo)
failed to bind to /127.0.0.1:2553, shutting down Netty transport

In the previous versions of reactivemongo, by default, instantiating the driver was starting a new actor system so maybe version 0.11.11 tries to reuse the existing system?

I have tried to modify the akka port used by the driver as follows:

val customConf = ConfigFactory.parseString("""
  akka {
    remote {
      netty.tcp.port = 4711
    }
  }
  """)

val typesafeConfig: com.typesafe.config.Config = ConfigFactory.load(customConf)

val driver = new reactivemongo.api.MongoDriver(Some(typesafeConfig))

But this does not work, the new port is not taken into account and I keep getting the same error:

[ERROR] -- NettyTransport(akka://reactivemongo)
failed to bind to /127.0.0.1:2552, shutting down Netty transport

You are using `connection(..)` aka `connection.apply`, you better use new `connection.database` which proper DB resolution. — cchantep, May 25 '16 at 20:46
done, all the connection() have been replaced by connection.db(). However it does not fix the problem. — david, May 26 '16 at 13:33
I didn't say .db but .database , which is not the same at all — cchantep, May 26 '16 at 15:29
Nope, does not help either ;-( still getting this java.lang.ExceptionInInitializerError — david, May 26 '16 at 18:27
What's mongodbInsert.scala:153) at tuktu.nosql.processors.mongodb — cchantep, May 26 '16 at 22:03
The call of the getFutureCollection method on MongoTools (which is declared as an object): MongoTools.getFutureCollection(settings, credentials, scramsha1, conn) — david, May 26 '16 at 22:19
You should try to make things simpler. Without a simple reproducer there is a lot of misuse than cause that. — cchantep, May 26 '16 at 22:42
I think I have a better idea of where the problem is. Just updated the question accordingly. — david, May 31 '16 at 08:51

score 0 · Answer 1 · answered May 31 '16 at 11:06

Actually, ReactiveMongo loads its configuration from the key 'mongo-async-driver'. So, Adding the following permits to configure ReactiveMongo underlying akka system:

val customConf = ConfigFactory.parseString("""
  mongo-async-driver {
    akka {
      loglevel = WARNING
      remote {
        enabled-transports = ["akka.remote.netty.tcp"]
        netty.tcp {
          hostname = "127.0.0.1"
          port = 4711
        }
      }
    }
  }
  """)

reactivemongo play 2.3 0.11.7 to 0.11.11 upgrade raises ExceptionInInitializerError

1 Answers1