[jboss-jira] [JBoss JIRA] (WFLY-11553) Wildfly 14 is not getting startjava.lang.NoClassDefFoundError: org/wildfly/common/net/HostName

David Lloyd (Jira) issues at jboss.org
Thu Jan 3 11:04:00 EST 2019


     [ https://issues.jboss.org/browse/WFLY-11553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd closed WFLY-11553.
------------------------------
      Assignee:     (was: Jason Greene)
    Resolution: Rejected


For help with WildFly usage, please refer to the user forums: https://developer.jboss.org/en/wildfly?view=discussion

> Wildfly 14 is not getting startjava.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
> ----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-11553
>                 URL: https://issues.jboss.org/browse/WFLY-11553
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 14.0.0.Final
>            Reporter: Arpit Arora
>            Priority: Blocker
>
> Hi Team,
> I am facing this issue while Trying to start the Wildfly14.
> Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
> Listening for transport dt_socket at address: 8787
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogLevelInitTask to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogLevelInitTask
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
>         at org.jboss.logmanager.ExtLogRecord.<init>(ExtLogRecord.java:87)
>         at org.jboss.logmanager.Logger.log(Logger.java:796)
>         at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:53)
>         at org.jboss.logging.Logger.logf(Logger.java:2398)
>         at org.jboss.msc.service.ServiceLogger_$logger.greeting(ServiceLogger_$logger.java:40)
>         at org.jboss.msc.service.ServiceContainerImpl.<clinit>(ServiceContainerImpl.java:91)
>         at org.jboss.msc.service.ServiceContainer$Factory.create(ServiceContainer.java:250)
>         at org.jboss.as.server.BootstrapImpl$ShutdownHook.register(BootstrapImpl.java:229)
>         at org.jboss.as.server.BootstrapImpl$ShutdownHook.access$100(BootstrapImpl.java:219)
>         at org.jboss.as.server.BootstrapImpl.<init>(BootstrapImpl.java:70)
>         at org.jboss.as.server.Bootstrap$Factory.newInstance(Bootstrap.java:278)
>         at org.jboss.as.server.Main.main(Main.java:106)
>         at org.jboss.modules.Module.run(Module.java:352)
>         at org.jboss.modules.Module.run(Module.java:320)
>         at org.jboss.modules.Main.main(Main.java:593)
> Please tell me the workaround for the same, as soon as poosible



--
This message was sent by Atlassian Jira
(v7.12.1#712002)


More information about the jboss-jira mailing list