Nabble - Synapse - User

RE: Sample 0 connection Error

2009-12-16T09:13:25Z

sorry for not searching in the archive with markmail.
I have found the answer here:

On 10/8/07, Asankha C. Perera <asan...@...> wrote:

Eric

Are you using windows? Also whats your client application written in? Most probably what happens is that your client sends the request stating HTTP 1.1 which implies the use of keepalives unless a "Connection: close" header is specified along with the request. But as soon as it gets the response back - the client closes the connection and possibly terminates itself. One way to find out if this is the cause is to send the request to Synpase through TCPMon etc and check if what I am saying is taking place - note that the sample stockquote client etc that uses Axis2 in our samples also suffers from this - but this is not a defect with Synapse. We could update Synapse to just do a WARN on this.. your thoughts are welcome

asankha

> -----Original Message-----
> From: fat_nonsense@... [mailto:fat_nonsense@...]
> Sent: Wednesday, December 16, 2009 5:13 PM
> To: user@...
> Subject: Sample 0 connection Error
>
> Hello,
>
>
>
> I have just installed and tried the sample 0 application of Synapse.
> It seems to work somehow, but there is still an error message in the
> Synapse console output saying "An existing connection was closed by the
> remote host" (translated from german). On both sides, server and
> client, everything seems to be ok, it's just synapse.
>
> Here are the console outputs
>
>
>
> ____________________________________________________________________
>
> Axis2 Server console output:
>
>
>
> Wed Dec 16 16:50:55 CET 2009 samples.services.SimpleStockQuoteService
> :: Generating quote for : IBM
>
> ____________________________________________________________________
>
>
>
> Synapse console output:
>
>
>
> 2009-12-16 16:50:55,143 [192.168.2.1-Fat-Core2Duo] [HttpServerWorker-1]
> INFO LogMediator To:
> http://localhost:9000/soap/SimpleStockQuoteService, WSAction: urn:
>
> getQuote, SOAPAction: urn:getQuote, ReplyTo:
> http://www.w3.org/2005/08/addressing/anonymous, MessageID:
> urn:uuid:2304C5A25C1B68873B1260978654900, Direction: req
>
> uest, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Head
> er xmlns:wsa="htt
>
> p://www.w3.org/2005/08/addressing"><wsa:To>http://localhost:9000/soap/S
> impleStockQuoteService</wsa:To><wsa:MessageID>urn:uuid:2304C5A25C1B6887
> 3B1260978654900</w
>
> sa:MessageID><wsa:Action>urn:getQuote</wsa:Action></soapenv:Header><soa
> penv:Body><m0:getQuote
> xmlns:m0="http://services.samples/xsd"><m0:request><m0:symbol>IBM<
>
> /m0:symbol></m0:request></m0:getQuote></soapenv:Body></soapenv:Envelope
> >
>
> 2009-12-16 16:50:55,159 [192.168.2.1-Fat-Core2Duo] [HttpServerWorker-1]
> INFO TimeoutHandler This engine will expire all callbacks after : 86400
> seconds, irresp
>
> ective of the timeout action, after the specified or optional timeout
>
> 2009-12-16 16:50:55,205 [192.168.2.1-Fat-Core2Duo] [HttpClientWorker-1]
> INFO LogMediator To: http://www.w3.org/2005/08/addressing/anonymous,
> WSAction: , SOAPAc
>
> tion: , ReplyTo: http://www.w3.org/2005/08/addressing/anonymous,
> MessageID: urn:uuid:9253641FAB4022EBA1639719603782565-1091310631,
> Direction: response, Envelope
>
> : <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body
> ><ns:getQuoteResponse xmlns:ns=
>
> "http://services.samples/xsd"><ns:return
> type="samples.services.GetQuoteResponse"><ns:change>-
> 2.740026424743019</ns:change><ns:earnings>12.985968531667194</ns:e
>
> arnings><ns:high>-
> 99.59315516535092</ns:high><ns:last>99.61536938248533</ns:last><ns:last
> TradeTimestamp>Wed Dec 16 16:50:55 CET 2009</ns:lastTradeTimestamp><ns:
>
> low>-
> 97.2809218305695</ns:low><ns:marketCap>5.610176071955402E7</ns:marketCa
> p><ns:name>IBM
> Company</ns:name><ns:open>102.67366425811228</ns:open><ns:peRatio>23.
>
> 97205777063296</ns:peRatio><ns:percentageChange>-
> 2.4133990851988454</ns:percentageChange><ns:prevClose>113.5339132904851
> 5</ns:prevClose><ns:symbol>IBM</ns:symbo
>
> l><ns:volume>15275</ns:volume></ns:return></ns:getQuoteResponse></soape
> nv:Body></soapenv:Envelope>
>
> 2009-12-16 16:50:55,842 [192.168.2.1-Fat-Core2Duo] [I/O dispatcher 7]
> ERROR ServerHandler I/O error: An existing connection was closed by
> the remote host (translated)
>
> ______________________________________________________________
>
>
>
> Client console output:
>
>
>
> C:\Program Files\Apache Software Foundation\synapse-
> 1.2\samples\axis2Client>ant stockquote -
> Daddurl=http://localhost:9000/soap/SimpleStockQuoteService -Dtrpurl=
>
> http://localhost:8280 -Dmode=quote -Dsymbol=IBM
>
> Buildfile: build.xml
>
>
>
> init:
>
>
>
> compile:
>
>
>
> stockquote:
>
> [java] 2009-12-16 16:50:54,805 [-] [main] INFO
> MailTransportSender MAILTO Sender started
>
> [java] 2009-12-16 16:50:54,824 [-] [main] INFO JMSSender JMS
> Sender started
>
> [java] Standard :: Stock price = $99.61536938248533
>
>
>
> BUILD SUCCESSFUL
>
> Total time: 2 seconds
>
> ________________________________________________________________
>
>
>
> according to the tutorial the output should be like in this link:
>
> http://synapse.apache.org/Synapse_QuickStart.html
>
> I'm running jdk 1.6 on Windows 7 with deactivated UAC, and temporaly
> deactivated windows firewall trying to solve this error.
>
> Any advise or information about this error would be appreciated.
>
>
>
>
>
> Best regards,
>
>
>
>
>
> Thuy

Re: Sample 0 connection Error

2009-12-16T09:12:06Z

Hi Thuy

Please subscribe to the user list to post, as else your mails go into
moderation
> I have just installed and tried the sample 0 application of Synapse. It seems to work somehow, but there is still an error message in the Synapse console output saying "An existing connection was closed by the remote host" (translated from german). On both sides, server and client, everything seems to be ok, it's just synapse.
>
> 2009-12-16 16:50:55,842 [192.168.2.1-Fat-Core2Duo] [I/O dispatcher 7] ERROR ServerHandler I/O error: An existing connection was closed by the remote host (translated)
>
Are you trying this out on Windows? This most probably is a harmless
connection close when the application wanted to keep the socket alive..
Do not worry about it

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com

Sample 0 connection Error

2009-12-16T08:12:57Z

Hello,

I have just installed and tried the sample 0 application of Synapse. It seems to work somehow, but there is still an error message in the Synapse console output saying "An existing connection was closed by the remote host" (translated from german). On both sides, server and client, everything seems to be ok, it's just synapse.

Here are the console outputs

____________________________________________________________________

Axis2 Server console output:

Wed Dec 16 16:50:55 CET 2009 samples.services.SimpleStockQuoteService :: Generating quote for : IBM

____________________________________________________________________

Synapse console output:

2009-12-16 16:50:55,143 [192.168.2.1-Fat-Core2Duo] [HttpServerWorker-1] INFO LogMediator To: http://localhost:9000/soap/SimpleStockQuoteService, WSAction: urn:

getQuote, SOAPAction: urn:getQuote, ReplyTo: http://www.w3.org/2005/08/addressing/anonymous, MessageID: urn:uuid:2304C5A25C1B68873B1260978654900, Direction: req

uest, Envelope: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="htt

p://www.w3.org/2005/08/addressing"><wsa:To>http://localhost:9000/soap/SimpleStockQuoteService</wsa:To><wsa:MessageID>urn:uuid:2304C5A25C1B68873B1260978654900</w

sa:MessageID><wsa:Action>urn:getQuote</wsa:Action></soapenv:Header><soapenv:Body><m0:getQuote xmlns:m0="http://services.samples/xsd"><m0:request><m0:symbol>IBM<

/m0:symbol></m0:request></m0:getQuote></soapenv:Body></soapenv:Envelope>

2009-12-16 16:50:55,159 [192.168.2.1-Fat-Core2Duo] [HttpServerWorker-1] INFO TimeoutHandler This engine will expire all callbacks after : 86400 seconds, irresp

ective of the timeout action, after the specified or optional timeout

2009-12-16 16:50:55,205 [192.168.2.1-Fat-Core2Duo] [HttpClientWorker-1] INFO LogMediator To: http://www.w3.org/2005/08/addressing/anonymous, WSAction: , SOAPAc

tion: , ReplyTo: http://www.w3.org/2005/08/addressing/anonymous, MessageID: urn:uuid:9253641FAB4022EBA1639719603782565-1091310631, Direction: response, Envelope

: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:getQuoteResponse xmlns:ns=

"http://services.samples/xsd"><ns:return type="samples.services.GetQuoteResponse"><ns:change>-2.740026424743019</ns:change><ns:earnings>12.985968531667194</ns:e

arnings><ns:high>-99.59315516535092</ns:high><ns:last>99.61536938248533</ns:last><ns:lastTradeTimestamp>Wed Dec 16 16:50:55 CET 2009</ns:lastTradeTimestamp><ns:

low>-97.2809218305695</ns:low><ns:marketCap>5.610176071955402E7</ns:marketCap><ns:name>IBM Company</ns:name><ns:open>102.67366425811228</ns:open><ns:peRatio>23.

97205777063296</ns:peRatio><ns:percentageChange>-2.4133990851988454</ns:percentageChange><ns:prevClose>113.53391329048515</ns:prevClose><ns:symbol>IBM</ns:symbo

l><ns:volume>15275</ns:volume></ns:return></ns:getQuoteResponse></soapenv:Body></soapenv:Envelope>

2009-12-16 16:50:55,842 [192.168.2.1-Fat-Core2Duo] [I/O dispatcher 7] ERROR ServerHandler I/O error: An existing connection was closed by the remote host (translated)

______________________________________________________________

Client console output:

C:\Program Files\Apache Software Foundation\synapse-1.2\samples\axis2Client>ant stockquote -Daddurl=http://localhost:9000/soap/SimpleStockQuoteService -Dtrpurl=

http://localhost:8280 -Dmode=quote -Dsymbol=IBM

Buildfile: build.xml

init:

compile:

stockquote:

[java] 2009-12-16 16:50:54,805 [-] [main] INFO MailTransportSender MAILTO Sender started

[java] 2009-12-16 16:50:54,824 [-] [main] INFO JMSSender JMS Sender started

[java] Standard :: Stock price = $99.61536938248533

BUILD SUCCESSFUL

Total time: 2 seconds

________________________________________________________________

according to the tutorial the output should be like in this link:

http://synapse.apache.org/Synapse_QuickStart.html

I'm running jdk 1.6 on Windows 7 with deactivated UAC, and temporaly deactivated windows firewall trying to solve this error.

Any advise or information about this error would be appreciated.

Best regards,

Thuy

Re: publishing an RPC-encoded WSDL in Synapse

2009-12-15T01:21:37Z

Nice to hear that you got it to work!

Thanks,
Ruwan

On Tue, Dec 15, 2009 at 10:16 AM, Sabareeswar P. B. <
Sabareeswar_PB@...> wrote:

> Thanks a lot Ruwan! it worked.
>
> Regards,
> Sabareeswar
> -----Original Message-----
> From: Ruwan Linton [mailto:ruwan.linton@...]
> Sent: Monday, December 14, 2009 6:49 PM
> To: user@...
> Subject: Re: publishing an RPC-encoded WSDL in Synapse
>
> It has to be on the proxy level and please note the spelling of the
> parameter name;
>
> <proxy name="Workflow">
>
> <target>
>
> <inSequence>
>
> <send>
>
> <endpoint>
>
> <address uri="http://localhost:8080/workflow"/>
>
> </endpoint>
>
> </send>
>
> </inSequence>
>
> <outSequence>
>
> <send/>
>
> </outSequence>
>
> </target>
>
> <publishWSDL
> uri="file:repository/conf/sample/resources/proxy/rpc.wsdl"/>
>
> <parameter name="useOriginalwsdl">true</parameter>
>
> </proxy>
>
> Thanks,
> Ruwan
>
>
> On Mon, Dec 14, 2009 at 6:30 PM, Sabareeswar P. B. <
> Sabareeswar_PB@...> wrote:
>
> > Thanks for replying Ruwan!
> >
> >
> >
> > I tried this out but still not getting the rpc wsdl as it is.
> >
> >
> >
> > I tried it with both
> >
> > <parameter name="useOriginalWSDL" value="true"/>
> >
> > And
> >
> > <parameter name="useOriginalWSDL">true</parameter>
> >
> >
> >
> > under publishWSDL as..
> >
> >
> >
> > <definitions xmlns="http://ws.apache.org/ns/synapse">
> >
> > <proxy name="Workflow">
> >
> > <target>
> >
> > <inSequence>
> >
> > <send>
> >
> > <endpoint>
> >
> > <address uri="http://localhost:8080/workflow"/>
> >
> > </endpoint>
> >
> > </send>
> >
> > </inSequence>
> >
> > <outSequence>
> >
> > <send/>
> >
> > </outSequence>
> >
> > </target>
> >
> > <publishWSDL
> > uri="file:repository/conf/sample/resources/proxy/rpc.wsdl">
> >
> > <parameter name="useOriginalWSDL">true</parameter>
> >
> > </publishWSDL>
> >
> > </proxy>
> >
> > </definitions>
> >
> >
> >
> > Regards,
> >
> > Sabareeswar
> >
> > +91 80 668 82267
> >
> > -----Original Message-----
> > From: Ruwan Linton [mailto:ruwan.linton@...]
> > Sent: Friday, December 11, 2009 9:21 PM
> > To: user@...
> > Subject: Re: publishing an RPC-encoded WSDL in Synapse
> >
> >
> >
> > Please use the parameter useOriginalWSDL as a parameter while creating
> the
> >
> > proxy.
> >
> >
> >
> > <parameter name="useOriginalWSDL" value="true"/>
> >
> >
> >
> > Thanks,
> >
> > Ruwan
> >
> >
> >
> > On Wed, Dec 9, 2009 at 2:31 PM, Sabareeswar P. B. <
> >
> > Sabareeswar_PB@...> wrote:
> >
> >
> >
> > > Hi,
> >
> > >
> >
> > > My requirement is to use Synapse and a soap intermediary between a web
> >
> > > service which exposes a document-literal WSDL and a web service client
> > which
> >
> > > has been generated out of an rpc-encoded WSDL.
> >
> > >
> >
> > > So I had planned to use the publishWSDL feature in Synapse to expose
> the
> >
> > > rpc-encoded WSDL to the client and internally forward the soap message
> to
> >
> > > the document-literal web service (after necessary transformations).
> >
> > >
> >
> > > The issue is that even if I point publishWSDL to an rpc-encoded WSDL,
> the
> >
> > > resulting wsdl from synapse is document-literal.
> >
> > >
> >
> > > Could someone please suggest me how to expose the rpc-encoded wsdl as
> it
> >
> > > is?
> >
> > >
> >
> > > Regards,
> >
> > > Sabareeswar
> >
> > >
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> > Ruwan Linton
> >
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> >
> > WSO2 Inc.; http://wso2.org
> >
> > email: ruwan@...; cell: +94 77 341 3097
> >
> > blog: http://ruwansblog.blogspot.com
> >
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org
> email: ruwan@...; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

RE: publishing an RPC-encoded WSDL in Synapse

2009-12-14T20:46:46Z

Thanks a lot Ruwan! it worked.

Regards,
Sabareeswar
-----Original Message-----
From: Ruwan Linton [mailto:ruwan.linton@...]
Sent: Monday, December 14, 2009 6:49 PM
To: user@...
Subject: Re: publishing an RPC-encoded WSDL in Synapse

It has to be on the proxy level and please note the spelling of the
parameter name;

<proxy name="Workflow">

<target>

<inSequence>

<send>

<endpoint>

<address uri="http://localhost:8080/workflow"/>

</endpoint>

</send>

</inSequence>

<outSequence>

<send/>

</outSequence>

</target>

<publishWSDL
uri="file:repository/conf/sample/resources/proxy/rpc.wsdl"/>

<parameter name="useOriginalwsdl">true</parameter>

</proxy>

Thanks,
Ruwan

On Mon, Dec 14, 2009 at 6:30 PM, Sabareeswar P. B. <
Sabareeswar_PB@...> wrote:

> Thanks for replying Ruwan!
>
>
>
> I tried this out but still not getting the rpc wsdl as it is.
>
>
>
> I tried it with both
>
> <parameter name="useOriginalWSDL" value="true"/>
>
> And
>
> <parameter name="useOriginalWSDL">true</parameter>
>
>
>
> under publishWSDL as..
>
>
>
> <definitions xmlns="http://ws.apache.org/ns/synapse">
>
> <proxy name="Workflow">
>
> <target>
>
> <inSequence>
>
> <send>
>
> <endpoint>
>
> <address uri="http://localhost:8080/workflow"/>
>
> </endpoint>
>
> </send>
>
> </inSequence>
>
> <outSequence>
>
> <send/>
>
> </outSequence>
>
> </target>
>
> <publishWSDL
> uri="file:repository/conf/sample/resources/proxy/rpc.wsdl">
>
> <parameter name="useOriginalWSDL">true</parameter>
>
> </publishWSDL>
>
> </proxy>
>
> </definitions>
>
>
>
> Regards,
>
> Sabareeswar
>
> +91 80 668 82267
>
> -----Original Message-----
> From: Ruwan Linton [mailto:ruwan.linton@...]
> Sent: Friday, December 11, 2009 9:21 PM
> To: user@...
> Subject: Re: publishing an RPC-encoded WSDL in Synapse
>
>
>
> Please use the parameter useOriginalWSDL as a parameter while creating the
>
> proxy.
>
>
>
> <parameter name="useOriginalWSDL" value="true"/>
>
>
>
> Thanks,
>
> Ruwan
>
>
>
> On Wed, Dec 9, 2009 at 2:31 PM, Sabareeswar P. B. <
>
> Sabareeswar_PB@...> wrote:
>
>
>
> > Hi,
>
> >
>
> > My requirement is to use Synapse and a soap intermediary between a web
>
> > service which exposes a document-literal WSDL and a web service client
> which
>
> > has been generated out of an rpc-encoded WSDL.
>
> >
>
> > So I had planned to use the publishWSDL feature in Synapse to expose the
>
> > rpc-encoded WSDL to the client and internally forward the soap message to
>
> > the document-literal web service (after necessary transformations).
>
> >
>
> > The issue is that even if I point publishWSDL to an rpc-encoded WSDL, the
>
> > resulting wsdl from synapse is document-literal.
>
> >
>
> > Could someone please suggest me how to expose the rpc-encoded wsdl as it
>
> > is?
>
> >
>
> > Regards,
>
> > Sabareeswar
>
> >
>
>
>
>
>
>
>
> --
>
> Ruwan Linton
>
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>
> WSO2 Inc.; http://wso2.org
>
> email: ruwan@...; cell: +94 77 341 3097
>
> blog: http://ruwansblog.blogspot.com
>

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

Re: publishing an RPC-encoded WSDL in Synapse

2009-12-14T05:19:15Z

It has to be on the proxy level and please note the spelling of the
parameter name;

<proxy name="Workflow">

<target>

<inSequence>

<send>

<endpoint>

<address uri="http://localhost:8080/workflow"/>

</endpoint>

</send>

</inSequence>

<outSequence>

<send/>

</outSequence>

</target>

<publishWSDL
uri="file:repository/conf/sample/resources/proxy/rpc.wsdl"/>

<parameter name="useOriginalwsdl">true</parameter>

</proxy>

Thanks,
Ruwan

On Mon, Dec 14, 2009 at 6:30 PM, Sabareeswar P. B. <
Sabareeswar_PB@...> wrote:

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

RE: publishing an RPC-encoded WSDL in Synapse

2009-12-14T05:00:00Z

Thanks for replying Ruwan!

I tried this out but still not getting the rpc wsdl as it is.

I tried it with both

<parameter name="useOriginalWSDL" value="true"/>

And

<parameter name="useOriginalWSDL">true</parameter>

under publishWSDL as..

<definitions xmlns="http://ws.apache.org/ns/synapse">

<proxy name="Workflow">

<target>

<inSequence>

<send>

<endpoint>

<address uri="http://localhost:8080/workflow"/>

</endpoint>

</send>

</inSequence>

<outSequence>

<send/>

</outSequence>

</target>

<publishWSDL uri="file:repository/conf/sample/resources/proxy/rpc.wsdl">

<parameter name="useOriginalWSDL">true</parameter>

</publishWSDL>

</proxy>

</definitions>

Regards,

Sabareeswar

+91 80 668 82267

-----Original Message-----
From: Ruwan Linton [mailto:ruwan.linton@...]
Sent: Friday, December 11, 2009 9:21 PM
To: user@...
Subject: Re: publishing an RPC-encoded WSDL in Synapse

Please use the parameter useOriginalWSDL as a parameter while creating the

proxy.

<parameter name="useOriginalWSDL" value="true"/>

Thanks,

Ruwan

On Wed, Dec 9, 2009 at 2:31 PM, Sabareeswar P. B. <

Sabareeswar_PB@...> wrote:

> Hi,

>

> My requirement is to use Synapse and a soap intermediary between a web

> service which exposes a document-literal WSDL and a web service client which

> has been generated out of an rpc-encoded WSDL.

>

> So I had planned to use the publishWSDL feature in Synapse to expose the

> rpc-encoded WSDL to the client and internally forward the soap message to

> the document-literal web service (after necessary transformations).

>

> The issue is that even if I point publishWSDL to an rpc-encoded WSDL, the

> resulting wsdl from synapse is document-literal.

>

> Could someone please suggest me how to expose the rpc-encoded wsdl as it

> is?

>

> Regards,

> Sabareeswar

>

--

Ruwan Linton

Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb

WSO2 Inc.; http://wso2.org

email: ruwan@...; cell: +94 77 341 3097

blog: http://ruwansblog.blogspot.com

Re: publishing an RPC-encoded WSDL in Synapse

2009-12-11T07:50:48Z

Please use the parameter useOriginalWSDL as a parameter while creating the
proxy.

<parameter name="useOriginalWSDL" value="true"/>

Thanks,
Ruwan

On Wed, Dec 9, 2009 at 2:31 PM, Sabareeswar P. B. <
Sabareeswar_PB@...> wrote:

> Hi,
>
> My requirement is to use Synapse and a soap intermediary between a web
> service which exposes a document-literal WSDL and a web service client which
> has been generated out of an rpc-encoded WSDL.
>
> So I had planned to use the publishWSDL feature in Synapse to expose the
> rpc-encoded WSDL to the client and internally forward the soap message to
> the document-literal web service (after necessary transformations).
>
> The issue is that even if I point publishWSDL to an rpc-encoded WSDL, the
> resulting wsdl from synapse is document-literal.
>
> Could someone please suggest me how to expose the rpc-encoded wsdl as it
> is?
>
> Regards,
> Sabareeswar
>

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

Re: Synapse as a connector to non-FIX engine

2009-12-10T06:57:34Z

Sorry wrong link , it should change as
http://people.apache.org/~veithen/transport/tcp-transport.html.
- Asanka

2009/12/10 Asanka Abeysinghe <asankaa@...>

> Hi Pani,
> I did point the AMQP and HTTP protocol bridging samples to get an idea for
> you to start implementing your use-case , not trying to switch you to AMQP
> :).
> We don't have a sample that demonstrate the usage of TCP transport but you
> can find information from the TCP transport guide [1], sample 380
> demonstrate on writing custom mediators using Java.
> Regards
> Asanka
>
> [1] http://people.apache.org/~veithen/transport/jms.html<http://people.apache.org/%7Eveithen/transport/jms.html>
>
>
>
> On Thu, Dec 10, 2009 at 3:41 PM, Phani Arava <phani@...> wrote:
>
>> Asanka,
>>
>> Thanks a lot for the reply. Well I have gone through the examples in the
>> morning. Iam getting a fair idea on the same, but being an ignorant person
>> on AMQP and from what i have read on the same AMQP is a wire protocol
>> standard. I cannot be using AMQP/JMS because my provider is not complicant
>> for the same. (Pardon my ignorance if any...)
>>
>> Iam looking for a good example on TCP transport, with maybe bytebuffer /
>> POJO example, it will be easier for java novices like me.
>>
>> Regards
>> Phani
>>
>> On Thu, Dec 10, 2009 at 3:15 PM, Asanka Abeysinghe <asankaa@...>
>> wrote:
>>
>> > Hi Phani,
>> > If I read you correctly you are need to send a FIX message coming from a
>> > FIX
>> > endpoint to a endpoint that does not support FIX and accept messages
>> > through
>> > row TCP sockets.
>> > Yes, you can do this by making a proxy service accept messages from
>> > FIX-{version} by making the incoming transport as FIX and configure the
>> > proxy service to have TCP transport as outgoing.
>> > Synapse converts the FIX message into a XML infoset internally so you
>> might
>> > have to do transformation to the XML payload in the case of your non FIX
>> > endpoint accept messages on XML format. If your non FIX endpoint is
>> > requesting a non XML format then you have to do more work on writing a
>> > mediator/message formatter to do the formatting.
>> > There are two samples 259 (FIX to HTTP), 260 (FIX to AMQP/JMS) in the
>> > synapse trunk and 1.3 branch (that you have to build or take from a
>> nightly
>> > build), those samples will explain on how to implement the pattern
>> protocol
>> > bridging with FIX.
>> > Regards
>> > Asanka
>> >
>> > On Thu, Dec 10, 2009 at 8:29 AM, Phani Arava <phani@...>
>> wrote:
>> >
>> > > Hi All,
>> > >
>> > > Iam pretty new to synapse (not exactly very good with Java..) trying
>> out
>> > my
>> > > hands with synapse. Till now succesful in running the sample_257.
>> > >
>> > > Actually trying to connect a non-FIX exchange with synapse. The
>> protocol
>> > > defined by this exchange is given to us (Plain old TCP sockets) . Can
>> we
>> > > define an adapter for my app to connect to Synapse (for FIX) and
>> synapse
>> > > connects to the exchange with the message protocol.
>> > >
>> > > How to go about this whole project. What more of java whould i be
>> > exploring
>> > > before getting into synapse configurations ?
>> > >
>> > > Regards
>> > > Phani
>> > >
>> >
>> >
>> >
>> > --
>> > Asanka Abeysinghe
>> > Architect - WSO2, Inc.
>> > m: +94 77 7340064 p: +94 11 2688451/3
>> > e: asankaa@... w: http://www.wso2.com
>> > b: http://www.asankama.com
>> >
>>
>
>
>
> --
> Asanka Abeysinghe
> Architect - WSO2, Inc.
> m: +94 77 7340064 p: +94 11 2688451/3
> e: asankaa@... w: http://www.wso2.com
> b: http://www.asankama.com
>

--
Asanka Abeysinghe
Architect - WSO2, Inc.
m: +94 77 7340064 p: +94 11 2688451/3
e: asankaa@... w: http://www.wso2.com
b: http://www.asankama.com

Re: Synapse as a connector to non-FIX engine

2009-12-10T06:50:32Z

Hi Pani,
I did point the AMQP and HTTP protocol bridging samples to get an idea for
you to start implementing your use-case , not trying to switch you to AMQP
:).
We don't have a sample that demonstrate the usage of TCP transport but you
can find information from the TCP transport guide [1], sample 380
demonstrate on writing custom mediators using Java.
Regards
Asanka

[1] http://people.apache.org/~veithen/transport/jms.html

On Thu, Dec 10, 2009 at 3:41 PM, Phani Arava <phani@...> wrote:

> Asanka,
>
> Thanks a lot for the reply. Well I have gone through the examples in the
> morning. Iam getting a fair idea on the same, but being an ignorant person
> on AMQP and from what i have read on the same AMQP is a wire protocol
> standard. I cannot be using AMQP/JMS because my provider is not complicant
> for the same. (Pardon my ignorance if any...)
>
> Iam looking for a good example on TCP transport, with maybe bytebuffer /
> POJO example, it will be easier for java novices like me.
>
> Regards
> Phani
>
> On Thu, Dec 10, 2009 at 3:15 PM, Asanka Abeysinghe <asankaa@...>
> wrote:
>
> > Hi Phani,
> > If I read you correctly you are need to send a FIX message coming from a
> > FIX
> > endpoint to a endpoint that does not support FIX and accept messages
> > through
> > row TCP sockets.
> > Yes, you can do this by making a proxy service accept messages from
> > FIX-{version} by making the incoming transport as FIX and configure the
> > proxy service to have TCP transport as outgoing.
> > Synapse converts the FIX message into a XML infoset internally so you
> might
> > have to do transformation to the XML payload in the case of your non FIX
> > endpoint accept messages on XML format. If your non FIX endpoint is
> > requesting a non XML format then you have to do more work on writing a
> > mediator/message formatter to do the formatting.
> > There are two samples 259 (FIX to HTTP), 260 (FIX to AMQP/JMS) in the
> > synapse trunk and 1.3 branch (that you have to build or take from a
> nightly
> > build), those samples will explain on how to implement the pattern
> protocol
> > bridging with FIX.
> > Regards
> > Asanka
> >
> > On Thu, Dec 10, 2009 at 8:29 AM, Phani Arava <phani@...> wrote:
> >
> > > Hi All,
> > >
> > > Iam pretty new to synapse (not exactly very good with Java..) trying
> out
> > my
> > > hands with synapse. Till now succesful in running the sample_257.
> > >
> > > Actually trying to connect a non-FIX exchange with synapse. The
> protocol
> > > defined by this exchange is given to us (Plain old TCP sockets) . Can
> we
> > > define an adapter for my app to connect to Synapse (for FIX) and
> synapse
> > > connects to the exchange with the message protocol.
> > >
> > > How to go about this whole project. What more of java whould i be
> > exploring
> > > before getting into synapse configurations ?
> > >
> > > Regards
> > > Phani
> > >
> >
> >
> >
> > --
> > Asanka Abeysinghe
> > Architect - WSO2, Inc.
> > m: +94 77 7340064 p: +94 11 2688451/3
> > e: asankaa@... w: http://www.wso2.com
> > b: http://www.asankama.com
> >
>

--
Asanka Abeysinghe
Architect - WSO2, Inc.
m: +94 77 7340064 p: +94 11 2688451/3
e: asankaa@... w: http://www.wso2.com
b: http://www.asankama.com

Re: Synapse as a connector to non-FIX engine

2009-12-10T02:11:32Z

Asanka,

Thanks a lot for the reply. Well I have gone through the examples in the
morning. Iam getting a fair idea on the same, but being an ignorant person
on AMQP and from what i have read on the same AMQP is a wire protocol
standard. I cannot be using AMQP/JMS because my provider is not complicant
for the same. (Pardon my ignorance if any...)

Iam looking for a good example on TCP transport, with maybe bytebuffer /
POJO example, it will be easier for java novices like me.

Regards
Phani

On Thu, Dec 10, 2009 at 3:15 PM, Asanka Abeysinghe <asankaa@...> wrote:

> Hi Phani,
> If I read you correctly you are need to send a FIX message coming from a
> FIX
> endpoint to a endpoint that does not support FIX and accept messages
> through
> row TCP sockets.
> Yes, you can do this by making a proxy service accept messages from
> FIX-{version} by making the incoming transport as FIX and configure the
> proxy service to have TCP transport as outgoing.
> Synapse converts the FIX message into a XML infoset internally so you might
> have to do transformation to the XML payload in the case of your non FIX
> endpoint accept messages on XML format. If your non FIX endpoint is
> requesting a non XML format then you have to do more work on writing a
> mediator/message formatter to do the formatting.
> There are two samples 259 (FIX to HTTP), 260 (FIX to AMQP/JMS) in the
> synapse trunk and 1.3 branch (that you have to build or take from a nightly
> build), those samples will explain on how to implement the pattern protocol
> bridging with FIX.
> Regards
> Asanka
>
> On Thu, Dec 10, 2009 at 8:29 AM, Phani Arava <phani@...> wrote:
>
> > Hi All,
> >
> > Iam pretty new to synapse (not exactly very good with Java..) trying out
> my
> > hands with synapse. Till now succesful in running the sample_257.
> >
> > Actually trying to connect a non-FIX exchange with synapse. The protocol
> > defined by this exchange is given to us (Plain old TCP sockets) . Can we
> > define an adapter for my app to connect to Synapse (for FIX) and synapse
> > connects to the exchange with the message protocol.
> >
> > How to go about this whole project. What more of java whould i be
> exploring
> > before getting into synapse configurations ?
> >
> > Regards
> > Phani
> >
>
>
>
> --
> Asanka Abeysinghe
> Architect - WSO2, Inc.
> m: +94 77 7340064 p: +94 11 2688451/3
> e: asankaa@... w: http://www.wso2.com
> b: http://www.asankama.com
>

Re: Synapse as a connector to non-FIX engine

2009-12-10T01:45:27Z

Hi Phani,
If I read you correctly you are need to send a FIX message coming from a FIX
endpoint to a endpoint that does not support FIX and accept messages through
row TCP sockets.
Yes, you can do this by making a proxy service accept messages from
FIX-{version} by making the incoming transport as FIX and configure the
proxy service to have TCP transport as outgoing.
Synapse converts the FIX message into a XML infoset internally so you might
have to do transformation to the XML payload in the case of your non FIX
endpoint accept messages on XML format. If your non FIX endpoint is
requesting a non XML format then you have to do more work on writing a
mediator/message formatter to do the formatting.
There are two samples 259 (FIX to HTTP), 260 (FIX to AMQP/JMS) in the
synapse trunk and 1.3 branch (that you have to build or take from a nightly
build), those samples will explain on how to implement the pattern protocol
bridging with FIX.
Regards
Asanka

On Thu, Dec 10, 2009 at 8:29 AM, Phani Arava <phani@...> wrote:

> Hi All,
>
> Iam pretty new to synapse (not exactly very good with Java..) trying out my
> hands with synapse. Till now succesful in running the sample_257.
>
> Actually trying to connect a non-FIX exchange with synapse. The protocol
> defined by this exchange is given to us (Plain old TCP sockets) . Can we
> define an adapter for my app to connect to Synapse (for FIX) and synapse
> connects to the exchange with the message protocol.
>
> How to go about this whole project. What more of java whould i be exploring
> before getting into synapse configurations ?
>
> Regards
> Phani
>

--
Asanka Abeysinghe
Architect - WSO2, Inc.
m: +94 77 7340064 p: +94 11 2688451/3
e: asankaa@... w: http://www.wso2.com
b: http://www.asankama.com

Synapse as a connector to non-FIX engine

2009-12-09T18:59:00Z

Hi All,

Iam pretty new to synapse (not exactly very good with Java..) trying out my
hands with synapse. Till now succesful in running the sample_257.

Actually trying to connect a non-FIX exchange with synapse. The protocol
defined by this exchange is given to us (Plain old TCP sockets) . Can we
define an adapter for my app to connect to Synapse (for FIX) and synapse
connects to the exchange with the message protocol.

How to go about this whole project. What more of java whould i be exploring
before getting into synapse configurations ?

Regards
Phani

publishing an RPC-encoded WSDL in Synapse

2009-12-09T01:01:44Z

Hi,

My requirement is to use Synapse and a soap intermediary between a web service which exposes a document-literal WSDL and a web service client which has been generated out of an rpc-encoded WSDL.

So I had planned to use the publishWSDL feature in Synapse to expose the rpc-encoded WSDL to the client and internally forward the soap message to the document-literal web service (after necessary transformations).

The issue is that even if I point publishWSDL to an rpc-encoded WSDL, the resulting wsdl from synapse is document-literal.

Could someone please suggest me how to expose the rpc-encoded wsdl as it is?

Regards,
Sabareeswar

RE: Select endpoint based on header information

2009-12-02T07:42:42Z

You can use the filter and send mediators to accomplish this.
http://synapse.apache.org/Synapse_Configuration_Language.html#filter
http://synapse.apache.org/Synapse_Configuration_Language.html#send

Synapse defines the header variable to get at the SOAP header with
xpath.
http://synapse.apache.org/Synapse_Configuration_Language.html#property

Here is a sample.

<?xml version="1.0"?>
<definitions xmlns="http://ws.apache.org/ns/synapse">
<in>
<filter xpath="$header/foo">
<send>
<endpoint>
<address uri="http://foo" />
</endpoint>
</send>
<filter
</in>
</definitions>

You should check out the samples 1 and 2.
http://synapse.apache.org/Synapse_Samples.html#Sample1
http://synapse.apache.org/Synapse_Samples.html#Sample2

Good luck!

-----Original Message-----
From: Massimo Cancellara [mailto:massimo@...]
Sent: Wednesday, December 02, 2009 6:23 AM
To: user@...
Subject: Select endpoint based on header information

Hi,

I'm new to Synapse and I'm trying to understand if it can fit my
scenario.

Is it possible for a mediator to set the endpoint basing on informations
in an ad-hoc header? If yes, how (just a suggestion on where to look at)

Thanks, regards

Massimo

Select endpoint based on header information

2009-12-02T04:22:54Z

Hi,

I'm new to Synapse and I'm trying to understand if it can fit my scenario.

Is it possible for a mediator to set the endpoint basing on informations in an ad-hoc header? If yes, how (just a suggestion on where to look at)

Thanks, regards

Massimo

RE: Synapse 1.3: REST help (PUT/DELETE)

2009-11-24T02:59:29Z

Hi Asankha,

> > We're looking at using Apache Synapse as a mocking framework for some
> REST services.
> >
> > >From looking at JIRA, it seems that the PUT/DELETE methods are now
> supported in the 1.3 branch, which I have checked out and built.
> >
> > Does anybody have any experience using these new methods, or are few
> people using them as yet? It's just that it is unclear how the
> configuration language would support them, and the documentation and
> examples have not yet been updated in this branch (understandable so of
> course).
> >
> > Any guidance would be appreciated.
> >
> The support implemented gives the ability to Synapse to mediate REST
> service calls. I am not sure I fully understand your expectations as a
> mocking framework.. if you could share a sample use-case I can easily
> let you know if its possible, and how. If you need to share any
> confidential code/samples, you could mail them directly to me

Thanks for the quick reply. We're looking at using Synapse to mock RESTful services; that is, to simulate real services to help with Continuous Integration of consumers of these services when they are down, changing etc. So similar to what IBM are doing here:

http://www.ibm.com/developerworks/edu/ws-dw-ws-synapse.html

but with REST/POX only. The services we wish to simulate make heavy use of HTTP stuff, such as PUT/DELETE, common headers, HTTP basic authentication, and the like.

So in general, out solution would have to consume HTTP requests (POST/GET/PUT/DELETE), and if appropriate, return an XML response based on transformations of the request headers, request data and perhaps files and other data sources etc. The XML requests/responses are defined by XML schemata, without the use of WADL.

Do you think Synapse 1.3 (given aside that it's unreleased), would be able to handle this task? If not, how far is our use case away from what Synapse REST support is heading? If so, I would consider it a _major_ selling point (as it were) for Synapse since we have found nothing, either commercial or otherwise, that does REST mocking/simulation. The SOAPUI folk have some rudimentary REST mocking support, but they only support returning canned responses from static files. They do have some plans in this area I am told however.

If Synapse is not far from what we need, is there any scope for us to contribute (in some way) to help this along?

Kind regards,

James.

Re: Synapse 1.3: REST help (PUT/DELETE)

2009-11-24T02:37:22Z

Hi James
> We're looking at using Apache Synapse as a mocking framework for some REST services.
>
> >From looking at JIRA, it seems that the PUT/DELETE methods are now supported in the 1.3 branch, which I have checked out and built.
>
> Does anybody have any experience using these new methods, or are few people using them as yet? It's just that it is unclear how the configuration language would support them, and the documentation and examples have not yet been updated in this branch (understandable so of course).
>
> Any guidance would be appreciated.
>
The support implemented gives the ability to Synapse to mediate REST
service calls. I am not sure I fully understand your expectations as a
mocking framework.. if you could share a sample use-case I can easily
let you know if its possible, and how. If you need to share any
confidential code/samples, you could mail them directly to me

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com

Synapse 1.3: REST help (PUT/DELETE)

2009-11-24T02:21:42Z

Hi All,

We're looking at using Apache Synapse as a mocking framework for some REST services.

From looking at JIRA, it seems that the PUT/DELETE methods are now supported in the 1.3 branch, which I have checked out and built.

Does anybody have any experience using these new methods, or are few people using them as yet? It's just that it is unclear how the configuration language would support them, and the documentation and examples have not yet been updated in this branch (understandable so of course).

Any guidance would be appreciated.

Regards,

--
James Carnegie
Nokia UK Limited

Synapse 1.3-SNAPSHOT nightly builds

2009-11-13T06:02:51Z

Hi All

I've configured a Synapse 1.3-SNAPSHOT build in Hudson, and builds will
be available from:
http://hudson.zones.apache.org/hudson/view/All/job/Synapse%20-%201.3%20-%20SNAPSHOT/

The last successful build will be available at:
http://hudson.zones.apache.org/hudson/view/All/job/Synapse%20-%201.3%20-%20SNAPSHOT/lastSuccessfulBuild/org.apache.synapse$synapse-distribution/artifact/org.apache.synapse/synapse-distribution/1.3.0-SNAPSHOT/synapse-1.3.0-SNAPSHOT-bin.zip

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com

Re: java.io.IOException: Too many open files

2009-11-12T11:07:25Z

Those are settings in the /etc/sysctl.conf and /etc/security/limits.conf
files respectively.

Alternatively, you can try to do, ulimit -n 4096, before starting your
Synapse server. However, that option may not work on some systems.

Azeez

On Thu, Nov 12, 2009 at 6:01 PM, Khaled Farj <k.a.s.farj@...>wrote:

> Hi asankha,
> About the testing, that's exactly what my work is about, I am testing web
> service apps.
> However I could not figure out what you mean about these values and where I
> can find these values ..?.
>
> Cheers
> khaled
>
>
> >-----Original Message-----
> >From: Asankha Perera [mailto:asankha.apache@...] On
> >Behalf Of Asankha C. Perera
> >Sent: 12 November 2009 17:46
> >To: user@...
> >Subject: Re: java.io.IOException: Too many open files
> >
> >Hi Khaled
> >> Thanks asankha, I have done what you said and I changed to
> >Synapse-1.2, evrything works well until the request number
> >(1680) !! And almost the same Exception is thrown again.. ?.
> >My work is for sending 3000 requests to Synapse which in turn
> >sends them to the actual Web Service applications.
> >>
> >> Any help, please?
> >>
> >Do you have the following set? .. I usually set those for load testing.
> >See [http://wso2.org/library/3740 etc]
> >
> >/etc/sysctl.conf
> >net.ipv4.ip_local_port_range = 1024 65535
> >net.ipv4.tcp_fin_timeout = 30 fs.file-max = 2097152
> >net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_tw_reuse = 1
> >
> >/etc/security/limits.conf
> >* soft nofile 4096
> >* hard nofile 65535
> >
> >
> >cheers
> >asankha
> >
> >--
> >Asankha C. Perera
> >AdroitLogic, http://adroitlogic.org
> >
> >http://esbmagic.blogspot.com
> >
> >
> >
> >
> >
>

--
Thanks
Afkham Azeez

Blog: http://afkham.org
Developer Portal: http://www.wso2.org
WSAS Blog: http://wso2wsas.blogspot.com
Company: http://wso2.com
GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760

RE: java.io.IOException: Too many open files

2009-11-12T10:01:06Z

Hi asankha,
About the testing, that's exactly what my work is about, I am testing web service apps.
However I could not figure out what you mean about these values and where I can find these values ..?.

Cheers
khaled

>-----Original Message-----
>From: Asankha Perera [mailto:asankha.apache@...] On
>Behalf Of Asankha C. Perera
>Sent: 12 November 2009 17:46
>To: user@...
>Subject: Re: java.io.IOException: Too many open files
>
>Hi Khaled
>> Thanks asankha, I have done what you said and I changed to
>Synapse-1.2, evrything works well until the request number
>(1680) !! And almost the same Exception is thrown again.. ?.
>My work is for sending 3000 requests to Synapse which in turn
>sends them to the actual Web Service applications.
>>
>> Any help, please?
>>
>Do you have the following set? .. I usually set those for load testing.
>See [http://wso2.org/library/3740 etc]
>
>/etc/sysctl.conf
>net.ipv4.ip_local_port_range = 1024 65535
>net.ipv4.tcp_fin_timeout = 30 fs.file-max = 2097152
>net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_tw_reuse = 1
>
>/etc/security/limits.conf
>* soft nofile 4096
>* hard nofile 65535
>
>
>cheers
>asankha
>
>--
>Asankha C. Perera
>AdroitLogic, http://adroitlogic.org
>
>http://esbmagic.blogspot.com
>
>
>
>
>

Re: java.io.IOException: Too many open files

2009-11-12T09:45:50Z

Hi Khaled
> Thanks asankha, I have done what you said and I changed to Synapse-1.2, evrything works well until the request number (1680) !! And almost the same Exception is thrown again.. ?. My work is for sending 3000 requests to Synapse which in turn sends them to the actual Web Service applications.
>
> Any help, please?
>
Do you have the following set? .. I usually set those for load testing.
See [http://wso2.org/library/3740 etc]

/etc/sysctl.conf
net.ipv4.ip_local_port_range = 1024 65535
net.ipv4.tcp_fin_timeout = 30
fs.file-max = 2097152
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1

/etc/security/limits.conf
* soft nofile 4096
* hard nofile 65535

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com

RE: java.io.IOException: Too many open files

2009-11-12T09:39:59Z

Hi again,

Thanks asankha, I have done what you said and I changed to Synapse-1.2, evrything works well until the request number (1680) !! And almost the same Exception is thrown again.. ?. My work is for sending 3000 requests to Synapse which in turn sends them to the actual Web Service applications.

Any help, please?

2009-11-12 17:28:14,653 [10.8.147.11-localhost] [HttpServerWorker-7] ERROR ServerWorker Error getting ip address for ?wsdl output
java.net.SocketException: Too many open files
at java.net.NetworkInterface.getAll(Native Method)
at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:204)
at org.apache.synapse.transport.nhttp.ServerWorker.getIpAddress(ServerWorker.java:540)
at org.apache.synapse.transport.nhttp.ServerWorker.processGet(ServerWorker.java:341)
at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:192)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
2009-11-12 17:28:14,796 [10.8.147.11-cage03.ncl.ac.uk] [HttpServerWorker-7] ERROR ServerHandler Unexpected HTTP protocol error : Transfer-encoding header already present
org.apache.http.ProtocolException: Transfer-encoding header already present
at org.apache.http.protocol.ResponseContent.process(ResponseContent.java:67)
at org.apache.http.protocol.BasicHttpProcessor.process(BasicHttpProcessor.java:304)
at org.apache.synapse.transport.nhttp.ServerHandler.commitResponse(ServerHandler.java:212)
at org.apache.synapse.transport.nhttp.HttpCoreNIOSender.sendAsyncResponse(HttpCoreNIOSender.java:409)
at org.apache.synapse.transport.nhttp.HttpCoreNIOSender.invoke(HttpCoreNIOSender.java:264)
at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:530)
at org.apache.synapse.transport.nhttp.ServerWorker.handleException(ServerWorker.java:489)
at org.apache.synapse.transport.nhttp.ServerWorker.processGet(ServerWorker.java:347)
at org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:192)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

Thanks
Khaled

>-----Original Message-----
>From: Asankha Perera [mailto:asankha.apache@...] On
>Behalf Of Asankha C. Perera
>Sent: 12 November 2009 01:47
>To: user@...
>Subject: Re: java.io.IOException: Too many open files
>
>Hi Khaled
>> I am using Synapse-1.1.1 but I have got the error stated below:
>>
>You could try increasing file limits if under a Linux environment etc..
>however, I would strongly suggest you upgrade to 1.2, in which
>we have removed the usage of pipes altogether with a much
>better implementation
>
>cheers
>asankha
>
>--
>Asankha C. Perera
>AdroitLogic, http://adroitlogic.org
>
>http://esbmagic.blogspot.com
>
>
>
>
>

Re: java.io.IOException: Too many open files

2009-11-11T17:46:40Z

Hi Khaled
> I am using Synapse-1.1.1 but I have got the error stated below:
>
You could try increasing file limits if under a Linux environment etc..
however, I would strongly suggest you upgrade to 1.2, in which we have
removed the usage of pipes altogether with a much better implementation

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com

java.io.IOException: Too many open files

2009-11-11T15:57:53Z

Hi guys,

I am using Synapse-1.1.1 but I have got the error stated below:

What I am using Synapse is as follows:

I have published three proxies in synapse that are Service1, Service2 and Service3. and I have a client which its job is sending three requests to the Synapse - a request for each proxy Service deployed in Synapse (Service1, Service2 and Service3) - my client sends three requests each time and then synapse forwards each request to the actual service and then receives the responses then forward them to the client. Everything works fine at this point, however when the client sends more than 300 request the below exception is thrown in Synapse.. !. I wander if that has something to do with Synapse pool threads OR what ????
Can anybody tell me what is going on please?

2009-11-11 18:18:46,385 [10.8.147.11-localhost] [I/O dispatcher 8] ERROR ServerHandler Error processing request received for : /soap/Service3?wsdl
java.io.IOException: Too many open files
at sun.nio.ch.IOUtil.initPipe(Native Method)
at sun.nio.ch.PipeImpl.<init>(PipeImpl.java:25)
at sun.nio.ch.SelectorProviderImpl.openPipe(SelectorProviderImpl.java:27)
at java.nio.channels.Pipe.open(Pipe.java:133)
at org.apache.synapse.transport.nhttp.util.PipeImpl.<init>(PipeImpl.java:77)
at org.apache.synapse.transport.nhttp.ServerHandler.requestReceived(ServerHandler.java:118)
at org.apache.synapse.transport.nhttp.LoggingNHttpServiceHandler.requestReceived(LoggingNHttpServiceHandler.java:92)
at org.apache.http.impl.nio.DefaultNHttpServerConnection.consumeInput(DefaultNHttpServerConnection.java:123)
at org.apache.synapse.transport.nhttp.PlainServerIOEventDispatch.inputReady(PlainServerIOEventDispatch.java:69)
at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:98)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:195)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:180)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:142)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:70)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:318)
at java.lang.Thread.run(Thread.java:595)
2009-11-11 18:18:46,387 [10.8.147.11-cage03.ncl.ac.uk] [I/O dispatcher 8] WARN HttpCoreNIOListener System may be unstable: IOReactor encountered a runtime exception : null
java.lang.NullPointerException
at org.apache.synapse.transport.nhttp.ServerHandler.inputReady(ServerHandler.java:171)
at org.apache.synapse.transport.nhttp.LoggingNHttpServiceHandler.inputReady(LoggingNHttpServiceHandler.java:123)
at org.apache.http.impl.nio.DefaultNHttpServerConnection.consumeInput(DefaultNHttpServerConnection.java:135)
at org.apache.synapse.transport.nhttp.PlainServerIOEventDispatch.inputReady(PlainServerIOEventDispatch.java:69)
at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:98)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:195)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:180)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:142)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:70)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:318)
at java.lang.Thread.run(Thread.java:595).

Thanks
Khaled

Re: Disabling FastInfoset for Synapse endpoints

2009-11-09T13:38:29Z

Hi Ralph,

Whether the message is written to the wire as a FI or not is a functionality
of the message formatter so disabling the FI to the backend endpoint and
re-enabling the FI for the response to the client is theoretically possible
with Synapse, but I have never tried this.

To try this out, configure the axis2.xml to enable the FI as described in
this article [1] and then set the messageType property to
application/soap+fastinfoset or application/fastinfoset as appropriately
using the property mediator in the synapse configuration to enable FI and
change the messageType propety to the relevant message type of the backend
endpoint to disable FI for the backend requests.

[1] - http://wso2.org/library/2686

Thanks,
Ruwan

On Mon, Nov 9, 2009 at 10:10 PM, <Ralph.Henze@...> wrote:

> Hi,
>
> I want to configure synapse as a FastInfoset-capable proxy for a number of
> existing services.
> Some of them are based on SOAP stacks other than Axis2 and do not have the
> capability of FastInfoset.
>
> Is there an easy way to configure synapse in a way that proxy services can
> be called using FastInfoset and endpoints get called using simple
> soap/xml?
> This should include the backward direction; meaning that non-FI responses
> from the endpoints get translated into FI-responses to the client.
>
> Thank you.
>
> Greetings, Ralph.

--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@...; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

Disabling FastInfoset for Synapse endpoints

2009-11-09T08:40:21Z

Hi,

I want to configure synapse as a FastInfoset-capable proxy for a number of
existing services.
Some of them are based on SOAP stacks other than Axis2 and do not have the
capability of FastInfoset.

Is there an easy way to configure synapse in a way that proxy services can
be called using FastInfoset and endpoints get called using simple
soap/xml?
This should include the backward direction; meaning that non-FI responses
from the endpoints get translated into FI-responses to the client.

Thank you.

Greetings, Ralph.

RE: Adding a security token

2009-10-28T05:47:21Z

Thanks Asankha! Will refer the Rampart site.

Regards,
Sabareeswar
-----Original Message-----
From: Asankha Perera [mailto:asankha.apache@...] On Behalf Of Asankha C. Perera
Sent: Wednesday, October 28, 2009 6:13 PM
To: user@...
Subject: Re: Adding a security token

Hi Sabareeswar

> I am new to frameworks like WS-policy and WS-Security.
>
> I am using synapse as a SOAP intermediary and I want to introduce a username token in the soap message which comes out of synapse.
> The token must look like
>
> xmlns:oas="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
> <oas:Security>
> <oas:UsernameToken>
> <oas:Username>admin</oas:Username>
> <oas:Password>admin123</oas:Password>
> </oas:UsernameToken>
> </oas:Security>
>
> Could you please tell me how I must proceed with synapse?
>

Basically Synapse does not go into exactly which WS-Security policy you
enforce.. you just provide it with a policy that states what you want.
For outgoing messages, what you need is similar to
http://synapse.apache.org/Synapse_Samples.html#Sample100

You should have the sample policy used for the above as
repository/conf/sample/resources/policy/policy_3.xml in your
distribution. Synapse uses Apache Rampart to get this done, so it is
Rampart that will read the policy and apply it. You will have better
luck if you ask someone on the Apache Rampart mailing list or search
through the samples for the above case.. I am sorry I do not have much
free time right now to look for this myself, but if you really cannot
find anything from Rampart, ping me again next week

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com

Re: Adding a security token

2009-10-28T05:43:08Z

Hi Sabareeswar

Adding a security token

2009-10-27T21:49:19Z

Hi,
I am new to frameworks like WS-policy and WS-Security.

I am using synapse as a SOAP intermediary and I want to introduce a username token in the soap message which comes out of synapse.
The token must look like

xmlns:oas="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
<oas:Security>
<oas:UsernameToken>
<oas:Username>admin</oas:Username>
<oas:Password>admin123</oas:Password>
</oas:UsernameToken>
</oas:Security>

Could you please tell me how I must proceed with synapse?

Regards,
Sabareeswar
+91 80 668 82267

Re: Antwort: Re: Antwort: Re: Antwort: Re: Connection timeout problem

2009-10-26T07:14:58Z

Hi Ralph / Supun
> For future versions of Synapse it would be desirable that synapse gets the ability to respond with "100 Continue" responses. This would prevent interoperability issues with older .net clients like this.
>
> Asankha provided us with a quick fix; perhaps it would be possible that his fix flows into the Synapse trunk?
>
I've committed the fix against SYNAPSE-231

cheers
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com

Antwort: Re: Antwort: Re: Antwort: Re: Connection timeout problem

2009-10-26T01:40:37Z

Hi Suprun,

yes, we have a solution for this.

Our analysis showed that the timeouts were due to a misbehaviour of our
.net service client.
The client is sending a "100-continue" HTTP header and waits infinitely
for a "100 Continue" response before sending the request body, resulting
in timeouts.
This behaviour is not according to HTTP 1.1 spec, though.

Synapse by now is not responding to 100-continue headers and waits for the
client to send the request body (according to HTTP 1.1).

For future versions of Synapse it would be desirable that synapse gets the
ability to respond with "100 Continue" responses.
This would prevent interoperability issues with older .net clients like
this.

Asankha provided us with a quick fix; perhaps it would be possible that
his fix flows into the Synapse trunk?

Thank you and cheers!

i. A. Ralph Henze
Dipl.-Informatiker (Univ.)
Sparda-Datenverarbeitung eG
AE-ABS/Softwarearchitektur

Supun Kamburugamuva <supun06@...> schrieb am 26.10.2009 05:04:58:

> [Bild entfernt]
>
> Re: Antwort: Re: Antwort: Re: Connection timeout problem
>
> Supun Kamburugamuva
>
> an:
>
> user
>
> 26.10.2009 05:05
>
> [Bild entfernt]
>
> Von:
>
> Supun Kamburugamuva <supun06@...>
>
> An:
>
> user@...
>
> Bitte Antwort an user@...
>
> Hi Ralph,
>
> Did you get a solution to this problem?
>
> Thanks,
> Supun..
>
> On Thu, Sep 3, 2009 at 1:13 AM, Asankha C. Perera

<asankha@...>wrote:
>
> > Hi Ralph
> > > The GET /soap/ requests are those issued by the monitoring system.
The
> > > monitoring assumes that the esb is available if the list of services
is
> > > retrieved or there is a problem/outage otherwise.
> > >
> > Typically it would be better to issue a real call through Synapse
itself
> > for monitoring purposes. I think Eric might be able to tell you more
> > about the monitoring etc they do in their deployment environment.
> > > In our infrastructure there is an Apache HTTP server that is placed
in
> > > front of synapse, so that the tcp connection client from synapse's
> > > perspective is always the HTTP server. The HTTP server terminates
SSL
> > > connections and connects to synapse via mod_proxy. Do you presume
that a
> > > possible solution lies in HTTP server configuration?
> > >
> > >
> > >> It seems like you issue a GET /soap/ request? I also saw many of
those..
> > >> what is the purpose of issuing that? Anyway.. this seems like a
harmless
> > >> possible bug - where the connection gets timedout - but Synapse
thinks
> > >> its response was not fully read by the client. This could happen if
the
> > >> client just looks at the header of the response, and does not read
the
> > >> entity body - which will prevent the HTTP connection from being
re-used
> > >> again (i.e. as a keepalive) - however, I also suspect a slight bug
in
> > >> the code where this message could be dumped in a harmless case. Do
you
> > >> see an actual error at the client side?
> > >>
> > >
> > > Yes, there is an effect at the service client side. About 10 percent
of
> > > client requests are responded with HTTP error code 502.
> > Synapse does not return 502.. so this is returned by Apache.. but the
> > reason behind would need some investigation.. If you could re-create
> > this with a single request and get me a tcpdump it would be great
> > > I'm not sure of
> > > how that behaviour relates to the timeout message, because there are
a
> > lot
> > > more timeout messages in the log than actual client errors. But we
didn't
> > > have that when we were on synapse 1.2. But as stated earlier,
synapse 1.2
> > > freezed up to 3 times a day and had to be restarted, which we assume
is a
> > > consequence of bug SYNAPSE-404.
> > >
> > > Are you planning to prepare a fix?
> > >
> > Yes, I could fix the issue I suspect - but that would not solve the
502

> > issue.. what I noticed is that Synapse may report the "Connection
> > Timeout - before message body was fully read " message when the remote
> > party (i.e. client to synapse) terminated its socket - since that was
> > what was happening in your logs
> >
> > cheers
> > asankha
> >
> > --
> > Asankha C. Perera
> > AdroitLogic, http://adroitlogic.org
> >
> > http://esbmagic.blogspot.com
> >
> >
> >
> >
> >
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>

Re: Antwort: Re: Antwort: Re: Connection timeout problem

2009-10-25T21:04:58Z

Hi Ralph,

Did you get a solution to this problem?

Thanks,
Supun..

On Thu, Sep 3, 2009 at 1:13 AM, Asankha C. Perera <asankha@...>wrote:

> Hi Ralph
> > The GET /soap/ requests are those issued by the monitoring system. The
> > monitoring assumes that the esb is available if the list of services is
> > retrieved or there is a problem/outage otherwise.
> >
> Typically it would be better to issue a real call through Synapse itself
> for monitoring purposes. I think Eric might be able to tell you more
> about the monitoring etc they do in their deployment environment.
> > In our infrastructure there is an Apache HTTP server that is placed in
> > front of synapse, so that the tcp connection client from synapse's
> > perspective is always the HTTP server. The HTTP server terminates SSL
> > connections and connects to synapse via mod_proxy. Do you presume that a
> > possible solution lies in HTTP server configuration?
> >
> >
> >> It seems like you issue a GET /soap/ request? I also saw many of those..
> >> what is the purpose of issuing that? Anyway.. this seems like a harmless
> >> possible bug - where the connection gets timedout - but Synapse thinks
> >> its response was not fully read by the client. This could happen if the
> >> client just looks at the header of the response, and does not read the
> >> entity body - which will prevent the HTTP connection from being re-used
> >> again (i.e. as a keepalive) - however, I also suspect a slight bug in
> >> the code where this message could be dumped in a harmless case. Do you
> >> see an actual error at the client side?
> >>
> >
> > Yes, there is an effect at the service client side. About 10 percent of
> > client requests are responded with HTTP error code 502.
> Synapse does not return 502.. so this is returned by Apache.. but the
> reason behind would need some investigation.. If you could re-create
> this with a single request and get me a tcpdump it would be great
> > I'm not sure of
> > how that behaviour relates to the timeout message, because there are a
> lot
> > more timeout messages in the log than actual client errors. But we didn't
> > have that when we were on synapse 1.2. But as stated earlier, synapse 1.2
> > freezed up to 3 times a day and had to be restarted, which we assume is a
> > consequence of bug SYNAPSE-404.
> >
> > Are you planning to prepare a fix?
> >
> Yes, I could fix the issue I suspect - but that would not solve the 502
> issue.. what I noticed is that Synapse may report the "Connection
> Timeout - before message body was fully read " message when the remote
> party (i.e. client to synapse) terminated its socket - since that was
> what was happening in your logs
>
> cheers
> asankha
>
> --
> Asankha C. Perera
> AdroitLogic, http://adroitlogic.org
>
> http://esbmagic.blogspot.com
>
>
>
>
>

--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com

Re: Clone Mediator endpoint

2009-10-23T04:26:42Z

Thank you for your reply, unfortunately I had to switch to a more pressing
project, so it will be some time before I have a chance to test this.

Thank you,
Florin

2009/10/20 Ruwan Linton <ruwan.linton@...>

> Yes, Hiranya is correct on this...
>
> The clone mediator target mediates the message using the specified sequence
> and then send the message using the specified endpoint.
>
> So you shouldn't try to send the message in the target sequence.
>
> Thanks,
> Ruwan
>
> On Tue, Oct 20, 2009 at 7:40 PM, Hiranya Jayathilaka
> <hiranya911@...>wrote:
>
> > On Tue, Oct 20, 2009 at 1:41 PM, Florin Bejinaru
> > <florinbejinaru@...>wrote:
> >
> > > The Error I am getting is :
> > >
> > > 2009-10-20 00:33:50,308 [10.9.4.40-Florin-9Aug2009] [SynapseWorker-1]
> > ERROR
> > > ClientUtils The system cannot infer the transport information from the
> > > /services/Event URL.
> > > 2009-10-20 00:33:50,312 [10.9.4.40-Florin-9Aug2009] [SynapseWorker-1]
> > ERROR
> > > Axis2Sender Unexpected error during sending message out
> > > org.apache.axis2.AxisFault: The system cannot infer the transport
> > > information from the /services/Event URL.
> > >
> > > which I don't get if I set the "to" attribute on the target element.
> > >
> >
> > Looking at the source code of the CloneMediator and the Target class, I
> > can't see why this approach doesn't work. It should work without any
> > issues.
> > Here's the relevant code segment from the Taget class.
> >
> > *if (sequence != null) {
> > synCtx.getEnvironment().injectAsync(synCtx, sequence);
> > } else if (sequenceRef != null) {
> > SequenceMediator refSequence = (SequenceMediator)
> > synCtx.getSequence(sequenceRef);
> > if (refSequence != null) {
> > synCtx.getEnvironment().injectAsync(synCtx, refSequence);
> > }
> > } else if (endpoint != null) {
> > endpoint.send(synCtx);
> > } else if (endpointRef != null) {
> > Endpoint epr =
> > synCtx.getConfiguration().getEndpoint(endpointRef);
> > if (epr != null) {
> > epr.send(synCtx);
> > }
> > }*
> >
> > Can you please verify that Synapse doesn't send any messages to the
> > endpoint
> > you have specified? Note that when an endpoint is refered by the target
> it
> > tries to send the message to that endpoint. Therefore putting a send
> > mediator in the clone mediator target is not required and that could even
> > cause issues. May be the clone mediator actually sends messages to the
> > specified endpoint and what is failing is the send mediator which tries
> to
> > send the message to the 'To' address set in the message.
> >
> > Thanks,
> > Hiranya
> >
> >
> > --
> > Hiranya Jayathilaka
> > Software Engineer;
> > WSO2 Inc.; http://wso2.org
> > E-mail: hiranya@...; Mobile: +94 77 633 3491
> > Blog: http://techfeast-hiranya.blogspot.com
> >
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@...; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>