tomcat启动失败 Exception fixing docBase for context

最新推荐文章于 2023-03-26 00:08:22 发布
最新推荐文章于 2023-03-26 00:08:22 发布
阅读量2.1k 收藏
点赞数 1
分类专栏： Spring java学习 spring-boot 文章标签： tomcat 服务器 java
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/can96/article/details/120883259
版权
java学习 同时被 3 个专栏收录
16 篇文章 0 订阅
订阅专栏
spring-boot
6 篇文章 0 订阅
订阅专栏
Spring
3 篇文章 0 订阅
订阅专栏

  1. 问题描述：
    在服务器部署java程序时，向服务器上传了war包，程序自启动失败，手动启动失败，查看程序业务日志，发现没有启动信息，没有启动成功；随即，查看tomcat启动日志 catalina.out 发现启动报错，分析后发现是war包解压失败或war包不存在。去查看war存放目录，好家伙，发现多了一个 空的*.war ！立马把它删了，再次启动，启动成功。
    在tomcat启动准备前会到war存放目录下扫描war并进行解压。 这种多了一个空的war包，在准备阶段，解压报错，或者解压错了war包，启动自然不成功。这种情况下，会出现程序偶尔启动成功（正确解压到war包），偶尔启动失败（解压到空的war/错误的war），很是恶心

  2. 报错定位日志：
    在这里插入图片描述
    在这里插入图片描述
    在这里插入图片描述

  3. 报错信息

Oct 21, 2021 10:50:42 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /home/tomcat/war/var/web-uat/webapps/*.war
Oct 21, 2021 10:50:42 AM org.apache.tomcat.util.modeler.Registry registerComponent
SEVERE: Error registering Catalina:j2eeType=WebModule,name=//localhost/*,J2EEApplication=none,J2EEServer=none
javax.management.RuntimeOperationsException
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:413)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
        at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:742)
        at org.apache.catalina.util.LifecycleMBeanBase.register(LifecycleMBeanBase.java:158)
        at org.apache.catalina.util.LifecycleMBeanBase.initInternal(LifecycleMBeanBase.java:61)
        at org.apache.catalina.core.ContainerBase.initInternal(ContainerBase.java:1196)
        at org.apache.catalina.core.StandardContext.initInternal(StandardContext.java:6668)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1015)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:991)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020)
        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:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Repository: cannot add mbean for pattern name Catalina:j2eeType=WebModule,name=//localhost/*,J2EEApplication=none,J2EEServer=none
        ... 23 more

Oct 21, 2021 10:50:42 AM org.apache.catalina.util.LifecycleMBeanBase register
WARNING: Failed to register object [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/*]] with name [Catalina:j2eeType=WebModule,name=//localhost/*,J2EEApplication=none,J2EEServer=none] during component initialisation
javax.management.RuntimeOperationsException
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:413)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
        at org.apache.tomcat.util.modeler.Registry.registerComponent(Registry.java:742)
        at org.apache.catalina.util.LifecycleMBeanBase.register(LifecycleMBeanBase.java:158)
        at org.apache.catalina.util.LifecycleMBeanBase.initInternal(LifecycleMBeanBase.java:61)
        at org.apache.catalina.core.ContainerBase.initInternal(ContainerBase.java:1196)
        at org.apache.catalina.core.StandardContext.initInternal(StandardContext.java:6668)
        at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:135)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1015)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:991)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020)
        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:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Repository: cannot add mbean for pattern name Catalina:j2eeType=WebModule,name=//localhost/*,J2EEApplication=none,J2EEServer=none
        ... 23 more

Oct 21, 2021 10:50:42 AM org.apache.catalina.startup.ContextConfig beforeStart
SEVERE: Exception fixing docBase for context [/*]
java.util.zip.ZipException: zip file is empty
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:225)
        at java.util.zip.ZipFile.<init>(ZipFile.java:155)
        at java.util.jar.JarFile.<init>(JarFile.java:166)
        at java.util.jar.JarFile.<init>(JarFile.java:103)
        at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:93)
        at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:69)
        at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:99)
        at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122)
        at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89)
        at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:111)
        at org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:737)
        at org.apache.catalina.startup.ContextConfig.beforeStart(ContextConfig.java:862)
        at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:390)
        at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
        at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
        at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:388)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:144)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1015)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:991)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020)
        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:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Oct 21, 2021 10:50:42 AM org.apache.catalina.core.StandardContext resourcesStart
SEVERE: Error starting static Resources
java.lang.IllegalArgumentException: Invalid or unreadable WAR file : zip file is empty
        at org.apache.naming.resources.WARDirContext.setDocBase(WARDirContext.java:136)
        at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:5239)
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5430)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1015)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:991)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020)
        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:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Oct 21, 2021 10:50:42 AM org.apache.catalina.core.ContainerBase addChildInternal
SEVERE: ContainerBase.addChild: start: 
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/*]]
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:162)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1015)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:991)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020)
        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:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Error in resourceStart()
        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5431)
        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
        ... 10 more

Oct 21, 2021 10:50:42 AM org.apache.catalina.startup.HostConfig deployWAR
SEVERE: Error deploying web application archive /home/tomcat/war/var/web-uat/webapps/*.war
java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/*]]
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1019)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:991)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
        at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127)
        at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020)
        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:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Oct 21, 2021 10:50:42 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive /home/tomcat/war/var/web-uat/webapps/*.war has finished in 54 ms
Oct 21, 2021 10:50:42 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /home/tomcat/war/var/web-uat/webapps/ROOT.war
Oct 21, 2021 10:50:46 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.`
Can96
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
tomcat不能自动解压war包
xuanfengling的专栏
05-30 4万+
问题是从tomcat不能自动解压war包开始， 首先查看service.conf配置，没有问题；然后检查了jre、tomcat安装时候的配置，没有问题； 最后，查看tomcat运行日志（其实第一步就应该查看这个了）catalina.xxxx.log，看到日志记录了异常信息，也可以通过tail -f catalina.out 查看实时日志信息。上面所说的异常信息是Exception fixing
tomcat启动报错：java.util.zip.ZipException的解决方法
01-11
发现问题 早上起来报错误，Jenkins打包到tomcat服务器，死活启动不起来，一些定时任务也没跑成功。 报错如下： org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing docBase for context [/test] java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFi
出现Exception fixing docBase for context [/路径] java.util.zip.ZipException: error in opening zip file
qq_39993224的博客
06-28 944
一. 记录自己出的一次war包打包后放在tomcat中无法解压问题，原因是由于里面某个静态文件或图片无法解压，出现该问题后可以在打包后先自己用win或者360先手动解压一次看是否有问题。
cp201x资源启动程序
05-20
Install driver for USB-UART bridge converter on Linux Ubuntu12.04 Ubuntu下USB转串口芯片驱动程序安装，支持cp210x,pl2303等 Reference: Fixing the cp210x open - Unable to enable UART Error When you plugin your USB-UART converter, and run "> ls /dev/tty*", if you don't see the /dev/ttyUSB0 (or similar), your Linux does not detect your USB-UART device. We need to install the driver for your device. Here we use Ubuntu12.04, and Updated the source to 3.2.0 version. If there is difference about version Number from your OS platform, please try to modify it into yours. 1.Download the Linux Source Code Open a terminal and execute the following commands. Note that your version of Linux may differ slightly -- adjust accordingly. $ cd ~ $ sudo apt-get install build-essential linux-source $ cp /usr/src/linux-source-3.2.0.tar.bz2 . $ bunzip2 linux-source-3.2.0.tar.bz2 $ tar xf linux-source-3.2.0.tar $ cd ~/linux-source-3.2.0 2.Recompile and Reinstall the cp210x Driver From within a terminal, execute: $ cd ~/linux-source-3.2.0 $ make oldconfig $ make prepare $ make scripts $ cp /usr/src/linux-headers-3.2.0-34-generic-pae/Module.symvers . Here, I have the "3.2.0-29" version also, I launched the command above, but not the below: "cp /usr/src/linux-headers-3.2.0-29-generic-pae/Module.symvers ." Recompile and Reinstall the cp210x Driver Here, We can actually install many kinds of USB-UART converter drivers. We take cp210x as the example. From within a terminal, execute: $ make M=drivers/usb/serial $ sudo mv /lib/modules/$(uname -r)/kernel/drivers/usb/serial/cp210x.ko /lib/modules/$(uname -r)/kernel/drivers/usb/serial/cp210x.ko.old $ sudo cp drivers/usb/serial/cp210x.ko /lib/modules/$(uname -r)/kernel/drivers/usb/serial/ $ sudo modprobe -r cp210x $ sudo modprobe cp210x Reboot Linux system. Run Terminal: $ ls /dev/tty* The we can see the device is detected by Linux Host OS: 【技术】Ubuntu下USB转串口芯片驱动程序安装cp210x,pl2303 Reference: http://pharos.ece.utexas.edu/wiki/index.php/Fixing_the_cp210x_open_-_Unable_to_enable_UART_Error_-_04/17/2011 Then, We can configure the minicom to communicate with our target board. ====================================================== Here is an example of configure the parameters of minicom for TLL6527M PAL board: I just copied it here hardly without any font editing. Sorry about that. Serial Communications from Host-PC to TLL6527M Target Hardware The TLL System Design Environment (SDE) running on the host PC comes pre-configured with the required settings for serial-UART communications between the host PC and the TLL6527M base module. Generally, for use with TLL6527M the settings need not to be changed (Note: From the SDE OS version 0.3.2, the serial terminal program Minicom is set to open /dev/ttyUSB0 with the needed configuration as mentioned above.). To start serial communication from host to the TLL6527M, open the serial communication terminal program Minicom. Just open a terminal window on your Linux SDE running on the host PC and type the command "minicom" at the command prompt on your host PC terminal console. The TLL6527M on power-up is set by default to the following serial-UART communication settings: Bits per second = 115200 Data bits = 8 Parity = None Stop Bits = 1 Flow control = None Make sure that the TLL6527M's USB-UART port has been mapped to a ttyUSBx device node in the /dev folder on the host PC SDE. See following example: 【技术】Ubuntu下USB转串口芯片驱动程序安装cp210x,pl2303 Now make sure that this "ttyUSBx" is set as the destination port, baud rate is 115200, and 8N1 mode for minicom, by running the command 'minicom -s'. Note that running the "minicom -s" command as a normal user will only apply the settings for the current session. In order to make the settings permanent, these commands need to be run with root privileges.See example below: 【技术】Ubuntu下USB转串口芯片驱动程序安装cp210x,pl2303 The following window will appear on your host PC terminal window: 【技术】Ubuntu下USB转串口芯片驱动程序安装cp210x,pl2303 Go to ‘Serial port setup’, following screen will appear, make sure that serial device is set to ‘/dev/ttyUSB0’ and bps/par/bits is set to 115200 8N1: 【技术】Ubuntu下USB转串口芯片驱动程序安装cp210x,pl2303 Now go back to the main menu and choose ‘save setup as dfl’. This will save the configuration settings and from next time onwards user can directly run ‘minicom’ command without the option ‘–s’ and it will load settings from the saved file. 【技术】Ubuntu下USB转串口芯片驱动程序安装cp210x,pl2303 RESET the target by using the SDE's TLL6527M reset utility or by pressing the RESET button on the target. Following messages will be displayed on the terminal. By default, U-Boot is setup to automatically start booting the OS after waiting for a few seconds for the user to interrupt the automatic launch by pressing any key. So to stop U-Boot from loading uClinux and provide U-Boot command prompt, just hit any key. (This is assuming TLL6527M is flashed with u-boot and uClinux. TLL6527Ms are pre-flashed with firmware before shipping).
论文翻译Automated Fixing of Programs with Contracts
05-13
论文翻译Automated Fixing of Programs with Contracts
【tomcat】org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application
Axi.ZYTao
09-22 9597
使用tomcat发布应用程序产生以下报错， org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive [/home/sj/tools/tomcat-3/webapps/estamp.war] java.lang.IllegalStateException: Error starting child 原因是tomcat中conf下配置文件设置不对，修改即可，具体详见原文： https://b
Exception fixing docBase for context [/config]
靠脑袋是真滴记不住啊！！！！！！！！
04-25 5703
报错信息： [2019-04-25 05:39:30,478] Artifact config-web:war: Artifact is being deployed, please wait... 25-Apr-2019 17:39:30.533 严重 [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.startup.ContextCon...
Tomcat idea启动不成功，报错
qq_27261375的博客
06-04 1188
Tomcat idea启动不成功，报错 tomcat启动时不成功，环境变量也都配了。JAVA_HOME,CATALINA_HOME放到了Path里了。但是还是报错，提示以下类型的错误： 29-Oct-2018 13:25:42.084 严重 [RMI TCP Connection(2)-127.0.0.1] org.apache.catalina.startup.ContextConfig.bef...
Tomcat启动springboot项目war包报错：启动子级时出错
HPGANG的博客
03-23 4617
报错信息 java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:225) at java.util.zip.ZipFile.<init>(ZipFile.java:155) ... 严重 [Catalina-utility-2] org.apache.c
tomcat exception fixing docbase for context
迎风飞翔的专栏
03-26 2049
本机tomcat6 服务器tomcat8 将war包拷贝到服务器后，报错tomcat exception fixing docbase for context。 大意就是war包解压不了。 暂时方案：右键war包，以rar方式解压。之后项目能够正常启动。 先标记一下，回头再仔细研究 ...
java.lang.IllegalStateException: Error starting child
Echouuu的博客
12-21 5165
项目打包到服务器，启动tomcat报错 问题： org.apache.catalina.startup.HostConfig.deployWAR 部署 Web 应用程序 archive [路径] 时出错 java.lang.IllegalStateException: Error starting child at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:720) at org.apach
Ebooks For Dummies Collection
11-05
A+ Certification 2nd Ed For Dummies.pdf A+ Certification For Dummies 3rd Ed.chm Access 2007 AIO Desk Reference For Dummies.pdf Access 2007 Vba Programming For Dummies Feb 2007.pdf Access Forms & ...
writing running and fixing codes.one
11-17
writing running and fixing codes.one
已解决org.apache.catalina.startup.HostConfig.deployDirector
热门推荐
03-26 6万+
如果在部署过程中出现问题，可能是由于以下几个原因导致的： 目录结构错误：确保部署目录的结构正确，应包含WEB-INF目录和对应的配置文件（如web.xml）。 权限问题：检查Tomcat进程对部署目录的访问权限是否足够。确保Tomcat用户或组具有读取和执行目录的权限。 配置错误：检查Tomcat的配置文件（如server.xml）中是否正确配置了Host元素和Context元素。确保部署目录在配置文件中被正确引用。 内存不足：如果服务器的内存资源有限，可能会导致无法成功部署大型应用程序。可以尝试调
向centos上传war包后重启tomcat报错ZipException: error in opening zip file
Dragonzh的博客
08-14 384
org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing docBase for context [/demo] java.util.zip.ZipException: error in opening zip file 这个问题的原因很多种，其中一种是我自己遇到的，分享出来，就是不要在tomcat正在运行的时候...
Tomcat部署web项目
timelikeswind的博客
03-28 207
1.将项目打包为war包 右键项目->Export WARfile，将其置于tomcat安装路径的webapps目录下，war包会自动解压，点击startup.bat开启tomcat服务器后即可访问。 2.编辑conf目录下server.xml，设置Tomcat默认访问项目 docBase的值可为默认访问项目在webapps目录下时，相对于webapps的相对路径，也可为项目的...
Exception fixing docBase for context
diandanpao7184的博客
06-13 286
原因在给tomcat的war包，传输过程中出了问题，或者不是2进制传输，重新用2进制传送到linux里的tomcat webapps 目录中 就解决了。 转载于:https://www.cnblogs.com/yousen/p/4572903.html...
热部署
Can96的博客
04-05 3756
热部署，是指在不关闭或重启服务的情况下，更新Java类文件或配置文件，实现修改内容生效；通过热部署，可提高开发效率，节省程序打包重启的时间，同时，可实现生产环境中需要不停机或重启的服务的升级。 1.热部署实现原理 对于Java应用程序，热部署就是程序运行时实现Java类文件更新。要实现程序在运行中进行程序更新，就需要让java虚拟机在检测到Java类文件发生变化时，把原来的类文件卸载，并重新加载新的类文件。总的来说，热部署的本质是让jvm重新加载新的class文件。 ...
Error while waiting for device: Retry after fixing problem by hand
最新发布
05-31
这个错误通常意味着Android Studio无法连接到您的设备或模拟器。您可以尝试以下步骤来解决这个问题： 1. 确保您的设备已连接到计算机，并且已经启用了USB调试模式。您可以在设备的“开发者选项”中找到这个选项。 2. 重新启动Android Studio，并尝试再次连接设备。 3. 如果您使用的是模拟器，请确保它已经启动，并且正在运行一个Android映像。 4. 检查您的设备或模拟器是否已经在Android Studio的设备列表中出现。您可以在Android Studio的“工具栏”中找到“设备”选项。 5. 如果您使用的是模拟器，请尝试关闭它，并重新启动一个新的模拟器。有时候模拟器会出现问题，导致无法连接。 如果上述步骤都没有解决问题，您可以尝试重新安装Android Studio，或者在Android Studio的“设置”中检查ADB设置是否正确。如果仍然无法解决问题，请提供更多的详细信息，我会尽力帮助您。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值