在启动项目时出现了启动服务失败,应该如何解决?

在启动项目时出现了启动服务失败,如何解决?求大神告知

2019-12-9 11:38:50 com.caucho.monitor.MonitorHook$CheckTask doMonitorWinService
严重: stop monitor windows service fail...
[11:38:50.968] {Thread-1} stop monitor windows service fail...
2019-12-9 11:38:51 com.caucho.monitor.MonitorHook$CheckTask configMonitorWinService
严重: config monitor windows service fail...
[11:38:51.203] {Thread-1} config monitor windows service fail...
2019-12-9 11:38:51 com.caucho.monitor.MonitorHook$CheckTask doMonitorWinService
严重: start monitor windows service fail...
[11:38:51.328] {Thread-1} start monitor windows service fail...
[11:39:36.578] {http--8090-1$28721780} javax.servlet.ServletException: java.lang.NullPointerException
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.dispatch.ServletConfigImpl.createServlet(ServletConfigImpl.java:768)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.dispatch.ServletManager.init(ServletManager.java:159)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.webapp.WebApp.start(WebApp.java:1874)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.deploy.DeployController.startImpl(DeployController.java:667)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.deploy.DeployController.restartImpl(DeployController.java:630)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.deploy.StartAutoRedeployAutoStrategy.request(StartAutoRedeployAutoStrategy.java:125)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.deploy.DeployController.request(DeployController.java:600)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.webapp.WebAppContainer.getWebApp(WebAppContainer.java:922)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.webapp.WebAppContainer.buildInvocation(WebAppContainer.java:711)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.host.Host.buildInvocation(Host.java:489)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.host.HostContainer.buildInvocation(HostContainer.java:314)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.cluster.Server.buildInvocation(Server.java:1013)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.dispatch.DispatchServer.buildInvocation(DispatchServer.java:209)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:265)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.port.TcpConnection.run(TcpConnection.java:682)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:730)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.util.ThreadPool$Item.run(ThreadPool.java:649)
[11:39:36.578] {http--8090-1$28721780}  at java.lang.Thread.run(Thread.java:662)
[11:39:36.578] {http--8090-1$28721780} Caused by: java.lang.NullPointerException
[11:39:36.578] {http--8090-1$28721780}  at weaver.conn.RecordSet.getColumnIndex(RecordSet.java:1634)
[11:39:36.578] {http--8090-1$28721780}  at weaver.conn.RecordSet.getInt(RecordSet.java:1308)
[11:39:36.578] {http--8090-1$28721780}  at weaver.system.SystemThreadManager.doSystemThread(SystemThreadManager.java:219)
[11:39:36.578] {http--8090-1$28721780}  at weaver.general.InitServer.init(InitServer.java:345)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.dispatch.ServletConfigImpl.createServletImpl(ServletConfigImpl.java:830)
[11:39:36.578] {http--8090-1$28721780}  at com.caucho.server.dispatch.ServletConfigImpl.createServlet(ServletConfigImpl.java:732)
[11:39:36.578] {http--8090-1$28721780}  ... 17 more

1个回答

空指针,你还早找找下你那里空指针了

javax.servlet.ServletException: java.lang.NullPointerException
Csdn user default icon
上传中...
上传图片
插入图片
抄袭、复制答案,以达到刷声望分或其他目的的行为,在CSDN问答是严格禁止的,一经发现立刻封号。是时候展现真正的技术了!
其他相关推荐
idea启动项目时,提示快速设置失败?
![图片说明](https://img-ask.csdn.net/upload/201704/25/1493105064_515105.png) 出现这个错误是这样的: 我写完代码上传之后,电脑因为断电关机了,而这个时候我的代码已经上传完了,在远程仓库已经看到了上传上去了,再次启动idea,启动服务的时候,项目就出现了这个错误,而别人更新代码的服务依然可以启动,网上找了很多,试了都不可以,还烦请大神帮忙解决一下。
eclipse 项目启动编译失败的问题
项目启动完成提示某个文件的某个bean编译失败,但是我查看了编译后的文件,里面是有被编译的某个类的 网上的方法基本试过了,没什么用,请知道怎么解决的大神出来支招,不胜感谢!
【JAVA】怎么样在spring创建bean失败的时候能正常启动,比如mongoDB
项目中使用了mongoDB,但是经常mongodb的服务器崩溃,然后启动项目的时候就会因为无法初始化Mongtemplete而启动失败 这里想问一个解决方法,项目中有个接口是查mongodb的,在目前代码基础上 怎么样不管mongodb是否挂了,都能启动项目,没挂的时候启动了让接口可以用 mongodb挂了的话接口用不了就是了 或者大家是怎么处理这些情况呢,因为说是什么要保证项目尽量对除了数据库意外的东西弱依赖???? 求解
tomcat集群+oscache 启动服务时 log4j 打印缓存监听jgroups启动失败
使用两个虚拟机搭建了一个小型tomcat集群,发布web项目(内置oscache缓存机制) oscache.properties广播配置为官方配置,网上资料一大堆,不再描述。 tomcat服务器正常启动,具体问题描述如下: **问题1**:启动tomcat服务器,log4j打印oscache错误信息如下: 2015-03-05 15:14:47,697 INFO GeneralCacheAdministrator:98 - Constructed GeneralCacheAdministrator() 2015-03-05 15:14:47,699 INFO GeneralCacheAdministrator:301 - Creating new cache 2015-03-05 15:14:47,759 INFO AbstractBroadcastingListener:35 - AbstractBroadcastingListener registered 2015-03-05 15:14:48,469 ERROR AbstractCacheAdministrator:332 - Could not initialize listener 'com.opensymphony.oscache.plugins.clustersupport.JavaGroupsBroadcastingListener'. Listener ignored. com.opensymphony.oscache.base.InitializationException: Initialization failed: org.jgroups.ChannelException: unable to setup the protocol stack at com.opensymphony.oscache.plugins.clustersupport.JavaGroupsBroadcastingListener.initialize(JavaGroupsBroadcastingListener.java:119) 尝试禁用服务器IPv6 也不能解决以上错误 **问题2**:访问启用两个浏览器会话,分别访问服务中的一个服务器节点, 测试缓存同步: 一个会话单次更新一个缓存对象,另一个会话缓存被更新,再次更新不再生效,反向更新操作亦是如此,单次单向更新操作缓存生效 求问题原因和解决方案
tomcat访问项目出现异常
启动没有报错,在访问8080页面以及项目时出现异常。 8080界面报500异常![图片说明](https://img-ask.csdn.net/upload/201711/28/1511860172_593163.png) 访问自己的项目时,则报出404异常,项目已部署到tomcat中,之前也正常打开过。 百度上面找到的两个解决方法没有用,一个说catalina.jar的冲突,在项目的lib下没有找到所说的追加的catalina.jar;另一个说在context.xml中context元素下追加Loader delegate="true" 也没有效果。 把自己的项目删除在访问8080也失败。
tomcat启动struts1.3项目超时,如何解决?
我的struts1.3项目在以前的网络(A城市的电信)下是启动起来的,现在换了网络(B城市的移动)启动不起来了,我在怀疑是不是eclipse读取dtd文件的时候太慢了。导致启动失败,在工作过程中,我也有tomcat启动超过45秒的情况,一般是把tomcat timeout配置更长,可是这很不科学,因为他在启动的时候就卡住了,你把tomcat启动允许最大时间配置的再长也无法。 控制台输出如下: ``` 九月 05, 2016 9:29:17 下午 org.apache.catalina.core.AprLifecycleListener init 信息: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\jdk\jdk_7u79\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/jdk/jdk_7u79/bin/../jre/bin/client;C:/jdk/jdk_7u79/bin/../jre/bin;C:/jdk/jdk_7u79/bin/../jre/lib/i386;D:\app\Administrator\product\11.2.0\dbhome_1\bin;C:\jdk\jdk_7u79\bin;C:\Windows\System32;C:\Program Files\Subversion\bin;C:\Program Files\TortoiseSVN\bin;D:\maven\apache-maven-3.3.9\bin;;C:\Windows;C:\Windows\system32\wbem;D:\mysql-5.6.24-win32\bin;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;D:\JavaTools\eclipse;;. 九月 05, 2016 9:29:18 下午 org.apache.tomcat.util.digester.SetPropertiesRule begin 警告: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:FileUpdateAndDownload' did not find a matching property. 九月 05, 2016 9:29:19 下午 org.apache.coyote.http11.Http11Protocol init 信息: Initializing Coyote HTTP/1.1 on http-6789 九月 05, 2016 9:29:19 下午 org.apache.catalina.startup.Catalina load 信息: Initialization processed in 2486 ms 九月 05, 2016 9:29:19 下午 org.apache.catalina.core.StandardService start 信息: Starting service Catalina 九月 05, 2016 9:29:19 下午 org.apache.catalina.core.StandardEngine start 信息: Starting Servlet Engine: Apache Tomcat/6.0.44 九月 05, 2016 9:29:21 下午 org.apache.struts.action.ActionServlet initChain 信息: Loading chain catalog from jar:file:/D:/JavaProgram/.metadata/.plugins/org.eclipse.wst.server.core/tmp1/wtpwebapps/FileUpdateAndDownload/WEB-INF/lib/struts-core-1.3.10.jar!/org/apache/struts/chain/chain-config.xml ``` 我的struts-config.xml配置如下: ``` <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE struts-config PUBLIC "-Apache Software Foundation//DTD struts Configuration 1.3//EN" "http://struts.apache.org/dtds/struts-config_1_3.dtd"> <struts-config> <!-- 配置表单 --> <form-beans> <form-bean name="loginForm" type="com.shizongger.web.form.LoginForm" /> </form-beans> <!-- 配置action --> <action-mappings> <action path="/login" name="loginForm" type="com.shizongger.web.action.LoginAction" > <forward name="success" path="WEB-INF/users/main.jsp" /> <forward name="fail" path="WEB-INF/users/login.jsp" /> </action> </action-mappings> </struts-config> ``` web.xml配置如下: ``` <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5"> <welcome-file-list> <welcome-file>index.jsp</welcome-file> </welcome-file-list> <servlet> <servlet-name>action</servlet-name> <servlet-class>org.apache.struts.action.ActionServlet</servlet-class> <init-param> <param-name>config</param-name> <param-value>/WEB-INF/config/struts-config.xml</param-value> </init-param> <load-on-startup>0</load-on-startup> </servlet> <servlet-mapping> <servlet-name>action</servlet-name> <url-pattern>*.do</url-pattern> </servlet-mapping> </web-app> ```
tomact 启动出问题 求解决
本人用的是 tomact8,没有项目时候启动没有问题,add 项目时候说tomact启动失败。百度之后说项目里面的web.xml里面有配置的东西有问题。但是同一个项目在别的机器上面就可以跑,请问这个问题怎么解决。![图片说明](https://img-ask.csdn.net/upload/201703/20/1489995724_780835.png) 控制台报的错误信息: java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/loggingpaper]] 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:916) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/loggingpaper]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153) ... 6 more Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@41d3ad35] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4928) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5058) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) ... 6 more Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@59b93ae8] at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:136) at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:699) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147) ... 9 more Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: invalid LOC header (bad signature) at org.apache.catalina.webresources.JarResourceSet.initInternal(JarResourceSet.java:96) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102) ... 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.JarResourceSet.initInternal(JarResourceSet.java:94) ... 13 more
IntelliJ idea Web项目配置问题(JDBC驱动注册失败)
今天想要把开发工具从Eclipse换成Intellij idea。于是把一个在Eclipse中开发的项目导入到了idea。各种配置完之后,项目可以启动,可以打开主页,但是无法登陆系统。控制台打印JDBC驱动注册失败,如图。请问这个问题怎么解决啊!各位大哥帮帮忙,小弟谢过啦! ![图片说明](https://img-ask.csdn.net/upload/201707/07/1499410224_172849.png) ![图片说明](https://img-ask.csdn.net/upload/201707/07/1499410236_207775.png) ![图片说明](https://img-ask.csdn.net/upload/201707/07/1499410249_960795.png) 另外数据库连接是没问题的。在Eclipse中启动也没有问题
OpenOffice 服务连接失败
java.net.ConnectException: connection failed: socket,host=127.0.0.1,port=8100,tcpNoDelay=1: 在做word转换的时候,使用代码 String command = OpenOffice_HOME + "OpenOffice\\program\\soffice.exe -headless -accept=\"socket,host=127.0.0.1,port=8100;urp;\" -nofirststartwizard"; System.out.println(command); Process pro = Runtime.getRuntime().exec(command); // 端口号8100 --链接 OpenOfficeConnection connection = new SocketOpenOfficeConnection("127.0.0.1", 8100); connection.connect(); // convert DocumentConverter converter = new OpenOfficeDocumentConverter(connection); converter.convert(docFile, pdfFile); // close the connection connection.disconnect(); 转换文档的时候,连接失败,我在另一台电脑上启动项目后,可以正常转换,怎么解决这个错误。
如果解决打开多个进程失败的问题?
在Linux系统下使用QT进行项目编程出现以下问题: 主程序启动之后需要启动若干个进程,多个进程之间使用socket进行通信。 当打开的进程数量达到一定数值之后,再打开新的进程时可以得到相应的进程编号,但却查询不到相应的进程,请问各位大神指教!
eclipse启动动态项目run on server,tomcat起不来
小白一枚,跪求大神解答,eclipse启动动态项目run on server,tomcat起不来,请问这个情况如何解决 控制台信息如下: 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Server.服务器版本: Apache Tomcat/9.0.19 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Server.构建: Apr 12 2019 14:22:48 UTC 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Server version number: 9.0.19.0 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: OS Name: Windows 7 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: OS.版本: 6.1 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: 结.造: amd64 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Java 环境变量: C:\Program Files\Java\jre1.8.0_73 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: JVM 版本: 1.8.0_73-b02 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: JVM.供应商: Oracle Corporation 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: CATALINA_BASE: E:\workspace\program\.metadata\.plugins\org.eclipse.wst.server.core\tmp1 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: CATALINA_HOME: D:\apache-tomcat-9.0.19 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Command line argument: -Dcatalina.base=E:\workspace\program\.metadata\.plugins\org.eclipse.wst.server.core\tmp1 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Command line argument: -Dcatalina.home=D:\apache-tomcat-9.0.19 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Command line argument: -Dwtp.deploy=E:\workspace\program\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Command line argument: -Djava.endorsed.dirs=D:\apache-tomcat-9.0.19\endorsed 十二月 04, 2019 10:34:27 下午 org.apache.catalina.startup.VersionLoggerListener log 信息: Command line argument: -Dfile.encoding=GBK 十二月 04, 2019 10:34:27 下午 org.apache.catalina.core.AprLifecycleListener lifecycleEvent 信息: Loaded APR based Apache Tomcat Native library [1.2.21] using APR version [1.6.5]. 十二月 04, 2019 10:34:27 下午 org.apache.catalina.core.AprLifecycleListener lifecycleEvent 信息: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 十二月 04, 2019 10:34:27 下午 org.apache.catalina.core.AprLifecycleListener lifecycleEvent 信息: APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] 十二月 04, 2019 10:34:27 下午 org.apache.catalina.core.AprLifecycleListener initializeSSL 信息: OpenSSL successfully initialized [OpenSSL 1.1.1a 20 Nov 2018] 十二月 04, 2019 10:34:28 下午 org.apache.coyote.AbstractProtocol init 信息: 初始化协议处理器 ["http-nio-8080"] 十二月 04, 2019 10:35:10 下午 org.apache.catalina.util.LifecycleBase handleSubClassException 严重: 初始化组件[Connector[HTTP/1.1-8080]]失败。 org.apache.catalina.LifecycleException: Protocol handler initialization failed at org.apache.catalina.connector.Connector.initInternal(Connector.java:983) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.core.StandardService.initInternal(StandardService.java:535) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:1059) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.startup.Catalina.load(Catalina.java:584) at org.apache.catalina.startup.Catalina.load(Catalina.java:607) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:306) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:491) Caused by: java.io.IOException: Unable to establish loopback connection at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source) at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.nio.ch.PipeImpl.<init>(Unknown Source) at sun.nio.ch.SelectorProviderImpl.openPipe(Unknown Source) at java.nio.channels.Pipe.open(Unknown Source) at sun.nio.ch.WindowsSelectorImpl.<init>(Unknown Source) at sun.nio.ch.WindowsSelectorProvider.openSelector(Unknown Source) at java.nio.channels.Selector.open(Unknown Source) at org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector(NioSelectorPool.java:54) at org.apache.tomcat.util.net.NioSelectorPool.close(NioSelectorPool.java:109) at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:341) at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1121) at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1129) at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:557) at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:74) at org.apache.catalina.connector.Connector.initInternal(Connector.java:980) ... 13 more Caused by: java.net.ConnectException: Connection timed out: connect at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.SocketChannelImpl.connect(Unknown Source) at java.nio.channels.SocketChannel.open(Unknown Source) at sun.nio.ch.PipeImpl$Initializer$LoopbackConnector.run(Unknown Source) ... 30 more 十二月 04, 2019 10:35:10 下午 org.apache.coyote.AbstractProtocol init 信息: 初始化协议处理器 ["ajp-nio-8009"] 十二月 04, 2019 10:35:52 下午 org.apache.catalina.util.LifecycleBase handleSubClassException 严重: 初始化组件[Connector[AJP/1.3-8009]]失败。 org.apache.catalina.LifecycleException: Protocol handler initialization failed at org.apache.catalina.connector.Connector.initInternal(Connector.java:983) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.core.StandardService.initInternal(StandardService.java:535) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:1059) at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136) at org.apache.catalina.startup.Catalina.load(Catalina.java:584) at org.apache.catalina.startup.Catalina.load(Catalina.java:607) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:306) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:491) Caused by: java.io.IOException: Unable to establish loopback connection at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source) at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.nio.ch.PipeImpl.<init>(Unknown Source) at sun.nio.ch.SelectorProviderImpl.openPipe(Unknown Source) at java.nio.channels.Pipe.open(Unknown Source) at sun.nio.ch.WindowsSelectorImpl.<init>(Unknown Source) at sun.nio.ch.WindowsSelectorProvider.openSelector(Unknown Source) at java.nio.channels.Selector.open(Unknown Source) at org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector(NioSelectorPool.java:54) at org.apache.tomcat.util.net.NioSelectorPool.close(NioSelectorPool.java:109) at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:341) at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1121) at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1129) at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:557) at org.apache.catalina.connector.Connector.initInternal(Connector.java:980) ... 13 more Caused by: java.net.ConnectException: Connection timed out: connect at sun.nio.ch.Net.connect0(Native Method) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.Net.connect(Unknown Source) at sun.nio.ch.SocketChannelImpl.connect(Unknown Source) at java.nio.channels.SocketChannel.open(Unknown Source) at sun.nio.ch.PipeImpl$Initializer$LoopbackConnector.run(Unknown Source) ... 29 more 十二月 04, 2019 10:35:52 下午 org.apache.catalina.startup.Catalina load 信息: 服务器在[85,235]毫秒内初始化 十二月 04, 2019 10:35:52 下午 org.apache.catalina.core.StandardService startInternal 信息: Starting service [Catalina] 十二月 04, 2019 10:35:52 下午 org.apache.catalina.core.StandardEngine startInternal 信息: Starting Servlet engine: [Apache Tomcat/9.0.19] 十二月 04, 2019 10:35:53 下午 org.apache.catalina.util.SessionIdGeneratorBase createSecureRandom 警告: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [557] milliseconds. 十二月 04, 2019 10:35:53 下午 org.apache.jasper.servlet.TldScanner scanJars 信息: 至少有一个JAR被扫描用于TLD但尚未包含TLD。 为此记录器启用调试日志记录,以获取已扫描但未在其中找到TLD的完整JAR列表。 在扫描期间跳过不需要的JAR可以缩短启动时间和JSP编译时间。 十二月 04, 2019 10:35:53 下午 org.apache.catalina.startup.Catalina start 信息: Server startup in [1,428] milliseconds
docker -v 挂载目录, 宿主机上个别目录挂载失败无报错
1. 项目原来是放在/home目录下, 日志要挂载,以便在宿主机可以实时查看日志, docker 启动命令: docker run -it -d --name test -p 27015:80 --restart=always -v / home/service/log:/usr/src/app/data/log test_ser:0.1 2. 把项目换了个路径,放到了/webapp下, docker 启动命令: docker run -it -d --name test -p 27015:80 --restart=always -v /webapp/service/log:/usr/src/app/data/log test_ser:0.1 启动过程和容器里日志没有可见的错误. 3. 只是换了个目录,结果死活挂载不成功. 多方查询无果. drwxr-xr-x. 28 root root 4096 Dec 30 23:34 home drwxr-xr-x 40 root root 4096 Jan 6 18:53 webapp 4. webapp是外部硬盘挂载,不过这种情况docker 是可以支持的. /dev/mapper/datavg-datalv 500G 106G 394G 22% /webapp 5. 现在的问题是 宿主机上别的目录docker 挂载没问题,就这个/webapp目录挂载不起作用. ![图片说明](https://img-ask.csdn.net/upload/202001/09/1578550264_891314.png) ![图片说明](https://img-ask.csdn.net/upload/202001/09/1578550281_998106.png) ![图片说明](https://img-ask.csdn.net/upload/202001/09/1578550462_576120.png) 请问有没有人遇到过这样的问题?有解决方法么?
SSM项目,启用service注解失败
我是一个新手,写一个项目,用git和maven搭了个SSM框架,启动tomcat的时候报这个错误,可是service接口里,却一点错误没有,请教大神怎么解决![这是错误信息](https://img-ask.csdn.net/upload/201612/16/1481898669_439279.jpg) ![图片说明](https://img-ask.csdn.net/upload/201612/16/1481898703_223163.jpg) ![![图片说明](https://img-ask.csdn.net/upload/201612/16/1481898758_986884.jpg)
装完VS2010出现了问题
曾经装了vs2012,后来删除掉,又装20010,有问题,现在重新装2012的时候不知什么原因打不开.exe文件了,最后还是选择装2010,装好后出现1>------ 已启动生成: 项目: 123, 配置: Debug Win32 ------ 1>生成启动时间为 2015/10/5 11:38:11。 1>InitializeBuildStatus: 1> 正在对“Debug\123.unsuccessfulbuild”执行 Touch 任务。 1>ClCompile: 1> 所有输出均为最新。 1> 所有输出均为最新。 1>ResourceCompile: 1> 所有输出均为最新。 1>LINK : fatal error LNK1123: 转换到 COFF 期间失败: 文件无效或损坏 1> 1>生成失败。 1> 1>已用时间 00:00:00.38 ========== 生成: 成功 0 个,失败 1 个,最新 0 个,跳过 0 个 ========== 根据网友的解答方案,把网上有的什么VS2010在经历一些更新后,建立Win32 Console Project时会出“error LNK1123” 错误,解决方案为: 将 项目|项目属性|配置属性|清单工具|输入和输出|嵌入清单 “是”改为“否”即可,但是每新建一个项目都要这样设置一次。 若按照上面解决方案依然发生“error LNK1123”错误,解决方案如下: 在电脑中搜索查看是否有多个cvtres.exe。 比如其中: 一个是C:\Program Files(x86)\Microsoft Visual Studio 10.0\vc\bin\cvtres.exe 一个是C:\Windows\Microsoft.NET\Framework\v4.0.30319\cvtres.exe。 右键属性|详细信息 查看两者版本号,删除/重命名较旧的版本,或者重新设置Path变量。 注意:此方法为治本的办法,删除旧版本的cvtres.exe后,就不需要每次都设置配置了。 这些都用了,都不行,现在想问是不是当初删2012的时候把C盘的本来重要的东西删了,还有什么可能
求助!!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)
求java大神帮忙解决问题
新手碰到奇葩问题了,就是启动本地项目后输入本地的地址访问项目实现上传照片,无论照片多大都能上传,但是我去访问服务器的外网项目时上传照片,照片的大小应该是超过50kb(感觉50kb大小的样子)就上传失败,小于50kb就能成功,为什么超过了就失败呢,什么提示都没有直接无法显示该页面,如图: ![图片说明](https://img-ask.csdn.net/upload/201606/07/1465280663_296469.png) tomcat看了并没有设置上传照片的大小,struts2也是没有限制上传照片的大小, 请问会不会是上传照片请求时间长了引起的呢,感觉等待时间也不长啊,有没有大神给指点下是怎么回事啊
mfc : error PRJ0015 : vs2008
# vs2008 mfc : error PRJ0015 : 您的系统缺少 NULL 设备。无法启动生成。 项目生成时出现如下错误: 1>------ 已启动全部重新生成: 项目: DanTest01, 配置: Debug Win32 ------ 1>正在删除项目“DanTest01”(配置“Debug|Win32”)的中间文件和输出文件 1>项目 : error PRJ0015 : 您的系统缺少 NULL 设备。无法启动生成。 1>生成日志保存在“file://c:\Users\qingchen\Documents\Visual Studio 2008\Projects\DanTest01\DanTest01\Debug\BuildLog.htm” 1>DanTest01 - 1 个错误,0 个警告 ========== 全部重新生成: 成功 0 个,失败 1 个,跳过 0 个 ========== 工具是vs2008,做的mfc单文档,前天还可以,今天突然出现着个错误,所有的项目都不能生成,重新安装了vs2008也没有解决,查了半天没搞清楚怎么回事?请教高手指点,谢谢
caffe生成解决方案时出错
编译环境:win10 vs2017 15.5.6 boost_1_70_0 主要报错: Unknown compiler version - please run the configure tests and report the results 再次点生成解决方案时的主要报错: for each 语句不能在“std::array *”类型的变量上操作 ; “std::array”: 模板 参数太少 ; 无法打开文件“libboost_date_time-vc140-mt-gd-1_59.lib” 等等; 因为只能一条条复制,所以如有需要,可提供详细错误; 下面是重新生成解决方案的具体报错,有大佬来救救我吗,感激不尽!需要更详细信息可以直说。 报错:1>------ 已启动全部重新生成: 项目: libcaffe, 配置: Debug x64 ------ 1>ProtoCompile.cmd : Create proto temp directory "C:\Users\Kay Chow\Documents\caffe-master\windows\..\src\caffe\proto\temp" 1>ProtoCompile.cmd : Generating "C:\Users\Kay Chow\Documents\caffe-master\windows\..\src\caffe\proto\temp\caffe.pb.h" and "C:\Users\Kay Chow\Documents\caffe-master\windows\..\src\caffe\proto\temp\caffe.pb.cc" 1>ProtoCompile.cmd : Create proto include directory 1>子目录或文件 C:\Users\Kay Chow\Documents\caffe-master\windows\..\include\caffe\proto 已经存在。 1>ProtoCompile.cmd : Compare newly compiled caffe.pb.h with existing one 1>blob.cpp 1>common.cpp 1>data_reader.cpp 1>data_transformer.cpp 1>internal_thread.cpp 1>layer.cpp 1>absval_layer.cpp 1>accuracy_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>argmax_layer.cpp 1>base_conv_layer.cpp 1>base_data_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>batch_norm_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>batch_reindex_layer.cpp 1>bias_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>bnll_layer.cpp 1>box_annotator_ohem_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>concat_layer.cpp 1>contrastive_loss_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>conv_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>crop_layer.cpp 1>cudnn_conv_layer.cpp 1>cudnn_lcn_layer.cpp 1>cudnn_lrn_layer.cpp 1>cudnn_pooling_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>cudnn_relu_layer.cpp 1>cudnn_sigmoid_layer.cpp 1>cudnn_softmax_layer.cpp 1>cudnn_tanh_layer.cpp 1>data_layer.cpp 1>deconv_layer.cpp 1>dropout_layer.cpp 1>dummy_data_layer.cpp 1>eltwise_layer.cpp 1>elu_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>embed_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>euclidean_loss_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>exp_layer.cpp 1>filter_layer.cpp 1>flatten_layer.cpp 1>hdf5_data_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>hdf5_output_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>hinge_loss_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>im2col_layer.cpp 1>image_data_layer.cpp 1>infogain_loss_layer.cpp 1>inner_product_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>input_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>log_layer.cpp 1>loss_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>lrn_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>memory_data_layer.cpp 1>multinomial_logistic_loss_layer.cpp 1>mvn_layer.cpp 1>neuron_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>parameter_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>pooling_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>power_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>prelu_layer.cpp 1>psroi_pooling_layer.cpp 1>reduction_layer.cpp 1>relu_layer.cpp 1>reshape_layer.cpp 1>scale_layer.cpp 1>sigmoid_cross_entropy_loss_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>sigmoid_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>silence_layer.cpp 1>slice_layer.cpp 1>smooth_l1_loss_layer.cpp 1>smooth_L1_loss_ohem_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>softmax_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>softmax_loss_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>softmax_loss_ohem_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>split_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>spp_layer.cpp 1>tanh_layer.cpp 1>threshold_layer.cpp 1>tile_layer.cpp 1>window_data_layer.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>layer_factory.cpp 1>net.cpp 1>parallel.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>caffe.pb.cc 1>solver.cpp 1>adadelta_solver.cpp 1>adagrad_solver.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>adam_solver.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>nesterov_solver.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>rmsprop_solver.cpp 1>sgd_solver.cpp 1>syncedmem.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>benchmark.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>blocking_queue.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>cudnn.cpp 1>db.cpp 1>db_leveldb.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>db_lmdb.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>hdf5.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>im2col.cpp 1>insert_splits.cpp 1>io.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>math_functions.cpp 1>signal_handler.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>upgrade_proto.cpp 1>Unknown compiler version - please run the configure tests and report the results 1>Unknown compiler version - please run the configure tests and report the results 1>libcaffe.vcxproj -> C:\Users\Kay Chow\Documents\caffe-master\windows\..\Build\x64\Debug\libcaffe.lib 1>BinplaceCudaDependencies : CPU only build, don't copy cuda dependencies. 2>------ 已启动全部重新生成: 项目: caffe, 配置: Debug x64 ------ 3>------ 已启动全部重新生成: 项目: caffe.managed, 配置: Debug x64 ------ 4>------ 已启动全部重新生成: 项目: convert_cifar_data, 配置: Debug x64 ------ 5>------ 已启动全部重新生成: 项目: classification, 配置: Debug x64 ------ 6>------ 已启动全部重新生成: 项目: convert_mnist_data, 配置: Debug x64 ------ 7>------ 已启动全部重新生成: 项目: convert_mnist_siamese_data, 配置: Debug x64 ------ 8>------ 已启动全部重新生成: 项目: upgrade_net_proto_binary, 配置: Debug x64 ------ 9>------ 已启动全部重新生成: 项目: upgrade_net_proto_text, 配置: Debug x64 ------ 2>caffe.cpp 9>upgrade_net_proto_text.cpp 2>Unknown compiler version - please run the configure tests and report the results 4>convert_cifar_data.cpp 3>Stdafx.cpp 9>Unknown compiler version - please run the configure tests and report the results 5>classification.cpp 6>convert_mnist_data.cpp 7>convert_mnist_siamese_data.cpp 4>Unknown compiler version - please run the configure tests and report the results 5>Unknown compiler version - please run the configure tests and report the results 8>upgrade_net_proto_binary.cpp 6>Unknown compiler version - please run the configure tests and report the results 8>Unknown compiler version - please run the configure tests and report the results 7>Unknown compiler version - please run the configure tests and report the results 3>AssemblyInfo.cpp 3>caffelib.cpp 3>caffelib.cpp(61): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(62): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(62): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(68): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(68): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(68): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(69): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(69): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(127): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(128): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(128): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(136): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(136): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(136): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(137): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(137): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(64): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(64): error C2027: 使用了未定义类型“std::array” 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(64): error C3536: “outputs”: 初始化之前无法使用 3>caffelib.cpp(64): error C2109: 下标要求数组或指针类型 3>caffelib.cpp(65): error C2440: “return”: 无法从“int”转换为“std::array *” 3>caffelib.cpp(65): note: 从整型转换为指针类型要求 reinterpret_cast、C 样式转换或函数样式转换 3>caffelib.cpp(71): error C3285: for each 语句不能在“std::array *”类型的变量上操作 3>caffelib.cpp(72): error C2065: “name”: 未声明的标识符 3>caffelib.cpp(74): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(74): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(74): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(74): error C2027: 使用了未定义类型“std::array” 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(78): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(78): error C2027: 使用了未定义类型“std::array” 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(78): error C3536: “values”: 初始化之前无法使用 3>caffelib.cpp(78): error C2109: 下标要求数组或指针类型 3>caffelib.cpp(79): error C3536: “outputs”: 初始化之前无法使用 3>caffelib.cpp(79): error C2109: 下标要求数组或指针类型 3>caffelib.cpp(81): error C2440: “return”: 无法从“int”转换为“std::array *” 3>caffelib.cpp(81): note: 从整型转换为指针类型要求 reinterpret_cast、C 样式转换或函数样式转换 3>caffelib.cpp(132): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(132): error C2027: 使用了未定义类型“std::array” 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(132): error C3536: “outputs”: 初始化之前无法使用 3>caffelib.cpp(132): error C2109: 下标要求数组或指针类型 3>caffelib.cpp(133): error C2440: “return”: 无法从“int”转换为“std::array *” 3>caffelib.cpp(133): note: 从整型转换为指针类型要求 reinterpret_cast、C 样式转换或函数样式转换 3>caffelib.cpp(141): error C3285: for each 语句不能在“std::array *”类型的变量上操作 3>caffelib.cpp(142): error C2065: “name”: 未声明的标识符 3>caffelib.cpp(144): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(144): error C3699: “^”: 不能在类型“std::array”上使用此间接寻址 3>caffelib.cpp(144): note: 编译器将“^”替换为“*”以继续进行分析 3>caffelib.cpp(144): error C2027: 使用了未定义类型“std::array” 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(148): error C2976: “std::array”: 模板 参数太少 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(148): error C2027: 使用了未定义类型“std::array” 3>D:\VS2017\VC\Tools\MSVC\14.12.25827\include\utility(474): note: 参见“std::array”的声明 3>caffelib.cpp(148): error C3536: “values”: 初始化之前无法使用 3>caffelib.cpp(148): error C2109: 下标要求数组或指针类型 3>caffelib.cpp(149): error C3536: “outputs”: 初始化之前无法使用 3>caffelib.cpp(149): error C2109: 下标要求数组或指针类型 3>caffelib.cpp(151): error C2440: “return”: 无法从“int”转换为“std::array *” 3>caffelib.cpp(151): note: 从整型转换为指针类型要求 reinterpret_cast、C 样式转换或函数样式转换 3>已完成生成项目“caffe.managed.vcxproj”的操作 - 失败。 4>LINK : fatal error LNK1104: 无法打开文件“libboost_thread-vc140-mt-gd-1_59.lib” 10>------ 已启动全部重新生成: 项目: upgrade_solver_proto_text, 配置: Debug x64 ------ 4>已完成生成项目“convert_cifar_data.vcxproj”的操作 - 失败。 6>LINK : fatal error LNK1104: 无法打开文件“libboost_thread-vc140-mt-gd-1_59.lib” 6>已完成生成项目“convert_mnist_data.vcxproj”的操作 - 失败。 10>upgrade_solver_proto_text.cpp 7>LINK : fatal error LNK1104: 无法打开文件“libboost_thread-vc140-mt-gd-1_59.lib” 7>已完成生成项目“convert_mnist_siamese_data.vcxproj”的操作 - 失败。 10>Unknown compiler version - please run the configure tests and report the results 9>LINK : fatal error LNK1104: 无法打开文件“libboost_date_time-vc140-mt-gd-1_59.lib” 9>已完成生成项目“upgrade_net_proto_text.vcxproj”的操作 - 失败。 8>LINK : fatal error LNK1104: 无法打开文件“libboost_date_time-vc140-mt-gd-1_59.lib” 8>已完成生成项目“upgrade_net_proto_binary.vcxproj”的操作 - 失败。 5>LINK : fatal error LNK1104: 无法打开文件“libboost_date_time-vc140-mt-gd-1_59.lib” 5>已完成生成项目“classification.vcxproj”的操作 - 失败。 2>LINK : fatal error LNK1104: 无法打开文件“libboost_date_time-vc140-mt-gd-1_59.lib” 2>已完成生成项目“caffe.vcxproj”的操作 - 失败。 11>------ 已启动全部重新生成: 项目: compute_image_mean, 配置: Debug x64 ------ 12>------ 已启动全部重新生成: 项目: convert_imageset, 配置: Debug x64 ------ 13>------ 已启动全部重新生成: 项目: extract_features, 配置: Debug x64 ------ 14>------ 已启动全部重新生成: 项目: test_all, 配置: Debug x64 ------ 15>------ 已启动全部重新生成: 项目: pycaffe, 配置: Debug x64 ------ 16>------ 已启动全部重新生成: 项目: matcaffe, 配置: Debug x64 ------ 15>Skipping project pycaffe, Python support is not enabled in CommonSettings.props. 16>Skipping project matcaffe, Matlab support is not enabled in CommonSettings.props. 12>convert_imageset.cpp 11>compute_image_mean.cpp 13>extract_features.cpp 14>test_accuracy_layer.cpp 14>test_argmax_layer.cpp 14>test_batch_norm_layer.cpp 14>test_batch_reindex_layer.cpp 14>test_benchmark.cpp 14>test_bias_layer.cpp 14>test_blob.cpp 14>test_caffe_main.cpp 14>Unknown compiler version - please run the configure tests and report the results 13>Unknown compiler version - please run the configure tests and report the results 12>Unknown compiler version - please run the configure tests and report the results 11>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 10>LINK : fatal error LNK1104: 无法打开文件“libboost_date_time-vc140-mt-gd-1_59.lib” 10>已完成生成项目“upgrade_solver_proto_text.vcxproj”的操作 - 失败。 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 11>LINK : fatal error LNK1104: 无法打开文件“libboost_filesystem-vc140-mt-gd-1_59.lib” 11>已完成生成项目“compute_image_mean.vcxproj”的操作 - 失败。 12>LINK : fatal error LNK1104: 无法打开文件“libboost_filesystem-vc140-mt-gd-1_59.lib” 12>已完成生成项目“convert_imageset.vcxproj”的操作 - 失败。 13>LINK : fatal error LNK1104: 无法打开文件“libboost_filesystem-vc140-mt-gd-1_59.lib” 13>已完成生成项目“extract_features.vcxproj”的操作 - 失败。 14>test_common.cpp 14>test_concat_layer.cpp 14>test_contrastive_loss_layer.cpp 14>test_convolution_layer.cpp 14>test_crop_layer.cpp 14>test_data_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_data_transformer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_db.cpp 14>test_deconvolution_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_dummy_data_layer.cpp 14>test_eltwise_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_embed_layer.cpp 14>test_euclidean_loss_layer.cpp 14>test_filler.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_filter_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_flatten_layer.cpp 14>test_gradient_based_solver.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_hdf5data_layer.cpp 14>test_hdf5_output_layer.cpp 14>test_hinge_loss_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_im2col_layer.cpp 14>test_image_data_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_infogain_loss_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_inner_product_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_internal_thread.cpp 14>test_io.cpp 14>test_layer_factory.cpp 14>test_lrn_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_math_functions.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_maxpool_dropout_layers.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_memory_data_layer.cpp 14>test_multinomial_logistic_loss_layer.cpp 14>test_mvn_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_net.cpp 14>test_neuron_layer.cpp 14>test_platform.cpp 14>test_pooling_layer.cpp 14>test_power_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_protobuf.cpp 14>test_random_number_generator.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_reduction_layer.cpp 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(1010): error C2220: 警告被视为错误 - 没有生成“object”文件 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(992): note: 编译 类 模板 成员函数 "void caffe::NetTest_TestLossWeightMidNet_Test<T>::TestBody(void)" 时 14> with 14> [ 14> T=Type 14> ] 14>c:\users\kay chow\documents\caffe-master\src\gtest\gtest.h(7341): note: 参见对正在编译的 类 模板 实例化 "caffe::NetTest_TestLossWeightMidNet_Test<T>" 的引用 14> with 14> [ 14> T=Type 14> ] (编译源文件 ..\..\src\caffe\test\test_net.cpp) 14>c:\users\kay chow\documents\caffe-master\src\gtest\gtest.h(7327): note: 编译 类 模板 成员函数 "bool testing::internal::TypeParameterizedTest<caffe::NetTest,testing::internal::TemplateSel<caffe::NetTest_TestLossWeightMidNet_Test>,caffe::gtest_type_params_NetTest_>::Register(const char *,const char *,const char *,int)" 时 (编译源文件 ..\..\src\caffe\test\test_net.cpp) 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(992): note: 参见对正在编译的函数 模板 实例化“bool testing::internal::TypeParameterizedTest<caffe::NetTest,testing::internal::TemplateSel<caffe::NetTest_TestLossWeightMidNet_Test>,caffe::gtest_type_params_NetTest_>::Register(const char *,const char *,const char *,int)”的引用 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(992): note: 参见对正在编译的 类 模板 实例化 "testing::internal::TypeParameterizedTest<caffe::NetTest,testing::internal::TemplateSel<caffe::NetTest_TestLossWeightMidNet_Test>,caffe::gtest_type_params_NetTest_>" 的引用 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(1010): warning C4838: 从“double”转换到“Dtype”需要收缩转换 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(961): warning C4838: 从“double”转换到“Dtype”需要收缩转换 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(941): note: 编译 类 模板 成员函数 "void caffe::NetTest_TestLossWeight_Test<T>::TestBody(void)" 时 14> with 14> [ 14> T=Type 14> ] 14>c:\users\kay chow\documents\caffe-master\src\gtest\gtest.h(7341): note: 参见对正在编译的 类 模板 实例化 "caffe::NetTest_TestLossWeight_Test<T>" 的引用 14> with 14> [ 14> T=Type 14> ] (编译源文件 ..\..\src\caffe\test\test_net.cpp) 14>c:\users\kay chow\documents\caffe-master\src\gtest\gtest.h(7327): note: 编译 类 模板 成员函数 "bool testing::internal::TypeParameterizedTest<caffe::NetTest,testing::internal::TemplateSel<caffe::NetTest_TestLossWeight_Test>,caffe::gtest_type_params_NetTest_>::Register(const char *,const char *,const char *,int)" 时 (编译源文件 ..\..\src\caffe\test\test_net.cpp) 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(941): note: 参见对正在编译的函数 模板 实例化“bool testing::internal::TypeParameterizedTest<caffe::NetTest,testing::internal::TemplateSel<caffe::NetTest_TestLossWeight_Test>,caffe::gtest_type_params_NetTest_>::Register(const char *,const char *,const char *,int)”的引用 14>c:\users\kay chow\documents\caffe-master\src\caffe\test\test_net.cpp(941): note: 参见对正在编译的 类 模板 实例化 "testing::internal::TypeParameterizedTest<caffe::NetTest,testing::internal::TemplateSel<caffe::NetTest_TestLossWeight_Test>,caffe::gtest_type_params_NetTest_>" 的引用 14>test_reshape_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_scale_layer.cpp 14>test_sigmoid_cross_entropy_loss_layer.cpp 14>test_slice_layer.cpp 14>test_softmax_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_softmax_with_loss_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_solver.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_solver_factory.cpp 14>test_split_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_spp_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_stochastic_pooling.cpp 14>test_syncedmem.cpp 14>test_tanh_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_threshold_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>Unknown compiler version - please run the configure tests and report the results 14>test_tile_layer.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>test_upgrade_proto.cpp 14>test_util_blas.cpp 14>gtest-all.cpp 14>Unknown compiler version - please run the configure tests and report the results 14>已完成生成项目“test_all.vcxproj”的操作 - 失败。 ========== 全部重新生成: 成功 3 个,失败 13 个,跳过 0 个 ==========
在VS2.17配置PCL1.9.0,出现 LINK : fatal error LNK1181: 无法打开输入文件“cmake.obj”
按照 这篇博文 配置的 PCL1.9.0 https://blog.csdn.net/weixin_41991128/article/details/83864713#1_43 但是建立工程进行编译时,出现如下错误: 1>------ 已启动全部重新生成: 项目: Project3, 配置: Release x64 ------ 1>main.cpp **1>LINK : fatal error LNK1181: 无法打开输入文件“cmake.obj”** 1>已完成生成项目“Project3.vcxproj”的操作 - 失败。 ========== 全部重新生成: 成功 0 个,失败 1 个,跳过 0 个 ========== 目前还没有找到解决问题的方法,还请各位大神 路过时 留意一下,恳请指导一下,谢谢!
动态规划入门到熟悉,看不懂来打我啊
持续更新。。。。。。 2.1斐波那契系列问题 2.2矩阵系列问题 2.3跳跃系列问题 3.1 01背包 3.2 完全背包 3.3多重背包 3.4 一些变形选讲 2.1斐波那契系列问题 在数学上,斐波纳契数列以如下被以递归的方法定义:F(0)=0,F(1)=1, F(n)=F(n-1)+F(n-2)(n&gt;=2,n∈N*)根据定义,前十项为1, 1, 2, 3...
Java学习的正确打开方式
在博主认为,对于入门级学习java的最佳学习方法莫过于视频+博客+书籍+总结,前三者博主将淋漓尽致地挥毫于这篇博客文章中,至于总结在于个人,实际上越到后面你会发现学习的最好方式就是阅读参考官方文档其次就是国内的书籍,博客次之,这又是一个层次了,这里暂时不提后面再谈。博主将为各位入门java保驾护航,各位只管冲鸭!!!上天是公平的,只要不辜负时间,时间自然不会辜负你。 何谓学习?博主所理解的学习,它是一个过程,是一个不断累积、不断沉淀、不断总结、善于传达自己的个人见解以及乐于分享的过程。
程序员必须掌握的核心算法有哪些?
由于我之前一直强调数据结构以及算法学习的重要性,所以就有一些读者经常问我,数据结构与算法应该要学习到哪个程度呢?,说实话,这个问题我不知道要怎么回答你,主要取决于你想学习到哪些程度,不过针对这个问题,我稍微总结一下我学过的算法知识点,以及我觉得值得学习的算法。这些算法与数据结构的学习大多数是零散的,并没有一本把他们全部覆盖的书籍。下面是我觉得值得学习的一些算法以及数据结构,当然,我也会整理一些看过...
Python——画一棵漂亮的樱花树(不同种樱花+玫瑰+圣诞树喔)
最近翻到一篇知乎,上面有不少用Python(大多是turtle库)绘制的树图,感觉很漂亮,我整理了一下,挑了一些我觉得不错的代码分享给大家(这些我都测试过,确实可以生成) one 樱花树 动态生成樱花 效果图(这个是动态的): 实现代码 import turtle as T import random import time # 画樱花的躯干(60,t) def Tree(branch, ...
大学四年自学走来,这些私藏的实用工具/学习网站我贡献出来了
大学四年,看课本是不可能一直看课本的了,对于学习,特别是自学,善于搜索网上的一些资源来辅助,还是非常有必要的,下面我就把这几年私藏的各种资源,网站贡献出来给你们。主要有:电子书搜索、实用工具、在线视频学习网站、非视频学习网站、软件下载、面试/求职必备网站。 注意:文中提到的所有资源,文末我都给你整理好了,你们只管拿去,如果觉得不错,转发、分享就是最大的支持了。 一、电子书搜索 对于大部分程序员...
shell脚本:备份数据库、代码上线
备份MySQL数据库 场景: 一台MySQL服务器,跑着5个数据库,在没有做主从的情况下,需要对这5个库进行备份 需求: 1)每天备份一次,需要备份所有的库 2)把备份数据存放到/data/backup/下 3)备份文件名称格式示例:dbname-2019-11-23.sql 4)需要对1天以前的所有sql文件压缩,格式为gzip 5)本地数据保留1周 6)需要把备份的数据同步到远程备份中心,假如...
如何安装 IntelliJ IDEA 最新版本——详细教程
IntelliJ IDEA 简称 IDEA,被业界公认为最好的 Java 集成开发工具,尤其在智能代码助手、代码自动提示、代码重构、代码版本管理(Git、SVN、Maven)、单元测试、代码分析等方面有着亮眼的发挥。IDEA 产于捷克,开发人员以严谨著称的东欧程序员为主。IDEA 分为社区版和付费版两个版本。 我呢,一直是 Eclipse 的忠实粉丝,差不多十年的老用户了。很早就接触到了 IDEA...
面试还搞不懂redis,快看看这40道面试题(含答案和思维导图)
Redis 面试题 1、什么是 Redis?. 2、Redis 的数据类型? 3、使用 Redis 有哪些好处? 4、Redis 相比 Memcached 有哪些优势? 5、Memcache 与 Redis 的区别都有哪些? 6、Redis 是单进程单线程的? 7、一个字符串类型的值能存储最大容量是多少? 8、Redis 的持久化机制是什么?各自的优缺点? 9、Redis 常见性...
为什么要推荐大家学习字节码?
配套视频: 为什么推荐大家学习Java字节码 https://www.bilibili.com/video/av77600176/ 一、背景 本文主要探讨:为什么要学习 JVM 字节码? 可能很多人会觉得没必要,因为平时开发用不到,而且不学这个也没耽误学习。 但是这里分享一点感悟,即人总是根据自己已经掌握的知识和技能来解决问题的。 这里有个悖论,有时候你觉得有些技术没用恰恰是...
【设计模式】单例模式的八种写法分析
网上泛滥流传单例模式的写法种类,有说7种的,也有说6种的,当然也不排除说5种的,他们说的有错吗?其实没有对与错,刨根问底,写法终究是写法,其本质精髓大体一致!因此完全没必要去追究写法的多少,有这个时间还不如跟着宜春去网吧偷耳机、去田里抓青蛙得了,一天天的....
《面试宝典》:检验是否为合格的初中级程序员的面试知识点,你都知道了吗?查漏补缺
欢迎关注文章系列,一起学习 《提升能力,涨薪可待篇》 《面试知识,工作可待篇》 《实战演练,拒绝996篇》 也欢迎关注公 众 号【Ccww笔记】,原创技术文章第一时间推出 如果此文对你有帮助、喜欢的话,那就点个赞呗,点个关注呗! 《面试知识,工作可待篇》-Java笔试面试基础知识大全 前言 是不是感觉找工作面试是那么难呢? 在找工作面试应在学习的基础进行总结面试知识点,工作也指日可待,欢...
在阿里,40岁的奋斗姿势
在阿里,40岁的奋斗姿势 在阿里,什么样的年纪可以称为老呢?35岁? 在云网络,有这样一群人,他们的平均年龄接近40,却刚刚开辟职业生涯的第二战场。 他们的奋斗姿势是什么样的呢? 洛神赋 “翩若惊鸿,婉若游龙。荣曜秋菊,华茂春松。髣髴兮若轻云之蔽月,飘飖兮若流风之回雪。远而望之,皎若太阳升朝霞;迫而察之,灼若芙蕖出渌波。” 爱洛神,爱阿里云 2018年,阿里云网络产品部门启动洛神2.0升...
【超详细分析】关于三次握手与四次挥手面试官想考我们什么?
在面试中,三次握手和四次挥手可以说是问的最频繁的一个知识点了,我相信大家也都看过很多关于三次握手与四次挥手的文章,今天的这篇文章,重点是围绕着面试,我们应该掌握哪些比较重要的点,哪些是比较被面试官给问到的,我觉得如果你能把我下面列举的一些点都记住、理解,我想就差不多了。 三次握手 当面试官问你为什么需要有三次握手、三次握手的作用、讲讲三次三次握手的时候,我想很多人会这样回答: 首先很多人会先讲下握...
压测学习总结(1)——高并发性能指标:QPS、TPS、RT、吞吐量详解
一、QPS,每秒查询 QPS:Queries Per Second意思是“每秒查询率”,是一台服务器每秒能够相应的查询次数,是对一个特定的查询服务器在规定时间内所处理流量多少的衡量标准。互联网中,作为域名系统服务器的机器的性能经常用每秒查询率来衡量。 二、TPS,每秒事务 TPS:是TransactionsPerSecond的缩写,也就是事务数/秒。它是软件测试结果的测量单位。一个事务是指一...
新程序员七宗罪
当我发表这篇文章《为什么每个工程师都应该开始考虑开发中的分析和编程技能呢?》时,我从未想到它会对读者产生如此积极的影响。那些想要开始探索编程和数据科学领域的人向我寻求建议;还有一些人问我下一篇文章的发布日期;还有许多人询问如何顺利过渡到这个职业。我非常鼓励大家继续分享我在这个旅程的经验,学习,成功和失败,以帮助尽可能多的人过渡到一个充满无数好处和机会的职业生涯。亲爱的读者,谢谢你。 -罗伯特。 ...
活到老,学到老,程序员也该如此
全文共2763字,预计学习时长8分钟 图片来源:Pixabay 此前,“网传阿里巴巴要求尽快实现P8全员35周岁以内”的消息闹得沸沸扬扬。虽然很快被阿里辟谣,但苍蝇不叮无缝的蛋,无蜜不招彩蝶蜂。消息从何而来?真相究竟怎样?我们无从而知。我们只知道一个事实:不知从何时开始,程序猿也被划在了“吃青春饭”行业之列。 饱受“996ICU”摧残后,好不容易“头秃了变强了”,即将步入为“高...
2019年Spring Boot面试都问了什么?快看看这22道面试题!
Spring Boot 面试题 1、什么是 Spring Boot? 2、Spring Boot 有哪些优点? 3、什么是 JavaConfig? 4、如何重新加载 Spring Boot 上的更改,而无需重新启动服务器? 5、Spring Boot 中的监视器是什么? 6、如何在 Spring Boot 中禁用 Actuator 端点安全性? 7、如何在自定义端口上运行 Sprin...
小白学 Python 爬虫(5):前置准备(四)数据库基础
人生苦短,我用 Python 前文传送门: 小白学 Python 爬虫(1):开篇 小白学 Python 爬虫(2):前置准备(一)基本类库的安装 小白学 Python 爬虫(3):前置准备(二)Linux基础入门 小白学 Python 爬虫(4):前置准备(三)Docker基础入门 本篇文章,我们接着介绍基础内容,数据库。 爬虫将数据爬取完成后,总要有地方存放吧,这个数据存在哪里呢? ...
面试官:关于Java性能优化,你有什么技巧
通过使用一些辅助性工具来找到程序中的瓶颈,然后就可以对瓶颈部分的代码进行优化。 一般有两种方案:即优化代码或更改设计方法。我们一般会选择后者,因为不去调用以下代码要比调用一些优化的代码更能提高程序的性能。而一个设计良好的程序能够精简代码,从而提高性能。 下面将提供一些在JAVA程序的设计和编码中,为了能够提高JAVA程序的性能,而经常采用的一些方法和技巧。 1.对象的生成和大小的调整。 J...
JavaScript 中, 5 种增加代码可读性的最佳实践
作者:Milos Protic 译者:前端小智 来源:blog.risingstack 为了保证的可读性,本文采用意译而非直译。 简介 如果咱们关注代码本身结构及可读笥,而不是只关心它是否能工作,那么咱们写代码是有一定的水准。专业开发人员将为未来的自己和“其他人”编写代码,而不仅仅只编写能应付当前工作的代码。 在此基础上,可读性高的代码可以定义为自解释的、易于人理解的、易于更改...
【图解算法面试】记一次面试:说说游戏中的敏感词过滤是如何实现的?
版权声明:本文为苦逼的码农原创。未经同意禁止任何形式转载,特别是那些复制粘贴到别的平台的,否则,必定追究。欢迎大家多多转发,谢谢。 小秋今天去面试了,面试官问了一个与敏感词过滤算法相关的问题,然而小秋对敏感词过滤算法一点也没听说过。于是,有了下下事情的发生… 面试官开怼 面试官:玩过王者荣耀吧?了解过敏感词过滤吗?,例如在游戏里,如果我们发送“你在干嘛?麻痹演员啊你?”,由于“麻痹”是一个敏感词,...
程序员需要了解的硬核知识之汇编语言(一)
之前的系列文章从 CPU 和内存方面简单介绍了一下汇编语言,但是还没有系统的了解一下汇编语言,汇编语言作为第二代计算机语言,会用一些容易理解和记忆的字母,单词来代替一个特定的指令,作为高级编程语言的基础,有必要系统的了解一下汇编语言,那么本篇文章希望大家跟我一起来了解一下汇编语言。 汇编语言和本地代码 我们在之前的文章中探讨过,计算机 CPU 只能运行本地代码(机器语言)程序,用 C 语言等高级语...
GitHub 标星 1.6w+,我发现了一个宝藏项目,作为编程新手有福了!
大家好,我是 Rocky0429,一个最近老在 GitHub 上闲逛的蒟蒻… 特别惭愧的是,虽然我很早就知道 GitHub,但是学会逛 GitHub 的时间特别晚。当时一方面是因为菜,看着这种全是英文的东西难受,不知道该怎么去玩,另一方面是一直在搞 ACM,没有做一些工程类的项目,所以想当然的以为和 GitHub 也没什么关系(当然这种想法是错误的)。 后来自己花了一个星期看完了 Pyt...
Java知识体系最强总结(2020版)
更新于2019-12-15 10:38:00 本人从事Java开发已多年,平时有记录问题解决方案和总结知识点的习惯,整理了一些有关Java的知识体系,这不是最终版,会不定期的更新。也算是记录自己在从事编程工作的成长足迹,通过博客可以促进博主与阅读者的共同进步,结交更多志同道合的朋友。特此分享给大家,本人见识有限,写的博客难免有错误或者疏忽的地方,还望各位大佬指点,在此表示感激不尽。 文章目录...
计算机专业的书普遍都这么贵,你们都是怎么获取资源的?
介绍几个可以下载编程电子书籍的网站。 1.Github Github上编程书资源很多,你可以根据类型和语言去搜索。推荐几个热门的: free-programming-books-zh_CN:58K 星的GitHub,编程语言、WEB、函数、大数据、操作系统、在线课程、数据库相关书籍应有尽有,共有几百本。 Go语言高级编程:涵盖CGO,Go汇编语言,RPC实现,Protobuf插件实现,Web框架实...
毕业5年,我问遍了身边的大佬,总结了他们的学习方法
我问了身边10个大佬,总结了他们的学习方法,原来成功都是有迹可循的。
这些软件太强了,Windows必装!尤其程序员!
Windows可谓是大多数人的生产力工具,集娱乐办公于一体,虽然在程序员这个群体中都说苹果是信仰,但是大部分不都是从Windows过来的,而且现在依然有很多的程序员用Windows。 所以,今天我就把我私藏的Windows必装的软件分享给大家,如果有一个你没有用过甚至没有听过,那你就赚了????,这可都是提升你幸福感的高效率生产力工具哦! 走起!???? NO、1 ScreenToGif 屏幕,摄像头和白板...
大学四年因为知道了这32个网站,我成了别人眼中的大神!
依稀记得,毕业那天,我们导员发给我毕业证的时候对我说“你可是咱们系的风云人物啊”,哎呀,别提当时多开心啦????,嗯,我们导员是所有导员中最帅的一个,真的???? 不过,导员说的是实话,很多人都叫我大神的,为啥,因为我知道这32个网站啊,你说强不强????,这次是绝对的干货,看好啦,走起来! PS:每个网站都是学计算机混互联网必须知道的,真的牛杯,我就不过多介绍了,大家自行探索,觉得没用的,尽管留言吐槽吧???? 社...
Fiddler+夜神模拟器进行APP抓包
Fiddler+夜神模拟器进行APP抓包 作者:霞落满天 需求:对公司APP进行抓包获取详细的接口信息,这是现在开发必备的。 工具:Fiddler抓包,夜神模拟器 模拟手机 安装APP 1.下载Fiddler https://www.telerik.com/download/fiddler Fiddler正是在这里帮助您记录计算机和Internet之间传递的所有HTTP和HTTPS通信...
相关热词 c# id读写器 c#俄罗斯方块源码 c# linq原理 c# 装箱有什么用 c#集合 复制 c# 一个字符串分组 c++和c#哪个就业率高 c# 批量动态创建控件 c# 模块和程序集的区别 c# gmap 截图
立即提问