taosdata/TDengine

ava.sql.SQLException: JNI ERROR (0x2354): Unable to establish connection

Open

#21,892 opened on Jun 28, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (5,002 forks)batch import
help wantedquestion

Repository metrics

Stars
 (24,849 stars)
PR merge metrics
 (Avg merge 1d 1h) (4 merged PRs in 30d)

Description

Caused by: java.sql.SQLException: JNI ERROR (0x2354): Unable to establish connection at com.taosdata.jdbc.TSDBError.createSQLException(TSDBError.java:85) at com.taosdata.jdbc.TSDBJNIConnector.connect(TSDBJNIConnector.java:82) at com.taosdata.jdbc.TSDBConnection.connect(TSDBConnection.java:35) at com.taosdata.jdbc.TSDBConnection.(TSDBConnection.java:21) at com.taosdata.jdbc.TSDBDriver.connect(TSDBDriver.java:160) at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138) at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:358) at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:206) at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:477) at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:560) at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:115) at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:112) at org.springframework.jdbc.datasource.DataSourceUtils.fetchConnection(DataSourceUtils.java:158) at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:116) at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:79)

请问是什么原因? 客户端版本：TDengine-client-3.0.4.1

Contributor guide

Research direction
Check the TDengine server status, verify connection parameters (host, port, user, password), ensure the JDBC driver version matches the server, and inspect network/firewall settings. The JNI error suggests a native layer problem; ensure the TDengine client library is properly installed and linked.
Tech stack
javac
Domain
databasebackend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaJDBCBasic TDengine knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60