[Smartfrog-checkins] [Smartfrog.org-JIRA] Commented: (SFOS-707) NPE when starting components, but no stack trace appears

[Steve L. (JIRA) <ji...@sm...>]

    [ http://jira.smartfrog.org/jira/browse/SFOS-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10891#action_10891 ] 

Steve Loughran commented on SFOS-707:
-------------------------------------

Not fixed after adding extra logging code and better recursive traces. Why? When you bring the thing up in the debugger, there is no stack trace.

Searching "NPE no stack trace" shows that this is not unheard of, and can be triggered by JVM problems.

Moving back to restlet 1.0.6 makes the problem go away. But is restlet just the symptom, and the underlying cause elsewhere? Need to test on a different JVM.

> NPE when starting components, but no stack trace appears
> --------------------------------------------------------
>
>                 Key: SFOS-707
>                 URL: http://jira.smartfrog.org/jira/browse/SFOS-707
>             Project: SmartFrog
>          Issue Type: Bug
>          Components: testharness
>    Affects Versions: 3.12.025dev
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: 3.12.023 dev
>
>
> When we move up to restlet 1.1-SNAPSHOT, the tests fail as AWS is missing (reported, fixed in their SVN). However, when this is reported in the junit test runs, the details of the NPE are missing, only the trace of all the wrapped components. We need to ensure that all stack traces get reported in the junit-side of things, even when tests fail in startup, so that the generated reports are useful.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira