tomcat错误

作者: 平_方 | 来源:发表于2018-11-19 16:50 被阅读0次

TomCat中部署Servlet解析
tomcat错误
Tomcat配置访问后台弱口令拿shell复现
tomcat7启动报错org.apache.catalina.L
#01 dpkg使用apt安装 Tomcat 7失败
Mac 下配置 Intellij IDEA ＋ Tomcat 出
解决 jar not loaded. See Servlet S
解决Intellij idea Error:java错误
tomcat安装遇到的问题
Property maxActive is not used i

1.java.io.IOException: Can not lock the registry cache file

(1)报错内容

DubboSaveRegistryCache-thread-1 | WARN  | com.alibaba.dubbo.common.logger.log4j.Log4jLogger:Log4jLogger.java(78) |  [DUBBO] Failed to save registry store file, cause: Can not lock the registry cache file /root/.dubbo/dubbo-registry-10.141.4.168.cache, ignore and retry later, maybe multi java process use the file, please config: dubbo.registry.file=xxx.properties, dubbo version: 2.8.3, current host: 127.0.0.1
java.io.IOException: Can not lock the registry cache file /root/.dubbo/dubbo-registry-10.141.4.168.cache, ignore and retry later, maybe multi java process use the file, please config: dubbo.registry.file=xxx.properties
        at com.alibaba.dubbo.registry.support.AbstractRegistry.doSaveProperties(AbstractRegistry.java:193) ~[dubbo-2.8.3.jar:2.8.3]
        at com.alibaba.dubbo.registry.support.AbstractRegistry$SaveProperties.run(AbstractRegistry.java:150) [dubbo-2.8.3.jar:2.8.3]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_60]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_60]
        at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]

(2)解决办法

报错的大概意思是 Dubbo在保存服务列表时失败，Can not lock the registry cache file /root/.dubbo/dubbo-registry-10.141.4.168.cache，拿不到文件锁，无法保存服务列表。

错误原因

出现这个的原因是服务向ZK注册的同时，会缓存Consumer的列表，写入user.home/.dubbo/dubbo-registry-” + url.getHost() + “.cache 这个文件，当在同一个机器上启动多个Provider的时候，就会出现文件锁争用的问题，报上面这个错误。

解决办法

既然是由于竞争文件锁导致的，那么让服务模块各自缓存自己的cache文件就可以避免这样的问题了。
具体做法是：在启动脚本里添加如下

JAVA_OPTS="$JAVA_OPTS -Ddubbo.registry.file=$CATALINA_HOME/dubbo/dubbo-registry-ip.cache"

这样就会在$CATALINA_HOME目录下生成dubbo这个目录，cache文件就缓存在这个里边了。

2.java.net.BindException: 地址已在使用

(1)报错内容

web.context.ContextLoader - Context initialization failed
com.alibaba.dubbo.rpc.RpcException: Fail to start server(url: dubbo://192.168.1.121:18191/com.tongbanjie.security.facade.api.AuthCodeValidationFacade?
anyhost=true&application=security&channel.readonly.sent=true&codec=dubbo&default.retries=0&default.timeout=30000&dubbo=2.5.3&heartbeat=60000&interface
=com.tongbanjie.security.facade.api.AuthCodeValidationFacade&methods=verifyAuthCode&pid=16819&revision=1.0-SNAPSHOT&side=provider&timestamp=1463571401
299&version=2.0) Failed to bind NettyServer on /192.168.1.121:18191, cause: Failed to bind to: /0.0.0.0:18191
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:289)
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.openServer(DubboProtocol.java:266)
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.export(DubboProtocol.java:253)
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:55)
        at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:56)
        at com.alibaba.dubbo.rpc.Protocol$Adpative.export(Protocol$Adpative.java)
        at com.alibaba.dubbo.registry.integration.RegistryProtocol.doLocalExport(RegistryProtocol.java:153)
        at com.alibaba.dubbo.registry.integration.RegistryProtocol.export(RegistryProtocol.java:107)
        at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper.export(ProtocolFilterWrapper.java:53)
        at com.alibaba.dubbo.rpc.protocol.ProtocolListenerWrapper.export(ProtocolListenerWrapper.java:54)
        at com.alibaba.dubbo.rpc.Protocol$Adpative.export(Protocol$Adpative.java)
        at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:485)
        at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:281)
        at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:242)
        at com.alibaba.dubbo.config.ServiceConfig.export(ServiceConfig.java:143)
        at com.alibaba.dubbo.config.spring.ServiceBean.onApplicationEvent(ServiceBean.java:109)
        at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)
        at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)
        at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:948)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
        at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:410)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:306)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4210)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4709)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:583)
        at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079)
        at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1002)
        at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506)
        at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
        at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:822)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
        at org.apache.catalina.core.StandardService.start(StandardService.java:525)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
Caused by: com.alibaba.dubbo.remoting.RemotingException: Failed to bind NettyServer on /192.168.1.121:18191, cause: Failed to bind to: /0.0.0.0:18191
        at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:72)
        at com.alibaba.dubbo.remoting.transport.netty.NettyServer.<init>(NettyServer.java:63)
        at com.alibaba.dubbo.remoting.transport.netty.NettyTransporter.bind(NettyTransporter.java:33)
        at com.alibaba.dubbo.remoting.Transporter$Adpative.bind(Transporter$Adpative.java)
        at com.alibaba.dubbo.remoting.Transporters.bind(Transporters.java:48)
        at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchanger.bind(HeaderExchanger.java:41)
        at com.alibaba.dubbo.remoting.exchange.Exchangers.bind(Exchangers.java:63)
        at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol.createServer(DubboProtocol.java:287)
        ... 50 more
Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to: /0.0.0.0:18191
        at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:303)
        at com.alibaba.dubbo.remoting.transport.netty.NettyServer.doOpen(NettyServer.java:94)
        at com.alibaba.dubbo.remoting.transport.AbstractServer.<init>(AbstractServer.java:67)
        ... 57 more
Caused by: java.net.BindException: 地址已在使用
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Net.java:344)
        at sun.nio.ch.Net.bind(Net.java:336)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:148)
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:100)
        at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:74)
        at org.jboss.netty.channel.Channels.bind(Channels.java:468)
        at org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:192)
        at org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:348)
        at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:176)
        at org.jboss.netty.channel.socket.nio.NioServerSocketChannel.<init>(NioServerSocketChannel.java:85)
        at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:142)
        at org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:90)
        at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:282)
        ... 59 more

(2)解决办法

应该是dubbo端口占用导致spring启动失败，从而此处报错
查看info日志

0518 21:00:04 679 INFO ] [main] web.context.ContextLoader - Root WebApplicationContext: initialization started
[0518 21:00:04 868 INFO ] [main] context.support.XmlWebApplicationContext - Refreshing Root WebApplicationContext: startup date [Wed May 18 21:00:04 C
ST 2016]; root of context hierarchy
[0518 21:00:05 021 INFO ] [main] factory.xml.XmlBeanDefinitionReader - Loading XML bean definitions from class path resource [META-INF/spring/security
-context.xml]
.........
[0518 21:00:12 567 INFO ] [main] web.servlet.DispatcherServlet - FrameworkServlet 'springmvc': initialization completed in 1209 ms
[0518 21:00:15 330 INFO ] [main] web.context.ContextLoader - Root WebApplicationContext: initialization started
[0518 21:00:15 434 INFO ] [main] context.support.XmlWebApplicationContext - Refreshing Root WebApplicationContext: startup date [Wed May 18 21:00:15 C
ST 2016]; root of context hierarchy

Root WebApplicationContext 启动了两次，第二次报错了，容器关闭。启动两次，这就可以理解为什么dubbo端口怎么改都会被占用了
tomcat配置，在server.xml:
正常的：

<Host name="localhost" debug="0" appBase="/data/www/ROOT/xxx"
      unpackWARs="true" autoDeploy="false" deployOnStartup="false"
      xmlValidation="false" xmlNamespaceAware="false" >
  <Context path="" docBase="xxxxx" debug="0" reloadable="false"/>
</Host>

不正常的：

<Host name="localhost" debug="0" appBase="/data/www/ROOT/xxx"
      unpackWARs="true" autoDeploy="true" deployOnStartup="true"
      xmlValidation="false" xmlNamespaceAware="false" >
  <Context path="" docBase="xxxxx" debug="0" reloadable="false"/>
</Host>

改了，还真就正常了，spring context只启动一次，dubbo端口也不再被占用。
那么下边来查查tomcat server.xml中，autoDeploy和deployOnStartup的含义
autoDeploy:如果此项设为true,表示Tomcat服务处于运行状态时,能够监测appBase下的文件,如果有新有web应用加入进来,会自运发布这个WEB应用
unpackWARs:如果此项设置为true,表示把WEB应用的WAR文件先展开为开放目录结构后再运行.如果设为false将直接运行为WAR文件
deployOnStartup:如果此项设为true,表示Tomcat服务器启动时会自动发布appBase目录下所有的Web应用.如果Web应用中的server.xml没有相应的<Context>元素,将采用Tomcat默认的Context
显式设置autoDeploy为False。避免了在server.xml中增加Context配置时两次部署相同的Web应用程序。

TomCat中部署Servlet解析
错误实例： tomcat启动错误： 1.Error running tomcat: Address localho...
tomcat错误
1.java.io.IOException: Can not lock the registry cache fi...
Tomcat配置访问后台弱口令拿shell复现
复现环境： apache-tomcat-8.5.41 如果登录tomcat manager APP 401错误，如...
tomcat7启动报错org.apache.catalina.L
错误日志如下：又看到错误信息 Tomcat有三种运行模式：bio、nio、apr，不同模式下Tomcat的运行效...
#01 dpkg使用apt安装 Tomcat 7失败
问题：安装Tomcat7时，出现以下错误：当我尝试删除Tomcat7时，我得到了这个错误：如何修复这里问题以...
Mac 下配置 Intellij IDEA ＋ Tomcat 出
今天构建 web 项目时启动 tomcat 服务，出现如上错误： Error running Tomcat 8.0...
解决 jar not loaded. See Servlet S
项目打成的war包部署到tomcat后，启动报如下错误： validateJarFile(/home/tomcat...
解决Intellij idea Error:java错误
解决Intellij idea Error:java: 项目编译的各种错误错误原因 Tomcat、IDEA、项...
tomcat安装遇到的问题
tomcat安装问题说明 1、tomcat8版本启动，如报以下错误：解决方法：在tomcat的安装目录下找到\...
Property maxActive is not used i
使用tomcat 配置db数据源时，出现这个错误。 org.apache.tomcat.dbcp.dbcp2.Ba...