Uploaded image for project: 'JS - JobScheduler'
  1. JS - JobScheduler
  2. JS-1710

HikariPool$PoolInitializationException if JocOrderStatistics is called

    XMLWordPrintable

Details

    • Fix
    • Status: Dismissed (View Workflow)
    • Major
    • Resolution: Duplicate
    • None
    • 1.11.2, 1.12
    • None

    Description

      Current Situation

      In an environment with Microsoft SQL Server 2012 (SP3) (KB3072779) - 11.0.6020.0 (X64) the JobScheduler has no problems to access the database but the
      web service ./jobscheduler/master/api/order?return=JocOrderStatistics
      comes with

      com.sos.scheduler.engine.plugins.newwebservice.routes.ApiRoute [WARN ] - com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: null
      com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: null
      	at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:512)
      	at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:105)
      	at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:71)
      	at com.sos.scheduler.engine.kernel.database.JdbcConnectionPool$.com$sos$scheduler$engine$kernel$database$JdbcConnectionPool$$newConnectionPool(JdbcConnectionPool.scala:44)
      	at com.sos.scheduler.engine.kernel.database.JdbcConnectionPool.com$sos$scheduler$engine$kernel$database$JdbcConnectionPool$$dataSource$lzycompute(JdbcConnectionPool.scala:20)
      	at com.sos.scheduler.engine.kernel.database.JdbcConnectionPool.com$sos$scheduler$engine$kernel$database$JdbcConnectionPool$$dataSource(JdbcConnectionPool.scala:20)
      	at com.sos.scheduler.engine.kernel.database.JdbcConnectionPool.throttledExecutionContext$lzycompute(JdbcConnectionPool.scala:22)
      	at com.sos.scheduler.engine.kernel.database.JdbcConnectionPool.throttledExecutionContext(JdbcConnectionPool.scala:22)
      	at com.sos.scheduler.engine.kernel.database.JdbcConnectionPool.future(JdbcConnectionPool.scala:39)
      	at com.sos.scheduler.engine.kernel.database.JdbcConnectionPool.readOnly(JdbcConnectionPool.scala:27)
      	at com.sos.scheduler.engine.kernel.order.OrderSubsystem.fetchDistributedOrderStatistics(OrderSubsystem.scala:100)
      	at com.sos.scheduler.engine.kernel.order.OrderSubsystem.distributedOrderStatistics(OrderSubsystem.scala:93)
      	at com.sos.scheduler.engine.kernel.DirectSchedulerClient$$anonfun$jocOrderStatistics$1.apply(DirectSchedulerClient.scala:119)
      	at com.sos.scheduler.engine.kernel.DirectSchedulerClient$$anonfun$jocOrderStatistics$1.apply(DirectSchedulerClient.scala:117)
      	at com.sos.scheduler.engine.kernel.DirectSchedulerClient$$anonfun$respondWithSnapshotFuture$1.apply(DirectSchedulerClient.scala:192)
      	at com.sos.scheduler.engine.kernel.DirectSchedulerClient$$anonfun$respondWithSnapshotFuture$1.apply(DirectSchedulerClient.scala:192)
      	at com.sos.scheduler.engine.common.async.FutureCompletion$$anon$1.call(FutureCompletion.scala:46)
      	at com.sos.scheduler.engine.common.async.TimedCall$$anonfun$1.apply(TimedCall.scala:21)
      	at scala.util.Try$.apply(Try.scala:192)
      	at com.sos.scheduler.engine.common.async.TimedCall$class.onApply(TimedCall.scala:21)
      	at com.sos.scheduler.engine.common.async.FutureCompletion$$anon$1.onApply(FutureCompletion.scala:43)
      	at com.sos.scheduler.engine.common.async.CallRunner.f$1(CallRunner.scala:36)
      	at com.sos.scheduler.engine.common.async.CallRunner.executeMatureCalls(CallRunner.scala:42)
      	at com.sos.scheduler.engine.kernel.Scheduler$$anonfun$executeCallQueue$1.apply$mcZ$sp(Scheduler.scala:206)
      	at com.sos.scheduler.engine.kernel.Scheduler$$anonfun$executeCallQueue$1.apply(Scheduler.scala:206)
      	at com.sos.scheduler.engine.kernel.Scheduler$$anonfun$executeCallQueue$1.apply(Scheduler.scala:206)
      	at com.sos.scheduler.engine.kernel.async.SchedulerThreadFutures$.inSchedulerThread(SchedulerThreadFutures.scala:15)
      	at com.sos.scheduler.engine.kernel.Scheduler.executeCallQueue(Scheduler.scala:206)
      	at com.sos.scheduler.engine.kernel.Scheduler.onEnteringSleepState(Scheduler.scala:200)
      Caused by: java.lang.AbstractMethodError
      	at net.sourceforge.jtds.jdbc.JtdsConnection.isValid(JtdsConnection.java:2833)
      	at com.zaxxer.hikari.pool.PoolBase.checkDriverSupport(PoolBase.java:400)
      	at com.zaxxer.hikari.pool.PoolBase.setupConnection(PoolBase.java:375)
      	at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:346)
      	at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:506)
      	... 28 more
      

      Desired Behavior

      The web service ./jobscheduler/master/api/order?return=JocOrderStatistics should work properly.

      Attachments

        Issue Links

          Activity

            People

              jz Joacim Zschimmer
              oh Oliver Haufe
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: