5 Replies Latest reply on Feb 3, 2009 6:21 AM by cicinsain

JBoss AS InterceptorRegistry warning

bdlink Dec 13, 2008 5:51 PM

What does the following warning mean, where is it documented, what do I do to get rid of it? I know EJBTHREE-1246 says bean developers do not have to worry. Example is from O'Reilly EJB3 workbook. example 4.1.

13:11:44,515 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, Inte
rceptorRegistry should be used via the bean container
13:11:44,515 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, Inte
rceptorRegistry should be used via the bean container
13:11:44,515 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void com.titan.travelagent.T
ravelAgentBean.createCabin(com.titan.domain.Cabin)
13:11:44,515 WARN [InterceptorRegistry] applicable interceptors is non-existent for public com.titan.domain.Cabin com.t
itan.travelagent.TravelAgentBean.findCabin(int)
13:11:44,531 WARN [InterceptorRegistry] applicable interceptors is non-existent for public void com.titan.travelagent.T
ravelAgentBean.createCabin(com.titan.domain.Cabin)
13:11:44,531 WARN [InterceptorRegistry] applicable interceptors is non-existent for public com.titan.domain.Cabin com.t
itan.travelagent.TravelAgentBean.findCabin(int)

1. Re: JBoss AS InterceptorRegistry warning

jsb Jan 15, 2009 8:34 PM (in response to bdlink)

I'd like to know more about this as well. If a bean developer may safely ignore this warning, why am I being warned at all?

More immediately, when we run our load tests, we end up with gigs of log file filled with warnings. We work around this by moving the logging level from WARN to ERROR or filtering out this particular warning, but if it's important enough to warn us, I feel funny about hiding it.

It would be good to know what it means and what could or should be done about it.
Actions
2. Re: JBoss AS InterceptorRegistry warning

mapoitras Feb 2, 2009 1:39 PM (in response to bdlink)

I would be interested in finding out more about this as well. If someone has an answer for us, that would be appreciated.
Actions
3. Re: JBoss AS InterceptorRegistry warning

alrubinger Feb 2, 2009 2:11 PM (in response to bdlink)

https://jira.jboss.org/jira/browse/EJBTHREE-1709

S,
ALR
Actions
4. Re: JBoss AS InterceptorRegistry warning

cicinsain Feb 3, 2009 4:39 AM (in response to bdlink)

I suspect that has something to do with Java 6 update 12. Infact, I never had that error before installing Java 6u12. And also the simple fact that this problem appears the same day Java 6u12 was released, makes me suspecting even more.
Actions
5. Re: JBoss AS InterceptorRegistry warning

cicinsain Feb 3, 2009 6:21 AM (in response to bdlink)

Sorry, I was completely wrong! In my case it happened because the input file was not in the right place.
Actions

Go to original post