status
stringclasses 1
value | repo_name
stringlengths 9
24
| repo_url
stringlengths 28
43
| issue_id
int64 1
104k
| updated_files
stringlengths 8
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 37
56
| pull_url
stringlengths 37
54
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
timestamp[ns, tz=UTC] | language
stringclasses 5
values | commit_datetime
timestamp[us, tz=UTC] |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | apache/dubbo | https://github.com/apache/dubbo | 3,057 | ["dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/command/impl/Ls.java", "dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/server/DubboLogo.java", "dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/textui/TKv.java", "dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/textui/TLadder.java", "dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/textui/TTable.java", "dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/textui/TTree.java"] | qos控制台在windows下界面是乱的 |
| https://github.com/apache/dubbo/issues/3057 | https://github.com/apache/dubbo/pull/3058 | 7d3c6bc0aa379d05013172f11e38c0b301049b41 | 77891b4dc13ef73c161950b555cfeecfab71bcba | 2018-12-25T08:41:05Z | java | 2018-12-26T02:25:42Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 3,011 | ["dubbo-dependencies-bom/pom.xml"] | Added UT for ActiveLimitFilter and GenericFilter | Added UT for
1. ActiveLimitFilter
2. GenericFilter
| https://github.com/apache/dubbo/issues/3011 | https://github.com/apache/dubbo/pull/10324 | 807fc1220382aa962523476d54080791493dedab | 71c6e604f0a6bdc3daa4121723b7dce1987ec269 | 2018-12-18T18:20:41Z | java | 2022-07-15T08:30:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 3,005 | ["dubbo-dependencies-bom/pom.xml"] | 2.6.2版本的filter | - [ ] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [ ] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: xxx
* Operating System version: xxx
* Java version: xxx
### Steps to reproduce this issue
1. xxx
2. xxx
3. xxx
Pls. provide [GitHub address] to reproduce this issue.
### Expected Result
What do you expected from the above steps？
### Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
```
Just put your stack trace here!
```
| https://github.com/apache/dubbo/issues/3005 | https://github.com/apache/dubbo/pull/10324 | 807fc1220382aa962523476d54080791493dedab | 71c6e604f0a6bdc3daa4121723b7dce1987ec269 | 2018-12-18T10:30:03Z | java | 2022-07-15T08:30:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,994 | ["dubbo-dependencies-bom/pom.xml"] | Enhance the java doc of dubbo-container module. | Enhance the java doc of dubbo-container module.
Related project: https://github.com/apache/incubator-dubbo/projects/2 | https://github.com/apache/dubbo/issues/2994 | https://github.com/apache/dubbo/pull/10324 | 807fc1220382aa962523476d54080791493dedab | 71c6e604f0a6bdc3daa4121723b7dce1987ec269 | 2018-12-18T04:44:09Z | java | 2022-07-15T08:30:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,992 | ["dubbo-dependencies-bom/pom.xml"] | Enhance the java doc of dubbo-common module. | Enhance the java doc of dubbo-common module.
Related project: https://github.com/apache/incubator-dubbo/projects/2 | https://github.com/apache/dubbo/issues/2992 | https://github.com/apache/dubbo/pull/10324 | 807fc1220382aa962523476d54080791493dedab | 71c6e604f0a6bdc3daa4121723b7dce1987ec269 | 2018-12-18T04:42:49Z | java | 2022-07-15T08:30:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,991 | ["dubbo-dependencies-bom/pom.xml"] | Enhance the java doc of dubbo-cluster module | Enhance the java doc of dubbo-cluster module.
Related project: https://github.com/apache/incubator-dubbo/projects/2 | https://github.com/apache/dubbo/issues/2991 | https://github.com/apache/dubbo/pull/10324 | 807fc1220382aa962523476d54080791493dedab | 71c6e604f0a6bdc3daa4121723b7dce1987ec269 | 2018-12-18T04:41:42Z | java | 2022-07-15T08:30:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,990 | ["dubbo-dependencies-bom/pom.xml", "dubbo-metadata/dubbo-metadata-report-redis/pom.xml"] | Dubbo Service 的方法名不允许有下划线等字符，此限制是否必要 | 
| https://github.com/apache/dubbo/issues/2990 | https://github.com/apache/dubbo/pull/11379 | 95e583ed7f8f9014cfc374b1ce81e46872c8b8b6 | 10030010a65d3f1fb30d3dd3b23d572dc645a500 | 2018-12-18T03:35:14Z | java | 2023-01-28T03:26:23Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,977 | ["dubbo-rpc/dubbo-rpc-dubbo/src/main/java/org/apache/dubbo/rpc/protocol/dubbo/DubboCodec.java"] | DubboCodec re-implements Codec2 |
### Environment
* Dubbo version: 2.7.0-SNAPSHOT
* Operating System version: xxx
* Java version: xxx
### Steps to reproduce this issue
DubboCodec extends from ExchangeCodec, which already implements codec2, but DubboCodec still re-implements codec2, and it makes me confused. Is this designed specifically？
| https://github.com/apache/dubbo/issues/2977 | https://github.com/apache/dubbo/pull/3547 | e1cb03bac5d295c3e1140a02fccd5a8c7384cec9 | 8c934c9c8bb979a731f02638bdb7c1641d70bf73 | 2018-12-16T12:10:12Z | java | 2019-03-01T17:27:16Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,910 | ["dubbo-dependencies-bom/pom.xml"] | [2.7.0-development docs] Background | ## 总体目标
在2.7.0版本中，Dubbo提出了将注册中心和服务治理中心分离的思想，概念上向时下流行的微服务注册中心、配置中心模型看齐。同时在此基础上，2.7.0版本又额外引入了一个元数据中心，通过更丰富的元数据内容进一步提高服务治理能力。
从每个中心的职责划分的角度，我们期望带来的好处是：
- 注册中心。通过裁剪冗余的URL数据，减轻配置中心的存储和推送压力
- 配置中心。让开发者可以对接微服务场景下更常用的、更专业的配置中心，如Nacos, Apollo, Consul, Etcd等。如果按不同的生命周期阶段划分，配置中心在Dubbo中承担了如下几个角色。
- 启动阶段的配置管控。类似Spring Cloud Config实现External Configuration管控。
- 运行期的服务治理。从2.6及之前版本的注册中心中剥离出来的服务治理能力，运行期存储并推送各种覆盖规则、路由规则等
- 运行期的配置变更读取。Dubbo的一些，目前框架内仅在非核心的RPC链路上读取，如启动销毁阶段，并且开放给用户使用。
- 元数据中心。尽可能多的注册服务的元数据到此中心，例如方法名列表、方法签名、方法参数类型定义等，为实现服务测试、mock提供可能，这部分的存储实现将是可扩展的，包括zookeeper, redis等。
## 工作原理
以Dubbo应用的生命周期描述，对比之前单注册中心的工作模式，Dubbo的工作流程如下：
## 示例说明
平时在Dubbo中我们接触最多的就是一长串的URL，接下来，我们就以一个简单URL为例来说明2.7版本带来的变化。
### 典型URL
以下是一个典型的Dubbo注册中心URL（2.6及以前版本）
> dubbo://ip:port/org.apache.dubbo.compose.ic.service.vas.ValueAddServiceCompose?anyhost=true&application=dubbo-demo&default.actives=400&default.delay=-1&default.dispatcher=all&default.group=online&default.loadbalance=leastactive&default.service.filter=-monitor&default.threads=400&default.timeout=2000&default.version=1.0&delay=1&dubbo=3.0.5.1&environment=product&interface= org.apache.dubbo.compose.ic.service.vas.ValueAddServiceCompose&logger=slf4j&methods=queryValueAddServiceEditVOs,auditPassByValueAddServiceIdList,getValueAddServiceVOByServiceIds,getValueAddServiceInfoByGoodsIdList,getRuleMatchVOByGoodsIdList,getValueAddServiceEditVOById,getValueAddServiceEditVOByIds,queryValueAddServiceVOs,disableValueAddService,auditRejectByValueAddServiceIdList,saveValueAddServiceEditVO,enableValueAddService&organization=dubbo-demo&owner=John&pid=54812&revision=1.0.0&sentry_target_cluster_name=dubbo-demo-test&side=provider×tamp=1530671441040
在一些企业的大规模实践的基础上，我们逐渐发现这样组织的注册中心URL存在一些问题：
- 注册中心存储的URL过长，导致存储压力骤增，变更事件的推送效率明显下降；同时给订阅方带来了额外的计算压力，尤其是大规模实例场景下的内存增长显著。
- 注册中心承担了过多服务治理配置的功能：负责初始配置的同步，同时负责存储各种运行期配置规则。这一方面加剧了注册中心的压力，另一方面配置规则的灵活性也受到了一定的限制，同时也无法利用一些更专业的微服务配置中心带来的强大功能。
- 服务的元数据过于简略，如我们只有methods, pid, owner等，但为更详细的了解服务状态，我们需要尽可能多的属性，尽可能丰富的服务元数据。以methods为例，虽然方法列表的内容已经很长了，但当我们要在OPS开发服务测试/mock功能时，却发现需要的方法签名等数据还是无法获取。
### 按作用拆分
对应以上问题，我们先简单的将URL中的内容划分为3部分：
1. Endpoint地址
dubbo://ip:port/org.apache.dubbo.compose.ic.service.vas.ValueAddServiceCompose
2. 需要同步或治理的服务数据default.actives=400&default.delay=-1&default.dispatcher=all&default.group=online&default.loadbalance=leastactive&default.service.filter=-monitor&default.threads=400&default.timeout=2000
3. 服务查询、监控需要的元数据methods=queryValueAddServiceEditVOs,auditPassByValueAddServiceIdList,getValueAddServiceVOByServiceIds,getValueAddServiceInfoByGoodsIdList,getRuleMatchVOByGoodsIdList,getValueAddServiceEditVOById,getValueAddServiceEditVOByIds,queryValueAddServiceVOs,disableValueAddService,auditRejectByValueAddServiceIdList,saveValueAddServiceEditVO,enableValueAddService&organization=dubbo-demo&owner=John&pid=54812&revision=1.0.0&sentry_target_cluster_name=dubbo-demo-test
### 映射到3个中心
对于第1部分，是服务自动发现的核心，我们还是继续要通过注册中心来实现同步，同时鉴于Dubbo当前基于服务粒度的服务发现模型，第2部分中部分内容我们也将在2.7.0的URL中仍继续保留，一方面是为向前保持兼容性，另一方面也是为服务治理提供最大的可能性，所以最终我们发送到注册中心的数据格式是：
> dubbo://ip:port/org.apache.dubbo.compose.ic.service.vas.ValueAddServiceCompose?group=online&timeout=2000
对于第2部分的数据，也是Dubbo的动态配置覆盖规则关注的部分，2.7.0开始，我们将覆盖规则下发到配置中心，由配置中心负责规则的推送，同时定义了更灵活的、多维度的覆盖规则格式：
```yaml
---
apiVersion: v2.7
scope: application/service
key: governance-appoverride-provider/group+service+version
enabled: true
configs:
- addresses: ["0.0.0.0"] # must not contain port when works on consumer side
providerAddresses: ["1.1.1.1:20880", "2.2.2.2:20881"] # must contain port
applications/services: []
parameters:
timeout: 1000
cluster: failfase
loadbalance: random
- addresses: ["0.0.0.0:20880"] # must contain port when works on provider side, specify multiple addresses if you want to apply to multiple ports.
applications/services: []
parameters:
threadpool: fixed
threads: 200
iothreads: 4
dispatcher: all
queues: 0
weight: 200
...
```
最后，服务查询和监控数据，2.7.0的原则是尽可能的予以丰富，所以在保留第3部分全部数据的基础上，又增加了服务方法签名的元数据：
```text
``` | https://github.com/apache/dubbo/issues/2910 | https://github.com/apache/dubbo/pull/10324 | 807fc1220382aa962523476d54080791493dedab | 71c6e604f0a6bdc3daa4121723b7dce1987ec269 | 2018-12-07T09:15:22Z | java | 2022-07-15T08:30:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,864 | ["pom.xml"] | Build failed with -Prelease | - [x] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [x] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: master branch
* Operating System version: macos
* Java version: java11
### Steps to reproduce this issue
1. `./mvnw package -DskipTests -Pjava8-vm-args -Prelease`
### Expected Result
build success
### Actual Result
build failed
If there is an exception, please attach the exception trace:
```
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadoc) on project dubbo: MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - /Users/xxx/Documents/incubator-dubbo/dubbo-common/src/main/java/org/apache/dubbo/common/logger/log4j2/Log4j2LoggerAdapter.java:23: error: package org.apache.logging.log4j does not exist
[ERROR] import org.apache.logging.log4j.LogManager;
[ERROR] ^
[ERROR] /Users/xxx/Documents/incubator-dubbo/dubbo-common/src/main/java/org/apache/dubbo/common/logger/log4j2/Log4j2LoggerAdapter.java:35: error: package org.apache.logging.log4j does not exist
[ERROR] private static org.apache.logging.log4j.Level toLog4j2Level(Level level) {
[ERROR] ^
[ERROR] /Users/xxx/Documents/incubator-dubbo/dubbo-common/src/main/java/org/apache/dubbo/common/logger/log4j2/Log4j2LoggerAdapter.java:57: error: package org.apache.logging.log4j does not exist
[ERROR] private static Level fromLog4j2Level(org.apache.logging.log4j.Level level) {
[ERROR] ^
[ERROR] /Users/xxx/Documents/incubator-dubbo/dubbo-common/src/main/java/org/apache/dubbo/common/logger/log4j2/Log4j2Logger.java:23: error: package org.apache.logging.log4j does not exist
[ERROR] private final org.apache.logging.log4j.Logger logger;
[ERROR] ^
[ERROR] /Users/xxx/Documents/incubator-dubbo/dubbo-common/src/main/java/org/apache/dubbo/common/logger/log4j2/Log4j2Logger.java:25: error: package org.apache.logging.log4j does not exist
[ERROR] public Log4j2Logger(org.apache.logging.log4j.Logger logger) {
[ERROR] ^
[ERROR]
[ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/bin/javadoc @options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/Users/xxx/Documents/incubator-dubbo/dubbo-all/target/apidocs' dir.
[ERROR]
[ERROR] -> [Help 1]
```
### Solution
`log4j-core` was defined in `dubbo-common/pom.xml` as `provied`
change to default scope `compile`
| https://github.com/apache/dubbo/issues/2864 | https://github.com/apache/dubbo/pull/2923 | e508ad467f94e853885fdf47a74d312eb5c6001b | a03d4877a54d8474d351f9e355d42affef7f73c0 | 2018-12-02T08:55:24Z | java | 2018-12-11T02:33:03Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,850 | ["dubbo-cluster/src/main/java/org/apache/dubbo/rpc/cluster/directory/AbstractDirectory.java"] | consumer stub logic don't run when config multi registries | - [x] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [x] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: 2.6.5
* Operating System version: Windows 7
* Java version: 1.8.0_31
### Steps to reproduce this issue
1. API的方式配置两个registry地址，例如： registryConfig.setAddress("127.0.0.1:2181|127.0.0.1:2182")。
2. API的方式配置ReferenceConfig按照文档配置stub，例如： referenceConfig.setStub("com.liupeng.dubbo.api.MyStub")。
3.API的方式启动consumer。
Pls. provide [GitHub address] to reproduce this issue.
### Expected Result
What do you expected from the above steps？
### Actual Result
What actually happens?
If there is an exception, please attach the exception trace:
```
Just put your stack trace here!
```
| https://github.com/apache/dubbo/issues/2850 | https://github.com/apache/dubbo/pull/2887 | e8af04d9ef58dd6e6485995fafe40095a3ce7d77 | 585b3a5c4cee72dc0a597cef22bce83cd2df2d52 | 2018-11-29T09:03:23Z | java | 2018-12-06T09:48:19Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,840 | ["dubbo-dependencies-bom/pom.xml"] | Q: 如何控制单台不并发，多台之间可以并发？ | 比如提供者A，在a机器上部署了A1，在b机器上部署了A2(人工保证不会在同一台设备下部署多份)
怎么控制a/b自身不能并发的，a与b之间是可以同时执行同一个提供者？
我试了```并发控制```里说的```<dubbo:service interface="com.foo.BarService" executes="1" />```
但是不是我想要的结果，消费者一并发消费者这边就报错了。我以为是请求到提供者那边wait住。
Q：那这种情况我应该如何实现？ | https://github.com/apache/dubbo/issues/2840 | https://github.com/apache/dubbo/pull/13007 | baec513773b2c2b9ab3212b39fe5cc9f8d6195b3 | 60cbc4a5b6ca806636bc58a0215c09c4dcf3217d | 2018-11-28T04:01:56Z | java | 2023-09-04T09:17:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,777 | ["dubbo-remoting/dubbo-remoting-api/src/main/java/org/apache/dubbo/remoting/exchange/support/header/HeaderExchangeClient.java", "dubbo-remoting/dubbo-remoting-api/src/main/java/org/apache/dubbo/remoting/exchange/support/header/HeaderExchangeServer.java"] | heartbeat threads blocks process shutdown | heartbeat threads blocks process shutdown because its hashed-wheel-timer is non-daemon thread. | https://github.com/apache/dubbo/issues/2777 | https://github.com/apache/dubbo/pull/2778 | 7f5fd469ee44cc2802194cbecde48d7d1fc920e4 | bff16ebe1fa6d73d64e1f90b5aacc3812eb40d90 | 2018-11-13T06:06:05Z | java | 2018-11-13T08:05:38Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,769 | ["dubbo-config/dubbo-config-spring/src/main/resources/META-INF/compat/dubbo.xsd", "dubbo-config/dubbo-config-spring/src/main/resources/META-INF/dubbo.xsd"] | About setting the connections to the method part. | There are currently two problems. The first question, is the setting of connections on the method valid?
The second question, is it necessary to set the connections property on the method?
After testing, the connections property on the method does not take effect. There is no impact on the number of connections.
Should we disable the connections property on the method? I think it should be disabled.
Currently an invoker is targeting a service instead of a method. It is not appropriate for us to set connections to the method.
If we can set connections to the method and take effect, how do we weigh the relationship between the service's connections and the methods' connections? | https://github.com/apache/dubbo/issues/2769 | https://github.com/apache/dubbo/pull/9011 | f784131cc2dbc97fb63013019092c9dbda112fb3 | e94bc47265814932ae76ddbc61265e3987a15446 | 2018-11-09T08:38:05Z | java | 2021-10-13T07:41:04Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,766 | ["pom.xml"] | [Dubbo - telnet] Unrecognized overload method | - [x] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [x] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: 2.7.0+
* Operating System version: mac
* Java version: 1.8
### Steps to reproduce this issue
Assume that there is an interface below：
```
package com.youzan.nova.service;
import java.util.Set;
public interface OverrideService {
void invoke(Integer id, Set<String> orderNumbers);
void invoke(Long id, Set<String> orderNumbers);
}
package com.youzan.nova.service;
import java.util.Set;
public class OverrideServiceImpl implements OverrideService {
@Override
public void invoke(Integer id, Set<String> orderNumbers) {
System.out.println(id);
}
@Override
public void invoke(Long id, Set<String> orderNumbers) {
System.out.println(id);
}
}
```
Start telnet call service：
```
invoke com.youzan.nova.service.OverrideService.invoke("13", Set["1"])
invoke com.youzan.nova.service.OverrideService.invoke("13L", Set["1"])
```
Always only call the method `invoke(Long id, Set<String> orderNumbers)`. | https://github.com/apache/dubbo/issues/2766 | https://github.com/apache/dubbo/pull/11403 | 2f30ba11b2e2309842271aee5c4b14e0a6cabfe5 | f8d66c4774d4a79c04ecbb5724f5a9dedf486911 | 2018-11-09T04:00:42Z | java | 2023-01-30T09:29:47Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,765 | ["pom.xml"] | The service provider could not be found about the rmi protocol |
### Environment
* Dubbo version: 2.6.2
* Operating System version: CentOS7
* Java version: 1.8
### Steps to reproduce this issue
1. <dubbo:protocol name="rmi" port="20879" host="192.168.51.113" /> Select rmi protocol
2. The service provider is on the 192.168.51.113 machine
Service consumers on other machines sun as 192.168.52.119
3. Service consumer reports exception, cannot find service exception is "java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:"
But I did not configure localhost at all.
Pls. provide [GitHub address] to reproduce this issue.
### Expected Result
The service consumer can get the address of the service provider correctly
### Actual Result
Service consumer reports exception, cannot find service exception is "java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:"
But I did not configure localhost at all.
If there is an exception, please attach the exception trace:
```
Caused by: com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method getEquipInitListByCollectPointKey in the service com.agioe.atm.domain.monitoring.alarm.service.GlobalDevCacheService. Tried 1 times of the providers [192.168.51.113:20879] (1/1) from the registry 192.168.51.113:2181 on the consumer 192.168.52.119 using the dubbo version 2.6.2. Last error is: Failed to invoke remote service: interface com.agioe.atm.domain.monitoring.alarm.service.GlobalDevCacheService, method: getEquipInitListByCollectPointKey, cause: Could not connect to remote service [rmi://192.168.51.113:20879/com.agioe.atm.domain.monitoring.alarm.service.GlobalDevCacheService]; nested exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect
at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:102)
at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:238)
at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:75)
at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52)
at com.alibaba.dubbo.common.bytecode.proxy6.getEquipInitListByCollectPointKey(proxy6.java)
at com.agioe.atm.alarmlinkage.engine.support.AlarmLinkageJmsListener.alarm(AlarmLinkageJmsListener.java:68)
at com.agioe.atm.alarmlinkage.engine.support.AlarmLinkageJmsListener.lambda$recvRealtimeData$1(AlarmLinkageJmsListener.java:58)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:291)
at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinTask.doInvoke(ForkJoinTask.java:401)
at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:734)
at java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:160)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:583)
at com.agioe.atm.alarmlinkage.engine.support.AlarmLinkageJmsListener.recvRealtimeData(AlarmLinkageJmsListener.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:180)
at org.springframework.messaging.handler.invocation.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:112)
at org.springframework.jms.listener.adapter.MessagingMessageListenerAdapter.invokeHandler(MessagingMessageListenerAdapter.java:104)
... 10 common frames omitted
Caused by: org.springframework.remoting.RemoteConnectFailureException: Could not connect to remote service [rmi://192.168.51.113:20879/com.agioe.atm.domain.monitoring.alarm.service.GlobalDevCacheService]; nested exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
```
### A piece of my mind
This seems to be a problem with the rmi protocol itself
My solution is:
System.setProperty("java.rmi.server.hostname", "192.168.51.113");
Now that dubbo has used zookeeper as a registry,can't you optimize this rmi protocol Naming.lookup ? | https://github.com/apache/dubbo/issues/2765 | https://github.com/apache/dubbo/pull/11403 | 2f30ba11b2e2309842271aee5c4b14e0a6cabfe5 | f8d66c4774d4a79c04ecbb5724f5a9dedf486911 | 2018-11-09T03:34:10Z | java | 2023-01-30T09:29:47Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,757 | ["dubbo-config/dubbo-config-api/src/main/java/org/apache/dubbo/config/AbstractConfig.java"] | ReferenceBean's getObject() called in toString() | Intellij Idea's debugger renders object to string in object view (Preferences -> Build, Execution, Deployment -> Debugger -> Data Views -> Java -> Enable 'toString()' object view). This behavior is enabled by default and it leads some strange problem when debug in Dubbo, for examples: #2431, or user may observe a ReferenceConfig may init twice or ReferenceConfig#urls may have two same entries if the breakpoint happens to set in the relevant places. You may interested in looking into the details from http://t.cn/EAhta27, where @code4wt gives the excellent analysis. | https://github.com/apache/dubbo/issues/2757 | https://github.com/apache/dubbo/pull/2754 | b0107e767651d066d68c3beaaca9736aed2292b8 | aa9f16e9eee8181b1619fd77c621d5fd57b27e82 | 2018-11-08T03:05:44Z | java | 2018-11-08T03:27:07Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,718 | ["dubbo-dependencies-bom/pom.xml"] | 模拟提供者与zookeper网络断开后，消费者不能继续调用提供者 | ### 环境
* Dubbo 版本：2.6.0
* 操作系统版本：centos
* Java版本: 1.8
### 操作步骤
1. 启动提供者
2. 启动消费者
3. iptables禁用提供者的zookeper端口2181
### 结果
看提供者的日志是提供者主动断开与消费者的连接的，不解的地方是zookeeper上的该接口的提供者节点数据也没有了，按理说掐断网络的瞬间不是优雅停机，节点数据是不会删除的（zookeeper有过期删除机智吗？）。接着我试验了用iptable禁用了消费者与zookeeper的2181端口，可以正常消费。按着提供方的现象，是不是可以理解为只要zookeeper挂掉之后，整个服务将不可用，dubbo变成了一个伪的无中心机构。
| https://github.com/apache/dubbo/issues/2718 | https://github.com/apache/dubbo/pull/12819 | 4bc91875314bfae2ed3708b51a4045bfd8791746 | 5f9d5802ec3a2e655c105eef7d7efaff183ff2f8 | 2018-10-31T07:46:41Z | java | 2023-07-31T11:03:27Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,619 | ["dubbo-remoting/dubbo-remoting-netty/src/main/java/org/apache/dubbo/remoting/transport/netty/NettyBackedChannelBuffer.java", "dubbo-remoting/dubbo-remoting-netty4/src/main/java/org/apache/dubbo/remoting/transport/netty4/NettyBackedChannelBuffer.java"] | is there a problem in NettyBackedChannelBuffer.setBytes(...)? | hi,I see the code for method setBytes in class com.alibaba.dubbo.remoting.transport.netty4.NettyBackedChannelBuffer.java which is below,is there a problem ?
| https://github.com/apache/dubbo/issues/2619 | https://github.com/apache/dubbo/pull/3448 | caac0b573c8f87d0147983c149d5f7d96db2b20c | b757e19f494cf8bdd18ed9bd7672733e7e41f2d6 | 2018-10-09T05:39:30Z | java | 2019-02-11T09:51:09Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,600 | ["dubbo-all/pom.xml"] | add javadoc to dubbo-all module | ```
<profiles>
<profile>
<id>release</id>
<build>
<plugins>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<version>${maven_javadoc_version}</version>
<executions>
<execution>
<id>attach-javadoc</id>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<doclint>none</doclint>
</configuration>
</execution>
</executions>
<configuration>
<includeDependencySources>true</includeDependencySources>
<dependencySourceIncludes>
<dependencySourceInclude>com.alibaba:dubbo-*</dependencySourceInclude>
<dependencySourceExclude>com.alibaba:hessian-*</dependencySourceExclude>
</dependencySourceIncludes>
<show>public</show>
<charset>UTF-8</charset>
<encoding>UTF-8</encoding>
<docencoding>UTF-8</docencoding>
<links>
<link>http://docs.oracle.com/javase/7/docs/api</link>
</links>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
```
master and 2.6.x both need to add, for master, dependencySourceInclude must be `org.apache.dubbo-*` | https://github.com/apache/dubbo/issues/2600 | https://github.com/apache/dubbo/pull/2604 | 3c34ee88fd79b5df0441320e53042b60a00bf76b | 046bc3081f7a98d539f9fb1b9af375ad80868ea8 | 2018-10-08T07:00:07Z | java | 2018-10-09T00:49:48Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,583 | ["dubbo-config/dubbo-config-api/src/main/java/org/apache/dubbo/config/model/ApplicationModel.java", "dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/command/impl/Offline.java", "dubbo-plugin/dubbo-qos/src/main/java/org/apache/dubbo/qos/command/impl/Online.java"] | ApplicationModel serviceName is not unique | - [ ] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [ ] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: all
* Operating System version: all
* Java version: all
### Steps to reproduce this issue
1. create two ReferenceConfig for same service with different configuration.
<dubbo:reference id="demoService" interface="com.alibaba.dubbo.DemoService">
</dubbo:reference>
<dubbo:reference id="demoServiceAsync" interface="com.alibaba.dubbo.DemoService" async="true">
</dubbo:reference>
2. startup the consumer application.
3. get the ConsumerModel from ApplicationModel.
Pls. provide [GitHub address] to reproduce this issue.
### Expected Result
ApplicationModel.allConsumerModels() should returns two ConsumerModel.
### Actual Result
ApplicationModel.allConsumerModels() only returns the first ConsumerModel.
If there is an exception, please attach the exception trace:
With future investigation, ReferenceConfig cannot put the second ConsumerModel as they are in same serviceName.
Also, this is the same issue for provider with below configuration.
<bean id="demoService" class="com.alibaba.dubbo.DemoServiceImpl"/>
<dubbo:service interface="com.alibaba.dubbo.DemoService" ref="demoService">
</dubbo:service>
<bean id="demoService2" class="com.alibaba.dubbo.DemoServiceImpl2"/>
<dubbo:service interface="com.alibaba.dubbo.DemoService" ref="demoService2">
</dubbo:service>
Here is my PR: https://github.com/apache/incubator-dubbo/pull/2582 | https://github.com/apache/dubbo/issues/2583 | https://github.com/apache/dubbo/pull/2614 | 5a25e7dc0d7178df341ef5f18ee403a6d048796b | ccce69e75fd34a48f02899cb5a61c07742c17c43 | 2018-09-29T06:01:20Z | java | 2018-10-09T08:37:28Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,558 | [".travis.yml"] | Remove Java 9/10 on travis CI | Now Java 11 has been released, and it's a long term maintained version.
Java 9 and Java 10 are only supported six months.
So, remove Java 9 and 10 on Travis, only support Java8 and Java 11. | https://github.com/apache/dubbo/issues/2558 | https://github.com/apache/dubbo/pull/2559 | 4fd352b6c3c4027c312b35b7b49ac82bf320f0ad | 755bbf92741d4fcfed52bf314a5971a53c46b00c | 2018-09-26T03:09:26Z | java | 2018-09-26T03:40:00Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,557 | ["dubbo-common/src/main/java/org/apache/dubbo/common/utils/ConfigUtils.java"] | org.apache.dubbo.common.utils.ConfigUtils#loadProperties(java.lang.String, boolean, boolean) miss windows scene |
### Environment
* Dubbo version: dubbo-2.6.4
* Operating System version: windows 10
* Java version: JDK1.8
When run the testcase(com.alibaba.dubbo.config.AbstractInterfaceConfigTest#checkApplication1) in windows environment,It will be wrong.
So It should add scene judgement in windows environment(org.apache.dubbo.common.utils.ConfigUtils#loadProperties(java.lang.String, boolean, boolean),Line 220).
```java
if (fileName.startsWith("/")) {
````
change to
```java
if (fileName.startsWith("/")||fileName.matches("^[A-z]:\\\\\\S+$")) {
````
the testcase (com.alibaba.dubbo.config.AbstractInterfaceConfigTest#checkApplication1) will go well.
| https://github.com/apache/dubbo/issues/2557 | https://github.com/apache/dubbo/pull/2562 | 00b718cbb214d82f6781c82b18c0c5c605940b98 | cd7ba294b22a9b392030fe5c6ee06247fc7868c1 | 2018-09-25T15:15:44Z | java | 2018-09-26T09:09:45Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,533 | ["dubbo-compatible/src/test/java/org/apache/dubbo/generic/GenericServiceTest.java", "dubbo-rpc/dubbo-rpc-dubbo/src/test/java/org/apache/dubbo/rpc/protocol/dubbo/DubboProtocolTest.java", "dubbo-rpc/dubbo-rpc-dubbo/src/test/java/org/apache/dubbo/rpc/protocol/dubbo/ExplicitCallbackTest.java"] | JDK11 master ut failed | ```
2018-09-19 03:25:53,034 WARN [org.apache.dubbo.remoting.exchange.support.DefaultFuture:received] - [DUBBO] The timeout response finally returned at 2018-09-19 03:25:53.034, response Response [id=1039, version=null, status=20, event=false, error=null, result=RpcResult [result=Lower, exception=null]], channel: /172.17.0.6:49932 -> /172.17.0.6:9010, dubbo version: 2.7.0-SNAPSHOT, current host: 172.17.0.6
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.319 sec <<< FAILURE! - in org.apache.dubbo.rpc.protocol.dubbo.DubboProtocolTest
testDubboProtocolWithMina(org.apache.dubbo.rpc.protocol.dubbo.DubboProtocolTest) Time elapsed: 1.315 sec <<< ERROR!
org.apache.dubbo.rpc.RpcException: Invoke remote method timeout. method: enumlength, provider: dubbo://127.0.0.1:9010/org.apache.dubbo.rpc.protocol.dubbo.support.DemoService?client=mina, cause: Waiting server-side response timeout by scan timer. start time: 2018-09-19 03:25:51.798, end time: 2018-09-19 03:25:53.032, client elapsed: 0 ms, server elapsed: 1234 ms, timeout: 1000 ms, request: Request [id=1039, version=2.0.2, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=enumlength, parameterTypes=[class [Lorg.apache.dubbo.rpc.protocol.dubbo.support.Type;], arguments=[[Lorg.apache.dubbo.rpc.protocol.dubbo.support.Type;@60e0cfe6], attachments={path=org.apache.dubbo.rpc.protocol.dubbo.support.DemoService, version=0.0.0}]], channel: /172.17.0.6:49932 -> /172.17.0.6:9010
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocolTest.testDubboProtocolWithMina(DubboProtocolTest.java:95)
Caused by: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2018-09-19 03:25:51.798, end time: 2018-09-19 03:25:53.032, client elapsed: 0 ms, server elapsed: 1234 ms, timeout: 1000 ms, request: Request [id=1039, version=2.0.2, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=enumlength, parameterTypes=[class [Lorg.apache.dubbo.rpc.protocol.dubbo.support.Type;], arguments=[[Lorg.apache.dubbo.rpc.protocol.dubbo.support.Type;@60e0cfe6], attachments={path=org.apache.dubbo.rpc.protocol.dubbo.support.DemoService, version=0.0.0}]], channel: /172.17.0.6:49932 -> /172.17.0.6:9010
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocolTest.testDubboProtocolWithMina(DubboProtocolTest.java:95)
Recived callback: server invoke callback : arg:1537327557966
Tests run: 5, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 3.011 sec <<< FAILURE! - in org.apache.dubbo.rpc.protocol.dubbo.ExplicitCallbackTest
TestCallbackMultiInstans(org.apache.dubbo.rpc.protocol.dubbo.ExplicitCallbackTest) Time elapsed: 1.737 sec <<< ERROR!
java.lang.IllegalStateException: callback instance not found
```
https://api.travis-ci.org/v3/job/430358124/log.txt | https://github.com/apache/dubbo/issues/2533 | https://github.com/apache/dubbo/pull/2552 | 0d20194cadada4f131395e9d0fff0a89ca2fe3bc | 4fd352b6c3c4027c312b35b7b49ac82bf320f0ad | 2018-09-20T01:26:18Z | java | 2018-09-25T09:46:30Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,516 | ["dubbo-config/dubbo-config-spring/src/main/java/org/apache/dubbo/config/spring/ServiceBean.java", "dubbo-config/dubbo-config-spring/src/main/java/org/apache/dubbo/config/spring/extension/SpringExtensionFactory.java", "dubbo-config/dubbo-config-spring/src/main/java/org/apache/dubbo/config/spring/status/DataSourceStatusChecker.java", "dubbo-config/dubbo-config-spring/src/main/java/org/apache/dubbo/config/spring/status/SpringStatusChecker.java", "dubbo-config/dubbo-config-spring/src/test/java/org/apache/dubbo/config/spring/status/DataSourceStatusCheckerTest.java", "dubbo-config/dubbo-config-spring/src/test/java/org/apache/dubbo/config/spring/status/SpringStatusCheckerTest.java"] | Remove getSpringContext() from org.apache.dubbo.config.spring.ServiceBean | org.apache.dubbo.config.spring.ServiceBean#getSpringContext looks like a hack, we need to remove it. | https://github.com/apache/dubbo/issues/2516 | https://github.com/apache/dubbo/pull/2517 | e6b0bc8a856abd7f2d7a2e0f06ccc78dc90e2e0a | 84410f79602a561b26957dc5149f599efd44aa2b | 2018-09-18T02:23:59Z | java | 2018-09-21T09:59:18Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,499 | ["dubbo-common/src/main/java/org/apache/dubbo/common/utils/CompatibleTypeUtils.java", "dubbo-common/src/test/java/org/apache/dubbo/common/utils/CompatibleTypeUtilsTest.java", "dubbo-common/src/test/java/org/apache/dubbo/common/utils/PojoUtilsTest.java"] | PojoUtil realize type convert not support subclasses of 'java.util.date' | - [x] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [x] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: 2.5.x, 2.6.x
* Operating System version: windows 7
* Java version: jdk1.7,jdk1.8
### Steps to reproduce this issue
1. String convert to java.sql.Time
2. String convert to java.sql.Date
3. String convert to java.sql.Timestamp
### Expected Result
The Convert is successful and you can get the object of the converted type.
### Actual Result
Conversion failed.
When the interface is called by 'jmeter-plugin-dubbo', it is passed into the hashmap through a generalization call. The value in the hashmap is a Date string, and an error occurred when the server accepts a type of java.sql.timestamp |Date
If there is an exception, please attach the exception trace:
```
java.lang.RuntimeException: Failed to set pojo TestVo property timestamp value 2018-09-13 10:00:00(class java.lang.String), cause: argument type mismatch
at com.alibaba.dubbo.common.utils.PojoUtils.realize0(PojoUtils.java:456)
at com.alibaba.dubbo.common.utils.PojoUtils.realize(PojoUtils.java:196)
at com.alibaba.dubbo.common.utils.PojoUtils.realize(PojoUtils.java:86)
at com.alibaba.dubbo.rpc.filter.GenericFilter.invoke(GenericFilter.java:68)
at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
at com.alibaba.dubbo.rpc.filter.ClassLoaderFilter.invoke(ClassLoaderFilter.java:38)
at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
at com.alibaba.dubbo.rpc.filter.EchoFilter.invoke(EchoFilter.java:38)
at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:72)
at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol$1.reply(DubboProtocol.java:103)
at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.handleRequest(HeaderExchangeHandler.java:96)
at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:172)
at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:51)
at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:80)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at com.alibaba.dubbo.common.utils.PojoUtils.realize0(PojoUtils.java:453)
... 16 more
```
| https://github.com/apache/dubbo/issues/2499 | https://github.com/apache/dubbo/pull/2500 | 96eec3ddc42feacb9f749b75d6df97ba77c2b51b | 8254e3da52f2b08c37a9e0fcf399142bf8b5fe38 | 2018-09-13T07:45:18Z | java | 2018-09-14T01:03:41Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,446 | ["dubbo-common/src/main/java/org/apache/dubbo/common/utils/ReflectUtils.java", "dubbo-rpc/dubbo-rpc-api/src/main/java/org/apache/dubbo/rpc/support/RpcUtils.java"] | jarslink做module隔离时,dubbo调用会抛ClassNotFoundException | 用jarslink做module隔离时,dubbo调用会抛ClassNotFoundException.经查是ClassLoader不一致.
```
public static Class<?> getReturnType(Invocation invocation) {
try {
if (invocation != null && invocation.getInvoker() != null
&& invocation.getInvoker().getUrl() != null
&& !invocation.getMethodName().startsWith("$")) {
String service = invocation.getInvoker().getUrl().getServiceInterface();
if (service != null && service.length() > 0) {
Class<?> cls = ReflectUtils.forName(service);
Method method = cls.getMethod(invocation.getMethodName(), invocation.getParameterTypes());
if (method.getReturnType() == void.class) {
return null;
}
return method.getReturnType();
}
}
} catch (Throwable t) {
logger.warn(t.getMessage(), t);
}
return null;
}
``` | https://github.com/apache/dubbo/issues/2446 | https://github.com/apache/dubbo/pull/2447 | 51f0677c8eaca9a7d8a37e663a344e8b02543350 | e18810baba0e2314f11a2c8c080cd58d9af446bf | 2018-09-05T04:42:19Z | java | 2018-09-11T07:32:25Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,413 | ["dubbo-common/src/main/java/org/apache/dubbo/common/io/StreamUtils.java", "dubbo-common/src/test/java/org/apache/dubbo/common/io/StreamUtilsTest.java"] | Resource leak in StreamUtils | ### Environment
* Dubbo version: master branch latest
* Operating System version: all
* Java version: 1.8
### Step to reproduce this issue
1. start StreamUtils UT
2. using `lsof test-class/StreamUtilsTest.txt` to check opened file handle
### Expected Result
after running all the UT, there shouldn't be any opened handles left
### Actual Result
several file handles left
### How to fix
- `overwrite` the `close` method of `InputStream` constructed in `limitedInputStream` and `markSupportedInputStream`
- `close` the InputStream in corresponding UT | https://github.com/apache/dubbo/issues/2413 | https://github.com/apache/dubbo/pull/2414 | ff36fb0d5ab175b8a90fd717692c9c49f934ef8a | d173e841c41704d13e7357eb5704764353384963 | 2018-08-31T03:24:50Z | java | 2018-09-06T11:22:51Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,405 | ["dubbo-kubernetes/pom.xml"] | SpringExtensionFactory 导致的OOM | 使用256版本dubbo，测试时候发现应用有OOM，dump日志后发现大量的 SpringExtensionFactory中的hashmap占了真个4G内存的76%，发现加载了大量不同的xmlwebapplication对象.
什么情况下会导致SpringExtensionFactory重复加载xmlwebapplication？
以下是dump出来的内存占用分析:
| https://github.com/apache/dubbo/issues/2405 | https://github.com/apache/dubbo/pull/11483 | e327f8ff7ceae1842e99a877909851e7963188d0 | ef7c5187a464a7b3d944c37d8d723c26e69efc60 | 2018-08-29T12:24:10Z | java | 2023-02-06T09:23:58Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,400 | ["dubbo-kubernetes/pom.xml"] | ReferenceConfig(dubbo://127.0.0.1:20880) is not DESTROYED when FINALIZ | - [ ] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [ ] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: xxx
* Operating System version: xxx
* Java version: xxx
### Step to reproduce this issue
1. xxx
2. xxx
3. xxx
Pls. provide [GitHub address] to reproduce this issue.
### Expected Result
What do you expected from the above steps？
### Actual Result
What is actually happen?
If there is an exception, please attach the exception trace:
```
Just put your stack trace here!
```
| https://github.com/apache/dubbo/issues/2400 | https://github.com/apache/dubbo/pull/11483 | e327f8ff7ceae1842e99a877909851e7963188d0 | ef7c5187a464a7b3d944c37d8d723c26e69efc60 | 2018-08-29T04:54:07Z | java | 2023-02-06T09:23:58Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,348 | ["dubbo-registry/dubbo-registry-api/src/test/java/org/apache/dubbo/registry/support/AbstractRegistryTest.java"] | AbstractRegistry unit test enhancement. | Design and provide unit tests to cover more use cases. | https://github.com/apache/dubbo/issues/2348 | https://github.com/apache/dubbo/pull/2409 | 9135546c847edb3eb6d8abd3efd46f9ab702bd2e | cd60e58e1a579749c89c6ac8ddb39f8e8e894ef5 | 2018-08-26T14:35:56Z | java | 2018-09-19T09:28:43Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,191 | ["dubbo-remoting/dubbo-remoting-zookeeper/src/main/java/org/apache/dubbo/remoting/zookeeper/curator/CuratorZookeeperClient.java", "dubbo-remoting/dubbo-remoting-zookeeper/src/main/java/org/apache/dubbo/remoting/zookeeper/zkclient/ZkclientZookeeperClient.java"] | org.apache.curator.ConnectionState - Connection timed out for connection | provider注册启动时，报如下错配置dubbo.registry.timeout不生效，一直是5000Ms，求解。
org.apache.curator.ConnectionState - Connection timed out for connection string (localhost:2183) and timeout (5000) / elapsed (5103)
org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss
at org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java:225)
at org.apache.curator.ConnectionState.getZooKeeper(ConnectionState.java:94)
at org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:117)
at org.apache.curator.framework.imps.CuratorFrameworkImpl.getZooKeeper(CuratorFrameworkImpl.java:489)
at org.apache.curator.framework.imps.ExistsBuilderImpl$3.call(ExistsBuilderImpl.java:237)
at org.apache.curator.framework.imps.ExistsBuilderImpl$3.call(ExistsBuilderImpl.java:226)
at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:109)
at org.apache.curator.framework.imps.ExistsBuilderImpl.pathInForegroundStandard(ExistsBuilderImpl.java:223)
at org.apache.curator.framework.imps.ExistsBuilderImpl.pathInForeground(ExistsBuilderImpl.java:216)
at org.apache.curator.framework.imps.ExistsBuilderImpl.forPath(ExistsBuilderImpl.java:175)
at org.apache.curator.framework.imps.ExistsBuilderImpl.forPath(ExistsBuilderImpl.java:32)
at com.alibaba.dubbo.remoting.zookeeper.curator.CuratorZookeeperClient.checkExists(CuratorZookeeperClient.java:117)
at com.alibaba.dubbo.remoting.zookeeper.support.AbstractZookeeperClient.create(AbstractZookeeperClient.java:58)
at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry.doRegister(ZookeeperRegistry.java:114)
at com.alibaba.dubbo.registry.support.FailbackRegistry.register(FailbackRegistry.java:131)
at com.alibaba.dubbo.registry.integration.RegistryProtocol.register(RegistryProtocol.java:125)
at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:145)
at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:98)
at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:55)
at com.alibaba.dubbo.qos.protocol.QosProtocolWrapper.export(QosProtocolWrapper.java:54)
at com.alibaba.dubbo.rpc.Protocol$Adaptive.export(Protocol$Adaptive.java)
at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:506)
at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:358)
at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:317)
at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:216)
at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:123)
at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:49)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:399)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:353)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:887)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:161)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:552)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:752)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:388)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:327)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1246)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1234)
at com.faw.provider.Application.main(Application.java:10) | https://github.com/apache/dubbo/issues/2191 | https://github.com/apache/dubbo/pull/2217 | 518c5961e69ac6f1a5e48b193dc52b55d208f5d7 | 9f21b9f8461cd8422ecd590df6854b045162dd1b | 2018-08-06T07:31:26Z | java | 2018-08-09T03:13:59Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,178 | ["dubbo-dependencies-bom/pom.xml"] | Please consider supporting Java 8 Date/Time type when serializing with Kryo | ### Environment
* Dubbo version: 2.6.2
* Java version: 1.8
I am using java.time.LocalDateTime and Dubbo complains "**class java.time.LocalDateTime has no zero-arg constructor and this will affect the serialization performance**", which is caused by Dubbo's wrapper class "**CompatibleKryo**"
Any thoughts ??
```
package com.alibaba.dubbo.common.serialize.kryo;
import com.alibaba.dubbo.common.logger.Logger;
import com.alibaba.dubbo.common.logger.LoggerFactory;
import com.alibaba.dubbo.common.serialize.kryo.utils.ReflectionUtils;
import com.esotericsoftware.kryo.Kryo;
import com.esotericsoftware.kryo.Serializer;
import com.esotericsoftware.kryo.serializers.JavaSerializer;
public class CompatibleKryo extends Kryo {
private static final Logger logger = LoggerFactory.getLogger(CompatibleKryo.class);
@Override
public Serializer getDefaultSerializer(Class type) {
if (type == null) {
throw new IllegalArgumentException("type cannot be null.");
}
if (!type.isArray() && !type.isEnum() && !ReflectionUtils.checkZeroArgConstructor(type)) {
if (logger.isWarnEnabled()) {
logger.warn(type + " has no zero-arg constructor and this will affect the serialization performance");
}
return new JavaSerializer();
}
return super.getDefaultSerializer(type);
}
}
``` | https://github.com/apache/dubbo/issues/2178 | https://github.com/apache/dubbo/pull/11993 | c2b809adac5681305a1d41530d49881448c57618 | 694de269500f56fcb974eda440205de2735cffad | 2018-08-03T06:43:42Z | java | 2023-04-04T09:12:51Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,129 | [".travis.yml"] | Enable ASF header check for Travis CI | https://github.com/apache/dubbo/issues/2129 | https://github.com/apache/dubbo/pull/2130 | ed4384a2e5ba4d047a3e73d666244b3f41521f5d | 3eae6246ee237e5d99a830b0443010f41cfc5c98 | 2018-07-25T02:00:17Z | java | 2018-07-25T10:31:52Z |
|
closed | apache/dubbo | https://github.com/apache/dubbo | 2,127 | ["dubbo-rpc/dubbo-rpc-rest/src/main/java/org/apache/dubbo/rpc/protocol/rest/RpcContextFilter.java", "dubbo-rpc/dubbo-rpc-rest/src/test/java/org/apache/dubbo/rpc/protocol/rest/RestProtocolTest.java"] | NullPointExexception in RpcContextFilter | - [ ] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [ ] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: 2.6.1 - newest
### Step to reproduce this issue
1.
String value = null;
RpcContext.getContext().getAttachments().put("demokey", value)
2.
then invoke one method will NullPointException
**The Exception reason:
In RpcContextFilter.java，public void filter(ClientRequestContext requestContext) throws IOException
for (Map.Entry<String, String> entry : RpcContext.getContext().getAttachments().entrySet()) {
if (entry.getValue().contains(",") || entry.getValue().contains("=")
the entry.getValue not judge null!!**
| https://github.com/apache/dubbo/issues/2127 | https://github.com/apache/dubbo/pull/2171 | 9f21b9f8461cd8422ecd590df6854b045162dd1b | 895a4dd690f8190a972e9d4ae370bf5b1c8700c7 | 2018-07-24T08:48:59Z | java | 2018-08-09T03:28:12Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,088 | ["dubbo-rpc/dubbo-rpc-rest/src/main/java/org/apache/dubbo/rpc/protocol/rest/RestProtocol.java", "dubbo-rpc/dubbo-rpc-rest/src/test/java/org/apache/dubbo/rpc/protol/rest/RestProtocolTest.java"] | [BUG]Miss context path when export a rest service explicitly | - [x] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [x] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/wiki/FAQ) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: latest
### Step to reproduce this issue
1. export a rest service DemoService with a url: rest://127.0.0.1:4444/test/
2. then we will get a real rest service with rest://127.0.0.1:4444/test/DemoService
3. but when we export a rest service DemoService with a url: rest://127.0.0.1:4444/test
4. then we will get a real rest service with rest://127.0.0.1:4444/DemoService
Those are the different results, in the second case the context path test is missing.
So users use explicit exporter and invoker to call rest services, they would feel puzzled.
We should fix it by modifying getContextPath method.
| https://github.com/apache/dubbo/issues/2088 | https://github.com/apache/dubbo/pull/2092 | ad126d53bb220dc8c46fbf40cf763afa65c5145b | 0513b065a244c418cb68c6f69df392fc3a56ad41 | 2018-07-16T16:23:46Z | java | 2018-07-18T12:35:19Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,067 | ["dubbo-dependencies-bom/pom.xml"] | 2.5.3版本reference注解调用抛空指针异常 | 环境：2.5.3
异常：
A服务通过reference注解引用B，A启动的时候B服务宕机，后面重启B服务
A服务调用B的时候抛NullPointException
正常：
后面重启A服务，调用B服务才正常
| https://github.com/apache/dubbo/issues/2067 | https://github.com/apache/dubbo/pull/13459 | 394d487117e3c83849a28149fc8b3bb5a0edfd69 | 849e108835479bbeefcfd983fd427168a7e4a8a8 | 2018-07-11T15:17:40Z | java | 2023-12-04T13:31:25Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 2,061 | ["dubbo-dependencies-bom/pom.xml"] | ThriftProtocol BUG | - [x] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this repository and believe that this is not a duplicate.
- [x] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/wiki/FAQ) of this repository and believe that this is not a duplicate.
### Environment
* Dubbo version: 2.6.2
* Operating System version: win10
* Java version: 1.8
### Step to reproduce this issue
1、the code in **ThriftProtocol**
String serviceKey = serviceKey(channel.getLocalAddress().getPort(), serviceName, null, null);
DubboExporter<?> exporter = (DubboExporter<?>) exporterMap.get(serviceKey);
2、why set the serviceVersion and serviceGroup null ? I do not understand
```
com.alibaba.dubbo.remoting.RemotingException: Not found exported service: com.zbss.common.api.config.service.ConfigService$Iface:20080 in [service-config/com.zbss.common.api.config.service.ConfigService$Iface:20080], may be version or group mismatch , channel: consumer: /192.168.3.63:61251 --> provider: /192.168.3.63:20080, message:RpcInvocation [methodName=getVendorConfig, parameterTypes=[class java.lang.String], arguments=[123], attachments={interface=com.zbss.common.api.config.service.ConfigService$Iface}]
at com.alibaba.dubbo.rpc.protocol.thrift.ThriftProtocol$1.reply(ThriftProtocol.java:67)
at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.handleRequest(HeaderExchangeHandler.java:96)
at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:172)
at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:51)
at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:80)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
```
| https://github.com/apache/dubbo/issues/2061 | https://github.com/apache/dubbo/pull/11993 | c2b809adac5681305a1d41530d49881448c57618 | 694de269500f56fcb974eda440205de2735cffad | 2018-07-10T09:54:55Z | java | 2023-04-04T09:12:51Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,990 | ["dubbo-dependencies-bom/pom.xml"] | 跑在容器里provider端不停的报All clients has discontected... | provider可以正常提供服务, 但是基本上每隔20秒, 就一直输出以下日志, 貌似直接运行不会这样, 是容器里不能建立长连接吗? 还是我需要做什么设置?
```
[2018-06-26 13:57:09.914 - WARN] c.a.d.remoting.transport.AbstractServer : - [DUBBO] All clients has discontected from /127.0.0.1:9090. You can graceful shutdown now., dubbo version: 2.6.1.2, current host: 172.1.2.155
[2018-06-26 13:57:29.924 - WARN] c.a.d.remoting.transport.AbstractServer : - [DUBBO] All clients has discontected from /127.0.0.1:9090. You can graceful shutdown now., dubbo version: 2.6.1.2, current host: 172.1.2.155
[2018-06-26 13:57:49.911 - WARN] c.a.d.remoting.transport.AbstractServer : - [DUBBO] All clients has discontected from /127.0.0.1:9090. You can graceful shutdown now., dubbo version: 2.6.1.2, current host: 172.1.2.155
[2018-06-26 13:58:09.904 - WARN] c.a.d.remoting.transport.AbstractServer : - [DUBBO] All clients has discontected from /127.0.0.1:9090. You can graceful shutdown now., dubbo version: 2.6.1.2, current host: 172.1.2.155
[2018-06-26 13:58:29.933 - WARN] c.a.d.remoting.transport.AbstractServer : - [DUBBO] All clients has discontected from /127.0.0.1:9090. You can graceful shutdown now., dubbo version: 2.6.1.2, current host: 172.1.2.155
[2018-06-26 13:58:49.906 - WARN] c.a.d.remoting.transport.AbstractServer : - [DUBBO] All clients has discontected from /127.0.0.1:9090. You can graceful shutdown now., dubbo version: 2.6.1.2, current host: 172.1.2.155
```
补充一下: 容器环境是docker+k8s, 网络使用的是flannel的gw模式.
| https://github.com/apache/dubbo/issues/1990 | https://github.com/apache/dubbo/pull/10064 | f7957db329c58fd67be0d61d49ccf5cc98971922 | fe135983ed74c0fa5538a44d675cfdb8db9aa9ed | 2018-06-26T06:06:52Z | java | 2022-05-22T01:10:36Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,925 | ["dubbo-config/dubbo-config-api/src/main/java/org/apache/dubbo/config/ServiceConfig.java", "dubbo-config/dubbo-config-spring/src/main/java/org/apache/dubbo/config/spring/ServiceBean.java"] | Redundant toString() is called | branch : master , version : 2.7.0-SNAPSHOT
ServiceConfig#doExportUrlsFor1Protocol , line 482
<img width="890" alt="image" src="https://user-images.githubusercontent.com/6971152/41273922-035827c2-6e4e-11e8-8a72-71562d138cf9.png">
The type of Constant.SCOPE_Xxx is String already , no need to call toString() again | https://github.com/apache/dubbo/issues/1925 | https://github.com/apache/dubbo/pull/1969 | d21d9942b37ad5baccf698b19a17b372c0c9557c | 705bf37cbb039f718e3b98718511526dfd2efd64 | 2018-06-12T06:37:22Z | java | 2018-06-21T04:02:15Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,917 | ["dubbo-registry/dubbo-registry-redis/src/main/java/org/apache/dubbo/registry/redis/RedisRegistry.java"] | Condition is not properly used ? | https://github.com/apache/incubator-dubbo/blob/3e9b66854c6f70b1dfa7dd19e689bd04ae0ecb41/dubbo-registry/dubbo-registry-redis/src/main/java/com/alibaba/dubbo/registry/redis/RedisRegistry.java#L590
https://github.com/apache/incubator-dubbo/blob/3e9b66854c6f70b1dfa7dd19e689bd04ae0ecb41/dubbo-registry/dubbo-registry-redis/src/main/java/com/alibaba/dubbo/registry/redis/RedisRegistry.java#L602
Just read the RedisRegistry.java and got doubtful about the above lines. Is the following code more appropriate ?
```
if (first) {
// blah blah
}
```
| https://github.com/apache/dubbo/issues/1917 | https://github.com/apache/dubbo/pull/3466 | 813fed53e8da58beb48bae9ed602f133abb3f747 | 9031a4c20455ba16a63233f10783a55915afcd9b | 2018-06-11T10:22:39Z | java | 2019-02-18T02:30:59Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,879 | ["dubbo-container/dubbo-container-api/src/main/resources/META-INF/assembly/bin/start.sh"] | start.sh脚本问题 | start.sh脚本中有三处使用ps命令的地方：第一处是ps -ef ~~~，第二处和第三处是ps -f ~~~。
但是ps -f并不能查出进程，我们在生产环境都统一改成了ps -ef，请问这里是不是有点小问题？
执行命令日志如下：
[afei@jtcrtvdra35 ~]$ ps -f | grep java
afei 30036 28792 0 14:53 pts/1 00:00:00 grep --color java
[afei@jtcrtvdra35 ~]$
[afei@jtcrtvdra35 ~]$ ps -ef | grep java
afei 325 1 0 Apr11 ? 11:43:37 java ... ...
afei 1406 1 0 May18 ? 02:20:11 java ... ...
... ...
| https://github.com/apache/dubbo/issues/1879 | https://github.com/apache/dubbo/pull/1900 | 28266668d38424bf936e21d16e6f32c8750685b7 | 5916e8b1e853c74ed9d2b832f170756b35f478fb | 2018-06-04T06:55:17Z | java | 2018-06-07T11:30:58Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,864 | ["dubbo-build-tools/pom.xml", "dubbo-dependencies-bom/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper-curator5/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper/pom.xml", "dubbo-dependencies/pom.xml", "dubbo-distribution/pom.xml", "pom.xml"] | 生产者、消费者、注册中心不在同一个工程时，@reference调用远程接口无法识别 | 
生产者可以正常发布
dubbo监控中心也可以看到生产者
就是在消费者引入远程生产者接口的时候本地不识别，编译不通过，请问这个问题该如何解决？如何让dubbo调用远程主机的接口服务呢？？能否讲解一下 翻了一下官网文档 没有发现相关解释~谢谢了~
| https://github.com/apache/dubbo/issues/1864 | https://github.com/apache/dubbo/pull/13460 | 849e108835479bbeefcfd983fd427168a7e4a8a8 | 94725ece64fe9b84a4c2b8a261507d311db057bd | 2018-05-29T15:18:11Z | java | 2023-12-04T13:32:03Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,860 | ["dubbo-build-tools/pom.xml", "dubbo-dependencies-bom/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper-curator5/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper/pom.xml", "dubbo-dependencies/pom.xml", "dubbo-distribution/pom.xml", "pom.xml"] | 升级到2.6.0版本后,重复调用问题 | dubbo新版本的源码中,retries 默认为0,自己手动配置retries =0,也会出现接口重复调用 | https://github.com/apache/dubbo/issues/1860 | https://github.com/apache/dubbo/pull/13460 | 849e108835479bbeefcfd983fd427168a7e4a8a8 | 94725ece64fe9b84a4c2b8a261507d311db057bd | 2018-05-29T09:51:43Z | java | 2023-12-04T13:32:03Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,821 | ["dubbo-dependencies-bom/pom.xml"] | Got out of memory when building the source code | I tried to build the 2.6.2 source code by running "mvn clean install" from the route, I got the out of memory here. If I comment out the checkstyle check, I can run the test and build the kit.
Here is my box information:
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T15:58:13+08:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_151.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac" | https://github.com/apache/dubbo/issues/1821 | https://github.com/apache/dubbo/pull/13005 | 168b6578077f232c91d1ddec965a505eff84770a | a4280b20a492d2fa571e0e6a7dc77c372b5065c8 | 2018-05-21T02:32:48Z | java | 2023-09-04T09:16:15Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,815 | ["dubbo-dependencies-bom/pom.xml"] | When using the restfull protocol transaction rollback failed | dubbo+mybatis
使用rest协议时,方法内调用其他spring service的方法,发生异常时事务回滚失败,使用dubbo协议时正常
Using rest protocol, method calls within other spring service, the method of transaction rollback failed, when an exception occurs when using the dubbo protocol is normal | https://github.com/apache/dubbo/issues/1815 | https://github.com/apache/dubbo/pull/11993 | c2b809adac5681305a1d41530d49881448c57618 | 694de269500f56fcb974eda440205de2735cffad | 2018-05-18T06:47:03Z | java | 2023-04-04T09:12:51Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,812 | ["dubbo-dependencies-bom/pom.xml"] | dubbo rest | 现在dubbo支持rest协议吗？ | https://github.com/apache/dubbo/issues/1812 | https://github.com/apache/dubbo/pull/13005 | 168b6578077f232c91d1ddec965a505eff84770a | a4280b20a492d2fa571e0e6a7dc77c372b5065c8 | 2018-05-17T08:17:01Z | java | 2023-09-04T09:16:15Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,789 | ["dubbo-build-tools/pom.xml", "dubbo-dependencies-bom/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper-curator5/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper/pom.xml", "dubbo-dependencies/pom.xml", "dubbo-distribution/pom.xml", "pom.xml"] | 关于Adaptive求教 | 感觉Dubbo的Adaptive设计严重降低了代码的可读性，特别是在还包裹了很多AOP的情况下
比如说ReferenceConfig的createProxy方法里面的
`invoker = refprotocol.refer(interfaceClass, urls.get(0));`
求教这个refprotocol到底是在哪里被加强的？ | https://github.com/apache/dubbo/issues/1789 | https://github.com/apache/dubbo/pull/13416 | f1632c33ad31d7de427a88ea4a4f829650f91cb5 | 841ddb6e1f82d01f41a2c2a009de15a818c472be | 2018-05-13T09:34:54Z | java | 2023-11-30T12:49:38Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,787 | ["dubbo-dependencies-bom/pom.xml"] | Unstable UT: ZookeeperRegistryTest | I've seen it at least twice, one can be found [here](https://github.com/apache/incubator-dubbo/pull/1776)
```
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
Running com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistryTest
log4j:WARN No appenders could be found for logger (com.alibaba.dubbo.common.logger.LoggerFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.835 sec <<< FAILURE! - in com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistryTest
testStatusChecker(com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistryTest) Time elapsed: 1.082 sec <<< FAILURE!
java.lang.AssertionError:
Expected: is <ERROR>
but: was <OK>
at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistryTest.testStatusChecker(ZookeeperRegistryTest.java:137)
Results :
Failed tests:
ZookeeperRegistryTest.testStatusChecker:137
Expected: is <ERROR>
but: was <OK>
Tests run: 8, Failures: 1, Errors: 0, Skipped: 0
``` | https://github.com/apache/dubbo/issues/1787 | https://github.com/apache/dubbo/pull/11993 | c2b809adac5681305a1d41530d49881448c57618 | 694de269500f56fcb974eda440205de2735cffad | 2018-05-12T13:53:27Z | java | 2023-04-04T09:12:51Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,756 | ["dubbo-build-tools/pom.xml", "dubbo-dependencies-bom/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper-curator5/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper/pom.xml", "dubbo-dependencies/pom.xml", "dubbo-distribution/pom.xml", "pom.xml"] | AbstractClusterInvokerTest throws OutOfMemoryError | After replace easymock to mockito, when run unit test in the terminal,
```
mvn test -pl dubbo-cluster -Dtest=com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvokerTest
```
It fails, and the exception is:
```
-------------------------------------------------------------------------------
Test set: com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvokerTest
-------------------------------------------------------------------------------
Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 23.367 sec <<< FAILURE! - in com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvokerTest
com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvokerTest Time elapsed: 22.21 sec <<< ERROR!
java.lang.OutOfMemoryError: GC overhead limit exceeded
```
| https://github.com/apache/dubbo/issues/1756 | https://github.com/apache/dubbo/pull/13416 | f1632c33ad31d7de427a88ea4a4f829650f91cb5 | 841ddb6e1f82d01f41a2c2a009de15a818c472be | 2018-05-09T02:46:36Z | java | 2023-11-30T12:49:38Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,755 | ["dubbo-test/dubbo-test-check/pom.xml"] | [Bug] Bean name of @Service annotated class does not resolve placeholder | Code as following:
```java
@Service(
version = "${dubbo.service.version}",
application = "${dubbo.application.id}",
protocol = "${dubbo.protocol.id}",
registry = "${dubbo.registry.id}"
)
public class DefaultDemoService implements DemoService {
public String sayHello(String name) {
return "Hello, " + name + " (from Spring Boot)";
}
}
```
The placeholder was not resolved from the bean name of `DefaultDemoService` , thus it's name will contain "${dubbo.service.version}" | https://github.com/apache/dubbo/issues/1755 | https://github.com/apache/dubbo/pull/12009 | ce9991e69964f5dba92626dc9290a902da7eb075 | e29a8498a90d02217d1d3b49da72412dbd04976f | 2018-05-08T14:08:03Z | java | 2023-04-04T09:13:30Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,743 | ["dubbo-remoting/dubbo-remoting-zookeeper/src/main/java/org/apache/dubbo/remoting/zookeeper/curator/CuratorZookeeperClient.java", "dubbo-remoting/dubbo-remoting-zookeeper/src/main/java/org/apache/dubbo/remoting/zookeeper/zkclient/ZkclientZookeeperClient.java"] | use CuratorFrameworkFactory.DEFAULT_CONNECTION_TIMEOUT_MS | https://github.com/apache/incubator-dubbo/blob/04c93e8b98250230c4d22423372acd1c29e2c770/dubbo-remoting/dubbo-remoting-zookeeper/src/main/java/com/alibaba/dubbo/remoting/zookeeper/curator/CuratorZookeeperClient.java#L49
rt | https://github.com/apache/dubbo/issues/1743 | https://github.com/apache/dubbo/pull/2217 | 518c5961e69ac6f1a5e48b193dc52b55d208f5d7 | 9f21b9f8461cd8422ecd590df6854b045162dd1b | 2018-05-05T06:02:56Z | java | 2018-08-09T03:13:59Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,727 | ["dubbo-rpc/dubbo-rpc-hessian/src/test/java/com/alibaba/dubbo/rpc/protocol/hessian/HessianProtocolTest.java"] | HessianProtocolTest is unstable |
```
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
Running com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest
log4j:WARN No appenders could be found for logger (com.alibaba.dubbo.common.logger.LoggerFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
2018-05-02 09:42:39.952:INFO::Logging to STDERR via org.mortbay.log.StdErrLog
2018-05-02 09:42:40.111:INFO::jetty-6.1.26
2018-05-02 09:42:40.334:INFO::Started [email protected]:5342
2018-05-02 09:42:41.284:WARN::/com.alibaba.dubbo.rpc.protocol.hessian.HessianService: com.caucho.hessian.io.HessianProtocolException: sayHello: expected int at 0x7a (z)
2018-05-02 09:42:41.409:WARN::/com.alibaba.dubbo.rpc.protocol.hessian.HessianService: com.caucho.hessian.io.HessianProtocolException: sayHello: expected int at 0x7a (z)
Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 2.58 sec <<< FAILURE! - in com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest
testHttpClient(com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest) Time elapsed: 0.746 sec <<< ERROR!
com.caucho.hessian.client.HessianRuntimeException: com.caucho.hessian.io.HessianProtocolException: 'ï¿¿' is an unknown code
at com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest.testHttpClient(HessianProtocolTest.java:83)
Caused by: com.caucho.hessian.io.HessianProtocolException: 'ï¿¿' is an unknown code
at com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest.testHttpClient(HessianProtocolTest.java:83)
testHessianProtocol(com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest) Time elapsed: 0.002 sec <<< ERROR!
com.caucho.hessian.client.HessianRuntimeException: com.caucho.hessian.io.HessianProtocolException: 'ï¿¿' is an unknown code
at com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest.testHessianProtocol(HessianProtocolTest.java:48)
Caused by: com.caucho.hessian.io.HessianProtocolException: 'ï¿¿' is an unknown code
at com.alibaba.dubbo.rpc.protocol.hessian.HessianProtocolTest.testHessianProtocol(HessianProtocolTest.java:48)
Results :
Tests in error:
HessianProtocolTest.testHessianProtocol:48 » HessianRuntime com.caucho.hessian...
HessianProtocolTest.testHttpClient:83 » HessianRuntime com.caucho.hessian.io.H...
Tests run: 5, Failures: 0, Errors: 2, Skipped: 0
``` | https://github.com/apache/dubbo/issues/1727 | https://github.com/apache/dubbo/pull/1811 | e20618a66fbe8106e1f1c813dec7c09d11a1ebb7 | a45206c64f1e293bd164b4f489d9830e5b296112 | 2018-05-02T09:48:13Z | java | 2018-05-17T08:04:19Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,702 | ["dubbo-dependencies-bom/pom.xml"] | [Project 1]- enhance the test coverage | ## Project Description
### Requirement:
Add unit test to enhance the test coverage
Welcome everyone to join in，you can comment on the issue that you're interest with.
### Project address
https://github.com/apache/incubator-dubbo/projects/1
### Test coverage guide
When writing test code, we should see the [Test coverage guide]( https://github.com/apache/incubator-dubbo/wiki/Test-coverage-guide) at first. There are some naming specifications and test case design suggestions.
The issues are as follows:
## Issues
|status | issues | assignee |
| ------------------------------------------------------------ | ------------- | ------ |
|done| @lovepoem | [part-1 : dubbo-cluster module](https://github.com/apache/incubator-dubbo/issues/1679) |
| done |@zonghaishang | [part-2 : dubbo-common/src/main/java/com/alibaba/dubbo/common/beanutil(bytecode\|compiler\|extension)](https://github.com/apache/incubator-dubbo/issues/1680) |
| done |@htynkn | [part-3 : dubbo-common/src/main/java/com/alibaba/dubbo/common/concurrent(io\|json\|logger) modules](https://github.com/apache/incubator-dubbo/issues/1681) |
|done|@beiwei30 | [part-4 : dubbo-common/src/main/java/com/alibaba/dubbo/common/status(store\|threadpoolutils) modules](https://github.com/apache/incubator-dubbo/issues/1682) |
| done | @beiwei30 | [part-5 : dubbo-config/dubbo-config-api module](https://github.com/apache/incubator-dubbo/issues/1683) |
| done |@htynkn | [part-6 : dubbo-config/dubbo-config-spring module](https://github.com/apache/incubator-dubbo/issues/1684) |
| |@stoneapple | [part-7 : dubbo-container module](https://github.com/apache/incubator-dubbo/issues/1685) |
|done|@qinnnyul | [part-8 : dubbo-filter module](https://github.com/apache/incubator-dubbo/issues/1687) |
|done |@htynkn | [part-9 :dubbo-monitor module](https://github.com/apache/incubator-dubbo/issues/1688) |
| done |@beiwei30| [part-10 : dubbo-plugin module](https://github.com/apache/incubator-dubbo/issues/1689) |
| | | [part-11 : dubbo-registry/dubbo-registry-api and dubbo-registry/dubbo-registry-default modules](https://github.com/apache/incubator-dubbo/issues/1690) |
| done | @satansk | [part-12: dubbo-registry/dubbo-registry-multicast(dubbo-registry-redis\|dubbo-registry-zookeeper)](https://github.com/apache/incubator-dubbo/issues/1691) |
| | |[part-13 : dubbo-remoting/dubbo-remoting-api(dubbo-remoting-grizzly\|dubbo-remoting-http) modules](https://github.com/apache/incubator-dubbo/issues/1692) |
| done | @DeadLion | [part-14 : dubbo-remoting/dubbo-remoting-mina(dubbo-remoting-netty/dubbo-remoting-netty4) modules](https://github.com/apache/incubator-dubbo/issues/1693) |
| done | @htynkn | [part-15 : dubbo-remoting/dubbo-remoting-p2p(dubbo-remoting-zookeeper) module](https://github.com/apache/incubator-dubbo/issues/1694) |
| done | @whanice | [part-16 : dubbo-rpc/dubbo-rpc-api(dubbo-rpc-default\|dubbo-rpc-dubbo) module](https://github.com/apache/incubator-dubbo/issues/1695) |
| done |@kimmking | [part-17 : dubbo-rpc/dubbo-rpc-hessian(dubbo-rpc-http\|dubbo-rpc-injvm) module](https://github.com/apache/incubator-dubbo/issues/1696) |
| done | @htynkn | [part-18 : dubbo-rpc/dubbo-rpc-memcached(dubbo-rpc-redis\|dubbo-rpc-rest) modules](https://github.com/apache/incubator-dubbo/issues/1697) |
| done | @kimmking | [part-19 : dubbo-rpc/dubbo-rpc-rmi（dubbo-rpc-thrift\|dubbo-rpc-webservice） modules](https://github.com/apache/incubator-dubbo/issues/1698) |
| done |@htynkn | [part-20 : dubbo-serialization/dubbo-serialization-api(dubbo-serialization-fastjson\|dubbo-serialization-fst) module](https://github.com/apache/incubator-dubbo/issues/1699) |
| done |@diecui1202 | [part-21 : dubbo-serialization/dubbo-serialization-hessian2(dubbo-serialization-jdk\|dubbo-serialization-kryo) modules](https://github.com/apache/incubator-dubbo/issues/1700) | | https://github.com/apache/dubbo/issues/1702 | https://github.com/apache/dubbo/pull/11993 | c2b809adac5681305a1d41530d49881448c57618 | 694de269500f56fcb974eda440205de2735cffad | 2018-04-26T06:15:09Z | java | 2023-04-04T09:12:51Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,698 | ["dubbo-rpc/dubbo-rpc-thrift/src/test/java/org/apache/dubbo/rpc/protocol/thrift/ThriftCodecTest.java"] | Enhance the test coverage part-19 : dubbo-rpc/dubbo-rpc-rmi（dubbo-rpc-thrift|dubbo-rpc-webservice） modules | dubbo-rpc/dubbo-rpc-rmi
dubbo-rpc/dubbo-rpc-thrift
dubbo-rpc/dubbo-rpc-webservice/ | https://github.com/apache/dubbo/issues/1698 | https://github.com/apache/dubbo/pull/2042 | b36a6eea627f9854c909b3a9368ddb06fc6610e4 | ef78bbdbf3f19df412e114b2fea878aa5d06de4d | 2018-04-26T06:02:14Z | java | 2018-07-09T06:16:43Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,696 | ["dubbo-rpc/dubbo-rpc-injvm/src/main/java/org/apache/dubbo/rpc/protocol/injvm/InjvmProtocol.java", "dubbo-rpc/dubbo-rpc-injvm/src/test/java/org/apache/dubbo/rpc/protocol/injvm/InjvmProtocolTest.java", "dubbo-rpc/dubbo-rpc-injvm/src/test/java/org/apache/dubbo/rpc/protocol/injvm/ProtocolTest.java"] | Enhance the test coverage part-17 : dubbo-rpc/dubbo-rpc-hessian(dubbo-rpc-http|dubbo-rpc-injvm) module | Add unit to the modules
dubbo-rpc/dubbo-rpc-hessian
dubbo-rpc/dubbo-rpc-http
dubbo-rpc/dubbo-rpc-injvm | https://github.com/apache/dubbo/issues/1696 | https://github.com/apache/dubbo/pull/2041 | ef78bbdbf3f19df412e114b2fea878aa5d06de4d | 137393c7a76e813f5108fd8e1e4a2ddb57207c38 | 2018-04-26T06:00:25Z | java | 2018-07-09T06:17:16Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,691 | ["dubbo-registry/dubbo-registry-api/src/main/java/com/alibaba/dubbo/registry/RegistryService.java", "dubbo-registry/dubbo-registry-multicast/src/main/java/com/alibaba/dubbo/registry/multicast/MulticastRegistry.java", "dubbo-registry/dubbo-registry-multicast/src/test/java/com/alibaba/dubbo/registry/multicast/MulticastRegistryTest.java"] | Enhance the test coverage part-12: dubbo-registry/dubbo-registry-multicast(dubbo-registry-redis|dubbo-registry-zookeeper) | Add unit test to the modules:
dubbo-registry/dubbo-registry-multicast
dubbo-registry/dubbo-registry-redis
dubbo-registry/dubbo-registry-zookeeper | https://github.com/apache/dubbo/issues/1691 | https://github.com/apache/dubbo/pull/1738 | c459f6c9afc43154fd9a9838f2dc96297dd0ce4d | 8b55a0b31e1c7f9b7d6df5171865bbc11a4d8544 | 2018-04-26T05:52:25Z | java | 2018-06-08T03:41:08Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,688 | ["dubbo-monitor/dubbo-monitor-api/src/test/java/com/alibaba/dubbo/monitor/support/AbstractMonitorFactoryTest.java", "dubbo-monitor/dubbo-monitor-api/src/test/java/com/alibaba/dubbo/monitor/support/MonitorFilterTest.java", "dubbo-monitor/dubbo-monitor-default/src/test/java/com/alibaba/dubbo/monitor/dubbo/DubboMonitorFactoryTest.java", "dubbo-monitor/dubbo-monitor-default/src/test/java/com/alibaba/dubbo/monitor/dubbo/DubboMonitorTest.java", "dubbo-monitor/dubbo-monitor-default/src/test/java/com/alibaba/dubbo/monitor/dubbo/StatisticsTest.java"] | Enhance the test coverage part-9 :dubbo-monitor module | Add unit test to dubbo-monitor module | https://github.com/apache/dubbo/issues/1688 | https://github.com/apache/dubbo/pull/1741 | 6912d9a14fe2c35dee306da9a8e953ba29d736da | 322add3243aaa92f7d56cf68377ff065326337fa | 2018-04-26T05:49:01Z | java | 2018-05-14T07:48:41Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,642 | ["dependencies-bom/pom.xml", "dubbo-rpc/dubbo-rpc-rest/pom.xml", "dubbo-rpc/dubbo-rpc-rest/src/main/java/com/alibaba/dubbo/rpc/protocol/rest/integration/swagger/DubboSwaggerApiListingResource.java", "dubbo-rpc/dubbo-rpc-rest/src/main/java/com/alibaba/dubbo/rpc/protocol/rest/integration/swagger/DubboSwaggerService.java", "dubbo-rpc/dubbo-rpc-rest/src/test/java/com/alibaba/dubbo/rpc/protocol/rest/integration/swagger/DubboSwaggerApiListingResourceTest.java", "dubbo-rpc/dubbo-rpc-rest/src/test/java/com/alibaba/dubbo/rpc/protocol/rest/integration/swagger/SwaggerService.java"] | After the dubbox merge, can we integrate the swagger UI to generate the API documentation for the rest protocol? | dubbo version: `2.6.1`
> dubbox 合并进来后，如何使用swagger来生成rest协议的api文档？或者说，集成swagger UI进来的大致思路是什么呢？
> After the dubbox merge, how do you use the swagger to generate the API documentation for the rest protocol? Or, what's the general idea of integrating the swagger UI? | https://github.com/apache/dubbo/issues/1642 | https://github.com/apache/dubbo/pull/1856 | 04c26e6cb0f07d776769f2e53edd7ef92e078f77 | 71fda0a5fd305d923579161d6c4cdd972f187033 | 2018-04-20T05:51:30Z | java | 2018-06-06T08:27:13Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,641 | ["dubbo-common/src/main/java/org/apache/dubbo/common/status/support/LoadStatusChecker.java"] | [Enhancement] the algorithm of load issue on Windows | @alphatan
---
My research of this problem.
According to [this answer](https://stackoverflow.com/a/28751028/5671078) of the question "Alternate of getSystemLoadAverage() for Windows?", the method `getSystemLoadAverage` of java.lang.management.OperatingSystemMXBean would return `-1` in `Windows`.
It'd be suggested to use `com.sun.management.OperatingSystemMXBean` and its `getSystemCpuLoad()` and `getProcessCpuLoad()` instead.
| https://github.com/apache/dubbo/issues/1641 | https://github.com/apache/dubbo/pull/2631 | ccce69e75fd34a48f02899cb5a61c07742c17c43 | d73831895bc8dc9e85d6818571d6fa17a27ba404 | 2018-04-20T04:47:45Z | java | 2018-10-10T05:48:23Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,638 | ["dubbo-build-tools/pom.xml", "dubbo-dependencies-bom/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper-curator5/pom.xml", "dubbo-dependencies/dubbo-dependencies-zookeeper/pom.xml", "dubbo-dependencies/pom.xml", "dubbo-distribution/pom.xml", "pom.xml"] | [Codecov configuration] PR failing if test coverage went down | As discuss in mail list: https://lists.apache.org/thread.html/cf55ed71de3ebeaa7db3a6a81ee1a6dc86ceeac2c2b185ea56e6391d@%3Cdev.dubbo.apache.org%3E
For pull request, we ask every pull request has necessary unit test.
Codecov has a feature to fail PR if test coverage went down. Which means for any pull request, if it add some code without any unit test, the PR will fail.
This can help to increase test coverage.
Considering tiny change, we need a threshold value which allow the coverage to drop by X%, and posting a success status. Please find more detail in mail list link
Related links:
https://docs.codecov.io/docs/commit-status
https://github.com/codecov/support/issues/351 | https://github.com/apache/dubbo/issues/1638 | https://github.com/apache/dubbo/pull/13460 | 849e108835479bbeefcfd983fd427168a7e4a8a8 | 94725ece64fe9b84a4c2b8a261507d311db057bd | 2018-04-19T13:43:10Z | java | 2023-12-04T13:32:03Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,621 | ["dubbo-dependencies-bom/pom.xml"] | parameter routing | dubbo 有没有计划实现 根据 “参数” 进行路由？ | https://github.com/apache/dubbo/issues/1621 | https://github.com/apache/dubbo/pull/12704 | 57c23c38f794e2f4cdada9735da56cd02843fd72 | e05ef9f7d984da5203732db64b09fd5612754497 | 2018-04-17T16:04:38Z | java | 2023-07-11T01:47:42Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,619 | ["dubbo-dependencies-bom/pom.xml"] | Exception during demo provider start | When running the provider demo (com.alibaba.dubbo.demo.provider.Provider#main), there is an warn message with an exception stack trace as follows:
```sh
[17/04/18 04:30:35:035 CST] main INFO config.AbstractConfig: [DUBBO] The service ready on spring started. service: com.alibaba.dubbo.demo.DemoService, dubbo version: 2.0.0, current host: 30.5.96.22
[17/04/18 04:33:28:028 CST] main WARN config.AbstractConfig: [DUBBO] Address family not supported by protocol family (connect failed), dubbo version: 2.0.0, current host: 30.5.96.22
java.net.ConnectException: Address family not supported by protocol family (connect failed)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:400)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:243)
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:225)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:402)
at java.base/java.net.Socket.connect(Socket.java:591)
at com.alibaba.dubbo.config.ServiceConfig.findConfigedHosts(ServiceConfig.java:577)
at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:469)
at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:357)
at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:316)
at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:215)
at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:121)
at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:50)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:393)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:347)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:883)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:93)
at com.alibaba.dubbo.demo.provider.Provider.main(Provider.java:27)
```
The functionality works fine. However, this will make user confused. We need to avoid this stack trace to be printed. | https://github.com/apache/dubbo/issues/1619 | https://github.com/apache/dubbo/pull/12704 | 57c23c38f794e2f4cdada9735da56cd02843fd72 | e05ef9f7d984da5203732db64b09fd5612754497 | 2018-04-17T10:05:44Z | java | 2023-07-11T01:47:42Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,597 | ["dubbo-filter/dubbo-filter-cache/src/main/java/com/alibaba/dubbo/cache/filter/CacheFilter.java", "dubbo-filter/dubbo-filter-cache/src/test/java/com/alibaba/dubbo/cache/filter/CacheFilterTest.java"] | CacheFilter,when value is null,it will throw NPE(if use ehcache for jcache),why not check null here | com.alibaba.dubbo.cache.filter.CacheFilter
when value is null,it will throw NPE(if use ehcache for jcache),why not check null here?
if the value is null ,maybe we have no need to cache it.
`package com.alibaba.dubbo.cache.filter;
public class CacheFilter implements Filter {
private CacheFactory cacheFactory;
public void setCacheFactory(CacheFactory cacheFactory) {
this.cacheFactory = cacheFactory;
}
public Result invoke(Invoker<?> invoker, Invocation invocation) throws RpcException {
if (cacheFactory != null && ConfigUtils.isNotEmpty(invoker.getUrl().getMethodParameter(invocation.getMethodName(), Constants.CACHE_KEY))) {
Cache cache = cacheFactory.getCache(invoker.getUrl().addParameter(Constants.METHOD_KEY, invocation.getMethodName()));
if (cache != null) {
String key = StringUtils.toArgumentString(invocation.getArguments());
if (cache != null && key != null) {
Object value = cache.get(key);
if (value != null) {
return new RpcResult(value);
}
Result result = invoker.invoke(invocation);
**if (!result.hasException()) {**// should check value null or not ?
cache.put(key, result.getValue());
}
return result;
}
}
}
return invoker.invoke(invocation);
}
}` | https://github.com/apache/dubbo/issues/1597 | https://github.com/apache/dubbo/pull/1828 | d03ff27bd0c2e77689bfe11f16f5e9276dc62081 | a6d8f1c5b20d30b3fe3206332d56bc6de1baa282 | 2018-04-12T10:46:06Z | java | 2018-05-22T07:25:35Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,592 | ["dubbo-dependencies-bom/pom.xml"] | Monitor stats not accurate | 发现一个问题，在启用simple-monitor时，发现第一次调用rpc时，触发MonitorFilter的collect方法时，
Monitor monitor = monitorFactory.getMonitor(url);
if (monitor == null) {
return;
}
此时的monitor为空。后续接着调用rpc时，monitor又不为空。所以怀疑是MonitorFactory延迟加载导致。这里会导致一个问题，就是Collect的数量总是比实际少几条。 | https://github.com/apache/dubbo/issues/1592 | https://github.com/apache/dubbo/pull/10064 | f7957db329c58fd67be0d61d49ccf5cc98971922 | fe135983ed74c0fa5538a44d675cfdb8db9aa9ed | 2018-04-12T01:17:51Z | java | 2022-05-22T01:10:36Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,581 | ["dubbo-dependencies-bom/pom.xml"] | 注册中心怎么通知consumer端知道provider发布了和断开了 | 我现在有个应用，就是在consumer端需要知道目前provider的地址列表，并且provider如果停止了，consumer能够捕捉到相关信息，注册了也可以捕捉到相关信息，谢谢 | https://github.com/apache/dubbo/issues/1581 | https://github.com/apache/dubbo/pull/12566 | dce7b87632acabdcb1c0e1f6527eb3095e0c5992 | 1d74057890315372502b9a30cd3064b713af8bb2 | 2018-04-10T09:37:41Z | java | 2023-06-28T11:55:09Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,530 | ["dubbo-spring-boot/pom.xml"] | dubbo admin manual isn't newest | Hello, I find dubbo has be updated recently. But I found there are some problems, dubbo admin manual isn't newest. So I couldn't install "demo provider", "demo consumer", "simple configuration center", "simple monitor center".
**install demo provider** [http://dubbo.io/books/dubbo-admin-book-en/install/provider-demo.html](url)
**install demo consumer** [http://dubbo.io/books/dubbo-admin-book-en/install/consumer-demo.html](url)
**install simple configuration center** [http://dubbo.io/dubbo-admin-book-en/install/simple-registry-center.html](url)
**install simple monitor center** [http://dubbo.io/dubbo-admin-book-en/install/simple-monitor-center.html](url)
Please update these files, we suppose we could use mvn command to build sub projects, and then in target files to use these demo functions. | https://github.com/apache/dubbo/issues/1530 | https://github.com/apache/dubbo/pull/13074 | 47643da11bc59f946a10942e03e3c5788548a3c1 | 45d72b53bc2590068a5f9d3d3028bcb78ceb3604 | 2018-03-30T08:18:14Z | java | 2023-09-20T01:41:46Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,521 | [".travis.yml", "dubbo-common/src/main/java/com/alibaba/dubbo/common/utils/ReflectUtils.java", "pom.xml"] | Add java9 in CI build | Currently dubbo support java6, java7 and java8.
All unit test pass in java9, we should consider add official support for java9 and even java10.
Currently travis support java9. java10 is in progress (https://github.com/travis-ci/travis-ci/issues/9368)
As discussed in mail list, the first step is to add java9 in travis ci. | https://github.com/apache/dubbo/issues/1521 | https://github.com/apache/dubbo/pull/1575 | 2e84f07203cc1955b1822e0821fa908ea77a20d0 | c25d462ff48c725440393da801e8c614df600248 | 2018-03-28T06:56:49Z | java | 2018-04-10T03:47:50Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,515 | ["pom.xml"] | HTTP协议不像文档描述的那样可以从浏览器，JS中使用呀 | HTTP协议不像文档描述的那样可以从浏览器，JS中使用呀，
使用POSTMAN，和各类浏览器，各种水土不服。。。 | https://github.com/apache/dubbo/issues/1515 | https://github.com/apache/dubbo/pull/13258 | b95ff45e04011f032a71e4c21de2629cc6b8831f | de91ad817e142fb2b3988b50c161475ef2da637b | 2018-03-27T09:28:43Z | java | 2023-10-23T08:32:14Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,513 | ["pom.xml"] | [Suggestion] Add checkstyle for CI | hey team,
I notice there is some unused code (for example: https://github.com/apache/incubator-dubbo/blob/master/hessian-lite/src/main/java/com/alibaba/com/caucho/hessian/io/Hessian2Input.java#L88)
Looks like dubbo doesn't have checkstyle in maven configuration or it doesn't have correct rule.
do we have any plan to add checkstyle check in CI? | https://github.com/apache/dubbo/issues/1513 | https://github.com/apache/dubbo/pull/13258 | b95ff45e04011f032a71e4c21de2629cc6b8831f | de91ad817e142fb2b3988b50c161475ef2da637b | 2018-03-26T12:10:55Z | java | 2023-10-23T08:32:14Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,512 | ["dubbo-spring-boot/pom.xml"] | dubbo service register zookeeper very slow | https://github.com/apache/dubbo/issues/1512 | https://github.com/apache/dubbo/pull/13004 | 60cbc4a5b6ca806636bc58a0215c09c4dcf3217d | 5bf698c368757856cc2438c667074a94327af3ab | 2018-03-26T08:07:39Z | java | 2023-09-04T09:17:13Z |
|
closed | apache/dubbo | https://github.com/apache/dubbo | 1,510 | ["dubbo-config/dubbo-config-api/src/main/java/com/alibaba/dubbo/config/MonitorConfig.java", "dubbo-config/dubbo-config-spring/src/main/resources/META-INF/dubbo.xsd", "dubbo-monitor/dubbo-monitor-api/src/main/java/com/alibaba/dubbo/monitor/support/MonitorFilter.java", "dubbo-monitor/dubbo-monitor-default/src/main/java/com/alibaba/dubbo/monitor/dubbo/DubboMonitor.java"] | dubbo monitor missing parameters | When collect dubbo invoke data, these parameters( `version`,`group`) are missing.
After check monitor module, it will allow user custom monitor interval, but no place to override the default value (60s). | https://github.com/apache/dubbo/issues/1510 | https://github.com/apache/dubbo/pull/1407 | 38f45eec3ad193a7b35ea0f9dfdce7cb30611705 | 2e84f07203cc1955b1822e0821fa908ea77a20d0 | 2018-03-26T07:50:50Z | java | 2018-04-10T02:37:25Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,472 | ["dubbo-dependencies-bom/pom.xml"] | 直连模式参数回调功能抛异常 | 直连模式下，使用参数回调功能Consumer端会抛出以下异常：
Caused by: java.lang.IllegalStateException: Serialized class com.dubbo.callback.Consumer$1 must implement java.io.Serializable | https://github.com/apache/dubbo/issues/1472 | https://github.com/apache/dubbo/pull/11342 | d279cf40521d4d8285103e5bdc1311702efec0d1 | 672691e58df5a63d2e5b7479670f926575df8284 | 2018-03-15T13:02:29Z | java | 2023-01-19T13:04:25Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,447 | ["dubbo-remoting/dubbo-remoting-netty4/src/main/java/com/alibaba/dubbo/remoting/transport/netty4/NettyClient.java", "dubbo-remoting/dubbo-remoting-netty4/src/main/java/com/alibaba/dubbo/remoting/transport/netty4/NettyServer.java", "dubbo-remoting/dubbo-remoting-netty4/src/main/java/com/alibaba/dubbo/remoting/transport/netty4/logging/NettyHelper.java"] | NettyHelper in netty extension populated Logger "InternalLogger" in netty. | 系统中有自己的Netty服务器，同时指定Dubbo用Netty，然后LoggingHandler就没法用了。下面的代码回导致我的Netty服务器无法使用Netty自带的日志体系。如果我强制自己的Netty服务器晚于Dubbo加载，那么Dubbo也是无法使用到DubboLogger的。
```
public class NettyHelper {
public static void setNettyLoggerFactory() {
InternalLoggerFactory factory = InternalLoggerFactory.getDefaultFactory();
if (factory == null || !(factory instanceof DubboLoggerFactory)) {
InternalLoggerFactory.setDefaultFactory(new DubboLoggerFactory());
}
}
```
# Added content in English. Help with Google Translate
System is TCP server using Netty4, and Dubbo is specified to use Netty4. When I add LoggingHandler to ChannelPipeline of my System, The log is not expected.
Like this:
I tracked the code and found the Logger is `com.alibaba.dubbo.remoting.transport.netty4.logging.NettyHelper.DubboLogger` instead of `io.netty.util.internal.logging.Slf4JLogger`. DubboLogger added other content arount the original log. The NeetyHelper replace the InternalLoggerFactory when Dubbo loading, like the code block above shows.
# By the way.
My system build by Spring Boot, use default logging framework which is Slf4j + Logback.
Dubbo's logger is not extend default logger, but replace it.
| https://github.com/apache/dubbo/issues/1447 | https://github.com/apache/dubbo/pull/1717 | 6784375811518a200685e635ee51edc548629971 | 903db35c605709806ef6a91831e5ea2a26a2e8a1 | 2018-03-10T03:28:41Z | java | 2018-05-03T07:07:34Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,439 | ["dubbo-monitor/dubbo-monitor-default/src/main/java/com/alibaba/dubbo/monitor/dubbo/DubboMonitor.java"] | dubbo monitor log | It should be Debug level.
https://github.com/alibaba/dubbo/blob/23084275bf695f41b5f84d927c351e9b2b04a2be/dubbo-monitor/dubbo-monitor-default/src/main/java/com/alibaba/dubbo/monitor/dubbo/DubboMonitor.java#L77 | https://github.com/apache/dubbo/issues/1439 | https://github.com/apache/dubbo/pull/1443 | 8b6f4456d5664f4e7f32b0e772befc4b12086aaa | 98a906a9d24d056b45c3943bdd10b7af60eb8bfb | 2018-03-09T06:54:00Z | java | 2018-04-21T06:27:15Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,422 | ["pom.xml"] | Consumer cannot get the list of providers when use ZK as registry(sometimes it happens). | the bug is：when consumer and provider started at the same time(or it happens in runtime,when cosumer and provider can't connect to zk,and then network recover)，sometimes the consumer will lost the provider list，causing the RpcException。restart consumer or provider will recover it。
code is here：
doSubscribe method id ZookeeperRegistry.java(169-182lines)
```
List<URL> urls = new ArrayList<URL>();
for (String path : toCategoriesPath(url)) {
ConcurrentMap<NotifyListener, ChildListener> listeners = zkListeners.get(url);
if (listeners == null) {
zkListeners.putIfAbsent(url, new ConcurrentHashMap<NotifyListener, ChildListener>());
listeners = zkListeners.get(url);
}
ChildListener zkListener = listeners.get(listener);
if (zkListener == null) {
listeners.putIfAbsent(listener, new ChildListener() {
// A. it will invoke in zk thread,when zk node changed
public void childChanged(String parentPath, List<String> currentChilds) {
ZookeeperRegistry.this.notify(url, listener, toUrlsWithEmpty(url, parentPath, currentChilds));
}
});
zkListener = listeners.get(listener);
}
zkClient.create(path, false);
List<String> children = zkClient.addChildListener(path, zkListener);
if (children != null) {
urls.addAll(toUrlsWithEmpty(url, path, children));
}
}
// B.it will invoke in main thread,or failoverRegister thread
notify(url, listener, urls);
```
notity(url,listener,urls) method will invoke at:
A：it will invoke in zk thread,when zk node changed
B：it will invoke in main thread,or failoverRegister thread
The cause of the problem：
1. when consumer start，before main thread invoke B, thread completes its running slice on the CPU，and wait the next CPU time.at this time（1. provider not registed in zk,the urls is empty list。 2. it registed the zk watch event,will listener to zk node change event.）
2.provider started，registed in zk, the zk node is changed
3.reveive the zk node change event,invoke A in the zk thread。（A will invoke in zk thread，and B will invoke in another thread）
4.At the end of the A method，the consumer obtain the real provider list.
5.main thread obtain the CPU time，invoke B method，and this time urls is empty list。and update the consumer's provider list to empty。it cause the problem
the problem happens A invoke before B,If you can control the method execution order(B invoke before A),the bug will fix。 | https://github.com/apache/dubbo/issues/1422 | https://github.com/apache/dubbo/pull/12218 | 2c1ede9db0e230cae3ec232d21645c0f91bbb1ff | 120db0bf15e7a94c225ece528221903b5c8f04d4 | 2018-03-05T14:13:03Z | java | 2023-05-02T13:47:51Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,390 | ["dubbo-dependencies-bom/pom.xml"] | about "The parameters of execution method of dubbo service are organized by 'Object[]'.will bring 2 problems" | 目前dubbo的requst的方法参数通过Object[]组织的，然后被序列化传输到服务端，服务端再反序列化，这样会涉及到几个问题:
1.基本类型会自动装箱拆箱带来性能影响。
1.基本类型和引用类型参数都被序列化框架一起处理带来性能影响。
代码简写例子:
rpc服务方法
```java
public String say(String name) {
return "hi:" + name;
}
```
rpc服务方法参数封装
```java
class TestServiceSayParam$Generate{
private String name;
public String getParam1() {
return name;
}
public byte[] serialize() {
return name.getBytes();
}
public TestServiceSayParam$Generate unSerialize(byte[] data) {
TestServiceSayParam$Generate param = new TestServiceSayParam$Generate();
param.name = new String(data);
return param;
}
}
```
以上代码分别在服务端和客户端初始化时动态生成，带来的作用:
1.避免基本类型装箱拆箱。
2.基本来下和引用类型分别序列化。
| https://github.com/apache/dubbo/issues/1390 | https://github.com/apache/dubbo/pull/10064 | f7957db329c58fd67be0d61d49ccf5cc98971922 | fe135983ed74c0fa5538a44d675cfdb8db9aa9ed | 2018-02-23T13:32:21Z | java | 2022-05-22T01:10:36Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,385 | ["dubbo-dependencies-bom/pom.xml"] | Consumer annotation config actually unnecessary set basePackages for @DubboComponentScan | from [document](http://dubbo.io/books/dubbo-user-book-en/configuration/annotation.html):
consumer side should set path to scan:
`@DubboComponentScan(basePackages = "com.alibaba.dubbo.test.service")`
but at source code [DubboComponentScanRegistrar](https://github.com/alibaba/dubbo/blob/master/dubbo-config/dubbo-config-spring/src/main/java/com/alibaba/dubbo/config/spring/context/annotation/DubboComponentScanRegistrar.java):
`registerReferenceAnnotationBeanPostProcessor(registry);`
so that no packagesToScan is pass to reference annotation regsiter,
the document should be fixed.
I found this after a wrong package configuration. | https://github.com/apache/dubbo/issues/1385 | https://github.com/apache/dubbo/pull/12177 | d37f4405288541745964f7653950fdc9e029121f | 6e2299653d0c39de9b6dfdc092050d0524d07c25 | 2018-02-22T10:29:02Z | java | 2023-04-25T05:58:45Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,383 | ["dubbo-dependencies-bom/pom.xml"] | Ask for compatible problem | Our system A using dubbo 2.5.3 + Jdk1.6 + ZK 3.3.6 .
Now i want to new dubbo(2.5.9) and jdk (1.8) version in new module B.
Can i upgrade zk to 3.4.6 and keep A using dubbo 2.5.3 + Jdk1.6, and A as consumer , B as provider? | https://github.com/apache/dubbo/issues/1383 | https://github.com/apache/dubbo/pull/11342 | d279cf40521d4d8285103e5bdc1311702efec0d1 | 672691e58df5a63d2e5b7479670f926575df8284 | 2018-02-22T09:51:59Z | java | 2023-01-19T13:04:25Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,367 | ["dubbo-dependencies-bom/pom.xml"] | How to extend the "Exchanger" SPI? I want to add parameters to URL dynamically. | 信息交换扩展，这方面介绍的不多，怎么自定义实现啊？
基于传输层之上，实现 Request-Response 信息交换语义。
<dubbo:protocol exchanger="xxx" />
扩展接口：
com.alibaba.dubbo.remoting.exchange.Exchanger
com.alibaba.dubbo.remoting.exchange.ExchangeServer
com.alibaba.dubbo.remoting.exchange.ExchangeClient
需求：
Dubbo与Spring Session如何共享session？
我把Dubbo配置成http协议，放在Tomcat下。
已经扩展了Spring Session在Cookie、URL里获取sessionId。
现在是在Dubbo下如何扩展在Cookie、URL里设置sessionId？？？
（代码修改量少）
这个Exchanger层是怎么自定义实现的？
我看到里面有URL参数类型，这个是否可以添加URL里的参数，以达到consume端发送调用请求时传送sessionId，Spring Session在provide端拦截URL获取sessionId。
即：Spring Session同步sessionId，以达到session共享。
（解析Spring Session源码，这样是可以达到session共享的在servlet3下）
求指教... | https://github.com/apache/dubbo/issues/1367 | https://github.com/apache/dubbo/pull/11342 | d279cf40521d4d8285103e5bdc1311702efec0d1 | 672691e58df5a63d2e5b7479670f926575df8284 | 2018-02-11T12:49:17Z | java | 2023-01-19T13:04:25Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,366 | ["dubbo-dependencies-bom/pom.xml"] | dubbo admin was installed successfully, but it keeps warning "Zookeeper is not connected yet" | dubbo admin安装后，provider和consumer可以正常发现，但总是出现警告提示 Zookeeper is not connected yet，感觉是dubbo admin(193.0.10.128)一直在连接zookeeper://127.0.0.1:2181/，但配置文件我已经修改了（dubbo.registry.address=zookeeper://193.0.10.129:2181）。配置及报错信息如下：
dubbo admin修改如下：
vi webapps/ROOT/WEB-INF/dubbo.properties
dubbo.properties
dubbo.registry.address=zookeeper://193.0.10.129:2181
dubbo.admin.root.password=root
dubbo.admin.guest.password=guest
报错信息如下：
2018-02-11 14:42:52,991 [DubboRegistryFailedRetryTimer-thread-1] INFO com.alibaba.dubbo.registry.support.FailbackRegistry (FailbackRegistry.java:369) - [DUBBO] Retry subscribe {admin://193.0.10.128?category=providers,consumers,routers,configurators&check=false&classifier=*&enabled=*&group=*&interface=*&version=*=[com.alibaba.dubbo.governance.sync.RegistryServerSync@3d20aa1]}, dubbo version: 2.0.1, current host: 193.0.10.128
2018-02-11 14:42:52,991 [DubboRegistryFailedRetryTimer-thread-1] WARN com.alibaba.dubbo.registry.support.FailbackRegistry (FailbackRegistry.java:380) - [DUBBO] Failed to retry subscribe {admin://193.0.10.128?category=providers,consumers,routers,configurators&check=false&classifier=*&enabled=*&group=*&interface=*&version=*=[com.alibaba.dubbo.governance.sync.RegistryServerSync@3d20aa1]}, waiting for again, cause: Failed to subscribe admin://193.0.10.128?category=providers,consumers,routers,configurators&check=false&classifier=*&enabled=*&group=*&interface=*&version=* to zookeeper zookeeper://127.0.0.1:2181/com.alibaba.dubbo.registry.RegistryService?application=dubbo-admin&check=false&dubbo=2.0.1&file=false&interface=com.alibaba.dubbo.registry.RegistryService&pid=27985×tamp=1518329932598, cause: Zookeeper is not connected yet!, dubbo version: 2.0.1, current host: 193.0.10.128
com.alibaba.dubbo.rpc.RpcException: Failed to subscribe admin://193.0.10.128?category=providers,consumers,routers,configurators&check=false&classifier=*&enabled=*&group=*&interface=*&version=* to zookeeper zookeeper://127.0.0.1:2181/com.alibaba.dubbo.registry.RegistryService?application=dubbo-admin&check=false&dubbo=2.0.1&file=false&interface=com.alibaba.dubbo.registry.RegistryService&pid=27985×tamp=1518329932598, cause: Zookeeper is not connected yet!
at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry.doSubscribe(ZookeeperRegistry.java:185)
at com.alibaba.dubbo.registry.support.FailbackRegistry.retry(FailbackRegistry.java:377)
at com.alibaba.dubbo.registry.support.FailbackRegistry$1.run(FailbackRegistry.java:70)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: Zookeeper is not connected yet!
at com.alibaba.dubbo.remoting.zookeeper.zkclient.ZkClientWrapper.createPersistent(ZkClientWrapper.java:98)
at com.alibaba.dubbo.remoting.zookeeper.zkclient.ZkclientZookeeperClient.createPersistent(ZkclientZookeeperClient.java:61)
at com.alibaba.dubbo.remoting.zookeeper.support.AbstractZookeeperClient.create(AbstractZookeeperClient.java:63)
at com.alibaba.dubbo.registry.zookeeper.ZookeeperRegistry.doSubscribe(ZookeeperRegistry.java:149)
... 9 more
| https://github.com/apache/dubbo/issues/1366 | https://github.com/apache/dubbo/pull/12110 | 9b692fe5dfb6fa32d995423e2888c76fde9dee11 | 9aa6a9e08c12de264dc3d10932b6c69a55de5ab0 | 2018-02-11T07:50:56Z | java | 2023-04-19T02:10:29Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,363 | ["dubbo-dependencies-bom/pom.xml"] | Some problems with use netty4 | use netty version:4.0.36.Final.
the customer and the provider In the same pc.
there have some error log ,but the server is health.
```2018-02-10 17:14:03.055 [main] ERROR com.alibaba.dubbo.qos.server.Server - [DUBBO] qos-server can not bind localhost:22222, dubbo version: 2.6.0, current host: 127.0.0.1``` | https://github.com/apache/dubbo/issues/1363 | https://github.com/apache/dubbo/pull/11342 | d279cf40521d4d8285103e5bdc1311702efec0d1 | 672691e58df5a63d2e5b7479670f926575df8284 | 2018-02-10T09:20:02Z | java | 2023-01-19T13:04:25Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,362 | ["dubbo-config/dubbo-config-api/src/test/java/com/alibaba/dubbo/config/cache/CacheTest.java", "dubbo-filter/dubbo-filter-cache/src/main/java/com/alibaba/dubbo/cache/CacheFactory.java", "dubbo-filter/dubbo-filter-cache/src/main/java/com/alibaba/dubbo/cache/filter/CacheFilter.java", "dubbo-filter/dubbo-filter-cache/src/main/java/com/alibaba/dubbo/cache/support/AbstractCacheFactory.java"] | When using method level cache, no matter what i config, it's always LruCache. | consumer配置：
<dubbo:reference id="demoService" check="false" interface="com.alibaba.dubbo.demo.DemoService">
<dubbo:method name="sayHello" timeout="60000" **cache="threadlocal"**/>
</dubbo:reference>
在执行的过程中，我们发现其实并不会创建ThreadlocalCache，而是用的LruCache，原因是在
可以看到，当将cache配置在方法上而不是服务上的时候，传入的url只有"method.cache"参数而没有"cache"参数，但是CacheFactory$Adaptive这个类并没有作区分。 | https://github.com/apache/dubbo/issues/1362 | https://github.com/apache/dubbo/pull/1396 | 3d4f2fcdbbc327c2dac872962f65b2f011c7d247 | d770d9245c3c3abb3cebf4eda3778ca4595f1542 | 2018-02-10T08:37:37Z | java | 2018-03-05T02:34:41Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,335 | ["dubbo-dependencies-bom/pom.xml"] | We are using DUBBO. | 公司：杭州爱客仕科技有限公司
地址：中国浙江杭州
联系方式： 微信 ceilrain，邮箱：[email protected]
业务场景：内部系统服务化 | https://github.com/apache/dubbo/issues/1335 | https://github.com/apache/dubbo/pull/12500 | 4c67c26c8eb758b266caee5b5b00a7e9a37d8c7a | a01ac38cbf24bbeef62fe3289fe1e40b4ac0e92f | 2018-02-06T06:52:31Z | java | 2023-06-12T11:46:12Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,332 | ["dubbo-dependencies-bom/pom.xml"] | Are you sure? zkclient 0.20 |
| https://github.com/apache/dubbo/issues/1332 | https://github.com/apache/dubbo/pull/12049 | 9b01940d30e7821fa8dff88e87f2cac53c5fbe40 | 87d1b1fcacb8cc1668c32bf830cd7f4b1de5574a | 2018-02-06T02:22:50Z | java | 2023-04-10T11:13:14Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,324 | ["dubbo-dependencies-bom/pom.xml"] | <dubbo:method "oninvoke" injection failure. | <!--配置回调函数 -->
<dubbo:method name="sayHello" oninvoke="callback.oninvoke" onthrow="callback.onthrow" onreturn="callback.onreturn"></dubbo:method> spring 启动报错，如下图
初步定位是DubboBeanDefinitionParser 类下parse方法中，oninvoke 没有像 onreturn（193行附近）那样，将callback.oninvoke 拆解成invoke 和invokeMethod，而是直接将callback.oninvoke当做Bean去处理，导致报错 | https://github.com/apache/dubbo/issues/1324 | https://github.com/apache/dubbo/pull/12049 | 9b01940d30e7821fa8dff88e87f2cac53c5fbe40 | 87d1b1fcacb8cc1668c32bf830cd7f4b1de5574a | 2018-02-05T05:24:19Z | java | 2023-04-10T11:13:14Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,321 | ["dubbo-maven-plugin/pom.xml", "dubbo-native-plugin/pom.xml"] | Will MonitorFilter cause performance problem? | 高并发情况下，当启用了MonitorFilter的时候，请求会不定时的出现高延迟，关闭MonitorFilter后正常。
经过分析，可能出现问题的地方有：
1. 从MonitorFactory中获取Monitor有一个全局锁；
2. getIp(）问题
3. 可能是其他问题。 | https://github.com/apache/dubbo/issues/1321 | https://github.com/apache/dubbo/pull/13476 | 0d418fc40ca68e11ada060f82f6e75e147a27fb5 | a9a3a0975f56a0af1b7c11c4847a43a81cf28269 | 2018-02-05T01:54:12Z | java | 2023-12-12T02:24:11Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,297 | ["dubbo-cluster/src/main/java/com/alibaba/dubbo/rpc/cluster/support/AbstractClusterInvoker.java"] | There's no need to create loadbalancer when invokers is empty. | 
这里，如果invokers为空的话，创建loadbalancer也没有用吧？是否可以去掉？ | https://github.com/apache/dubbo/issues/1297 | https://github.com/apache/dubbo/pull/1376 | ace2f4f3618d168caaf12ff869467bd980586d62 | c7197b0943a5d670a2e5e2d3e313eb63095ff5c7 | 2018-01-30T11:32:13Z | java | 2018-02-24T06:57:38Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,293 | ["dubbo-config/dubbo-config-api/src/main/java/org/apache/dubbo/config/utils/ReferenceConfigCache.java", "dubbo-config/dubbo-config-api/src/test/java/org/apache/dubbo/config/utils/ReferenceConfigCacheTest.java"] | A question for ReferenceConfigCache. | 官网的例子通过ReferenceConfigCache缓存ReferenceConfig实例,
```java
ReferenceConfigCache cache = ReferenceConfigCache.getCache();
// cache.get方法中会缓存 Reference对象，并且调用ReferenceConfig.get方法启动ReferenceConfig
XxxService xxxService = cache.get(reference);
```
源码中cache.get()的实现是先get, 如果== null 再put ReferenceConfig实例, 而没有提供可以由用户判断cache是否已存在的api, 我在通过groovy脚本泛化调用的时候, 需要设定当前应用与注册中心, 然后获取ReferenceConfig实例, 如下:
```java
...
// 连接注册中心配置
RegistryConfig registry = new RegistryConfig();
// 注册中心协议与地址
registry.setAddress("zookeeper://127.0.0.1:2181");
// 当前消费者应用配置
ApplicationConfig application = new ApplicationConfig();
application.setName("consumer-name");
application.setRegistry(registry);
reference.setApplication(application);
ReferenceConfigCache referenceConfigCache = ReferenceConfigCache.getCache();
GenericService genericService = referenceConfigCache.get(reference);
// 泛化调用
genericService.$invoke(XXXX);
```
每一次都会把这个脚本跑一遍, 也就是每一次都会去new RegistryConfig, 和ApplicationConfig这两个实例, 虽然除了第一次以外, ReferenceConfig都是是从原有的cache中获得; 但是并没有符合这个cache工具类的原有目的. 所以ReferenceConfigCache的get()方法能否提供单独的get()方法;
还是我的使用方式不对?
非常感谢~ | https://github.com/apache/dubbo/issues/1293 | https://github.com/apache/dubbo/pull/3505 | 9031a4c20455ba16a63233f10783a55915afcd9b | 7c236ca8f74e6797dac4d432a37294ee8a4529d5 | 2018-01-29T03:45:37Z | java | 2019-02-19T15:09:54Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,283 | ["dependencies-bom/pom.xml", "pom.xml"] | Maven build failed on Java 9 | Trying to build Dubbo on Java 9, I got build failure with the following stack trace:
```
Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end 3, length 1
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3116)
at java.base/java.lang.String.substring(String.java:1885)
at org.apache.commons.lang.SystemUtils.getJavaVersionAsFloat(SystemUtils.java:1133)
at org.apache.commons.lang.SystemUtils.<clinit>(SystemUtils.java:818)
... 59 more
```
Looks like commons-lang does not understand the version semantics of Java 9. | https://github.com/apache/dubbo/issues/1283 | https://github.com/apache/dubbo/pull/1345 | 720dff8456901faaca60ea42501fc94e21804e17 | d3887355484bb9574dd5d94655251b157b0971ba | 2018-01-26T07:29:55Z | java | 2018-02-08T08:09:21Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,260 | ["dubbo-config/dubbo-config-api/src/main/java/com/alibaba/dubbo/config/ReferenceConfig.java"] | typo in ReferenceConfig | ### ReferenceConfig#init , at line 307
change : prifix -> prefix
<img width="746" alt="1" src="https://user-images.githubusercontent.com/6971152/35309902-a22d3ed2-00e9-11e8-9928-e394b9e3d632.png">
### by the way, ReferenceConfig#setInterface , at line 476
it's no need to cast null to String
<img width="903" alt="2" src="https://user-images.githubusercontent.com/6971152/35309908-b09e4a92-00e9-11e8-9725-8e6ff8071370.png">
| https://github.com/apache/dubbo/issues/1260 | https://github.com/apache/dubbo/pull/1272 | 2f7f91ceff52ae885b68aff59a8fde5173b2aff3 | 9ca9bb04b926ba33c6755aff8373314e60f2be89 | 2018-01-24T01:34:25Z | java | 2018-01-25T11:24:48Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,254 | ["dependencies-bom/pom.xml", "dubbo-remoting/dubbo-remoting-http/pom.xml"] | Upgrade tomcat version to 8.5.x | The current dependency to tomcat is 8.0.x, which has been announced as [End of Life](http://tomcat.apache.org/tomcat-80-eol.html) on 30 June 2018.
So we should upgrade tomcat to 8.5.x. | https://github.com/apache/dubbo/issues/1254 | https://github.com/apache/dubbo/pull/1781 | 9c4017e9ba7ba170262f388ac159bcccb11ce209 | 6912d9a14fe2c35dee306da9a8e953ba29d736da | 2018-01-23T02:30:38Z | java | 2018-05-14T07:47:35Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,245 | ["hessian-lite/src/main/java/com/alibaba/com/caucho/hessian/io/JavaDeserializer.java"] | Method invokes inefficient Number constructor | ### JavaDeserializer#getParamArg
<img width="515" alt="1" src="https://user-images.githubusercontent.com/6971152/35181255-599cce00-fdf9-11e7-95b4-7d29314161be.png">
for values that between -128 ~ 127 , autoboxing or call valueOf() is more efficient than using consctrutor , and use less memory .
reference blog :
http://blog.csdn.net/qq_27093465/article/details/52473649
ways to change : change to autoboxing or Xxx.valueOf(0);
### below is the change :
```java
protected static Object getParamArg(Class cl) {
if (!cl.isPrimitive())
return null;
else if (boolean.class.equals(cl))
return Boolean.FALSE;
else if (byte.class.equals(cl))
return 0;
else if (short.class.equals(cl))
return 0;
else if (char.class.equals(cl))
return 0;
else if (int.class.equals(cl))
return 0;
else if (long.class.equals(cl))
return 0L;
else if (float.class.equals(cl))
return 0F;
else if (double.class.equals(cl))
return 0D;
else
throw new UnsupportedOperationException();
}
```
| https://github.com/apache/dubbo/issues/1245 | https://github.com/apache/dubbo/pull/1375 | fddedf66608e99f29ad5cf71d36ff8c04ba63b43 | ddb677bec828771b1dacb670cb96c767c8fb5647 | 2018-01-20T08:11:06Z | java | 2018-02-24T06:20:07Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,216 | ["dubbo-admin/src/main/java/com/alibaba/dubbo/governance/web/governance/module/screen/Providers.java"] | providers.size >= 0 always true | com.alibaba.dubbo.governance.web.governance.module.screen.Providers#getServiceAppMap
at line 133 ， should be providers.size > 0 or just delete this comparison cause the next for will skip if proviers.size == 0 | https://github.com/apache/dubbo/issues/1216 | https://github.com/apache/dubbo/pull/1222 | 64e0fa51e0966ced631146484be7fca94213f04e | b309f792f8b5ebfea16b4cc13720e35306d94b38 | 2018-01-12T15:37:41Z | java | 2018-01-16T07:43:22Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,167 | [".mvn/wrapper/maven-wrapper.jar", ".mvn/wrapper/maven-wrapper.properties", "mvnw", "mvnw.cmd"] | remove maven wrapper | https://github.com/apache/dubbo/issues/1167 | https://github.com/apache/dubbo/pull/1333 | 98c548aab1fef47b29cf7af451b7cd447205ec0a | 61d717834ada7b462f186ffd5628e697c3d5ae6d | 2018-01-04T07:42:55Z | java | 2018-02-07T06:57:35Z |
|
closed | apache/dubbo | https://github.com/apache/dubbo | 1,037 | ["dubbo-maven-plugin/pom.xml", "dubbo-native-plugin/pom.xml"] | ERROR com.alibaba.dubbo.qos.server.Server - [DUBBO] qos-server can not bind localhost:22222, dubbo version: 2.5.8, | ERROR com.alibaba.dubbo.qos.server.Server - [DUBBO] qos-server can not bind localhost:22222, dubbo version: 2.5.8,
我启动了一个服务，一个消费的服务，然后二个绑定的都是22222,怎么修改这个端口号呢？用的springmvc集成的 | https://github.com/apache/dubbo/issues/1037 | https://github.com/apache/dubbo/pull/11869 | 01049311ace1dfc0cbead9aa3cf1e1038fc6db0d | 08f3c6b0185438e43187390505c9639f9d66e60c | 2017-12-13T09:43:31Z | java | 2023-03-23T11:48:52Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,025 | ["dubbo-dependencies-bom/pom.xml"] | Timeline of REST support. | 大概什么时候实现支持 REST ？ | https://github.com/apache/dubbo/issues/1025 | https://github.com/apache/dubbo/pull/12367 | 2277c5826bee1161e617ef6d490aee66ee5c05d2 | 4820d357b072a2a71d0da64c8f101eae6479fcf3 | 2017-12-11T03:33:44Z | java | 2023-05-23T12:11:05Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 1,023 | ["dubbo-dependencies-bom/pom.xml"] | Will upgrade spring to the higher version? | Spring 版本会升级吗？什么时间升级 ？ | https://github.com/apache/dubbo/issues/1023 | https://github.com/apache/dubbo/pull/12367 | 2277c5826bee1161e617ef6d490aee66ee5c05d2 | 4820d357b072a2a71d0da64c8f101eae6479fcf3 | 2017-12-11T01:59:03Z | java | 2023-05-23T12:11:05Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 989 | ["dubbo-dependencies-bom/pom.xml"] | problem with zookeeper+spring boot | There is a problem in our system. We use zookeeper and spring boot. The protocal is dubbo protocal. After the service run for one or two days, this logcat comes out. At first we use zookeeper and spring mvc. And it works fine.
```java
10:06:15 [New I/O server worker #1-3] WARN o.j.n.channel.DefaultChannelPipeline - [DUBBO] An exception was thrown by a user handler while handling an exception event ([id: 0x5f0f8a6d, /11.11.111.111:56890 => /11.11.11.111:41538] EXCEPTION: com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.all.AllChannelHandler error when process received event .), dubbo version: 2.5.3, current host: 11.11.11.111
com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.all.AllChannelHandler error when process caught event .
at com.alibaba.dubbo.remoting.transport.dispatcher.all.AllChannelHandler.caught(AllChannelHandler.java:67)
at com.alibaba.dubbo.remoting.transport.AbstractChannelHandlerDelegate.caught(AbstractChannelHandlerDelegate.java:44)
at com.alibaba.dubbo.remoting.transport.AbstractChannelHandlerDelegate.caught(AbstractChannelHandlerDelegate.java:44)
at com.alibaba.dubbo.remoting.transport.AbstractPeer.caught(AbstractPeer.java:127)
at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.exceptionCaught(NettyHandler.java:112)
at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.exceptionCaught(NettyCodecAdapter.java:165)
at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:432)
at org.jboss.netty.channel.AbstractChannelSink.exceptionCaught(AbstractChannelSink.java:52)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:148)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:351)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:202)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Caused by: java.util.concurrent.RejectedExecutionException: Thread pool is EXHAUSTED! Thread Name: DubboServerHandler-11.11.11.111:41538, Pool Size: 500 (active: 500, core: 500, max: 500, largest: 500), Task: 154422 (completed: 153922), Executor status:(isShutdown:false, isTerminated:false, isTerminating:false), in dubbo://11.11.11.111:41538!
at com.alibaba.dubbo.common.threadpool.support.AbortPolicyWithReport.rejectedExecution(AbortPolicyWithReport.java:53)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372)
at com.alibaba.dubbo.remoting.transport.dispatcher.all.AllChannelHandler.caught(AllChannelHandler.java:65)
... 17 common frames omitted
``` | https://github.com/apache/dubbo/issues/989 | https://github.com/apache/dubbo/pull/12178 | e3600af21a55e42e4c8f106cdf18d24c95467a4a | 3fdd66752a66a5fcede2ec1df52276a6310e8ac7 | 2017-12-04T09:04:52Z | java | 2023-04-24T09:20:19Z |
closed | apache/dubbo | https://github.com/apache/dubbo | 973 | ["dubbo-native-plugin/pom.xml"] | When will the dubbo-springboot-starter be released? | Is there a time schedule? | https://github.com/apache/dubbo/issues/973 | https://github.com/apache/dubbo/pull/11551 | fbf8681aa9da5e063d856d3ca4bfa956cc319e4b | fa62779c5dea914e24e344a0eea0c4f4446328be | 2017-11-30T02:37:08Z | java | 2023-02-14T05:45:27Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.