Spring Boot version: 2.1.8.RELEASE
When developing a spring boot application. Most of times we just put it on the given property with a value:
spring.profiles.active = myProfile
But sometimes we don't. While a standalone spring boot application or when running on a wildfly, when this property is not set, the default property value will be "default".
No active profile set, falling back to default profiles: default
When running on a Websphere Application Server (tested on version 9.0.0.11), the default value will just be "@spring.profile.active@".
The following profiles are active: @spring.profile.active@
Shouldn't it be just like standalone and wildfly?
Thanks
Comment From: snicoll
When running on a Websphere Application Server (tested on version 9.0.0.11), the default value will just be "@spring.profile.active@".
This looks like an unresolved token to me. Something else is setting that property to @spring.profile.active@ (maybe a token that wasn't filtered by Maven?).
There is nothing in Spring Boot that sets this property to such value. Can you please review your arrangement? If you have a place where you set that property, you may want to double check it's not set to this value by your build when you package the app for WAS.
Comment From: daviMustafa
I'll look forward but when I compiled the package I wasn't even setting this property. I just left it application.properties without it.
Comment From: daviMustafa
Ok, fixed. It was a problem on my Websphere picking up old configurations when it was suppose to pick up the new ones.
Comment From: snicoll
Thanks for letting us know.