New Ansible-based CI slaves
by Sebastian Laskawiec
Hey!
I'm not sure if you have noticed but we have 3 Ansible slaves now [1].
However there are also bad news :) We use some time thresholds in our CI
builds and it will take some time to fill all caches in CI slaves
(.m2/repository for example). Please be patient and rerun your jobs if
needed.
Please let me or Dan know in case of any problems.
Thanks
Sebastian
[1] http://ci.infinispan.org/agents.html?tab=registeredAgents
9 years, 7 months
Getting ready for 8.2.0.Beta2
by Tristan Tarrant
Hi all,
we will be releasing Beta2 on tuesday, so please please help us shorten
the PR queue as soon as possible.
Tristan
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat
9 years, 7 months
Got a local cache despite it is configured as distributed
by Pierrick HYMBERT
Hi all,
I am blocked to deploy a test app that use a distributed infinispan (8.0.1)
cache within 2 wildfly (10.0.0) domain nodes and a cache entry producer
deployed as clustered singleton service.
Your feedback/advise are really appreciated!
Cache definition:
<cache-container name="my-cache-container">
<transport lock-timeout="60000"/>
<distributed-cache name="myAppCache" mode="SYNC">
<transaction mode="NONE"/>
<eviction strategy="NONE"/>
</distributed-cache>
</cache-container>
Sample code:
@Resource(lookup = "java:jboss/infinispan/container/my-cache-container")
private EmbeddedCacheManager cacheContainer;
private Cache<Long, Long> myAppCache;
@PostConstruct
public void startNotClustered() throws NamingException {
this.myAppCache = this.cacheContainer.getCache("myAppCache");
...
}
...
@Schedule(hour = "*", minute = "*", second = "*")
public void consume() {
logger.info("Cache size on node {} = {}",
System.getProperty("jboss.node.name"), myAppCache.size());
}
Server one sample logs:
2016-01-31 14:52:03,789 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 1) Produce
new cache entry 1454241123789 on node master:server-one
2016-01-31 14:52:04,005 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 2) Cache
size on node master:server-one = 35
2016-01-31 14:52:04,796 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 3) Produce
new cache entry 1454241124796 on node master:server-one
2016-01-31 14:52:05,006 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 4) Cache
size on node master:server-one = 36
2016-01-31 14:52:05,801 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 5) Produce
new cache entry 1454241125801 on node master:server-one
2016-01-31 14:52:06,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 6) Cache
size on node master:server-one = 37
2016-01-31 14:52:06,807 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 7) Produce
new cache entry 1454241126807 on node master:server-one
2016-01-31 14:52:07,005 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 8) Cache
size on node master:server-one = 38
2016-01-31 14:52:07,813 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 9) Produce
new cache entry 1454241127813 on node master:server-one
2016-01-31 14:52:08,006 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 10) Cache
size on node master:server-one = 39
2016-01-31 14:52:08,817 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 1) Produce
new cache entry 1454241128817 on node master:server-one
2016-01-31 14:52:09,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 2) *Cache
size on node master:server-one = 40*
Server two logs:
2016-01-31 14:51:56,006 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 4) Cache
size on node master:server-two = 0
2016-01-31 14:51:57,008 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 5) Cache
size on node master:server-two = 0
2016-01-31 14:51:58,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 6) Cache
size on node master:server-two = 0
2016-01-31 14:51:59,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 7) Cache
size on node master:server-two = 0
2016-01-31 14:52:00,006 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 8) Cache
size on node master:server-two = 0
2016-01-31 14:52:01,008 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 9) Cache
size on node master:server-two = 0
2016-01-31 14:52:02,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 10) Cache
size on node master:server-two = 0
2016-01-31 14:52:03,006 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 1) Cache
size on node master:server-two = 0
2016-01-31 14:52:04,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 2) Cache
size on node master:server-two = 0
2016-01-31 14:52:05,008 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 3) Cache
size on node master:server-two = 0
2016-01-31 14:52:06,006 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 4) Cache
size on node master:server-two = 0
2016-01-31 14:52:07,006 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 5) Cache
size on node master:server-two = 0
2016-01-31 14:52:08,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 6) Cache
size on node master:server-two = 0
2016-01-31 14:52:09,007 INFO
[org.hypik.test.jboss.eap7.server.TestService] (EJB default - 7) *Cache
size on node master:server-two = 0*
I have attached all necessary info to investigate, but I am not sure
attachement is allowed, so you can see source and logs here:
https://www.dropbox.com/s/l1uhmfg5tkjkikw/infinispan-issue-wildfly-10.0.0...
С уважением / Cordialement / Best regards,
*Pierrick **HYMBERT*
9 years, 8 months
Progress with Java9 testing
by Sanne Grinovero
Hi all,
some roadblocks have been solved. Most notably:
- ISPN-6090: The Meta-Inf annotation processor which we use was fixed.
- WildFly 10 had a problem which would prevent it from booting,
version 10.0.0.Final is out now and works fine so integration tests
should work fine now (when you upgrade).
- ISPN-6085: Avoid using sun.misc.VM
The next blocker is:
[ERROR] Failed to execute goal
org.scala-tools:maven-scala-plugin:2.15.2:script (generate-blueprint)
on project infinispan-core: wrap:
org.apache.commons.exec.ExecuteException: Process exited with an
error: 1(Exit value: 1) -> [Help 1]
Could someone of our Scala experts volunteer please?
https://jdk9.java.net/download/
Critical dependencies such as JBoss Logger, Hibernate Search, Lucene,
already are fully compatible so what are you all waiting for :)
I met the OpenJDK team over the weekend at FOSDEM and they reminded
once more that they are ready to help and eager to address feedback;
but if you all wait for the Final to be shipped to test it that's
going to be too late to address some of the changes which are
happening.
Thanks,
Sanne
9 years, 8 months
Tweaking Infinispan Server JGroups stack values
by Galder Zamarreño
Hey Paul/Tristan,
Say you have Infinispan Server installed locally, and you want to quickly start an instance with a lower FD_ALL.timeout, GMS.join_timeout, MERGE3.min_interval adn MERGE3.max_interval without touching the XML configuration.
Is it possible to do that? Can you pass modified parameters for these options via system properties?
I'm not looking to modify them in a particular stack but modifying them all stacks would be fine for me.
The context for this is testing topology changes for JS client. Having a cluster started and running tests continously is very convenient for me. With that in mind, a very easy way to test topology changes that does not involve restarting a process is to suspend/resume a process (Node's child processes make this pretty easy to do). My intention is try to tweak the parameters above so that timeouts are lower and hence I can quickly force a topology change.
Cheers,
--
Galder Zamarreño
Infinispan, Red Hat
9 years, 8 months
