[jira] [Resolved] (SCB-1456) Fix the plugin bug that throws some exception when specifying configuration property contractLocation as a file
[ https://issues.apache.org/jira/browse/SCB-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1456. Resolution: Fixed > Fix the plugin bug that throws some exception when specifying configuration > property contractLocation as a file > --- > > Key: SCB-1456 > URL: https://issues.apache.org/jira/browse/SCB-1456 > Project: Apache ServiceComb > Issue Type: Bug > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Fix the plugin bug that throws some exception when specifying configuration > property contractLocation as a file -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1456) Fix the plugin bug that throws some exception when specifying configuration property contractLocation as a file
[ https://issues.apache.org/jira/browse/SCB-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1456. -- > Fix the plugin bug that throws some exception when specifying configuration > property contractLocation as a file > --- > > Key: SCB-1456 > URL: https://issues.apache.org/jira/browse/SCB-1456 > Project: Apache ServiceComb > Issue Type: Bug > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Fix the plugin bug that throws some exception when specifying configuration > property contractLocation as a file -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SCB-1458) add settings for distribution
kakulisen created SCB-1458: -- Summary: add settings for distribution Key: SCB-1458 URL: https://issues.apache.org/jira/browse/SCB-1458 Project: Apache ServiceComb Issue Type: Task Components: toolkit Affects Versions: toolkit-0.1.0 Reporter: kakulisen Assignee: kakulisen Fix For: toolkit-0.1.0 add settings for distribution -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1434) add a springboot2 archetype
[ https://issues.apache.org/jira/browse/SCB-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zibin Lin resolved SCB-1434. Resolution: Fixed > add a springboot2 archetype > --- > > Key: SCB-1434 > URL: https://issues.apache.org/jira/browse/SCB-1434 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: Zibin Lin >Priority: Major > Fix For: java-chassis-1.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > > add a springboot2 archetype to generate a simple project integrated > springboot2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1455) Adjust the directory where the document is generated
[ https://issues.apache.org/jira/browse/SCB-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1455. -- > Adjust the directory where the document is generated > > > Key: SCB-1455 > URL: https://issues.apache.org/jira/browse/SCB-1455 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Adjust the directory where the document is generated -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1455) Adjust the directory where the document is generated
[ https://issues.apache.org/jira/browse/SCB-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1455. Resolution: Fixed > Adjust the directory where the document is generated > > > Key: SCB-1455 > URL: https://issues.apache.org/jira/browse/SCB-1455 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Adjust the directory where the document is generated -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SCB-1457) delete no use code in ProtobufManager
YongLiang Guo created SCB-1457: -- Summary: delete no use code in ProtobufManager Key: SCB-1457 URL: https://issues.apache.org/jira/browse/SCB-1457 Project: Apache ServiceComb Issue Type: Improvement Affects Versions: java-chassis-1.2.1 Reporter: YongLiang Guo Assignee: YongLiang Guo Fix For: java-chassis-1.3.0 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1425) Docs for @SagaEnd annotation
[ https://issues.apache.org/jira/browse/SCB-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Asif Siddiqui updated SCB-1425: Fix Version/s: (was: pack-0.5.0) > Docs for @SagaEnd annotation > > > Key: SCB-1425 > URL: https://issues.apache.org/jira/browse/SCB-1425 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Daniel Qian >Assignee: Daniel Qian >Priority: Minor > Labels: doc > > Provide docs for @SagaEnd -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-668) Using docker-compose file to start Services from docker plugin in the Accept test
[ https://issues.apache.org/jira/browse/SCB-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Asif Siddiqui updated SCB-668: --- Fix Version/s: (was: pack-0.5.0) > Using docker-compose file to start Services from docker plugin in the Accept > test > - > > Key: SCB-668 > URL: https://issues.apache.org/jira/browse/SCB-668 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Daniel Qian >Priority: Major > > Docker maven plugin support to start the service from > [docker-compose|https://dmp.fabric8.io/#docker-compose], which could save us > some time as we can reuse the docker compose file for the Accept test. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SCB-1456) Fix the plugin bug that throws some exception when specifying configuration property contractLocation as a file
kakulisen created SCB-1456: -- Summary: Fix the plugin bug that throws some exception when specifying configuration property contractLocation as a file Key: SCB-1456 URL: https://issues.apache.org/jira/browse/SCB-1456 Project: Apache ServiceComb Issue Type: Bug Components: toolkit Affects Versions: toolkit-0.1.0 Reporter: kakulisen Assignee: kakulisen Fix For: toolkit-0.1.0 Fix the plugin bug that throws some exception when specifying configuration property contractLocation as a file -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SCB-835) Alpha should call the compensation method once it gets the abort event
[ https://issues.apache.org/jira/browse/SCB-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913194#comment-16913194 ] Willem Jiang commented on SCB-835: -- With the state machine implementation, we should implement state machine function for TCC at the same time. > Alpha should call the compensation method once it gets the abort event > -- > > Key: SCB-835 > URL: https://issues.apache.org/jira/browse/SCB-835 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Fix For: pack-0.6.0 > > > It's more straightforward to call the compensation method once Alpha got the > compensation method instead of let the event scanner to do that kind of job. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SCB-668) Using docker-compose file to start Services from docker plugin in the Accept test
[ https://issues.apache.org/jira/browse/SCB-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913182#comment-16913182 ] Daniel Qian commented on SCB-668: - [~njiang] fabric d-m-p related issues are not resolved yet, so nothing could be done for this issue right now. > Using docker-compose file to start Services from docker plugin in the Accept > test > - > > Key: SCB-668 > URL: https://issues.apache.org/jira/browse/SCB-668 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Daniel Qian >Priority: Major > Fix For: pack-0.5.0 > > > Docker maven plugin support to start the service from > [docker-compose|https://dmp.fabric8.io/#docker-compose], which could save us > some time as we can reuse the docker compose file for the Accept test. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1057) check the TxEndedEvent is received before doing the compensate
[ https://issues.apache.org/jira/browse/SCB-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1057: -- Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > check the TxEndedEvent is received before doing the compensate > -- > > Key: SCB-1057 > URL: https://issues.apache.org/jira/browse/SCB-1057 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Hanwen.Huang >Priority: Major > Fix For: pack-0.6.0 > > > if timeout happens during the compensation method executing and the > compensate method was invoked before the compensation method is finished. > compensated failure happened. > like [zhfeng|[https://github.com/zhfeng]] said, the alpha server needs to > check the TxEndedEvent is received before doing the compensate, it's great. > hope it has a better way to solve that. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SCB-1057) check the TxEndedEvent is received before doing the compensate
[ https://issues.apache.org/jira/browse/SCB-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913178#comment-16913178 ] Willem Jiang commented on SCB-1057: --- We need to rethink about the retry implementation this time. It could be better we just fail the transaction if there is a timeout exception from Alpha side. > check the TxEndedEvent is received before doing the compensate > -- > > Key: SCB-1057 > URL: https://issues.apache.org/jira/browse/SCB-1057 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Hanwen.Huang >Priority: Major > Fix For: pack-0.5.0 > > > if timeout happens during the compensation method executing and the > compensate method was invoked before the compensation method is finished. > compensated failure happened. > like [zhfeng|[https://github.com/zhfeng]] said, the alpha server needs to > check the TxEndedEvent is received before doing the compensate, it's great. > hope it has a better way to solve that. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-575) Publish the Java doc of ServiceComb projects
[ https://issues.apache.org/jira/browse/SCB-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-575. -- Resolution: Won't Fix Current we don't release API document to the website. > Publish the Java doc of ServiceComb projects > > > Key: SCB-575 > URL: https://issues.apache.org/jira/browse/SCB-575 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis, Saga >Reporter: Willem Jiang >Assignee: Yang Bo >Priority: Major > Fix For: pack-0.5.0 > > > We should generate the API document and publish it to the website. > * Aggregate the java doc > * Submit the generated pages to ServiceComb website. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (SCB-668) Using docker-compose file to start Services from docker plugin in the Accept test
[ https://issues.apache.org/jira/browse/SCB-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned SCB-668: Assignee: Daniel Qian (was: Gao Xin) > Using docker-compose file to start Services from docker plugin in the Accept > test > - > > Key: SCB-668 > URL: https://issues.apache.org/jira/browse/SCB-668 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Daniel Qian >Priority: Major > Fix For: pack-0.5.0 > > > Docker maven plugin support to start the service from > [docker-compose|https://dmp.fabric8.io/#docker-compose], which could save us > some time as we can reuse the docker compose file for the Accept test. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SCB-668) Using docker-compose file to start Services from docker plugin in the Accept test
[ https://issues.apache.org/jira/browse/SCB-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913173#comment-16913173 ] Willem Jiang commented on SCB-668: -- [~chanjarster] Is there any update of this issue? > Using docker-compose file to start Services from docker plugin in the Accept > test > - > > Key: SCB-668 > URL: https://issues.apache.org/jira/browse/SCB-668 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Gao Xin >Priority: Major > Fix For: pack-0.5.0 > > > Docker maven plugin support to start the service from > [docker-compose|https://dmp.fabric8.io/#docker-compose], which could save us > some time as we can reuse the docker compose file for the Accept test. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1299) Showing the type,createtime in the Saga UI
[ https://issues.apache.org/jira/browse/SCB-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang closed SCB-1299. -- Resolution: Fixed > Showing the type,createtime in the Saga UI > -- > > Key: SCB-1299 > URL: https://issues.apache.org/jira/browse/SCB-1299 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.5.0 > > > It's quite important for the user to know the event type and time when they > are tracing the issue of saga event. > Here is the issue link[1] from the Github. > [1]https://github.com/apache/servicecomb-pack/issues/464 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (SCB-1299) Showing the type,createtime in the Saga UI
[ https://issues.apache.org/jira/browse/SCB-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913170#comment-16913170 ] Lei Zhang commented on SCB-1299: Starting with version 0.5.0 saga-frontend will be replaced by the new web GUI. You can visit https://github.com/apache/servicecomb-pack/blob /master/docs/fsm/fsm_manual_zh.md to learn more > Showing the type,createtime in the Saga UI > -- > > Key: SCB-1299 > URL: https://issues.apache.org/jira/browse/SCB-1299 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.5.0 > > > It's quite important for the user to know the event type and time when they > are tracing the issue of saga event. > Here is the issue link[1] from the Github. > [1]https://github.com/apache/servicecomb-pack/issues/464 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-798) GrpcMessageSender uses aync send API
[ https://issues.apache.org/jira/browse/SCB-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-798: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > GrpcMessageSender uses aync send API > > > Key: SCB-798 > URL: https://issues.apache.org/jira/browse/SCB-798 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Major > Fix For: pack-0.6.0 > > > We could leverage aync sending API to increase the performance Pack system. > Omega need to support the transaction status lookup incase the message is not > sent rightly. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1011) Saga interceptor should check the gloable transaction ID
[ https://issues.apache.org/jira/browse/SCB-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1011: -- Labels: easy-fix (was: ) > Saga interceptor should check the gloable transaction ID > > > Key: SCB-1011 > URL: https://issues.apache.org/jira/browse/SCB-1011 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Labels: easy-fix > Fix For: pack-0.6.0 > > > The interceptor should check if the transaction ID is set before send the > event to the alpha server. In this way we could help user find out if he > setup the distributed transaction rightly. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-835) Alpha should call the compensation method once it gets the abort event
[ https://issues.apache.org/jira/browse/SCB-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-835: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > Alpha should call the compensation method once it gets the abort event > -- > > Key: SCB-835 > URL: https://issues.apache.org/jira/browse/SCB-835 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Fix For: pack-0.6.0 > > > It's more straightforward to call the compensation method once Alpha got the > compensation method instead of let the event scanner to do that kind of job. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1011) Saga interceptor should check the gloable transaction ID
[ https://issues.apache.org/jira/browse/SCB-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1011: -- Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > Saga interceptor should check the gloable transaction ID > > > Key: SCB-1011 > URL: https://issues.apache.org/jira/browse/SCB-1011 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Fix For: pack-0.6.0 > > > The interceptor should check if the transaction ID is set before send the > event to the alpha server. In this way we could help user find out if he > setup the distributed transaction rightly. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1026) Saga compensation should support to define the retry times
[ https://issues.apache.org/jira/browse/SCB-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-1026. --- Resolution: Won't Fix Retry could introduce some other issue, so I close this issue with Won't Fix. > Saga compensation should support to define the retry times > -- > > Key: SCB-1026 > URL: https://issues.apache.org/jira/browse/SCB-1026 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Willem Jiang >Priority: Major > Fix For: pack-0.5.0 > > > We should let use chose the retry times of Saga compensation. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1107) Omega should send the compensation failure to alpha
[
https://issues.apache.org/jira/browse/SCB-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated SCB-1107:
--
Fix Version/s: (was: pack-0.5.0)
pack-0.6.0
> Omega should send the compensation failure to alpha
> ---
>
> Key: SCB-1107
> URL: https://issues.apache.org/jira/browse/SCB-1107
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Saga
>Reporter: Willem Jiang
>Priority: Major
> Fix For: pack-0.6.0
>
>
> When the Omega call the compensation method fail, Omega should let Alpha know
> about it.
> In the file of
> https://github.com/apache/servicecomb-pack/blob/master/omega/omega-context/src/main/java/org/apache/servicecomb/pack/omega/context/CallbackContext.java
> {code}
> } catch (IllegalAccessException | InvocationTargetException e) {
> LOG.error(
> "Pre-checking for callback method " +
> contextInternal.callbackMethod.toString()
> + " was somehow skipped, did you forget to configure callback
> method checking on service startup?",
> e);
> }
> {code}
> Omega just catches the invocation exception to avoid Alpha sending out the
> compensation command again, but we need to update the compensation method
> status, to let Alpha know if the compensation method is invoked rightly.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Assigned] (SCB-1299) Showing the type,createtime in the Saga UI
[ https://issues.apache.org/jira/browse/SCB-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned SCB-1299: - Assignee: Lei Zhang > Showing the type,createtime in the Saga UI > -- > > Key: SCB-1299 > URL: https://issues.apache.org/jira/browse/SCB-1299 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.5.0 > > > It's quite important for the user to know the event type and time when they > are tracing the issue of saga event. > Here is the issue link[1] from the Github. > [1]https://github.com/apache/servicecomb-pack/issues/464 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-896) Split saga transaction event into hot and cold
[ https://issues.apache.org/jira/browse/SCB-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-896: - Fix Version/s: (was: pack-0.5.0) > Split saga transaction event into hot and cold > -- > > Key: SCB-896 > URL: https://issues.apache.org/jira/browse/SCB-896 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: cherrylzhao >Assignee: cherrylzhao >Priority: Major > > split saga transaction event into hot and cold. > - transaction event table. (Hot) > storage txEvent receiving from omega directly. > - transaction finished table.(cold) > When receiving global transaction end instruction. > - if there does’t exist compensation, > move related transaction record to finish table asynchronous. > - if need compensation, when receiving compensation finished command > from omega, >move the related event to finished table asynchronous. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-908) TCC Events restful API
[ https://issues.apache.org/jira/browse/SCB-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-908: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > TCC Events restful API > --- > > Key: SCB-908 > URL: https://issues.apache.org/jira/browse/SCB-908 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: cherrylzhao >Assignee: Mohammad Asif Siddiqui >Priority: Major > Fix For: pack-0.6.0 > > > For TCC workflow, we need provide a rest interface to fetch transaction > status. > user can do manual recovery based on this information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-558) Introduce Retry event to simplify the Scanner work
[ https://issues.apache.org/jira/browse/SCB-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-558: - Fix Version/s: (was: pack-0.5.0) > Introduce Retry event to simplify the Scanner work > -- > > Key: SCB-558 > URL: https://issues.apache.org/jira/browse/SCB-558 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Major > > Current Alpha need spent lots of effort to find out the transaction which is > aborted when we introduce the retry. It could be more easy for us to verify > it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-301) [pack] acceptance tests of transaction timeout and retry failed
[ https://issues.apache.org/jira/browse/SCB-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-301: - Fix Version/s: (was: pack-0.5.0) > [pack] acceptance tests of transaction timeout and retry failed > --- > > Key: SCB-301 > URL: https://issues.apache.org/jira/browse/SCB-301 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Yin Xiang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-303) [pack] acceptance tests of alpha cluster down and recovery
[ https://issues.apache.org/jira/browse/SCB-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-303: - Fix Version/s: (was: pack-0.5.0) > [pack] acceptance tests of alpha cluster down and recovery > -- > > Key: SCB-303 > URL: https://issues.apache.org/jira/browse/SCB-303 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Yin Xiang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-302) [pack] acceptance tests of one alpha in cluster of three down
[ https://issues.apache.org/jira/browse/SCB-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-302: - Fix Version/s: (was: pack-0.5.0) > [pack] acceptance tests of one alpha in cluster of three down > - > > Key: SCB-302 > URL: https://issues.apache.org/jira/browse/SCB-302 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Yin Xiang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-277) [pack] concurrent event processing issue
[ https://issues.apache.org/jira/browse/SCB-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-277: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > [pack] concurrent event processing issue > > > Key: SCB-277 > URL: https://issues.apache.org/jira/browse/SCB-277 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Minor > Fix For: pack-0.6.0 > > > currently, when alpha is down, it starts from the first event till the last > on restart. > multiple alphas may process the same event at the same time, which results in > concurrent update errors when persisting events as commands. it may not > affect correctness, but does leave warning logs. > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-990) Support to lookup the Omega instance if the original instance is not exit
[ https://issues.apache.org/jira/browse/SCB-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-990: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > Support to lookup the Omega instance if the original instance is not exit > - > > Key: SCB-990 > URL: https://issues.apache.org/jira/browse/SCB-990 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Labels: easyfix > Fix For: pack-0.6.0 > > > Current we just look up the instance of Service which is start the > transaction, if the service is stateless , we could support to invoke the > other service instance in case of the original instance is out of service. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1003) Support the transaction suspend and resume
[ https://issues.apache.org/jira/browse/SCB-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1003: -- Fix Version/s: pack-0.6.0 > Support the transaction suspend and resume > -- > > Key: SCB-1003 > URL: https://issues.apache.org/jira/browse/SCB-1003 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Labels: improvement, pack > Fix For: pack-0.6.0 > > > We may need to provide the API in the Omega to support the transaction > suspend and resume to let the user control the whole transaction process. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1004) Alpha has limit request rate protection
[ https://issues.apache.org/jira/browse/SCB-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1004: -- Labels: easy-fix improvement pack (was: improvement pack) > Alpha has limit request rate protection > --- > > Key: SCB-1004 > URL: https://issues.apache.org/jira/browse/SCB-1004 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Labels: easy-fix, improvement, pack > Fix For: pack-0.6.0 > > > It's important to avoid the Omega request flood by using the limit request > rate protection, if we provide the Alpha service online. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1004) Alpha has limit request rate protection
[ https://issues.apache.org/jira/browse/SCB-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1004: -- Fix Version/s: pack-0.6.0 > Alpha has limit request rate protection > --- > > Key: SCB-1004 > URL: https://issues.apache.org/jira/browse/SCB-1004 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Labels: improvement, pack > Fix For: pack-0.6.0 > > > It's important to avoid the Omega request flood by using the limit request > rate protection, if we provide the Alpha service online. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1005) HA solution of the Alpha EventScanner
[ https://issues.apache.org/jira/browse/SCB-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-1005. --- Resolution: Won't Fix Since Pack 0.4.0, we already support cluster out of box. > HA solution of the Alpha EventScanner > -- > > Key: SCB-1005 > URL: https://issues.apache.org/jira/browse/SCB-1005 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > > We can only start one Alpha EventScanner in the backend, which means we > cannot start multiple EventScanner in the cluster mode. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1006) Support SagaEnd Callback invocation
[
https://issues.apache.org/jira/browse/SCB-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated SCB-1006:
--
Fix Version/s: pack-0.6.0
> Support SagaEnd Callback invocation
> ---
>
> Key: SCB-1006
> URL: https://issues.apache.org/jira/browse/SCB-1006
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Saga
>Reporter: Willem Jiang
>Priority: Major
> Labels: improvement, pack
> Fix For: pack-0.6.0
>
>
> Here is the use case for using the lock to provide the isolation in Saga.
> We just want to release this lock after the saga invocation is finished. Here
> is the code snippet for it. method2 wraps the Saga event to release the
> lock.
> {code}
> @SagaStart
> void doSagaTx() {
>doLocalTx1();
>doLocalTx1();
> }
> @Compensable(timeout=5, compensationMethod="cancelLocalTx1")
> void doLocalTx1(){
>...
> }
> void cancelLocalTx1(){
>
> }
> @Compensable(timeout=5, compensationMethod="cancelLocalTx2")
> void doLocalTx2(){
>...
> }
> void cancelLocalTx2(){
>
> }
> void method2() {
>Lock resourceLock = getResourceLock();
>if (resourceLock.tryLock()) {
> try {
> doSagaTx();
> } finally {
> resourceLock.release();
> }
>} else {
> // Resource was locked
>}
> }
> {code}
> But, this method is not good enough, as if there are something wrong inside
> of the Saga transaction, we need to wait for a while to let the transaction
> coordinator to finish the compensation invocation before release the
> resource lock.
> If ServiceComb saga can provide a callback when the saga transaction is
> finished, it could save lots of my time. The code just like this.
> {code}
> @SagaStart(endMethod="sagaTxEnd")
> void doSagaTx(resourceLock) {
>doLocalTx1();
>doLocalTx1();
> }
> void sagaTxEnd(resourceLock){
>resourceLock.release();
> }
> @Compensable(timeout=5, compensationMethod="cancelLocalTx1")
> void doLocalTx1(){
>...
> }
> void cancelLocalTx1(){
>
> }
> @Compensable(timeout=5, compensationMethod="cancelLocalTx2")
> void doLocalTx2(){
>...
> }
> void cancelLocalTx2(){
>
> }
> void method2() {
>Lock resourceLock = getResourceLock();
>if (resourceLock.tryLock()) {
> doSagaTx(resourceLock);
>} else {
> // Resource was locked
>}
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (SCB-1203) Occasional failure TccLoadBalanceSenderTest.participateFailedThenRetry
[
https://issues.apache.org/jira/browse/SCB-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated SCB-1203:
--
Fix Version/s: pack-0.6.0
> Occasional failure TccLoadBalanceSenderTest.participateFailedThenRetry
> --
>
> Key: SCB-1203
> URL: https://issues.apache.org/jira/browse/SCB-1203
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Reporter: Willem Jiang
>Priority: Major
> Fix For: pack-0.6.0
>
>
> Here is an issue from Github.
> https://github.com/apache/servicecomb-pack/issues/430
> alpha server 0.4.0 master
> Use mvn clean install -Pdemo,spring-boot-2
> error log
> {code}
> ---
> T E S T S
> ---
> Running
> org.apache.servicecomb.pack.omega.connector.grpc.tcc.GrpcTccClientMessageSenderTest
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.594 sec -
> in
> org.apache.servicecomb.pack.omega.connector.grpc.tcc.GrpcTccClientMessageSenderTest
> Running
> org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.391 sec
> <<< FAILURE! - in
> org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest
> participateFailedThenRetry(org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest)
> Time elapsed: 2.388 sec <<< FAILURE!
> java.lang.AssertionError:
> Expected: is <3>
> but: was <4>
> at
> org.apache.servicecomb.pack.omega.connector.grpc.tcc.TccLoadBalanceSenderTest.participateFailedThenRetry(TccLoadBalanceSenderTest.java:213)
> Running
> org.apache.servicecomb.pack.omega.connector.grpc.LoadBalanceContextBuilderTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.115 sec -
> in
> org.apache.servicecomb.pack.omega.connector.grpc.LoadBalanceContextBuilderTest
> Running
> org.apache.servicecomb.pack.omega.connector.grpc.PushBackReconnectRunnableTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec -
> in
> org.apache.servicecomb.pack.omega.connector.grpc.PushBackReconnectRunnableTest
> Running
> org.apache.servicecomb.pack.omega.connector.grpc.saga.RetryableMessageSenderTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec -
> in
> org.apache.servicecomb.pack.omega.connector.grpc.saga.RetryableMessageSenderTest
> Running
> org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalanceSenderWithTLSTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.579 sec -
> in
> org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalanceSenderWithTLSTest
> Running
> org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest
> Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.497 sec -
> in
> org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest
> Results :
> Failed tests:
> TccLoadBalanceSenderTest.participateFailedThenRetry:213
> Expected: is <3>
> but: was <4>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (SCB-1223) Prepare 0.4.0 servicecomb pack release
[ https://issues.apache.org/jira/browse/SCB-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-1223. --- Resolution: Fixed > Prepare 0.4.0 servicecomb pack release > -- > > Key: SCB-1223 > URL: https://issues.apache.org/jira/browse/SCB-1223 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Mohammad Asif Siddiqui >Assignee: Mohammad Asif Siddiqui >Priority: Major > Fix For: pack-0.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1223) Prepare 0.4.0 servicecomb pack release
[ https://issues.apache.org/jira/browse/SCB-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1223: -- Fix Version/s: pack-0.4.0 > Prepare 0.4.0 servicecomb pack release > -- > > Key: SCB-1223 > URL: https://issues.apache.org/jira/browse/SCB-1223 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Mohammad Asif Siddiqui >Assignee: Mohammad Asif Siddiqui >Priority: Major > Fix For: pack-0.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1282) Support to inject a customer IdGenerator in Omega Spring Starter
[ https://issues.apache.org/jira/browse/SCB-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1282: -- Labels: easyfix (was: ) > Support to inject a customer IdGenerator in Omega Spring Starter > > > Key: SCB-1282 > URL: https://issues.apache.org/jira/browse/SCB-1282 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Reporter: Willem Jiang >Priority: Major > Labels: easyfix > Fix For: pack-0.6.0 > > > User may want to implement it's own transaction id system himself, we should > support it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1282) Support to inject a customer IdGenerator in Omega Spring Starter
[ https://issues.apache.org/jira/browse/SCB-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1282: -- Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > Support to inject a customer IdGenerator in Omega Spring Starter > > > Key: SCB-1282 > URL: https://issues.apache.org/jira/browse/SCB-1282 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Reporter: Willem Jiang >Priority: Major > Fix For: pack-0.6.0 > > > User may want to implement it's own transaction id system himself, we should > support it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (SCB-1298) Add Zookeeper as the Alpha server load balancer
[ https://issues.apache.org/jira/browse/SCB-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned SCB-1298: - Assignee: cmonkey > Add Zookeeper as the Alpha server load balancer > > > Key: SCB-1298 > URL: https://issues.apache.org/jira/browse/SCB-1298 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Willem Jiang >Assignee: cmonkey >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. Adding the zooker starter on the Alpha side > 2. Adding the zooker starter on the Omega side > 3. Adding the accept test -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1298) Add Zookeeper as the Alpha server load balancer
[ https://issues.apache.org/jira/browse/SCB-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-1298. --- Resolution: Fixed > Add Zookeeper as the Alpha server load balancer > > > Key: SCB-1298 > URL: https://issues.apache.org/jira/browse/SCB-1298 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Willem Jiang >Assignee: cmonkey >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. Adding the zooker starter on the Alpha side > 2. Adding the zooker starter on the Omega side > 3. Adding the accept test -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1299) Showing the type,createtime in the Saga UI
[ https://issues.apache.org/jira/browse/SCB-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1299: -- Fix Version/s: pack-0.5.0 > Showing the type,createtime in the Saga UI > -- > > Key: SCB-1299 > URL: https://issues.apache.org/jira/browse/SCB-1299 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Fix For: pack-0.5.0 > > > It's quite important for the user to know the event type and time when they > are tracing the issue of saga event. > Here is the issue link[1] from the Github. > [1]https://github.com/apache/servicecomb-pack/issues/464 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1300) Added the accept test of retry then recovery
[ https://issues.apache.org/jira/browse/SCB-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1300: -- Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > Added the accept test of retry then recovery > - > > Key: SCB-1300 > URL: https://issues.apache.org/jira/browse/SCB-1300 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Willem Jiang >Priority: Major > Fix For: pack-0.6.0 > > > Current we don't have the retry failed and recovery test senoria in the > accept test, we should add one. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1425) Docs for @SagaEnd annotation
[ https://issues.apache.org/jira/browse/SCB-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1425: -- Affects Version/s: (was: pack-0.5.0) > Docs for @SagaEnd annotation > > > Key: SCB-1425 > URL: https://issues.apache.org/jira/browse/SCB-1425 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Daniel Qian >Assignee: Daniel Qian >Priority: Minor > Labels: doc > > Provide docs for @SagaEnd -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1425) Docs for @SagaEnd annotation
[ https://issues.apache.org/jira/browse/SCB-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1425: -- Fix Version/s: pack-0.5.0 > Docs for @SagaEnd annotation > > > Key: SCB-1425 > URL: https://issues.apache.org/jira/browse/SCB-1425 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Daniel Qian >Assignee: Daniel Qian >Priority: Minor > Labels: doc > Fix For: pack-0.5.0 > > > Provide docs for @SagaEnd -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-275) [pack] retry compensation on failure/timeout/crash
[ https://issues.apache.org/jira/browse/SCB-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-275: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > [pack] retry compensation on failure/timeout/crash > -- > > Key: SCB-275 > URL: https://issues.apache.org/jira/browse/SCB-275 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > Fix For: pack-0.6.0 > > > when omega is unreachable, we may not receive TxCompensatedEvent. > in such case, we have to ask omega to retry on timeout or on omega > disconnected (alpha needs some mechanism to detect connection disruption). -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-268) [pack] compact events to remove unnecessary fields
[ https://issues.apache.org/jira/browse/SCB-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-268: - Fix Version/s: (was: pack-0.5.0) pack-0.6.0 > [pack] compact events to remove unnecessary fields > -- > > Key: SCB-268 > URL: https://issues.apache.org/jira/browse/SCB-268 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Assignee: Willem Jiang >Priority: Major > Fix For: pack-0.6.0 > > > only TxStartedEvent needs to contain all tx information. > Asking other events to provide info such as payloads, compensationMethod, > parentTxId, etc. is not necessary. > > compacting events not only reduces network load and null/duplicate data in > database -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-241) [pack] visualize transaction status in alpha
[ https://issues.apache.org/jira/browse/SCB-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-241. -- Resolution: Fixed We have UI for saga transaction. > [pack] visualize transaction status in alpha > > > Key: SCB-241 > URL: https://issues.apache.org/jira/browse/SCB-241 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > > as a user, I want to see real time transaction status and query history > transaction status to better analysis the whole system. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-241) [pack] visualize transaction status in alpha
[ https://issues.apache.org/jira/browse/SCB-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-241: - Fix Version/s: (was: pack-0.5.0) > [pack] visualize transaction status in alpha > > > Key: SCB-241 > URL: https://issues.apache.org/jira/browse/SCB-241 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > > as a user, I want to see real time transaction status and query history > transaction status to better analysis the whole system. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-240) [pack] performance impacts test
[ https://issues.apache.org/jira/browse/SCB-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-240: - Fix Version/s: (was: pack-0.5.0) > [pack] performance impacts test > --- > > Key: SCB-240 > URL: https://issues.apache.org/jira/browse/SCB-240 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Priority: Major > > as a user, I want to know how much performance loss if I introduce pack as my > transaction consistency solution. > We need to deploy the application (which has multiple micro services) and > start a client to send the request to the application. > 1. Running the application without Omega enabled. > 2. Running the application with Omega enabled (without inject the error) > 3. Running the application with Omega enabled (with some failed transactions) > > In Pack mode, every transaction's call could generate events from Omega to > Alpha. > We may need to collect the calling information to optimize to performance. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-170) [pack] separate serialization from grpc to reuse the same stream
[ https://issues.apache.org/jira/browse/SCB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-170: - Fix Version/s: (was: pack-0.5.0) > [pack] separate serialization from grpc to reuse the same stream > > > Key: SCB-170 > URL: https://issues.apache.org/jira/browse/SCB-170 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Yin Xiang >Priority: Major > > currently, messaging protocol, serialization, and transportation are all done > with grpc/protobuf. > doing so makes sharing a single stream among different messages hard to do. > a better way is to separate serialization from grpc. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (SCB-1455) Adjust the directory where the document is generated
kakulisen created SCB-1455: -- Summary: Adjust the directory where the document is generated Key: SCB-1455 URL: https://issues.apache.org/jira/browse/SCB-1455 Project: Apache ServiceComb Issue Type: Task Components: toolkit Affects Versions: toolkit-0.1.0 Reporter: kakulisen Assignee: kakulisen Fix For: toolkit-0.1.0 Adjust the directory where the document is generated -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-19) request json generator
[ https://issues.apache.org/jira/browse/SCB-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-19: Fix Version/s: (was: pack-0.5.0) > request json generator > -- > > Key: SCB-19 > URL: https://issues.apache.org/jira/browse/SCB-19 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > > as a user, i want to generate saga request json by dragging and dropping > services on GUI, so that i can minimize the manual coding myself and avoid > human error -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-18) stateful service support
[ https://issues.apache.org/jira/browse/SCB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-18: Fix Version/s: (was: pack-0.5.0) > stateful service support > > > Key: SCB-18 > URL: https://issues.apache.org/jira/browse/SCB-18 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Priority: Major > > currently saga sub-transactions are load balanced to multiple service > instances with service discovery, but it doesn't work well with stateful > service. > stateful service support can either be supported with service registry or > caching request address in saga -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1123) Provide a implementation of the Long Running Action specification
[ https://issues.apache.org/jira/browse/SCB-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1123: -- Fix Version/s: (was: pack-0.5.0) > Provide a implementation of the Long Running Action specification > - > > Key: SCB-1123 > URL: https://issues.apache.org/jira/browse/SCB-1123 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Zheng Feng >Assignee: Mohammad Asif Siddiqui >Priority: Major > Labels: GSoC2019, gsoc2019 > > The LRA spec [1] is the saga based solution for the micro services and it > will be released with the MicroProfile. So it could be useful to provide a > implementation of this spec. > Note, currently the LRA coordinator has to expose the JAX-RS interface. > [1] > https://github.com/eclipse/microprofile-lra/blob/master/spec/src/main/asciidoc/microprofile-lra-spec.adoc -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-14) transaction tracing with zipkin
[ https://issues.apache.org/jira/browse/SCB-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-14: Fix Version/s: (was: pack-0.5.0) > transaction tracing with zipkin > --- > > Key: SCB-14 > URL: https://issues.apache.org/jira/browse/SCB-14 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Assignee: Willem Jiang >Priority: Major > > integration with zipkin to providing timing info of transactions/compensations > *given* > configured saga with zipkin trace collector address and zipkin enabled > *when* > saga receives a request > *then* > tracing info is reported to zipkin trace collector -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1360) the issue of verifying contract file is not correct
[ https://issues.apache.org/jira/browse/SCB-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1360. Fix Version/s: toolkit-0.1.0 Resolution: Fixed > the issue of verifying contract file is not correct > --- > > Key: SCB-1360 > URL: https://issues.apache.org/jira/browse/SCB-1360 > Project: Apache ServiceComb > Issue Type: Bug > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > > Configured in \servicecomb-java-chassis\samples\bmi project: > > ./contracts > ./sourceContracts > > and modify one letter in contract file in ./contracts directory. > Command: mvn toolkit:verifyContracts > Result with something wrong:the result show that the contract file is the > same. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1358) the issue of invalid naming of generated contract files
[ https://issues.apache.org/jira/browse/SCB-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1358. Fix Version/s: toolkit-0.1.0 Resolution: Fixed > the issue of invalid naming of generated contract files > --- > > Key: SCB-1358 > URL: https://issues.apache.org/jira/browse/SCB-1358 > Project: Apache ServiceComb > Issue Type: Bug > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > > Configured in \servicecomb-java-chassis\samples\bmi project: > > ./contracts > > Command: mvn toolkit:generateContracts > Result with something wrong:generate contract file naming > CalculatorRestEndpointyaml -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1359) the issue of generating document failure
[ https://issues.apache.org/jira/browse/SCB-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1359. Fix Version/s: toolkit-0.1.0 Resolution: Fixed > the issue of generating document failure > > > Key: SCB-1359 > URL: https://issues.apache.org/jira/browse/SCB-1359 > Project: Apache ServiceComb > Issue Type: Bug > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > > Configured in \servicecomb-java-chassis\samples\bmi project: > > ./contracts > ./documents > swagger-ui > > Command: mvn toolkit:generateDoc > Result with something wrong: > [ERROR] Failed to execute goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > (default-cli) on project bmi: Execution default-cli of goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > failed.: NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > (default-cli) on project bmi: Execution default-cli of goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-cli of goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 20 more > Caused by: java.lang.NullPointerException > at > org.apache.servicecomb.toolkit.plugin.GenerateContractsDocMojo$1.visitFile(GenerateContractsDocMojo.java:80) > at > org.apache.servicecomb.toolkit.plugin.GenerateContractsDocMojo$1.visitFile(GenerateContractsDocMojo.java:70) > at java.nio.file.Files.walkFileTree(Files.java:2670) > at java.nio.file.Files.walkFileTree(Files.java:2742) > at > org.apache.servicecomb.toolkit.plugin.GenerateContractsDocMojo.execute(GenerateContractsDocMojo.java:70) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > ... 21 more > [ERROR] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1361) optimize toolkit user experience
[ https://issues.apache.org/jira/browse/SCB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1361. Fix Version/s: toolkit-0.1.0 Resolution: Fixed > optimize toolkit user experience > - > > Key: SCB-1361 > URL: https://issues.apache.org/jira/browse/SCB-1361 > Project: Apache ServiceComb > Issue Type: Bug > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > > some parameters of toolkit-maven-plugin are not easy to understand,eg. > > ./contracts > ./documents > swagger-ui > > outputDir,format,docOutputDir and so on,they should be optimized. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1351) Some issues about using toolkit plugin
[ https://issues.apache.org/jira/browse/SCB-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1351. Fix Version/s: toolkit-0.1.0 Resolution: Fixed > Some issues about using toolkit plugin > -- > > Key: SCB-1351 > URL: https://issues.apache.org/jira/browse/SCB-1351 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > use toolkit plugin to generate contract file,document and verify contract > from myself sample,find some error as below, > 1.the generated contract file is incorrect,it has no sufix name. > 2.generate document from contract file, > [ERROR] Failed to execute goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > (default-cli) on project bmi: Execution default-cli of goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > failed.: NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > (default-cli) on project bmi: Execution default-cli of goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > failed. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:191) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-cli of goal > org.apache.servicecomb.toolkit:toolkit-maven-plugin:0.1.0-SNAPSHOT:generateDoc > failed. > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 20 more > Caused by: java.lang.NullPointerException > at > org.apache.servicecomb.toolkit.plugin.GenerateContractsDocMojo$1.visitFile(GenerateContractsDocMojo.java:80) > at > org.apache.servicecomb.toolkit.plugin.GenerateContractsDocMojo$1.visitFile(GenerateContractsDocMojo.java:70) > at java.nio.file.Files.walkFileTree(Files.java:2670) > at java.nio.file.Files.walkFileTree(Files.java:2742) > at > org.apache.servicecomb.toolkit.plugin.GenerateContractsDocMojo.execute(GenerateContractsDocMojo.java:70) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > ... 21 more > [ERROR] > 3.the report of contract verification is not correct.It does not correctly > distinguish between different letter contract files. > 4.some parameters of toolkit-maven-plugin are not easy to understand,eg > outputDir,format,docOutputDir and so on,they should be optimized. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1384) refact the code to optimize user experience
[ https://issues.apache.org/jira/browse/SCB-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1384. Fix Version/s: toolkit-0.1.0 Resolution: Fixed > refact the code to optimize user experience > --- > > Key: SCB-1384 > URL: https://issues.apache.org/jira/browse/SCB-1384 > Project: Apache ServiceComb > Issue Type: Improvement > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Integrate the function of generating contracts and generating documents into > a single function, and streamline and optimize user configuration items. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1383) support toolkit maven plugin commands that generating code
[ https://issues.apache.org/jira/browse/SCB-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1383. Fix Version/s: toolkit-0.1.0 Resolution: Fixed done > support toolkit maven plugin commands that generating code > -- > > Key: SCB-1383 > URL: https://issues.apache.org/jira/browse/SCB-1383 > Project: Apache ServiceComb > Issue Type: Improvement > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > support toolkit maven plugin commands that generating code -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1400) Complement and improve unit test
[ https://issues.apache.org/jira/browse/SCB-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1400. Fix Version/s: toolkit-0.1.0 Resolution: Fixed done > Complement and improve unit test > > > Key: SCB-1400 > URL: https://issues.apache.org/jira/browse/SCB-1400 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Minor > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1412) some redudent folder generated after running test
[ https://issues.apache.org/jira/browse/SCB-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1412. Fix Version/s: toolkit-0.1.0 Resolution: Fixed done > some redudent folder generated after running test > - > > Key: SCB-1412 > URL: https://issues.apache.org/jira/browse/SCB-1412 > Project: Apache ServiceComb > Issue Type: Bug > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 1h > Remaining Estimate: 0h > > run with command: mvn clean install > result: redundent folder which is named "null" was generated in > toolkit-maven-plugin directory -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1428) Improve toolkit-maven-plugin test to make it running is not dependent by maven plugin
[ https://issues.apache.org/jira/browse/SCB-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1428. Resolution: Fixed done > Improve toolkit-maven-plugin test to make it running is not dependent by > maven plugin > - > > Key: SCB-1428 > URL: https://issues.apache.org/jira/browse/SCB-1428 > Project: Apache ServiceComb > Issue Type: Improvement > Components: toolkit >Reporter: mabin >Assignee: mabin >Priority: Minor > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1444) support to generate mutiple modules in the same project
[ https://issues.apache.org/jira/browse/SCB-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mabin resolved SCB-1444. Fix Version/s: toolkit-0.1.0 Resolution: Fixed done > support to generate mutiple modules in the same project > --- > > Key: SCB-1444 > URL: https://issues.apache.org/jira/browse/SCB-1444 > Project: Apache ServiceComb > Issue Type: Improvement > Components: toolkit >Reporter: mabin >Assignee: mabin >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1426) Support for configuring the toolkit maven plugin in the parent pom
[ https://issues.apache.org/jira/browse/SCB-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1426. Resolution: Fixed Completed and merged, see https://github.com/apache/servicecomb-toolkit/pull/14 > Support for configuring the toolkit maven plugin in the parent pom > -- > > Key: SCB-1426 > URL: https://issues.apache.org/jira/browse/SCB-1426 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > > Support for configuring the toolkit maven plugin in the parent pom -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1426) Support for configuring the toolkit maven plugin in the parent pom
[ https://issues.apache.org/jira/browse/SCB-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1426. -- > Support for configuring the toolkit maven plugin in the parent pom > -- > > Key: SCB-1426 > URL: https://issues.apache.org/jira/browse/SCB-1426 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > > Support for configuring the toolkit maven plugin in the parent pom -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1422) optimize classmaker
[ https://issues.apache.org/jira/browse/SCB-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1422. Resolution: Fixed > optimize classmaker > --- > > Key: SCB-1422 > URL: https://issues.apache.org/jira/browse/SCB-1422 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > print the error of the command execution and add the unit test for the > ClassMaker -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1422) optimize classmaker
[ https://issues.apache.org/jira/browse/SCB-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1422. -- > optimize classmaker > --- > > Key: SCB-1422 > URL: https://issues.apache.org/jira/browse/SCB-1422 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > print the error of the command execution and add the unit test for the > ClassMaker -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (SCB-1422) optimize classmaker
[ https://issues.apache.org/jira/browse/SCB-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen reassigned SCB-1422: -- Assignee: kakulisen > optimize classmaker > --- > > Key: SCB-1422 > URL: https://issues.apache.org/jira/browse/SCB-1422 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > print the error of the command execution and add the unit test for the > ClassMaker -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1363) update licenses and notice
[ https://issues.apache.org/jira/browse/SCB-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1363. -- > update licenses and notice > -- > > Key: SCB-1363 > URL: https://issues.apache.org/jira/browse/SCB-1363 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 1. There are some third part license which not currently used in our binary > release, we should not include them into our binary release. > 2. Support to add the license file into the packaged jar -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (SCB-1426) Support for configuring the toolkit maven plugin in the parent pom
[ https://issues.apache.org/jira/browse/SCB-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen reassigned SCB-1426: -- Assignee: kakulisen > Support for configuring the toolkit maven plugin in the parent pom > -- > > Key: SCB-1426 > URL: https://issues.apache.org/jira/browse/SCB-1426 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > > Support for configuring the toolkit maven plugin in the parent pom -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1363) update licenses and notice
[ https://issues.apache.org/jira/browse/SCB-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1363. Resolution: Fixed > update licenses and notice > -- > > Key: SCB-1363 > URL: https://issues.apache.org/jira/browse/SCB-1363 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 1. There are some third part license which not currently used in our binary > release, we should not include them into our binary release. > 2. Support to add the license file into the packaged jar -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1433) Remove unit test for constant
[ https://issues.apache.org/jira/browse/SCB-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1433. Resolution: Fixed > Remove unit test for constant > - > > Key: SCB-1433 > URL: https://issues.apache.org/jira/browse/SCB-1433 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > remove unit test for constant -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1433) Remove unit test for constant
[ https://issues.apache.org/jira/browse/SCB-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1433. -- > Remove unit test for constant > - > > Key: SCB-1433 > URL: https://issues.apache.org/jira/browse/SCB-1433 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > remove unit test for constant -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1436) Model is not generated, but the related package is imported
[ https://issues.apache.org/jira/browse/SCB-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1436. -- > Model is not generated, but the related package is imported > --- > > Key: SCB-1436 > URL: https://issues.apache.org/jira/browse/SCB-1436 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Model is not generated, but the related package is imported -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1371) Support for query transaction data based on RESTful API
[ https://issues.apache.org/jira/browse/SCB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-1371: --- Fix Version/s: pack-0.6.0 > Support for query transaction data based on RESTful API > --- > > Key: SCB-1371 > URL: https://issues.apache.org/jira/browse/SCB-1371 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.6.0 > > > Support for query terminated transaction data by RESTful API > Support for query running transaction data by RESTful API > Support for query running transaction data by RESTful API > Support for query suspended global transaction by RESTful API -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1370) Support for in-process nested global transactions
[ https://issues.apache.org/jira/browse/SCB-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-1370: --- Fix Version/s: pack-0.6.0 > Support for in-process nested global transactions > - > > Key: SCB-1370 > URL: https://issues.apache.org/jira/browse/SCB-1370 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: Lei Zhang >Priority: Major > Fix For: pack-0.6.0 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1436) Model is not generated, but the related package is imported
[ https://issues.apache.org/jira/browse/SCB-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1436. Resolution: Fixed > Model is not generated, but the related package is imported > --- > > Key: SCB-1436 > URL: https://issues.apache.org/jira/browse/SCB-1436 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Model is not generated, but the related package is imported -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1368) Support for Akka-based Alpha clusters
[ https://issues.apache.org/jira/browse/SCB-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-1368: --- Fix Version/s: pack-0.6.0 > Support for Akka-based Alpha clusters > - > > Key: SCB-1368 > URL: https://issues.apache.org/jira/browse/SCB-1368 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.6.0 > > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1452) update README
[ https://issues.apache.org/jira/browse/SCB-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1452. Resolution: Fixed > update README > - > > Key: SCB-1452 > URL: https://issues.apache.org/jira/browse/SCB-1452 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > update README -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1452) update README
[ https://issues.apache.org/jira/browse/SCB-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1452. -- > update README > - > > Key: SCB-1452 > URL: https://issues.apache.org/jira/browse/SCB-1452 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > update README -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1258) Using StateMachine for tracing the transaction states
[ https://issues.apache.org/jira/browse/SCB-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-1258: --- Fix Version/s: (was: pack-0.5.0) > Using StateMachine for tracing the transaction states > - > > Key: SCB-1258 > URL: https://issues.apache.org/jira/browse/SCB-1258 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Willem Jiang >Assignee: Lei Zhang >Priority: Major > Labels: alpha > > Using the state machine could reduce the code complexity of Alpha. > We could start a simple POC to verify the implementation. > We could also use it to trace the command sending states. > * Statemachine should handle timeout dynamically > * Statemachine should support message(event) persistent > * Support to the states of transaction from outside > * Statemachine cluster support -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (SCB-1454) The modules tag is not generated in the pom file when using cli
[ https://issues.apache.org/jira/browse/SCB-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen closed SCB-1454. -- > The modules tag is not generated in the pom file when using cli > --- > > Key: SCB-1454 > URL: https://issues.apache.org/jira/browse/SCB-1454 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The modules tag is not generated in the pom file when using cli -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1454) The modules tag is not generated in the pom file when using cli
[ https://issues.apache.org/jira/browse/SCB-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kakulisen resolved SCB-1454. Resolution: Fixed > The modules tag is not generated in the pom file when using cli > --- > > Key: SCB-1454 > URL: https://issues.apache.org/jira/browse/SCB-1454 > Project: Apache ServiceComb > Issue Type: Task > Components: toolkit >Affects Versions: toolkit-0.1.0 >Reporter: kakulisen >Assignee: kakulisen >Priority: Major > Fix For: toolkit-0.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The modules tag is not generated in the pom file when using cli -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1372) Collection state machine health to metrics
[ https://issues.apache.org/jira/browse/SCB-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1372: -- Fix Version/s: pack-0.5.0 > Collection state machine health to metrics > -- > > Key: SCB-1372 > URL: https://issues.apache.org/jira/browse/SCB-1372 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Start transaction counter > End transaction counter > Suspend transaction counter > Long transaction type, etc. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1373) Improve acceptance testing for state machines
[ https://issues.apache.org/jira/browse/SCB-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1373: -- Fix Version/s: pack-0.6.0 > Improve acceptance testing for state machines > - > > Key: SCB-1373 > URL: https://issues.apache.org/jira/browse/SCB-1373 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: Lei Zhang >Priority: Major > Fix For: pack-0.6.0 > > > sub-transaction timeout exception for akka acceptance test > compensation failure for akka acceptance test > compensation retry success for akka acceptance test -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1374) Implement Alpha Event Channel Plugin
[ https://issues.apache.org/jira/browse/SCB-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1374: -- Fix Version/s: pack-0.5.0 > Implement Alpha Event Channel Plugin > > > Key: SCB-1374 > URL: https://issues.apache.org/jira/browse/SCB-1374 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > After receiving the event, Alpha puts the event channel and returns quickly. > This can improve TPS. Alpha defaults to use the MemoryActorEventChannel, and > can extend other implementations through the interface. > Use alpha.feature.akka.channel.type to switch event channel type. > alpha.feature.akka.channel.type=redis use RedisActorEventChannel > alpha.feature.akka.channel.type=kafka use KafkaActorEventChannel > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1372) Collection state machine health to metrics
[ https://issues.apache.org/jira/browse/SCB-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1372: -- Affects Version/s: (was: pack-0.5.0) > Collection state machine health to metrics > -- > > Key: SCB-1372 > URL: https://issues.apache.org/jira/browse/SCB-1372 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Start transaction counter > End transaction counter > Suspend transaction counter > Long transaction type, etc. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (SCB-1374) Implement Alpha Event Channel Plugin
[ https://issues.apache.org/jira/browse/SCB-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated SCB-1374: -- Affects Version/s: (was: pack-0.5.0) > Implement Alpha Event Channel Plugin > > > Key: SCB-1374 > URL: https://issues.apache.org/jira/browse/SCB-1374 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > After receiving the event, Alpha puts the event channel and returns quickly. > This can improve TPS. Alpha defaults to use the MemoryActorEventChannel, and > can extend other implementations through the interface. > Use alpha.feature.akka.channel.type to switch event channel type. > alpha.feature.akka.channel.type=redis use RedisActorEventChannel > alpha.feature.akka.channel.type=kafka use KafkaActorEventChannel > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (SCB-1356) add NACOS to DiscoveryType
[ https://issues.apache.org/jira/browse/SCB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved SCB-1356. --- Resolution: Fixed > add NACOS to DiscoveryType > --- > > Key: SCB-1356 > URL: https://issues.apache.org/jira/browse/SCB-1356 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: cmonkey >Assignee: cmonkey >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Reopened] (SCB-1356) add NACOS to DiscoveryType
[ https://issues.apache.org/jira/browse/SCB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reopened SCB-1356: --- Assignee: cmonkey > add NACOS to DiscoveryType > --- > > Key: SCB-1356 > URL: https://issues.apache.org/jira/browse/SCB-1356 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: cmonkey >Assignee: cmonkey >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (SCB-1349) support Nacos Discovery
[ https://issues.apache.org/jira/browse/SCB-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned SCB-1349: - Assignee: cmonkey > support Nacos Discovery > --- > > Key: SCB-1349 > URL: https://issues.apache.org/jira/browse/SCB-1349 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.5.0 >Reporter: cmonkey >Assignee: cmonkey >Priority: Major > Fix For: pack-0.5.0 > > Time Spent: 1h > Remaining Estimate: 0h > > support Nacos Discovery -- This message was sent by Atlassian Jira (v8.3.2#803003)
