July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6242) Upgrade to CDI 1.2 and use only Annotated Beans Discovery

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6242?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6242: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha4 9.0.0.Final Resolution: Done > Upgrade to CDI 1.2 and use only Annotated Beans Discovery > --------------------------------------------------------- > > Key: ISPN-6242 > URL: https://issues.jboss.org/browse/ISPN-6242 > Project: Infinispan > Issue Type: Task > Components: CDI Integration > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6868) Expose extra configuration for the SSLContext protocol in the Hot Rod client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6868?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6868: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha4 9.0.0.Final Resolution: Done > Expose extra configuration for the SSLContext protocol in the Hot Rod client > ---------------------------------------------------------------------------- > > Key: ISPN-6868 > URL: https://issues.jboss.org/browse/ISPN-6868 > Project: Infinispan > Issue Type: Bug > Components: Security > Affects Versions: 9.0.0.Alpha3 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > > Currently in the HotRod client the {{SSLContext}} is created with the hardcoded "TLS" protocol, and this can only be overriden by providing a whole custom instance of {{SSLContext}} programmatically. We should provide an extra property to change the protocol for the default SSLContext case, allowing it to be supported via properties files -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6858) Prepare a plan for refactoring server parser and writer part

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6858?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6858: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Prepare a plan for refactoring server parser and writer part > ------------------------------------------------------------ > > Key: ISPN-6858 > URL: https://issues.jboss.org/browse/ISPN-6858 > Project: Infinispan > Issue Type: Task > Reporter: Sebastian Łaskawiec > Assignee: Tristan Tarrant > Priority: Optional > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > > Our Server Parser/Writer code doesn't look nice and has lots and lots of duplication. We should prepare a plan how to refactor it (and possibly distribute tasks all over the team). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6886) Continous query user guide

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6886?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6886: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Continous query user guide > -------------------------- > > Key: ISPN-6886 > URL: https://issues.jboss.org/browse/ISPN-6886 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6887) Named query parameters user guide

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6887?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6887: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > Named query parameters user guide > --------------------------------- > > Key: ISPN-6887 > URL: https://issues.jboss.org/browse/ISPN-6887 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-201) make JDBC cache store use DB transactions for commit/rollback

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-201?page=com.atlassian.jira.plugin.s... ] Sebastian Łaskawiec updated ISPN-201: ------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > make JDBC cache store use DB transactions for commit/rollback > ------------------------------------------------------------- > > Key: ISPN-201 > URL: https://issues.jboss.org/browse/ISPN-201 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Ryan Emerson > Labels: modshape > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > > current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-201) make JDBC cache store use DB transactions for commit/rollback

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-201?page=com.atlassian.jira.plugin.s... ] Sebastian Łaskawiec updated ISPN-201: ------------------------------------- Fix Version/s: 9.0.0.Alpha4 > make JDBC cache store use DB transactions for commit/rollback > ------------------------------------------------------------- > > Key: ISPN-201 > URL: https://issues.jboss.org/browse/ISPN-201 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Mircea Markus > Assignee: Ryan Emerson > Labels: modshape > Fix For: 9.0.0.Alpha4, 9.0.0.Final > > > current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 commented on ISPN-6679: ------------------------------------------- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6673) Implement Rolling Upgrades with Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6673?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6673: ------------------------------------------- A full Rolling Upgrade procedure requires an efficient way of changing configuration in runtime. This might be answered by Kubernetes Rolling Updates which require proper Health check API (see https://issues.jboss.org/browse/ISPN-6679) > Implement Rolling Upgrades with Kubernetes > ------------------------------------------ > > Key: ISPN-6673 > URL: https://issues.jboss.org/browse/ISPN-6673 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > There are 2 mechanisms which seems to do the same but are totally different: > * [Kubernetes Rolling Update|http://kubernetes.io/docs/user-guide/rolling-updates/] - replaces Pods in controllable fashon > * [Infinispan Rolling Updgrate|http://infinispan.org/docs/stable/user_guide/user_guide.html#_Ro...] - a procedure for upgrading Infinispan or changing the configuration > Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6890) Infinispan server can not start with Kubernetes

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6890?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-6890: --------------------------------------- Assignee: Gustavo Fernandes (was: Sebastian Łaskawiec) > Infinispan server can not start with Kubernetes > ----------------------------------------------- > > Key: ISPN-6890 > URL: https://issues.jboss.org/browse/ISPN-6890 > Project: Infinispan > Issue Type: Bug > Components: Cloud Integrations > Affects Versions: 9.0.0.Alpha3, 8.2.3.Final > Reporter: Sebastian Łaskawiec > Assignee: Gustavo Fernandes > > Infinispan server can not start when deploying on Kubernetes. > Error message: > {code} > $ oc logs pod/infinispan-server-1-t53ad > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /opt/jboss/infinispan-server > JAVA: /usr/lib/jvm/java/bin/java > JAVA_OPTS: -server -server -Xms64m -Xmx512m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > java.lang.IllegalArgumentException: Failed to instantiate class "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler" for handler "FILE" > at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:116) > at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:335) > at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:288) > at org.jboss.logmanager.config.LogContextConfigurationImpl.commit(LogContextConfigurationImpl.java:297) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:546) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:514) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:476) > at java.util.logging.LogManager$3.run(LogManager.java:399) > at java.util.logging.LogManager$3.run(LogManager.java:396) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396) > at java.util.logging.LogManager.access$800(LogManager.java:145) > at java.util.logging.LogManager$2.run(LogManager.java:345) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338) > at java.util.logging.LogManager.getLogManager(LogManager.java:378) > at org.jboss.modules.Main.main(Main.java:482) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:114) > ... 17 more > Caused by: java.io.FileNotFoundException: /opt/jboss/infinispan-server/standalone/log/server.log (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:151) > at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.setFile(PeriodicRotatingFileHandler.java:102) > at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:189) > at org.jboss.logmanager.handlers.FileHandler.<init>(FileHandler.java:119) > at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.<init>(PeriodicRotatingFileHandler.java:70) > ... 22 more > java.lang.IllegalStateException: WFLYSRV0124: Could not create server data directory: /opt/jboss/infinispan-server/standalone/data > at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:473) > at org.jboss.as.server.Main.determineEnvironment(Main.java:297) > at org.jboss.as.server.Main.main(Main.java:94) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.modules.Module.run(Module.java:329) > at org.jboss.modules.Main.main(Main.java:507) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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