Ok, so you have developed an enterprise application using JBoss. You deploy, and you fire up your web app, and it hangs. The web site never comes up and before you know it your processor is screaming. You check and double check. You're kicking in chairs and knocking down tables, in a restaurant, in a western town. What to do?
Well, I had this problem a while ago and corrected it. It came up again this morning. I knew I had resolved something similar. It was the same problem and of course the same solution.
The problem is that JBoss isn't a graceful server if you get a JNDI name wrong. So if you have this problem, double check the following:
- Your configuration files like your ejb-jar.xml or your web.xml. It is possible that names, links, or references are not matching up correctly.
- Your code. Remember that the standard lookup prefix is java:comp/env/ when looking up resources on a J2EE server. Check the names of the resources you are looking for in your code. This happened to be my problem consistently.
I hope this helps. I will check the mailing lists and bug databases and see if it has already been taken care of. If it hasn't, I will create a new report. If you have similar problems and/or solutions I would like to see them, so comment away.
Wed, 30 Nov 2005 06:48 PM GMT
You must not catch or report jndi lookups or something. Secondly, all deployment errors are in the logs (server.log or stdout). JBoss has had its bugs over the years but silent naming failures? That is a new one on me.
Wed, 30 Nov 2005 07:29 PM GMT
No I am looking at my code and all my errors march up correctly and float to the surface if anything goes wrong. I think what I will do if I have time is find a small app on the net and break it. If I am wrong I'll fix my app. If I am right I'll report.