当前位置: 首页 > 知识库问答 >
问题:

升级Mac OS后glassfish-4启动失败

荀俊迈
2023-03-14

我已经升级到MacOS Sierra,我的Netbeans 8.0.2在尝试运行Glassfish时抛出一个错误。

请检查服务器管理员用户名和密码属性。

另外,请检查服务器日志文件以了解其他可能的原因。

我尝试了在stackoverflow中找到的所有可行的解决方案,但都没有成功。

Glassfish 4 Admin未从Netbeans 7.4运行(密码不正确)

这是玻璃鱼的日志

objc[35340]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/bin/java (0x1000a54c0) and /Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/jre/lib/libinstrument.dylib (0x1001b84e0). One of the two will be used. Which one is undefined.
Listening for transport dt_socket at address: 9009
Launching GlassFish on Felix platform
Nov 02, 2016 11:28:52 AM com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner createBundleProvisioner
INFO: Create bundle provisioner class = class com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner.
Nov 02, 2016 11:28:53 AM com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner$DefaultCustomizer getLocations
WARNING: Skipping entry  because it is not an absolute URI.
Nov 02, 2016 11:28:53 AM com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner$DefaultCustomizer getLocations
WARNING: Skipping entry  because it is not an absolute URI.
Registered com.sun.enterprise.glassfish.bootstrap.osgi.EmbeddedOSGiGlassFishRuntime@c76ff05 in service registry.
Found populator: com.sun.enterprise.v3.server.GFDomainXml
#!## LogManagerService.postConstruct : rootFolder=/Applications/NetBeans/glassfish-4.1/glassfish
#!## LogManagerService.postConstruct : templateDir=/Applications/NetBeans/glassfish-4.1/glassfish/lib/templates
#!## LogManagerService.postConstruct : src=/Applications/NetBeans/glassfish-4.1/glassfish/lib/templates/logging.properties
#!## LogManagerService.postConstruct : dest=/Applications/NetBeans/glassfish-4.1/glassfish/domains/domain4/config/logging.properties
Info:   Running GlassFish Version: GlassFish Server Open Source Edition  4.1  (build 13)
Info:   Server log file is using Formatter class: com.sun.enterprise.server.logging.ODLLogFormatter
Info:   Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
Info:   Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
Info:   Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.
Info:   Authorization Service has successfully initialized.
Info:   Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry
Info:   Grizzly Framework 2.3.15 started in: 58ms - bound to [/0.0.0.0:9090]
Info:   Grizzly Framework 2.3.15 started in: 12ms - bound to [/0.0.0.0:9191]
Info:   Grizzly Framework 2.3.15 started in: 2ms - bound to [/0.0.0.0:4848]
Info:   Grizzly Framework 2.3.15 started in: 1ms - bound to [/0.0.0.0:3700]
Info:   GlassFish Server Open Source Edition  4.1  (13) startup time : Felix (37,175ms), startup services(1,405ms), total(38,580ms)
Info:   Creating a SecureRMIServerSocketFactory @ 0.0.0.0 with ssl config = GlassFishConfigBean.org.glassfish.grizzly.config.dom.Ssl
Info:   SSLParams =org.glassfish.admin.mbeanserver.ssl.SSLParams@5baca86
Warning:   All SSL cipher suites disabled for network-listener(s).  Using SSL implementation specific defaults
Info:   SSLParams =org.glassfish.admin.mbeanserver.ssl.SSLParams@5baca86
Warning:   All SSL cipher suites disabled for network-listener(s).  Using SSL implementation specific defaults
Info:   Grizzly Framework 2.3.15 started in: 11ms - bound to [/0.0.0.0:7676]
Info:   Registered com.sun.enterprise.glassfish.bootstrap.osgi.EmbeddedOSGiGlassFishImpl@3baf6936 as OSGi service registration: org.apache.felix.framework.ServiceRegistrationImpl@4acb2510.
Info:   visiting unvisited references
Info:   Created HTTP listener http-listener-1 on host/port 0.0.0.0:9090
Info:   Created HTTP listener http-listener-2 on host/port 0.0.0.0:9191
Info:   Created HTTP listener admin-listener on host/port 0.0.0.0:4848
Info:   Created virtual server server
Info:   Created virtual server __asadmin
Info:   Setting JAAS app name glassfish-web
Info:   Virtual server server loaded default web module 
Info:   Java security manager is disabled.
Info:   Entering Security Startup Service.
Info:   Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
Info:   Security Service(s) started successfully.
Info:   visiting unvisited references
Info:   visiting unvisited references
Info:   visiting unvisited references
Info:   Initializing Mojarra 2.2.7 ( 20140610-1547 https://svn.java.net/svn/mojarra~svn/tags/2.2.7@13362) for context ''
Info:   HV000001: Hibernate Validator 5.0.0.Final
Info:   SSLServerSocket /0.0.0.0:8686 and [SSL: ServerSocket[addr=/0.0.0.0,localport=8686]] created
Info:   Loading application [__admingui] at [/]
Info:   Loading application __admingui done in 15,743 ms
Info:   JMXStartupService has started JMXConnector on JMXService URL service:jmx:rmi://10.57.116.239:8686/jndi/rmi://10.57.116.239:8686/jmxrmi

我不知道还能做什么。

请帮我解决这个问题。

共有1个答案

姬俊能
2023-03-14

您可以设置系统java版本,这可以由jenv完成;请参考http://boxingp.github.io/blog/2015/01/25/manage-multiple-versions-of-java-on-os-x/

 类似资料:
  • 我将camel从2.8.0升级到2.10.3版本,我的sftp组件开始出现故障。Afaik,sftp组件默认使用stepwise,在升级之前没有更改目录的麻烦。 cd与V2.8.0兼容 20130114 18:42:52,956信息[Camel(camel-1)线程#0-sftp://user@host/outgoing]remoteFileConsumer[133]:连接并登录到:sftp://

  • 我不知道具体的问题,但重启我的机器后,在Windows10顺便说一句,glassfish就不会再启动了。我的日志 版本=GlassFish Server Open Source Edition 3.1.2.2(build 5)java版本“1.7.0_51”java(TM)SE运行时环境(build 1.7.0_51-B13)java HotSpot(TM)64位服务器VM(build 24.51

  • 我最近刚刚将团队的一个Spring Boot应用程序从2.1.3版升级到2.3.0版,并将Hibernate版本从5.3.6.final升级到5.4.15.final。 一切都很好,但是现在当应用程序在服务器上启动时,启动需要800-900秒(大约15分钟),而以前只需要30秒。 需要注意的是,当在localhost上运行2.1.3和2.3.0时,应用程序的启动是相同的,大约为12-15秒。 只有

  • 我在周末将笔记本电脑从Kubuntu 12.04升级到12.10,一切看起来都很好,直到我重新开始工作。 笔记本电脑是一台通过php5 fpm运行Nginx和php的webdev机器,但现在看来php5 fpm不会启动。当我运行/etc/init时。d/php5 fpm重启我刚收到一条消息说失败。我在syslog或/var/log/fpm php中没有收到任何消息。www.log提供有关正在发生的

  • 我正在尝试将项目从3.6.10版升级到4.3.6版,在应用程序启动时出现“提交失败”错误。而不是使用: ,为了获得会话,现在我正在使用: 事务由TransactionManager和Spring的NameMatchTransactionAttribute资源处理。 这是我得到的堆栈跟踪: 这是我的会话工厂bean配置: