[Dev] WSO2 Committers += Aruna Herath

2017-07-31 Thread Viraj Rajaguru
Hi All,

It's my pleasure to announce Aruna Herath as a WSO2 Committer.

Congratulations Aruna !

Thanks,
Viraj.

-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Fwd: Read and Send a file as Attachment.

2017-07-31 Thread Malaka Silva
Hi Vivek,

Not sure if this is currently supported. Looping integration team.

-- Forwarded message --
From: Vivek Kumar 
Date: Mon, Jul 31, 2017 at 5:28 PM
Subject: Read and Send a file as Attachment.
To: "mal...@wso2.com" 


Hi Malak,

We have requirement like we want to read a file from file location(
*D://data/fileName.log*) and send it as an attachment in the mail.



I have tried to achieve this using VFS file processing.

I find file *fileName.log *in the attachment but it contains envelope of
mediation flow not the actual content the file had.If have googled a lot
and found nothing helpful.

After analysing MailTransportSender.java , I am thinking like it is not
supported yet in wso2.

Please help me if there is any way I can achieve this WSO2ESB.



*Vivek Kumar*

*Associate System Analyst*

*Office:  *+91-120-4737401 <+91%20120%20473%207401>

*Mobile*: +91 8588897434 <+91%2085888%2097434>

*Email*:vivku...@salmon.com 

*Skype:*   vivekhereatskype





Information contained in this e-mail and any attachments is confidential
and intended for the use of the addressee only. Dissemination,
distribution, copying or use of this communication without prior permission
of the addressee is strictly prohibited. If you have received this
transmission in error, please advise the originator by reply e-mail and
delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector
57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356.




Information contained in this e-mail and any attachments is confidential
and intended for the use of the addressee only. Dissemination,
distribution, copying or use of this communication without prior permission
of the addressee is strictly prohibited. If you have received this
transmission in error, please advise the originator by reply e-mail and
delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector
57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356.



-- 

Best Regards,

Malaka Silva
Associate Director / Architect
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
https://wso2.com/signature
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Don't make Trees rare, we should keep them with care
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Issue in accessing same boss and worker group in HTTP carbon transport from MSF4J and Siddhi together

2017-07-31 Thread Yasara Dissanayake
Hi all,


Currently I’m working on implementing HTTP carbon transport for Siddhi. The
problem I face there is that since MSF4J also using HTTP carbon transport
we are facing the issue of keeping single bossGroup and workGroup for both
MSF4J and Siddhi [1]. Therefore we cannot independently control the
configurations of thread groups in Siddhi level and MSF4J level. As the
offline discussion had with shafreen and rajith, I’m currently using the
the thread groups which created by MSF4J and start
ServerconnectorController [2] and cannot  stop it at siddhi level since it
would give exception [3] as it stops the eventloop groups still used by
MSF4J . Further, when we try to pause the HTTP transport in Siddhi level ,
it will block the  HTTP transport in MSF4J and stop the server as well.Any
 possible resolution for this issue is highly appreciated since this seems
to be a blocker when invoking HTTP carbon transport.  I have created an
issue to track on this[4].


[1]
https://github.com/wso2/carbon-transports/blob/master/http/org.wso2.carbon.transport.http.netty/src/main/java/org/wso2/carbon/transport/http/netty/internal/HTTPTransportContextHolder.java#L49-L63

[2]
https://github.com/wso2-extensions/siddhi-io-http/blob/master/component/src/main/java/org/wso2/extension/siddhi/io/http/source/HttpConnectorRegistry.java#L130-L134

[3]

[2017-07-30 22:47:09,324] ERROR
{io.netty.util.concurrent.DefaultPromise.rejectedExecution} - Failed to
submit a listener notification task. Event loop shut down?
java.util.concurrent.RejectedExecutionException: event executor terminated

   at
io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:821)

   at
io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:327)

   at
io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:320)

   at
io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:746)

   at
io.netty.util.concurrent.DefaultPromise.safeExecute(DefaultPromise.java:760)

   at
io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:428)

   at
io.netty.util.concurrent.DefaultPromise.setFailure(DefaultPromise.java:113)

   at
io.netty.channel.DefaultChannelPromise.setFailure(DefaultChannelPromise.java:87)

   at
io.netty.channel.AbstractChannelHandlerContext.safeExecute(AbstractChannelHandlerContext.java:1011)

   at
io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:826)

   at
io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:724)

   at
io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:705)

   at
org.wso2.carbon.transport.http.netty.listener.ResponseCallback.done(ResponseCallback.java:108)

   at
org.wso2.msf4j.internal.entitywriter.ObjectEntityWriter.writeData(ObjectEntityWriter.java:57)

   at org.wso2.msf4j.Response.processEntity(Response.java:292)

   at org.wso2.msf4j.Response.send(Response.java:285)

   at
org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMethodInfo.java:157)

   at
org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(MSF4JMessageProcessor.java:208)

   at
org.wso2.msf4j.internal.MSF4JMessageProcessor.lambda$receive$53(MSF4JMessageProcessor.java:120)

   at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

   at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

   at java.lang.Thread.run(Thread.java:748)

[4] https://github.com/wso2/carbon-transports/issues/340


Thanks & Regards,
Yasara.
-- 


*Yasara Dissanayake*
*Software Engineer*
*WSO2 Lanka (pvt) Ltd.*

*Web : http://wso2.com/ *

*Email   : yas...@gmail.com Mobile : +94702107422
<+94%2070%20210%207422>*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] JDBCUserstore Config "IsEmailUserName"

2017-07-31 Thread Hasintha Indrajee
Is there any usage of subject ?. If so any idea where we honor this config
element ? Docs do have this [1]

[1] https://docs.wso2.com/display/IS530/Configuring+a+JDBC+User+Store

-- 
Hasintha Indrajee
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Issue in accessing same boss and worker group in HTTP carbon transport from MSF4J and Siddhi together

2017-07-31 Thread Shafreen Anfar
Hi Yasara,

Why do you want to shutdown the EventLoop groups. AFAIR, it was due to some
blocking operation in worker (child) thread pool right ?

On Mon, Jul 31, 2017 at 10:49 PM, Yasara Dissanayake 
wrote:

> Hi all,
>
>
> Currently I’m working on implementing HTTP carbon transport for Siddhi.
> The problem I face there is that since MSF4J also using HTTP carbon
> transport we are facing the issue of keeping single bossGroup and workGroup
> for both MSF4J and Siddhi [1]. Therefore we cannot independently control
> the configurations of thread groups in Siddhi level and MSF4J level. As
> the offline discussion had with shafreen and rajith, I’m currently using
> the the thread groups which created by MSF4J and start
> ServerconnectorController [2] and cannot  stop it at siddhi level since it
> would give exception [3] as it stops the eventloop groups still used by
> MSF4J . Further, when we try to pause the HTTP transport in Siddhi level
> , it will block the  HTTP transport in MSF4J and stop the server as
> well.Any  possible resolution for this issue is highly appreciated since
> this seems to be a blocker when invoking HTTP carbon transport.  I have
> created an issue to track on this[4].
>
>
> [1] https://github.com/wso2/carbon-transports/blob/master/
> http/org.wso2.carbon.transport.http.netty/src/main/java/org/wso2/carbon/
> transport/http/netty/internal/HTTPTransportContextHolder.java#L49-L63
>
> [2]https://github.com/wso2-extensions/siddhi-io-http/
> blob/master/component/src/main/java/org/wso2/extension/
> siddhi/io/http/source/HttpConnectorRegistry.java#L130-L134
>
> [3]
>
> [2017-07-30 22:47:09,324] ERROR 
> {io.netty.util.concurrent.DefaultPromise.rejectedExecution}
> - Failed to submit a listener notification task. Event loop shut down?
> java.util.concurrent.RejectedExecutionException: event executor terminated
>
>at io.netty.util.concurrent.SingleThreadEventExecutor.reject(
> SingleThreadEventExecutor.java:821)
>
>at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(
> SingleThreadEventExecutor.java:327)
>
>at io.netty.util.concurrent.SingleThreadEventExecutor.addTask(
> SingleThreadEventExecutor.java:320)
>
>at io.netty.util.concurrent.SingleThreadEventExecutor.execute(
> SingleThreadEventExecutor.java:746)
>
>at io.netty.util.concurrent.DefaultPromise.safeExecute(
> DefaultPromise.java:760)
>
>at io.netty.util.concurrent.DefaultPromise.notifyListeners(
> DefaultPromise.java:428)
>
>at io.netty.util.concurrent.DefaultPromise.setFailure(
> DefaultPromise.java:113)
>
>at io.netty.channel.DefaultChannelPromise.setFailure(
> DefaultChannelPromise.java:87)
>
>at io.netty.channel.AbstractChannelHandlerContext.safeExecute(
> AbstractChannelHandlerContext.java:1011)
>
>at io.netty.channel.AbstractChannelHandlerContext.write(
> AbstractChannelHandlerContext.java:826)
>
>at io.netty.channel.AbstractChannelHandlerContext.write(
> AbstractChannelHandlerContext.java:724)
>
>at io.netty.channel.AbstractChannelHandlerContext.write(
> AbstractChannelHandlerContext.java:705)
>
>at org.wso2.carbon.transport.http.netty.listener.ResponseCallback.done(
> ResponseCallback.java:108)
>
>at org.wso2.msf4j.internal.entitywriter.ObjectEntityWriter.writeData(
> ObjectEntityWriter.java:57)
>
>at org.wso2.msf4j.Response.processEntity(Response.java:292)
>
>at org.wso2.msf4j.Response.send(Response.java:285)
>
>at org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(
> HttpMethodInfo.java:157)
>
>at org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod(
> MSF4JMessageProcessor.java:208)
>
>at org.wso2.msf4j.internal.MSF4JMessageProcessor.lambda$receive$53(
> MSF4JMessageProcessor.java:120)
>
>at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
>
>at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
>
>at java.lang.Thread.run(Thread.java:748)
>
> [4] https://github.com/wso2/carbon-transports/issues/340
>
>
> Thanks & Regards,
> Yasara.
> --
>
>
> *Yasara Dissanayake*
> *Software Engineer*
> *WSO2 Lanka (pvt) Ltd.*
>
> *Web : http://wso2.com/ *
>
> *Email   : yas...@gmail.com Mobile : +94702107422
> <+94%2070%20210%207422>*
> 
>



-- 
Regards,
*Shafreen*
Software Engineer
WSO2 Inc
Mobile : 077-556-395-1
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Issue in accessing same boss and worker group in HTTP carbon transport from MSF4J and Siddhi together

2017-07-31 Thread Yasara Dissanayake
Hi Shfreen,

It is workable without shutting down EventLoop Groups from
ServerConnectorController. But in this scenario AFAIU both MSF4j and Siddhi
uses same ServerConnectorController and it gives following issues when
considering the use case for siddhi.


   1.

   Cannot configure event group sizes (boss group size and worker group
   size) independently from siddhi side. This is needed us when supporting
   orderly process AFAIU.
   2.

   Cannot pause siddi level transport since it will block the thread group
   as in [1] . Even if we use a queue to add events, it will block the thread
   group when inserting to the queue. In that scenario thread group will also
   get blocked for someone else like MSF4j


[1]-
https://github.com/wso2-extensions/siddhi-io-http/blob/master/component/src/main/java/org/wso2/extension/siddhi/io/http/source/HttpSourceListener.java#L71-L83


Regards and Thatnks,

Yasara.

On Mon, Jul 31, 2017 at 11:20 PM, Shafreen Anfar  wrote:

> Hi Yasara,
>
> Why do you want to shutdown the EventLoop groups. AFAIR, it was due to
> some blocking operation in worker (child) thread pool right ?
>
> On Mon, Jul 31, 2017 at 10:49 PM, Yasara Dissanayake 
> wrote:
>
>> Hi all,
>>
>>
>> Currently I’m working on implementing HTTP carbon transport for Siddhi.
>> The problem I face there is that since MSF4J also using HTTP carbon
>> transport we are facing the issue of keeping single bossGroup and workGroup
>> for both MSF4J and Siddhi [1]. Therefore we cannot independently control
>> the configurations of thread groups in Siddhi level and MSF4J level. As
>> the offline discussion had with shafreen and rajith, I’m currently using
>> the the thread groups which created by MSF4J and start
>> ServerconnectorController [2] and cannot  stop it at siddhi level since it
>> would give exception [3] as it stops the eventloop groups still used by
>> MSF4J . Further, when we try to pause the HTTP transport in Siddhi level
>> , it will block the  HTTP transport in MSF4J and stop the server as
>> well.Any  possible resolution for this issue is highly appreciated since
>> this seems to be a blocker when invoking HTTP carbon transport.  I have
>> created an issue to track on this[4].
>>
>>
>> [1] https://github.com/wso2/carbon-transports/blob/master/http/
>> org.wso2.carbon.transport.http.netty/src/main/java/org/
>> wso2/carbon/transport/http/netty/internal/HTTPTransportCo
>> ntextHolder.java#L49-L63
>>
>> [2]https://github.com/wso2-extensions/siddhi-io-http/blob/
>> master/component/src/main/java/org/wso2/extension/siddhi
>> /io/http/source/HttpConnectorRegistry.java#L130-L134
>>
>> [3]
>>
>> [2017-07-30 22:47:09,324] ERROR 
>> {io.netty.util.concurrent.DefaultPromise.rejectedExecution}
>> - Failed to submit a listener notification task. Event loop shut down?
>> java.util.concurrent.RejectedExecutionException: event executor
>> terminated
>>
>>at io.netty.util.concurrent.SingleThreadEventExecutor.reject(Si
>> ngleThreadEventExecutor.java:821)
>>
>>at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask
>> (SingleThreadEventExecutor.java:327)
>>
>>at io.netty.util.concurrent.SingleThreadEventExecutor.addTask(S
>> ingleThreadEventExecutor.java:320)
>>
>>at io.netty.util.concurrent.SingleThreadEventExecutor.execute(S
>> ingleThreadEventExecutor.java:746)
>>
>>at io.netty.util.concurrent.DefaultPromise.safeExecute(DefaultP
>> romise.java:760)
>>
>>at io.netty.util.concurrent.DefaultPromise.notifyListeners(Defa
>> ultPromise.java:428)
>>
>>at io.netty.util.concurrent.DefaultPromise.setFailure(DefaultPr
>> omise.java:113)
>>
>>at io.netty.channel.DefaultChannelPromise.setFailure(DefaultCha
>> nnelPromise.java:87)
>>
>>at io.netty.channel.AbstractChannelHandlerContext.safeExecute(A
>> bstractChannelHandlerContext.java:1011)
>>
>>at io.netty.channel.AbstractChannelHandlerContext.write(Abstrac
>> tChannelHandlerContext.java:826)
>>
>>at io.netty.channel.AbstractChannelHandlerContext.write(Abstrac
>> tChannelHandlerContext.java:724)
>>
>>at io.netty.channel.AbstractChannelHandlerContext.write(Abstrac
>> tChannelHandlerContext.java:705)
>>
>>at org.wso2.carbon.transport.http.netty.listener.ResponseCallba
>> ck.done(ResponseCallback.java:108)
>>
>>at org.wso2.msf4j.internal.entitywriter.ObjectEntityWriter.
>> writeData(ObjectEntityWriter.java:57)
>>
>>at org.wso2.msf4j.Response.processEntity(Response.java:292)
>>
>>at org.wso2.msf4j.Response.send(Response.java:285)
>>
>>at org.wso2.msf4j.internal.router.HttpMethodInfo.invoke(HttpMet
>> hodInfo.java:157)
>>
>>at org.wso2.msf4j.internal.MSF4JMessageProcessor.dispatchMethod
>> (MSF4JMessageProcessor.java:208)
>>
>>at org.wso2.msf4j.internal.MSF4JMessageProcessor.lambda$receive
>> $53(MSF4JMessageProcessor.java:120)
>>
>>at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1142)
>>
>>at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.

Re: [Dev] JDBCUserstore Config "IsEmailUserName"

2017-07-31 Thread Johann Nallathamby
I have also seen this and feel it's redundant. If there is no real purpose
for this can we  deprecate it and remove any usage of this property? If it
allows control per user store, then EnableEmailUserName is redundant in
carbon.xml.

Thoughts?

On Tue, Aug 1, 2017 at 12:33 AM, Hasintha Indrajee 
wrote:

> Is there any usage of subject ?. If so any idea where we honor this config
> element ? Docs do have this [1]
>
> [1] https://docs.wso2.com/display/IS530/Configuring+a+JDBC+User+Store
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453 <+94%2077%20189%202453>
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] JDBCUserstore Config "IsEmailUserName"

2017-07-31 Thread Isura Karunaratne
On Tue, Aug 1, 2017 at 2:49 AM Johann Nallathamby  wrote:

> I have also seen this and feel it's redundant. If there is no real purpose
> for this can we  deprecate it and remove any usage of this property? If it
> allows control per user store, then EnableEmailUserName is redundant in
> carbon.xml.
>
> Thoughts?
>

Yes. Currently, there is no usage of that property. We can deprecate it and
remove. There are a lot of usages of EnableEmailUserName property. So, in
c4 based products we have to rely EnableEmailUserName property.

Thanks
Isura

> On Tue, Aug 1, 2017 at 12:33 AM, Hasintha Indrajee 
> wrote:
>
>> Is there any usage of subject ?. If so any idea where we honor this
>> config element ? Docs do have this [1]
>>
>> [1] https://docs.wso2.com/display/IS530/Configuring+a+JDBC+User+Store
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453 <+94%2077%20189%202453>
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Senior Lead Solutions Engineer
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
-- 

*Isura Dilhara Karunaratne*
Senior Software Engineer | WSO2
Email: is...@wso2.com
Mob : +94 772 254 810
Blog : http://isurad.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev