[
https://issues.apache.org/jira/browse/PIRK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400898#comment-15400898
]
Suneel Marthi commented on PIRK-28:
-----------------------------------
Thanks for that pointer, have it working now. The culprit happened to be
Elasticsearch that was bringing in Storm as a dependency => which was
bringing in old log4j jars.
Will be updating the PR in a few mins.
On Sat, Jul 30, 2016 at 7:51 PM, Ellison Anne Williams (JIRA) <
> Logger Statements Not Working in/from Drivers
> ---------------------------------------------
>
> Key: PIRK-28
> URL: https://issues.apache.org/jira/browse/PIRK-28
> Project: PIRK
> Issue Type: Bug
> Reporter: Ellison Anne Williams
> Assignee: Suneel Marthi
>
> Noticed today that logging is not functioning within the QuerierDriver and
> ResponderDriver (and the corresponding CLI classes). It does, however, appear
> to be working correctly when running through the unit tests (i.e. not calling
> a main() first).
> More investigation to get to the root cause is needed...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)