You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@systemml.apache.org by "Matthias Boehm (JIRA)" <ji...@apache.org> on 2017/08/15 20:04:01 UTC

[jira] [Closed] (SYSTEMML-1839) NPE on parfor initialization w/o log4j configuration

     [ https://issues.apache.org/jira/browse/SYSTEMML-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Boehm closed SYSTEMML-1839.
------------------------------------

> NPE on parfor initialization w/o log4j configuration
> ----------------------------------------------------
>
>                 Key: SYSTEMML-1839
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-1839
>             Project: SystemML
>          Issue Type: Bug
>            Reporter: Matthias Boehm
>            Assignee: Matthias Boehm
>             Fix For: SystemML 1.0
>
>
> When calling SystemML in embedded deployments (e.g., through JMLC), there is not necessarily a log4j configuration in the classpath or JVM arguments. In such environments the static initialization of {{ParForStatementBlock}} fails with a nullpointer exception because we try to obtain the default log level and convert it to string although this default might be null.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)