Payara5 服务器不会部署：未知协议 RFB

【问题标题】：Payara5 Server will not deploy: Unknown Protocol RFBPayara5 服务器不会部署：未知协议 RFB
【发布时间】：2020-02-19 15:06:48
【问题描述】：

在干净的 Eclipse 环境中，payara5 不会部署。我已经下载了正确版本的服务器，使用 java 1.8 并简单地添加了新服务器来启动它。我无法摆脱这个错误。 payara 登陆页面有效，但是管理控制台超时。任何帮助表示赞赏。

    2019-10-23T13:13:32.432+0200|INFORMATION: Running Payara Version: Payara Server  5.193.1 #badassfish (build 275)
2019-10-23T13:13:32.438+0200|INFORMATION: Server log file is using Formatter class: com.sun.enterprise.server.logging.ODLLogFormatter
2019-10-23T13:13:33.015+0200|INFORMATION: Registered fish.payara.ha.hazelcast.store.HazelcastBackingStoreFactoryProxy for persistence-type = hazelcast in BackingStoreFactoryRegistry
2019-10-23T13:13:33.173+0200|INFORMATION: Network Listener http-listener-1 started in: 18ms - bound to [/0.0.0.0:8080]
2019-10-23T13:13:33.202+0200|INFORMATION: Network Listener http-listener-2 started in: 4ms - bound to [/0.0.0.0:8181]
2019-10-23T13:13:33.213+0200|INFORMATION: Network Listener admin-listener started in: 3ms - bound to [/0.0.0.0:4848]
2019-10-23T13:13:33.215+0200|INFORMATION: Grizzly 2.4.3 started in: 352ms - bound to [http-listener-1:8080, http-listener-2:8181, admin-listener:4848]
2019-10-23T13:13:33.305+0200|INFORMATION: Network Listener iiop-service started in: 3ms - bound to [/0.0.0.0:3700]
2019-10-23T13:13:33.404+0200|INFO: HV000001: Hibernate Validator 6.0.16.Final
2019-10-23T13:13:35.437+0200|WARNUNG: [172.30.241.97]:4900 [development] [3.12] Connection[id=3, /172.30.241.97:53016->/172.30.241.97:5900, qualifier=null, endpoint=[172.30.241.97]:5900, alive=false, type=NONE] closed. Reason: Exception in Connection[id=3, /172.30.241.97:53016->/172.30.241.97:5900, qualifier=null, endpoint=[172.30.241.97]:5900, alive=true, type=NONE], thread=hz._hzInstance_1_development.IO.thread-out-1
java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen
    at sun.nio.ch.SocketDispatcher.write0(Native Method)
    at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51)
    at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
    at sun.nio.ch.IOUtil.write(IOUtil.java:65)
    at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
    at com.hazelcast.internal.networking.nio.NioOutboundPipeline.flushToSocket(NioOutboundPipeline.java:273)
    at com.hazelcast.internal.networking.nio.NioOutboundPipeline.process(NioOutboundPipeline.java:207)
    at com.hazelcast.internal.networking.nio.NioPipeline.run(NioPipeline.java:227)
    at com.hazelcast.internal.networking.nio.NioThread.processTaskQueue(NioThread.java:341)
    at com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:276)
    at com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:235)

2019-10-23T13:13:35.437+0200|WARNUNG: [172.30.241.97]:4900 [development] [3.12] Connection[id=1, /10.82.9.38:53013->/10.82.9.38:5900, qualifier=null, endpoint=[10.82.9.38]:5900, alive=false, type=NONE] closed. Reason: Exception in Connection[id=1, /10.82.9.38:53013->/10.82.9.38:5900, qualifier=null, endpoint=[10.82.9.38]:5900, alive=true, type=NONE], thread=hz._hzInstance_1_development.IO.thread-out-2
java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen
    at sun.nio.ch.SocketDispatcher.write0(Native Method)
    at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51)
    at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
    at sun.nio.ch.IOUtil.write(IOUtil.java:65)
    at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
    at com.hazelcast.internal.networking.nio.NioOutboundPipeline.flushToSocket(NioOutboundPipeline.java:273)
    at com.hazelcast.internal.networking.nio.NioOutboundPipeline.process(NioOutboundPipeline.java:207)
    at com.hazelcast.internal.networking.nio.NioPipeline.run(NioPipeline.java:227)
    at com.hazelcast.internal.networking.nio.NioThread.processTaskQueue(NioThread.java:341)
    at com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:276)
    at com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:235)

2019-10-23T13:13:35.437+0200|WARNUNG: [172.30.241.97]:4900 [development] [3.12] Connection[id=4, /10.0.75.1:53015->/10.0.75.1:5900, qualifier=null, endpoint=[10.0.75.1]:5900, alive=false, type=NONE] closed. Reason: Exception in Connection[id=4, /10.0.75.1:53015->/10.0.75.1:5900, qualifier=null, endpoint=[10.0.75.1]:5900, alive=true, type=NONE], thread=hz._hzInstance_1_development.IO.thread-out-0
java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen
    at sun.nio.ch.SocketDispatcher.write0(Native Method)
    at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51)
    at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
    at sun.nio.ch.IOUtil.write(IOUtil.java:65)
    at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
    at com.hazelcast.internal.networking.nio.NioOutboundPipeline.flushToSocket(NioOutboundPipeline.java:273)
    at com.hazelcast.internal.networking.nio.NioOutboundPipeline.process(NioOutboundPipeline.java:207)
    at com.hazelcast.internal.networking.nio.NioPipeline.run(NioPipeline.java:227)
    at com.hazelcast.internal.networking.nio.NioThread.processTaskQueue(NioThread.java:341)
    at com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:276)
    at com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:235)

和

2019-10-23T13:13:39.427+0200|WARNUNG: [172.30.241.97]:4900 [development] [3.12] Connection[id=18, /192.168.56.1:53035->/192.168.56.1:5900, qualifier=null, endpoint=[192.168.56.1]:5900, alive=false, type=NONE] closed. Reason: Exception in Connection[id=18, /192.168.56.1:53035->/192.168.56.1:5900, qualifier=null, endpoint=[192.168.56.1]:5900, alive=true, type=NONE], thread=hz._hzInstance_1_development.IO.thread-in-1
java.lang.IllegalStateException: Unknown protocol: RFB
    at com.hazelcast.nio.tcp.UnifiedProtocolDecoder.onRead(UnifiedProtocolDecoder.java:107)
    at com.hazelcast.internal.networking.nio.NioInboundPipeline.process(NioInboundPipeline.java:135)
    at com.hazelcast.internal.networking.nio.NioThread.processSelectionKey(NioThread.java:369)
    at com.hazelcast.internal.networking.nio.NioThread.processSelectionKeys(NioThread.java:354)
    at com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:280)
    at com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:235)

【问题讨论】：

    标签： java jakarta-ee server glassfish payara


    【解决方案1】：

    这是一个已知问题。看这里： https://github.com/payara/Payara/issues/3995

    编辑：如果您不需要 Hazelcast，您可以按如下方式禁用它：

    ./bin/asadmin set-hazelcast-configuration --enabled=false

    （如果需要 VNC，也可以更改 Hazelcast 端口）

    Edit2：对于 Payara 的下一个版本，您将能够在创建域时直接更改 Hazelcast 端口：https://github.com/payara/Payara/pull/4270

    【讨论】：

    • 谢谢！卸载 VNC 解决了我的问题。我已经尝试用任务管理器结束它。它会自动重启并阻塞端口 5900。
    • @christoph-john 我得到了./bin/asadmin set-hazelcast-configuration --enabled=false 远程服务器不监听 [localhost:4848] 上的请求。服务器起来了吗？没有这样的本地命令：set-hazelcast-configuration。无法访问服务器远程执行命令。验证服务器是否可用。命令 set-hazelcast-configuration 失败。 %
    • @joseluisbz 发出命令时Payara运行时会发生什么？
    • @ChristophJohn ahh OK，Payara 运行时工作... % sh payara5-2020-3/bin/asadmin set-hazelcast-configuration --startport=5902 命令 set-hazelcast-configuration 执行成功。 %检测到配置。谢谢！
    【解决方案2】：

    我能够解决问题。确保 TightVNCServer 没有阻塞端口 5900。只是用任务管理器结束它是行不通的。它会自动重启。在我的情况下，只有卸载有助于解锁端口 5900 并运行 glassfish payara 服务器。

    【讨论】：

      猜你喜欢
      • 2011-11-11
      • 2012-03-08
      • 2019-03-28
      • 1970-01-01
      • 2017-09-09
      • 1970-01-01
      • 2021-08-22
      • 2014-04-17
      • 2019-01-14
      相关资源
      最近更新 更多
      热门标签
      Java Python linux javascript Mysql C# Docker 算法 前端 SpringBoot Redis Vue spring 设计模式 .net core .net kubernetes c++ 数据库 数据结构 大数据 js 机器学习 微服务 Android Go 程序员 面试 JVM ASP.net core 云原生 人工智能 后端 PHP git CSS golang k8s Nginx Django mybatis 深度学习 多线程 React 架构 devops 爬虫 云计算 Spring Boot LeetCode