LocalRegistry for java-chassis is created only for test purpose and not intended for product use. Is there many scenarios need this? Or we need to reorganize its code to meet product use.
------------------ ???????? ------------------ ??????: "willem.jiang"<[email protected]>; ????????: 2018??7??25??(??????) ????2:22 ??????: "dev"<[email protected]>; ????: Re: Cannot find the instance in ServiceComb Discovery Hi, jimin, Changed the System property fix the issue, but it looks like we have some undocument information need to updated. Willem Jiang Twitter: willemjiang Weibo: ????willem On Wed, Jul 25, 2018 at 11:44 AM, wjm wjm <[email protected]> wrote: > you write a local registry.yaml, but missed some important data > a easy way to fix: do not write the registry.yaml > because you test case is self invoke self, ServiceComb engine can generate > informations dynamiclly > > change: org.apache.servicecomb.saga.discovery.service.center. > ServiceCenterDiscoveryRestTransportTest#setUpLocalRegistry > > private static void setUpLocalRegistry() { > System.setProperty(LOCAL_REGISTRY_FILE_KEY,"notExistJustForceLocal"); > } > > > > 2018-07-24 11:17 GMT+08:00 Willem Jiang <[email protected]>: > > > Hi > > > > When I recovery the old saga code in the SCB-692 branch[1] , I got the > > error when running the ServiceCenterDiscoveryRestTransportTest in the > > ServiceComb Discovery module. > > It looks like the service provide already registered, but the Service > Path > > Manager cannot find the right instance. I tried to debug the code, but > > there are some points those I missed. > > > > You can reproduce the error by checking out the saga code and switch to > > SCB-692 branch. > > > > [1]https://github.com/apache/incubator-servicecomb-saga/tree/SCB-692 > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: ????willem > > >
