systemml-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glenn Weidner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SYSTEMML-1839) NPE on parfor initialization w/o log4j configuration
Date Sat, 09 Sep 2017 03:50:00 GMT

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

Glenn Weidner updated SYSTEMML-1839:
------------------------------------
    Fix Version/s:     (was: SystemML 1.0)
                   SystemML 0.15

> 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 0.15
>
>
> 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)

Mime
View raw message