[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager; and change consumer default versionRule from latest to all 3.allow consumer schema set or method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 jackson hold classes by a LRU map, will not always hold class, so there is no big problems. 5/6 traced by other issue, close this one. was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager; and change consumer default versionRule from latest to all 3.allow consumer schema set or method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 jackson hold classes by a LRU map, will not always hold class, so there is no big problems. > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager; and change consumer default versionRule > from latest to all > 3.allow consumer schema set or method set bigger than contract > 4.protobuf dynamic class created in microservice classloader > 5.seems that can delete MicroserviceMetaManager > 6.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > > jackson hold classes by a LRU map, will not always hold class, so there is no > big problems. > 5/6 traced by other issue, close this one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager; and change consumer default versionRule from latest to all 3.allow consumer schema set or method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 jackson hold classes by a LRU map, will not always hold class, so there is no big problems. was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer schema set or method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.change consumer default versionRule from latest to all 7.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still hold the classes? > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager; and change consumer default versionRule > from latest to all > 3.allow consumer schema set or method set bigger than contract > 4.protobuf dynamic class created in microservice classloader > 5.seems that can delete MicroserviceMetaManager > 6.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > > jackson hold classes by a LRU map, will not always hold class, so there is no > big problems. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer schema set or method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.change consumer default versionRule from latest to all 7.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still hold the classes? was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer schema set or method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still hold the classes? > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager > 3.allow consumer schema set or method set bigger than contract > 4.protobuf dynamic class created in microservice classloader > 5.seems that can delete MicroserviceMetaManager > 6.change consumer default versionRule from latest to all > 7.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > > how jackson to process same name class but belongs to different classloader, > if classloader unloaded, will jackson still hold the classes? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer schema set or method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still hold the classes? was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still hold the classes? > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager > 3.allow consumer schema set or method set bigger than contract > 4.protobuf dynamic class created in microservice classloader > 5.seems that can delete MicroserviceMetaManager > 6.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > > how jackson to process same name class but belongs to different classloader, > if classloader unloaded, will jackson still hold the classes? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.seems that can delete MicroserviceMetaManager 6.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still hold the classes? was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 6.seems that can delete MicroserviceMetaManager how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still reference the classes? > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager > 3.allow consumer method set bigger than contract > 4.protobuf dynamic class created in microservice classloader > 5.seems that can delete MicroserviceMetaManager > 6.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > > how jackson to process same name class but belongs to different classloader, > if classloader unloaded, will jackson still hold the classes? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer method set bigger than contract 4.protobuf dynamic class created in microservice classloader 5.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 6.seems that can delete MicroserviceMetaManager how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still reference the classes? was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer method set smaller than contract 4.protobuf dynamic class created in microservice classloader 5.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 6.seems that can delete MicroserviceMetaManager how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still reference the classes? > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager > 3.allow consumer method set bigger than contract > 4.protobuf dynamic class created in microservice classloader > 5.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > 6.seems that can delete MicroserviceMetaManager > > how jackson to process same name class but belongs to different classloader, > if classloader unloaded, will jackson still reference the classes? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.allow consumer method set smaller than contract 4.protobuf dynamic class created in microservice classloader 5.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 6.seems that can delete MicroserviceMetaManager how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still reference the classes? was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.protobuf dynamic class created in microservice classloader 4.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 5.seems that can delete MicroserviceMetaManager how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still reference the classes? > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager > 3.allow consumer method set smaller than contract > 4.protobuf dynamic class created in microservice classloader > 5.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > 6.seems that can delete MicroserviceMetaManager > > how jackson to process same name class but belongs to different classloader, > if classloader unloaded, will jackson still reference the classes? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.protobuf dynamic class created in microservice classloader 4.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 5.seems that can delete MicroserviceMetaManager how jackson to process same name class but belongs to different classloader, if classloader unloaded, will jackson still reference the classes? was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.protobuf dynamic class created in microservice classloader 4.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 5.seems that can delete MicroserviceMetaManager > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager > 3.protobuf dynamic class created in microservice classloader > 4.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > 5.seems that can delete MicroserviceMetaManager > > how jackson to process same name class but belongs to different classloader, > if classloader unloaded, will jackson still reference the classes? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-589) allow consumer upgrade before producer
[ https://issues.apache.org/jira/browse/SCB-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-589: Description: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.protobuf dynamic class created in microservice classloader 4.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 5.seems that can delete MicroserviceMetaManager was: 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge 2.consumer microserviceMeta will not save in microserviceMetaManager any more, just like edge, use appManager 3.protobuf dynamic class created in microservice classloader 4.edge remains task should be finished: https://issues.apache.org/jira/browse/SCB-279 > allow consumer upgrade before producer > -- > > Key: SCB-589 > URL: https://issues.apache.org/jira/browse/SCB-589 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > 1.normal consumer use PrivateMicroserviceClassLoaderFactory, just like edge > 2.consumer microserviceMeta will not save in microserviceMetaManager any > more, just like edge, use appManager > 3.protobuf dynamic class created in microservice classloader > 4.edge remains task should be finished: > https://issues.apache.org/jira/browse/SCB-279 > 5.seems that can delete MicroserviceMetaManager -- This message was sent by Atlassian JIRA (v7.6.3#76005)
