作者：wslhk

springboot3.5.0 jpa有bug

springboot 3.5.0 jpa使用jpql的时候如 “select u from User as u”,会报错如
org.hibernate.query.SyntaxException: At 1:** and token ‘)’, no viable alternative at input ‘select new User(*) ，改返回上个版本3.4.6正常

多个@ControllerAdvice控制异常处理排序

环境Springboot3，多个@ControllerAdvice 发现当有比如异常AException，AException继承了Exception时。异常没有由 AException 的处理逻辑处理，测试这两个方式都是有效的：

1：@ComponentScan(basePackages={“处理 AException 所在目录”}) 与加载顺序有关，需要把 AException 处理类优先加载

2：@Order 注解，需要放在类上！放方法上是无效的。优先级为正序，如0优先于1。默认值为Int最大值。

感觉用@Order好一点

elementplus 2.9.10 卸载el-form时出现的错误

ElementPlusError: [ElForm] unexpected width 0    ElementPlusError error.ts:4
    debugWarn error.ts:13
    getLabelWidthIndex utils.ts:15
    deregisterLabelWidth utils.ts:28
    updateLabelWidth form-label-wrap.tsx:56
    promise callback*nextTick runtime-core.esm-bundler.js:289
    updateLabelWidth form-label-wrap.tsx:51
    setup form-label-wrap.tsx:65
    createHook runtime-core.esm-bundler.js:2815
    callWithErrorHandling runtime-core.esm-bundler.js:199

表单中设置labelWidth属性为’auto’ ，卸载el-form时如设置v-if=’false’的时候会出现异常，如果labelWidth有值比如labelWidth=’0’则正常。觉着像elementplus的bug，解决方式是在v-if=’false’前主动把labelWidth赋值一个数字。

springboot3.4.x jpa中ddl_auto需要注意时间格式

老项目是在springboot2时创建的mysql表有的字段用的date格式，但程序没有加jpa的@Column注解，导致程序升级到springboot3的时候时间格式变成了datetime，一些依赖时间的判断出错了。

项目升级需要注意下mysql中date格式，需要补齐@Column注解

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) on project xxx: Fatal error compiling: error: invalid target release: 17 -> [Help 1]

使用jenkins做单元测试的时候出现的异常

项目环境是jdk17,本地测试，测试服运行都没有问题，只有单元测试出异常。原因是maven中节点环境变量的JAVA_HOME指向的JDK版本是/usr/lib/jvm/openjdk，我的服务器是11,改成正确的路径就好了

开始以为是maven-compiler-plugin 版本有对应关系，不匹配。

因为命令行直接打java -version是正确的版本17，没有发现问题

springboot+mysql emoji存储异常

测试服运行正常，正式服无法存储

尝试了网上的方法
1、mysql链接后加 characterEncoding参数，无效
2、数据库字段原来也是utf8mb4改成了utf8mb4_unicode ，无效

最终有效果的是:
升级mysql依赖版本 从mysql-connector-java改成 mysql-connector-j的最新版，有效了。

有相似情况的可以试试

容器中jackson时间戳时区错误问题

场景：k8s部署springboot项目，发现返回时间戳时区是错的

我以为时间戳是统一的没有时区问题，还是理解的粗浅了

尝试过改节点时区，改容器时区，改spring.jackson.time-zone配置，都没效果

有效过的是main里运行 TimeZone.setDefault(TimeZone.getTimeZone(“Asia/Shanghai”));

win10多人远程登录

1、系统属性，开启远程桌面，添加远程桌面登录用户；

2、快捷键win+R，输入 gpedit.msc ，打开本地组策略编辑器。选择“【管理模板】—>【Windows组件】—>【远程桌面服务】—>【远程桌面会话主机】—>【连接】

配置【限制连接的数量】，点击“已启用”，其中允许的RD最大连接数可以自己视情况而定

配置【允许用户通过使用远程桌面服务进行远程连接】，选择启用。

配置【将远程桌面服务用户限制到单独的远程桌面服务会话】，选择启用：

3、快捷键win+R键，输入msconfig，选择安全模式，重启进入安全模式

4、安全模式下运行如下脚本：



    # PowerShell script used to patch termsrv.dll file and allow multiple RDP connections on Windows 10 (1809 and never) and Windows 11 
    # Details here http://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/
     
    # Stop RDP service, make a backup of the termsrv.dllfile and change the permissions 
    Stop-Service UmRdpService -Force
    Stop-Service TermService -Force
    $termsrv_dll_acl = Get-Acl c:\windows\system32\termsrv.dll
    Copy-Item c:\windows\system32\termsrv.dll c:\windows\system32\termsrv.dll.copy
    takeown /f c:\windows\system32\termsrv.dll
    $new_termsrv_dll_owner = (Get-Acl c:\windows\system32\termsrv.dll).owner
    cmd /c "icacls c:\windows\system32\termsrv.dll /Grant $($new_termsrv_dll_owner):F /C"
    # search for a pattern in termsrv.dll file 
    $dll_as_bytes = Get-Content c:\windows\system32\termsrv.dll -Raw -Encoding byte
    $dll_as_text = $dll_as_bytes.forEach('ToString', 'X2') -join ' '
    $patternregex = ([regex]'39 81 3C 06 00 00(\s\S\S){6}')
    $patch = 'B8 00 01 00 00 89 81 38 06 00 00 90'
    $checkPattern=Select-String -Pattern $patternregex -InputObject $dll_as_text
    If ($checkPattern -ne $null) {
        $dll_as_text_replaced = $dll_as_text -replace $patternregex, $patch
    }
    Elseif (Select-String -Pattern $patch -InputObject $dll_as_text) {
        Write-Output 'The termsrv.dll file is already patch, exitting'
        Exit
    }
    else { 
        Write-Output "Pattern not found "
    }
    # patching termsrv.dll
    [byte[]] $dll_as_bytes_replaced = -split $dll_as_text_replaced -replace '^', '0x'
    Set-Content c:\windows\system32\termsrv.dll.patched -Encoding Byte -Value $dll_as_bytes_replaced
    # comparing two files 
    fc.exe /b c:\windows\system32\termsrv.dll.patched c:\windows\system32\termsrv.dll
    # replacing the original termsrv.dll file 
    Copy-Item c:\windows\system32\termsrv.dll.patched c:\windows\system32\termsrv.dll -Force
    Set-Acl c:\windows\system32\termsrv.dll $termsrv_dll_acl
    Start-Service UmRdpService
    Start-Service TermService

原文链接：https://blog.csdn.net/luexon/article/details/125078585

记录一个docker升级docker-ce问题

老系统装的docker发现很多镜像已经不再支持，查网上需要装docker-ce，卸载docker，添加源：https://download.docker.com/linux/centos/docker-ce.repo。安装docker-ce最后启动docker报异常：

journalctl -xe
-- The start-up result is done.
Dec 08 17:30:01 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: Starting Session 2097629 of user root.
-- Subject: Unit session-2097629.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit session-2097629.scope has begun starting up.
Dec 08 17:30:01 iZbp1j6nqn3qz7t3ojr1ccZ CROND[6511]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Dec 08 17:30:13 iZbp1j6nqn3qz7t3ojr1ccZ sshd[6516]: Invalid user ftpadmin from 47.96.36.95 port 39610
Dec 08 17:30:13 iZbp1j6nqn3qz7t3ojr1ccZ sshd[6516]: input_userauth_request: invalid user ftpadmin [preauth]
Dec 08 17:30:13 iZbp1j6nqn3qz7t3ojr1ccZ sshd[6516]: pam_unix(sshd:auth): check pass; user unknown
Dec 08 17:30:13 iZbp1j6nqn3qz7t3ojr1ccZ sshd[6516]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.96.36.95
Dec 08 17:30:15 iZbp1j6nqn3qz7t3ojr1ccZ sshd[6516]: Failed password for invalid user ftpadmin from 47.96.36.95 port 39610 ssh2
Dec 08 17:30:15 iZbp1j6nqn3qz7t3ojr1ccZ sshd[6516]: Received disconnect from 47.96.36.95 port 39610:11: Bye Bye [preauth]
Dec 08 17:30:15 iZbp1j6nqn3qz7t3ojr1ccZ sshd[6516]: Disconnected from 47.96.36.95 port 39610 [preauth]
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ polkitd[502]: Registered Authentication Agent for unix-process:6549:6800316710 (system bus name :1.4195603 [/usr/bin/pkttyagent --notify-fd 5 --fallback],
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has begun starting up.
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ dockerd[6555]: time="2023-12-08T17:31:08.763547319+08:00" level=info msg="Starting up"
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ dockerd[6555]: time="2023-12-08T17:31:08.798534673+08:00" level=error msg="[graphdriver] /var/lib/docker contains several valid graphdrivers: overlay2, de
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ dockerd[6555]: failed to start daemon: error initializing graphdriver: /var/lib/docker contains several valid graphdrivers: overlay2, devicemapper; cleanu
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has failed.
-- 
-- The result is failed.
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: Unit docker.service entered failed state.
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: docker.service failed.
Dec 08 17:31:08 iZbp1j6nqn3qz7t3ojr1ccZ polkitd[502]: Unregistered Authentication Agent for unix-process:6549:6800316710 (system bus name :1.4195603, object path /org/freedesktop/PolicyKit1/Auth
Dec 08 17:31:11 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: docker.service holdoff time over, scheduling restart.
Dec 08 17:31:11 iZbp1j6nqn3qz7t3ojr1ccZ systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has begun starting up.

最后看到这个贴：https://zhuanlan.zhihu.com/p/660028084。

rm -rf /var/lib/docker/*
systemctl start docker

终于能启动了