Maybe people at the DDF can put their heads together and help solve this problem if there is time ;)
I looked at https://ops4j1.jira.com/wiki/spaces/PAXEXAM4/pages/54263891/Logging+Configuration and hoped that https://git.opendaylight.org/gerrit/#/c/70092/ will solve this issue, but it didn't. Not sure where to go next. -Lori On Wed, Mar 7, 2018 at 12:58 PM, Lori Jakab <lorand.jakab+...@gmail.com> wrote: > Bumping the thread, maybe someone gets a chance to take a look. See > also the attachment. > > On Fri, Mar 2, 2018 at 10:59 AM, Lori Jakab <lorand.jakab+...@gmail.com> > wrote: >> Hi again, >> >> Here's some progress, but no success yet. I created one patch for >> controller and one for lispflowmapping: >> >> https://git.opendaylight.org/gerrit/#/c/68992/ >> https://git.opendaylight.org/gerrit/#/c/68993/ >> >> Building lispflowmapping locally after having built the patched >> controller, while our integration tests were running, I peeked into >> the >> src/opendaylight/lispflowmapping/integrationtest/target/exam/34657ef9-8712-4a1e-a25d-40a9c3a81d1e/etc/org.ops4j.pax.logging.cfg >> file, which was the resulting logging configuration file in the >> PaxExam environment, and which I attached to this email. I don't see >> anything off, but I still don't get any log output in >> integrationtest/target/surefire-reports/org.opendaylight.lispflowmapping.integrationtest.MappingServiceIntegrationTest-output.txt >> >> Any further suggestions? >> >> Thanks, >> -Lori >> >> On Thu, Mar 1, 2018 at 3:37 PM, Sam Hague <sha...@redhat.com> wrote: >>> >>> >>> On Thu, Mar 1, 2018 at 3:43 AM, Stephen Kitt <sk...@redhat.com> wrote: >>>> >>>> Hi Lori, >>>> >>>> On Wed, 28 Feb 2018 20:22:49 +0200 >>>> Lori Jakab <lorand.jakab+...@gmail.com> wrote: >>>> > Some time between January 11th and January 17th something changed that >>>> > affects the integration test logging in the lispflowmapping project. >>>> > See the before and after examples here: >>>> > >>>> > >>>> > https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/lispflowmapping-maven-verify-oxygen-mvn33-openjdk8/91/integrationtest/target/surefire-reports/org.opendaylight.lispflowmapping.integrationtest.MappingServiceIntegrationTest-output.txt.gz >>>> > >>>> > >>>> > https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/lispflowmapping-maven-verify-oxygen-mvn33-openjdk8/93/integrationtest/target/surefire-reports/org.opendaylight.lispflowmapping.integrationtest.MappingServiceIntegrationTest-output.txt.gz >>>> > >>>> > I'm reaching out to the odlparent-dev list first to see maybe you have >>>> > an idea what could potentially be causing this, some change in Karaf >>>> > or Pax-Exam, and if there is anything you recommend me to investigate? >>>> >>>> This could well be related to the switch from Log4J to Log4J2 as the >>>> default logging provider. If you’re overriding >>>> etc/org.ops4j.pax.logging.cfg you need to make sure your configuration >>>> properties start with “log4j2.” instead of “log4j.”. See the default >>>> org.ops4j.pax.logging.cfg provided by our Karaf distribution for >>>> details... >>> >>> Here is a patch to csit where we made the updates. Notice also in addition >>> to changing >>> from log4j to log4j2 that the module and level settings have changed. >>> >>> https://git.opendaylight.org/gerrit/67749 >>>> >>>> >>>> Regards, >>>> >>>> Stephen >>>> >>>> _______________________________________________ >>>> Odlparent-dev mailing list >>>> odlparent-...@lists.opendaylight.org >>>> https://lists.opendaylight.org/mailman/listinfo/odlparent-dev >>>> >>> _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
