48

I have a single application.yml configuration file for my Spring Boot app that defines two profiles (as described in the documentation).

When the production profile is enabled, I would like to set the http.maxConnections system property to a custom value, e.g.

spring:
    profiles:
        active: dev
---
spring:
    profiles: dev
---
spring:
    profiles: production
http:
    maxConnections: 15

But this doesn't actually set the system level property; it appears to just create an application-level property. I've verified this through both http://locahost:8080/env and a JMX Console when comparing launching by 

java -jar -Dspring.profiles.active=production myapp.jar

versus 

java -Dhttp.maxConnections=15 myapp.jar

I suppose I could create a bean that's @Conditional on the "production" profile that programmatically callsSystem.setProperty based on my application.yml-defined property, but is there a simpler way through configuration files alone?

bdkosher
  • 5,753
  • 2
  • 33
  • 40

4 Answers4

21

You may try.

@Profile("production")
@Component
public class ProductionPropertySetter {

   @PostConstruct
   public void setProperty() {
      System.setProperty("http.maxConnections", "15");
   }

}
Betlista
  • 10,327
  • 13
  • 69
  • 110
TheKojuEffect
  • 20,103
  • 19
  • 89
  • 125
  • the problem is, you need to redeploy if you want to change this, otherwise you could just modify it and reboot your app – Palcente Apr 27 '16 at 16:41
  • 2
    @Palcente yes, that make sense. I believe you can put properties in `application-production.yml` which will be used in `production` profile. – TheKojuEffect Apr 27 '16 at 16:43
  • 1
    System.setProperty("http.maxConnections", "15");// int is not allowed here :)) – meadlai Mar 19 '19 at 09:32
15

I suppose I could create a bean that's @Conditional on the "production" profile that programmatically callsSystem.setProperty based on my application.yml-defined property, but is there a simpler way through configuration files alone?

I think that's your best bet here. Spring Boot does that itself in its LoggingSystem where various logging.* properties are mapped to System properties.

Note that you'll probably want to set the system properties as early as possible, probably as soon as the Environment is prepared. To do so, you can use an ApplicationListener that listens for the ApplicationEnvironmentPreparedEvent. Your ApplicationListener implementation should be registered via an entry in spring.factories.

Andy Wilkinson
  • 108,729
  • 24
  • 257
  • 242
3

You can inject the environment into the constructor of the class that specifies the beans. This allows you to write application properties to the system properties before the beans are being created.

@Configuration
public class ApplicationBeans {

   @Autowired
   public ApplicationBeans(Environment environment) {
      // set system properties before the beans are being created.
      String property = "com.application.property";
      System.getProperties().setProperty(property, environment.getProperty(property));
   }

   /**
    * Bean that depends on the system properties
    */
   @Bean
   public SomeBean someBean() {
      return new SomeBean();
   }
}
jjoller
  • 661
  • 9
  • 17
-1

You can also use PropertyPlaceholderConfigurer from org.springframework.beans.factory.config to get handle over your properties file

RamBharath
  • 1