奇怪的错误 already initialized constant OPTIONS 及解决方案

本文记录了一个Rails应用启动过程中遇到的问题及解决过程。作者在启动应用时遇到了与action_web_service相关的错误,通过排查依赖和gem安装情况最终解决了问题。
agideo@ats1:~/apps/app_name$ ruby script/server -e production
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with production environment...
Exiting
/home/agideo/apps/app_name/vendor/rails/railties/lib/commands/servers/mongrel.rb:15: warning: already initialized constant OPTIONS
/home/agideo/apps/app_name/vendor/rails/railties/lib/commands/servers/mongrel.rb:18: undefined method `options' for []:Array (NoMethodError)
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:32:in `gem_original_require'
from /usr/lib/ruby/1.8/rubygems/custom_require.rb:32:in `require'
from /home/agideo/apps/app_name/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require'
from /home/agideo/apps/app_name/vendor/rails/activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in'
from /home/agideo/apps/app_name/vendor/rails/activesupport/lib/active_support/dependencies.rb:495:in `require'
from /home/agideo/apps/app_name/vendor/rails/railties/lib/commands/server.rb:39
from script/server:3:in `require'
from script/server:3


运行时奇怪的 错误

网上的资料说缺少 gem

找出所有的 require 来

grep -rni '^require' ./*  


对了N个小时 还是不行

最后无意中 ruby script/console production 试了一下,看到了

`gem_original_require': no such file to load -- action_web_service (MissingSourceFile)

晕啊.就是它

打开
vi config/environment.rb


加一句

config.frameworks -= [ :action_web_service ]


当然你也可以

gem install actionwebservice


终于可以睡觉了

rails 新的版本已经没有 action_web_service
FO: Starting Servlet Engine: Apache Tomcat/7.0.59 Sep 03, 2025 1:28:08 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory /data/EnterpriseApp/TomcatApp/tomcat-7.0-bdcs_hande/webapps/bdcs Sep 03, 2025 1:28:09 PM org.apache.catalina.startup.ContextConfig processAnnotationsJar SEVERE: Unable to process Jar entry [META-INF/versions/9/module-info.class] from Jar [jar:file:/data/EnterpriseApp/TomcatApp/tomcat-7.0-bdcs_hande/webapps/bdcs/WEB-INF/lib/commons-net-3.10.0.jar!/] for annotations org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 19 at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:97) at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:55) at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:177) at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:85) at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2089) at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1965) at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1931) at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1916) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1330) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:889) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:386) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5412) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1245) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1895) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Sep 03, 2025 1:28:10 PM org.apache.catalina.startup.TaglibUriRule body INFO: TLD skipped. URI: webwork is already defined log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /logs/bdcs.log (No such file or directory) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at java.io.FileOutputStream.<init>(FileOutputStream.java:133) at org.apache.log4j.FileAppender.setFile(FileAppender.java:272) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151) at org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:206) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:123) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:87) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:645) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:603) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:500) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:406) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:432) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:460) at org.apache.log4j.LogManager.<clinit>(LogManager.java:113) at org.apache.log4j.Category.getInstance(Category.java:530) at org.apache.commons.logging.impl.Log4jFactory.getInstance(Log4jFactory.java:140) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:257) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:390) at com.opensymphony.clickstream.ClickstreamListener.<clinit>(ClickstreamListener.java:24) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at java.lang.Class.newInstance(Class.java:442) at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:116) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4932) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5524) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1245) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1895) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) log4j:ERROR Either File or DatePattern options are not set for appender [bdcs]. 09-03 13:28:11.438 INFO [ContextLoader.java:142] Root WebApplicationContext: initialization started 09-03 13:28:11.457 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/sso/test_sso_context.xml] 09-03 13:28:11.479 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/exporthr/test_exporthr_context.xml] 09-03 13:28:11.486 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/prodtech/prod_prodtech_context.xml] 09-03 13:28:11.500 INFO [XmlBeanDefinitionReader.java:119] Loading XML bean definitions from class path resource [com/smics/apps/bdcs/mail_content.xml] 09-03 13:28:11.501 ERROR [ContextLoader.java:172] Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [com/smics/apps/bdcs/mail_content.xml]; nested exception is java.io.FileNotFoundException: class path resource [com/smics/apps/bdcs/mail_content.xml] cannot be opened because it does not exist java.io.FileNotFoundException: class path resource [com/smics/apps/bdcs/mail_content.xml] cannot be opened because it does not exist at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:127) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:99) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:114) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:82) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:87) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:262) at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:131) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:224) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:150) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:48) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5016) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5524) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1245) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1895) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)什么原因
最新发布
09-04
<think> 我们面对的是一个Tomcat启动时的错误日志,主要包含两类错误: 1. SEVERE: Unable to process Jar entry [META-INF/versions/9/module-info.class] ... Invalid byte tag in constant pool: 19 2. 后续的log4j错误和Spring的BeanDefinitionStoreException(找不到mail_content.xml) 首先分析第一个错误- 错误发生在处理`commons-net-3.10.0.jar`中的`module-info.class`文件时。 - 原因是Tomcat 7.0.59使用的`tomcat-util-bcel`版本较低,无法识别Java 9引入的模块化信息(module-info.class)。 - 因为`commons-net-3.10.0`版本开始支持Java 9模块化,所以包含了此文件。 第二个错误链: - log4j错误:试图创建日志文件`/logs/bdcs.log`失败(文件或目录不存在),并且配置错误(File或DatePattern选项未设置)。 - Spring初始化错误:在类路径上找不到`com/smics/apps/bdcs/mail_content.xml`。 综合来看,根本原因可能有: 1. **Tomcat版本过低**:Tomcat 7.0.59(发布于2015年)不支持Java 9及以上编译的类文件(如module-info.class)。解决方案是升级Tomcat或使用不包含模块化信息的旧版本依赖。 2. **依赖jar包不兼容**:`commons-net-3.10.0.jar`是为Java 9及以上设计的,而Tomcat 7支持的最高Java版本是Java 8。 3. **日志配置错误**:log4j配置文件错误,导致无法创建日志文件(可能是路径不存在或权限问题)。 4. **资源文件缺失**:Spring配置文件`mail_content.xml`在类路径中不存在。 ### 解决方案: **1. 解决模块化jar包问题(主要崩溃点)** - **推荐方案**:升级Tomcat到至少8.5.x(支持Java 9+),因为Tomcat 7已停止维护。 - **临时规避**:降级`commons-net`到3.9.0或更早版本(不包含`module-info.class`)。 步骤: - 删除`webapps/bdcs/WEB-INF/lib/commons-net-3.10.0.jar` - 下载[commons-net-3.9.0.jar](https://repo1.maven.org/maven2/commons-net/commons-net/3.9.0/)并放入lib目录 **2. 修复log4j日志配置** - 检查log4j.properties/log4j.xml中关于`bdcs` appender的配置,确保`File`和`DatePattern`正确设置。 - 手动创建`/logs/`目录并赋予写权限(或修改配置为有效路径)。 **3. 解决Spring资源缺失问题** - 确认`mail_content.xml`存在于项目中: - 检查源码目录(如`src/main/resources/com/smics/apps/bdcs/`)是否有该文件。 - 如果不存在,需补充文件或调整配置。 - 如果文件路径不正确,修改Spring配置中引用的路径。 **4. 其他建议** - 确保所有依赖的jar包与Java 8兼容(因为Tomcat 7最高支持Java 8)。 - 检查整个项目的编译环境是否为Java 8。 ### 详细操作步骤(临时修复): ```bash # 1. 移除有问题的jar包 cd /data/EnterpriseApp/TomcatApp/tomcat-7.0-bdcs_hande/webapps/bdcs/WEB-INF/lib rm commons-net-3.10.0.jar # 2. 下载旧版本commons-net wget https://repo1.maven.org/maven2/commons-net/commons-net/3.9.0/commons-net-3.9.0.jar # 3. 创建日志目录(根据log4j配置调整) sudo mkdir -p /logs sudo chown tomcat_user:tomcat_group /logs # 替换为实际运行Tomcat的用户和组 # 4. 检查并补充缺失的mail_content.xml文件 # 从项目源码中复制到类路径对应位置(如WEB-INF/classes/com/smics/apps/bdcs/) ``` 完成以上步骤后重启Tomcat观察是否正常。 如果问题仍未解决,请提供更多环境信息(如Java版本、项目结构等)。 </think> 根据您提供的Tomcat启动日志,错误主要由三个核心问题导致: ### 一、主要错误原因分析 1. **Java版本不兼容问题** ```log SEVERE: Unable to process Jar entry [META-INF/versions/9/module-info.class] org.apache.tomcat.util.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 19 ``` - **根本原因**:Tomcat 7.0.59 无法解析Java 9+编译的模块化JAR(`module-info.class`) - **具体冲突**:`commons-net-3.10.0.jar`包含Java 9模块信息,但Tomcat 7仅支持到Java 8字节码 2. **日志配置文件错误** ```log log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /logs/bdcs.log log4j:ERROR Either File or DatePattern options are not set for appender [bdcs] ``` - 日志路径`/logs/bdcs.log`不存在 - log4j配置缺失关键参数(File/DatePattern) 3. **Spring配置文件缺失** ```log java.io.FileNotFoundException: class path resource [com/smics/apps/bdcs/mail_content.xml] cannot be opened ``` - 关键配置文件`mail_content.xml`未部署到正确位置 - Spring初始化时无法加载该资源 --- ### 二、解决方案 #### 第一步:解决Java版本冲突 1. **降级依赖库** ```bash # 删除不兼容的jar包 rm /data/EnterpriseApp/TomcatApp/tomcat-7.0-bdcs_hande/webapps/bdcs/WEB-INF/lib/commons-net-3.10.0.jar # 使用兼容版本(例如3.6) wget https://repo1.maven.org/maven2/commons-net/commons-net/3.6/commons-net-3.6.jar cp commons-net-3.6.jar /path/to/webapps/bdcs/WEB-INF/lib/ ``` 2. **或升级Tomcat**(推荐) Tomcat 9+ 原生支持Java 11+模块系统 ```bash # 下载Tomcat 9 wget https://downloads.apache.org/tomcat/tomcat-9/v9.0.xx/bin/apache-tomcat-9.0.xx.tar.gz ``` #### 第二步:修复日志配置 1. **创建日志目录** ```bash sudo mkdir -p /logs sudo chown tomcat_user:tomcat_group /logs # 替换为实际用户组 ``` 2. **检查log4j配置** 确保配置文件中包含: ```properties log4j.appender.bdcs=org.apache.log4j.DailyRollingFileAppender log4j.appender.bdcs.File=/logs/bdcs.log log4j.appender.bdcs.DatePattern='.'yyyy-MM-dd ``` #### 第三步:补充缺失配置文件 1. **定位并部署缺失文件** - 在源代码项目中查找`mail_content.xml` - 复制到部署目录: ```bash cp src/resources/mail_content.xml \ /data/EnterpriseApp/TomcatApp/tomcat-7.0-bdcs_hande/webapps/bdcs/WEB-INF/classes/com/smics/apps/bdcs/ ``` 2. **验证类路径结构** ```bash tree WEB-INF/classes/com/smics/apps/bdcs/ ├── mail_content.xml # 必须存在 └── other_config.xml ``` --- ### 三、次要问题修复 ```log INFO: TLD skipped. URI: webwork is already defined ``` - **原因**:重复的标签库定义 - **解决**:删除`webapps/bdcs/WEB-INF/lib/`下多余的`webwork-*.jar`包 --- ### 完整修复流程 ```mermaid sequenceDiagram participant User participant Server User->>Server: 启动Tomcat Server->>Tomcat: 检测Java版本兼容性 alt Java 9+ JAR存在 Tomcat-->>Server: 抛出ClassFormatException Server->>User: 降级JAR或升级Tomcat else 配置文件缺失 Tomcat-->>Server: FileNotFoundException Server->>User: 补全mail_content.xml end Server->>LogSystem: 初始化日志 alt 日志路径无效 LogSystem-->>Server: 创建/logs目录 end Server->>User: 启动成功 ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值