Disable "invalid entry for security.provider.X" error message in log file when security.provider.X is empty

A DESCRIPTION OF THE PROBLEM :
My application is running with a custom list of security providers. The list is passed to the application in an alternate java security file like:
% java -Djava.security.properties=/path/to/my/java.security ...

The list of security providers in the file is:
```
security.provider.1=BCFIPS C:HYBRID;ENABLE{All}
security.provider.2=SUN
security.provider.3=BCJSSE fips:BCFIPS
security.provider.4=
```
When I start the application, it outputs "invalid entry for security.provider.4" on standard error, but otherwise behaves as intended.
If I remove the "security.provider.4" line, all providers from master security file with priority 4+ (like SunJSSE, SunJCE) are registered. This is not acceptable.

Can we stop logging "invalid entry..." when an empty entry is encountered?