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

Fixing logging in case of OSGI error, due to null NodeEngine #8758

Merged
merged 1 commit into from Aug 22, 2016
Merged

Fixing logging in case of OSGI error, due to null NodeEngine #8758

merged 1 commit into from Aug 22, 2016

Conversation

tombujok
Copy link
Contributor

Fixes #8755

@tombujok tombujok added this to the 3.8 milestone Aug 22, 2016
@jerrinot
Copy link
Contributor

👍 on green

@devOpsHazelcast
Copy link
Collaborator

Test PASSed.

@tombujok tombujok merged commit f0e0079 into hazelcast:master Aug 22, 2016
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Source: Internal PR or issue was opened by an employee Team: Core
Projects
None yet
Milestone
3.8
Development

Successfully merging this pull request may close these issues.

NullPointerException when DefaultNodeExtension class has been loaded by two different class-loaders.
4 participants
@tombujok @jerrinot @devOpsHazelcast @mmedenjak