You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Leo de Blaauw <Le...@qnh.nl> on 2008/05/07 08:50:27 UTC

Name Not Found exceptions

Hi All,
 
Could someone on here shed some light on the following exception(lots of em)
in our logfiles for glassfish:
 
[#|2008-05-07T08:36:16.936+0200|SEVERE|sun-appserver9.1|javax.enterprise.syst
em.core.naming|_ThreadID=14;_ThreadName=pool-1-thread-8;org.apache.cxf.transp
ort.ConduitInitiatorManagerImpl/bus;_RequestID=85853593-22e0-4157-90e9-e452cc
8b38d3;|NAM0006: JMS Destination object not found:
org.apache.cxf.transport.ConduitInitiatorManagerImpl/bus|#]
 
All in all the system functions just fine, just seems the default cxf:bus in
our Spring applicationcontext,
works just fine. To me it seems this default bus just tries to initialize its
stuff via jms first and goes
default on another way if that fails. What bothers me though is this
splattering of exceptions wich to
our system admins signals something very wrong with the application if they
find exceptions in the log
files. It seems better to me to either log this on the DEBUG level and signal
one warning that the bus
is defaulting to show its not really a severe system error.

Regards,

Leo de Blaauw