You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2011/09/09 16:02:08 UTC
[jira] [Resolved] (CAMEL-4429) CXFProducer should tell CXF to
ignore the part response handling when it uses MESSSAGE dataformat
[ https://issues.apache.org/jira/browse/CAMEL-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-4429.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.8.2
Applied patch into trunk and Camel 2.8.x branch.
> CXFProducer should tell CXF to ignore the part response handling when it uses MESSSAGE dataformat
> --------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4429
> URL: https://issues.apache.org/jira/browse/CAMEL-4429
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 2.8.2, 2.9.0
>
>
> IN CXF-3788, CXF HTTPConduit will handle the partial response when the HTTP response code is 202 nor matter the operation is oneway or not. It will cause the camel-cxf producer wait for the response for server for ever.
> CXF-3796 introduces a new message header to help us to workaround this issue, we need to set this header in CxfProducer when the data format is MESSAGE.
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Resolved] (CAMEL-4429) CXFProducer should tell CXF to
ignore the part response handling when it uses MESSSAGE dataformat
Posted by Aki Yoshida <el...@googlemail.com>.
Hi Willem,
I found where this 500 originally comes from (there is an NPE raised
in RawMessageContentRedirectInterceptor when no PR is returned). I
will verify this condition a little more and will update the ticket
with the patch.
thanks.
regards, aki
2011/9/14 Aki Yoshida <el...@googlemail.com>:
> Hi Willem,
> thanks.
>
> I just tried the camel-trunk's test case against CXF 2.5.0-SNAPSHOT
> without this property set. The twoway greeter calls (greetMe and
> sayHi) are not blocked and worked fine. But the greeter.greetMeOneWay
> call seems to throw an exception after the call is completed. And this
> exception is returned back from the RouterPort as HTTP 500 and the
> test is failing.
>
> So, the original blocking behavior is not there any more but there is
> still a problem.
>
> I will look into this.
>
> Regards, aki
>
>
> 2011/9/14 Willem Jiang <wi...@gmail.com>:
>> Hi Aki
>>
>> The test case is part of the test of CxfGreeterMessageRouterTest in the
>> camel-cxf module.
>> I just built the latest cxf-2.4.x branch and run the test.
>> The test failed if I doesn't set the option which is introduced in
>> CAMEL-4429 on the CxfProducer :(.
>>
>> As the CxfProducer doesn't know the binding operation as it doesn't check
>> the underlay input steam, I still need to use the option to let HttpConduit
>> do not consume the underlay message.
>>
>> Willem
>>
>> On 9/14/11 6:33 PM, Aki Yoshida wrote:
>>>
>>> Hi Willem,
>>>
>>> I updated the patch for CXF-3788 to avoid the problem you discovered
>>> for the original patch. I have tested the updated patch against a jaxw
>>> disptach test case in CXF. I would like to verify that this correction
>>> works for the test case you had without using this request property
>>> setting. Is your test case in the camel-cxf test folder? If not, could
>>> you tell me which one?
>>>
>>> Thanks.
>>> regards, aki
>>>
>>> 2011/9/9 Willem Jiang (JIRA)<ji...@apache.org>:
>>>>
>>>> [
>>>> https://issues.apache.org/jira/browse/CAMEL-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>>> ]
>>>>
>>>> Willem Jiang resolved CAMEL-4429.
>>>> ---------------------------------
>>>>
>>>> Resolution: Fixed
>>>> Fix Version/s: 2.8.2
>>>>
>>>> Applied patch into trunk and Camel 2.8.x branch.
>>>>
>>>>> CXFProducer should tell CXF to ignore the part response handling when
>>>>> it uses MESSSAGE dataformat
>>>>>
>>>>> --------------------------------------------------------------------------------------------------
>>>>>
>>>>> Key: CAMEL-4429
>>>>> URL: https://issues.apache.org/jira/browse/CAMEL-4429
>>>>> Project: Camel
>>>>> Issue Type: Improvement
>>>>> Components: camel-cxf
>>>>> Reporter: Willem Jiang
>>>>> Assignee: Willem Jiang
>>>>> Fix For: 2.8.2, 2.9.0
>>>>>
>>>>>
>>>>> IN CXF-3788, CXF HTTPConduit will handle the partial response when the
>>>>> HTTP response code is 202 nor matter the operation is oneway or not. It will
>>>>> cause the camel-cxf producer wait for the response for server for ever.
>>>>> CXF-3796 introduces a new message header to help us to workaround this
>>>>> issue, we need to set this header in CxfProducer when the data format is
>>>>> MESSAGE.
>>>>>
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
Re: [jira] [Resolved] (CAMEL-4429) CXFProducer should tell CXF to
ignore the part response handling when it uses MESSSAGE dataformat
Posted by Aki Yoshida <el...@googlemail.com>.
Hi Willem,
thanks.
I just tried the camel-trunk's test case against CXF 2.5.0-SNAPSHOT
without this property set. The twoway greeter calls (greetMe and
sayHi) are not blocked and worked fine. But the greeter.greetMeOneWay
call seems to throw an exception after the call is completed. And this
exception is returned back from the RouterPort as HTTP 500 and the
test is failing.
So, the original blocking behavior is not there any more but there is
still a problem.
I will look into this.
Regards, aki
2011/9/14 Willem Jiang <wi...@gmail.com>:
> Hi Aki
>
> The test case is part of the test of CxfGreeterMessageRouterTest in the
> camel-cxf module.
> I just built the latest cxf-2.4.x branch and run the test.
> The test failed if I doesn't set the option which is introduced in
> CAMEL-4429 on the CxfProducer :(.
>
> As the CxfProducer doesn't know the binding operation as it doesn't check
> the underlay input steam, I still need to use the option to let HttpConduit
> do not consume the underlay message.
>
> Willem
>
> On 9/14/11 6:33 PM, Aki Yoshida wrote:
>>
>> Hi Willem,
>>
>> I updated the patch for CXF-3788 to avoid the problem you discovered
>> for the original patch. I have tested the updated patch against a jaxw
>> disptach test case in CXF. I would like to verify that this correction
>> works for the test case you had without using this request property
>> setting. Is your test case in the camel-cxf test folder? If not, could
>> you tell me which one?
>>
>> Thanks.
>> regards, aki
>>
>> 2011/9/9 Willem Jiang (JIRA)<ji...@apache.org>:
>>>
>>> [
>>> https://issues.apache.org/jira/browse/CAMEL-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>> ]
>>>
>>> Willem Jiang resolved CAMEL-4429.
>>> ---------------------------------
>>>
>>> Resolution: Fixed
>>> Fix Version/s: 2.8.2
>>>
>>> Applied patch into trunk and Camel 2.8.x branch.
>>>
>>>> CXFProducer should tell CXF to ignore the part response handling when
>>>> it uses MESSSAGE dataformat
>>>>
>>>> --------------------------------------------------------------------------------------------------
>>>>
>>>> Key: CAMEL-4429
>>>> URL: https://issues.apache.org/jira/browse/CAMEL-4429
>>>> Project: Camel
>>>> Issue Type: Improvement
>>>> Components: camel-cxf
>>>> Reporter: Willem Jiang
>>>> Assignee: Willem Jiang
>>>> Fix For: 2.8.2, 2.9.0
>>>>
>>>>
>>>> IN CXF-3788, CXF HTTPConduit will handle the partial response when the
>>>> HTTP response code is 202 nor matter the operation is oneway or not. It will
>>>> cause the camel-cxf producer wait for the response for server for ever.
>>>> CXF-3796 introduces a new message header to help us to workaround this
>>>> issue, we need to set this header in CxfProducer when the data format is
>>>> MESSAGE.
>>>>
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>>>
>>
>
>
>
Re: [jira] [Resolved] (CAMEL-4429) CXFProducer should tell CXF to
ignore the part response handling when it uses MESSSAGE dataformat
Posted by Willem Jiang <wi...@gmail.com>.
Hi Aki
The test case is part of the test of CxfGreeterMessageRouterTest in the
camel-cxf module.
I just built the latest cxf-2.4.x branch and run the test.
The test failed if I doesn't set the option which is introduced in
CAMEL-4429 on the CxfProducer :(.
As the CxfProducer doesn't know the binding operation as it doesn't
check the underlay input steam, I still need to use the option to let
HttpConduit do not consume the underlay message.
Willem
On 9/14/11 6:33 PM, Aki Yoshida wrote:
> Hi Willem,
>
> I updated the patch for CXF-3788 to avoid the problem you discovered
> for the original patch. I have tested the updated patch against a jaxw
> disptach test case in CXF. I would like to verify that this correction
> works for the test case you had without using this request property
> setting. Is your test case in the camel-cxf test folder? If not, could
> you tell me which one?
>
> Thanks.
> regards, aki
>
> 2011/9/9 Willem Jiang (JIRA)<ji...@apache.org>:
>>
>> [ https://issues.apache.org/jira/browse/CAMEL-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Willem Jiang resolved CAMEL-4429.
>> ---------------------------------
>>
>> Resolution: Fixed
>> Fix Version/s: 2.8.2
>>
>> Applied patch into trunk and Camel 2.8.x branch.
>>
>>> CXFProducer should tell CXF to ignore the part response handling when it uses MESSSAGE dataformat
>>> --------------------------------------------------------------------------------------------------
>>>
>>> Key: CAMEL-4429
>>> URL: https://issues.apache.org/jira/browse/CAMEL-4429
>>> Project: Camel
>>> Issue Type: Improvement
>>> Components: camel-cxf
>>> Reporter: Willem Jiang
>>> Assignee: Willem Jiang
>>> Fix For: 2.8.2, 2.9.0
>>>
>>>
>>> IN CXF-3788, CXF HTTPConduit will handle the partial response when the HTTP response code is 202 nor matter the operation is oneway or not. It will cause the camel-cxf producer wait for the response for server for ever.
>>> CXF-3796 introduces a new message header to help us to workaround this issue, we need to set this header in CxfProducer when the data format is MESSAGE.
>>>
>>
>> --
>> This message is automatically generated by JIRA.
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>
Re: [jira] [Resolved] (CAMEL-4429) CXFProducer should tell CXF to
ignore the part response handling when it uses MESSSAGE dataformat
Posted by Aki Yoshida <el...@googlemail.com>.
Hi Willem,
I updated the patch for CXF-3788 to avoid the problem you discovered
for the original patch. I have tested the updated patch against a jaxw
disptach test case in CXF. I would like to verify that this correction
works for the test case you had without using this request property
setting. Is your test case in the camel-cxf test folder? If not, could
you tell me which one?
Thanks.
regards, aki
2011/9/9 Willem Jiang (JIRA) <ji...@apache.org>:
>
> [ https://issues.apache.org/jira/browse/CAMEL-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Willem Jiang resolved CAMEL-4429.
> ---------------------------------
>
> Resolution: Fixed
> Fix Version/s: 2.8.2
>
> Applied patch into trunk and Camel 2.8.x branch.
>
>> CXFProducer should tell CXF to ignore the part response handling when it uses MESSSAGE dataformat
>> --------------------------------------------------------------------------------------------------
>>
>> Key: CAMEL-4429
>> URL: https://issues.apache.org/jira/browse/CAMEL-4429
>> Project: Camel
>> Issue Type: Improvement
>> Components: camel-cxf
>> Reporter: Willem Jiang
>> Assignee: Willem Jiang
>> Fix For: 2.8.2, 2.9.0
>>
>>
>> IN CXF-3788, CXF HTTPConduit will handle the partial response when the HTTP response code is 202 nor matter the operation is oneway or not. It will cause the camel-cxf producer wait for the response for server for ever.
>> CXF-3796 introduces a new message header to help us to workaround this issue, we need to set this header in CxfProducer when the data format is MESSAGE.
>>
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>