Properties Collection: Error unable to bootstrap local properties

I am getting an error printed to the console stating unable to bootstrarp local properties. The properties are loaded at application time as the static variable APP_SETTINGS the rest of the application uses the Fully qualified class name to get to the properties files. It sounds like it may not be reading the .properties file but, everything is still wrote to the logfiles that are set in the properties file

heres some code

Main Constructor

publicstaticvoid main(String[] args){

APP_SETTINGS =new Properties();

AGENTS =new Hashtable<String, Agent>();

readConfig(args[0]);

APP_LOG = com.fidelitysolutionsinc.evps.logging.ApplicationLog.getInstance();

Thread ald =new AgentLoadingDaemon();

ald.start();

Thread th1 =new com.fidelitysolutionsinc.evps.http.HTTP();

AgentProcessor ap =new AgentProcessor();

th1.start();

ap.run();

}

publicstaticvoid readConfig(String file){

APP_SETTINGS.load(new FileInputStream(file));

[..OMITTED PRINT Messages...]

so as you can see the the main calls the readCofig and passes it the file name of the properties file as was provided in the main args parameter. This part works, i get no errors, its only happens later on during execution of the app.

All classes get to the APP_SETTINGS using the fully qualified classname: com.fidelitysolutionsinc.evps.EVPS.APP_SETTINGS.

Here is how some example code of how I am accessing the properties

private Properties appSettings = com.fidelitysolutionsinc.evps.EVPS.APP_SETTINGS;

StringBuffer fn =new StringBuffer();

fn.append(appSettings.getProperty("APPLICATION_HOME"));

Any suggestions

[2295 byte] By [joshholla] at [2007-11-27 5:08:28]
# 1
> I am getting an error printed to the console stating> unable to bootstrarp local properties.Then to start with, you should find the piece of code that prints this message.
DrClapa at 2007-7-12 10:27:56 > top of Java-index,Core,Core APIs...
# 2
Thats it, I am not explicitly printing the the message, and it happens at run time, I have try/catches everywhere and it is not throwing any exceptions. I guess i'll just put printlns after every time i access the properties
joshholla at 2007-7-12 10:27:56 > top of Java-index,Core,Core APIs...
# 3
But something is printing the message. Perhaps it's code that you have not looked at yet. (Do a search across all your code for that message.) Or perhaps the code you have does not match the code that is actually running. This would be a bad thing if it were true.
DrClapa at 2007-7-12 10:27:56 > top of Java-index,Core,Core APIs...
# 4
OK if its not anything in the java stack then it must be something in a library I'm using. because i don't have any System.out.println's any where in the code, It's all being logged using a custom logging framework. Even exceptions are printed to a string writer so they can be logged.
joshholla at 2007-7-12 10:27:56 > top of Java-index,Core,Core APIs...