September 2014 - infinispan-dev - Jboss List Archives

Forum: Version, JGroups and Infinispan Config

by Radim Vansa

Hi, I have a feeling that most of the first replies on JBoss forum are asking users about their Infinispan version, configuration and JGroups configuration. Could we add few fields asking for those along with the question? Radim -- Radim Vansa <rvansa(a)redhat.com> JBoss DataGrid QA

11 years

1
0
0 / 0

Early Access builds for JDK 9 b28 and JDK 8u40 b04 are available on java.net

by Rory O'Donnell Oracle, Dublin Ireland

Hi Galder, Early Access build for JDK 9 b28 <https://jdk9.java.net/download/> is available on java.net, summary of changes are listed here <http://www.java.net/download/jdk9/changes/jdk9-b28.html> Early Access build for JDK 8u40 b04 <http://jdk8.java.net/download.html> is available on java.net, summary of changes are listed here. <http://www.java.net/download/jdk8u40/changes/jdk8u40-b04.html> Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland

11 years, 1 month

1
0
0 / 0

Infinispan within JBoss EAP 6.2

by Renato Resende Ribeiro de Oliveira

Hello there, I am not sure if this list is the right place to ask that, but i am getting out of options. I am trying to deploy an application in JBoss EAP 6.2 in cluster mode and i need the feature of shared user sessions across cluster nodes. If i deploy a test application in the EAP the Infinispan subsystem starts normally, printing the following messages on the logs: [Host Controller] 17:50:16,558 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Conteúdo adicionado na localização /home/renato/jbdevstudio/runtimes/jboss-eap/domain/data/content/10/880e56bde8806be9fc5736829dd5733d717974/content [Server:server-two] 17:50:16,790 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Iniciando a implantação do "cluster.war" (runtime-name: "cluster.war") [Server:server-one] 17:50:16,790 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Iniciando a implantação do "cluster.war" (runtime-name: "cluster.war") [Server:server-one] 17:50:18,481 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-one] 17:50:18,481 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 63) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-one] 17:50:18,490 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-one] 17:50:18,492 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 63) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-one] 17:50:18,494 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-one] 17:50:18,497 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-one] 17:50:18,558 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 50) ISPN000078: Starting JGroups Channel [Server:server-one] 17:50:18,571 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the send buffer of socket DatagramSocket was set to 640KB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux) [Server:server-one] 17:50:18,572 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the receive buffer of socket DatagramSocket was set to 20MB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux) [Server:server-one] 17:50:18,572 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the send buffer of socket MulticastSocket was set to 640KB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux) [Server:server-one] 17:50:18,573 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux) [Server:server-one] 17:50:18,576 INFO [stdout] (ServerService Thread Pool -- 50) [Server:server-one] 17:50:18,576 INFO [stdout] (ServerService Thread Pool -- 50) ------------------------------------------------------------------- [Server:server-one] 17:50:18,576 INFO [stdout] (ServerService Thread Pool -- 50) GMS: address=master:server-one/web, cluster=web, physical address= 127.0.0.1:55200 [Server:server-one] 17:50:18,577 INFO [stdout] (ServerService Thread Pool -- 50) ------------------------------------------------------------------- [Server:server-two] 17:50:18,654 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 51) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-two] 17:50:18,655 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 53) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-two] 17:50:18,658 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 51) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-two] 17:50:18,660 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 53) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-two] 17:50:18,660 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-two] 17:50:18,661 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-6) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. [Server:server-two] 17:50:18,715 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 50) ISPN000078: Starting JGroups Channel [Server:server-two] 17:50:18,728 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the send buffer of socket DatagramSocket was set to 640KB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux) [Server:server-two] 17:50:18,729 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the receive buffer of socket DatagramSocket was set to 20MB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux) [Server:server-two] 17:50:18,729 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the send buffer of socket MulticastSocket was set to 640KB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux) [Server:server-two] 17:50:18,729 WARN [org.jgroups.protocols.UDP] (ServerService Thread Pool -- 50) JGRP000014: the receive buffer of socket MulticastSocket was set to 25MB, but the OS only allocated 212,99KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux) [Server:server-two] 17:50:18,731 INFO [stdout] (ServerService Thread Pool -- 50) [Server:server-two] 17:50:18,731 INFO [stdout] (ServerService Thread Pool -- 50) ------------------------------------------------------------------- [Server:server-two] 17:50:18,731 INFO [stdout] (ServerService Thread Pool -- 50) GMS: address=master:server-two/web, cluster=web, physical address= 127.0.0.1:55350 [Server:server-two] 17:50:18,732 INFO [stdout] (ServerService Thread Pool -- 50) ------------------------------------------------------------------- [Server:server-two] 17:50:20,747 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 50) ISPN000094: Received new cluster view: [master:server-two/web|0] [master:server-two/web] [Server:server-two] 17:50:20,797 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 50) ISPN000079: Cache local address is master:server-two/web, physical addresses are [127.0.0.1:55350] [Server:server-two] 17:50:20,802 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 50) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.7.Final [Server:server-two] 17:50:20,812 INFO [org.jboss.as.clustering] (MSC service thread 1-7) JBAS010238: O número de membroos do clusyer: 1 [Server:server-two] 17:50:20,856 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 53) ISPN000161: Using a batchMode transaction manager [Server:server-two] 17:50:20,856 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 50) ISPN000161: Using a batchMode transaction manager [Server:server-two] 17:50:20,990 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 53) ISPN000031: MBeans were successfully registered to the platform MBean server. [Server:server-two] 17:50:20,990 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 50) ISPN000031: MBeans were successfully registered to the platform MBean server. [Server:server-two] 17:50:20,998 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53) JBAS010281: Cache default-host/cluster inicializado a partir do recipiente web [Server:server-two] 17:50:20,998 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 50) JBAS010281: Cache repl inicializado a partir do recipiente web [Server:server-two] 17:50:21,038 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Registra o contexto da web: /cluster [Server:server-two] 17:50:21,166 INFO [org.jboss.as.clustering] (Incoming-1,shared=udp) JBAS010225: Nova visualização do cluster para a partição web (id: 1, delta: 1, merge: false) : [master:server-two/web, master:server-one/web] [Server:server-two] 17:50:21,167 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-1,shared=udp) ISPN000094: Received new cluster view: [master:server-two/web|1] [master:server-two/web, master:server-one/web] [Server:server-one] 17:50:21,188 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 50) ISPN000094: Received new cluster view: [master:server-two/web|1] [master:server-two/web, master:server-one/web] [Server:server-one] 17:50:21,253 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 50) ISPN000079: Cache local address is master:server-one/web, physical addresses are [127.0.0.1:55200] [Server:server-one] 17:50:21,259 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 50) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.7.Final [Server:server-one] 17:50:21,272 INFO [org.jboss.as.clustering] (MSC service thread 1-4) JBAS010238: O número de membroos do clusyer: 2 [Server:server-one] 17:50:21,307 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 59) ISPN000161: Using a batchMode transaction manager [Server:server-one] 17:50:21,308 INFO [org.infinispan.factories.TransactionManagerFactory] (ServerService Thread Pool -- 63) ISPN000161: Using a batchMode transaction manager [Server:server-one] 17:50:21,446 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 63) ISPN000031: MBeans were successfully registered to the platform MBean server. [Server:server-one] 17:50:21,446 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 59) ISPN000031: MBeans were successfully registered to the platform MBean server. [Server:server-one] 17:50:21,517 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 63) JBAS010281: Cache default-host/cluster inicializado a partir do recipiente web [Server:server-one] 17:50:21,527 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 59) JBAS010281: Cache repl inicializado a partir do recipiente web [Server:server-one] 17:50:21,540 INFO [org.jboss.web] (ServerService Thread Pool -- 59) JBAS018210: Registra o contexto da web: /cluster [Server:server-two] 17:50:21,762 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Implantado "cluster.war" (runtime-name: "cluster.war") [Server:server-one] 17:50:21,762 INFO [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Implantado "cluster.war" (runtime-name: "cluster.war") So, for cluster.war everything works perfect. This WAR has no libs and just a web.xml with the <distributable /> tag. So i created another WAR just inserting a lib dependency for my web framework VRaptor. When i try to deploy it without any further modifications, the Infinispan simply doesn't start. The log of this deploy follows: [Host Controller] 17:56:30,287 INFO [org.jboss.as.repository] (management-handler-thread - 6) JBAS014900: Conteúdo adicionado na localização /home/renato/jbdevstudio/runtimes/jboss-eap/domain/data/content/68/3e481ea59173e8225b374da58aada4e7ba7924/content [Server:server-two] 17:56:30,646 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Iniciando a implantação do "cluster-vraptor.war" (runtime-name: "cluster-vraptor.war") [Server:server-one] 17:56:30,659 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Iniciando a implantação do "cluster-vraptor.war" (runtime-name: "cluster-vraptor.war") [Server:server-one] 17:56:31,693 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015893: Foi encontrado o nome de classe inválido 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' para o tipo de serviço 'org.xmlpull.v1.XmlPullParserFactory' [Server:server-two] 17:56:31,699 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015893: Foi encontrado o nome de classe inválido 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' para o tipo de serviço 'org.xmlpull.v1.XmlPullParserFactory' [Server:server-two] 17:56:32,130 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016012: A implantação deployment "cluster-vraptor.war" contém anotaçõs CDI mas o beans.xml não foi encontrado. [Server:server-one] 17:56:32,261 WARN [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016012: A implantação deployment "cluster-vraptor.war" contém anotaçõs CDI mas o beans.xml não foi encontrado. [Server:server-two] 17:56:32,297 INFO [org.jboss.web] (ServerService Thread Pool -- 63) JBAS018210: Registra o contexto da web: /cluster-vraptor [Server:server-one] 17:56:32,397 INFO [org.jboss.web] (ServerService Thread Pool -- 81) JBAS018210: Registra o contexto da web: /cluster-vraptor [Server:server-one] 17:56:33,504 INFO [org.jboss.as.server] (host-controller-connection-threads - 2) JBAS018559: Implantado "cluster-vraptor.war" (runtime-name: "cluster-vraptor.war") [Server:server-two] 17:56:33,503 INFO [org.jboss.as.server] (host-controller-connection-threads - 2) JBAS018559: Implantado "cluster-vraptor.war" (runtime-name: "cluster-vraptor.war") Nothing of the clustering Infinispan module starts. This framework adds some dependecies to the libs, all extra jars included in the second deployment: aopalliance-1.0.jar gson-2.2.4.jar guava-11.0.2.jar guice-3.0.jar guice-multibindings-3.0.jar iogi-1.0.0.jar javassist-3.12.1.GA.jar javax.inject-1.jar jsr305-1.3.9.jar log4j-1.2.16.jar mirror-1.6.1.jar objenesis-1.3.jar paranamer-2.5.2.jar scannotation-1.0.2.jar slf4j-api-1.6.1.jar slf4j-log4j12-1.6.1.jar vraptor-3.5.4.jar xmlpull-1.1.3.1.jar xpp3_min-1.1.4c.jar xstream-1.4.7.jar The VRaptor framework declares a Servlet Filter that is initialized statically, i don't know if this is a relevant information. What i want to know is why this happen and what can i do to fix this issue. There is any further configuration that i can do to make this work? There is any known issue regarding the co-existence of Infinispan 5.2.7 and any of these libs? I completely out of ideas and clues. Thanks for the help. Regards. -- *Renato Resende Ribeiro de Oliveira* DIretor de Produção e Tecnologia - ProGolden Soluções Tecnológicas MSc - Computer Science - Universidade Federal de Lavras Skype: renatorro.comp.ufla.br ICQ: 669012672 Phone: +55 (31) 9823-9631 Conheça o PrêmioIdeia - Inovação Colaborativa na sua empresa! http://www.premioideia.com/

11 years, 1 month

1
1
0 / 0

Ant based kill not fully working? Re: ISPN-4567

by Galder Zamarreño

Hi, Dan has reported [1]. It appears as if the last server started in infinispan-as-module-client-integrationtests did not really get killed. From what I see, this kill was done via the specific Ant target present in that Maven module. I also remembered recently [2] was added. Maybe we need to get as-modules/client to be configured with it so that it properly kills servers? What I’m not sure is where we’d put it so that it can be consumed both by server/integration/testsuite and as-modules/client? The problem is that the class, as is, brings in arquillian dependency. If we can separate the arquillian stuff from the actual code, the class itself could maybe go in commons test source directory? @Tristan, thoughts? @Jakub, can I assign this to you? [1] https://issues.jboss.org/browse/ISPN-4567 [2] https://github.com/infinispan/infinispan/blob/master/server/integration/t... -- Galder Zamarreño galder(a)redhat.com twitter.com/galderz

11 years, 1 month

5
6
0 / 0

Weekly Infinispan IRC meeting 2014-09-01

by Tristan Tarrant

Get the minutes from here: http://transcripts.jboss.org/meeting/irc.freenode.org/infinispan/2014/inf...

11 years, 1 month

1
0
0 / 0

Test groups

by Sebastian Łaskawiec

Hi! Recently I've been working with some tests and I noticed that we have pretty large number of Maven profiles responsible for selecting which test suites should be executed: * test-CI * test-functional * test-jgroups * test-transaction * test-unit * test-unstable * test-xsite Perhaps some of them might be removed and we could create some more useful hierarchy. Here is my proposition: * test-smoke - all unit test with some basic functional tests based on Arquillian. This profile would be invoked by default and with our CI server. There is already a ticket to implement such profile in Jira [1]. I think it would be a good practice to reject all Pull Requests which fail against this profile. * test-acceptance - Full test suite without performance test. This should be executed once a day (nightly profile?) * test-performance - Reserved for performance/stress tests. * test-code-quality - test-acceptance with Sonar, Firebug, Jacoco or any other tool for measuring code quality. Executed once a day. In my opinion above hierarchy will help to identify serious problems faster and will help us in productisation stream. What do you think? [1] https://issues.jboss.org/browse/ISPN-4665 Best regards Sebastian

11 years, 1 month

1
0
0 / 0

Infinispan Jira workflow

by Tristan Tarrant

I was just looking at the Jira workflow for Infinispan and noticed that all issues start off in the "Open" state and assigned to the default owner for the component. Unfortunately this does not mean that the actual "assignee" has taken ownership, or that he intends to work on it in the near future, or that he has even looked at it. I would therefore like to introduce a state for fresh issues which is just before "Open". This can be "New" or "Unverified/Untriaged" and will make it easier to find all those "lurker" issues which are lost in the noise. What do you think ? Tristan

11 years, 1 month

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-dev September 2014