3 Replies Latest reply on Feb 15, 2011 9:56 PM by jaikiran

    suspicious AsynchronousClientInterceptor logging

    jhutton

      I'm seeing a lot of log messages such as

       

      13:49:30,869 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,869 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,869 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,869 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,869 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,870 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,870 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,870 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

      13:49:30,870 INFO  [org.jboss.ejb3.async.impl.interceptor.AsynchronousClientInterceptor] OID: null

       

      repeated over and over when invoking a standard method on a Stateless EJB from a jax-rs end point, using JBoss AS6 and RestEasy. The app in question contains a web-app that uses many more SLSBs in the same way, but the log messages only appear when the jax-rs end point is invoked.

       

      I'm not using the @Asynchronous annotation at all with the SLSB in question. Does anyone know what the cause of this might be?