本文介绍了Payara5服务器将不会部署:未知协议RFB的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
在干净的日食环境中，不会部署payara5.我已经使用Java 1.8下载了正确版本的服务器，并只是将其添加到新服务器中以启动它.我无法摆脱这个错误.payara登陆页面有效，但是管理控制台超时.任何帮助表示赞赏.
In a clean eclipse environment payara5 will not deploy. I have downloaded the correct version of the server, using java 1.8 and simply added it with new server to start it. I cannot get rid of this error. The payara landing page works, however administrative console timeouts. Any help aprreciated.
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)
推荐答案
这是一个已知问题.看这里: https://github.com/payara/Payara/issues/3995
This is a known issue. See here:https://github.com/payara/Payara/issues/3995
如果不需要Hazelcast，则可以按以下方式禁用它:
if you don't need Hazelcast you can disable it as follows:
./bin/asadmin set-hazelcast-configuration --enabled=false
(或在需要VNC时更改Hazelcast端口)
(or change the Hazelcast port if you need VNC)
Edit2:对于下一版本的Payara，您将能够在创建域时直接更改Hazelcast端口: https://github.com/payara/Payara/pull/4270
for the next version of Payara you will be able to change the Hazelcast port directly on creation of the domain: https://github.com/payara/Payara/pull/4270
这篇关于Payara5服务器将不会部署:未知协议RFB的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！