[JBoss JIRA] (ISPN-9556) NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9556?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9556:
----------------------------------
Status: Open (was: New)
> NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
> --------------------------------------------------------------------------
>
> Key: ISPN-9556
> URL: https://issues.jboss.org/browse/ISPN-9556
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: Tristan Tarrant
> Priority: Critical
> Fix For: 9.4.0.Final
>
>
> When running Infinispan server in Openshift it is failing due:
> {noformat}
> 18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9556) NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9556?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9556:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6287
> NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
> --------------------------------------------------------------------------
>
> Key: ISPN-9556
> URL: https://issues.jboss.org/browse/ISPN-9556
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: Tristan Tarrant
> Priority: Critical
> Fix For: 9.4.0.Final
>
>
> When running Infinispan server in Openshift it is failing due:
> {noformat}
> 18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9556) NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9556?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9556:
----------------------------------
Fix Version/s: 9.4.0.Final
> NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
> --------------------------------------------------------------------------
>
> Key: ISPN-9556
> URL: https://issues.jboss.org/browse/ISPN-9556
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: Tristan Tarrant
> Priority: Critical
> Fix For: 9.4.0.Final
>
>
> When running Infinispan server in Openshift it is failing due:
> {noformat}
> 18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9556) NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-9556?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-9556:
-------------------------------------
Assignee: Tristan Tarrant
> NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
> --------------------------------------------------------------------------
>
> Key: ISPN-9556
> URL: https://issues.jboss.org/browse/ISPN-9556
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: Tristan Tarrant
> Priority: Critical
>
> When running Infinispan server in Openshift it is failing due:
> {noformat}
> 18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9556) NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
by Diego Lovison (JIRA)
[ https://issues.jboss.org/browse/ISPN-9556?page=com.atlassian.jira.plugin.... ]
Diego Lovison updated ISPN-9556:
--------------------------------
Steps to Reproduce:
1) Create a docker file `Dockerfile-infinispan-server`
{code:docker}
FROM jboss/infinispan-server
COPY infinispan-server-cloud.xml /opt/jboss/infinispan-server/standalone/configuration/
{code}
2) Build using: docker build -t infinispan-server-dlovison -f Dockerfile-infinispan-server .
3) Execute:
{code:bash}
cat /etc/resolv.conf | grep nameserver | awk '{print $2}'
{code}
Copy the first address. Example: 1.1.1.1
4) Execute: docker run -i -t infinispan-server-dlovison:latest -c infinispan-server-cloud.xml -Djboss.default.jgroups.stack=dnsping -Djgroups.dns_address=1.1.1.1
Keep in mind that you need change '1.1.1.1' and use the value returned from the step 3
----
It will return an error:
{noformat}
18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper
{noformat}
----
Maybe the fix is the same from: ISPN-9534
> NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
> --------------------------------------------------------------------------
>
> Key: ISPN-9556
> URL: https://issues.jboss.org/browse/ISPN-9556
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Priority: Critical
>
> When running Infinispan server in Openshift it is failing due:
> {noformat}
> 18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9556) NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
by Diego Lovison (JIRA)
Diego Lovison created ISPN-9556:
-----------------------------------
Summary: NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift
Key: ISPN-9556
URL: https://issues.jboss.org/browse/ISPN-9556
Project: Infinispan
Issue Type: Bug
Reporter: Diego Lovison
Priority: Critical
When running Infinispan server in Openshift it is failing due:
{noformat}
18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9543) Unable to login in management console after securing cache container
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-9543?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9543:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Unable to login in management console after securing cache container
> --------------------------------------------------------------------
>
> Key: ISPN-9543
> URL: https://issues.jboss.org/browse/ISPN-9543
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management, Security, Server
> Affects Versions: 9.4.0.CR3
> Environment: JDG 7.2.2 continuously logs errors in server log and management console becomes unavailable.
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.4.0.Final
>
>
> I configured cache container security in standalone.xml file :
> ~~~
> <cache-container name="local" default-cache="default" statistics="true">
> <security>
> <authorization>
> <identity-role-mapper />
> <role name="admin" permissions="ALL"/>
> </authorization>
> </security>
> ~~~
> I created a management user "Saurabh" and assigned role "admin" to him- PFA attached mgmt-groups.properties.
> Below is the exception snippet :
> ~~~
> 2018-09-18 22:57:57,118 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 4) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
> ("subsystem" => "datagrid-infinispan"),
> ("cache-container" => "local")
> ]): java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [org.jboss.as.core.security.SimplePrincipal@6f98bb1c, saurabh@ManagementRealm, admin@ManagementRealm, admin, InetAddressPrincipal <127.0.0.1/127.0.0.1>]' lacks 'ADMIN' permission
> at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:87)
> ~~~
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9541) Module initialization is not thread-safe
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9541?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9541:
-------------------------------
Comment: was deleted
(was: These server startup errors are probably related:
{noformat}
16:57:41,261 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan-endpoint.hotrod.hotrod-connector: DGENDPT10004: Failed to start HotRodServer
at org.infinispan.server.endpoint.subsystem.ProtocolServerService.start(ProtocolServerService.java:160)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.infinispan.commons.CacheConfigurationException: ISPN005029: No task manager available to register the admin operations handler
at org.infinispan.server.core.AbstractProtocolServer.registerAdminOperationsHandler(AbstractProtocolServer.java:70)
at org.infinispan.server.core.AbstractProtocolServer.startInternal(AbstractProtocolServer.java:55)
at org.infinispan.server.hotrod.HotRodServer.startInternal(HotRodServer.java:250)
at org.infinispan.server.hotrod.HotRodServer.startInternal(HotRodServer.java:106)
at org.infinispan.server.core.AbstractProtocolServer.start(AbstractProtocolServer.java:79)
at org.infinispan.server.endpoint.subsystem.SecurityActions$6.run(SecurityActions.java:136)
at org.infinispan.server.endpoint.subsystem.SecurityActions$6.run(SecurityActions.java:133)
at org.infinispan.security.Security.doPrivileged(Security.java:44)
at org.infinispan.server.endpoint.subsystem.SecurityActions.doPrivileged(SecurityActions.java:42)
at org.infinispan.server.endpoint.subsystem.SecurityActions.startProtocolServer(SecurityActions.java:140)
at org.infinispan.server.endpoint.subsystem.ProtocolServerService.startProtocolServer(ProtocolServerService.java:194)
at org.infinispan.server.endpoint.subsystem.ProtocolServerService.start(ProtocolServerService.java:152)
... 8 more
{noformat}
{noformat}
16:57:42,424 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.datagrid-infinispan-endpoint.rest.rest-connector: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan-endpoint.rest.rest-connector: DGENDPT10016: Could not start the web context for the REST Server
at org.infinispan.server.endpoint.subsystem.RestService.start(RestService.java:158)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at org.infinispan.server.core.AbstractProtocolServer.registerTransportMBean(AbstractProtocolServer.java:115)
at org.infinispan.server.core.AbstractProtocolServer.startTransport(AbstractProtocolServer.java:92)
at org.infinispan.server.core.AbstractProtocolServer.startInternal(AbstractProtocolServer.java:61)
at org.infinispan.rest.RestServer.startInternal(RestServer.java:85)
at org.infinispan.rest.RestServer.startInternal(RestServer.java:23)
at org.infinispan.server.core.AbstractProtocolServer.start(AbstractProtocolServer.java:79)
at org.infinispan.server.endpoint.subsystem.RestService.start(RestService.java:155)
... 8 more
{noformat}
https://ci.infinispan.org/job/Infinispan/job/PR-6247/1/testReport/junit/o...
)
> Module initialization is not thread-safe
> ----------------------------------------
>
> Key: ISPN-9541
> URL: https://issues.jboss.org/browse/ISPN-9541
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Server
> Affects Versions: 9.4.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 9.4.0.Final
>
>
> In my ISPN-9127 fix I created a {{BasicComponentRegistry}} interface that represents a mostly-read-only collection of components. It has {{replaceComponent()}} method and a {{rewire()}} method for testing purposes, but it turns out modules were also relying on the ability to replace existing components in order to work.
> Replacing global components is normally safe during the {{ModuleLifecycle.cacheManagerStarting()}}, because none of the components are started yet, so when a component starts later we can still start its dependencies first. But because some modules starts some global components, e.g. by calling {{manager.getCache(name)}}, that assumption breaks.
> The {{infinispan-server-event-logger}} module is a bit more sneaky: it doesn't replace a component, instead it replaces the actual implementation of the event logger in the {{EventLogManager}} component. Events that happen before the module's {{cacheManagerStarting()}} or after {{cacheManagerStopping()}} will be silently dropped from the persistent event log.
> I am investigating making the module a factory of factories. Instead of having a monolitic {{cacheManagerStarting()}} method, it could define a set of components that it can create, and a set of components that should be started before the cache manager is "running". We probably need a way to depend on other modules as well, maybe reusing the {{@Inject}} and {{@ComponentName}} annotations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months
[JBoss JIRA] (ISPN-9544) Server cache manager stop/restart breaks cache topology management
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-9544?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9544:
-------------------------------
Summary: Server cache manager stop/restart breaks cache topology management (was: Asymmetric ForkChannels break cache topology management)
> Server cache manager stop/restart breaks cache topology management
> ------------------------------------------------------------------
>
> Key: ISPN-9544
> URL: https://issues.jboss.org/browse/ISPN-9544
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 9.4.0.CR3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
>
> Before {{FORK}} was introduced, {{ClsuterTopologyManagerImpl}} and {{LocalTopologyManagerImpl}} assumed that the coordinator would always reply to other members' requests. After the introduction of {{FORK}} we added some hacks to work around the fact that the coordinator may not yet have a {{ForkChannel}} with our ID running **yet**, but we still expect the {{FORK}} setup to be symmetric after a reasonable amount of time.
> Stopping a {{FORK}} and starting it back without restarting the underlying channel also doesn't work, because a {{FORK}} start/stop does not trigger a new view. When a node sends a request to the coordinator and receives back a {{CacheNotFoundResponse}}, it assumes that it will also receive a new view, but if the {{CacheNotFoundResponse}} was a consequence of stopping a single {{DefaultCacheManager}}/{{ForkChannel}}, that view will never arrive.
> We don't restart individual cache managers in our tests, but the spark connector test suite does it, and it sometimes fails because of it:
> {noformat}
> 2018-09-26 21:18:03,035 INFO [org.infinispan.CLUSTER] (MSC service thread 1-4) ISPN000094: Received new cluster view for channel cluster: [server2|6] (3) [server2, server0, server1]
> 2018-09-26 21:18:05,778 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) server1 sending request 37 to server2: CacheTopologyControlCommand{cache=org.infinispan.spark.suites.DistributedSuite, type=POLICY_GET_STATUS, sender=server1, joinInfo=null, topologyId=0, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, phase=null, actualMembers=null, throwable=null, viewId=6}
> 2018-09-26 21:18:05,795 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (jgroups-4,server1) server1 received response for request 37 from server2: CacheNotFoundResponse
> 2018-09-26 21:18:05,798 TRACE [org.infinispan.topology.LocalTopologyManagerImpl] (MSC service thread 1-5) Coordinator left the cluster while querying rebalancing status, retrying
> 2018-09-26 21:18:05,823 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) server1 sending request 41 to server2: CacheTopologyControlCommand{cache=org.infinispan.spark.suites.DistributedSuite, type=POLICY_GET_STATUS, sender=server1, joinInfo=null, topologyId=0, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, phase=null, actualMembers=null, throwable=null, viewId=6}
> 2018-09-26 21:18:05,841 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (jgroups-19,server1) server1 received response for request 41 from server2: CacheNotFoundResponse
> 2018-09-26 21:18:05,846 TRACE [org.infinispan.topology.LocalTopologyManagerImpl] (MSC service thread 1-5) Coordinator left the cluster while querying rebalancing status, retrying
> 2018-09-26 21:18:05,871 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-5) Waiting for transaction data for view 7, current view is 6
> 2018-09-26 21:19:05,779 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered."org.infinispan.spark.suites.DistributedSuite": org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered."org.infinispan.spark.suites.DistributedSuite": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1364)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.infinispan.util.concurrent.TimeoutException: ISPN000451: Timed out waiting for view 7, current view is 6
> at org.infinispan.topology.LocalTopologyManagerImpl.waitForView(LocalTopologyManagerImpl.java:558)
> at org.infinispan.topology.LocalTopologyManagerImpl.executeOnCoordinatorRetry(LocalTopologyManagerImpl.java:598)
> at org.infinispan.topology.LocalTopologyManagerImpl.isCacheRebalancingEnabled(LocalTopologyManagerImpl.java:580)
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:233)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:1056)
> at org.infinispan.cache.impl.AbstractDelegatingCache.start(AbstractDelegatingCache.java:451)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:653)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:598)
> at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:481)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:465)
> at org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager.getCache(AbstractDelegatingEmbeddedCacheManager.java:157)
> at org.infinispan.server.infinispan.SecurityActions.lambda$startCache$4(SecurityActions.java:122)
> at org.infinispan.security.Security.doPrivileged(Security.java:44)
> at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:69)
> at org.infinispan.server.infinispan.SecurityActions.startCache(SecurityActions.java:126)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:87)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 3 months