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-4104 Fixes NPE in monitoring console startup in case hazelcast is disabled #4188

Merged
merged 1 commit into from
Aug 30, 2019

Conversation

jbee
Copy link
Contributor

@jbee jbee commented Aug 30, 2019

PR fixes error reported in #4186 .

@jbee jbee self-assigned this Aug 30, 2019
@jbee jbee requested a review from Pandrex247 August 30, 2019 06:47
@jbee
Copy link
Contributor Author

jbee commented Aug 30, 2019

jenkins test please

Copy link
Contributor

@cubastanley cubastanley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

\o/

Copy link

@AlanRoth AlanRoth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I quickbuild and skiptests on Windows 10, maybe environment issue but looks related?

./asadmin start-domain
Exception in thread "main" java.lang.IllegalStateException: The service 'org.glassfish.hk2.api.DynamicConfigurationService' could not be located by the locator 'ServiceLocatorImpl(__HK2_Generated_0,0,1909546776)'!
        at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.getServiceOrFail(AbstractModulesRegistryImpl.java:141)
        at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.initializeServiceLocator(AbstractModulesRegistryImpl.java:124)
        at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.newServiceLocator(AbstractModulesRegistryImpl.java:119)
        at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.createServiceLocator(AbstractModulesRegistryImpl.java:197)
        at com.sun.enterprise.module.common_impl.AbstractModulesRegistryImpl.createServiceLocator(AbstractModulesRegistryImpl.java:203)
        at com.sun.enterprise.module.single.StaticModulesRegistry.createServiceLocator(StaticModulesRegistry.java:64)
        at com.sun.enterprise.admin.cli.CLIContainer.getServiceLocator(CLIContainer.java:212)
        at com.sun.enterprise.admin.cli.CLIContainer.getLocalCommand(CLIContainer.java:244)
        at com.sun.enterprise.admin.cli.CLICommand.getCommand(CLICommand.java:240)
        at com.sun.enterprise.admin.cli.AdminMain.executeCommand(AdminMain.java:362)
        at com.sun.enterprise.admin.cli.AdminMain.doMain(AdminMain.java:298)
        at org.glassfish.admin.cli.AsadminMain.main(AsadminMain.java:56)

@jbee
Copy link
Contributor Author

jbee commented Aug 30, 2019

@AlanRoth Does not look related to me but we can wait with the merge and look for more insight.

@AlanRoth
Copy link

@jbee If you think it's unrelated, you're free to merge. :)

@svendiedrichsen
Copy link
Contributor

@jbee Would this fix lead to a release of Payara 5.193.1?

@dmatej
Copy link
Contributor

dmatej commented Aug 30, 2019

@AlanRoth Usually this is caused by one of these (on Linux):

  • JDK11 as default java program (no AS_HOME or JAVA_HOME set)
  • some instance is already running

@jbee
Copy link
Contributor Author

jbee commented Aug 30, 2019

@svendiedrichsen I have a chat internal on a 5.193.1 release.

Copy link

@AlanRoth AlanRoth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ignore my last comment, fix works :)

@jbee
Copy link
Contributor Author

jbee commented Aug 30, 2019

@svendiedrichsen We feel that turning of hazelcast on DAS is so uncommon that a release isn't justified. There is an easy enough workaround in removing the monitoring-console-core.jar from glassfish/modules that can be applied by those that use the setting.

@svendiedrichsen
Copy link
Contributor

@svendiedrichsen We feel that turning of hazelcast on DAS is so uncommon that a release isn't justified. There is an easy enough workaround in removing the monitoring-console-core.jar from glassfish/modules that can be applied by those that use the setting.

Thanks for the info, @jbee .

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.

6 participants