* Make use of multi-thread builds of maven
* Bump up maven version to get rid of parallel build bug
* Apply the same to E2E tests
* Apply the same to JavaDoc task
* Revert E2E settings
* Add maven tuning opts
* Increase maven fork process memory
* Override ES settings in FAQ
* Resend traffic data when invalid
* Remove unsupported ES setting
* Use seperated buffer directory and remove unnecessary web app 2
* Change OAL generator tool to runtime.
Step 1. change project structure. API links and maven pom.
* Part of metrics class generation
* Metrcis class generated.
* Set up the basic structure of new OAL engine.
* Finish metrics generation.
* Support dispatcher generation.
* Format codes.
* Generate dispatcher all methods.
* Implement disable in hardcode.
* Clear up
* Fix compile startup.
* Update license and document of new OAL engine.
* Fix rat.
* Disable class output in default
* Copy from @kezhenxu94 's test PR, https://github.com/apache/skywalking/pull/3110
* Wait for the mount command to finish
* improve ContextManager.stopSpan and awaitFinishAsync performance: call ThreadLocal only once
For the [JMH benchmark test](https://gitlab.com/qxo1/Common-JMH-benchmark/-/jobs/251025992) :
On gitlab CI(java 8): call ThreadLocal once vs twice fast over 10%
My T480 java 8 : fast over 40%; java 11: fast over 50%;
[The JMH benchmark code ](https://github.com/qxo/Common-JMH-benchmark/blob/master/src/main/java/test/ThreadLocalGetXTimeBenchmark.java)
* Update apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/context/ContextManager.java
Co-Authored-By: kezhenxu94 <kezhenxu94@163.com>
* Update apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/context/ContextManager.java
Co-Authored-By: kezhenxu94 <kezhenxu94@163.com>
* Update apm-sniffer/apm-agent-core/src/main/java/org/apache/skywalking/apm/agent/core/context/ContextManager.java
Co-Authored-By: 吴晟 Wu Sheng <wu.sheng@foxmail.com>
* Set up 10 seconds deadline after gRPC client sending
* The duration of deadline contains three segments: connecting,
request and response
For blocking stub, I just set deadline before invoke service. For
bi-streaming stub, I found all of them are used as a blocking style,
that after getting streaming response client stub just close current
streaming. Base on above reality, I pick the same way as blocking one.
* etcd configuration is not implemented and the provider definition is copied from cluster management, which could cause multiple loading by module manager.
* Fix a missing delete.
e2e test setup. cc @hanahmily @peng-yongsheng @IanCao @zhaoyuguang @JaredTan95
# e2e test case
One single standalone Spring service, accessing H2 database. This service has been installed the agent.
OAP runs in single mode with H2 storage too.
The e2e test will verify the results through GraphQL query
1. Traces exist.
2. Service/Service Instance/Endpoint exist and have expected metrics.
3. Topology exists and match expected.
kezhenxu94
彭勇升 pengys
吴晟 Wu Sheng
于玉桔
qxo
qxo
zhangwei
Daming
Jared Tan
li.can
kezhenxu94
Alan Lau
evanxuhe
zygfengyuwuzu
Gao Hongtao
zhousiliang163
Xin,Zhang
Roshi