[jira] [Created] (SCB-1526) The contribution guide link is invalid in kie home page
little-cui created SCB-1526: --- Summary: The contribution guide link is invalid in kie home page Key: SCB-1526 URL: https://issues.apache.org/jira/browse/SCB-1526 Project: Apache ServiceComb Issue Type: Bug Components: Kie Reporter: little-cui -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SCB-1489) Micro-service instance wouldn't work after we shotdown our service center for updating while we had enable RSA authentication between services.
[
https://issues.apache.org/jira/browse/SCB-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951966#comment-16951966
]
Haishi Yao commented on SCB-1489:
-
I think there are at least two improvements should be done:
1. java-chassis should check the error response content from service-center.
Not all kind of error cause the microservice instance rerun the
microservice/instance register process.
2. once the instanceId is changed, the token cache in RSAConsumerTokenManager
should be refreshed instantly.
> Micro-service instance wouldn't work after we shotdown our service center for
> updating while we had enable RSA authentication between services.
> ---
>
> Key: SCB-1489
> URL: https://issues.apache.org/jira/browse/SCB-1489
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Liu HuaiZhou
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We had add RSA authentication between services following [Documents
> |[https://docs.servicecomb.io/java-chassis/en_US/security/rsa.html]]. The
> micro-service instances interrupted when we shutdown service center and
> update it for latest version.Following are snap logs for comsumer and
> provider instances.
> consumer log：
> [2019-04-27 05:58:10,995/UTC][main][INFO]InvocationException:
> code=490;msg=CommonExceptionData [message=Cse Internal Bad Request]
> com.huawei.paas.cse.demo.pojo.client.PojoClient.main(PojoClient.java:119)
> [2019-04-27 05:58:12,995/UTC][main][INFO]create MicroserviceVersions,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceVersions.(MicroserviceVersions.java:84)
> [2019-04-27
> 05:58:13,001/UTC][registry-vert.x-eventloop-thread-0][WARN]failed to
> findInstances:
> {"errorCode":"400012","errorMessage":"Micro-service does not
> exist","detail":"Consumer does not exist."}
> org.apache.servicecomb.serviceregistry.client.http.ServiceRegistryClientImpl.lambda$null$4(ServiceRegistryClientImpl.java:213)
> [2019-04-27 05:58:13,001/UTC][main][INFO]remove microservice,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceManager.removeMicroservice(MicroserviceManager.java:76)
> [2019-04-27 05:58:13,001/UTC][main][INFO]create MicroserviceVersionRule,
> appId=liushuang-noauth, microserviceName=pojolwx585706, versionRule=0.0.0+.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceVersions.createAndInitMicroserviceVersionRule(MicroserviceVersions.java:231)
> [2019-04-27 05:58:13,001/UTC][main][INFO]create MicroserviceVersions,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceVersions.(MicroserviceVersions.java:84)
> [2019-04-27
> 05:58:13,004/UTC][registry-vert.x-eventloop-thread-0][WARN]failed to
> findInstances:
> {"errorCode":"400012","errorMessage":"Micro-service does not
> exist","detail":"Consumer does not exist."}
> org.apache.servicecomb.serviceregistry.client.http.ServiceRegistryClientImpl.lambda$null$4(ServiceRegistryClientImpl.java:213)
> [2019-04-27 05:58:13,004/UTC][main][INFO]remove microservice,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceManager.removeMicroservice(MicroserviceManager.java:76)
> [2019-04-27 05:58:13,004/UTC][main][ERROR]invoke failed,
> pojolwx585706.helloworldGreeter.SayHello
> org.apache.servicecomb.core.provider.consumer.InvokerUtils.innerSyncInvoke(InvokerUtils.java:80)
> org.apache.servicecomb.foundation.common.exceptions.ServiceCombException:
> org.apache.servicecomb.core.filter.OperationInstancesDiscoveryFilter
> discovery return null.
> at
> org.apache.servicecomb.serviceregistry.discovery.DiscoveryTree.doDiscovery(DiscoveryTree.java:169)
> at
> org.apache.servicecomb.serviceregistry.discovery.DiscoveryTree.discovery(DiscoveryTree.java:130)
> at
> org.apache.servicecomb.serviceregistry.discovery.DiscoveryTree.discovery(DiscoveryTree.java:123)
> at
> org.apache.servicecomb.loadbalance.LoadbalanceHandler.getOrCreateLoadBalancer(LoadbalanceHandler.java:360)
> at
> org.apache.servicecomb.loadbalance.LoadbalanceHandler.handle(LoadbalanceHandler.java:179)
> at org.apache.servicecomb.core.Invocation.next(Invocation.java:151)
> at
> org.apache.servicecomb.core.provider.consumer.InvokerUtils.innerSyncInvoke(InvokerUtils.java:72)
> at org.apache.servicecomb.provider.pojo.Invoker.syncInvoke(Invoker.java:161)
> at org.apache.servicecomb.provider.pojo.Invoker.invoke(Invoker.java:157)
> at com.sun.proxy.$Proxy28.SayHello(Unknown Source)
> at
[jira] [Commented] (SCB-1489) Micro-service instance wouldn't work after we shotdown our service center for updating while we had enable RSA authentication between services.
[
https://issues.apache.org/jira/browse/SCB-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951964#comment-16951964
]
Haishi Yao commented on SCB-1489:
-
Hello, I met the similar problem, and here may be the actual root cause:
1. service-center gets some error and may response error randomly.
2. consumer may get heartbeat failure and try to rerun the microservice
register process. When it try to query the microservice record, service-center
response a failure and mislead the consumer that its microservice record does
not exist. As a result, the consumer clear its instanceId cache and rerun
instance registry process. After that, the instanceId of consumer is changed,
while the token cache in RSAConsumerTokenManager is not refreshed.
3. consumer send request to provider, with the old token. And provider parse
the outdated consumer instanceId from the token. And there is no instance can
be found in service-center by that instanceId.
> Micro-service instance wouldn't work after we shotdown our service center for
> updating while we had enable RSA authentication between services.
> ---
>
> Key: SCB-1489
> URL: https://issues.apache.org/jira/browse/SCB-1489
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Liu HuaiZhou
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We had add RSA authentication between services following [Documents
> |[https://docs.servicecomb.io/java-chassis/en_US/security/rsa.html]]. The
> micro-service instances interrupted when we shutdown service center and
> update it for latest version.Following are snap logs for comsumer and
> provider instances.
> consumer log：
> [2019-04-27 05:58:10,995/UTC][main][INFO]InvocationException:
> code=490;msg=CommonExceptionData [message=Cse Internal Bad Request]
> com.huawei.paas.cse.demo.pojo.client.PojoClient.main(PojoClient.java:119)
> [2019-04-27 05:58:12,995/UTC][main][INFO]create MicroserviceVersions,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceVersions.(MicroserviceVersions.java:84)
> [2019-04-27
> 05:58:13,001/UTC][registry-vert.x-eventloop-thread-0][WARN]failed to
> findInstances:
> {"errorCode":"400012","errorMessage":"Micro-service does not
> exist","detail":"Consumer does not exist."}
> org.apache.servicecomb.serviceregistry.client.http.ServiceRegistryClientImpl.lambda$null$4(ServiceRegistryClientImpl.java:213)
> [2019-04-27 05:58:13,001/UTC][main][INFO]remove microservice,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceManager.removeMicroservice(MicroserviceManager.java:76)
> [2019-04-27 05:58:13,001/UTC][main][INFO]create MicroserviceVersionRule,
> appId=liushuang-noauth, microserviceName=pojolwx585706, versionRule=0.0.0+.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceVersions.createAndInitMicroserviceVersionRule(MicroserviceVersions.java:231)
> [2019-04-27 05:58:13,001/UTC][main][INFO]create MicroserviceVersions,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceVersions.(MicroserviceVersions.java:84)
> [2019-04-27
> 05:58:13,004/UTC][registry-vert.x-eventloop-thread-0][WARN]failed to
> findInstances:
> {"errorCode":"400012","errorMessage":"Micro-service does not
> exist","detail":"Consumer does not exist."}
> org.apache.servicecomb.serviceregistry.client.http.ServiceRegistryClientImpl.lambda$null$4(ServiceRegistryClientImpl.java:213)
> [2019-04-27 05:58:13,004/UTC][main][INFO]remove microservice,
> appId=liushuang-noauth, microserviceName=pojolwx585706.
> org.apache.servicecomb.serviceregistry.consumer.MicroserviceManager.removeMicroservice(MicroserviceManager.java:76)
> [2019-04-27 05:58:13,004/UTC][main][ERROR]invoke failed,
> pojolwx585706.helloworldGreeter.SayHello
> org.apache.servicecomb.core.provider.consumer.InvokerUtils.innerSyncInvoke(InvokerUtils.java:80)
> org.apache.servicecomb.foundation.common.exceptions.ServiceCombException:
> org.apache.servicecomb.core.filter.OperationInstancesDiscoveryFilter
> discovery return null.
> at
> org.apache.servicecomb.serviceregistry.discovery.DiscoveryTree.doDiscovery(DiscoveryTree.java:169)
> at
> org.apache.servicecomb.serviceregistry.discovery.DiscoveryTree.discovery(DiscoveryTree.java:130)
> at
> org.apache.servicecomb.serviceregistry.discovery.DiscoveryTree.discovery(DiscoveryTree.java:123)
> at
> org.apache.servicecomb.loadbalance.LoadbalanceHandler.getOrCreateLoadBalancer(LoadbalanceHandler.java:360)
> at
>
[jira] [Created] (SCB-1525) print codec error stack
liubao created SCB-1525: --- Summary: print codec error stack Key: SCB-1525 URL: https://issues.apache.org/jira/browse/SCB-1525 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: liubao Assignee: liubao Codec error message is very common in development, and servicecomb default do not print them, this makes problem analyse a bit complicated. >From users feedback, we will print some of these logs, and for codec error >that will print user data, we add a configuration for debug usage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1497) mesher support skywalking
[ https://issues.apache.org/jira/browse/SCB-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenshuo resolved SCB-1497. --- Resolution: Fixed Done > mesher support skywalking > - > > Key: SCB-1497 > URL: https://issues.apache.org/jira/browse/SCB-1497 > Project: Apache ServiceComb > Issue Type: New Feature > Components: mesher >Reporter: chenshuo >Priority: Critical > Attachments: image-2019-10-10-15-05-02-666.png, > image-2019-10-15-15-34-02-788.png > > Time Spent: 20m > Remaining Estimate: 0h > > We need a new feature which is making mersher support for skywalking. > > I use [https://github.com/SkyAPM/go2sky] for mesher to connect to > skywalking. I get following picture： > !image-2019-10-15-15-34-02-788.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-1497) mesher support skywalking
[ https://issues.apache.org/jira/browse/SCB-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenshuo updated SCB-1497: -- Attachment: image-2019-10-15-15-34-02-788.png Description: We need a new feature which is making mersher support for skywalking. I use [https://github.com/SkyAPM/go2sky] for mesher to connect to skywalking. I get following picture： !image-2019-10-15-15-34-02-788.png! was: We need a new feature which is making mersher support for skywalking. I use [https://github.com/SkyAPM/go2sky] for mesher to connect to skywalking. I get following picture. There are still some work to do for example test case and code format. !image-2019-10-10-15-05-02-666.png! > mesher support skywalking > - > > Key: SCB-1497 > URL: https://issues.apache.org/jira/browse/SCB-1497 > Project: Apache ServiceComb > Issue Type: New Feature > Components: mesher >Reporter: chenshuo >Priority: Critical > Attachments: image-2019-10-10-15-05-02-666.png, > image-2019-10-15-15-34-02-788.png > > Time Spent: 20m > Remaining Estimate: 0h > > We need a new feature which is making mersher support for skywalking. > > I use [https://github.com/SkyAPM/go2sky] for mesher to connect to > skywalking. I get following picture： > !image-2019-10-15-15-34-02-788.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
