Nabble - WSO2 ESB Users

Re: How to use Axis client in a class mediator

2009-11-23T07:56:24Z

Arjan Visser wrote:
> Paul,
>
> Yes, that’s exactly what I need! Is this feature on the WSO2 ESB roadmap?
>
Yes, this will be available soon on the next release.

But, you could do this with a set of callout mediators even now. On a
side note do you need the response of the first iteration to go for the
next iteration?, I am trying to understand the requirement for the
serial iteration...

If the above is the case adding a single threaded thread pool will not
solve the problem, if it is not that I would like to know the
requirement to better support your exact requirement.

Thanks,
Ruwan

> Arjan
>
> -----Original Message-----
> From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...]
> On Behalf Of Paul Fremantle
> Sent: maandag 23 november 2009 13:44
> To: esb-java-user@...
> Subject: Re: [esb-java-user] How to use Axis client in a class mediator
>
> Rajika/Arjan
>
> Recently I discussed adding a thread-pool size to the iterate mediator
> for exactly this reason - the requirement to have only a single thread
> executing. Would that solve your problem?
>
> Paul
>
> 2009/11/23 Arjan Visser <arjan.visser@...>:
>
>> A callout mediator works for just 1 call. I need to do a number of calls
>>
> in
>
>> sequence. Also iterator does not work because it processes all calls in
>> parallel. What I need is a serial iterator.
>>
>>
>>
>> For every <article> in <articles> I need to do a SOAP call in sequence.
>>
> How
>
>> to implement this in the bus?
>>
>>
>>
>> <articles>
>>
>> <article>ID1</article>
>>
>> <article>ID2</article>
>>
>> <article>ID2</article>
>>
>> </articles>
>>
>>
>>
>>
>>
>>
>>
>> ________________________________
>>
>> From: esb-java-user-bounces@...
>>
> [mailto:esb-java-user-bounces@...]
>
>> On Behalf Of Rajika Kumarasiri
>> Sent: maandag 23 november 2009 12:53
>> To: esb-java-user@...
>> Subject: Re: [esb-java-user] How to use Axis client in a class mediator
>>
>>
>>
>>
>>
>> On Mon, Nov 23, 2009 at 3:49 PM, Arjan Visser <arjan.visser@...>
>> wrote:
>> Try using callout mediator.
>>
>> Rajika
>>
>> Hi,
>>
>>
>>
>> I have to use Axis2 client in a class mediator for calling an external
>> webservice. This call has to be a blocking call. When I use this client in
>> the class mediator, I get the following error:
>>
>>
>>
>> 2009-11-23 11:08:23,015 [-] [HttpClientWorker-8] ERROR AxisEngine Message
>> Receiver not found for AxisOperation: {http://ws.apach
>>
>> }anonOutInOp
>>
>> org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation:
>> {http://ws.apache.org/namespaces/axis2}anonOutInOp
>>
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:174)
>>
>> at
>> org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:229)
>>
>> at
>>
>>
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerP
> ool.java:58)
>
>> at
>>
>>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
> va:886)
>
>> at
>>
>>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
> 08)
>
>> at java.lang.Thread.run(Thread.java:619)
>>
>>
>>
>> What is the right way to use a blocking SOAP call in a mediator? Using the
>> same class mediator in a standalone Java projects works fine (using the
>> Axis2 libraries packed with WSO2).
>>
>>
>>
>> Used version : 2.1.2
>>
>>
>>
>> Arjan
>>
>> _______________________________________________
>> Esb-java-user mailing list
>> Esb-java-user@...
>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>>
>>
>> _______________________________________________
>> Esb-java-user mailing list
>> Esb-java-user@...
>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>>
>>
>
>
>
>

Re: How to use Axis client in a class mediator

2009-11-23T05:17:41Z

Paul,

Yes, thats exactly what I need! Is this feature on the WSO2 ESB roadmap?

Arjan

-----Original Message-----
From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...]
On Behalf Of Paul Fremantle
Sent: maandag 23 november 2009 13:44
To: esb-java-user@...
Subject: Re: [esb-java-user] How to use Axis client in a class mediator

Rajika/Arjan

Recently I discussed adding a thread-pool size to the iterate mediator
for exactly this reason - the requirement to have only a single thread
executing. Would that solve your problem?

Paul

2009/11/23 Arjan Visser <arjan.visser@...>:
> A callout mediator works for just 1 call. I need to do a number of calls
in
> sequence. Also iterator does not work because it processes all calls in
> parallel. What I need is a serial iterator.
>
>
>
> For every <article> in <articles> I need to do a SOAP call in sequence.
How

> to implement this in the bus?
>
>
>
> <articles>
>
> <article>ID1</article>
>
> <article>ID2</article>
>
> <article>ID2</article>
>
> </articles>
>
>
>
>
>
>
>
> ________________________________
>
> From: esb-java-user-bounces@...

[mailto:esb-java-user-bounces@...]

> On Behalf Of Rajika Kumarasiri
> Sent: maandag 23 november 2009 12:53
> To: esb-java-user@...
> Subject: Re: [esb-java-user] How to use Axis client in a class mediator
>
>
>
>
>
> On Mon, Nov 23, 2009 at 3:49 PM, Arjan Visser <arjan.visser@...>
> wrote:
> Try using callout mediator.
>
> Rajika
>
> Hi,
>
>
>
> I have to use Axis2 client in a class mediator for calling an external
> webservice. This call has to be a blocking call. When I use this client in
> the class mediator, I get the following error:
>
>
>
> 2009-11-23 11:08:23,015 [-] [HttpClientWorker-8] ERROR AxisEngine Message
> Receiver not found for AxisOperation: {http://ws.apach
>
> }anonOutInOp
>
> org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation:
> {http://ws.apache.org/namespaces/axis2}anonOutInOp
>
>         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:174)
>
>         at
> org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:229)
>
>         at
>

org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerP
ool.java:58)
>
> at
>
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:886)
>
> at
>
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
08)

>
> at java.lang.Thread.run(Thread.java:619)
>
>
>
> What is the right way to use a blocking SOAP call in a mediator? Using the
> same class mediator in a standalone Java projects works fine (using the
> Axis2 libraries packed with WSO2).
>
>
>
> Used version : 2.1.2
>
>
>
> Arjan
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>

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

Office: +44 844 484 8143
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
twitter.com/pzfreo
paul@...

WSO2 - a breath of fresh oxygen for enterprise middleware
http://wso2.com

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: How to use Axis client in a class mediator

2009-11-23T04:44:15Z

Rajika/Arjan

Recently I discussed adding a thread-pool size to the iterate mediator
for exactly this reason - the requirement to have only a single thread
executing. Would that solve your problem?

Paul

2009/11/23 Arjan Visser <arjan.visser@...>:

> A callout mediator works for just 1 call. I need to do a number of calls in
> sequence. Also iterator does not work because it processes all calls in
> parallel. What I need is a serial iterator.
>
>
>
> For every <article> in <articles> I need to do a SOAP call in sequence. How
> to implement this in the bus?
>
>
>
> <articles>
>
> <article>ID1</article>
>
> <article>ID2</article>
>
> <article>ID2</article>
>
> </articles>
>
>
>
>
>
>
>
> ________________________________
>
> From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...]
> On Behalf Of Rajika Kumarasiri
> Sent: maandag 23 november 2009 12:53
> To: esb-java-user@...
> Subject: Re: [esb-java-user] How to use Axis client in a class mediator
>
>
>
>
>
> On Mon, Nov 23, 2009 at 3:49 PM, Arjan Visser <arjan.visser@...>
> wrote:
> Try using callout mediator.
>
> Rajika
>
> Hi,
>
>
>
> I have to use Axis2 client in a class mediator for calling an external
> webservice. This call has to be a blocking call. When I use this client in
> the class mediator, I get the following error:
>
>
>
> 2009-11-23 11:08:23,015 [-] [HttpClientWorker-8] ERROR AxisEngine Message
> Receiver not found for AxisOperation: {http://ws.apach
>
> }anonOutInOp
>
> org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation:
> {http://ws.apache.org/namespaces/axis2}anonOutInOp
>
>         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:174)
>
>         at
> org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:229)
>
>         at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
>
>         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)
>
>
>
> What is the right way to use a blocking SOAP call in a mediator? Using the
> same class mediator in a standalone Java projects works fine (using the
> Axis2 libraries packed with WSO2).
>
>
>
> Used version : 2.1.2
>
>
>
> Arjan
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>

Re: How to use Axis client in a class mediator

2009-11-23T04:09:13Z

A callout mediator works for just 1 call. I need to do a number of calls in sequence. Also iterator does not work because it processes all calls in parallel. What I need is a serial iterator.

For every <article> in <articles> I need to do a SOAP call in sequence. How to implement this in the bus?

</articles>

From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...] On Behalf Of Rajika Kumarasiri
Sent: maandag 23 november 2009 12:53
To: esb-java-user@...
Subject: Re: [esb-java-user] How to use Axis client in a class mediator

On Mon, Nov 23, 2009 at 3:49 PM, Arjan Visser <arjan.visser@...> wrote:
Try using callout mediator.

Rajika

Hi,

I have to use Axis2 client in a class mediator for calling an external webservice. This call has to be a blocking call. When I use this client in the class mediator, I get the following error:

2009-11-23 11:08:23,015 [-] [HttpClientWorker-8] ERROR AxisEngine Message Receiver not found for AxisOperation: {http://ws.apach

}anonOutInOp

org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation: {http://ws.apache.org/namespaces/axis2}anonOutInOp

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:174)

at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:229)

at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)

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)

What is the right way to use a blocking SOAP call in a mediator? Using the same class mediator in a standalone Java projects works fine (using the Axis2 libraries packed with WSO2).

Used version : 2.1.2

Arjan

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: How to use Axis client in a class mediator

2009-11-23T03:53:02Z

On Mon, Nov 23, 2009 at 3:49 PM, Arjan Visser <arjan.visser@...> wrote:
Try using callout mediator.

Rajika

Hi,

I have to use Axis2 client in a class mediator for calling an external webservice. This call has to be a blocking call. When I use this client in the class mediator, I get the following error:

2009-11-23 11:08:23,015 [-] [HttpClientWorker-8] ERROR AxisEngine Message Receiver not found for AxisOperation: {http://ws.apach

}anonOutInOp

org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation: {http://ws.apache.org/namespaces/axis2}anonOutInOp

        at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:174)

        at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:229)

        at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)

        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)

What is the right way to use a blocking SOAP call in a mediator? Using the same class mediator in a standalone Java projects works fine (using the Axis2 libraries packed with WSO2).

Used version : 2.1.2

Arjan

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

How to use Axis client in a class mediator

2009-11-23T02:19:16Z

Hi,

I have to use Axis2 client in a class mediator for calling an external webservice. This call has to be a blocking call. When I use this client in the class mediator, I get the following error:

2009-11-23 11:08:23,015 [-] [HttpClientWorker-8] ERROR AxisEngine Message Receiver not found for AxisOperation: {http://ws.apach

}anonOutInOp

org.apache.axis2.AxisFault: Message Receiver not found for AxisOperation: {http://ws.apache.org/namespaces/axis2}anonOutInOp

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:174)

at org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:229)

at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)

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)

What is the right way to use a blocking SOAP call in a mediator? Using the same class mediator in a standalone Java projects works fine (using the Axis2 libraries packed with WSO2).

Used version : 2.1.2

Arjan

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: wsoesb wrapper.log clogs up disk.

2009-10-20T12:04:34Z

Seems like the ESB has received an unexpected response. Can you provide
any information on reproducing this, even though the ESB receives an
unexpected message it shouldn't loop in.

Thanks,
Ruwan

Arjan Visser wrote:

>
> Hi,
>
>
>
> We found that wso2esb filled up our complete harddisk with wrapper.log
> files. (6GB of logfiles)
>
>
>
> Many times a second the following log is found.
>
>
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | [2009-10-19 15:16:41,025]
> WARN - HttpCoreNIOListener System may be unstable: IOReactor
> encountered a r
>
> untime exception : null
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | java.lang.NullPointerException
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.synapse.transport.nhttp.ServerHandler.outputReady(ServerHandler.java:209)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.DefaultNHttpServerConnection.produceOutput(DefaultNHttpServerConnecti
>
> on.java:213)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.DefaultServerIOEventDispatch.outputReady(DefaultServerIOEventDispatch
>
> .java:151)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:177)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:317)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:294)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:256)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:96)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIO
>
> Reactor.java:556)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | at
> java.lang.Thread.run(Thread.java:619)
>
> INFO | jvm 1 | 2009/10/19 15:16:41 | [2009-10-19 15:16:41,025]
> WARN - HttpCoreNIOListener System may be unstable: IOReactor
> encountered a r
>
> untime exception : null
>
>
>
>
>
> Any idea what is going on here ?
>
>
>
>
>
> Version: wso2esb v2.1.1.
>
> * *
>
>
>
>
>
>
>
> * *
>
>
>
> Sun jdk: jdk1.6.0_11
>
>
>
> We never saw such issues with v1.7.1 (or 2.1.0)
>
>
>
>
>
>
>
> Regards,
>
> Arjan
>
> / /
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>

wsoesb wrapper.log clogs up disk.

2009-10-20T02:00:46Z

Hi,

We found that wso2esb filled up our complete harddisk with wrapper.log files. (6GB of logfiles)

Many times a second the following log is found.

INFO | jvm 1 | 2009/10/19 15:16:41 | [2009-10-19 15:16:41,025] WARN - HttpCoreNIOListener System may be unstable: IOReactor encountered a r

untime exception : null

INFO | jvm 1 | 2009/10/19 15:16:41 | java.lang.NullPointerException

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.synapse.transport.nhttp.ServerHandler.outputReady(ServerHandler.java:209)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.DefaultNHttpServerConnection.produceOutput(DefaultNHttpServerConnecti

on.java:213)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.DefaultServerIOEventDispatch.outputReady(DefaultServerIOEventDispatch

.java:151)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:177)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:317)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:294)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:256)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:96)

INFO | jvm 1 | 2009/10/19 15:16:41 | at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIO

Reactor.java:556)

INFO | jvm 1 | 2009/10/19 15:16:41 | at java.lang.Thread.run(Thread.java:619)

INFO | jvm 1 | 2009/10/19 15:16:41 | [2009-10-19 15:16:41,025] WARN - HttpCoreNIOListener System may be unstable: IOReactor encountered a r

untime exception : null

Any idea what is going on here ?

Version: wso2esb v2.1.1.
			Sun jdk: jdk1.6.0_11 We never saw such issues with v1.7.1 (or 2.1.0) Regards, Arjan

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: How to disable XKMS, GenericAJAXClient and wso2carbon-sts services

2009-10-12T06:41:14Z

On Mon, Oct 12, 2009 at 6:00 AM, Arjan Visser <arjan.visser@...> wrote:

hi Arjan,
Have a look at here[1].

-Rajika
[1] - http://wso2.org/mailarchive/carbon-dev/2009-October/037425.html

A fresh WSO2 ESB installation (version 2.1.0 and 2.1.1) always contains the XKMS, GenericAJAXClient and wso2carbon-sts services. Are they required? If not, is it possible to disable them permanent, also when the ESB restarts?

Arjan

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

--
http://wso2.org
http://llvm.org
http://www.minix3.org/

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

How to disable XKMS, GenericAJAXClient and wso2carbon-sts services

2009-10-12T06:00:04Z

A fresh WSO2 ESB installation (version 2.1.0 and 2.1.1) always contains the XKMS, GenericAJAXClient and wso2carbon-sts services. Are they required? If not, is it possible to disable them permanent, also when the ESB restarts?

Arjan

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

[Carbon-dev] WSO2 Enterprise Service Bus (ESB) 2.1.1 Released!

2009-10-09T18:39:25Z

The WSO2 Enterprise Service Bus (ESB) 2.1.1 Released!

The WSO2 ESB team is pleased to announce the release of version 2.1.1 of the Open Source Enterprise Service Bus (ESB). This is an enhanced and improved release of the WSO2 ESB 2.1.0 which went out on July 2009.

WSO2 ESB is a lightweight and easy-to-use Open Source Enterprise Service Bus (ESB) available under the Apache Software License v2.0. WSO2 ESB allows administrators to simply and easily configure message routing, intermediation, transformation, logging, task scheduling, load balancing, failover routing, event brokering, etc.. The runtime has been designed to be completely asynchronous, non-blocking and streaming based on the Apache Synapse core.

WSO2 ESB 2.1.1 is developed on top of the revolutionary Carbon platform (Middleware a' la carte), and is based on the OSGi framework to achieve the better modularity for your SOA architecture. This also contains a lots of new features and many other optional components to customize the behavior of the server. Further, if you do not want any of the built in features, you can uninstall those features without any trouble. In other words, this ESB can be customized to your SOA needs.

You can download this distribution from http://wso2.org/downloads/esb and give it a try.

How to Run

Extract the downloaded zip
Go to the bin directory in the extracted folder
Run the wso2server.sh or wso2server.bat as appropriate
Point your browser to the URL https://localhost:9443/carbon
Use "admin", "admin" as the username and password to login as an admin and create a user account
Assign the required permissions to the user through a role
If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script
Samples configurations can be started by the wso2esb-samples script passing the sample number with the -sn option, please have a look at the samples guide for more information, on running samples

Key Features of WSO2 ESB

Proxy services - facilitating synchronous/asynchronous transport, interface (WSDL/Schema/Policy), message format (SOAP 1.1/1.2, POX/REST, Text, Binary), QoS (WS-Addressing/WS-Security/WS-RM) and optimization switching (MTOM/SwA).
Non-blocking HTTP/S transports based on Apache HttpCore for ultrafast execution and support for thousands of connections at high concurreny with constant memory usage.
Built in Registry/Repository, facilitating dynamic updating and reloading of the configuration and associated resources (e.g. XSLTs, XSD, WSDL, Policies, JS, Configurations ..)
Easily extendable via custom Java class (mediator and command)/Spring mediators, or BSF Scripting languages (Javascript, Ruby, Groovy, etc.)
Built in support for scheduling tasks using the Quartz scheduler.
Load-balancing (with or without sticky sessions)/Fail-over, and clustered Throttling and Caching support
WS-Security, WS-Reliable Messaging, Caching & Throttling configurable via (message/operation/service level) WS-Policies
Lightweight, XML and Web services centric messaging model
Support for industrial standards (Hessian binary web service protocol/ Financial Information eXchange protocol and optional Helth Level-7 protocol)
Enhanced support for the VFS(File/FTP/SFTP)/JMS/Mail transports with optional TCP/UDP transports and transport switching for any of the above transports
Support for message splitting & aggregation using the EIP and service callouts
Database lookup & store support with DBMediators with reusable database connection pools
WS-Eventing support with event sources and event brokering
Rule based mediation of the messages using the Drools rule engine
Transactions support via the JMS transport and Transaction mediator for database mediators
Internationalized GUI management console with user/permission management for configuration development and monitoring support with statistics, configurable logging and tracing
JMX monitoring support and JMX management capabilities like, Gracefull/Forcefull shutdown/restart

New Features of the WSO2 ESB 2.1.1

This ESB release is based on the award winning WSO2 Carbon "Middleware a' la carte", an OSGi based SOA platform, version 2.0.1 by WSO2 Inc.
Rule based mediation via Drools
Fine grained autherization for services via the Entitlement mediator
Reliable-Messaging specification 1.1 support
Enhanced WS-Eventing support and Event Sources making it an even broker
Enhanced AJAX based sequence, endpoint and proxy service editors
Enhanced transport configuration management through the graphical console
Enhanced integrated registry and search functionalities with versionning, notifications, rating of resources, and commenting
Enhanced remote registry support
Default persistence to the registry for the configuration elements
Enhanced permission model with the user management
Enhanced REST/GET and other HTTP method support
P2 based OSGi feature support, for optional features like service management, runtime governance and so on..

Bug Fixes and Enhancements

Endpoint management issues in clustered environments have been fixed (CARBON-5108)
Defects in DBReport, DBLookup mediator UIs have been corrected (CARBON-5084)
Script mediator UI has been improved to handle some exceptional scenarios (CARBON-5080)
XQuery mediator UI has been enhanced to handle some exceptional scenarios (CARBON-5078)
ESB management console has been enhanced to work properly on WebLogic application server
UI enhancements to support WebSphere application server
Sequence management UI has undergone some minor enhancements
Enhancements to support front end - back end separation of the server
Reported issues related to transaction mediator have been fixed (CARBON-4225)
Issues releated to task creation and management have been rectified
Many documentation updates and enhancements

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List : esb-java-dev@... | esb-java-dev-request@... | Mail Archive
User List : esb-java-user@... | esb-java-user-request@... | Mail Archive

Reporting Issues

WSO2 encourages you to report issues and your enhancement requests for the WSO2 ESB using the public JIRA.

You can also watch how they are resolved, and comment on the progress..

Discussion Forums

Alternatively, questions could be raised using the forums available.

WSO2 ESB Forum : Discussion forum for WSO2 ESB developers/users

Training

WSO2 Inc. offers a variety of professional Training Programs, including training on general Web services as well as WSO2 ESB, Apache Synapse, Apache Axis2 and number of other products.

For additional support information please refer to http://wso2.com/training/course-catalog/

Support

WSO2 Inc. offers a variety of development and production support programs, ranging from Web-based support up through normal business hours, to premium 24x7 phone support.

For additional support information please refer to http://wso2.com/support/

For more information on WSO2 ESB, visit the WSO2 Oxygen Tank (http://wso2.org)

We welcome your feedback on this implementation. Thank you for your interest in WSO2 ESB.

-- The WSO2 ESB Team --

-- 
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://blog.ruwan.org

_______________________________________________
Carbon-dev mailing list
Carbon-dev@...
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL

2009-10-06T06:17:50Z

Cool, nice to hear you got it to work.

Thanks,
Ruwan

Arjan Visser wrote:

> Ruwan,
>
> Disabling the VFS transports solved the "Faulty Services". I think there is
> a caching problem, because in the Management Console UI, VFS was already
> disabled. I had first to add, and then to remove VFS again in order to
> disable VFS for the faulty services.
>
> Arjan
>
> -----Original Message-----
> From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...]
> On Behalf Of Ruwan Linton
> Sent: dinsdag 6 oktober 2009 11:44
> To: esb-java-user@...
> Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an
> xml parse error when parsing a WSDL
>
> Arjan Visser wrote:
>
>> Hi Ruwan,
>>
>> The CXF client is already configured to parse the wsdl with the full wsdl
>> path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However,
>> apparently the CXF client first parses
>> http://dev.boosttechhouse.com:8780/services/ (I don't know why...).
>> Using the CXF client connecting to a ESB 1.7 is working fine. The problem
>> occurred when I moved the "Foo" service to ESB 2.1.
>>
>>
> OK I think the way CXF parses the WSDL is wrong there is no need to
> parse the root context to parse the WSDL, it could be dangerous to do
> so. On the other hand we can fix this non-well-formed HTML on the
> services page.
>
>> Do you also know how to get rid of the "Faulty Services" XKMS and
>> wso2carbon-sts when VFS is enabled global? This creates for me a
>>
> workaround,
>
>> because the horizontal line will disappear if no "Faulty Services" are
>> detected.
>>
>>
> Yes, you need to go to service list and disable the VFS transport for
> all the services where you have not configured VFS properly.
>
> Go to Services > Service Dashboard (Foo) > Transports > disable VFS
>
> Thanks,
> Ruwan
>
>> Arjan
>>
>> -----Original Message-----
>> From: esb-java-user-bounces@...
>>
> [mailto:esb-java-user-bounces@...]
>
>> On Behalf Of Ruwan Linton
>> Sent: dinsdag 6 oktober 2009 11:05
>> To: esb-java-user@...
>> Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in
>>
> an
>
>> xml parse error when parsing a WSDL
>>
>> Hi Arjan,
>>
>> First of all this is not a WSDL that you are trying to parse, this is a
>> HTML page that is presented to the user containing the list of services
>> deployed on the server.
>>
>> If you want to get the WSDL of service Foo the WSDL path should be
>> http://dev.boosttechhouse.com:8780/services/Foo?wsdl
>>
>> In the mean time I will fix this HTML to be a welformed HTML.
>>
>> Thanks,
>> Ruwan
>>
>> Arjan Visser wrote:
>>
>>
>>> Using the Apache CXF 2.2.2 client results in an xml parse error when
>>> parsing a WSDL published by the ESB (version 2.1.0).
>>>
>>>
>>>
>>> Error message:
>>>
>>> Application has thrown exception, unwinding now
>>> javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
>>> Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.:
>>> org.xml.sax.SAXParseException: The element type "hr" must be
>>> terminated by the matching end-tag "</hr>".
>>>
>>>
>>>
>>> This is cause by a missing </hr> tag in the generated 'services' page
>>> (example http://dev.boosttechhouse.com:8780/services/).
>>>
>>>
>>>
>>> Code snippet from generated page:
>>>
>>> <hr><h2><font color="blue">Faulty Services</font></h2><h3><font
>>> color="blue">wso2carbon-sts</font></h3><h3><font
>>> color="blue">XKMS</font></h3>
>>>
>>>
>>>
>>> Is there a workaround for this problem? The reason of the "Faulty
>>> Services" section is because I enabled VFS transport globally and then
>>> the ESB complains: "Unable to configure the service XKMS for the VFS
>>> transport: The service has no configuration for the transport. This
>>> service is being marked as faulty and will not be available over the
>>> VFS transport."
>>>
>>> If I could manage to get rid of this warning, the "Faulty Services"
>>> section will disappear and parsing of the wsdl will be ok.
>>>
>>>
>>>
>>> Arjan
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Esb-java-user mailing list
>>> Esb-java-user@...
>>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>>
>>>
>>>
>>
>>
>
>
>

Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL

2009-10-06T04:38:04Z

Ruwan,

Disabling the VFS transports solved the "Faulty Services". I think there is
a caching problem, because in the Management Console UI, VFS was already
disabled. I had first to add, and then to remove VFS again in order to
disable VFS for the faulty services.

Arjan

-----Original Message-----
From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...]
On Behalf Of Ruwan Linton
Sent: dinsdag 6 oktober 2009 11:44
To: esb-java-user@...
Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an
xml parse error when parsing a WSDL

Arjan Visser wrote:
> Hi Ruwan,
>
> The CXF client is already configured to parse the wsdl with the full wsdl
> path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However,
> apparently the CXF client first parses
> http://dev.boosttechhouse.com:8780/services/ (I don't know why...).
> Using the CXF client connecting to a ESB 1.7 is working fine. The problem
> occurred when I moved the "Foo" service to ESB 2.1.
>
OK I think the way CXF parses the WSDL is wrong there is no need to
parse the root context to parse the WSDL, it could be dangerous to do
so. On the other hand we can fix this non-well-formed HTML on the
services page.
> Do you also know how to get rid of the "Faulty Services" XKMS and
> wso2carbon-sts when VFS is enabled global? This creates for me a
workaround,
> because the horizontal line will disappear if no "Faulty Services" are
> detected.
>
Yes, you need to go to service list and disable the VFS transport for
all the services where you have not configured VFS properly.

Go to Services > Service Dashboard (Foo) > Transports > disable VFS

Thanks,
Ruwan
> Arjan
>
> -----Original Message-----
> From: esb-java-user-bounces@...
[mailto:esb-java-user-bounces@...]
> On Behalf Of Ruwan Linton
> Sent: dinsdag 6 oktober 2009 11:05
> To: esb-java-user@...
> Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in
an

> xml parse error when parsing a WSDL
>
> Hi Arjan,
>
> First of all this is not a WSDL that you are trying to parse, this is a
> HTML page that is presented to the user containing the list of services
> deployed on the server.
>
> If you want to get the WSDL of service Foo the WSDL path should be
> http://dev.boosttechhouse.com:8780/services/Foo?wsdl
>
> In the mean time I will fix this HTML to be a welformed HTML.
>
> Thanks,
> Ruwan
>
> Arjan Visser wrote:
>
>> Using the Apache CXF 2.2.2 client results in an xml parse error when
>> parsing a WSDL published by the ESB (version 2.1.0).
>>
>>
>>
>> Error message:
>>
>> Application has thrown exception, unwinding now
>> javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
>> Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.:
>> org.xml.sax.SAXParseException: The element type "hr" must be
>> terminated by the matching end-tag "</hr>".
>>
>>
>>
>> This is cause by a missing </hr> tag in the generated 'services' page
>> (example http://dev.boosttechhouse.com:8780/services/).
>>
>>
>>
>> Code snippet from generated page:
>>
>> <hr><h2><font color="blue">Faulty Services</font></h2><h3><font
>> color="blue">wso2carbon-sts</font></h3><h3><font
>> color="blue">XKMS</font></h3>
>>
>>
>>
>> Is there a workaround for this problem? The reason of the "Faulty
>> Services" section is because I enabled VFS transport globally and then
>> the ESB complains: "Unable to configure the service XKMS for the VFS
>> transport: The service has no configuration for the transport. This
>> service is being marked as faulty and will not be available over the
>> VFS transport."
>>
>> If I could manage to get rid of this warning, the "Faulty Services"
>> section will disappear and parsing of the wsdl will be ok.
>>
>>
>>
>> Arjan
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Esb-java-user mailing list
>> Esb-java-user@...
>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>>
>
>
>

--
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://blog.ruwan.org

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL

2009-10-06T02:43:41Z

Arjan Visser wrote:
> Hi Ruwan,
>
> The CXF client is already configured to parse the wsdl with the full wsdl
> path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However,
> apparently the CXF client first parses
> http://dev.boosttechhouse.com:8780/services/ (I don't know why...).
> Using the CXF client connecting to a ESB 1.7 is working fine. The problem
> occurred when I moved the "Foo" service to ESB 2.1.
>
OK I think the way CXF parses the WSDL is wrong there is no need to
parse the root context to parse the WSDL, it could be dangerous to do
so. On the other hand we can fix this non-well-formed HTML on the
services page.
> Do you also know how to get rid of the "Faulty Services" XKMS and
> wso2carbon-sts when VFS is enabled global? This creates for me a workaround,
> because the horizontal line will disappear if no "Faulty Services" are
> detected.
>
Yes, you need to go to service list and disable the VFS transport for
all the services where you have not configured VFS properly.

Go to Services > Service Dashboard (Foo) > Transports > disable VFS

Thanks,
Ruwan

> Arjan
>
> -----Original Message-----
> From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...]
> On Behalf Of Ruwan Linton
> Sent: dinsdag 6 oktober 2009 11:05
> To: esb-java-user@...
> Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an
> xml parse error when parsing a WSDL
>
> Hi Arjan,
>
> First of all this is not a WSDL that you are trying to parse, this is a
> HTML page that is presented to the user containing the list of services
> deployed on the server.
>
> If you want to get the WSDL of service Foo the WSDL path should be
> http://dev.boosttechhouse.com:8780/services/Foo?wsdl
>
> In the mean time I will fix this HTML to be a welformed HTML.
>
> Thanks,
> Ruwan
>
> Arjan Visser wrote:
>
>> Using the Apache CXF 2.2.2 client results in an xml parse error when
>> parsing a WSDL published by the ESB (version 2.1.0).
>>
>>
>>
>> Error message:
>>
>> Application has thrown exception, unwinding now
>> javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
>> Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.:
>> org.xml.sax.SAXParseException: The element type "hr" must be
>> terminated by the matching end-tag "</hr>".
>>
>>
>>
>> This is cause by a missing </hr> tag in the generated 'services' page
>> (example http://dev.boosttechhouse.com:8780/services/).
>>
>>
>>
>> Code snippet from generated page:
>>
>> <hr><h2><font color="blue">Faulty Services</font></h2><h3><font
>> color="blue">wso2carbon-sts</font></h3><h3><font
>> color="blue">XKMS</font></h3>
>>
>>
>>
>> Is there a workaround for this problem? The reason of the "Faulty
>> Services" section is because I enabled VFS transport globally and then
>> the ESB complains: "Unable to configure the service XKMS for the VFS
>> transport: The service has no configuration for the transport. This
>> service is being marked as faulty and will not be available over the
>> VFS transport."
>>
>> If I could manage to get rid of this warning, the "Faulty Services"
>> section will disappear and parsing of the wsdl will be ok.
>>
>>
>>
>> Arjan
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Esb-java-user mailing list
>> Esb-java-user@...
>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>>
>
>
>

Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL

2009-10-06T02:26:54Z

Hi Ruwan,

The CXF client is already configured to parse the wsdl with the full wsdl
path, like http://dev.boosttechhouse.com:8780/services/Foo?wsdl. However,
apparently the CXF client first parses
http://dev.boosttechhouse.com:8780/services/ (I don't know why...).
Using the CXF client connecting to a ESB 1.7 is working fine. The problem
occurred when I moved the "Foo" service to ESB 2.1.

Do you also know how to get rid of the "Faulty Services" XKMS and
wso2carbon-sts when VFS is enabled global? This creates for me a workaround,
because the horizontal line will disappear if no "Faulty Services" are
detected.

Arjan

-----Original Message-----
From: esb-java-user-bounces@... [mailto:esb-java-user-bounces@...]
On Behalf Of Ruwan Linton
Sent: dinsdag 6 oktober 2009 11:05
To: esb-java-user@...
Subject: Re: [esb-java-user] Using the Apache CXF 2.2.2 client results in an
xml parse error when parsing a WSDL

Hi Arjan,

First of all this is not a WSDL that you are trying to parse, this is a
HTML page that is presented to the user containing the list of services
deployed on the server.

If you want to get the WSDL of service Foo the WSDL path should be
http://dev.boosttechhouse.com:8780/services/Foo?wsdl

In the mean time I will fix this HTML to be a welformed HTML.

Thanks,
Ruwan

Arjan Visser wrote:

>
> Using the Apache CXF 2.2.2 client results in an xml parse error when
> parsing a WSDL published by the ESB (version 2.1.0).
>
>
>
> Error message:
>
> Application has thrown exception, unwinding now
> javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR:
> Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.:
> org.xml.sax.SAXParseException: The element type "hr" must be
> terminated by the matching end-tag "</hr>".
>
>
>
> This is cause by a missing </hr> tag in the generated 'services' page
> (example http://dev.boosttechhouse.com:8780/services/).
>
>
>
> Code snippet from generated page:
>
> <hr><h2><font color="blue">Faulty Services</font></h2><h3><font
> color="blue">wso2carbon-sts</font></h3><h3><font
> color="blue">XKMS</font></h3>
>
>
>
> Is there a workaround for this problem? The reason of the "Faulty
> Services" section is because I enabled VFS transport globally and then
> the ESB complains: "Unable to configure the service XKMS for the VFS
> transport: The service has no configuration for the transport. This
> service is being marked as faulty and will not be available over the
> VFS transport."
>
> If I could manage to get rid of this warning, the "Faulty Services"
> section will disappear and parsing of the wsdl will be ok.
>
>
>
> Arjan
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>

Re: Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL

2009-10-06T02:05:17Z

Hi Arjan,

First of all this is not a WSDL that you are trying to parse, this is a
HTML page that is presented to the user containing the list of services
deployed on the server.

If you want to get the WSDL of service Foo the WSDL path should be
http://dev.boosttechhouse.com:8780/services/Foo?wsdl

In the mean time I will fix this HTML to be a welformed HTML.

Thanks,
Ruwan

Arjan Visser wrote:

Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL

2009-10-06T01:30:52Z

Using the Apache CXF 2.2.2 client results in an xml parse error when parsing a WSDL published by the ESB (version 2.1.0).

Error message:

Application has thrown exception, unwinding now javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'http://dev.boosttechhouse.com:8780/services/'.: org.xml.sax.SAXParseException: The element type "hr" must be terminated by the matching end-tag "</hr>".

This is cause by a missing </hr> tag in the generated 'services' page (example http://dev.boosttechhouse.com:8780/services/).

Code snippet from generated page:

<hr><h2><font color="blue">Faulty Services</font></h2><h3><font color="blue">wso2carbon-sts</font></h3><h3><font color="blue">XKMS</font></h3>

Is there a workaround for this problem? The reason of the "Faulty Services" section is because I enabled VFS transport globally and then the ESB complains: "Unable to configure the service XKMS for the VFS transport: The service has no configuration for the transport. This service is being marked as faulty and will not be available over the VFS transport."

If I could manage to get rid of this warning, the "Faulty Services" section will disappear and parsing of the wsdl will be ok.

Arjan

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: ensure unique vfs filename, access uuid from sequence

2009-09-15T09:46:52Z

Harm Verhagen wrote:
> Hi,
>
> to ensure the output filename of a vfs endpoint is unique I'd like to
> add the uuid to the filename.
> How can I access the messages uuid from a sequence?
Hi Harm,

You could easily get the message id using the get-property XPath
function as follows;

get-property('MessageID')

So the property mediator config will be;

<syn:property name="transport.vfs.ReplyFileName"
expression="fn:concat('B_',get-property('SYSTEM_DATE',
'yyyyMMdd_HHmmss_'),fn:substring(get-property('SYSTEM_TIME'),8,6),get-property('MessageID'),'.xml')"
scope="transport"/>

Thanks,
Ruwan

>
>
>
> I'm already able to add the current time including ms to the name, but
> for messages handled in parallel this still could give collisions.
> I the filename below I'd like to append the urn:uuid.
>
> <syn:property name="transport.vfs.ReplyFileName"
> expression="fn:concat('B_',get-property('SYSTEM_DATE',
> 'yyyyMMdd_HHmmss_'),fn:substring(get-property('SYSTEM_TIME'),8,6),'.xml')"
> scope="transport"/>
> <syn:send>
> <syn:endpoint>
> <syn:address uri="vfs:file:///home/incoming/inbox"
> format="pox"/>
> </syn:endpoint>
> </syn:send>
>
>
> Regards,
> Harm
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>

ensure unique vfs filename, access uuid from sequence

2009-09-15T06:35:11Z

Hi,

to ensure the output filename of a vfs endpoint is unique I'd like to add the uuid to the filename.
How can I access the messages uuid from a sequence?

I'm already able to add the current time including ms to the name, but for messages handled in parallel this still could give collisions.
I the filename below I'd like to append the urn:uuid.

<syn:property name="transport.vfs.ReplyFileName" expression="fn:concat('B_',get-property('SYSTEM_DATE', 'yyyyMMdd_HHmmss_'),fn:substring(get-property('SYSTEM_TIME'),8,6),'.xml')" scope="transport"/>
        <syn:send>
            <syn:endpoint>
                <syn:address uri="vfs:file:///home/incoming/inbox" format="pox"/>
            </syn:endpoint>
        </syn:send>

Regards,
Harm

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: tasks UI has issues

2009-09-10T22:38:15Z

Hi,

Yes, we have already reported these issues and the developers are
looking into them at the moment and they will be fixed in the next
release.

https://wso2.org/jira/browse/CARBON-5077
https://wso2.org/jira/browse/CARBON-4993

Thanks,
Evanthika

On Fri, Sep 11, 2009 at 7:15 AM, Ruwan Linton <ruwan@...> wrote:

> Hi Harm,
>
> We will have a look at it and get back to you on this. Seems like the
> issue is there and we will be fixing that for the 2.1.1 release which
> will be out in probably 2 weeks time.
>
> Thanks,
> Ruwan
>
> Harm Verhagen wrote:
>> Its even worse.
>> It seems that whenever one has a task, you. can _no longer_ edit
>> synapse.xml directly via the webui.
>> Hitting "Update" or "Save" always (without editing anything) gives:
>> Failed to save configuration. Error was: Unable to update the Synapse
>> configuration.Error starting up Scheduler : Error scheduling job :
>> JobDetail 'synapse.simple.quartz.testtask': jobClass:
>> 'org.apache.synapse.startup.quartz.SimpleQuartzJob isStateful: false
>> isVolatile: false isDurable: false requestsRecovers: false with
>> trigger Trigger
>> 'synapse.simple.quartz.testtask-trigger--7434854807021528161':
>> triggerClass: 'org.quartz.SimpleTrigger isVolatile: true calendar:
>> 'null' misfireInstruction: 0 nextFireTime: Thu Sep 10 15:46:57 CEST
>> 2009 Check log for more details
>>
>>
>> Can you confirm this ? (and do you have a workaround ?)
>>
>>
>> my synapse.xml snippet
>> <syn:task name="testtask" class="com.tst.CallSequence"
>> group="synapse.simple.quartz">
>> <syn:trigger interval="5"/>
>> <syn:property name="sequence" value="check_users"/>
>> <syn:property name="method" value="astring"/>
>> </syn:task>
>>
>>
>> Regards,
>> Harm
>>
>>
>> On Thu, Sep 10, 2009 at 3:09 PM, Harm Verhagen
>> <harm.verhagen@... <mailto:harm.verhagen@...>> wrote:
>> > I noticed that managing tasks via tha UI has serious issues.
>> >
>> > example:
>> > try to change the interval of an existing task
>> >
>> > result:
>> > you get errors about an already existing task. The task does not run
>> > with the updated inteval.
>> > and
>> > if you don't get any error, the modifications are not seen in
>> > Configure/synapse/Current configuration. Nor in the conf/synapse.xml
>> > (after hitting Save).
>> >
>> > Is this a known issue?
>> >
>> > version: wso2esb v2.1
>> >
>> > Regards,
>> > Harm
>> >
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Esb-java-user mailing list
>> Esb-java-user@...
>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>
>
> --
> 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://blog.ruwan.org
>
>
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: tasks UI has issues

2009-09-10T18:45:33Z

Hi Harm,

We will have a look at it and get back to you on this. Seems like the
issue is there and we will be fixing that for the 2.1.1 release which
will be out in probably 2 weeks time.

Thanks,
Ruwan

Harm Verhagen wrote:

> Its even worse.
> It seems that whenever one has a task, you. can _no longer_ edit
> synapse.xml directly via the webui.
> Hitting "Update" or "Save" always (without editing anything) gives:
> Failed to save configuration. Error was: Unable to update the Synapse
> configuration.Error starting up Scheduler : Error scheduling job :
> JobDetail 'synapse.simple.quartz.testtask': jobClass:
> 'org.apache.synapse.startup.quartz.SimpleQuartzJob isStateful: false
> isVolatile: false isDurable: false requestsRecovers: false with
> trigger Trigger
> 'synapse.simple.quartz.testtask-trigger--7434854807021528161':
> triggerClass: 'org.quartz.SimpleTrigger isVolatile: true calendar:
> 'null' misfireInstruction: 0 nextFireTime: Thu Sep 10 15:46:57 CEST
> 2009 Check log for more details
>
>
> Can you confirm this ? (and do you have a workaround ?)
>
>
> my synapse.xml snippet
> <syn:task name="testtask" class="com.tst.CallSequence"
> group="synapse.simple.quartz">
> <syn:trigger interval="5"/>
> <syn:property name="sequence" value="check_users"/>
> <syn:property name="method" value="astring"/>
> </syn:task>
>
>
> Regards,
> Harm
>
>
> On Thu, Sep 10, 2009 at 3:09 PM, Harm Verhagen
> <harm.verhagen@... <mailto:harm.verhagen@...>> wrote:
> > I noticed that managing tasks via tha UI has serious issues.
> >
> > example:
> > try to change the interval of an existing task
> >
> > result:
> > you get errors about an already existing task. The task does not run
> > with the updated inteval.
> > and
> > if you don't get any error, the modifications are not seen in
> > Configure/synapse/Current configuration. Nor in the conf/synapse.xml
> > (after hitting Save).
> >
> > Is this a known issue?
> >
> > version: wso2esb v2.1
> >
> > Regards,
> > Harm
> >
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>

Re: tasks UI has issues

2009-09-10T06:47:23Z

Its even worse.
It seems that whenever one has a task, you. can _no longer_ edit synapse.xml directly via the webui.
Hitting "Update" or "Save" always (without editing anything) gives:
Failed to save configuration. Error was: Unable to update the Synapse configuration.Error starting up Scheduler : Error scheduling job : JobDetail 'synapse.simple.quartz.testtask': jobClass: 'org.apache.synapse.startup.quartz.SimpleQuartzJob isStateful: false isVolatile: false isDurable: false requestsRecovers: false with trigger Trigger 'synapse.simple.quartz.testtask-trigger--7434854807021528161': triggerClass: 'org.quartz.SimpleTrigger isVolatile: true calendar: 'null' misfireInstruction: 0 nextFireTime: Thu Sep 10 15:46:57 CEST 2009 Check log for more details

Can you confirm this ? (and do you have a workaround ?)

my synapse.xml snippet
    <syn:task name="testtask" class="com.tst.CallSequence" group="synapse.simple.quartz">
        <syn:trigger interval="5"/>
        <syn:property name="sequence" value="check_users"/>
        <syn:property name="method" value="astring"/>
    </syn:task>

Regards,
Harm

On Thu, Sep 10, 2009 at 3:09 PM, Harm Verhagen <harm.verhagen@...> wrote:
> I noticed that managing tasks via tha UI has serious issues.
>
> example:
> try to change the interval of an existing task
>
> result:
> you get errors about an already existing task. The task does not run
> with the updated inteval.
> and
> if you don't get any error, the modifications are not seen in
> Configure/synapse/Current configuration. Nor in the conf/synapse.xml
> (after hitting Save).
>
> Is this a known issue?
>
> version: wso2esb v2.1
>
> Regards,
> Harm
>

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

tasks UI has issues

2009-09-10T06:09:15Z

I noticed that managing tasks via tha UI has serious issues.

example:
try to change the interval of an existing task

result:
you get errors about an already existing task. The task does not run
with the updated inteval.
and
if you don't get any error, the modifications are not seen in
Configure/synapse/Current configuration. Nor in the conf/synapse.xml
(after hitting Save).

Is this a known issue?

version: wso2esb v2.1

Regards,
Harm

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: faulting on a vfs handling sequence

2009-09-08T11:38:07Z

Harm Verhagen wrote:

> Ruwan wrote
>
>> I went through the code and realized that the mediation cannot trigger
>> any of those :-(, the fact that the transports are asynchronous makes it
>> bit hard to trigger the errors from the mediation to the transport
>> listener error flow. That is because the transport listener is operating
>> with a separate thread pool and gives the control to the worker pool
>> once it is read, and worker pool handles the mediation.
>>
> Thats unfortunate. I guess thats what typically would be expected from
> a file reader component.
>
>
>> Because of that the above configurations applies only for the transport
>> level failures (basically I/O errors when reading the file or any issues
>> related to loading the file into the environment)
>>
>>> Question: how to trigger the VFS to move a message. (After the VFS
>>> itself has successfully read the file) to the
>>> MoveAfterErrors|MoveAfterFailure folder.
>>>
>>>
>> There is no way at least for the moment, without some configuration to
>> do it at the configuration it self. For example you may setup an onError
>> sequence to send the file to location specified in the MoveAfterErrors
>> location by using a VFS endpoint.
>>
> Is there a way to access the actual filename beeing processed in a
> sequence? (then a custom mediator could do the file moving).
>

Yes you could write a custom mediator to do that and put the custom
mediator on the onError sequence, you could access the file name which
is being processing by using the following code fragment within a mediator;

String fileName = ((Map)
msgCtx.getProperty(MessageContext.TRANSPORT_HEADERS)).get(VFSConstants.FILE_NAME).toString();

Hope this will help you.

Thanks,
Ruwan
> Regards,
> Harm
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>

--
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://blog.ruwan.org

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: faulting on a vfs handling sequence

2009-09-08T08:09:04Z

Ruwan wrote
> I went through the code and realized that the mediation cannot trigger
> any of those :-(, the fact that the transports are asynchronous makes it
> bit hard to trigger the errors from the mediation to the transport
> listener error flow. That is because the transport listener is operating
> with a separate thread pool and gives the control to the worker pool
> once it is read, and worker pool handles the mediation.
Thats unfortunate. I guess thats what typically would be expected from
a file reader component.

> Because of that the above configurations applies only for the transport
> level failures (basically I/O errors when reading the file or any issues
> related to loading the file into the environment)
> > Question: how to trigger the VFS to move a message. (After the VFS
> > itself has successfully read the file) to the
> > MoveAfterErrors|MoveAfterFailure folder.
> >
> There is no way at least for the moment, without some configuration to
> do it at the configuration it self. For example you may setup an onError
> sequence to send the file to location specified in the MoveAfterErrors
> location by using a VFS endpoint.

Is there a way to access the actual filename beeing processed in a
sequence? (then a custom mediator could do the file moving).

Regards,
Harm

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: VFSTransportListener not obeying transport.PollInterval

2009-09-04T21:08:24Z

Harm Verhagen wrote:

> FYI,
>
> Maybe you already know this.. I report it just in case....
> The proxy caching problem is wider that just the timeout.
> Also deactivating vfs listener proxies doesn't work. (Home > Manage
>
>> Service > List > Service Group Dashboard > Service Dashboard ->
>>
> Deactiviate)
> The deactivated proxy keeps scanning and handling the files in the directory.
>

Yes, Harm... we are in the process of fixing that.

Thanks,
Ruwan

> esb version: 2.1
> Regards,
> Harm
>
>
> On Mon, Aug 31, 2009 at 11:47 PM, Harm Verhagen<harm.verhagen@...> wrote:
>
>> Yes that works around the problem.
>> Whenever I also change the name, the new polltime is taken into account.
>>
>> NB: After that whenever use a name that has been used before, it takes the
>> _old_ time again of when the name was first used.
>>
>> note: I modified time & name by editing the xml in UI -> Configure ->
>> synapse + hit update after modify.
>>
>>
>> Regards,
>> Harm
>>
>> On Mon, Aug 31, 2009 at 6:56 AM, Evanthika Amarasiri <evanthika@...>
>> wrote:
>>
>>> Hi Harm,
>>>
>>> The issue is not with the transport.PollInterval property. The issue is
>>> with Proxy Services. When you change the poll interval and let it execute,
>>> it will still read the poll interval specified previously since the Proxy
>>> services has a caching issue. If you need to let the Proxy Service read the
>>> new poll interval, you will have to change the name of the Proxy Service
>>> through 'Manage Synapse Configuration'. Could you please try this out and
>>> let us know whether it solves the issue?
>>>
>>> Thanks,
>>> Evanthika
>>>
>>> On Thu, Aug 27, 2009 at 8:17 PM, Harm Verhagen <harm.verhagen@...>
>>> wrote:
>>>
>>>> It seems esb is reading the timeout somewhere from an internal database
>>>> instead of from the synapse.xml.
>>>> Modifying synapse.xml directy in webui doesn't help, changing property in
>>>> proxy configuration doesnt help.
>>>>
>>>> both
>>>>
>>>> ./wso2server.bat -DuseSynapseXML
>>>>
>>>> ./wso2server.bat --cleanRegistry
>>>> dont work
>>>>
>>>> Any ideas ?
>>>>
>>>> Regards,
>>>> Harm
>>>>
>>>> On Thu, Aug 27, 2009 at 4:35 PM, Harm Verhagen <harm.verhagen@...>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I noticed that a proxy with vfs transport, does not obey the
>>>>> PollInterval. I set it to 8 here.
>>>>> It seems however that the files are processed every 30 seconds.
>>>>> restarting the bus doesn't help.
>>>>>
>>>>> I did not overrule the default vfs transport settings in the webUI, Just
>>>>> specified a proxy.
>>>>> I expect that any proxy specifiy settings should be used, right ?
>>>>>
>>>>>
>>>>> Is this a known issue ?
>>>>>
>>>>>
>>>>>
>>>>> synapse snippet
>>>>> <syn:proxy name="SCOFileReader" transports="vfs" startOnLoad="true"
>>>>> trace="enable">
>>>>> <syn:target inSequence="sco-input"/>
>>>>> <syn:parameter
>>>>> name="transport.vfs.MoveAfterErrors">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.ActionAfterProcess">MOVE</syn:parameter>
>>>>> <syn:parameter name="transport.PollInterval">8</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.FileURI">file:///c:/TESTPATH/Incoming/BTP_inbox</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.MoveAfterProcess">file:///c:/TESTPATH/Incoming/BTP_processed</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.MoveAfterFailure">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.ActionAfterErrors">MOVE</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.FileNamePattern">.*.xml</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.ContentType">application/xml</syn:parameter>
>>>>> <syn:parameter
>>>>> name="transport.vfs.ActionAfterFailure">MOVE</syn:parameter>
>>>>> </syn:proxy>
>>>>>
>>>>>
>>>>> With the following logs
>>>>> [2009-08-27 16:28:20,531] DEBUG - VFSTransportListener Scanning
>>>>> directory or file : file:///home/user/test/in
>>>>> [2009-08-27 16:28:34,765] DEBUG - VFSTransportListener Unable to access
>>>>> or read file or directory : file:///home/user/test/in
>>>>> [2009-08-27 16:28:35,703] DEBUG - VFSTransportListener Scanning
>>>>> directory or file : file:///c:/TESTPATH/Incoming/BTP_inbox
>>>>> [2009-08-27 16:28:49,765] DEBUG - VFSTransportListener Scanning
>>>>> directory or file : file:///home/user/test/in
>>>>> [2009-08-27 16:29:01,328] DEBUG - VFSTransportListener Unable to access
>>>>> or read file or directory : file:///home/user/test/in
>>>>> [2009-08-27 16:29:05,718] DEBUG - VFSTransportListener Scanning
>>>>> directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
>>>>> [2009-08-27 16:29:16,515] DEBUG - VFSTransportListener Scanning
>>>>> directory or file : file:///home/user/test/in
>>>>> [2009-08-27 16:29:28,015] DEBUG - VFSTransportListener Unable to access
>>>>> or read file or directory : file:///home/user/test/in
>>>>> [2009-08-27 16:29:35,718] DEBUG - VFSTransportListener Scanning
>>>>> directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
>>>>> [2009-08-27 16:29:43,031] DEBUG - VFSTransportListener Scanning
>>>>> directory or file : file:///home/user/test/in
>>>>>
>>>>> This shows every 30 seconds a scan of the directory.
>>>>> the "//home/user/test/in" seem to come from the default vfs settings
>>>>> (which I'm not using).
>>>>>
>>>>> version: wso2esb: 2.1 on java6, windows xp.
>>>>>
>>>>> Regards,
>>>>> Harm
>>>>>
>>>> _______________________________________________
>>>> Esb-java-user mailing list
>>>> Esb-java-user@...
>>>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>>>
>>>>
>>> _______________________________________________
>>> Esb-java-user mailing list
>>> Esb-java-user@...
>>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>>
>>>
>>
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>

Re: faulting on a vfs handling sequence

2009-09-04T21:03:16Z

Hi Harm,

Sorry for the delay in responding. I was busy with some other work.

See my comments below;

Harm Verhagen wrote:

>> Fault mediator make the message in hand s fault message, it doesn't
>> trigger a fault to the transport. You can try writing a custom mediator
>> and throwing a SynapseException at the mediate method. I am afraid there
>> is no way that you can fault a sequence in the standard configuration,
>> not sure whether that is good or not after looking at your requirement. :-)
>>
>>
>
> I tried writing a custom mediator :
> Unfortunately it doesn't work. Throwing a SynapseException does not
> trigger the VFS to move the file to the error folder.
> It still happyly moves my file to the transport.vfs.MoveAfterProcess.
>
> mediator snippet:
> public boolean mediate(MessageContext messageContext) {
> if (log.isDebugEnabled())
> log.debug("FaultMediator.mediate()");
>
> log.error("FaultMediator invoking fault, message = " + message + " ,
> message2 = ");
>
> throw new SynapseException("Faulting: " + message + ", " + message2);
> }
>
>
> I get the folling loggin.
> [2009-09-02 12:05:16,010] DEBUG - VFSTransportListener Processing file
> :file:///c:/dir/Incoming/inbox/S_USERDATA_20090713_093939_000008.xml
> [2009-09-02 12:05:16,026] INFO - LogMediator To: ,MessageID:
> urn:uuid:F9C82012783CAD548C1251885917857,Directi
> on: request
> [2009-09-02 12:05:16,041] ERROR - FaultMediator FaultMediator invoking
> fault, message = txt , message2 =
> [2009-09-02 12:05:16,041] DEBUG - VFSTransportListener Processed file
> : file:///c:/dir/Incoming/inbox/S_USERDATA_20090713_093939_000008.xml
> of Content-type : application/xml
> [2009-09-02 12:05:16,041] DEBUG - VFSTransportListener Moving to file
> :file:///c:/dir/Incoming/processed/S_USERDATA_20090713_093939_000008.xml
>
>
> Besides this problem, an exception not caused by a custom mediator,
> also doesn't make the VFS move the file to the
> transport.vfs.MoveAfterFailure|MoveAfterErrors directory.
> for example: when server in the URL of a call-out sequence is down,
> you get an exception (as expected). However the VFS still moves the
> file happily to the transport.vfs.MoveAfterProcess folder.
>

I went through the code and realized that the mediation cannot trigger
any of those :-(, the fact that the transports are asynchronous makes it
bit hard to trigger the errors from the mediation to the transport
listener error flow. That is because the transport listener is operating
with a separate thread pool and gives the control to the worker pool
once it is read, and worker pool handles the mediation.

Because of that the above configurations applies only for the transport
level failures (basically I/O errors when reading the file or any issues
related to loading the file into the environment)
> Question: how to trigger the VFS to move a message. (After the VFS
> itself has successfully read the file) to the
> MoveAfterErrors|MoveAfterFailure folder.
>
There is no way at least for the moment, without some configuration to
do it at the configuration it self. For example you may setup an onError
sequence to send the file to location specified in the MoveAfterErrors
location by using a VFS endpoint.
> side question: when will MoveAfterFailure be used, and when MoveAfterErrors ?
>
Well, MoveAfterErrors seem to be obsolete and not in use
MoveAfterFailure occurs when there is an file read/load errors.

Thanks,
Ruwan

>
> version: ESB v2.1
>
> Regards,
> Harm
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>
>

Re: v.2.1 custom mediator class loading problem

2009-09-02T09:03:37Z

Thanks Harm, for sharing this piece of information with all the users :-)

Ruwan

Harm Verhagen wrote:

> Ok,
> Let me answer this myself
>
> In case you have a plain jar (my case) you should put it in
> repository\components\mediators. [1]
> Even better is if you make it an osgi-bundle. [1,2]
>
> Regards,
> Harm
>
> ref:
> [1] http://supunk.blogspot.com/2009/07/writing-wso2-esb-mediator.html
> [2] http://wso2.org/forum/thread/5635
>
> On Wed, Sep 2, 2009 at 10:55 AM, Harm Verhagen
> <harm.verhagen@... <mailto:harm.verhagen@...>> wrote:
>
> Hi,
>
>
> I'm trying to load a custom mediator with esb v2.1 an i'm
> experiencing problems.
> (I can successfully do the same with v1.7, same jarfile, same
> synapse.xml snippet)
>
> I keep getting the following exception
> [2009-09-02 10:37:02,150] ERROR - ClassMediatorFactory Error :
> com.esb.mediators.FaultMediator
> java.lang.ClassNotFoundException: com.esb.mediators.FaultMediator
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
>
> synapse snippet.
> <syn:class name="com.esb.mediators.FaultMediator">
> <syn:property name="message" value="fault!"/>
> </syn:class>
>
> First I thought, I didn't put the jar in the correct place on disk....
> But thats not the problem. even when putting my jar in every
> directory within esb2.1 that contained jars I still get this error.
> I tried putting it next to every instance of
> org.wso2.esb.samples-2.1.0.jar
>
> The following sampling code works OK.org.wso2.esb.samples-2.1.0.jar
> <syn:class name="samples.mediators.DiscountQuoteMediator">
> <syn:property name="discountFactor" value="10"/>
> <syn:property name="bonusFor" value="5"/>
> </syn:class>
>
>
>
> What am I missing ? Do I need to register jar files somewhere
> first ? Instead of just putting them in a direcotry. (I did find
> some references to org.wso2.esb.samples-2.1.0.jar in a file
> called bundles.info <http://bundles.info>)
>
> Regards,
> Harm
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user@...
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>

Re: VFSTransportListener not obeying transport.PollInterval

2009-09-02T05:04:56Z

FYI,

Maybe you already know this.. I report it just in case....
The proxy caching problem is wider that just the timeout.
Also deactivating vfs listener proxies doesn't work. (Home > Manage
> Service > List > Service Group Dashboard > Service Dashboard ->
Deactiviate)
The deactivated proxy keeps scanning and handling the files in the directory.

esb version: 2.1
Regards,
Harm

On Mon, Aug 31, 2009 at 11:47 PM, Harm Verhagen<harm.verhagen@...> wrote:

> Yes that works around the problem.
> Whenever I also change the name, the new polltime is taken into account.
>
> NB: After that whenever use a name that has been used before, it takes the
> _old_ time again of when the name was first used.
>
> note: I modified time & name by editing the xml in UI -> Configure ->
> synapse + hit update after modify.
>
>
> Regards,
> Harm
>
> On Mon, Aug 31, 2009 at 6:56 AM, Evanthika Amarasiri <evanthika@...>
> wrote:
>>
>> Hi Harm,
>>
>> The issue is not with the transport.PollInterval property. The issue is
>> with Proxy Services. When you change the poll interval and let it execute,
>> it will still read the poll interval specified previously since the Proxy
>> services has a caching issue. If you need to let the Proxy Service read the
>> new poll interval, you will have to change the name of the Proxy Service
>> through 'Manage Synapse Configuration'. Could you please try this out and
>> let us know whether it solves the issue?
>>
>> Thanks,
>> Evanthika
>>
>> On Thu, Aug 27, 2009 at 8:17 PM, Harm Verhagen <harm.verhagen@...>
>> wrote:
>>>
>>> It seems esb is reading the timeout somewhere from an internal database
>>> instead of from the synapse.xml.
>>> Modifying synapse.xml directy in webui doesn't help, changing property in
>>> proxy configuration doesnt help.
>>>
>>> both
>>>
>>> ./wso2server.bat -DuseSynapseXML
>>>
>>> ./wso2server.bat --cleanRegistry
>>> dont work
>>>
>>> Any ideas ?
>>>
>>> Regards,
>>> Harm
>>>
>>> On Thu, Aug 27, 2009 at 4:35 PM, Harm Verhagen <harm.verhagen@...>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I noticed that a proxy with vfs transport, does not obey the
>>>> PollInterval. I set it to 8 here.
>>>> It seems however that the files are processed every 30 seconds.
>>>> restarting the bus doesn't help.
>>>>
>>>> I did not overrule the default vfs transport settings in the webUI, Just
>>>> specified a proxy.
>>>> I expect that any proxy specifiy settings should be used, right ?
>>>>
>>>>
>>>> Is this a known issue ?
>>>>
>>>>
>>>>
>>>> synapse snippet
>>>>     <syn:proxy name="SCOFileReader" transports="vfs" startOnLoad="true"
>>>> trace="enable">
>>>>         <syn:target inSequence="sco-input"/>
>>>>         <syn:parameter
>>>> name="transport.vfs.MoveAfterErrors">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.ActionAfterProcess">MOVE</syn:parameter>
>>>>         <syn:parameter name="transport.PollInterval">8</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.FileURI">file:///c:/TESTPATH/Incoming/BTP_inbox</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.MoveAfterProcess">file:///c:/TESTPATH/Incoming/BTP_processed</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.MoveAfterFailure">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.ActionAfterErrors">MOVE</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.FileNamePattern">.*.xml</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.ContentType">application/xml</syn:parameter>
>>>>         <syn:parameter
>>>> name="transport.vfs.ActionAfterFailure">MOVE</syn:parameter>
>>>>     </syn:proxy>
>>>>
>>>>
>>>> With the following logs
>>>> [2009-08-27 16:28:20,531] DEBUG - VFSTransportListener Scanning
>>>> directory or file : file:///home/user/test/in
>>>> [2009-08-27 16:28:34,765] DEBUG - VFSTransportListener Unable to access
>>>> or read file or directory : file:///home/user/test/in
>>>> [2009-08-27 16:28:35,703] DEBUG - VFSTransportListener Scanning
>>>> directory or file : file:///c:/TESTPATH/Incoming/BTP_inbox
>>>> [2009-08-27 16:28:49,765] DEBUG - VFSTransportListener Scanning
>>>> directory or file : file:///home/user/test/in
>>>> [2009-08-27 16:29:01,328] DEBUG - VFSTransportListener Unable to access
>>>> or read file or directory : file:///home/user/test/in
>>>> [2009-08-27 16:29:05,718] DEBUG - VFSTransportListener Scanning
>>>> directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
>>>> [2009-08-27 16:29:16,515] DEBUG - VFSTransportListener Scanning
>>>> directory or file : file:///home/user/test/in
>>>> [2009-08-27 16:29:28,015] DEBUG - VFSTransportListener Unable to access
>>>> or read file or directory : file:///home/user/test/in
>>>> [2009-08-27 16:29:35,718] DEBUG - VFSTransportListener Scanning
>>>> directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
>>>> [2009-08-27 16:29:43,031] DEBUG - VFSTransportListener Scanning
>>>> directory or file : file:///home/user/test/in
>>>>
>>>> This shows every 30 seconds a scan of the directory.
>>>> the "//home/user/test/in" seem to come from the default vfs settings
>>>> (which I'm not using).
>>>>
>>>> version: wso2esb: 2.1 on java6, windows xp.
>>>>
>>>> Regards,
>>>> Harm
>>>
>>>
>>> _______________________________________________
>>> Esb-java-user mailing list
>>> Esb-java-user@...
>>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>>
>>
>>
>> _______________________________________________
>> Esb-java-user mailing list
>> Esb-java-user@...
>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>
>

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: faulting on a vfs handling sequence

2009-09-02T03:04:27Z

> Fault mediator make the message in hand s fault message, it doesn't
> trigger a fault to the transport. You can try writing a custom mediator
> and throwing a SynapseException at the mediate method. I am afraid there
> is no way that you can fault a sequence in the standard configuration,
> not sure whether that is good or not after looking at your requirement. :-)
>

I tried writing a custom mediator :
Unfortunately it doesn't work. Throwing a SynapseException does not
trigger the VFS to move the file to the error folder.
It still happyly moves my file to the transport.vfs.MoveAfterProcess.

mediator snippet:
public boolean mediate(MessageContext messageContext) {
if (log.isDebugEnabled())
log.debug("FaultMediator.mediate()");

log.error("FaultMediator invoking fault, message = " + message + " ,
message2 = ");

throw new SynapseException("Faulting: " + message + ", " + message2);
}

I get the folling loggin.
[2009-09-02 12:05:16,010] DEBUG - VFSTransportListener Processing file
:file:///c:/dir/Incoming/inbox/S_USERDATA_20090713_093939_000008.xml
[2009-09-02 12:05:16,026] INFO - LogMediator To: ,MessageID:
urn:uuid:F9C82012783CAD548C1251885917857,Directi
on: request
[2009-09-02 12:05:16,041] ERROR - FaultMediator FaultMediator invoking
fault, message = txt , message2 =
[2009-09-02 12:05:16,041] DEBUG - VFSTransportListener Processed file
: file:///c:/dir/Incoming/inbox/S_USERDATA_20090713_093939_000008.xml
of Content-type : application/xml
[2009-09-02 12:05:16,041] DEBUG - VFSTransportListener Moving to file
:file:///c:/dir/Incoming/processed/S_USERDATA_20090713_093939_000008.xml

Besides this problem, an exception not caused by a custom mediator,
also doesn't make the VFS move the file to the
transport.vfs.MoveAfterFailure|MoveAfterErrors directory.
for example: when server in the URL of a call-out sequence is down,
you get an exception (as expected). However the VFS still moves the
file happily to the transport.vfs.MoveAfterProcess folder.

Question: how to trigger the VFS to move a message. (After the VFS
itself has successfully read the file) to the
MoveAfterErrors|MoveAfterFailure folder.
side question: when will MoveAfterFailure be used, and when MoveAfterErrors ?

version: ESB v2.1

Regards,
Harm

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: v.2.1 custom mediator class loading problem

2009-09-02T02:10:19Z

Ok,
Let me answer this myself

In case you have a plain jar (my case) you should put it in repository\components\mediators. [1]
Even better is if you make it an osgi-bundle. [1,2]

Regards,
Harm

ref:
[1] http://supunk.blogspot.com/2009/07/writing-wso2-esb-mediator.html
[2] http://wso2.org/forum/thread/5635

On Wed, Sep 2, 2009 at 10:55 AM, Harm Verhagen <harm.verhagen@...> wrote:

Hi,

I'm trying to load a custom mediator with esb v2.1 an i'm experiencing problems.
(I can successfully do the same with v1.7, same jarfile, same synapse.xml snippet)

I keep getting the following exception
[2009-09-02 10:37:02,150] ERROR - ClassMediatorFactory Error : com.esb.mediators.FaultMediator
java.lang.ClassNotFoundException: com.esb.mediators.FaultMediator
        at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)

synapse snippet.
<syn:class name="com.esb.mediators.FaultMediator">
            <syn:property name="message" value="fault!"/>
</syn:class>

First I thought, I didn't put the jar in the correct place on disk....
But thats not the problem. even when putting my jar in every directory within esb2.1 that contained jars I still get this error.
I tried putting it next to every instance of      org.wso2.esb.samples-2.1.0.jar

The following sampling code works OK.org.wso2.esb.samples-2.1.0.jar
<syn:class name="samples.mediators.DiscountQuoteMediator">
                <syn:property name="discountFactor" value="10"/>
                <syn:property name="bonusFor" value="5"/>
</syn:class>

What am I missing ? Do I need to register jar files somewhere first ? Instead of just putting them in a direcotry. (I did find some references to org.wso2.esb.samples-2.1.0.jar in a file called bundles.info)

Regards,
Harm

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

v.2.1 custom mediator class loading problem

2009-09-02T01:55:53Z

Hi,

I'm trying to load a custom mediator with esb v2.1 an i'm experiencing problems.
(I can successfully do the same with v1.7, same jarfile, same synapse.xml snippet)

I keep getting the following exception
[2009-09-02 10:37:02,150] ERROR - ClassMediatorFactory Error : com.esb.mediators.FaultMediator
java.lang.ClassNotFoundException: com.esb.mediators.FaultMediator
        at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
        at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
        at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)

synapse snippet.
<syn:class name="com.esb.mediators.FaultMediator">
            <syn:property name="message" value="fault!"/>
</syn:class>

First I thought, I didn't put the jar in the correct place on disk....
But thats not the problem. even when putting my jar in every directory within esb2.1 that contained jars I still get this error.
I tried putting it next to every instance of      org.wso2.esb.samples-2.1.0.jar

The following sampling code works OK.org.wso2.esb.samples-2.1.0.jar
<syn:class name="samples.mediators.DiscountQuoteMediator">
                <syn:property name="discountFactor" value="10"/>
                <syn:property name="bonusFor" value="5"/>
</syn:class>

What am I missing ? Do I need to register jar files somewhere first ? Instead of just putting them in a direcotry. (I did find some references to org.wso2.esb.samples-2.1.0.jar in a file called bundles.info)

Regards,
Harm

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: VFSTransportListener not obeying transport.PollInterval

2009-08-31T14:47:53Z

Yes that works around the problem.
Whenever I also change the name, the new polltime is taken into account.

NB: After that whenever use a name that has been used before, it takes the _old_ time again of when the name was first used.

note: I modified time & name by editing the xml in UI -> Configure -> synapse + hit update after modify.

Regards,
Harm

On Mon, Aug 31, 2009 at 6:56 AM, Evanthika Amarasiri <evanthika@...> wrote:

Hi Harm,

The issue is not with the transport.PollInterval property. The issue is with Proxy Services. When you change the poll interval and let it execute, it will still read the poll interval specified previously since the Proxy services has a caching issue. If you need to let the Proxy Service read the new poll interval, you will have to change the name of the Proxy Service through 'Manage Synapse Configuration'. Could you please try this out and let us know whether it solves the issue?

Thanks,
Evanthika
On Thu, Aug 27, 2009 at 8:17 PM, Harm Verhagen <harm.verhagen@...> wrote:
It seems esb is reading the timeout somewhere from an internal database instead of from the synapse.xml.
Modifying synapse.xml directy in webui doesn't help, changing property in proxy configuration doesnt help.

both
./wso2server.bat -DuseSynapseXML
./wso2server.bat --cleanRegistry
dont work
Any ideas ?

Regards,
Harm

On Thu, Aug 27, 2009 at 4:35 PM, Harm Verhagen <harm.verhagen@...> wrote:

Hi,

I noticed that a proxy with vfs transport, does not obey the PollInterval. I set it to 8 here.
It seems however that the files are processed every 30 seconds.
restarting the bus doesn't help.

I did not overrule the default vfs transport settings in the webUI, Just specified a proxy.
I expect that any proxy specifiy settings should be used, right ?

Is this a known issue ?

synapse snippet
    <syn:proxy name="SCOFileReader" transports="vfs" startOnLoad="true" trace="enable">
        <syn:target inSequence="sco-input"/>
        <syn:parameter name="transport.vfs.MoveAfterErrors">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterProcess">MOVE</syn:parameter>
        <syn:parameter name="transport.PollInterval">8</syn:parameter>
        <syn:parameter name="transport.vfs.FileURI">file:///c:/TESTPATH/Incoming/BTP_inbox</syn:parameter>
        <syn:parameter name="transport.vfs.MoveAfterProcess">file:///c:/TESTPATH/Incoming/BTP_processed</syn:parameter>
        <syn:parameter name="transport.vfs.MoveAfterFailure">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterErrors">MOVE</syn:parameter>
        <syn:parameter name="transport.vfs.FileNamePattern">.*.xml</syn:parameter>
        <syn:parameter name="transport.vfs.ContentType">application/xml</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterFailure">MOVE</syn:parameter>
    </syn:proxy>

With the following logs
[2009-08-27 16:28:20,531] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:28:34,765] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:28:35,703] DEBUG - VFSTransportListener Scanning directory or file : file:///c:/TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:28:49,765] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:29:01,328] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:29:05,718] DEBUG - VFSTransportListener Scanning directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:29:16,515] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:29:28,015] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:29:35,718] DEBUG - VFSTransportListener Scanning directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:29:43,031] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in

This shows every 30 seconds a scan of the directory.
the "//home/user/test/in" seem to come from the default vfs settings (which I'm not using).

version: wso2esb: 2.1 on java6, windows xp.

Regards,
Harm
_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: VFSTransportListener not obeying transport.PollInterval

2009-08-30T22:34:27Z

Hi Harm,

As another workaround you can change the poll interval, save the configuration to the synapse.xml on the file system (Through Manage Synapse Configuration) and start the server with wso2server.bat -DuseSynapseXML.

Thanks,
Evanthika

On Mon, Aug 31, 2009 at 10:26 AM, Evanthika Amarasiri <evanthika@...> wrote:

Hi Harm,

The issue is not with the transport.PollInterval property. The issue is with Proxy Services. When you change the poll interval and let it execute, it will still read the poll interval specified previously since the Proxy services has a caching issue. If you need to let the Proxy Service read the new poll interval, you will have to change the name of the Proxy Service through 'Manage Synapse Configuration'. Could you please try this out and let us know whether it solves the issue?

Thanks,
Evanthika
On Thu, Aug 27, 2009 at 8:17 PM, Harm Verhagen <harm.verhagen@...> wrote:
It seems esb is reading the timeout somewhere from an internal database instead of from the synapse.xml.
Modifying synapse.xml directy in webui doesn't help, changing property in proxy configuration doesnt help.

both
./wso2server.bat -DuseSynapseXML
./wso2server.bat --cleanRegistry
dont work
Any ideas ?

Regards,
Harm

On Thu, Aug 27, 2009 at 4:35 PM, Harm Verhagen <harm.verhagen@...> wrote:

Hi,

I noticed that a proxy with vfs transport, does not obey the PollInterval. I set it to 8 here.
It seems however that the files are processed every 30 seconds.
restarting the bus doesn't help.

I did not overrule the default vfs transport settings in the webUI, Just specified a proxy.
I expect that any proxy specifiy settings should be used, right ?

Is this a known issue ?

synapse snippet
    <syn:proxy name="SCOFileReader" transports="vfs" startOnLoad="true" trace="enable">
        <syn:target inSequence="sco-input"/>
        <syn:parameter name="transport.vfs.MoveAfterErrors">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterProcess">MOVE</syn:parameter>
        <syn:parameter name="transport.PollInterval">8</syn:parameter>
        <syn:parameter name="transport.vfs.FileURI">file:///c:/TESTPATH/Incoming/BTP_inbox</syn:parameter>
        <syn:parameter name="transport.vfs.MoveAfterProcess">file:///c:/TESTPATH/Incoming/BTP_processed</syn:parameter>
        <syn:parameter name="transport.vfs.MoveAfterFailure">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterErrors">MOVE</syn:parameter>
        <syn:parameter name="transport.vfs.FileNamePattern">.*.xml</syn:parameter>
        <syn:parameter name="transport.vfs.ContentType">application/xml</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterFailure">MOVE</syn:parameter>
    </syn:proxy>

With the following logs
[2009-08-27 16:28:20,531] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:28:34,765] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:28:35,703] DEBUG - VFSTransportListener Scanning directory or file : file:///c:/TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:28:49,765] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:29:01,328] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:29:05,718] DEBUG - VFSTransportListener Scanning directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:29:16,515] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:29:28,015] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:29:35,718] DEBUG - VFSTransportListener Scanning directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:29:43,031] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in

This shows every 30 seconds a scan of the directory.
the "//home/user/test/in" seem to come from the default vfs settings (which I'm not using).

version: wso2esb: 2.1 on java6, windows xp.

Regards,
Harm
_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Re: VFSTransportListener not obeying transport.PollInterval

2009-08-30T21:56:36Z

Hi Harm,

The issue is not with the transport.PollInterval property. The issue is with Proxy Services. When you change the poll interval and let it execute, it will still read the poll interval specified previously since the Proxy services has a caching issue. If you need to let the Proxy Service read the new poll interval, you will have to change the name of the Proxy Service through 'Manage Synapse Configuration'. Could you please try this out and let us know whether it solves the issue?

Thanks,
Evanthika

On Thu, Aug 27, 2009 at 8:17 PM, Harm Verhagen <harm.verhagen@...> wrote:

It seems esb is reading the timeout somewhere from an internal database instead of from the synapse.xml.
Modifying synapse.xml directy in webui doesn't help, changing property in proxy configuration doesnt help.

both
./wso2server.bat -DuseSynapseXML
./wso2server.bat --cleanRegistry
dont work
Any ideas ?

Regards,
Harm

On Thu, Aug 27, 2009 at 4:35 PM, Harm Verhagen <harm.verhagen@...> wrote:

Hi,

I noticed that a proxy with vfs transport, does not obey the PollInterval. I set it to 8 here.
It seems however that the files are processed every 30 seconds.
restarting the bus doesn't help.

I did not overrule the default vfs transport settings in the webUI, Just specified a proxy.
I expect that any proxy specifiy settings should be used, right ?

Is this a known issue ?

synapse snippet
    <syn:proxy name="SCOFileReader" transports="vfs" startOnLoad="true" trace="enable">
        <syn:target inSequence="sco-input"/>
        <syn:parameter name="transport.vfs.MoveAfterErrors">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterProcess">MOVE</syn:parameter>
        <syn:parameter name="transport.PollInterval">8</syn:parameter>
        <syn:parameter name="transport.vfs.FileURI">file:///c:/TESTPATH/Incoming/BTP_inbox</syn:parameter>
        <syn:parameter name="transport.vfs.MoveAfterProcess">file:///c:/TESTPATH/Incoming/BTP_processed</syn:parameter>
        <syn:parameter name="transport.vfs.MoveAfterFailure">file:///c:/TESTPATH/Incoming/BTP_error</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterErrors">MOVE</syn:parameter>
        <syn:parameter name="transport.vfs.FileNamePattern">.*.xml</syn:parameter>
        <syn:parameter name="transport.vfs.ContentType">application/xml</syn:parameter>
        <syn:parameter name="transport.vfs.ActionAfterFailure">MOVE</syn:parameter>
    </syn:proxy>

With the following logs
[2009-08-27 16:28:20,531] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:28:34,765] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:28:35,703] DEBUG - VFSTransportListener Scanning directory or file : file:///c:/TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:28:49,765] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:29:01,328] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:29:05,718] DEBUG - VFSTransportListener Scanning directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:29:16,515] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in
[2009-08-27 16:29:28,015] DEBUG - VFSTransportListener Unable to access or read file or directory : file:///home/user/test/in
[2009-08-27 16:29:35,718] DEBUG - VFSTransportListener Scanning directory or file : file:///c:TESTPATH/Incoming/BTP_inbox
[2009-08-27 16:29:43,031] DEBUG - VFSTransportListener Scanning directory or file : file:///home/user/test/in

This shows every 30 seconds a scan of the directory.
the "//home/user/test/in" seem to come from the default vfs settings (which I'm not using).

version: wso2esb: 2.1 on java6, windows xp.

Regards,
Harm

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

_______________________________________________
Esb-java-user mailing list
Esb-java-user@...
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user