Using Drupal, we've tried to import the configuration files from the solr_api_search module. When importing them and trying to initialize the core, I see the following error (Solr 7.7.2):
Could not load conf for core testcore: Can't load schema /data/solr_data/data/testcore/conf/schema.xml: Plugin init failure for [schema.xml] fieldType \"collated_ar\": Error loading class 'solr.ICUCollationField'
This is what the inside of the solrcore.properties file looks like. I added the solr.install.dir option after some people with similar issues reported that it fixed their problem:
solr.replication.master=false
solr.replication.slave=false
solr.replication.pollInterval=00:00:60
solr.replication.masterUrl=http://localhost:8983/solr
solr.replication.confFiles=schema.xml,schema_extra_types.xml,schema_extra_fields.xml,elevate.xml,stopwords_ar.txt,synonyms_ar.txt,nouns_ar.txt,protwords_ar.txt,accents_ar.txt,stopwords_en.txt,synonyms_en.txt,protwords_en.txt,accents_en.txt,stopwords_fr.txt,synonyms_fr.txt,nouns_fr.txt,protwords_fr.txt,accents_fr.txt,stopwords_de.txt,synonyms_de.txt,nouns_de.txt,protwords_de.txt,accents_de.txt,stopwords_el.txt,synonyms_el.txt,nouns_el.txt,protwords_el.txt,accents_el.txt,stopwords_hi.txt,synonyms_hi.txt,nouns_hi.txt,protwords_hi.txt,accents_hi.txt,stopwords_it.txt,synonyms_it.txt,nouns_it.txt,protwords_it.txt,accents_it.txt,stopwords_und.txt,synonyms_und.txt,protwords_und.txt,accents_und.txt,stopwords_pl.txt,synonyms_pl.txt,nouns_pl.txt,protwords_pl.txt,accents_pl.txt,stopwords_pt-br.txt,synonyms_pt-br.txt,nouns_pt-br.txt,protwords_pt-br.txt,accents_pt-br.txt,stopwords_ru.txt,synonyms_ru.txt,nouns_ru.txt,protwords_ru.txt,accents_ru.txt,stopwords_es.txt,synonyms_es.txt,nouns_es.txt,protwords_es.txt,accents_es.txt,stopwords_tr.txt,synonyms_tr.txt,nouns_tr.txt,protwords_tr.txt,accents_tr.txt
solr.luceneMatchVersion=7.7
solr.install.dir=/opt/solr
This is the process running with ps -ef:
java -server -Xms512m -Xmx512m -XX:NewRatio=3 -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=8 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ConcGCThreads=4 -XX:ParallelGCThreads=4 -XX:+CMSScavengeBeforeRemark -XX:PretenureSizeThreshold=64m -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=50 -XX:CMSMaxAbortablePrecleanTime=6000 -XX:+CMSParallelRemarkEnabled -XX:+ParallelRefProcEnabled -verbose:gc -XX:+PrintHeapAtGC -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/data/solr_data/logs/solr_gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M -Dsolr.log.dir=/data/solr_data/logs -Djetty.port=8983 -DSTOP.PORT=7983 -DSTOP.KEY=solrrocks -Duser.timezone=UTC -Djetty.home=/opt/solr/server -Dsolr.solr.home=/data/solr_data/data -Dsolr.data.home= -Dsolr.install.dir=/opt/solr -Dsolr.default.confdir=/opt/solr/server/solr/configsets/_default/conf -Dlog4j.configurationFile=file:/data/solr_data/log4j.properties -Xss256k -Xss256k -Dsolr.jetty.https.port=8983 -Dsolr.log.muteconsole -XX:OnOutOfMemoryError=/opt/solr/bin/oom_solr.sh 8983 /data/solr_data/logs -jar start.jar --module=http
I have the following libraries inside of /opt/solr/contrib/analysis-extras/lib
-rw-r--r--. 1 solr solr 12370975 Jun 20 2018 icu4j-62.1.jar
-rw-r--r--. 1 solr solr 20140 Feb 18 2018 morfologik-fsa-2.1.5.jar
-rw-r--r--. 1 solr solr 1886867 Feb 18 2018 morfologik-polish-2.1.5.jar
-rw-r--r--. 1 solr solr 53644 Feb 18 2018 morfologik-stemming-2.1.5.jar
-rw-r--r--. 1 solr solr 1245779 Jun 29 2018 opennlp-tools-1.9.0.jar
Is there some option that I am missing in order to get Solr to load the .jar files?
SOlr requires different features that require an optional libraries. All of these are comes with Solr. You need to adjust solr.install.dir like already mentioned in file named INSTALL.md
Updating path to solr.install.dir=/opt/solr in solrcore.properties to fix the issue.
Check the jar named as "icu4j-62.1.jar". Check the path of the same is mentioned in solrConfig.xml and check it the lib is getting loaded.
Development environment:
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 11.0.6, vendor: Oracle Corporation, runtime: /home/linuxlp/opt/graalvm/graalvm-svm-linux-20.1.0-ea+28
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-31-generic", arch: "amd64", family: "unix"
My application uses Reactor Netty for client http rest services. The io.netty libraries are generating INFO errors since some of these classes are getting initialized at build time, but they need to be initialized at runtime. There is a Graalvm flag --initialize-at-run-time that I would like to try, but I don't see how to implement it. I tried to implement it in a config file "initruntime" and put that file in the resources/META-INF/substrate/config directory, but this didn't work. Part of client-debug0.log file is included below showing one of the exceptions:
[Sun May 24 18:38:16 EDT 2020][INFO] [SUB] Error: Class initialization of io.netty.handler.ssl.JettyNpnSslEngine failed. Use the option --initialize-at-run-time=io.netty.handler.ssl.JettyNpnSslEngine to explicitly request delayed initialization of this class.
You can add this command to the list of native-image commands like this:
<nativeImageArgs>
<nativeImageArg>--initialize-at-build-time=com.mycompany.main.internal.NativeImageStaticInitializer</nativeImageArg>
</nativeImageArgs>
I am trying to run jasmine test using grunt-contrib-jasmine
Below is my Gruntfile.js code
module.exports = function(grunt) {
grunt.initConfig({
jasmine : {
// Your project's source files
src : 'src/**/*.js',
// Your Jasmine spec files
specs : 'specs/**/*spec.js',
// Your spec helper files
helpers : 'specs/helpers/*.js'
}
});
// Register tasks.
grunt.loadNpmTasks('grunt-contrib-jasmine');
// Default task.
grunt.registerTask('default', 'jasmine');
};
Then I tried running "grunt jasmine" command from command prompt. It gives me an error like below
The issue you're describing was reported in this grunt issue. It was then fixed in this commit to grunt-contrib-jasmine on February 13 2016.
As of this writing, the most recent release of grunt-contrib-jasmine is v1.0.0, released on January 26 2016. So, the fix didn't make it into the most recent release, which is what NPM pulls when you do an install.
You can get around this by bypassing the NPM repository and going straight to GitHub for a prerelease version of grunt-contrib-jasmine. You do this by changing your package.json to read:
"dependencies: {
"grunt-contrib-jasmine": "git://github.com/gruntjs/grunt-contrib-jasmine#1e78d891704fa13fe7c7abf4cabf43cefacafcaf"
}
(The commit SHA in the URL just happens to be the most recent one at the time of this writing; feel free to replace it with a later one if you like.)
Ideally, this solution will become obsolete, when grunt-contrib-jasmine releases v1.0.1 (or higher) with the fix commit. Today though, this is what fixed the problem for me.
I'm trying to use cucumber (via Velocity) in a brand new Meteor project.
meteor create cucetest
cd cucetest
meteor add xolvio:cucumber
meteor
I have tried this on OS X El Capitan 10.11 and also on a brand new Cloud 9 IDE Ubuntu vm (using meteor --port $IP:$PORT).
Unfortunately, after adding sample features Velocity reports an error, with the cucumber log showing the following:
[xolvio:cucumber] Bad response from Chimp server.
{ statusCode: 200,
content: '',
headers:
{ 'content-type': 'application/json; charset=utf-8',
'cache-control': 'no-cache',
'content-length': '0',
date: 'Fri, 23 Oct 2015 21:04:56 GMT',
connection: 'keep-alive' },
data: null }
Is there anything I'm missing as I'm itching to start writing features but can't get cucumber working on my Mac or Ubuntu dev machines?
Grab the following Gist that I made:
https://gist.github.com/ffxsam/30905336d8cb43ed7b4d
This is a scaffolding script I use for every Meteor+React project. Never mind that it uses React, that part isn't relevant. You should be able to do meteor run and Cucumber should work perfectly (it takes a minute or two for the mirror to start up).
If anything, you can just look at the tests folder to see how things should be set up.
i try to deploy my meteor application, but it still fail. I use meteor 0.6.1, and its package system.
in my root app, i created the following file tree :
packages
cheerio
package.js
iconv-lite
package.js
here is the content of the package.js :
Package.describe({
summary: 'Cheerio, an html parser with Jquery like API, but server side'
});
Npm.depends({cheerio: '0.10.8'});
and
Package.describe({
summary: 'Encoding management'
});
Npm.depends({'iconv-lite': '0.2.7'});
Then i do a meteor deploy appName, and then a meteor logs appName
and here is the error :
[Tue Apr 09 2013 13:14:59 GMT+0000 (UTC)] INFO ReferenceError: module is not defined
at app/packages/cheerio/index.js:5:11
at /meteor/containers/72e47bd9-1446-3b0f-126d-113dfb566c3c/bundle/server/server.js:282:7
at Array.forEach (native)
at Function._.each._.forEach (/meteor/dev_bundles/0.3.0/lib/node_modules/underscore/underscore.js:79:11)
at run (/meteor/containers/72e47bd9-1446-3b0f-126d-113dfb566c3c/bundle/server/server.js:227:7)
So i get a problem because the var module is not defined in the js file.
I don't know what to do, and any help would be great.
Thanks
Based on this website: meteor-npm-integration, i wrote a little subject to explain a little bit more the system of meteor Npm package: tumblr.
I think you still need at least one js file that you add using api.add_files from package.js, which you have it doing the Npm.require