You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by "Mallder, Valerie" <Va...@jhuapl.edu> on 2016/07/13 20:05:25 UTC
Where is this log4j error warning coming from in OODT 1.0?
Hello,
I am in the process of integrating OODT 1.0 into my pipeline (upgrading from 0.10) and I am getting two new warnings in my log file. I am only running workflow manager and file manager and nothing else (yes, I had to copy the filemgr (to resolve CoreMetKeys), crawler (to resolve ProductCrawler), and pge (to resolve STDPGETaskInstance) jar files to workflow/lib). Do workflow manager and file manger use log4j now? The regular logger is working fine.
log4j:WARN No appenders could be found for logger (org.apache.commons.httpclient.HttpClient).
log4j:WARN Please initialize the log4j system properly.
Here is how I am starting both applications, you can assume all environment variables shown are set to the intended values and they are shown at the bottom for reference. Let me know if I should change or add a property setting or something here.
# Start file manager
$JAVA_EXECUTABLE -Djava.ext.dirs=${PROJECT_HOME}/lib:${FILEMGR_HOME}/lib \
-Djava.util.logging.config.file=${FILEMGR_LOGGING_PROPS} \
-Dorg.apache.oodt.cas.filemgr.properties=${FILEMGR_PROPS} \
org.apache.oodt.cas.filemgr.system.XmlRpcFileManager --portNum $FILEMGR_PORT &
# Start workflow manager
$JAVA_EXECUTABLE -Djava.ext.dirs=${PROJECT_HOME}/lib:${WORKFLOW_HOME}/lib \
-Djava.util.logging.config.file=${WORKFLOW_LOGGING_PROPS} \
-Dorg.apache.oodt.cas.workflow.properties=${WORKFLOW_PROPS} \
-Dorg.apache.oodt.cas.pge.task.metkeys.legacyMode="true" \
-Dorg.apache.oodt.cas.pge.task.status.legacyMode="true" \
org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager --portNum $WORKFLOW_PORT &
Here are the environment settings
PROJECT_HOME=/project/oodt/dev/jedi
JAVA_EXECUTABLE=/project/oodt/bin/jdk1.8.0_66/bin/java
CURRENT_HOST=slothrop.jhuapl.edu
FILEMGR_HOME=/project/oodt/bin/oodt/cas-filemgr-1.0
FILEMGR_PORT=9016
FILEMGR_PROPS=${PROJECT_HOME}/etc/filemgr/filemgr.properties
FILEMGR_LOGGING_PROPS=${PROJECT_HOME}/etc/filemgr/${CURRENT_HOST}.logging.properties
WORKFLOW_HOME=/project/oodt/bin/oodt/cas-workflow-1.0
WORKFLOW_PORT=9001
WORKFLOW _PROPS=${PROJECT_HOME}/etc/workflow/workflow.properties
WORKFLOW _LOGGING_PROPS=${PROJECT_HOME}/etc/workflow/${CURRENT_HOST}.logging.properties
Thanks for your help!
Val
Re: Where is this log4j error warning coming from in OODT 1.0?
Posted by Tom Barber <to...@meteorite.bi>.
Dunno! I don't believe we've ever created .tar.gz files because the maven
build spits out zip files. I'm sure we could if it was required, but zip is
pretty universal. I pretty much only every build radix builds which just
drags down the maven artifacts, but if you work off of zipped up builds its
something we can deal with.
On Fri, Jul 15, 2016 at 12:54 AM, Mallder, Valerie <
Valerie.Mallder@jhuapl.edu> wrote:
> Hi Tom, thanks for responding. Just wondering where it's coming from since
> it wasn't there before. It's not a big deal, I just try to do my due
> diligence and address the warnings and errors that can easily be addressed.
>
> Hey, here's a another question for you, not too long ago I downloaded a
> .tar.gz file for the 1.0 release and I can't remember where I downloaded it
> from. I went to github today to look for it and when I try to download it
> it only lets me download a .zip file. Where are all the .tar.gz files for
> all the releases? Just curious.
>
> Thanks,
> Val
>
>
> Thanks,
> Val
>
>
> Sent with Good Work (www.good.com)
>
> From: Tom Barber <to...@meteorite.bi>>
> Date: Thursday, Jul 14, 2016, 7:29 PM
> To: dev@oodt.apache.org <de...@oodt.apache.org>>
> Subject: Re: Where is this log4j error warning coming from in OODT 1.0?
>
> Hi Val
>
> Saw your message. I've seen this on umpteen projects but never investigated
> it indepth. I don't believe any of our internal logging has change but of
> course other projects can depend on whatever logging system they so choose.
> My guess would be if they are new, we've probably upgraded the httpclient
> at some point and they changed their logging setup.
>
> This all said, its only a warning, not a full blown error, is it causing
> you grief or are you just wondering where it cropped up from?
>
> Tom
>
> On Wed, Jul 13, 2016 at 9:05 PM, Mallder, Valerie <
> Valerie.Mallder@jhuapl.edu> wrote:
>
> > Hello,
> >
> > I am in the process of integrating OODT 1.0 into my pipeline (upgrading
> > from 0.10) and I am getting two new warnings in my log file. I am only
> > running workflow manager and file manager and nothing else (yes, I had to
> > copy the filemgr (to resolve CoreMetKeys), crawler (to resolve
> > ProductCrawler), and pge (to resolve STDPGETaskInstance) jar files to
> > workflow/lib). Do workflow manager and file manger use log4j now? The
> > regular logger is working fine.
> >
> >
> > log4j:WARN No appenders could be found for logger
> > (org.apache.commons.httpclient.HttpClient).
> > log4j:WARN Please initialize the log4j system properly.
> >
> > Here is how I am starting both applications, you can assume all
> > environment variables shown are set to the intended values and they are
> > shown at the bottom for reference. Let me know if I should change or
> add a
> > property setting or something here.
> >
> > # Start file manager
> > $JAVA_EXECUTABLE -Djava.ext.dirs=${PROJECT_HOME}/lib:${FILEMGR_HOME}/lib
> \
> > -Djava.util.logging.config.file=${FILEMGR_LOGGING_PROPS} \
> > -Dorg.apache.oodt.cas.filemgr.properties=${FILEMGR_PROPS} \
> > org.apache.oodt.cas.filemgr.system.XmlRpcFileManager --portNum
> > $FILEMGR_PORT &
> >
> > # Start workflow manager
> > $JAVA_EXECUTABLE
> -Djava.ext.dirs=${PROJECT_HOME}/lib:${WORKFLOW_HOME}/lib \
> > -Djava.util.logging.config.file=${WORKFLOW_LOGGING_PROPS} \
> > -Dorg.apache.oodt.cas.workflow.properties=${WORKFLOW_PROPS} \
> > -Dorg.apache.oodt.cas.pge.task.metkeys.legacyMode="true" \
> > -Dorg.apache.oodt.cas.pge.task.status.legacyMode="true" \
> > org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager --portNum
> > $WORKFLOW_PORT &
> >
> >
> > Here are the environment settings
> >
> > PROJECT_HOME=/project/oodt/dev/jedi
> > JAVA_EXECUTABLE=/project/oodt/bin/jdk1.8.0_66/bin/java
> > CURRENT_HOST=slothrop.jhuapl.edu
> > FILEMGR_HOME=/project/oodt/bin/oodt/cas-filemgr-1.0
> > FILEMGR_PORT=9016
> > FILEMGR_PROPS=${PROJECT_HOME}/etc/filemgr/filemgr.properties
> >
> >
> FILEMGR_LOGGING_PROPS=${PROJECT_HOME}/etc/filemgr/${CURRENT_HOST}.logging.properties
> > WORKFLOW_HOME=/project/oodt/bin/oodt/cas-workflow-1.0
> > WORKFLOW_PORT=9001
> > WORKFLOW _PROPS=${PROJECT_HOME}/etc/workflow/workflow.properties
> > WORKFLOW
> >
> _LOGGING_PROPS=${PROJECT_HOME}/etc/workflow/${CURRENT_HOST}.logging.properties
> >
> > Thanks for your help!
> > Val
> >
> >
> >
>
RE: Where is this log4j error warning coming from in OODT 1.0?
Posted by "Mallder, Valerie" <Va...@jhuapl.edu>.
Hi Tom, thanks for responding. Just wondering where it's coming from since it wasn't there before. It's not a big deal, I just try to do my due diligence and address the warnings and errors that can easily be addressed.
Hey, here's a another question for you, not too long ago I downloaded a .tar.gz file for the 1.0 release and I can't remember where I downloaded it from. I went to github today to look for it and when I try to download it it only lets me download a .zip file. Where are all the .tar.gz files for all the releases? Just curious.
Thanks,
Val
Thanks,
Val
Sent with Good Work (www.good.com)
From: Tom Barber <to...@meteorite.bi>>
Date: Thursday, Jul 14, 2016, 7:29 PM
To: dev@oodt.apache.org <de...@oodt.apache.org>>
Subject: Re: Where is this log4j error warning coming from in OODT 1.0?
Hi Val
Saw your message. I've seen this on umpteen projects but never investigated
it indepth. I don't believe any of our internal logging has change but of
course other projects can depend on whatever logging system they so choose.
My guess would be if they are new, we've probably upgraded the httpclient
at some point and they changed their logging setup.
This all said, its only a warning, not a full blown error, is it causing
you grief or are you just wondering where it cropped up from?
Tom
On Wed, Jul 13, 2016 at 9:05 PM, Mallder, Valerie <
Valerie.Mallder@jhuapl.edu> wrote:
> Hello,
>
> I am in the process of integrating OODT 1.0 into my pipeline (upgrading
> from 0.10) and I am getting two new warnings in my log file. I am only
> running workflow manager and file manager and nothing else (yes, I had to
> copy the filemgr (to resolve CoreMetKeys), crawler (to resolve
> ProductCrawler), and pge (to resolve STDPGETaskInstance) jar files to
> workflow/lib). Do workflow manager and file manger use log4j now? The
> regular logger is working fine.
>
>
> log4j:WARN No appenders could be found for logger
> (org.apache.commons.httpclient.HttpClient).
> log4j:WARN Please initialize the log4j system properly.
>
> Here is how I am starting both applications, you can assume all
> environment variables shown are set to the intended values and they are
> shown at the bottom for reference. Let me know if I should change or add a
> property setting or something here.
>
> # Start file manager
> $JAVA_EXECUTABLE -Djava.ext.dirs=${PROJECT_HOME}/lib:${FILEMGR_HOME}/lib \
> -Djava.util.logging.config.file=${FILEMGR_LOGGING_PROPS} \
> -Dorg.apache.oodt.cas.filemgr.properties=${FILEMGR_PROPS} \
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager --portNum
> $FILEMGR_PORT &
>
> # Start workflow manager
> $JAVA_EXECUTABLE -Djava.ext.dirs=${PROJECT_HOME}/lib:${WORKFLOW_HOME}/lib \
> -Djava.util.logging.config.file=${WORKFLOW_LOGGING_PROPS} \
> -Dorg.apache.oodt.cas.workflow.properties=${WORKFLOW_PROPS} \
> -Dorg.apache.oodt.cas.pge.task.metkeys.legacyMode="true" \
> -Dorg.apache.oodt.cas.pge.task.status.legacyMode="true" \
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager --portNum
> $WORKFLOW_PORT &
>
>
> Here are the environment settings
>
> PROJECT_HOME=/project/oodt/dev/jedi
> JAVA_EXECUTABLE=/project/oodt/bin/jdk1.8.0_66/bin/java
> CURRENT_HOST=slothrop.jhuapl.edu
> FILEMGR_HOME=/project/oodt/bin/oodt/cas-filemgr-1.0
> FILEMGR_PORT=9016
> FILEMGR_PROPS=${PROJECT_HOME}/etc/filemgr/filemgr.properties
>
> FILEMGR_LOGGING_PROPS=${PROJECT_HOME}/etc/filemgr/${CURRENT_HOST}.logging.properties
> WORKFLOW_HOME=/project/oodt/bin/oodt/cas-workflow-1.0
> WORKFLOW_PORT=9001
> WORKFLOW _PROPS=${PROJECT_HOME}/etc/workflow/workflow.properties
> WORKFLOW
> _LOGGING_PROPS=${PROJECT_HOME}/etc/workflow/${CURRENT_HOST}.logging.properties
>
> Thanks for your help!
> Val
>
>
>
Re: Where is this log4j error warning coming from in OODT 1.0?
Posted by Tom Barber <to...@meteorite.bi>.
Hi Val
Saw your message. I've seen this on umpteen projects but never investigated
it indepth. I don't believe any of our internal logging has change but of
course other projects can depend on whatever logging system they so choose.
My guess would be if they are new, we've probably upgraded the httpclient
at some point and they changed their logging setup.
This all said, its only a warning, not a full blown error, is it causing
you grief or are you just wondering where it cropped up from?
Tom
On Wed, Jul 13, 2016 at 9:05 PM, Mallder, Valerie <
Valerie.Mallder@jhuapl.edu> wrote:
> Hello,
>
> I am in the process of integrating OODT 1.0 into my pipeline (upgrading
> from 0.10) and I am getting two new warnings in my log file. I am only
> running workflow manager and file manager and nothing else (yes, I had to
> copy the filemgr (to resolve CoreMetKeys), crawler (to resolve
> ProductCrawler), and pge (to resolve STDPGETaskInstance) jar files to
> workflow/lib). Do workflow manager and file manger use log4j now? The
> regular logger is working fine.
>
>
> log4j:WARN No appenders could be found for logger
> (org.apache.commons.httpclient.HttpClient).
> log4j:WARN Please initialize the log4j system properly.
>
> Here is how I am starting both applications, you can assume all
> environment variables shown are set to the intended values and they are
> shown at the bottom for reference. Let me know if I should change or add a
> property setting or something here.
>
> # Start file manager
> $JAVA_EXECUTABLE -Djava.ext.dirs=${PROJECT_HOME}/lib:${FILEMGR_HOME}/lib \
> -Djava.util.logging.config.file=${FILEMGR_LOGGING_PROPS} \
> -Dorg.apache.oodt.cas.filemgr.properties=${FILEMGR_PROPS} \
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager --portNum
> $FILEMGR_PORT &
>
> # Start workflow manager
> $JAVA_EXECUTABLE -Djava.ext.dirs=${PROJECT_HOME}/lib:${WORKFLOW_HOME}/lib \
> -Djava.util.logging.config.file=${WORKFLOW_LOGGING_PROPS} \
> -Dorg.apache.oodt.cas.workflow.properties=${WORKFLOW_PROPS} \
> -Dorg.apache.oodt.cas.pge.task.metkeys.legacyMode="true" \
> -Dorg.apache.oodt.cas.pge.task.status.legacyMode="true" \
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager --portNum
> $WORKFLOW_PORT &
>
>
> Here are the environment settings
>
> PROJECT_HOME=/project/oodt/dev/jedi
> JAVA_EXECUTABLE=/project/oodt/bin/jdk1.8.0_66/bin/java
> CURRENT_HOST=slothrop.jhuapl.edu
> FILEMGR_HOME=/project/oodt/bin/oodt/cas-filemgr-1.0
> FILEMGR_PORT=9016
> FILEMGR_PROPS=${PROJECT_HOME}/etc/filemgr/filemgr.properties
>
> FILEMGR_LOGGING_PROPS=${PROJECT_HOME}/etc/filemgr/${CURRENT_HOST}.logging.properties
> WORKFLOW_HOME=/project/oodt/bin/oodt/cas-workflow-1.0
> WORKFLOW_PORT=9001
> WORKFLOW _PROPS=${PROJECT_HOME}/etc/workflow/workflow.properties
> WORKFLOW
> _LOGGING_PROPS=${PROJECT_HOME}/etc/workflow/${CURRENT_HOST}.logging.properties
>
> Thanks for your help!
> Val
>
>
>