Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you about what all the configuration attributes in SpringBoot refer to. The article is rich in content and analyzes and describes it from a professional point of view. I hope you can get something after reading this article.

The Chinese description of all configuration items in SpringBoot (translated by Deepl) is provided by the SpringBoot Chinese community.

1. The default value of the Core properties configuration item indicates that debugfalse enables debug logging. Info.*

Any attribute to add to the info endpoint. Logging.config

The location of the log profile. For example, classpath:logback.xml stands for Logback. The translation word used by logging.exception-conversion-word%wEx when recording an exception. Whether logging.file.clean-history-on-startfalse cleans up the archive log file at startup. Only the default logback settings are supported. The maximum number of days logging.file.max-history7.0 archived log files can be saved. Only the default logback settings are supported. Logging.file.max-size10MB maximum log file size. Only the default logback settings are supported. Logging.file.name

Log file name (for example, myapp.log). The name can be the exact location or the relative location of the current directory. Logging.file.path

Location of the log file. For example, / var/log. The total size of log backups to be saved by logging.file.total-size-cap0B. Only the default logback settings are supported. Logging.group.*

The log group can quickly replace multiple recorders at the same time. For example, logging.group.db=org.hibernate,org.springframework.jdbc. Logging.level.*

Log level severity mapping. For example, logging.level.org.springframework=DEBUG. Logging.pattern.console%clr (% d {${LOG_DATEFORMAT_PATTERN:-yyyy-MM-dd HH:mm:ss.SSS}}) {faint}% clr (${LOG_LEVEL_PATTERN:-%5p})% clr (${PID:-}) {magenta}% clr (-) {faint}% clr ([.15t]) {faint}% clr (%-40.40logger {39}) {cyan}% clr (:) {faint}% M% n ${LOG_EXCEPTION_CONVERSION_WORD:-%wEx} output to the log format of the console. Only the default logback settings are supported. The format of the date in the logging.pattern.dateformatyyyy-MM-dd HH:mm:ss.SSS log. Only the default logback settings are supported. Logging.pattern.file%d {${LOG_DATEFORMAT_PATTERN:-yyyy-MM-dd HH:mm:ss.SSS}} ${LOG_LEVEL_PATTERN:-%5p} ${PID:-}-[% t]%%-40.40logger {39}:% m% n ${LOG_EXCEPTION_CONVERSION_WORD:-%wEx} output to the log format of the file. Only the default logback settings are supported. Application mode at the logging.pattern.level%5p log level. Only the default logback settings are supported. Logging.pattern.rolling-file-name$ {LOG_FILE}.% d {yyyy-MM-dd}.% i.gz mode for rolling log file names. Only the default logback settings are supported. Logging.register-shutdown-hookfalse registers a shutdown hook for the logging system when it initializes it. Add @ EnableAspectJAutoProxy to spring.aop.autotrue. Whether spring.aop.proxy-target-classtrue wants to create a subclass-based (CGLIB) proxy (true) instead of a standard Java interface-based proxy (false). Whether spring.application.admin.enabledfalse enables the administrative features of the application. The JMX name of the spring.application.admin.jmx-nameorg.springframework.boot:type=Admin,name=SpringApplication application management MBean. Spring.application.name

Application name. Spring.autoconfigure.exclude

The automatic configuration class to exclude. Spring.banner.charsetUTF-8Banner file encoding. The bit depth used by spring.banner.image.bitdepth4.0 for ANSI colors. The supported values are 4 (16 colors) or 8 (256 colors). Spring.banner.image.height

The height of the banner image, in chars (based on image height by default). Whether the picture of the dark terminal theme of spring.banner.image.invertfalse should be upside down. Spring.banner.image.locationclasspath:banner.gif banner picture file location (you can also use jpg or png). Spring.banner.image.margin2.0 left-hand image margin in characters. The pixel mode to be used when spring.banner.image.pixelmodeTEXT renders the image. The width of the spring.banner.image.width76.0 banner image, in chars. Spring.banner.locationclasspath:banner.txt banner text resource location. Whether spring.beaninfo.ignoretrue skips searching for the BeanInfo class. Spring.codec.log-request-detailsfalse records the table data at the DEBUG level and the title at the TRACE level. Spring.codec.max-in-memory-size

The limit on the number of bytes that can be buffered whenever the input stream needs to be aggregated. This applies only to automatically configured WebFlux servers and WebClient instances. By default, this option is not set, in which case it applies to the default values for each codec. Most codecs are limited to 256K by default. Spring.config.additional-location

In addition to the default values, the profile location is also used. Spring.config.location

Replace the profile location of the default value. Spring.config.nameapplication profile name. Spring.info.build.encodingUTF-8 file encoding. The location of the build-info.properties file generated by spring.info.build.locationclasspath:META-INF/build-info.properties. Spring.info.git.encodingUTF-8 file encoding. The location of the git.properties file generated by spring.info.git.locationclasspath:git.properties. Spring.jmx.default-domain

JMX domain name. Spring.jmx.enabledfalse exposes the administrative Bean to the JMX domain. Spring.jmx.servermbeanServerMBeanServer bean name. Whether spring.jmx.unique-namesfalse should guarantee that the runtime object name is unique. The shutdown timeout for any phase of spring.lifecycle.timeout-per-shutdown-phase30s (SmartLifecycle beans group with the same Phase value). Whether spring.main.allow-bean-definition-overridingfalse allows bean definition overrides by registering a definition with the same name as the existing definition. The mode used to display banners when the spring.main.banner-modeconsole application is running. Spring.main.cloud-platform

Automatic detection of overlay cloud platform. Whether spring.main.lazy-initializationfalse should initialize lazily. Whether spring.main.log-startup-infotrue records information about the application at startup. Whether the spring.main.register-shutdown-hooktrue application should register a shutdown hook. Spring.main.sources

The source (class name, package name, or XML resource location) to include in the ApplicationContext. Spring.main.web-application-type

The flag used to explicitly request a specific type of Web application, if not set, is automatically detected based on classpath. If it is not set, it is automatically detected according to classpath. Spring.mandatory-file-encoding

The expected character encoding that the application must use. Whether spring.messages.always-use-message-formatfalse always applies MessageFormat rules or even parses messages with no parameters. Spring.messages.basenamemessages is a comma-separated list of base names (essentially a fully qualified classpath location), each of which follows ResourceBundle conventions, but support for slash-based locations has been relaxed. If it does not contain a package qualifier, such as "org.mypackage", it will be resolved from the classpath root directory. Spring.messages.cache-duration

Loaded resource bundle file cache time. When not set, the bundled file will be cached forever. If no suffix of duration is specified, seconds are used. Spring.messages.encodingUTF-8 information bundling coding. If spring.messages.fallback-to-system-localetrue turns off this feature, the only fallback will be the default file (for example, the "messages.properties" of the "messages" base name). Whether spring.messages.use-code-as-default-messagefalse uses the message code as the default message instead of throwing "NoSuchMessageException". Recommended only during development. Spring.output.ansi.enableddetect configures ANSI output. Spring.pid.fail-on-write-error

If you use ApplicationPidFileWriter but cannot write to the PID file, it fails. Spring.pid.file

The location of the PID file to write (if ApplicationPidFileWriter is used). Spring.profiles

At least one of the comma-separated list of profile expressions should match to include the file. Spring.profiles.active

A comma-separated list of active profiles. Can be overridden by a command line switch. Spring.profiles.include

Unconditionally activate the specified comma-separated list of profiles (if YAML is used, activate the list of profiles). Whether spring.quartz.auto-startuptrue automatically starts the scheduler after initialization. Spring.quartz.jdbc.comment-prefix [#, -] SQL initializes the prefix for single-line comments in the script. Spring.quartz.jdbc.initialize-schemaembedded database schema initialization mode. The path to the SQL file that spring.quartz.jdbc.schemaclasspath:org/quartz/impl/jdbcjobstore/tables_@@platform@@.sql uses to initialize the database schema. Spring.quartz.job-store-typememory quartz shop type. Whether the job configured by spring.quartz.overwrite-existing-jobsfalse should overwrite the existing job definition. Spring.quartz.properties.*

Additional Quartz Scheduler attribute. The name of the spring.quartz.scheduler-namequartzScheduler scheduler. The delay time for the scheduler to start after spring.quartz.startup-delay0s initialization is complete. If you don't need to run any jobs before the entire application starts, it makes sense to set this property. Whether spring.quartz.wait-for-jobs-to-complete-on-shutdownfalse waits for the running work to finish when shutting down. Whether the spring.reactor.debug-agent.enabledtrue reactor commissioning agent should be enabled when the reactor tool exists. Whether spring.task.execution.pool.allow-core-thread-timeouttrue allows core threads to time out. This can achieve the dynamic growth and contraction of the pool. The number of spring.task.execution.pool.core-size8.0 core threads. The time limit that an spring.task.execution.pool.keep-alive60s thread can remain idle before it is terminated. Spring.task.execution.pool.max-size

The maximum number of threads allowed. If the task is full of queues, the pool can expand to that size to accommodate the load. Ignored if the queue is unconstrained. Spring.task.execution.pool.queue-capacity

Queue capacity. Unlimited capacity does not increase the queue pool, so the maximum capacity attribute is ignored. Whether the spring.task.execution.shutdown.await-terminationfalse executor should wait for the scheduled task to be completed at shutdown. Spring.task.execution.shutdown.await-termination-period

The maximum amount of time the executor should wait for the remaining tasks to be completed. Spring.task.execution.thread-name-prefixtask- is used as the prefix for the newly created thread name. The maximum number of threads allowed by spring.task.scheduling.pool.size1.0. Whether the spring.task.scheduling.shutdown.await-terminationfalse executor should wait for the scheduled task to be completed at shutdown. Spring.task.scheduling.shutdown.await-termination-period

The maximum amount of time the executor should wait for the remaining tasks to be completed. Spring.task.scheduling.thread-name-prefixscheduling- is used as the prefix for the newly created thread name. Tracefalse enables trace logging. The above is what all the configuration properties in the SpringBoot shared by the editor refer to. If you happen to have similar doubts, please refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.