为什么我会收到此 FileNotFoundException 以及如何解决它?

Leg*_*ude 1 logging log4j amazon-web-services tomcat7

我正在尝试在我的 tomcat 服务器上实现 Log4J 日志记录(我们在本地环境中已经有了这个,我准备将我们的服务迁移到 AWS)。我已按照Tomcat7 文档中说明进行操作,并将所有内容都放在正确的位置。当我尝试启动 Tomcat 时,我FileNotFound在日志中收到异常并且应用程序无法启动。

Configuration error
java.io.FileNotFoundException: /usr/share/tomcat7/conf/logging.properties (No such file or directory)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:146)
        at java.io.FileInputStream.<init>(FileInputStream.java:101)
        at org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:466)
        at org.apache.juli.ClassLoaderLogManager.readConfiguration(ClassLoaderLogManager.java:311)
        at java.util.logging.LogManager$2.run(LogManager.java:320)
        at java.util.logging.LogManager$2.run(LogManager.java:318)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:318)
        at java.util.logging.LogManager.getLogManager(LogManager.java:300)
        at java.util.logging.Logger.<init>(Logger.java:265)
        at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1468)
        at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1466)
        at java.util.logging.LogManager$1.run(LogManager.java:204)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.util.logging.LogManager.<clinit>(LogManager.java:181)
        at java.util.logging.Logger.demandLogger(Logger.java:339)
        at java.util.logging.Logger.getLogger(Logger.java:393)
        at org.apache.juli.logging.impl.Jdk14Logger.getLogger(Jdk14Logger.java:164)
        at org.apache.juli.logging.impl.Jdk14Logger.<init>(Jdk14Logger.java:55)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at org.apache.juli.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1025)
        at org.apache.juli.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:844)
        at org.apache.juli.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:541)
        at org.apache.juli.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:292)
        at org.apache.juli.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:269)
        at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:657)
        at org.apache.catalina.startup.Bootstrap.<clinit>(Bootstrap.java:49)
Run Code Online (Sandbox Code Playgroud)

我怀疑这是因为我们的 Tomcat7 配置有一些非标准的东西,但是 AWS 上的初始设置是由一位不再对我可用的顾问执行的。我在哪里可以查看,我应该检查什么来纠正这个问题?

好的答案应该不教我把一个logging.properties文件/usr/share/tomcat7/conf/,因为这不是我有多么现有的配置工作(我没有这个问题存在)和tomcat7文件明确地告诉用户删除logging.properties../conf/,除非有一些需要注意的需要它没有在 tomcat 文档中表达。

Leg*_*ude 6

问题似乎与tomcat7bash shell 脚本有关(由上述顾问编写或更新)。此脚本已硬编码以检查logging.propertiesJava 选项 ( -Djava.util.logging.config.file="${CATALINA_BASE}/conf/logging.properties") 中的文件。

从 tomcat7 脚本中删除这一行已更正了问题。