[jira] [Resolved] (SCB-262) many groupId in pom file still start with io.servicecomb while sc package have been renamed as org.apache.servicecomb
[ https://issues.apache.org/jira/browse/SCB-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-262. --- Resolution: Resolved > many groupId in pom file still start with io.servicecomb while sc package > have been renamed as org.apache.servicecomb > - > > Key: SCB-262 > URL: https://issues.apache.org/jira/browse/SCB-262 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Bo Li >Priority: Major > > Need to update website description of groupId for pom file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-274) As the Configuration support of Apollo and Configuration Center are quite similar, it doesn't make sense that we put these two module into different places and have differ
[ https://issues.apache.org/jira/browse/SCB-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-274. --- Resolution: Resolved > As the Configuration support of Apollo and Configuration Center are quite > similar, it doesn't make sense that we put these two module into different > places and have different configuration codes. > > > Key: SCB-274 > URL: https://issues.apache.org/jira/browse/SCB-274 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-121) Section header missed for servicecomb website document at run-mode part.
[ https://issues.apache.org/jira/browse/SCB-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-121. --- Resolution: Resolved > Section header missed for servicecomb website document at run-mode part. > > > Key: SCB-121 > URL: https://issues.apache.org/jira/browse/SCB-121 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Bo Li >Priority: Minor > > Only step 2 for run-mode at http://servicecomb.io/users/run-mode/ at WEB > container mode section shows up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-113) Metrics document translation
[ https://issues.apache.org/jira/browse/SCB-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li closed SCB-113. - Resolution: Resolved > Metrics document translation > > > Key: SCB-113 > URL: https://issues.apache.org/jira/browse/SCB-113 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Priority: Major > > Just Metrics document need to translate. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-107) Document Translation
[ https://issues.apache.org/jira/browse/SCB-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-107. --- Resolution: Resolved > Document Translation > > > Key: SCB-107 > URL: https://issues.apache.org/jira/browse/SCB-107 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > > There are some user guide document in Chinese need to be translated into > English. > Please refer to http://servicecomb.io/users/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-109) Develop Service Provider Translation
[ https://issues.apache.org/jira/browse/SCB-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-109. --- Resolution: Resolved > Develop Service Provider Translation > > > Key: SCB-109 > URL: https://issues.apache.org/jira/browse/SCB-109 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Priority: Major > > Develop Service Provider translation contains: > # Service Definition > # Service Contract > # Develop Microservice with SpringMVC > # Develop Microservice with JAX-RS > # Develop Microservice with Transparent-RPC > # Service Interface Constraints > # Service Configurations > # Communicate Protocol > # Application Boot Up Process > # Service Heartbeat -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-111) General Development Translation
[ https://issues.apache.org/jira/browse/SCB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li closed SCB-111. - Resolution: Resolved > General Development Translation > --- > > Key: SCB-111 > URL: https://issues.apache.org/jira/browse/SCB-111 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Priority: Major > > General Development Translation contains following part: > # Develop and Test in Local Environment > # User ServiceComb in SpringBoot > # Distribute Tracing > # Customized Tracing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-108) User Guide Translation
[ https://issues.apache.org/jira/browse/SCB-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li closed SCB-108. - Resolution: Resolved > User Guide Translation > -- > > Key: SCB-108 > URL: https://issues.apache.org/jira/browse/SCB-108 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Priority: Major > > *User guide contains two part:* > * Java Chassis Architecture > * Setup Environment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-105) Invalid hyperlink at http://servicecomb.io/cn/developers/submit-codesI
[ https://issues.apache.org/jira/browse/SCB-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li closed SCB-105. - Resolution: Resolved > Invalid hyperlink at http://servicecomb.io/cn/developers/submit-codesI > -- > > Key: SCB-105 > URL: https://issues.apache.org/jira/browse/SCB-105 > Project: Apache ServiceComb > Issue Type: Bug > Components: website >Reporter: Bo Li >Priority: Minor > > Hyperlink is not available after the project was moved to ApacheInfra. > At http://servicecomb.io/cn/developers/submit-codes/ > PR guild, Github, it jumps to old repository but not ApacheInfra. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-93) inconsistent configuration folders
[ https://issues.apache.org/jira/browse/SCB-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li closed SCB-93. Resolution: Resolved > inconsistent configuration folders > -- > > Key: SCB-93 > URL: https://issues.apache.org/jira/browse/SCB-93 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Reporter: Bo Li >Priority: Major > > he certificates stores under etc/ssl folder, while the application > configuration files stores under conf folder, which looks inconsistent. Is it > a better idea to merge both of it under etc folder? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-94) How about changing the log module to logus or other opensource project?
[ https://issues.apache.org/jira/browse/SCB-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li closed SCB-94. Resolution: Resolved > How about changing the log module to logus or other opensource project? > --- > > Key: SCB-94 > URL: https://issues.apache.org/jira/browse/SCB-94 > Project: Apache ServiceComb > Issue Type: Bug > Components: Service-Center >Reporter: Bo Li >Priority: Major > > How about to change the log module to logus or other opensource project? > https://github.com/ServiceComb/service-center/tree/master/lager -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-88) error occurs when start a service following "quick start"
[
https://issues.apache.org/jira/browse/SCB-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li resolved SCB-88.
--
Resolution: Resolved
> error occurs when start a service following "quick start"
> -
>
> Key: SCB-88
> URL: https://issues.apache.org/jira/browse/SCB-88
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> {code}
> java.net.ConnectException: Failed to connect to /127.0.0.1:9411
> at
> okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:189)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:173)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:193)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:129)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:98)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:109)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:124)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:170)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.access$100(RealCall.java:33) ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall$AsyncCall.execute(RealCall.java:120)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
> [okhttp-3.4.1.jar:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_121]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-87) can anyone provide a gradle script?
[ https://issues.apache.org/jira/browse/SCB-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-87. -- Resolution: Resolved > can anyone provide a gradle script? > --- > > Key: SCB-87 > URL: https://issues.apache.org/jira/browse/SCB-87 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-84) Is there a interface for user to find service according to schemaId
[ https://issues.apache.org/jira/browse/SCB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-84. -- Resolution: Resolved > Is there a interface for user to find service according to schemaId > --- > > Key: SCB-84 > URL: https://issues.apache.org/jira/browse/SCB-84 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-80) ResponseEntity Type error occurs
[
https://issues.apache.org/jira/browse/SCB-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li resolved SCB-80.
--
Resolution: Resolved
> ResponseEntity Type error occurs
> -
>
> Key: SCB-80
> URL: https://issues.apache.org/jira/browse/SCB-80
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> Given:
> * tomcat 8.5.x
> * java-chassis 0.4.0
> * service-center 1.0.1
> if header and body included in responseEntity, error 1 and error 2 occurs, if
> not, only error 2 occurs.
> error 1:
> {code}
> [2017-11-22
> 16:36:39.101][ufm][][ERROR][io.servicecomb.common.rest.AbstractRestInvocation][sendResponseQuietly,131][Failed
> to send rest response,
> operation:ufm.api-v2-accounts.setWatermark.][pool-30-thread-3]
> java.lang.NullPointerException: null
> at
> org.apache.coyote.http11.Http11OutputBuffer.commit(Http11OutputBuffer.java:368)
> at
> org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1300)
> at
> org.apache.coyote.AbstractProcessor.action(AbstractProcessor.java:254)
> at org.apache.coyote.Response.action(Response.java:174)
> at org.apache.coyote.Response.sendHeaders(Response.java:356)
> at
> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:303)
> at
> org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:284)
> at org.apache.catalina.connector.Response.flushBuffer(Response.java:541)
> at
> org.apache.catalina.connector.ResponseFacade.flushBuffer(ResponseFacade.java:312)
> at
> javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:176)
> at
> io.servicecomb.foundation.vertx.http.StandardHttpServletResponseEx.flushBuffer(StandardHttpServletResponseEx.java:80)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.sendResponse(AbstractRestInvocation.java:164)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.sendResponseQuietly(AbstractRestInvocation.java:129)
> at
> io.servicecomb.common.rest.RestProducerInvocation.lambda$doInvoke$1(RestProducerInvocation.java:121)
> at
> io.servicecomb.core.handler.ShutdownHookHandler.lambda$handle$0(ShutdownHookHandler.java:70)
> at
> io.servicecomb.swagger.engine.SwaggerProducerOperation.invoke(SwaggerProducerOperation.java:113)
> at
> io.servicecomb.core.handler.impl.ProducerOperationHandler.handle(ProducerOperationHandler.java:38)
> at io.servicecomb.core.Invocation.next(Invocation.java:132)
> at
> io.servicecomb.core.handler.ShutdownHookHandler.handle(ShutdownHookHandler.java:68)
> at io.servicecomb.core.Invocation.next(Invocation.java:132)
> at
> io.servicecomb.common.rest.RestProducerInvocation.doInvoke(RestProducerInvocation.java:120)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.invoke(AbstractRestInvocation.java:93)
> at
> io.servicecomb.common.rest.RestProducerInvocation.runOnExecutor(RestProducerInvocation.java:94)
> at
> io.servicecomb.common.rest.RestProducerInvocation.lambda$scheduleInvocation$0(RestProducerInvocation.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)
> {code}
> error 2
> {code}
> [2017-11-22
> 16:36:39.105][ufm][][ERROR][io.servicecomb.common.rest.AbstractRestInvocation][invoke,95][unknown
> edge exception.][pool-30-thread-3]
> java.lang.IllegalStateException: It is illegal to call this method if the
> current request is not in asynchronous mode (i.e. isAsyncStarted() returns
> false)
> at
> org.apache.catalina.connector.Request.getAsyncContext(Request.java:1742)
> at
> org.apache.catalina.connector.RequestFacade.getAsyncContext(RequestFacade.java:1056)
> at
> javax.servlet.ServletRequestWrapper.getAsyncContext(ServletRequestWrapper.java:431)
> at
> io.servicecomb.common.rest.AbstractRestInvocation.sendResponseQuietly(AbstractRestInvocation.java:135)
> at
> io.servicecomb.common.rest.RestProducerInvocation.lambda$doInvoke$1(RestProducerInvocation.java:121)
> at
> io.servicecomb.core.handler.ShutdownHookHandler.lambda$handle$0(ShutdownHookHandler.java:70)
> at
> io.servicecomb.swagger.engine.SwaggerProducerOperation.invoke(SwaggerProducerOperation.java:113)
> at
> io.servicecomb.core.handler.impl.ProducerOperationHandler.handle(ProducerOperationHandler.java:38)
> at io.servicecomb.core.Invocation.next(Invocation.java:132)
> at
> io.servicecomb.core.handler.ShutdownHookHandler.handle(ShutdownHookHandler.java:68)
> at io.servicecomb.core.Invocation.next(Invocation.java:132)
>
[jira] [Resolved] (SCB-81) Question about yaml file version
[ https://issues.apache.org/jira/browse/SCB-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-81. -- Resolution: Resolved > Question about yaml file version > > > Key: SCB-81 > URL: https://issues.apache.org/jira/browse/SCB-81 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > > * how to user yaml file version, i notived that microservice.yaml file's > version is 0.0.3. > * what's the relation between the three number separated by dot above? > * is there any limit of those numbers? what's tha maximum? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-83) BMI Calculator throws exception
[
https://issues.apache.org/jira/browse/SCB-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li resolved SCB-83.
--
Resolution: Resolved
> BMI Calculator throws exception
> ---
>
> Key: SCB-83
> URL: https://issues.apache.org/jira/browse/SCB-83
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> when running BMI Calculator repeatly, it throws:
> {code}
> Internal Server Error: com.netflix.zuul.exception.ZuulException
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-82) NoClassDefFoundError occurs when creating Provider service following "QuickStart"
[
https://issues.apache.org/jira/browse/SCB-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li resolved SCB-82.
--
Resolution: Resolved
> NoClassDefFoundError occurs when creating Provider service following
> "QuickStart"
> -
>
> Key: SCB-82
> URL: https://issues.apache.org/jira/browse/SCB-82
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> {code}
> java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/FormatFeature
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-79) Value of Content-Length is null when using @ReaustHeader("Content-Length")
[
https://issues.apache.org/jira/browse/SCB-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li resolved SCB-79.
--
Resolution: Resolved
> Value of Content-Length is null when using @ReaustHeader("Content-Length")
> ---
>
> Key: SCB-79
> URL: https://issues.apache.org/jira/browse/SCB-79
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> Using @RequesHeader to get value of Content-Length doesn't work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-76) error log has insufficient information when type not supported
[ https://issues.apache.org/jira/browse/SCB-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-76. -- Resolution: Resolved > error log has insufficient information when type not supported > --- > > Key: SCB-76 > URL: https://issues.apache.org/jira/browse/SCB-76 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Labels: newbie > > this error is thrown when a certain is not supported in controller > java.lang.Error: not support def type: class > io.swagger.models.properties.BaseIntegerProperty > the type BaseIntegerProperty is not what user specified and the user > specified type is not shown in log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-78) Request body is always null when using request.getinputstream
[
https://issues.apache.org/jira/browse/SCB-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li resolved SCB-78.
--
Resolution: Resolved
> Request body is always null when using request.getinputstream
> -
>
> Key: SCB-78
> URL: https://issues.apache.org/jira/browse/SCB-78
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> {code}
>@RequestMapping(value = "/", method = {RequestMethod.GET})
> public String something(@PathVariable(value = "appId") String appId,
> Model model,
> HttpServletRequest httpRequest) {
> httpRequest.getInputStream();// always ""
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-75) Why it must be json format when receiving bytes through @RequestBody byte[] buffer
[
https://issues.apache.org/jira/browse/SCB-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li resolved SCB-75.
--
Resolution: Resolved
> Why it must be json format when receiving bytes through @RequestBody byte[]
> buffer
> --
>
> Key: SCB-75
> URL: https://issues.apache.org/jira/browse/SCB-75
> Project: Apache ServiceComb
> Issue Type: Bug
>Reporter: Bo Li
>Priority: Major
>
> Parameter invalid error occurs when received data is not json format when
> using @requestbody byte[] buffer
> {code}
> @RequestMapping(value = "/update", method = RequestMethod.PUT)
> public ResponseEntity update(@PathVariable("accountId") Long
> accountId,
> @RequestHeader("Date") String date,
> @RequestBody byte[] buffer, HttpServletRequest request)
> {
>byte[] data = buffer; //buffer data have to be json format here
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-72) Can isolation information of provider and consumer been discovered through capability of release and subscription?
[ https://issues.apache.org/jira/browse/SCB-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-72. -- Resolution: Resolved > Can isolation information of provider and consumer been discovered through > capability of release and subscription? > -- > > Key: SCB-72 > URL: https://issues.apache.org/jira/browse/SCB-72 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > There could be internal wrong when current service is isolated, although > loadbalance can be used to filter abnormal service, extra method to get that > kind for information is still in need, Please fix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-70) Question about loadblance
[ https://issues.apache.org/jira/browse/SCB-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-70. -- Resolution: Resolved > Question about loadblance > - > > Key: SCB-70 > URL: https://issues.apache.org/jira/browse/SCB-70 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > > 我想使用负载均衡功能，按照官网的说明配置了pojo-consumer的microservice.yaml。以下是我实验的大致过程： > 我启动多个pojo-provider实例在不同的端口，然后启动pojo-consumer，一切都正常。可是当我关掉一个pojo-provider实例时，pojo-consumer调用服务接口就失败了。 > 按我的理解，pojo-consumer在当前调用实例断开后，应该自动切换到另外一个pojo-provider实例上调用服务接口继续工作，然而实验结果并不是这样的。 > 请问我对ServiceComb负载均衡的理解是否有出错？ > 另外，能否增加microservice.yaml各配置项的使用说明。 > 非常感谢 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-554) translate ServiceComb Saga Downloads
[ https://issues.apache.org/jira/browse/SCB-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-554. --- Resolution: Resolved > translate ServiceComb Saga Downloads > > > Key: SCB-554 > URL: https://issues.apache.org/jira/browse/SCB-554 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-550) website document translation
[ https://issues.apache.org/jira/browse/SCB-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-550. --- Resolution: Resolved > website document translation > > > Key: SCB-550 > URL: https://issues.apache.org/jira/browse/SCB-550 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-553) translate ServiceComb Java-Chassis Downloads
[ https://issues.apache.org/jira/browse/SCB-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-553. --- Resolution: Resolved > translate ServiceComb Java-Chassis Downloads > > > Key: SCB-553 > URL: https://issues.apache.org/jira/browse/SCB-553 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-552) translate ServiceComb Service-Center Downloads
[ https://issues.apache.org/jira/browse/SCB-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-552. --- Resolution: Resolved > translate ServiceComb Service-Center Downloads > -- > > Key: SCB-552 > URL: https://issues.apache.org/jira/browse/SCB-552 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-551) translate Set Up Write Access for Committer
[ https://issues.apache.org/jira/browse/SCB-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-551. --- Resolution: Resolved > translate Set Up Write Access for Committer > --- > > Key: SCB-551 > URL: https://issues.apache.org/jira/browse/SCB-551 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-554) translate ServiceComb Saga Downloads
[ https://issues.apache.org/jira/browse/SCB-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-554: - Assignee: Bo Li > translate ServiceComb Saga Downloads > > > Key: SCB-554 > URL: https://issues.apache.org/jira/browse/SCB-554 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-553) translate ServiceComb Java-Chassis Downloads
[ https://issues.apache.org/jira/browse/SCB-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-553: - Assignee: Bo Li > translate ServiceComb Java-Chassis Downloads > > > Key: SCB-553 > URL: https://issues.apache.org/jira/browse/SCB-553 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-552) translate ServiceComb Service-Center Downloads
[ https://issues.apache.org/jira/browse/SCB-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-552: - Assignee: Bo Li > translate ServiceComb Service-Center Downloads > -- > > Key: SCB-552 > URL: https://issues.apache.org/jira/browse/SCB-552 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-551) translate Set Up Write Access for Committer
[ https://issues.apache.org/jira/browse/SCB-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-551: - Assignee: Bo Li > translate Set Up Write Access for Committer > --- > > Key: SCB-551 > URL: https://issues.apache.org/jira/browse/SCB-551 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-553) translate ServiceComb Java-Chassis Downloads
Bo Li created SCB-553: - Summary: translate ServiceComb Java-Chassis Downloads Key: SCB-553 URL: https://issues.apache.org/jira/browse/SCB-553 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-554) translate ServiceComb Saga Downloads
Bo Li created SCB-554: - Summary: translate ServiceComb Saga Downloads Key: SCB-554 URL: https://issues.apache.org/jira/browse/SCB-554 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-552) translate ServiceComb Service-Center Downloads
Bo Li created SCB-552: - Summary: translate ServiceComb Service-Center Downloads Key: SCB-552 URL: https://issues.apache.org/jira/browse/SCB-552 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-551) translate Set Up Write Access for Committer
Bo Li created SCB-551: - Summary: translate Set Up Write Access for Committer Key: SCB-551 URL: https://issues.apache.org/jira/browse/SCB-551 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-550) website document translation
[ https://issues.apache.org/jira/browse/SCB-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-550: - Assignee: Bo Li > website document translation > > > Key: SCB-550 > URL: https://issues.apache.org/jira/browse/SCB-550 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-550) website document translation
Bo Li created SCB-550: - Summary: website document translation Key: SCB-550 URL: https://issues.apache.org/jira/browse/SCB-550 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-86) can not find handler :tracing-provider
[
https://issues.apache.org/jira/browse/SCB-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li closed SCB-86.
Resolution: Resolved
> can not find handler :tracing-provider
> --
>
> Key: SCB-86
> URL: https://issues.apache.org/jira/browse/SCB-86
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Assignee: yangyongzheng
>Priority: Major
>
> {code}java.lang.Error: can not find handler: tracing-project {code} error
> occurs when runing bmi distributed tracing demo.
> microservice.yaml configuration is:
> {code}
> APPLICATION_ID: bmi
> service_description:
> # name of the declaring microservice
> name: calculator
> version: 0.0.1
> cse:
> service:
> registry:
> address: http://127.0.0.1:30100
> rest:
> address: 0.0.0.0:
> handler:
> chain:
> Provider:
> default: tracing-provider
> {code}
> exception throwed when runing CalculationApplication:
> {code}
> 2017-09-19 11:57:28,586 [ERROR] Application startup failed
> org.springframework.boot.SpringApplication.reportFailure(SpringApplication.java:840)
> java.lang.Error: can not find handler :tracing-provider
> at
> io.servicecomb.core.handler.AbstractHandlerManager.convertToChainClass(AbstractHandlerManager.java:68)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.handler.AbstractHandlerManager.createHandlerChain(AbstractHandlerManager.java:82)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:110)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:32)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.foundation.common.AbstractObjectManager.getOrCreate(AbstractObjectManager.java:36)
> ~[foundation-common-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.loader.SchemaLoader.registerSchema(SchemaLoader.java:94)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:112)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:42)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:59)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:75)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
> ~[provider-rest-common-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:43)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:113)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:99)
> ~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
> at
> org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
> ~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
> at
> org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
> ~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:318)
> [spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1187)
> [spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
> at
>
[jira] [Commented] (SCB-189) support async restTemplate
[ https://issues.apache.org/jira/browse/SCB-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425156#comment-16425156 ] Bo Li commented on SCB-189: --- This task is finished in SCB-379 https://issues.apache.org/jira/browse/SCB-379 Task SCB-379 is created because my carelessness. > support async restTemplate > -- > > Key: SCB-189 > URL: https://issues.apache.org/jira/browse/SCB-189 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: Bo Li >Priority: Major > Fix For: service-center-1.0.0-m2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-460) Add blogs to introduce config-center integration in ServiceComb
[ https://issues.apache.org/jira/browse/SCB-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-460. --- Resolution: Resolved > Add blogs to introduce config-center integration in ServiceComb > --- > > Key: SCB-460 > URL: https://issues.apache.org/jira/browse/SCB-460 > Project: Apache ServiceComb > Issue Type: New Feature > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-461) Add blog to introduce how to join the community
[ https://issues.apache.org/jira/browse/SCB-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-461. --- Resolution: Resolved > Add blog to introduce how to join the community > --- > > Key: SCB-461 > URL: https://issues.apache.org/jira/browse/SCB-461 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-461) Add blog to introduce how to join the community
Bo Li created SCB-461: - Summary: Add blog to introduce how to join the community Key: SCB-461 URL: https://issues.apache.org/jira/browse/SCB-461 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Bo Li Assignee: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-460) Add blogs to introduce config-center integration in ServiceComb
Bo Li created SCB-460: - Summary: Add blogs to introduce config-center integration in ServiceComb Key: SCB-460 URL: https://issues.apache.org/jira/browse/SCB-460 Project: Apache ServiceComb Issue Type: New Feature Components: website Reporter: Bo Li Assignee: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-189) support async restTemplate
[ https://issues.apache.org/jira/browse/SCB-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-189: - Assignee: Bo Li (was: wujimin) > support async restTemplate > -- > > Key: SCB-189 > URL: https://issues.apache.org/jira/browse/SCB-189 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: Bo Li >Priority: Major > Fix For: service-center-1.0.0-m2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-379) Support Spring AsyncRestTemplate
[ https://issues.apache.org/jira/browse/SCB-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-379: - Assignee: Bo Li > Support Spring AsyncRestTemplate > > > Key: SCB-379 > URL: https://issues.apache.org/jira/browse/SCB-379 > Project: Apache ServiceComb > Issue Type: New Feature >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-371) support multiple config sources
[ https://issues.apache.org/jira/browse/SCB-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-371: - Assignee: Bo Li > support multiple config sources > --- > > Key: SCB-371 > URL: https://issues.apache.org/jira/browse/SCB-371 > Project: Apache ServiceComb > Issue Type: Sub-task >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > > As a user, he/she may want to try multiple configuration sources. > Need to support that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-379) Support Spring AsyncRestTemplate
Bo Li created SCB-379: - Summary: Support Spring AsyncRestTemplate Key: SCB-379 URL: https://issues.apache.org/jira/browse/SCB-379 Project: Apache ServiceComb Issue Type: New Feature Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-378) Add readme for samples so that users can run the samples code by just reading the readme doc
[ https://issues.apache.org/jira/browse/SCB-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-378: - Assignee: Bo Li > Add readme for samples so that users can run the samples code by just reading > the readme doc > > > Key: SCB-378 > URL: https://issues.apache.org/jira/browse/SCB-378 > Project: Apache ServiceComb > Issue Type: Task >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-378) Add readme for samples so that users can run the samples code by just reading the readme doc
Bo Li created SCB-378: - Summary: Add readme for samples so that users can run the samples code by just reading the readme doc Key: SCB-378 URL: https://issues.apache.org/jira/browse/SCB-378 Project: Apache ServiceComb Issue Type: Task Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-210) Use map feature to design microservice yaml file to support control flag of config center
[ https://issues.apache.org/jira/browse/SCB-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-210. --- Resolution: Resolved > Use map feature to design microservice yaml file to support control flag of > config center > - > > Key: SCB-210 > URL: https://issues.apache.org/jira/browse/SCB-210 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > > check comment of wujimin at: > https://github.com/apache/incubator-servicecomb-java-chassis/pull/489/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-371) support multiple config sources
Bo Li created SCB-371: - Summary: support multiple config sources Key: SCB-371 URL: https://issues.apache.org/jira/browse/SCB-371 Project: Apache ServiceComb Issue Type: Sub-task Reporter: Bo Li As a user, he/she may want to try multiple configuration sources. Need to support that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (SCB-210) Use map feature to design microservice yaml file to support control flag of config center
[ https://issues.apache.org/jira/browse/SCB-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16385670#comment-16385670 ] Bo Li edited comment on SCB-210 at 3/5/18 6:50 AM: --- 在foundations/foundataion-config/README.md下面看到了关于配置项映射的描述 进行配置项映射 有些情况下，我们要屏蔽我们使用的一些开源组件的配置并给用户提供我们自己的配置项。在这种情况下，可以通过classpath下的config.yaml进行映射定义： registry: client: serviceUrl: defaultZone: eureka.client.serviceUrl.defaultZone 定义映射后，在配置装载的时候框架会默认进行映射，把以我们定义的配置项映射为开源组件可以认的配置项。 was (Author: bo li): 在foundations/foundataion-config/README.md下面看到了关于配置项映射的描述。 ## 进行配置项映射 有些情况下，我们要屏蔽我们使用的一些开源组件的配置并给用户提供我们自己的配置项。在这种情况下，可以通过classpath下的config.yaml进行映射定义： registry: client: serviceUrl: defaultZone: eureka.client.serviceUrl.defaultZone 定义映射后，在配置装载的时候框架会默认进行映射，把以我们定义的配置项映射为开源组件可以认的配置项。 > Use map feature to design microservice yaml file to support control flag of > config center > - > > Key: SCB-210 > URL: https://issues.apache.org/jira/browse/SCB-210 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > > check comment of wujimin at: > https://github.com/apache/incubator-servicecomb-java-chassis/pull/489/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-349) Add document about how to use JIRA
[ https://issues.apache.org/jira/browse/SCB-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-349: - Assignee: Bo Li > Add document about how to use JIRA > -- > > Key: SCB-349 > URL: https://issues.apache.org/jira/browse/SCB-349 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-349) Add document about how to use JIRA
Bo Li created SCB-349: - Summary: Add document about how to use JIRA Key: SCB-349 URL: https://issues.apache.org/jira/browse/SCB-349 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-263) Exception occurs when a service first create in Apollo without released.
[ https://issues.apache.org/jira/browse/SCB-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-263. --- Resolution: Resolved Add notice in document to remind user to release namespace when project was first created at Apollo portal. > Exception occurs when a service first create in Apollo without released. > > > Key: SCB-263 > URL: https://issues.apache.org/jira/browse/SCB-263 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > > Json parser crashed when no configuration items released because there is no > body.configurations can be fetched. > Check body content before parse json. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-274) As the Configuration support of Apollo and Configuration Center are quite similar, it doesn't make sense that we put these two module into different places and have differe
Bo Li created SCB-274: - Summary: As the Configuration support of Apollo and Configuration Center are quite similar, it doesn't make sense that we put these two module into different places and have different configuration codes. Key: SCB-274 URL: https://issues.apache.org/jira/browse/SCB-274 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: Bo Li -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-263) Exception occurs when a service first create in Apollo without released.
Bo Li created SCB-263: - Summary: Exception occurs when a service first create in Apollo without released. Key: SCB-263 URL: https://issues.apache.org/jira/browse/SCB-263 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Bo Li Json parser crashed when no configuration items released because there is no body.configurations can be fetched. Check body content before parse json. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-263) Exception occurs when a service first create in Apollo without released.
[ https://issues.apache.org/jira/browse/SCB-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-263: - Assignee: Bo Li > Exception occurs when a service first create in Apollo without released. > > > Key: SCB-263 > URL: https://issues.apache.org/jira/browse/SCB-263 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > > Json parser crashed when no configuration items released because there is no > body.configurations can be fetched. > Check body content before parse json. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-262) many groupId in pom file still start with io.servicecomb while sc package have been renamed as org.apache.servicecomb
Bo Li created SCB-262: - Summary: many groupId in pom file still start with io.servicecomb while sc package have been renamed as org.apache.servicecomb Key: SCB-262 URL: https://issues.apache.org/jira/browse/SCB-262 Project: Apache ServiceComb Issue Type: Bug Components: website Reporter: Bo Li Need to update website description of groupId for pom file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-40) config change history
[ https://issues.apache.org/jira/browse/SCB-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-40: Assignee: Bo Li > config change history > - > > Key: SCB-40 > URL: https://issues.apache.org/jira/browse/SCB-40 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: mabin >Assignee: Bo Li >Priority: Minor > Fix For: java-chassis-1.0.0-m1 > > > Java-chassis can trace and record the operation event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-40) config change history
[ https://issues.apache.org/jira/browse/SCB-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330091#comment-16330091 ] Bo Li commented on SCB-40: -- The Apollo configuration center we have chosen before support tracing the changing history of configuration items perfectly. So this issue haved been resolved. > config change history > - > > Key: SCB-40 > URL: https://issues.apache.org/jira/browse/SCB-40 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: mabin >Priority: Minor > Fix For: java-chassis-1.0.0-m1 > > > Java-chassis can trace and record the operation event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-77) UI for config editing and viewing
[ https://issues.apache.org/jira/browse/SCB-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16330087#comment-16330087 ] Bo Li commented on SCB-77: -- The Apollo configuration center we have chosen before support edit and view configuration items perfectly. > UI for config editing and viewing > - > > Key: SCB-77 > URL: https://issues.apache.org/jira/browse/SCB-77 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: mabin >Assignee: Bo Li >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-77) UI for config editing and viewing
[ https://issues.apache.org/jira/browse/SCB-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-77: Assignee: Bo Li > UI for config editing and viewing > - > > Key: SCB-77 > URL: https://issues.apache.org/jira/browse/SCB-77 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: mabin >Assignee: Bo Li >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-133) Dynamic configuration document for users
[ https://issues.apache.org/jira/browse/SCB-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li resolved SCB-133. --- Resolution: Resolved > Dynamic configuration document for users > > > Key: SCB-133 > URL: https://issues.apache.org/jira/browse/SCB-133 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-210) Use map feature to design microservice yaml file to support control flag of config center
[ https://issues.apache.org/jira/browse/SCB-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317995#comment-16317995 ] Bo Li commented on SCB-210: --- Need to ask some help from ZhangQi about how to use the feature of mapping a key to another. > Use map feature to design microservice yaml file to support control flag of > config center > - > > Key: SCB-210 > URL: https://issues.apache.org/jira/browse/SCB-210 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li > > check comment of wujimin at: > https://github.com/apache/incubator-servicecomb-java-chassis/pull/489/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-210) Use map feature to design microservice yaml file to support control flag of config center
[ https://issues.apache.org/jira/browse/SCB-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-210: - Assignee: Bo Li > Use map feature to design microservice yaml file to support control flag of > config center > - > > Key: SCB-210 > URL: https://issues.apache.org/jira/browse/SCB-210 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li > > check comment of wujimin at: > https://github.com/apache/incubator-servicecomb-java-chassis/pull/489/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-210) Use map feature to design microservice yaml file to support control flag of config center
Bo Li created SCB-210: - Summary: Use map feature to design microservice yaml file to support control flag of config center Key: SCB-210 URL: https://issues.apache.org/jira/browse/SCB-210 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Bo Li check comment of wujimin at: https://github.com/apache/incubator-servicecomb-java-chassis/pull/489/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-208) create a root module for third party config center support including foundation-config-cc
[ https://issues.apache.org/jira/browse/SCB-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16317580#comment-16317580 ] Bo Li commented on SCB-208: --- Root module dynamic-config have already been created, module of config-apollo is for Apollo. Next, we need to transfer foundation-config-cc to this root module too. > create a root module for third party config center support including > foundation-config-cc > - > > Key: SCB-208 > URL: https://issues.apache.org/jira/browse/SCB-208 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-208) create a root module for third party config center support including foundation-config-cc
[ https://issues.apache.org/jira/browse/SCB-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-208: - Assignee: Bo Li > create a root module for third party config center support including > foundation-config-cc > - > > Key: SCB-208 > URL: https://issues.apache.org/jira/browse/SCB-208 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-208) create a root module for third party config center support including foundation-config-cc
Bo Li created SCB-208: - Summary: create a root module for third party config center support including foundation-config-cc Key: SCB-208 URL: https://issues.apache.org/jira/browse/SCB-208 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: Bo Li Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-142) Document translation for Developers section in website
Bo Li created SCB-142: - Summary: Document translation for Developers section in website Key: SCB-142 URL: https://issues.apache.org/jira/browse/SCB-142 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-30) Analyse how to implement dynamic configuration in Chassis
[ https://issues.apache.org/jira/browse/SCB-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-30: Assignee: Bo Li > Analyse how to implement dynamic configuration in Chassis > - > > Key: SCB-30 > URL: https://issues.apache.org/jira/browse/SCB-30 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: Bo Li >Assignee: Bo Li >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-63) The third party config center survey
[ https://issues.apache.org/jira/browse/SCB-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Li reassigned SCB-63: Assignee: Bo Li > The third party config center survey > > > Key: SCB-63 > URL: https://issues.apache.org/jira/browse/SCB-63 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: mabin >Assignee: Bo Li > > Analyse major open source dynamic config center and choose classic one to > support. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-133) Dynamic configuration document for users
Bo Li created SCB-133: - Summary: Dynamic configuration document for users Key: SCB-133 URL: https://issues.apache.org/jira/browse/SCB-133 Project: Apache ServiceComb Issue Type: Sub-task Reporter: Bo Li -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-123) Add DISLAIMER to the ServiceComb git repo
[ https://issues.apache.org/jira/browse/SCB-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303459#comment-16303459 ] Bo Li commented on SCB-123: --- To include Apache disclaimer for git repos: # Modify current README.md file to update project description by PR. Already done! # Update git repos description by JIRA so that administrators can edit current repo description. In progress. > Add DISLAIMER to the ServiceComb git repo > - > > Key: SCB-123 > URL: https://issues.apache.org/jira/browse/SCB-123 > Project: Apache ServiceComb > Issue Type: Task >Reporter: Willem Jiang >Assignee: Bo Li > Labels: easyfix > > The Git repos need to have DISLAIMER according to Roman's suggestion[1]. > [1]https://lists.apache.org/thread.html/a4d302ef3f031de4512d3cc1e51a0ff4ca00635db15076bc54c13321@%3Cdev.servicecomb.apache.org%3E -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-122) Add incubating note to website
[ https://issues.apache.org/jira/browse/SCB-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303453#comment-16303453 ] Bo Li commented on SCB-122: --- To include Apache DISCLAIMER # Modify ServiceComb to Apache ServiceComb (incubating) at header and footer # Update ServiceComb logo at header to Apache ServiceComb (incubating) > Add incubating note to website > -- > > Key: SCB-122 > URL: https://issues.apache.org/jira/browse/SCB-122 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Willem Jiang >Assignee: Bo Li > Labels: easyfix > >Your website at http://servicecomb.incubator.apache.org/ >looks great, but you need to pay attention to the ASF >podling branding guidelines: > https://incubator.apache.org/guides/branding.html#disclaimers >In particular you need to include the Incubator disclaimer >AND most importantly make sure that it is clear that this is >Apache ServiceComb (incubating) and not just ServiceComb. >A good example to follow would be something like: > http://annotator.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-122) Add incubating note to website
[ https://issues.apache.org/jira/browse/SCB-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303089#comment-16303089 ] Bo Li commented on SCB-122: --- Or I can update the logo ServiceComb to Apache ServiceComb (incubating) at the header section. > Add incubating note to website > -- > > Key: SCB-122 > URL: https://issues.apache.org/jira/browse/SCB-122 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Willem Jiang >Assignee: Bo Li > Labels: easyfix > >Your website at http://servicecomb.incubator.apache.org/ >looks great, but you need to pay attention to the ASF >podling branding guidelines: > https://incubator.apache.org/guides/branding.html#disclaimers >In particular you need to include the Incubator disclaimer >AND most importantly make sure that it is clear that this is >Apache ServiceComb (incubating) and not just ServiceComb. >A good example to follow would be something like: > http://annotator.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-122) Add incubating note to website
[ https://issues.apache.org/jira/browse/SCB-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303080#comment-16303080 ] Bo Li commented on SCB-122: --- I will add the disclaimer ASAP. How about put it at the footer section in original website? [~njiang] > Add incubating note to website > -- > > Key: SCB-122 > URL: https://issues.apache.org/jira/browse/SCB-122 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Willem Jiang >Assignee: Bo Li > Labels: easyfix > >Your website at http://servicecomb.incubator.apache.org/ >looks great, but you need to pay attention to the ASF >podling branding guidelines: > https://incubator.apache.org/guides/branding.html#disclaimers >In particular you need to include the Incubator disclaimer >AND most importantly make sure that it is clear that this is >Apache ServiceComb (incubating) and not just ServiceComb. >A good example to follow would be something like: > http://annotator.incubator.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-121) Section header missed for servicecomb website document at run-mode part.
Bo Li created SCB-121: - Summary: Section header missed for servicecomb website document at run-mode part. Key: SCB-121 URL: https://issues.apache.org/jira/browse/SCB-121 Project: Apache ServiceComb Issue Type: Bug Components: website Reporter: Bo Li Priority: Minor Only step 2 for run-mode at http://servicecomb.io/users/run-mode/ at WEB container mode section shows up. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-115) Security document translation
Bo Li created SCB-115: - Summary: Security document translation Key: SCB-115 URL: https://issues.apache.org/jira/browse/SCB-115 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li # Use TLS doc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-114) Deployment document translation
Bo Li created SCB-114: - Summary: Deployment document translation Key: SCB-114 URL: https://issues.apache.org/jira/browse/SCB-114 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li # Run Mode doc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-112) Edging Service document translation
Bo Li created SCB-112: - Summary: Edging Service document translation Key: SCB-112 URL: https://issues.apache.org/jira/browse/SCB-112 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li Edging Service document translation contains following part: # confd and Nginx # Zuul -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-111) General Development Translation
Bo Li created SCB-111: - Summary: General Development Translation Key: SCB-111 URL: https://issues.apache.org/jira/browse/SCB-111 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li General Development Translation contains following part: # Develop and Test in Local Environment # User ServiceComb in SpringBoot # Distribute Tracing # Customized Tracing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-110) Develop Service Consumer Document Translation
Bo Li created SCB-110: - Summary: Develop Service Consumer Document Translation Key: SCB-110 URL: https://issues.apache.org/jira/browse/SCB-110 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li Develop Service Consumer Document Translation contains following part: # Develop with Rest Template # Develop with Transparent RPC # Use Service Contract # Invoke Control -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-109) Develop Service Provider Translation
Bo Li created SCB-109: - Summary: Develop Service Provider Translation Key: SCB-109 URL: https://issues.apache.org/jira/browse/SCB-109 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li Develop Service Provider translation contains: # Service Definition # Service Contract # Develop Microservice with SpringMVC # Develop Microservice with JAX-RS # Develop Microservice with Transparent-RPC # Service Interface Constraints # Service Configurations # Communicate Protocol # Application Boot Up Process # Service Heartbeat -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-108) User Guide Translation
Bo Li created SCB-108: - Summary: User Guide Translation Key: SCB-108 URL: https://issues.apache.org/jira/browse/SCB-108 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li *User guide contains two part:* * Java Chassis Architecture * Setup Environment -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-107) Document Translation
Bo Li created SCB-107: - Summary: Document Translation Key: SCB-107 URL: https://issues.apache.org/jira/browse/SCB-107 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Bo Li There are some user guide document in Chinese need to be translated into English. Please refer to http://servicecomb.io/users/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-105) Invalid hyperlink at http://servicecomb.io/cn/developers/submit-codesI
Bo Li created SCB-105: - Summary: Invalid hyperlink at http://servicecomb.io/cn/developers/submit-codesI Key: SCB-105 URL: https://issues.apache.org/jira/browse/SCB-105 Project: Apache ServiceComb Issue Type: Bug Components: website Reporter: Bo Li Priority: Minor Hyperlink is not available after the project was moved to ApacheInfra. At http://servicecomb.io/cn/developers/submit-codes/ PR guild, Github, it jumps to old repository but not ApacheInfra. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-94) How about changing the log module to logus or other opensource project?
Bo Li created SCB-94: Summary: How about changing the log module to logus or other opensource project? Key: SCB-94 URL: https://issues.apache.org/jira/browse/SCB-94 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Reporter: Bo Li How about to change the log module to logus or other opensource project? https://github.com/ServiceComb/service-center/tree/master/lager -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-93) inconsistent configuration folders
Bo Li created SCB-93: Summary: inconsistent configuration folders Key: SCB-93 URL: https://issues.apache.org/jira/browse/SCB-93 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Reporter: Bo Li he certificates stores under etc/ssl folder, while the application configuration files stores under conf folder, which looks inconsistent. Is it a better idea to merge both of it under etc folder? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-89) Restart local service-center and service-center hung
Bo Li created SCB-89: Summary: Restart local service-center and service-center hung Key: SCB-89 URL: https://issues.apache.org/jira/browse/SCB-89 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Reporter: Bo Li # Download service-center-0.4.0-linux-amd64.tar.gz # Execute start.sh # Send CTRL+C after SC is ready # Execute start.sh again # And SC hung for some reasons. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SCB-88) error occurs when start a service following "quick start"
[
https://issues.apache.org/jira/browse/SCB-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li updated SCB-88:
-
Component/s: Java-Chassis
> error occurs when start a service following "quick start"
> -
>
> Key: SCB-88
> URL: https://issues.apache.org/jira/browse/SCB-88
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>
> {code}
> java.net.ConnectException: Failed to connect to /127.0.0.1:9411
> at
> okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:189)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:173)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:193)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:129)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:98)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:109)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:124)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:170)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.access$100(RealCall.java:33) ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall$AsyncCall.execute(RealCall.java:120)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
> [okhttp-3.4.1.jar:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_121]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-88) error occurs when start a service following "quick start"
Bo Li created SCB-88:
Summary: error occurs when start a service following "quick start"
Key: SCB-88
URL: https://issues.apache.org/jira/browse/SCB-88
Project: Apache ServiceComb
Issue Type: Bug
Reporter: Bo Li
{code}
java.net.ConnectException: Failed to connect to /127.0.0.1:9411
at
okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:189)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:173)
~[okhttp-3.4.1.jar:na]
at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:193)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:129)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:98)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
~[okhttp-3.4.1.jar:na]
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:109)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
~[okhttp-3.4.1.jar:na]
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:124)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
~[okhttp-3.4.1.jar:na]
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:170)
~[okhttp-3.4.1.jar:na]
at okhttp3.RealCall.access$100(RealCall.java:33) ~[okhttp-3.4.1.jar:na]
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:120) ~[okhttp-3.4.1.jar:na]
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
[okhttp-3.4.1.jar:na]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_121]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-87) can anyone provide a gradle script?
Bo Li created SCB-87: Summary: can anyone provide a gradle script? Key: SCB-87 URL: https://issues.apache.org/jira/browse/SCB-87 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Bo Li -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-86) can not find handler :tracing-provider
Bo Li created SCB-86:
Summary: can not find handler :tracing-provider
Key: SCB-86
URL: https://issues.apache.org/jira/browse/SCB-86
Project: Apache ServiceComb
Issue Type: Bug
Components: Java-Chassis
Reporter: Bo Li
{code}java.lang.Error: can not find handler: tracing-project {code} error
occurs when runing bmi distributed tracing demo.
microservice.yaml configuration is:
{code}
APPLICATION_ID: bmi
service_description:
# name of the declaring microservice
name: calculator
version: 0.0.1
cse:
service:
registry:
address: http://127.0.0.1:30100
rest:
address: 0.0.0.0:
handler:
chain:
Provider:
default: tracing-provider
{code}
exception throwed when runing CalculationApplication:
{code}
2017-09-19 11:57:28,586 [ERROR] Application startup failed
org.springframework.boot.SpringApplication.reportFailure(SpringApplication.java:840)
java.lang.Error: can not find handler :tracing-provider
at
io.servicecomb.core.handler.AbstractHandlerManager.convertToChainClass(AbstractHandlerManager.java:68)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.handler.AbstractHandlerManager.createHandlerChain(AbstractHandlerManager.java:82)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:110)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:32)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.foundation.common.AbstractObjectManager.getOrCreate(AbstractObjectManager.java:36)
~[foundation-common-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.loader.SchemaLoader.registerSchema(SchemaLoader.java:94)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:112)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:42)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:59)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:75)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
~[provider-rest-common-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:43)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:113)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:99)
~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:318)
[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1187)
[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1176)
[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
io.servicecomb.samples.bmi.CalculatorApplication.main(CalculatorApplication.java:29)
[classes/:?]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-84) Is there a interface for user to find service according to schemaId
Bo Li created SCB-84: Summary: Is there a interface for user to find service according to schemaId Key: SCB-84 URL: https://issues.apache.org/jira/browse/SCB-84 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Bo Li -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-82) NoClassDefFoundError occurs when creating Provider service following "QuickStart"
Bo Li created SCB-82:
Summary: NoClassDefFoundError occurs when creating Provider
service following "QuickStart"
Key: SCB-82
URL: https://issues.apache.org/jira/browse/SCB-82
Project: Apache ServiceComb
Issue Type: Bug
Components: Java-Chassis
Reporter: Bo Li
{code}
java.lang.NoClassDefFoundError: com/fasterxml/jackson/core/FormatFeature
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-81) Question about yaml file version
Bo Li created SCB-81: Summary: Question about yaml file version Key: SCB-81 URL: https://issues.apache.org/jira/browse/SCB-81 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Bo Li * how to user yaml file version, i notived that microservice.yaml file's version is 0.0.3. * what's the relation between the three number separated by dot above? * is there any limit of those numbers? what's tha maximum? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
