[jira] [Assigned] (SCB-2865) Spring Boot Actuator endpoints should be disabled for security purposes.
[ https://issues.apache.org/jira/browse/SCB-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reassigned SCB-2865: -- Assignee: Lei Zhang > Spring Boot Actuator endpoints should be disabled for security purposes. > > > Key: SCB-2865 > URL: https://issues.apache.org/jira/browse/SCB-2865 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Affects Versions: pack-0.7.1 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SCB-2865) Spring Boot Actuator endpoints should be disabled for security purposes.
Lei Zhang created SCB-2865: -- Summary: Spring Boot Actuator endpoints should be disabled for security purposes. Key: SCB-2865 URL: https://issues.apache.org/jira/browse/SCB-2865 Project: Apache ServiceComb Issue Type: Bug Components: Saga Affects Versions: pack-0.7.1 Reporter: Lei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SCB-2858) Bump maven from 3.5.2 to 3.6.3
[ https://issues.apache.org/jira/browse/SCB-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2858. Fix Version/s: pack-0.8.0 Resolution: Fixed > Bump maven from 3.5.2 to 3.6.3 > -- > > Key: SCB-2858 > URL: https://issues.apache.org/jira/browse/SCB-2858 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SCB-2858) Bump maven from 3.5.2 to 3.6.3
Lei Zhang created SCB-2858: -- Summary: Bump maven from 3.5.2 to 3.6.3 Key: SCB-2858 URL: https://issues.apache.org/jira/browse/SCB-2858 Project: Apache ServiceComb Issue Type: Task Components: Saga Reporter: Lei Zhang Assignee: Lei Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SCB-2478) Update pack releasae guide
[ https://issues.apache.org/jira/browse/SCB-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2478. Fix Version/s: pack-0.7.1 pack-0.8.0 Resolution: Fixed > Update pack releasae guide > -- > > Key: SCB-2478 > URL: https://issues.apache.org/jira/browse/SCB-2478 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.1, pack-0.8.0 > > > https://github.com/apache/servicecomb-website/edit/master/_developers/release_guide.md -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SCB-2679) Improve test coverage
[ https://issues.apache.org/jira/browse/SCB-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2679. Fix Version/s: pack-0.8.0 Resolution: Fixed > Improve test coverage > - > > Key: SCB-2679 > URL: https://issues.apache.org/jira/browse/SCB-2679 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: pack-0.7.0, pack-0.7.1 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.8.0 > > > Add a refactored[1] module to Coverage Aggregate > > [1] https://github.com/apache/servicecomb-pack/pull/749 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SCB-2679) Improve test coverage
[ https://issues.apache.org/jira/browse/SCB-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reassigned SCB-2679: -- Assignee: Lei Zhang > Improve test coverage > - > > Key: SCB-2679 > URL: https://issues.apache.org/jira/browse/SCB-2679 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: pack-0.7.0, pack-0.7.1 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > Add a refactored[1] module to Coverage Aggregate > > [1] https://github.com/apache/servicecomb-pack/pull/749 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SCB-2679) Improve test coverage
Lei Zhang created SCB-2679: -- Summary: Improve test coverage Key: SCB-2679 URL: https://issues.apache.org/jira/browse/SCB-2679 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: pack-0.7.0, pack-0.7.1 Reporter: Lei Zhang Add a refactored[1] module to Coverage Aggregate [1] https://github.com/apache/servicecomb-pack/pull/749 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SCB-2657) Fix wrong version placeholder for branch 0.7.x
[ https://issues.apache.org/jira/browse/SCB-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2657. Fix Version/s: pack-0.7.1 Resolution: Fixed > Fix wrong version placeholder for branch 0.7.x > --- > > Key: SCB-2657 > URL: https://issues.apache.org/jira/browse/SCB-2657 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.1 > > > https://github.com/apache/servicecomb-pack/issues/763 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SCB-2641) Use flatten-maven-plugin to update version placeholders ${revision} for the main pom
[
https://issues.apache.org/jira/browse/SCB-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang resolved SCB-2641.
Fix Version/s: pack-0.8.0
Resolution: Fixed
> Use flatten-maven-plugin to update version placeholders ${revision} for the
> main pom
>
>
> Key: SCB-2641
> URL: https://issues.apache.org/jira/browse/SCB-2641
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
> Fix For: pack-0.8.0
>
>
> The flatten-maven-plugin is missing from the main pom, resulting in no
> replacement of version placeholders in apache snapshot repositories
>
> *The current wrong pom*
> {code:java}
> http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>
> org.apache
> apache
> 18
>
> org.apache.servicecomb.pack
> pack
> pom
> ${revision}
> {code}
>
> *{color:#172b4d}Placeholders should be replaced in the correct cases, like
> this{color}*
>
> {code:java}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>
> org.apache
> apache
> 18
>
> org.apache.servicecomb.pack
> pack
> pom
> 0.8.0-SNAPSHOT
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (SCB-2657) Fix wrong version placeholder for branch 0.7.x
[ https://issues.apache.org/jira/browse/SCB-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reassigned SCB-2657: -- Assignee: Lei Zhang > Fix wrong version placeholder for branch 0.7.x > --- > > Key: SCB-2657 > URL: https://issues.apache.org/jira/browse/SCB-2657 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > https://github.com/apache/servicecomb-pack/issues/763 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SCB-2657) Fix wrong version placeholder for branch 0.7.x
Lei Zhang created SCB-2657: -- Summary: Fix wrong version placeholder for branch 0.7.x Key: SCB-2657 URL: https://issues.apache.org/jira/browse/SCB-2657 Project: Apache ServiceComb Issue Type: Sub-task Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang https://github.com/apache/servicecomb-pack/issues/763 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SCB-2641) Use flatten-maven-plugin to update version placeholders ${revision} for the main pom
[
https://issues.apache.org/jira/browse/SCB-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang reassigned SCB-2641:
--
Assignee: Lei Zhang
> Use flatten-maven-plugin to update version placeholders ${revision} for the
> main pom
>
>
> Key: SCB-2641
> URL: https://issues.apache.org/jira/browse/SCB-2641
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> The flatten-maven-plugin is missing from the main pom, resulting in no
> replacement of version placeholders in apache snapshot repositories
>
> *The current wrong pom*
> {code:java}
> http://maven.apache.org/POM/4.0.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>
> org.apache
> apache
> 18
>
> org.apache.servicecomb.pack
> pack
> pom
> ${revision}
> {code}
>
> *{color:#172b4d}Placeholders should be replaced in the correct cases, like
> this{color}*
>
> {code:java}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
>
> org.apache
> apache
> 18
>
> org.apache.servicecomb.pack
> pack
> pom
> 0.8.0-SNAPSHOT
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (SCB-2641) Use flatten-maven-plugin to update version placeholders ${revision} for the main pom
Lei Zhang created SCB-2641:
--
Summary: Use flatten-maven-plugin to update version placeholders
${revision} for the main pom
Key: SCB-2641
URL: https://issues.apache.org/jira/browse/SCB-2641
Project: Apache ServiceComb
Issue Type: Task
Components: Saga
Affects Versions: pack-0.7.0
Reporter: Lei Zhang
The flatten-maven-plugin is missing from the main pom, resulting in no
replacement of version placeholders in apache snapshot repositories
*The current wrong pom*
{code:java}
http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
org.apache
apache
18
org.apache.servicecomb.pack
pack
pom
${revision}
{code}
*{color:#172b4d}Placeholders should be replaced in the correct cases, like
this{color}*
{code:java}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
org.apache
apache
18
org.apache.servicecomb.pack
pack
pom
0.8.0-SNAPSHOT
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SCB-2506) Configure GnuPG key in maven-gpg-plugin with a keyname
[
https://issues.apache.org/jira/browse/SCB-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2506:
---
Description:
I've created 2 keys with gpg.
{code:java}
pub rsa2048 2020-06-25 [SC]
F07544CB36B8E954734C22DFCEC8F20C94850063
uid [ 绝对 ] Lei Zhang
sub rsa2048 2020-06-25 [E]
pub rsa4096 2022-05-05 [SC]
CA242F7DE725DFB5A8E446492B338CEB8A381CFF
uid [ 绝对 ] Lei Zhang (CODE SIGNING KEY)
sub rsa4096 2022-05-05 [E]
{code}
I hope to select GPG key with the profile in settings.xml when releasing [1]
[1]https://maven.apache.org/plugins/maven-gpg-plugin/usage.html
was:
I've created 2 keys with gpg.
pub rsa2048 2020-06-25 [SC]
F07544CB36B8E954734C22DFCEC8F20C94850063
uid [ 绝对 ] Lei Zhang
sub rsa2048 2020-06-25 [E]
pub rsa4096 2022-05-05 [SC]
CA242F7DE725DFB5A8E446492B338CEB8A381CFF
uid [ 绝对 ] Lei Zhang (CODE SIGNING KEY)
sub rsa4096 2022-05-05 [E]
I hope to select gpg key with profile in settings.xml when release[1]
[1]https://maven.apache.org/plugins/maven-gpg-plugin/usage.html
> Configure GnuPG key in maven-gpg-plugin with a keyname
> --
>
> Key: SCB-2506
> URL: https://issues.apache.org/jira/browse/SCB-2506
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Reporter: Lei Zhang
>Priority: Major
>
> I've created 2 keys with gpg.
> {code:java}
> pub rsa2048 2020-06-25 [SC]
> F07544CB36B8E954734C22DFCEC8F20C94850063
> uid [ 绝对 ] Lei Zhang
> sub rsa2048 2020-06-25 [E]
> pub rsa4096 2022-05-05 [SC]
> CA242F7DE725DFB5A8E446492B338CEB8A381CFF
> uid [ 绝对 ] Lei Zhang (CODE SIGNING KEY)
> sub rsa4096 2022-05-05 [E]
> {code}
> I hope to select GPG key with the profile in settings.xml when releasing [1]
> [1]https://maven.apache.org/plugins/maven-gpg-plugin/usage.html
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (SCB-2506) Configure GnuPG key in maven-gpg-plugin with a keyname
Lei Zhang created SCB-2506: -- Summary: Configure GnuPG key in maven-gpg-plugin with a keyname Key: SCB-2506 URL: https://issues.apache.org/jira/browse/SCB-2506 Project: Apache ServiceComb Issue Type: Task Components: Saga Reporter: Lei Zhang I've created 2 keys with gpg. pub rsa2048 2020-06-25 [SC] F07544CB36B8E954734C22DFCEC8F20C94850063 uid [ 绝对 ] Lei Zhang sub rsa2048 2020-06-25 [E] pub rsa4096 2022-05-05 [SC] CA242F7DE725DFB5A8E446492B338CEB8A381CFF uid [ 绝对 ] Lei Zhang (CODE SIGNING KEY) sub rsa4096 2022-05-05 [E] I hope to select gpg key with profile in settings.xml when release[1] [1]https://maven.apache.org/plugins/maven-gpg-plugin/usage.html -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (SCB-2477) Faster release with Maven CI Friendly Versions
[
https://issues.apache.org/jira/browse/SCB-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang resolved SCB-2477.
Fix Version/s: pack-0.7.0
Resolution: Fixed
> Faster release with Maven CI Friendly Versions
> --
>
> Key: SCB-2477
> URL: https://issues.apache.org/jira/browse/SCB-2477
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
> Fix For: pack-0.7.0
>
>
> Maven CI Friendly Versions[1] support use the ${revision} as placeholders for
> the version in your pom file
> [1] https://maven.apache.org/maven-ci-friendly.html
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (SCB-2486) Pack 0.7.0-SNAPSHOT Release Failed
[ https://issues.apache.org/jira/browse/SCB-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2486. Fix Version/s: pack-0.7.0 Resolution: Fixed > Pack 0.7.0-SNAPSHOT Release Failed > -- > > Key: SCB-2486 > URL: https://issues.apache.org/jira/browse/SCB-2486 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > [WARNING] The requested profile "passphrase" could not be activated because > it does not exist. > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on > project alpha-spec-saga-db: MavenReportException: Error while creating > archive: > [ERROR] Exit code: 1 - javadoc: 错误 - > 找不到javax.interceptor.InterceptorBinding的类文件 > [ERROR] > [ERROR] Command line was: > /Library/Java/JavaVirtualMachines/jdk1.8.0_201.jdk/Contents/Home/bin/javadoc > @options @packages > [ERROR] > [ERROR] Refer to the generated Javadoc files in > '/Users/zhanglei/coolbeevip/upstream/servicecomb-pack/alpha/alpha-spec-saga-db/target/apidocs' > dir. > [ERROR] > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn -rf :alpha-spec-saga-db -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SCB-2486) Pack 0.7.0-SNAPSHOT Release Failed
Lei Zhang created SCB-2486: -- Summary: Pack 0.7.0-SNAPSHOT Release Failed Key: SCB-2486 URL: https://issues.apache.org/jira/browse/SCB-2486 Project: Apache ServiceComb Issue Type: Task Components: Saga Reporter: Lei Zhang Assignee: Lei Zhang [WARNING] The requested profile "passphrase" could not be activated because it does not exist. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:jar (attach-javadocs) on project alpha-spec-saga-db: MavenReportException: Error while creating archive: [ERROR] Exit code: 1 - javadoc: 错误 - 找不到javax.interceptor.InterceptorBinding的类文件 [ERROR] [ERROR] Command line was: /Library/Java/JavaVirtualMachines/jdk1.8.0_201.jdk/Contents/Home/bin/javadoc @options @packages [ERROR] [ERROR] Refer to the generated Javadoc files in '/Users/zhanglei/coolbeevip/upstream/servicecomb-pack/alpha/alpha-spec-saga-db/target/apidocs' dir. [ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :alpha-spec-saga-db -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (SCB-2478) Update pack releasae guide
[ https://issues.apache.org/jira/browse/SCB-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2478: --- Description: https://github.com/apache/servicecomb-website/edit/master/_developers/release_guide.md > Update pack releasae guide > -- > > Key: SCB-2478 > URL: https://issues.apache.org/jira/browse/SCB-2478 > Project: Apache ServiceComb > Issue Type: Task > Components: website >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > https://github.com/apache/servicecomb-website/edit/master/_developers/release_guide.md -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (SCB-2478) Update pack releasae guide
Lei Zhang created SCB-2478: -- Summary: Update pack releasae guide Key: SCB-2478 URL: https://issues.apache.org/jira/browse/SCB-2478 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Lei Zhang Assignee: Lei Zhang -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (SCB-2477) Faster release with Maven CI Friendly Versions
[
https://issues.apache.org/jira/browse/SCB-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang reassigned SCB-2477:
--
Assignee: Lei Zhang
> Faster release with Maven CI Friendly Versions
> --
>
> Key: SCB-2477
> URL: https://issues.apache.org/jira/browse/SCB-2477
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> Maven CI Friendly Versions[1] support use the ${revision} as placeholders for
> the version in your pom file
> [1] https://maven.apache.org/maven-ci-friendly.html
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (SCB-2477) Faster release with Maven CI Friendly Versions
Lei Zhang created SCB-2477:
--
Summary: Faster release with Maven CI Friendly Versions
Key: SCB-2477
URL: https://issues.apache.org/jira/browse/SCB-2477
Project: Apache ServiceComb
Issue Type: Task
Components: Saga
Reporter: Lei Zhang
Maven CI Friendly Versions[1] support use the ${revision} as placeholders for
the version in your pom file
[1] https://maven.apache.org/maven-ci-friendly.html
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang resolved SCB-2425.
Fix Version/s: pack-0.7.0
Resolution: Fixed
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
> Fix For: pack-0.7.0
>
>
> The purpose of refactoring is to decouple distributed transaction
> implementation
> *Alpha Module*
> * Rename alpha-fsm to alpha-spec-saga-akka
> * Add alpha-spec-saga-db
> * Add alpha-spec-tcc-db
> * Keep Acceptance module artifactId and directory name the same, e.g. rename
> acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
> * Rename persistence-jpa to alpha/alpha-persistence-jpa
> *Alpha Using Spring SPI*
> * Load AlphaSpecXXXAutoConfiguration through spring.factories under each
> module
> * Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
> alpha.spec.names=saga-akka
> *Alpha Configuration*
> {code:java}
> alpha:
> spec:
> names: saga-db
> saga:
> akka:
> channel:
> name: memory
> memory:
> max-length: -1
> kafka:
> topic: servicecomb-pack-actor-event
> bootstrap-servers: 127.0.0.1:9092
> consumer:
> group-id: servicecomb-pack
> auto.offset.reset: earliest
> producer:
> batch-size: 16384
> retries: 0
> buffer.memory: 33554432
> repository:
> name: elasticsearch
> elasticsearch:
> uris: http://localhost:9200
> batch-size: 100
> refresh-time: 5000
> db:
> datasource:
> username: sa
> password:
> url: jdbc:hsqldb:mem:saga
> initialization-mode: always
> cluster:
> enabled: true
> type: jdbc
> expire: 5000
> tcc:
> db:
> memory-mode: true
> datasource:
> username: sa
> password:
> url: jdbc:hsqldb:mem:saga
> initialization-mode: always
> {code}
>
> *Omega Modules*
> * Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
> *Omega AutoConfiguration*
> * OmegaSagaSpringConfig using omega.spec.names=saga
> * OmegaTccSpringConfig using omega.spec.names=tcc
> * TransactionAspectConfig class of the omega-spring-tx module uses
> ConditionalOnExpression to initialize beans
> *Legacy Issue*
> * [Duplicate Code]Create class EclipseLinkJpaConfiguration in test case to
> avoid dependency on class EclipseLinkJpaConfiguration in
> alpha-persistence-jpa module
> * [Duplicate Code]Because of the metrics API, each Spec module contains same
> classes as follows
> {code:java}
> AlphaMetricsEndpointImpl.java
> MetricsService.java
> SagaAkkaAPIv1Controller.java, SagaAkkaAPIv1Impl.java
> SagaDbAPIv1Controller.java, SagaDbAPIv1Impl.java
> TccDbAPIv1Controller.java, TccDbAPIv1Impl.java
> {code}
> * saga-db saga-akka and tcc-db cannot be used together
> * Refactor Redis and Rabbit channel configuration in saga-akka module
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Legacy Issue*
* [Duplicate Code]Create class EclipseLinkJpaConfiguration in test case to
avoid dependency on class EclipseLinkJpaConfiguration in alpha-persistence-jpa
module
* [Duplicate Code]Because of the metrics API, each Spec module contains same
classes as follows
{code:java}
AlphaMetricsEndpointImpl.java
MetricsService.java
SagaAkkaAPIv1Controller.java, SagaAkkaAPIv1Impl.java
SagaDbAPIv1Controller.java, SagaDbAPIv1Impl.java
TccDbAPIv1Controller.java, TccDbAPIv1Impl.java
{code}
* saga-db saga-akka and tcc-db cannot be used together
* Refactor Redis and Rabbit channel configuration in saga-akka module
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Legacy Issue*
* [Duplicate Code]Create
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Legacy Issue*
* [Duplicate Code]Create class EclipseLinkJpaConfiguration in test case to
avoid dependency on class EclipseLinkJpaConfiguration in alpha-persistence-jpa
module
* [Duplicate Code]Because of the metrics API, each Spec module contains same
classes as follows(saga-xxx and tcc-xxx cannot be enabled at the same time)
{code:java}
AlphaMetricsEndpointImpl.java
MetricsService.java
SagaAkkaAPIv1Controller.java, SagaAkkaAPIv1Impl.java
SagaDbAPIv1Controller.java, SagaDbAPIv1Impl.java
TccDbAPIv1Controller.java, TccDbAPIv1Impl.java
{code}
* Refactor Redis and Rabbit channel configuration in saga-akka module
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Legacy Issue*
* [Duplicate
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Legacy Issue*
* [Duplicate Code]Create class EclipseLinkJpaConfiguration in test case to
avoid dependency on class EclipseLinkJpaConfiguration in alpha-persistence-jpa
module
* [Duplicate Code]Because of the metrics API, each Spec module contains same
classes as follows(saga-xxx and tcc-xxx cannot be enabled at the same time)
{code:java}
AlphaMetricsEndpointImpl.java
MetricsService.java
SagaAkkaAPIv1Controller.java, SagaAkkaAPIv1Impl.java
SagaDbAPIv1Controller.java, SagaDbAPIv1Impl.java
TccDbAPIv1Controller.java, TccDbAPIv1Impl.java
{code}
* Refactor Redis and Rabbit channel configuration in saga-akka module
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
*
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
* Because of the metrics API, each Spec module contains same classes as
follows(saga-xxx and tcc-xxx cannot be enabled at the same time)
{code:java}
AlphaMetricsEndpointImpl.java
MetricsService.java
SagaAkkaAPIv1Controller.java, SagaAkkaAPIv1Impl.java
SagaDbAPIv1Controller.java, SagaDbAPIv1Impl.java
TccDbAPIv1Controller.java, TccDbAPIv1Impl.java
{code}
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
* Because of the metrics API, each Spec module contains duplicate classes as
follows(saga-xxx and tcc-xxx cannot be enabled at the same time)
* AlphaMetricsEndpointImpl.java
* MetricsService.java
* APIv1Controller.java, APIv1Impl.java
* SagaDbAPIv1Controller.java, SagaDbAPIv1Impl.java
* TccDbAPIv1Controller.java, TccDbAPIv1Impl.java
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Rename persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Remove persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Remove persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Modules*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega AutoConfiguration*
* OmegaSagaSpringConfig using omega.spec.names=saga
* OmegaTccSpringConfig using omega.spec.names=tcc
* TransactionAspectConfig class of the omega-spring-tx module uses
ConditionalOnExpression to initialize beans
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Remove persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Components*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> The purpose of refactoring is to decouple
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Rename alpha-fsm to alpha-spec-saga-akka
* Add alpha-spec-saga-db
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Remove persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Components*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
*Duplicate Code*
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Add alpha-spec-saga-db
* Add alpha-spec-saga-akka
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Remove persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Components*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
* Duplicate Code
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> The purpose of refactoring is to decouple distributed transaction
> implementation
> *Alpha Module*
> * Rename alpha-fsm to alpha-spec-saga-akka
> * Add alpha-spec-saga-db
> * Add alpha-spec-tcc-db
> *
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Module*
* Add alpha-spec-saga-db
* Add alpha-spec-saga-akka
* Add alpha-spec-tcc-db
* Keep Acceptance module artifactId and directory name the same, e.g. rename
acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
* Remove persistence-jpa to alpha/alpha-persistence-jpa
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Components*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
* Duplicate Code
* Create class EclipseLinkJpaConfiguration in test case to avoid dependency on
class EclipseLinkJpaConfiguration in alpha-persistence-jpa module
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Components*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Components*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> The purpose of refactoring is to decouple distributed transaction
> implementation
> *Alpha Module*
> * Add alpha-spec-saga-db
> * Add alpha-spec-saga-akka
> * Add alpha-spec-tcc-db
> * Keep Acceptance module artifactId and directory name the same, e.g. rename
> acceptance-pack-akka-spring to acceptance-pack-akka-spring-demo
> * Remove persistence-jpa to alpha/alpha-persistence-jpa
> *Alpha Using Spring SPI*
> * Load AlphaSpecXXXAutoConfiguration through spring.factories under each
> module
> * Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
>
[jira] [Resolved] (SCB-2275) coveralls-maven-plugin fails on Java 11 - required class missing: DatatypeConverter
[ https://issues.apache.org/jira/browse/SCB-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2275. Resolution: Fixed > coveralls-maven-plugin fails on Java 11 - required class missing: > DatatypeConverter > --- > > Key: SCB-2275 > URL: https://issues.apache.org/jira/browse/SCB-2275 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > https://github.com/apache/servicecomb-pack/actions/runs/714189795 > Error: Failed to execute goal > org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report (default-cli) on > project pack: Execution default-cli of goal > org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report failed: A required > class was missing while executing > org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report: > javax/xml/bind/DatatypeConverter -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SCB-2238) FSM event channel supports Rabbit
[ https://issues.apache.org/jira/browse/SCB-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2238. Fix Version/s: pack-0.7.0 Resolution: Fixed > FSM event channel supports Rabbit > - > > Key: SCB-2238 > URL: https://issues.apache.org/jira/browse/SCB-2238 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha Components*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Components*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha module changes*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Component*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> The purpose of refactoring is to decouple distributed transaction
> implementation
> *Alpha Components*
> * alpha-spec-saga-db
> * alpha-spec-saga-akka
> * alpha-spec-tcc-db
> *Alpha Using Spring SPI*
> * Load AlphaSpecXXXAutoConfiguration through spring.factories under each
> module
> * Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
> alpha.spec.names=saga-akka,tcc-db
> *Alpha Configuration parameters*
> {code:java}
> alpha:
> spec:
> names: saga-db
> saga:
> akka:
> channel:
> name: memory
> memory:
> max-length: -1
> kafka:
> topic: servicecomb-pack-actor-event
> bootstrap-servers: 127.0.0.1:9092
> consumer:
> group-id: servicecomb-pack
> auto.offset.reset: earliest
> producer:
> batch-size: 16384
> retries: 0
> buffer.memory: 33554432
>
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha module changes*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Component*
* Split OmegaSpringConfig into OmegaSagaSpringConfig and OmegaTccSpringConfig
*Omega Configuration parameters*
* omega.spec.names=tcc or omega.spec.names=saga,tcc
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha module changes*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Configuration parameters*
omega.spec.names=tcc or omega.spec.names=saga,tcc
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> The purpose of refactoring is to decouple distributed transaction
> implementation
> *Alpha module changes*
> * alpha-spec-saga-db
> * alpha-spec-saga-akka
> * alpha-spec-tcc-db
> *Alpha Using Spring SPI*
> * Load AlphaSpecXXXAutoConfiguration through spring.factories under each
> module
> * Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
> alpha.spec.names=saga-akka,tcc-db
> *Alpha Configuration parameters*
> {code:java}
> alpha:
> spec:
> names: saga-db
> saga:
> akka:
> channel:
> name: memory
> memory:
> max-length: -1
> kafka:
> topic: servicecomb-pack-actor-event
> bootstrap-servers: 127.0.0.1:9092
> consumer:
> group-id: servicecomb-pack
> auto.offset.reset: earliest
> producer:
> batch-size: 16384
> retries: 0
> buffer.memory: 33554432
> repository:
> name: elasticsearch
> elasticsearch:
>
[jira] [Updated] (SCB-2425) Refactoring the Alpha module using Spring SPI
[
https://issues.apache.org/jira/browse/SCB-2425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2425:
---
Description:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha module changes*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Alpha Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Alpha Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
*Omega Configuration parameters*
omega.spec.names=tcc or omega.spec.names=saga,tcc
was:
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha module changes*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each
module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
> Refactoring the Alpha module using Spring SPI
> -
>
> Key: SCB-2425
> URL: https://issues.apache.org/jira/browse/SCB-2425
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> The purpose of refactoring is to decouple distributed transaction
> implementation
> *Alpha module changes*
> * alpha-spec-saga-db
> * alpha-spec-saga-akka
> * alpha-spec-tcc-db
> *Alpha Using Spring SPI*
> * Load AlphaSpecXXXAutoConfiguration through spring.factories under each
> module
> * Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
> alpha.spec.names=saga-akka,tcc-db
> *Alpha Configuration parameters*
> {code:java}
> alpha:
> spec:
> names: saga-db
> saga:
> akka:
> channel:
> name: memory
> memory:
> max-length: -1
> kafka:
> topic: servicecomb-pack-actor-event
> bootstrap-servers: 127.0.0.1:9092
> consumer:
> group-id: servicecomb-pack
> auto.offset.reset: earliest
> producer:
> batch-size: 16384
> retries: 0
> buffer.memory: 33554432
> repository:
> name: elasticsearch
> elasticsearch:
> uris: http://localhost:9200
> batch-size: 100
> refresh-time: 5000
> db:
> datasource:
> username: sa
> password:
> url:
[jira] [Created] (SCB-2425) Refactoring the Alpha module using Spring SPI
Lei Zhang created SCB-2425:
--
Summary: Refactoring the Alpha module using Spring SPI
Key: SCB-2425
URL: https://issues.apache.org/jira/browse/SCB-2425
Project: Apache ServiceComb
Issue Type: Task
Components: Saga
Affects Versions: pack-0.7.0
Reporter: Lei Zhang
Assignee: Lei Zhang
The purpose of refactoring is to decouple distributed transaction implementation
*Alpha module changes*
* alpha-spec-saga-db
* alpha-spec-saga-akka
* alpha-spec-tcc-db
*Using Spring SPI*
* Load AlphaSpecXXXAutoConfiguration through spring.factories under each
module
* Configure the SPI module by parameters, likes alpha.spec.names=saga-db or
alpha.spec.names=saga-akka,tcc-db
*Configuration parameters*
{code:java}
alpha:
spec:
names: saga-db
saga:
akka:
channel:
name: memory
memory:
max-length: -1
kafka:
topic: servicecomb-pack-actor-event
bootstrap-servers: 127.0.0.1:9092
consumer:
group-id: servicecomb-pack
auto.offset.reset: earliest
producer:
batch-size: 16384
retries: 0
buffer.memory: 33554432
repository:
name: elasticsearch
elasticsearch:
uris: http://localhost:9200
batch-size: 100
refresh-time: 5000
db:
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
cluster:
enabled: true
type: jdbc
expire: 5000
tcc:
db:
memory-mode: true
datasource:
username: sa
password:
url: jdbc:hsqldb:mem:saga
initialization-mode: always
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SCB-2421) Migrate Spring-Boot from 2.1.X.RELEASE to 2.3.X.RELEASE
[ https://issues.apache.org/jira/browse/SCB-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2421: --- Description: A small step Upgrade spring-boot to 2.3.12.RELEASE Upgrade spring-cloud to Hoxton.SR12 https://github.com/spring-cloud/spring-cloud-release/wiki/Supported-Versions#supported-releases was: Upgrade spring-boot to 2.3.12. https://github.com/spring-cloud/spring-cloud-release/wiki/Supported-Versions#supported-releases > Migrate Spring-Boot from 2.1.X.RELEASE to 2.3.X.RELEASE > --- > > Key: SCB-2421 > URL: https://issues.apache.org/jira/browse/SCB-2421 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > A small step > Upgrade spring-boot to 2.3.12.RELEASE > Upgrade spring-cloud to Hoxton.SR12 > https://github.com/spring-cloud/spring-cloud-release/wiki/Supported-Versions#supported-releases -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SCB-2421) Migrate Spring-Boot from 2.1.X.RELEASE to 2.3.X.RELEASE
[ https://issues.apache.org/jira/browse/SCB-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2421: --- Description: Upgrade spring-boot to 2.3.12. https://github.com/spring-cloud/spring-cloud-release/wiki/Supported-Versions#supported-releases > Migrate Spring-Boot from 2.1.X.RELEASE to 2.3.X.RELEASE > --- > > Key: SCB-2421 > URL: https://issues.apache.org/jira/browse/SCB-2421 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > Upgrade spring-boot to 2.3.12. > https://github.com/spring-cloud/spring-cloud-release/wiki/Supported-Versions#supported-releases -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SCB-2421) Migrate Spring-Boot from 2.1.X.RELEASE to 2.3.X.RELEASE
Lei Zhang created SCB-2421: -- Summary: Migrate Spring-Boot from 2.1.X.RELEASE to 2.3.X.RELEASE Key: SCB-2421 URL: https://issues.apache.org/jira/browse/SCB-2421 Project: Apache ServiceComb Issue Type: Sub-task Components: Saga Reporter: Lei Zhang Assignee: Lei Zhang -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SCB-2397) Add pack-dependencies module management dependencies
[ https://issues.apache.org/jira/browse/SCB-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2397. Fix Version/s: pack-0.7.0 Resolution: Fixed > Add pack-dependencies module management dependencies > > > Key: SCB-2397 > URL: https://issues.apache.org/jira/browse/SCB-2397 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > * Add pack-dependencies module > * Spring Boot 2.1.X and Spring Cloud Greenwich Release compatibility > matrix[1] > * Spring Cloud Greenwich.SR1 include Spring Cloud component version 2.1.1[2] > [1]https://spring.io/projects/spring-cloud > [2]https://github.com/spring-projects/spring-cloud/wiki/Spring-Cloud-Greenwich-Release-Notes#greenwichsr1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SCB-2397) Add pack-dependencies module management dependencies
[ https://issues.apache.org/jira/browse/SCB-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2397: --- Description: * Add pack-dependencies module * Spring Boot 2.1.X and Spring Cloud Greenwich Release compatibility matrix[1] * Spring Cloud Greenwich.SR1 include Spring Cloud component version 2.1.1[2] [1]https://spring.io/projects/spring-cloud [2]https://github.com/spring-projects/spring-cloud/wiki/Spring-Cloud-Greenwich-Release-Notes#greenwichsr1 > Add pack-dependencies module management dependencies > > > Key: SCB-2397 > URL: https://issues.apache.org/jira/browse/SCB-2397 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > * Add pack-dependencies module > * Spring Boot 2.1.X and Spring Cloud Greenwich Release compatibility > matrix[1] > * Spring Cloud Greenwich.SR1 include Spring Cloud component version 2.1.1[2] > [1]https://spring.io/projects/spring-cloud > [2]https://github.com/spring-projects/spring-cloud/wiki/Spring-Cloud-Greenwich-Release-Notes#greenwichsr1 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SCB-2397) Add pack-dependencies module management dependencies
Lei Zhang created SCB-2397: -- Summary: Add pack-dependencies module management dependencies Key: SCB-2397 URL: https://issues.apache.org/jira/browse/SCB-2397 Project: Apache ServiceComb Issue Type: Sub-task Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (SCB-2397) Add pack-dependencies module management dependencies
[ https://issues.apache.org/jira/browse/SCB-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reassigned SCB-2397: -- Assignee: Lei Zhang > Add pack-dependencies module management dependencies > > > Key: SCB-2397 > URL: https://issues.apache.org/jira/browse/SCB-2397 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SCB-2239) [JDK11] Support JDK11 LTS
[ https://issues.apache.org/jira/browse/SCB-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2239. Fix Version/s: pack-0.7.0 Resolution: Fixed > [JDK11] Support JDK11 LTS > - > > Key: SCB-2239 > URL: https://issues.apache.org/jira/browse/SCB-2239 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > Github Actions CI build and test for JDK11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2275) coveralls-maven-plugin fails on Java 11 - required class missing: DatatypeConverter
Lei Zhang created SCB-2275: -- Summary: coveralls-maven-plugin fails on Java 11 - required class missing: DatatypeConverter Key: SCB-2275 URL: https://issues.apache.org/jira/browse/SCB-2275 Project: Apache ServiceComb Issue Type: Task Components: Saga Reporter: Lei Zhang Assignee: Lei Zhang Fix For: pack-0.7.0 https://github.com/apache/servicecomb-pack/actions/runs/714189795 Error: Failed to execute goal org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report (default-cli) on project pack: Execution default-cli of goal org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report failed: A required class was missing while executing org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report: javax/xml/bind/DatatypeConverter -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2248) Update jacoco version 0.8.6 for Java 11
[ https://issues.apache.org/jira/browse/SCB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2248. Fix Version/s: pack-0.7.0 Resolution: Fixed > Update jacoco version 0.8.6 for Java 11 > --- > > Key: SCB-2248 > URL: https://issues.apache.org/jira/browse/SCB-2248 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > maven jacoco plugin 0.7.x not compatible java 11 > https://github.com/jacoco/jacoco/issues/551 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2248) Update jacoco version 0.8.6 for Java 11
[ https://issues.apache.org/jira/browse/SCB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2248: --- Description: maven jacoco plugin 0.7.x not compatible java 11 https://github.com/jacoco/jacoco/issues/551 was:https://github.com/jacoco/jacoco/issues/551 > Update jacoco version 0.8.6 for Java 11 > --- > > Key: SCB-2248 > URL: https://issues.apache.org/jira/browse/SCB-2248 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > maven jacoco plugin 0.7.x not compatible java 11 > https://github.com/jacoco/jacoco/issues/551 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2248) Update jacoco version 0.8.6 for Java 11
[ https://issues.apache.org/jira/browse/SCB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2248: --- Summary: Update jacoco version 0.8.6 for Java 11 (was: Update jacoco version 0.8.5 for Java 11) > Update jacoco version 0.8.6 for Java 11 > --- > > Key: SCB-2248 > URL: https://issues.apache.org/jira/browse/SCB-2248 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > https://github.com/jacoco/jacoco/issues/551 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2248) Update jacoco version 0.8.5 for Java 11
Lei Zhang created SCB-2248: -- Summary: Update jacoco version 0.8.5 for Java 11 Key: SCB-2248 URL: https://issues.apache.org/jira/browse/SCB-2248 Project: Apache ServiceComb Issue Type: Sub-task Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang https://github.com/jacoco/jacoco/issues/551 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2239) [JDK11] Support JDK11 LTS
Lei Zhang created SCB-2239: -- Summary: [JDK11] Support JDK11 LTS Key: SCB-2239 URL: https://issues.apache.org/jira/browse/SCB-2239 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang This is an umbrella issue for tracking all the problems for JDK11 in Pack -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2239) [JDK11] Support JDK11 LTS
[ https://issues.apache.org/jira/browse/SCB-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2239: --- Description: Github Actions CI build and test for JDK11 (was: Build and Run Pack on JDK11) > [JDK11] Support JDK11 LTS > - > > Key: SCB-2239 > URL: https://issues.apache.org/jira/browse/SCB-2239 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > Github Actions CI build and test for JDK11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2239) [JDK11] Support JDK11 LTS
[ https://issues.apache.org/jira/browse/SCB-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2239: --- Description: Build and Run Pack on JDK11 (was: This is an umbrella issue for tracking all the problems for JDK11 in Pack Build and Run Pack on JDK11) > [JDK11] Support JDK11 LTS > - > > Key: SCB-2239 > URL: https://issues.apache.org/jira/browse/SCB-2239 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > Build and Run Pack on JDK11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2239) [JDK11] Support JDK11 LTS
[ https://issues.apache.org/jira/browse/SCB-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2239: --- Description: This is an umbrella issue for tracking all the problems for JDK11 in Pack Build and Run Pack on JDK11 was:This is an umbrella issue for tracking all the problems for JDK11 in Pack > [JDK11] Support JDK11 LTS > - > > Key: SCB-2239 > URL: https://issues.apache.org/jira/browse/SCB-2239 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > This is an umbrella issue for tracking all the problems for JDK11 in Pack > Build and Run Pack on JDK11 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2204) Acceptance Tests Akka fails
[ https://issues.apache.org/jira/browse/SCB-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2204. Resolution: Fixed > Acceptance Tests Akka fails > --- > > Key: SCB-2204 > URL: https://issues.apache.org/jira/browse/SCB-2204 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > Failed scenarios: > src/test/resources/alpha_records_transaction_events.feature:171 # 7.Hotel > sub-transaction failed and Car sub-transaction compensate failed and global > transaction suspended > 7 Scenarios (1 failed, 6 passed) > 60 Steps (1 failed, 2 skipped, 57 passed) > 0m50.347s > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled > within 30 seconds. > at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:136) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:79) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:27) > at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:840) > at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:802) > at > org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:60) > at > org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:53) > at > org.apache.servicecomb.pack.PackStepdefs.lambda$new$7(PackStepdefs.java:101) > at ✽.Alpha records the following > events(src/test/resources/alpha_records_transaction_events.feature:178) > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 50.768 sec > <<< FAILURE! - in org.apache.servicecomb.pack.RunCucumberIT > 7.Hotel sub-transaction failed and Car sub-transaction compensate failed and > global transaction suspended(Alpha records transaction events) Time elapsed: > 31.034 sec <<< ERROR! > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled > within 30 seconds. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2222) Unstable test cases on poor performance CI
[ https://issues.apache.org/jira/browse/SCB-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-. Fix Version/s: pack-0.7.0 Resolution: Fixed > Unstable test cases on poor performance CI > -- > > Key: SCB- > URL: https://issues.apache.org/jira/browse/SCB- > Project: Apache ServiceComb > Issue Type: Test > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > This test case has a high probability of timeout errors on poor performance CI > https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true#step:6:1074 > https://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=true#step:6:1995 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2231) Github Actions only work on apache/servicecomb-pack
[ https://issues.apache.org/jira/browse/SCB-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2231. Fix Version/s: pack-0.7.0 Resolution: Fixed > Github Actions only work on apache/servicecomb-pack > --- > > Key: SCB-2231 > URL: https://issues.apache.org/jira/browse/SCB-2231 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SCB-2238) FSM event channel supports Rabbit
[ https://issues.apache.org/jira/browse/SCB-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reassigned SCB-2238: -- Assignee: Lei Zhang > FSM event channel supports Rabbit > - > > Key: SCB-2238 > URL: https://issues.apache.org/jira/browse/SCB-2238 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SCB-2238) FSM event channel supports Rabbit
[ https://issues.apache.org/jira/browse/SCB-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308290#comment-17308290 ] Lei Zhang commented on SCB-2238: Demand comes from the community [1] [1] https://github.com/apache/servicecomb-pack/issues/686 > FSM event channel supports Rabbit > - > > Key: SCB-2238 > URL: https://issues.apache.org/jira/browse/SCB-2238 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2238) FSM event channel supports Rabbit
Lei Zhang created SCB-2238: -- Summary: FSM event channel supports Rabbit Key: SCB-2238 URL: https://issues.apache.org/jira/browse/SCB-2238 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2231) Github Actions only work on apache/servicecomb-pack
Lei Zhang created SCB-2231: -- Summary: Github Actions only work on apache/servicecomb-pack Key: SCB-2231 URL: https://issues.apache.org/jira/browse/SCB-2231 Project: Apache ServiceComb Issue Type: Bug Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2222) Unstable test cases on poor performance CI
[ https://issues.apache.org/jira/browse/SCB-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-: --- Description: This test case has a high probability of timeout errors on poor performance CI https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true#step:6:1074 https://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=true#step:6:1995 was: This test case has a high probability of timeout errors on poor performance CI https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true https://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=truehttps://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=true#step:6:1995 > Unstable test cases on poor performance CI > -- > > Key: SCB- > URL: https://issues.apache.org/jira/browse/SCB- > Project: Apache ServiceComb > Issue Type: Test > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > This test case has a high probability of timeout errors on poor performance CI > https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true#step:6:1074 > https://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=true#step:6:1995 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2222) Unstable test cases on poor performance CI
[ https://issues.apache.org/jira/browse/SCB-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-: --- Description: This test case has a high probability of timeout errors on poor performance CI https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true https://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=truehttps://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=true#step:6:1995 was: This test case has a high probability of timeout errors on poor performance CI https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true Running org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 17.947 sec <<< FAILURE! - in org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest resetLatencyOnReconnection(org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest) Time elapsed: 5.874 sec <<< ERROR! org.awaitility.core.ConditionTimeoutException: Condition returned by method "resetLatencyOnReconnection" in class org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest was not fulfilled within 5 seconds. at org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest.resetLatencyOnReconnection(SagaLoadBalancedSenderTest.java:126) Results : Tests in error: SagaLoadBalancedSenderTest.resetLatencyOnReconnection:126 » ConditionTimeout C... Tests run: 38, Failures: 0, Errors: 1, Skipped: 0 > Unstable test cases on poor performance CI > -- > > Key: SCB- > URL: https://issues.apache.org/jira/browse/SCB- > Project: Apache ServiceComb > Issue Type: Test > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > This test case has a high probability of timeout errors on poor performance CI > https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true > https://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=truehttps://github.com/apache/servicecomb-pack/runs/2157935390?check_suite_focus=true#step:6:1995 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2227) [UI] Property or field 'upTime' cannot be found on null
[ https://issues.apache.org/jira/browse/SCB-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2227. Fix Version/s: pack-0.7.0 Resolution: Fixed > [UI] Property or field 'upTime' cannot be found on null > --- > > Key: SCB-2227 > URL: https://issues.apache.org/jira/browse/SCB-2227 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > 2021-03-20 03:35:58.997 ERROR fd4667eba990 --- [nio-8090-exec-1] > o.t.TemplateEngine : [THYMELEAF][http-nio-8090-exec-1] > Exception processing template "index": Exception evaluating SpringEL > expression: "systemInfo.upTime" (template: "index" - line 257, col 39) > org.thymeleaf.exceptions.TemplateProcessingException: Exception evaluating > SpringEL expression: "systemInfo.upTime" (template: "index" - line 257, col > 39) > at > org.thymeleaf.spring5.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:290) > at > org.thymeleaf.standard.expression.VariableExpression.executeVariableExpression(VariableExpression.java:166) > at > org.thymeleaf.standard.expression.SimpleExpression.executeSimple(SimpleExpression.java:66) > at > org.thymeleaf.standard.expression.Expression.execute(Expression.java:109) > at > org.thymeleaf.standard.expression.Expression.execute(Expression.java:138) > at > org.thymeleaf.standard.processor.AbstractStandardExpressionAttributeTagProcessor.doProcess(AbstractStandardExpressionAttributeTagProcessor.java:144) > at > org.thymeleaf.processor.element.AbstractAttributeTagProcessor.doProcess(AbstractAttributeTagProcessor.java:74) > at > org.thymeleaf.processor.element.AbstractElementTagProcessor.process(AbstractElementTagProcessor.java:95) > at > org.thymeleaf.util.ProcessorConfigurationUtils$ElementTagProcessorWrapper.process(ProcessorConfigurationUtils.java:633) > at > org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1314) > at > org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) > at org.thymeleaf.engine.Model.process(Model.java:282) > at > org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) > at > org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) > at org.thymeleaf.engine.Model.process(Model.java:282) > at > org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) > at > org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) > at org.thymeleaf.engine.Model.process(Model.java:282) > at org.thymeleaf.engine.Model.process(Model.java:290) > at > org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) > at > org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) > at > org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) > at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) > at > org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:661) > at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1098) > at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1072) > at > org.thymeleaf.spring5.view.ThymeleafView.renderFragment(ThymeleafView.java:362) > at > org.thymeleaf.spring5.view.ThymeleafView.render(ThymeleafView.java:189) > at > org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1371) > at > org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1117) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1056) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:942) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1005) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:897) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) > at
[jira] [Created] (SCB-2227) [UI] Property or field 'upTime' cannot be found on null
Lei Zhang created SCB-2227: -- Summary: [UI] Property or field 'upTime' cannot be found on null Key: SCB-2227 URL: https://issues.apache.org/jira/browse/SCB-2227 Project: Apache ServiceComb Issue Type: Bug Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang 2021-03-20 03:35:58.997 ERROR fd4667eba990 --- [nio-8090-exec-1] o.t.TemplateEngine : [THYMELEAF][http-nio-8090-exec-1] Exception processing template "index": Exception evaluating SpringEL expression: "systemInfo.upTime" (template: "index" - line 257, col 39) org.thymeleaf.exceptions.TemplateProcessingException: Exception evaluating SpringEL expression: "systemInfo.upTime" (template: "index" - line 257, col 39) at org.thymeleaf.spring5.expression.SPELVariableExpressionEvaluator.evaluate(SPELVariableExpressionEvaluator.java:290) at org.thymeleaf.standard.expression.VariableExpression.executeVariableExpression(VariableExpression.java:166) at org.thymeleaf.standard.expression.SimpleExpression.executeSimple(SimpleExpression.java:66) at org.thymeleaf.standard.expression.Expression.execute(Expression.java:109) at org.thymeleaf.standard.expression.Expression.execute(Expression.java:138) at org.thymeleaf.standard.processor.AbstractStandardExpressionAttributeTagProcessor.doProcess(AbstractStandardExpressionAttributeTagProcessor.java:144) at org.thymeleaf.processor.element.AbstractAttributeTagProcessor.doProcess(AbstractAttributeTagProcessor.java:74) at org.thymeleaf.processor.element.AbstractElementTagProcessor.process(AbstractElementTagProcessor.java:95) at org.thymeleaf.util.ProcessorConfigurationUtils$ElementTagProcessorWrapper.process(ProcessorConfigurationUtils.java:633) at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1314) at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) at org.thymeleaf.engine.Model.process(Model.java:282) at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) at org.thymeleaf.engine.Model.process(Model.java:282) at org.thymeleaf.engine.ProcessorTemplateHandler.handleOpenElement(ProcessorTemplateHandler.java:1587) at org.thymeleaf.engine.OpenElementTag.beHandled(OpenElementTag.java:205) at org.thymeleaf.engine.Model.process(Model.java:282) at org.thymeleaf.engine.Model.process(Model.java:290) at org.thymeleaf.engine.GatheringModelProcessable.process(GatheringModelProcessable.java:78) at org.thymeleaf.engine.ProcessorTemplateHandler.handleCloseElement(ProcessorTemplateHandler.java:1640) at org.thymeleaf.engine.CloseElementTag.beHandled(CloseElementTag.java:139) at org.thymeleaf.engine.TemplateModel.process(TemplateModel.java:136) at org.thymeleaf.engine.TemplateManager.parseAndProcess(TemplateManager.java:661) at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1098) at org.thymeleaf.TemplateEngine.process(TemplateEngine.java:1072) at org.thymeleaf.spring5.view.ThymeleafView.renderFragment(ThymeleafView.java:362) at org.thymeleaf.spring5.view.ThymeleafView.render(ThymeleafView.java:189) at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1371) at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1117) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1056) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:942) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1005) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:897) at javax.servlet.http.HttpServlet.service(HttpServlet.java:634) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:882) at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at
[jira] [Resolved] (SCB-2205) Polishing Github actions workflow
[ https://issues.apache.org/jira/browse/SCB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2205. Fix Version/s: pack-0.7.0 Resolution: Fixed > Polishing Github actions workflow > - > > Key: SCB-2205 > URL: https://issues.apache.org/jira/browse/SCB-2205 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > Splits the ci.yaml to pr and push script > Temporarily disable unstable test case for poor performance CI > Update GHA script for JIRA's recommendations in the GitHub Action Status > Add Coveralls > Add scheduled deploy workflow > Remove Travis -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2223) NEXUS's secret name is wrong
[ https://issues.apache.org/jira/browse/SCB-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2223. Resolution: Fixed > NEXUS's secret name is wrong > > > Key: SCB-2223 > URL: https://issues.apache.org/jira/browse/SCB-2223 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > suggestions given by infra > [1] > https://issues.apache.org/jira/browse/INFRA-21587?focusedCommentId=17303898=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17303898https://issues.apache.org/jira/browse/INFRA-21587?focusedCommentId=17303898=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17303898 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2219) Use Github secrets to configure snapshot deploy to Nexus authentication
[ https://issues.apache.org/jira/browse/SCB-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2219. Fix Version/s: pack-0.7.0 Resolution: Fixed > Use Github secrets to configure snapshot deploy to Nexus authentication > --- > > Key: SCB-2219 > URL: https://issues.apache.org/jira/browse/SCB-2219 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > Infra has added Nexus authentication information to Github secrets > https://issues.apache.org/jira/browse/INFRA-21587 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2220) Adding Github actions workflow status badge to README.md
[ https://issues.apache.org/jira/browse/SCB-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2220. Fix Version/s: pack-0.7.0 Resolution: Fixed > Adding Github actions workflow status badge to README.md > > > Key: SCB-2220 > URL: https://issues.apache.org/jira/browse/SCB-2220 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2223) NEXUS's secret name is wrong
Lei Zhang created SCB-2223: -- Summary: NEXUS's secret name is wrong Key: SCB-2223 URL: https://issues.apache.org/jira/browse/SCB-2223 Project: Apache ServiceComb Issue Type: Sub-task Components: Saga Reporter: Lei Zhang Assignee: Lei Zhang Fix For: pack-0.7.0 suggestions given by infra [1] https://issues.apache.org/jira/browse/INFRA-21587?focusedCommentId=17303898=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17303898https://issues.apache.org/jira/browse/INFRA-21587?focusedCommentId=17303898=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17303898 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2222) Unstable test cases on poor performance CI
Lei Zhang created SCB-: -- Summary: Unstable test cases on poor performance CI Key: SCB- URL: https://issues.apache.org/jira/browse/SCB- Project: Apache ServiceComb Issue Type: Test Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang This test case has a high probability of timeout errors on poor performance CI https://github.com/apache/servicecomb-pack/runs/2127211795?check_suite_focus=true Running org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 17.947 sec <<< FAILURE! - in org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest resetLatencyOnReconnection(org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest) Time elapsed: 5.874 sec <<< ERROR! org.awaitility.core.ConditionTimeoutException: Condition returned by method "resetLatencyOnReconnection" in class org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest was not fulfilled within 5 seconds. at org.apache.servicecomb.pack.omega.connector.grpc.saga.SagaLoadBalancedSenderTest.resetLatencyOnReconnection(SagaLoadBalancedSenderTest.java:126) Results : Tests in error: SagaLoadBalancedSenderTest.resetLatencyOnReconnection:126 » ConditionTimeout C... Tests run: 38, Failures: 0, Errors: 1, Skipped: 0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2220) Adding Github actions workflow status badge to README.md
Lei Zhang created SCB-2220: -- Summary: Adding Github actions workflow status badge to README.md Key: SCB-2220 URL: https://issues.apache.org/jira/browse/SCB-2220 Project: Apache ServiceComb Issue Type: Sub-task Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2219) Use Github secrets to configure snapshot deploy to Nexus authentication
Lei Zhang created SCB-2219: -- Summary: Use Github secrets to configure snapshot deploy to Nexus authentication Key: SCB-2219 URL: https://issues.apache.org/jira/browse/SCB-2219 Project: Apache ServiceComb Issue Type: Sub-task Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang Infra has added Nexus authentication information to Github secrets https://issues.apache.org/jira/browse/INFRA-21587 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2205) Polishing Github actions workflow
[
https://issues.apache.org/jira/browse/SCB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2205:
---
Description:
Splits the ci.yaml to pr and push script
Temporarily disable unstable test case for poor performance CI
Update GHA script for JIRA's recommendations in the GitHub Action Status
Add Coveralls
Add scheduled deploy workflow
Remove Travis
was:
* Merge push and pull_request branches to main.yaml
* Remove the condition ${{ github.event.repository.owner.login == 'apache' }}
when push
* Add sonarcloud.yml for Sonar Scanner and trigger when push
> Polishing Github actions workflow
> -
>
> Key: SCB-2205
> URL: https://issues.apache.org/jira/browse/SCB-2205
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> Splits the ci.yaml to pr and push script
> Temporarily disable unstable test case for poor performance CI
> Update GHA script for JIRA's recommendations in the GitHub Action Status
> Add Coveralls
> Add scheduled deploy workflow
> Remove Travis
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (SCB-2204) Acceptance Tests Akka fails
[ https://issues.apache.org/jira/browse/SCB-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reopened SCB-2204: > Acceptance Tests Akka fails > --- > > Key: SCB-2204 > URL: https://issues.apache.org/jira/browse/SCB-2204 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > Failed scenarios: > src/test/resources/alpha_records_transaction_events.feature:171 # 7.Hotel > sub-transaction failed and Car sub-transaction compensate failed and global > transaction suspended > 7 Scenarios (1 failed, 6 passed) > 60 Steps (1 failed, 2 skipped, 57 passed) > 0m50.347s > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled > within 30 seconds. > at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:136) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:79) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:27) > at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:840) > at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:802) > at > org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:60) > at > org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:53) > at > org.apache.servicecomb.pack.PackStepdefs.lambda$new$7(PackStepdefs.java:101) > at ✽.Alpha records the following > events(src/test/resources/alpha_records_transaction_events.feature:178) > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 50.768 sec > <<< FAILURE! - in org.apache.servicecomb.pack.RunCucumberIT > 7.Hotel sub-transaction failed and Car sub-transaction compensate failed and > global transaction suspended(Alpha records transaction events) Time elapsed: > 31.034 sec <<< ERROR! > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled > within 30 seconds. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1622) Improve the transaction compensation mechanism
[ https://issues.apache.org/jira/browse/SCB-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-1622. Fix Version/s: pack-0.6.0 Resolution: Fixed > Improve the transaction compensation mechanism > -- > > Key: SCB-1622 > URL: https://issues.apache.org/jira/browse/SCB-1622 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.6.0 > > > Currently, Alpha compensation mechanism has some defects [1]，When the > compensation method fails, only the output log without throwing an exception. > Alpha does not know that the compensation method failed. > > Step1: Modify the OnConnected method to bidirectional streaming RPC > This will be needed for the Step2 > > Step2: Catch an exception and send a compensation result to Alpha in the > compensation method[1] on the Omega side. Alpha waits for compensation result > and catching exception after calling compensation method > 1. Received TxCompensateSucceedAckEvent: transaction completed > 2. Received TxCompensateFailedAckEvent: throw > BusinessCompensationFailureException > 3. catch other exception throw OmegaConnectedException > > Step3. Added retry and timeout rule to compensate for failures > Exceeded the number of retries or timeout will change state to suspended > [1] [https://github.com/apache/servicecomb-pack/issues/590] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-1852) Provide manual compensation for failed transactions in AlphaUI
[ https://issues.apache.org/jira/browse/SCB-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-1852. Fix Version/s: pack-0.6.0 Resolution: Fixed > Provide manual compensation for failed transactions in AlphaUI > -- > > Key: SCB-1852 > URL: https://issues.apache.org/jira/browse/SCB-1852 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.6.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2004) When the business service startup is not completed, receiving a compensation request will cause gRPC and alpha to reconnect
[
https://issues.apache.org/jira/browse/SCB-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang resolved SCB-2004.
Fix Version/s: pack-0.6.0
Resolution: Fixed
> When the business service startup is not completed, receiving a compensation
> request will cause gRPC and alpha to reconnect
> ---
>
> Key: SCB-2004
> URL: https://issues.apache.org/jira/browse/SCB-2004
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Saga
>Affects Versions: pack-0.6.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
> Fix For: pack-0.6.0
>
>
> If the Alpha's compensation call is received during the business service
> startup process, compensation failure will occasionally occur
>
> Because at startup, it will be connected to Alpha first, and then all
> compensation methods will be scanned and put to the class CallbackContext, If
> business service receives a compensation request before CallbackContext
> initialization, you will get NullPointerExceptionBecause at startup, it will
> be connected to Alpha first, and then all compensation methods will be
> scanned and put to the class CallbackContext, If business service receives a
> compensation request before CallbackContext initialization, you will get
> NullPointerException
>
> {code:java}
> public void apply(String globalTxId, String localTxId, String parentTxId,
> String callbackMethod, Object... payloads) {
> CallbackContextInternal contextInternal = contexts.get(callbackMethod);
> <- this is empty
> String oldGlobalTxId = omegaContext.globalTxId();
> String oldLocalTxId = omegaContext.localTxId();
> try {
> omegaContext.setGlobalTxId(globalTxId);
> omegaContext.setLocalTxId(localTxId);
> contextInternal.callbackMethod.invoke(contextInternal.target, payloads);
> if (omegaContext.getAlphaMetas().isAkkaEnabled()) {
> sender.send(
> new TxCompensateAckSucceedEvent(omegaContext.globalTxId(),
> omegaContext.localTxId(),
> parentTxId, callbackMethod));
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (SCB-2199) Migrate travis-ci to github workflow
[ https://issues.apache.org/jira/browse/SCB-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2199. Fix Version/s: pack-0.7.0 Resolution: Fixed > Migrate travis-ci to github workflow > > > Key: SCB-2199 > URL: https://issues.apache.org/jira/browse/SCB-2199 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (SCB-2199) Migrate travis-ci to github workflow
[ https://issues.apache.org/jira/browse/SCB-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reopened SCB-2199: > Migrate travis-ci to github workflow > > > Key: SCB-2199 > URL: https://issues.apache.org/jira/browse/SCB-2199 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2203) The version of Java (1.8.0_252) you have used to run this analysis is deprecated and Sonarcloud.io stopped accepting it
[ https://issues.apache.org/jira/browse/SCB-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2203. Resolution: Fixed > The version of Java (1.8.0_252) you have used to run this analysis is > deprecated and Sonarcloud.io stopped accepting it > --- > > Key: SCB-2203 > URL: https://issues.apache.org/jira/browse/SCB-2203 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > [ERROR] Failed to execute goal > org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar > (default-cli) on project pack: > [ERROR] > [ERROR] The version of Java (1.8.0_252) you have used to run this analysis is > deprecated and we stopped accepting it. > [ERROR] Please update to at least Java 11. You can find more information > here: https://sonarcloud.io/documentation/upcoming/ > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2199) Migrate travis-ci to github workflow
[ https://issues.apache.org/jira/browse/SCB-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2199. Resolution: Fixed > Migrate travis-ci to github workflow > > > Key: SCB-2199 > URL: https://issues.apache.org/jira/browse/SCB-2199 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SCB-2204) Acceptance Tests Akka fails
[ https://issues.apache.org/jira/browse/SCB-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang resolved SCB-2204. Fix Version/s: pack-0.7.0 Resolution: Fixed > Acceptance Tests Akka fails > --- > > Key: SCB-2204 > URL: https://issues.apache.org/jira/browse/SCB-2204 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > Fix For: pack-0.7.0 > > > Failed scenarios: > src/test/resources/alpha_records_transaction_events.feature:171 # 7.Hotel > sub-transaction failed and Car sub-transaction compensate failed and global > transaction suspended > 7 Scenarios (1 failed, 6 passed) > 60 Steps (1 failed, 2 skipped, 57 passed) > 0m50.347s > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled > within 30 seconds. > at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:136) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:79) > at > org.awaitility.core.CallableCondition.await(CallableCondition.java:27) > at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:840) > at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:802) > at > org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:60) > at > org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:53) > at > org.apache.servicecomb.pack.PackStepdefs.lambda$new$7(PackStepdefs.java:101) > at ✽.Alpha records the following > events(src/test/resources/alpha_records_transaction_events.feature:178) > Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 50.768 sec > <<< FAILURE! - in org.apache.servicecomb.pack.RunCucumberIT > 7.Hotel sub-transaction failed and Car sub-transaction compensate failed and > global transaction suspended(Alpha records transaction events) Time elapsed: > 31.034 sec <<< ERROR! > org.awaitility.core.ConditionTimeoutException: Condition with lambda > expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled > within 30 seconds. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2205) Polishing Github actions workflow
[
https://issues.apache.org/jira/browse/SCB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2205:
---
Summary: Polishing Github actions workflow (was: Polishing Github
operation workflow)
> Polishing Github actions workflow
> -
>
> Key: SCB-2205
> URL: https://issues.apache.org/jira/browse/SCB-2205
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> * Merge push and pull_request branches to main.yaml
> * Remove the condition ${{ github.event.repository.owner.login == 'apache' }}
> when push
> * Add sonarcloud.yml for Sonar Scanner and trigger when push
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SCB-2205) Polishing Github operation workflow
[
https://issues.apache.org/jira/browse/SCB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2205:
---
Description:
* Merge push and pull_request branches to main.yaml
* Remove the condition ${{ github.event.repository.owner.login == 'apache' }}
when push
* Add sonarcloud.yml for Sonar Scanner and trigger when push
> Polishing Github operation workflow
> ---
>
> Key: SCB-2205
> URL: https://issues.apache.org/jira/browse/SCB-2205
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
>Affects Versions: pack-0.7.0
>Reporter: Lei Zhang
>Assignee: Lei Zhang
>Priority: Major
>
> * Merge push and pull_request branches to main.yaml
> * Remove the condition ${{ github.event.repository.owner.login == 'apache' }}
> when push
> * Add sonarcloud.yml for Sonar Scanner and trigger when push
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SCB-2205) Polishing Github operation workflow
[ https://issues.apache.org/jira/browse/SCB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2205: --- Summary: Polishing Github operation workflow (was: Fix pull request and push trigger condition) > Polishing Github operation workflow > --- > > Key: SCB-2205 > URL: https://issues.apache.org/jira/browse/SCB-2205 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2205) Fix pull request and push trigger condition
Lei Zhang created SCB-2205: -- Summary: Fix pull request and push trigger condition Key: SCB-2205 URL: https://issues.apache.org/jira/browse/SCB-2205 Project: Apache ServiceComb Issue Type: Task Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang Assignee: Lei Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2204) Acceptance Tests Akka fails
Lei Zhang created SCB-2204: -- Summary: Acceptance Tests Akka fails Key: SCB-2204 URL: https://issues.apache.org/jira/browse/SCB-2204 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: pack-0.6.0 Reporter: Lei Zhang Assignee: Lei Zhang Failed scenarios: src/test/resources/alpha_records_transaction_events.feature:171 # 7.Hotel sub-transaction failed and Car sub-transaction compensate failed and global transaction suspended 7 Scenarios (1 failed, 6 passed) 60 Steps (1 failed, 2 skipped, 57 passed) 0m50.347s org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled within 30 seconds. at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:136) at org.awaitility.core.CallableCondition.await(CallableCondition.java:79) at org.awaitility.core.CallableCondition.await(CallableCondition.java:27) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:840) at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:802) at org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:60) at org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:53) at org.apache.servicecomb.pack.PackStepdefs.lambda$new$7(PackStepdefs.java:101) at ✽.Alpha records the following events(src/test/resources/alpha_records_transaction_events.feature:178) Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 50.768 sec <<< FAILURE! - in org.apache.servicecomb.pack.RunCucumberIT 7.Hotel sub-transaction failed and Car sub-transaction compensate failed and global transaction suspended(Alpha records transaction events) Time elapsed: 31.034 sec <<< ERROR! org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in org.apache.servicecomb.pack.StepDefSupport was not fulfilled within 30 seconds. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SCB-2203) The version of Java (1.8.0_252) you have used to run this analysis is deprecated and Sonarcloud.io stopped accepting it
[ https://issues.apache.org/jira/browse/SCB-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reassigned SCB-2203: -- Assignee: Lei Zhang > The version of Java (1.8.0_252) you have used to run this analysis is > deprecated and Sonarcloud.io stopped accepting it > --- > > Key: SCB-2203 > URL: https://issues.apache.org/jira/browse/SCB-2203 > Project: Apache ServiceComb > Issue Type: Improvement >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > > [ERROR] Failed to execute goal > org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar > (default-cli) on project pack: > [ERROR] > [ERROR] The version of Java (1.8.0_252) you have used to run this analysis is > deprecated and we stopped accepting it. > [ERROR] Please update to at least Java 11. You can find more information > here: https://sonarcloud.io/documentation/upcoming/ > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2203) The version of Java (1.8.0_252) you have used to run this analysis is deprecated and Sonarcloud.io stopped accepting it
[ https://issues.apache.org/jira/browse/SCB-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2203: --- Summary: The version of Java (1.8.0_252) you have used to run this analysis is deprecated and Sonarcloud.io stopped accepting it (was: Java (1.8.0_252) you have used to run this analysis is deprecated) > The version of Java (1.8.0_252) you have used to run this analysis is > deprecated and Sonarcloud.io stopped accepting it > --- > > Key: SCB-2203 > URL: https://issues.apache.org/jira/browse/SCB-2203 > Project: Apache ServiceComb > Issue Type: Improvement >Reporter: Lei Zhang >Priority: Major > > [ERROR] Failed to execute goal > org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar > (default-cli) on project pack: > [ERROR] > [ERROR] The version of Java (1.8.0_252) you have used to run this analysis is > deprecated and we stopped accepting it. > [ERROR] Please update to at least Java 11. You can find more information > here: https://sonarcloud.io/documentation/upcoming/ > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2203) Java (1.8.0_252) you have used to run this analysis is deprecated
[ https://issues.apache.org/jira/browse/SCB-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2203: --- Summary: Java (1.8.0_252) you have used to run this analysis is deprecated (was: Sonarcloud.io Java (1.8.0_252) you have used to run this analysis is deprecated) > Java (1.8.0_252) you have used to run this analysis is deprecated > - > > Key: SCB-2203 > URL: https://issues.apache.org/jira/browse/SCB-2203 > Project: Apache ServiceComb > Issue Type: Improvement >Reporter: Lei Zhang >Priority: Major > > [ERROR] Failed to execute goal > org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar > (default-cli) on project pack: > [ERROR] > [ERROR] The version of Java (1.8.0_252) you have used to run this analysis is > deprecated and we stopped accepting it. > [ERROR] Please update to at least Java 11. You can find more information > here: https://sonarcloud.io/documentation/upcoming/ > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2201) Acceptance tests occasionally fails in CI
Lei Zhang created SCB-2201:
--
Summary: Acceptance tests occasionally fails in CI
Key: SCB-2201
URL: https://issues.apache.org/jira/browse/SCB-2201
Project: Apache ServiceComb
Issue Type: Improvement
Components: Saga
Affects Versions: pack-0.6.0
Reporter: Lei Zhang
021-03-02T15:13:13.3306582Z When User UserA requests to order 2 units of
ProductA with unit price 2 success # PackStepdefs.java:65
2021-03-02T15:13:13.4457584Z alpha> 2021-03-02 15:13:13.443 INFO ba04d452e180
--- [nio-8090-exec-5] o.a.s.p.a.s.t.AlphaTccEventController: Get the events
request
2021-03-02T15:13:13.4502117Z alpha> 2021-03-02 15:13:13.447 INFO ba04d452e180
--- [nio-8090-exec-5] o.a.s.p.a.s.t.AlphaTccEventController: Get the event
size 8
2021-03-02T15:13:13.4570031Z 15:13:13.456 [main] INFO
org.apache.servicecomb.pack.StepDefSupport - Retrieved data
[{serviceName=ordering, txType=STARTED}, {serviceName=inventory,
txType=P_TX_STATED}, {serviceName=inventory, txType=P_TX_ENDED},
{serviceName=payment, txType=P_TX_STATED}, {serviceName=payment,
txType=P_TX_ENDED}, {serviceName=ordering, txType=ENDED}, {serviceName=payment,
txType=COORDINATED}, {serviceName=inventory, txType=COORDINATED}] from service
2021-03-02T15:13:13.4629108Z Then Alpha records the following events
# PackStepdefs.java:85
2021-03-02T15:13:13.4638659Z cucumber.runtime.table.TableDiffException:
Tables were not identical:
2021-03-02T15:13:13.4639806Z | serviceName | txType |
2021-03-02T15:13:13.4640429Z | ordering| STARTED |
2021-03-02T15:13:13.4641082Z | inventory | P_TX_STATED |
2021-03-02T15:13:13.4641719Z | inventory | P_TX_ENDED |
2021-03-02T15:13:13.4642129Z | payment | P_TX_STATED |
2021-03-02T15:13:13.4642570Z | payment | P_TX_ENDED |
2021-03-02T15:13:13.4642939Z | ordering| ENDED |
2021-03-02T15:13:13.4643645Z - | inventory | COORDINATED |
2021-03-02T15:13:13.4644098Z | payment | COORDINATED |
2021-03-02T15:13:13.4644518Z + | inventory | COORDINATED |
2021-03-02T15:13:13.4644796Z
2021-03-02T15:13:13.4645714Zat
cucumber.runtime.table.TableDiffer.calculateDiffs(TableDiffer.java:41)
2021-03-02T15:13:13.4646889Zat
cucumber.api.DataTable.diff(DataTable.java:180)
2021-03-02T15:13:13.4648203Zat
org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:77)
2021-03-02T15:13:13.4651920Zat
org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:53)
2021-03-02T15:13:13.4653617Zat
org.apache.servicecomb.pack.PackStepdefs.lambda$new$6(PackStepdefs.java:91)
2021-03-02T15:13:13.4656175Zat ✽.Alpha records the following
events(src/test/resources/pack_tcc_confirm_scenario.feature:26)
2021-03-02T15:13:13.4656756Z
2021-03-02T15:13:13.4657360Z And Inventory Service contains the following
booking orders # PackStepdefs.java:94
2021-03-02T15:13:13.4658908Z And Payment Service contains the following
booking orders # PackStepdefs.java:98
2021-03-02T15:13:13.4660493Z 15:13:13.465 [main] INFO
org.apache.servicecomb.pack.PackStepdefs - Cleaning up services
2021-03-02T15:13:13.5379644Z
2021-03-02T15:13:13.5383278Z Failed scenarios:
2021-03-02T15:13:13.5387094Z
src/test/resources/pack_tcc_confirm_scenario.feature:18 # Everything is normal
2021-03-02T15:13:13.5389875Z
2021-03-02T15:13:13.5409913Z 2 Scenarios (1 failed, 1 passed)
2021-03-02T15:13:13.5435380Z 16 Steps (1 failed, 2 skipped, 13 passed)
2021-03-02T15:13:13.5436127Z 0m9.546s
2021-03-02T15:13:13.5436567Z
2021-03-02T15:13:13.5437553Z cucumber.runtime.table.TableDiffException: Tables
were not identical:
2021-03-02T15:13:13.5438924Z | serviceName | txType |
2021-03-02T15:13:13.5440100Z | ordering| STARTED |
2021-03-02T15:13:13.5480498Z | inventory | P_TX_STATED |
2021-03-02T15:13:13.5481247Z | inventory | P_TX_ENDED |
2021-03-02T15:13:13.5482043Z | payment | P_TX_STATED |
2021-03-02T15:13:13.5482556Z | payment | P_TX_ENDED |
2021-03-02T15:13:13.5483057Z | ordering| ENDED |
2021-03-02T15:13:13.5484133Z - | inventory | COORDINATED |
2021-03-02T15:13:13.5484978Z | payment | COORDINATED |
2021-03-02T15:13:13.5485524Z + | inventory | COORDINATED |
2021-03-02T15:13:13.5485917Z
2021-03-02T15:13:13.5486936Zat
cucumber.runtime.table.TableDiffer.calculateDiffs(TableDiffer.java:41)
2021-03-02T15:13:13.5488245Zat
cucumber.api.DataTable.diff(DataTable.java:180)
2021-03-02T15:13:13.5489670Zat
org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:77)
2021-03-02T15:13:13.5491631Zat
org.apache.servicecomb.pack.StepDefSupport.dataMatches(StepDefSupport.java:53)
[jira] [Created] (SCB-2200) Hibernate Validator Relocation Artifacts
Lei Zhang created SCB-2200: -- Summary: Hibernate Validator Relocation Artifacts Key: SCB-2200 URL: https://issues.apache.org/jira/browse/SCB-2200 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: pack-0.6.0 Reporter: Lei Zhang The artifact org.hibernate:hibernate-validator:jar:6.0.2.Final has been relocated to org.hibernate.validator:hibernate-validator:jar:6.0.2.Final in the saga-servicecomb-demo module -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SCB-2199) Migrate travis-ci to github workflow
[ https://issues.apache.org/jira/browse/SCB-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang reassigned SCB-2199: -- Assignee: Lei Zhang > Migrate travis-ci to github workflow > > > Key: SCB-2199 > URL: https://issues.apache.org/jira/browse/SCB-2199 > Project: Apache ServiceComb > Issue Type: Task > Components: Saga >Affects Versions: pack-0.6.0 >Reporter: Lei Zhang >Assignee: Lei Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2199) Migrate travis-ci to github workflowv
Lei Zhang created SCB-2199: -- Summary: Migrate travis-ci to github workflowv Key: SCB-2199 URL: https://issues.apache.org/jira/browse/SCB-2199 Project: Apache ServiceComb Issue Type: Task Components: Saga Affects Versions: pack-0.6.0 Reporter: Lei Zhang -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2023) Move to send coveralls after success
[ https://issues.apache.org/jira/browse/SCB-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Zhang updated SCB-2023: --- Labels: build (was: ) > Move to send coveralls after success > > > Key: SCB-2023 > URL: https://issues.apache.org/jira/browse/SCB-2023 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: pack-0.7.0 >Reporter: Lei Zhang >Priority: Major > Labels: build > > solution: > [https://github.com/lemurheavy/coveralls-public/issues/1264] > > issue: > [https://travis-ci.org/github/apache/servicecomb-pack/builds/700942494] > [ERROR] Failed to execute goal > org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report (default-cli) on > project pack: Processing of input or output data failed: Report submission to > Coveralls API failed with HTTP status 422: Unprocessable Entity > (service_job_id (700942498) must be unique for Travis Jobs not supplying a > Coveralls Repo Token) -> [Help 1] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SCB-2023) Move to send coveralls after success
Lei Zhang created SCB-2023: -- Summary: Move to send coveralls after success Key: SCB-2023 URL: https://issues.apache.org/jira/browse/SCB-2023 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: pack-0.7.0 Reporter: Lei Zhang solution: [https://github.com/lemurheavy/coveralls-public/issues/1264] issue: [https://travis-ci.org/github/apache/servicecomb-pack/builds/700942494] [ERROR] Failed to execute goal org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report (default-cli) on project pack: Processing of input or output data failed: Report submission to Coveralls API failed with HTTP status 422: Unprocessable Entity (service_job_id (700942498) must be unique for Travis Jobs not supplying a Coveralls Repo Token) -> [Help 1] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SCB-2004) When the business service startup is not completed, receiving a compensation request will cause gRPC and alpha to reconnect
[
https://issues.apache.org/jira/browse/SCB-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Zhang updated SCB-2004:
---
Description:
If the Alpha's compensation call is received during the business service
startup process, compensation failure will occasionally occur
Because at startup, it will be connected to Alpha first, and then all
compensation methods will be scanned and put to the class CallbackContext, If
business service receives a compensation request before CallbackContext
initialization, you will get NullPointerExceptionBecause at startup, it will be
connected to Alpha first, and then all compensation methods will be scanned and
put to the class CallbackContext, If business service receives a compensation
request before CallbackContext initialization, you will get NullPointerException
{code:java}
public void apply(String globalTxId, String localTxId, String parentTxId,
String callbackMethod, Object... payloads) {
CallbackContextInternal contextInternal = contexts.get(callbackMethod);
<- this is empty
String oldGlobalTxId = omegaContext.globalTxId();
String oldLocalTxId = omegaContext.localTxId();
try {
omegaContext.setGlobalTxId(globalTxId);
omegaContext.setLocalTxId(localTxId);
contextInternal.callbackMethod.invoke(contextInternal.target, payloads);
if (omegaContext.getAlphaMetas().isAkkaEnabled()) {
sender.send(
new TxCompensateAckSucceedEvent(omegaContext.globalTxId(),
omegaContext.localTxId(),
parentTxId, callbackMethod));
}
{code}
was:
If the Alpha's compensation call is received during the business service
startup process, compensation failure will occasionally occur
Because at startup, it will be connected to Alpha first, and then all
compensation methods will be scanned and put to the class CallbackContext, If
business service receives a compensation request before CallbackContext
initialization, you will get NullPointerExceptionBecause at startup, it will be
connected to Alpha first, and then all compensation methods will be scanned and
put to the class CallbackContext, If business service receives a compensation
request before CallbackContext initialization, you will get NullPointerException
{code:java}
public void apply(String globalTxId, String localTxId, String parentTxId,
String callbackMethod, Object... payloads) {
CallbackContextInternal contextInternal = contexts.get(callbackMethod);
<- this is empty
String oldGlobalTxId = omegaContext.globalTxId();
String oldLocalTxId = omegaContext.localTxId();
try {
omegaContext.setGlobalTxId(globalTxId);
omegaContext.setLocalTxId(localTxId);
contextInternal.callbackMethod.invoke(contextInternal.target, payloads);
if (omegaContext.getAlphaMetas().isAkkaEnabled()) {
sender.send(
new TxCompensateAckSucceedEvent(omegaContext.globalTxId(),
omegaContext.localTxId(),
parentTxId, callbackMethod));
}
{code}
> When the business service startup is not completed, receiving a compensation
> request will cause gRPC and alpha to reconnect
> ---
>
> Key: SCB-2004
> URL: https://issues.apache.org/jira/browse/SCB-2004
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Saga
>Affects Versions: pack-0.6.0
>Reporter: Lei Zhang
>Priority: Major
>
> If the Alpha's compensation call is received during the business service
> startup process, compensation failure will occasionally occur
>
> Because at startup, it will be connected to Alpha first, and then all
> compensation methods will be scanned and put to the class CallbackContext, If
> business service receives a compensation request before CallbackContext
> initialization, you will get NullPointerExceptionBecause at startup, it will
> be connected to Alpha first, and then all compensation methods will be
> scanned and put to the class CallbackContext, If business service receives a
> compensation request before CallbackContext initialization, you will get
> NullPointerException
>
> {code:java}
> public void apply(String globalTxId, String localTxId, String parentTxId,
> String callbackMethod, Object... payloads) {
> CallbackContextInternal contextInternal = contexts.get(callbackMethod);
> <- this is empty
> String oldGlobalTxId = omegaContext.globalTxId();
> String oldLocalTxId = omegaContext.localTxId();
> try {
> omegaContext.setGlobalTxId(globalTxId);
> omegaContext.setLocalTxId(localTxId);
> contextInternal.callbackMethod.invoke(contextInternal.target, payloads);
> if (omegaContext.getAlphaMetas().isAkkaEnabled()) {
> sender.send(
>
