EhCache在Spring中遇到的问题
EhCache在Spring中遇到的问题
- Spring集成EhCache时一些概念
- 用到的相关依赖
- 实际操作时遇到的问题
- 控制台输出太多Debug信息
-
- 解决方法——使用logback输出
Spring集成EhCache时一些概念
- Spring的实现类EhCacheCacheManager在实现接口中的方法时，没有自己去完成EhCache的操作，而是通过代理的方式，直接调用EhCache第三方jar包中的CacheManager方法。
- EnCacheManagerFactoryBean的作用
- EnCacheManagerFactoryBean对象的作用是加载encache.xml这个配置文件，生成EhCache第三方缓存的CacheManager
- 原先第三方缓存是通过EhCache.getInstance()来获取的，因此不能用Spring直接注入。
- 注意点：在Spring的工程中使用了EhCacheManagerFactoryBean来创建EhCache中的CacheManager对象之后，会与RoleServiceEhCache这个类中创建的cacheManager = CacheManager.getInstance();冲突。
用到的相关依赖
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0modelVersion>
<groupId>com.dfrz.java1908groupId>
<artifactId>26_Cache_ProjectartifactId>
<packaging>warpackaging>
<version>0.0.1-SNAPSHOTversion>
<name>26_Cache_Projectname>
<url>http://maven.apache.orgurl>
<properties>
<project.build.sourceEncoding>
UTF-8
project.build.sourceEncoding>
<maven.compiler.source>1.7maven.compiler.source>
<maven.compiler.target>1.7maven.compiler.target>
properties>
<dependencies>
<dependency>
<groupId>junitgroupId>
<artifactId>junitartifactId>
<version>3.8.1version>
<scope>testscope>
dependency>
<dependency>
<groupId>javax.servletgroupId>
<artifactId>javax.servlet-apiartifactId>
<version>3.1.0version>
<scope>providedscope>
dependency>
<dependency>
<groupId>javax.servlet.jspgroupId>
<artifactId>javax.servlet.jsp-apiartifactId>
<version>2.3.1version>
<scope>providedscope>
dependency>
<dependency>
<groupId>javax.servlet.jsp.jstlgroupId>
<artifactId>jstlartifactId>
<version>1.2version>
<scope>compilescope>
dependency>
<dependency>
<groupId>javax.servlet.jsp.jstlgroupId>
<artifactId>jstl-apiartifactId>
<version>1.2version>
dependency>
<dependency>
<groupId>org.glassfish.webgroupId>
<artifactId>jstl-implartifactId>
<version>1.2version>
dependency>
<dependency>
<groupId>commons-beanutilsgroupId>
<artifactId>commons-beanutilsartifactId>
<version>1.8.3version>
dependency>
<dependency>
<groupId>commons-codecgroupId>
<artifactId>commons-codecartifactId>
<version>1.9version>
dependency>
<dependency>
<groupId>commons-collectionsgroupId>
<artifactId>commons-collectionsartifactId>
<version>3.2version>
dependency>
<dependency>
<groupId>commons-dbcpgroupId>
<artifactId>commons-dbcpartifactId>
<version>1.4version>
dependency>
<dependency>
<groupId>commons-dbutilsgroupId>
<artifactId>commons-dbutilsartifactId>
<version>1.3version>
dependency>
<dependency>
<groupId>commons-poolgroupId>
<artifactId>commons-poolartifactId>
<version>1.5.6version>
dependency>
<dependency>
<groupId>commons-iogroupId>
<artifactId>commons-ioartifactId>
<version>2.4version>
dependency>
<dependency>
<groupId>commons-fileuploadgroupId>
<artifactId>commons-fileuploadartifactId>
<version>1.3.1version>
dependency>
<dependency>
<groupId>commons-langgroupId>
<artifactId>commons-langartifactId>
<version>2.5version>
dependency>
<dependency>
<groupId>org.apache.commonsgroupId>
<artifactId>commons-lang3artifactId>
<version>3.6version>
dependency>
<dependency>
<groupId>mysqlgroupId>
<artifactId>mysql-connector-javaartifactId>
<version>5.1.47version>
<scope>runtimescope>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-aopartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-aspectsartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-beansartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-contextartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-context-supportartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-coreartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-expressionartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-jdbcartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-ormartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-txartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-webartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>org.springframeworkgroupId>
<artifactId>spring-webmvcartifactId>
<version>5.2.12.RELEASEversion>
dependency>
<dependency>
<groupId>com.alibabagroupId>
<artifactId>druidartifactId>
<version>1.1.22version>
dependency>
<dependency>
<groupId>com.fasterxml.jackson.coregroupId>
<artifactId>jackson-coreartifactId>
<version>2.12.1version>
dependency>
<dependency>
<groupId>com.fasterxml.jackson.coregroupId>
<artifactId>jackson-databindartifactId>
<version>2.12.1version>
dependency>
<dependency>
<groupId>com.fasterxml.jackson.coregroupId>
<artifactId>jackson-annotationsartifactId>
<version>2.12.1version>
dependency>
<dependency>
<groupId>org.hibernategroupId>
<artifactId>hibernate-coreartifactId>
<version>5.1.0.Finalversion>
dependency>
<dependency>
<groupId>org.hibernategroupId>
<artifactId>hibernate-entitymanagerartifactId>
<version>5.1.0.Finalversion>
dependency>
<dependency>
<groupId>org.slf4jgroupId>
<artifactId>slf4j-apiartifactId>
<version>1.7.30version>
dependency>
<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-coreartifactId>
<version>1.2.3version>
dependency>
<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-classicartifactId>
<version>1.2.3version>
dependency>
<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-accessartifactId>
<version>1.2.3version>
dependency>
<dependency>
<groupId>net.sf.ehcachegroupId>
<artifactId>ehcacheartifactId>
<version>2.10.6version>
dependency>
dependencies>
<build>
<finalName>26_Cache_ProjectfinalName>
<plugins>
<plugin>
<artifactId>maven-clean-pluginartifactId>
<version>3.1.0version>
plugin>
<plugin>
<artifactId>maven-resources-pluginartifactId>
<version>3.0.2version>
plugin>
<plugin>
<artifactId>maven-compiler-pluginartifactId>
<version>3.7.0version>
<configuration>
<source>1.7source>
<target>1.7target>
<encoding>UTF-8encoding>
configuration>
plugin>
<plugin>
<artifactId>maven-jar-pluginartifactId>
<version>3.0.2version>
plugin>
<plugin>
<artifactId>maven-surefire-pluginartifactId>
<version>2.22.1version>
plugin>
<plugin>
<artifactId>maven-install-pluginartifactId>
<version>2.5.2version>
plugin>
<plugin>
<artifactId>maven-deploy-pluginartifactId>
<version>2.8.2version>
plugin>
<plugin>
<artifactId>maven-site-pluginartifactId>
<version>3.7.1version>
plugin>
<plugin>
<artifactId>
maven-project-info-reports-plugin
artifactId>
<version>3.0.0version>
plugin>
<plugin>
<artifactId>maven-war-pluginartifactId>
<version>2.4version>
<configuration>
<version>2.5version>
<failOnMissingWebXml>falsefailOnMissingWebXml>
configuration>
plugin>
plugins>
build>
project>
实际操作时遇到的问题
错误注入org.springframework.cache.Cache导致Service创建失败
@Autowired
private org.springframework.cache.CacheManager cacheManager;
@Autowired
private org.springframework.cache.Cache cache;
org.springframework.cache.Cache不是通过New产生的，而是通过CacheManger获取的，因此不能通过Spring直接注入，需要用cache = cacheManager.getCache(“xxx”);的方式来获取。
控制台输出太多Debug信息
10:57:33.185 [main] DEBUG org.springframework.orm.jpa.JpaTransactionManager - Closing JPA EntityManager [org.hibernate.jpa.internal.EntityManagerImpl@314c8b4a] after transaction
10:57:33.185 [main] DEBUG org.springframework.orm.jpa.JpaTransactionManager - Creating new transaction with name [com.service.UserService.printCache]: PROPAGATION_REQUIRED,ISOLATION_DEFAULT,-java.lang.Exception
10:57:33.185 [main] DEBUG org.springframework.orm.jpa.JpaTransactionManager - Opened new EntityManager [org.hibernate.jpa.internal.EntityManagerImpl@5ff60a8c] for JPA transaction
10:57:33.185 [main] DEBUG org.hibernate.engine.transaction.internal.TransactionImpl - begin
10:57:33.195 [main] DEBUG org.springframework.orm.jpa.JpaTransactionManager - Not exposing JPA transaction [org.hibernate.jpa.internal.EntityManagerImpl@5ff60a8c] as JDBC transaction because JpaDialect [org.springframework.orm.jpa.DefaultJpaDialect@576c5536] does not support JDBC Connection retrieval
org.springframework.cache.ehcache.EhCacheCache@5b247367
10:57:33.195 [main] DEBUG org.springframework.orm.jpa.JpaTransactionManager - Initiating transaction commit
10:57:33.195 [main] DEBUG org.springframework.orm.jpa.JpaTransactionManager - Committing JPA transaction on EntityManager [org.hibernate.jpa.internal.EntityManagerImpl@5ff60a8c]
10:57:33.195 [main] DEBUG org.hibernate.engine.transaction.internal.TransactionImpl - committing
10:57:33.195 [main] DEBUG org.springframework.orm.jpa.JpaTransactionManager - Closing JPA EntityManager [org.hibernate.jpa.internal.EntityManagerImpl@5ff60a8c] after transaction
解决方法——使用logback输出
- 注入依赖
<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-coreartifactId>
<version>1.2.3version>
dependency>
<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-classicartifactId>
<version>1.2.3version>
dependency>
<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-accessartifactId>
<version>1.2.3version>
dependency>
- 在Resources下编写logback.xml文件
<configuration scan="true" scanPeriod="60 seconds"
debug="false">
<appender name="console"
class="ch.qos.logback.core.ConsoleAppender">
<target>Sytem.outtarget>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] [%-5level] -%msg%n
pattern>
encoder>
appender>
<appender name="file" class="ch.qos.logback.core.FileAppender">
<file>E:/logback_file.logfile>
<append>trueappend>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] [%-5level] -%msg%n
pattern>
encoder>
appender>
<appender name="roll"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>E:/logback_roll.logfile>
<rollingPolicy
class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>
E:/logback_roll_%d{yyyy-MM-dd}.log
fileNamePattern>
<maxHistory>3maxHistory>
rollingPolicy>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] [%-5level] -%msg%n
pattern>
encoder>
appender>
<logger name="test.b.TestA" level="WARN" additivity="true">
<appender-ref ref="console" />
logger>
<logger name="org.hibernate"
level="ERROR" />
<root>
<level value="ERROR" />
<appender-ref ref="console" />
root>
configuration>
日志输出等级
log4j定义了8个级别的log(除去OFF和ALL 可以说分为6个级别),
* 优先级从高到低依次为:OFF FATAL ERROR WARN INFO DEBUG TRACE ALL
*
* ALL 最低等级的 用于打开所有日志记录
* TRACE 很低的日志级别 一般不会使用
* DEBUG 指出细粒度信息事件对调试应用程序是非常有帮助的 主要用于开发过程中打印一些运行信息
* INFO 消息在粗粒度级别上突出强调应用程序的运行过程
* 打印一些你感兴趣的或者重要的信息 这个可以用于生产环境中输出程序运行的一些重要信息
* 但是不能滥用 避免打印过多的日志
* WARN 表明会出现潜在错误的情形 有些信息不是错误信息 但是也要给程序员的一些提示
* ERROR 指出虽然发生错误事件 但仍然不影响系统的继续运行
* 打印错误和异常信息 如果不想输出太多的日志 可以使用这个级别
* FATAL 指出每个严重的错误事件将会导致应用程序的退出
* 这个级别比较高了 重大错误 这种级别你可以直接停止程序了
* OFF 最高等级的，用于关闭所有日志记录
*
* 如果将log level设置在某一个级别上 那么比此级别优先级高的log都能打印出来
* 例如 如果设置优先级为WARN 那么OFF FATAL ERROR WARN 4个级别的log能正常输出
* 而INFO DEBUG TRACE ALL级别的log则会被忽略
将root下的level更改为INFO或更高级即可