[jira] [Created] (SCB-1080) Add a log while get empty server list

2018-12-13 Thread laijianbin (JIRA)
laijianbin created SCB-1080:
---

 Summary: Add a log while get empty server list
 Key: SCB-1080
 URL: https://issues.apache.org/jira/browse/SCB-1080
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-1030) NPE when use DynamicSchemaLoader.registerSchemas(String, String)

2018-11-18 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691334#comment-16691334
 ] 

laijianbin commented on SCB-1030:
-

复现步骤:

步骤一

在启动函数中添加DynamicSchemaLoader.INSTANCE.registerSchemas("bmiproviderdfdfd", 
"classpath*:dynamicschema/*.yaml");

public class BmiproviderApplication {
 public static void main(String[] args) throws Exception {
 Log4jUtils.init();
 BeanUtils.init();
 DynamicSchemaLoader.INSTANCE.registerSchemas("bmiproviderdfdfd", 
"classpath*:dynamicschema/*.yaml");
 }
}

步骤二

访问静态接口,查看日志为空指针

!image-2018-11-19-15-23-58-612.png!

> NPE when use DynamicSchemaLoader.registerSchemas(String, String)
> 
>
> Key: SCB-1030
> URL: https://issues.apache.org/jira/browse/SCB-1030
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Attachments: image-2018-11-19-15-23-58-612.png
>
>
> 2018-11-19 11:46:14,758 [ERROR] http server failed. 
> org.apache.servicecomb.transport.rest.vertx.VertxRestDispatcher.failureHandler(VertxRestDispatcher.java:72)
> java.lang.NullPointerException
>  at 
> org.apache.servicecomb.common.rest.locator.OperationLocator.locate(OperationLocator.java:56)
>  at 
> org.apache.servicecomb.common.rest.locator.ServicePathManager.producerLocateOperation(ServicePathManager.java:116)
>  at 
> org.apache.servicecomb.common.rest.RestProducerInvocation.locateOperation(RestProducerInvocation.java:61)
>  at 
> org.apache.servicecomb.common.rest.AbstractRestInvocation.findRestOperation(AbstractRestInvocation.java:80)
>  at 
> org.apache.servicecomb.common.rest.RestProducerInvocation.findRestOperation(RestProducerInvocation.java:56)
>  at 
> org.apache.servicecomb.common.rest.RestProducerInvocation.invoke(RestProducerInvocation.java:45)
>  at 
> org.apache.servicecomb.transport.rest.vertx.VertxRestDispatcher.onRequest(VertxRestDispatcher.java:194)
>  at io.vertx.ext.web.impl.RouteImpl.handleContext(RouteImpl.java:223)
>  at 
> io.vertx.ext.web.impl.RoutingContextImplBase.iterateNext(RoutingContextImplBase.java:101)
>  at io.vertx.ext.web.impl.RoutingContextImpl.next(RoutingContextImpl.java:120)
>  at 
> org.apache.servicecomb.transport.rest.vertx.RestBodyHandler$BHandler.doEnd(RestBodyHandler.java:248)
>  at 
> org.apache.servicecomb.transport.rest.vertx.RestBodyHandler$BHandler.end(RestBodyHandler.java:226)
>  at 
> org.apache.servicecomb.transport.rest.vertx.RestBodyHandler.lambda$0(RestBodyHandler.java:86)
>  at 
> io.vertx.core.http.impl.HttpServerRequestImpl.handleEnd(HttpServerRequestImpl.java:418)
>  at 
> io.vertx.core.http.impl.ServerConnection.handleLastHttpContent(ServerConnection.java:475)
>  at 
> io.vertx.core.http.impl.ServerConnection.processMessage(ServerConnection.java:446)
>  at 
> io.vertx.core.http.impl.ServerConnection.handleMessage(ServerConnection.java:156)
>  at 
> io.vertx.core.http.impl.HttpServerImpl$ServerHandlerWithWebSockets.handleMessage(HttpServerImpl.java:705)
>  at 
> io.vertx.core.http.impl.HttpServerImpl$ServerHandlerWithWebSockets.handleMessage(HttpServerImpl.java:614)
>  at 
> io.vertx.core.net.impl.VertxHandler.lambda$channelRead$1(VertxHandler.java:150)
>  at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:342)
>  at io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:200)
>  at io.vertx.core.net.impl.VertxHandler.channelRead(VertxHandler.java:148)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
>  at 
> io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
>  at 
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
>  at 
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
>  at io.vertx.core.http.impl.Http1xOrH2CHandler.end(Http1xOrH2CHandler.java:49)
>  

[jira] [Updated] (SCB-1030) NPE when use DynamicSchemaLoader.registerSchemas(String, String)

2018-11-18 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin updated SCB-1030:

Attachment: image-2018-11-19-15-23-58-612.png

> NPE when use DynamicSchemaLoader.registerSchemas(String, String)
> 
>
> Key: SCB-1030
> URL: https://issues.apache.org/jira/browse/SCB-1030
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Attachments: image-2018-11-19-15-23-58-612.png
>
>
> 2018-11-19 11:46:14,758 [ERROR] http server failed. 
> org.apache.servicecomb.transport.rest.vertx.VertxRestDispatcher.failureHandler(VertxRestDispatcher.java:72)
> java.lang.NullPointerException
>  at 
> org.apache.servicecomb.common.rest.locator.OperationLocator.locate(OperationLocator.java:56)
>  at 
> org.apache.servicecomb.common.rest.locator.ServicePathManager.producerLocateOperation(ServicePathManager.java:116)
>  at 
> org.apache.servicecomb.common.rest.RestProducerInvocation.locateOperation(RestProducerInvocation.java:61)
>  at 
> org.apache.servicecomb.common.rest.AbstractRestInvocation.findRestOperation(AbstractRestInvocation.java:80)
>  at 
> org.apache.servicecomb.common.rest.RestProducerInvocation.findRestOperation(RestProducerInvocation.java:56)
>  at 
> org.apache.servicecomb.common.rest.RestProducerInvocation.invoke(RestProducerInvocation.java:45)
>  at 
> org.apache.servicecomb.transport.rest.vertx.VertxRestDispatcher.onRequest(VertxRestDispatcher.java:194)
>  at io.vertx.ext.web.impl.RouteImpl.handleContext(RouteImpl.java:223)
>  at 
> io.vertx.ext.web.impl.RoutingContextImplBase.iterateNext(RoutingContextImplBase.java:101)
>  at io.vertx.ext.web.impl.RoutingContextImpl.next(RoutingContextImpl.java:120)
>  at 
> org.apache.servicecomb.transport.rest.vertx.RestBodyHandler$BHandler.doEnd(RestBodyHandler.java:248)
>  at 
> org.apache.servicecomb.transport.rest.vertx.RestBodyHandler$BHandler.end(RestBodyHandler.java:226)
>  at 
> org.apache.servicecomb.transport.rest.vertx.RestBodyHandler.lambda$0(RestBodyHandler.java:86)
>  at 
> io.vertx.core.http.impl.HttpServerRequestImpl.handleEnd(HttpServerRequestImpl.java:418)
>  at 
> io.vertx.core.http.impl.ServerConnection.handleLastHttpContent(ServerConnection.java:475)
>  at 
> io.vertx.core.http.impl.ServerConnection.processMessage(ServerConnection.java:446)
>  at 
> io.vertx.core.http.impl.ServerConnection.handleMessage(ServerConnection.java:156)
>  at 
> io.vertx.core.http.impl.HttpServerImpl$ServerHandlerWithWebSockets.handleMessage(HttpServerImpl.java:705)
>  at 
> io.vertx.core.http.impl.HttpServerImpl$ServerHandlerWithWebSockets.handleMessage(HttpServerImpl.java:614)
>  at 
> io.vertx.core.net.impl.VertxHandler.lambda$channelRead$1(VertxHandler.java:150)
>  at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:342)
>  at io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:200)
>  at io.vertx.core.net.impl.VertxHandler.channelRead(VertxHandler.java:148)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
>  at 
> io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
>  at 
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
>  at 
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
>  at io.vertx.core.http.impl.Http1xOrH2CHandler.end(Http1xOrH2CHandler.java:49)
>  at 
> io.vertx.core.http.impl.Http1xOrH2CHandler.channelRead(Http1xOrH2CHandler.java:27)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
>  at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
>  at 
> 

[jira] [Created] (SCB-1030) NPE when use DynamicSchemaLoader.registerSchemas(String, String)

2018-11-18 Thread laijianbin (JIRA)
laijianbin created SCB-1030:
---

 Summary: NPE when use DynamicSchemaLoader.registerSchemas(String, 
String)
 Key: SCB-1030
 URL: https://issues.apache.org/jira/browse/SCB-1030
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin


2018-11-19 11:46:14,758 [ERROR] http server failed. 
org.apache.servicecomb.transport.rest.vertx.VertxRestDispatcher.failureHandler(VertxRestDispatcher.java:72)
java.lang.NullPointerException
 at 
org.apache.servicecomb.common.rest.locator.OperationLocator.locate(OperationLocator.java:56)
 at 
org.apache.servicecomb.common.rest.locator.ServicePathManager.producerLocateOperation(ServicePathManager.java:116)
 at 
org.apache.servicecomb.common.rest.RestProducerInvocation.locateOperation(RestProducerInvocation.java:61)
 at 
org.apache.servicecomb.common.rest.AbstractRestInvocation.findRestOperation(AbstractRestInvocation.java:80)
 at 
org.apache.servicecomb.common.rest.RestProducerInvocation.findRestOperation(RestProducerInvocation.java:56)
 at 
org.apache.servicecomb.common.rest.RestProducerInvocation.invoke(RestProducerInvocation.java:45)
 at 
org.apache.servicecomb.transport.rest.vertx.VertxRestDispatcher.onRequest(VertxRestDispatcher.java:194)
 at io.vertx.ext.web.impl.RouteImpl.handleContext(RouteImpl.java:223)
 at 
io.vertx.ext.web.impl.RoutingContextImplBase.iterateNext(RoutingContextImplBase.java:101)
 at io.vertx.ext.web.impl.RoutingContextImpl.next(RoutingContextImpl.java:120)
 at 
org.apache.servicecomb.transport.rest.vertx.RestBodyHandler$BHandler.doEnd(RestBodyHandler.java:248)
 at 
org.apache.servicecomb.transport.rest.vertx.RestBodyHandler$BHandler.end(RestBodyHandler.java:226)
 at 
org.apache.servicecomb.transport.rest.vertx.RestBodyHandler.lambda$0(RestBodyHandler.java:86)
 at 
io.vertx.core.http.impl.HttpServerRequestImpl.handleEnd(HttpServerRequestImpl.java:418)
 at 
io.vertx.core.http.impl.ServerConnection.handleLastHttpContent(ServerConnection.java:475)
 at 
io.vertx.core.http.impl.ServerConnection.processMessage(ServerConnection.java:446)
 at 
io.vertx.core.http.impl.ServerConnection.handleMessage(ServerConnection.java:156)
 at 
io.vertx.core.http.impl.HttpServerImpl$ServerHandlerWithWebSockets.handleMessage(HttpServerImpl.java:705)
 at 
io.vertx.core.http.impl.HttpServerImpl$ServerHandlerWithWebSockets.handleMessage(HttpServerImpl.java:614)
 at 
io.vertx.core.net.impl.VertxHandler.lambda$channelRead$1(VertxHandler.java:150)
 at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:342)
 at io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:200)
 at io.vertx.core.net.impl.VertxHandler.channelRead(VertxHandler.java:148)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 at 
io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:310)
 at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:284)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 at io.vertx.core.http.impl.Http1xOrH2CHandler.end(Http1xOrH2CHandler.java:49)
 at 
io.vertx.core.http.impl.Http1xOrH2CHandler.channelRead(Http1xOrH2CHandler.java:27)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 at 
io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
 at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
 at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
 at 

[jira] [Closed] (SCB-1019) consumer support application/xml MIME type

2018-11-18 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-1019.
---
Resolution: Invalid
  Assignee: laijianbin

> consumer support application/xml MIME type
> --
>
> Key: SCB-1019
> URL: https://issues.apache.org/jira/browse/SCB-1019
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-1019) (https://issues.apache.org/jira/browse/SCB

2018-11-11 Thread laijianbin (JIRA)
laijianbin created SCB-1019:
---

 Summary: (https://issues.apache.org/jira/browse/SCB
 Key: SCB-1019
 URL: https://issues.apache.org/jira/browse/SCB-1019
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-942) choose the highest priority from all implementation classes

2018-09-27 Thread laijianbin (JIRA)
laijianbin created SCB-942:
--

 Summary: choose the highest priority from all implementation 
classes
 Key: SCB-942
 URL: https://issues.apache.org/jira/browse/SCB-942
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-932) Time jump cause the new request injected

2018-09-27 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-932.
--
Resolution: Fixed

> Time jump cause the new request injected
> 
>
> Key: SCB-932
> URL: https://issues.apache.org/jira/browse/SCB-932
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-710) If failed to get SC instance ,autoDiscoveryInited should be "false"

2018-09-20 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-710.
--
Resolution: Fixed

> If failed to get SC instance ,autoDiscoveryInited should be "false"
> ---
>
> Key: SCB-710
> URL: https://issues.apache.org/jira/browse/SCB-710
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-884) already return, no need else

2018-09-20 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-884.
--
Resolution: Fixed

> already return, no need else
> 
>
> Key: SCB-884
> URL: https://issues.apache.org/jira/browse/SCB-884
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-920) Remove duplicate dependencies

2018-09-20 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-920.
--
Resolution: Fixed

I make a mistake, there is no need to modify

> Remove duplicate dependencies
> -
>
> Key: SCB-920
> URL: https://issues.apache.org/jira/browse/SCB-920
> Project: Apache ServiceComb
>  Issue Type: Task
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.1.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-932) Time jump cause the new request injected

2018-09-20 Thread laijianbin (JIRA)
laijianbin created SCB-932:
--

 Summary: Time jump cause the new request injected
 Key: SCB-932
 URL: https://issues.apache.org/jira/browse/SCB-932
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-920) Remove duplicate dependencies

2018-09-17 Thread laijianbin (JIRA)
laijianbin created SCB-920:
--

 Summary: Remove duplicate dependencies
 Key: SCB-920
 URL: https://issues.apache.org/jira/browse/SCB-920
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-811) refact handler-loadbalance Configuration.java

2018-08-06 Thread laijianbin (JIRA)
laijianbin created SCB-811:
--

 Summary: refact handler-loadbalance Configuration.java
 Key: SCB-811
 URL: https://issues.apache.org/jira/browse/SCB-811
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-801) delete useless demo

2018-08-03 Thread laijianbin (JIRA)
laijianbin created SCB-801:
--

 Summary: delete useless demo
 Key: SCB-801
 URL: https://issues.apache.org/jira/browse/SCB-801
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-595) Compatible with old SC versions

2018-07-13 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-595.
--
   Resolution: Fixed
Fix Version/s: (was: java-chassis-1.0.0)

> Compatible with old SC versions
> ---
>
> Key: SCB-595
> URL: https://issues.apache.org/jira/browse/SCB-595
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>
> As Framework version use json style like xxx:xxx,but old Service 
> Center(eg:2.2.49) is not Compatible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-595) Compatible with old SC versions

2018-07-13 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542775#comment-16542775
 ] 

laijianbin commented on SCB-595:


This problem now no need to resolve,so I close this issue

> Compatible with old SC versions
> ---
>
> Key: SCB-595
> URL: https://issues.apache.org/jira/browse/SCB-595
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.0.0
>
>
> As Framework version use json style like xxx:xxx,but old Service 
> Center(eg:2.2.49) is not Compatible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-737) avoid null point exception

2018-07-11 Thread laijianbin (JIRA)
laijianbin created SCB-737:
--

 Summary: avoid null point exception
 Key: SCB-737
 URL: https://issues.apache.org/jira/browse/SCB-737
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin


2018-07-11 
03:27:52,651Z(28241):ERROR{}[main]org.springframework.boot.SpringApplication.reportFailure(SpringApplication.java:771)-->Application
 startup failed

org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'batchConfig': Unsatisfied dependency expressed through 
field 'jobBuilderFactory'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'jobBuilders' defined in class path resource 
[org/springframework/batch/core/configuration/annotation/SimpleBatchConfiguration.class]:
 Bean instantiation via factory method failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to instantiate 
[org.springframework.batch.core.configuration.annotation.JobBuilderFactory]: 
Factory method 'jobBuilders' threw exception; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'jobRepository' defined in class path resource 
[org/springframework/batch/core/configuration/annotation/SimpleBatchConfiguration.class]:
 Initialization of bean failed; nested exception is 
java.lang.NullPointerException

 

RELEASE]

    at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:207)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1136)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1064)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:585)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    ... 19 more

Caused by: java.lang.NullPointerException

    at 
org.apache.servicecomb.provider.rest.common.RestProducers.processProvider(RestProducers.java:52)
 ~[provider-rest-common-1.0.0.B003.6.jar:1.0.0.B003.6]

    at 
org.apache.servicecomb.provider.rest.common.RestProducers.postProcessAfterInitialization(RestProducers.java:43)
 ~[provider-rest-common-1.0.0.B003.6.jar:1.0.0.B003.6]

    at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:423)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1594)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:554)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
 ~[spring-beans-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 
org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:381)
 ~[spring-context-4.3.5.RELEASE.jar:4.3.5.RELEASE]

    at 

[jira] [Commented] (SCB-718) If auto discovery failed , will cause a dead cycle

2018-07-06 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534548#comment-16534548
 ] 

laijianbin commented on SCB-718:


This bug must open auto  discovery switch

> If auto discovery failed , will cause a dead cycle
> --
>
> Key: SCB-718
> URL: https://issues.apache.org/jira/browse/SCB-718
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-718) If auto discovery failed , will cause a dead cycle

2018-07-05 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534350#comment-16534350
 ] 

laijianbin commented on SCB-718:


There are two change to resolve this bug

1.Executing auto discovery init method after micro-service instance registered

2.Add a Timer schedule get instance cache

> If auto discovery failed , will cause a dead cycle
> --
>
> Key: SCB-718
> URL: https://issues.apache.org/jira/browse/SCB-718
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-710) If failed to get SC instance ,autoDiscoveryInited should be "false"

2018-07-03 Thread laijianbin (JIRA)
laijianbin created SCB-710:
--

 Summary: If failed to get SC instance ,autoDiscoveryInited should 
be "false"
 Key: SCB-710
 URL: https://issues.apache.org/jira/browse/SCB-710
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-693) registry microservice failed if get host address failed

2018-06-24 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521781#comment-16521781
 ] 

laijianbin commented on SCB-693:


java.net.SocketException: No such device(getFlags() failed)

at java.net.NetworkInterface.isUp0(Native method)

at java.net.NetworkInterface.isUp(NetworkInterface.java 387)

> registry microservice failed if get host address failed
> ---
>
> Key: SCB-693
> URL: https://issues.apache.org/jira/browse/SCB-693
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>
> !20180625-101900(eSpace).png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-693) registry microservice failed if get host address failed

2018-06-24 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521778#comment-16521778
 ] 

laijianbin commented on SCB-693:


!image-2018-06-25-10-29-06-532.png!

> registry microservice failed if get host address failed
> ---
>
> Key: SCB-693
> URL: https://issues.apache.org/jira/browse/SCB-693
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>
> !20180625-101900(eSpace).png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Issue Comment Deleted] (SCB-693) registry microservice failed if get host address failed

2018-06-24 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin updated SCB-693:
---
Comment: was deleted

(was: !20180625-101900(eSpace).png!)

> registry microservice failed if get host address failed
> ---
>
> Key: SCB-693
> URL: https://issues.apache.org/jira/browse/SCB-693
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>
> !20180625-101900(eSpace).png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-693) registry microservice failed if get host address failed

2018-06-24 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16521776#comment-16521776
 ] 

laijianbin commented on SCB-693:


!20180625-101900(eSpace).png!

> registry microservice failed if get host address failed
> ---
>
> Key: SCB-693
> URL: https://issues.apache.org/jira/browse/SCB-693
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>
> !20180625-101900(eSpace).png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-693) registry microservice failed if get host address failed

2018-06-24 Thread laijianbin (JIRA)
laijianbin created SCB-693:
--

 Summary: registry microservice failed if get host address failed
 Key: SCB-693
 URL: https://issues.apache.org/jira/browse/SCB-693
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin


!20180625-101900(eSpace).png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-471) vertx upgrade causes use config center push mode error

2018-06-03 Thread laijianbin (JIRA)


 [ 
https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-471.
--
Resolution: Fixed

> vertx upgrade causes use config center push mode error 
> ---
>
> Key: SCB-471
> URL: https://issues.apache.org/jira/browse/SCB-471
> Project: Apache ServiceComb
>  Issue Type: Task
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-471) vertx upgrade causes use config center push mode error

2018-06-03 Thread laijianbin (JIRA)


[ 
https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499698#comment-16499698
 ] 

laijianbin commented on SCB-471:


There is no problem right now,so I close this JIRA

> vertx upgrade causes use config center push mode error 
> ---
>
> Key: SCB-471
> URL: https://issues.apache.org/jira/browse/SCB-471
> Project: Apache ServiceComb
>  Issue Type: Task
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-599) Service registry failed when service before Service Center start

2018-05-24 Thread laijianbin (JIRA)

 [ 
https://issues.apache.org/jira/browse/SCB-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-599.
--
Resolution: Fixed

> Service registry failed when service before Service Center start
> 
>
> Key: SCB-599
> URL: https://issues.apache.org/jira/browse/SCB-599
> Project: Apache ServiceComb
>  Issue Type: Task
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-599) Service registry failed when service before Service Center start

2018-05-21 Thread laijianbin (JIRA)

 [ 
https://issues.apache.org/jira/browse/SCB-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-599.
--
Resolution: Fixed
  Assignee: laijianbin

> Service registry failed when service before Service Center start
> 
>
> Key: SCB-599
> URL: https://issues.apache.org/jira/browse/SCB-599
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-471) vertx upgrade causes use config center push mode error

2018-05-21 Thread laijianbin (JIRA)

[ 
https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483417#comment-16483417
 ] 

laijianbin commented on SCB-471:


I will commit PR as soon as possible

> vertx upgrade causes use config center push mode error 
> ---
>
> Key: SCB-471
> URL: https://issues.apache.org/jira/browse/SCB-471
> Project: Apache ServiceComb
>  Issue Type: Task
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-331) Log optimization

2018-05-21 Thread laijianbin (JIRA)

[ 
https://issues.apache.org/jira/browse/SCB-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483415#comment-16483415
 ] 

laijianbin commented on SCB-331:


I have commited a PR,but liubao think it is no need to modify.So i closed this 
issue

https://github.com/apache/incubator-servicecomb-java-chassis/pull/551

> Log optimization
> 
>
> Key: SCB-331
> URL: https://issues.apache.org/jira/browse/SCB-331
> Project: Apache ServiceComb
>  Issue Type: Task
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.0.0-m1
>
>
> public static DynamicWatchedConfiguration 
> createConfigFromConfigCenter(Configuration localConfiguration) {
>  if (localConfiguration.getProperty(configCenterUrlKey) == null)
> { LOGGER.info("config center URL is missing, skip to load configuration from 
> config center"); return null; }
> changed to
> public static DynamicWatchedConfiguration 
> createConfigFromConfigCenter(Configuration localConfiguration) {
> if (localConfiguration.getProperty(configCenterUrlKey) == null)
> { LOGGER.info("config center URL is not configured"); return null; }
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (SCB-331) Log optimization

2018-05-21 Thread laijianbin (JIRA)

 [ 
https://issues.apache.org/jira/browse/SCB-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin closed SCB-331.
--
Resolution: Fixed

> Log optimization
> 
>
> Key: SCB-331
> URL: https://issues.apache.org/jira/browse/SCB-331
> Project: Apache ServiceComb
>  Issue Type: Task
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
> Fix For: java-chassis-1.0.0-m1
>
>
> public static DynamicWatchedConfiguration 
> createConfigFromConfigCenter(Configuration localConfiguration) {
>  if (localConfiguration.getProperty(configCenterUrlKey) == null)
> { LOGGER.info("config center URL is missing, skip to load configuration from 
> config center"); return null; }
> changed to
> public static DynamicWatchedConfiguration 
> createConfigFromConfigCenter(Configuration localConfiguration) {
> if (localConfiguration.getProperty(configCenterUrlKey) == null)
> { LOGGER.info("config center URL is not configured"); return null; }
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (SCB-599) Service registry failed when service before Service Center start

2018-05-21 Thread laijianbin (JIRA)

 [ 
https://issues.apache.org/jira/browse/SCB-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin updated SCB-599:
---
Summary: Service registry failed when service before Service Center start  
(was: Service registry failed when service before Service Center)

> Service registry failed when service before Service Center start
> 
>
> Key: SCB-599
> URL: https://issues.apache.org/jira/browse/SCB-599
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (SCB-599) Service registry failed when service before Service Center

2018-05-21 Thread laijianbin (JIRA)

[ 
https://issues.apache.org/jira/browse/SCB-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483407#comment-16483407
 ] 

laijianbin commented on SCB-599:


https://github.com/apache/incubator-servicecomb-java-chassis/pull/717

> Service registry failed when service before Service Center
> --
>
> Key: SCB-599
> URL: https://issues.apache.org/jira/browse/SCB-599
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-599) Service registry failed when service before Service Center

2018-05-21 Thread laijianbin (JIRA)
laijianbin created SCB-599:
--

 Summary: Service registry failed when service before Service Center
 Key: SCB-599
 URL: https://issues.apache.org/jira/browse/SCB-599
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-595) Compatible with old SC versions

2018-05-18 Thread laijianbin (JIRA)
laijianbin created SCB-595:
--

 Summary: Compatible with old SC versions
 Key: SCB-595
 URL: https://issues.apache.org/jira/browse/SCB-595
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin


As Framework version use json style like xxx:xxx,but old Service 
Center(eg:2.2.49) is not Compatible



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-471) vertx upgrade causes use config center push mode error

2018-04-10 Thread laijianbin (JIRA)
laijianbin created SCB-471:
--

 Summary: vertx upgrade causes use config center push mode error 
 Key: SCB-471
 URL: https://issues.apache.org/jira/browse/SCB-471
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (SCB-331) Log optimization

2018-02-06 Thread laijianbin (JIRA)

 [ 
https://issues.apache.org/jira/browse/SCB-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin updated SCB-331:
---
Summary: Log optimization  (was: 日志优化)

> Log optimization
> 
>
> Key: SCB-331
> URL: https://issues.apache.org/jira/browse/SCB-331
> Project: Apache ServiceComb
>  Issue Type: Task
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>
> 将public static DynamicWatchedConfiguration 
> createConfigFromConfigCenter(Configuration localConfiguration) {
> if (localConfiguration.getProperty(configCenterUrlKey) == null) {
> LOGGER.info("config center URL is missing, skip to load configuration from 
> config center");
> return null;
> }中的日志进行优化,改成config center URL is not configured



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Created] (SCB-331) 日志优化

2018-02-06 Thread laijianbin (JIRA)
laijianbin created SCB-331:
--

 Summary: 日志优化
 Key: SCB-331
 URL: https://issues.apache.org/jira/browse/SCB-331
 Project: Apache ServiceComb
  Issue Type: Task
Reporter: laijianbin
Assignee: laijianbin


将public static DynamicWatchedConfiguration 
createConfigFromConfigCenter(Configuration localConfiguration) {
if (localConfiguration.getProperty(configCenterUrlKey) == null) {
LOGGER.info("config center URL is missing, skip to load configuration from 
config center");
return null;
}中的日志进行优化,改成config center URL is not configured



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (SCB-297) the local cache is not updated when the server reboots at the situation of accross application

2018-01-25 Thread laijianbin (JIRA)

 [ 
https://issues.apache.org/jira/browse/SCB-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

laijianbin resolved SCB-297.

Resolution: Fixed

https://github.com/apache/incubator-servicecomb-java-chassis/pull/529/files

> the local cache is not updated when the  server reboots at the situation of  
> accross application
> 
>
> Key: SCB-297
> URL: https://issues.apache.org/jira/browse/SCB-297
> Project: Apache ServiceComb
>  Issue Type: Bug
>  Components: Java-Chassis
>Reporter: laijianbin
>Assignee: laijianbin
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)