I have a similar issue with an application I am trying to analyze using Insight. I deployed the application by copying the .war file in the webapps directory (i.e. it is not running in the ROOT context).
First of all, using the default configuration (which works fine on regular (non-Spring) Tomcat), the application won't start at all, and I get a lengthy Exception stack trace in my applications log file that the "myDataSource" bean could not be instanciated. The root cause is a javax.naming.NamingException with no error message.
The "myDataSource" bean is configured as follows:
By default, the application provides the configuration for the resource in its META-INF/context.xml file. I tried moving the resource definition into the tc server's server.xml file under <GlobalNamingResources>, but I still get the same error.
<bean id="myDataSource" class="org.springframework.jndi.JndiObjectFactoryBean">
So I changed the data source definition to skip JNDI and configure it directly in my Spring configuration, like so:
Now I can run the application on tc server and it shows up in Insight as well, but the traces contain nothing but information about the HTTP requests made (no call tracing, and no SQL tracing either, just like the OP). Also, under "Application Health", there are no endpoints listed.
<bean id="myDataSource" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
<property name="driverClassName" value="com.mysql.jdbc.Driver"/>
<property name="url" value="jdbc:mysql://localhost:3306/mydatabase"/>
<property name="username" value="xxxxxxx"/>
<property name="password" value="xxxxxxx"/>
I tried moving the MySQL JDBC driver into the webapp/lib directory, but it doesn't change anything. Still no SQL trace information available.
I'm using mysql-connector-java-5.0.7-bin.jar, the application is built using Spring 2.5 and Hibernate 3.0 (through JPA).