You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2013/08/02 01:53:48 UTC

[jira] [Resolved] (SYNAPSE-698) NPE in SynapseConfiguration.destroy()

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

Hiranya Jayathilaka resolved SYNAPSE-698.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: NIGHTLY

I've refactored the SynapseConfiguration class to address this issue.

1. SynapseConfiguration keeps track of its initialization status and disallows back to back calls to init/destroy methods.
2. Synapse timer is initialized in init method and destroyed properly in the destroy method
                
> NPE in SynapseConfiguration.destroy()
> -------------------------------------
>
>                 Key: SYNAPSE-698
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-698
>             Project: Synapse
>          Issue Type: Bug
>            Reporter: Myles Bunbury
>            Assignee: Hiranya Jayathilaka
>             Fix For: NIGHTLY
>
>
> If for some reason org.apache.synapse.config.SynapseConfiguration.destroy() is called twice, a NPE results on line 767 since the synapseTimer variable has already been set to NULL.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org