You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "wujimin (JIRA)" <ji...@apache.org> on 2018/07/18 02:35:00 UTC
[jira] [Updated] (SCB-748) change invocation mechanism from strong
type to weak type
[ https://issues.apache.org/jira/browse/SCB-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
wujimin updated SCB-748:
------------------------
Description:
to support protobuf codec not coupled with business logic, we must create classloader for each microserviceId(app/microservice/version), and create classes in it dynamiclly.
that makes logic very complex, because must support generic and recursive reference.
and in edge, create too many classes, will cause jvm meta area overflow
change invocation mechanism from strong type to weak type
was:
to support protobuf codec not coupled with business logic, we must create classloader for each microserviceId(app/microservice/version), and create classes in it dynamiclly.
that makes logic very complex, because must support generic and recursive reference.
and in edge, create too many classes, will cause jvm meta area overflow
> change invocation mechanism from strong type to weak type
> ---------------------------------------------------------
>
> Key: SCB-748
> URL: https://issues.apache.org/jira/browse/SCB-748
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Java-Chassis
> Reporter: wujimin
> Assignee: wujimin
> Priority: Major
>
> to support protobuf codec not coupled with business logic, we must create classloader for each microserviceId(app/microservice/version), and create classes in it dynamiclly.
> that makes logic very complex, because must support generic and recursive reference.
> and in edge, create too many classes, will cause jvm meta area overflow
> change invocation mechanism from strong type to weak type
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)