2016-05-31 13 views
2

Wenn ich AEM-Instanz gestartet, ich in der Konsole validation.properties FileNotFound Fehler, gesehenAEM 6.2 Startfehler ESAPI Verzeichnis oder nicht lesbare Datei

komplette Log:

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0 
31.05.2016 17:24:26.379 *INFO * [main] Setting sling.home=crx-quickstart (command line) 
31.05.2016 17:24:26.395 *INFO * [main] Starting Apache Sling in D:\AEM 6.2\crx-quickstart 
31.05.2016 17:24:26.395 *INFO * [main] Sling Extension Lib Home : D:\AEM 6.2\crx-quickstart\launchpad\ext 
31.05.2016 17:24:26.395 *INFO * [Apache Sling Control [email protected]/127.0.0.1:56056] Apache Sling Control Listener started 
31.05.2016 17:24:26.410 *INFO * [main] Checking launcher JAR in folder D:\AEM 6.2\crx-quickstart\launchpad 
31.05.2016 17:24:26.426 *INFO * [main] Existing launcher is up to date, using it: 5.4.0.2_6_10-B004 (org.apache.sling.launchpad.base.jar) 
31.05.2016 17:24:26.441 *INFO * [main] Loading launcher class org.apache.sling.launchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar 
31.05.2016 17:24:26.444 *INFO * [main] External Libs Home (ext) is null or does not exists. 
31.05.2016 17:24:26.459 *INFO * [main] Setting sling.properties=conf/sling.properties 
31.05.2016 17:24:26.461 *INFO * [main] Setting sling.home=crx-quickstart 
31.05.2016 17:24:26.463 *INFO * [main] Setting sling.launchpad=D:\AEM 6.2\crx-quickstart\launchpad 
31.05.2016 17:24:26.464 *INFO * [main] Setting org.osgi.service.http.port=4502 
31.05.2016 17:24:26.465 *INFO * [main] Starting launcher ... 
31.05.2016 17:24:26.476 *INFO * [main] HTTP server port: 4502 
31.05.2016 17:24:27.706 *INFO* [FelixStartLevel] org.apache.sling.commons.log.logback.internal.Activator LogbackManager initialized at bundle startup 
31.05.2016 17:24:27.726 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice Service [org.apache.sling.commons.logservice.internal.LogServiceFactory,18, [org.osgi.service.log.LogService]] ServiceEvent REGISTERED 
31.05.2016 17:24:27.731 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice Service [org.apache.sling.commons.logservice.internal.LogReaderServiceFactory,19, [org.osgi.service.log.LogReaderService]] ServiceEvent REGISTERED 
31.05.2016 17:24:27.736 *INFO* [FelixStartLevel] org.apache.sling.commons.logservice BundleEvent STARTED 
31.05.2016 17:24:27.740 *INFO* [FelixStartLevel] org.apache.sling.installer.core BundleEvent RESOLVED 
31.05.2016 17:24:27.740 *INFO* [FelixStartLevel] org.apache.sling.installer.core BundleEvent STARTING 
**Attempting to load ESAPI.properties via file I/O. 
Attempting to load ESAPI.properties as resource file via file I/O. 
Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\AEM 6.2\ESAPI.properties 
Not found in SystemResource Directory/resourceDirectory: .esapi\ESAPI.properties 
Not found in 'user.home' (C:\Users\Raj Kumar) directory: C:\Users\Raj Kumar\esapi\ESAPI.properties 
Loading ESAPI.properties via file I/O failed. Exception was: java.io.FileNotFoundException 
Attempting to load ESAPI.properties via the classpath. 
SUCCESSFULLY LOADED ESAPI.properties via the CLASSPATH from '/ (root)' using class loader for DefaultSecurityConfiguration class! 
Attempting to load validation.properties via file I/O. 
Attempting to load validation.properties as resource file via file I/O. 
Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\AEM 6.2\validation.properties 
Not found in SystemResource Directory/resourceDirectory: .esapi\validation.properties 
Not found in 'user.home' (C:\Users\Raj Kumar) directory: C:\Users\Raj Kumar\esapi\validation.properties 
Loading validation.properties via file I/O failed. 
Attempting to load validation.properties via the classpath.** 
SUCCESSFULLY LOADED validation.properties via the CLASSPATH from '/ (root)' using class loader for DefaultSecurityConfiguration class! 
RAWProcessor succesfully installed 
31.05.2016 17:24:52.803 *INFO * [main] Startup completed 

Fehler:

Attempting to load ESAPI.properties via file I/O. 
    Attempting to load ESAPI.properties as resource file via file I/O. 
    Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\AEM 6.2\ESAPI.properties 
    Not found in SystemResource Directory/resourceDirectory: .esapi\ESAPI.properties 
    Not found in 'user.home' (C:\Users\Raj Kumar) directory: C:\Users\Raj Kumar\esapi\ESAPI.properties 
    Loading ESAPI.properties via file I/O failed. Exception was: java.io.FileNotFoundException 
    Attempting to load ESAPI.properties via the classpath. 
    SUCCESSFULLY LOADED ESAPI.properties via the CLASSPATH from '/ (root)' using class loader for DefaultSecurityConfiguration class! 
    Attempting to load validation.properties via file I/O. 
    Attempting to load validation.properties as resource file via file I/O. 
    Not found in 'org.owasp.esapi.resources' directory or file not readable: D:\AEM 6.2\validation.properties 
    Not found in SystemResource Directory/resourceDirectory: .esapi\validation.properties 
    Not found in 'user.home' (C:\Users\Raj Kumar) directory: C:\Users\Raj Kumar\esapi\validation.properties 
    Loading validation.properties via file I/O failed. 
    Attempting to load validation.properties via the classpath. 

Was ist die Datei validation.properties?

Wie behebt man diesen Fehler?

Ich sah den gleichen Fehler für CQ 5.6 auch, aber nicht die Idee der Ursache davon. kann jemand erklären?

Vielen Dank im Voraus.

Antwort

1

Die Datei validation.properties wird innerhalb der "com.day.cq.cq-xs-protection" verwendet. bündeln Um zu sehen, was es

  1. zu Felix Konsole (http://host:port/system/console/bundles/) die Bündelnummer herausfinden, gehen enthält "Adobe Granite XSS-Schutz (com.day.cq.cq-xssprotection)" genannt.
  2. Gehen Sie zu ihrem-aem-installation-folder \ crx-quickstart \ launchpad \ felix und suchen Sie den Ordner mit der gleichen Bundle-Nummer.
  3. kopieren Sie das Bundle in den Bundle-Ordner mit einigen Standardversion.0.0 auf einen Pfad.
  4. Verwenden Sie einen beliebigen Dekompiler, und sehen Sie, dass dort die Datei ESAPI.properties enthalten ist, die den Eintrag validation.properties enthält. Auf derselben Ebene befindet sich eine Datei validation.properties, die ebenfalls im selben Bundle enthalten ist. enter image description here

Während Inbetriebnahme von AEM-Instanz können Sie die unten Fehler in der stdout.log Datei. was sagt Ihnen, wo es erfolgreich geladen wird.

enter image description here

Sie können mehr Details über sie finden Sie unten. https://www.owasp.org/index.php/Category:OWASP_Enterprise_Security_API

Und die vaidator Eigenschaften Datei, die Sie versuchen können, anpassen https://www.owasp.org/index.php/ESAPI_Getting_Started_Guide