1.eclipse启动错误解决方法:
删除文件 [workspace]/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
2.Java compiler level does not match解决方法:
进入 windows—proferences—java–compiler设置编译出来的文件使用的格式是 1.7版本的。
进入项目–properties—java Compiler 把项目编译版本也设置成 1.7。
进入项目–properties—Myeclipse—project Facets设置java文件的版本为 1.7,并打勾。
检查工程目录下.setting文件夹内的org.eclipse.wst.common.project.facet.core.xml配置文件。
3.Unsupported major.minor version 51.0解决办法:
项目——>右键——>属性——>Java Compiler——>Compiler Compliance Level——>选择你使用的JDK版本——>应用。
4.Target runtime Apache Tomcat 6.0 is not defined 解决方法:
修改/.settings/org.eclipse.wst.common.project.facet.core.xml
5.com.sun.crypto.provider.SunJCE()报错:
解决办法:Window -> Preferences -> Java -> Compiler -> Errors/Warnings -> Deprecated and restricted API -> Forbidden reference (access rules) -> Warnings
1.关于测试类所在工程含有websocket注解:Failed to load ApplicationContext
Caused by: java.lang.IllegalArgumentException: A ServletContext is required to configure default servlet handling
解决方法:
spring-boot:
@RunWith(SpringRunner.class)
@SpringBootTest(classes=Application.class,webEnvironment=WebEnvironment.DEFINED_PORT)
spring:
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = { "classpath:spring/spring-*.xml" })
@WebAppConfiguration
2.The last packet sent successfully to the server was 0 milliseconds ago.
大部分原因是由于数据库回收了连接,而系统的缓冲池不知道,继续使用被回收的连接所致的。
第一种解决办法,就是将mysql回收空闲连接的时间变长,mysql默认回收时间是8小时,可以在mysql目录下的my.ini中增加下面配置,将时间改为1天。
[mysqld] wait_timeout=86400 #单位是秒,最大好像是24天:
第二种解决办法,可以通过配置,让缓冲池去测试连接是否被回收,如果被回收,则不继续使用.
#SQL查询,用来验证从连接池取出的连接
dbcp.validationQuery=SELECT 1
#指明连接是否被空闲连接回收器(如果有)进行检验,如果检测失败,则连接将被从池中去除
dbcp.testWhileIdle=true
#在空闲连接回收器线程运行期间休眠的时间值,以毫秒为单位,一般比minEvictableIdleTimeMillis小
dbcp.timeBetweenEvictionRunsMillis=300000
#在每次空闲连接回收器线程(如果有)运行时检查的连接数量,最好和maxActive一致
dbcp.numTestsPerEvictionRun=50
#连接池中连接,在时间段内一直空闲,被逐出连接池的时间(1000*60*60),以毫秒为单位
dbcp.minEvictableIdleTimeMillis=3600000
PL SQL:D:\oracle\product\10.2.0\client_1\NETWORK\ADMIN\tnsnames.ora
su - oracle
sql> conn / as sysdba
sql> startup
sql> shutdown
sql> quit
lsnrctl start/stop/status 启动/停止/查看监听器
ps -ef|grep ora 查看是否有Oracle的进程,特别是PMON、SMON、LGWR、DBWN、CKPT、MMON、MMNL、RECO等Oracle核心进程
[oracle@mcs-master ~]$ ps -ef | grep ora
oracle 20182 1 0 11:02 ? 00:00:00 ora_pmon_eomcr
oracle 20184 1 0 11:02 ? 00:00:00 ora_psp0_eomcr
oracle 20186 1 0 11:02 ? 00:00:00 ora_vktm_eomcr
oracle 20190 1 0 11:02 ? 00:00:00 ora_gen0_eomcr
oracle 20192 1 0 11:02 ? 00:00:00 ora_mman_eomcr
oracle 20196 1 0 11:02 ? 00:00:00 ora_diag_eomcr
oracle 20198 1 0 11:02 ? 00:00:00 ora_dbrm_eomcr
oracle 20200 1 0 11:02 ? 00:00:00 ora_vkrm_eomcr
oracle 20202 1 0 11:02 ? 00:00:00 ora_dia0_eomcr
oracle 20204 1 0 11:02 ? 00:00:00 ora_dbw0_eomcr
oracle 20206 1 0 11:02 ? 00:00:00 ora_lgwr_eomcr
oracle 20208 1 0 11:02 ? 00:00:00 ora_ckpt_eomcr
oracle 20210 1 0 11:02 ? 00:00:00 ora_lg00_eomcr
lsnrctl status 查看监听是否正常
[oracle@mcs-master ~]$ lsnrctl status
LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 11-JUL-2017 11:10:32
Copyright (c) 1991, 2014, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=mcs-master)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 12.1.0.2.0 - Production
Start Date 11-JUL-2017 10:51:50
Uptime 0 days 0 hr. 18 min. 42 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/12.1.0/db_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/mcs-master/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=mcs-master)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=mcs-master)(PORT=5500))(Security=
(my_wallet_directory=/u01/app/oracle/admin/eomcr/xdb_wallet))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "eomcr" has 1 instance(s).
Instance "eomcr", status READY, has 1 handler(s) for this service...
Service "eomcrXDB" has 1 instance(s).
Instance "eomcr", status READY, has 1 handler(s) for this service...
The command completed successfully