JamonPerformanceMonitorInterceptor registers double

[mortenhaugen]

Having the following definitions:

 <aop:config proxy-target-class="true">
  	<aop:advisor 
  		advice-ref="jamonInterceptor"
  		pointcut="execution(* abc.Test.query(..))"/>

  </aop:config>

  <bean id="jamonInterceptor" class="org.springframework.aop.interceptor.JamonPerformanceMonitorInterceptor">
        <property name="trackAllInvocations" value="true"/>
    </bean>

JAMon (jamonadminapi.jsp) shows 2 hits, while the intercepted Test.query method is actually called just once (verified by debugging and by tracing). JAMon shows identical execution time for the "two" executions, and LastAccess time = FirstAccess time.
I have of course tried several times, resetting JAMon between each try.

Has anyone experienced similar "double" hits in JAMon, and even have an explanation and a solution?

[mortenhaugen]

I found a connection between the double JAMon hits and session scope / <aop:scoped-proxy/>.
This gives double hits:

<bean id="test" class="abc.Test" scope="session">
     <aop:scoped-proxy/>
</bean>

while this gives just the expected single hits:

<bean id="test" class="abc.Test">
</bean>

(The abc.Test class is referenced from a singleton bean).

Is there a way to avoid these double hits?

[wpoitras]

Setting a breakpoint in Test.query might give you some insight into where Spring is calling it twice.

[mortenhaugen]

Spring does not call Test.query twice. It's just the JamonPerformanceMonitorInterceptor that registers the call twice when the Test bean is in session scope (and thus proxied). I suspect the proxying to cause the double interception/registration...