--Original Message-
From: Rick Hillegas
Sent: 09 January 2023 21:19
To: Kevin Walls ; derby-dev@db.apache.org
Cc: David Delabassee
Subject: Re: FW: Re: [External] : Re: JDK 20 Rampdown Phase 1 & Valhalla LW4
Early-Access builds
Thanks for running that experiment, Kevin. I have reproduced you
g
Subject: Re: [External] : Re: JDK 20 Rampdown Phase 1 & Valhalla LW4
Early-Access builds
Hi Rick,
David pointed me at this thread about the ObjectInputFilter and Derby. I see
the notes on the use of -D to set a filter to run the test, but am unsure how
the database itself is started. Th
Hi David,
Derby now builds and tests cleanly after the changes introduced by Open
JDK build 20-ea+27-2213. Our experience is described at
https://issues.apache.org/jira/browse/DERBY-7149.
Thanks,
-Rick
On 12/21/22 2:27 AM, David Delabassee wrote:
Hi Rick,
There's now a default
Thanks for the quick response, David. I'm afraid I'm still confused.
Editing conf/management/management.properties to set
com.sun.management.jmxremote.serial.filter.pattern=*
causes
java junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.management.CacheManagerMBeanTest
Hi Rick,
Just to confirm, the params passed below in your tests are passed to the
JVM that is throwing the exception, right ?
Can you try to comment the filter in
`JDK/conf/management/management.properties` ?
--David
On 21/12/2022 19:25, Rick Hillegas wrote:
Thanks for those pointers,
Thanks for those pointers, David. I'm afraid that my naive attempts have
failed to circumvent this filtering. All of the following commands fail
with the same "java.io.InvalidClassException: filter status: REJECTED"
error:
java junit.textui.TestRunner
Hi Rick,
There's now a default serialization filter for JMX since 20-EA build 22
(1), see release notes (2) and test (3). To confirm this is indeed the
issue, you can either relax the filter to allow your target classes to
be deserialized, or disable the filter.
(1)
Hi David,
Open JDK build 20-ea+27-2213 introduces another problem. I see the
following error when unmarshalling an object on behalf of an MBean:
java.io.InvalidClassException: filter status: REJECTED
I do not see this problem under build 19+36-2238.
Can you point me at the experts who can
Hi Rick,
I suggest to bring this on https://mail.openjdk.org/mailman/listinfo/net-dev
Thanks,
--David
On 15/12/2022 00:06, Rick Hillegas wrote:
Thanks for the heads-up, David. I see many deprecation warnings and
javadoc warnings when I build Derby with Open JDK build 20-ea+27-2213.
Right
Thanks for the heads-up, David. I see many deprecation warnings and
javadoc warnings when I build Derby with Open JDK build 20-ea+27-2213.
Right now, I am trying to track down a fix for the problems introduced
by this change:
- JDK-8294241: Deprecate URL public constructors
My naive attempt
Welcome to the final OpenJDK Quality Outreach update for 2022!
JDK 20, scheduled for General Availability on March 21 2023, is now in
Rampdown Phase One (RDP1) [1]. At this point, the overall JDK 20 [2]
feature set is frozen (see below the final list of JEPs integrated into
JDK 20) and only
11 matches
Mail list logo
