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@cancellara.biz] 
Sent: Wednesday, December 02, 2009 6:23 AM
To: user@synapse.apache.org
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

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

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.

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

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

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

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@newcastle.ac.uk>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@gmail.com] On
> >Behalf Of Asankha C. Perera
> >Sent: 12 November 2009 17:46
> >To: user@synapse.apache.org
> >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

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@gmail.com] On 
>Behalf Of Asankha C. Perera
>Sent: 12 November 2009 17:46
>To: user@synapse.apache.org
>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
>
>
>
>
>

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

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@gmail.com] On 
>Behalf Of Asankha C. Perera
>Sent: 12 November 2009 01:47
>To: user@synapse.apache.org
>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
>
>
>
>
>

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

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

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@spb.de> 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@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

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.

Thanks Asankha! Will refer the Rampart site.

Regards,
Sabareeswar
-----Original Message-----
From: Asankha Perera [mailto:asankha.apache@gmail.com] On Behalf Of Asankha C. Perera
Sent: Wednesday, October 28, 2009 6:13 PM
To: user@synapse.apache.org
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

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

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

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

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@gmail.com> 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@gmail.com>
> 
> An:
> 
> user@synapse.apache.org
> 
> Bitte Antwort an user@synapse.apache.org
> 
> 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@apache.org>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
> 

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@apache.org>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

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@gmail.com>

> 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@gmail.com>wrote:
>
> > On Tue, Oct 20, 2009 at 1:41 PM, Florin Bejinaru
> > <florinbejinaru@gmail.com>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@wso2.com;  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@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>

Thank you Paul. I wasn't aware that it was a WS-Security standard.

Essentially I want the oas:Security node to go inside the header. I am now trying to do it
with a policy document (which, btw, isn't working): am I going in the right direction?

\repository\conf\sample\resources\policy\ao_policy.xml
<wsp:Policy
   xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"
   xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
   xmlns:oas="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
   oas:Id="ao_policy" >
      <oas:Security>
         <oas:UsernameToken>
            <oas:Username>myusername</oas:Username>
            <oas:Password>mypassword</oas:Password>
         </oas:UsernameToken>
      </oas:Security>
</wsp:Policy>

<definitions xmlns="http://ws.apache.org/ns/synapse" xmlns:urn="urn:realops.com:amp:workflow">
<localEntry key="ao_policy" src="file:repository/conf/sample/resources/policy/ao_policy.xml"/>
    <sequence name="main" onError="fault">
        <in>
		<header name="urn:grid-name" value="SMECGRID"/>
            <send>
                <endpoint name="stockquote">
                    <address uri="http://localhost:5002/baocdp/ws/workflow"/>
			  <enableSec policy="ao_policy"/>
                </endpoint>
            </send>
        </in>
   </sequence>
</definitions>


Regards,
Sabareeswar
-----Original Message-----
From: Paul Fremantle [mailto:pzfreo@gmail.com] 
Sent: Friday, October 23, 2009 1:35 PM
To: user@synapse.apache.org
Subject: Re: Issues in using Custom Mediation

Sabareeswar

Hi.

I don't understand why you are using the callout mediator. Also
Synapse already supports adding security into outgoing flows using
WS-Policy. Is this standard WS-Security Username token you are adding?

Paul



On Fri, Oct 23, 2009 at 8:28 AM, Sabareeswar P. B.
<Sabareeswar_PB@infosys.com> wrote:
> Hi,
>
> We are using synapse between
> 1)       A web service client that was created from a wsdl that doesn't have any authentication
parameters.
> 2)       A web service provider that requires authentication.
>
> One of the requirements is to introduce a header element as per the requirements of the
service provider.
>
> I am using custom mediation in java to do this. The java class and the synapse.xml are
given below.
> The problem is that the Header changes that I do in the custom class are not appearing
in the Header that goes to the web service provider.
> In fact, the soap envelope to the web service provider doesn't have a soapHeader field
at all, though it appears properly when I try to log it within the java class.
>
> Could you please provide any pointers to this?
>
> public class AddHeaders extends AbstractMediator {
>    public boolean mediate(MessageContext mc) {
>            try {
>                        NamespaceImpl secns = new NamespaceImpl
>                        ("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd","oas");
>
>                        NamespaceImpl omns = new NamespaceImpl
>                        ("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd","oas");
>
>                        OMFactory sfactory = new DOMSOAPFactory();
>                        ElementImpl security = new ElementImpl(new DocumentImpl(sfactory),
"Security", omns, sfactory);
>                        ElementImpl usernameToken = new ElementImpl(security, "UsernameToken",
omns, sfactory);
>                        ElementImpl username = new ElementImpl(usernameToken, "Username",
omns, sfactory);
>                        username.setText("myusername");
>
>                        ElementImpl password = new ElementImpl(usernameToken, "Password",
omns, sfactory);
>                        password.setText("mypassword");
>
>                        mc.getEnvelope().getHeader().addChild(security);
>            }catch(Exception e){
>                        System.out.println("exp: " + e);
>            }
>            System.out.println("Logging the Header" + mc.getEnvelope().getHeader().toString());
>                        return true;
>    }
> }
>
>
> <definitions xmlns="http://ws.apache.org/ns/synapse">
>    <class name="samples.mediators.AddHeaders"/>
>    <callout serviceURL="http://localhost:5002/baocdp/ws/workflow"
>             action="execute-workflow">
>        <source xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
>                xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
>                            xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
>        <target xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
>                xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
>                xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
>    </callout>
>    <property name="RESPONSE" value="true"/>
> </definitions>
>
> Regards,
> Sabareeswar
>
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
> for the use of the addressee(s). If you are not the intended recipient, please
> notify the sender by e-mail and delete the original message. Further, you are not
> to copy, disclose, or distribute this e-mail or its contents to any other person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
> every reasonable precaution to minimize this risk, but is not liable for any damage
> you may sustain as a result of any virus in this e-mail. You should carry out your
> own virus checks before opening the e-mail or attachment. Infosys reserves the
> right to monitor and review the content of all messages sent to or from this e-mail
> address. Messages sent to or from this e-mail address may be stored on the
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
>



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

Sabareeswar

Hi.

I don't understand why you are using the callout mediator. Also
Synapse already supports adding security into outgoing flows using
WS-Policy. Is this standard WS-Security Username token you are adding?

Paul



On Fri, Oct 23, 2009 at 8:28 AM, Sabareeswar P. B.
<Sabareeswar_PB@infosys.com> wrote:
> Hi,
>
> We are using synapse between
> 1)       A web service client that was created from a wsdl that doesn't have any authentication
parameters.
> 2)       A web service provider that requires authentication.
>
> One of the requirements is to introduce a header element as per the requirements of the
service provider.
>
> I am using custom mediation in java to do this. The java class and the synapse.xml are
given below.
> The problem is that the Header changes that I do in the custom class are not appearing
in the Header that goes to the web service provider.
> In fact, the soap envelope to the web service provider doesn't have a soapHeader field
at all, though it appears properly when I try to log it within the java class.
>
> Could you please provide any pointers to this?
>
> public class AddHeaders extends AbstractMediator {
>    public boolean mediate(MessageContext mc) {
>            try {
>                        NamespaceImpl secns = new NamespaceImpl
>                        ("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd","oas");
>
>                        NamespaceImpl omns = new NamespaceImpl
>                        ("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd","oas");
>
>                        OMFactory sfactory = new DOMSOAPFactory();
>                        ElementImpl security = new ElementImpl(new DocumentImpl(sfactory),
"Security", omns, sfactory);
>                        ElementImpl usernameToken = new ElementImpl(security, "UsernameToken",
omns, sfactory);
>                        ElementImpl username = new ElementImpl(usernameToken, "Username",
omns, sfactory);
>                        username.setText("myusername");
>
>                        ElementImpl password = new ElementImpl(usernameToken, "Password",
omns, sfactory);
>                        password.setText("mypassword");
>
>                        mc.getEnvelope().getHeader().addChild(security);
>            }catch(Exception e){
>                        System.out.println("exp: " + e);
>            }
>            System.out.println("Logging the Header" + mc.getEnvelope().getHeader().toString());
>                        return true;
>    }
> }
>
>
> <definitions xmlns="http://ws.apache.org/ns/synapse">
>    <class name="samples.mediators.AddHeaders"/>
>    <callout serviceURL="http://localhost:5002/baocdp/ws/workflow"
>             action="execute-workflow">
>        <source xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
>                xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
>                            xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
>        <target xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
>                xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
>                xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
>    </callout>
>    <property name="RESPONSE" value="true"/>
> </definitions>
>
> Regards,
> Sabareeswar
>
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
> for the use of the addressee(s). If you are not the intended recipient, please
> notify the sender by e-mail and delete the original message. Further, you are not
> to copy, disclose, or distribute this e-mail or its contents to any other person and
> any such actions are unlawful. This e-mail may contain viruses. Infosys has taken
> every reasonable precaution to minimize this risk, but is not liable for any damage
> you may sustain as a result of any virus in this e-mail. You should carry out your
> own virus checks before opening the e-mail or attachment. Infosys reserves the
> right to monitor and review the content of all messages sent to or from this e-mail
> address. Messages sent to or from this e-mail address may be stored on the
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
>



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

Hi,

We are using synapse between
1)       A web service client that was created from a wsdl that doesn't have any authentication
parameters.
2)       A web service provider that requires authentication.

One of the requirements is to introduce a header element as per the requirements of the service
provider.

I am using custom mediation in java to do this. The java class and the synapse.xml are given
below.
The problem is that the Header changes that I do in the custom class are not appearing in
the Header that goes to the web service provider.
In fact, the soap envelope to the web service provider doesn't have a soapHeader field at
all, though it appears properly when I try to log it within the java class.

Could you please provide any pointers to this?

public class AddHeaders extends AbstractMediator {
    public boolean mediate(MessageContext mc) {
            try {
                        NamespaceImpl secns = new NamespaceImpl
                        ("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd","oas");

                        NamespaceImpl omns = new NamespaceImpl
                        ("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd","oas");

                        OMFactory sfactory = new DOMSOAPFactory();
                        ElementImpl security = new ElementImpl(new DocumentImpl(sfactory),
"Security", omns, sfactory);
                        ElementImpl usernameToken = new ElementImpl(security, "UsernameToken",
omns, sfactory);
                        ElementImpl username = new ElementImpl(usernameToken, "Username",
omns, sfactory);
                        username.setText("myusername");

                        ElementImpl password = new ElementImpl(usernameToken, "Password",
omns, sfactory);
                        password.setText("mypassword");

                        mc.getEnvelope().getHeader().addChild(security);
            }catch(Exception e){
                        System.out.println("exp: " + e);
            }
            System.out.println("Logging the Header" + mc.getEnvelope().getHeader().toString());
                        return true;
    }
}


<definitions xmlns="http://ws.apache.org/ns/synapse">
    <class name="samples.mediators.AddHeaders"/>
    <callout serviceURL="http://localhost:5002/baocdp/ws/workflow"
             action="execute-workflow">
        <source xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
                xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
                            xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
        <target xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
                xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
                xpath="s11:Body/child::*[fn:position()=1] | s12:Body/child::*[fn:position()=1]"/>
    </callout>
    <property name="RESPONSE" value="true"/>
</definitions>

Regards,
Sabareeswar


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Hi Sabareeswar
> Am not able to subscribe to the link - I think it is being blocked by the firewall.
>   
Ok, I've added you manually, so you should be able to post in future..
> And regarding the usage of an XML "value", the character entity (<) is not getting
translated to "<", though there is no problem with (&gt;).
>   
I meant to allow one to write as follows - similarly to how we allow
tasks to define XML properties [1]

<header name="urn:grid-name" value="SMECGRID" xmlns:urn="...."/>
<header name="urn:grid-name" value="SMECGRID" xmlns:urn="....">
       <oas:Security>
         <oas:UsernameToken>
            <oas:Username>admin</oas:Username>
            <oas:Password>admin123</oas:Password>
         </oas:UsernameToken>
      </oas:Security>
</header>

This way, any valid XML content can be specified easily and elegantly

cheers
asankha

[1] http://synapse.apache.org/Synapse_Configuration_Language.html#task

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

http://esbmagic.blogspot.com

Hi Sabareeswar

Please join [1] the user mailing list to receive future replies, else
your message goes into manual moderation.
> We are using synapse between
> 1)       A web service client that was created from a wsdl that doesn't have any authentication
parameters.
> 2)       A web service provider that requires authentication.
>
> One of the requirements is to introduce a header element as per the requirements of the
service provider.
> Is it possible to use the "header" tag in synapse to create a SOAP:Header element as
given below?
>   
Not currently.. however it would be possible if the header mediator was
extended to read an XML value instead of a String attribute.
>    <soapenv:Header>
>       <urn:grid-name>SMECGRID</urn:grid-name>
>       <oas:Security>
>          <oas:UsernameToken>
>             <oas:Username>admin</oas:Username>
>             <oas:Password>admin123</oas:Password>
>          </oas:UsernameToken>
>       </oas:Security>
>    </soapenv:Header>
>
> If not, is using Custom mediation in Java a good approach?
>   
Yes, that will be a workaround. If you could enhance the HeaderMediator
code itself, you could use it as well as share it back with the others

cheers
asankha

[1] http://synapse.apache.org/mail-lists.html

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

http://esbmagic.blogspot.com

Hi,

We are using synapse between
1)       A web service client that was created from a wsdl that doesn't have any authentication
parameters.
2)       A web service provider that requires authentication.

One of the requirements is to introduce a header element as per the requirements of the service
provider.
Is it possible to use the "header" tag in synapse to create a SOAP:Header element as given
below?
   <soapenv:Header>
      <urn:grid-name>SMECGRID</urn:grid-name>
      <oas:Security>
         <oas:UsernameToken>
            <oas:Username>admin</oas:Username>
            <oas:Password>admin123</oas:Password>
         </oas:UsernameToken>
      </oas:Security>
   </soapenv:Header>

If not, is using Custom mediation in Java a good approach?

Thanks

Regards,
Sabareeswar


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

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@gmail.com>wrote:

> On Tue, Oct 20, 2009 at 1:41 PM, Florin Bejinaru
> <florinbejinaru@gmail.com>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@wso2.com;  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@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com

On Tue, Oct 20, 2009 at 1:41 PM, Florin Bejinaru
<florinbejinaru@gmail.com>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@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com

An error occured while fetching this message, sorry !

Your approach seems to be correct and it should work, can you please attach
the error log that you are getting with this configuration?

Also do you have the registry declaration in the synapse.xml, I assume yes,
since you have other dynamic endpoints working. You may also attach the
synapse.xml configuration so that I can reproduce the issue if there are
any.

Thanks,
Ruwan

On Tue, Oct 20, 2009 at 2:54 AM, Florin Bejinaru
<florinbejinaru@gmail.com>wrote:

> I have to specify a "to" address of a clone mediator, but I need to do it
> dynamically so I thought that  :
> <clone>
>    <target endpoint="endpoint/dynamic_endpoint.xml">
>          <sequence>...
>
> should do the trick, but I am getting an exception when trying to <send />
> in the clone mediator, how can I set the endpoint of the clone mediator so
> that it points to an external endpoint file.
>
> I should also mention that I am using other <endpoint
> key="endpoint/other_dynamic_endpoint.xml"/> endpoints just fine so it's not
> the endpoints xml files.
>



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

I have to specify a "to" address of a clone mediator, but I need to do it
dynamically so I thought that  :
<clone>
    <target endpoint="endpoint/dynamic_endpoint.xml">
          <sequence>...

should do the trick, but I am getting an exception when trying to <send />
in the clone mediator, how can I set the endpoint of the clone mediator so
that it points to an external endpoint file.

I should also mention that I am using other <endpoint
key="endpoint/other_dynamic_endpoint.xml"/> endpoints just fine so it's not
the endpoints xml files.

Asankha,

Yes if services been started at least ones, there will be no problem,
There is also similar issue, If I supply wrong password for sftp polling
proxy, vfstransport will aggressively polls even if the proxy is off by
default.


Asankha C. Perera wrote:
> 
> This sounds like a problem with stopping and restarting the service with
> the WSO2 UI? .. for example, if you leave the service on as default - it
> works right?
> 

-- 
View this message in context: http://www.nabble.com/The-system-is-attempting-to-access-an-inactive-service-tp25885640p25902663.html
Sent from the Synapse - User mailing list archive at Nabble.com.

Hi Asankha,

Yes, it's version 1.2 within wso2 1.7.1.
We have a number of small projects together on one instance and used
integrated repository's xml files to store sequences and endpoints to keep
the synapse.xml smaller, and simplify and automate deployment process.

Cheers,
Dmitry


Asankha C. Perera wrote:
> 
> I've recently got to know about an issue with indirect endpoints by a
> production client against the original 1.2 release. Do you "require"
> indirect endpoints - or have you used it just because it seemed ok?
> 

-- 
View this message in context: http://www.nabble.com/Endpoint-becomes-indirect-and-do-not-switch-on-after-suspendDurationOnFailure-expires-tp25885867p25902612.html
Sent from the Synapse - User mailing list archive at Nabble.com.

Hi Dmitry
> Endpoint becomes indirect and do not switch on after suspendDurationOnFailure
> expires.
>
> WARN : IndirectEndpoint  - Endpoint : esb-event-dead-letter is currently
> inactive - invoking fault handler / assuming failure
>   
Again, I need to know the exact version you are reporting this against..
I've recently got to know about an issue with indirect endpoints by a
production client against the original 1.2 release. Do you "require"
indirect endpoints - or have you used it just because it seemed ok?

cheers
asankha

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

http://esbmagic.blogspot.com

Hi Dmitry
> After restarting WSO2, VFS transport hangs if listener proxy is off on
> startup. 
>   
Are you using the WSO2 version or Synapse? Can you let me know the
version of Synapse which is in use?
> That happens only when transport accesses an inactive proxy which never been
> started in the current session. If I start and then stop it, the problem
> goes away.
>   
This sounds like a problem with stopping and restarting the service with
the WSO2 UI? .. for example, if you leave the service on as default - it
works right?

cheers
asankha

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

http://esbmagic.blogspot.com

Endpoint becomes indirect and do not switch on after suspendDurationOnFailure
expires.

WARN : IndirectEndpoint  - Endpoint : esb-event-dead-letter is currently
inactive - invoking fault handler / assuming failure

I've set suspendDurationOnFailure to 60 so that after 1 min it should give
me an error, something like unable to sent because of bla bla, instead it
never becomes online again

Any ideas? 

Cheers

<syn:endpoint name="esb-event-retry"
xmlns:syn="http://ws.apache.org/ns/synapse">
	<syn:address
	
uri="jms:/esb_event_retry?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&amp;java.naming.provider.url=tcp://localhost:61616&amp;java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&amp;java.naming.security.principal=esb&amp;java.naming.security.credentials=xxxxxxxxxxx">
          <syn:timeout>
              <syn:duration>15</syn:duration>
              <syn:action>fault</syn:action>
          </syn:timeout>
          <syn:suspendDurationOnFailure>60</syn:suspendDurationOnFailure>
   </syn:address>
</syn:endpoint>
-- 
View this message in context: http://www.nabble.com/Endpoint-becomes-indirect-and-do-not-switch-on-after-suspendDurationOnFailure-expires-tp25885867p25885867.html
Sent from the Synapse - User mailing list archive at Nabble.com.

After restarting WSO2, VFS transport hangs if listener proxy is off on
startup. 

That happens only when transport accesses an inactive proxy which never been
started in the current session. If I start and then stop it, the problem
goes away.

Any ideas?

Thanks a lot,

2009-10-02 16:55:14,272 ERROR : VFSTransportListener - Error processing File
URI : sftp://esb:xxxxxxxx@xxxxxxpp2/home/ucmxfer/test/IN/dump.synapce84.csv
org.apache.axis2.AxisFault: The system is attempting to access an inactive
service: ccs-ucm-listener
at
org.apache.axis2.engine.AxisConfiguration.getService(AxisConfiguration.java:755)
at
org.apache.synapse.transport.vfs.VFSTransportListener.processFile(VFSTransportListener.java:404)
at
org.apache.synapse.transport.vfs.VFSTransportListener.scanFileOrDirectory(VFSTransportListener.java:241)
at
org.apache.synapse.transport.vfs.VFSTransportListener.onPoll(VFSTransportListener.java:145)
at
org.apache.synapse.transport.base.AbstractPollingTransportListener$1$1.run(AbstractPollingTransportListener.java:94)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619) 
-- 
View this message in context: http://www.nabble.com/The-system-is-attempting-to-access-an-inactive-service-tp25885640p25885640.html
Sent from the Synapse - User mailing list archive at Nabble.com.

There is a reason why vtd-xml is tagged as ESB, look at the link below and 
you will
see my point

http://ximpleware.wordpress.com/2009/08/19/some-independent-performance-test-result/
----- Original Message ----- 
From: "Asankha C. Perera" <asankha@apache.org>
To: <user@synapse.apache.org>; <crackeur@comcast.net>
Sent: Sunday, October 04, 2009 9:10 PM
Subject: Re: VTD-XML 2.7


> Hi Jimmy
>> VTD-XML 2.7 (http://vtd-xml.sf.net) is released and can be downloaded at
>>
> Is this released only under a GPL license? If so Synapse will not be
> able to make use of it.. Also I am curious as the project is tagged as
> "esb".. are there any other ESB implementations using it at present?
>
> cheers
> asankha
>
> -- 
> Asankha C. Perera
> AdroitLogic, http://adroitlogic.org
>
> http://esbmagic.blogspot.com
>
>
>
>
> 

Hi Jimmy
> VTD-XML 2.7 (http://vtd-xml.sf.net) is released and can be downloaded at
>   
Is this released only under a GPL license? If so Synapse will not be
able to make use of it.. Also I am curious as the project is tagged as
"esb".. are there any other ESB implementations using it at present?

cheers
asankha

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

http://esbmagic.blogspot.com