You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/10/26 09:45:48 UTC

[GitHub] [shardingsphere] strongduanmu opened a new issue, #21769: ServiceProviderNotFoundServerException occurs when I configure mysql as protocol type and oracle as storage type

strongduanmu opened a new issue, #21769:
URL: https://github.com/apache/shardingsphere/issues/21769

   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
   
   [66f346e](https://github.com/apache/shardingsphere/commit/66f346e1911f44e45469160938d870fcdb936d81)
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   
   ShardingSphere-Proxy
   
   ### Expected behavior
   
   ShardingSphere-Proxy start successfully.
   
   ### Actual behavior
   
   ```
   Thanks for using Atomikos! This installation is not registered yet. 
   REGISTER FOR FREE at http://www.atomikos.com/Main/RegisterYourDownload and receive:
   - tips & advice 
   - working demos 
   - access to the full documentation 
   - special exclusive bonus offers not available to others 
   - everything you need to get the most out of using Atomikos!
   Exception in thread "main" org.apache.shardingsphere.infra.util.spi.exception.ServiceProviderNotFoundServerException: SPI-00001: No implementation class load from SPI `org.apache.shardingsphere.proxy.frontend.spi.DatabaseProtocolFrontendEngine` with type `Oracle`.
   	at org.apache.shardingsphere.infra.util.spi.type.typed.TypedSPIRegistry.getRegisteredService(TypedSPIRegistry.java:117)
   	at org.apache.shardingsphere.proxy.frontend.protocol.DatabaseProtocolFrontendEngineFactory.newInstance(DatabaseProtocolFrontendEngineFactory.java:46)
   	at org.apache.shardingsphere.proxy.version.ShardingSphereProxyVersion.setDatabaseVersion(ShardingSphereProxyVersion.java:70)
   	at org.apache.shardingsphere.proxy.version.ShardingSphereProxyVersion.lambda$setVersion$0(ShardingSphereProxyVersion.java:49)
   	at java.util.concurrent.ConcurrentHashMap$KeySetView.forEach(ConcurrentHashMap.java:4649)
   	at org.apache.shardingsphere.proxy.version.ShardingSphereProxyVersion.setVersion(ShardingSphereProxyVersion.java:49)
   	at org.apache.shardingsphere.proxy.initializer.BootstrapInitializer.init(BootstrapInitializer.java:61)
   	at org.apache.shardingsphere.proxy.Bootstrap.main(Bootstrap.java:52)
   Disconnected from the target VM, address: '127.0.0.1:62837', transport: 'socket'
   
   Process finished with exit code 1
   ```
   
   ### Reason analyze (If you can)
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   
   `server.yaml`:
   
   ```yaml
   mode:
     type: Cluster
     repository:
       type: ZooKeeper
       props:
         namespace: governance_ds
         server-lists: localhost:2181
         retryIntervalMilliseconds: 500
         timeToLiveSeconds: 60
         maxRetries: 3
         operationTimeoutMilliseconds: 500
   
   authority:
     users:
       - user: root@%
         password: root
       - user: sharding
         password: sharding
     privilege:
       type: ALL_PERMITTED
   
   rules:
     - !TRANSACTION
       defaultType: XA
       providerType: Atomikos
     - !SQL_PARSER
       sqlCommentParseEnabled: true
       sqlStatementCache:
         initialCapacity: 2000
         maximumSize: 65535
       parseTreeCache:
         initialCapacity: 128
         maximumSize: 1024
   
   props:
     max-connections-size-per-query: 1
     kernel-executor-size: 16  # Infinite by default.
     proxy-frontend-flush-threshold: 128  # The default value is 128.
     proxy-hint-enabled: false
     sql-show: true
     check-table-metadata-enabled: false
       # Proxy backend query fetch size. A larger value may increase the memory usage of ShardingSphere Proxy.
       # The default value is -1, which means set the minimum value for different JDBC drivers.
     proxy-backend-query-fetch-size: -1
     proxy-frontend-executor-size: 0 # Proxy frontend executor size. The default value is 0, which means let Netty decide.
       # Available options of proxy backend executor suitable: OLAP(default), OLTP. The OLTP option may reduce time cost of writing packets to client, but it may increase the latency of SQL execution
       # and block other clients if client connections are more than `proxy-frontend-executor-size`, especially executing slow SQL.
     proxy-backend-executor-suitable: OLAP
     proxy-frontend-max-connections: 0 # Less than or equal to 0 means no limitation.
       # Available sql federation type: NONE (default), ORIGINAL, ADVANCED
     sql-federation-type: NONE
       # Available proxy backend driver type: JDBC (default), ExperimentalVertx
     proxy-backend-driver-type: JDBC
     proxy-mysql-default-version: 5.7.22 # In the absence of schema name, the default version will be used.
     proxy-default-port: 3307 # Proxy default port.
     proxy-netty-backlog: 1024 # Proxy netty backlog.
     proxy-frontend-database-protocol-type: MySQL
   ```
   
   `config-sharding.yaml`:
   
   ```yaml
   databaseName: sharding_db
   
   dataSources:
     ds_0:
       url: jdbc:oracle:thin:@localhost:1521:XE
       username: TEST
       password: 123456
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
       minPoolSize: 1
     ds_1:
       url: jdbc:mysql://127.0.0.1:3306/demo_ds_1?serverTimezone=UTC&useSSL=false
       username: root
       password: 123456
       connectionTimeoutMilliseconds: 30000
       idleTimeoutMilliseconds: 60000
       maxLifetimeMilliseconds: 1800000
       maxPoolSize: 50
       minPoolSize: 1
   
   rules:
   - !SHARDING
     tables:
       t_order:
         actualDataNodes: ds_${0..1}.t_order_${0..1}
         tableStrategy:
           standard:
             shardingColumn: order_id
             shardingAlgorithmName: t_order_inline
         keyGenerateStrategy:
           column: order_id
           keyGeneratorName: snowflake
       t_order_item:
         actualDataNodes: ds_${0..1}.t_order_item_${0..1}
         tableStrategy:
           standard:
             shardingColumn: order_id
             shardingAlgorithmName: t_order_item_inline
         keyGenerateStrategy:
           column: order_item_id
           keyGeneratorName: snowflake
     bindingTables:
       - t_order,t_order_item
     defaultDatabaseStrategy:
       standard:
         shardingColumn: user_id
         shardingAlgorithmName: database_inline
     defaultTableStrategy:
       none:
   
     shardingAlgorithms:
       database_inline:
         type: INLINE
         props:
           algorithm-expression: ds_${user_id % 2}
       t_order_inline:
         type: INLINE
         props:
           algorithm-expression: t_order_${order_id % 2}
       t_order_item_inline:
         type: INLINE
         props:
           algorithm-expression: t_order_item_${order_id % 2}
   
     keyGenerators:
       snowflake:
         type: SNOWFLAKE
   ```
   
   ### Example codes for reproduce this issue (such as a github link).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [shardingsphere] TeslaCN closed issue #21769: ServiceProviderNotFoundServerException occurs when I configure mysql as protocol type and oracle as storage type

Posted by GitBox <gi...@apache.org>.
TeslaCN closed issue #21769: ServiceProviderNotFoundServerException occurs when I configure mysql as protocol type and oracle as storage type
URL: https://github.com/apache/shardingsphere/issues/21769


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org