From: Steve L. (JIRA) <ji...@sm...> - 2008-02-28 14:29:42
|
[ http://jira.smartfrog.org/jira/browse/SFOS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved SFOS-698. --------------------------------- Resolution: Fixed -different text for deploy => create and start => start -throwables are logged at error level before being wrapped; wrapped exceptions are ignored (assume they are already logged) > Improve logging/diagnostics when a throwable is raised during component deploy/startup > -------------------------------------------------------------------------------------- > > Key: SFOS-698 > URL: http://jira.smartfrog.org/jira/browse/SFOS-698 > Project: SmartFrog > Issue Type: Improvement > Components: .sfCore > Affects Versions: 3.12.022 > Reporter: Steve Loughran > Assignee: Steve Loughran > Fix For: 3.12.025dev > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > If you throw some kind of runtime exception in component startup, it isnt reported very well. The client sees: > SmartFrogLifecycleException:: [sfStart] Failed to create a new child., cause: java.lang.NullPointerException, SmartFrog 3.12.025dev (2008-02-28 13:20:01 GMT), primSFCompleteName: HOST morzine:rootProcess:testWarDeployed:tests:operations, primContext: included, reference: HOST morzine:rootProcess:testWarDeployed:tests:operations, primContext: included, cause: SmartFrogLifecycleException:: [sfStart] Failed to create a new child., cause: java.lang.NullPointerException, SmartFrog 3.12.025dev (2008-02-28 13:20:01 GMT), primSFCompleteName: HOST > The server sees nothing more detailed in the log. > We cant even tell if it happened in the sfDeploy or sfStart operations, as the same text is used in both methods. -- 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 |