jdk8backported package
by Radim Vansa
Hi,
although we're on Java 8, there's still the package
org.infinispan.*.jdk8backported in our codebase. Is there any plan (and
possibility) to remove these and use implementation provided by runtime?
Or have we tweaked them too much, so shall we rather rename them?
Radim
--
Radim Vansa <rvansa(a)redhat.com>
JBoss Performance Team
8 years, 4 months
Status 2015-08-05
by Sebastian Laskawiec
Hey!
Unfortunately I won't be able to join you during the status meeting on
Monday, so here's what managed to do last week:
- I mainly worked on HelthChack API:
- https://issues.jboss.org/browse/ISPN-6679
-
https://github.com/slaskawi/infinispan/tree/ISPN-6679/Healthcheck_api
- Interfaces and JMX are done, the only missing bit is the Wildfly
integrations (currently implemented as metrics)
- Tomaz Cerar mentioned there is no way to use Custom Handlers for
Management API (we can not implement gathering statistics with a
custom URL
like http://localhost:9990/health). We can use HTTP GET for obtaining
resources or POST for operations and runtime resources.
- I need to think it over and choose one of the solutions (using
metrics seem to be the worst approach)
- I talked with James about printing out last X lines of log - again
it's not an easy task and James suggested that it can be using
the logging
subsystem. I will look into that too.
- I fixed a couple of Windows errors for the product (they were ok in
the upstream).
- I started implementing a CI job for our Docker images and OpenShift
- I also prepared a blog post about Infinispan and OpenShift (it will be
released next week).
- There are also some good news from my home city - we're opening
Bydgoszcz JUG (I'd love to see you guys pronouncing "Bydgoszcz" :D) in
September/October and I reserved 2 talks about Open Source (maintaining,
contributing etc) and Infinispan+OpenShift/Kubernetes. Wish me luck!
Thanks
Sebastian
8 years, 5 months
Sequential interceptors API
by Radim Vansa
Hi,
I would like to encourage you to play with the (relatively) new API for
sequential interceptors, and voice your comments - especially you corish
devs, and Galder who has much experience with async invocations and that
kind of stuff from JS-world.
I am now trying to use the asynchronous methods only (the
forkInvocationSync() is only temporary helper!); Dan has made it this
way as he wanted to avoid unnecessary allocations, and I welcome this
GC-awareness, but regrettably I find it rather hard to use, due to its
handler-style nature. For the simplest style interceptors (do this,
invoke next interceptor, and process result) it's fine, but when you
want to do something like:
visitFoo(cmd) {
Object x = null;
if (/* ... */) {
x = invoke(new OtherCommand());
}
invoke(new DifferentCommand(x));
Object retval = invoke(cmd);
return wrap(retval);
}
I find myself passing handlers deep down. There is allocation cost for
closures, so API that does not allocate CompletableFutures does not pay off.
I don't say that I could improve it (I have directed my comments to Dan
on IRC when I had something in particular), I just say that this is very
important API for further Infinispan development and everyone should pay
attention before it gets final.
So please, play with it, and show your opinion.
Radim
--
Radim Vansa <rvansa(a)redhat.com>
JBoss Performance Team
8 years, 5 months