oodt-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheryl John <shery...@gmail.com>
Subject Re: Crawler messages from PGE task in a workflow
Date Thu, 10 Nov 2011 08:50:48 GMT
Yep, this majorly reduced the log messages because of the springframework
logs. I thought this was something that should be turned off from the
crawler's properties.

Thanks a lot!


On Thu, Nov 10, 2011 at 12:19 AM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Thanks Sheryl:
>
> Try adding:
>
> org.springframework.level = OFF
>
> To get rid of a lot of the Spring logging messages...
>
> I'll keep looking.
>
> Cheers,
> Chris
>
> On Nov 9, 2011, at 11:40 PM, Sheryl John wrote:
>
> > Chris,
> >
> > Yup, I was using the workflow one.
> > logging properties : http://pastebin.com/2Y03uQKX
> >
> > Workflow logs  : http://pastebin.com/DnL8Rh4G
> >
> > Thanks,
> >
> > On Wed, Nov 9, 2011 at 11:23 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> > Thanks Sheryl.
> >
> > Can you post your logging.properties? You need to make sure that it's
> being loaded in the workflow one. Are you using resource manager,
> > or just workflow right now?
> >
> > Just use pastebin and you can post the logging.properties you should be
> good. As for that exception below, Bfost, any idea?
> >
> > Cheers,
> > Chris
> >
> > On Nov 9, 2011, at 11:17 PM, Sheryl John wrote:
> >
> > > Hi Chris,
> > >
> > > Thanks for pointing out how to turn on/off the log levels.
> > > Yup, I'm getting the product id of the ingested file.
> > > I tried adding some log levels for the workflow manager and the other
> packages like the crawler, but it did not reduce the log messages.
> > >
> > > I checked the log files and noticed that it was also throwing out some
> exceptions like the following:
> > >
> > > FINE: Ignoring namespace handler
> [org.springframework.scripting.config.LangNamespaceHandler]: handler class
> not found
> > > java.lang.ClassNotFoundException:
> org.springframework.scripting.config.LangNamespaceHandler
> > >       at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> > >       at java.security.AccessController.doPrivileged(Native Method)
> > >       at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> > >       at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> > >       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> > >       at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> > >       at
> org.springframework.util.ClassUtils.forName(ClassUtils.java:249)
> > >       at
> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.initHandlerMappings(DefaultNamespaceHandlerResolver.java:117)
> > >       at
> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(DefaultNamespaceHandlerResolver.java:96)
> > >       at
> org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<init>(DefaultNamespaceHandlerResolver.java:83).....
> > > ...
> > > And two other exceptions like the above.
> > >
> > >
> > > On Wed, Nov 9, 2011 at 10:14 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> > > 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.
> > >
> > > Thanks!
> > >
> > > Cheer,s
> > > Chris
> > >
> > >
> > > 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 getBean
> > > > 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
> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >
> > >
> > >
> > >
> > > --
> > > -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
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
> >
> >
> > --
> > -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
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>


-- 
-Sheryl

Mime
View raw message