From duke at openjdk.org  Mon Dec  5 16:44:40 2022
From: duke at openjdk.org (Martin Skarsaune)
Date: Mon, 5 Dec 2022 16:44:40 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v28]
In-Reply-To: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
Message-ID: <YcnNCyI9B7B0tNwd1Z3ap6Dgs4qHBSOdZpPydswuQ4o=.36e971a3-c3b0-40c3-99e8-51731daf99a8@github.com>

> Setting back for review. The azure problem requires a fix in Jolokia.
> 
> Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol.

Martin Skarsaune has updated the pull request incrementally with one additional commit since the last revision:

  JMC-7455: Handle unlocking of credentials if set

-------------

Changes:
  - all: https://git.openjdk.org/jmc/pull/332/files
  - new: https://git.openjdk.org/jmc/pull/332/files/4ed92653..0028a086

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jmc&pr=332&range=27
 - incr: https://webrevs.openjdk.org/?repo=jmc&pr=332&range=26-27

  Stats: 48 lines in 2 files changed: 35 ins; 4 del; 9 mod
  Patch: https://git.openjdk.org/jmc/pull/332.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/332/head:pull/332

PR: https://git.openjdk.org/jmc/pull/332

From duke at openjdk.org  Tue Dec  6 20:52:20 2022
From: duke at openjdk.org (Martin Skarsaune)
Date: Tue, 6 Dec 2022 20:52:20 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v28]
In-Reply-To: <YcnNCyI9B7B0tNwd1Z3ap6Dgs4qHBSOdZpPydswuQ4o=.36e971a3-c3b0-40c3-99e8-51731daf99a8@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
 <YcnNCyI9B7B0tNwd1Z3ap6Dgs4qHBSOdZpPydswuQ4o=.36e971a3-c3b0-40c3-99e8-51731daf99a8@github.com>
Message-ID: <CZu3GGq0eQBd-sqbJ9ZwXYq4cKkd0zpGKmIUcCk7EQ8=.c4d98f6b-6bc8-4ebc-9e04-ffc9aa42e9b4@github.com>

On Mon, 5 Dec 2022 16:44:40 GMT, Martin Skarsaune <duke at openjdk.org> wrote:

>> Setting back for review. The azure problem requires a fix in Jolokia.
>> 
>> Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol.
>
> Martin Skarsaune has updated the pull request incrementally with one additional commit since the last revision:
> 
>   JMC-7455: Handle unlocking of credentials if set

Manual tests look good. Solved a problem with stored credentials. Have requested merges and a release on the jolokia side.
Still problems running the test though. Would it be possible to request a CI run on this PR?

-------------

PR: https://git.openjdk.org/jmc/pull/332

From erik.gahlin at oracle.com  Thu Dec  8 07:00:38 2022
From: erik.gahlin at oracle.com (Erik Gahlin)
Date: Thu, 8 Dec 2022 07:00:38 +0000
Subject: Minor change in JFR file format
Message-ID: <DS7PR10MB51185F597BDDEF0982C4E92A9D1D9@DS7PR10MB5118.namprd10.prod.outlook.com>

Hello,

Sometimes the size of a check point event can be larger than what can fit in an integer (32-bits). Both the JDK and JMC parser read the size field as a compressed long, but casts it to an int. In JMC, see SeekableInputStream:

int CompressedIntsDataInput::readInt() throws IOException {
  return (int) readCompressedLong();
}

ChunkLoaderV1::readConstantPoolEvent(...)

Today:
input.readInt(); // size

Should be changed to:
input.readLong(); // size

We are considering bumping the minor version (a non-breaking change) of the file format, but we are not sure if it is necessary as it was already treated as a long value by the JMC parser?

It's more of a problem for the JDK parser, it checks that the number of bytes read matches that of the event size, but since it is already broken for large check point events, a change will not make it more broken. See this JDK bug for details:
https://bugs.openjdk.org/browse/JDK-8298129

This change will not impact the size of ordinary events.

Erik
[https://opengraph.githubassets.com/5bce3a4387800bd74848b1e763ac6ab97f987eba35c7583bb37c8a666782fe3c/openjdk/jmc]<https://github.com/openjdk/jmc/blob/68387c5bd454fcf4bdda07d0cbe8d6eb59e2a840/core/org.openjdk.jmc.flightrecorder/src/main/java/org/openjdk/jmc/flightrecorder/internal/parser/v1/ChunkLoaderV1.java#L103>
jmc/ChunkLoaderV1.java at 68387c5bd454fcf4bdda07d0cbe8d6eb59e2a840 ? openjdk/jmc<https://github.com/openjdk/jmc/blob/68387c5bd454fcf4bdda07d0cbe8d6eb59e2a840/core/org.openjdk.jmc.flightrecorder/src/main/java/org/openjdk/jmc/flightrecorder/internal/parser/v1/ChunkLoaderV1.java#L103>
Repository for OpenJDK Mission Control, a production time profiling and diagnostics tools suite. https://openjdk.org/projects/jmc - jmc/ChunkLoaderV1.java at 68387c5bd454fcf4bdda07d0cbe8d6eb59e2a84...
github.com
?
?
?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221208/12a88fd5/attachment-0001.htm>

From jclf at azul.com  Mon Dec 12 20:03:26 2022
From: jclf at azul.com (Jason Fordham)
Date: Mon, 12 Dec 2022 15:03:26 -0500
Subject: Minor change in JFR file format
In-Reply-To: <DS7PR10MB51185F597BDDEF0982C4E92A9D1D9@DS7PR10MB5118.namprd10.prod.outlook.com>
References: <DS7PR10MB51185F597BDDEF0982C4E92A9D1D9@DS7PR10MB5118.namprd10.prod.outlook.com>
Message-ID: <30588c22-0327-1b90-d3f9-cc5b0441bb69@azul.com>

Hi Erik,

> Sometimes the size of a check point event can be larger than what can
> fit in an integer (32-bits). Both the JDK and JMC parser read the size
> field as a compressed long, but casts it to an int. In JMC, see
> SeekableInputStream:
>
> int CompressedIntsDataInput::readInt() throws IOException {
>    return (int) readCompressedLong();
> }
>
> ChunkLoaderV1::readConstantPoolEvent(...)
>
> Today:
> input.readInt(); // size
>
> Should be changed to:
> input.readLong(); // size
>
> We are considering bumping the minor version (a non-breaking change) of
> the file format, but we are not sure if it is necessary as it was already
> treated as a long value by the JMC parser?
>
> It's more of a problem for the JDK parser, it checks that the number of
> bytes read matches that of the event size, but since it is already broken
> for large check point events, a change will not make it more broken. See
> this JDK bug for details:
> https://bugs.openjdk.org/browse/JDK-8298129
>
> This change will not impact the size of ordinary events.

I thought you should know that this issue is not purely theoretical: it 
actually came up at a customer site, and they reported that 
InvalidJfrFileException occurred for "multiple hosts on production 
instances". This led to us providing them with a short-term fix, and 
opening JDK-8297402. They're using their own jfr reader, and using the 
JMC parser classes.

It's possible that the customer would like to be able to read their 
historical collection of JFRs using a single tool, and I believe the new 
parser code for command line jfr and the JMC GUI will still fail for any 
existing recordings that need more than 28 bits to encode an integer 
value. If this doesn't make up your mind to bump the minor version 
number, would you mind waiting to make a decision on this until I've 
heard back from the customer to see if they need to continue to read 
existing JFRs?

Kind regards,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221212/a37f8139/attachment.htm>

From jclf at azul.com  Thu Dec 15 01:52:34 2022
From: jclf at azul.com (Jason Fordham)
Date: Wed, 14 Dec 2022 20:52:34 -0500
Subject: Minor change in JFR file format
In-Reply-To: <30588c22-0327-1b90-d3f9-cc5b0441bb69@azul.com>
References: <DS7PR10MB51185F597BDDEF0982C4E92A9D1D9@DS7PR10MB5118.namprd10.prod.outlook.com>
 <30588c22-0327-1b90-d3f9-cc5b0441bb69@azul.com>
Message-ID: <600dc728-5f3a-c7c9-8eba-2bcea6baf0c3@azul.com>

Hi Erik,

On 12/12/22 3:03 PM, Jason Fordham wrote:
> On 12/08/22, Erik Gahlin wrote:
>
>> We are considering bumping the minor version (a non-breaking change) of
>> the file format, but we are not sure if it is necessary as it was already
>> treated as a long value by the JMC parser?
>>
>> It's more of a problem for the JDK parser, it checks that the number of
>> bytes read matches that of the event size, but since it is already broken
>> for large check point events, a change will not make it more broken. See
>> this JDK bug for details:
>> https://bugs.openjdk.org/browse/JDK-8298129
>>
>> This change will not impact the size of ordinary events.

The customer involved has confirmed that they would like to be able to 
read their historical collection of JFRs using a single tool, and so a 
bump in the minor version number would make maintaining their automated 
tools easier going forward. I hope this information doesn't come too late.

Kind regards,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221214/332a8668/attachment-0001.htm>

From schaturvedi at openjdk.org  Fri Dec 16 07:06:14 2022
From: schaturvedi at openjdk.org (Suchita Chaturvedi)
Date: Fri, 16 Dec 2022 07:06:14 GMT
Subject: RFR: 7879: Automated Analysis taking very long time to produce
 results for Class Leak Rule and showing wrong results. [v5]
In-Reply-To: <YZnD8PtT1b2K2BFAMkfx3Y90ALkSYxT3Qk_GUS3MYtk=.a7fc9164-f162-4801-b7d5-661b56af782c@github.com>
References: <O1zBHVRTCZY4R-YebBwcj-VuqnoX8gTh52GpFqR9Kww=.03e244f7-c76c-444c-a1aa-58b8fb240381@github.com>
 <N9N2CuE2gUgqADsPV9-afPJaL9gVsf7Ilo1uN-qHLCY=.6261af1a-1bde-4d8e-be53-fb6cea429f6e@github.com>
 <KRhw1ASVMQ2y817XC6LKFXNZ4J2u1hAr326ddvD-rQY=.a6327067-339b-4eca-acfb-544d224acc0f@github.com>
 <xJPwC--X3u_XvEymyxnPV-s55a7pkcwjDxCCvMh6Nhs=.fd00fe55-3b24-46e9-9bdc-d130d0f4dcaa@github.com>
 <0mioSkY_ti5RLq-M3K5DGfXwv4WbQKjpsiNmxei5spo=.35ddaaf5-1bce-4ea0-b4ec-01a8c4027264@github.com>
 <YZnD8PtT1b2K2BFAMkfx3Y90ALkSYxT3Qk_GUS3MYtk=.a7fc9164-f162-4801-b7d5-661b56af782c@github.com>
Message-ID: <ulFkY3xe3aGHx9lbty8hCLYeFTpJQuciuuvb4LIQIEk=.eff675c4-a953-4c92-be1a-1f3aabbfd3b0@github.com>

On Fri, 7 Oct 2022 07:28:55 GMT, Brice Dutheil <bdutheil at openjdk.org> wrote:

>>> > @bric3 We need to show the names of top 5 classes which were loaded maximum times without being unloaded. So the ordering matters here. That's why I have skipped that comment.
>>> 
>>> I'm a bit confused, as in `DefaultIItemResultSet` the _insertion_ in `data` order is dependent on the iteration order of the aggregate collection, since it's a set, there's no ordering guarantees. Although I lack knowledge of the actual type and the implementation is a `TreeSet` or something alike.
>>> 
>>> https://github.com/openjdk/jmc/blob/1696e03a1fddb9cc68d32bf21a281ef24366e552/core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/java/org/openjdk/jmc/flightrecorder/rules/jdk/util/DefaultIItemResultSet.java#L95-L99
>>> 
>>> Moreover the usage of the thread pool here will not guarantee the `add` operation will happen in the same order as the tasks have been submitted. Which leads me to think that the code should be reworked here to ensure that the results will be inserted in order.
>> 
>> I have used a synchronized block for data. After that I am getting consistent results. Without that I was getting different results every time. I mean when I was working for test JFR wldf.jfr without synchronized block on data, the top 5 results varied every time.
>
>> I have used a synchronized block for data. After that I am getting consistent results. Without that I was getting different results every time. I mean when I was working for test JFR wldf.jfr without synchronized block on data, the top 5 results varied every time.
> 
> Have you tried with an intermediate `ConcurrentLinkedQueue`, then copy the results in the data array list ?

Hi @bric3 @Gunde @aptmac , Did you get a chance to check the latest patch? Please let me know what else is required, so that we can close this PR.

-------------

PR: https://git.openjdk.org/jmc/pull/419

From hirt at openjdk.org  Mon Dec 19 22:51:56 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Mon, 19 Dec 2022 22:51:56 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v28]
In-Reply-To: <CZu3GGq0eQBd-sqbJ9ZwXYq4cKkd0zpGKmIUcCk7EQ8=.c4d98f6b-6bc8-4ebc-9e04-ffc9aa42e9b4@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
 <YcnNCyI9B7B0tNwd1Z3ap6Dgs4qHBSOdZpPydswuQ4o=.36e971a3-c3b0-40c3-99e8-51731daf99a8@github.com>
 <CZu3GGq0eQBd-sqbJ9ZwXYq4cKkd0zpGKmIUcCk7EQ8=.c4d98f6b-6bc8-4ebc-9e04-ffc9aa42e9b4@github.com>
Message-ID: <m9xSgsBitw5LRXk49xuaYcF5SvxrcR4mqUjeqhzldYY=.1e6db6aa-5153-4b4b-953e-437a4fe2ea2a@github.com>

On Tue, 6 Dec 2022 20:48:30 GMT, Martin Skarsaune <duke at openjdk.org> wrote:

>> Martin Skarsaune has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   JMC-7455: Handle unlocking of credentials if set
>
> Manual tests look good. Solved a problem with stored credentials. Have requested merges and a release on the jolokia side.
> Still problems running the test though. Would it be possible to request a CI run on this PR?

Hi @skarsaune! Are you ready to make this PR ready for review? 

Regarding the tests, typically the tests would be run in your fork, on commits to your branch. I can try running them on a few OSes locally here though.

-------------

PR: https://git.openjdk.org/jmc/pull/332

From duke at openjdk.org  Tue Dec 20 11:10:41 2022
From: duke at openjdk.org (Virag Purnam)
Date: Tue, 20 Dec 2022 11:10:41 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
Message-ID: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>

Upgrade to Eclipse 2022-12

-------------

Commit messages:
 - 7997: Upgrade to Eclipse 2022-12

Changes: https://git.openjdk.org/jmc/pull/459/files
 Webrev: https://webrevs.openjdk.org/?repo=jmc&pr=459&range=00
  Issue: https://bugs.openjdk.org/browse/JMC-7997
  Stats: 36 lines in 5 files changed: 22 ins; 0 del; 14 mod
  Patch: https://git.openjdk.org/jmc/pull/459.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/459/head:pull/459

PR: https://git.openjdk.org/jmc/pull/459

From bdutheil at openjdk.org  Tue Dec 20 11:42:02 2022
From: bdutheil at openjdk.org (Brice Dutheil)
Date: Tue, 20 Dec 2022 11:42:02 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
Message-ID: <zJutoUEAw9PXB5Kcz1WNkVF2Hz5SwN9Z2UCm_gXwnLA=.68ef6015-735d-4120-82a6-34cf9dd27d95@github.com>

On Tue, 20 Dec 2022 10:59:59 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Upgrade to Eclipse 2022-12

releng/platform-definitions/platform-definition-2022-12/platform-definition-2022-12.target line 63:

> 61:         <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="planner" includeSource="true" type="InstallableUnit">
> 62:             <unit id="org.eclipse.babel.nls_eclipse_ja.feature.group" version="4.22.0.v20211218020001"/>
> 63:             <unit id="org.eclipse.babel.nls_eclipse_zh.feature.group" version="4.22.0.v20211218020001"/>

Is there a 4.26 version ?

-------------

PR: https://git.openjdk.org/jmc/pull/459

From hirt at openjdk.org  Tue Dec 20 12:14:57 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Tue, 20 Dec 2022 12:14:57 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
Message-ID: <0aJ-KONE5GBUCWOsa_ISeDoOiwLtUUPBuM-GmZsWLKo=.f9527079-f6c7-4e9d-86a8-87ee4c3feb75@github.com>

On Tue, 20 Dec 2022 10:59:59 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Upgrade to Eclipse 2022-12

Haha. I did 7996 at the same time. :)

-------------

PR: https://git.openjdk.org/jmc/pull/459

From hirt at openjdk.org  Tue Dec 20 12:14:58 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Tue, 20 Dec 2022 12:14:58 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <zJutoUEAw9PXB5Kcz1WNkVF2Hz5SwN9Z2UCm_gXwnLA=.68ef6015-735d-4120-82a6-34cf9dd27d95@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
 <zJutoUEAw9PXB5Kcz1WNkVF2Hz5SwN9Z2UCm_gXwnLA=.68ef6015-735d-4120-82a6-34cf9dd27d95@github.com>
Message-ID: <hAPrDJ7AGeOgqU_hMsTVDfOQc7GWLeLBRSpDdLsgdoo=.9fc8ee32-f238-478b-813e-8a0783cccb4b@github.com>

On Tue, 20 Dec 2022 11:38:53 GMT, Brice Dutheil <bdutheil at openjdk.org> wrote:

>> Upgrade to Eclipse 2022-12
>
> releng/platform-definitions/platform-definition-2022-12/platform-definition-2022-12.target line 63:
> 
>> 61:         <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="planner" includeSource="true" type="InstallableUnit">
>> 62:             <unit id="org.eclipse.babel.nls_eclipse_ja.feature.group" version="4.22.0.v20211218020001"/>
>> 63:             <unit id="org.eclipse.babel.nls_eclipse_zh.feature.group" version="4.22.0.v20211218020001"/>
> 
> Is there a 4.26 version ?

Nope, there isn't.

-------------

PR: https://git.openjdk.org/jmc/pull/459

From hirt at openjdk.org  Tue Dec 20 12:18:37 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Tue, 20 Dec 2022 12:18:37 GMT
Subject: RFR: 7996: Upgrade to 2022-12
Message-ID: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>

Also adding missing project file for 2022-09.

-------------

Commit messages:
 - 7996: Upgrade to 2022-12

Changes: https://git.openjdk.org/jmc/pull/460/files
 Webrev: https://webrevs.openjdk.org/?repo=jmc&pr=460&range=00
  Issue: https://bugs.openjdk.org/browse/JMC-7996
  Stats: 295 lines in 11 files changed: 36 ins; 241 del; 18 mod
  Patch: https://git.openjdk.org/jmc/pull/460.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/460/head:pull/460

PR: https://git.openjdk.org/jmc/pull/460

From hirt at openjdk.org  Tue Dec 20 12:18:58 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Tue, 20 Dec 2022 12:18:58 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
Message-ID: <TXsY9K2RwQHpfPbR042fXLd1ZoJU7HVLkG-jcDcuYwc=.c7badddd-5501-4218-b95b-9710e8a4f4c7@github.com>

On Tue, 20 Dec 2022 10:59:59 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Upgrade to Eclipse 2022-12

Wanna take mine or yours @viragpurnam? I also deleted a few old (more than a year old) platforms, and fixed the project files in #460.

-------------

PR: https://git.openjdk.org/jmc/pull/459

From duke at openjdk.org  Tue Dec 20 12:23:58 2022
From: duke at openjdk.org (Virag Purnam)
Date: Tue, 20 Dec 2022 12:23:58 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <0aJ-KONE5GBUCWOsa_ISeDoOiwLtUUPBuM-GmZsWLKo=.f9527079-f6c7-4e9d-86a8-87ee4c3feb75@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
 <0aJ-KONE5GBUCWOsa_ISeDoOiwLtUUPBuM-GmZsWLKo=.f9527079-f6c7-4e9d-86a8-87ee4c3feb75@github.com>
Message-ID: <mhlx4FkJXq9pbETDLPBnO31JKv8NHCtj-izDVppZSXs=.596833db-49cc-441a-a5b8-4ad989460395@github.com>

On Tue, 20 Dec 2022 12:11:33 GMT, Marcus Hirt <hirt at openjdk.org> wrote:

> Haha. I did 7996 at the same time. :)

:) Will take Yours 7996. I will close my PR.

-------------

PR: https://git.openjdk.org/jmc/pull/459

From duke at openjdk.org  Tue Dec 20 12:26:53 2022
From: duke at openjdk.org (Virag Purnam)
Date: Tue, 20 Dec 2022 12:26:53 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <mhlx4FkJXq9pbETDLPBnO31JKv8NHCtj-izDVppZSXs=.596833db-49cc-441a-a5b8-4ad989460395@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
 <0aJ-KONE5GBUCWOsa_ISeDoOiwLtUUPBuM-GmZsWLKo=.f9527079-f6c7-4e9d-86a8-87ee4c3feb75@github.com>
 <mhlx4FkJXq9pbETDLPBnO31JKv8NHCtj-izDVppZSXs=.596833db-49cc-441a-a5b8-4ad989460395@github.com>
Message-ID: <K-OVIucggTauXr68T3R7pJbPoDeb9fHItCVfOsgrRIY=.e587c3c1-5d61-486a-a8e1-20f5b2ba136e@github.com>

On Tue, 20 Dec 2022 12:20:57 GMT, Virag Purnam <duke at openjdk.org> wrote:

>> Haha. I did 7996 at the same time. :)
>
>> Haha. I did 7996 at the same time. :)
> 
> :) Will take Yours 7996. I will close my PR.

> Wanna take mine or yours @viragpurnam? I also deleted a few old (more than a year old) platforms, and fixed the project files in #460.

Will take yours.. :) Later I will upgrade spifly version to 1.3.6

-------------

PR: https://git.openjdk.org/jmc/pull/459

From hirt at openjdk.org  Tue Dec 20 12:33:53 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Tue, 20 Dec 2022 12:33:53 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
Message-ID: <ADZHPLqCWj7cO5U0TeBxlf78LtQZjRKXwX8nPBJMocY=.9fb21b0a-255f-40eb-bd5a-e825bc69e795@github.com>

On Tue, 20 Dec 2022 10:59:59 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Upgrade to Eclipse 2022-12

Ok. Sounds good!

-------------

PR: https://git.openjdk.org/jmc/pull/459

From bdutheil at openjdk.org  Tue Dec 20 12:33:55 2022
From: bdutheil at openjdk.org (Brice Dutheil)
Date: Tue, 20 Dec 2022 12:33:55 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <hAPrDJ7AGeOgqU_hMsTVDfOQc7GWLeLBRSpDdLsgdoo=.9fc8ee32-f238-478b-813e-8a0783cccb4b@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
 <zJutoUEAw9PXB5Kcz1WNkVF2Hz5SwN9Z2UCm_gXwnLA=.68ef6015-735d-4120-82a6-34cf9dd27d95@github.com>
 <hAPrDJ7AGeOgqU_hMsTVDfOQc7GWLeLBRSpDdLsgdoo=.9fc8ee32-f238-478b-813e-8a0783cccb4b@github.com>
Message-ID: <MlDSoX40-VmP7_BlFhh0aDLBz51h1pzOyIQrQ0fTHB0=.99096718-7f29-4375-a6a9-00de1ad7b6be@github.com>

On Tue, 20 Dec 2022 12:12:30 GMT, Marcus Hirt <hirt at openjdk.org> wrote:

>> releng/platform-definitions/platform-definition-2022-12/platform-definition-2022-12.target line 63:
>> 
>>> 61:         <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="planner" includeSource="true" type="InstallableUnit">
>>> 62:             <unit id="org.eclipse.babel.nls_eclipse_ja.feature.group" version="4.22.0.v20211218020001"/>
>>> 63:             <unit id="org.eclipse.babel.nls_eclipse_zh.feature.group" version="4.22.0.v20211218020001"/>
>> 
>> Is there a 4.26 version ?
>
> Nope, there isn't.

oh ok

-------------

PR: https://git.openjdk.org/jmc/pull/459

From bdutheil at openjdk.org  Tue Dec 20 12:35:54 2022
From: bdutheil at openjdk.org (Brice Dutheil)
Date: Tue, 20 Dec 2022 12:35:54 GMT
Subject: RFR: 7996: Upgrade to 2022-12
In-Reply-To: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
References: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
Message-ID: <F1sh0mwr1_rknBgbZFkoDZJuA0Rwze9EnBYltjRkEl0=.6de54e5a-7907-4e2b-8d81-c6f1a6fb288c@github.com>

On Tue, 20 Dec 2022 12:10:37 GMT, Marcus Hirt <hirt at openjdk.org> wrote:

> Also adding missing project file for 2022-09.

Marked as reviewed by bdutheil (Author).

-------------

PR: https://git.openjdk.org/jmc/pull/460

From duke at openjdk.org  Tue Dec 20 12:47:59 2022
From: duke at openjdk.org (Virag Purnam)
Date: Tue, 20 Dec 2022 12:47:59 GMT
Subject: RFR: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
Message-ID: <n0Kn75PUDOx-sv_r-0nZVeYbXFfDme6ip9YROBUZws8=.815b6a1a-a9ea-4521-bff0-7c86a5ede36c@github.com>

On Tue, 20 Dec 2022 10:59:59 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Upgrade to Eclipse 2022-12

Duplicate of https://github.com/openjdk/jmc/pull/460

-------------

PR: https://git.openjdk.org/jmc/pull/459

From duke at openjdk.org  Tue Dec 20 12:48:00 2022
From: duke at openjdk.org (Virag Purnam)
Date: Tue, 20 Dec 2022 12:48:00 GMT
Subject: Withdrawn: 7997: Upgrade to Eclipse 2022-12
In-Reply-To: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
References: <g-JvOIVGQ3xX-bno5NCdtanF-BeJT2v-YwvWyH4DtpY=.583b8fdc-2035-4df5-afdd-a863247dcd24@github.com>
Message-ID: <a2-SwaEAhMVoMM_NW0vS6V6fh93u4gPOjQHa6lakalE=.8ade4063-3e36-4b76-97d3-eec0f8c63fa8@github.com>

On Tue, 20 Dec 2022 10:59:59 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Upgrade to Eclipse 2022-12

This pull request has been closed without being integrated.

-------------

PR: https://git.openjdk.org/jmc/pull/459

From marcus.hirt at datadoghq.com  Tue Dec 20 15:34:50 2022
From: marcus.hirt at datadoghq.com (Marcus Hirt)
Date: Tue, 20 Dec 2022 16:34:50 +0100
Subject: New jmc Committer: Virag Purnam
Message-ID: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>

Hi all,

I hereby nominate Virag Purnam to jmc Committer.

Virag has contributed to JMC since joining Oracle, not only helping
out with commits in the project, but also with related work internally
at Oracle, such as getting third-party approvals etc.

Here is a list of some of Virag's direct contributions:
https://github.com/openjdk/jmc/pulls?q=viragpurnam

Votes are due by the 29th of December 2022, 17:00 CET.

Only current jmc Committers [1] are eligible to vote on this
nomination. Votes must be cast in the open by replying to this mailing
list.

For Lazy Consensus voting instructions, see [2].

Kind regards,
Marcus

[1] https://openjdk.java.net/census
[2] https://openjdk.java.net/projects/#committer-vote

From suchita.chaturvedi at oracle.com  Tue Dec 20 15:39:54 2022
From: suchita.chaturvedi at oracle.com (Suchita Chaturvedi)
Date: Tue, 20 Dec 2022 15:39:54 +0000
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
References: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
Message-ID: <DM6PR10MB3628A3DE8A116A6BB632F89DFBEA9@DM6PR10MB3628.namprd10.prod.outlook.com>

Yes.

Sent from Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: jmc-dev <jmc-dev-retn at openjdk.org> on behalf of Marcus Hirt <marcus.hirt at datadoghq.com>
Sent: Tuesday, December 20, 2022 9:04:50 PM
To: jmc-dev at openjdk.java.net <jmc-dev at openjdk.java.net>
Subject: New jmc Committer: Virag Purnam

Hi all,

I hereby nominate Virag Purnam to jmc Committer.

Virag has contributed to JMC since joining Oracle, not only helping
out with commits in the project, but also with related work internally
at Oracle, such as getting third-party approvals etc.

Here is a list of some of Virag's direct contributions:
https://github.com/openjdk/jmc/pulls?q=viragpurnam

Votes are due by the 29th of December 2022, 17:00 CET.

Only current jmc Committers [1] are eligible to vote on this
nomination. Votes must be cast in the open by replying to this mailing
list.

For Lazy Consensus voting instructions, see [2].

Kind regards,
Marcus

[1] https://openjdk.java.net/census
[2] https://openjdk.java.net/projects/#committer-vote
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221220/e3d85d2f/attachment.htm>

From aptmac at openjdk.org  Tue Dec 20 20:58:55 2022
From: aptmac at openjdk.org (Alex Macdonald)
Date: Tue, 20 Dec 2022 20:58:55 GMT
Subject: RFR: 7996: Upgrade to 2022-12
In-Reply-To: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
References: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
Message-ID: <dy9vtobLuNhKC3_s_HxKq2DxyYnBJuvRreGAmvOEQ68=.e93f17af-75d0-4758-a117-ae84cb318af3@github.com>

On Tue, 20 Dec 2022 12:10:37 GMT, Marcus Hirt <hirt at openjdk.org> wrote:

> Also adding missing project file for 2022-09.

releng/platform-definitions/pom.xml line 3:

> 1: <?xml version="1.0" encoding="UTF-8"?>
> 2: <!--
> 3:    Copyright (c) 2022, Oracle and/or its affiliates. All rights reserved.

Did you mean to remove the 2018 from the copyright years here?

-------------

PR: https://git.openjdk.org/jmc/pull/460

From duke at openjdk.org  Tue Dec 20 21:24:56 2022
From: duke at openjdk.org (Martin Skarsaune)
Date: Tue, 20 Dec 2022 21:24:56 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v28]
In-Reply-To: <m9xSgsBitw5LRXk49xuaYcF5SvxrcR4mqUjeqhzldYY=.1e6db6aa-5153-4b4b-953e-437a4fe2ea2a@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
 <YcnNCyI9B7B0tNwd1Z3ap6Dgs4qHBSOdZpPydswuQ4o=.36e971a3-c3b0-40c3-99e8-51731daf99a8@github.com>
 <CZu3GGq0eQBd-sqbJ9ZwXYq4cKkd0zpGKmIUcCk7EQ8=.c4d98f6b-6bc8-4ebc-9e04-ffc9aa42e9b4@github.com>
 <m9xSgsBitw5LRXk49xuaYcF5SvxrcR4mqUjeqhzldYY=.1e6db6aa-5153-4b4b-953e-437a4fe2ea2a@github.com>
Message-ID: <iU9e0XySFiaKmOWdycTZzlY_epyWa3Qmudkf4QpHB3c=.2ac93052-291c-4359-b623-00eabe283533@github.com>

On Mon, 19 Dec 2022 22:49:46 GMT, Marcus Hirt <hirt at openjdk.org> wrote:

>> Manual tests look good. Solved a problem with stored credentials. Have requested merges and a release on the jolokia side.
>> Still problems running the test though. Would it be possible to request a CI run on this PR?
>
> Hi @skarsaune! Are you ready to make this PR ready for review? 
> 
> Regarding the tests, typically the tests would be run in your fork, on commits to your branch. I can try running them on a few OSes locally here though.

1. Great if you can run the tests @thegreystone ! The jolokia tests run , but the Kubernetes tests not. They should be set up the same way, but it here is probably a silly error somewhere.

2. Thanks for checking in ??. I just asked for a release of jolokia. I hope to conclude that soon.

-------------

PR: https://git.openjdk.org/jmc/pull/332

From hirt at openjdk.org  Tue Dec 20 21:40:56 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Tue, 20 Dec 2022 21:40:56 GMT
Subject: RFR: 7996: Upgrade to 2022-12
In-Reply-To: <dy9vtobLuNhKC3_s_HxKq2DxyYnBJuvRreGAmvOEQ68=.e93f17af-75d0-4758-a117-ae84cb318af3@github.com>
References: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
 <dy9vtobLuNhKC3_s_HxKq2DxyYnBJuvRreGAmvOEQ68=.e93f17af-75d0-4758-a117-ae84cb318af3@github.com>
Message-ID: <j9OcpPXJCVz1xjVgMQBZ0E1gZSMd3-kwc5ncQy8bP7A=.797ffaf0-0f54-409e-9a17-1a7a8d84ec96@github.com>

On Tue, 20 Dec 2022 20:56:40 GMT, Alex Macdonald <aptmac at openjdk.org> wrote:

>> Also adding missing project file for 2022-09.
>
> releng/platform-definitions/pom.xml line 3:
> 
>> 1: <?xml version="1.0" encoding="UTF-8"?>
>> 2: <!--
>> 3:    Copyright (c) 2022, Oracle and/or its affiliates. All rights reserved.
> 
> Did you mean to remove the 2018 from the copyright years here?

Good catch.

-------------

PR: https://git.openjdk.org/jmc/pull/460

From hirt at openjdk.org  Tue Dec 20 21:49:10 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Tue, 20 Dec 2022 21:49:10 GMT
Subject: RFR: 7996: Upgrade to 2022-12 [v2]
In-Reply-To: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
References: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
Message-ID: <jlvjAoJGUr0Ldd2rIYWieBNE8DAgldNvR4ocmKaX5pk=.b26fb911-a277-4fc5-b62f-c2d130144d6f@github.com>

> Also adding missing project file for 2022-09.

Marcus Hirt has updated the pull request incrementally with one additional commit since the last revision:

  Fixing accidentally edited copyright

-------------

Changes:
  - all: https://git.openjdk.org/jmc/pull/460/files
  - new: https://git.openjdk.org/jmc/pull/460/files/986eb40d..010b35ca

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jmc&pr=460&range=01
 - incr: https://webrevs.openjdk.org/?repo=jmc&pr=460&range=00-01

  Stats: 2 lines in 1 file changed: 0 ins; 1 del; 1 mod
  Patch: https://git.openjdk.org/jmc/pull/460.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/460/head:pull/460

PR: https://git.openjdk.org/jmc/pull/460

From aptmac at openjdk.org  Wed Dec 21 04:17:55 2022
From: aptmac at openjdk.org (Alex Macdonald)
Date: Wed, 21 Dec 2022 04:17:55 GMT
Subject: RFR: 7996: Upgrade to 2022-12 [v2]
In-Reply-To: <jlvjAoJGUr0Ldd2rIYWieBNE8DAgldNvR4ocmKaX5pk=.b26fb911-a277-4fc5-b62f-c2d130144d6f@github.com>
References: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
 <jlvjAoJGUr0Ldd2rIYWieBNE8DAgldNvR4ocmKaX5pk=.b26fb911-a277-4fc5-b62f-c2d130144d6f@github.com>
Message-ID: <jlrlXbdHk8EgzWEUR9E3XHCLNWKG0pcVYjXwHa8MaSc=.744512cb-1b2a-4fba-80d7-44830d4b94a7@github.com>

On Tue, 20 Dec 2022 21:49:10 GMT, Marcus Hirt <hirt at openjdk.org> wrote:

>> Also adding missing project file for 2022-09.
>
> Marcus Hirt has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Fixing accidentally edited copyright

Marked as reviewed by aptmac (Reviewer).

-------------

PR: https://git.openjdk.org/jmc/pull/460

From miro.wengner at gmail.com  Wed Dec 21 10:11:04 2022
From: miro.wengner at gmail.com (Miro Wengner)
Date: Wed, 21 Dec 2022 11:11:04 +0100
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
References: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
Message-ID: <7838C632-9A76-42A8-8A93-96C5AD95E7F6@gmail.com>

yes

> On 20. Dec 2022, at 16:34, Marcus Hirt <marcus.hirt at datadoghq.com> wrote:
> 
> Hi all,
> 
> I hereby nominate Virag Purnam to jmc Committer.
> 
> Virag has contributed to JMC since joining Oracle, not only helping
> out with commits in the project, but also with related work internally
> at Oracle, such as getting third-party approvals etc.
> 
> Here is a list of some of Virag's direct contributions:
> https://github.com/openjdk/jmc/pulls?q=viragpurnam
> 
> Votes are due by the 29th of December 2022, 17:00 CET.
> 
> Only current jmc Committers [1] are eligible to vote on this
> nomination. Votes must be cast in the open by replying to this mailing
> list.
> 
> For Lazy Consensus voting instructions, see [2].
> 
> Kind regards,
> Marcus
> 
> [1] https://openjdk.java.net/census
> [2] https://openjdk.java.net/projects/#committer-vote


From patrick at reini.net  Wed Dec 21 11:36:21 2022
From: patrick at reini.net (Patrick Reinhart)
Date: Wed, 21 Dec 2022 12:36:21 +0100
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <7838C632-9A76-42A8-8A93-96C5AD95E7F6@gmail.com>
References: <7838C632-9A76-42A8-8A93-96C5AD95E7F6@gmail.com>
Message-ID: <CD6CE7FB-1E3E-4AF3-A84B-ED57450240FC@reini.net>

yes

From christoph.langer at sap.com  Wed Dec 21 12:51:03 2022
From: christoph.langer at sap.com (Langer, Christoph)
Date: Wed, 21 Dec 2022 12:51:03 +0000
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
References: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
Message-ID: <DB6PR0202MB269433D62B20587087B2C3C58AEB9@DB6PR0202MB2694.eurprd02.prod.outlook.com>

Vote:yes

/Christoph

> -----Original Message-----
> From: jmc-dev <jmc-dev-retn at openjdk.org> On Behalf Of Marcus Hirt
> Sent: Dienstag, 20. Dezember 2022 16:35
> To: jmc-dev at openjdk.java.net
> Subject: New jmc Committer: Virag Purnam
> 
> Hi all,
> 
> I hereby nominate Virag Purnam to jmc Committer.
> 
> Virag has contributed to JMC since joining Oracle, not only helping out with
> commits in the project, but also with related work internally at Oracle, such as
> getting third-party approvals etc.
> 
> Here is a list of some of Virag's direct contributions:
> https://github.com/openjdk/jmc/pulls?q=viragpurnam
> 
> Votes are due by the 29th of December 2022, 17:00 CET.
> 
> Only current jmc Committers [1] are eligible to vote on this nomination. Votes
> must be cast in the open by replying to this mailing list.
> 
> For Lazy Consensus voting instructions, see [2].
> 
> Kind regards,
> Marcus
> 
> [1]
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenjdk.
> java.net%2Fcensus&data=05%7C01%7Cchristoph.langer%40sap.com%7Ca0410
> 9aeced246281aaf08dae29fcce9%7C42f7676cf455423c82f6dc2d99791af7%7C
> 0%7C0%7C638071473216331314%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
> C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%
> 7C%7C%7C&sdata=wl7GrsmvZ70cAol7zUoMs8IevvfVVJNqp%2BQQ4cpFEjw%3
> D&reserved=0
> [2]
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenjdk.
> java.net%2Fprojects%2F%23committer-
> vote&data=05%7C01%7Cchristoph.langer%40sap.com%7Ca04109aeced24628
> 1aaf08dae29fcce9%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C63
> 8071473216331314%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&s
> data=K1FxOnHS%2BfV10mxxZsZ6h%2BtvJNb65kWaxQM3N%2BbeiCM%3D&re
> served=0

From jean-philippe.bempel at datadoghq.com  Wed Dec 21 13:11:50 2022
From: jean-philippe.bempel at datadoghq.com (Jean-Philippe Bempel)
Date: Wed, 21 Dec 2022 14:11:50 +0100
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
References: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
Message-ID: <CAFcyPZ1LMXoLdGAoyU7DftY6DbKc85qnvF6ZwjcN1Gro6-ExVQ@mail.gmail.com>

Vote: yes

On Tue, Dec 20, 2022 at 4:35 PM Marcus Hirt <marcus.hirt at datadoghq.com>
wrote:

> Hi all,
>
> I hereby nominate Virag Purnam to jmc Committer.
>
> Virag has contributed to JMC since joining Oracle, not only helping
> out with commits in the project, but also with related work internally
> at Oracle, such as getting third-party approvals etc.
>
> Here is a list of some of Virag's direct contributions:
> https://github.com/openjdk/jmc/pulls?q=viragpurnam
>
> Votes are due by the 29th of December 2022, 17:00 CET.
>
> Only current jmc Committers [1] are eligible to vote on this
> nomination. Votes must be cast in the open by replying to this mailing
> list.
>
> For Lazy Consensus voting instructions, see [2].
>
> Kind regards,
> Marcus
>
> [1] https://openjdk.java.net/census
> [2] https://openjdk.java.net/projects/#committer-vote
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221221/8724f535/attachment.htm>

From marcus.hirt at datadoghq.com  Wed Dec 21 15:04:32 2022
From: marcus.hirt at datadoghq.com (Marcus Hirt)
Date: Wed, 21 Dec 2022 16:04:32 +0100
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
References: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
Message-ID: <CAOpWGx3vTt1m4uk3aTu_qtQ43n89BgZmURQBsBKpO2JH8DtzhQ@mail.gmail.com>

Vote: yes

On Tue, Dec 20, 2022 at 4:34 PM Marcus Hirt <marcus.hirt at datadoghq.com>
wrote:

> Hi all,
>
> I hereby nominate Virag Purnam to jmc Committer.
>
> Virag has contributed to JMC since joining Oracle, not only helping
> out with commits in the project, but also with related work internally
> at Oracle, such as getting third-party approvals etc.
>
> Here is a list of some of Virag's direct contributions:
> https://github.com/openjdk/jmc/pulls?q=viragpurnam
>
> Votes are due by the 29th of December 2022, 17:00 CET.
>
> Only current jmc Committers [1] are eligible to vote on this
> nomination. Votes must be cast in the open by replying to this mailing
> list.
>
> For Lazy Consensus voting instructions, see [2].
>
> Kind regards,
> Marcus
>
> [1] https://openjdk.java.net/census
> [2] https://openjdk.java.net/projects/#committer-vote
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221221/276c058a/attachment-0001.htm>

From hirt at openjdk.org  Wed Dec 21 15:10:59 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Wed, 21 Dec 2022 15:10:59 GMT
Subject: Integrated: 7996: Upgrade to 2022-12
In-Reply-To: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
References: <WpBZWg-4voNLyaEQjVPkMGlfg6pzoqG_aUU7XPKPpOQ=.94db9263-31bd-41a6-8787-ebe0cf5b1b99@github.com>
Message-ID: <7wMkF2liOGO_fTudd64CI5UQrm9hCLFqWDtl1qErF9U=.0ec356ce-6acd-4991-ade8-4d2740242601@github.com>

On Tue, 20 Dec 2022 12:10:37 GMT, Marcus Hirt <hirt at openjdk.org> wrote:

> Also adding missing project file for 2022-09.

This pull request has now been integrated.

Changeset: f8b044ea
Author:    Marcus Hirt <hirt at openjdk.org>
URL:       https://git.openjdk.org/jmc/commit/f8b044ea74d8af14d587cd5b12941d32fa18ac8d
Stats:     293 lines in 11 files changed: 35 ins; 241 del; 17 mod

7996: Upgrade to 2022-12

Reviewed-by: bdutheil, aptmac

-------------

PR: https://git.openjdk.org/jmc/pull/460

From duke at openjdk.org  Wed Dec 21 17:01:35 2022
From: duke at openjdk.org (Virag Purnam)
Date: Wed, 21 Dec 2022 17:01:35 GMT
Subject: RFR: 7998: Upgrading spifly and jetty project version
Message-ID: <VLHj8b8pznx6hiGpT_RdWQzGJylsXKNQRko0PbbD5rc=.04437744-bf7c-49b0-9eba-fe2b28d51cd3@github.com>

Eclipse 22-12 uses Jetty Project 10.0.12 and ASM 9.4. To keep the versions consistent with Eclipse 22-12, upgraded the third party libraries. I will update the **thirdpartyreadme.txt** file later.
Jetty Project from10.0.11 to 10.0.12.
Spifly from 1.3.4 to 1.3.6. (To match ASM 9.4)

-------------

Commit messages:
 - 7998: Upgrading spifly and jetty project version

Changes: https://git.openjdk.org/jmc/pull/461/files
 Webrev: https://webrevs.openjdk.org/?repo=jmc&pr=461&range=00
  Issue: https://bugs.openjdk.org/browse/JMC-7998
  Stats: 7 lines in 2 files changed: 0 ins; 0 del; 7 mod
  Patch: https://git.openjdk.org/jmc/pull/461.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/461/head:pull/461

PR: https://git.openjdk.org/jmc/pull/461

From hirt at openjdk.org  Wed Dec 21 18:28:55 2022
From: hirt at openjdk.org (Marcus Hirt)
Date: Wed, 21 Dec 2022 18:28:55 GMT
Subject: RFR: 7998: Upgrading spifly and jetty project version
In-Reply-To: <VLHj8b8pznx6hiGpT_RdWQzGJylsXKNQRko0PbbD5rc=.04437744-bf7c-49b0-9eba-fe2b28d51cd3@github.com>
References: <VLHj8b8pznx6hiGpT_RdWQzGJylsXKNQRko0PbbD5rc=.04437744-bf7c-49b0-9eba-fe2b28d51cd3@github.com>
Message-ID: <CcifcbZTBRjjf0ISYl5ElzAAhdZxtlgx8TU46euhTiw=.e22dd556-45cf-4295-bd84-27ddfacf7a3c@github.com>

On Wed, 21 Dec 2022 16:55:24 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Eclipse 22-12 uses Jetty Project 10.0.12 and ASM 9.4. To keep the versions consistent with Eclipse 22-12, upgraded the third party libraries. I will update the **thirdpartyreadme.txt** file later.
> Jetty Project from10.0.11 to 10.0.12.
> Spifly from 1.3.4 to 1.3.6. (To match ASM 9.4)

Marked as reviewed by hirt (Lead).

-------------

PR: https://git.openjdk.org/jmc/pull/461

From duke at openjdk.org  Thu Dec 22 06:21:54 2022
From: duke at openjdk.org (Virag Purnam)
Date: Thu, 22 Dec 2022 06:21:54 GMT
Subject: Integrated: 7998: Upgrading spifly and jetty project version
In-Reply-To: <VLHj8b8pznx6hiGpT_RdWQzGJylsXKNQRko0PbbD5rc=.04437744-bf7c-49b0-9eba-fe2b28d51cd3@github.com>
References: <VLHj8b8pznx6hiGpT_RdWQzGJylsXKNQRko0PbbD5rc=.04437744-bf7c-49b0-9eba-fe2b28d51cd3@github.com>
Message-ID: <4NKPmu4RjaJsmkJ39zpPmP7Gsi2Ic_WE2GpbL_tt-yg=.ef1e1aa2-dc1a-48d3-ad16-acd242ff264f@github.com>

On Wed, 21 Dec 2022 16:55:24 GMT, Virag Purnam <duke at openjdk.org> wrote:

> Eclipse 22-12 uses Jetty Project 10.0.12 and ASM 9.4. To keep the versions consistent with Eclipse 22-12, upgraded the third party libraries. I will update the **thirdpartyreadme.txt** file later.
> Jetty Project from10.0.11 to 10.0.12.
> Spifly from 1.3.4 to 1.3.6. (To match ASM 9.4)

This pull request has now been integrated.

Changeset: 0cabfbca
Author:    vpurnam <vpurnam at VPURNAM-7420.in.oracle.com>
Committer: Suchita Chaturvedi <schaturvedi at openjdk.org>
URL:       https://git.openjdk.org/jmc/commit/0cabfbcaa34d04bdf0d4bdaa5a3501c996a7f349
Stats:     7 lines in 2 files changed: 0 ins; 0 del; 7 mod

7998: Upgrading spifly and jetty project version

Reviewed-by: hirt

-------------

PR: https://git.openjdk.org/jmc/pull/461

From patrick at reini.net  Thu Dec 22 06:55:23 2022
From: patrick at reini.net (Patrick Reinhart)
Date: Thu, 22 Dec 2022 07:55:23 +0100
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <CAOpWGx3vTt1m4uk3aTu_qtQ43n89BgZmURQBsBKpO2JH8DtzhQ@mail.gmail.com>
References: <CAOpWGx3vTt1m4uk3aTu_qtQ43n89BgZmURQBsBKpO2JH8DtzhQ@mail.gmail.com>
Message-ID: <0FAD4D7C-98EF-422A-B188-3D3B8BCEBCA8@reini.net>

Vote: yes

From miro.wengner at gmail.com  Thu Dec 22 09:12:20 2022
From: miro.wengner at gmail.com (Miro Wengner)
Date: Thu, 22 Dec 2022 10:12:20 +0100
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <0FAD4D7C-98EF-422A-B188-3D3B8BCEBCA8@reini.net>
References: <CAOpWGx3vTt1m4uk3aTu_qtQ43n89BgZmURQBsBKpO2JH8DtzhQ@mail.gmail.com>
 <0FAD4D7C-98EF-422A-B188-3D3B8BCEBCA8@reini.net>
Message-ID: <481B2095-1EED-4DE0-A7A7-E1A41309F082@gmail.com>

Vote: yes

> On 22. Dec 2022, at 07:55, Patrick Reinhart <patrick at reini.net> wrote:
> 
> Vote: yes


From almacdon at redhat.com  Thu Dec 22 14:41:37 2022
From: almacdon at redhat.com (Alex Macdonald)
Date: Thu, 22 Dec 2022 09:41:37 -0500
Subject: New jmc Committer: Virag Purnam
In-Reply-To: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
References: <CAOpWGx2Zyn_tm38cafGVoFmWV5PZd9avurvMMWi-ivddDPAy4Q@mail.gmail.com>
Message-ID: <CAOsn=kpfxqiXKgJEyxHJJtoFCVC136_HNF_Yx4w0aZPM4dtf9A@mail.gmail.com>

Vote: yes

On Tue, Dec 20, 2022 at 10:35 AM Marcus Hirt <marcus.hirt at datadoghq.com> wrote:
>
> Hi all,
>
> I hereby nominate Virag Purnam to jmc Committer.
>
> Virag has contributed to JMC since joining Oracle, not only helping
> out with commits in the project, but also with related work internally
> at Oracle, such as getting third-party approvals etc.
>
> Here is a list of some of Virag's direct contributions:
> https://github.com/openjdk/jmc/pulls?q=viragpurnam
>
> Votes are due by the 29th of December 2022, 17:00 CET.
>
> Only current jmc Committers [1] are eligible to vote on this
> nomination. Votes must be cast in the open by replying to this mailing
> list.
>
> For Lazy Consensus voting instructions, see [2].
>
> Kind regards,
> Marcus
>
> [1] https://openjdk.java.net/census
> [2] https://openjdk.java.net/projects/#committer-vote
>


From duke at openjdk.org  Mon Dec 26 21:37:14 2022
From: duke at openjdk.org (Martin Skarsaune)
Date: Mon, 26 Dec 2022 21:37:14 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v29]
In-Reply-To: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
Message-ID: <ol7rkHs4kRZDgEa0ERF33t6EFM2ToJQYxz9hHy5mhPw=.6ced7f71-fa95-4481-89fd-5138141dfa44@github.com>

> Setting back for review. The azure problem requires a fix in Jolokia.
> 
> Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol.

Martin Skarsaune has updated the pull request incrementally with one additional commit since the last revision:

  JMC-7455: Upgrade jolokia to 1.7.2

-------------

Changes:
  - all: https://git.openjdk.org/jmc/pull/332/files
  - new: https://git.openjdk.org/jmc/pull/332/files/0028a086..7754b8be

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jmc&pr=332&range=28
 - incr: https://webrevs.openjdk.org/?repo=jmc&pr=332&range=27-28

  Stats: 26 lines in 11 files changed: 0 ins; 0 del; 26 mod
  Patch: https://git.openjdk.org/jmc/pull/332.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/332/head:pull/332

PR: https://git.openjdk.org/jmc/pull/332

From duke at openjdk.org  Mon Dec 26 22:04:36 2022
From: duke at openjdk.org (Martin Skarsaune)
Date: Mon, 26 Dec 2022 22:04:36 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v30]
In-Reply-To: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
Message-ID: <_DG9ZnMngspt4XdVxnDpP3pxbwGZuTmdRCy7kBeUnx4=.bd926c17-e9e0-47b8-9c43-163cc0f55c1a@github.com>

> Setting back for review. The azure problem requires a fix in Jolokia.
> 
> Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol.

Martin Skarsaune has updated the pull request with a new target base due to a merge or a rebase. The pull request now contains 31 commits:

 - Merge remote-tracking branch 'origin/master' into jolokia-support
 - JMC-7455: Prepare for merge
 - JMC-7455: Upgrade jolokia to 1.7.2
 - JMC-7455: Handle unlocking of credentials if set
 - JMC-7455: No longer rely on selflink (as in https://github.com/rhuss/jolokia/pull/489)
 - JMC-7455: Handle credentials not yet present
 - JMC-7455: Cosmetic: Undo formatting of copyright that got messed up
 - JMC-7455: Upgrade to 9.0.0
 - JMC-7455: Secure credentials. Make it possible to test outside of maven
 - JMC-7455: Verifications and more authorization tests
 - ... and 21 more: https://git.openjdk.org/jmc/compare/0cabfbca...41501e7d

-------------

Changes: https://git.openjdk.org/jmc/pull/332/files
 Webrev: https://webrevs.openjdk.org/?repo=jmc&pr=332&range=29
  Stats: 4604 lines in 82 files changed: 4603 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jmc/pull/332.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/332/head:pull/332

PR: https://git.openjdk.org/jmc/pull/332

From duke at openjdk.org  Mon Dec 26 22:15:10 2022
From: duke at openjdk.org (Martin Skarsaune)
Date: Mon, 26 Dec 2022 22:15:10 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v31]
In-Reply-To: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
Message-ID: <Y7aRG1pITZMqsxgoil5h629cZPSCR58D2DuP4Ofco68=.05449cc7-ce01-4852-b2c4-e356209ab11f@github.com>

> Setting back for review. The azure problem requires a fix in Jolokia.
> 
> Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol.

Martin Skarsaune has refreshed the contents of this pull request, and previous commits have been removed. The incremental views will show differences compared to the previous content of the PR. The pull request contains one new commit since the last revision:

  Merge remote-tracking branch 'origin/master' into jolokia-support

-------------

Changes:
  - all: https://git.openjdk.org/jmc/pull/332/files
  - new: https://git.openjdk.org/jmc/pull/332/files/41501e7d..1783f1bc

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jmc&pr=332&range=30
 - incr: https://webrevs.openjdk.org/?repo=jmc&pr=332&range=29-30

  Stats: 2 lines in 1 file changed: 0 ins; 1 del; 1 mod
  Patch: https://git.openjdk.org/jmc/pull/332.diff
  Fetch: git fetch https://git.openjdk.org/jmc pull/332/head:pull/332

PR: https://git.openjdk.org/jmc/pull/332

From duke at openjdk.org  Mon Dec 26 22:36:52 2022
From: duke at openjdk.org (Martin Skarsaune)
Date: Mon, 26 Dec 2022 22:36:52 GMT
Subject: RFR: 7455: Add support for jolokia JMX service connection [v31]
In-Reply-To: <Y7aRG1pITZMqsxgoil5h629cZPSCR58D2DuP4Ofco68=.05449cc7-ce01-4852-b2c4-e356209ab11f@github.com>
References: <V5HVftATlhcY-J3P7RedCgruJpd5CISO6C7p06Df348=.a378eb7f-073a-4841-92ed-a8e93be922e5@github.com>
 <Y7aRG1pITZMqsxgoil5h629cZPSCR58D2DuP4Ofco68=.05449cc7-ce01-4852-b2c4-e356209ab11f@github.com>
Message-ID: <PSI_ysrkegprylIuMrR3OXcn0fFm4EhrLQx9gSopcvw=.dc533b81-66a9-406a-b002-ad3c5cc45d6d@github.com>

On Mon, 26 Dec 2022 22:15:10 GMT, Martin Skarsaune <duke at openjdk.org> wrote:

>> Setting back for review. The azure problem requires a fix in Jolokia.
>> 
>> Make use of support for JMX service connection in jolokia 1.7.0 and later to connect to JVMs over this protocol.
>
> Martin Skarsaune has refreshed the contents of this pull request, and previous commits have been removed. The incremental views will show differences compared to the previous content of the PR. The pull request contains one new commit since the last revision:
> 
>   Merge remote-tracking branch 'origin/master' into jolokia-support

Jolokia is updated now. Merged with master and marking ready for review. PR is ready for slaughter ? 
Kuternetes tests still fail when I run `./build.sh --test` I need some assistance in understanding that one.

-------------

PR: https://git.openjdk.org/jmc/pull/332

From ondersezgin at gmail.com  Fri Dec  9 14:05:42 2022
From: ondersezgin at gmail.com (Onder SEZGIN)
Date: Fri, 09 Dec 2022 14:05:42 -0000
Subject: invitation to slack group
Message-ID: <CAE9ARBT4F33+KQsmg6kJB8zTiZ4TQd3MerG3tgaxQB7Dha452w@mail.gmail.com>

hi,

may i request an invitation to jmc slack?

Thanks
Onder
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jmc-dev/attachments/20221209/803445af/attachment.htm>