January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6714) Add JDBC support for MariaDB

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6714?page=com.atlassian.jira.plugin.... ] Ryan Emerson reopened ISPN-6714: -------------------------------- > Add JDBC support for MariaDB > ---------------------------- > > Key: ISPN-6714 > URL: https://issues.jboss.org/browse/ISPN-6714 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha2, 8.2.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Minor > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > This should be an easy addition, as Maria DB tries to remain compatible with MySQL where possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6714) Add JDBC support for MariaDB

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6714?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6714: ------------------------------- Affects Version/s: 8.2.6.Final > Add JDBC support for MariaDB > ---------------------------- > > Key: ISPN-6714 > URL: https://issues.jboss.org/browse/ISPN-6714 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha2, 8.2.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Minor > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > This should be an easy addition, as Maria DB tries to remain compatible with MySQL where possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7391) Provide simple username/password/realm configuration attributes for the Hot Rod client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7391?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7391: ---------------------------------- Status: Open (was: New) > Provide simple username/password/realm configuration attributes for the Hot Rod client > -------------------------------------------------------------------------------------- > > Key: ISPN-7391 > URL: https://issues.jboss.org/browse/ISPN-7391 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Fix For: 9.0.0.Final > > > Asking the user to specify a callback handler is overkill when most of the time he just needs username/password/realm. Allow these to be set easily by using an internal basic callbackhandler. This configuration would be mutually exclusive with an explicit callback handler -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7391) Provide simple username/password/realm configuration attributes for the Hot Rod client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7391?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7391: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4796 > Provide simple username/password/realm configuration attributes for the Hot Rod client > -------------------------------------------------------------------------------------- > > Key: ISPN-7391 > URL: https://issues.jboss.org/browse/ISPN-7391 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Asking the user to specify a callback handler is overkill when most of the time he just needs username/password/realm. Allow these to be set easily by using an internal basic callbackhandler. This configuration would be mutually exclusive with an explicit callback handler -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7391) Provide simple username/password/realm configuration attributes for the Hot Rod client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7391?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-7391: ------------------------------------- Assignee: Tristan Tarrant > Provide simple username/password/realm configuration attributes for the Hot Rod client > -------------------------------------------------------------------------------------- > > Key: ISPN-7391 > URL: https://issues.jboss.org/browse/ISPN-7391 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Asking the user to specify a callback handler is overkill when most of the time he just needs username/password/realm. Allow these to be set easily by using an internal basic callbackhandler. This configuration would be mutually exclusive with an explicit callback handler -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7392) The policy elements are ignored in the server sasl configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7392: ---------------------------------- Status: Open (was: New) > The policy elements are ignored in the server sasl configuration > ---------------------------------------------------------------- > > Key: ISPN-7392 > URL: https://issues.jboss.org/browse/ISPN-7392 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7392) The policy elements are ignored in the server sasl configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7392: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4796 > The policy elements are ignored in the server sasl configuration > ---------------------------------------------------------------- > > Key: ISPN-7392 > URL: https://issues.jboss.org/browse/ISPN-7392 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7130) Failed clearing MariaDB JDBC cache store

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7130?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned ISPN-7130: ---------------------------------- Assignee: Ryan Emerson > Failed clearing MariaDB JDBC cache store > ---------------------------------------- > > Key: ISPN-7130 > URL: https://issues.jboss.org/browse/ISPN-7130 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 8.2.4.Final > Reporter: Paul Ferraro > Assignee: Ryan Emerson > Priority: Minor > > During scenarion {code}eap-7x-failover-db-session-shutdown-repl-sync-mariadb-10{code} (failover test when session are stored in MariaDB database) we saw errors on server when the server was shutting down. According to stacktrace it could be related to Infinispan. > {code} > 10:25:43,315 INFO [org.jboss.test.clusterbench.common.session.CommonHttpSessionServlet] (default task-1) New session created: OcWgFKcNH9Qyn1lQO2wJBdIkrf3d-_wr2gVoUeBp > [JBossINF] 10:25:49,725 ERROR [org.infinispan.persistence.jdbc.binary.JdbcBinaryStore] (expiration-thread--p18-t1) ISPN008001: Failed clearing cache store: java.sql.SQLException: No Parameters set. The command addBatch() must have been set > [JBossINF] at org.mariadb.jdbc.internal.util.ExceptionMapper.getSqlException(ExceptionMapper.java:149) > [JBossINF] at org.mariadb.jdbc.MariaDbServerPreparedStatement.executeBatch(MariaDbServerPreparedStatement.java:211) > [JBossINF] at org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeBatch(CachedPreparedStatement.java:714) > [JBossINF] at org.jboss.jca.adapters.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:1190) > [JBossINF] at org.infinispan.persistence.jdbc.binary.JdbcBinaryStore.purge(JdbcBinaryStore.java:329) > [JBossINF] at org.infinispan.persistence.manager.PersistenceManagerImpl.purgeExpired(PersistenceManagerImpl.java:373) > [JBossINF] at org.infinispan.expiration.impl.ClusterExpirationManager.processExpiration(ClusterExpirationManager.java:90) > [JBossINF] at org.infinispan.expiration.impl.ExpirationManagerImpl$ScheduledTask.run(ExpirationManagerImpl.java:231) > [JBossINF] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > [JBossINF] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [JBossINF] at org.jboss.as.clustering.infinispan.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:48) > [JBossINF] at java.lang.Thread.run(Thread.java:745) > {code} > It was shortly after cluster-wide rebalance finished > {code} > 10:25:07,403 INFO [org.infinispan.CLUSTER] (remote-thread--p8-t1) ISPN000310: Starting cluster-wide rebalance for cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar, topology CacheTopology{id=6, rebalanceId=4, currentCH=DefaultConsistentHash{ns=256, owners = (3)[dev212: 90+92, dev215: 85+81, dev213: 81+83]}, pendingCH=DefaultConsistentHash{ns=256, owners = (4)[dev212: 67+72, dev215: 65+63, dev213: 59+55, dev214: 65+66]}, unionCH=null, actualMembers=[dev212, dev215, dev213, dev214]} > [JBossINF] 10:25:07,403 INFO [org.infinispan.CLUSTER] (remote-thread--p8-t1) [Context=clusterbench-ee7.ear/clusterbench-ee7-ejb.jar][Scope=dev212]ISPN100002: Started local rebalance > [JBossINF] 10:25:07,404 INFO [org.infinispan.CLUSTER] (transport-thread--p14-t21) [Context=clusterbench-ee7.ear/clusterbench-ee7-ejb.jar][Scope=dev212]ISPN100003: Finished local rebalance > [JBossINF] 10:25:07,408 INFO [org.infinispan.CLUSTER] (remote-thread--p8-t1) [Context=clusterbench-ee7.ear/clusterbench-ee7-ejb.jar][Scope=dev213]ISPN100003: Finished local rebalance > [JBossINF] 10:25:07,413 INFO [org.infinispan.CLUSTER] (remote-thread--p8-t1) [Context=clusterbench-ee7.ear/clusterbench-ee7-ejb.jar][Scope=dev215]ISPN100003: Finished local rebalance > [JBossINF] 10:25:07,436 INFO [org.infinispan.CLUSTER] (remote-thread--p8-t1) [Context=clusterbench-ee7.ear/clusterbench-ee7-ejb.jar][Scope=dev214]ISPN100003: Finished local rebalance > [JBossINF] 10:25:07,436 INFO [org.infinispan.CLUSTER] (remote-thread--p8-t1) ISPN000336: Finished cluster-wide rebalance for cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar, topology id = 6 > [JBossINF] 10:25:08,270 INFO [org.infinispan.CLUSTER] (remote-thread--p6-t5) [Context=clusterbench-ee7.ear.clusterbench-ee7-web-granular.war][Scope=dev214]ISPN100003: Finished local rebalance > [JBossINF] 10:25:08,270 INFO [org.infinispan.CLUSTER] (remote-thread--p6-t5) ISPN000336: Finished cluster-wide rebalance for cache clusterbench-ee7.ear.clusterbench-ee7-web-granular.war, topology id = 6 > {code} > or after new cluster view was received > {code} > 10:29:53,838 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (thread-4,ee,dev212) ISPN000094: Received new cluster view for channel ejb: [dev215|6] (3) [dev215, dev214, dev212] > {code} > No errors or warning occured on client at that time. > Link to server log: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-db-se... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7395) The policy elements are ignored in the server sasl configuration

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created ISPN-7395: -------------------------------------- Summary: The policy elements are ignored in the server sasl configuration Key: ISPN-7395 URL: https://issues.jboss.org/browse/ISPN-7395 Project: Infinispan Issue Type: Bug Reporter: Wolf-Dieter Fink Assignee: Tristan Tarrant Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7392) The policy elements are ignored in the server sasl configuration

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-7392?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on ISPN-7392: ---------------------------------------- This server configuration is expected to work: <subsystem xmlns="urn:infinispan:server:endpoint:8.0"> <hotrod-connector cache-container="local" socket-binding="hotrod"> <topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/> <authentication security-realm="ApplicationRealm"> <sasl mechanisms="PLAIN" server-name="myServer"> <policy> <no-anonymous value="true"/> </policy> </sasl> </authentication> </hotrod-connector> As workaround SASL properties can be used: <subsystem xmlns="urn:infinispan:server:endpoint:8.0"> <hotrod-connector cache-container="local" socket-binding="hotrod"> <topology-state-transfer lazy-retrieval="false" lock-timeout="1000" replication-timeout="5000"/> <authentication security-realm="ApplicationRealm"> <sasl mechanisms="PLAIN" server-name="myServer"> <property name="javax.security.sasl.policy.noanonymous">true</property> </sasl> </authentication> </hotrod-connector> > The policy elements are ignored in the server sasl configuration > ---------------------------------------------------------------- > > Key: ISPN-7392 > URL: https://issues.jboss.org/browse/ISPN-7392 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > Server SASL mech policies can be specified via properties or policy elements. When using the latter, the policy elements are not converted to the corresponding properties and applied to the mech config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017