Home > Back-end >  Sharding postgresql - proxy connection error: always find a JDBC type '2003'
Sharding postgresql - proxy connection error: always find a JDBC type '2003'

Time:09-25

Project will use depots table, recently saw some depots table of the current middleware, feeling sharding - proxy can also try once, then
Local with Navicat Premium15.0.4 access sharding - proxy service,
Encounter a few more strange questions, always can't find the reason, think excuse me expert help see,

The first problem is the local Navicat Premium can display the test connection is successful,
Double-click the connection name after save connection,
Originally, double-click the link name should be able to see the list of all database under the current connection, but I always can't see,
Just connect the name of the color from gray to green, no open database list down,
Right connection name - & gt; To create a new query, this time will pop up a query window, the window to write SQL can be successfully executed (database is connected the success),
But why can't see the database list?

Another is sharding - log on the proxy server is always in the following two mistakes,
Haven't done for a long time, not many shrding - proxy information,
Trouble you to help adults see, thank you very much,

error:
Java. Lang. IllegalArgumentException: always find a JDBC type '2003' in PostgreSQL column type
The at org. Apache. Shardingsphere. Shardingproxy. Transport. Postgresql. Constant. PostgreSQLColumnType. ValueOfJDBCType (PostgreSQLColumnType. Java: 187)
At org.apache.shardingsphere.shardingproxy.transport.postgresql.packet.com, mand. Query. PostgreSQLColumnDescription. & lt; init> (PostgreSQLColumnDescription. Java: 48)
At org.apache.shardingsphere.shardingproxy.frontend.postgresql.com, mand. Query. Text. PostgreSQLComQueryExecutor. GetPostgreSQLColumnDescriptions (PostgreSQLComQueryExecutor. Java: 100)
At org.apache.shardingsphere.shardingproxy.frontend.postgresql.com, mand. Query. Text. PostgreSQLComQueryExecutor. CreateQueryPacket (PostgreSQLComQueryExecutor. Java: 88)
At org.apache.shardingsphere.shardingproxy.frontend.postgresql.com mand. Query. Text. PostgreSQLComQueryExecutor. Execute (PostgreSQLComQueryExecutor. Java: 75)
The at org.apache.shardingsphere.shardingproxy.frontend.command.Com mandExecutorTask. ExecuteCommand (CommandExecutorTask. Java: 92)
The at org.apache.shardingsphere.shardingproxy.frontend.command.Com mandExecutorTask. Run (CommandExecutorTask. Java: 72)
The at Java. Util. Concurrent. ThreadPoolExecutor. RunWorker (ThreadPoolExecutor. Java: 1142)
The at Java. Util. Concurrent. ThreadPoolExecutor $Worker. The run (ThreadPoolExecutor. Java: 617)
The at Java. Lang. Thread. The run (Thread. Java: 745)

error:
CONSOLE_LOG_PATTERN_IS_UNDEFINEDorg postgresql. Util. PSQLException: The server 's client_encoding parameter was changed to UNICODE. The JDBC driver requires client_encoding to be UTF8 for correct operation.
The at org. Postgresql. Core. The v3. QueryExecutorImpl. ReceiveParameterStatus (QueryExecutorImpl. Java: 2604)
The at org. Postgresql. Core. The v3. QueryExecutorImpl. ProcessResults (QueryExecutorImpl. Java: 2219)
The at org. Postgresql. Core. The v3. QueryExecutorImpl. Execute (QueryExecutorImpl. Java: 308)
The at org. Postgresql. JDBC. PgStatement. ExecuteInternal (PgStatement. Java: 441)
The at org. Postgresql. JDBC. PgStatement. Execute (PgStatement. Java: 365)
The at org. Postgresql. JDBC. PgStatement. ExecuteWithFlags (PgStatement. Java: 307)
The at org. Postgresql. JDBC. PgStatement. ExecuteCachedSql (PgStatement. Java: 293)
The at org. Postgresql. JDBC. PgStatement. ExecuteWithFlags (PgStatement. Java: 270)
The at org. Postgresql. JDBC. PgStatement. Execute (PgStatement. Java: 266)
The at org. Postgresql. JDBC. PgStatement. Execute (PgStatement. Java: 1168)
At com. Zaxxer. Hikari. Pool. ProxyStatement. Execute (ProxyStatement. Java: 103)
At com. Zaxxer. Hikari. Pool. HikariProxyStatement. Execute (HikariProxyStatement. Java)

CodePudding user response:

Routing with the first one is wrong, the second problem is the code that a client connection problems, set the tone for utf-8 can,

CodePudding user response:

reference 1st floor licyclone001 response:
routing with the first one is wrong, the second problem is the code that a client connection problems, set the tone for utf-8 can,


Hello,
You speak of these two aspects I probably know, the key is not clear how to solve,
Trouble can give a detailed solution?
For example, the routing configuration is wrong, then how should match, modify which configuration files?

thank you

CodePudding user response:

Problem solved? I also met the same problem, two easy to solve problems, mainly is a problem, I look at the 2003 represents an array, but useless data at the array type
  • Related