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.

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

PAYARA-3736: Let HazelcastConfigSpecificConfiguration register itself #3976

Merged
merged 1 commit into from
Jun 3, 2019

Conversation

pdudits
Copy link
Contributor

@pdudits pdudits commented May 24, 2019

After HK2 upgrade, the @Named annotation prevents the config object to be
added into config automatically.

To test, backup a Payara4 domain, and restore it into Payara5. Before it failed because of this injection not being satisfied, now it will only compain about missing Grizzly ALPN classes (but will start).

… into domain

After HK2 upgrade, the @nAmed annotation prevents the config object to be
added into config automatically.
@pdudits
Copy link
Contributor Author

pdudits commented May 24, 2019

Jenkins test please

@arjantijms
Copy link
Contributor

now it will only compain about missing Grizzly ALPN classes (but will start).

This may need further investigation?

@pdudits
Copy link
Contributor Author

pdudits commented May 27, 2019

This may need further investigation?

No, it is known issue (next step in migration guide is adding relevant JVM options). However internal issue was created ti possibly automate that step via asadmin start-domain --upgrade.

@pdudits pdudits requested review from AlanRoth and removed request for MattGill98 May 31, 2019 08:29
@pdudits pdudits merged commit ec48e4e into payara:master Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants