Re: [DISCUSS] Dubbo Release schedule

[Yong Zhu]

hi, Justin

As John said in
https://lists.apache.org/thread.html/c4bc85049b02b179ef1c785b7c1a3d29c5832e389a93f2b0d91151a0@%3Cdev.dubbo.apache.org%3E

It is not mandatory to change the project groupId to org.apache.dubbo in
the first release. Is that right? We will finished it before graduating.

2018-04-19 8:48 GMT+08:00 Justin Mclean :

> Hi,
>
> > 0. Should we have release manager for these artifacts? Is there any
> > committer volunteer to be release manager?
>
> In general Apache project do have release managers.
>
> > 1. Should we keep the release cycle for 2.6.x?  Our first Apache
> > release might take some time because we have bunch of things to do
> > [1][2][3]. If we need to do keep it, we'd better enter code freeze
> > soon as start to prepare for the release.
>
> I would suggest making a release branch and not doing a code freeze as the
> release may take a little time to get right.
>
> One issue I’m concerned about is IP clearance [1] as that is likely to
> block the release.
>
> Thanks,
> Justin
>
> 1 https://issues.apache.org/jira/browse/DUBBO-3
>
>

[GitHub] myfly150 opened a new issue #1631: Problem when trying script routing rules example in Chapter 6.33 of Dubbo user manual

[GitBox]

myfly150 opened a new issue #1631: Problem when trying script routing rules 
example in Chapter 6.33 of Dubbo user manual 
URL: https://github.com/apache/incubator-dubbo/issues/1631
 
 
   When I tried the  script routing rules example ,  the return value of the 
example script was always the value of "invokers".
   The example script is as follow：
   ```
   function route(invokers) {
   var result = new java.util.ArrayList(invokers.size());
   for (i = 0; i < invokers.size(); i ++) {
   if ("10.20.153.10".equals(invokers.get(i).getUrl().getHost())) {
   result.add(invokers.get(i));
   }
   }
   return result;
   } (invokers); // Indicates that the method is executed immediately
   ```
   According to the grammar of javascript, the meaning of the example script is 
:
   ```
   function route(invokers) { ... } ;
   
   (invokers)  // This is a single expression .The return value is always 
invokers.
   ```
   
   instead of 
   ```
   function route(invokers) { ... } ;
   route(invokers)
   ```
   Actually, brackets surrounding the codeblock is simple solution.
   ```
   (function route(invokers) { ... } (invokers) )
   ```
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [DISCUSS] Dubbo Release schedule

[Jun Liu]

>> 2. What should be included in the 2.6.x release? My suggestion is
>> label the issues and pull request with a milestone like
>> "2.6.2-release”.
> 
> +1 milestone, every committer should check the milestone before a merge or 
> commit.
> Actually, we already have a milestone ‘2.6.2’ tracking issues for this 
> release, only not maintained in time. let me check all the commits and make 
> sure every one being tracked with a issue labeled with 2.6.2 milestone.

BTW, check expected to be done by this week.

> On 19 Apr 2018, at 10:22 AM, Jun Liu  wrote:
> 
> Hi ALL,
> 
>> 0. Should we have release manager for these artifacts? Is there any
>> committer volunteer to be release manager?
> 
> Fortunately, haven't missed this release yet. I’d like to be the release 
> manager for the first apache release.
> 
>> 1. Should we keep the release cycle for 2.6.x?  Our first Apache
>> release might take some time because we have bunch of things to do
>> [1][2][3]. If we need to do keep it, we'd better enter code freeze
>> soon as start to prepare for the release.
> 
> Agree with Justin’s solution, create a new branch for the first release, not 
> freeze the master branch, as it may take some time. 
> 
>> 2. What should be included in the 2.6.x release? My suggestion is
>> label the issues and pull request with a milestone like
>> "2.6.2-release”.
> 
> +1 milestone, every committer should check the milestone before a merge or 
> commit.
> Actually, we already have a milestone ‘2.6.2’ tracking issues for this 
> release, only not maintained in time. let me check all the commits and make 
> sure every one being tracked with a issue labeled with 2.6.2 milestone.
> 
>> 3. Should we have a release cycle for 2.5.x and
>> dubbo-spring-boot-starter? If we do, what the release cycle is?
> 
> My suggestion, no need of release cycle for 2.5.x and boot-starter. 
> Especially for 2.5.x, release whenever it’s needed, usually when reported 
> with important bugs.
> 
>> 4. Should we stop accepting new pull request while we are preparing
>> the release? Since 2.6.x is on the master branch, if we are working on
>> that branch for release, new pull request won't be able to come in.
> 
> A temporary release branch can resolve.
> 
>> 5. Should we keep maintaining 2.5.x branch forever? Or do we have an
>> end of life of 2.5.x and encourage people to migrate to 2.6.x?
> 
> 
> Currently, 2.6.x is the recommend release.
> We will announce EOL some day.
> 
>> On 12 Apr 2018, at 2:36 PM, Huxing Zhang  wrote:
>> 
>> Hi All,
>> 
>> For now, the dubbo community have three release artifact:
>> 1. dubbo 2.6.x
>> 2. dubbo 2.5.x
>> 3. dubbo-spring-boot-starter
>> 
>> The release cycle of 2.6.x is roughly a month, while 2.5.x is
>> uncertain because it is a maintenance branch that only accept bugfix.
>> 
>> dubbo-spring-boot-starter only have 1 release until now, and depends
>> on the dubbo 2.6.x.
>> 
>> Since we are going to have our first Apache release, I have a couple
>> of questions and would like to discuss with the community:
>> 
>> 0. Should we have release manager for these artifacts? Is there any
>> committer volunteer to be release manager?
>> 
>> 1. Should we keep the release cycle for 2.6.x?  Our first Apache
>> release might take some time because we have bunch of things to do
>> [1][2][3]. If we need to do keep it, we'd better enter code freeze
>> soon as start to prepare for the release.
>> 
>> 2. What should be included in the 2.6.x release? My suggestion is
>> label the issues and pull request with a milestone like
>> "2.6.2-release".
>> 
>> 3. Should we have a release cycle for 2.5.x and
>> dubbo-spring-boot-starter? If we do, what the release cycle is?
>> 
>> 4. Should we stop accepting new pull request while we are preparing
>> the release? Since 2.6.x is on the master branch, if we are working on
>> that branch for release, new pull request won't be able to come in.
>> 
>> 5. Should we keep maintaining 2.5.x branch forever? Or do we have an
>> end of life of 2.5.x and encourage people to migrate to 2.6.x?
>> 
>> [1] http://www.apache.org/dev/#releases
>> [2] https://incubator.apache.org/guides/releasemanagement.html
>> [3] https://rocketmq.apache.org/docs/release-manual
>> 
>> -- 
>> Best Regards！
>> Huxing
> 

[GitHub] zonghaishang opened a new pull request #1630: [Dubbo- checkstyle not working for jdk7 ] active checkstyle for jdk7.

[GitBox]

zonghaishang opened a new pull request #1630: [Dubbo- checkstyle not working 
for jdk7 ] active checkstyle for jdk7.
URL: https://github.com/apache/incubator-dubbo/pull/1630
 
 
   ## What is the purpose of the change
   
   1. active checkstyle for jdk7.
   
   ## Brief changelog
   
   1. pom.xml `[1.8,)[1.7,)https://github.com/apache/incubator-dubbo/issues) filed for the 
change (usually before you start working on it). Trivial changes like typos do 
not require a GITHUB issue. Your pull request should address just this issue, 
without pulling in other changes - one PR resolves one issue.
   - [x] Format the pull request title like `[Dubbo-XXX] Fix UnknownException 
when host config not exist #XXX`. Each commit in the pull request should have a 
meaningful subject line and body.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [ ] Write necessary unit-test to verify your logic correction, more mock a 
little better when cross module dependency exist. If the new feature or 
significant change is committed, please remember to add integration-test in 
[test module](https://github.com/alibaba/dubbo/tree/master/dubbo-test).
   - [ ] Run `mvn clean install -DskipITs` to make sure unit-test pass. Run 
`mvn clean test-compile failsafe:integration-test`  to make sure 
integration-test pass.
   - [ ] If this contribution is large, please follow the [Software Donation 
Guide](https://github.com/apache/incubator-dubbo/wiki/Software-donation-guide).
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [DISCUSS] Dubbo Release schedule

[Jun Liu]

Hi ALL,

> 0. Should we have release manager for these artifacts? Is there any
> committer volunteer to be release manager?

Fortunately, haven't missed this release yet. I’d like to be the release 
manager for the first apache release.

> 1. Should we keep the release cycle for 2.6.x?  Our first Apache
> release might take some time because we have bunch of things to do
> [1][2][3]. If we need to do keep it, we'd better enter code freeze
> soon as start to prepare for the release.

Agree with Justin’s solution, create a new branch for the first release, not 
freeze the master branch, as it may take some time. 

> 2. What should be included in the 2.6.x release? My suggestion is
> label the issues and pull request with a milestone like
> "2.6.2-release”.

+1 milestone, every committer should check the milestone before a merge or 
commit.
Actually, we already have a milestone ‘2.6.2’ tracking issues for this release, 
only not maintained in time. let me check all the commits and make sure every 
one being tracked with a issue labeled with 2.6.2 milestone.

> 3. Should we have a release cycle for 2.5.x and
> dubbo-spring-boot-starter? If we do, what the release cycle is?

My suggestion, no need of release cycle for 2.5.x and boot-starter. Especially 
for 2.5.x, release whenever it’s needed, usually when reported with important 
bugs.

> 4. Should we stop accepting new pull request while we are preparing
> the release? Since 2.6.x is on the master branch, if we are working on
> that branch for release, new pull request won't be able to come in.

A temporary release branch can resolve.

> 5. Should we keep maintaining 2.5.x branch forever? Or do we have an
> end of life of 2.5.x and encourage people to migrate to 2.6.x?


Currently, 2.6.x is the recommend release.
We will announce EOL some day.

> On 12 Apr 2018, at 2:36 PM, Huxing Zhang  wrote:
> 
> Hi All,
> 
> For now, the dubbo community have three release artifact:
> 1. dubbo 2.6.x
> 2. dubbo 2.5.x
> 3. dubbo-spring-boot-starter
> 
> The release cycle of 2.6.x is roughly a month, while 2.5.x is
> uncertain because it is a maintenance branch that only accept bugfix.
> 
> dubbo-spring-boot-starter only have 1 release until now, and depends
> on the dubbo 2.6.x.
> 
> Since we are going to have our first Apache release, I have a couple
> of questions and would like to discuss with the community:
> 
> 0. Should we have release manager for these artifacts? Is there any
> committer volunteer to be release manager?
> 
> 1. Should we keep the release cycle for 2.6.x?  Our first Apache
> release might take some time because we have bunch of things to do
> [1][2][3]. If we need to do keep it, we'd better enter code freeze
> soon as start to prepare for the release.
> 
> 2. What should be included in the 2.6.x release? My suggestion is
> label the issues and pull request with a milestone like
> "2.6.2-release".
> 
> 3. Should we have a release cycle for 2.5.x and
> dubbo-spring-boot-starter? If we do, what the release cycle is?
> 
> 4. Should we stop accepting new pull request while we are preparing
> the release? Since 2.6.x is on the master branch, if we are working on
> that branch for release, new pull request won't be able to come in.
> 
> 5. Should we keep maintaining 2.5.x branch forever? Or do we have an
> end of life of 2.5.x and encourage people to migrate to 2.6.x?
> 
> [1] http://www.apache.org/dev/#releases
> [2] https://incubator.apache.org/guides/releasemanagement.html
> [3] https://rocketmq.apache.org/docs/release-manual
> 
> -- 
> Best Regards！
> Huxing

Re: [DISCUSS] Dubbo Release schedule

[Von Gosling]

Hi,

> I would suggest making a release branch and not doing a code freeze as the 
> release may take a little time to get right.
> 
> One issue I’m concerned about is IP clearance [1] as that is likely to block 
> the release.

I would like to follow and double-check the IP clearance process, any block 
about here now ?



>> 0. Should we have release manager for these artifacts? Is there any
>> committer volunteer to be release manager?
> 
> In general Apache project do have release managers.


Yes. IMO, we’d better make clear the release process before we ask for the 
release manager, right ? Here is some hint[1] about release process from other 
Apache Project. 


[1] http://rocketmq.apache.org/docs/release-manual

Best Regards,
Von Gosling

> 在 2018年4月19日，08:48，Justin Mclean  写道：
> 
> Hi,
> 
>> 0. Should we have release manager for these artifacts? Is there any
>> committer volunteer to be release manager?
> 
> In general Apache project do have release managers.
> 
>> 1. Should we keep the release cycle for 2.6.x?  Our first Apache
>> release might take some time because we have bunch of things to do
>> [1][2][3]. If we need to do keep it, we'd better enter code freeze
>> soon as start to prepare for the release.
> 
> I would suggest making a release branch and not doing a code freeze as the 
> release may take a little time to get right.
> 
> One issue I’m concerned about is IP clearance [1] as that is likely to block 
> the release.
> 
> Thanks,
> Justin
> 
> 1 https://issues.apache.org/jira/browse/DUBBO-3
> 

[GitHub] goal578 opened a new issue #1628: dubbo 进程状态资讯

[GitBox]

goal578 opened a new issue #1628: dubbo 进程状态资讯
URL: https://github.com/apache/incubator-dubbo/issues/1628
 
 
   生产系统有个dubbo服务偶尔出现客户端连不上了，但是telnet Ip 端口是可以通。然后用 telnet 命令 看相关状态，请问有些参数设么意思？如 
max,total,task
   
++++
   | resource   | status | message  
  |
   
++++
   | spring | OK | applicationContext.xml   
  |
   | memory | OK | max:8122M,total:8122M,used:2996M,free:5126M  
  |
   | threadpool | OK | Pool status:OK, max:100, core:100, largest:100, 
active:2, task:2821428, service port: 
   | load   | OK | load:0.99,cpu:4  
  |
   | summary| OK |  
  |
   
++++
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [DISCUSS] Dubbo Release schedule

[Justin Mclean]

Hi,

> 0. Should we have release manager for these artifacts? Is there any
> committer volunteer to be release manager?

In general Apache project do have release managers.

> 1. Should we keep the release cycle for 2.6.x?  Our first Apache
> release might take some time because we have bunch of things to do
> [1][2][3]. If we need to do keep it, we'd better enter code freeze
> soon as start to prepare for the release.

I would suggest making a release branch and not doing a code freeze as the 
release may take a little time to get right.

One issue I’m concerned about is IP clearance [1] as that is likely to block 
the release.

Thanks,
Justin

1 https://issues.apache.org/jira/browse/DUBBO-3

Re: [DISCUSS] Dubbo Release schedule

[Huxing Zhang]

Ping.

On Thu, 12 Apr 2018 at 14:36, Huxing Zhang  wrote:

> Hi All,
>
> For now, the dubbo community have three release artifact:
> 1. dubbo 2.6.x
> 2. dubbo 2.5.x
> 3. dubbo-spring-boot-starter
>
> The release cycle of 2.6.x is roughly a month, while 2.5.x is
> uncertain because it is a maintenance branch that only accept bugfix.
>
> dubbo-spring-boot-starter only have 1 release until now, and depends
> on the dubbo 2.6.x.
>
> Since we are going to have our first Apache release, I have a couple
> of questions and would like to discuss with the community:
>
> 0. Should we have release manager for these artifacts? Is there any
> committer volunteer to be release manager?
>
> 1. Should we keep the release cycle for 2.6.x?  Our first Apache
> release might take some time because we have bunch of things to do
> [1][2][3]. If we need to do keep it, we'd better enter code freeze
> soon as start to prepare for the release.
>
> 2. What should be included in the 2.6.x release? My suggestion is
> label the issues and pull request with a milestone like
> "2.6.2-release".
>
> 3. Should we have a release cycle for 2.5.x and
> dubbo-spring-boot-starter? If we do, what the release cycle is?
>
> 4. Should we stop accepting new pull request while we are preparing
> the release? Since 2.6.x is on the master branch, if we are working on
> that branch for release, new pull request won't be able to come in.
>
> 5. Should we keep maintaining 2.5.x branch forever? Or do we have an
> end of life of 2.5.x and encourage people to migrate to 2.6.x?
>
> [1] http://www.apache.org/dev/#releases
> [2] https://incubator.apache.org/guides/releasemanagement.html
> [3] https://rocketmq.apache.org/docs/release-manual
>
> --
> Best Regards！
> Huxing
>
-- 
Best Regards！
Huxing

[GitHub] zonghaishang opened a new pull request #1627: [Dubbo- demo easy to use ] enhance for demo start.

[GitBox]

zonghaishang opened a new pull request #1627: [Dubbo- demo easy to use ] 
enhance for demo start.
URL: https://github.com/apache/incubator-dubbo/pull/1627
 
 
   ## What is the purpose of the change
   
   Start dubbo in a more elegant way, see： 
https://github.com/apache/incubator-dubbo/issues/1626
   
   ## Brief changelog
   
   1.  enhancement for dubbo-demo startup.
   
   ## Verifying this change
   
   1. run `com.alibaba.dubbo.demo.provider.Provider#main`
   2. run `com.alibaba.dubbo.demo.consumer.Consumer#main`
   
   Follow this checklist to help us incorporate your contribution quickly and 
easily:
   
   - [x] Make sure there is a 
[GITHUB_issue](https://github.com/apache/incubator-dubbo/issues) filed for the 
change (usually before you start working on it). Trivial changes like typos do 
not require a GITHUB issue. Your pull request should address just this issue, 
without pulling in other changes - one PR resolves one issue.
   - [x] Format the pull request title like `[Dubbo-XXX] Fix UnknownException 
when host config not exist #XXX`. Each commit in the pull request should have a 
meaningful subject line and body.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [ ] Write necessary unit-test to verify your logic correction, more mock a 
little better when cross module dependency exist. If the new feature or 
significant change is committed, please remember to add integration-test in 
[test module](https://github.com/alibaba/dubbo/tree/master/dubbo-test).
   - [x] Run `mvn clean install -DskipITs` to make sure unit-test pass. Run 
`mvn clean test-compile failsafe:integration-test`  to make sure 
integration-test pass.
   - [ ] If this contribution is large, please follow the [Software Donation 
Guide](https://github.com/apache/incubator-dubbo/wiki/Software-donation-guide).
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] zonghaishang opened a new issue #1626: Improve dubbo-demo startup

[GitBox]

zonghaishang opened a new issue #1626: Improve dubbo-demo startup
URL: https://github.com/apache/incubator-dubbo/issues/1626
 
 
   1. In the development environment may use dubbo-admin, using a new startup 
method to facilitate the user to use elegant shutdown features.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] warriorSL2016 commented on issue #947: fix: 运行demo的时候，连接无线网，默认会获取IPv6 地址，导致报错

[GitBox]

warriorSL2016 commented on issue #947: fix: 运行demo的时候，连接无线网，默认会获取IPv6 地址，导致报错
URL: https://github.com/apache/incubator-dubbo/pull/947#issuecomment-382391000
 
 
   我也遇到这个恶心的问题了, 使用   , 
运行官网实例的dubbo-demo项目, 并且还是使用提示的使用debug,或者配置-Djava.net.preferIPv4Stack=true, 
防止使用ipv6, 服务方能正常启动, 但是消费方根本就找不到服务, 请给出解释, 浪费了很长时间错误栈如下:
   
   com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method sayHello in 
the service com.alibaba.dubbo.demo.DemoService. No provider available for the 
service com.alibaba.dubbo.demo.DemoService from registry 224.5.6.7:1234 on the 
consumer 192.168.2.110 using the dubbo version 2.0.0. Please check if the 
providers have been started and registered.
at 
com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.checkInvokers(AbstractClusterInvoker.java:252)
at 
com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:55)
at 
com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:233)
at 
com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:70)
at 
com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:51)
at com.alibaba.dubbo.common.bytecode.proxy0.sayHello(proxy0.java)
at com.alibaba.dubbo.demo.consumer.Consumer.main(Consumer.java:35)
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] zistrong commented on issue #617: Dubbo的最佳实践是什么

[GitBox]

zistrong commented on issue #617: Dubbo的最佳实践是什么
URL: https://github.com/apache/incubator-dubbo/issues/617#issuecomment-382389412
 
 
   provider启动一个java进程就行了。 为啥还要放到javaee容器中。


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] DayuZhu closed issue #766: dubbo-admin-2.5.6启动日志报错 ERROR 但控制台可访问

[GitBox]

DayuZhu closed issue #766: dubbo-admin-2.5.6启动日志报错 ERROR 但控制台可访问
URL: https://github.com/apache/incubator-dubbo/issues/766
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] DayuZhu closed issue #617: Dubbo的最佳实践是什么

[GitBox]

DayuZhu closed issue #617: Dubbo的最佳实践是什么
URL: https://github.com/apache/incubator-dubbo/issues/617
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] DayuZhu opened a new issue #1625: Dubbo的开发文档勘误

[GitBox]

DayuZhu opened a new issue #1625: Dubbo的开发文档勘误
URL: https://github.com/apache/incubator-dubbo/issues/1625
 
 
   1，Dubbo的开发文档中文版中的框架设计 整体设计图的 ExchangeExchangeSerever 是不是拼写错误？！
   2，DubboHandler这个handler还有么？尴尬的是我没有搜到！
   [
   ![qq 
20180418175356](https://user-images.githubusercontent.com/18682988/38925416-22795fbe-4332-11e8-8d13-6b0b8e3addc1.png)
   ](url)
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] kkillala commented on issue #1307: dubbo-admin没了？

[GitBox]

kkillala commented on issue #1307: dubbo-admin没了？
URL: 
https://github.com/apache/incubator-dubbo/issues/1307#issuecomment-382333182
 
 
   @web1992 谢了兄弟。


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] kkillala commented on issue #1603: dubbo-admin 模块去哪了？

[GitBox]

kkillala commented on issue #1603: dubbo-admin 模块去哪了？
URL: 
https://github.com/apache/incubator-dubbo/issues/1603#issuecomment-382332610
 
 
   去哪了啊？


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] beiwei30 commented on issue #1618: dubbo admin on windows

[GitBox]

beiwei30 commented on issue #1618: dubbo admin on windows
URL: 
https://github.com/apache/incubator-dubbo/issues/1618#issuecomment-382313778
 
 
   ```sh
   java.lang.NoSuchMethodError: 
java.util.concurrent.ConcurrentHashMap.keySet()Ljava/util/concurrent/ConcurrentHashMap$KeySetView;
   ```
   
   This exception is usually caused by run java8 compiled code in java 7 or 
below. Pls. try to recompile both dubbo and dubbo-admin, and try again.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] beiwei30 closed issue #1618: dubbo admin on windows

[GitBox]

beiwei30 closed issue #1618: dubbo admin on windows
URL: https://github.com/apache/incubator-dubbo/issues/1618
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] Caochonger commented on issue #1012: Wanted: who's using dubbo

[GitBox]

Caochonger commented on issue #1012: Wanted: who's using dubbo
URL: 
https://github.com/apache/incubator-dubbo/issues/1012#issuecomment-382309925
 
 
   公司：个人组织
   地址：中国北京
   联系方式：xbj.sh...@foxmail.com
   场景：分布式服务扩展


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] takeseem commented on issue #1609: incomplete: Fix hessian2 serialized short, byte is converted to int bug (#1232)

[GitBox]

takeseem commented on issue #1609: incomplete: Fix hessian2 serialized short, 
byte is converted to int bug (#1232)
URL: 
https://github.com/apache/incubator-dubbo/issues/1609#issuecomment-382290066
 
 
   今天仔细看下代码，hessian1确实没有用了，建议从hessian-lite中移除。


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] lovepoem closed pull request #19: typo fix

[GitBox]

lovepoem closed pull request #19: typo fix
URL: https://github.com/apache/incubator-dubbo-docs/pull/19
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/dubbo-user-book/preface/architecture.md 
b/dubbo-user-book/preface/architecture.md
index 2b0f5b2..62dcb22 100644
--- a/dubbo-user-book/preface/architecture.md
+++ b/dubbo-user-book/preface/architecture.md
@@ -34,7 +34,7 @@ Dubbo 架构具有以下几个特点，分别是连通性、健壮性、伸缩
 * 注册中心和监控中心全部宕机，不影响已运行的提供者和消费者，消费者在本地缓存了提供者列表
 * 注册中心和监控中心都是可选的，服务消费者可以直连服务提供者
 
-## 健状性
+## 健壮性
 
 * 监控中心宕掉不影响使用，只是丢失部分采样数据
 * 数据库宕掉后，注册中心仍能通过缓存提供服务列表查询，但不能注册新服务


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] shawnsky opened a new pull request #19: typo fix

[GitBox]

shawnsky opened a new pull request #19: typo fix
URL: https://github.com/apache/incubator-dubbo-docs/pull/19
 
 
   user book typo fix: 健状性->健壮性


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services