oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Crawler messages from PGE task in a workflow
Date Thu, 10 Nov 2011 06:14:46 GMT
Hey Sheryl,

Thanks for your question. If you get something that says: Result: product id .... some long
UUID, you are good.
The log messages are driven by either the resource mgr (if you are running in resmgr mode)
or the workflow manager 
and its logging.properties file. If you look inside of $WORKFLOW/etc/logging.properties (or
the corresponding $RESMGR one), 
then you can add in log levels there, to turn on or off. If you want to reduce the scope of
those messages, you can add a:

> org.apache.oodt.commons.level = SEVERE

to turn off all msgs that are below the SEVERE level and greatly reduce your log footprint.
You can also add other log messages
for packages to reduce those logs too.

Let me know if that helps.



On Nov 9, 2011, at 5:32 PM, Sheryl John wrote:

> Hi,
> I am trying to get an output product from a PGETask ingested into the File Manager after
the task is done in a workflow. 
> Since, this is my first time using the Crawler in the PGETask, I just wanted to confirm
if the messages displayed is what is expected or normal.
> After I kick off the event, the really long list of messages looks like:
> FINE: Creating shared instance of singleton bean 'metFileExtension'
> FINE: Creating instance of bean 'org.apache.oodt.commons.option.handler.BeanInfo#26d58939'
with merged definition [Root bean: class [org.apache.oodt.commons.option.handler.BeanInfo];
scope=singleton; abstract=false; lazyInit=false; autowireCandidate=false; autowireMode=0;
dependencyCheck=0; factoryBeanName=null; factoryMethodName=null; initMethodName=null; destroyMethodName=null;
defined in class path resource [org/apache/oodt/cas/crawl/option/cmd-line-option-beans.xml]]
> Nov 9, 2011 5:13:57 PM org.springframework.beans.factory.support.AbstractBeanFactory
> FINE: Returning cached instance of singleton bean 'MetExtractorProductCrawler'
>  :
> and more springframework related messages.
> In the end, I finally get to  see that data product is ingested with the met file in
the right location. Is it normal to get this long list of the entries? Or does it look like
I've unnecessarily specified something in the configs?
> Thanks 
> Sheryl

Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

View raw message