You are right Rupert. The zip file cannot be opened because it is not recognized as a valid archive - due to the exception it got into earlier. The write.lock file is created by SolrIndexWriter (Solr product/package). In the initial create the lock is properly closed, however on subsequent calls, it does not close it. Did not get a chance to see how to fix this is part of Solr. In the interim, just to make sure the test goes through, which it does, I changed SolrYardIndexingDestination.writeSolrIndexArchive method to exclude "write.lock". I will get to Solr debug later in the day and gather more info.
Vasanth. -----Original Message----- From: Rupert Westenthaler [mailto:rupert.westentha...@gmail.com] Sent: Tuesday, October 15, 2013 5:25 AM To: dev@stanbol.apache.org Subject: Re: Apache Stanbol Entityhub Indexing Destination SolrYard 0.12.0-SNAPSHOT build failure... On Mon, Oct 14, 2013 at 6:32 PM, <vasanth.l...@ubs.com> wrote: > Yes Rupert. It extracts all the files however, it tries to add entry > (write.lock) which is not probably closed. It will be a few hours before I > can get to my workspace to give a meaningful response. Will revert later this > evening. Maybe it would be a good idea the exclude the 'write.lock' from the archive. But the test is failing when the UnitTest tries to open the previously '{name}.solrindex.zip' file created by the SolrYardIndexingDestination. It is NOT related to the creation of that file. So I do not understand why you think that this is related to adding the 'write.lock' entry. best Rupert > > Regards, > Vasanth. > > -----Original Message----- > From: Rupert Westenthaler [mailto:rupert.westentha...@gmail.com] > Sent: Monday, October 14, 2013 12:15 PM > To: dev@stanbol.apache.org > Subject: Re: Apache Stanbol Entityhub Indexing Destination SolrYard > 0.12.0-SNAPSHOT build failure... > > Hi Vasanth > > The SolrYard destination creates a Zip Archive containing a compressed > SolrCore. The failing fails as it tries to open this file to check if all > expected files are present. > > Here is the Exception > > java.util.zip.ZipException: error in opening zip file > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:127) > at java.util.zip.ZipFile.<init>(ZipFile.java:143) > at > org.apache.stanbol.entityhub.indexing.destination.solryard.SolrYardInd > exingDestinationTest.validateSolrDestination(SolrYardIndexingDestinati > onTest.java:208) > > > The file in question does exist (because this is asserted earlier). > You can find it under > > > entityhub/indexing/destination/solryard/target/test-files/testConfigs/ > simple/indexing/dist/simple.solrindex.zip > > Would be nice if you can try to open/excract the file using an other tool. I > would like to know if this is an issue of the JVM or if the file is corrupted. > > Thanks for reporting > > best > Rupert > > > On Mon, Oct 14, 2013 at 5:26 PM, <vasanth.l...@ubs.com> wrote: >> >> Thanks for your response David (?). I tried mvn clean install - >> results in the same error. I skipped tests and continued. However, I >> was wondering if we have a clean test - seems this is related to Solr >> indexes being uwrapped into a folder and the write.lock file not >> getting deleted (/ released). >> >> -----Original Message----- >> From: Antonio David Perez Morales [mailto:ape...@zaizi.com] >> Sent: Monday, October 14, 2013 11:23 AM >> To: Stanbol Dev List >> Subject: Re: Apache Stanbol Entityhub Indexing Destination SolrYard >> 0.12.0-SNAPSHOT build failure... >> >> Hi Vasanth >> >> Have you tried with `mvn clean install`? >> >> Some Stanbol tests use the target directory to store temporal files >> during the tests execution. >> If the directory already exists with incorrect information the tests >> can fail. >> >> Looking at your test traces, it seems that you are using Windows and >> I think there were errors on windows and the temp directory. >> >> If you are still getting errors using a maven clean installation try >> to skip the tests (using -DskipTests in mvn command) to ensure that >> it's not a problem of Stanbol maven packages. >> >> Regards >> >> >> On Sat, Oct 12, 2013 at 5:09 PM, vasanth loka <vasantl...@gmail.com> >> wrote: >> >>> I get test failures when i build entityhub from sources. Any help to >>> get this fixed? >>> >>> >>> Tests run: 6, Failures: 0, Errors: 2, Skipped: 0 >>> >>> [INFO] >>> -------------------------------------------------------------------- >>> - >>> - >>> -- >>> [INFO] Reactor Summary: >>> [INFO] >>> [INFO] Apache Stanbol Entityhub .......................... SUCCESS >>> [1.133s] [INFO] Apache Stanbol Entityhub Generic Service API ...... >>> SUCCESS [3.921s] [INFO] Apache Stanbol Entityhub Generic Test >>> Framework ... SUCCESS [1.675s] [INFO] Apache Stanbol Entityhub >>> Generic >> >>> Core ............. SUCCESS [3.389s] [INFO] Apache Stanbol Entityhub >>> Model Clerezza ........... SUCCESS [2.431s] [INFO] Apache Stanbol >>> Entityhub Query SPARQL ............. SUCCESS [1.941s] [INFO] Apache >>> Stanbol Entityhub Site Linked Data Protocol SUCCESS [1.431s] [INFO] >>> Apache Stanbol Entityhub Managed Site ............. SUCCESS [1.213s] >>> [INFO] Apache Stanbol Entityhub Yard based on Clerezza ... SUCCESS >>> [2.168s] [INFO] Apache Stanbol Entityhub Yard based on Solr ....... >>> SUCCESS [10.263s] [INFO] Apache Stanbol Entityhub Web Jersey HTTP >>> Endpoint . SUCCESS [3.653s] [INFO] Apache Stanbol Entityhub LDPath >>> Support ........... SUCCESS [13.683s] [INFO] Apache Stanbol >>> Entityhub Indexing ................. SUCCESS [0.029s] [INFO] Apache >>> Stanbol Entityhub Indexing Core ............ SUCCESS [8.494s] [INFO] >>> Apache Stanbol Entityhub Indexing Source for Jena TDB SUCCESS >>> [5.189s] [INFO] Apache Stanbol Entityhub Indexing Source for vCard >>> SUCCESS [1.228s] [INFO] Apache Stanbol Entityhub Indexing >>> Destination SolrYard >> >>> FAILURE [7.149s] [INFO] Apache Stanbol Entityhub Indexing Generic >>> RDF ..... SKIPPED [INFO] Apache Stanbol Entityhub Indexing for >>> geonames.org SKIPPED [INFO] Apache Stanbol Entityhub Indexing for >>> DBpedia.org . SKIPPED [INFO] Apache Stanbol Entityhub Indexing for >>> dblp ........ SKIPPED [INFO] Apache Stanbol Entityhub Indexing for >>> freebase.com SKIPPED [INFO] Apache Stanbol Entityhub Default >>> Configuration .... SKIPPED [INFO] >>> -------------------------------------------------------------------- >>> - >>> - >>> -- >>> [INFO] BUILD FAILURE >>> [INFO] >>> -------------------------------------------------------------------- >>> - >>> - >>> -- >>> >>> >> >> -- >> >> ------------------------------ >> This message should be regarded as confidential. If you have received >> this email in error please notify the sender and destroy it immediately. >> >> Statements of intent shall only become binding when confirmed in hard >> copy by an authorised signatory. >> >> Zaizi Ltd is registered in England and Wales with the registration >> number 6440931. The Registered Office is Brook House, 229 Shepherds >> Bush Road, London W6 7AN. >> Please visit our website at >> http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html >> for important disclosures and information about our e-mail policies. >> For your protection, please do not transmit orders or instructions by >> e-mail or include account numbers, Social Security numbers, credit >> card numbers, passwords, or other personal information. > > > > -- > | Rupert Westenthaler rupert.westentha...@gmail.com > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen > > Please visit our website at > http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html > for important disclosures and information about our e-mail policies. > For your protection, please do not transmit orders or instructions by > e-mail or include account numbers, Social Security numbers, credit > card numbers, passwords, or other personal information. -- | Rupert Westenthaler rupert.westentha...@gmail.com | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
Please visit our website at http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html for important disclosures and information about our e-mail policies. For your protection, please do not transmit orders or instructions by e-mail or include account numbers, Social Security numbers, credit card numbers, passwords, or other personal information.
