-
阿里云香港服务器 https443 端口移动网络间歇性无法访问
2018-11-22 12:23提交工单试试。我网上查,阿里香港服务器 都有这个问题 https://yq.aliyun.com/ask/120562
-
sym 3.4.1 异常
2018-11-19 23:59org.b3log.symphony.service.ArticleMgmtService.genArticleAudio
代码 有个 bug,这样改下就好来。
@terminus -
sym 3.4.1 异常
2018-11-13 00:103.4.3 修复过这个问题,我升级到 3.4.3,工程启动隔一段时间,还是会报数据库连接泄漏,你升级试试
https://gitee.com/dl88250/symphony/commit/cc871eeb4e889b40f73df72267128865ed06d472 -
sym 3.4.1 异常
2018-11-11 10:21噢
[WARN ]-[2018-11-11 08:58:45]-[com.zaxxer.hikari.pool.ProxyLeakTask:84]: Connection leak detection triggered for com.mysql.cj.jdbc.ConnectionImpl@7fbb1b83 on thread Thread-146, stack trace follows
java.lang.Exception: Apparent connection leak detected
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128)
at org.b3log.latke.repository.jdbc.util.Connections.getConnection(Connections.java:190)
at org.b3log.latke.repository.jdbc.JdbcTransaction.(JdbcTransaction.java:61)
at org.b3log.latke.repository.jdbc.JdbcRepository.beginTransaction(JdbcRepository.java:749)
at org.b3log.latke.repository.AbstractRepository.beginTransaction(AbstractRepository.java:184)
at org.b3log.symphony.service.ArticleMgmtService.lambda$0(ArticleMgmtService.java:333)
at java.lang.Thread.run(Thread.java:748)
[WARN ]-[2018-11-11 08:58:56]-[com.zaxxer.hikari.pool.ProxyLeakTask:84]: Connection leak detection triggered for com.mysql.cj.jdbc.ConnectionImpl@5a26a567 on thread Thread-147, stack trace follows
java.lang.Exception: Apparent connection leak detected
...
[WARN ]-[2018-11-11 09:00:16]-[com.zaxxer.hikari.pool.ProxyLeakTask:84]: Connection leak detection triggered for com.mysql.cj.jdbc.ConnectionImpl@42af8e02 on thread Thread-148, stack trace follows
java.lang.Exception: Apparent connection leak detected
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128)
...
[WARN ]-[2018-11-11 09:00:19]-[com.zaxxer.hikari.pool.ProxyLeakTask:84]: Connection leak detection triggered for com.mysql.cj.jdbc.ConnectionImpl@69a5e494 on thread Thread-149, stack trace follows
java.lang.Exception: Apparent connection leak detected
... -
sym 3.4.1 异常
2018-11-11 01:09升级来代码,还是有这个问题,我在检查下 看看
[WARN ]-[2018-11-11 00:57:33]-[com.zaxxer.hikari.pool.ProxyLeakTask:84]: Connection leak detection triggered for com.mysql.cj.jdbc.ConnectionImpl@72ceafeb on thread Thread-25, stack trace follows java.lang.Exception: Apparent connection leak detected at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128) at org.b3log.latke.repository.jdbc.util.Connections.getConnection(Connections.java:190) at org.b3log.latke.repository.jdbc.JdbcTransaction.<init>(JdbcTransaction.java:61) at org.b3log.latke.repository.jdbc.JdbcRepository.beginTransaction(JdbcRepository.java:749) at org.b3log.latke.repository.AbstractRepository.beginTransaction(AbstractRepository.java:184) at org.b3log.symphony.service.ArticleMgmtService.lambda$0(ArticleMgmtService.java:333) at java.lang.Thread.run(Thread.java:748) [WARN ]-[2018-11-11 00:57:41]-[com.zaxxer.hikari.pool.ProxyLeakTask:84]: Connection leak detection triggered for com.mysql.cj.jdbc.ConnectionImpl@7d29cb42 on thread Thread-26, stack trace follows java.lang.Exception: Apparent connection leak detected at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128) at org.b3log.latke.repository.jdbc.util.Connections.getConnection(Connections.java:190) at org.b3log.latke.repository.jdbc.JdbcTransaction.<init>(JdbcTransaction.java:61) at org.b3log.latke.repository.jdbc.JdbcRepository.beginTransaction(JdbcRepository.java:749) at org.b3log.latke.repository.AbstractRepository.beginTransaction(AbstractRepository.java:184) at org.b3log.symphony.service.ArticleMgmtService.lambda$0(ArticleMgmtService.java:333) at java.lang.Thread.run(Thread.java:748)
-
请问下学历低的话入前端这行可以吗?
2018-08-26 14:15年轻,能提这样的问题,很钦佩,我 25 岁边工作,边自学 java,1 年后入行。学历是敲门砖,对大多数人来说非常重要。可以边上学,边学习技术。