[GitHub] [synapse] madhawa-gunasekara opened a new pull request #23: Fix SYNAPSE-1106

[GitBox]

madhawa-gunasekara opened a new pull request #23: Fix SYNAPSE-1106
URL: https://github.com/apache/synapse/pull/23
 
 
   MessageContext class store messageContext object in a ThreadLocalVariable 
where it doesn't clear created ThreadLocal variables properly. Therefore 
synapse passthrough threads contain created the Theadlocal variable which 
refers to the created soap envelope during the mediation level. Because of the 
retained ThreadLocal variables, Passthrough threads consumes a huge amount of 
memory which leads to OOM.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[GitHub] [synapse] madhawa-gunasekara opened a new pull request #22: Fix SYNAPSE-1105

[GitBox]

madhawa-gunasekara opened a new pull request #22: Fix SYNAPSE-1105
URL: https://github.com/apache/synapse/pull/22
 
 
   TargetConnections getConnection method doesn't retrun null when the 
connection is not available.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1114) HTTP Transport based on Netty.io

[Isuru Udana (Jira)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036337#comment-17036337
 ] 

Isuru Udana commented on SYNAPSE-1114:
--

Thanks, Madhawa.
Please note that Jira ticket cannot be assigned to you at this moment as you 
are yet to become a committer. 

> HTTP Transport based on Netty.io
> 
>
> Key: SYNAPSE-1114
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1114
> Project: Synapse
>  Issue Type: New Feature
>  Components: Transports
>Reporter: Isuru Udana
>Assignee: Isuru Udana
>Priority: Major
>
> Netty is an NIO client-server framework that enables development of 
> high-performing network applications. 
> It has a simple API that an application can use to interact with. 
> The use of netty will allow us to extend the HTTP transport capabilities 
> beyond a simple client-server application. Support for HTTP/2 is one such 
> feature.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Commented] (SYNAPSE-1114) HTTP Transport based on Netty.io

[Madhawa Kasun Gunasekara (Jira)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036335#comment-17036335
 ] 

Madhawa Kasun Gunasekara commented on SYNAPSE-1114:
---

Hi [~isudana], I will work on this, Can you please assign this to me

> HTTP Transport based on Netty.io
> 
>
> Key: SYNAPSE-1114
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1114
> Project: Synapse
>  Issue Type: New Feature
>  Components: Transports
>Reporter: Isuru Udana
>Assignee: Isuru Udana
>Priority: Major
>
> Netty is an NIO client-server framework that enables development of 
> high-performing network applications. 
> It has a simple API that an application can use to interact with. 
> The use of netty will allow us to extend the HTTP transport capabilities 
> beyond a simple client-server application. Support for HTTP/2 is one such 
> feature.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

[jira] [Created] (SYNAPSE-1114) HTTP Transport based on Netty.io

[Isuru Udana (Jira)]

Isuru Udana created SYNAPSE-1114:


 Summary: HTTP Transport based on Netty.io
 Key: SYNAPSE-1114
 URL: https://issues.apache.org/jira/browse/SYNAPSE-1114
 Project: Synapse
  Issue Type: New Feature
  Components: Transports
Reporter: Isuru Udana
Assignee: Isuru Udana


Netty is an NIO client-server framework that enables development of 
high-performing network applications. 
It has a simple API that an application can use to interact with. 
The use of netty will allow us to extend the HTTP transport capabilities beyond 
a simple client-server application. Support for HTTP/2 is one such feature.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Positioning Synapse as an Integration Framework

[Madhawa Kasun Gunasekara]

Hi,

We came up with the below list.

Tasks

   -

   Reduce memory footprint
   -

   Create docker, Kubernetes artifacts [
   https://issues.apache.org/jira/projects/SYNAPSE/issues/SYNAPSE-]
   -

   Integrate travis/jenkins for the pull requests - Isuru
   -

   JDK11 support (openjdk) [
   https://issues.apache.org/jira/projects/SYNAPSE/issues/SYNAPSE-1112]


   -

   Unit testing framework
   -

   Netty transport


Thanks,
Madhawa


On Thu, Feb 13, 2020 at 4:26 PM Isuru Udana  wrote:

>
>
> On Thu, Feb 13, 2020 at 8:53 PM Madhawa Kasun Gunasekara <
> madhaw...@gmail.com> wrote:
>
>> Hi All,
>>
>> Shall we start working on this? I believe there are so many things to
>> improve. so let's start listing them. after that, we can prioritize items
>> and create Jira tickets.
>>
>> +1. I will first work on integrating a build system (Travis or Jenkins)
> for Pull Requests, that will make PR merging easier.
>
> Thanks.
>
>
>> Thanks,
>> Madhawa
>>
>>
>> On Tue, Jan 7, 2020 at 7:10 PM Madhawa Kasun Gunasekara <
>> madhaw...@gmail.com> wrote:
>>
>>> +1,
>>> Moving forward for the container friendly integration framework is a
>>> great idea. How about considering for version 4.x.x. release. I can help
>>> too.
>>>
>>> Thanks,
>>> Madhawa
>>>
>>>
>>> On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana  wrote:
>>>
 Hi All,

 It has been 12 years since Synapse was founded (2007-12-19). As we all
 know in the last few years we did not have a good run. The activity of the
 project has significantly gone down and there is not much of a contribution
 from the majority of the committers.

 Also, ESB architectural style is no longer the preferred style for
 doing the integration. The world has been moved towards container friendly
 products, microservices, and cloud-native technologies. However, the
 integration problem solved by the ESB architecture still exists and handled
 by different entities.

 Even though Synapse is an ESB, it has most of the qualities (ex: faster
 startup time, low resource consumption, etc.) that are important for
 containers and microservices integrations. So with a little effort, we
 could make Synapse a container friendly product that suits any
 architectural style for doing the integration.

 So, should we consider positioning Synapse as an 'Integration
 Framework' or an 'Integration Product' that serves all architectural 
 styles?
 Will that help us reactivate the project?

 Please share your thoughts.

 Thank you.



 -- Forwarded message -
 From: Isuru Udana 
 Date: Thu, Dec 12, 2019 at 7:03 AM
 Subject: Re: Positioning Synapse as an Integration Framework
 To: 


 I will open this discussion to the community to reach a wide audience.

 On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
 vanjikuma...@gmail.com> wrote:

> I am not too sure about adopting the very abstract term Integration
> Framework; However, I can assure that moving towards container-native
> is a
> logical move.
> I can help on this to produce an initial set of artifacts.
>
>
>
> On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana  wrote:
>
> > Hi PMC,
> >
> > It has been 12 years since Synapse was founded (2007-12-19). As we
> all know
> > in the last few years we did not have a good run. The activity of the
> > project has significantly gone down and there is not much of a
> contribution
> > from the majority of the committers/PMC members.
> >
> > Also, ESB architectural style is no longer the preferred style for
> doing
> > the integration. The world has been moved towards container friendly
> > products, microservices, and cloud-native technologies. However, the
> > integration problem solved by the ESB architecture still exists and
> handled
> > by different entities.
> >
> > Even though Synapse is an ESB, it has most of the qualities (ex:
> faster
> > startup time, low resource consumption, etc.) that are important for
> > containers and microservices integrations. So with a little effort,
> we
> > could make Synapse a container friendly product that suits any
> > architectural style for doing the integration.
> >
> > So, should we consider positioning Synapse as an 'Integration
> Framework' or
> > an 'Integration Product' that serves all architectural styles?
> > Will that help us reactivate the project?
> >
> >
> > --
> > *Isuru Udana*
> >
> >
> >
> > *email: isud...@gmail.com  blog:
> > http://mytecheye.blogspot.com/ *
> >
>
>
> --
> Best Regards,
> Vanji
>


 --
 *Isuru Udana*
 Senior Technical Lead




 *; WSO2 Inc.; http://wso2.com 

[jira] [Commented] (SYNAPSE-1112) Move to OpenJDK

[Madhawa Kasun Gunasekara (Jira)]

[ 
https://issues.apache.org/jira/browse/SYNAPSE-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036316#comment-17036316
 ] 

Madhawa Kasun Gunasekara commented on SYNAPSE-1112:
---

Support openjdk11

> Move to OpenJDK 
> 
>
> Key: SYNAPSE-1112
> URL: https://issues.apache.org/jira/browse/SYNAPSE-1112
> Project: Synapse
>  Issue Type: Task
>Reporter: Ravi Undupitiya
>Assignee: Isuru Udana
>Priority: Major
> Fix For: FUTURE
>
>
> Given the recent Oracle JDK licensing changes, we should ensure synapse can 
> be built and used on OpenJDK and change our build to OpenJDK.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Re: Positioning Synapse as an Integration Framework

[Isuru Udana]

On Thu, Feb 13, 2020 at 8:53 PM Madhawa Kasun Gunasekara <
madhaw...@gmail.com> wrote:

> Hi All,
>
> Shall we start working on this? I believe there are so many things to
> improve. so let's start listing them. after that, we can prioritize items
> and create Jira tickets.
>
> +1. I will first work on integrating a build system (Travis or Jenkins)
for Pull Requests, that will make PR merging easier.

Thanks.


> Thanks,
> Madhawa
>
>
> On Tue, Jan 7, 2020 at 7:10 PM Madhawa Kasun Gunasekara <
> madhaw...@gmail.com> wrote:
>
>> +1,
>> Moving forward for the container friendly integration framework is a
>> great idea. How about considering for version 4.x.x. release. I can help
>> too.
>>
>> Thanks,
>> Madhawa
>>
>>
>> On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana  wrote:
>>
>>> Hi All,
>>>
>>> It has been 12 years since Synapse was founded (2007-12-19). As we all
>>> know in the last few years we did not have a good run. The activity of the
>>> project has significantly gone down and there is not much of a contribution
>>> from the majority of the committers.
>>>
>>> Also, ESB architectural style is no longer the preferred style for doing
>>> the integration. The world has been moved towards container friendly
>>> products, microservices, and cloud-native technologies. However, the
>>> integration problem solved by the ESB architecture still exists and handled
>>> by different entities.
>>>
>>> Even though Synapse is an ESB, it has most of the qualities (ex: faster
>>> startup time, low resource consumption, etc.) that are important for
>>> containers and microservices integrations. So with a little effort, we
>>> could make Synapse a container friendly product that suits any
>>> architectural style for doing the integration.
>>>
>>> So, should we consider positioning Synapse as an 'Integration Framework'
>>> or an 'Integration Product' that serves all architectural styles?
>>> Will that help us reactivate the project?
>>>
>>> Please share your thoughts.
>>>
>>> Thank you.
>>>
>>>
>>>
>>> -- Forwarded message -
>>> From: Isuru Udana 
>>> Date: Thu, Dec 12, 2019 at 7:03 AM
>>> Subject: Re: Positioning Synapse as an Integration Framework
>>> To: 
>>>
>>>
>>> I will open this discussion to the community to reach a wide audience.
>>>
>>> On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
>>> vanjikuma...@gmail.com> wrote:
>>>
 I am not too sure about adopting the very abstract term Integration
 Framework; However, I can assure that moving towards container-native
 is a
 logical move.
 I can help on this to produce an initial set of artifacts.



 On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana  wrote:

 > Hi PMC,
 >
 > It has been 12 years since Synapse was founded (2007-12-19). As we
 all know
 > in the last few years we did not have a good run. The activity of the
 > project has significantly gone down and there is not much of a
 contribution
 > from the majority of the committers/PMC members.
 >
 > Also, ESB architectural style is no longer the preferred style for
 doing
 > the integration. The world has been moved towards container friendly
 > products, microservices, and cloud-native technologies. However, the
 > integration problem solved by the ESB architecture still exists and
 handled
 > by different entities.
 >
 > Even though Synapse is an ESB, it has most of the qualities (ex:
 faster
 > startup time, low resource consumption, etc.) that are important for
 > containers and microservices integrations. So with a little effort, we
 > could make Synapse a container friendly product that suits any
 > architectural style for doing the integration.
 >
 > So, should we consider positioning Synapse as an 'Integration
 Framework' or
 > an 'Integration Product' that serves all architectural styles?
 > Will that help us reactivate the project?
 >
 >
 > --
 > *Isuru Udana*
 >
 >
 >
 > *email: isud...@gmail.com  blog:
 > http://mytecheye.blogspot.com/ *
 >


 --
 Best Regards,
 Vanji

>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Senior Technical Lead
>>>
>>>
>>>
>>>
>>> *; WSO2 Inc.; http://wso2.com email: isud...@gmail.com
>>>  blog: http://mytecheye.blogspot.com/
>>> *
>>>
>>>
>>>
>>>

-- 
*Isuru Udana*
Associate Director/Architect



*; WSO2 Inc.; http://wso2.com email: isud...@gmail.com
 *

Re: Positioning Synapse as an Integration Framework

[Madhawa Kasun Gunasekara]

Hi All,

Shall we start working on this? I believe there are so many things to
improve. so let's start listing them. after that, we can prioritize items
and create Jira tickets.

Thanks,
Madhawa


On Tue, Jan 7, 2020 at 7:10 PM Madhawa Kasun Gunasekara 
wrote:

> +1,
> Moving forward for the container friendly integration framework is a great
> idea. How about considering for version 4.x.x. release. I can help too.
>
> Thanks,
> Madhawa
>
>
> On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana  wrote:
>
>> Hi All,
>>
>> It has been 12 years since Synapse was founded (2007-12-19). As we all
>> know in the last few years we did not have a good run. The activity of the
>> project has significantly gone down and there is not much of a contribution
>> from the majority of the committers.
>>
>> Also, ESB architectural style is no longer the preferred style for doing
>> the integration. The world has been moved towards container friendly
>> products, microservices, and cloud-native technologies. However, the
>> integration problem solved by the ESB architecture still exists and handled
>> by different entities.
>>
>> Even though Synapse is an ESB, it has most of the qualities (ex: faster
>> startup time, low resource consumption, etc.) that are important for
>> containers and microservices integrations. So with a little effort, we
>> could make Synapse a container friendly product that suits any
>> architectural style for doing the integration.
>>
>> So, should we consider positioning Synapse as an 'Integration Framework'
>> or an 'Integration Product' that serves all architectural styles?
>> Will that help us reactivate the project?
>>
>> Please share your thoughts.
>>
>> Thank you.
>>
>>
>>
>> -- Forwarded message -
>> From: Isuru Udana 
>> Date: Thu, Dec 12, 2019 at 7:03 AM
>> Subject: Re: Positioning Synapse as an Integration Framework
>> To: 
>>
>>
>> I will open this discussion to the community to reach a wide audience.
>>
>> On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
>> vanjikuma...@gmail.com> wrote:
>>
>>> I am not too sure about adopting the very abstract term Integration
>>> Framework; However, I can assure that moving towards container-native is
>>> a
>>> logical move.
>>> I can help on this to produce an initial set of artifacts.
>>>
>>>
>>>
>>> On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana  wrote:
>>>
>>> > Hi PMC,
>>> >
>>> > It has been 12 years since Synapse was founded (2007-12-19). As we all
>>> know
>>> > in the last few years we did not have a good run. The activity of the
>>> > project has significantly gone down and there is not much of a
>>> contribution
>>> > from the majority of the committers/PMC members.
>>> >
>>> > Also, ESB architectural style is no longer the preferred style for
>>> doing
>>> > the integration. The world has been moved towards container friendly
>>> > products, microservices, and cloud-native technologies. However, the
>>> > integration problem solved by the ESB architecture still exists and
>>> handled
>>> > by different entities.
>>> >
>>> > Even though Synapse is an ESB, it has most of the qualities (ex: faster
>>> > startup time, low resource consumption, etc.) that are important for
>>> > containers and microservices integrations. So with a little effort, we
>>> > could make Synapse a container friendly product that suits any
>>> > architectural style for doing the integration.
>>> >
>>> > So, should we consider positioning Synapse as an 'Integration
>>> Framework' or
>>> > an 'Integration Product' that serves all architectural styles?
>>> > Will that help us reactivate the project?
>>> >
>>> >
>>> > --
>>> > *Isuru Udana*
>>> >
>>> >
>>> >
>>> > *email: isud...@gmail.com  blog:
>>> > http://mytecheye.blogspot.com/ *
>>> >
>>>
>>>
>>> --
>>> Best Regards,
>>> Vanji
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior Technical Lead
>>
>>
>>
>>
>> *; WSO2 Inc.; http://wso2.com email: isud...@gmail.com
>>  blog: http://mytecheye.blogspot.com/
>> *
>>
>>
>>
>>