June 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4339) Make config-modifier.xsl independent of version of schema

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4339?page=com.atlassian.jira.plugin.... ] Tomas Sykora commented on ISPN-4339: ------------------------------------ Thank [~vchepeli] VERY MUCH for your support with this. It was already integrated! > Make config-modifier.xsl independent of version of schema > --------------------------------------------------------- > > Key: ISPN-4339 > URL: https://issues.jboss.org/browse/ISPN-4339 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Labels: testsuite > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > For example rolling upgrades tests need to transform configuration xml files from different versions of Infinispan (schema 6.0, 7.0 ... etc.) Current config-modifier.xsl uses strict xmlns elements together with specification of a schema version. > Get rid of it and make it independent. So we can use just one config modifier for modification of even old XML config files coming from old server distributions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4341) Verify Query functionality in OSGi

by Martin Gencur (JIRA)

Martin Gencur created ISPN-4341: ----------------------------------- Summary: Verify Query functionality in OSGi Key: ISPN-4341 URL: https://issues.jboss.org/browse/ISPN-4341 Project: Infinispan Issue Type: Task Components: Test Suite - Query Reporter: Martin Gencur Assignee: Sanne Grinovero The goal is to migrate tests for Query into Karaf and find out which tests are passing/failing, whether there are problems with class loading etc. This task should help assess the feasIbility of running queries in embedded mode in OSGi. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4336) Don't start any server when compiling as-integration-client

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4336?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4336: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha5 Resolution: Done > Don't start any server when compiling as-integration-client > ----------------------------------------------------------- > > Key: ISPN-4336 > URL: https://issues.jboss.org/browse/ISPN-4336 > Project: Infinispan > Issue Type: Bug > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.Alpha5 > > > When running "mvn -DskipTests clean install" you will see in the log something similar: > [echo] Starting Infinispan server from /home/comp_/cc/infinispan/infinispan/integrationtests/as-integration-client/target/server > [echo] Waiting for Infinispan server to start > [echo] Infinispan server started -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4337) Race condition in as-integration-client on adding +x to standalone.sh

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4337?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4337: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha5 Resolution: Done > Race condition in as-integration-client on adding +x to standalone.sh > --------------------------------------------------------------------- > > Key: ISPN-4337 > URL: https://issues.jboss.org/browse/ISPN-4337 > Project: Infinispan > Issue Type: Bug > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.Alpha5 > > > "chmod +x" and "./standalone.sh" are both spawned because of this "./standalone.sh" can execute before the chmod and fail with: > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (infinispan-server-startup) on project infinispan-as-module-client-integrationtests: An Ant BuildException has occured: Execute failed: java.io.IOException: Cannot run program "/home/comp_/cc/infinispan/infinispan/integrationtests/as-integration-client/target/server/bin/standalone.sh" (in directory "/home/comp_/cc/infinispan/infinispan/integrationtests/as-integration-client"): error=13, Permission denied > [ERROR] around Ant part ...<exec spawn="true" executable="/home/comp_/cc/infinispan/infinispan/integrationtests/as-integration-client/target/server/bin/standalone.sh" osfamily="unix">... @ 10:159 in /home/comp_/cc/infinispan/infinispan/integrationtests/as-integration-client/target/antrun/build-main.xml -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4235) RHQ JMX does not support multiple cache managers properly

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4235?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4235: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2598 > RHQ JMX does not support multiple cache managers properly > --------------------------------------------------------- > > Key: ISPN-4235 > URL: https://issues.jboss.org/browse/ISPN-4235 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 7.0.0.Alpha3 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > The JMX RHQ pluging currently queries all cache managers and lumps them together. Thus if you have multiple cache managers in separate domains they all show as 1 cache manager with all the caches for each underneath it. We need to separate each cache manager by domain in the plugin so that each can be administered separately. > It appears the CacheManagerDiscovery lumps all the managers by type in createDiscoveredResources. We would then have to change the CacheManagerComponent to properly query the specific mbean. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4235) RHQ JMX does not support multiple cache managers properly

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4235?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4235: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha5 7.0.0.Final Resolution: Done > RHQ JMX does not support multiple cache managers properly > --------------------------------------------------------- > > Key: ISPN-4235 > URL: https://issues.jboss.org/browse/ISPN-4235 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 7.0.0.Alpha3 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > The JMX RHQ pluging currently queries all cache managers and lumps them together. Thus if you have multiple cache managers in separate domains they all show as 1 cache manager with all the caches for each underneath it. We need to separate each cache manager by domain in the plugin so that each can be administered separately. > It appears the CacheManagerDiscovery lumps all the managers by type in createDiscoveredResources. We would then have to change the CacheManagerComponent to properly query the specific mbean. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4339) Make config-modifier.xsl independent of version of schema

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4339?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4339: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha5 7.0.0.Final Resolution: Done > Make config-modifier.xsl independent of version of schema > --------------------------------------------------------- > > Key: ISPN-4339 > URL: https://issues.jboss.org/browse/ISPN-4339 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 7.0.0.Alpha4 > Reporter: Tomas Sykora > Assignee: Tomas Sykora > Labels: testsuite > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > For example rolling upgrades tests need to transform configuration xml files from different versions of Infinispan (schema 6.0, 7.0 ... etc.) Current config-modifier.xsl uses strict xmlns elements together with specification of a schema version. > Get rid of it and make it independent. So we can use just one config modifier for modification of even old XML config files coming from old server distributions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4260) Server test suite leaving process org.h2.tools.Server running when a test fails

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4260?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4260: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2596 > Server test suite leaving process org.h2.tools.Server running when a test fails > ------------------------------------------------------------------------------- > > Key: ISPN-4260 > URL: https://issues.jboss.org/browse/ISPN-4260 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.0.0.Alpha3 > Reporter: Martin Gencur > Assignee: Vitalii Chepeliuk > Priority: Minor > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > We should perform an action to stop the process even if some tests fail. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4260) Server test suite leaving process org.h2.tools.Server running when a test fails

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4260?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4260: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha5 7.0.0.Final Resolution: Done > Server test suite leaving process org.h2.tools.Server running when a test fails > ------------------------------------------------------------------------------- > > Key: ISPN-4260 > URL: https://issues.jboss.org/browse/ISPN-4260 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.0.0.Alpha3 > Reporter: Martin Gencur > Assignee: Vitalii Chepeliuk > Priority: Minor > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > > We should perform an action to stop the process even if some tests fail. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4332) Validate that Infinispan works with Apache Aries TransactionManager

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4332?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4332: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha5 7.0.0.Final Resolution: Done > Validate that Infinispan works with Apache Aries TransactionManager > ------------------------------------------------------------------- > > Key: ISPN-4332 > URL: https://issues.jboss.org/browse/ISPN-4332 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha5, 7.0.0.Final > > Attachments: TestSuite.txt > > > Apache Aries TM[1] runs in OSGi already[2], so let's validate that our test suite works fine with it. > Would be nice to have a maven profile that allows running transactions with this manager on demand. > [1]http://search.maven.org/#artifactdetails%7Corg.apache.aries.transaction... > [2] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.0... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2014