July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6893) Remove scala code

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6893?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-6893: --------------------------------------- [~ijuma] indeed, but we need something that works now. Reasons for dropping Scala (in no particular order of importance / impact): * no usable build for Java 9 available yet * getting rid of the horrible hybrid code we have * more predictable performance of the constructs we use * lower the barrier to contribution both by internal and external developers * reduce the distribution size by 7MB * speed-up the build > Remove scala code > ----------------- > > Key: ISPN-6893 > URL: https://issues.jboss.org/browse/ISPN-6893 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > > Scala doesn't support Java 9. We need to remove it to make sure we have compatibility. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6893) Remove scala code

by Ismael Juma (JIRA)

[ https://issues.jboss.org/browse/ISPN-6893?page=com.atlassian.jira.plugin.... ] Ismael Juma commented on ISPN-6893: ----------------------------------- Support for Java 9 is planned, see: https://github.com/scala/scala-dev/issues/139 > Remove scala code > ----------------- > > Key: ISPN-6893 > URL: https://issues.jboss.org/browse/ISPN-6893 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > > Scala doesn't support Java 9. We need to remove it to make sure we have compatibility. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6679) Implement REST readiness and healthcheck probe in Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6679?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-6679 at 7/27/16 5:43 AM: -------------------------------------------------------------------- As a work around we can use a simple, CLI command for checking if the cluster is ready: {code} /opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=$(hostname -i):9990 '/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=*:read-attribute(name=cache-rebalancing-status)' | awk '/result/{gsub("\"", "", $3); print $3}' | awk '{if(NR>1)print}' | grep -v 'PENDING\|IN_PROGRESS\|SUSPENDED' Returns non 0 if rebalaning is in progress {code} And there is also a work around for a liveness check: {code} /opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=$(hostname -i):9990 '/:read-attribute(name=server-state)' | awk '/result/{gsub("\"", "", $3); print $3}' | grep running returns non 0 if is *not* running {code} was (Author: sebastian.laskawiec): As a work around we can use a simple, CLI command for checking if the cluster is ready: {code} /opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=$(hostname -i):9990 '/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=*:read-attribute(name=cache-rebalancing-status)' | awk '/result/{gsub("\"", "", $3); print $3}' | awk '{if(NR>1)print}' | grep -v 'PENDING\|IN_PROGRESS\|SUSPENDED' Returns non 0 if rebalaning is in progress {code} And there is also a work around for a liveness check: {code} /opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=$(hostname -i):9990 '/:read-attribute(name=server-state)' | awk '/result/{gsub("\"", "", $3); print $3}' | grep running returns 0 if is *not* running! {code} > Implement REST readiness and healthcheck probe in Kubernetes > ------------------------------------------------------------ > > Key: ISPN-6679 > URL: https://issues.jboss.org/browse/ISPN-6679 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6679) Implement REST readiness and healthcheck probe in Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6679?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-6679 at 7/27/16 5:42 AM: -------------------------------------------------------------------- As a work around we can use a simple, CLI command for checking if the cluster is ready: {code} /opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=$(hostname -i):9990 '/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=*:read-attribute(name=cache-rebalancing-status)' | awk '/result/{gsub("\"", "", $3); print $3}' | awk '{if(NR>1)print}' | grep -v 'PENDING\|IN_PROGRESS\|SUSPENDED' Returns non 0 if rebalaning is in progress {code} And there is also a work around for a liveness check: {code} /opt/jboss/infinispan-server/bin/ispn-cli.sh -c --controller=$(hostname -i):9990 '/:read-attribute(name=server-state)' | awk '/result/{gsub("\"", "", $3); print $3}' | grep running returns 0 if is *not* running! {code} was (Author: sebastian.laskawiec): As a work around we can use a simple, CLI command for checking if the cluster is ready: {code} ./ispn-cli.sh -c '/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=*:read-attribute(name=cache-rebalancing-status)' | grep 'PENDING\|IN_PROGRESS\|SUSPENDED' returns 0 if is *not* ready! {code} And there is also a work around for a liveness check: {code} ./ispn-cli.sh -c '/:read-attribute(name=server-state)' | awk '/result/{gsub("\"", "", $3); print $3}' | grep -v running returns 0 if is *not* running! {code} > Implement REST readiness and healthcheck probe in Kubernetes > ------------------------------------------------------------ > > Key: ISPN-6679 > URL: https://issues.jboss.org/browse/ISPN-6679 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2034) Add backwards serialization compatibility tests

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2034?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-2034. ------------------------------------ Resolution: Won't Fix > Add backwards serialization compatibility tests > ----------------------------------------------- > > Key: ISPN-2034 > URL: https://issues.jboss.org/browse/ISPN-2034 > Project: Infinispan > Issue Type: Enhancement > Components: Marshalling > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: compatibility > > Take each existing minor branch, i.e. 4.1.x, 4.0.x,...etc and modify VersionAwareMarshallerTest so that payloads are stored in a data file. > Then, take data files for each branch and store in git (master and 5.1.x), and try reading them with the existing externalizer/marshalling set up. > It should work... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6899) Investigate ALPN support

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6899?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6899: ------------------------------------------- JEP 244 highlights: * Will be implemented in JDK9 * This is an implementation of ALPN (not NPN) * JEP 244 will be used for HTTP/2 client implementation (JEP 110) * The server application will be able to scan a plain Client Hello message and choose protocol based on other factors such as SNI, Cipher suites etc * The implementation will hook into {{SSLEngine}} and {{SSLSocket}} * The design will be similar to SNI (JEP 114) > Investigate ALPN support > ------------------------ > > Key: ISPN-6899 > URL: https://issues.jboss.org/browse/ISPN-6899 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Optional > > Application layer Protocol Negotiation might be used by the Hot Rod server and allow creating a unified client package. The client could use many different transport technologies (Hot Rod, REST) and negotiate with the server which one could be used. > ALPN RFC: https://tools.ietf.org/html/rfc7301 > ALPN JDK9 support: http://openjdk.java.net/jeps/244 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6899) Investigate ALPN support

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6899?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6899: ------------------------------------------- RFC Highlights: * Allows supporting multiple application on the same TCP/UDP port * During the handshake the client sends a list of supported protocols (in client TLS Hello) and the server chooses the protocol and sends it back (server Hello). {noformat} Client Server ClientHello --------> ServerHello (ALPN extension & (ALPN extension & list of protocols) selected protocol) Certificate* ServerKeyExchange* CertificateRequest* <-------- ServerHelloDone Certificate* ClientKeyExchange CertificateVerify* [ChangeCipherSpec] Finished --------> [ChangeCipherSpec] <-------- Finished Application Data <-------> Application Data {noformat} * The server should pick the most highly preferred protocol and shall not respond with different protocol than supplied by the client. * ALPN effectively deprecates NPN > Investigate ALPN support > ------------------------ > > Key: ISPN-6899 > URL: https://issues.jboss.org/browse/ISPN-6899 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Optional > > Application layer Protocol Negotiation might be used by the Hot Rod server and allow creating a unified client package. The client could use many different transport technologies (Hot Rod, REST) and negotiate with the server which one could be used. > ALPN RFC: https://tools.ietf.org/html/rfc7301 > ALPN JDK9 support: http://openjdk.java.net/jeps/244 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6899) Investigate ALPN support

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6899: ----------------------------------------- Summary: Investigate ALPN support Key: ISPN-6899 URL: https://issues.jboss.org/browse/ISPN-6899 Project: Infinispan Issue Type: Feature Request Components: Cloud Integrations Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Priority: Optional Application layer Protocol Negotiation might be used by the Hot Rod server and allow creating a unified client package. The client could use many different transport technologies (Hot Rod, REST) and negotiate with the server which one could be used. ALPN RFC: https://tools.ietf.org/html/rfc7301 ALPN JDK9 support: http://openjdk.java.net/jeps/244 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6898) Avoid collisions in JCache

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6898?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec closed ISPN-6898. ------------------------------------- Resolution: Won't Fix > Avoid collisions in JCache > -------------------------- > > Key: ISPN-6898 > URL: https://issues.jboss.org/browse/ISPN-6898 > Project: Infinispan > Issue Type: Bug > Components: JCache > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > > When using JCache-annotations the DefaultCacheKeyGenerator exclusively looks at parameter values to form the cache key. Therefore it will be very likely that collissions occur (resulting in difficult to find ClassCastExceptions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6898) Avoid collisions in JCache

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6898: ----------------------------------------- Summary: Avoid collisions in JCache Key: ISPN-6898 URL: https://issues.jboss.org/browse/ISPN-6898 Project: Infinispan Issue Type: Bug Components: JCache Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Priority: Minor When using JCache-annotations the DefaultCacheKeyGenerator exclusively looks at parameter values to form the cache key. Therefore it will be very likely that collissions occur (resulting in difficult to find ClassCastExceptions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2016