After further investigation I isolated the problem to a timing issue in Felix. There is a tiny window of time where the Felix configuration manager is ready to accept requests but our bundle had not started yet. Our main application POSTs configuration over to Sling, and it managed to hit that time window. I was able to reproduce it by spamming the Sling server with configuration POSTs while it was starting up.
We were launching our own bundle with level 20... I changed it to level 0 and the problem went away, presumably because the configuration metadata is immediately available. -----Original Message----- From: Bertrand Delacretaz [mailto:[email protected]] Sent: Thursday, March 17, 2016 6:15 AM To: users Subject: Re: Configuration data types Hi, On Wed, Mar 16, 2016 at 9:24 PM, Roll, Kevin <[email protected]> wrote: > ...I dug into Felix a bit and found that the code that writes these files [1] > *always* writes the data type, *unless* that type happens to be String... I have no idea what's going on but suggest setting a breakpoint in that method to check what calls it with incorrect values. -Bertrand
