You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2011/03/29 15:52:05 UTC
[jira] [Issue Comment Edited] (CXF-3429) ServerImpl should shutdown
Destination before setMessageObserver=null
[ https://issues.apache.org/jira/browse/CXF-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012481#comment-13012481 ]
Willem Jiang edited comment on CXF-3429 at 3/29/11 1:50 PM:
------------------------------------------------------------
Applied patch into trunk and 2.3.x-fixes branch with thanks to David.
was (Author: njiang):
Applied patch into trunk and 2.3.x-fixes branch.
> ServerImpl should shutdown Destination before setMessageObserver=null
> ---------------------------------------------------------------------
>
> Key: CXF-3429
> URL: https://issues.apache.org/jira/browse/CXF-3429
> Project: CXF
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.10
> Reporter: David Liu
> Assignee: Willem Jiang
> Fix For: 2.4, 2.3.4
>
>
> Hi,
> During shutdown the CXF server, we encounter the NullPointerException from time to time.
> The issue is that ServerImpl will set MessageObserver to null, and then it shutdown desination. however, if the server is multi-thread and probably some thread is runing, then it can result in NullPointerException because MessageObserver is null.
> Can we fix this bug by shutdown the Destination first and then set MessageObserver to null?
>
> Also, do we have a workaround for this issue?
> {code}
> public class ServerImpl implements Server {
> public void stop() {
> LOG.fine("Server is stopping.");
> ...
> getDestination().setMessageObserver(null);
> getDestination().shutdown();
> }
> {code}
> David
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira