| Knowledgebase Home | Contact |
 Search the Knowledgebase |
 Jump to ID |
 Browse by Category |
| An Audium application that uses a Database element with JNDI logs an error | ||||||||||||
| Categories: Audium Call Services 3.4.x and 3.5, Audium Studio (3.4.x) | ||||||||||||
This article describes some debugging steps to take if an Audium application that includes a Database element logs an error at runtime. SYMPTOMS An error similar to the following is logged: SERVER ERROR: An Audium element encountered an exception. The exception was: There was a problem looking up the JNDI data source 'jdbc/test' If a JSP (or other dynamic language) script is written to test the JNDI connection, it may work as expected. RESOLUTION There are several places to look for the cause of this problem: Your application server's JNDI configuration - Please refer to your application server's documentation for detailed instructions about how to configure a JNDI data source. If a web-based management system is available, it is generally recommended that this be used, in order to avoid syntax errors while editting the configuration files. For information about configuring a JNDI data source under Tomcat, this site may be helpful. - Once you have ensured that the data source is properly configured, try accessing it through Java or some other language that supports database access via JNDI. If this works, then your application server is configured properly. The configuration of the Database element - If the element is using a complex query, change it to use a simple one just for testing (i.e. SELECT * FROM some_table_name). - Change the type to "Single" for testing purposes. - Set the JNDI name to the name of your JNDI connection (important note: Do not preface the connection name with any special codes such as "jdbc/" or "java:comp/env/jdbc". If your connection is named "myconnection", this is exactly what should appear in this setting). If these changes are followed, the Database element should work as expected (assuming that your application server is properly configured). Once the element is working, change each setting back one-by-one (if appropriate) to what your application actually requires, to isolate which of these settings is causing the error. |
Print this page
Post a comment
| Visitor Comments |
| No visitor comments posted. Post a comment |
| Attachments |
| No attachments were found. |