我的书签
添加书签
移除书签5-39 - Error occurred with Dubbo Config Bean Initializer
本页为目录页，无正文内容；下属章节见左侧目录。
5-39 - Error occurred with Dubbo Config Bean Initializer
- Introduction
- Concepts and Architecture
- Relationship with gRPC, Spring Cloud, Istio
- Core Advantages
- Features
- User Manual
- Java SDK
- Version Information
- Quick Start
- User Guide
- Quickly Create Applications
- Communication Protocol
- Observability Service
- Service Discovery
- Package and Deploy
- Traffic Control
- Custom Extensions
- Custom Extensions
- RPC Framework
- Server and Client
- Thread Model
- Asynchronous Call
- Filter Interceptor
- Timeout Duration
- Version and Group
- Passing Additional Parameters
- Cluster Fault Tolerance (Retry)
- Generic Call
- More features
- Generic Implementation
- Echo Testing
- Dynamically Specify IP Call at Runtime
- Direct Connection Provider
- Event Notifications Triggered by Calls
- Server Callback to Client
- Service Downgrade
- Local Stub
- Local Call
- Concurrency Control
- Connection Control
- Host Configuration
- Result Cache Invocation
- Route Status Collection
- Service Reference Configuration Object Cache
- Parameter Validation
- Reactive Programming
- Distributed Transactions
- HTTP Gateway Access
- Rate Limiting and Degradation
- Security Policy
- Troubleshooting
- Reference Manual
- Configuration Instructions
- Serialization Protocol
- RPC Protocol
- Registry Center and Service Discovery
- Configuration Center
- Metadata Center
- Performance Benchmark
- GraalVM
- SPI Plugin Extension Points
- SPI Overview
- SPI Plugin List
- Some Key SPI Usage Instructions
- Protocol Extension
- Call Interceptor Extension
- Invoker Listener Extension
- Export Listener Extension
- Cluster extension
- Router Extensions
- Load Balance Extension
- Merger Result Extension
- Registry Center Extension
- Monitoring Center Extension
- Extension Point Loading Extensions
- Dynamic Proxy Extension
- Liveness Probe
- Readiness Probe
- Startup Probe
- Compiler Extension
- Configuration Center Extension
- Metadata Center Extension
- Message Dispatch Extension
- Thread Pool Extension
- Serialization Extension
- Serialization Extension
- Network Transport Extension
- Information Exchange Extension
- Networking Extension
- Peer-to-peer network node aggregator extension
- Telnet Command Extension
- Status Check Extension
- Container Extension
- Cache Extension
- Validation Extension
- Logger Adapter Extension
- Logger Adapter Extension
- QoS Anonymous Access Permission Verification Extension
- Routing Rules
- 5-6 - Attribute conflict of interface types
- 5-8 - The protocol will use a randomly available port
- 5-16 - Unable to find any valid protocol
- 5-25 - Custom implementation causes undefined exceptions
- 5-36 - Error occurred during filter validation
- 6-12 - Error occurring during ZK client destruction
- 6-13 - Stream Closed Exception
- Standalone Operation Commands (QOS)
- Source Code Architecture
- Error Code FAQ
- 0 - Common Layer
- 0-1 - Thread Pool Resource Exhaustion
- 0-2 - Illegal Property Value
- 0-3 - Unable to access cache path
- 0-4 - Cache Entry Limit Exceeded
- 0-5 - Cache file size exceeded
- 0-6 - Thread Interruption Exception
- 0-7 - Reflection class not found
- 0-8 - Reflection Failure
- 0-9 - Notification event failure
- 0-10 - Current call is not supported
- 0-11 - Service Stopping Failed
- 0-12 - Unknown Exception
- 0-13 - An exception occurs in the metrics collector
- 0-14 - Monitoring Exceptions
- 0-15 - Exception Occurred When Loading Extension Class
- 0-16 - No available executor
- 0-17 - An unknown exception occurs when the executor is shutting down
- 0-18 - Thread pool executor is misused
- 0-19 - Exception Occurred While Processing Task
- 0-20 - Exception occurs when storing stack information
- 0-21 - Too many instances are built
- 0-22 - Input and Output Stream Exception
- 0-23 - Serialization data conversion exception
- 0-24 - Exception of Overriding Field Values
- 0-25 - Load Mapping Error
- 0-26 - Warning message when publishing metadata service
- 0-27 - Thread Pool Isolation Configuration Exception
- 0-28 - Dangerous Actions
- 0-29 - Tracer dependency not found
- 0-99 - Called a Deprecated Method
- 1 - Registry Center Layer
- 1-1 - Invalid Address
- 1-3 - URL destruction failure
- 1-4 - Empty Address
- 1-5 - Received URL with no parameters
- 1-6 - Error clearing URL cache
- 1-7 - Failed to read and write the service cache of the registry
- 1-8 - Failure to unregister (unsubscribe) address during destruction
- 1-9 - Failure to read and write the registry service cache
- 1-10 - Failed to read and write the service cache of the registry
- 1-11 - Service instance registration failure
- 1-12 - Instances of “Registered Service” have been destroyed
- 1-13 - Failed to execute retry task
- 1-14 - Dynamic Configuration Recognition Failure
- 1-15 - Service destruction failed
- 1-16 - Unsupported categories exist
- 1-17 - metadata Server failure
- 1-18 - Metadata service port not provided
- 1-19 - K8S Listener Exception
- 1-20 - K8S Pod does not exist
- 1-21 - No available services in K8S
- 1-22 - Incorrect K8S configuration address
- 1-26 - xDS Certificate Generation Failure
- 1-27 - K8S Listening Exception
- 1-28 - xDS Stub Error
- 1-29 - xDS File Read Failed
- 1-30 - xDS Request Failed
- 1-31 - xDS Response Failure
- 1-32 - xDS Channel initialization failure
- 1-33 - xDS service discovery initialization failure
- 1-34 - Error occurred while parsing xDS
- 1-35 - ZK Exception
- 1-36 - Unknown Exception
- 1-37 - Nacos Exception
- 1-38 - Socket Connection Exception
- 1-39 - Failed to retrieve metadata
- 1-40 - Route waiting time is too long
- 1-41 - Istio Exception
- 1-42 - Low Version Services Exist in Nacos
- 2 - Routing Layer
- 2-1 - Routing selection execution failed
- 2-2 - No Available Provider (Address Not Found)
- 2-3 - Route shutdown failure
- 2-4 - Merger interface loading failure
- 2-5 - Filtering Provider Failure
- 2-6 - The list of providers filtered by conditional routing is empty
- 2-7 - Condition Routing Execution Exception
- 2-8 - Provider Returns Exception Response
- 2-9 - Timeout check task failure
- 2-10 - Failure to call the service provider
- 2-11 - Invalid Tag Routing Rule
- 2-12 - The provider application name is empty when using tag routing
- 2-13 - Failed to receive loading mesh routing rules
- 2-14 - Script routing execution failed
- 2-15 - Route rule parsing failed
- 2-16 - Request retry failed multiple times
- 2-17 - mock request failure
- 2-18 - Mesh routing rules not being listened to
- 2-19 - Asynchronous Request Failure
- 2-20 - Failed to Merge Group Result
- 3 - Dynamic Proxy Layer
- 3-1 - Failed to convert the address into Invoker
- 3-2 - Failed to publish or push service
- 3-3 - Failure to generate bytecode through Javassist
- 3-4 - Client request timeout
- 3-5 - Asynchronous response raises exceptions
- 3-6 - Proxy execution service encountered an exception
- 3-7 - Server response result timeout
- 3-8 - Proxy Failure
- 4 - Protocol Layer
- 4-1 - Unsupported Protocol
- 4-2 - An Initial Error Occurred for the Serialization Optimizer
- 4-3 - Interface reference call failed
- 4-4 - Unsafe Serialization Method
- 4-5 - Stream Closure Exception
- 4-6 - Deserialization Failure
- 4-7 - Error Occurred When Closing Client
- 4-8 - Error occurred when shutting down the server
- 4-9 - Parsing Failed
- 4-10 - Triple serialization result failure
- 4-11 - Request initiation failed
- 4-12 - Failed to create Triple stream
- 4-13 - Server Timeout
- 4-14 - Response Result Failure
- 4-15 - Client Stream Listener
- 4-16 - Service is closed
- 4-17 - Errors occur when shutting down all callers
- 4-18 - Unable to obtain service model from the call
- 4-19 - Possible errors in parameter values
- 4-20 - Data Decoding Failure
- 4-21 - Unsafe serialization data detected
- 5 - Configuration (Central) Layer
- 5-1 - Configuration Center Connection Failure
- 5-2 - Failure in Registering/Unregistering Shutdown Hook Methods
- 5-3 - An unexpected error occurs when destroying method calls
- 5-4 - Method not found in service interface
- 5-5 - Unable to get env variable
- 5-6 - Attribute conflict of interface types
- 5-7 - Unexpected error occurred while canceling export
- 5-7 - Unexpected error occurred while canceling export
- 5-8 - The protocol will use a randomly available port
- 5-9 - Service configuration export failed
- 5-9 - Service configuration export failed
- 5-10 - Service registration interface application mapping failed
- 5-11 - Registration Instance Error
- 5-12 - Refresh instance and metadata error
- 5-12 - Refresh instance and metadata error
- 5-13 - Unable to Destroy Model
- 5-14 - Model startup error
- 5-14 - Model startup error
- 5-15 - Model Reference Error
- 5-15 - Model Reference Error
- 5-16 - Unable to find any valid protocol
- 5-17 - Parameter Value Format Error
- 5-17 - Parameter Value Format Error
- 5-18 - Notification Registration Event Failed
- 5-18 - Notification Registration Event Failed
- 5-20 - Error occurred when stopping the dubbo module
- 5-20 - Error occurred when stopping the dubbo module
- 5-21 - Exception occurred when destroying the service
- 5-21 - Exception occurred when destroying the service
- 5-22 - An error occurred when initializing the registry
- 5-23 - Waiting for export/reference service to encounter an exception
- 5-24 - Asynchronous waiting for service reference exceptions
- 5-25 - Custom implementation causes undefined exceptions
- 5-26 - Metadata has been exported
- 5-27 - Incorrect usage of internal class API
- 5-27 - Incorrect usage of internal class API
- 5-28 - No available annotations found
- 5-28 - No available annotations found
- 5-29 - Scan package not configured
- 5-29 - Scan package not configured
- 5-30 - Duplicate Bean Definition Declaration
- 5-31 - Status Check Error
- 5-32 - Error Occurred When Apollo Disconnected
- 5-33 - Exception Occurred During Apollo Configuration Update Event
- 5-34 - Error Occurred in NACOS
- 5-35 - Container initialization failure
- 5-36 - Error occurred during filter validation
- 5-37 - Dynamic configuration listener processing error
- 5-37 - Dynamic configuration listener processing error
- 5-38 - Configuration parameter undefined
- 5-39 - Error occurred with Dubbo Config Bean Initializer
- 5-40 - Dubbo configuration bean not found
- 5-41 - Failed to Read SSL Certificate
- 5-42 - Dubbo Certificate Issuance Failure
- 5-43 - Dubbo certificate issuance connection is insecure
- 6 - Network Transport Layer
- 6-1 - Server Connection Failure
- 6-2 - Client Timeout
- 6-3 - Network connection closure failure
- 6-4 - Unknown Exception in Network Communication Layer
- 6-5 - Network disconnection failure
- 6-6 - Unsupported Message
- 6-7 - Server connection failure
- 6-8 - Failed to decode return data
- 6-9 - Server Connection Failure
- 6-10 - Payload Limit Exceeded Exception
- 6-11 - Character set not supported
- 6-12 - Error occurring during ZK client destruction
- 6-13 - Stream Closed Exception
- 6-14 - Server response failure
- 6-15 - Skip unread stream data
- 6-16 - Exception Occurred During Reconnection
- 7 - QoS Plugin Module
- 7-1 - QOS is Closed
- 7-2 - QOS is enabled
- 7-3 - Set the warning percentage value for timeout
- 7-4 - QOS Service Startup Failure
- 7-5 - QOS command not found
- 7-6 - QOS encountered an unknown exception
- 7-7 - QOS Unauthorized Access
- 81 - Unit Test Helper Module (Registry)
- 81-1 - ZK Startup Exception
- 81-2 - ZK Destruction Exception
- 81-3 - Unable to download file via URL
- 81-4 - Embedded ZooKeeper Runtime Exception
- 99 - Other Unknown Errors
- 99-0 - Internal Unknown Error
- 99-1 - Program Interrupted
- Introduction to the error code mechanism
- Upgrades and Compatibility
- Golang SDK
- Node.js SDK
- Web SDK
- Python SDK
- Rust SDK
- Control Panel
- Java SDK
- Architecture and Installation
- Document Query
- Others
- Metrics
- Integration Adaptation
- Proposals
- Protocol Specifications
- Erlang SDK
- Pixiu gateway
- Getting Started Overview
- User Documentation
- Developer Guide
- Security Announcements
暂无相关搜索结果！
本文档使用 WanXiangYunDang 构建
