Re: Is camel cxf failover is working ? It doesn't seem to work at all. Please confirm.

[rdomingo <rd...@domingo.nl>]

check.

Please don't add any new replies to this topic, but use other topic:
"Problem with CXF Failover -> Already connected error" 



Claus Ibsen-2 wrote:
> 
> Hi
> 
> Please do NOT start a new thread on the same topic you already have
> started.
> And people have already replied and helped you on this matter.
> 
> 
> On Tue, Mar 16, 2010 at 9:32 PM, rdomingo <rd...@domingo.nl> wrote:
>>
>> It look like there is a huge bug in camel cxf failover, it doesn't seem
>> to
>> work at all :(
>>
>> Is there anybody who got it running ??
>>
>> I just retested cxf failover using camel versions 2.0.0,  2.1.0 and even
>> 1.6.2 (jdk1.5 and jdk6), but all resulting in same error:
>> ...
>> org.apache.cxf.interceptor.Fault: Already connected
>>        at
>> org.apache.camel.component.cxf.CxfConsumer$1.invoke(CxfConsumer.java:101)
>>        at
>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>>        at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> ...
>> Caused by: java.lang.IllegalStateException: Already connected
>>        at
>> java.net.HttpURLConnection.setFixedLengthStreamingMode(HttpURLConnection.java:121)
>>        at
>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.thresholdNotReached(HTTPConduit.java:1888)
>>        at
>> org.apache.cxf.io.AbstractThresholdOutputStream.close(AbstractThresholdOutputStream.java:99)
>>        at
>> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1979)
>> ...
>>
>> My Config:
>>  <route>
>>            <from
>>
>> uri="cxf://http://0.0.0.0:8081/fooServer/echo?wsdlURL=http://localhost:8080/fooServer1-0.0.1a-SNAPSHOT/echo&#63;wsdl&amp;serviceName={http://www.telecats.nl/nl.telecats.bvibluenode.adt.server-push.fooService}EchoService&amp;portName={http://www.telecats.nl/nl.telecats.bvibluenode.adt.server-push.fooService}EchoServiceImplPort&amp;dataFormat=MESSAGE";
>> />
>>            <loadBalance>
>>                <failover>
>>                    <exception>java.lang.Exception</exception>
>>                    <exception>java.io.IOException</exception>
>>                </failover>
>> <!-- first webservice -->
>>                <to
>>
>> uri="cxf://http://localhost:8080/fooServer1-0.0.1a-SNAPSHOT/echo?wsdlURL=http://localhost:8080/fooServer1-0.0.1a-SNAPSHOT/echo&#63;wsdl&amp;serviceName={http://www.telecats.nl/nl.telecats.bvibluenode.adt.server-push.fooService}EchoService&amp;portName={http://www.telecats.nl/nl.telecats.bvibluenode.adt.server-push.fooService}EchoServiceImplPort&amp;dataFormat=MESSAGE";
>> />
>> <!-- second webservice -->
>>                    <to
>>
>> uri="cxf://http://localhost:8080/fooServer1-0.0.1b-SNAPSHOT/echo?wsdlURL=http://localhost:8080/fooServer1-0.0.1b-SNAPSHOT/echo&#63;wsdl&amp;serviceName={http://www.telecats.nl/nl.telecats.bvibluenode.adt.server-push.fooService}EchoService&amp;portName={http://www.telecats.nl/nl.telecats.bvibluenode.adt.server-push.fooService}EchoServiceImplPort&amp;dataFormat=MESSAGE";
>> />
>>            </loadBalance>
>>        </route>
>>
>>
>> For more details see my other post "Problem with CXF Failover -> Already
>> connected error"
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Is-camel-cxf-failover-is-working---It-doesn%27t-seem-to-work-at-all.-Please-confirm.-tp27924101p27924101.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
> 
> 
> 
> -- 
> Claus Ibsen
> Apache Camel Committer
> 
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
> 
> 

-- 
View this message in context: http://old.nabble.com/Is-camel-cxf-failover-working---It-doesn%27t-seem-to-work-at-all.-Please-confirm.-tp27924101p27928207.html
Sent from the Camel - Users mailing list archive at Nabble.com.