Ask Your Question
0

How to connect to ADABAS through Connx JDBC Driver ?

asked 2020-04-27 13:45:33 -0500

Hi, I'm using a JDBC Lookup executor connecting to a ADABAS database through Connx JDBC.

JDBC driver was registered in SDC as a external library but I'm getting this exception when pipeline starts:

com.streamsets.datacollector.runner.PipelineRuntimeException: CONTAINER_0800 - Can't start pipeline due 1 validation error(s). First one: JDBC_06 - Failed to initialize connection pool: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: Not supported yet.
    at com.streamsets.datacollector.execution.runner.common.ProductionPipeline.run(ProductionPipeline.java:141)
    at com.streamsets.datacollector.execution.runner.common.ProductionPipelineRunnable.run(ProductionPipelineRunnable.java:75)
    at com.streamsets.datacollector.execution.runner.standalone.StandaloneRunner.start(StandaloneRunner.java:720)
    at com.streamsets.datacollector.execution.AbstractRunner.lambda$scheduleForRetries$0(AbstractRunner.java:363)
    at com.streamsets.pipeline.lib.executor.SafeScheduledExecutorService$SafeCallable.lambda$call$0(SafeScheduledExecutorService.java:226)
    at com.streamsets.datacollector.security.GroupsInScope.execute(GroupsInScope.java:33)
    at com.streamsets.pipeline.lib.executor.SafeScheduledExecutorService$SafeCallable.call(SafeScheduledExecutorService.java:222)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    at com.streamsets.datacollector.metrics.MetricSafeScheduledExecutorService$MetricsTask.run(MetricSafeScheduledExecutorService.java:100)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)

Any ideas on what may be going on?

Thanks.

edit retag flag offensive close merge delete

Comments

Is there a 'caused by' below that stack trace? That should give a better idea of the problem. You may need to look in sdc.log

metadaddy gravatar imagemetadaddy ( 2020-04-27 14:54:33 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2020-04-28 09:06:04 -0500

Thank you, metadaddy, for your update.

I've enabled debug and the log gave me a better idea about the issue. It appears to me that the cause is a JDBC driver limitation.

2020-04-28 10:34:57,938     MACK_GET_SAM_20200427/MACKGETSAM20200427b11d2a70-71d8-4f98-b665-1b4d37c04ff5    ERROR   HikariPool-1 - Exception during pool initialization.    HikariPool  *admin  0   ProductionPipelineRunnable-MACKGETSAM20200427b11d2a70-71d8-4f98-b665-1b4d37c04ff5-MACK_GET_SAM_20200427
java.lang.UnsupportedOperationException: Not supported yet.
    at com.Connx.jdbc.TCJdbc.TCJdbcConnection.isValid(TCJdbcConnection.java:1227)
    at com.zaxxer.hikari.pool.PoolBase.checkDriverSupport(PoolBase.java:454)
    at com.zaxxer.hikari.pool.PoolBase.setupConnection(PoolBase.java:421)
    at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:374)
    at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:198)
    at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:467)
    at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:541)
    at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:115)
    at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:81)
    at com.streamsets.pipeline.lib.jdbc.JdbcUtil.createDataSourceForRead(JdbcUtil.java:964)
    at com.streamsets.pipeline.stage.processor.jdbclookup.JdbcLookupProcessor.init(JdbcLookupProcessor.java:144)
    at com.streamsets.pipeline.api.base.BaseStage.init(BaseStage.java:48)
    at com.streamsets.pipeline.api.base.configurablestage.DStage.init(DStage.java:36)
    at com.streamsets.datacollector.runner.StageRuntime.lambda$init$0(StageRuntime.java:220)
    at com.streamsets.datacollector.util.LambdaUtil.withClassLoaderInternal(LambdaUtil.java:148)
    at com.streamsets.datacollector.util.LambdaUtil.withClassLoader(LambdaUtil.java:44)
    at com.streamsets.datacollector.runner.StageRuntime.init(StageRuntime.java:218)
    at com.streamsets.datacollector.runner.StagePipe.init(StagePipe.java:107)
    at com.streamsets.datacollector.runner.StagePipe.init(StagePipe.java:44)
    at com.streamsets.datacollector.runner.Pipeline.initPipe(Pipeline.java:392)
    at com.streamsets.datacollector.runner.Pipeline.lambda$init$0(Pipeline.java:381)
    at com.streamsets.datacollector.runner.PipeRunner.acceptConsumer(PipeRunner.java:221)
    at com.streamsets.datacollector.runner.PipeRunner.forEach(PipeRunner.java:175)
    at com.streamsets.datacollector.runner.Pipeline.init(Pipeline.java:378)
    at com.streamsets.datacollector.execution.runner.common.ProductionPipeline.run(ProductionPipeline.java:98)
    at com.streamsets.datacollector.execution.runner.common.ProductionPipelineRunnable.run(ProductionPipelineRunnable.java:75)
    at com.streamsets.datacollector.execution.runner.standalone.StandaloneRunner.start(StandaloneRunner.java:720)
    at com.streamsets.datacollector.execution.runner.common.AsyncRunner.lambda$start$3(AsyncRunner.java:151)
    at com.streamsets.pipeline.lib.executor.SafeScheduledExecutorService$SafeCallable.lambda$call$0(SafeScheduledExecutorService.java:226)
    at com.streamsets.datacollector.security.GroupsInScope.execute(GroupsInScope.java:33)
    at com.streamsets.pipeline.lib.executor.SafeScheduledExecutorService$SafeCallable.call(SafeScheduledExecutorService.java:222)
    at com.streamsets.pipeline.lib.executor.SafeScheduledExecutorService$SafeCallable.lambda$call$0(SafeScheduledExecutorService.java:226)
    at com.streamsets.datacollector.security.GroupsInScope.execute(GroupsInScope.java:33)
    at com.streamsets.pipeline.lib.executor.SafeScheduledExecutorService$SafeCallable.call(SafeScheduledExecutorService.java:222)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
    at com.streamsets.datacollector.metrics.MetricSafeScheduledExecutorService$MetricsTask.run(MetricSafeScheduledExecutorService.java:100)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
2020-04-28 10:34:57,943 ...
(more)
edit flag offensive delete link more

Comments

A new version of Connx JDBC Driver was provided and the issue was solved.

ReneMendes gravatar imageReneMendes ( 2020-05-05 07:16:30 -0500 )edit
Login/Signup to Answer

Question Tools

1 follower

Stats

Asked: 2020-04-27 13:45:11 -0500

Seen: 23 times

Last updated: Apr 28