| After deploying the application, you may encounter several problems. These are detailed in the following list, along with possible solutions: You tried deploying your application, but it did not get deployed. You got an error on the Administration Console saying that the JNDI name of your Data Source was not found. Solution: Check whether the name you have specified in the weblogic-cmp-rdbms-jar.xml file is exactly the same as what you have mapped in Tx Data Source settings. You tried deploying your application, but you got an error on the console saying that the connection pool does not exist. Solution: Check the name of your connection pool in the Tx Data Source settings. This should be exactly the same as the name of your connection pool. This name setting is case sensitive. When you type out the address http://localhost:7001/AirlinesApp/Welcome, you get a message saying "File not found." Solution: First, check to see whether you have placed the JSP files in the correct directory. Then check your web.xml file to see whether you have properly mapped the location of the files to the names of the files. These are the most common errors. Your application deployed, and you tried out the first navigation. After typing out the search criteria, you didn't get any results, although your database has values exactly matching your query. You got a message saying that your EJB was not found. Solution: The weblogic-ejb-jar.xml has a mapping for the local-jndi-name tag to map to your local EJB. If you map your EJB jndi name in the jndi-name tag instead, you will encounter this problem. |