You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2007/12/05 19:39:43 UTC
[jira] Created: (CXF-1264) JettyHTTPDestination does not set a
thread default bus
JettyHTTPDestination does not set a thread default bus
------------------------------------------------------
Key: CXF-1264
URL: https://issues.apache.org/jira/browse/CXF-1264
Project: CXF
Issue Type: Bug
Components: Transports
Affects Versions: 2.0.4
Reporter: Sergey Beryozkin
Fix For: 2.0.4
JettyHttpDestination does not set the thread default bus similar to the way AbstractCxfServlet does it.
This causes a pronlem in environments where with multiple Buses : the first created bus is assumed to be the thread default bus by default, thus turning any lazily-handled configuration associated with other buses (for ex, a config for a client outbound request to be made as part of processing a given inbound request) ineffective
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1264) JettyHTTPDestination does not set a
thread default bus
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-1264:
-----------------------------
Affects Version/s: (was: 2.0.4)
2.0
2.0.1
2.0.2
2.0.3
> JettyHTTPDestination does not set a thread default bus
> ------------------------------------------------------
>
> Key: CXF-1264
> URL: https://issues.apache.org/jira/browse/CXF-1264
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3
> Reporter: Sergey Beryozkin
> Assignee: Daniel Kulp
> Fix For: 2.0.4
>
> Attachments: cxf-patch-1264.patch
>
>
> JettyHttpDestination does not set the thread default bus similar to the way AbstractCxfServlet does it.
> This causes a pronlem in environments where with multiple Buses : the first created bus is assumed to be the thread default bus by default, thus turning any lazily-handled configuration associated with other buses (for ex, a config for a client outbound request to be made as part of processing a given inbound request) ineffective
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1264) JettyHTTPDestination does not set a
thread default bus
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-1264:
--------------------------------
Assignee: Daniel Kulp
> JettyHTTPDestination does not set a thread default bus
> ------------------------------------------------------
>
> Key: CXF-1264
> URL: https://issues.apache.org/jira/browse/CXF-1264
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0.4
> Reporter: Sergey Beryozkin
> Assignee: Daniel Kulp
> Fix For: 2.0.4
>
> Attachments: cxf-patch-1264.patch
>
>
> JettyHttpDestination does not set the thread default bus similar to the way AbstractCxfServlet does it.
> This causes a pronlem in environments where with multiple Buses : the first created bus is assumed to be the thread default bus by default, thus turning any lazily-handled configuration associated with other buses (for ex, a config for a client outbound request to be made as part of processing a given inbound request) ineffective
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-1264) JettyHTTPDestination does not set a
thread default bus
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin updated CXF-1264:
----------------------------------
Attachment: cxf-patch-1264.patch
Patch with a test submitted
> JettyHTTPDestination does not set a thread default bus
> ------------------------------------------------------
>
> Key: CXF-1264
> URL: https://issues.apache.org/jira/browse/CXF-1264
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0.4
> Reporter: Sergey Beryozkin
> Fix For: 2.0.4
>
> Attachments: cxf-patch-1264.patch
>
>
> JettyHttpDestination does not set the thread default bus similar to the way AbstractCxfServlet does it.
> This causes a pronlem in environments where with multiple Buses : the first created bus is assumed to be the thread default bus by default, thus turning any lazily-handled configuration associated with other buses (for ex, a config for a client outbound request to be made as part of processing a given inbound request) ineffective
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1264) JettyHTTPDestination does not set a
thread default bus
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1264.
------------------------------
Resolution: Fixed
I've applied the patch, but I've also updated all the Observers to properly set the threadlocalbus so the transports don't really have to.
> JettyHTTPDestination does not set a thread default bus
> ------------------------------------------------------
>
> Key: CXF-1264
> URL: https://issues.apache.org/jira/browse/CXF-1264
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3
> Reporter: Sergey Beryozkin
> Assignee: Daniel Kulp
> Fix For: 2.0.4
>
> Attachments: cxf-patch-1264.patch
>
>
> JettyHttpDestination does not set the thread default bus similar to the way AbstractCxfServlet does it.
> This causes a pronlem in environments where with multiple Buses : the first created bus is assumed to be the thread default bus by default, thus turning any lazily-handled configuration associated with other buses (for ex, a config for a client outbound request to be made as part of processing a given inbound request) ineffective
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.