Liferay problem right classes are not creating showing warning in the console - gradle

Liferay problem right classes are not creating showing warning in the console. I need to solve this problem.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.liferay.petra.reflect.ReflectionUtil (file:/C:/Users/Asus/.gradle/caches/modules-2/files-2.1/com.liferay/com.liferay.portal.tools.service.builder/1.0.441/e697b9a1615661eb9346e8449b3f3c679fae845/com.liferay.portal.tools.service.builder-1.0.441.jar) to method java.lang.Object.clone()
WARNING: Please consider reporting this to the maintainers of com.liferay.petra.reflect.ReflectionUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
tried to uninstall install and also delete the file which is causing the problem.

Related

Hyperledger composer Rest API filter not working for asset

I am trying to execute Rest API using following filter
api/Commodity?filter={"where":{"owner":"resource:org.example.mynetwork.Trader%231"},%20"include":"resolve"}
but getting following error -
{"error":{"statusCode":500,"name":"Error","message":"2 UNKNOWN: error executing chaincode: transaction returned with failure: Error: ExecuteQuery not supported for leveldb","code":2,"metadata":{"_internal_repr":{}},"details":"error executing chaincode: transaction returned with failure: Error: ExecuteQuery not supported for leveldb","stack":"Error: 2 UNKNOWN: error executing chaincode: transaction returned with failure: Error: ExecuteQuery not supported for leveldb\n at new createStatusError (/home/composer/.npm-global/lib/node_modules/#ibmblockchain/composer-rest-server/node_modules/grpc/src/client.js:64:15)\n at /home/composer/.npm-global/lib/node_modules/#ibmblockchain/composer-rest-server/node_modules/grpc/src/client.js:583:15"}}
Kindly suggest what is wrong here?
The important part of the response is here Error: ExecuteQuery not supported for leveldb
This says that your fabric is configured to use the inbuilt leveldb system for storing the world state. Because of this you cannot perform any type of query on it, and that includes rest filters.
You need to change your fabric setup to use couchdb as the world state store instead.
Fabric documentation can be found here about building fabric networks and on this page there is a specific section about enabling couchdb.
see https://hyperledger-fabric.readthedocs.io/en/release-1.2/build_network.html

[Error]: Failed to run command with error: Error Domain=Parse Code=428

I get this error sometimes when trying to save things to Parse or to fetch data from it.
This is not constant and appear once in a while making the operation to fail.
I have contacted Parse for that. Here is their answer:
Starting on 4/28/2016, apps that have not migrated their database may see a "428" error code if the request cannot be handled by the remaining shared pool of resources. If you see this error in your logs, we highly recommend migrating the database for your app without delay.
Means this happens because of starting this date all apps are on low priority but those who started DB migration. So, Migration of the DB should resolve that.

Sonarqube Analysis org.joda.convert ERROR

Why do I get this error:
Class not found: org.joda.convert.ToString
None of my code uses this class (maven-based sonar analysis), and it doesn't seem to affect the analysis. However, I get worried whenever there are "[ERROR]" logs in the output. My exact command is:
mvn org.codehaus.mojo:sonar-maven-plugin:2.6:sonar
I switched to this because someone in another related answer suggested this...
This error message is logged by the analyzer whenever it tries to complete a symbol during semantic analysis and cannot find a .class file.
This will happen wether your classes are using this class directly or transitively (via a dependence, or a dependence of a dependence, etc.). This is arguably an error per say in all cases but this is an important information for users to know because lacking some classes can lead to incomplete results (some issues might not be raised because symbols won't be resolved).

pwdChangedTime which is not allowed by any of the objectclasses defined in that entry in OpenDj LDAP

I installed a new LDAP server (OpenDJ 2.4.6). I am trying to enable the replication with reference of existing server. But I am getting the below issue.
I ran the replication command, existing server (1st server). Can you please help/suggest on the below issue?
Establishing connections ..... Done.
Checking registration information .....
Error updating registration information. Details: Registration information
error. Error type: 'ERROR_UNEXPECTED'. Details:
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Entry
cn=admin,cn=Administrators,cn=admin data violates the Directory Server schema
configuration because it includes attribute pwdChangedTime which is not
allowed by any of the objectclasses defined in that entry]; remaining name
'cn=admin,cn=Administrators,cn=admin data'
See /tmp/opends-replication-6304872164983350730.log for a detailed log of this
operation.
Schema violation indicates that the entry is not compliant with the schema defined on the directory server.
Since the pwdChangedTime is by default defined in the Schema as an operational attribute and the error occurs with the dsreplication command (which is known to produce valid data), this probably indicates that you have messed up with the default schema and altered it in a non standard and incompatible way.

SQLException like archiver error. Connect internal only, until freed

can any one give me an idea regarding this below error:
2011-02-11 05:48:42,858
-[c=STATS_VITALS] Error running system monitor for connectionCloseTime:
java.sql.SQLException: ORA-00257: archiver error.
Connect internal only, until freed.
java.sql.SQLException: ORA-00257: archiver error.
Connect internal only, until freed.
This usually occurs when the system encounters an error while trying to archive a redo log. Was this working previously and it just failed now for the first time, or is this a new installation? Do you know where your logs are being archived? If so, check to see if that location is out of space as a first step. Once you have more information we might be able to help you a little more effectively.

Resources