[ome-users] how to turn down the logging of omero3 beta 2.3

[josh.moore at gmx.de]

Hi again, Bernhard,

there are a couple of more categories that need to be added to make
non-OMERO things silent, specifically:

  <category name="com.arjuna">
  <category name="javax.enterprise">
  <category name="org.jnp">

which are already in place in this log4j config file:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: jboss-log4j.xml
Type: application/octet-stream
Size: 6124 bytes
Desc: not available
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-users/attachments/20081105/8b8ab0d5/attachment.obj>
-------------- next part --------------

when using that my output looks like this:

... Initializing EHCache CacheManager
... Loaded store ome.services.sharing.BlobShareStore at 5e14d9 with -1 shares and -1 objects
... Initialized FullTextAnalyzer
... Verified database patch: OMERO3A__11
... -------------------------------------------------
... OMERO Version: 3.0-Beta3 (Rev: 2461) Ready.
... -------------------------------------------------
... no update needed
... Initializing Full-Text Indexer
... Starting Quartz Scheduler now
... Calculating ExtendedMetadata...
... JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 51s
...  Meth:      interface ome.services.util.Executor$Work.doWork
...  Args:      [null, null, ome.tools.spring.InternalServiceFactory at 29566a]
...  Auth:       user=0,group=0,event=105600(Sessions)
... Adding log:INSERT,class ome.model.meta.Session,15401

Could you see if that works for you?
~J

josh.moore at gmx.de writes:
 > 
 > Bernhard Voigt writes:
 >  > hi all!
 > 
 > Hi Bernhard,
 > 
 >  > ?s there a way to turn down the logging which goes to
 >  > jboss/server/default/log? i've tried to reduce the logging in log4j.xml in
 >  > the omero folder prior to deployment but this only changes the output of the
 >  > jboss console log. i tried to change the logging setting in
 >  > jboss/server/default/conf/jboss-log4j.xml but it was not very successfull.
 >  > still lots of debug messages from several classes e.g. ome.logic.AdminImpl,
 >  > org.quartz.core.JobRunShell,org.springframework.jmx.support.JmxUtils and
 >  > others.
 > 
 > The jboss/server/default/conf/jboss-log4j.xml should be the proper place to
 > do it. The most straight-forward way would be to add the line:
 > 
 >   <param name="Threshold" value="INFO"/>
 > 
 > or 
 > 
 >   <param name="Threshold" value="WARN"/>
 > 
 > to the <appender name="FILE" element. You can see an example of this
 > under the <appender name="CONSOLE" element. This will completely limit
 > all output regardless of how the categories are configured.
 > 
 > The other option is to individually limit each category that you are
 > seeing. *However*, the spring & quarz categories should already be
 > limited, which means something may be amiss. I'll look into it and get
 > back to you.
 > 
 > Cheers,
 > ~Josh.
 >