Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

BundleDelegatingClassLoader randomly loads classes from wrong classloader when running Pax Exam tests in native container #13977

Closed
viktorklang opened this issue Apr 4, 2014 · 3 comments
Closed

BundleDelegatingClassLoader randomly loads classes from wrong classloader when running Pax Exam tests in native container #13977

viktorklang opened this issue Apr 4, 2014 · 3 comments
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on t:osgi
Milestone
2.4.x

Comments

@viktorklang
Copy link
Member

imported from https://www.assembla.com/spaces/akka/tickets/3977

The problem occurs when we are running tests using Pax Exam and in the Native Container.

The findTransitiveBundles method returns a list of bundles to use when loading classes specified in the configuration. This list is unordered and when bundle 0 is first in the list the classes will be loaded from the JVM classloader which then causes a ClassCastException. This causes the integration tests to be unstable. One simple solution is to sort this list in a descending order.
@viktorklang viktorklang added this to the 2.3.x milestone Apr 13, 2014
@bantonsson bantonsson modified the milestones: Current, 2.3.x Apr 15, 2014
@patriknw patriknw modified the milestones: 2.4.x, 2.4.0 Aug 16, 2015
@patriknw patriknw added the help wanted Issues that the core team will likely not have time to work on label Aug 16, 2015
@briantopping
Copy link
Contributor

This should be resolved by #19323, I didn't realize this issue existed before creating it. Should I close that one out and move the discussion here?

@rkuhn rkuhn removed the 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted label Mar 9, 2016
@patriknw
Copy link
Member

@briantopping is this solved?

@patriknw patriknw added the 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted label Mar 18, 2016
@PhilAndrew PhilAndrew mentioned this issue Aug 22, 2016
Closed
@Captain1653 Captain1653 mentioned this issue Jul 16, 2021
Merged
@patriknw
Copy link
Member

Obsolete, see #28304

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted help wanted Issues that the core team will likely not have time to work on t:osgi
Projects
None yet
Milestone
2.4.x
Development

No branches or pull requests
5 participants
@viktorklang @briantopping @patriknw @rkuhn @bantonsson