Hi Charles,
This is a known issue, which is caused by try to set fault message
back to InOnly MessageExchange. From the log you can see you sent cxf
bc provider a InOnly ME.
This issue is tracked by SMXCOMP-589[1] and already fixed since 2009.02.
Could you just use new released smx-cxf-bc 2010.01, you also need
update sharedLib to the latest version.
[1]https://issues.apache.org/activemq/browse/SMXCOMP-589
Freeman
On 2010-3-23, at 下午6:01, Charles Moulliard wrote:
Hi,
The wsdl fthat I try to user with ServiceMix 3.3.1 (servicemix-cxf-
bc /
2009.01) contains a soap:fault header. The jbi endpoint does not
seem to
like that :
10:48:17,610 ERROR - CxfBcComponent - Error processing
exchange InOnly[
id: ID:10.70.152.186-1278a6913eb-3:0
status: Active
role: provider
endpoint: ValHubReplyMessageOutboundPort
in: <?xml version="1.0" encoding="UTF-8"?><PriceReply xmlns="
http://www.ecb.int/
valHub"><HeadermessageType="standardPriceReply"><SenderNCB>FR</
SenderNCB><ReceiverNCB>FR</
ReceiverNCB><CreationDate>2010-03-22T18:01:42</CreationDate></
Header><InstrumentPriceDataSet><InstrumentPriceData><IsinCode>XS015778
3936</IsinCode><PricingDate>2010-01-26T12:00:00</
PricingDate><ErrorCode>0</ErrorCode><CleanPrice>93.9495</
CleanPrice><AccruedInterest>0.0276</
AccruedInterest><PoolFactor>0.169418053</PoolFactor></
InstrumentPriceData><InstrumentPriceData><IsinCode>XS0158000629</
IsinCode><PricingDate>2010-01-26T12:00:00</PricingDate><ErrorCode>0</
ErrorCode><CleanPrice>92.3868</CleanPrice><AccruedInterest>0.1832</
AccruedInterest><PoolFactor>0.301347883</PoolFactor></
InstrumentPriceData><InstrumentPriceData><IsinCode>XS0165595801</
IsinCode><PricingDate>2010-01-26T12:00:00</PricingDate><ErrorCode>0</
ErrorCode><CleanPrice>93.9817</CleanPrice><AccruedInterest>0.0647</
AccruedInterest><PoolFactor>0.826927543</PoolFactor></
InstrumentPriceData><InstrumentPriceData><IsinCode>XS0165883850</
IsinCode><PricingDate>2010-01-26T12:00:00</PricingDate><ErrorCode>0</
ErrorCode><CleanPrice>95.0</CleanPrice><AccruedInterest>0.0</
AccruedInterest><PoolFactor>1.0</PoolFactor></
InstrumentPriceData><InstrumentPriceData><IsinCode>XS0169467379</
IsinCode><PricingDate>2010-01-26T12:00:00</PricingDate><ErrorCode>0</
ErrorCode><CleanPrice>94.7301</CleanPrice><AccruedInterest>0.1018</
AccruedInterest><PoolFactor>0.039777921</PoolFactor><...
]
10:51:10,656 ERROR - DeadLetterChannel - Failed
delivery for
exchangeId: ID-DE1199W4/1726-1269337506986/0-4. On delivery attempt: 2
caught: javax.jbi.messaging.MessagingException: Fault not supported
javax.jbi.messaging.MessagingException: Fault not supported
at
org
.apache
.servicemix
.jbi
.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:
366)
at
org
.apache
.servicemix
.jbi.messaging.MessageExchangeImpl.setFault(MessageExchangeImpl.java:
290)
at
org
.apache
.servicemix.cxfbc.CxfBcProvider.faultProcess(CxfBcProvider.java:277)
wsdl
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="UseOfCollateralOutbound"
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:exdi="http://exdi.ecb.int";
xmlns:vh="http://www.ecb.int/valHub";
targetNamespace="http://www.ecb.int/valHub";>
<wsdl:types>
<xs:schema>
<xs:import schemaLocation="EXDI.xsd" namespace="http://
exdi.ecb.int" />
</xs:schema>
<xs:schema>
<xs:import schemaLocation="valHubPriceReply.xsd" namespace="
http://www.ecb.int/valHub"; />
</xs:schema>
</wsdl:types>
<wsdl:message name="ValHubMessageOutbound">
<wsdl:part element="exdi:metadata" name="metadata" />
<wsdl:part element="vh:PriceReply" name="parameters" />
</wsdl:message>
<wsdl:message name="ValHubMessageOutboundResponse">
<wsdl:part element="exdi:processingResponse" name="parameters" />
</wsdl:message>
<wsdl:message name="ValHubMessageOutboundFault">
<wsdl:part element="exdi:faultDetail" name="faultDetail" />
</wsdl:message>
<wsdl:portType name="ValHubMessageOutboundPortType">
<wsdl:operation name="ValHubMessageOutbound">
<wsdl:input message="vh:ValHubMessageOutbound" />
<wsdl:output message="vh:ValHubMessageOutboundResponse" />
<wsdl:fault name="ValHubMessageOutboundFault"
message="vh:ValHubMessageOutboundFault" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="ValHublMessageOutboundBinding"
type="vh:ValHubMessageOutboundPortType">
<soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"; />
<wsdl:operation name="ValHubMessageOutbound">
<soap:operation soapAction="" />
<wsdl:input>
<soap:header message="vh:ValHubMessageOutbound" part="metadata"
use="literal" />
<soap:body parts="parameters" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
<wsdl:fault name="ValHubMessageOutboundFault">
<soap:fault name="ValHubMessageOutboundFault" use="literal" />
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="ValHubReplyMessageOutboundService">
<wsdl:port name="ValHubMessageReplyOutboundPort"
binding="vh:ValHublMessageOutboundBinding">
<soap:address location="ValHublMessageOutbound" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Is this error due to a bad configuration or a feature not supported ?
Kind regards,
--
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
