怎么使用tomcat直接运行一个maven项目?

我在一台电脑上,直接把一个maven项目打包了,然后把打包好的war包classes那些拷到另一台电脑,直接放到tomcat的webapp目录下,tomcat能正常启动但就是不能打开这个项目,会一直加载,没报404,请问我是不是漏了什么步骤?
项目在原来的电脑上运行是没问题的,我按网上的方法mvn package打包的项目

2个回答

那需要看看你打的包有没有问题了,此外看看 Tomcat 的catalina.out 日志看看有没有启动异常。

wojiushiwo945you
毕小宝 回复riderpunch: JAVA_OPTS="$JAVA_OPTS -server -Xms512m -Xmx2048m -XX:PermSize=512M -XX:MaxPermSize=512m -Djava.protocol.handler.pkgs=org.apache.catalina.webresources"
8 个月之前 回复
wojiushiwo945you
毕小宝 回复riderpunch: 那需要修改下 Tomcat 启动文件中的 catalina.sh 文件中 JVM 的配置部分,调大 JVM 初始堆空间。
8 个月之前 回复
qq_42325220
riderpunch 会有内存溢出异常.新电脑就配置环境其他什么修改都没有
8 个月之前 回复

只需要把war放在webapp下就可以了

li7763416
渣渣it男 回复riderpunch: war包里面有class文件
8 个月之前 回复
qq_42325220
riderpunch war包里面应该只有jsp的相关文件没有java文件吧,还是我打包的时候有问题?
8 个月之前 回复
Csdn user default icon
上传中...
上传图片
插入图片
抄袭、复制答案,以达到刷声望分或其他目的的行为,在CSDN问答是严格禁止的,一经发现立刻封号。是时候展现真正的技术了!
其他相关推荐
Linux tomcat发布项目出错
java maven项目,在本机eclipse上运行没有问题,数据库直接连的服务器。 在服务运行时一直出错。 根据网上的方法,用run as maven build生成过war,直接用export生成war试过,最后 用本机eclipse运行的tomcat里的项目直接拷贝出来拿过去发布还是出错,错误要么说 没有初始化,要么就是数据库连接错误。本机windows10、macos/BSD生成都试过。 用macos的eclipse跑没问题,把eclipse的tomcat里的项目直接拉出来放到单独的tomcat 运行还是出错,错误跟服务器一致。错误如下: ![图片说明](https://img-ask.csdn.net/upload/201712/03/1512276500_806508.png) 求大神解释,是不是tomcat少什么配置?
myeclipse 在tomcat上部署springboot项目异常
这两天接手公司其他人的一个springboot项目,这也是我第一次做springboot项目,所以现在自己的myeclipse上跑了一下,当时的tomcat6上部署,然后不报错但是也没成功,然后就更换了tomcat7,但是报异常 org.apache.catalina.deploy.WebXml addServlet 这个我根据百度到的已经在conf/context.xml里面配置了可是没有效果 给我项目的人说可以直接部署在tomcat上面,然后我是像maven项目一样正常部署在tomcat上,然后其他的maven项目可以运行,这个springboot项目就不行,求大佬解惑,springboot项目如何跑不起来?要怎么解决 ![图片说明](https://img-ask.csdn.net/upload/201808/26/1535275569_380123.jpg) ![图片说明](https://img-ask.csdn.net/upload/201808/26/1535275586_259564.jpg)
maven依赖找不到被依赖项目依赖的包
我有两个项目A和B,A项目中有代码和dependency依赖的包,B项目通过dependency依赖A项目。 现在问题是:A项目通过install打的jar包是正常的,直接放在B项目的WEB-INF/lib下(不用dependency依赖),B是可以运行的。 但是,如果B用dependency依赖A,我在tomcat目录下看到B项目的WEB-INF/lib下生成的A项目的jar包只有项目代码的二进制文件,而没有pom用dependency依赖的包的编译文件,就导致B项目无法启动,请问这个该怎么解决,设置过Deployment Assembly了
springBoot放到tomcat里运行访问不到controller
目录结构如图所示 ![图片说明](https://img-ask.csdn.net/upload/201901/31/1548918842_972424.jpg) controller ![图片说明](https://img-ask.csdn.net/upload/201901/31/1548918915_470976.jpg) 启动tomcat正常 ![图片说明](https://img-ask.csdn.net/upload/201901/31/1548918981_937865.jpg) 访问controller ![图片说明](https://img-ask.csdn.net/upload/201901/31/1548919022_921895.jpg) 这是怎么回事呢,如果我直接用springBoot的内置tomcat是可以正常访问controller的,求大神搭救 不是带不带项目名的原因,都访问不了的。之前一直用的maven,嫌配置文件太麻烦,改用了springBoot
springboot项目文件上传路径和读取路径不一致
``` //根目录路径 String rootPath = request.getRealPath("/") + "attached/"; //根目录URL String rootUrl = request.getContextPath() + "/attached/"; ``` 代码如上,框架用的是springboot,内置tomcat,项目管理的maven 我在文件上传和下载类用的获取路径的方法都是上面的代码,但是我在运行的时候,发现文件上传目录是在C:\Users\Administrator\AppData\Local\Temp\tomcat-docbase.1083509166823006581.8888\attached/下面 url是在/attached/下面 下载目录是在C:\Users\Administrator\AppData\Local\Temp\tomcat-docbase.1083509166823006581.8888\attached/下面 url是在/attached/下面,看起来是一样的。 但是我加载的图片就是损坏的,路径找不到,如果我直接从项目下面找就能找到。我感觉是url的额相对路径有问题。这个url的相对路径到底是从哪里开始的?
【新手】intellij idea 构建spring mvc
新手一个,没有使用maven构建spring,出了不少问题求大神帮助, 我直接创建一个spring mvc项目后,直接运行,没有加任何代码,配置了tomcat8,但是直接报错了, ![org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class org.springframework.web.context.ContextLoaderListener](https://img-ask.csdn.net/upload/201703/11/1489171041_696389.png) 之后我将lib下的所有spring包放到了tomcat的lib下,就没有报错了 这是为什么,idea没有像eclipse一样的构建路径吗?而且这个问题出现的好奇怪,没有看到过其他人发生过,找遍网上也没有答案。
springboot配置支持jsp依赖报错,但是不影响项目运行。
想Spring boot 支持jsp,在pom.xml文件中加入了依赖如下: ``` <dependency> <groupId>org.apache.tomcat.embed</groupId> <artifactId>tomcat-embed-jasper</artifactId> <scope>provided</scope> </dependency> <!-- jstl标签 --> <dependency> <groupId>javax.servlet</groupId> <artifactId>jstl</artifactId> </dependency> ``` 结果启动项目报错,但是最后还是成功启动了,所有功能都能实现且无异常。但是报错让人很不舒服。。。 在Maven Dependencies中,有提及的mchange-commons-java-0.2.11.jar包。 ``` . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.1.5.RELEASE) 2019-05-18 22:36:53.484 INFO 10320 --- [ main] com.theo.alpha.AlphaApplication : Starting AlphaApplication on theo with PID 10320 (E:\springboot\alpha\target\classes started by Theo in E:\springboot\alpha) 2019-05-18 22:36:53.493 INFO 10320 --- [ main] com.theo.alpha.AlphaApplication : No active profile set, falling back to default profiles: default 2019-05-18 22:36:58.575 INFO 10320 --- [g-Init-Reporter] com.mchange.v2.log.MLog : MLog clients using slf4j logging. 2019-05-18 22:36:58.673 INFO 10320 --- [ main] com.mchange.v2.c3p0.C3P0Registry : Initializing c3p0-0.9.5.2 [built 08-December-2015 22:06:04 -0800; debug? true; trace: 10] 2019-05-18 22:37:00.287 INFO 10320 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8081 (http) 2019-05-18 22:37:00.408 INFO 10320 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2019-05-18 22:37:00.412 INFO 10320 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.19] 2019-05-18 22:37:01.735 WARN 10320 --- [ main] o.a.tomcat.util.scan.StandardJarScanner : Failed to scan [file:/C:/Users/Theo/.m2/repository/com/mchange/c3p0/0.9.5.2/mchange-commons-java-0.2.11.jar] from classloader hierarchy java.io.FileNotFoundException: C:\Users\Theo\.m2\repository\com\mchange\c3p0\0.9.5.2\mchange-commons-java-0.2.11.jar (系统找不到指定的文件。) at java.util.zip.ZipFile.open(Native Method) ~[na:1.8.0_152] at java.util.zip.ZipFile.<init>(ZipFile.java:225) ~[na:1.8.0_152] at java.util.zip.ZipFile.<init>(ZipFile.java:155) ~[na:1.8.0_152] at java.util.jar.JarFile.<init>(JarFile.java:166) ~[na:1.8.0_152] at java.util.jar.JarFile.<init>(JarFile.java:130) ~[na:1.8.0_152] at org.apache.tomcat.util.compat.JreCompat.jarFileNewInstance(JreCompat.java:164) ~[tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.tomcat.util.scan.JarFileUrlJar.<init>(JarFileUrlJar.java:65) ~[tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:49) ~[tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:374) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.tomcat.util.scan.StandardJarScanner.processURLs(StandardJarScanner.java:309) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.tomcat.util.scan.StandardJarScanner.doScanClassPath(StandardJarScanner.java:266) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:229) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262) [tomcat-embed-jasper-9.0.19.jar:9.0.19] at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:104) [tomcat-embed-jasper-9.0.19.jar:9.0.19] at org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:83) [tomcat-embed-jasper-9.0.19.jar:9.0.19] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5139) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1377) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1367) [tomcat-embed-core-9.0.19.jar:9.0.19] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_152] at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) [tomcat-embed-core-9.0.19.jar:9.0.19] at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) [na:1.8.0_152] at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:902) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:831) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1377) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1367) [tomcat-embed-core-9.0.19.jar:9.0.19] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_152] at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) [tomcat-embed-core-9.0.19.jar:9.0.19] at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134) [na:1.8.0_152] at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:902) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.StandardService.startInternal(StandardService.java:423) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:932) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.apache.catalina.startup.Tomcat.start(Tomcat.java:455) [tomcat-embed-core-9.0.19.jar:9.0.19] at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.initialize(TomcatWebServer.java:106) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.<init>(TomcatWebServer.java:86) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getTomcatWebServer(TomcatServletWebServerFactory.java:427) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getWebServer(TomcatServletWebServerFactory.java:180) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.createWebServer(ServletWebServerApplicationContext.java:181) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:154) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) [spring-context-5.1.7.RELEASE.jar:5.1.7.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:316) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248) [spring-boot-2.1.5.RELEASE.jar:2.1.5.RELEASE] at com.theo.alpha.AlphaApplication.main(AlphaApplication.java:10) [classes/:na] 2019-05-18 22:37:01.782 INFO 10320 --- [ main] org.apache.jasper.servlet.TldScanner : 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. 2019-05-18 22:37:01.809 INFO 10320 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/alpha] : Initializing Spring embedded WebApplicationContext 2019-05-18 22:37:01.809 INFO 10320 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 8078 ms 2019-05-18 22:37:04.034 INFO 10320 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService 'applicationTaskExecutor' 2019-05-18 22:37:05.326 INFO 10320 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8081 (http) with context path '/alpha' 2019-05-18 22:37:05.346 INFO 10320 --- [ main] com.theo.alpha.AlphaApplication : Started AlphaApplication in 13.509 seconds (JVM running for 15.915) ``` 删除依赖后不报错,但是直接访问jsp页面会变成下载,通过Controller跳转到jsp页面会报错 ``` Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback. Sat May 18 23:03:06 CST 2019 There was an unexpected error (type=Not Found, status=404). No message available ``` 以下是项目的POM.xml文件 ``` <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.1.5.RELEASE</version> <relativePath /> <!-- lookup parent from repository --> </parent> <groupId>com.theo</groupId> <artifactId>alpha</artifactId> <version>0.0.1-SNAPSHOT</version> <name>alpha</name> <description>Demo project for Spring Boot</description> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding> <java.version>1.8</java.version> </properties> <dependencies> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-jdbc</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> <dependency> <groupId>org.mybatis.spring.boot</groupId> <artifactId>mybatis-spring-boot-starter</artifactId> <version>2.0.1</version> </dependency> <dependency> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> </dependency> <dependency> <groupId>com.mchange</groupId> <artifactId>c3p0</artifactId> <version>0.9.5.2</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope> </dependency> <!-- jsp支持 --> <!-- <dependency> <groupId>org.apache.tomcat.embed</groupId> <artifactId>tomcat-embed-jasper</artifactId> <scope>provided</scope> </dependency> --> <!-- jstl标签库 --> <dependency> <groupId>javax.servlet</groupId> <artifactId>jstl</artifactId> </dependency> <!-- 上传下载用 --> <dependency> <groupId>commons-fileupload</groupId> <artifactId>commons-fileupload</artifactId> <version>1.3.1</version> </dependency> <dependency> <groupId>commons-io</groupId> <artifactId>commons-io</artifactId> <version>2.4</version> </dependency> <!-- 自定义标签 --> <dependency> <groupId>taglibs</groupId> <artifactId>standard</artifactId> <version>1.1.2</version> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build> </project> ```
spring boot 项目用winsw组件注册成windows服务的时候,访问接口 swing组件不显示的问题?
因为公司项目需要在windows下通过restful接口去调用本地设备,需要调用摄像头,我用opencv的方法去调用摄像头,用swing 组件去显示摄像头拍摄的视频,并通过按钮去去拍照,但是发现在idea中,用psotman去测试的时候项目完美运行,但是把项目打包成jar包,用winsw工具注册成windows服务,用psotman去调用的时候,就发生了异常,无法调用,显示一个java.awt.HeadlessException异常,按照官网的方式 new SpringApplicationBuilder(DemoSwingApplication.class) .headless(false).web(WebApplicationType.NONE) .run(args); 引入以后,发现摄像头灯亮了,但是swing那个界面一直未出现,当把那个headless(false)改为headless(true)时我的服务就直接挂掉了。 win10 64位 环境:jdk 1.8 工具:idea2019.2.2 opencv:4.1 spring boot:2.1.6 注册服务工具:winsw :2.2
关于jsp的page属性不加载的问题
我之前写了一个maven web项目,在电脑上能够运行,然后我把文件拷贝回家,他竟然都不报错,tomcat成功启动,在eclipse的web浏览器中能够正常显示页面,然而除了头上的page属性啊,taglib包这些未解析,直接原文输出,如果用360浏览器显示的画,全部是原文输出,什么都不解析了,我的web头文件的版本是3.0的,我也有写!doctype,有大神能帮我分析一下吗?![![图片说明](https://img-ask.csdn.net/upload/201704/16/1492304952_634214.png)![!图片说明](https://img-ask.csdn.net/upload/201704/16/1492304946_103460.png)
关于 No suitable driver问题,问题已经解决,但问题本身很奇怪
这个问题之前有过发生,但我都没较真,解决就过去了,但今天认真对比了下发现很奇怪。望大神帮助指点 先说问题: 项目为maven 的 spring mvc+mybatis框架,本地运行了一下后,去tomcat下打包,上传服务器 ,上传后,修改jdbc.properties文件,更改数据库。 之后tomcat正常启动,登录页面正常打开(未访问DB的页面),登录后,开始报错: No suitable driver 。 按网上的说法一一尝试皆无效。 本地服务远程连接DB无问题运行。 后来解决方法:把本地跑的布署项目包直接上传服务器,OK。 返回查问题根本原因。**发现不能远程修改jdbc.properties文件只要动一下就报no suitable driver错误。复制本地的过去就没问题。文字一模一样。** 另外: 本地文件编辑在eclipse中编辑,编码utf-8。 服务器上用的记事本。 我有点怀疑是系统底层编码问题,但实在无头绪理清,在此求教大神帮忙~
idea无报错但显示空白页面是什么原因?
####idea2018.3 自带的tomcat JDK1.8 引入的eclipse maven项目 编译和启动都成功了 没有报错 然后进入localhost8080端口 显示空白页面 控制台报了如下信息: ``` 2019-07-26 14:31:41.420 [http-nio-8080-exec-1] INFO o.a.c.core.ContainerBase.[Tomcat].[localhost].[/] - Initializing Spring FrameworkServlet 'dispatcherServlet' 2019-07-26 14:31:41.420 [http-nio-8080-exec-1] INFO org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'dispatcherServlet': initialization started 2019-07-26 14:31:41.453 [http-nio-8080-exec-1] INFO org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'dispatcherServlet': initialization completed in 33 ms 2019-07-26 14:31:41.503 [http-nio-8080-exec-1] ERROR o.springframework.boot.web.support.ErrorPageFilter - Cannot forward to error page for request [/] as the response has already been committed. As a result, the response may have the wrong status code. If your application is running on WebSphere Application Server you may be able to resolve this problem by setting com.ibm.ws.webcontainer.invokeFlushAfterService to false ``` 直接在网址输入http://localhost:8080/login 报如下: ``` 2019-07-26 15:13:28.972 [http-nio-8080-exec-9] WARN o.s.w.s.m.m.a.ExceptionHandlerExceptionResolver - Resolved exception caused by Handler execution: com.coin.manager.interceptor.UserSessionException: 页面已失效,请重新登录 2019-07-26 15:13:28.978 [http-nio-8080-exec-9] WARN o.s.w.s.m.m.a.ExceptionHandlerExceptionResolver - Resolved exception caused by Handler execution: com.coin.manager.interceptor.UserSessionException: 页面已失效,请重新登录 2019-07-26 15:13:32.408 [http-nio-8080-exec-10] WARN o.s.w.s.m.m.a.ExceptionHandlerExceptionResolver - Resolved exception caused by Handler execution: org.springframework.web.HttpRequestMethodNotSupportedException: Request method 'GET' not supported 2019-07-26 15:13:32.410 [http-nio-8080-exec-10] ERROR o.springframework.boot.web.support.ErrorPageFilter - Cannot forward to error page for request [/login] as the response has already been committed. As a result, the response may have the wrong status code. If your application is running on WebSphere Application Server you may be able to resolve this problem by setting com.ibm.ws.webcontainer.invokeFlushAfterService to false ``` ####**不知道是什么原因,是tomcat的问题吗?还是拦截器的原因?可是这个是从svn拉下来的,同事的eclipse完美运行** ``` # 页面默认前缀目录 spring.mvc.view.prefix=/WEB-INF/page/ # 响应页面默认后缀 spring.mvc.view.suffix=.jsp ```
javaweb程序在eclipse上突然无法运行
之前写的一个web项目,能正常运行。然后中间考试了几天,再打开程序就不能运行了。 直接maven打包放到tomcat中的webapps中可以运行,但是在eclipse中就一直报下面的错误: 严重: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/insurance]] at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:939) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1419) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1409) 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:748) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/insurance]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) ... 6 more Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@a00ee03] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4860) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4995) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 6 more Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@17bf21a6] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:112) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:140) at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:724) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 9 more Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: invalid LOC header (bad signature) at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:142) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107) ... 12 more Caused by: java.util.zip.ZipException: invalid LOC header (bad signature) at java.util.zip.ZipFile.read(Native Method) at java.util.zip.ZipFile.access$1400(ZipFile.java:60) at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717) at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419) at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158) at sun.misc.IOUtils.readFully(IOUtils.java:65) at java.util.jar.JarFile.getBytes(JarFile.java:425) at java.util.jar.JarFile.getManifestFromReference(JarFile.java:193) at java.util.jar.JarFile.getManifest(JarFile.java:180) at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:140) ... 13 more 十二月 05, 2017 7:50:16 下午 org.apache.catalina.core.ContainerBase startInternal 严重: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]] at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:939) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:793) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.startup.Catalina.start(Catalina.java:670) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:353) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:493) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1419) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1409) 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:748) Caused by: org.apache.catalina.LifecycleException: A child container failed during start at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:947) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 6 more 十二月 05, 2017 7:50:16 下午 org.apache.catalina.startup.Catalina start 严重: The required Server component failed to start so Tomcat is unable to start. org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) at org.apache.catalina.startup.Catalina.start(Catalina.java:670) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:353) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:493) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:793) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 7 more Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 9 more Caused by: org.apache.catalina.LifecycleException: A child container failed during start at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:947) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) ... 11 more 网上找遍方法都不行,在IDEA也是一样的错误,其他的项目也是一样的错。重装tomcat了也不行。 maven仓库没问题,删了重新下也是一样,然后项目maven test也是build success的。
求助!!wildfly单机部署war包时启动失败,报错。
我是在idea把正常运行的项目打成war包放在了wildfly(10和17两个版本都试了)的standalone\deployments目录下,然后直接运行standalone.bat的。启动时报错,无法加载bean。但是放到tomcat可以正常启动运行。 查遍中外文档和提问,还是没有解决。日志信息如下。 ``` 2019-06-13 14:20:54,155 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final 2019-06-13 14:20:54,643 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.7.Final 2019-06-13 14:20:54,653 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final 2019-06-13 14:20:54,752 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) starting 2019-06-13 14:20:54,753 DEBUG [org.jboss.as.config] (MSC service thread 1-2) Configured system properties: awt.toolkit = sun.awt.windows.WToolkit file.encoding = GBK file.encoding.pkg = sun.io file.separator = \ java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment java.awt.printerjob = sun.awt.windows.WPrinterJob java.class.path = D:\widefly\wildfly-17.0.0.Final\jboss-modules.jar java.class.version = 52.0 java.endorsed.dirs = D:\jdk1.8\jre\lib\endorsed java.ext.dirs = D:\jdk1.8\jre\lib\ext;C:\Windows\Sun\Java\lib\ext java.home = D:\jdk1.8\jre java.io.tmpdir = C:\Users\Lenovo\AppData\Local\Temp\ java.library.path = D:\jdk1.8\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;D:\jdk1.8\bin;D:\jdk1.8\jre\bin;C:\Program Files\TortoiseSVN\bin;D:\Maven\apache-maven-3.3.9\bin;D:\widefly\wildfly-17.0.0.Final\bin;C:\Users\Lenovo\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\Lenovo\AppData\Local\Programs\Python\Python37\;C:\Users\Lenovo\AppData\Local\Microsoft\WindowsApps;;. java.net.preferIPv4Stack = true java.runtime.name = Java(TM) SE Runtime Environment java.runtime.version = 1.8.0_211-b12 java.specification.name = Java Platform API Specification java.specification.vendor = Oracle Corporation java.specification.version = 1.8 java.util.logging.manager = org.jboss.logmanager.LogManager java.vendor = Oracle Corporation java.vendor.url = http://java.oracle.com/ java.vendor.url.bug = http://bugreport.sun.com/bugreport/ java.version = 1.8.0_211 java.vm.info = mixed mode java.vm.name = Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name = Java Virtual Machine Specification java.vm.specification.vendor = Oracle Corporation java.vm.specification.version = 1.8 java.vm.vendor = Oracle Corporation java.vm.version = 25.211-b12 javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder jboss.home.dir = D:\widefly\wildfly-17.0.0.Final jboss.host.name = desktop-e1tfeli jboss.modules.dir = D:\widefly\wildfly-17.0.0.Final\modules jboss.modules.system.pkgs = org.jboss.byteman jboss.node.name = desktop-e1tfeli jboss.qualified.host.name = desktop-e1tfeli jboss.server.base.dir = D:\widefly\wildfly-17.0.0.Final\standalone jboss.server.config.dir = D:\widefly\wildfly-17.0.0.Final\standalone\configuration jboss.server.data.dir = D:\widefly\wildfly-17.0.0.Final\standalone\data jboss.server.deploy.dir = D:\widefly\wildfly-17.0.0.Final\standalone\data\content jboss.server.log.dir = D:\widefly\wildfly-17.0.0.Final\standalone\log jboss.server.name = desktop-e1tfeli jboss.server.persist.config = true jboss.server.temp.dir = D:\widefly\wildfly-17.0.0.Final\standalone\tmp line.separator = logging.configuration = file:D:\widefly\wildfly-17.0.0.Final\standalone\configuration/logging.properties module.path = D:\widefly\wildfly-17.0.0.Final\modules org.jboss.boot.log.file = D:\widefly\wildfly-17.0.0.Final\standalone\log\server.log org.jboss.resolver.warning = true os.arch = amd64 os.name = Windows 10 os.version = 10.0 path.separator = ; program.name = standalone.bat sun.arch.data.model = 64 sun.boot.class.path = D:\jdk1.8\jre\lib\resources.jar;D:\jdk1.8\jre\lib\rt.jar;D:\jdk1.8\jre\lib\sunrsasign.jar;D:\jdk1.8\jre\lib\jsse.jar;D:\jdk1.8\jre\lib\jce.jar;D:\jdk1.8\jre\lib\charsets.jar;D:\jdk1.8\jre\lib\jfr.jar;D:\jdk1.8\jre\classes sun.boot.library.path = D:\jdk1.8\jre\bin sun.cpu.endian = little sun.cpu.isalist = amd64 sun.desktop = windows sun.io.unicode.encoding = UnicodeLittle sun.java.command = D:\widefly\wildfly-17.0.0.Final\jboss-modules.jar -mp D:\widefly\wildfly-17.0.0.Final\modules org.jboss.as.standalone -Djboss.home.dir=D:\widefly\wildfly-17.0.0.Final sun.java.launcher = SUN_STANDARD sun.jnu.encoding = GBK sun.management.compiler = HotSpot 64-Bit Tiered Compilers sun.os.patch.level = sun.stderr.encoding = ms936 sun.stdout.encoding = ms936 user.country = CN user.dir = D:\widefly\wildfly-17.0.0.Final\bin user.home = C:\Users\Lenovo user.language = zh user.name = Lenovo user.script = user.timezone = Asia/Shanghai user.variant = 2019-06-13 14:20:54,754 DEBUG [org.jboss.as.config] (MSC service thread 1-2) VM Arguments: -Dprogram.name=standalone.bat -Xms128M -Xmx2048M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=512m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=D:\widefly\wildfly-17.0.0.Final\standalone\log\server.log -Dlogging.configuration=file:D:\widefly\wildfly-17.0.0.Final\standalone\configuration/logging.properties 2019-06-13 14:20:55,611 INFO [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.9.1.Final 2019-06-13 14:20:56,314 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. 2019-06-13 14:20:56,336 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. 2019-06-13 14:20:57,497 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) 2019-06-13 14:20:57,511 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.7.2.Final 2019-06-13 14:20:57,518 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.7.2.Final 2019-06-13 14:20:57,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0001: Activating Infinispan subsystem. 2019-06-13 14:20:57,550 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 60) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem 2019-06-13 14:20:57,559 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 63) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem 2019-06-13 14:20:57,560 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 72) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique. 2019-06-13 14:20:57,589 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 74) WFLYWS0002: Activating WebServices Extension 2019-06-13 14:20:57,595 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 52) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors 2019-06-13 14:20:57,598 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 61) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem 2019-06-13 14:20:57,599 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 64) WFLYNAM0001: Activating Naming Subsystem 2019-06-13 14:20:57,611 INFO [org.jboss.as.security] (ServerService Thread Pool -- 70) WFLYSEC0002: Activating Security Subsystem 2019-06-13 14:20:57,621 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 53) WFLYRS0016: RESTEasy version 3.7.0.Final 2019-06-13 14:20:57,626 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 58) WFLYJSF0007: Activated the following JSF Implementations: [main] 2019-06-13 14:20:57,635 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.16.Final) 2019-06-13 14:20:57,637 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4) 2019-06-13 14:20:57,639 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=5.0.3.Final 2019-06-13 14:20:57,645 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 62) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem 2019-06-13 14:20:57,719 INFO [io.smallrye.metrics] (MSC service thread 1-2) Converted [2] config entries and added [4] replacements 2019-06-13 14:20:57,727 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 2.0.21.Final starting 2019-06-13 14:20:57,730 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2 2019-06-13 14:20:57,735 INFO [io.smallrye.metrics] (MSC service thread 1-2) Converted [3] config entries and added [14] replacements 2019-06-13 14:20:57,755 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service 2019-06-13 14:20:57,786 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.12.Final 2019-06-13 14:20:57,786 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 2019-06-13 14:20:57,871 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0014: Creating file handler for path 'D:\widefly\wildfly-17.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 2019-06-13 14:20:57,930 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host. 2019-06-13 14:20:57,930 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing. 2019-06-13 14:20:57,962 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server. 2019-06-13 14:20:57,970 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0018: Host default-host starting 2019-06-13 14:20:58,046 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 2019-06-13 14:20:58,105 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: EJB subsystem suspension complete 2019-06-13 14:20:58,173 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 2019-06-13 14:20:58,278 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none 2019-06-13 14:20:58,294 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory D:\widefly\wildfly-17.0.0.Final\standalone\deployments 2019-06-13 14:20:58,303 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "jeeplus.war" (runtime-name: "jeeplus.war") 2019-06-13 14:20:58,561 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 2019-06-13 14:20:58,636 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.2) 2019-06-13 14:22:01,638 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xbean.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/batik-js-1.7.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,652 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry avalon-framework-4.2.0.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,652 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry batik-all-1.6.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,653 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry commons-io-1.3.1.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,654 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry commons-logging-1.0.4.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,655 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry fop-hyph.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,655 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jai_codec.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,656 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jai_core.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,656 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jimi.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,657 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry serializer-2.7.0.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,657 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry servlet-2.2.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,658 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xalan-2.7.0.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,662 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xercesImpl-2.7.1.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,664 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xml-apis-1.3.02.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,664 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xmlunit1.0.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/fop-0.94.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,676 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry ridl.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/juh-2.3.0.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,676 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jurt.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/juh-2.3.0.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,677 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry ridl.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/jurt-2.3.0.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,678 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry unoloader.jar in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/jurt-2.3.0.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,678 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry ../../lib/ in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/jurt-2.3.0.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:01,679 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry ../bin/ in /D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/lib/jurt-2.3.0.jar does not point to a valid jar for a Class-Path reference. 2019-06-13 14:22:03,113 WARN [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause) 2019-06-13 14:22:03,113 WARN [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause) 2019-06-13 14:22:03,151 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.14.Final 2019-06-13 14:22:03,202 WARN [org.jboss.as.jaxrs] (MSC service thread 1-7) WFLYRS0018: Explicit usage of Jackson annotation in a JAX-RS deployment; the system will disable JSON-B processing for the current deployment. Consider setting the 'resteasy.preferJacksonOverJsonB' property to 'false' to restore JSON-B. 2019-06-13 14:22:03,206 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0004: Deploying JDBC-compliant driver class com.alibaba.druid.proxy.DruidDriver (version 4.0) 2019-06-13 14:22:03,213 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0004: Deploying JDBC-compliant driver class com.alibaba.druid.mock.MockDriver (version 0.0) 2019-06-13 14:22:03,214 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 2019-06-13 14:22:03,216 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class net.sourceforge.jtds.jdbc.Driver (version 1.3) 2019-06-13 14:22:03,224 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0) 2019-06-13 14:22:03,228 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 42.1) 2019-06-13 14:22:03,229 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.apache.solr.client.solrj.io.sql.DriverImpl (version 1.0) 2019-06-13 14:22:03,269 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war_org.h2.Driver_1_3 2019-06-13 14:22:03,270 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war_net.sourceforge.jtds.jdbc.Driver_1_3 2019-06-13 14:22:03,270 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war_com.alibaba.druid.proxy.DruidDriver_4_0 2019-06-13 14:22:03,271 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war_com.mysql.cj.jdbc.Driver_8_0 2019-06-13 14:22:03,270 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war_com.alibaba.druid.mock.MockDriver_0_0 2019-06-13 14:22:03,271 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war 2019-06-13 14:22:03,276 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war_org.apache.solr.client.solrj.io.sql.DriverImpl_1_0 2019-06-13 14:22:03,277 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = jeeplus.war_org.postgresql.Driver_42_1 2019-06-13 14:22:03,471 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started client-mappings cache from ejb container 2019-06-13 14:22:03,586 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) No Spring WebApplicationInitializer types detected on classpath 2019-06-13 14:22:03,600 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Set web app root system property: 'webapp.root' = [D:\widefly\wildfly-17.0.0.Final\standalone\tmp\vfs\temp\temp5858f9dbed7b899b\content-8652ab40c8a74b5c] 2019-06-13 14:22:03,603 INFO [io.undertow.servlet] (ServerService Thread Pool -- 111) Initializing log4j from [classpath:properties/log4j.properties] 2019-06-13 14:22:08,112 WARN [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 111) Bean creation exception on non-lazy FactoryBean type check: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'actMapper' defined in VFS resource ["/D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/classes/com/jeeplus/modules/act/mapper/ActMapper.class"]: Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException 2019-06-13 14:22:09,473 WARN [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 111) Bean creation exception on non-lazy FactoryBean type check: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'actNodeSetingInfoMapper' defined in VFS resource ["/D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/classes/com/jeeplus/modules/act/mapper/ActNodeSetingInfoMapper.class"]: Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException 2019-06-13 14:22:10,806 WARN [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 111) Bean creation exception on non-lazy FactoryBean type check: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'actSetingInfoMapper' defined in VFS resource ["/D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/classes/com/jeeplus/modules/act/mapper/ActSetingInfoMapper.class"]: Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException 2019-06-13 14:22:11,979 WARN [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 111) Bean creation exception on non-lazy FactoryBean type check: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'testPieClassMapper' defined in VFS resource ["/D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/classes/com/jeeplus/modules/echarts/mapper/other/TestPieClassMapper.class"]: Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException 2019-06-13 14:22:13,133 WARN [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 111) Bean creation exception on non-lazy FactoryBean type check: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'TExamQusetionUserMapper' defined in VFS resource ["/D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/classes/com/jeeplus/modules/examque/mapper/TExamQusetionUserMapper.class"]: Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException 2019-06-13 14:22:14,159 WARN [org.springframework.beans.factory.support.DefaultListableBeanFactory] (ServerService Thread Pool -- 111) Bean creation exception on non-lazy FactoryBean type check: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'examQuestionMapper' defined in VFS resource ["/D:/widefly/wildfly-17.0.0.Final/bin/content/jeeplus.war/WEB-INF/classes/com/jeeplus/modules/examquestion/mapper/ExamQuestionMapper.class"]: Cannot resolve reference to bean 'sqlSessionFactory' while setting bean property 'sqlSessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sqlSessionFactory' defined in class path resource [spring/spring-context.xml]: Invocation of init method failed; nested exception is java.lang.NullPointerException ``` ![报错信息1](https://img-ask.csdn.net/upload/201906/13/1560407452_637434.png) ![报错信息2](https://img-ask.csdn.net/upload/201906/13/1560407517_691665.png)
130 个相见恨晚的超实用网站,一次性分享出来
文末没有公众号,只求 点赞 + 关注 搞学习 知乎:www.zhihu.com 大学资源网:http://www.dxzy163.com/ 简答题:http://www.jiandati.com/ 网易公开课:https://open.163.com/ted/ 网易云课堂:https://study.163.com/ 中国大学MOOC:www.icourse163.org 网易云课堂:stu
终于明白阿里百度这样的大公司,为什么面试经常拿ThreadLocal考验求职者了
点击上面↑「爱开发」关注我们每晚10点,捕获技术思考和创业资源洞察什么是ThreadLocalThreadLocal是一个本地线程副本变量工具类,各个线程都拥有一份线程私有的数
win10系统安装教程(U盘PE+UEFI安装)
一、准备工作 u盘,电脑一台,win10原版镜像(msdn官网) 二、下载wepe工具箱  极力推荐微pe(微pe官方下载) 下载64位的win10 pe,使用工具箱制作启动U盘打开软件,   选择安装到U盘(按照操作无需更改) 三、重启进入pe系统   1、关机后,将U盘插入电脑 2、按下电源后,按住F12进入启动项选择(技嘉主板是F12)     选择需要启
程序员必须掌握的核心算法有哪些?
由于我之前一直强调数据结构以及算法学习的重要性,所以就有一些读者经常问我,数据结构与算法应该要学习到哪个程度呢?,说实话,这个问题我不知道要怎么回答你,主要取决于你想学习到哪些程度,不过针对这个问题,我稍微总结一下我学过的算法知识点,以及我觉得值得学习的算法。这些算法与数据结构的学习大多数是零散的,并没有一本把他们全部覆盖的书籍。下面是我觉得值得学习的一些算法以及数据结构,当然,我也会整理一些看过
大学四年自学走来,这些私藏的实用工具/学习网站我贡献出来了
大学四年,看课本是不可能一直看课本的了,对于学习,特别是自学,善于搜索网上的一些资源来辅助,还是非常有必要的,下面我就把这几年私藏的各种资源,网站贡献出来给你们。主要有:电子书搜索、实用工具、在线视频学习网站、非视频学习网站、软件下载、面试/求职必备网站。 注意:文中提到的所有资源,文末我都给你整理好了,你们只管拿去,如果觉得不错,转发、分享就是最大的支持了。 一、PDF搜索网站推荐 对于大部
C语言魔塔游戏
很早就很想写这个,今天终于写完了。 游戏截图: 编译环境: VS2017 游戏需要一些图片,如果有想要的或者对游戏有什么看法的可以加我的QQ 2985486630 讨论,如果暂时没有回应,可以在博客下方留言,到时候我会看到。 下面我来介绍一下游戏的主要功能和实现方式 首先是玩家的定义,使用结构体,这个名字是可以自己改变的 struct gamerole { char n
java源码分析 Arrays.asList()与Collections.unmodifiableList()
举个栗子 本章示例代码来自java编程思想——17.4.1未获支持的操作——Unsupported类。 import java.util.*; public class Unsupported { static void test(String msg, List&lt;String&gt; list) { System.out.println("--- " + msg
究竟你适不适合买Mac?
我清晰的记得,刚买的macbook pro回到家,开机后第一件事情,就是上了淘宝网,花了500元钱,找了一个上门维修电脑的师傅,上门给我装了一个windows系统。。。。。。 表砍我。。。 当时买mac的初衷,只是想要个固态硬盘的笔记本,用来运行一些复杂的扑克软件。而看了当时所有的SSD笔记本后,最终决定,还是买个好(xiong)看(da)的。 已经有好几个朋友问我mba怎么样了,所以今天尽量客观
Python爬虫爬取淘宝,京东商品信息
小编是一个理科生,不善长说一些废话。简单介绍下原理然后直接上代码。 使用的工具(Python+pycharm2019.3+selenium+xpath+chromedriver)其中要使用pycharm也可以私聊我selenium是一个框架可以通过pip下载 pip install selenium -i https://pypi.tuna.tsinghua.edu.cn/simple/ 
Java学习笔记(七十二)—— Cookie
概述 会话技术: 会话:一次会话中包含多次请求和响应 一次会话:浏览器第一次给服务器发送资源请求,会话建立,直到有一方断开为止 功能:在一次会话的范围内的多次请求间,共享数据 方式: 客户端会话技术:Cookie,把数据存储到客户端 服务器端会话技术:Session,把数据存储到服务器端 Cookie 概念:客户端会话技术,将数据存储到客户端 快速入门: 使用步骤: 创建C
程序员写了一个新手都写不出的低级bug,被骂惨了。
你知道的越多,你不知道的越多 点赞再看,养成习惯 本文 GitHub https://github.com/JavaFamily 已收录,有一线大厂面试点思维导图,也整理了很多我的文档,欢迎Star和完善,大家面试可以参照考点复习,希望我们一起有点东西。 前前言 为啥今天有个前前言呢? 因为你们的丙丙啊,昨天有牌面了哟,直接被微信官方推荐,知乎推荐,也就仅仅是还行吧(心里乐开花)
Java工作4年来应聘要16K最后没要,细节如下。。。
前奏: 今天2B哥和大家分享一位前几天面试的一位应聘者,工作4年26岁,统招本科。 以下就是他的简历和面试情况。 基本情况: 专业技能: 1、&nbsp;熟悉Sping了解SpringMVC、SpringBoot、Mybatis等框架、了解SpringCloud微服务 2、&nbsp;熟悉常用项目管理工具:SVN、GIT、MAVEN、Jenkins 3、&nbsp;熟悉Nginx、tomca
2020年,冯唐49岁:我给20、30岁IT职场年轻人的建议
点击“技术领导力”关注∆  每天早上8:30推送 作者| Mr.K   编辑| Emma 来源| 技术领导力(ID:jishulingdaoli) 前天的推文《冯唐:职场人35岁以后,方法论比经验重要》,收到了不少读者的反馈,觉得挺受启发。其实,冯唐写了不少关于职场方面的文章,都挺不错的。可惜大家只记住了“春风十里不如你”、“如何避免成为油腻腻的中年人”等不那么正经的文章。 本文整理了冯
程序员该看的几部电影
##1、骇客帝国(1999) 概念:在线/离线,递归,循环,矩阵等 剧情简介: 不久的将来,网络黑客尼奥对这个看似正常的现实世界产生了怀疑。 他结识了黑客崔妮蒂,并见到了黑客组织的首领墨菲斯。 墨菲斯告诉他,现实世界其实是由一个名叫“母体”的计算机人工智能系统控制,人们就像他们饲养的动物,没有自由和思想,而尼奥就是能够拯救人类的救世主。 可是,救赎之路从来都不会一帆风顺,到底哪里才是真实的世界?
蓝桥杯知识点汇总:基础知识和常用算法
文章目录JAVA基础语法:算法竞赛常用的JAVA API:基础算法待更: 此系列包含蓝桥杯所考察的绝大部分知识点,一共有基础语法,常用API,基础算法和数据结构,和往年真题四部分,虽然语言以JAVA为主,但算法部分是相通的,C++组的小伙伴也可以看哦。所有文章的链接都会在此公布,还有很多没有更新,会持续更新,如果大佬发现文章有错误的地方请指正,我会十分感谢。另外,有什么问题可私信我~ JAVA基础
作为一个程序员,CPU的这些硬核知识你必须会!
CPU对每个程序员来说,是个既熟悉又陌生的东西? 如果你只知道CPU是中央处理器的话,那可能对你并没有什么用,那么作为程序员的我们,必须要搞懂的就是CPU这家伙是如何运行的,尤其要搞懂它里面的寄存器是怎么一回事,因为这将让你从底层明白程序的运行机制。 随我一起,来好好认识下CPU这货吧 把CPU掰开来看 对于CPU来说,我们首先就要搞明白它是怎么回事,也就是它的内部构造,当然,CPU那么牛的一个东
破14亿,Python分析我国存在哪些人口危机!
2020年1月17日,国家统计局发布了2019年国民经济报告,报告中指出我国人口突破14亿。 猪哥的朋友圈被14亿人口刷屏,但是很多人并没有看到我国复杂的人口问题:老龄化、男女比例失衡、生育率下降、人口红利下降等。 今天我们就来分析一下我们国家的人口数据吧! 一、背景 1.人口突破14亿 2020年1月17日,国家统计局发布了 2019年国民经济报告 ,报告中指出:年末中国大陆总人口(包括31个
实现简单的轮播图(单张图片、多张图片)
前言 刚学js没多久,这篇博客就当做记录了,以后还会完善的,希望大佬们多多指点。ps:下面出现的都是直接闪动,没有滑动效果的轮播图。 单张图片的替换 原理 1.将几张图片叠在一起,通过改变"display:block"和"display:none"这两个属性实现替换。 (前提:在css中给所有图片加上display:none属性) 2.不用将图片叠在一起,将一个div当做"窗口",通过"of
强烈推荐10本程序员在家读的书
很遗憾,这个鼠年春节注定是刻骨铭心的,新型冠状病毒让每个人的神经都是紧绷的。那些处在武汉的白衣天使们,尤其值得我们的尊敬。而我们这些窝在家里的程序员,能不外出就不外出,就是对社会做出的最大的贡献。 有些读者私下问我,窝了几天,有点颓丧,能否推荐几本书在家里看看。我花了一天的时间,挑选了 10 本我最喜欢的书,你可以挑选感兴趣的来读一读。读书不仅可以平复恐惧的压力,还可以对未来充满希望,毕竟苦难终
Linux自学篇——linux命令英文全称及解释
man: Manual 意思是手册,可以用这个命令查询其他命令的用法。 pwd:Print working directory 显示当前目录 su:Swith user 切换用户,切换到root用户 cd:Change directory 切换目录 ls:List files 列出目录下的文件 ps:Process Status 进程状态 mk
Python实战:抓肺炎疫情实时数据,画2019-nCoV疫情地图
文章目录1. 前言2. 数据下载3. 数据处理4. 数据可视化 1. 前言 今天,群里白垩老师问如何用python画武汉肺炎疫情地图。白垩老师是研究海洋生态与地球生物的学者,国家重点实验室成员,于不惑之年学习python,实为我等学习楷模。先前我并没有关注武汉肺炎的具体数据,也没有画过类似的数据分布图。于是就拿了两个小时,专门研究了一下,遂成此文。 2月6日追记:本文发布后,腾讯的数据源多次变更u
智力题(程序员面试经典)
NO.1  有20瓶药丸,其中19瓶装有1克/粒的药丸,余下一瓶装有1.1克/粒的药丸。给你一台称重精准的天平,怎么找出比较重的那瓶药丸?天平只能用一次。 解法 有时候,严格的限制条件有可能反倒是解题的线索。在这个问题中,限制条件是天平只能用一次。 因为天平只能用一次,我们也得以知道一个有趣的事实:一次必须同时称很多药丸,其实更准确地说,是必须从19瓶拿出药丸进行称重。否则,如果跳过两瓶或更多瓶药
Java与Python学习通法(1)和(2)序言和编程语言发展史怎么学
大家好,我是 jacky 朱元禄,很高兴跟大家一起学习 《Java与Python学习通法系列》。 首先,说一下,我为什么要录这个课; 我们都已经知道Java 和 Python的视频教程和书籍,可以说是非常非常多了,那我录制本系列课的意义是什么呢? (1)课程特色一:我想告诉大家学习编程语言是有捷径的,这个捷径就是 理解技术背后的“哲学逻辑”,或者说是“人文逻辑”,相信你听完 jack
在家远程办公效率低?那你一定要收好这个「在家办公」神器!
相信大家都已经收到国务院延长春节假期的消息,接下来,在家远程办公可能将会持续一段时间。 但是问题来了。远程办公不是人在电脑前就当坐班了,相反,对于沟通效率,文件协作,以及信息安全都有着极高的要求。有着非常多的挑战,比如: 1在异地互相不见面的会议上,如何提高沟通效率? 2文件之间的来往反馈如何做到及时性?如何保证信息安全? 3如何规划安排每天工作,以及如何进行成果验收? ......
作为一个程序员,内存和磁盘的这些事情,你不得不知道啊!!!
截止目前,我已经分享了如下几篇文章: 一个程序在计算机中是如何运行的?超级干货!!! 作为一个程序员,CPU的这些硬核知识你必须会! 作为一个程序员,内存的这些硬核知识你必须懂! 这些知识可以说是我们之前都不太重视的基础知识,可能大家在上大学的时候都学习过了,但是嘞,当时由于老师讲解的没那么有趣,又加上这些知识本身就比较枯燥,所以嘞,大家当初几乎等于没学。 再说啦,学习这些,也看不出来有什么用啊!
阿里架构师花近十年时间整理出来的Java核心知识pdf(Java岗)
由于细节内容实在太多啦,所以只把部分知识点截图出来粗略的介绍,每个小节点里面都有更细化的内容! 整理了一份Java核心知识点。覆盖了JVM、锁、并发、Java反射、Spring原理、微服务、Zookeeper、数据库、数据结构等大量知识点。       欢迎大家加入java学习交流社区  点击加入   可获取文中文档       小编推荐:     
Python基础知识点梳理
python基础知识点梳理 摘要: 本文主要介绍一些平时经常会用到的python基础知识点,用于加深印象,也算是对于学习这门语言的一个总结与回顾。python的详细语法介绍可以查看官方编程手册,也有一些在线网站对python语法进行了比较全面的介绍,比如菜鸟教程: python3 教程|菜鸟教程 为了方便聚焦知识点,本文涉及的操作实例并不多,想学好一门语言关键还得自己多编码多实践。 python语
2020年2月全国程序员工资统计,平均工资13716元
趋势 2020年2月,中国大陆程序员平均工资13716元,比上个月增加。具体趋势如图: 各主要程序员城市工资变化 城市 北京,上海,深圳,杭州,广州四地的工资最高。 city 平均工资 最低工资 中位数 最高工资 招聘人数 百分比 北京 18098 3750 15000 45000 20529 9.53% 深圳 16903 5750 15000 37500 30941 14
Java坑人面试题系列: 包装类(中级难度)
Java Magazine上面有一个专门坑人的面试题系列: https://blogs.oracle.com/javamagazine/quiz-2。 这些问题的设计宗旨,主要是测试面试者对Java语言的了解程度,而不是为了用弯弯绕绕的手段把面试者搞蒙。 如果你看过往期的问题,就会发现每一个都不简单。 这些试题模拟了认证考试中的一些难题。 而 “中级(intermediate)” 和 “高级(ad
为什么说程序员做外包没前途?
之前做过不到3个月的外包,2020的第一天就被释放了,2019年还剩1天,我从外包公司离职了。我就谈谈我个人的看法吧。首先我们定义一下什么是有前途 稳定的工作环境 不错的收入 能够在项目中不断提升自己的技能(ps:非技术上的认知也算) 找下家的时候能找到一份工资更高的工作 如果你目前还年轻,但高不成低不就,只有外包offer,那请往下看。 外包公司你应该
基于Python的人脸自动戴口罩系统
目录 1、项目背景 2、页面设计 3、器官识别 4、退出系统 1、项目背景 2019年新型冠状病毒感染的肺炎疫情发生以来,牵动人心,举国哀痛,口罩、酒精、消毒液奇货可居。 抢不到口罩,怎么办?作为技术人今天分享如何使用Python实现自动戴口罩系统,来安慰自己,系统效果如下所示: 本系统的实现原理是借助 Dlib模块的Landmark人脸68个关键点检测库轻松识别出人脸五官
这个世界上人真的分三六九等,你信吗?
偶然间,在知乎上看到一个问题 一时间,勾起了我深深的回忆。 以前在厂里打过两次工,做过家教,干过辅导班,做过中介。零下几度的晚上,贴过广告,满脸、满手地长冻疮。   再回首那段岁月,虽然苦,但让我学会了坚持和忍耐。让我明白了,在这个世界上,无论环境多么的恶劣,只要心存希望,星星之火,亦可燎原。   下文是原回答,希望能对你能有所启发。   如果我说,这个世界上人真的分三六九等,
Java基础知识点梳理
Java基础知识点梳理 摘要: 虽然已经在实际工作中经常与java打交道,但是一直没系统地对java这门语言进行梳理和总结,掌握的知识也比较零散。恰好利用这段时间重新认识下java,并对一些常见的语法和知识点做个总结与回顾,一方面为了加深印象,方便后面查阅,一方面为了学好java打下基础。 Java简介 java语言于1995年正式推出,最开始被命名为Oak语言,由James Gosling(詹姆
jQuery实现高仿QQ音乐
几个实现的效果看视频吧: bandicam 2020-02-05 16-28-20-127 动图很是不清楚 github地址奉上:https://github.com/tangmusenLiu/Large-warehouse https://github.com/tangmu
《请停止无效的努力》读书笔记
一、如何快速找到你的天赋优势 1、人的价值定位 1.1、冰山模型 &nbsp; &nbsp; &nbsp; &nbsp; 你能创造多大的价值,离不开三大内在因素: 第一要素:知识和技能,位于冰山显露的部分,是非常显性,容易展示出来的; 第二要素:能力,比如:思考能力、人际交往能力等,需要通过仔细的行为观察才能看出,位于冰山的中间部分; 第三要素:天赋。包括潜在能力、性格特质、动机、价值观等
2020年全新Java学习路线图,含配套视频,学完即为中级Java程序员!!
新的一年来临,突如其来的疫情打破了平静的生活! 在家的你是否很无聊,如果无聊就来学习吧! 世上只有一种投资只赚不赔,那就是学习!!! 传智播客于2020年升级了Java学习线路图,硬核升级,免费放送! 学完你就是中级程序员,能更快一步找到工作! 一、Java基础 JavaSE基础是Java中级程序员的起点,是帮助你从小白到懂得编程的必经之路。 在Java基础板块中有6个子模块的学
相关热词 c#如何定义数组列表 c#倒序读取txt文件 java代码生成c# c# tcp发送数据 c#解决时间格式带星期 c#类似hashmap c#设置istbox的值 c#获取多线程返回值 c# 包含数字 枚举 c# timespan
立即提问