[JBoss JIRA] (WFLY-4975) Can't create colocated HA topology with JGroups discovery
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4975?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4975.
----------------------------
> Can't create colocated HA topology with JGroups discovery
> ---------------------------------------------------------
>
> Key: WFLY-4975
> URL: https://issues.jboss.org/browse/WFLY-4975
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Alpha5
> Reporter: Ondřej Kalman
> Assignee: Jeff Mesnil
> Priority: Blocker
> Fix For: 10.0.0.CR1
>
> Attachments: standalone-full-ha-1.xml, standalone-full-ha-2.xml
>
>
> Hi, I tried to start two nodes in colocated topology with JGroups as discovery method (it's defalut for EAP7), but i'm not able to do it. After both nodes are up, this exception starts spamming in logs:
> java.io.NotSerializableException: org.jgroups.JChannel
> 10:56:50,187 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> 10:56:50,188 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> 10:56:50,188 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> 10:56:50,188 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> 10:56:50,188 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> 10:56:50,188 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> 10:56:50,189 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> 10:56:50,189 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> 10:56:50,189 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> 10:56:50,189 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> 10:56:50,189 ERROR [stderr] (default I/O-5) at java.util.ArrayList.writeObject(ArrayList.java:747)
> 10:56:50,189 ERROR [stderr] (default I/O-5) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 10:56:50,190 ERROR [stderr] (default I/O-5) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 10:56:50,190 ERROR [stderr] (default I/O-5) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 10:56:50,190 ERROR [stderr] (default I/O-5) at java.lang.reflect.Method.invoke(Method.java:483)
> 10:56:50,190 ERROR [stderr] (default I/O-5) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:988)
> 10:56:50,190 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
> 10:56:50,190 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> 10:56:50,191 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> 10:56:50,191 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)
> 10:56:50,191 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)
> 10:56:50,191 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)
> 10:56:50,191 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)
> 10:56:50,192 ERROR [stderr] (default I/O-5) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> 10:56:50,192 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.config.impl.ConfigurationImpl.copy(ConfigurationImpl.java:1528)
> 10:56:50,192 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.server.cluster.ha.ColocatedHAManager.activateReplicatedBackup(ColocatedHAManager.java:190)
> 10:56:50,192 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.server.cluster.ha.ColocatedHAManager.activateBackup(ColocatedHAManager.java:104)
> 10:56:50,192 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.server.impl.ColocatedActivation$1.handlePacket(ColocatedActivation.java:141)
> 10:56:50,193 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.server.cluster.ClusterController$ClusterControllerChannelHandler.handlePacket(ClusterController.java:424)
> 10:56:50,193 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:652)
> 10:56:50,193 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:402)
> 10:56:50,193 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:379)
> 10:56:50,193 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694)
> 10:56:50,193 ERROR [stderr] (default I/O-5) at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:73)
> 10:56:50,194 ERROR [stderr] (default I/O-5) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
> 10:56:50,194 ERROR [stderr] (default I/O-5) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
> 10:56:50,194 ERROR [stderr] (default I/O-5) at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:242)
> 10:56:50,194 ERROR [stderr] (default I/O-5) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:339)
> 10:56:50,194 ERROR [stderr] (default I/O-5) at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:324)
> 10:56:50,194 ERROR [stderr] (default I/O-5) at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:847)
> 10:56:50,195 ERROR [stderr] (default I/O-5) at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435)
> 10:56:50,195 ERROR [stderr] (default I/O-5) at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371)
> 10:56:50,195 ERROR [stderr] (default I/O-5) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> 10:56:50,195 ERROR [stderr] (default I/O-5) at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> 10:56:50,195 ERROR [stderr] (default I/O-5) at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)
> 10:56:50,196 ERROR [stderr] (default I/O-5) at org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
> Is there anything wrong with my configs?
> I think that problem is in non serializable org.jgroups.JChannel
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-3663) WildFly should manage JGroups and Infinispan thread pools by default
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3663?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-3663.
----------------------------
> WildFly should manage JGroups and Infinispan thread pools by default
> --------------------------------------------------------------------
>
> Key: WFLY-3663
> URL: https://issues.jboss.org/browse/WFLY-3663
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
> Fix For: 10.0.0.Beta1
>
>
> In our default configuration, both JGroups and Infinispan manage their own thread pools. Unfortunately, both projects do not handle thread pool lifecycle so well. Both projects use ExecutorService.shutdownNow() to end their thread pool lifecycles. This means that a channel or cache can stop, but still leave active threads running (albeit interrupted). We should have services that manage the lifecycle of our thread pools which ensure that all threads have terminated during Service.stop().
> This causes occasional OOMs in the Windows CI testsuite runs, due to too many threads lying around.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-4668) mod-cluster configure via CLI may end with msg: Failed to start service Caused by: java.lang.NullPointerException"
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4668?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4668.
----------------------------
> mod-cluster configure via CLI may end with msg: Failed to start service Caused by: java.lang.NullPointerException"
> ------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4668
> URL: https://issues.jboss.org/browse/WFLY-4668
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 9.0.0.CR1
> Reporter: Jan Stourac
> Assignee: Stuart Douglas
> Fix For: 10.0.0.Alpha3
>
>
> When setting up mod-cluster via CLI then msg Failed to start service Caused by: java.lang.NullPointerException" may appear.
> Particular file where exception is thrown is: ModClusterService.java, line 90 . Reason for exception is that advertise socket binding has to have set multicast address also (mod cluster just expect it is set it does not check it). In case multicat address is set then adding mod-cluster filter is successful.
> I would expect that more reasonable message is print to user instead of generic NPE.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-5036) The infinispan-directory-provider jar is packaged in multiple modules
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5036?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5036.
----------------------------
> The infinispan-directory-provider jar is packaged in multiple modules
> ---------------------------------------------------------------------
>
> Key: WFLY-5036
> URL: https://issues.jboss.org/browse/WFLY-5036
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JPA / Hibernate
> Affects Versions: 10.0.0.Alpha6
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Priority: Minor
> Fix For: 10.0.0.CR1
>
>
> The module integrating Infinispan storage for Hibernate Search indexes is currently duplicated, as a result of a rename of the project ownership and it being moved from Hibernate to Infinispan for maintenance, and not all dependencies being in synch yet.
> This problem might be resolved by the move to feature packs, but creating this issue to make sure of that.
> As far as I know the problem doesn't result in any lack of functionality, other than taking some unnecessary space.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-5100) Server does not start when transaction subsystem configures journal object store
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5100?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5100.
----------------------------
> Server does not start when transaction subsystem configures journal object store
> --------------------------------------------------------------------------------
>
> Key: WFLY-5100
> URL: https://issues.jboss.org/browse/WFLY-5100
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 10.0.0.Beta1, 10.0.0.Beta2, 10.0.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Amos Feng
> Priority: Blocker
> Fix For: 10.0.0.Beta2
>
> Attachments: standalone.xml
>
>
> Currently when object store is configured to use journal to save the txn log the server won't start.
> For WFLY 10.Beta1 there is trouble of attributes naming - see WFLY-5078. But either when used old naming [1] (hornetq instead of activemq) the server fails to start [2].
> For WFLY 10.CR1 the naming works fine and {{use-journal-store}} works when used via jboss-cli.sh but the server starts still with the errors.
> [1]
> {code}
> /subsystem=transactions:write-attribute(name=use-journal-store, value=true)
> {code}
> [2]
> {code}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.arjuna.ats.arjuna.exceptions.FatalError: ARJUNA012135: Could not create Store type: com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqObjectStoreAdaptor
> at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:155)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:110)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:67)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<init>(CommitMarkableResourceRecordRecoveryModule.java:156)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at java.lang.Class.newInstance(Class.java:442)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192)
> at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:444)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:865)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121)
> at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112)
> at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54)
> at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:119)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> Caused by: java.lang.NoClassDefFoundError: org/apache/activemq/artemis/core/journal/SequentialFileFactory
> at com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqObjectStoreAdaptor.<init>(HornetqObjectStoreAdaptor.java:78)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at java.lang.Class.newInstance(Class.java:442)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:151)
> ... 24 more
> Caused by: java.lang.ClassNotFoundException: org.apache.activemq.artemis.core.journal.SequentialFileFactory from [Module "org.jboss.jts:main" from local module loader @707f7052 (finder: local module finder @11028347 (roots: /home/ochaloup/jboss/jboss-eap-7.0.0.DR8/modules,/home/ochaloup/jboss/jboss-eap-7.0.0.DR8/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> ... 32 more
> ...
> ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaRecoveryManager" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: Failed to start service
> Caused by: com.arjuna.ats.arjuna.exceptions.FatalError: ARJUNA012135: Could not create Store type: com.arjuna.ats.internal.arjuna.objectstore.hornetq.HornetqObjectStoreAdaptor
> Caused by: java.lang.NoClassDefFoundError: org/apache/activemq/artemis/core/journal/SequentialFileFactory
> Caused by: java.lang.ClassNotFoundException: org.apache.activemq.artemis.core.journal.SequentialFileFactory from [Module \"org.jboss.jts:main\" from local module loader @707f7052 (finder: local module finder @11028347 (roots: /home/ochaloup/jboss/jboss-eap-7.0.0.DR8/modules,/home/ochaloup/jboss/jboss-eap-7.0.0.DR8/modules/system/layers/base))]"}}
> INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.txn.ArjunaRecoveryManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: Failed to start service
> {code}
> The reason is explained in comment
> https://issues.jboss.org/browse/WFLY-5078?focusedCommentId=13098047#comme...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month