Early Access builds for JDK 9 b45, JDK 8u40 b21 & JDK 7u80 b04 are available on java.net
by Rory O'Donnell
Hi Galder,
Now that JDK 9 Early Access build images are modular [1], there is a fresh
Early Access build for JDK 9 b45 <https://jdk9.java.net/download/>
available on java.net.
The summary of changes are listed here
<http://www.java.net/download/jdk9/changes/jdk9-b45.html>
In addition, there are new Early Access builds for the ongoing update
releases.
The Early Access build for JDK 8u40 b21
<http://jdk8.java.net/download.html> is available on java.net, with the
summary of changes listed here.
<http://www.java.net/download/jdk8u40/changes/jdk8u40-b21.html>
Finally, the Early Access build for JDK 7u80 b04
<https://jdk7.java.net/download.html>is available on java.net,
with the summary of changes listed here.
<http://download.java.net/jdk7u80/changes/jdk7u80-b04.html>
As we enter the later phases of development for JDK 7u80 & JDK 8u40,
please log any show stoppers as soon as possible.
Rgds,Rory
[1] http://mreinhold.org/blog/jigsaw-modular-images
--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland
10 years, 8 months
Indexing deadlock (solution suggestion)
by Radim Vansa
Hi,
what I was suggesting in the call in order to get rid of the indexing:
Currently we're doing this:
1. thread on primary owner executes the write and sends indexing request
(synchronous RPC) to index master, waits for the response
2. remote/OOB thread on indexing master enqueues the indexing request
and waits
3. indexing thread (on indexing master) retrieves the request, processes
it and wakes up the waiting remote/OOB thread
4. remote/OOB thread sends RPC response
5. primary owner receives the RPC response (in OOB thread, inside
JGroups) and wakes up the thread sending the RPC
What I suggest is that:
1. thread on primary owner executes the write and sends indexing request
as asynchronous RPC (single message) to index master, and waits on a
custom synchronization primitive
2. remote/OOB thread on indexing master enqueues the indexing request
and returns back to the threadpool
3. indexing thread (on indexing master) retrieves the request, processes
it and sends asynchronouse RPC (again single message) to the primary owner
4. primary owner (in OOB thread) receives the message and wakes up
thread waiting on the custom synchronization primitive (in Infinispan)
My 2c
Radim
--
Radim Vansa <rvansa(a)redhat.com>
JBoss DataGrid QA
10 years, 8 months
Failed Hot Rod tests.. since several weeks
by Sanne Grinovero
Hi all,
these tests are failing me regularly since at least November, is
someone looking at them?
As usual, you might have noticed I stopped sending pull requests since
the build fails here.
thanks,
Sanne
Results :
Failed tests:
MultiHotRodServerIspnDirReplQueryTest>MultiHotRodServerQueryTest.testAttributeQuery:124
expected:<1> but was:<0>
MultiHotRodServerIspnDirReplQueryTest>MultiHotRodServerQueryTest.testEmbeddedAttributeQuery:137
expected:<1> but was:<0>
MultiHotRodServerIspnDirReplQueryTest>MultiHotRodServerQueryTest.testProjections:167
expected:<1> but was:<0>
Tests run: 865, Failures: 3, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Infinispan BOM ..................................... SUCCESS [ 0.091 s]
[INFO] Infinispan Common Parent ........................... SUCCESS [ 1.019 s]
[INFO] Infinispan Checkstyle Rules ........................ SUCCESS [ 2.012 s]
[INFO] Infinispan Commons ................................. SUCCESS [ 5.641 s]
[INFO] Infinispan Core .................................... SUCCESS [06:59 min]
[INFO] Infinispan Extended Statistics ..................... SUCCESS [ 34.332 s]
[INFO] Parent pom for server modules ...................... SUCCESS [ 0.075 s]
[INFO] Infinispan Server - Core Components ................ SUCCESS [ 12.236 s]
[INFO] Infinispan Query DSL API ........................... SUCCESS [ 0.735 s]
[INFO] Infinispan Object Filtering API .................... SUCCESS [ 1.610 s]
[INFO] Parent pom for cachestore modules .................. SUCCESS [ 0.123 s]
[INFO] Infinispan JDBC CacheStore ......................... SUCCESS [ 19.649 s]
[INFO] Parent pom for the Lucene integration modules ...... SUCCESS [ 0.068 s]
[INFO] Infinispan Lucene Directory Implementation ......... SUCCESS [ 9.066 s]
[INFO] Infinispan Query API ............................... SUCCESS [ 45.772 s]
[INFO] Infinispan Tools ................................... SUCCESS [ 1.343 s]
[INFO] Infinispan Remote Query Client ..................... SUCCESS [ 0.457 s]
[INFO] Infinispan Remote Query Server ..................... SUCCESS [ 7.949 s]
[INFO] Infinispan Tree API ................................ SUCCESS [ 7.558 s]
[INFO] Infinispan JPA CacheStore .......................... SUCCESS [ 16.348 s]
[INFO] Infinispan Hot Rod Server .......................... SUCCESS [01:14 min]
[INFO] Infinispan Hot Rod Client .......................... FAILURE [ 58.719 s]
10 years, 9 months
Infinispan Management Console project - JIRA/gh issues?
by Tomas Sykora
Greetings all!
I know that the team puts hands on more important stuff recently but I want to find out (decide) what tool do we want to use for driving issues for Infinispan Management Console sub-project.
Currently, I am struggling with the fact that I have some ideas in my mind and I don't have a good place for raising an issue and further discussion. Also I am not aware of other contributors' intentions and I am not sure whether my effort is duplication of someone's work.
Can we please decide what tracking tool do we use for Infinispan Management Console so we can start raising feature requests, discussions, issues, etc.?
I personally vote for GitHub issues.
Thank you very much for any input :)
Tomas
10 years, 9 months
Infinispan tutorial
by Tristan Tarrant
Hi guys,
I've been working on how to spruce up our website, docs and code samples.
While quickstarts are ok, they come as monolithic blobs which tell you
nothing about how you got there. For this reason I believe a
step-by-step tutorial approach is better and I've been looking at the
AngularJS tutorials [0] as good examples on how to achieve this.
I have created a repo [1] on my GitHub user where each commit is a step
in the tutorial. I have tagged the commits using 'step-n' so that you
can checkout any of the steps and run them:
git checkout step-1
mvn clean package exec:java
The GitHub web interface can be used to show the diff between steps, so
that it can be linked from the docs [2].
Currently I'm not aiming to build a real application (although
suggestions are welcome in this sense), but just going through the
basics, adding features one by one, etc.
Comments are welcome.
Tristan
---
[0] https://docs.angularjs.org/tutorial/step_00
[1] https://github.com/tristantarrant/infinispan-embedded-tutorial
[2]
https://github.com/tristantarrant/infinispan-embedded-tutorial/compare/st...
10 years, 9 months
