Olsond

try to be alive

0%

开发备忘录

发表于 更新于 分类于
工作备忘记录

Spring boot 相关

纠错

首先，bootstrap.yml作为配置文件，是在springcloud中实现的，而不是springboot！
sb根本就不会加载bootstrap.yml！
百度的答案都是sb中这两者区别，错到德玛西亚去了。

  • 认识bootstrap.yml
    在springcloud中，使用bootstrap首先加载一些配置，这部分是高优先级不会被后续覆盖的。
    通常是用做加载配置中心配置。不要在这里配置其他属性，会出现很诡异的事。(我测了，配置0000，得出0)所以就乖乖的按照springcloud的建议来。最后，bootstrap.yml作为配置文件，是springcloud中的定义

Spring Cloud Open Fegin

  • FEIGN是走HTTP的，即使利用接口特性做成类RPC的方式，但也还是走HTTP的。但是就我使用感受，速度还行，比想象中要快。rpc固然速度比http快，但是你要考虑的稳定性、数据传输的可靠性、熔断保护，以及更方便的链路监控和追踪，这时候HTTP的优势就体现了。

  • Spring cloud的http从以下几个方面可以优化

    • 换成okhttp3。
    • 应用中不要做异步传输，防止异步等待，如果遇到异步场景，一定要利用好消息队列和缓存。
    • 如果http1.1，有些场景利用keep-alive，减少连接损耗。
    • 可以考虑尝试HTTP/2

Springboot2.x

  • Spring boot 2.x 无法使用servlet: context-path, 采用的是 spring.webflux.base-path:
  • @ConditionalOnProperty 注解介绍
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
@Retention(RetentionPolicy.RUNTIME)
@Target({ ElementType.TYPE, ElementType.METHOD })
@Documented
@Conditional(OnPropertyCondition.class)
public @interface ConditionalOnProperty {
  // 数组，获取对应property名称的值，与name不可同时使用
  String[] value() default {};
  // 配置属性名称的前缀，比如spring.http.encoding
  String prefix() default "";
  // 数组，配置属性完整名称或部分名称
  // 可与prefix组合使用，组成完整的配置属性名称，与value不可同时使用
  String[] name() default {};
  // 可与name组合使用，比较获取到的属性值与havingValue给定的值是否相同，相同才加载配置
  String havingValue() default "";
  // 缺少该配置属性时是否可以加载。如果为true，没有该配置属性时也会正常加载；反之则不会生效
  boolean matchIfMissing() default false;
}

Springboot data redis 和data-elasticsearch中的netty冲突

使用场景

  • spring-data-elasticsearch 和 spring-boot-data-redis都是使用的netty作为通信框架, 如果在加载时优先加载redis 链接的bean, 那么后续es创建时会导致启动失败, 异常日志 Caused by: java.lang.IllegalStateException: availableProcessors is already set to [4], rejecting [4]
  • 具体原因在elasticsearch项目的这个类中有实现, 原因是又针对netty的处理器配置设置了一次参数,导致nettyRutime时检测到重复赋值…
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
package org.elasticsearch.transport.netty4;
// 省略....

public class Netty4Utils {

    private static final AtomicBoolean isAvailableProcessorsSet = new AtomicBoolean();

    /**
     * Set the number of available processors that Netty uses for sizing various resources (e.g., thread pools).
     *
     * @param availableProcessors the number of available processors
     * @throws IllegalStateException if available processors was set previously and the specified value does not match the already-set value
     */
    public static void setAvailableProcessors(final int availableProcessors) {
        // we set this to false in tests to avoid tests that randomly set processors from stepping on each other
        final boolean set = Booleans.parseBoolean(System.getProperty("es.set.netty.runtime.available.processors", "true"));
        if (set == false) {
            return;
        }

        /*
         * This can be invoked twice, once from Netty4Transport and another time from Netty4HttpServerTransport; however,
         * Netty4Runtime#availableProcessors forbids settings the number of processors twice so we prevent double invocation here.
         */
        if (isAvailableProcessorsSet.compareAndSet(false, true)) {
            NettyRuntime.setAvailableProcessors(availableProcessors);
        } else if (availableProcessors != NettyRuntime.availableProcessors()) {
            /*
             * We have previously set the available processors yet either we are trying to set it to a different value now or there is a bug
             * in Netty and our previous value did not take, bail.
             */
            final String message = String.format(
                Locale.ROOT,
                "available processors value [%d] did not match current value [%d]",
                availableProcessors,
                NettyRuntime.availableProcessors()
            );
            throw new IllegalStateException(message);
        }
    }

解决方案

  • github的issus
  • 将es配置优先加载
  • 启动类中添加覆盖配置
1
2
3
4
5
6
7
8
9
10
11
public static void main(String[] args) {  
	System.setProperty("es.set.netty.runtime.available.processors", "false");  
	SpringApplication.run(Application.class, args);  
}

// or

static {
	System.setProperty("es.set.netty.runtime.available.processors", "false");
}

  • 启动时添加启动参数也可以覆盖配置 -Des.set.netty.runtime.available.processors=false

总结

如果集成了其他使用netty的相关框架在spring boot配置类中加载, 都会导致和elasticserach配置冲突造成启动失败, 例如: spring-boot-starter-actuator中的elasticsearch健康检查配置

spring-boot中的@Order注解

  • 通过@Order注解来注入集合时，指定顺序的场景, 首先我们定义两个Bean实现同一个接口，并添加上@Order注解
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
public interface IBean {
}

@Order(2)
@Component
public class AnoBean1 implements IBean {

    private String name = "ano order bean 1";

    public AnoBean1() {
        System.out.println(name);
    }
}

@Order(1)
@Component
public class AnoBean2 implements IBean {

    private String name = "ano order bean 2";

    public AnoBean2() {
        System.out.println(name);
    }
}
  • 然后在一个测试bean中，注入IBean的列表，我们需要测试这个列表中的Bean的顺序是否和我们定义的@Order规则一致
1
2
3
4
5
6
7
8
9
@Component
public class AnoTestBean {

    public AnoTestBean(List<IBean> anoBeanList) {
        for (IBean bean : anoBeanList) {
            System.out.println("in ano testBean: " + bean.getClass().getName());
        }
    }
}
  • 根据我们的预期, anoBeanList集合中，anoBean2应该在前面
1
2
3
4
ano order bean 1
ano order bean 2
in ano testBean:com.git.hui.boot.beanorder.order.right.ano.order.AnoBean2
in ano testBean:com.git.hui.boot.beanorder.order.right.ano.order.AnoBean1
  • 只能决定使用顺序不能指定初始化加载顺序.

spring-boot 依赖外部jar的使用

依赖配置

1
2
3
4
5
6
7
8
<dependency>  
	<!-- groupId 和 artifactId随意填写-->
	<groupId>com.cfit</groupId>  
	<artifactId>af-as-third-api</artifactId>  
	<version>0.0.1-SNAPSHOT</version>  
	<scope>system</scope>  
	<systemPath>${pom.basedir}/../lib/xxxx.jar</systemPath>  
</dependency>

打包配置

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
<build>
	<plugins>
		<plugin>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-maven-plugin</artifactId>
			<version>${spring-boot.version}</version>
			<configuration>
			    <!-- 一定要有这个配置 -->
				<includeSystemScope>true</includeSystemScope>
				<excludes>
					<exclude>
						<groupId>org.project.lombok</groupId>
						<artifactId>lombok</artifactId>
					</exclude>
				</excludes>
			</configuration>
			<executions>
				<execution>
					<goals>
						<goal>repackage</goal>
					</goals>
				</execution>
			</executions>
		</plugin>
	</plugins>
</build>

spring interceptor使用注意项

如不是特殊情况需要在拦截器interceptor中获取body的, 建议替换成filter实现或者一定要声明filter搭配interceptor进行request包装类来将body向下传递, 原因是在执行优先级filter > interceptor > controller 中的body内容是inputStream形式向下传递的, 如果在interceptor中取出了body内容, 会导致filter传递完的inputStream无法继续向下传递, 而controller无法获取到参数, 产生stream is closed异常

Spring boot validator 校验 和 独立配置返回消息内容整合

spring boot validator是由hibernate-validator实现的, hibernate-validator 使用的是 JSR-303 的默认ValidationMessages.properties包, 所以需要手动设置加载自定义springboot message 文件

官方解释: 指定用于解析验证消息的自定义 Spring MessageSource，而不是依赖 JSR-303 的默认ValidationMessages.properties包,在类路径中。 这可能指的是 Spring 上下文的共享messageSource

加载自定义消息配置文件

1
2
3
4
5
6
7
8
9
10
11
12
13
  /**
    * Specify a custom Spring MessageSource for resolving validation messages,
 * instead of relying on JSR-303's default "ValidationMessages.properties" bundle
 * in the classpath. This may refer to a Spring context's shared "messageSource" bean,
    */
@Bean
public LocalValidatorFactoryBean localValidatorFactoryBean() {
	LocalValidatorFactoryBean localValidatorFactoryBean = new LocalValidatorFactoryBean();
	ReloadableResourceBundleMessageSource messageSource = new ReloadableResourceBundleMessageSource();
	messageSource.setBasename("classpath:message"); // 这里加载自定message.properties文件
	localValidatorFactoryBean.setValidationMessageSource(messageSource);
	return localValidatorFactoryBean;
}

问题: LocalValidatorFactoryBean设置自定义的messageSource不生效, 是由于项目中有配置继承了WebMvcConfigurationSupport类, 导致Validator实例会被该配置中的OptionalValidatorFactoryBean类创建的LocalValidatorFactoryBean覆盖掉丢失messageSource
解决: 修改当前配置继承的WebMvcConfigurationSupport类替换成实现WebMvcConfigurer即可,这样会加载自定义重写的springmvc配置, spring mvc会判断是否加载了Validator直接使用

聚合工程多模块message文件的处理

  • 重写spring-boot的MessageSourceAutoConfiguration中的MessageSource不使用ResourceBundleMessageSource 而使用 ReloadableResourceBundleMessageSource
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
@Bean
public MessageSource messageSource() throws Exception {
    ReloadableResourceBundleMessageSource reloadableResourceBundleMessageSource =
            new ReloadableResourceBundleMessageSource();
    reloadableResourceBundleMessageSource.setDefaultEncoding("UTF-8");
    PathMatchingResourcePatternResolver resourcePatternResolver = new PathMatchingResourcePatternResolver();
    Resource[] resources = resourcePatternResolver.getResources("classpath*:message*");
    if (resources.length > 0) {
        Set<String> urlSet = Arrays.stream(resources).map(resource ->
        {
            try {
                return resource.getURL().toString().replace(".properties","");
            } catch (IOException e) {
                throw new RuntimeException(e);
            }
        }).collect(Collectors.toSet());
        if (CollectionUtil.isNotEmpty(urlSet)) {
            reloadableResourceBundleMessageSource.setBasenames(urlSet.toArray(new String[0]));
        } else {
            reloadableResourceBundleMessageSource.setBasename("messages");
        }
    }
    return reloadableResourceBundleMessageSource;
}
  • 不重写配置, 直接在yaml设置多个文件
1
2
3
4
spring:
  messages:
    basename: message,message_shared
    encoding: UTF-8

声明校验错误提示信息配置

  • 设置引用变量
1
2
# message.properties
name.length.validation=名称长度只允许在{min} ~ {max}之间
  • 在实体类中属性上使用相关注解
1
2
@Length(min = 8, max = 100, message = "{name.length.validation}")
private String name;
  • 还可以使用MessageSource进行动态添加占位符参数, 调整返回的校验消息内容
1
2
# message.properties
name.length.validation={0} 名称长度只允许在{min} ~ {max}之间

异常处理方法

  • 全局拦截, 在Controller声明的方法
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
 @Autowired
 private MessageSource messageSource;

 /**
  * 处理调用接口validator失败抛出的异常
  */
 @ExceptionHandler(BindException.class)
 public ResponseResult<Void> bindExceptionHandler(MethodArgumentNotValidException argumentNotValidException) {
     List<FieldError> fieldErrors = argumentNotValidException.getBindingResult().getFieldErrors();
     List<String> collect = fieldErrors.stream()
             // 如果不使用messageSource进行参数处理,则可直接返回fieldError.getDefaultMessage()
             .map(fieldError -> getMessage(fieldError.getDefaultMessage(), new Object[]{fieldError.getField()}, fieldError.getDefaultMessage(), LocaleContextHolder.getLocale()))
             .collect(Collectors.toList());
     return ResponseResult.error(String.valueOf(HttpStatus.BAD_REQUEST.value()), "数据验证失败，不合法的参数格式，请核对！", collect);
 }

public String getMessage(String code, Object[] args, String defaultMessage, Locale locale) {
     return messageSource.getMessage(code, args, defaultMessage, locale);
 }
  • 如果是在方法层级校验, 需要设置自定义的校验器, 否则无法返回mesages.properties的错误消息
1
2
3
4
5
6
7
8
9
10
   /**
 * 设置方法验证后处理器的校验器
 * @return
 */
@Bean
public MethodValidationPostProcessor methodValidationPostProcessor() {
	MethodValidationPostProcessor methodValidationPostProcessor = new MethodValidationPostProcessor();
	methodValidationPostProcessor.setValidator(localValidatorFactoryBean());
	return methodValidationPostProcessor;
}
  • 接口中使用注解方式
1
2
3
4
5
@Validated
public class User {
    void mergeUser (@NotBlank(message="{name.isNotBlank}")
                                 @Length(max=10, message=""{name.length.validation}") String name)
}

Springboot使用 @RequestPart

场景

使用可以需要将文件和对象分参数一起提交, 请求content-type类型是multipart/form-data传递

例子

  • 前端参数封装example (by vue)
1
2
3
4
5
6
7
8
9
const studentVo = { }
const formData = new FormData();
formData.append("file",  file) 
formData.append("studentVO",  new Blob([JSON.stringify(studentVo)], {type: "application/json"}));
axios.post('url', formData, {headers: {'Content-Type': 'multipart/form-data'}})
  .then(response => {

  }).catch(() => {
})
  • 后端接口example
1
2
3
4
@PostMapping(value = "/upload")  
public String uploadStuInfo (@RequestPart("file") MultipartFile multipartFile, @RequestPart StudentVO studentVO) {  
// todo  
}

总结

如果后端参数定义的是对象, 前端一定需要转换成blob类型, 否则会提示 org.springframework.web.HttpMediaTypeNotSupportedException: application/octet-stream....

spring boot 内置tomcat设置

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
@Bean
    public TomcatServletWebServerFactory servletContainer() {
        TomcatServletWebServerFactory factory = new TomcatServletWebServerFactory();
        factory.addContextCustomizers(context -> {
            SecurityConstraint securityConstraint = new SecurityConstraint();
            securityConstraint.setUserConstraint("CONFIDENTIAL");
            SecurityCollection collection = new SecurityCollection();
            collection.addPattern("/*");
            collection.addMethod("HEAD");
            collection.addMethod("PUT");
            collection.addMethod("PATCH");
            collection.addMethod("DELETE");
            collection.addMethod("TRACE");
            collection.addMethod("COPY");
            collection.addMethod("SEARCH");
            collection.addMethod("PROPFIND");
            securityConstraint.addCollection(collection);
            context.addConstraint(securityConstraint);
        });
        // 优化参数
        factory.addConnectorCustomizers(connector -> {
            connector.setAllowTrace(true);
			connector.setPort(8083);
			connector.setProperty("connectionTimeout", "30000");
             //CPU数
			connector.setProperty("acceptorThreadCount", "4");
			connector.setProperty("minSpareThreads", "50");
			connector.setProperty("maxSpareThreads", "50");
			connector.setProperty("maxThreads", "1000");
			connector.setProperty("maxConnections", "10000");
			connector.setProperty("protocol", "org.apache.coyote.http11.Http11Nio2Protocol");
			connector.setProperty("redirectPort", "443");
			connector.setProperty("compression", "on");
        });
        return factory;
    }

Ali QL Express 工具使用

  • 初始化
  • 转换表达式
  • 执行

Java Timer vs ExecutorService?

Q: I have code where I schedule a task usingjava.util.Timer. I was looking around and sawExecutorServicecan do the same. So this question here, have you usedTimerandExecutorServiceto schedule tasks, what is the benefit of one using over another?

Also wanted to check if anyone had used theTimerclass and ran into any issues which theExecutorServicesolved for them.

A:

According toJava Concurrency in Practice:

  • Timercan be sensitive to changes in the system clock,ScheduledThreadPoolExecutorisn’t.
  • Timerhas only one execution thread, so long-running task can delay other tasks.ScheduledThreadPoolExecutorcan be configured with any number of threads. Furthermore, you have full control over created threads, if you want (by providingThreadFactory).
  • Runtime exceptions thrown inTimerTaskkill that one thread, thus makingTimerdead :-( … i.e. scheduled tasks will not run anymore.ScheduledThreadExecutornot only catches runtime exceptions, but it lets you handle them if you want (by overridingafterExecutemethod fromThreadPoolExecutor). Task which threw exception will be canceled, but other tasks will continue to run.

If you can useScheduledThreadExecutorinstead ofTimer, do so.

One more thing… whileScheduledThreadExecutorisn’t available in Java 1.4 library, there is aBackport of JSR 166 (java.util.concurrent) to Java 1.2, 1.3, 1.4, which has theScheduledThreadExecutorclass.

Mapstruct 插件

  • idea 安装mapstruct support 插件, 写expression好用
  • 不同类型使用代码表达式转换, @Mapping注解可以设置某个属性映射关系, expression表达式则是实现的源代码, 也可以使用@Mapper注解中导入的实现类的方法名
  • 如果表达式中含有导入的外部包, 则使用 @Mapper(import={Arrays.class} 类似引入即可
1
2
3
4
5
6
@Mapper
public interface MergeRuleConfigConvert extends BaseConvert<RuleConfigMergeVO, RuleConfigPO> {
    @Mapping(expression = "java(String.join(\",\", mergeVO.getRuleParamIds()))", target = "ruleParamId")
    RuleConfigPO toModel(RuleConfigMergeVO mergeVO);
}
public static final RuleConfigPO.MergeRuleConfigConvert CONFIG_MERGE_CONVERT = Mappers.getMapper(MergeRuleConfigConvert.class);
  • 结合lombok插件, 实体类中涉及到继承父类属性, 并且都使用了@SuperBuilder, 自动生成的convert实现类不会出现问题
  • 如果手动设置@Mapping,且转换类在使用父类属性时, 需要设置 @Mapper(builder = @org.mapstruct.Builder(disableBuilder = true), 否则自动生成convert实现类方法中会直接编译成了父类导致报错
1
2
3
4
5
6
7
@Mapper(builder = @org.mapstruct.Builder(disableBuilder = true), imports = {Arrays.class})
public interface RuleConfigResConvert extends BaseConvert<RuleConfigResVO, RuleConfigPO> {
    @Mapping(expression = "java(Arrays.asList(ruleConfigPO.getRuleParamId() .split(\",\")))", target = "ruleParamIds")
    RuleConfigResVO fromModel(RuleConfigPO ruleConfigPO);
}
public static final RuleConfigPO.RuleConfigResConvert CONFIG_RES_CONVERT = Mappers.getMapper(RuleConfigPO.RuleConfigResConvert.class);

springboot启动脚本加载优先级

  • 没有指定配置文件的情况下当前jar包目录同级有配置文件或者有config文件夹, 优先加载外部的,会覆盖内部classes下的.
1
2
3
4
# 启动指定外部配置文件
nohup java -Xms2048M -Xmx2048M -XX:MaxPermSize=512M -jar ./xxxxxxxx.jar -Dspring.config.location=./application.yml > /dev/null 2>&1
# 启动指定环境变量加载配置文件
nohup java -Xms2048M -Xmx2048M -XX:MaxPermSize=512M -jar ./xxxxxxxx.jar --spring.profiles.active=dev > /dev/null 2>&1

hutool excel工具

读取excel过慢, 注意不同操作系统环境有内存泄露风险, 推荐使用easyexcel

Es 相关

ES 跨集群搜索设置

  • elasticsearch.yml 相关配置
1
2
3
4
5
6
7
8
9
10
11
http.host: 0.0.0.0
http.port: 9200
node.name: node-1
cluster.initial_master_nodes: ["node-1"]
cluster.name: cluster_name
network.host: 0.0.0.0
network.publish_host: 127.0.0.1  #一定要配置
http.cors.enabled: true

xpack.ml.enabled: false
xpack.security.enabled: false
  • kibana.yml 设置
1
2
3
4
5
6
server.host: "0.0.0.0"
server.shutdownTimeout: "5s"
 # macos容器启动的kibana需要使用域名访问
elasticsearch.hosts: [ "http://docker.for.mac.host.internal:9201"] 
monitoring.ui.container.elasticsearch.enabled: true
i18n.locale: "zh-CN"
  • 设置远程集群搜索
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
PUT _cluster/settings
{
  "persistent": {
    "cluster": {
      "remote": {
        "cluster_one": {
          "seeds": [
            "IP:9300"
          ]
        },
        "cluster_two": {
          "seeds": [
            "IP:9301"
          ]
        },
        "cluster_three": {
          "seeds": [
            "IP:9302"
          ]
        }
      }
    }
  }
}

GET _cluster/health

GET _remote/info

GET flute_cluster:knowledgesearch/_search

组合查询

  • example : and condition1 or ( condition 2 and condition 3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
POST _search
{
    "from": 0,
    "size": 20,
    "sort": {},
    "query": {
        "bool": {
            "should": [
                {
                    "term": {
                        "condition1": 0
                    }
                },
                {
                    "bool": {
                        "must": [
                            {
                                "term": {
                                    "condition2": 1
                                }
                            },
                            {
                                "wildcard": {
                                    "condition3": {
                                        "wildcard": "*115916589957645297*"
                                    }
                                }
                            }
                        ]
                    }
                }
            ]
        }
    }
}

Vue 相关

优化

  • vue-cli4 工程 vue.config.js设置
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
chainWebpack: config => {
    config.module.rule('svg')
      .exclude.add(path.join(__dirname, 'src/assets/icon'))
      .end()
    config.module
      .rule('icons')
      .test(/\.svg$/).include
      .add(path.join(__dirname, 'src/assets/icon'))
      .end()
      .use('svg-sprite-loader')
      .loader('svg-sprite-loader')
      .options({ symbolId: 'icon-[name]' })
      .end()
    config.module
      .rule('image')
      .test(/\.(png|jpe?g|gif)(\?.*)?$/)
      .use('image-webpack-loader')
      .loader('image-webpack-loader')
      .options({
        // 此处为ture的时候不会启用压缩处理,目的是为了开发模式下调试速度更快
        disable: process.env.NODE_ENV === 'development'
      }).end()
    
    config.when(process.env.VUE_BUILD_CONF === 'prod',
      config => {
        config.plugin('CompressionPlugin').use('compression-webpack-plugin', [{
          filename: '[path][base].gz',
          algorithm: 'gzip',
          // 要压缩的文件（正则）
          test: /\.(js|css|json|txt|ico|svg)(\?.*)?$/i,
          // 最小文件开启压缩
          threshold: 10240,
          minRatio: 0.8
        }])
        config
          .plugin('ScriptExtHtmlWebpackPlugin')
          .after('html')
          .use('script-ext-html-webpack-plugin', [{
            inline: /runtime\..*\.js$/
          }])
          .end()

        config
          .optimization.splitChunks({
            chunks: 'all',
            cacheGroups: {
              libs: {
                name: 'chunk-libs',
                test: /[\\/]node_modules[\\/]/,
                priority: 10,
                chunks: 'initial' // only package third parties that are initially dependent
              },
              elementUI: {
                name: 'chunk-elementUI', // split elementUI into a single package
                priority: 20, // the weight needs to be larger than libs and app or it will be packaged into libs or app
                test: /[\\/]node_modules[\\/]_?element-ui(.*)/ // in order to adapt to cnpm
              },
              commons: {
                name: 'chunk-commons',
                test: resolve('src/components'), // can customize your rules
                minChunks: 3, //  minimum common number
                priority: 5,
                reuseExistingChunk: true
              }
            }
          })
        config.optimization.runtimeChunk('single')
        // 去掉debugger console
        config.optimization.minimizer('terser').tap((args) => {
          // 注释console.*
          args[0].terserOptions.compress.drop_console = true
          // remove debugger
          args[0].terserOptions.compress.drop_debugger = true
          // 移除 console.log
          args[0].terserOptions.compress.pure_funcs = ['console.log']
          // 去掉注释 如果需要看chunk-vendors公共部分插件，可以注释掉就可以看到注释了
          args[0].terserOptions.output = {
            comments: false
          };
          return args
        })
      }
    )
  }

使用docker 安装使用 onlyoffice

安装

  • 如果开启使用example页面功能, 需要需要配置/etc/onlyoffice/documentserver-example/default.json文件中的 example 的地址,配置为 docker 网卡地址

访问

  • onlyoffice 是使用 jwt 签名进行验证用户的真实性以及请求来源的真实性
  • 在 7.2 版本后默认启用了 jwt认证 功能, 启动服务会生成相应的签名密钥, 签名的secret密钥可以在 /etc/onlyoffice/documentserver/local.json中找到, 调用onlyoffice 页面时一定需要携带 token内容, 完整的参数如下 e.g
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
{
    "document": {
        "info": {
            "owner": "Me",
            "favorite": null,
            "uploaded": "Wed Sep 13 2023"
        },
        "permissions": {
            "comment": true,
            "copy": true,
            "download": true,
            "edit": true,
            "print": true,
            "fillForms": true,
            "modifyFilter": true,
            "modifyContentControl": true,
            "review": true,
            "chat": true,
            "commentGroups": {},
            "protect": true
        },
        "fileType": "docx",
        "key": "1671695205",
        "urlUser": "http://localhost:4000/download?fileName=new.docx&userAddress%2FUsers%2Fdy%2FDevSoftWare%2Fidea%2Fgithub%2Fonlyoffice-example%2Fdocuments%2F127.0.0.1%2F",
        "title": "new.docx",
        "url": "http://localhost:4000/download?fileName=new.docx&userAddress=%2FUsers%2Fdy%2FDevSoftWare%2Fidea%2Fgithub%2Fonlyoffice-example%2Fdocuments%2F127.0.0.1%2F",
        "directUrl": "",
        "referenceData": {
            "instanceId": "http://localhost:4000",
            "fileKey": "{\"userAddress\":\"127.0.0.1\",\"fileName\":\"new.docx\"}"
        }
    },
    "documentType": "word",
    "editorConfig": {
        "actionLink": null,
        "callbackUrl": "http://localhost:4000/track?fileName=new.docx&userAddress=%2FUsers%2Fdy%2FDevSoftWare%2Fidea%2Fgithub%2Fonlyoffice-example%2Fdocuments%2F127.0.0.1%2F",
        "coEditing": null,
        "createUrl": "http://localhost:4000/create?fileExt=docx&sample=false",
        "customization": {
            "logo": {
                "image": "",
                "imageEmbedded": "",
                "url": "https://www.onlyoffice.com"
            },
            "goback": {
                "url": "http://localhost:4000/"
            },
            "autosave": true,
            "comments": true,
            "compactHeader": false,
            "compactToolbar": false,
            "compatibleFeatures": false,
            "forcesave": false,
            "help": true,
            "hideRightMenu": false,
            "hideRulers": false,
            "submitForm": false,
            "about": true,
            "feedback": true
        },
        "embedded": {
            "embedUrl": null,
            "saveUrl": null,
            "shareUrl": null,
            "toolbarDocked": null
        },
        "lang": "en",
        "mode": "edit",
        "user": {
            "id": "1",
            "name": "John Smith",
            "group": ""
        },
        "templates": [
            {
                "image": "",
                "title": "Blank",
                "url": "http://localhost:4000/create?fileExt=docx&sample=false"
            },
            {
                "image": "http://localhost:4000/css/img/file_docx.svg",
                "title": "With sample content",
                "url": "http://localhost:4000/create?fileExt=docx&sample=true"
            }
        ]
    },
    "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
    "type": "desktop",
    "width": "100%",
    "height": "100%",
    "events": {}
}
  • 请求原理: 后端生成配置信息以及使用 onlyOffice提供的secret 密钥将配置信息进行jwt签名, 生成 token一并返回, 页面携带 token 以及文件地址访问 onlyoffice 服务, 借助 onlyoffice 的 api 打开编辑或预览文件

问题

  • 在官方提供的后端spring 例子中, 创建文件无法打开页面问题, 在 chrome 中, 不安全的网站(非 https)内容默认是阻止重定向的, 在 chrome输入chrome://settings/content中找到相应网站设置不安全内容设置为允许
  • 打开文件提示文件下载失败: 最主要的问题是documentServer无法访问应用服务后端提供的文件地址, 检查页面返回的editorConfig对象中的url地址ip是否允许documentServer访问

springboot 批量获取redis key超时问题

Scan命令是一种比Keys命令更加高效、安全的遍历Redis key的方式,可以减少因为大量 key 集中在一起而导致的阻塞和性能问题。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
// 实例化 RedisTemplate (按实际场景使用template)
RedisTemplate<String, String> redisTemplate = new RedisTemplate<>();
redisTemplate.setConnectionFactory(connectionFactory);
redisTemplate.afterPropertiesSet();

// 构造 ScanOptions
ScanOptions options = ScanOptions.scanOptions().match("prefix:*").count(1000).build();

// 获取 ScanCursor
ScanCursor<String> cursor = (ScanCursor<String>) redisTemplate.executeWithStickyConnection((RedisCallback) redisConnection -> {
    Cursor<byte[]> cursor1 = redisConnection.scan(options);
    return new ScanCursorWrapper(cursor1);
});



// 遍历 ScanCursor
while (cursor.hasNext()) {
    String key = cursor.next();
    // 对 key 进行操作
    // 有可能出现重复的key需要去重
    // ...
}

/**
*
	* redisTemplate
*/
public static Set<String> getKeysByPattern(String keyPattern) {  
	log.info(">>>>>>>>> clean keys");  
	return redisTemplate.execute((RedisCallback<Set<String>>) connection -> {  
				Set<String> keys = new HashSet<>();  
				Cursor<byte[]> cursor = connection.scan(ScanOptions.scanOptions().match(keyPattern+ "  *").count(10000).build());
				
				while (cursor.hasNext()) {  
					keys.add(new String(cursor.next()));  
				}  
				cursor.close();  
				return keys;  
	});  
}

首先实例化 RedisTemplate，并设置了它的连接工厂和属性。然后构造了一个 ScanOptions，用于指定 Scan 的参数，包括需要匹配的 key 前缀和每次返回的 key 数量等。接着通过 RedisTemplate 的 executeWithStickyConnection 方法执行 RedisCallback，获取一个 ScanCursor。最后遍历 ScanCursor 并对每个 key 进行操作。

需要注意的是，Scan 命令的返回结果是一个游标，需要通过循环遍历来获取所有的 key。同时，如果在循环遍历过程中有新的 key 被添加到 Redis 中，也有可能被遗漏。因此，在遍历过程中需要保证数据的一致性和可靠性。

Maven wrapper 代理地址

1
2
distributionUrl=https://mirrors.huaweicloud.com/repository/maven/org/apache/maven/apache-maven/3.6.3/apache-maven-3.6.3-bin.zip
wrapperUrl=https://mirrors.huaweicloud.com/repository/maven/io/takari/maven-wrapper/0.5.6/maven-wrapper-0.5.6.jar