[JBoss JIRA] (ISPN-4139) Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/ISPN-4139?page=com.atlassian.jira.plugin.... ]
Hardy Ferentschik commented on ISPN-4139:
-----------------------------------------
{quote}
Infinispan Query uses Hibernate Search, currently still using 4.5.0. So there are tests in this tree which use Hibernate Search 4.5 in combination with the Lucene Directory too, run with Lucene 3.6.2
{quote}
:-( Would it not help to extract these Lucene sub modules from the main Infinispan tree? Not only is there an nasty interdependency, but you also need a full Infinispan release in order to get out a new version of the Infinispan Directory (which is required by Search). Why not move Infinispan Directory in its own repo or Hibernate Search?
{quote}
If you have a plan to fix this issue I'm happy to reassign to you as I've been busy with debugging other Search issues,
{quote}
Ok. Right now, I have also other things I want to finish first. Let's see who gets to it first. We just need to make sure t sync in case either one of us starts working on this.
{quote}
but be aware of the intricate compatibility requirements.
{quote}
:-(
> Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
> -----------------------------------------------------
>
> Key: ISPN-4139
> URL: https://issues.jboss.org/browse/ISPN-4139
> Project: Infinispan
> Issue Type: Task
> Components: Lucene Directory
> Reporter: Hardy Ferentschik
> Assignee: Sanne Grinovero
>
> * {{DirectoryLuceneV4}} should not probably extend {{BaseDirectory}} instead of plain {{Directory}}
> * {{Lock#release}} got removed into {{Lock#close}}. {{BaseLuceneLock}} needs to change, but I am not sure how this works in order to support Lucene 3 and 4!?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4139) Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-4139?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-4139:
---------------------------------------
{quote}How is this even related?{quote}
Infinispan Query uses Hibernate Search, currently still using 4.5.0. So there are tests in this tree which use Hibernate Search 4.5 in combination with the Lucene Directory too, run with Lucene 3.6.2
We need to solve our integration issues in Hibernate Search to replace the one used by Infinispan Query so that I can drop the need to have the Lucene Directory to support both old and new Lucene versions. Current roadblock is the serialization, and as you know we might introduce more roadbocks while making more changes in Search 5.. which is why it's good to keep an eye on both projects as we need to converge quickly.
If you have a plan to fix this issue I'm happy to reassign to you as I've been busy with debugging other Search issues, but be aware of the intricate compatibility requirements. If you can avoid any SPI changes it would be best; otherwise I think we'd be better off postponing this upgrade after we dropped Lucene 3.6, and postponed the update in Search too.
> Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
> -----------------------------------------------------
>
> Key: ISPN-4139
> URL: https://issues.jboss.org/browse/ISPN-4139
> Project: Infinispan
> Issue Type: Task
> Components: Lucene Directory
> Reporter: Hardy Ferentschik
> Assignee: Sanne Grinovero
>
> * {{DirectoryLuceneV4}} should not probably extend {{BaseDirectory}} instead of plain {{Directory}}
> * {{Lock#release}} got removed into {{Lock#close}}. {{BaseLuceneLock}} needs to change, but I am not sure how this works in order to support Lucene 3 and 4!?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4139) Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/ISPN-4139?page=com.atlassian.jira.plugin.... ]
Hardy Ferentschik commented on ISPN-4139:
-----------------------------------------
{quote}
Lol, that's the reason for me to work on including Search 5 in Infinispan asap: to get rid of that (remove the Lucene3 support)
{quote}
How is this even related?
> Upgrade Lucene 4 Infinispan Directory to Lucene 4.7.0
> -----------------------------------------------------
>
> Key: ISPN-4139
> URL: https://issues.jboss.org/browse/ISPN-4139
> Project: Infinispan
> Issue Type: Task
> Components: Lucene Directory
> Reporter: Hardy Ferentschik
> Assignee: Sanne Grinovero
>
> * {{DirectoryLuceneV4}} should not probably extend {{BaseDirectory}} instead of plain {{Directory}}
> * {{Lock#release}} got removed into {{Lock#close}}. {{BaseLuceneLock}} needs to change, but I am not sure how this works in order to support Lucene 3 and 4!?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-3724) REST RollUps -- Unsupported protocol version 60 throws annoying ERROR and WARN
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3724?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3724:
-----------------------------------------------
Pedro Ruivo <pruivo(a)redhat.com> changed the Status of [bug 1031660|https://bugzilla.redhat.com/show_bug.cgi?id=1031660] from ASSIGNED to MODIFIED
> REST RollUps -- Unsupported protocol version 60 throws annoying ERROR and WARN
> ------------------------------------------------------------------------------
>
> Key: ISPN-3724
> URL: https://issues.jboss.org/browse/ISPN-3724
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.0.CR1
> Reporter: Tomas Sykora
> Assignee: Mircea Markus
> Labels: 620
> Fix For: 6.0.1.Final, 7.0.0.Alpha1
>
> Attachments: restRollups6dot0to6dot0tryingToGetHRkey, RestRollUpsUnsupportedProtocol60
>
>
> Trying to process REST rolling upgrades using latest infinispan server 6.0.0 snapshot as a TARGET node and the same server as a source node.
> Run Infinispan-server testsuite test for REST Rolling Upgrades.
> mvn clean verify -P suite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades -DfailIfNoTests=false
> See new attached file with current stacktrace. REST rolling upgrades from 5.2.x to 6.0 will probably _not_ be supported.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4104) Generic store cache child creation fails
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4104?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-4104:
--------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/2452, https://github.com/infinispan/infinispan/pull/2455 (was: https://github.com/infinispan/infinispan/pull/2452)
> Generic store cache child creation fails
> ----------------------------------------
>
> Key: ISPN-4104
> URL: https://issues.jboss.org/browse/ISPN-4104
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: William Burns
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> This issue is similar to: https://issues.jboss.org/browse/ISPN-4103
> I can see this error during server restart:
> 10:38:01,682 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "clustered"),
> ("distributed-cache" => "namedCache")
> ]) - failure description: "JBAS010292: org.infinispan.persistence.file.SingleFileStore is not a valid cache store"
> After issuing of operation this configuration fragment is added into standalone.xml configuration file: <store name="genericStore" class="org.infinispan.persistence.file.SingleFileStore" preload="true" passivation="false" purge="false"/>
> Child creation using not generic, but pure File Cache Store option works OK. Store is configured and using this class: org.infinispan.persistence.file.SingleFileStore, however, when trying to do the same using generic store creation, it fails.
> See error in linked JIRA (for loader) as I suspect there is the same cause for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4138) Regression in InfinispanSubsystemTestCase: management broken
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/ISPN-4138?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on ISPN-4138:
---------------------------------------
No strong opinion but I'd not generally classify this as a duplicate: this morning Infinispan was broken, while ISPN-4103 was resolved yesterday.
If you knew already you should have reopened ISPN-4103, and maybe even reverted it immediately: there is the risk now that someone in future backports only half of the fix.
> Regression in InfinispanSubsystemTestCase: management broken
> ------------------------------------------------------------
>
> Key: ISPN-4138
> URL: https://issues.jboss.org/browse/ISPN-4138
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management, Server
> Reporter: Sanne Grinovero
> Assignee: Mircea Markus
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> {noformat}
> Infinispan Server - Infinispan Subsystem .......... FAILURE
> Failed tests: testDescribeHandler[0](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[0](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[1](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[1](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[2](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[2](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[3](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[3](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[4](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[4](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[6](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[6](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> Tests in error:
> testParseAndMarshalModel[0](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[1](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[2](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[3](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[4](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[6](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> Tests run: 65, Failures: 12, Errors: 6, Skipped: 2{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4138) Regression in InfinispanSubsystemTestCase: management broken
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4138?page=com.atlassian.jira.plugin.... ]
William Burns resolved ISPN-4138.
---------------------------------
Resolution: Duplicate Issue
This was fixed in https://github.com/infinispan/infinispan/pull/2455 for ISPN-4103
> Regression in InfinispanSubsystemTestCase: management broken
> ------------------------------------------------------------
>
> Key: ISPN-4138
> URL: https://issues.jboss.org/browse/ISPN-4138
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management, Server
> Reporter: Sanne Grinovero
> Assignee: Mircea Markus
> Priority: Blocker
> Fix For: 7.0.0.Alpha2
>
>
> {noformat}
> Infinispan Server - Infinispan Subsystem .......... FAILURE
> Failed tests: testDescribeHandler[0](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[0](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[1](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[1](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[2](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[2](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[3](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[3](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[4](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[4](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> testDescribeHandler[6](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): JBAS014807: Management resource '[("subsystem" => "infinispan")]' not found
> testInstallIntoController[6](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase)
> Tests in error:
> testParseAndMarshalModel[0](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[1](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[2](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[3](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[4](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> testParseAndMarshalModel[6](org.jboss.as.clustering.infinispan.subsystem.InfinispanSubsystemTestCase): ParseError at [row,col]:[1,44](..)
> Tests run: 65, Failures: 12, Errors: 6, Skipped: 2{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (ISPN-4104) Generic store cache child creation fails
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4104?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4104:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1076047|https://bugzilla.redhat.com/show_bug.cgi?id=1076047] from ASSIGNED to MODIFIED
> Generic store cache child creation fails
> ----------------------------------------
>
> Key: ISPN-4104
> URL: https://issues.jboss.org/browse/ISPN-4104
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Reporter: Tomas Sykora
> Assignee: William Burns
> Fix For: 7.0.0.Alpha2, 7.0.0.Final
>
>
> This issue is similar to: https://issues.jboss.org/browse/ISPN-4103
> I can see this error during server restart:
> 10:38:01,682 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 19) JBAS014613: Operation ("add") failed - address: ([
> ("subsystem" => "infinispan"),
> ("cache-container" => "clustered"),
> ("distributed-cache" => "namedCache")
> ]) - failure description: "JBAS010292: org.infinispan.persistence.file.SingleFileStore is not a valid cache store"
> After issuing of operation this configuration fragment is added into standalone.xml configuration file: <store name="genericStore" class="org.infinispan.persistence.file.SingleFileStore" preload="true" passivation="false" purge="false"/>
> Child creation using not generic, but pure File Cache Store option works OK. Store is configured and using this class: org.infinispan.persistence.file.SingleFileStore, however, when trying to do the same using generic store creation, it fails.
> See error in linked JIRA (for loader) as I suspect there is the same cause for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years