diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-859261505
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-858336538
--
This is an automated message from the
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-858332946
--
This is an automated message from the
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-858332523
从现象看 servicecomb 这里的线程 都是 100%啊 @liubao68
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-851798836
service-comb 应该没有那种 就是 假如 服务 频繁的发出超时请求, 底层检测到服务不可用,优雅停机下线, @liubao68
--
This is an automated message from the Apache Git Service.
To respond to the message,
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-850145359
> > 你的问题应该和servicecomb参数配置无关。 最大的可能性是内存管理的问题，可以观察下高并发的情况下内存占用情况。
>
> 请问一下,使用resttemplate exchange 的方式 发送 cse的地址
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-850144797
> 你的问题应该和servicecomb参数配置无关。 最大的可能性是内存管理的问题，可以观察下高并发的情况下内存占用情况。
请问一下,使用resttemplate exchange 的方式 发送 cse的地址 如果请求超时,关于HttpEntity对象会释放吗,
--
This is an
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849604650
> 你发的日志代表服务已经被外部终止了，属于shutdown hook的执行逻辑。建议你排查下内存、CPU以及容器设置。 前面已经回复过类似信息：
>
> `docker部署很有可能是由于资源限制，比如CPU、内存，被容器终止了。 建议你留意下内存变化，特别是 -Xmx
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849529939
@liubao68
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849529550
--
This is an automated message from the
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849529116
我调整过 配置项的 client 或者server 的 timeout时间 发现服务重启时间就更快了 不知道 那里有问题
--
This is an automated message from the Apache Git Service.
To respond to the message, please
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849511002
他自动调用了这里的代码 日志就是 close vertx transport
--
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849509576
我加入阿里巴巴的组件,加入了熔断和限流的限制后,服务1500就不会重启,所以根本原因在于发送请求到服务这里,应该是挤压过多导致的重启,但是下属服务1500就不会重启,这说不通啊
--
This is an automated message from the Apache Git Service.
To
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849508875
这个问题其实我根本不想纠结。。。但是最主要下属服务 1500就是不重启,我这个服务1500调用它就重启，，，
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849506493
这种是我配置问题 还是我内部逻辑 导致什么 引起的 close vertx
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-849506098
我在本地进行压测服务,均为一个实例,每秒并发1000正常,每秒并发1500,运行大约3分钟 服务自动重启,我看到日志测有一个 success close
vertx
--
This is an automated message from the Apache Git Service.
To respond to
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-764185135
This is an automated message from the Apache Git Service.
To respond to the message, please log
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-764185737
主要我们的日志写在docker容器内,没有持久化,所以当容器重启后,日志也就没了...
This is an automated message from the Apache Git
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-764185135
{
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763427367
这块是关于我说的httpserver failed的地方
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763425979
出现这个问题的地方我看是底层里的代码,这个应该和我的业务逻辑代码 无关把？
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763425123
![Uploading image.png…]()
This is an automated message from the Apache Git Service.
To
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763424139
博主能否提供一个交流群 我们讨论一下这个问题可以吗
This is an automated message from the Apache Git Service.
To respond
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763398893
2021-01-20 15:30:01.173 - [ERROR] - [registry-vert.x-eventloop-thread-0] -
[o.a.s.s.client.http.RestUtils] - [RestUtils.java:95] - GET
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763389526
主要出现重启的服务就是我这个站点转发的服务,其余的服务基本上没见过重启的说.
This is an automated message from the Apache Git
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763388418
> docker部署很有可能是由于资源限制，比如CPU、内存，被容器终止了。 建议你留意下内存变化，特别是 -Xmx
-Xms等设置，部分JDK版本对容器支持不是很好，无法自动分配合理的内存，需要手工设置这些参数以保障不超过容器限制。
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763357414
服务一直是稳定运行一段时间后 重启,我们采用的是docker方式部署
This is an automated message from the Apache Git Service.
To
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763356820
日志层面报的错就是这些
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763355782
> 你的问题和日志之间的关联不是很好理解。
>
> ```
> The request is rejected. Cannot process the request due to STATUS =
STOPPING
> ```
>
>
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-763274873
麻烦 能指点一下是否是 配置测的代码 有问题？ 还是什么原因导致的重启 这个很影响我们的服务稳定性啊
This is an automated message from the Apache
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-762748823
描述下我这个服务做的事情,灵活根据4处对端服务器的数据进行内存管控对端服务是否可用,随后请求过来的数据,提取转发的到哪个服务器,然后在通过resttemplate转发.(resttemplate
支持https转发以及转发走的是ip+端口)
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-762739567
@rvs @jbonofre @WillemJiang @ke4qqq 我看错误都是这些,以及httpserver failed ,能帮忙 指点下
问题的所在吗
This is an
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-762739403
2021-01-19 16:14:05.177 - [ERROR] - [vert.x-eventloop-thread-10] -
[io.vertx.core.impl.ContextImpl] - [ContextImpl.java:342] - Unhandled exception
diwenzheng commented on issue #2205:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/2205#issuecomment-762739265
我们目前用的版本是1.3.0,在我们业务高并发的情况下,最大5分钟30W的并发量,我们外围服务有30个实例,为何我更改了实例向注册中心发送心跳的时间以及重试次数,服务还会过一段时间重启？
34 matches
Mail list logo
