Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

CreateDynamicProxy(): no class defined exceptions when implementing core JDK interfaces

Description

When working with dynamic proxies, i am seeing a weird error when implementing core JDK interfaces. These interfaces are part of JDK8.

Example proxy:

Example Usage:

When I first run the code in the server, the code fails with a no class defined exception. If I restart the server, the error goes away. This is not good for stability.

You can see a travis build on this here:
https://travis-ci.org/coldbox-modules/cbstreams/jobs/360321909

Environment

None

Attachments

1

Activity

Show:

Dominic Watson 11 July 2018 at 08:31

Hey - thanks for looking into this. I've created a separate pull request with just the test case in (and targeting 5.2 branch).

Running the test with the change you linked to, above, still fails - not sure if that commit was meant for this ticket (it mentions LDEV-1911)?

Michael Offner 11 July 2018 at 05:55

Michael Offner 10 July 2018 at 15:29

problem is here:
https://github.com/lucee/Lucee/blob/5.2/core/src/main/java/lucee/transformer/bytecode/util/JavaProxyFactory.java#L330

classes loaded by the bootstrap classloader do not return a classloader (don't ask why) and because of that the classloader loading the class will not have that classloader and also cannot find that class

Dominic Watson 10 July 2018 at 06:48
Edited

I've tested various versions from the Forgebox repo, and the only version of Lucee 5 in which this works is 5.0.0-SNAPSHOT+243. I get the same errors on the next version hosted on there which is 5.0.0+252.

Looking through the commit history around /core/src/main/java/lucee/commons/lang/PhysicalClassLoader.java brought up this issue which was fixed in 5.0.0.49: LDEV-826.

I suggest that the changes introduced here have caused this new behaviour. Looking further into it to see if I can provide a fix.

Dominic Watson 9 July 2018 at 16:24

+1 here. Using commandbox to spin up a server and even a restart fails for me. I always get this error (using 5.2.7+63).

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 30 March 2018 at 15:51
Updated 20 May 2021 at 09:18
Resolved 17 July 2018 at 09:28