You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/15 21:38:59 UTC
[jira] [Commented] (APEXCORE-251) Journal output stream is null
error message
[ https://issues.apache.org/jira/browse/APEXCORE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668448#comment-15668448 ]
ASF GitHub Bot commented on APEXCORE-251:
-----------------------------------------
GitHub user vrozov opened a pull request:
https://github.com/apache/apex-core/pull/419
APEXCORE-251 - Suppress "Journal output stream is null..." warning in unit tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vrozov/apex-core APEXCORE-251
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/419.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #419
----
commit 430efdfd5be6efd66c306297764806d64f025020
Author: Vlad Rozov <v....@datatorrent.com>
Date: 2016-11-15T21:30:55Z
APEXCORE-251 - Suppress "Journal output stream is null..." warning in unit tests
----
> Journal output stream is null error message
> -------------------------------------------
>
> Key: APEXCORE-251
> URL: https://issues.apache.org/jira/browse/APEXCORE-251
> Project: Apache Apex Core
> Issue Type: Task
> Reporter: Chetan Narsude
> Assignee: Vlad Rozov
>
> A simple checkout and test run prints that message a gazillion times as WARN.
> {code}
> 2015-11-07 07:30:05,047 [master] WARN stram.Journal write - Journal output stream is null. Skipping write to the WAL.
> {code}
> Looks like it could be a debug message or something. Make it less verbose.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)