[jira] Commented: (CXF-1086) Noise log traffic due to lifecycle management problem with jetty server

["willem Jiang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532576 ] 

willem Jiang commented on CXF-1086:
-----------------------------------

Hi Benson,

I just committed a quick fix for your system test.  The key issue is that we need to configure  the bus first (set up the jetty engine with a new JettyEngineFactory) , after we can create the service with right bus.
If we mixed the bus setup and service creation in a same application context, the serverFactoryBean will pick a default bus to initiate the service. And when the application context refreshed, the JettyEngineFactory which is instantiated by  Spring will be set to the bus with the resource context handler, so your service can't be accessible.

Willem.


> Noise log traffic due to lifecycle management problem with jetty server
> -----------------------------------------------------------------------
>
>                 Key: CXF-1086
>                 URL: https://issues.apache.org/jira/browse/CXF-1086
>             Project: CXF
>          Issue Type: Bug
>          Components: Bus
>    Affects Versions: 2.0.2
>            Reporter: benson margulies
>            Assignee: willem Jiang
>            Priority: Minor
>         Attachments: http.diff
>
>
> In the test case I'm about to attach, the code logs severe messages complaining that the server can't start because it is already started. Now, if the desired behavior is to lazily murder and restart the server on this sort of error, then the error should not be so severe. If the intent is that this configuration should cleanly close down, then it shouldn't get the error at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.