New Relic agent is installed but never attached to the JVM (v5.0.4 and later)

未关闭
#1,542 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@stokpop 已经在做这个了。

开始于 2026年11月12日。

  • #714 来自 @stokpop —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
go, java

调研方向

Start with the New Relic framework code in new_relic.go and the 9.x entries in manifest.yml, which show the bare agent jar with a .zip name. The fix that matters is upstream in buildpacks-ci, where the watcher downloads the wrong artifact, and an open pull request (#714) already exists for this. Done means an integration test that checks newrelic.jar and the license key in the running JVM's arguments, and passes for New Relic 9.x.

由索引模型根据 Issue 内容生成。

描述

With a newrelic service binding, staging succeeds and the log says the agent is installed, but the running JVM has no New Relic -javaagent and no license key. The only hint is a warning during finalize:

WARNING Failed to finalize framework New Relic Agent: failed to locate newrelic.jar: newrelic.jar not found in /tmp/contents.../deps/0/new_relic_agent

Datadog and SkyWalking bound to the same app are present in the JVM arguments, New Relic is not.

How it was found: while writing an integration test that binds several agents at once (New Relic, Datadog, SkyWalking) and checks the running JVM's arguments instead of only the staging log. This is part of an upcoming improvement of the integration tests, so that every framework is verified in the running JVM. So far 17 of the 23 frameworks that attach an agent (-javaagent or -agentpath) have been checked this way: 16 pass and New Relic is the only one that fails. The other 6 are not checked: AppDynamics, Checkmarx, Introscope and Riverbed are skipped because they need vendor credentials, and Seeker and Java Memory Assistant have no test.

Cause: new_relic.go expects newrelic/newrelic.jar inside the unpacked dependency, as in the vendor distribution newrelic-java-<version>.zip (used up to 8.15.0). The 9.x dependencies in manifest.yml (9.2.0 to 9.5.0, first shipped in v5.0.4) are the bare agent jar with a .zip name. libbuildpack unpacks .zip dependencies, so the jar is exploded and no newrelic.jar remains.

The pipeline produced this: the newrelic watcher in buildpacks-ci downloads newrelic-agent-<version>.jar (cloudfoundry/buildpacks-ci#633), while the binary-builder recipe names the artifact newrelic-java-<version>.zip (cloudfoundry/binary-builder#111). The recipe never opens the file, so the .zip extension comes from its expected file name, not from the content.

Fix: make the watcher download newrelic-java-<version>.zip. The distribution exists for 9.2.0, 9.4.0 and 9.5.0 and contains newrelic/newrelic.jar (the same 41,319,404 bytes as the published bare jar for 9.5.0). I plan to open that PR in buildpacks-ci, plus an integration test here that asserts newrelic.jar and the license key in the running JVM's arguments. The corrected artifact is published when the pipeline next builds a New Relic version; I have not checked whether 9.5.0 can be rebuilt on demand.

Why it went unnoticed: the integration test only asserts New Relic Agent in the staging log, which is printed before the failing step. A failed Finalize is only a warning, while Supply failures are fatal. Making Finalize failures fatal is a separate behaviour change worth discussing.

v4: the Ruby buildpack used a bare jar (download_jar) and added -javaagent directly, so this worked.

主要语言
Go
星标
455
派生
2.5k
平均合并
22 小时 9 分钟
30 天内合并 PR
69

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cloudfoundry/java-buildpack 的其他 Issue

查看 cloudfoundry/java-buildpack 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。