+1 (binding)
zzz...@gmail.com 于2021年6月24日周四 上午9:08写道：
> +1 (binding)
>
> ---Original---
> *From:* "bismy"
> *Date:* Tue, Jun 22, 2021 20:43 PM
> *To:* "dev";
> *Subject:* [VOTE] Release Apache ServiceComb Java-Chassis version 2.3.0
>
> Hello All,
>
>
> This is a call for a Vote to release
+1 binding
bismy 于2021年2月26日周五 上午10:20写道：
> Hello All,
>
> This is a call for a Vote to release Apache ServiceComb Java-Chassis
> version 2.2.0
>
> Release Notes :
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12349527
>
> Release Candidate :
>
+1
bismy 于2021年2月9日周二 下午5:48写道：
> Hi all,
>
>
> In order to meet customers requirements of continuous intergration, I am
> going to change the schedule of java chassis release plan. As
>
>
> 1. release minor versions without vote and no RN is provided. e.g. I will
> release 2.1.6, 2.1.7, etc at
+1 (binding)
bismy 于2021年1月20日周三 下午2:41写道：
> This is my +1
>
>
>
>
> --原始邮件--
> 发件人:
> "dev"
> <
> willem.ji...@gmail.com;
> 发送时间:2021年1月19日(星期二)
+1 (Binding)
checked: mvn clean install -Pit
Willem Jiang 于2020年12月29日周二 下午3:40写道：
> +1. （Binding）
> I checked the release note， git tag， source kit.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Dec 28, 2020 at 5:43 PM bismy wrote:
> >
> > Hello All,
> >
> > This is
+1 (binding)
* maven clean install -Pit
* verified by a business framework based on 2.1.3
Willem Jiang 于2020年11月27日周五 下午10:59写道：
> +1 (binding)
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Nov 27, 2020 at 5:10 PM bismy wrote:
> >
> > Hello All,
> >
> > This is a
+1
checked mvn clean install -Pit
bismy 于2020年10月28日周三 下午3:17写道：
> Hello All,
>
> This is a call for a Vote to release Apache ServiceComb Java-Chassis
> version 1.3.1
>
> Release Notes :
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12346561
>
> Release Candidate
+1
checked mvn clean install -Pit
bismy 于2020年10月28日周三 上午9:30写道：
> Hello All,
>
> This is a call for a Vote to release Apache ServiceComb Java-Chassis
> version 2.1.2
>
> Release Notes :
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626version=12348680
>
> Release
+1
checked mvn clean install -Pit
yhs0092 于2020年8月12日周三 上午11:55写道：
> +1
> I have checked,
> local build is OK,
>
> tag and commitId is OK.
>
>
>
>
>
> Yours sincerely
>
>
> Yao Haishi
> yhs0...@163.com
>
>
> At 2020-08-12 11:09:50, "bismy" wrote:
> >Hello All,
> >
> >This is a call for a Vote
+1
checked mvn clean install -Pit
bismy 于2020年8月12日周三 上午10:51写道：
> Hello All,
>
> This is a call for a Vote to release Apache ServiceComb Java-Chassis
> version 2.1.1
>
> Release Notes :
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626version=12348418
>
> Release
+1 Binding.
Build from source OK.
Rat check OK.
yhs0092 于2020年6月30日周二 下午2:09写道：
> +1 binding
>
>
> I have checked,
> 1. Release commit id and Tag are good.
> 2. mvn clean install -Pit build is good.
> 3. source code of Release Candidate is consistent with GitHub code repo.
>
>
> Yours
another way is not conside compatible
old project use old extensions, but we mark old extensions deprecated, and
delete them after months
new project use new filter extension
wjm wjm 于2020年5月26日周二 上午9:39写道：
> in compatible mode, default filter chain is:
>
> servicecomb:
> f
ang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, May 25, 2020 at 3:37 PM wjm wjm wrote:
> >
> > thanks for the reply,
> >
> > for your question, the wrapper maybe like:
> >
> > class WrapHandlersToFilter implements Filter{
> &
IRA.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, May 22, 2020 at 5:32 PM wjm wjm wrote:
> >
> > please read content in: https://issues.apache.org/jira/browse/SCB-1929#
>
please read content in: https://issues.apache.org/jira/browse/SCB-1929#
+1
RKD <2513931...@qq.com> 于2020年3月23日周一 下午9:09写道：
> +1
>
>
>
>
> --Original--
> From:"bismy" Date:Mon, Mar 23, 2020 07:48 PM
> To:"dev"
> Subject:[VOTE] Release Apache ServiceComb Java-Chassis version 2.0.1
>
>
>
> Hello All,
>
> This is a call for a Vote to
+1
- git tag and commit id is OK.
- mvn clean install -Pit build OK.
Willem Jiang 于2020年2月20日周四 上午8:59写道：
> I guess it may relate to the docker maven plugin, it looks the version
> is too old :(.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Feb 19, 2020 at 12:07 PM
+1
Liubao (A) 于2019年8月12日周一 上午9:46写道：
> +1
>
> Thanks
>
> -邮件原件-
> 发件人: LA [mailto:liang951...@qq.com]
> 发送时间: 2019年8月9日 17:23
> 收件人: dev
> 主题: [DISCUSSION] Set all dependency version as properties in
> java-chasis-dependencies
>
> Hi Team,
>
>
> In java-chasis-dependencies, some
to fix them
> after the weak type work is finished.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Jul 6, 2019 at 11:46 AM wjm wjm wrote:
>
> ohoh, lots of source files? maybe cause very difficult to merge weak type
> branch?
>
> yhs009
ohoh, lots of source files? maybe cause very difficult to merge weak type
branch?
yhs0092 于2019年7月5日周五 下午7:43写道：
> Hi, guys. I've run code static checks for the source code of
> ServiceComb-Java-Chassis and find several potential problems.
> I want to raise an issue to fix these problems. The
+1
在 2019年6月21日星期五，Zheng Feng 写道：
> +1 binding
>
> Xiaoliang Tian 于2019年6月21日周五 下午4:41写道：
>
> > Hi All,
> >this is a call for vote to bring service mesh called "mesher" into
> > Apache Software Foundation (ASF) as ServiceComb's sub-project.
> >
> >
> > Voting will start now ( Wednesday,
Welcome ~
Zheng Feng 于2019年6月20日周四 上午9:46写道：
> Welcome to the team !
>
> Willem Jiang 于2019年6月20日周四 上午9:25写道：
>
> > Please join me and the rest of the ServiceComb PMC members in welcoming
> our
> > new ServiceComb committer: Tian Xiaoliang (田晓亮).
> >
> > Tian Xiaoliang has been with Apache
+1
Liubao (A) 于2019年6月10日周一 上午11:27写道：
> +1. Glad to have this meetup.
>
> -邮件原件-
> 发件人: Willem Jiang [mailto:willem.ji...@gmail.com]
> 发送时间: 2019年6月10日 11:02
> 收件人: dev
> 主题: Re: Proposal for Holding an Apache ServiceComb Meetup as a Co-located
> Event in KubeCon & CloudNativeCon
Congratulations
Liubao (A) 于2019年6月10日周一 上午11:26写道：
> Congratulations to Yao Haishi.
>
> -邮件原件-
> 发件人: Zhang Lei [mailto:zhang_...@boco.com.cn]
> 发送时间: 2019年6月10日 11:05
> 收件人: dev@servicecomb.apache.org
> 主题: Re: Announce of new ServiceComb PMC member
>
> Congratulations.
>
> Lei
+1
Zen Lin 于2019年6月10日周一 上午9:49写道：
> +1 (binding)
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
>
> Liubao (A) 于2019年6月10日周一 上午9:09写道：
>
> > +1
> >
> > -邮件原件-
> > 发件人: Willem Jiang [mailto:willem.ji...@gmail.com]
> >
+1
Bin Ma 于2019年5月28日周二 下午7:37写道：
> Thanks for your suggestions, I will get the scenarios you provided and put
> into the roadmap of the toolkit to consider how to implement.
>
>
> Best Wishes & Regards
> ---
> Mabin
>
>
>
> Liubao (A) 于2019年5月28日周二 上午9:52写道：
>
> >
+1
Liubao (A) 于2019年5月20日周一 下午8:28写道：
> Thank you for your kindly reminding. This is a call for a vote.
>
> -邮件原件-
> 发件人: Willem Jiang [mailto:willem.ji...@gmail.com]
> 发送时间: 2019年5月20日 19:24
> 收件人: dev
> 主题: Re: [PROPOSAL]create a new project servicecomb-fence
>
> @Liubao，
>
> +1 for
+1 (binding)
Checked basic function of ServiceComb-Java-Chassis
Jean-Baptiste Onofré 于2019年5月15日周三 下午9:46写道：
> +1 (binding)
>
> Regards
> JB
>
> On 13/05/2019 12:16, Mohammad Asif Siddiqui wrote:
> > Hello All,
> >
> > This is a call for a Vote to release Apache ServiceComb Java-Chassis
>
+1
greate!!!
Liubao (A) 于2019年5月13日周一 下午4:51写道：
> Hi,
>
> I am working on integrating spring security to java-chassis to make
> developing authentication and authorization management easier. Now I have
> finished the framework and basic authorization management.
>
> This work is shown in [1].
>
yes, already merged.
Willem Jiang 于2019年5月9日周四 上午1:02写道：
> Please make sure the PR is merged, then we can start cut a new release
> again.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 8, 2019 at 9:15 AM wjm wjm wrote:
> >
-1 (binding)
@yaohai...@huawei.com
this problem is caused by [SCB-1046] 2018/12/8 in 1.2.0
i have merged your PR
Jean-Baptiste Onofré 于2019年5月8日周三 下午1:21写道：
> +1 (binding)
>
> Regards
> JB
>
> On 06/05/2019 08:21, Mohammad Asif Siddiqui wrote:
> > Hello All,
> >
> > This is a call for a
i notice that we have gpg file in project:
https://github.com/apache/servicecomb-java-chassis/blob/master/gpg-sec.tar.enc
because we did not use automic release, the gpg file is useless, can we
delete it?
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Apr 29, 2019 at 8:37 AM wjm wjm wrote:
> >
> > create 1.2.1 branch based on current master(1.3.0-SNAPSHOT)
> > or create a new branch based on 1.2.0 and then cherry pick?
> >
> > Willem Jiang
there are some important fix for 1.2.0
- when create microservice meta failed, will destroy failed meta, but
leak to destroy related configuration resources, rarely happen, but it's a
leak problem.
- when log framework is log4j2, will leak some log4j2 marker object for
every
https://github.com/apache/servicecomb-java-chassis/pull/1180
inspector of configuration need to change some value to "**", eg:
password
+1
yhs0092 于2019年4月12日周五 上午11:09写道：
> Hi, currently our integration tests will run serveral microservice
> instances without limiting their memory consumption. As a result, I have to
> spare quite a large part of memory to ensure the execution of `mvn clean
> install -Pit` does not fail.
>
om/apache/servicecomb-java-chassis/commit/04c882beb1c8a75f15dfe7a0e68e44de158bbc2c
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Apr 8, 2019 at 11:05 PM wjm wjm wrote:
> >
> > "release tag" still have problem?
> >
> https://github.com/ap
"release tag" still have problem?
https://github.com/apache/servicecomb-java-chassis/compare/1.2.0...master
Mohammad Asif Siddiqui 于2019年4月8日周一 下午6:29写道：
> Hello All,
>
> This is a call for a Vote to release Apache ServiceComb Java-Chassis
> version 1.2.0 (RC-03)
>
> Release Notes :
>
>
recut the release?
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
> On Mon, Apr 8, 2019 at 9:09 AM wjm wjm wrote:
> >
> > “Release Tag” is not correct?
> >
> > Mohammad Asif Siddiqui 于2019年4月6日周六 下午9:21写道：
> >
> >
“Release Tag” is not correct?
Mohammad Asif Siddiqui 于2019年4月6日周六 下午9:21写道：
> Hello All,
>
> This is a call for a Vote to release Apache ServiceComb Java-Chassis
> version 1.2.0 (RC-02)
>
> Release Notes :
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344561
>
already merged.
Willem Jiang 于2019年4月5日周五 下午10:53写道：
> Hi wjm
>
> PR 1168, just added an application id , I think it should be fine to
> be part of java-chassis 1.2.0.
> Please verify it.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On
yes, need some fix.
https://github.com/apache/servicecomb-java-chassis/pull/1167already
merged.
https://github.com/apache/servicecomb-java-chassis/pull/1168 not
merged, need review and merge.
Willem Jiang 于2019年4月5日周五 下午3:40写道：
> Hi Asif
>
> As the CI is not unstable recently, we need
do we have a mechanism to use the configuration with high performance？
Xiaoliang Tian 于2019年3月29日周五 下午5:27写道：
> sure, mainly forcus on management , ease of use, rollback, key value
> version control. value validation.
>
> first we support API, later UX.
>
> bismy 于2019年3月29日周五 下午4:08写道：
>
> >
+1
zhang_...@boco.com.cn 于2019年4月3日周三 下午3:25写道：
> +1
>
> > 在 2019年4月3日，下午2:55，Zheng Feng 写道：
> >
> > Hi,
> >
> > I just wonder if we can enable this setting [1] on servicecomb-pack [2]
> and
> > it could be helpful when reviewing the PR. I think at least one people
> > review the changes and
java-chassis:
we have provide a new module named "inspector" to inspect internal data
of a microservice instance.
currently we only have one feature in inspector: view/test/download
schemas
https://issues.apache.org/jira/browse/SCB-1188
+1
checked release notes.
Zheng Feng 于2019年4月2日周二 下午2:13写道：
> +1 Release this package as 0.4.0
>
> I checked
> * The release tag is OK
> * The release candidate can be download and the signature is OK
> * Building and running the tests of the source codes is OK
> * Release notes is OK
>
>
>
>
[SCB-1059] - Bug fixes for v1.1.0
there are many fixes, it's better to list detail.
Willem Jiang 于2019年4月2日周二 上午10:17写道：
> +1 (binding)
> I checked the signed key and the license files and run the binary server
> on Mac.
>
> I just found a minor issue about the Notice file, we need to updated
Congratulations~
bismy 于2019年4月2日周二 上午10:46写道：
> Great!
>
>
>
>
> -- 原始邮件 --
> 发件人: "Sure";
> 发送时间: 2019年4月2日(星期二) 上午10:18
> 收件人: "dev";
>
> 主题: 回复：[ANN] New ServiceComb committer: Zhang Lei (张磊）
>
>
>
> Congratulations!
>
>
>
>
> -- 原始邮件
e blocker issues?
> I think we need to keep tracing them to make sure we cut the release on
> time.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Mar 31, 2019 at 11:56 AM wjm wjm wrote:
> >
> > sorry, java-chassis sti
sorry, java-chassis still have some issue need to be fixed.
zhang_...@boco.com.cn 于2019年3月26日周二 上午10:36写道：
> verification all passed with spring-boot-1 and spring-boot-2
>
> # Cluster
> 1. alpha cluster master node switch - Pass
> 2. random gRPC port - Pass
> 3. alpha cluster with random gRPC
https://github.com/netzwerg/paleo Apache-2.0
https://github.com/bodiam/markdown-to-asciidoc Apache-2.0
maybe can be fixed in:
https://github.com/apache/servicecomb-java-chassis/pull/1149
Willem Jiang 于2019年3月29日周五 下午5:56写道：
> When I using the maven license plugin to generate the license
>
java-chassis is ready.
bismy 于2019年3月19日周二 下午5:32写道：
> It's fine to me.
>
>
>
>
> -- 原始邮件 --
> 发件人: "zhang_...@boco.com.cn";
> 发送时间: 2019年3月19日(星期二) 下午5:16
> 收件人: "dev";
>
> 主题: Re: Release of ServiceComb
>
>
>
> I will update the document about alpha support
java -chassis just need to merge exist PR
Willem Jiang 于2019年3月19日周二 下午4:54写道：
> As we talked, it's time to prepare the release.
> There is only ten days to the end of this month, we need to make sure
> the branches are ready to go.
> Please reply this mail if you have any other big patch need
What is the responsibilities of the mentor?
Willem Jiang 于2019年3月10日周日 下午3:51写道：
> FYI, if you want to be a Google Summer of Code mentor, you could
> follow the instructions below to do the registration work.
> From my experience, you may also need to setup a proposal in the JIRA
> and try to
tion first,
> then we can consider to let management console redirect the request to
> the certain instance.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Mar 5, 2019 at 11:54 AM wjm wjm wrote:
> >
> > @yaohai...@huawei.com agree to you
+1
bismy 于2019年3月6日周三 下午4:22写道：
> Now java chassis depend on spring boot 2 2.0.0.RELEASE, this version is
> quite old fashioned. Although users can use dependency management to use
> other versions, but sometimes it is difficult to do so. Spring boot 2
> changed rapidly and many compatible
ok
Willem Jiang 于2019年3月6日周三 下午2:53写道：
> It's time for us to think about ServiceComb release now.
>
> As usual, we will release ServiceComb Java-Chassis 1.2.0, ServiceComb
> ServiceCenter 1.2.0 at the end of this month, then we will release
> ServiceComb Pack 0.4.0.
>
> Please reply the mail
it may be not so
> practical in production environment. If this feature is provided by another
> console service, it's more complex, but there are more chances to apply it
> into a production environment.
>
>
> Yours sincerely
>
>
> Yao Haishi
> yhs0...@163.com
&
es provide RESTful
> interfaces, and users get access to these informations via the console
> service.
>
>
> Yours sincerely
>
>
> Yao Haishi
> yhs0...@163.com
>
>
> On 3/5/2019 09:52，wjm wjm wrote：
> @zhang_lei
>
> ServiceComb can run with spring boot, bu
@zhang_lei
ServiceComb can run with spring boot, but will not depend on spring boot.
wjm wjm 于2019年3月5日周二 上午9:49写道：
> href of gif:
> https://issues.apache.org/jira/secure/attachment/12961084/swaggerAndDocument.gif
> and more question:
>
>- how to define the security of
href of gif:
https://issues.apache.org/jira/secure/attachment/12961084/swaggerAndDocument.gif
and more question:
- how to define the security of the new feature
- should open a new port for the feature?
wjm wjm 于2019年3月5日周二 上午9:20写道：
> currently it's difficult to collect internal sta
currently it's difficult to collect internal status of a microservice
instance when some problem happened.
eg:
routing depend on cached instances, discovery tree, strategy
of governances, and so on
when we resolving routing related problem, we can only guess the status
of all related modules.
agree to @bi...@qq.com
and maybe it's better to merge into new branch "weak-type", which belongs
to 2.0, and have some other incompatible features.
bismy 于2019年2月23日周六 下午5:54写道：
> This work should be done in a very carefully way, because it has
> compatibility concerns. My suggestion is not
conclusion:
before finish all feature of weak type, all related PR will be merged to
new branch: weak-type
wjm wjm 于2019年2月14日周四 上午1:27写道：
>
>
> bismy 于2019年2月12日周二 下午3:19写道：
>
>> - javaTypes
>>in org.apache.servicecomb.swagger.invocation.response.ResponseMeta n
> >ProtoStuff, ProtoStuff depend on strong type and not compatible to
> > ProtoBuf
> >for some datatye
> >- ..
> >
> >
> >
> > Willem Jiang 于2019年1月31日周四 下午9:07写道：
> >
> > > What's the difference between the strong
the mail I can tell the weak type is useful in the edge service,
> > can we just us it in the edge service?
> >
> > BTW, We need to be care if there is a API break change, heading to
> > version 2.0.0 is a good way, is there any other big change we need to
> > m
t; BTW, We need to be care if there is a API break change, heading to
> version 2.0.0 is a good way, is there any other big change we need to
> make in the java-chassis 2.0.0?
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Jan 30, 2019 at 8:39
currently, core mechanism is strong type
that caused to generate class dynamically in many special classloader, it's
dangerous:
- need to generate almost all business classes in edge, maybe cause jvm
meta overflow
- unable to support advanced features of swagger, such as allOf
-
https://github.com/apache/servicecomb-java-chassis/pull/1077
wjm wjm 于2019年1月25日周五 上午9:05写道：
> @yaohai...@huawei.com
> think about a business, normally 30 threads are enough, but when
> business is busy, maybe need 300 threads
> if use fixed thread pool, then after process b
he root cause later.
>
>
> [1] https://issues.apache.org/jira/browse/SCB-1133
>
>
> Yours sincerely
>
>
> Yao Haishi
> yhs0...@163.com
>
>
> On 1/25/2019 10:46，wjm wjm wrote：
> +1
>
> but if too complex, can IMPL it in weak type engine.
>
> yh
https://github.com/apache/servicecomb-java-chassis/pull/1074
wjm wjm 于2019年1月25日周五 下午6:20写道：
> oh. sorry, you are right
>
> 在 2019年1月25日星期五，Yang Bo 写道：
>
>> Is vertical-count a typo? Think it should be verticle-count.
>>
>> On Fri, Jan 25, 2019 at 5:36 PM wjm
oh. sorry, you are right
在 2019年1月25日星期五，Yang Bo 写道：
> Is vertical-count a typo? Think it should be verticle-count.
>
> On Fri, Jan 25, 2019 at 5:36 PM wjm wjm wrote:
>
> > new change:
> > all thread-count rename to vertical-count
> > still allow use
new change:
all thread-count rename to vertical-count
still allow use old key, but when use old key will print warning log,
notice it's ambiguous and deprecated, suggest to use new name
在 2019年1月24日星期四，wjm wjm 写道：
> eventloop will not eat all cpus, OS will schedule all the thre
> On Fri, Jan 25, 2019 at 4:43 PM wjm wjm wrote:
> >
> > currently, when we find something not so good during boot, we will print
> > log immediately
> > eg:
> >
> >- use deprecated configuration
> >- port listen failed
> >- ..
>
currently, when we find something not so good during boot, we will print
log immediately
eg:
- use deprecated configuration
- port listen failed
- ..
most developers will not notice these important messages
so maybe we can keep current implementation
and collect all the
+1
but if too complex, can IMPL it in weak type engine.
yhs0092 于2019年1月25日周五 上午9:55写道：
> Hello, I find out that currently it's not supported to define a inner
> class type in the REST service class as parameter. Should we allow such use
> case?
>
>
> For example, a REST service like below
nces is deployed on the same
> machine, a fixed thread pool is not so flexible since the instances cannot
> clean up some idle business thread?
> >
> >
> > Yours sincerely
> >
> >
> > Yao Haishi
> > yhs0...@163.com
> >
> >
> >
or default integrate only one ThreadPoolExecutor?
because most customers TPS is not so high, no need to do this optimize
wjm wjm 于2019年1月24日周四 上午10:35写道：
> currently we provide a default sync invocation executor:
>
>- default integrate two fixed thread pool
>- thread count
currently we provide a default sync invocation executor:
- default integrate two fixed thread pool
- thread count for one pool is equals cpu count
for most customers, thread count of one pool is too small, and fixed thread
pool is not so good, so will change to:
- default integrate two
eventloop will not eat all cpus, OS will schedule all the threads.
yhs0092 于2019年1月24日周四 上午9:49写道：
> Hi, wjm. Thank you for your sharing.
> As you say that if CPU count is less than 8, it's suggested that the
> thread-count is set to the CPU count. There is still a doubt for me. In the
>
currently, we created four type verticle for net send/receive and reactive
business logic:
- rest client verticle
- rest server verticle
- highway client verticle
- highway server verticle
instances of them controlled by configurations:
- servicecomb.rest.server.thread-count
-
egaContext when the
> InvocationBusinessMethodFinishEvent happened, we still need to find
> the right moment to setup the OmegaContext. So I think the option 1
> is the best way to go.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jan 21, 2019 at 10:51
t; > same problem in CXF simple frontend.
> > The solution could be enable the debug option in the compiler or add
> > annotation to the parameters.
> >
> > If we decide to setting the option on the compiler, we should not only
> > throw exception in the ru
all the following solutions can support this:
1.implement a handle, and require customers to configure it to be the last
handler
@Override
public void handle(Invocation invocation, AsyncResponse asyncResp)
throws Exception {
set context
try {
invocation.next(asyncResp);
} finally {
+1
and old samples can move to new repository
bismy 于2019年1月21日周一 下午3:34写道：
> Hello all,
>
>
> I suggest the create a new project servicecomb-samples to hosting code of
> servicecomb examples. Currently we have samples in each project, but is not
> enough for reasons:
>
>
> 1. Create new
+1
just one change: keep answer questions.
Willem Jiang 于2019年1月21日周一 下午4:05写道：
> I'm agree with Liubao.
>
> The background of moving the github issue is to attract more users by
> sporting the popular way of asking question in github issue.
> If we treat github issue as the mailing list of
>
ug option in the compiler or add
> annotation to the parameters.
>
> If we decide to setting the option on the compiler, we should not only
> throw exception in the runtime, but also document it.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> O
Scenes：
1.producer is springMVC dev mode
class QueryWrapper {
int x;
int y;
}
void method(QueryWrapper querys, int p2);
will produce swagger operation, have 3 parameters: x, y, p2
2.consumer is POJO dev mode, declare a interface:
interface TestIntf {
void method(int x, int
gitter?
Willem Jiang 于2019年1月4日周五 下午4:09写道：
> Hi Team,
>
> Any thoughts about it?
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Dec 24, 2018 at 9:17 AM Willem Jiang
> wrote:
> >
> > Hi Team
> >
> > We are try to run the biweekly meeting online[1] to get a chance to
+1
Willem Jiang 于2018年12月5日周三 下午6:06写道：
> Hi Asif,
>
> Thanks for the suggestion. I will updated the board report with the
> new version of introduction.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Dec 4, 2018 at 2:04 PM Mohammad Asif Siddiqui
> wrote:
> >
> > +1
>
+1 binding
check the source and binary release is OK
run demos is OK
Sukesh A C 于2018年11月28日周三 下午12:19写道：
> +1 binding.
>
> Checks done:
> - verified signatures and hashes
> - LICENSE is ok
> - run demos
>
> Thanks,
> Sukesh.
>
> -Original Message-
> From: Mohammad Asif Siddiqui
it's better to make huawei config center opensource
after governance opensource, can work with huawei config center directly
Yang Bo 于2018年11月27日周二 下午2:21写道：
> Etcd in itself is good enough to be used as a config center. I don't see
> the need for an extra layer, it reduces performance and adds
+1 binding
Checks I did:
- NOTICE/LICENSE exists
- can make release kit from source
Mohammad Asif Siddiqui 于2018年11月26日周一 下午2:13写道：
> +1 binding
>
> Checks Done :
> - hashes and signatures is good
> - NOTICE/LICENSE exists
> - ran RAT tool
> - can make release kit from source
> - checked for
+1 binding
Checks Done:
- release notes
- binaries and maven repos
DeanLee <82529...@qq.com> 于2018年11月24日周六 下午3:43写道：
> +1 non binding
>
>
>
>
> Checks List:
>
> - Signatures and hashes is ok
>
> - Able to run saga-spring-cloud-demo demo with the instruction from README
>
> - NOTICE/LICENSE is
we can start release process between 11.19~11.23 for java chassis
Bin Ma 于2018年11月4日周日 上午12:13写道：
> OK,I will try to check the ServiceComb website first
>
>
> Best Wishes & Regards
> ---
> Mabin
>
>
>
> Willem Jiang 于2018年11月2日周五 上午8:30写道：
>
> > I already submit a
Congratulation
Mohammad Asif Siddiqui 于2018年11月13日周二 下午4:19写道：
> Congratulations Yao Haishi
>
> Regards
> Asif
>
> On 2018/11/13 02:46:53, Willem Jiang wrote:
> > Please join me and the rest of the ServiceComb PPMC members in welcoming
> our
> > new ServiceComb committer: Yao Haishi (姚海石).
> >
Great, thanks~
Zheng Feng 于2018年11月9日周五 上午10:43写道：
> Nice work ! I just open the PR to fix in the saga [1]
>
> [1] https://github.com/apache/servicecomb-saga/pull/332
>
> Willem Jiang 于2018年11月9日周五 上午10:02写道：
>
> > I did some clean up on java-chassis, saga, service-center README file
> > and
es
> > >
> > >
> > >
> > > I think Sure is just want SC provide some filtering query on the
> > > server side, we don't need to let the server cached all the query
> > > result.
> > > We just let the client to find out what th
hat they want to know, server
> > don't need to send all the data to the client unless the client wants
> > them.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, Nov 9, 2018 at 5:47 AM wjm wjm wr
that will cause SC cache results by different query parameters, is it too
heavy?
even has 2k instances , but client query by data version, if not changed,
only response 304 NOT MODIFIED
if instances changed, and response size is big, then can response with
compress
so there is no problem?
Sure
1 - 100 of 216 matches
Mail list logo
