Re: [Dev] [TestNG][G-Reg] Rest API delete with data body

[Dharshana Warusavitharana]

Hi Lahiru,

We discussed this in separate mail thread while the Test Case Hackathon.
Sending body for delete request is not mentioned in the spec and not
supported in many standard REST clients including JAX-RS2 and Wink. So we
raised the same concern for the ES team at that moment i think we have to
fix this on the ES side with align with the spec.

@Chandana WDYT

Thank you,
Dharshana.

On Wed, Apr 27, 2016 at 7:58 AM, Lahiru J Ekanayake 
wrote:

> Hi,
>
> I'm trying to implement a Test scenario using GenericRestClient .* I want
> to send a Delete REST request with a data body.* For that, i have tried
> with G-Reg Generic Rest Client [1] that already implemented. It accepts
> String type data as a parameter. But its not used inside the method. Is
> there a way to send a DELETE request with a data body ?
>
>
>
> [1] -
> https://github.com/wso2/product-greg/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/greg/integration/common/utils/GenericRestClient.java#L144
>
>
> Regards
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>


-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94770342233
blog : http://dharshanaw.blogspot.com

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

Re: [Dev] [Architecture] Common configuration for publishing events from carbon servers to DAS/CEP

[Niranjan Karunanandham]

Hi Malith,

Since this feature will be included in the next ESB release, IMO it would
be better to close the current PR and have it included in the same PR after
the product release.

Regards,
Nira

On Mon, Apr 25, 2016 at 6:05 PM, Malith Dhanushka  wrote:

> Hi Niranjan,
>
> Correction on my previous reply. we have to ship this feature by default
> with ESB and APIM. So this needs to be released with the immediate ESB or
> APIM release.
>
> @Viraj - Please include this feature in next ESB release. I have already
> sent a pull request by including this to carbon-feature-repository.
>
> Thanks,
> Malith
>
> On Mon, Apr 25, 2016 at 5:44 PM, Malith Dhanushka  wrote:
>
>> Hi Niranjan,
>>
>> Since this feature doesn't ship by default in any of the products, please
>> go ahead and merge this as an special case.
>>
>> Thanks,
>> Malith
>>
>> On Tue, Apr 12, 2016 at 10:56 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Malith,
>>>
>>> On Fri, Mar 18, 2016 at 11:42 AM, Malith Dhanushka 
>>> wrote:
>>>


 On Fri, Mar 18, 2016 at 11:38 AM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> This new change is only for OSGi based servers in the platform right?
> Are there any changes for standalone data publishing API's used with
> non-OSGi servers in the platform or is it still the same as before? We 
> have
> AS 6.0.0 which is based on pure tomcat and currently we are using the
> minimum required data publishing libs and the standalone data publishing
> API's to publish HTTP stats to DAS.
>

 Yes this new change is only for OSGi based servers and no change in
 standalone data publishing API's.


> On Mon, Mar 14, 2016 at 4:51 PM, Malith Dhanushka 
> wrote:
>
>> Hi all,
>>
>> Please follow the steps bellow when publishing events from carbon
>> servers to DAS/CEP. Here we keep the DAS/CEP server location in
>> CARBON_HOME/repository/deployment/server/eventpublishers directory and 
>> this
>> is common across platform.
>>
>> - Install the Event Publisher Aggregate feature from p2_repo [1]
>>
>> - Install Registry Core feature if not installed
>>
>> - Create event stream and deploy that to
>> CARBON_HOME/repository/deployment/server/eventstreams
>>
>> - Create publishers for the created stream and deploy that to
>>  CARBON_HOME/repository/deployment/server/eventpublishers
>> Following is a sample configuration,
>>
>> 
>> > xmlns="http://wso2.org/carbon/eventpublisher;>
>>   
>>   
>>   
>> admin
>> thrift
>> non-blocking
>> 0
>> tcp://localhost:7611
>> X
>>   
>> 
>>
>> - Publish events to the created stream using
>> org.wso2.carbon.event.stream.core.EventStreamService OSGI service.
>> Following is a sample code snippet.
>>
>> Event event = new Event();
>> event.setTimeStamp(System.currentTimeMillis());
>> event.setStreamId("streamTest:1.0.0");
>> event.setPayloadData(new Object[]{data});
>> eventStreamService.publish(event);
>>
>> Please note that Event Publisher Aggregate feature is not yet
>> included in carbon feature repo. It will be available with the immediate
>> analytics feature release.
>>
> Usually features are added to the p2-repo (carbon-feature-repository
>>> repo) when products are released. The product team has to send a PR of all
>>> the features they are using in the product (from the p2-profile-gen pom).
>>> Therefore this feature should come from the PR from the products which are
>>> using this feature when the product is released.
>>>
>>>

>> [1]
>> https://github.com/wso2/carbon-analytics-common/tree/master/features/event-publisher/org.wso2.carbon.event.publisher.aggregate.feature
>>
>> Thanks,
>> Malith
>> --
>> Malith Dhanushka
>> Senior Software Engineer - Data Technologies
>> *WSO2, Inc. : wso2.com *
>> *Mobile*  : +94 716 506 693
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Associate Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com
> *
> Twitter - *http://twitter.com/kishanthan
> *
>



 --
 Malith Dhanushka
 Senior Software Engineer - Data Technologies
 *WSO2, Inc. : wso2.com *
 *Mobile*  : +94 716 506 693

 ___
 

Re: [Dev] GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

Hi all,
Thanks for accepting my project proposal. :) Thank you very much on helping
me to prepare a good proposal. I am looking forward to get started with the
project ASAP

On Sat, Mar 26, 2016 at 12:16 PM, Isuru Udana  wrote:

> Hi Dinanjana,
>
>
>
> On Sat, Mar 26, 2016 at 8:31 AM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hi Kasun,
>> So shall I update the draft ? What do you think. I think the best
>> approach is to make this a separate application. Otherwise it will anyways
>> have an effect on the performance of ESB. Because this tool includes some
>> serious IO operations
>>
> Even though we built it as a separate application while we are taking
> thread-dumps, etc, can lead to a degrade in performance to a great extent,
> that's why we need to design it carefully.
>
> Thanks.
>
>>
>> On Sat, Mar 26, 2016 at 8:25 AM, Kasun Indrasiri  wrote:
>>
>>> It's fine. But just want to make sure this is added to the project plan
>>> as we move forward.
>>>
>>> On Sat, Mar 26, 2016 at 8:01 AM, Dinanjana Gunaratne <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
 Hi Kasun ,
 It's now I saw this mail. Can I do the change now ? I guess it's too
 late now. Anyway on your second point I have said that making flight
 recorder a separate application will stop applying any performance
 degradation on ESB. Anyway it would have been better if I have added the
 comparison.Can I do those changes now ?And i am really sorry for the late
 reply.

 On Fri, Mar 25, 2016 at 11:54 PM, Kasun Indrasiri 
 wrote:

> Dinanjana, can you please include several use cases related to
> possible production issues in an ESB (such as out of memory, CPU spinning,
> deadlock etc.). Also, running the ESB flight recorder should have minimal
> impact on the ESB performance. Hence your proposal should include an ESB
> performance comparison with and without flight recorder.
>
> The proposal looks good.
>
> Thanks,
> Kasun
>
> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hi Isuru ,
>> Thanks for the input :)
>>
>> On Fri, Mar 25, 2016 at 6:37 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hi Isuru ,
>>> Thanks for the input :)
>>>
>>> On Fri, Mar 25, 2016 at 6:34 PM, Isuru Udana 
>>> wrote:
>>>
 Hi Dinanjana,

 Proposal looks really good to me. Added several comments as well.

 On Fri, Mar 25, 2016 at 8:21 AM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Hello all,
> I submitted my proposal to gsoc site and shared the draft with
> WSO2 earlier this week. Any thoughts on my proposal ?
>
> On Sun, Mar 20, 2016 at 7:04 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hi all,
>> Can i have the location of source of carbondump tool ?
>>
>> On Wed, Mar 9, 2016 at 12:05 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hi all,
>>> I went through webinar and actually through the code of ESB. I
>>> couldn't grasped much with the code though. Now I have a high level
>>> understanding on what ESB does. I assumed that the esb is built on 
>>> carbon
>>> kernel. So we can have our monitoring service there inside the 
>>> carbon or
>>> else we can have a seperate microservice which can remotely monitor 
>>> the
>>> mbean server of the relevant JVM and extract metrics we require
>>>
>>> On Thu, Mar 3, 2016 at 5:35 PM, Isuru Ranawaka 
>>> wrote:
>>>
 Hi Dinanjana,

 While you are reading the  documentation you can figure out
 important features that needs to be included  and come up with a 
 set of
 features.Then we can finalize the scope of the project and start 
 working on
 it. Since you have already worked on  this kind of project can you 
 propose
 set of features and informations that will be helpfull to 
 implement them.


 thanks

 On Thu, Mar 3, 2016 at 9:56 AM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Hi all,
> Not currently. I am going through the documentation :) Thanks
> for the help :)
>
> On Thu, Mar 3, 2016 at 9:52 AM, Isuru Udana 
> wrote:
>
>> Hi Dinanjana,
>>
>> Do you need further help to understand the ESB architecture ?

[Dev] [TestNG][G-Reg] Rest API delete with data body

[Lahiru J Ekanayake]

Hi,

I'm trying to implement a Test scenario using GenericRestClient .* I want
to send a Delete REST request with a data body.* For that, i have tried
with G-Reg Generic Rest Client [1] that already implemented. It accepts
String type data as a parameter. But its not used inside the method. Is
there a way to send a DELETE request with a data body ?



[1] -
https://github.com/wso2/product-greg/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/greg/integration/common/utils/GenericRestClient.java#L144


Regards


-- 



*Lahiru J Ekanayake**Software Engineer*
Mobile : +94 (0) 77 8812629 / +94(0) 778509547
Email : lahi...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] WSO2 Dashboard Server 2.1.0-M1 Released!

[Lasantha Samarakoon]

*WSO2 Dashboard Server 2.1.0-M1 Released!*

WSO2 Dashboard Server team is pleased to announce the release of WSO2
Dashboard Server 2.1.0 Milestone 1 [1]. This release comes with the
following bug fixes and features.

Bug

   - [UES-900 ] - Difficult to delete
   characters in the beginning of a URL in a dashboard


Improvement

   - [UES-892 ] - Reword the message
   displayed when entering a duplicate dashboard name
   - [UES-898 ] - Login should happen
   through https by default


New Feature

   - [UES-926 ] - Show- Hide gadget
   Feature
   - [UES-927 ] - Pertain the state
   of gadgets within page
   - [UES-929 ] - Pluggable store
   support Feature
   - [UES-930 ] - Support for special
   widgets without redendering within iframe
   - [UES-931 ] - Flexibility to
   add/remove more operations in the gadget title bar



Reporting Issues

Issues can be reported through the Public JIRA project [2] for WSO2
Dashboard Server.

[1] https://github.com/wso2/product-ds/releases/tag/v2.1.0-m1
[2] https://wso2.org/jira/browse/UES



Regards,

WSO2 Dashboard Server Team



*Lasantha Samarakoon* | Software Engineer
WSO2, Inc.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 (71) 214 1576
Email:  lasant...@wso2.com
Web:www.wso2.com

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

Re: [Dev] carbon-dashboard 1.0.16 released to staging

[Udara Rathnayake]

Hi Jayanga,

Please drop above, as we have encounted some problems.
At the same time please close the new repo and provide us the repo URL.

Thanks!

On Tue, Apr 26, 2016 at 9:09 PM, Jayanga Dissanayake 
wrote:

> Hi Udara,
>
> The repo is closed. You can access the repo via [1].
> Please verify.
>
> [1]
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbondashboards-1002/
>
> Thanks,
> Jayanga.
>
> *Jayanga Dissanayake*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259
>
> On Tue, Apr 26, 2016 at 8:37 PM, Udara Rathnayake  wrote:
>
>> Hi Build team,
>>
>> Please close this and provide the repo.
>>
>> Thanks!
>>
>> --
>> Regards,
>> UdaraR
>>
>
>


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

Re: [Dev] carbon-dashboard 1.0.16 released to staging

[Jayanga Dissanayake]

Hi Udara,

The repo is closed. You can access the repo via [1].
Please verify.

[1]
http://maven.wso2.org/nexus/content/repositories/orgwso2carbondashboards-1002/

Thanks,
Jayanga.

*Jayanga Dissanayake*
Senior Software Engineer
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259

On Tue, Apr 26, 2016 at 8:37 PM, Udara Rathnayake  wrote:

> Hi Build team,
>
> Please close this and provide the repo.
>
> Thanks!
>
> --
> Regards,
> UdaraR
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] carbon-dashboard 1.0.16 released to staging

[Udara Rathnayake]

Hi Build team,

Please close this and provide the repo.

Thanks!

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

Re: [Dev] Make tasks claimable conditionaly

[Manuranga Perera]

Yes, I agree, we have to use two approaches. One for assigning future tasks
and one for re-assigning existing tasks.

For reassigning existing tasks, we can use
   1) REST API- I think this will be easier if we have the necessary
endpoints
   2) onMessage

For new tasks, we can use
   1) Cheeking the available user using service task and set that as the
candidate user

Note that we will have to revert it back when the user is available again.
This complicates the solution since we have to remember it all.
On the other hand, if we use something like a temporary role we don't have
to remember it. We can just put the user back in that role.

-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Developer Studio Kernel RC released !

[Kavith Lokuhewage]

Hello Devs,

Please note that source tag in above link has been incorrectly named.
Hence, we have recreated the tag for RC with proper name at following path.
https://github.com/wso2/developer-studio/tree/developer-studio-kernel-4.1.0-RC


Thanks,

On Tue, Apr 26, 2016 at 4:40 PM, Awanthika Senarath 
wrote:

> Hello Devs,
>
>
> We are pleased to announce the vote for RC of
> *WSO2 Developer Studio Kernel 4.1.0.*
>
> P2 repository of WSO2 developer Studio kernel 4.1.0 is available here
> .
>  Source
> and Tag Location to be voted upon is available here
> 
> .
>
> Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse 4.5)
>
> Developer Studio Kernel contains a single feature which has the bundles
> that are required to implement WSO2 specific product tooling on Eclipse.
>
>- This release contains Developer Studio migration to Eclipse mars
>- Improvements in the Developer Studio Updater tool for automatic
>updates
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
>
> Regards,
> Dev Studio Team
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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

Re: [Dev] [DEV] [ESB] Change payload response (LDAP Connector)

[Willian Antunes]

@Nuwan and @Malaka,

I'm using LDAP Connector
 not a endpoint
mediator itself. I tried with messageType but it didn't work. Thus I tried
with the following as well without success:





Does it apply to Connectors? In my case wouldn't be better using Script
Mediator  to change
the LDAP answer?

On Tue, Apr 26, 2016 at 5:11 AM, Nuwan Pallewela  wrote:

> Hi Willian,
>
> Do you want to change the message structure?
>
> If you don't need to change the message structure, you can change the
> axis2 messageType property to "json/application" and esb formatters will
> convert it to JSON.
> Eg:
>
> 
>
> If you want to change the message structure you can use FastXSLT mediator [1] 
> and then formatter to convert it to JSON as mention above.
> Performance of FastXSLT mediator in transforming messages is also better as 
> you can see in the [2].
>
> You can find more information abount JSON support in [3].
>
> [1] https://docs.wso2.com/display/ESB481/FastXSLT+Mediator
> [2] 
> http://soatutorials.blogspot.com/2016/01/wso2-esb-performance-tuning-for-xslt.html
> [3] 
> https://docs.wso2.com/display/ESB481/JSON+Support#JSONSupport-ConvertingapayloadbetweenXMLandJSON
>
> Thanks,
> Nuwan
>
> On Tue, Apr 26, 2016 at 2:47 AM, Willian Antunes <
> willian.lima.antu...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> One I consult my internal LDAP using LDAP Connector to retrieve the
>> details regarding some user I receive a huge response. For example (I'm
>> omitting anothers groups contained in memberOf):
>>
>> http://www.w3.org/2003/05/soap-envelope;>
>> http://org.wso2.esbconnectors.ldap;>
>> 
>> CN=Willian Lima Antunes,OU=Users,OU=Online,OU=DU
>> Editorial,DC=aqlbras,DC=com,DC=br
>> Willian Lima Antunes - Tecnologia Digital - Editora
>> Globo
>> Willian
>> wantu...@willianantunes.com.br
>> Lima Antunes
>>
>> CN=grupoedgfuncionarios,CN=Users,DC=aqlbras,DC=com,DC=br
>>
>> CN=EgspPRINT_6A1-new,CN=Users,DC=aqlbras,DC=com,DC=br
>>
>> CN=EgspPRINT_9A3,CN=Users,DC=aqlbras,DC=com,DC=br
>>
>> CN=EgspPRINT_8A1,CN=Users,DC=aqlbras,DC=com,DC=br
>> CN=aws,OU=Groups,OU=Online,OU=DU
>> Editorial,DC=aqlbras,DC=com,DC=br
>> CN=Ecommerce,OU=Groups,OU=Online,OU=DU
>> Editorial,DC=aqlbras,DC=com,DC=br
>> CN=Grupo E-commerce -
>> TI,CN=Users,DC=aqlbras,DC=com,DC=br
>>
>> CN=EgspUTLFILE_TRN02CP,CN=Users,DC=aqlbras,DC=com,DC=br
>> 
>> 
>> 
>>
>> What is the fastest way to change it to JSON? I know a way to do it
>> through Payload Factory mediator, but the work to map each value in a
>> variable is hard-working and the response may vary.
>>
>> Can I configure to receive a JSON instead of SOAP at the LDAP Connector
>> side?
>>
>> Any suggestions would be appreciated.
>>
>> Thanks.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
Yours sincerely,

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

Re: [Dev] Retrieving an OSGi service from CarbonContext in C5

[Sameera Jayasoma]

It should work. We've implemented JNDI OSGi spec just for this

On Tue, Apr 26, 2016 at 5:12 PM, Aruna Karunarathna  wrote:

>
>
> On Tue, Apr 26, 2016 at 4:57 PM, Nipuni Perera  wrote:
>
>> Hi Rasika,
>>
>> With Carbon-JNDI approach we provide a way to access osgi services from
>> the service registry. The OSGi url scheme syntax is different from java URL
>> scheme.
>>
>> The syntax is :  "osgi:service//"
>>
>> Eg : If you have a service registered in the service registry with a
>> class name "org.wso2.carbon.jndi.osgi.services.FooService", you should be
>> able to get the object with JNDI lookup :
>>
>> Object service = context.lookup("
>> osgi:service/org.wso2.carbon.jndi.osgi.services.FooService");
>>
>> Please find the samples and documentation from [1].
>>
>
> Hi Nipuni,
>
> Shall we test this carbon-jndi feature installing to the UUF server?.. We
> need to check whether the carbon-jndi works in the traditional way also,
> apart from accessing the service using,
>
> Object service =
> context.lookup("osgi:service/org.wso2.carbon.jndi.osgi.services.FooService");
>
> Regards,
> Aruna
>
>>
>> [1] https://github.com/wso2/carbon-jndi/
>>
>> Thanks,
>> Nipuni
>>
>>
>> On Tue, Apr 26, 2016 at 4:46 PM, Rasika Perera  wrote:
>>
>>> Hi Aruna & All,
>>>
>>> The requirement is that we need to provide a simple API to invoke a
>>> method in an OSGi Service from the JavaScript(Nashorn). As per the offline
>>> discussion with Aruna, JNDI is the recommended way to invoke OSGi services
>>> in C5.
>>>
>>> @Nipuni
>>> On the JNDI approach; are all OSGi services getting registered through a
>>> unique URI(eg. "java:comp/env/osgi-service-a") at the service startup?
>>>
>>> Thanks,
>>> Rasika
>>>
>>> On Tue, Apr 26, 2016 at 1:31 PM, Aruna Karunarathna 
>>> wrote:
>>>


 On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera 
 wrote:

> ​Hi All,
>
> Before C5, we had a method "getOSGiService(Class clazz,
> Hashtable props)​ to retrieve an OSGi service[1]. In 
> latest
> C5, I couldn't find any similar feature in [2].
>

 Can you elaborate more on your requirement here?. AFAIK there is no
 such way in C5 to retrieve OSGi services as in [1]

>
> ​What is the correct way to retrieve an OSGi service in C5?
>
> Or do we need to get it through directly from a "ServiceTracker" ?
>
> ​[1]
> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
> [2]
> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
> ​
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



 --

 *Aruna Sujith Karunarathna *
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 9040362 | Work: +94 112145345
 Email: ar...@wso2.com | Web: www.wso2.com


 On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera 
 wrote:

> ​Hi All,
>
> Before C5, we had a method "getOSGiService(Class clazz,
> Hashtable props)​ to retrieve an OSGi service[1]. In 
> latest
> C5, I couldn't find any similar feature in [2].
>
> ​What is the correct way to retrieve an OSGi service in C5?
>
> Or do we need to get it through directly from a "ServiceTracker" ?
>
> ​[1]
> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
> [2]
> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
> ​
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



 --

 *Aruna Sujith Karunarathna *
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 9040362 | Work: +94 112145345
 Email: ar...@wso2.com | Web: www.wso2.com


>>>
>>>
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> M: +94 71 680 9060 E: rasi...@wso2.com
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> Nipuni Perera
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> Email: nip...@wso2.com
>> Git hub profile: 

Re: [Dev] [AppManager] Fully qualified name issue in SAML response

[Dinusha Senanayaka]

IS Team,

Can you look into this issue please. This has broke the store/publisher
tenant login (We are using identity-5.0.9-SNAPSHOT versions).

- How to set fully qualified name when registering SP from config file.
- Skip sending carbon.super when fully qualified name is enabled.

Regards,
Dinusha.

On Mon, Apr 25, 2016 at 4:58 PM, Dinusha Senanayaka 
wrote:

> +Pushpalanka.
>
> On Mon, Apr 25, 2016 at 4:51 PM, Jenananthan Yogendran <
> jenanant...@wso2.com> wrote:
>
>> Hi All,
>>
>> After migrating the AppManager from kernel 4.2.0 to kernel 4.4.5  , fully
>> qualified name is not working as expected.
>>
>> We use file based SP configuration for Store app and Publisher
>> app(attached sso-idp-config files used in both kernel versions). In kernel
>> 4.2.0 , when login to store/publisher app, SAML response has user name with
>> tenant domain  as subject for tenants except carbon super tenant.
>>
>> After migration , SAML response has only user name as subject.Tenant
>> domain is missing for tenants.
>>
>> Also when checked the option "Use tenant domain in local subject
>> identifier" under "Local & Outbound Authentication Configuration" for
>> SPs created through UI, it appends the "carbon.super" domain for super
>> tenant users.
>>
>> Thanks
>> --
>> Jenananthan Yogendran
>> *Software Engineer,*
>> *WSO2 inc., http://wso2.com *
>>
>>
>
>
> --
> Dinusha Dilrukshi
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>



-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Retrieving an OSGi service from CarbonContext in C5

[Aruna Karunarathna]

On Tue, Apr 26, 2016 at 4:57 PM, Nipuni Perera  wrote:

> Hi Rasika,
>
> With Carbon-JNDI approach we provide a way to access osgi services from
> the service registry. The OSGi url scheme syntax is different from java URL
> scheme.
>
> The syntax is :  "osgi:service//"
>
> Eg : If you have a service registered in the service registry with a class
> name "org.wso2.carbon.jndi.osgi.services.FooService", you should be able to
> get the object with JNDI lookup :
>
> Object service = context.lookup("
> osgi:service/org.wso2.carbon.jndi.osgi.services.FooService");
>
> Please find the samples and documentation from [1].
>

Hi Nipuni,

Shall we test this carbon-jndi feature installing to the UUF server?.. We
need to check whether the carbon-jndi works in the traditional way also,
apart from accessing the service using,

Object service =
context.lookup("osgi:service/org.wso2.carbon.jndi.osgi.services.FooService");

Regards,
Aruna

>
> [1] https://github.com/wso2/carbon-jndi/
>
> Thanks,
> Nipuni
>
>
> On Tue, Apr 26, 2016 at 4:46 PM, Rasika Perera  wrote:
>
>> Hi Aruna & All,
>>
>> The requirement is that we need to provide a simple API to invoke a
>> method in an OSGi Service from the JavaScript(Nashorn). As per the offline
>> discussion with Aruna, JNDI is the recommended way to invoke OSGi services
>> in C5.
>>
>> @Nipuni
>> On the JNDI approach; are all OSGi services getting registered through a
>> unique URI(eg. "java:comp/env/osgi-service-a") at the service startup?
>>
>> Thanks,
>> Rasika
>>
>> On Tue, Apr 26, 2016 at 1:31 PM, Aruna Karunarathna 
>> wrote:
>>
>>>
>>>
>>> On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera 
>>> wrote:
>>>
 ​Hi All,

 Before C5, we had a method "getOSGiService(Class clazz,
 Hashtable props)​ to retrieve an OSGi service[1]. In latest
 C5, I couldn't find any similar feature in [2].

>>>
>>> Can you elaborate more on your requirement here?. AFAIK there is no such
>>> way in C5 to retrieve OSGi services as in [1]
>>>

 ​What is the correct way to retrieve an OSGi service in C5?

 Or do we need to get it through directly from a "ServiceTracker" ?

 ​[1]
 https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
 [2]
 https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
 ​

 --
 With Regards,

 *Rasika Perera*
 Software Engineer
 M: +94 71 680 9060 E: rasi...@wso2.com
 LinkedIn: http://lk.linkedin.com/in/rasika90

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>> On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera 
>>> wrote:
>>>
 ​Hi All,

 Before C5, we had a method "getOSGiService(Class clazz,
 Hashtable props)​ to retrieve an OSGi service[1]. In latest
 C5, I couldn't find any similar feature in [2].

 ​What is the correct way to retrieve an OSGi service in C5?

 Or do we need to get it through directly from a "ServiceTracker" ?

 ​[1]
 https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
 [2]
 https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
 ​

 --
 With Regards,

 *Rasika Perera*
 Software Engineer
 M: +94 71 680 9060 E: rasi...@wso2.com
 LinkedIn: http://lk.linkedin.com/in/rasika90

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> M: +94 71 680 9060 E: rasi...@wso2.com
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Blog : http://nipunipererablog.blogspot.com/
> Mobile: +94 (71) 5626680
> 
>
>


-- 

*Aruna Sujith Karunarathna *
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com

Re: [Dev] Retrieving an OSGi service from CarbonContext in C5

[Nipuni Perera]

Hi Rasika,

With Carbon-JNDI approach we provide a way to access osgi services from the
service registry. The OSGi url scheme syntax is different from java URL
scheme.

The syntax is :  "osgi:service//"

Eg : If you have a service registered in the service registry with a class
name "org.wso2.carbon.jndi.osgi.services.FooService", you should be able to
get the object with JNDI lookup :

Object service = context.lookup("
osgi:service/org.wso2.carbon.jndi.osgi.services.FooService");

Please find the samples and documentation from [1].

[1] https://github.com/wso2/carbon-jndi/

Thanks,
Nipuni


On Tue, Apr 26, 2016 at 4:46 PM, Rasika Perera  wrote:

> Hi Aruna & All,
>
> The requirement is that we need to provide a simple API to invoke a method
> in an OSGi Service from the JavaScript(Nashorn). As per the offline
> discussion with Aruna, JNDI is the recommended way to invoke OSGi services
> in C5.
>
> @Nipuni
> On the JNDI approach; are all OSGi services getting registered through a
> unique URI(eg. "java:comp/env/osgi-service-a") at the service startup?
>
> Thanks,
> Rasika
>
> On Tue, Apr 26, 2016 at 1:31 PM, Aruna Karunarathna 
> wrote:
>
>>
>>
>> On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera  wrote:
>>
>>> ​Hi All,
>>>
>>> Before C5, we had a method "getOSGiService(Class clazz,
>>> Hashtable props)​ to retrieve an OSGi service[1]. In latest
>>> C5, I couldn't find any similar feature in [2].
>>>
>>
>> Can you elaborate more on your requirement here?. AFAIK there is no such
>> way in C5 to retrieve OSGi services as in [1]
>>
>>>
>>> ​What is the correct way to retrieve an OSGi service in C5?
>>>
>>> Or do we need to get it through directly from a "ServiceTracker" ?
>>>
>>> ​[1]
>>> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
>>> [2]
>>> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
>>> ​
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> M: +94 71 680 9060 E: rasi...@wso2.com
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>> On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera  wrote:
>>
>>> ​Hi All,
>>>
>>> Before C5, we had a method "getOSGiService(Class clazz,
>>> Hashtable props)​ to retrieve an OSGi service[1]. In latest
>>> C5, I couldn't find any similar feature in [2].
>>>
>>> ​What is the correct way to retrieve an OSGi service in C5?
>>>
>>> Or do we need to get it through directly from a "ServiceTracker" ?
>>>
>>> ​[1]
>>> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
>>> [2]
>>> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
>>> ​
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> M: +94 71 680 9060 E: rasi...@wso2.com
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Nipuni Perera
Software Engineer; WSO2 Inc.; http://wso2.com
Email: nip...@wso2.com
Git hub profile: https://github.com/nipuni
Blog : http://nipunipererablog.blogspot.com/
Mobile: +94 (71) 5626680

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

Re: [Dev] Retrieving an OSGi service from CarbonContext in C5

[Rasika Perera]

Hi Aruna & All,

The requirement is that we need to provide a simple API to invoke a method
in an OSGi Service from the JavaScript(Nashorn). As per the offline
discussion with Aruna, JNDI is the recommended way to invoke OSGi services
in C5.

@Nipuni
On the JNDI approach; are all OSGi services getting registered through a
unique URI(eg. "java:comp/env/osgi-service-a") at the service startup?

Thanks,
Rasika

On Tue, Apr 26, 2016 at 1:31 PM, Aruna Karunarathna  wrote:

>
>
> On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera  wrote:
>
>> ​Hi All,
>>
>> Before C5, we had a method "getOSGiService(Class clazz, Hashtable> String> props)​ to retrieve an OSGi service[1]. In latest C5, I couldn't
>> find any similar feature in [2].
>>
>
> Can you elaborate more on your requirement here?. AFAIK there is no such
> way in C5 to retrieve OSGi services as in [1]
>
>>
>> ​What is the correct way to retrieve an OSGi service in C5?
>>
>> Or do we need to get it through directly from a "ServiceTracker" ?
>>
>> ​[1]
>> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
>> [2]
>> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
>> ​
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> M: +94 71 680 9060 E: rasi...@wso2.com
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera  wrote:
>
>> ​Hi All,
>>
>> Before C5, we had a method "getOSGiService(Class clazz, Hashtable> String> props)​ to retrieve an OSGi service[1]. In latest C5, I couldn't
>> find any similar feature in [2].
>>
>> ​What is the correct way to retrieve an OSGi service in C5?
>>
>> Or do we need to get it through directly from a "ServiceTracker" ?
>>
>> ​[1]
>> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
>> [2]
>> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
>> ​
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> M: +94 71 680 9060 E: rasi...@wso2.com
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio Kernel RC released !

[Awanthika Senarath]

Hello Devs,


We are pleased to announce the vote for RC of
*WSO2 Developer Studio Kernel 4.1.0.*

P2 repository of WSO2 developer Studio kernel 4.1.0 is available here
.
Source
and Tag Location to be voted upon is available here

.

Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse 4.5)

Developer Studio Kernel contains a single feature which has the bundles
that are required to implement WSO2 specific product tooling on Eclipse.

   - This release contains Developer Studio migration to Eclipse mars
   - Improvements in the Developer Studio Updater tool for automatic updates

[+] Stable - go ahead and release
[-]  Broken - do not release (please explain why)


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

[Dev] header intact

[Sadun Samintha]

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

Re: [Dev] ESB 4.9.0 OOM error.

[Isuru Udana]

Hi Ajith,

It looks like a never ending loop. I think OOM is obvious here.



On Tue, Apr 26, 2016 at 2:23 PM, Ajith Vitharana  wrote:

> Hi Chanaka.
>
> I found something interesting . So I had accidentally configured
>  uri-template as the endpoint of my API, So after sending one request ESB
> will go OOM. I can consistently reproduce this issue.
> Seems this is specific to Windows.
>
> 
> http://ws.apache.org/ns/synapse; name="TestAPI" context="
> */test*">
>
>   
>  
> 
>http://x.x.x:8280/test
> *"/>
> 
>  
>  
>   
>   
>  
>   
>
> 
>
>
> -Ajith
>
> On Tue, Apr 26, 2016 at 4:31 AM, Shashika Ubhayaratne 
> wrote:
>
>> Noted.
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>> On Tue, Apr 26, 2016 at 1:48 PM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Ajith,
>>>
>>> Thank you for reporting this issue. We haven't tested ESB 490 with
>>> Windows 10 when we were doing the release. We will investigate on this
>>> issue. Could you please share the REST API which you have used to test this
>>> scenario?
>>>
>>> @Shashika: Please note this and add this scenario to the testing effort
>>> of ESB 5.0.0.
>>>
>>> On Tue, Apr 26, 2016 at 12:57 PM, Ajith Vitharana 
>>> wrote:
>>>
 Hi All.

 I tried invoking simple REST API with ESB 4.9.0 vanilla pack on windows
 10 . I sent few request and observed the following error in the logs.


 TID: [-1234] [] [2016-04-26 03:12:22,669] ERROR
 {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
 exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
 java.lang.OutOfMemoryError: GC overhead limit exceeded


 ID: [-1234] [] [2016-04-26 03:12:45,434] ERROR
 {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
 exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
 java.lang.NoClassDefFoundError: Could not initialize class
 org.apache.synapse.transport.passthru.util.RelayUtils
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
 at
 org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
 at
 org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:86)
 at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
 at
 org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:680)
 at
 org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:515)
 at
 org.apache.synapse.endpoints.HTTPEndpoint.onFault(HTTPEndpoint.java:68)
 at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:259)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
 at
 org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:139)
 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)


 This is summary of memory analyze:

 7,379 instances of *"org.apache.synapse.transport.passthru.Pipe"*,
 loaded by *"synapse-nhttp-transport"* occupy *244,687,640 (29.45%)*
 bytes.

 *Keywords*
 synapse-nhttp-transport
 org.apache.synapse.transport.passthru.Pipe
 Details »
 Problem Suspect 2

 7,380 instances of
 *"org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection"*,
 loaded by *"synapse-nhttp-transport"* occupy *129,473,928 (15.58%)*
 bytes.

 *Keywords*
 synapse-nhttp-transport
 org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection
 Details »
 Problem Suspect 3

 7,379 instances of
 *"org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection"*,
 loaded by *"synapse-nhttp-transport"* occupy *127,685,424 (15.37%)*
 bytes. These instances are referenced from one instance of
 *"java.lang.Object[]"*, loaded by *""*

 *Keywords*
 java.lang.Object[]
 synapse-nhttp-transport
 org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection
 Details »
 Problem Suspect 4

 7,380 instances of *"org.apache.http.nio.util.SimpleOutputBuffer"*,
 loaded by *"httpcore-nio"* occupy *121,740,480 (14.65%)* 

Re: [Dev] ESB 4.9.0 OOM error.

[Ajith Vitharana]

On Tue, Apr 26, 2016 at 4:53 AM, Ajith Vitharana  wrote:

> Hi Chanaka.
>
> I found something interesting . So I had accidentally configured
>  uri-template as the endpoint of my API, So after sending one request ESB
> will go OOM. I can consistently reproduce this issue.
> Seems this is specific to Windows.
>

Seems this is *not*** specific to Windows.


>
> 
> http://ws.apache.org/ns/synapse; name="TestAPI" context="
> */test*">
>
>   
>  
> 
>http://x.x.x:8280/test
> *"/>
> 
>  
>  
>   
>   
>  
>   
>
> 
>
>
> -Ajith
>
> On Tue, Apr 26, 2016 at 4:31 AM, Shashika Ubhayaratne 
> wrote:
>
>> Noted.
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>> On Tue, Apr 26, 2016 at 1:48 PM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Ajith,
>>>
>>> Thank you for reporting this issue. We haven't tested ESB 490 with
>>> Windows 10 when we were doing the release. We will investigate on this
>>> issue. Could you please share the REST API which you have used to test this
>>> scenario?
>>>
>>> @Shashika: Please note this and add this scenario to the testing effort
>>> of ESB 5.0.0.
>>>
>>> On Tue, Apr 26, 2016 at 12:57 PM, Ajith Vitharana 
>>> wrote:
>>>
 Hi All.

 I tried invoking simple REST API with ESB 4.9.0 vanilla pack on windows
 10 . I sent few request and observed the following error in the logs.


 TID: [-1234] [] [2016-04-26 03:12:22,669] ERROR
 {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
 exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
 java.lang.OutOfMemoryError: GC overhead limit exceeded


 ID: [-1234] [] [2016-04-26 03:12:45,434] ERROR
 {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
 exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
 java.lang.NoClassDefFoundError: Could not initialize class
 org.apache.synapse.transport.passthru.util.RelayUtils
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
 at
 org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
 at
 org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
 at
 org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:86)
 at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
 at
 org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:680)
 at
 org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:515)
 at
 org.apache.synapse.endpoints.HTTPEndpoint.onFault(HTTPEndpoint.java:68)
 at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:259)
 at
 org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
 at
 org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:139)
 at
 org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)


 This is summary of memory analyze:

 7,379 instances of *"org.apache.synapse.transport.passthru.Pipe"*,
 loaded by *"synapse-nhttp-transport"* occupy *244,687,640 (29.45%)*
 bytes.

 *Keywords*
 synapse-nhttp-transport
 org.apache.synapse.transport.passthru.Pipe
 Details »
 Problem Suspect 2

 7,380 instances of
 *"org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection"*,
 loaded by *"synapse-nhttp-transport"* occupy *129,473,928 (15.58%)*
 bytes.

 *Keywords*
 synapse-nhttp-transport
 org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection
 Details »
 Problem Suspect 3

 7,379 instances of
 *"org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection"*,
 loaded by *"synapse-nhttp-transport"* occupy *127,685,424 (15.37%)*
 bytes. These instances are referenced from one instance of
 *"java.lang.Object[]"*, loaded by *""*

 *Keywords*
 java.lang.Object[]
 synapse-nhttp-transport
 org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection
 Details »
 Problem Suspect 4

 7,380 instances of *"org.apache.http.nio.util.SimpleOutputBuffer"*,
 loaded by *"httpcore-nio"* occupy *121,740,480 (14.65%)* bytes.

 *Keywords*

Re: [Dev] ESB 4.9.0 OOM error.

[Ajith Vitharana]

Hi Chanaka.

I found something interesting . So I had accidentally configured
 uri-template as the endpoint of my API, So after sending one request ESB
will go OOM. I can consistently reproduce this issue.
Seems this is specific to Windows.


http://ws.apache.org/ns/synapse; name="TestAPI" context="*/test*
">
   
  
 

   http://x.x.x:8280/test
*"/>

 
 
  
  
 
  
   



-Ajith

On Tue, Apr 26, 2016 at 4:31 AM, Shashika Ubhayaratne 
wrote:

> Noted.
>
> Shashika Ubhayaratne
> Associate Technical Lead - QA
> WSO2 Inc: http://www.wso2.com/
> Mobile: *+94773383831*
>
> On Tue, Apr 26, 2016 at 1:48 PM, Chanaka Fernando 
> wrote:
>
>> Hi Ajith,
>>
>> Thank you for reporting this issue. We haven't tested ESB 490 with
>> Windows 10 when we were doing the release. We will investigate on this
>> issue. Could you please share the REST API which you have used to test this
>> scenario?
>>
>> @Shashika: Please note this and add this scenario to the testing effort
>> of ESB 5.0.0.
>>
>> On Tue, Apr 26, 2016 at 12:57 PM, Ajith Vitharana 
>> wrote:
>>
>>> Hi All.
>>>
>>> I tried invoking simple REST API with ESB 4.9.0 vanilla pack on windows
>>> 10 . I sent few request and observed the following error in the logs.
>>>
>>>
>>> TID: [-1234] [] [2016-04-26 03:12:22,669] ERROR
>>> {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
>>> exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
>>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>>
>>>
>>> ID: [-1234] [] [2016-04-26 03:12:45,434] ERROR
>>> {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
>>> exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
>>> java.lang.NoClassDefFoundError: Could not initialize class
>>> org.apache.synapse.transport.passthru.util.RelayUtils
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>>> at
>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>>> at
>>> org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:86)
>>> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
>>> at
>>> org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:680)
>>> at
>>> org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:515)
>>> at
>>> org.apache.synapse.endpoints.HTTPEndpoint.onFault(HTTPEndpoint.java:68)
>>> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:259)
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>>> at
>>> org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:139)
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>
>>>
>>> This is summary of memory analyze:
>>>
>>> 7,379 instances of *"org.apache.synapse.transport.passthru.Pipe"*,
>>> loaded by *"synapse-nhttp-transport"* occupy *244,687,640 (29.45%)*
>>> bytes.
>>>
>>> *Keywords*
>>> synapse-nhttp-transport
>>> org.apache.synapse.transport.passthru.Pipe
>>> Details »
>>> Problem Suspect 2
>>>
>>> 7,380 instances of
>>> *"org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection"*,
>>> loaded by *"synapse-nhttp-transport"* occupy *129,473,928 (15.58%)*
>>> bytes.
>>>
>>> *Keywords*
>>> synapse-nhttp-transport
>>> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection
>>> Details »
>>> Problem Suspect 3
>>>
>>> 7,379 instances of
>>> *"org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection"*,
>>> loaded by *"synapse-nhttp-transport"* occupy *127,685,424 (15.37%)*
>>> bytes. These instances are referenced from one instance of
>>> *"java.lang.Object[]"*, loaded by *""*
>>>
>>> *Keywords*
>>> java.lang.Object[]
>>> synapse-nhttp-transport
>>> org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection
>>> Details »
>>> Problem Suspect 4
>>>
>>> 7,380 instances of *"org.apache.http.nio.util.SimpleOutputBuffer"*,
>>> loaded by *"httpcore-nio"* occupy *121,740,480 (14.65%)* bytes.
>>>
>>> *Keywords*
>>> org.apache.http.nio.util.SimpleOutputBuffer
>>> httpcore-nio
>>> --
>>> Ajith, Ahangama Vitharanalage.
>>>
>>> WSO2 Inc. - http://wso2.com
>>> Email  : aji...@wso2.com
>>> Blog: http://vitharana.org
>>> Mobile : +1-812-360-5335
>>>
>>>
>>
>>
>> --
>> Thank you and Best Regards,
>> 

Re: [Dev] ESB 4.9.0 OOM error.

[Shashika Ubhayaratne]

Noted.

Shashika Ubhayaratne
Associate Technical Lead - QA
WSO2 Inc: http://www.wso2.com/
Mobile: *+94773383831*

On Tue, Apr 26, 2016 at 1:48 PM, Chanaka Fernando  wrote:

> Hi Ajith,
>
> Thank you for reporting this issue. We haven't tested ESB 490 with Windows
> 10 when we were doing the release. We will investigate on this issue. Could
> you please share the REST API which you have used to test this scenario?
>
> @Shashika: Please note this and add this scenario to the testing effort of
> ESB 5.0.0.
>
> On Tue, Apr 26, 2016 at 12:57 PM, Ajith Vitharana  wrote:
>
>> Hi All.
>>
>> I tried invoking simple REST API with ESB 4.9.0 vanilla pack on windows
>> 10 . I sent few request and observed the following error in the logs.
>>
>>
>> TID: [-1234] [] [2016-04-26 03:12:22,669] ERROR
>> {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
>> exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>
>>
>> ID: [-1234] [] [2016-04-26 03:12:45,434] ERROR
>> {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
>> exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
>> java.lang.NoClassDefFoundError: Could not initialize class
>> org.apache.synapse.transport.passthru.util.RelayUtils
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
>> at
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
>> at
>> org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:86)
>> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
>> at
>> org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:680)
>> at
>> org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:515)
>> at org.apache.synapse.endpoints.HTTPEndpoint.onFault(HTTPEndpoint.java:68)
>> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:259)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
>> at
>> org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:139)
>> at
>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>
>>
>> This is summary of memory analyze:
>>
>> 7,379 instances of *"org.apache.synapse.transport.passthru.Pipe"*,
>> loaded by *"synapse-nhttp-transport"* occupy *244,687,640 (29.45%)*
>> bytes.
>>
>> *Keywords*
>> synapse-nhttp-transport
>> org.apache.synapse.transport.passthru.Pipe
>> Details »
>> Problem Suspect 2
>>
>> 7,380 instances of
>> *"org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection"*,
>> loaded by *"synapse-nhttp-transport"* occupy *129,473,928 (15.58%)*
>> bytes.
>>
>> *Keywords*
>> synapse-nhttp-transport
>> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection
>> Details »
>> Problem Suspect 3
>>
>> 7,379 instances of
>> *"org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection"*,
>> loaded by *"synapse-nhttp-transport"* occupy *127,685,424 (15.37%)*
>> bytes. These instances are referenced from one instance of
>> *"java.lang.Object[]"*, loaded by *""*
>>
>> *Keywords*
>> java.lang.Object[]
>> synapse-nhttp-transport
>> org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection
>> Details »
>> Problem Suspect 4
>>
>> 7,380 instances of *"org.apache.http.nio.util.SimpleOutputBuffer"*,
>> loaded by *"httpcore-nio"* occupy *121,740,480 (14.65%)* bytes.
>>
>> *Keywords*
>> org.apache.http.nio.util.SimpleOutputBuffer
>> httpcore-nio
>> --
>> Ajith, Ahangama Vitharanalage.
>>
>> WSO2 Inc. - http://wso2.com
>> Email  : aji...@wso2.com
>> Blog: http://vitharana.org
>> Mobile : +1-812-360-5335
>>
>>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.9.0 OOM error.

[Chanaka Fernando]

Hi Ajith,

Thank you for reporting this issue. We haven't tested ESB 490 with Windows
10 when we were doing the release. We will investigate on this issue. Could
you please share the REST API which you have used to test this scenario?

@Shashika: Please note this and add this scenario to the testing effort of
ESB 5.0.0.

On Tue, Apr 26, 2016 at 12:57 PM, Ajith Vitharana  wrote:

> Hi All.
>
> I tried invoking simple REST API with ESB 4.9.0 vanilla pack on windows 10
> . I sent few request and observed the following error in the logs.
>
>
> TID: [-1234] [] [2016-04-26 03:12:22,669] ERROR
> {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
> exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
> java.lang.OutOfMemoryError: GC overhead limit exceeded
>
>
> ID: [-1234] [] [2016-04-26 03:12:45,434] ERROR
> {org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
> exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.synapse.transport.passthru.util.RelayUtils
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
> at
> org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:86)
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
> at
> org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:680)
> at
> org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:515)
> at org.apache.synapse.endpoints.HTTPEndpoint.onFault(HTTPEndpoint.java:68)
> at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:259)
> at
> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
> at
> org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:139)
> at
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>
>
> This is summary of memory analyze:
>
> 7,379 instances of *"org.apache.synapse.transport.passthru.Pipe"*, loaded
> by *"synapse-nhttp-transport"* occupy *244,687,640 (29.45%)* bytes.
>
> *Keywords*
> synapse-nhttp-transport
> org.apache.synapse.transport.passthru.Pipe
> Details »
> Problem Suspect 2
>
> 7,380 instances of
> *"org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection"*,
> loaded by *"synapse-nhttp-transport"* occupy *129,473,928 (15.58%)*
> bytes.
>
> *Keywords*
> synapse-nhttp-transport
> org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection
> Details »
> Problem Suspect 3
>
> 7,379 instances of
> *"org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection"*,
> loaded by *"synapse-nhttp-transport"* occupy *127,685,424 (15.37%)*
> bytes. These instances are referenced from one instance of
> *"java.lang.Object[]"*, loaded by *""*
>
> *Keywords*
> java.lang.Object[]
> synapse-nhttp-transport
> org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection
> Details »
> Problem Suspect 4
>
> 7,380 instances of *"org.apache.http.nio.util.SimpleOutputBuffer"*,
> loaded by *"httpcore-nio"* occupy *121,740,480 (14.65%)* bytes.
>
> *Keywords*
> org.apache.http.nio.util.SimpleOutputBuffer
> httpcore-nio
> --
> Ajith, Ahangama Vitharanalage.
>
> WSO2 Inc. - http://wso2.com
> Email  : aji...@wso2.com
> Blog: http://vitharana.org
> Mobile : +1-812-360-5335
>
>


-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Kubernetes] Using MySQL as the Default DB for WSO2 K8s Artifacts

[Lakmal Warusawithana]

On Tue, Apr 26, 2016 at 1:20 PM, Isuru Haththotuwa  wrote:

> Hi Devs,
>
> We can do $subject in the Kubernetes Artifacts. Its possible to define the
> DB url with the relevant Kubernetes service name, hence there is no need to
> know the exact IP of the database pod.
>
> Currently in mysql docker image [1], its only possible to create one DB
> per container. Therefore to support the usual deployment clustered wso2
> products, we would need at least 3 pods:
>
>1. gov_db - shared across all products as necessary
>2. user_db - shared across all products as necessary
>3. product_db - used for config db (shared with all members of the
>same cluster) and any other product specific db tables
>
> This will allow the users to deploy the wso2 products using defined real
> distributed deployment patterns in a kubernetes environment with minimal
> effort, without doing any configuration changes.
>
> Note that the purpose of this effort is to make it easier to try out WSO2
> products in a K8s environment, and to try out K8s features like
> autoscaling, etc. without the hassle of configuring databases, etc. WDYT?
>
>
+1


> [1]. https://hub.docker.com/_/mysql/
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
Lakmal Warusawithana
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Retrieving an OSGi service from CarbonContext in C5

[Aruna Karunarathna]

On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera  wrote:

> ​Hi All,
>
> Before C5, we had a method "getOSGiService(Class clazz, Hashtable String> props)​ to retrieve an OSGi service[1]. In latest C5, I couldn't
> find any similar feature in [2].
>

Can you elaborate more on your requirement here?. AFAIK there is no such
way in C5 to retrieve OSGi services as in [1]

>
> ​What is the correct way to retrieve an OSGi service in C5?
>
> Or do we need to get it through directly from a "ServiceTracker" ?
>
> ​[1]
> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
> [2]
> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
> ​
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 

*Aruna Sujith Karunarathna *
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com


On Tue, Apr 26, 2016 at 12:33 PM, Rasika Perera  wrote:

> ​Hi All,
>
> Before C5, we had a method "getOSGiService(Class clazz, Hashtable String> props)​ to retrieve an OSGi service[1]. In latest C5, I couldn't
> find any similar feature in [2].
>
> ​What is the correct way to retrieve an OSGi service in C5?
>
> Or do we need to get it through directly from a "ServiceTracker" ?
>
> ​[1]
> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
> [2]
> https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
> ​
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> M: +94 71 680 9060 E: rasi...@wso2.com
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 

*Aruna Sujith Karunarathna *
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Kubernetes] Using MySQL as the Default DB for WSO2 K8s Artifacts

[Isuru Haththotuwa]

Hi Devs,

We can do $subject in the Kubernetes Artifacts. Its possible to define the
DB url with the relevant Kubernetes service name, hence there is no need to
know the exact IP of the database pod.

Currently in mysql docker image [1], its only possible to create one DB per
container. Therefore to support the usual deployment clustered wso2
products, we would need at least 3 pods:

   1. gov_db - shared across all products as necessary
   2. user_db - shared across all products as necessary
   3. product_db - used for config db (shared with all members of the same
   cluster) and any other product specific db tables

This will allow the users to deploy the wso2 products using defined real
distributed deployment patterns in a kubernetes environment with minimal
effort, without doing any configuration changes.

Note that the purpose of this effort is to make it easier to try out WSO2
products in a K8s environment, and to try out K8s features like
autoscaling, etc. without the hassle of configuring databases, etc. WDYT?

[1]. https://hub.docker.com/_/mysql/

-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB 4.9.0 OOM error.

[Ajith Vitharana]

Hi All.

I tried invoking simple REST API with ESB 4.9.0 vanilla pack on windows 10
. I sent few request and observed the following error in the logs.


TID: [-1234] [] [2016-04-26 03:12:22,669] ERROR
{org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
java.lang.OutOfMemoryError: GC overhead limit exceeded


ID: [-1234] [] [2016-04-26 03:12:45,434] ERROR
{org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.synapse.transport.passthru.util.RelayUtils
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at
org.apache.synapse.mediators.MediatorFaultHandler.onFault(MediatorFaultHandler.java:86)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:54)
at
org.apache.synapse.endpoints.AbstractEndpoint.invokeNextFaultHandler(AbstractEndpoint.java:680)
at
org.apache.synapse.endpoints.AbstractEndpoint.onFault(AbstractEndpoint.java:515)
at org.apache.synapse.endpoints.HTTPEndpoint.onFault(HTTPEndpoint.java:68)
at org.apache.synapse.FaultHandler.handleFault(FaultHandler.java:102)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:259)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
at
org.apache.synapse.transport.passthru.TargetErrorHandler$1.run(TargetErrorHandler.java:139)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)


This is summary of memory analyze:

7,379 instances of *"org.apache.synapse.transport.passthru.Pipe"*, loaded
by *"synapse-nhttp-transport"* occupy *244,687,640 (29.45%)* bytes.

*Keywords*
synapse-nhttp-transport
org.apache.synapse.transport.passthru.Pipe
Details »


Problem
Suspect 2

7,380 instances of
*"org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection"*,
loaded by *"synapse-nhttp-transport"* occupy *129,473,928 (15.58%)* bytes.

*Keywords*
synapse-nhttp-transport
org.apache.synapse.transport.http.conn.LoggingNHttpServerConnection
Details »


Problem
Suspect 3

7,379 instances of
*"org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection"*,
loaded by *"synapse-nhttp-transport"* occupy *127,685,424 (15.37%)* bytes.
These instances are referenced from one instance of *"java.lang.Object[]"*,
loaded by *""*

*Keywords*
java.lang.Object[]
synapse-nhttp-transport
org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection
Details »


Problem
Suspect 4

7,380 instances of *"org.apache.http.nio.util.SimpleOutputBuffer"*, loaded
by *"httpcore-nio"* occupy *121,740,480 (14.65%)* bytes.

*Keywords*
org.apache.http.nio.util.SimpleOutputBuffer
httpcore-nio
-- 
Ajith, Ahangama Vitharanalage.

WSO2 Inc. - http://wso2.com
Email  : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Retrieving an OSGi service from CarbonContext in C5

[Rasika Perera]

​Hi All,

Before C5, we had a method "getOSGiService(Class clazz, Hashtable props)​ to retrieve an OSGi service[1]. In latest C5, I couldn't
find any similar feature in [2].

​What is the correct way to retrieve an OSGi service in C5?

Or do we need to get it through directly from a "ServiceTracker" ?

​[1]
https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/context/CarbonContext.java#L322
[2]
https://github.com/wso2/carbon-kernel/blob/master/core/src/main/java/org/wso2/carbon/kernel/context/PrivilegedCarbonContext.java
​

-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Changing the Primary Keystore password in IS 5.0.0 SP1.

[Kamidu Punchihewa]

Hi Omindu,

Thank you. I change the both password and key password to the same value
and the Issues is fixed.

Thanks and Best Regards.

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Tue, Apr 26, 2016 at 11:37 AM, Omindu Rathnaweera 
wrote:

> Hi Kamindu,
>
> This can happen when the keystore and the private key password are not the
> same (see [1]). Can you try changing the private key password to match the
> keystore password and check? You can follow [2] to change the private key
> password.
>
> [1] - https://wso2.org/jira/browse/CARBON-14975
> [2] -
> http://xacmlinfo.org/2014/05/26/how-to-keystore-changing-java-key-store-passwords/
>
> Regards,
> Omindu.
>
> On Tue, Apr 26, 2016 at 10:57 AM, Kamidu Punchihewa 
> wrote:
>
>> Hi Tharindu,
>>
>> I debugged the mentioned class and checked the runtime values for the two
>> variables below as suggested:
>>
>>- keystorePath
>>- keystorePassword
>>
>> For both the variables the correct values were assigned at runtime. The
>> correct key store was assigned to the variables along with the new password
>> provided.
>> Any idea why the above mentioned error occurred even when the correct
>> password is provided?
>>
>> Thanks and Best Regards,
>>
>> Kamidu Sachith Punchihewa
>> *Software Engineer*
>> WSO2, Inc.
>> lean . enterprise . middleware
>> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>>
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>> On Mon, Apr 25, 2016 at 7:04 PM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Kamidu,
>>>
>>> If you have correctly set the new password in identity.xml file's
>>> *EntitlementSettings*, can you remote debug the
>>> *org.wso2.carbon.identity.entitlement* 's *4.2.2 *version to find out
>>> the actual cause.
>>>
>>> The particular class is
>>>
>>>
>>> *src/main/java/org/wso2/carbon/identity/entitlement/internal/EntitlementServiceComponent.java*
>>> You may need to check the values read for following variables in the
>>> class.
>>>
>>> //read the keystore and password used for ssl
>>> communication from config
>>> String keystorePath = IdentityUtil.getProperty(
>>> ThriftConfigConstants.PARAM_KEYSTORE_LOCATION);
>>> String keystorePassword = IdentityUtil.getProperty(
>>> ThriftConfigConstants.PARAM_KEYSTORE_PASSWORD);
>>>
>>> Regards,
>>> TharinduE
>>>
>>> On Mon, Apr 25, 2016 at 5:56 PM, Kamidu Punchihewa 
>>> wrote:
>>>
 Hi,

 I have a IS 5.0.0 SP1 pack and i have change the default password of
 the key store and changed the following config files accordingly.

- /repository/conf/identity.xml.
- /repository/conf/carbon.xml
- /repository/conf/axis2/axis2.xml
- /repository/conf/security/cipher-tool.properties
- /repository/conf/security/secret-conf.properties
- /repository/conf/security/cipher-text.properties
-

 /repository/deployment/server/jaggeryapps/dashboard/authentication/auth_config.json
-

 /repository/deployment/server/webapps/authenticationendpoint/WEB-INF/classes/TenantConfig.properties

 At Server startup the following error occurred.
 Is there are any more changes to be done?

 *Error Log :*

 [2016-04-25 17:51:39,207] ERROR
 {org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent}
 -  Error in initializing thrift transport
 org.apache.thrift.transport.TTransportException: Error creating the
 transport
 at
 

Re: [Dev] Converting a Certificate Request from .PEM to .DER

[Madhawa Perera]

Thank you Dilshan it works :)

On Mon, Apr 25, 2016 at 3:30 PM, Dilshan Edirisuriya 
wrote:

> Its just a base64 decode version of PEM. Just execute
> Base64.decode(str.getBytes()) by removing BEGIN CERTIFICATE, END
> CERTIFICATE parts.
>
> Regards,
>
> Dilshan
>
> On 25 April 2016 at 15:22, Madhawa Perera  wrote:
>
>> I'm trying to convert a certificate request which is in PEM format as
>> shown below.
>>
>> -BEGIN CERTIFICATE REQUEST-
>> MIIC/jCCAeYCAQAwgZ0xCzAJBgNVBAYTAlVTMQswCQYDVQQIDAJDQTEWMBQGA1UE
>> BwwNU2FuIEZyYW5jaXNjbzETMBEGA1UECgwKQnJvd24gQmVhcjEVMBMGA1UECwwM
>> YnJvd25iZWFyLm1lMRkwFwYDVQQDDBBhcHAuYnJvd25iZWFyLm1lMSIwIAYJKoZI
>> hvcNAQkBFhNnaXJvbGFtaXNAZ21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOC
>> AQ8AMIIBCgKCAQEA09S3Sn7leo53lko+A/l2UNvzxR34WNsIyORRWF68wphPoYsf
>> DEtOebG1U+iSRUjl/g0z7DCpNlBYboN3x1ac+upkyvyvrkk/k2cqTLh/zfjN67wM
>> 8W2tld+zBkT0EGzHHDqzrxsaCOurwHiQ4FqsrVl6frys3wPyPsXiH4UZFQeFCNKI
>> -END CERTIFICATE REQUEST-
>>
>> (This is not the full certificate request file I'm using, I have deleted
>> the content in the middle but it takes the above format)
>>
>> I can do the conversion by executing the following openssl command.
>>
>> *"openssl req -inform pem -outform der -in " + csrFileLocation + " -out
>> "+ derFileLocation + ".der"*
>>
>> However I need to use java to do the conversion (from pem to der) without
>> going through openssl command line tool or without executing the openssl
>> command using java.
>>
>> I have tried to do it with the bouncy castle but it didn't work for me.
>> Is there anyone out there who has tried this before?
>>
>> Any help appreciated.
>>
>> Thank you
>> Best Regards,
>> Madhawa
>>
>>
>> --
>> Madhawa Perera
>> *Software Engineer*
>> Mobile : +94 (0) 773655496
>> <%2B94%20%280%29%20773%20451194>
>> madha...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Madhawa Perera
*Software Engineer*
Mobile : +94 (0) 773655496
<%2B94%20%280%29%20773%20451194>
madha...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Changing the Primary Keystore password in IS 5.0.0 SP1.

[Omindu Rathnaweera]

Hi Kamindu,

This can happen when the keystore and the private key password are not the
same (see [1]). Can you try changing the private key password to match the
keystore password and check? You can follow [2] to change the private key
password.

[1] - https://wso2.org/jira/browse/CARBON-14975
[2] -
http://xacmlinfo.org/2014/05/26/how-to-keystore-changing-java-key-store-passwords/

Regards,
Omindu.

On Tue, Apr 26, 2016 at 10:57 AM, Kamidu Punchihewa 
wrote:

> Hi Tharindu,
>
> I debugged the mentioned class and checked the runtime values for the two
> variables below as suggested:
>
>- keystorePath
>- keystorePassword
>
> For both the variables the correct values were assigned at runtime. The
> correct key store was assigned to the variables along with the new password
> provided.
> Any idea why the above mentioned error occurred even when the correct
> password is provided?
>
> Thanks and Best Regards,
>
> Kamidu Sachith Punchihewa
> *Software Engineer*
> WSO2, Inc.
> lean . enterprise . middleware
> Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>
>
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> On Mon, Apr 25, 2016 at 7:04 PM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Kamidu,
>>
>> If you have correctly set the new password in identity.xml file's
>> *EntitlementSettings*, can you remote debug the
>> *org.wso2.carbon.identity.entitlement* 's *4.2.2 *version to find out
>> the actual cause.
>>
>> The particular class is
>>
>>
>> *src/main/java/org/wso2/carbon/identity/entitlement/internal/EntitlementServiceComponent.java*
>> You may need to check the values read for following variables in the
>> class.
>>
>> //read the keystore and password used for ssl
>> communication from config
>> String keystorePath = IdentityUtil.getProperty(
>> ThriftConfigConstants.PARAM_KEYSTORE_LOCATION);
>> String keystorePassword = IdentityUtil.getProperty(
>> ThriftConfigConstants.PARAM_KEYSTORE_PASSWORD);
>>
>> Regards,
>> TharinduE
>>
>> On Mon, Apr 25, 2016 at 5:56 PM, Kamidu Punchihewa 
>> wrote:
>>
>>> Hi,
>>>
>>> I have a IS 5.0.0 SP1 pack and i have change the default password of the
>>> key store and changed the following config files accordingly.
>>>
>>>- /repository/conf/identity.xml.
>>>- /repository/conf/carbon.xml
>>>- /repository/conf/axis2/axis2.xml
>>>- /repository/conf/security/cipher-tool.properties
>>>- /repository/conf/security/secret-conf.properties
>>>- /repository/conf/security/cipher-text.properties
>>>-
>>>
>>> /repository/deployment/server/jaggeryapps/dashboard/authentication/auth_config.json
>>>-
>>>
>>> /repository/deployment/server/webapps/authenticationendpoint/WEB-INF/classes/TenantConfig.properties
>>>
>>> At Server startup the following error occurred.
>>> Is there are any more changes to be done?
>>>
>>> *Error Log :*
>>>
>>> [2016-04-25 17:51:39,207] ERROR
>>> {org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent}
>>> -  Error in initializing thrift transport
>>> org.apache.thrift.transport.TTransportException: Error creating the
>>> transport
>>> at
>>> org.apache.thrift.transport.TSSLTransportFactory.createSSLContext(TSSLTransportFactory.java:201)
>>> at
>>> org.apache.thrift.transport.TSSLTransportFactory.getServerSocket(TSSLTransportFactory.java:102)
>>> at
>>> org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.startThriftEntitlementService(EntitlementServiceComponent.java:329)
>>> at
>>> org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.startThriftServices(EntitlementServiceComponent.java:300)
>>> at
>>> org.wso2.carbon.identity.entitlement.internal.EntitlementServiceComponent.activate(EntitlementServiceComponent.java:162)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>>