844: JMX attaching of Subject does not work when security manager not
allowed
-
Commit messages:
- Backport bcf4bb4882e06d8c52f6eb4e9c4e027ba0622c5f
Changes: https://git.openjdk.org/jdk/pull/19810/files
Webrev: https://webrevs.openjdk.org/?repo=jdk=19810=00
Issue:
On Thu, 20 Jun 2024 11:58:23 GMT, Matthias Baesken wrote:
> The following issue has been observed when running
> serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorThreadTest (and some
> other :tier1 tests)
> on Linux with ubsan enabled binaries :
>
>
On Thu, 20 Jun 2024 12:06:43 GMT, Severin Gehwolf wrote:
>> Please review this enhancement to the container detection code which allows
>> it to figure out whether the JVM is actually running inside a container
>> (`podman`, `docker`, `crio`), or with some other means that enforces
>>
On Thu, 20 Jun 2024 16:30:30 GMT, Coleen Phillimore wrote:
> If the default is to not keep the CLD alive, I don't like that we need the
> details of the side effect in the name. Just call it classes_do, etc. I don't
> care about no-keepalive in all these callers, if that's the right answer for
On Wed, 19 Jun 2024 15:06:25 GMT, Axel Boldt-Christmas
wrote:
>> ClassLoaderDataGraph provides APIs for walking different metadata. All the
>> iterators which are not designed to be used by the GC also keep the holder
>> of the CLDs alive and by extensions keeps all metadata alive. This is
On Fri, 14 Jun 2024 16:37:15 GMT, Leonid Mesnik wrote:
> The vmTestbase/vm/share is a shared test library for vmTestbase tests. This
> library contains a lot of code that is used by only by small number of tests
> or not used at all. There are no plans to actively develop new tests in
>
On Fri, 14 Jun 2024 22:08:17 GMT, Leonid Mesnik wrote:
> The nsk jdi,jdb,jdwp test suites support remote and manual launchers that are
> not used.
> These launchers might be configured by test options, however no tests use
> these options.
> The remote launchers allow to run debugee on
On Thu, 20 Jun 2024 11:58:23 GMT, Matthias Baesken wrote:
> The following issue has been observed when running
> serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorThreadTest (and some
> other :tier1 tests)
> on Linux with ubsan enabled binaries :
>
>
On Thu, 20 Jun 2024 11:58:23 GMT, Matthias Baesken wrote:
> The following issue has been observed when running
> serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorThreadTest (and some
> other :tier1 tests)
> on Linux with ubsan enabled binaries :
>
>
> Please review this enhancement to the container detection code which allows
> it to figure out whether the JVM is actually running inside a container
> (`podman`, `docker`, `crio`), or with some other means that enforces
> memory/cpu limits by means of the cgroup filesystem. If neither of
On Tue, 16 Apr 2024 18:25:52 GMT, Thomas Stuefe wrote:
>> Severin Gehwolf has updated the pull request with a new target base due to a
>> merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contains ten additional
>>
The following issue has been observed when running
serviceability/jvmti/HeapMonitor/MyPackage/HeapMonitorThreadTest (and some
other :tier1 tests)
on Linux with ubsan enabled binaries :
test/hotspot/jtreg/serviceability/jvmti/HeapMonitor/libHeapMonitorTest.cpp:518:9:
runtime error: null pointer
> Please review this enhancement to the container detection code which allows
> it to figure out whether the JVM is actually running inside a container
> (`podman`, `docker`, `crio`), or with some other means that enforces
> memory/cpu limits by means of the cgroup filesystem. If neither of
On Thu, 13 Jun 2024 16:55:15 GMT, Sonia Zaldana Calles
wrote:
> Hi all,
>
> This PR addresses [8334164](https://bugs.openjdk.org/browse/JDK-8334164).
>
> Testing:
> - [x] Verified specifying the literal `vm_memory_map_.txt` as the map
> name does not replace ``.
> - [x] Verified `` is
14 matches
Mail list logo
