Ok, well, it looks like I have found my problem, which I expect to be unique.
I was receiving this error message because I had a config file in my
application's classpath called app.properties.ear. This was actually in an
ejb-jar.jar file in the application ear file.
JBoss seemed to get quit
I too have just started experiencing this problem in development on a working
build, after several months of successful deployment on 4.0.3sp1.
I have googled a lot on this and seen little bits of info (like make sure there
isn't an empty 'classpath:" setting in our EAR MANIFEST.MF), but nothing
