AsperforMias opened a new issue, #3779:
URL: https://github.com/apache/dubbo-go/issues/3779

   ### What happened?
   
   Expected: the Integration Test job on `ubuntu-latest` finishes the 
dubbo-go-samples suite, including `java_interop/service_discovery/service`, and 
the job succeeds.
   
   Actual: since the GitHub-hosted runner image behind `ubuntu-latest` moved 
from `ubuntu-24.04` to `ubuntu-26.04`, that job is cancelled at its 30 minute 
limit. The Java client in `java_interop/service_discovery/service` logs 
`NoClassDefFoundError: com/alibaba/fastjson/JSONException` and the Maven 
process does not exit.
   
   Error (first red run, 
[39619613061](https://github.com/apache/dubbo-go/actions/runs/39619613061), job 
log `2026-10-22T05:19:28Z`):
   
   ```
   java.lang.NoClassDefFoundError: com/alibaba/fastjson/JSONException
        at java.util.ServiceLoader.getConstructor(ServiceLoader.java:623)
        at 
java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1111)
        at 
org.apache.dubbo.common.utils.JsonUtils.loadExtensions(JsonUtils.java:81)
        at 
org.apache.dubbo.common.utils.JsonUtils.toJavaObject(JsonUtils.java:106)
        at 
org.apache.dubbo.registry.client.metadata.StandardMetadataServiceURLBuilder.getMetadataServiceURLsParams(StandardMetadataServiceURLBuilder.java:196)
   Caused by: java.lang.ClassNotFoundException: 
com.alibaba.fastjson.JSONException
   ```
   
   The same stack is in 
[40082838939](https://github.com/apache/dubbo-go/actions/runs/40082838939) at 
`2026-10-24T09:57:50Z`. There is no Maven `BUILD FAILURE` after it. The next 
workflow line is `##[error]The operation was canceled` at the job timeout 
(`05:28:40Z` on the first red run, `10:10:28Z` on 40082838939).
   
   Severity: CI blocker for the Integration Test job. It does not change 
dubbo-go library code, and it does not change release artifacts. Unit Test and 
Check License Header on these runs succeeded.
   
   Impact scope:
   
   - Job: `Integration Test` in `.github/workflows/github-actions.yml` only. 
That job has `runs-on: ubuntu-latest`, `timeout-minutes: 30`, 
`./.github/actions/setup-go`, and no `actions/setup-java`.
   - Every `pull_request` run of this workflow since the image move has 
cancelled that job. Last success: 
[39560565003](https://github.com/apache/dubbo-go/actions/runs/39560565003) 
(created 2026-10-21T07:14:10Z, Integration Test 08:51:16Z–09:09:52Z). First 
cancel: 
[39619613061](https://github.com/apache/dubbo-go/actions/runs/39619613061). 
Same cancel on 
[39757462666](https://github.com/apache/dubbo-go/actions/runs/39757462666) 
(README only), 
[40038682961](https://github.com/apache/dubbo-go/actions/runs/40038682961) 
(#3773), and 
[40082838939](https://github.com/apache/dubbo-go/actions/runs/40082838939) 
(#3778). Unit Test and Check License Header succeeded on all four.
   - This workflow does not run on push to `develop` (`on.push` is `main`, 
`release-*`, `feature-*`). The failure shows up on pull requests targeting the 
repository, including PRs into `develop`.
   - Not a user-runtime bug and not a release-artifact bug. The Go code under 
test is not what throws. The throw is in Dubbo Java 3.3.6, loaded by the 
samples Java client.
   - dubbo-go-samples CI is not this failure. That workflow already runs 
`actions/setup-java@v4` with Temurin 17.
   
   Runner evidence, same Actions software `Version: 20261012.601` on both jobs:
   
   | Run | Image line | JDK / Maven from the job log |
   | --- | --- | --- |
   | 39560565003 | `Image: ubuntu-24.04` / `Version: 20261012.334.1` | 
`java.home=/usr/lib/jvm/temurin-17-jdk-amd64`, Maven 
`/usr/share/apache-maven-3.10.0`, `Thread.java:840` |
   | 39619613061 | `Image: ubuntu-26.04` / `Version: 20261012.163.1` | 
`java.home=/usr/lib/jvm/temurin-25-jdk-amd64`, Maven 
`/usr/share/apache-maven-3.9.15`, `Thread.java:1474`, 
`exec-maven-plugin-3.6.4.jar` |
   
   The two PR heads differ by one commit, `8ff7866c` `ci: run OpenAPI generator 
tests`, which touches only `.github/workflows/tools.yml`. `develop` and 
`dubbo-go-samples` `main` have no commits in 
`2026-10-21T07:14Z`–`2026-10-22T05:30Z` that touch this path. Both runs clone 
`dubbo-go-samples` branch `main`.
   
   Cause: Dubbo 3.3.6 `JsonUtils.loadExtensions` calls `Iterator.hasNext()` 
outside its `try`. On JDK 25, `ServiceLoader.getConstructor` resolves 
`FastJsonImpl`'s dependency on `com.alibaba.fastjson.JSONException` and throws 
`NoClassDefFoundError` (JDK-8350481). The samples service client has fastjson2 
(via `nacos-client`) and does not have fastjson 1. The interface-level sample 
`java_interop/service_discovery/interface` still prints 
`Greeting:Mamba!!!!!!!!!!!!` on the JDK 25 runner (`05:17:57Z` in 39619613061); 
its registry is `registry.type=interface` and does not build that metadata URL. 
apache/dubbo#15754 wraps `hasNext()` in the `try`. It merged to branch `3.3` on 
2025-11-06 (`3720471e`) and is not in tag `dubbo-3.3.6`. Maven Central 
`org.apache.dubbo:dubbo` `maven-metadata.xml` still has 
`<latest>3.3.6</latest>`. apache/dubbo#16295 is the same loader bug with gson 
(`JsonSyntaxException`), and it is still open.
   
   The client does not exit because `run.sh` uses `mvn exec:java` with 
`-Dexec.cleanupDaemonThreads=false`, and exec-maven-plugin 3.6.4 
`joinNonDaemonThreads` (`AbstractExecJavaBase.java:331`) calls `Thread.join(0)` 
on non-daemon threads before it reports the mojo failure. Dubbo 3.3.6 
`NamedThreadFactory(String)` creates `Dubbo-framework-registry-notification-*` 
with `daemon=false`. samples `integrate_test.sh` sets 
`GO_CLIENT_TIMEOUT_SECONDS` (default 90) and does not set a timeout around the 
Java client. The 30 minute cap is the job `timeout-minutes`.
   
   This is independent of the Go 1.27 change. 
`apache/skywalking-eyes/header@main` (`7f98a36a`) runs `actions/setup-go` with 
`go-version: "1.27"`. In this repository that action is only the `Check License 
Header` job. Jobs do not share a `PATH`. On run 40082838939 the license job log 
says `Setup go version spec 1.27` and `go version go1.27.3 linux/amd64` (job 
120839812966). The Integration Test job on the same run says `Setup go version 
spec 1.25.0` and `go version go1.25.0 linux/amd64`. The Go 1.27 jsonrpc crash 
is apache/dubbo-go#3777 / #3778. It is not what cancelled these Integration 
Test jobs.
   
   Why this repository, and not dubbo-go-samples: samples CI already pins 
Temurin 17, so the image's default JDK does not reach its Maven build. The job 
that is cancelled never calls `setup-java`. Pinning Java here is the change 
that selects the JDK for this job. A samples-only change would leave this job 
on the image JDK.
   
   Merge order. These are two separate external changes.
   
   1. JDK 25 on `ubuntu-latest` cancels dubbo-go Integration Test. Land the 
`setup-java` Temurin 17 change on `develop` first. After that, #3778 needs a 
new workflow run (update the branch onto `develop`). Re-running 
[40082838939](https://github.com/apache/dubbo-go/actions/runs/40082838939) uses 
the workflow file from that run, which has no `setup-java`, so the same cancel 
will happen again. #3778's Integration Test log is `go1.25.0`; its failure is 
this JDK 25 cancel, not the json v2 crash. Its Unit Test job already succeeded.
   2. Then update and merge #3778, which fixes #3777 for callers on Go 1.27.
   3. samples, separately: #1156 first. Its Build And Integration already 
passed 
([40082624365](https://github.com/apache/dubbo-go-samples/actions/runs/40082624365),
 22m38s). Then update #1155 so it picks up that workflow. #1155 run 
[40075757874](https://github.com/apache/dubbo-go-samples/actions/runs/40075757874)
 prints `go version go1.25.0` at "Check tool versions", then `go version 
go1.27.3` inside "Check license header", then the integration step fails 
dialing the jsonrpc server (`connection refused` on `127.0.0.1:20001` and 
`:20002`). That is the Go 1.27 leak, not JDK 25. samples CI already has 
`setup-java` Temurin 17.
   
   ### How can we reproduce it?
   
   1. Open a pull request against apache/dubbo-go without `actions/setup-java` 
on the Integration Test job, on a runner whose image is `ubuntu-26.04`.
   2. Wait until `java_interop/service_discovery/service` starts its Java 
client (`mvn exec:java`, Dubbo 3.3.6).
   3. The client logs `NoClassDefFoundError: 
com/alibaba/fastjson/JSONException` from `JsonUtils.loadExtensions` and does 
not exit.
   4. The job stays silent until `timeout-minutes: 30`, then GitHub cancels it.
   
   Recorded runs: success 
[39560565003](https://github.com/apache/dubbo-go/actions/runs/39560565003) 
(`ubuntu-24.04`, Temurin 17, `Greeting:Mamba!!!!!!!!!!!!` at `09:07:29Z`, `> 
ok: java_interop/service_discovery/service` at `09:08:35Z`); cancel 
[39619613061](https://github.com/apache/dubbo-go/actions/runs/39619613061).
   
   ### Environment
   
   - Repository: apache/dubbo-go `develop` at 
`97666ec89ab0c4a0fe949778f0f9a52d3b9b4f1b`. `go.mod` says `go 1.25.0`.
   - Workflow: `.github/workflows/github-actions.yml` Integration Test. 
`runs-on: ubuntu-latest`. No `setup-java` on that job. Setup Go is 
`./.github/actions/setup-go` (`go-version-file: go.mod`).
   - Runner image at the break: `ubuntu-24.04` `20261012.334.1` then 
`ubuntu-26.04` `20261012.163.1`.
   - JDK on the red job: Temurin 25 (`/usr/lib/jvm/temurin-25-jdk-amd64`). 
Maven on that image: 3.9.15. exec-maven-plugin resolved as 3.6.4.
   - Samples clone: `apache/dubbo-go-samples` branch `main` 
(`integrate_test.sh` in dubbo-go). Java client `dubbo.version` 3.3.6.
   - Dubbo fix: apache/dubbo#15754, merged to `3.3`, not in the 3.3.6 release. 
Maven Central latest release of `org.apache.dubbo:dubbo` is 3.3.6.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to