SpringBoot 启动报 Stopping service [Tomcat]

可能出现这个的原因有很多种,别人的为什么会 出现这个原因我暂时知道,我只列举出我出现这个问题的原因

#原因

因为我导了 一个POI 3.6的工具包  SpringBoot 不兼容,所以就是报错了, 然后我换成了4.0.0的工具包就一切都正常了

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
============================================<br><br>Out of the box, Tomcat 5.5 requires the Java 2 Standard Edition Runtime<br>Environment (JRE) version 5.0 or later. However, you can also run Tomcat<br>5.5 on earlier versions of the JRE, as detailed below.<br><br>=============================<br>Running With JRE 5.0 Or Later<br>=============================<br><br>(1) Download and Install the J2SE Runtime Environment (JRE)<br><br>(1.1) Download the Java 2 Standard Edition Runtime Environment (JRE),<br> release version 5.0 or later, from http://java.sun.com/j2se.<br><br>(1.2) Install the JRE according to the instructions included with the<br> release.<br><br>(1.3) Set an environment variable named JAVA_HOME to the pathname of<br> the directory into which you installed the JRE, e.g. c:\j2sdk5.0<br> or /usr/local/java/j2sdk5.0.<br><br><br>(2) Download and Install the Tomcat Binary Distribution<br><br>NOTE: As an alternative to downloading a binary distribution, you can create<br>your own from the Tomcat source repository, as described in "BUILDING.txt".<br>If you do this, the value to use for "${catalina.home}" will be the "dist"<br>subdirectory of your source distribution.<br><br>(2.1) Download a binary distribution of Tomcat from:<br><br> http://tomcat.apache.org<br><br>(2.2) Unpack the binary distribution into a convenient location so that the<br> distribution resides in its own directory (conventionally named<br> "apache-tomcat-[version]"). For the purposes of the remainder of this document,<br> the symbolic name "$CATALINA_HOME" is used to refer to the full<br> pathname of the release directory.<br><br><br>(3) Start Up Tomcat<br><br>(3.1) Tomcat can be started by executing the following commands:<br><br> $CATALINA_HOME\bin\startup.bat (Windows)<br><br> $CATALINA_HOME/bin/startup.sh (Unix)<br><br>(3.2) After startup, the default web applications included with Tomcat will be<br> available by visiting:<br><br> http://localhost:8080/<br><br>(3.3) Further information about configuring and running Tomcat can be found in<br> the documentation included here, as well as on the Tomcat web site:<br><br> http://tomcat.apache.org<br><br><br>(4) Shut Down Tomcat<br><br>(4.1) Tomcat can be shut down by executing the following command:<br><br> $CATALINA_HOME\bin\shutdown (Windows)<br><br> $CATALINA_HOME/bin/shutdown.sh (Unix)<br><br><br><br>====================================<br>Running Tomcat With J2SE Version 1.4<br>====================================<br><br>(1) Obtain the compat package:<br><br>(1.1) Download the compat package from the binary download site:<br> http://tomcat.apache.org<br><br> * Or build this package yourself from the source code: see <br> "BUILDING.txt" in this directory.<br><br>(2) Unzip the package in $CATALINA_HOME. It will place the XML<br> parser APIs and Xerces implementation in the common/endorsed<br> directory, and the JMX API jar (jmx.jar from Sun) in the bin<br> directory.<br><br>(3) Follow the same directions for starting and stopping the<br> server as if you were using J2SE 5.0.<br><br><br>==================================================<br>Advanced Configuration - Multiple Tomcat Instances<br>==================================================<br><br>In many circumstances, it is desirable to have a single copy of a Tomcat<br>binary distribution shared among multiple users on the same server. To make<br>this possible, you can pass a "-Dcatalina.base=$CATALINA_BASE" argument when<br>executing the startup command (see (2)). In this<br>"-Dcatalina.base=$CATALINA_BASE" argument, replace $CATALINA_BASE with the<br>directory that contains the files for your 'personal' Tomcat instance.<br><br>When you use this "-Dcatalina.base=$CATALINA_BASE" argument, Tomcat will<br>calculate all relative references for files in the following directories based<br>on the value of $CATALINA_BASE instead of $CATALINA_HOME:<br><br>* conf - Server configuration files (including server.xml)<br><br>* logs - Log and output files<br><br>* shared - For classes and resources that must be shared across all web<br> applications<br><br>* webapps - Automatically loaded web applications<br><br>* work - Temporary working directories for web applications<br><br>* temp - Directory used by the JVM for temporary files (java.io.tmpdir)<br><br>If you do not pass the "-Dcatalina.base=$CATALINA_BASE" argument to the<br>startup command, $CATALINA_BASE will default to the same value as $CATALINA_HOME,<br> which means that the same directory is used for all relative path resolutions.<br><br>The administration and manager web applications, which are defined in the<br>$CATALINA_BASE/conf/Catalina/localhost/admin.xml<br>and <br>$CATALINA_BASE/conf/Catalina/localhost/manager.xml files, will<br>not run in that configuration, unless either:<br>- The path specified in the docBase attribute of the Context element is made<br> absolute, and replaced respectively by $CATALINA_HOME/server/webapps/admin<br> and $CATALINA_HOME/server/webapps/manager<br>- Both web applications are copied or moved to $CATALINA_BASE, <br> and the path specified in the docBase attribute of the Context<br> element is modified appropriately.<br>- Both web applications are disabled by removing<br> $CATALINA_BASE/conf/Catalina/localhost/admin.xml<br> and<br> $CATALINA_BASE/conf/Catalina/localhost/manager.xml.<br><br><br>================<br>Troubleshooting<br>================<br><br>There are only really 3 things likely to go wrong during the stand-alone<br>Tomcat install:<br><br>(1) The most common hiccup is when another web server (or any process for that<br> matter) has laid claim to port 8080. This is the default HTTP port that<br> Tomcat attempts to bind to at startup. To change this, open the file:<br><br> $CATALINA_HOME/conf/server.xml<br><br> and search for '8080'. Change it to a port that isn't in use, and is<br> greater than 1024, as ports less than or equal to 1024 require superuser<br> access to bind under UNIX.<br><br> Restart Tomcat and you're in business. Be sure that you replace the "8080"<br> in the URL you're using to access Tomcat. For example, if you change the<br> port to 1977, you would request the URL http://localhost:1977/ in your browser.<br><br>(2) An "out of environment space" error when running the batch files in<br> Windows 95, 98, or ME operating systems.<br><br> Right-click on the STARTUP.BAT and SHUTDOWN.BAT files. Click on<br> "Properties", then on the "Memory" tab. For the "Initial environment" field,<br> enter in something like 4096.<br><br> After you click apply, Windows will create shortcuts which you can use<br> to start and stop the container.<br><br>(3) The 'localhost' machine isn't found. This could happen if you're behind a<br> proxy. If that's the case, make sure the proxy configuration for your<br> browser knows that you shouldn't be going through the proxy to access the<br> "localhost".<br><br> In Netscape, this is under Edit/Preferences -> Advanced/Proxies, and in<br> Internet Explorer, Tools -> Internet Options -> Connections -> LAN Settings.<br>
1. Getting Started with Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Installing Tomcat 1 Starting, Stopping, and Restarting Tomcat 17 Automatic Startup 29 Testing Your Tomcat Installation 34 Where Did Tomcat Come From? 35 2. Configuring Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 A Word About Using the Apache Web Server 38 Relocating the Web Applications Directory 39 Changing the Port Number from 8080 42 Java VM Configuration 51 Changing the JSP Compiler 54 Managing Realms, Roles, and Users 55 Controlling Sessions 70 Accessing JNDI and JDBC Resources 75 Servlet Auto-Reloading 78 Customized User Directories 78 Tomcat Example Applications 80 Common Gateway Interface (CGI) 80 The Tomcat Admin Webapp 82 3. Deploying Servlet and JSP Web Applications in Tomcat . . . . . . . . . . . . . . . . . 86 Layout of a Web Application 93 Deploying an Unpacked Webapp Directory 95 Deploying a WAR File 100 Hot Deployment 106 Working with WAR Files 107 The Manager Webapp 108 Automation with Apache Ant 111 Symbolic Links 124 4. Tomcat Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Measuring Web Server Performance 127 External Tuning 153 Internal Tuning 156 Capacity Planning 164 Additional Resources 167 5. Integration with the Apache Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 The Pros and Cons of Integration 170 Installing Apache Apache Integration with Tomcat 177 Tomcat Serving HTTP over the APR Connector 194 6. Tomcat Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 Securing the System 202 Multiple Server Security Models 204 Using the SecurityManager 205 Granting File Permissions 208 Setting Up a Tomcat chroot Jail 213 Filtering Bad User Input 224 Securing Tomcat with SSL 241 7. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 server.xml 260 web.xml 316 tomcat-users.xml 333 catalina.policy 333 catalina.properties 334 context.xml 335 8. Debugging and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Reading Logfiles 336 Hunting for Errors 337 URLs and the HTTP Conversation 337 Debugging with RequestDumperValve 342 When Tomcat Won’t Shut Down 343 9. Building Tomcat from Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Installing Apache Ant 348 Obtaining the Source 349 Downloading Support Libraries 351 Building Tomcat 352 10. Tomcat Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Clustering Terms 355 The Communication Sequence of an HTTP Request 356 Distributed Java Servlet Containers 366 Tomcat 6 Clustering Implementation 370 JDBC Request Distribution and Failover 388 Additional Resources 389 11. Final Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Supplemental Resources 391 Community 395 A. Installing Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 B. jbchroot.c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 C. BadInputValve.java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 D. BadInputFilter.java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426 E. RPM Package Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
基于C++&OPENCV 的全景图像拼接 C++是一种广泛使用的编程语言,它是由Bjarne Stroustrup于1979年在新泽西州美利山贝尔实验室开始设计开发的。C++是C语言的扩展,旨在提供更强大的编程能力,包括面向对象编程和泛型编程的支持。C++支持数据封装、继承和多态等面向对象编程的特性和泛型编程的模板,以及丰富的标准库,提供了大量的数据结构和算法,极大地提高了开发效率。12 C++是一种静态类型的、编译式的、通用的、大小写敏感的编程语言,它综合了高级语言和低级语言的特点。C++的语法与C语言非常相似,但增加了许多面向对象编程的特性,如类、对象、封装、继承和多态等。这使得C++既保持了C语言的低级特性,如直接访问硬件的能力,又提供了高级语言的特性,如数据封装和代码重用。13 C++的应用领域非常广泛,包括但不限于教育、系统开发、游戏开发、嵌入式系统、工业和商业应用、科研和高性能计算等领域。在教育领域,C++因其结构化和面向对象的特性,常被选为计算机科学和工程专业的入门编程语言。在系统开发领域,C++因其高效性和灵活性,经常被作为开发语言。游戏开发领域中,C++由于其高效性和广泛应用,在开发高性能游戏和游戏引擎中扮演着重要角色。在嵌入式系统领域,C++的高效和灵活性使其成为理想选择。此外,C++还广泛应用于桌面应用、Web浏览器、操作系统、编译器、媒体应用程序、数据库引擎、医疗工程和机器人等领域。16 学习C++的关键是理解其核心概念和编程风格,而不是过于深入技术细节。C++支持多种编程风格,每种风格都能有效地保证运行时间效率和空间效率。因此,无论是初学者还是经验丰富的程序员,都可以通过C++来设计和实现新系统或维护旧系统。3

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

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

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值