This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
My apologies for asking what I hope will be a fairly simple question. I'm relatively new to deployment of code to JBOSS, and I'm not sure where to start looking for the answer to this problem.
I have a .war that I have developed under Eclipse, and have deployed to JBOSS through Eclipse's automated deployment tool (I personally prefer Maven's command line interface, but I'm trying to get away from my "green screen" background, and trying to give GUI's a chance). I have moderately extensive unit tests written that SHOULD expose any properties file problems before I deploy the code, and the tests do not indicate that I should have a problem.
I can't think of any "timing" condition that would cause the application not to be able to find a file, but I can't think of any reason why a second attempt would find the file in the .war file when the first attempt would fail.
Any push in the right direction would help; I'm stuck for an angle from which to approach this problem.
Are you sure the reason you're not getting that error on the second attempt isn't because something else is happening sooner than when that error would get hit? In other words, perhaps on the second attempt, the application is not getting as far.
Anyway, you're not saying very much about what is going on with the application. What is the exception you're getting? Is there no way you can debug that to determine what the path is to the file the application is actually trying to find? Once we know that, it should be a simple matter to find where the application really is, and bring the real issue to light.
All you've said is the application can't find a file. Not much to go on there...
Joined: Mar 08, 2010
Thanks for the reply.
And now that I think it through; you're entirely correct, and this was a stupid developer error. How thoroughly embarrassing!
The properties file is used for logging; once the loggers are configured, I theoretically never have to read the file again, so subsequent calls don't even try. <sigh> There is a secondary problem with the code that had led me down the wrong path on this one, but even *I* should have figured this out on my own!
Mark E Hansen
Joined: Apr 01, 2009
Don't be embarrassed. Often times, I need a second pair of eyes to see some really simple mistakes I've made, and I've been developing since the early 1980's.