What value set the environment variable GRIDGAIN_HOME when embedding GridGain into another application?
Currently I'm not defining it, the application is working fine but the in the log there's the following warning:
WARN org.gridgain.grid.util.typedef.G - Failed to detect GridGain installation
home. It was neither provided in GridConfiguration nor it could be detected
from GRIDGAIN_HOME system property or environmental variable.
Can I just ignore it?
Yes, this warning can be ignored.
Related
I'm trying to initialize local Hybris 2205.3 version and getting following error -
ERROR [hybrisHTTP27] [HacInitUpdateFacade] Failed to initialize
java.lang.IllegalArgumentException: Property 'http://javax.xml.XMLConstants/property/accessExternalSchema' is not recognized.
Using Oracle JDK 17.0.4.1. Initialization triggered from HAC.
I've tried adding following property to tomcat.generaloptions also which didn't help -
"-Djavax.xml.accessExternalSchema=all"
Any pointers to fix this? Or need more information?
It could be that one of the custom jar is older version and conflicting with oob. In one of our project we faced a similar issue and found that xerces.jar version in custom code was of lower version.
Both the jars I.e in oob and custom there was xmlconstant class but lower version jar used in custom code didn't have accessExternalSchema as class variable and was being picked up by system on startup because of conflict.
Oracle JDK not supported anymore, you need to try with SapMachine 17.0.
Whole system requirements by version is here.
We resolved the issue with Oracle JDK 17 only. We faced the same issue while upgrade from 2105 to 2211. This is due to jar dependency. We tried with the above given solution but it didn't work for us. We researched more and found the issue with dependency with xerces which caused conflict. We also found there is "xerces-2.12-orbeon' xerces-2.12-orbeon in OOTB. We did two things to resolve the issue
we updated classpath with xerces-2.12-orbeon( OOTB jar) in out custom code
We need to modify few code base as we were using xerces for Base64 encrytion and decryption for SSO
Please let me know if you have any questions, I will try my best to respond in time.
Regards,
Abhijit Das
Please find the link here:
https://answers.sap.com/questions/13781195/hybris-2211-upgradation-error.html?childToView=13818282
I am trying to set extra CAs for my nodejs project, I tried using " set NODE_EXTRA_CA_CERTS={directorty}/ca.pem" but the nodejs project still cannot pick up the set env variable.
How can set this variable?
Used the answer from https://stackoverflow.com/a/56239954/3700823 myself.
On windows you should backslashes instead of slashes. And make sure you use the full path (like set NODE_EXTRA_CA_CERTS=C:\stuffed\subfolder\thefile.pem). Though some mention relative path (like set NODE_EXTRA_CA_CERTS=.\subfolder\thefile.pem) should work as well, not tested myself. Maybe that's only valid for *nix.
Then either try restart node.exe, or the machine to make sure node.exe starts using the environment variable. For me it began to work after rebooting.
As the nodejs documentation mentions, nodejs should warn you once about any issue.
Check the official documentation: https://nodejs.org/api/cli.html#node_extra_ca_certsfile
I'm creating a NodeJS based application with sapui5 framework but I'm facing a problem.
My app and view work well in my Windows 10 environment. Now I'm trying to continue developing it in Ubuntu but I'm facing this problem in Checkbox.js:
The resource from http://localhost:8000/resources/sap/m/Checkbox.js was blocked due to MIME type ("type/html") mismatch (X-Content-Type-Options: nosniff).
Uncaught (in promise) Error: failed to load 'sap/m/Checkbox.js' from resources/sap/m/Checkbox.js: script load error
As you can see, the control does exist:
All other controls work normally. So when I remove the checkbox, my view works without problems.
See the section Console shows Uncaught Error: failed to load 'sap/m/xxxxx.js' from the doc.
And the reply by Tobias (tobiasso85) on the same issue:
Serving the resources depends on the server and its underlying filesystem used.
While Unix based systems are case-sensitive,
Windows is not case-sensitive by default.
I.e. in your view, you must have somewhere <Checkbox> which works on Windows but not on Ubuntu.
→ Change it to <CheckBox>.
Same applies to <ComboBox>, <LightBox>, <FlexBox>, ... etc.
Bonus: there are Breadcrumbs from the sap.m lib and BreadCrumbs from the sap.uxap lib. 👍
PS: when working in an IDE or editor that supports VSCode extensions, consider installing the official UI5 Language Assistant. That extension would've notified you that something is wrong:
The "Combobox" name is neither a class name in the "sap.m" namespace nor an aggregation of the <parentControl> class.
I'm using solr 5.2.1 with jetty.In my logs(solr.log) there's an error with
"org.apache.solr.core.CoreContainer; Error creating core [dosweb]: Could not load conf for core project : Error loading solr config from solrconfig.xml" title
,and I understand it's because of misconfigured in solr version,and it is showing me this exception:Caused by: java.lang.IllegalArgumentException: Illegal parameter 'termIndexInterval'
,what I should do to fix it.
thanks alot.
Not enough data.
It seems like your core is misconfigured for 5.2.1
I'd suggest that you try first with a reference configuration core, or a reference empty core, make sure that works, and then merge the config from the dosWeb core to the newly created core in steps.
This way you will find the part of the configuration that causes the issue.
EDIT -
After you added information (still not enough - a snippet of the offending configuration would have been good) I've been able to track down the bug that refers to the issue you get.
https://issues.apache.org/jira/browse/SOLR-6560
Essentially - the configuration for termIndexInterval is now not only deprecated, but can't be done in a standard way at all. From what I understand from the bug, It's also not needed anymore.
I get this warning for my xdatamodeld file: "Version hash information not available for all models". How do I get rid of this? I've also started to get a crash at startup when I install the app as new ... wonder if they're related? This is the crash:
* Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Cannot create an NSPersistentStoreCoordinator with a nil model'
This is a iOS5 beta issue, caused by having a fetch request in your model file. For now, removing the fetch request fixes it.
I am experiencing the same thing once I have installed Xcode 4.2 with iOS 5 beta 5, maybe it's something there?
I did not have is last night while working on my production system, with Xcode 4.1. Unfortunately I am reinstalling it now, and it'd take a while before i know whether that's the cause.
The first error indicates that you have multiple .xcdatamodel files with the same name but different versions. One of more of the multiples lacks an internal version number i.e. the version hash.
The second error is caused by the first because the managed object model cannot create itself by merging model files of the same name but different and unknown versions. A persistent store coordinator in turn cannot intialize without a valid managed object model.
If this is occurring in development and you don't have multiple versions intentionally, then you probably have an old compiled .mom or .momd file on the simulator from a previous build. Delete the app off the simulator entirely, then clean the entire project in Xcode and rebuild and reinstall. That usually resolves the problem.
I ran into this problem on iOS 5 SDK and it wasn't any of the above problems. My problem was because I had a lot of attributes in a single entity, that I inadvertently had a duplicate (i.e. two lastUpdatedDate attributes in the same entity).