Hazelcast管理中心-无法通信的成员

问题描述 投票：2回答：1

我有此配置要连接：

config.getManagementCenterConfig().setEnabled(true);
config.getManagementCenterConfig().setUrl("http://localhost:8096/hazelcast-mancenter");

管理中心控制台上的错误：

2019-05-29 12:44:27 [qtp873415566-15] WARN  org.eclipse.jetty.server.HttpChannel - /hazelcast-mancenter/collector.do
org.springframework.web.util.NestedServletException: Request processing failed; nested exception is com.hazelcast.webmonitor.model.DeserializationException: nodeState field is null
        at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:982)
        at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
        at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:208)
        at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:177)
        at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:347)
        at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:263)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1634)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317)

客户端springboot应用程序控制台上的错误：

2019-05-29 12:54:27.059  INFO [-,,,] 12068 --- [           main] c.h.i.m.ManagementCenterService          : [10.1.204.138]:5701 [dev] [3.7.7] Hazelcast will connect to Hazelcast Management Center on address: 
http://localhost:8096/hazelcast-mancenter
2019-05-29 12:54:27.090  INFO [-,,,] 12068 --- [           main] com.hazelcast.core.LifecycleService      : [10.1.204.138]:5701 [dev] [3.7.7] [10.1.204.138]:5701 is STARTED
2019-05-29 12:54:27.090  INFO [-,,,] 12068 --- [MC.State.Sender] c.h.i.p.impl.PartitionStateManager       : [10.1.204.138]:5701 [dev] [3.7.7] Initializing cluster partition table arrangement...
2019-05-29 12:54:27.115  INFO [-,,,] 12068 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'hazelcastInstance' of type [com.hazelcast.instance.HazelcastInstanceProxy] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-05-29 12:54:27.197  INFO [-,,,] 12068 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'cacheManager' of type [com.hazelcast.spring.cache.HazelcastCacheManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-05-29 12:54:27.205  INFO [-,,,] 12068 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'cacheAutoConfigurationValidator' of type [org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration$CacheManagerValidator] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-05-29 12:54:27.292  INFO [-,,,] 12068 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$a3818d32] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-05-29 12:54:27.342  INFO [-,,,] 12068 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.sleuth.instrument.web.client.feign.TraceFeignClientAutoConfiguration$FeignBeanPostProcessorConfiguration' of type [org.springframework.cloud.sleuth.instrument.web.client.feign.TraceFeignClientAutoConfiguration$FeignBeanPostProcessorConfiguration$$EnhancerBySpringCGLIB$$c6f962fb] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-05-29 12:54:27.385  INFO [-,,,] 12068 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.sleuth.instrument.async.AsyncDefaultAutoConfiguration' of type [org.springframework.cloud.sleuth.instrument.async.AsyncDefaultAutoConfiguration$$EnhancerBySpringCGLIB$$6f4b3654] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-05-29 12:54:28.645  INFO [-,,,] 12068 --- [           main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat initialized with port(s): 8090 (http)
2019-05-29 12:54:28.667  INFO [-,,,] 12068 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2019-05-29 12:54:28.669  INFO [-,,,] 12068 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet Engine: Apache Tomcat/8.5.15
2019-05-29 12:54:28.799  WARN [-,,,] 12068 --- [MulticastThread] c.h.i.cluster.impl.MulticastService      : [10.1.204.138]:5701 [dev] [3.7.7] Received a JoinRequest with a different packet version! This -> 4, Incoming -> -84, Sender -> /10.1.204.123
2019-05-29 12:54:29.260  INFO [-,,,] 12068 --- [ost-startStop-1] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2019-05-29 12:54:29.260  INFO [-,,,] 12068 --- [ost-startStop-1] o.s.web.context.ContextLoader            : Root WebApplicationContext: initialization completed in 12542 ms
2019-05-29 12:54:30.158  WARN [-,,,] 12068 --- [MC.State.Sender] c.h.i.m.ManagementCenterService          : [10.1.204.138]:5701 [dev] [3.7.7] Failed to send response, responseCode:405 url:http://localhost:8096/hazelcast-mancenter/collector.do

我没有看到要进行的任何配置来设置nodeStatus，如错误堆栈跟踪中所述。

请让我们知道要进行什么配置。谢谢！

java spring-boot caching hazelcast
1个回答
0
投票

如@emre在评论中所述，有关于它的官方文本：

...管理中心与具有相同或先前次要版本的Hazelcast IMDG群集成员兼容。例如，Hazelcast Management Center版本3.12.x可与版本3.11.x或3.12.x的Hazelcast IMDG群集成员一起使用。

来自Hazelcast Management Center Documentation。

异常消息（DeserializationException: nodeState field is null）并没有真正帮助实现这一点。我也发生了同样的事情，我在版本1.5.9.RELEASE中使用的是Spring boot parent，因此它具有hazelcast（3.7.8）的依赖关系。您始终可以在spring-boot-dependencies项目的pom.xml文件中检查spring自动配置的依赖项的版本。在那里，您可以在如下定义的属性部分中看到hazelcast版本：

<hazelcast.version>3.7.8</hazelcast.version>

您可以

  • 将spring-boot-starter-parent版本更改为较新的版本（例如2.2.0.RELEASE），该问题应消失或
  • 仅使用较新的hazelcast版本覆盖您自己的pom.xml中的属性。
最新问题
© www.soinside.com 2019 - 2024. All rights reserved.