TopicConnectionFactory not bound

[alphafoo]

Hi-
I have a working application that contains a SLSB and a BMP entity bean. When I deploy it, I get these errors in the JBoss log, although no stack trace is reported and the application continues to deploy and run. I do not use JMS and I do not reference TopicConnectionFactory anywhere in my jboss.jcml file, so I don't know why the error would be there.

Is it required with JBoss to specify a JNDI name for the TopicConnectionFactory even if it is not going to be used?

Here is what I see:

[Container factory] Deploying MyEntityBean
[Container factory] Deploying MySLSBean
[Default] javax.naming.NameNotFoundException: TopicConnectionFactory not bound
[Default] javax.naming.NameNotFoundException: TopicConnectionFactory not bound

[charlesc]

Hi, you need to be more specific about this... what's the JBoss version you're running? Can you deploy any example application without error?

Charles

[alphafoo]

Sorry about the sparse details...I figured it was something obvious that I was missing. I'm running 2.4.3, and yes, I get the error on even the simplest of J2EE apps that contain an EJB.

I played around with the jcml file and have a hypothesis that JBoss is trying to use JMS for reporting/monitoring/metrics. I don't have JMS set up, so it complains when it tries to find the TopicConnectionFactory via JNDI.

Assuming this much is true, is there some way for me to tell JBoss not to do this sort of reporting, and therefore not look for the TopicConnectionFactory?

[alphafoo]

Oh, and I get one "TopicConnectionFactory not bound" message per bean deployed.

[alphafoo]

This is fun, sending messages to myself.

I finally figured out what was going on. My jboss.jcml file had this mbean:

true
false
true
true
false


Setting MetricsEnabled to false stopped JBoss from trying to use JMS topics to publish bean metrics, and the error at startup went away.

[strkrobertm]

Almost 2 years later and I have this same problem. (The not bound WARNing). I'm using 3.0.6 (and 3.2.1) and I set metrics enabled to false (standardjboss.xml) but I still get the warning.

Any ideas?