Re: [Dev] PassThroughMessageProcessor threads on Waiting State
Hi Junior, Yes. Passthrough worker pool configuration can be found in EI_home/conf/passthru-http.properties and by default, there are 400 core threads. Once EI receive the request, worker pool grows to 400 and It will remains in WAITING state until server shutdown. If you want to reduce the threads WAITING and your server load is not much, you can reduce the worker_pool_size_core. so that you can manage WAITING thread on lower value. Please note that since the worker_pool_queue_length is -1, It can queue unlimited message, so thread pool will not grow up to 500 max in any load and condition. If you set a positive value for worker_pool_queue_length(Ex:1000), once the queue is full, then additional threads are creating upto max value(500) and those threads are staling after 60 sec of idling when the load is low. Limiting a queue length may lead to cause message rejections once all threads occupied and queue is full. worker_pool_size_core=400 worker_pool_size_max=500 worker_thread_keepalive_sec=60 worker_pool_queue_length=-1 Name: PassThroughMessageProcessor-1 State: WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@9ae83d3 Total blocked: 0 Total waited: 1 Please refer documentation[1] for passthrough worker pool configuration. [1] https://docs.wso2.com/display/EI611/Tuning+the+HTTP+Transport Thanks, Nuwanw On Fri, Apr 6, 2018 at 9:37 AM, Shakila Sasikaran <shak...@wso2.com> wrote: > Hi Junior, > > Is this happening when the threads try to do the write operation? Do you > see any error in the log? If so, could you please share the > repository/logs/wso2carbon.log with us? > > Thanks > > On Thu, Apr 5, 2018 at 5:01 PM, Júnior <fjunio...@gmail.com> wrote: > >> Hi Shakila, >> >> I am using EI 6.1.0 >> >> Thanks, >> >> 2018-04-05 0:45 GMT-03:00 Shakila Sasikaran <shak...@wso2.com>: >> >>> Hi Junior, >>> >>> Which version are you using? Seems this is similar to >>> https://wso2.org/jira/browse/ESBJAVA-4392. >>> >>> Thanks >>> >>> On Thu, Apr 5, 2018 at 2:33 AM, Júnior <fjunio...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I am seeing a lot of PassThroughMessageProcessor threads in Waiting >>>> state. >>>> >>>> Is this normal? Is there a way to set then to remove stale threads? >>>> >>>> Thanks, >>>> -- >>>> Francisco Ribeiro >>>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate* >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Shakila Sasikaran >>> Software Engineer >>> Mobile :+94 (0) 77 526 6848 >>> shak...@wso2.com >>> WSO2, Inc. >>> lean . enterprise . middleware >>> http://www.wso2.com/ >>> >> >> >> >> -- >> Francisco Ribeiro >> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate* >> > > > > -- > Shakila Sasikaran > Software Engineer > Mobile :+94 (0) 77 526 6848 > shak...@wso2.com > WSO2, Inc. > lean . enterprise . middleware > http://www.wso2.com/ > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] About LDAP connector
Hi According to the code[1], Connector throws an exception when there is no result set found while searching the users. Not on error in connector. This seems to be invalid because It should not throw an exception by checking null. It should set a message and let the message flow continue. Searching may or may not contains user informations and the message flow should be decided by the developer, how It continue based on the result. However we have implemented it in a way that goes to fault sequence on empty result set and developer has no control. However It would be better if we can fix this code. To maintain backward compatibility, we can introduce a property(faultOnEmptyResult) and based on the property, we can decide whether it goes to fault or continue message flow. As a default behavior, we can set faultOnEmptyResult to true. Then existing develpers does not affect this change and backward compatibility remains. [1] https://github.com/wso2-extensions/esb-connector-ldap/blob/org.wso2.carbon.connector.ldap-1.0.3/src/main/java/org/wso2/carbon/connector/ldap/SearchEntry.java#L80 Thanks, Nuwanw On Mon, Apr 9, 2018 at 2:06 PM, Piriya Sivalingam <pir...@wso2.com> wrote: > Hi, > > In the LDAP connector, if we encounter any exception [1], it throws the > synapseException. Hence fault sequence gets triggered. But usually, if > there is any error in the mediation flow only, the synapseException is > thrown. > Could you kindly let me know whether this (throwing synapseException) is > the expected behavior here. > If so in order to avoid the messages going into the fault sequence, can we > handle it with a custom exception handler. > Could you kindly provide your input on this? > > [1] https://github.com/wso2-extensions/esb-connector-ldap/ > blob/org.wso2.carbon.connector.ldap-1.0.3/src/main/java/org/wso2/carbon/ > connector/ldap/SearchEntry.java#L95 > > -- > Regards, > > *Piriya Sivalingam* > > *Software Engineer - Support Team* > > *WSO2* > *Mobile : +94 77 8462039* > > [image: http://wso2.com/signature] <http://wso2.com/signature> > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Tes automation framework for SOA integration test
Hi Godwin, Since this is only a http service invocation, There is no need to use WSO2 automation framework. You have few options. Hope options listed below, will help you 1) Write your own maven test module using unit test framework like testng or junit. In the test module, you can use a existing http client implementation library to invoke the APIs and Proxy Service. So you can easily implement service chaining. 2) Use JMeter to invoke the APIs. JMeter has the ability to read the response from one service and create a new payload based on previous response. Then you can do the service chaining. And JMeter project can also be executed using maven plugin or command line. So CICD is also possible with JMeter. Thanks, Nuwanw On Thu, Jan 11, 2018 at 9:51 PM, Godwin Shrimal <god...@wso2.com> wrote: > Thanks for the response Vinod. > > > Thanks > Godwin > > On Fri, Jan 12, 2018 at 6:34 AM, Vinod Kavinda <vi...@wso2.com> wrote: > >> Hi Godwin, >> In that case, I think you can use the existing wso2 automation framework. >> You can refer mediation tests in the product-ei for reference. >> >> Regards, >> Vinod >> >> On Fri, Jan 12, 2018 at 4:48 AM, Godwin Shrimal <god...@wso2.com> wrote: >> >>> Hi Nuwan, >>> >>> Let me explain the scenario. I am building up an echo system and using >>> wso2ei-6.1.1 in the mediation layer. So I have many numbers of proxy >>> services and APIs. I want to write an automation test suit to test those >>> Proxy services and APIs (integration test). So service innovation will be >>> enough here and think services are already deployed. >>> >>> Thanks >>> Godwin >>> >>> On Thu, Jan 11, 2018 at 11:53 PM, Nuwan Wimalasekara <nuw...@wso2.com> >>> wrote: >>> >>>> Hi Godwin, >>>> >>>> The requirement is not clear to me. You want to service invocation only >>>> or service deployment and invocation for your testing. >>>> >>>> Thanks, >>>> Nuwanw >>>> >>>> On Thu, Jan 11, 2018 at 10:44 AM, Milinda Perera <milin...@wso2.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> @Nuwan: can we use our existing integration test framework that we use >>>>> in product-ei. Since all extensions, utils, etc released we can do >>>>> integration test using it. WDYT? >>>>> >>>>> Thanks, >>>>> Milinda >>>>> >>>>> >>>>> On Thu, Jan 11, 2018 at 4:39 PM, Godwin Shrimal <god...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Devs, >>>>>> >>>>>> I want to write the *integration* test for Proxy service and APIs >>>>>> deployed in wso2ei-6.1.1. Can someone propose a recommended open source >>>>>> framework for this? >>>>>> >>>>>> >>>>>> Thanks >>>>>> Godwin >>>>>> -- >>>>>> *Godwin Amila Shrimal* >>>>>> Associate Technical Lead >>>>>> WSO2 Inc.; http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> mobile: *+94772264165* >>>>>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/ >>>>>> <https://www.linkedin.com/in/godwin-amila-2ba26844/>* >>>>>> twitter: https://twitter.com/godwinamila >>>>>> <http://wso2.com/signature> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Milinda Perera >>>>> Senior Software Engineer; >>>>> WSO2 Inc. http://wso2.com , >>>>> Mobile: (+94) 714 115 032 <071%20411%205032> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Wimalasekara >>>> Associate Technical Lead >>>> WSO2, Inc.: http://wso2.com >>>> lean. enterprise. middleware >>>> >>>> phone: +94 71 668 4620 <+94%2071%20668%204620> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> *Godwin Amila Shrimal* >>> Associate Technical Lead >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: *+94772264165* >>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/ >>> <https://www.linkedin.com/in/godwin-amila-2ba26844/>* >>> twitter: https://twitter.com/godwinamila >>> <http://wso2.com/signature> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Vinod Kavinda >> Senior Software Engineer >> *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.* >> Mobile : +94 (0) 712 415544 >> Blog : http://soatechflicks.blogspot.com/ >> [image: http://wso2.com/signature] >> <http://wso2.com/signature> >> >> > > > -- > *Godwin Amila Shrimal* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: *+94772264165* > linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/ > <https://www.linkedin.com/in/godwin-amila-2ba26844/>* > twitter: https://twitter.com/godwinamila > <http://wso2.com/signature> > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Tes automation framework for SOA integration test
Hi Godwin, The requirement is not clear to me. You want to service invocation only or service deployment and invocation for your testing. Thanks, Nuwanw On Thu, Jan 11, 2018 at 10:44 AM, Milinda Perera <milin...@wso2.com> wrote: > Hi, > > @Nuwan: can we use our existing integration test framework that we use in > product-ei. Since all extensions, utils, etc released we can do integration > test using it. WDYT? > > Thanks, > Milinda > > > On Thu, Jan 11, 2018 at 4:39 PM, Godwin Shrimal <god...@wso2.com> wrote: > >> Hi Devs, >> >> I want to write the *integration* test for Proxy service and APIs >> deployed in wso2ei-6.1.1. Can someone propose a recommended open source >> framework for this? >> >> >> Thanks >> Godwin >> -- >> *Godwin Amila Shrimal* >> Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: *+94772264165* >> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/ >> <https://www.linkedin.com/in/godwin-amila-2ba26844/>* >> twitter: https://twitter.com/godwinamila >> <http://wso2.com/signature> >> > > > > -- > Milinda Perera > Senior Software Engineer; > WSO2 Inc. http://wso2.com , > Mobile: (+94) 714 115 032 <071%20411%205032> > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Riyafa Abdul Hameed
Hi Devs, It is my pleasure to welcome Riyafa Abdul Hameed as a WSO2 Committer. Riyafa has made a great contributions to product-EI, MB and Integration Team during the last few months and in recognition of her commitment and contributions, she has been voted as a Committer for WSO2. @Riyafa, welcome aboard and keep up the good work. Thanks, Nuwanw -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Enterprise Integrator 6.1.1-update9 Released!
Hi all, The WSO2 Integration team is pleased to announce the release of Enterprise Integrator 6.1.1-update9. It is available for download from here <https://github.com/wso2/product-ei/releases/download/v6.1.1-update9/wso2ei-6.1.1-update9.zip> . *Tasks/Bug Fixes and Improvements* https://github.com/wso2/product-ei/issues?=is%3Aissue%20milestone%3A6.1.1-update9%20is%3Aclosed *List of Open Issues* https://wso2.org/jira/issues/?filter=13994 https://github.com/wso2/product-ei/issues?q=is%3Aopen+is%3Aissue *Mailing Lists* Join our mailing lists and correspond with the developers directly. Developer List : dev@wso2.org | Subscribe | Mail Archive WSO2 Architecture List: architect...@wso2.org User Forum : StackOverflow *How To Contribute* Your feedback is most welcome! *Reporting Issues* We encourage you to report issues, improvements and feature requests regarding WSO2 Integrator through WSO2 EI GIT Issues. ~ The WSO2 Integration Team ~ -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Multiple receiver urls not supported in EI-6.1.1 Event Sink configuration
Hi Nirodha,
If this is an urgent, can you please create a Internal ticket. Anyway is
there any possibility to migrate to 6.2.0 M3 or wait for GA
Thanks,
Nuwanw
On Wed, Aug 30, 2017 at 1:06 AM, Nirodha Gallage <niro...@wso2.com> wrote:
> Any chance of getting it backported to 6.1.1?
>
> On Wed, Aug 30, 2017 at 11:27 AM, Manorama Perera <manor...@wso2.com>
> wrote:
>
>> Hi Nirodha,
>>
>> This bug is already reported at [1], and fixed[2] in EI 6.2.0 M3.
>>
>> [1] https://github.com/wso2/product-ei/issues/835
>> [2] https://github.com/wso2/carbon-mediation/pull/848
>>
>> Thanks,
>> Manorama
>>
>> On Wed, Aug 30, 2017 at 10:57 AM, Nirodha Gallage <niro...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> When creating Event Sink config in ESB 4.9.0 and ESB 5.0.0 it supported
>>> giving comma separated multiple Receiver URLs within curly braces,
>>>
>>> Eg: {tcp://192.168.56.168:7611,tcp://192.168.56.159:7611}
>>>
>>> But this is not supported in EI 6.1.1, and does not allow to save the
>>> config with an error "Incomplete URL or Invalid protocol.."
>>>
>>> Isn't it a bug? And is there any workaround for this?
>>>
>>> Regards,
>>> Nirodha
>>>
>>> --
>>>
>>> *Nirodha Gallage*
>>> Associate Technical Lead
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94716429078 <+94%2071%20642%209078>
>>>
>>
>>
>>
>> --
>> Manorama Perera
>> Software Engineer
>> WSO2, Inc.; http://wso2.com/
>>
>
>
>
> --
>
> *Nirodha Gallage*
> Associate Technical Lead
> WSO2 Inc.: http://wso2.com/
> Mobile: +94716429078 <071%20642%209078>
>
--
Nuwan Wimalasekara
Associate Technical Lead
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in Proxy service
Hi Lipsa, In your service configuration, You have enabled only https transport as the transport of the service. You have to either enable to http transport for the service or send the https request instead of http request from the client. Thanks, Nuwanw On Tue, Jun 20, 2017 at 10:56 AM, Lipsa Pradhan < lipsa.prad...@adnatesolutions.com> wrote: > Hello everyone, > > I had made a proxy service of one my dataservices. But I'm facing the > following error : > > > Expected transport is "https" but incoming > transport found : "http" > > > > How to resolve this? > > Regards > Lipsa Pradhan > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Accessing a secured wsdl when deploying a proxy service.
Hi all, We could implement to support accessing secured wsdl in both ways. Now the credentials can be defined with url itself or as a proxy service parameter. if the credentials are available, Every http request sends with the basic auth header to get the resource. 1) http://user:password@localhost:8282/securewsdl?wsdl"/> 2) http://localhost:8282/securewsdl?wsdl"/> YWRtaW46YWRtaW4= Thanks, Nuwanw On Mon, Mar 20, 2017 at 6:05 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote: > Hi all, > > When deploying a proxy service, WSDL can be defined with the parameter > publishWSDL. However if the WSDL is secured, ESB received a 401 error and > failed to deploy the proxy service. One thing we can do is that, we can add > a user name and parameter as below to access the basic auth secured > WSDL.(however below url is not working due to a minor bug in the code. Need > a fix to get it worked.). > > http://user:password@localhost:8282/securewsdl?wsdl"/> > > But again it failed to get access the wsdl when the wsdl contain secured > xsd imports. So a secured wsdl with secured xsd import can not be used in > ESB as a proxy service WSDL. > > There are two options we can improve the code ESB to get the scenario > working. > > 1) defined the wsdl url as bellow and get the username and password from > base url then add the Authorization header for all the xsd imports urls > when calling xsd references. > > http://user:password@localhost:8282/securewsdl?wsdl"/> > > *Limitation*: If we define the username and password as above, the > password can not be encrypt with secure vault as it become a malformed url > when creating the URL object. > > 2) Introduce a new parameter(wsdl.security.basicauth) to get the > Authorization header value and add the Authorization header when ever > making a http call for wsdl and xds references. > > Then we can encrypt the parameter for securing the given password. However > we have to implement securing proxy service parameters with wso2 secure > vault since it is not available with current implementation. > > Is there any other alternative to get above scenario working, appreciate > your thoughts. > > [1] https://wso2.org/jira/browse/ESBJAVA-5054 > > Thanks, > Nuwanw > > -- > Nuwan Wimalasekara > Associate Technical Lead > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > phone: +94 71 668 4620 <071%20668%204620> > > > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Accessing a secured wsdl when deploying a proxy service.
Hi all, When deploying a proxy service, WSDL can be defined with the parameter publishWSDL. However if the WSDL is secured, ESB received a 401 error and failed to deploy the proxy service. One thing we can do is that, we can add a user name and parameter as below to access the basic auth secured WSDL.(however below url is not working due to a minor bug in the code. Need a fix to get it worked.). http://user:password@localhost:8282/securewsdl?wsdl"/> But again it failed to get access the wsdl when the wsdl contain secured xsd imports. So a secured wsdl with secured xsd import can not be used in ESB as a proxy service WSDL. There are two options we can improve the code ESB to get the scenario working. 1) defined the wsdl url as bellow and get the username and password from base url then add the Authorization header for all the xsd imports urls when calling xsd references. http://user:password@localhost:8282/securewsdl?wsdl"/> *Limitation*: If we define the username and password as above, the password can not be encrypt with secure vault as it become a malformed url when creating the URL object. 2) Introduce a new parameter(wsdl.security.basicauth) to get the Authorization header value and add the Authorization header when ever making a http call for wsdl and xds references. Then we can encrypt the parameter for securing the given password. However we have to implement securing proxy service parameters with wso2 secure vault since it is not available with current implementation. Is there any other alternative to get above scenario working, appreciate your thoughts. [1] https://wso2.org/jira/browse/ESBJAVA-5054 Thanks, Nuwanw -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Integration tests for WSO2 IOT Server
ntimeException: Fail to start carbon server > at org.wso2.carbon.automation.extensions.servers.carbonserver.C > arbonServerExtension.handleException(CarbonServerExtension.java:70) > at org.wso2.carbon.automation.extensions.servers.carbonserver.C > arbonServerExtension.onExecutionStart(CarbonServerExtension.java:54) > ... 14 more > Caused by: java.lang.RuntimeException: Port 9763 is not open > at org.wso2.carbon.automation.extensions.servers.utils.ClientCo > nnectionUtil.waitForPort(ClientConnectionUtil.java:248) > at org.wso2.carbon.automation.extensions.servers.carbonserver.C > arbonServerManager.startServerUsingCarbonHome(CarbonServerMa > nager.java:120) > at org.wso2.carbon.automation.extensions.servers.carbonserver.T > estServerManager.startServer(TestServerManager.java:116) > at org.wso2.carbon.automation.extensions.servers.carbonserver.C > arbonServerExtension.onExecutionStart(CarbonServerExtension.java:50) > ... 14 more > > --- > > > Thanks and regards, > Menaka > > -- > *Menaka Jayawardena* > *Software Engineer - WSO2 Inc* > *Tel : 071 350 5470 <071%20350%205470>/ 071 885 1183 <071%20885%201183>* > *LinkedIn: https://lk.linkedin.com/in/menakajayawardena > <https://lk.linkedin.com/in/menakajayawardena>* > *Blog: https://menakamadushanka.wordpress.com/ > <https://menakamadushanka.wordpress.com/>* > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] carbon-mediation-4.6.9 Staged
Thanks Senduran On Sat, Dec 10, 2016 at 10:08 PM, Senduran Balasubramaniyam < sendu...@wso2.com> wrote: > Hi Nuwan et al., > > Carbon mediation 4.6.9 is released. > > Regards > Senduran > > > > On Sat, Dec 10, 2016 at 10:12 AM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Senduran, >> >> Can you please release >> >> Thanks, >> Nuwanw >> >> On Sat, Dec 10, 2016 at 9:31 AM, Heshitha Hettihewa <heshit...@wso2.com> >> wrote: >> >>> Hi Nuwan, >>> >>> I've tested XACML Mediator feature 4.6.9 and was able to install and run >>> the feature without issues. >>> >>> +1 for the release >>> >>> Thanks. >>> >>> On Fri, Dec 9, 2016 at 11:28 PM, Geesara Prathap <gees...@wso2.com> >>> wrote: >>> >>>> Hi Nuwan, >>>> >>>> I have tested the staged carbon-mediation-4.6.9 repo and it is stable >>>> and working fine. >>>> >>>> +1 for the release. >>>> >>>> Thanks, >>>> Geesara >>>> >>>> On Fri, Dec 9, 2016 at 10:03 PM, Nuwan Wimalasekara <nuw...@wso2.com> >>>> wrote: >>>> >>>>> Hi >>>>> >>>>> Please use the below url for repository >>>>> >>>>> [1] https://maven.wso2.org/nexus/content/repositories/orgwso >>>>> 2carbonmediation-1009 >>>>> >>>>> Thanks, >>>>> Nuwanw >>>>> >>>>> On Fri, Dec 9, 2016 at 5:29 PM, Nuwan Wimalasekara <nuw...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> Please find the staged carbon-mediation-4.6.9 at [1] >>>>>> >>>>>> [1] http://52.220.154.241:8081/nexus/content/repositories/or >>>>>> gwso2carbonmediation-1009 >>>>>> >>>>>> @Heshitha and Geesara >>>>>> >>>>>> Please test and confirm. >>>>>> >>>>>> Thanks, >>>>>> Nuwanw >>>>>> >>>>>> -- >>>>>> Nuwan Wimalasekara >>>>>> Associate Technical Lead >>>>>> WSO2, Inc.: http://wso2.com >>>>>> lean. enterprise. middleware >>>>>> >>>>>> phone: +94 71 668 4620 <071%20668%204620> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Nuwan Wimalasekara >>>>> Associate Technical Lead >>>>> WSO2, Inc.: http://wso2.com >>>>> lean. enterprise. middleware >>>>> >>>>> phone: +94 71 668 4620 <+94%2071%20668%204620> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Geesara Prathap Kulathunga >>>> Software Engineer >>>> WSO2 Inc; http://wso2.com >>>> Mobile : +940772684174 <+94%2077%20268%204174> >>>> >>>> >>> >>> >>> -- >>> Heshitha Hettihewa >>> *Software Engineer* >>> Mobile : +94716866386 >>> <%2B94%20%280%29%20773%20451194> >>> heshit...@wso2.com >>> >> >> >> >> -- >> Nuwan Wimalasekara >> Associate Technical Lead >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> phone: +94 71 668 4620 <+94%2071%20668%204620> >> >> >> >> > > > -- > *Senduran * > Senior Software Engineer, > WSO2, Inc.; http://wso2.com/ <http://wso2.com/> > Mobile: +94 77 952 6548 <077%20952%206548> > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] carbon-mediation-4.6.9 Staged
Hi Senduran, Can you please release Thanks, Nuwanw On Sat, Dec 10, 2016 at 9:31 AM, Heshitha Hettihewa <heshit...@wso2.com> wrote: > Hi Nuwan, > > I've tested XACML Mediator feature 4.6.9 and was able to install and run > the feature without issues. > > +1 for the release > > Thanks. > > On Fri, Dec 9, 2016 at 11:28 PM, Geesara Prathap <gees...@wso2.com> wrote: > >> Hi Nuwan, >> >> I have tested the staged carbon-mediation-4.6.9 repo and it is stable >> and working fine. >> >> +1 for the release. >> >> Thanks, >> Geesara >> >> On Fri, Dec 9, 2016 at 10:03 PM, Nuwan Wimalasekara <nuw...@wso2.com> >> wrote: >> >>> Hi >>> >>> Please use the below url for repository >>> >>> [1] https://maven.wso2.org/nexus/content/repositories/orgwso >>> 2carbonmediation-1009 >>> >>> Thanks, >>> Nuwanw >>> >>> On Fri, Dec 9, 2016 at 5:29 PM, Nuwan Wimalasekara <nuw...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> Please find the staged carbon-mediation-4.6.9 at [1] >>>> >>>> [1] http://52.220.154.241:8081/nexus/content/repositories/or >>>> gwso2carbonmediation-1009 >>>> >>>> @Heshitha and Geesara >>>> >>>> Please test and confirm. >>>> >>>> Thanks, >>>> Nuwanw >>>> >>>> -- >>>> Nuwan Wimalasekara >>>> Associate Technical Lead >>>> WSO2, Inc.: http://wso2.com >>>> lean. enterprise. middleware >>>> >>>> phone: +94 71 668 4620 <071%20668%204620> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Nuwan Wimalasekara >>> Associate Technical Lead >>> WSO2, Inc.: http://wso2.com >>> lean. enterprise. middleware >>> >>> phone: +94 71 668 4620 <+94%2071%20668%204620> >>> >>> >>> >>> >> >> >> -- >> Geesara Prathap Kulathunga >> Software Engineer >> WSO2 Inc; http://wso2.com >> Mobile : +940772684174 <+94%2077%20268%204174> >> >> > > > -- > Heshitha Hettihewa > *Software Engineer* > Mobile : +94716866386 > <%2B94%20%280%29%20773%20451194> > heshit...@wso2.com > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] carbon-mediation-4.6.9 Staged
Hi Please use the below url for repository [1] https://maven.wso2.org/nexus/content/repositories/orgwso2carbonmediation-1009 Thanks, Nuwanw On Fri, Dec 9, 2016 at 5:29 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote: > Hi All, > > Please find the staged carbon-mediation-4.6.9 at [1] > > [1] http://52.220.154.241:8081/nexus/content/repositories/ > orgwso2carbonmediation-1009 > > @Heshitha and Geesara > > Please test and confirm. > > Thanks, > Nuwanw > > -- > Nuwan Wimalasekara > Associate Technical Lead > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > phone: +94 71 668 4620 <071%20668%204620> > > > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] carbon-mediation-4.6.9 Staged
Hi All, Please find the staged carbon-mediation-4.6.9 at [1] [1] http://52.220.154.241:8081/nexus/content/repositories/orgwso2carbonmediation-1009 @Heshitha and Geesara Please test and confirm. Thanks, Nuwanw -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] carbon-mediation-4.6.8 Staged
Hi Senduran Can you please release the carbon-mediation 4.6.8 Thanks, Nuwanw On Thu, Dec 1, 2016 at 10:56 AM, Thilini Shanika <thili...@wso2.com> wrote: > Tested JSON Validator mediator with Guava and json-schema-validator orbit > upgrade [1] . Issues are not found > > +1 for release > > [1] https://wso2.org/jira/browse/APIMANAGER-5342 > > On Thu, Dec 1, 2016 at 10:27 AM, Chamila Adhikarinayake <chami...@wso2.com > > wrote: > >> Hi >> >> 1. Validated the regression issue[1] >> 2. Build APIM 2.1.0-Snapshot with integration tests. >> >> No issues found. +1 for release >> >> [1] https://wso2.org/jira/browse/APIMANAGER-5489 >> >> Chamila >> >> On Wed, Nov 30, 2016 at 5:57 PM, Nuwan Dias <nuw...@wso2.com> wrote: >> >>> Thanks. >>> >>> On Wed, Nov 30, 2016 at 4:44 PM, Nuwan Wimalasekara <nuw...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> Please find the staged carbon-mediation-4.6.8 at [1] >>>> >>>> >>>> [1] https://maven.wso2.org/nexus/content/repositories/orgwso >>>> 2carbonmediation-1009 >>>> >>>> Thanks, >>>> Nuwanw >>>> >>>> -- >>>> Nuwan Wimalasekara >>>> Associate Technical Lead >>>> WSO2, Inc.: http://wso2.com >>>> lean. enterprise. middleware >>>> >>>> phone: +94 71 668 4620 <+94%2071%20668%204620> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Software Architect - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 <+94%2077%20777%205729> >>> >> >> >> >> -- >> Regards, >> Chamila Adhikarinayake >> Software Engineer >> WSO2, Inc. >> Mobile - +94712346437 <+94%2071%20234%206437> >> Email - chami...@wso2.com >> Blog - http://helpfromadhi.blogspot.com/ >> > > > > -- > Thilini Shanika > Senior Software Engineer > WSO2, Inc.; http://wso2.com > 20, Palmgrove Avenue, Colombo 3 > > E-mail: tgtshan...@gmail.com > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] carbon-mediation-4.6.8 Staged
Hi All, Please find the staged carbon-mediation-4.6.8 at [1] [1] https://maven.wso2.org/nexus/content/repositories/orgwso2carbonmediation-1009 Thanks, Nuwanw -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] - Upgrade Google Guava version in Carbon-mediation
Hi Thilini, Guava is used by JSON Schema Validator mediator and It need to be tested with guava version 18. Thanks, Nuwanw On Fri, Nov 25, 2016 at 1:46 PM, Thilini Shanika <thili...@wso2.com> wrote: > Hi ESB Team, > > In order to get rid of Guava version conflicts in APIM, we need to upgrade > the guava version (version 15 to version 18) shift with carbon-mediation. > > Can you please review and merge PR[1] > > [1] - https://github.com/wso2/carbon-mediation/pull/760/files > > Thanks > > -- > Thilini Shanika > Senior Software Engineer > WSO2, Inc.; http://wso2.com > 20, Palmgrove Avenue, Colombo 3 > > E-mail: tgtshan...@gmail.com > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unable to add Respond mediator inside Aggregate mediator in the Out sequence
Hi Niranjan, Can you please try putting respond mediator after the aggregate mediator. You can use send mediator as well instead of respond mediator. .. . Thanks, Nuwans On Sat, Nov 5, 2016 at 7:17 PM, Niranjan Karunanandham <niran...@wso2.com> wrote: > Hi Nuwan, > > Thanks for the prompt reply. Please find my inline comments below. > > On Sat, Nov 5, 2016 at 6:02 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Niranjan, >> >> Once you put a respond mediator, the message send back to client and >> mediation should be stopped. So having mediators after respond will be not >> executed. if you need to call the back end service agin, use call mediator >> and finally call the respond where the message send back to client. >> > Yes, I am using the respond mediator at the end. This works fine if I > create using the UI. But when I try to do it using the Dev studio, I get > this error. It always me to save, but when I reopen this file, I get the > above said Warning message and it also removes the code. So even though it > is a warning, it is changing the actual code. This is the code: > > > > > > >xmlns:n="http://www.wso2.org/brs/sample/; > xmlns:ns3="http://org.apache.synapse/xsd; xmlns:soapenv=" > http://www.w3.org/2003/05/soap-envelope;> > > > > > > > > > > > > > > > Also if I put this into a sequence and refer it in the out sequence then > it does not work (if I do this via the Dev Studio). But if i do this via > the UI, it works. Is this a bug? > > >> >> In Developer studio, It is a validation because no point of having >> mediator after respond. But we do not have such a validation in proxy >> service UI. >> > But even thou it shows as warning, it removes some of the code (actually > the respond mediator tag and also some logic inside the aggregate mediator > is also lost) :( > >> >> Thanks, >> Nuwanw >> >> On Sat, Nov 5, 2016 at 3:34 PM, Niranjan Karunanandham <niran...@wso2.com >> > wrote: >> >>> Hi ESB, >>> >>> My requirement is to aggregate the data in the Out sequence and send it >>> to a backend. The payload received from the backend needs to be send back >>> to the client. I am able to do this using a proxy service in the UI. But >>> when I try to do this using Developer Studio 3.8.0, I get the following >>> error: >>> *"Warning! Reason: Not allow to add mediators after a Respond Mediator"* >>> >>> Any why this is allowed via the UI, but not by Developer Studio? >>> >>> Regards, >>> Nira >>> -- >>> >>> >>> *Niranjan Karunanandham* >>> Associate Technical Lead - WSO2 Inc. >>> WSO2 Inc.: http://www.wso2.com >>> >>> >> >> >> -- >> Nuwan Wimalasekara >> Associate Technical Lead >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> phone: +94 71 668 4620 >> >> >> >> > Regards, > Nira > > -- > > > *Niranjan Karunanandham* > Associate Technical Lead - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unable to add Respond mediator inside Aggregate mediator in the Out sequence
Hi Niranjan, Once you put a respond mediator, the message send back to client and mediation should be stopped. So having mediators after respond will be not executed. if you need to call the back end service agin, use call mediator and finally call the respond where the message send back to client. In Developer studio, It is a validation because no point of having mediator after respond. But we do not have such a validation in proxy service UI. Thanks, Nuwanw On Sat, Nov 5, 2016 at 3:34 PM, Niranjan Karunanandham <niran...@wso2.com> wrote: > Hi ESB, > > My requirement is to aggregate the data in the Out sequence and send it to > a backend. The payload received from the backend needs to be send back to > the client. I am able to do this using a proxy service in the UI. But when > I try to do this using Developer Studio 3.8.0, I get the following error: > *"Warning! Reason: Not allow to add mediators after a Respond Mediator"* > > Any why this is allowed via the UI, but not by Developer Studio? > > Regards, > Nira > -- > > > *Niranjan Karunanandham* > Associate Technical Lead - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Support multiple Set-Cookie header in Integration Server
Hi In our code, We are using a map to keep the headers. Even if there are multiple headers with same name with the incoming request, We only keep one. As the design we are unable to handle the multiple headers with same name at the moment. However HttpMessage received from netty includes all the headers and it keep multiple headers with same name since it use java.util.LinkedList to keep the headers. So we also should use List to support multiple header with same name and be careful when adding and updating the headers. Because we have to check whether It is a new header or updating the existing header Is there any intentional reason to use map in keeping the herders. Appreciate your thought on this [1] https://wso2.org/jira/browse/CTRANSPORT-10 Thanks, Nuwanw -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC4
Hi all. Tested and verified following - ESB Mediation Debugging [+] Stable - go ahead and release. Thanks, Nuwnaw On Fri, Aug 19, 2016 at 12:21 PM, Prabath Ariyarathna <prabat...@wso2.com> wrote: > Hi All. > > Tested and verified following. > >- File(VFS) Inbound Endpoint. >- HTTP/HTTPS Inbound Endpoints. >- Custom Inbound Endpoint. >- RabbitMQ Inbound Endpoint. > > [+] Stable - go ahead and release. > > Thanks. > > On Fri, Aug 19, 2016 at 11:30 AM, Nadeeshaan Gunasinghe < > nadeesh...@wso2.com> wrote: > >> Hi all, >> >> Tested the following, >> >> >>- Inbound Endpoints >> VFS, HTTP, HTTPS, WSO2 MB, JMS >>- JMS scenarios >> Message Processor, Message Store with ActiveMQ, Rabbit MQ and >>WSO2 MB >>- Capp Deployment through tooling >> >> [+] Stable - go ahead and release >> >> Thanks, >> >> *Nadeeshaan Gunasinghe* >> Software Engineer, WSO2 Inc. http://wso2.com >> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe >> <#m_7132569658457042904_m_5569028783450022843_> >> <http://www.facebook.com/nadeeshaan.gunasinghe> >> <http://lk.linkedin.com/in/nadeeshaan> <http://twitter.com/Nadeeshaan> >> <http://nadeeshaan.blogspot.com/> >> Get a signature like this: Click here! >> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==155679456732825> >> >> On Wed, Aug 17, 2016 at 8:13 AM, Senduran Balasubramaniyam < >> sendu...@wso2.com> wrote: >> >>> Hi All, >>> >>> This is the 4th Release Candidate of WSO2 Enterprise Service Bus 5.0.0 >>> >>> Please download, test the product and vote. Vote will be open for 72 >>> hours or as needed. >>> >>> Source and distribution >>> >>> Run-time: https://github.com/wso2/produc >>> t-esb/releases/tag/v5.0.0-rc4 >>> Tooling : https://github.com/wso2/devstu >>> dio-tooling-esb/releases/tag/v5.0.0-rc4 >>> Analytics: https://github.com/wso2/analyt >>> ics-esb/releases/tag/v5.0.0-rc4 >>> >>> Please vote as follows. >>> [+] Stable - go ahead and release >>> [-] Broken - do not release (explain why) >>> >>> Thanks, >>> - WSO2 ESB Team - >>> >>> -- >>> *Senduran * >>> Senior Software Engineer, >>> WSO2, Inc.; http://wso2.com/ <http://wso2.com/> >>> Mobile: +94 77 952 6548 >>> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > *Prabath Ariyarathna* > > *Associate Technical Lead* > > *WSO2, Inc. * > > *lean . enterprise . middleware * > > > *Email: prabat...@wso2.com <prabat...@wso2.com>* > > *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>* > > *Flicker : https://www.flickr.com/photos/47759189@N08 > <https://www.flickr.com/photos/47759189@N08>* > > *Mobile: +94 77 699 4730 * > > > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Supporting registry based parameter values in all Inbound Endpoints
Hi Gayan, Please refer the documentation[1] for how to secure the parameters using secure vault. [1] https://docs.wso2.com/display/ESB500/Working+with+Passwords Thanks, Nuwanw On Sat, Aug 13, 2016 at 8:35 AM, Chanaka Fernando <chana...@wso2.com> wrote: > Please refer [1]. > > [1] https://wso2.org/jira/browse/ESBJAVA-4715 > > On Sat, Aug 13, 2016 at 12:04 AM, Gayan Gunarathne <gay...@wso2.com> > wrote: > >> Are we support to use inbound endpoints with secure vault based >> parameters in ESB 5.0.0? If then could you please share some pointers how >> to use that? >> >> Thanks, >> Gayan >> >> On Tue, Jun 28, 2016 at 5:31 PM, Kasun Indrasiri <ka...@wso2.com> wrote: >> >>> The other aspect is the outbound side. For instance, for outbound >>> messaging we don't have a way to retries credentials from ESB secure vault? >>> >>> On Tue, Jun 21, 2016 at 10:20 AM, Kasun Indrasiri <ka...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> $subject is quite important when it comes to developing inbound >>>> endpoints and bind them to specific environments (with the use of registry >>>> key values paris). Also, at the same time we need to get this integrated to >>>> secure vault based parameters which are encrypted. >>>> >>>> Thanks, >>>> Kasun >>>> >>>> -- >>>> Kasun Indrasiri >>>> Software Architect >>>> WSO2, Inc.; http://wso2.com >>>> lean.enterprise.middleware >>>> >>>> cell: +94 77 556 5206 >>>> Blog : http://kasunpanorama.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> Gayan Gunarathne >> Technical Lead, WSO2 Inc. (http://wso2.com) >> Committer & PMC Member, Apache Stratos >> email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985> >> >> >> > > > > -- > Thank you and Best Regards, > Chanaka Fernando > Senior Technical Lead > m: +94 773337238 > https://wso2.com <https://wso2.com/signature> > > > > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Supporting secure vault capability in all Inbound Endpoint parameters
Hi
In ESB 5.0.0, wso2:vault-lookup('alias') expression can be used in all
inbound endpoint parameters. even in registry resource text, valut-lookup()
expression can be used and set resource as the parameter value.
Parameter value need to be encrypted and store with a alias and retrieve
the actual value in your ESB inbound configuration as below
{wso2:vault-lookup('my.password')}
OR
[1] https://wso2.org/jira/browse/ESBJAVA-4715
[2] https://github.com/wso2/wso2-synapse/pull/608
Thanks,
Nuwanw
--
Nuwan Wimalasekara
Associate Technical Lead
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] encodeURIComponent is not working in ESB-BETA
299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
>> "1d5[\r][\n]"
>> [2016-06-23 20:19:16,300] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
>> "{"map":{"timestamp":"2016-06-23
>> 14:49:15Z","error":"invalid_request","error_codes":{"myArrayList":[90014]},"trace_id":"7df362a8-c56d-401d-b654-93ecd331fbdd","error_description":"AADSTS90014:
>> The request body must contain the following parameter:
>> \u0027grant_type\u0027.\r\nTrace ID:
>> 7df362a8-c56d-401d-b654-93ecd331fbdd\r\nCorrelation ID:
>> a6c86ecc-59ce-49b0-b074-07c3be2b10fb\r\nTimestamp: 2016-06-23
>> 14:49:15Z","correlation_id":"a6c86ecc-59ce-49b0-b074-07c3be2b10fb"}}[\r][\n]"
>> [2016-06-23 20:19:16,300] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
>> "0[\r][\n]"
>> [2016-06-23 20:19:16,300] INFO
>> {org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
>> [2016-06-23 20:19:16,299] DEBUG - wire HTTP-Listener I/O dispatcher-1 <<
>> "[\r][\n]"
>> [2016-06-23 20:19:16,308] ERROR
>> {org.wso2.carbon.automation.core.PlatformTestManager} - On Test failure..
>> [2016-06-23 20:19:16,308] ERROR
>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>> org.json.JSONException: JSONObject["token_type"] not found.
>> [2016-06-23 20:19:16,308] INFO
>> {org.wso2.carbon.automation.core.PlatformTestManager} -
>> --Tests Failed
>> org.wso2.carbon.connector.integration.test.powerbi.PowerbiConnectorIntegrationTest.testGetAccessTokenFromAuthorizationCode
>>
>> [2] -
>> https://github.com/wso2-extensions/esb-connector-powerbi/blob/master/src/main/resources/powerbi-config/getAccessTokenFromAuthorizationCode.xml#L47
>> --
>>
>>
>> *Thank you and Regards**Hariprasath Thanarajah*
>> Associate Software Engineer | WSO2
>> E: haripras...@wso2.com
>> M: +94752806528, 0777216903
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>
--
Nuwan Wimalasekara
Associate Technical Lead
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AppM] [GW] Message body of the response getting dropped in tenant mode
gt; curl/7.43.0[\r][\n]" >>> [2016-06-18 15:46:33,075] DEBUG - wire >> "Accept: */*[\r][\n]" >>> [2016-06-18 15:46:33,075] DEBUG - wire >> "[\r][\n]" >>> [2016-06-18 15:46:33,303] DEBUG - wire << "GET /file/ HTTP/1.1[\r][\n]" >>> [2016-06-18 15:46:33,304] DEBUG - wire << "Accept: */*[\r][\n]" >>> [2016-06-18 15:46:33,304] DEBUG - wire << "Host: localhost:9763[\r][\n]" >>> [2016-06-18 15:46:33,305] DEBUG - wire << "Connection: >>> Keep-Alive[\r][\n]" >>> [2016-06-18 15:46:33,305] DEBUG - wire << "User-Agent: >>> Synapse-PT-HttpComponents-NIO[\r][\n]" >>> [2016-06-18 15:46:33,306] DEBUG - wire << "[\r][\n]" >>> [2016-06-18 15:46:33,307] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]" >>> [2016-06-18 15:46:33,307] DEBUG - wire >> "Content-Type: >>> text/html[\r][\n]" >>> [2016-06-18 15:46:33,308] DEBUG - wire >> "Content-Length: 193[\r][\n]" >>> [2016-06-18 15:46:33,308] DEBUG - wire >> "Date: Sat, 18 Jun 2016 >>> 10:16:33 GMT[\r][\n]" >>> [2016-06-18 15:46:33,309] DEBUG - wire >> "Server: WSO2 Carbon >>> Server[\r][\n]" >>> [2016-06-18 15:46:33,309] DEBUG - wire >> "[\r][\n]" >>> [2016-06-18 15:46:33,310] DEBUG - wire >> ">> action="upload.jag" name="submit" enctype="multipart/form-data">[\n]" >>> [2016-06-18 15:46:33,310] DEBUG - wire >> " >> name="myfile">[\n]" >>> [2016-06-18 15:46:33,311] DEBUG - wire >> " >> name="submit" value="Submit">[\n]" >>> [2016-06-18 15:46:33,312] DEBUG - wire >> "" >>> [2016-06-18 15:46:33,322] DEBUG - wire << "HTTP/1.1 200 OK[\r][\n]" >>> [2016-06-18 15:46:33,323] DEBUG - wire << "Content-Type: >>> text/html[\r][\n]" >>> [2016-06-18 15:46:33,323] DEBUG - wire << "Date: Sat, 18 Jun 2016 >>> 10:16:33 GMT[\r][\n]" >>> [2016-06-18 15:46:33,324] DEBUG - wire << "Transfer-Encoding: >>> chunked[\r][\n]" >>> [2016-06-18 15:46:33,324] DEBUG - wire << "[\r][\n]" >>> [2016-06-18 15:46:33,324] DEBUG - wire << "c1[\r][\n]" >>> [2016-06-18 15:46:33,325] DEBUG - wire << ">> action="upload.jag" name="submit" enctype="multipart/form-data">[\n]" >>> [2016-06-18 15:46:33,325] DEBUG - wire << " >> name="myfile">[\n]" >>> [2016-06-18 15:46:33,325] DEBUG - wire << " >> name="submit" value="Submit">[\n]" >>> [2016-06-18 15:46:33,326] DEBUG - wire << "[\r][\n]" >>> [2016-06-18 15:46:33,326] DEBUG - wire << "0[\r][\n]" >>> [2016-06-18 15:46:33,327] DEBUG - wire << "[\r][\n]" >>> >>> Regards, >>> Dinusha. >>> >>> >>> -- >>> Dinusha Dilrukshi >>> Associate Technical Lead >>> WSO2 Inc.: http://wso2.com/ >>> Mobile: +94725255071 >>> Blog: http://dinushasblog.blogspot.com/ >>> >> >> >> >> -- >> *Best Regards* >> >> *Rushmin Fernando* >> *Technical Lead* >> >> WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware >> >> mobile : +94772891266 >> >> >> > > > -- > 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 > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Removing only a jar file inside a patch directory will not reflected on patch applying process
Hi I know this is not a major issue. In the initial mail, I have mentioned that removing a jar file from a patch directory is not a good practise and there is a workaround too. But mistakenly doing this will make confusion in patch applying process. User thinks the jar is reverted. but actually it is not. Created a JIRA to track there is such a behaviour and we can prioritise whether we need to fix it or not. Thanks, Nuwanw On Wed, Jun 8, 2016 at 1:35 PM, Kishanthan Thangarajah <kishant...@wso2.com> wrote: > I don't think this a major issue to fix. Normally if you apply a patch, > you don't partially remove some jars from the patch directory as if you are > trying to update a patch. Either you remove that patch completely or apply > a new patch. IMO there is no concept of updating a patch rather you update > your system with a patch. > > On Wed, Jun 8, 2016 at 6:55 AM, Niranjan Karunanandham <niran...@wso2.com> > wrote: > >> Hi Nuwan, >> >> As per the logic in [1], when the jar is removed, the patches are not >> updated. But as mentioned by you, as a solution we can revert the jar by >> removing the patch directory and restarting the server. >> >> [1] - >> https://github.com/wso2/carbon-kernel/blob/v4.4.5/core/org.wso2.carbon.server/src/main/java/org/wso2/carbon/server/extensions/PatchInstaller.java >> >> Regards, >> Nira >> >> On Tue, Jun 7, 2016 at 7:22 PM, Nuwan Wimalasekara <nuw...@wso2.com> >> wrote: >> >>> Hi, >>> >>> Seems this is a bug. reported a JIRA[1] to track the issue further. >>> >>> [1] https://wso2.org/jira/browse/CARBON-15939 >>> >>> Thanks, >>> Nuwanw >>> >>> On Wed, Jun 1, 2016 at 12:21 PM, Nuwan Wimalasekara <nuw...@wso2.com> >>> wrote: >>> >>>> Hi Manoj, >>>> >>>> Yes. Even if the jar is removed, plugin directory has the same md5 >>>> value of removed jar. means It is not reverted. >>>> >>>> To revert the jar, we have to remove the patch directory and restart >>>> the server. >>>> >>>> Thanks, >>>> Nuwanw >>>> >>>> On Wed, Jun 1, 2016 at 12:03 PM, Manoj Kumara <ma...@wso2.com> wrote: >>>> >>>>> During patch application it validate the md5sum's of the jars as well. >>>>> Can you please verify the removed jar has a different md5 value from >>>>> what's >>>>> there in the server ? >>>>> >>>>> *Manoj Kumara* >>>>> WSO2 Inc. *| **lean. enterprise. middleware.* >>>>> *Mobile:* +94 713 448188 >>>>> >>>>> On Wed, Jun 1, 2016 at 11:53 AM, Nuwan Wimalasekara <nuw...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Carbon Team, >>>>>> >>>>>> I have observed $subject when I try to remove a jar file from patch >>>>>> directory. I know removing a jar file from patch directory is not a good >>>>>> practise when applying patches. But it may happen and then the behaviour >>>>>> is >>>>>> confusing. However if we update the a jar file inside a patch , it will >>>>>> reflect and update the plugins directory and works as expected. >>>>>> >>>>>> To reproduce the issue, we can apply a patch having two jar file and >>>>>> restart the server. Then it will apply the patch. after that, remove one >>>>>> of >>>>>> jar file in the patch directory and restart the server. The it will not >>>>>> detect as a patch change and will not revert the removed jar from >>>>>> patch. >>>>>> >>>>>> Is this a limitation in patch applying process or bug? >>>>>> >>>>>> Thanks, >>>>>> Nuwanw >>>>>> >>>>>> -- >>>>>> Nuwan Wimalasekara >>>>>> Senior Software Engineer - Test Automation >>>>>> WSO2, Inc.: http://wso2.com >>>>>> lean. enterprise. middleware >>>>>> >>>>>> phone: +94 71 668 4620 >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Wimalasekara >>>> Senior Software Engineer - Test Automation >>>> WSO2, Inc.: http://wso2.com >>>> lean. enterprise. middleware >>>> >>>> phone: +94 71 668 4620 >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Nuwan Wimalasekara >>> Associate Technical Lead >>> WSO2, Inc.: http://wso2.com >>> lean. enterprise. middleware >>> >>> phone: +94 71 668 4620 >>> >>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> >> *Niranjan Karunanandham* >> Associate Technical Lead - WSO2 Inc. >> WSO2 Inc.: http://www.wso2.com >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Kishanthan Thangarajah* > Technical Lead, > Platform Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* > Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Removing only a jar file inside a patch directory will not reflected on patch applying process
Hi, Seems this is a bug. reported a JIRA[1] to track the issue further. [1] https://wso2.org/jira/browse/CARBON-15939 Thanks, Nuwanw On Wed, Jun 1, 2016 at 12:21 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote: > Hi Manoj, > > Yes. Even if the jar is removed, plugin directory has the same md5 value > of removed jar. means It is not reverted. > > To revert the jar, we have to remove the patch directory and restart the > server. > > Thanks, > Nuwanw > > On Wed, Jun 1, 2016 at 12:03 PM, Manoj Kumara <ma...@wso2.com> wrote: > >> During patch application it validate the md5sum's of the jars as well. >> Can you please verify the removed jar has a different md5 value from what's >> there in the server ? >> >> *Manoj Kumara* >> WSO2 Inc. *| **lean. enterprise. middleware.* >> *Mobile:* +94 713 448188 >> >> On Wed, Jun 1, 2016 at 11:53 AM, Nuwan Wimalasekara <nuw...@wso2.com> >> wrote: >> >>> Hi Carbon Team, >>> >>> I have observed $subject when I try to remove a jar file from patch >>> directory. I know removing a jar file from patch directory is not a good >>> practise when applying patches. But it may happen and then the behaviour is >>> confusing. However if we update the a jar file inside a patch , it will >>> reflect and update the plugins directory and works as expected. >>> >>> To reproduce the issue, we can apply a patch having two jar file and >>> restart the server. Then it will apply the patch. after that, remove one of >>> jar file in the patch directory and restart the server. The it will not >>> detect as a patch change and will not revert the removed jar from patch. >>> >>> Is this a limitation in patch applying process or bug? >>> >>> Thanks, >>> Nuwanw >>> >>> -- >>> Nuwan Wimalasekara >>> Senior Software Engineer - Test Automation >>> WSO2, Inc.: http://wso2.com >>> lean. enterprise. middleware >>> >>> phone: +94 71 668 4620 >>> >>> >>> >>> >> > > > -- > Nuwan Wimalasekara > Senior Software Engineer - Test Automation > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > phone: +94 71 668 4620 > > > > -- Nuwan Wimalasekara Associate Technical Lead WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Removing only a jar file inside a patch directory will not reflected on patch applying process
Hi Manoj, Yes. Even if the jar is removed, plugin directory has the same md5 value of removed jar. means It is not reverted. To revert the jar, we have to remove the patch directory and restart the server. Thanks, Nuwanw On Wed, Jun 1, 2016 at 12:03 PM, Manoj Kumara <ma...@wso2.com> wrote: > During patch application it validate the md5sum's of the jars as well. Can > you please verify the removed jar has a different md5 value from what's > there in the server ? > > *Manoj Kumara* > WSO2 Inc. *| **lean. enterprise. middleware.* > *Mobile:* +94 713 448188 > > On Wed, Jun 1, 2016 at 11:53 AM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Carbon Team, >> >> I have observed $subject when I try to remove a jar file from patch >> directory. I know removing a jar file from patch directory is not a good >> practise when applying patches. But it may happen and then the behaviour is >> confusing. However if we update the a jar file inside a patch , it will >> reflect and update the plugins directory and works as expected. >> >> To reproduce the issue, we can apply a patch having two jar file and >> restart the server. Then it will apply the patch. after that, remove one of >> jar file in the patch directory and restart the server. The it will not >> detect as a patch change and will not revert the removed jar from patch. >> >> Is this a limitation in patch applying process or bug? >> >> Thanks, >> Nuwanw >> >> -- >> Nuwan Wimalasekara >> Senior Software Engineer - Test Automation >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> phone: +94 71 668 4620 >> >> >> >> > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Removing only a jar file inside a patch directory will not reflected on patch applying process
Hi Carbon Team, I have observed $subject when I try to remove a jar file from patch directory. I know removing a jar file from patch directory is not a good practise when applying patches. But it may happen and then the behaviour is confusing. However if we update the a jar file inside a patch , it will reflect and update the plugins directory and works as expected. To reproduce the issue, we can apply a patch having two jar file and restart the server. Then it will apply the patch. after that, remove one of jar file in the patch directory and restart the server. The it will not detect as a patch change and will not revert the removed jar from patch. Is this a limitation in patch applying process or bug? Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter
Hi Dilshani, Which ESB version are you using to test this scenario. Can you please check this on ESB 5.0.0-BETA pack? I could not observe such a behaviour in ESB 5.0.0-BETA. Thanks, Nuwanw On Thu, May 26, 2016 at 2:50 PM, Dilshani Subasinghe <dilsh...@wso2.com> wrote: > Hi Nuwan, > > Thank you for your response. I tried with both > > > *java.naming.provider.url=failover:tcp://localhost:61616, and * > > > *java.naming.provider.url=failover:(tcp://localhost:61616).* > But still missing messages. > > Regards, > Dilshani > > > On Thu, May 26, 2016 at 2:15 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Dilshani, >> >> >> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe <dilsh...@wso2.com> >> wrote: >> >>> Hi Nuwan, >>> >>> Yes I configured jms url with failover. Actually I used failover syntax >>> as u asked me to change >>> (java.naming.provider.url=failover:(tcp://localhost:61616) or >>> java.naming.provider.url=failover:tcp://localhost:61616) >>> >>> Proxy config: >>> >>> >> uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> *java.naming.provider.url=failover:tcp://localhost:61616* >>> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/> >>> >> >> >>> >>> I'm really sorry I didn't get your suggestion. Can you point out the >>> error within my config? >>> >> The problem in your config is , that there is no '*,*' at the end of >> the url. >> It should be as bellow. >> >> *java.naming.provider.url=failover:tcp://localhost:61616,* >> >> New Config: >> > uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory >> *java.naming.provider.url=failover:tcp://localhost:61616,* >> transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/> >> >> Thanks, >> Nuwanw >> >> >> >>> Regards, >>> Dilshani >>> >>> >>> On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara <nuw...@wso2.com> >>> wrote: >>> >>>> Hi Dilshani, >>>> >>>> In your proxy config, you have defined a jms url with failover. Can >>>> you please try the failover url syntax as one of bellow. I think it is due >>>> to invalid url definition of failover for ActiveMQ. >>>> >>>> Please refer[1] for failover url syntax in ActiveMQ >>>> >>>> java.naming.provider.url=failover:(tcp://localhost:61616) or >>>> java.naming.provider.url=failover:tcp://localhost:61616, >>>> >>>> [1] http://activemq.apache.org/failover-transport-reference.html >>>> >>>> Thanks, >>>> Nuwanw >>>> >>>> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe < >>>> dilsh...@wso2.com> wrote: >>>> >>>>> Hi ESB Team, >>>>> >>>>> I am testing JMS parameters and identified scenario of missing >>>>> messages when using "transport.Transactionality" parameter. >>>>> >>>>> Configured axis2.xml as follows; >>>>> >>>>> >>>> class="org.apache.axis2.transport.jms.JMSListener"> >>>>> >>>>> >>>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>>>> >>>> locked="false">failover:tcp://localhost:61616 >>>>> >>>> name="transport.jms.ConnectionFactoryJNDIName" >>>>> locked="false">TopicConnectionFactory >>>>> >>>> locked="false">topic >>>>> >>>> locked="false">topic >>>>> >>>>> * >>>> locked="false">local>>>> name="transport.jms.SessionTransacted" locked="false">true* >>>>> >>>>> >>>>> >>>>> >>>> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory
Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter
Hi Dilshani, On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe <dilsh...@wso2.com> wrote: > Hi Nuwan, > > Yes I configured jms url with failover. Actually I used failover syntax as > u asked me to change > (java.naming.provider.url=failover:(tcp://localhost:61616) or > java.naming.provider.url=failover:tcp://localhost:61616) > > Proxy config: > > uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory > *java.naming.provider.url=failover:tcp://localhost:61616* > transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/> > > > I'm really sorry I didn't get your suggestion. Can you point out the error > within my config? > The problem in your config is , that there is no '*,*' at the end of the url. It should be as bellow. *java.naming.provider.url=failover:tcp://localhost:61616,* New Config: Thanks, Nuwanw > Regards, > Dilshani > > > On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Dilshani, >> >> In your proxy config, you have defined a jms url with failover. Can you >> please try the failover url syntax as one of bellow. I think it is due to >> invalid url definition of failover for ActiveMQ. >> >> Please refer[1] for failover url syntax in ActiveMQ >> >> java.naming.provider.url=failover:(tcp://localhost:61616) or >> java.naming.provider.url=failover:tcp://localhost:61616, >> >> [1] http://activemq.apache.org/failover-transport-reference.html >> >> Thanks, >> Nuwanw >> >> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <dilsh...@wso2.com> >> wrote: >> >>> Hi ESB Team, >>> >>> I am testing JMS parameters and identified scenario of missing messages >>> when using "transport.Transactionality" parameter. >>> >>> Configured axis2.xml as follows; >>> >>> >> class="org.apache.axis2.transport.jms.JMSListener"> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName" >>> locked="false">TopicConnectionFactory >>> >> locked="false">topic >>> >> locked="false">topic >>> >>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true* >>> >>> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName" >>> locked="false">QueueConnectionFactory >>> >> locked="false">queue >>> >>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true* >>> >>> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName" >>> locked="false">TopicConnectionFactory >>> >> locked="false">topic >>> >> locked="false">topic >>> >>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true* >>> >>> >>> >>> And aslo added same parameters to JMS sender too. >>> >>> >> class="org.apache.axis2.transport.jms.JMSSender"> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName"
Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter
Hi Dilshani, Can you please try below endpoint config and see whether all the messages are delivering properly. Thanks, Nuwanw On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe <dilsh...@wso2.com> wrote: > Hi Nuwan, > > Yes I configured jms url with failover. Actually I used failover syntax as > u asked me to change > (java.naming.provider.url=failover:(tcp://localhost:61616) or > java.naming.provider.url=failover:tcp://localhost:61616) > > Proxy config: > > uri="jms:/MyQueue?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory > *java.naming.provider.url=failover:tcp://localhost:61616* > transport.jms.DestinationType=queuetransport.jms.SessionTransacted=truetransport.Transactionality=local"/> > > I'm really sorry I didn't get your suggestion. Can you point out the error > within my config? > > Regards, > Dilshani > > > On Thu, May 26, 2016 at 1:01 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Dilshani, >> >> In your proxy config, you have defined a jms url with failover. Can you >> please try the failover url syntax as one of bellow. I think it is due to >> invalid url definition of failover for ActiveMQ. >> >> Please refer[1] for failover url syntax in ActiveMQ >> >> java.naming.provider.url=failover:(tcp://localhost:61616) or >> java.naming.provider.url=failover:tcp://localhost:61616, >> >> [1] http://activemq.apache.org/failover-transport-reference.html >> >> Thanks, >> Nuwanw >> >> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <dilsh...@wso2.com> >> wrote: >> >>> Hi ESB Team, >>> >>> I am testing JMS parameters and identified scenario of missing messages >>> when using "transport.Transactionality" parameter. >>> >>> Configured axis2.xml as follows; >>> >>> >> class="org.apache.axis2.transport.jms.JMSListener"> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName" >>> locked="false">TopicConnectionFactory >>> >> locked="false">topic >>> >> locked="false">topic >>> >>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true* >>> >>> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName" >>> locked="false">QueueConnectionFactory >>> >> locked="false">queue >>> >>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true* >>> >>> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName" >>> locked="false">TopicConnectionFactory >>> >> locked="false">topic >>> >> locked="false">topic >>> >>> * >> locked="false">local>> name="transport.jms.SessionTransacted" locked="false">true* >>> >>> >>> >>> And aslo added same parameters to JMS sender too. >>> >>> >> class="org.apache.axis2.transport.jms.JMSSender"> >>> >>> >> locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory >>> >> locked="false">failover:tcp://localhost:61616 >>> >> name="transport.jms.ConnectionFactoryJNDIName" >>> locked="false">TopicConnectionFactory >>>
Re: [Dev] [ESB][JMS] Missing messages when using "transport.Transactionality" parameter
Hi Dilshani, In your proxy config, you have defined a jms url with failover. Can you please try the failover url syntax as one of bellow. I think it is due to invalid url definition of failover for ActiveMQ. Please refer[1] for failover url syntax in ActiveMQ java.naming.provider.url=failover:(tcp://localhost:61616) or java.naming.provider.url=failover:tcp://localhost:61616, [1] http://activemq.apache.org/failover-transport-reference.html Thanks, Nuwanw On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <dilsh...@wso2.com> wrote: > Hi ESB Team, > > I am testing JMS parameters and identified scenario of missing messages > when using "transport.Transactionality" parameter. > > Configured axis2.xml as follows; > >class="org.apache.axis2.transport.jms.JMSListener"> > > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory > locked="false">failover:tcp://localhost:61616 > locked="false">TopicConnectionFactory > locked="false">topic > locked="false">topic > > * locked="false">local name="transport.jms.SessionTransacted" locked="false">true* > > > > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory > locked="false">failover:tcp://localhost:61616 > locked="false">QueueConnectionFactory > locked="false">queue > > * locked="false">local name="transport.jms.SessionTransacted" locked="false">true* > > > > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory > locked="false">failover:tcp://localhost:61616 > locked="false">TopicConnectionFactory > locked="false">topic > locked="false">topic > > * locked="false">local name="transport.jms.SessionTransacted" locked="false">true* > > > > And aslo added same parameters to JMS sender too. > >class="org.apache.axis2.transport.jms.JMSSender"> > > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory > locked="false">failover:tcp://localhost:61616 > locked="false">TopicConnectionFactory > locked="false">topic > locked="false">topic > > * locked="false">local name="transport.jms.SessionTransacted" locked="false">true* > > > > locked="false">org.apache.activemq.jndi.ActiveMQInitialContextFactory > locked="false">failover:tcp://localhost:61616 > locked="false">QueueConnectionFactory > locked="false">queue > > > * locked="false">local name="transport.jms.SessionTransacted" > locked="false">true* > > > >- Used activeMQ as JMS broker >- I used the scenario of "ESB as Both a JMS Producer and Consumer" [1] >- When testing that used external publisher to send messages to JMS >queue > > *Results:* > >- *Messages will be missing when consuming through ESB.*(It may >publish 1 messages to jms queue and only get around 100 or less number >of messages through ESB) > > *Further identifications:* > >- *Tried with inbound endpoints. It works properly.* > > *Attachments:* > > - inboundResult.png - This shows results with inbound endpoint. >- proxyResult.png - This shows results with proxy configuration. >- QueueProxy.xml -attached relevant proxy configuration. > > Any clarification on this situation ? > > [1] > https://docs.wso2.com/display/ESB500/ESB+as+Both+a+JMS+Producer+and+Consumer > Thank you. > > -- > Best Regards, > > Dilshani Subasinghe > Software Engineer - QA > WSO2, Inc.;http://wso2.com/ > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ> > lean.enterprise.middleware > Mobile: +94773375185 > Blog: dilshanilive.blogspot.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"
Log is corrected as bellow when having below parameter values. 1 6 [2016-05-19 11:23:20,338] ERROR - ServiceTaskManager Reconnection attempt : 1 for service : JmsProxy failed. Next retry in 20 seconds [2016-05-19 11:23:45,357] ERROR - ServiceTaskManager Reconnection attempt : 2 for service : JmsProxy failed. Next retry in 40 seconds [2016-05-19 11:24:30,378] INFO - ServiceTaskManager InitialReconnectDuration reached to MaxReconnectDuration. [2016-05-19 11:24:30,379] ERROR - ServiceTaskManager Reconnection attempt : 3 for service : JmsProxy failed. Next retry in 60 seconds [2016-05-19 11:25:35,411] INFO - ServiceTaskManager InitialReconnectDuration reached to MaxReconnectDuration. [2016-05-19 11:25:35,411] ERROR - ServiceTaskManager Reconnection attempt : 4 for service : JmsProxy failed. Next retry in 60 seconds Thanks, Nuwanw On Thu, May 19, 2016 at 11:11 AM, Dilshani Subasinghe <dilsh...@wso2.com> wrote: > Noted and reported a jira [1] to cover up fixing the issue. > > [1] https://wso2.org/jira/browse/ESBJAVA-4625 > > Regards, > Dilshani > > > On Thu, May 19, 2016 at 10:47 AM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> HI Dilshani, >> >> On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe <dilsh...@wso2.com> >> wrote: >> >>> Hi Nuwan, >>> >>> Thanks a lot for your clarification. But need more explanation on your >>> comments. >>> >>> 1. *if the user define only transport.jms.InitialReconnectDuration, It >>> will always be multiplied by the transport.jms.ReconnectProgressFactor >>> until it reach to transport.jms.MaxReconnectDuration. * >>> >>> We can define "transport.jms.MaxReconnectDuration" as 30 seconds and >>> shut down the jms broker. It may increase retry time interval by >>> ReconnectProgressFactor and doesn't consider about MaxReconnectDuration. >>> >> >> The log is not correct. It waits for MaxReconnectDuration. But logs show >> incorrect value. Thanks for reporting the issue. Will fix the logs. >> >>> >>> As I know MaxReconnectDuration is used to define upper level of >>> reconnect time limit. I don't understand exact relationship between " >>> ReconnectProgressFactor" and "MaxReconnectDuration". Can you verify it >>> further? >>> >>> When include ">> locked="false">3" and testing with exact scenario you can >>> find logs as follows: >>> >>> [2016-05-18 18:01:21,257] ERROR - ServiceTaskManager Reconnection >>> attempt : 1 for service : QueueProxy failed. Next retry in 20 seconds >>> [2016-05-18 18:01:21,258] ERROR - ServiceTaskManager Reconnection >>> attempt : 1 for service : TopicProxy failed. Next retry in 20 seconds >>> [2016-05-18 18:01:51,262] ERROR - ServiceTaskManager Reconnection >>> attempt : 2 for service : QueueProxy failed. Next retry in 40 seconds >>> [2016-05-18 18:01:51,263] ERROR - ServiceTaskManager Reconnection >>> attempt : 2 for service : TopicProxy failed. Next retry in 40 seconds >>> [2016-05-18 18:02:31,269] ERROR - ServiceTaskManager Reconnection >>> attempt : 3 for service : QueueProxy failed. Next retry in 60 seconds >>> [2016-05-18 18:02:31,271] ERROR - ServiceTaskManager Reconnection >>> attempt : 3 for service : TopicProxy failed. Next retry in 60 seconds >>> >>> 2. >>> >>> >>> *if the user define only transport.jms.InitialReconnectDuration, It will >>> always be multiplied by the transport.jms.ReconnectProgressFactor until it >>> reach to transport.jms.MaxReconnectDuration. * >>> I also tried above scenario while adding both InitialReconnectDuration >>> and MaxReconnectDuration. What do you mean by "*It will always be >>> multiplied by the transport.jms.ReconnectProgressFactor until it reach >>> to transport.jms.MaxReconnectDuration.*" >>> >>> When I am testing got the same result as above scenario: >>> >>> >> locked="false">1 >>> >> locked="false">3 >>> >>> Logs: >>> >>> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection >>> attempt : 1 for service : QueueProxy failed. Next retry in 20 seconds >>> [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection >>> attempt : 1 for service : TopicProxy failed. Next retry in 20 seconds >>> [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection >>> attempt : 2 for service : QueueProxy failed. Next retry in 40 second
Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"
HI Dilshani, On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe <dilsh...@wso2.com> wrote: > Hi Nuwan, > > Thanks a lot for your clarification. But need more explanation on your > comments. > > 1. *if the user define only transport.jms.InitialReconnectDuration, It > will always be multiplied by the transport.jms.ReconnectProgressFactor > until it reach to transport.jms.MaxReconnectDuration. * > > We can define "transport.jms.MaxReconnectDuration" as 30 seconds and shut > down the jms broker. It may increase retry time interval by > ReconnectProgressFactor and doesn't consider about MaxReconnectDuration. > The log is not correct. It waits for MaxReconnectDuration. But logs show incorrect value. Thanks for reporting the issue. Will fix the logs. > > As I know MaxReconnectDuration is used to define upper level of reconnect > time limit. I don't understand exact relationship between " > ReconnectProgressFactor" and "MaxReconnectDuration". Can you verify it > further? > > When include " locked="false">3" and testing with exact scenario you can > find logs as follows: > > [2016-05-18 18:01:21,257] ERROR - ServiceTaskManager Reconnection attempt > : 1 for service : QueueProxy failed. Next retry in 20 seconds > [2016-05-18 18:01:21,258] ERROR - ServiceTaskManager Reconnection attempt > : 1 for service : TopicProxy failed. Next retry in 20 seconds > [2016-05-18 18:01:51,262] ERROR - ServiceTaskManager Reconnection attempt > : 2 for service : QueueProxy failed. Next retry in 40 seconds > [2016-05-18 18:01:51,263] ERROR - ServiceTaskManager Reconnection attempt > : 2 for service : TopicProxy failed. Next retry in 40 seconds > [2016-05-18 18:02:31,269] ERROR - ServiceTaskManager Reconnection attempt > : 3 for service : QueueProxy failed. Next retry in 60 seconds > [2016-05-18 18:02:31,271] ERROR - ServiceTaskManager Reconnection attempt > : 3 for service : TopicProxy failed. Next retry in 60 seconds > > 2. > > > *if the user define only transport.jms.InitialReconnectDuration, It will > always be multiplied by the transport.jms.ReconnectProgressFactor until it > reach to transport.jms.MaxReconnectDuration. * > I also tried above scenario while adding both InitialReconnectDuration and > MaxReconnectDuration. What do you mean by "*It will always be multiplied > by the transport.jms.ReconnectProgressFactor until it reach > to transport.jms.MaxReconnectDuration.*" > > When I am testing got the same result as above scenario: > > locked="false">1 > locked="false">3 > > Logs: > > [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt > : 1 for service : QueueProxy failed. Next retry in 20 seconds > [2016-05-18 18:19:02,148] ERROR - ServiceTaskManager Reconnection attempt > : 1 for service : TopicProxy failed. Next retry in 20 seconds > [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt > : 2 for service : QueueProxy failed. Next retry in 40 seconds > [2016-05-18 18:19:32,153] ERROR - ServiceTaskManager Reconnection attempt > : 2 for service : TopicProxy failed. Next retry in 40 seconds > > Hope you will clarify more on these factors. > > Regards, > Dilshani > > > On Wed, May 18, 2016 at 5:53 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Dilshani, >> >> If the user need to define constant interval for reconnect, user can >> define transport.jms.ReconnectInterval. Then it will wait defined value for >> each reconnect attempt. >> >> if the user define only transport.jms.InitialReconnectDuration, It will >> always be multiplied by the transport.jms.ReconnectProgressFactor until >> it reach to transport.jms.MaxReconnectDuration. >> >> transport.jms.ReconnectProgressFactor is set to 2 by default to >> increasing the reconnect interval exponential until it reach >> to transport.jms.MaxReconnectDuration. >> >> >> On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe <dilsh...@wso2.com> >> wrote: >> >>> Hi ESB Team, >>> >>> When consider about "JMS connection factory parameters" [1] , user can >>> define "transport.jms.InitialReconnectDuration" parameter to give time >>> duration which will define initial reconnection time after broken JMS >>> connection. >>> >>> But the given value will be multiply with 2. That 2 is coming from >>> "reconnectionProgressionFactor" which can be over ride by >>> "transport.jms.ReconnectProgressFactor" (Which is another jms connection >
Re: [Dev] [ESB][JMS] "transport.jms.InitialReconnectDuration" parameter will automatically multiply with "transport.jms.ReconnectProgressFactor"
Hi Dilshani,
If the user need to define constant interval for reconnect, user can
define transport.jms.ReconnectInterval. Then it will wait defined value for
each reconnect attempt.
if the user define only transport.jms.InitialReconnectDuration, It will
always be multiplied by the transport.jms.ReconnectProgressFactor until it
reach to transport.jms.MaxReconnectDuration.
transport.jms.ReconnectProgressFactor is set to 2 by default to increasing
the reconnect interval exponential until it reach
to transport.jms.MaxReconnectDuration.
On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi ESB Team,
>
> When consider about "JMS connection factory parameters" [1] , user can
> define "transport.jms.InitialReconnectDuration" parameter to give time
> duration which will define initial reconnection time after broken JMS
> connection.
>
> But the given value will be multiply with 2. That 2 is coming from
> "reconnectionProgressionFactor" which can be over ride by
> "transport.jms.ReconnectProgressFactor" (Which is another jms connection
> factory parameter).
>
> ServiceTaskManager.java class will handle above function as follows:
>
>i
> *f (reconnectDuration != null) {*
>
//if transport.jms.ReconnectInterval is available.
>
>
>
>
>
>
>
>
>
> *retryDuration =
> reconnectDuration;log.error("Reconnection
> attempt : " + (r++) + " for service : "
> +serviceName + " failed. Next retry in
> " + (retryDuration / 1000) +" seconds.
> (Fixed Interval)");} else
> {retryDuration = (long) (retryDuration *
> reconnectionProgressionFactor);
> log.error("Reconnection attempt : " + (r++) + " for service : "
> +serviceName + " failed. Next retry in
> " + (retryDuration / 1000) +"
> seconds");*
>
>
> There are two facts to clarify with above situation.
>
> 1. According to user perspective, it may be wrong to multiply the value
> which is given by user.
>
> Ex: User may add 10 seconds as initial retry interval, but ESB does it
> within 20 seconds.
>
> Note: When we add "transport.jms.ReconnectProgressFactor" in to axis2.xml,
> it can be override.
>
> * locked="false">1*
>
> 2. Why we hard code *reconnectionProgressionFactor *as 2 ? Can we change
> it or is it impossible because of the behavior of axis2 ?
>
> As a suggestion, it will be better to add it as 1. (It may also solve the
> problem discussed above step)
>
>
>
>
>
> */** Progression factory for geometric series that calculates
> re-connection times */private double reconnectionProgressionFactor =
> 2.0; // default to [bounded] exponential*
> Any clarification on above factors will be really appreciated.
>
>
> [1] - https://docs.wso2.com/display/ESB500/JMS+Transport
> [2] - https://axis.apache.org/axis2/java/transports/jms.html
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB][Automation] How to configure testcases to be run on a standalone server
Hi Abimaran, In automation.xml, set the executionEnvironment as platform and configure the sever information in productGroup instance configuration where type="standalone" platform Thanks, Nuwanw On Mon, Apr 25, 2016 at 11:09 AM, Abimaran Kugathasan <abima...@wso2.com> wrote: > Hi Devs, > > How can we configure testcases to be run on the standalone ESB? > > I don't need to start a ESB through automation framework, but, want to > configure the automation framework to run the testcases on a standalone ESB. > > How can we point the hostname/port for the standalone ESB through > automation framework? > > -- > Thanks > Abimaran Kugathasan > > Software Engineer | WSO2 Inc > Data & APIs Technologies Team > Mobile : +94 773922820 > > <http://stackoverflow.com/users/515034> > <http://lk.linkedin.com/in/abimaran> > <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> > <https://twitter.com/abimaran> > > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Automation] How to apply a configuration file before starting a server using CarbonTestServerManager?
Hi Bhathiya,
You can start a new server instance using below code segment.
AutomationContext regTestContext = new AutomationContext("AM",
"AMTestServer", TestUserMode.SUPER_TENANT_ADMIN);
Map < String, String > startupParameterMap = new HashMap < > ();
startupParameterMap.put("-DportOffset", "230");
TestServerManager testServerManager = new
TestServerManager(regTestContext, null, startupParameterMap) {
public void configureServer() throws AutomationFrameworkException {
try {
File sourceFile = new
File(TestConfigurationProvider.getResourceLocation() +
"registry.xml");
//copying registry.xml file to conf folder
FileManager.copyFile(sourceFile, this.getCarbonHome() +
File.separator + "repository" + File.separator + "conf" +
File.separator + "registry.xml");
} catch (IOException e) {
throw new AutomationFrameworkException(e.getMessage(), e);
}
}
};
testServerManager.startServer();
Thanks,
Nuwanw
On Mon, Apr 11, 2016 at 2:52 PM, Bhathiya Jayasekara <bhath...@wso2.com>
wrote:
> Hi Automation team,
>
> In this[1] test, we have *CarbonTestServerManager *with
> *MultipleServersManager *to spawn a new APIM server. Now I need to apply
> a modified api-manager.xml file before starting this server. How can I do
> that? Appreciate some help.
>
> public void setEnvironment() throws Exception {
> // to start the server from a different port offset
> serverPropertyMap.put("-DportOffset", "510");
> // start with OSGI component service
> serverPropertyMap.put("-DosgiConsole", Integer.toString(telnetPort));
> AutomationContext autoCtx = new AutomationContext();
> CarbonTestServerManager server =
> new CarbonTestServerManager(autoCtx, System.getProperty("carbon.zip"),
> serverPropertyMap);
> manager.startServers(server);
> }
>
>
> [1]
> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/server/mgt/OSGIServerBundleStatusTestCase.java#L63
>
> Thanks,
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com <http://wso2.com>*
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> <http://www.linkedin.com/in/bhathiyaj>*
> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
> *Blog: http://movingaheadblog.blogspot.com
> <http://movingaheadblog.blogspot.com/>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Response Body is missing In tenant mode
Hi The issue[1] is fixed now. Problem was that the pull request[2] was not merged in to wso2-synapse. The pull request[2] was supposed to fix the issue[3] which was introduced by the fix done for issue[4]. Missing the fix[1] in synapse-nhttp-transport with carbon kernel 4.4.4 having the fix[4], led to this issue. PR[1] is merged and now APIs are working fine for tenant as well. [1] https://wso2.org/jira/browse/ESBJAVA-4512 [2] https://github.com/wso2/wso2-synapse/pull/450 [3] https://wso2.org/jira/browse/ESBJAVA-4386 [4] https://wso2.org/jira/browse/CARBON-15759 Thanks, Nuwanw On Tue, Mar 22, 2016 at 5:26 PM, Sam Sivayogam <s...@wso2.com> wrote: > No i tried with 404, 503 but its the same > > On Tue, Mar 22, 2016 at 11:51 AM, Viraj Senevirathne <vir...@wso2.com> > wrote: > >> Hi Sam, >> Is it working for other status code? >> >> On Mon, Mar 21, 2016 at 8:07 PM, Sam Sivayogam <s...@wso2.com> wrote: >> >>> Hi All, >>> >>> After doing the following upgrades in APIM, Response Body is missing >>> when invoking the REST API[1] In tenant mode. >>> >>> Carbon kernel 4.4.3 to 4.4.4 >>> Carbon mediation 4.6.1-ALPHA to 4.6.1-BETA >>> Carbon multi-tenancy 4.5.0 to 4.5.1 >>> >>> I was also able to reproduce the same issue in the latest build which I >>> got from [2]. I added the REST API[1] in super tenant mode and tenant mode. >>> when I invoke the API in super tenant mode it works perfectly and I get a >>> JSON response with HTTP Response code 200. But when I Invoke the same API >>> in tenant mode the response body is missing and the HTTP Response code is >>> 200 . In the attached wire logs you can see that response body is coming >>> from backend service and its dropped when sending back the response to >>> client. Is this a known issue ? >>> >>> [1] >>> http://ws.apache.org/ns/synapse; >>> name="testapi" >>> context="/testapi"> >>> >>> >>> >>> >>>https://httpbin.org/"/> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> [2] >>> https://wso2.org/jenkins/view/product-builds/job/product-esb/lastStableBuild/org.wso2.esb$wso2esb/ >>> >>> Thanks, >>> Sam >>> -- >>> *Sam Sivayogam* >>> >>> Software Engineer >>> Mobile : +94 772 906 439 >>> Office : +94 112 145 345 >>> *WSO2, Inc. :** wso2.com <http://wso2.com/>* >>> lean.enterprise.middleware. >>> >> >> >> >> -- >> Viraj Senevirathne >> Software Engineer; WSO2, Inc. >> >> Mobile : +94 71 958 0269 >> Email : vir...@wso2.com >> > > > > -- > *Sam Sivayogam* > > Software Engineer > Mobile : +94 772 906 439 > Office : +94 112 145 345 > *WSO2, Inc. :** wso2.com <http://wso2.com/>* > lean.enterprise.middleware. > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: [ESB] Regarding an Error message
gt;> at >> org.apache.synapse.core.axis2.Axis2Sender.sendBack(Axis2Sender.java:212) >> at >> org.apache.synapse.mediators.builtin.RespondMediator.mediate(RespondMediator.java:28) >> at >> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81) >> at >> org.apache.synapse.mediators.eip.splitter.IterateMediator.mediate(IterateMediator.java:241) >> at >> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:267) >> at >> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:679) >> at >> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:244) >> at >> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529) >> at >> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172) >> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) >> at >> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247) >> at >> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: java.lang.NullPointerException >> at >> org.apache.synapse.transport.passthru.util.SourceResponseFactory.create(SourceResponseFactory.java:64) >> at >> org.apache.synapse.transport.passthru.PassThroughHttpSender.submitResponse(PassThroughHttpSender.java:462) >> at >> org.apache.synapse.transport.passthru.PassThroughHttpSender.invoke(PassThroughHttpSender.java:267) >> ... 16 more >> >> >> >> >> -- >> Ravindi de Silva >> *Software Engineer- Intern* >> Mobile : +94 (0) 779689620 >> ravi...@wso2.com >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thusitha Dayaratne > Software Engineer > WSO2 Inc. - lean . enterprise . middleware | wso2.com > > Mobile +94712756809 > Blog alokayasoya.blogspot.com > Abouthttp://about.me/thusithathilina > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AppCloud] [Automation] Reading a file from resources folder
Hi You can get the resource location using TestConfigurationProvider.getResourceLocation() Thanks, Nuwanw On Thu, Mar 10, 2016 at 2:25 PM, Danushka Fernando <danush...@wso2.com> wrote: > Hi Nuwan > Yes. I want to access a file inside resources folder from test automation > module. > > Thanks & Regards > Danushka Fernando > Senior Software Engineer > WSO2 inc. http://wso2.com/ > Mobile : +94716332729 > > On Thu, Mar 10, 2016 at 1:45 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Dhanushka, >> >> Are you trying to read the resource from maven test module? >> >> Thanks, >> Nuwanw >> >> On Thu, Mar 10, 2016 at 11:46 AM, Danushka Fernando <danush...@wso2.com> >> wrote: >> >>> Hi >>> I am trying to do $subject in a test case. I tried code below. Didn't >>> work. Can some one shed some light here. >>> >>> ClassLoader classLoader = getClass().getClassLoader(); >>> File uploadArtifact = new >>> File(classLoader.getResource(resourcePath).getFile()); >>> >>> >>> Thanks & Regards >>> Danushka Fernando >>> Senior Software Engineer >>> WSO2 inc. http://wso2.com/ >>> Mobile : +94716332729 >>> >> >> >> >> -- >> Nuwan Wimalasekara >> Senior Software Engineer - Test Automation >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> phone: +94 71 668 4620 >> >> >> >> > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AppCloud] [Automation] Reading a file from resources folder
Hi Dhanushka, Are you trying to read the resource from maven test module? Thanks, Nuwanw On Thu, Mar 10, 2016 at 11:46 AM, Danushka Fernando <danush...@wso2.com> wrote: > Hi > I am trying to do $subject in a test case. I tried code below. Didn't > work. Can some one shed some light here. > > ClassLoader classLoader = getClass().getClassLoader(); > File uploadArtifact = new > File(classLoader.getResource(resourcePath).getFile()); > > > Thanks & Regards > Danushka Fernando > Senior Software Engineer > WSO2 inc. http://wso2.com/ > Mobile : +94716332729 > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] If OUT_ONLY is true, call mediator failed to send the request body to backend service
Hi Viraj/Isuru,
Thanks for the response. I debug the code and found that message is cloning
properly with buffer. But the problem is when try to send the request body
to backend by the TargetHandler, the buffer has zero length content. That
is why, it does not send the message body to backend. need to find when it
get cleared and will debug further.
Thanks,
Nuwanw
On Thu, Mar 10, 2016 at 9:32 AM, Isuru Udana <isu...@wso2.com> wrote:
> Hi Nuwan,
>
> We are cloning the message because we need to keep the original message to
> proceed with the rest of the meditators in the message flow. We we do not
> clone at the Call, since the stream is getting consumed for the first
> invocation, we won't be able to continue.
>
> Thanks.
>
> On Wed, Mar 9, 2016 at 5:41 PM, Viraj Senevirathne <vir...@wso2.com>
> wrote:
>
>> Hi Nuwan,
>>
>> In call mediator if OUT_ONLY is true it will clone the message and will
>> send that new message context to the backend. If there are other mediators
>> after call mediator mediation will continue with the original message
>> context. This is happening as call mediator is a non blocking sender (It
>> will not wait).
>>
>> But if you don't want cloning you will have to use call mediator in
>> *blocking* mode. Then original message context will be passed and it
>> will wait till request send out to the backend before starting mediating
>> subsequent mediators.
>>
>> Thank You,
>>
>>
>> On Wed, Mar 9, 2016 at 5:32 PM, Nuwan Wimalasekara <nuw...@wso2.com>
>> wrote:
>>
>>> Hi
>>>
>>> Call mediator is not submitting the request body to backend service if
>>> OUT_ONLY is true. When the TargetHandler try to send the message body by
>>> reading the Buffer_source, It already got cleared.
>>>
>>> The problem is that inside the call mediator, messageContext is cloned.
>>> Then the buffer is not created in Pipe class. so the buffer has zero length
>>> content.
>>> Is there any reason to clone the message if OUT_ONLY is true inside the
>>> call mediator?
>>>
>>> if we remove cloning the message and proceed with the incomming message
>>> context, the issue is resolved.
>>>
>>>
>>> boolean outOnlyMessage =
>>> "true".equals(synInCtx.getProperty(SynapseConstants.OUT_ONLY));
>>>
>>> // Prepare the outgoing message context
>>> MessageContext synOutCtx = null;
>>> if (outOnlyMessage) {
>>> try {
>>> *synOutCtx =
>>> MessageHelper.cloneMessageContext(synInCtx);*
>>> } catch (AxisFault axisFault) {
>>> handleException("Error occurred while cloning msg
>>> context", axisFault, synInCtx);
>>> }
>>> } else {
>>> synOutCtx = synInCtx;
>>> }
>>>
>>>
>>> Proxy configuration introduce issue.
>>>
>>>
>>>
>>>
>>>
>>>
>>>http://localhost:9000/services/SimpleStockQuoteService"/>
>>>
>>>
>>>
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-4469
>>>
>>> Thanks,
>>> Nuwanw
>>>
>>> --
>>> Nuwan Wimalasekara
>>> Senior Software Engineer - Test Automation
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> phone: +94 71 668 4620
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Viraj Senevirathne
>> Software Engineer; WSO2, Inc.
>>
>> Mobile : +94 71 958 0269
>> Email : vir...@wso2.com
>>
>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] If OUT_ONLY is true, call mediator failed to send the request body to backend service
Hi
Call mediator is not submitting the request body to backend service if
OUT_ONLY is true. When the TargetHandler try to send the message body by
reading the Buffer_source, It already got cleared.
The problem is that inside the call mediator, messageContext is cloned.
Then the buffer is not created in Pipe class. so the buffer has zero length
content.
Is there any reason to clone the message if OUT_ONLY is true inside the
call mediator?
if we remove cloning the message and proceed with the incomming message
context, the issue is resolved.
boolean outOnlyMessage =
"true".equals(synInCtx.getProperty(SynapseConstants.OUT_ONLY));
// Prepare the outgoing message context
MessageContext synOutCtx = null;
if (outOnlyMessage) {
try {
*synOutCtx = MessageHelper.cloneMessageContext(synInCtx);*
} catch (AxisFault axisFault) {
handleException("Error occurred while cloning msg context",
axisFault, synInCtx);
}
} else {
synOutCtx = synInCtx;
}
Proxy configuration introduce issue.
http://localhost:9000/services/SimpleStockQuoteService"/>
[1] https://wso2.org/jira/browse/ESBJAVA-4469
Thanks,
Nuwanw
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Test-Automation] Error After Updating Selenium version
HOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.application.mgt.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.idp.mgt.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.mgt.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.oauth.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.entitlement.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.automationutils:org.wso2.carbon.integration.common.admin.client:jar:4.4.1:compile > [INFO] | +- > org.wso2.carbon.commons:org.wso2.carbon.user.mgt.stub:jar:4.4.3:compile > [INFO] | +- > org.wso2.carbon.commons:org.wso2.carbon.logging.view.stub:jar:4.4.3:compile > [INFO] | +- > org.wso2.carbon.commons:org.wso2.carbon.ndatasource.stub:jar:4.4.3:compile > [INFO] | +- > org.wso2.carbon:org.wso2.carbon.server.admin.stub:jar:4.4.0:compile > [INFO] | +- org.wso2.carbon:org.wso2.carbon.utils:jar:4.4.3:compile > [INFO] | | +- org.wso2.carbon:org.wso2.carbon.queuing:jar:4.4.3:compile > [INFO] | | +- org.wso2.carbon:org.wso2.carbon.base:jar:4.4.3:compile > [INFO] | | | \- > org.wso2.carbon:org.wso2.carbon.securevault:jar:4.4.3:compile > [INFO] | | +- > org.igniterealtime.smack.wso2:smack:jar:3.0.4.wso2v1:compile > [INFO] | | +- > org.igniterealtime.smack.wso2:smackx:jar:3.0.4.wso2v1:compile > [INFO] | | +- org.apache.ant.wso2:ant:jar:1.7.0.wso2v1:compile > [INFO] | | | \- org.apache.ant:ant:jar:1.7.0:compile > [INFO] | | | \- org.apache.ant:ant-launcher:jar:1.7.0:compile > [INFO] | | +- > org.eclipse.equinox:javax.servlet:jar:3.0.0.v201112011016:compile > [INFO] | | \- > org.wso2.carbon:org.wso2.carbon.registry.api:jar:4.4.3:compile > [INFO] | +- > org.wso2.carbon.identity:org.wso2.carbon.security.mgt.stub:jar:4.5.1:compile > [INFO] | +- > org.wso2.carbon.commons:org.wso2.carbon.application.mgt.stub:jar:4.4.3:compile > [INFO] | +- > org.wso2.carbon.multitenancy:org.wso2.carbon.tenant.mgt.stub:jar:4.4.1:compile > [INFO] | \- > org.wso2.carbon.identity:org.wso2.carbon.identity.user.profile.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.um.ws.api.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.sso.saml.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.claim.mgt.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.provider.openid.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.scim.common.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.user.account.association.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.automation:org.wso2.carbon.automation.engine:jar:4.4.2:compile > [INFO] | +- org.testng:testng:jar:6.1.1:test > [INFO] | | +- junit:junit:jar:3.8.1:test > [INFO] | | +- org.beanshell:bsh:jar:2.0b4:compile > [INFO] | | +- com.beust:jcommander:jar:1.12:test > [INFO] | | \- org.yaml:snakeyaml:jar:1.6:test > [INFO] | +- commons-io:commons-io:jar:2.2:compile > [INFO] | +- org.jacoco:org.jacoco.core:jar:0.7.4.201502262128:compile > [INFO] | | \- org.ow2.asm:asm-debug-all:jar:5.0.1:compile > [INFO] | +- org.jacoco:org.jacoco.report:jar:0.7.4.201502262128:compile > [INFO] | +- org.codehaus.plexus:plexus-utils:jar:3.0.22:compile > [INFO] | \- commons-collections:commons-collections:jar:3.2.2:compile > [INFO] +- org.wso2.carbon:org.wso2.carbon.user.core:jar:4.4.3:compile > [INFO] | +- org.wso2.carbon:javax.cache.wso2:jar:4.4.3:compile > [INFO] | | \- > org.apache.geronimo.specs:geronimo-jta_1.1_spec:jar:1.1:compile > [INFO] | +- org.wso2.carbon:org.wso2.carbon.user.api:jar:4.4.3:compile > [INFO] | +- xerces.wso2:xercesImpl:jar:2.8.1.wso2v2:compile > [INFO] | +- commons-dbcp.wso2:commons-dbcp:jar:1.4.0.wso2v1:compile > [INFO] | +- org.wso2.carbon:org.wso2.carbon.logging:jar:4.4.3:compile > [INFO] | | +- org.apache.log4j.wso2:log4j:jar:1.2.17.wso2v1:compile > [INFO] | | \- org.wso2.carbon:org.wso2.carbon.bootstrap:jar:4.4.3:compile > [INFO] | | \- wrapper:wrapper:jar:3.2.3:compile > [INFO] | +- org.wso2.securevault:org.wso2.securevault:jar:1.0.0:compile > [INFO] | | +- log4j:log4j:jar:1.2.14:compile > [INFO] | | \- jline:jline:jar:0.9.94:compile > [INFO] | \- > org.wso2.orbit.commons-collections:commons-collections:jar:3.2.2.wso2v1:compile > [INFO] +- org.wso2.is: > org.wso2.sample.is.sso.agent:war:5.2.0-SNAPSHOT:compile > [INFO] +- org.wso2.is:playground2:war:5.2.0-SNAPSHOT:compile > [INFO] +- org.wso2.is:PassiveSTSSampleApp:war:5.2.0-SNAPSHOT:compile > [INFO] +- com.googlecode.json-simple:json-simple:jar:1.1:test > [INFO] +- org.jacoco:org.jacoco.agent:jar:0.7.4.201502262128:compile > [INFO] +- > org.wso2.carbon.identity:org.wso2.carbon.identity.sts.passive.stub:jar:5.0.8-SNAPSHOT:compile > [INFO] +- > org.wso2.carbon.automationutils:org.wso2.carbon.integration.common.extensions:jar:4.4.1:compile > [INFO] | \- net.lingala.zip4j:zip4j:jar:1.2.3:compile > [INFO] \- bouncycastle:bcprov-jdk15:jar:132:compile > > How can I fix this issue? > > Thank You! > > -- > *Chamila Dilshan Wijayarathna,* > Software Engineer > Mobile:(+94)788193620 > WSO2 Inc., http://wso2.com/ > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] Integration tests run before deploying web app
Hi Geesara,
You can use WebAppDeploymentUtil.isWebApplicationDeployed()[1] method to
check whether the web application is deployed or not. It will wait and
return true once the web app got deployed.
[1]
https://github.com/wso2/product-as/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/appserver/integration/common/utils/WebAppDeploymentUtil.java
Thanks,
Nuwanw
On Tue, Nov 10, 2015 at 11:52 AM, Amalka Subasinghe <ama...@wso2.com> wrote:
> We can read the carbon log and check whether there's a web app deployed
> log.
>
> Automation team might know some more options :)
>
>
>
> On Tue, Nov 10, 2015 at 7:51 PM, Geesara Prathap <gees...@wso2.com> wrote:
>
>> Hi Amalka,
>>
>> Actually that is what I asked. What sort of logic should be invoked
>> through a @Before method? I can periodically send requests to service
>> endpoint check whether service is available or not. But what would be the
>> proper way to achieve this.
>>
>> Thanks,
>>
>> On Tue, Nov 10, 2015 at 6:24 PM, Amalka Subasinghe <ama...@wso2.com>
>> wrote:
>>
>>> You can implement some waiting logic to check whether the web app
>>> deployed in the server and invoke it in @BeforeClass method
>>>
>>>
>>> On Mon, Nov 9, 2015 at 10:25 PM, Geesara Prathap <gees...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> I wrote some integration test cases to test a web service. Here is my
>>>> the build section of maven configuration looks like.
>>>>
>>>> * *
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> *maven-war-plugin*
>>>>
>>>> *2.3*
>>>>
>>>> **
>>>>
>>>> *src/main/webapp/WEB-INF/web.xml*
>>>>
>>>> *${name}*
>>>>
>>>> *
>>>> /home/geesara/wso2/products/wso2as-5.3.0/repository/deployment/server/webapps*
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>>
>>>> **
>>>>
>>>> *maven-compiler-plugin*
>>>>
>>>> *3.1*
>>>>
>>>> **
>>>>
>>>> *1.7*
>>>>
>>>> *1.7*
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>>
>>>> **
>>>>
>>>> *org.apache.maven.plugins*
>>>>
>>>> *maven-failsafe-plugin*
>>>>
>>>> *2.12.4*
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> *integration-test*
>>>>
>>>> **
>>>>
>>>> *integration-test*
>>>>
>>>> *verify*
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> **
>>>>
>>>> As the $subject, How should we wait until web app has been deployed on
>>>> the server to execute integration test cases.
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> --
>>>> Geesara Prathap Kulathunga
>>>> Software Engineer
>>>> WSO2 Inc; http://wso2.com
>>>> phone: +940772684174
>>>>
>>>
>>>
>>>
>>> --
>>> Amalka Subasinghe
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> Mobile: +94 77 9401267
>>>
>>
>>
>>
>> --
>> Geesara Prathap Kulathunga
>> Software Engineer
>> WSO2 Inc; http://wso2.com
>> phone: +940772684174
>>
>
>
>
> --
> Amalka Subasinghe
> Senior Software Engineer
> WSO2 Inc.
> Mobile: +94 77 9401267
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Integration test] testng.xml Reading Error (java.lang.reflect.InvocationTargetException)
stNG.runSuitesLocally(TestNG.java:1149)
> at org.testng.TestNG.run(TestNG.java:1057)
> at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
> at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
> at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException:
> Unexpected subelement {http://mgt.service.carbon.wso2.org/xsd}CAppArtifact
> at
> org.wso2.carbon.service.mgt.stub.types.carbon.ServiceMetaData$Factory.parse(ServiceMetaData.java:2857)
> at
> org.wso2.carbon.service.mgt.stub.types.carbon.ServiceMetaDataWrapper$Factory.parse(ServiceMetaDataWrapper.java:1053)
> at
> org.wso2.carbon.service.mgt.stub.types.axis2.ListServicesResponse$Factory.parse(ListServicesResponse.java:417)
> at
> org.wso2.carbon.service.mgt.stub.ServiceAdminStub.fromOM(ServiceAdminStub.java:12898)
> ... 39 more
> Caused by: org.apache.axis2.databinding.ADBException: Unexpected
> subelement {http://mgt.service.carbon.wso2.org/xsd}CAppArtifact
> at
> org.wso2.carbon.service.mgt.stub.types.carbon.ServiceMetaData$Factory.parse(ServiceMetaData.java:2851)
> ... 42 more
>
> SKIPPED: testPassThroughProxy
> Pass through proxy service invocation test
>
>
>
> On Wed, Oct 14, 2015 at 12:32 PM, Nuwan Wimalasekara <nuw...@wso2.com>
> wrote:
>
>> Hi Rajjaz,
>>
>> In your pom file, testng.xml file path is wrong. So surefire can not
>> locate the testng.xml file defined. Please define relative path to solve
>> this issue.
>>
>> /src/test/resources/testng.xml
>>
>> Above should be corrected as bellow.
>>
>> *src/test/resources/testng.xml*
>>
>> Thanks,
>> Nuwanw
>>
>> On Wed, Oct 14, 2015 at 12:21 PM, Rajjaz Mohammed <raj...@wso2.com>
>> wrote:
>>
>>> Hi Dev,
>>> I'm writing a simple integration test [1] but while running the test i'm
>>> getting the following error[2]. and i attached my pom also. can anyone
>>> guide on me on this?
>>>
>>> [1] https://docs.wso2.com/display/TA430/Writing+a+Test+Case+for+ESB
>>>
>>> [2]
>>> ---
>>> T E S T S
>>> ---
>>> Forking command line: /bin/sh -c cd
>>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target &&
>>> /home/rajjaz/Documents/jdk1.7.0_79/jre/bin/java -Xms512m -Xmx1024m
>>> -XX:MaxPermSize=128m -jar
>>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefirebooter7361817641598581788.jar
>>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire8778537678578881741tmp
>>> /home/rajjaz/esb-connectors/ejb/org.wso2.carbon.connector/target/surefire/surefire_06295743703835172308tmp
>>> org.apache.maven.surefire.util.SurefireReflectionException:
>>> java.lang.reflect.InvocationTargetException; nested exception is
>>> java.lang.reflect.InvocationTargetException: null
>>> java.lang.reflect.InvocationTargetException
>>> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>>> at
>>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(Provid
Re: [Dev] [Integration test] testng.xml Reading Error (java.lang.reflect.InvocationTargetException)
:862) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-test of goal > org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The > forked VM terminated without saying properly goodbye. VM crash or > System.exit called ? > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 20 more > Caused by: java.lang.RuntimeException: The forked VM terminated without > saying properly goodbye. VM crash or System.exit called ? > at > org.apache.maven.plugin.surefire.booterclient.output.ForkClient.close(ForkClient.java:257) > at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:301) > at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:116) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:740) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:682) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:648) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:586) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > ... 21 more > > -- > Thank you > Best Regards > > *Rajjaz HM* > Associate Software Engineer > WSO2 Inc. <http://wso2.com/> > lean | enterprise | middleware > Mobile | +94752833834 > Email | raj...@wso2.com > LinkedIn | Blogger | WSO2 Profile > <http://wso2.com/about/team/mohammer_rajjaz/> > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Integration test] testng.xml Reading Error (java.lang.reflect.InvocationTargetException)
java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:197) > 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution > default-test of goal > org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The > forked VM terminated without saying properly goodbye. VM crash or > System.exit called ? > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) > ... 20 more > Caused by: java.lang.RuntimeException: The forked VM terminated without > saying properly goodbye. VM crash or System.exit called ? > at > org.apache.maven.plugin.surefire.booterclient.output.ForkClient.close(ForkClient.java:257) > at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:301) > at > org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:116) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:740) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAllProviders(AbstractSurefireMojo.java:682) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:648) > at > org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:586) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > ... 21 more > > -- > Thank you > Best Regards > > *Rajjaz HM* > Associate Software Engineer > WSO2 Inc. <http://wso2.com/> > lean | enterprise | middleware > Mobile | +94752833834 > Email | raj...@wso2.com > LinkedIn | Blogger | WSO2 Profile > <http://wso2.com/about/team/mohammer_rajjaz/> > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Can we pass a variable from TestManagerListener to a TestCase?
Hi Amalka, As per my understand, There is no way to pass parameters form TestManagerListener to Individual test classes. However There are two possible way to achieve your requirement. 1) Tenant Management admin service can be used in test classes to get the tenant id if the tenant domain is static. 2) Static variable can be used to store the tenant id in TestManagerListener and that variable can be refer in test classes. in both ways you can get the tenant id which you created in TestManagerListener. Thanks, Nuwanw On Tue, Oct 13, 2015 at 2:27 PM, Amalka Subasinghe <ama...@wso2.com> wrote: > No we can't > > What I want to do it, when executing TestManagerListener.onStart() class > we create a tenant and then in the test cases i want to use that tenant's > id. > > if we hard code the tenant id in automation.xml file, every time we have > to manually create the tenant in the af setup before execute our test cases. > > > > On Tue, Oct 13, 2015 at 2:22 PM, Mahesh Chinthaka <mahe...@wso2.com> > wrote: > >> Hi Amalka, >> >> What is the use case ? Why do you want to pass a value from onStart >> method to a test case. >> Configuring the value in automation.xml and reading it inside the test >> case wont help ? >> >> Thanks >> >> On Tue, Oct 13, 2015 at 2:16 PM, Amalka Subasinghe <ama...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I want to set a value to a variable in TestManagerListener.onStart() >>> method and use it in a test case. How can I do it? >>> >>> Thanks >>> Amalka >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Mahesh Chinthaka Vidanagama* | Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 63 63 083 | Work: +94 112 145 345 >> Email: mahe...@wso2.com | Web: www.wso2.com >> > > > > -- > Amalka Subasinghe > Senior Software Engineer > WSO2 Inc. > Mobile: +94 77 9401267 > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sending custom responses in automation test
Hi Senduran, You can simply create another proxy service or API to send the empty body response with 202 status code. if not you can create a axis2 service which return the response as you expected and deploy it on ESB or axis2 server. Thanks, Nuwanw On Wed, Oct 7, 2015 at 10:20 AM, Senduran Balasubramaniyam < sendu...@wso2.com> wrote: > Hi Krishantha, > > Following are the steps I followed to verify the scenario. > >- Created a mock service to respond with status code 202, empty body >with content-type text/html >- Invoked the service from ESB and added a log full after calling the >endpoint > > since there is a content type available ESB will try to build the message > but since the message body is empty it will throw an exception > > Thanks > Senduran > > On Wed, Oct 7, 2015 at 10:11 AM, Krishantha Samaraweera < > krishan...@wso2.com> wrote: > >> Hi Senduran, >> >> Can you list the steps that you have followed to verify the scenario >> manually. >> >> Thanks, >> Krishantha. >> >> On Tue, Oct 6, 2015 at 10:05 AM, Senduran Balasubramaniyam < >> sendu...@wso2.com> wrote: >> >>> Hi Krishantha, >>> >>> I need to write a test for ESB where my proxy service should receive >>> some custom responses. >>> For example >>> Empty body with status code 202 and content type text/html. >>> Could you please guide me to do this >>> >>> Thank you >>> Senduran >>> >>> -- >>> *Senduran * >>> Software Engineer, >>> WSO2, Inc.; http://wso2.com/ <http://wso2.com/> >>> Mobile: +94 77 952 6548 >>> >> >> >> >> -- >> Krishantha Samaraweera >> Senior Technical Lead - Test Automation >> Mobile: +94 77 7759918 >> WSO2, Inc.; http://wso2.com/ >> lean . enterprise . middleware. >> > > > > -- > *Senduran * > Software Engineer, > WSO2, Inc.; http://wso2.com/ <http://wso2.com/> > Mobile: +94 77 952 6548 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Code Styling - Throwing Exceptions
Hi Manuranga, We have discussed the subject in the mail thread "Best Practice in Throwing Exceptions in test methods signature"@d...@wso2.com as well. You can get some information from the thread. Thanks, Nuwanw On Tue, Oct 6, 2015 at 12:01 PM, Manuranga Perera <m...@wso2.com> wrote: > Following issue came up during a code review. when writing tests should we > throw individual Exception types [1] or should we just throw Exception > super class. > > I though the best practice is to throw individual classes. But I got to > know that there is a common practice to throw Exception class in this case. > Is this correct. Should we follow the same? > > [1] > https://github.com/wso2/product-ues/pull/25/files#diff-c64bcb3f71c33d2ce7a50ad8f39f6c38R41 > > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : m...@wso2.com > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Patch Automation] Can we deploy a war file programmatically?
Hi Abimaran, WebappAdmin service can be used deploy a war file. WebAppAdminClient is already implemented and you can reuse the client. Thanks, Nuwanw On Thu, Oct 1, 2015 at 10:11 AM, Abimaran Kugathasan <abima...@wso2.com> wrote: > Hi, > > > We can deploy aar files using ServiceAdminClient into a product. Can we do > the same for war file. Does our automation framework support it? > > If so, can anybody please point me the Class or module name? > > -- > Thanks > Abimaran Kugathasan > > Software Engineer | WSO2 Inc > Data & APIs Technologies Team > Mobile : +94 773922820 > > <http://stackoverflow.com/users/515034> > <http://lk.linkedin.com/in/abimaran> > <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> > <https://twitter.com/abimaran> > > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Timeout error when creating APIs using APIM 1.9.0 REST API
Hi Udara,
Please refer below links[1] and [2]
[1]
https://github.com/nuwanw/product-apim/blob/master/modules/integration/tests-common/integration-test-utils/src/main/java/org/wso2/am/integration/test/utils/clients/APIPublisherRestClient.java
[2]
https://github.com/nuwanw/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/samples/YouTubeAPITestCase.java
Thanks,
Nuwnw
On Fri, Sep 11, 2015 at 10:39 PM, Udara Liyanage <ud...@wso2.com> wrote:
> Hi Nuwan,
>
> Could you please point me to the test case location, me too is looking for
> a similar sample.
>
> On Fri, Sep 11, 2015 at 3:39 PM, Nuwan Wimalasekara <nuw...@wso2.com>
> wrote:
>
>> Hi Udara,
>>
>> In APIM integration test, HTTP endpoint is used to call the
>> RestAPI(Publisher and Store) and It is working fine without any issue. This
>> should work
>>
>> Thanks,
>> Nuwanw
>>
>> On Fri, Sep 11, 2015 at 9:41 AM, Nuwan Dias <nuw...@wso2.com> wrote:
>>
>>> They run on HTTPS only. If you send an http request, it automatically
>>> redirects to https.
>>>
>>> On Fri, Sep 11, 2015 at 8:46 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I could create APIs by changing to port 9443 and protocol to HTTPS.
>>>> However why does REST APIs runs on HTTP?
>>>>
>>>> curl -X POST -c cookies
>>>> https://localhost:9443/publisher/site/blocks/user/login/ajax/login.jag
>>>> -d 'action=login=admin=admin' -k
>>>>
>>>>
>>>> curl -b cookies -k
>>>> https://localhost:9443/publisher/site/blocks/item-add/ajax/add.jag -d
>>>> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
>>>> a phone
>>>> number=phone,mobile,multimedia=nonsecured===Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
>>>> x...@ee.com=xx=g...@ww.com"
>>>> -d'endpoint_config={"production_endpoints":{"url":"
>>>> http://ws.cdyne.com/phoneverify/phoneverify.asmx","config":null},"endpoint_type":"http
>>>> "}';
>>>>
>>>> On Fri, Sep 11, 2015 at 4:18 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I got this error while trying the sample Add API command mentioned in
>>>>> the doc <https://docs.wso2.com/display/AM190/Publisher+APIs>. No
>>>>> backend error is displayed, any idea?
>>>>>
>>>>>
>>>>> $ curl -X POST -c cookies
>>>>> http://localhost:9763/publisher/site/blocks/user/login/ajax/login.jag
>>>>> -d 'action=login=admin=admin'
>>>>> {"error" : false}
>>>>>
>>>>>
>>>>> $ curl -X POST -b cookies
>>>>> http://localhost:9763/publisher/site/blocks/item-add/ajax/add.jag -d
>>>>> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
>>>>> a phone
>>>>> number=phone,mobile,multimedia=nonsecured=Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
>>>>> x...@ee.com=xx=g...@ww.com"
>>>>> -d'endpoint_config={"production_endpoints":{"url":"
>>>>> http://ws.cdyne.com/phoneverify/phoneverify.asmx
>>>>> ","config":null},"endpoint_type":"http"}';
>>>>> {"error" : true, "message" : "*timeout*"}
>>>>>
>>>>> --
>>>>>
>>>>> Udara Liyanage
>>>>> Software Engineer
>>>>> WSO2, Inc.: http://wso2.com
>>>>> lean. enterprise. middleware
>>>>>
>>>>> web: http://udaraliyanage.wordpress.com
>>>>> phone: +94 71 443 6897
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Udara Liyanage
>>>> Software Engineer
>>>> WSO2, Inc.: http://wso2.com
>>>> lean. enterprise. middleware
>>>>
>>>> web: http://udaraliyanage.wordpress.com
>>>> phone: +94 71 443 6897
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nuwan Wimalasekara
>> Senior Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Timeout error when creating APIs using APIM 1.9.0 REST API
Hi Udara,
In APIM integration test, HTTP endpoint is used to call the
RestAPI(Publisher and Store) and It is working fine without any issue. This
should work
Thanks,
Nuwanw
On Fri, Sep 11, 2015 at 9:41 AM, Nuwan Dias <nuw...@wso2.com> wrote:
> They run on HTTPS only. If you send an http request, it automatically
> redirects to https.
>
> On Fri, Sep 11, 2015 at 8:46 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
>> Hi,
>>
>> I could create APIs by changing to port 9443 and protocol to HTTPS.
>> However why does REST APIs runs on HTTP?
>>
>> curl -X POST -c cookies
>> https://localhost:9443/publisher/site/blocks/user/login/ajax/login.jag
>> -d 'action=login=admin=admin' -k
>>
>>
>> curl -b cookies -k
>> https://localhost:9443/publisher/site/blocks/item-add/ajax/add.jag -d
>> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
>> a phone
>> number=phone,mobile,multimedia=nonsecured===Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
>> x...@ee.com=xx=g...@ww.com"
>> -d'endpoint_config={"production_endpoints":{"url":"
>> http://ws.cdyne.com/phoneverify/phoneverify.asmx","config":null},"endpoint_type":"http
>> "}';
>>
>> On Fri, Sep 11, 2015 at 4:18 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I got this error while trying the sample Add API command mentioned in
>>> the doc <https://docs.wso2.com/display/AM190/Publisher+APIs>. No
>>> backend error is displayed, any idea?
>>>
>>>
>>> $ curl -X POST -c cookies
>>> http://localhost:9763/publisher/site/blocks/user/login/ajax/login.jag
>>> -d 'action=login=admin=admin'
>>> {"error" : false}
>>>
>>>
>>> $ curl -X POST -b cookies
>>> http://localhost:9763/publisher/site/blocks/item-add/ajax/add.jag -d
>>> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
>>> a phone
>>> number=phone,mobile,multimedia=nonsecured=Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
>>> x...@ee.com=xx=g...@ww.com"
>>> -d'endpoint_config={"production_endpoints":{"url":"
>>> http://ws.cdyne.com/phoneverify/phoneverify.asmx
>>> ","config":null},"endpoint_type":"http"}';
>>> {"error" : true, "message" : "*timeout*"}
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48
by another process means, two servers are running at
>>>>>>>> the
>>>>>>>> same time?
>>>>>>>>
>>>>>>>> On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
>>>>>>>> niran...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> I was able to build the Kernel 4.4.x branch successfully. As Supun
>>>>>>>>> mentioned this looks like an intermittent issue. I will look into
>>>>>>>>> this further and update this thread.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Nira
>>>>>>>>>
>>>>>>>>> On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
>>>>>>>>> niran...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Supun,
>>>>>>>>>>
>>>>>>>>>> I will look into this. Just now triggered a build in openstack.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Nira
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga <sup...@wso2.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
>>>>>>>>>>> test method fails saying below,
>>>>>>>>>>>
>>>>>>>>>>> Aruna/ Niranjan can one of you have a look ? This is 4.4.x
>>>>>>>>>>> branch.
>>>>>>>>>>> fyi, I built 4.4.x last night with all tests and build passed
>>>>>>>>>>> for me. May be this is intermittent.
>>>>>>>>>>>
>>>>>>>>>>> INFO
>>>>>>>>>>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
>>>>>>>>>>> - [2015-09-11 02:04:44,020] FATAL
>>>>>>>>>>> {org.wso2.carbon.utils.dbcreator.DatabaseCreator} - Failed to
>>>>>>>>>>> create database tables for registry resource store. Database may be
>>>>>>>>>>> already in use: "Locked by another process". Possible solutions:
>>>>>>>>>>> close all other connection(s); use the server mode; SQL
>>>>>>>>>>> statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b
>>>>>>>>>>> [90020-140] (Sanitized)
>>>>>>>>>>> INFO
>>>>>>>>>>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
>>>>>>>>>>> - org.h2.jdbc.JdbcSQLException: Database may be already in use:
>>>>>>>>>>> "Locked by another process". Possible solutions: close all other
>>>>>>>>>>> connection(s); use the server mode; SQL statement:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/org.wso2.carbon$org.wso2.carbon.kernel.integration.test/48/testReport/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 11, 2015 at 7:47 AM, <cbuil...@wso2.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> See <
>>>>>>>>>>>> https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/48/changes>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Supun Malinga,
>>>>>>>>>>>
>>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>>> WSO2 Inc.
>>>>>>>>>>> http://wso2.com
>>>>>>>>>>> email: sup...@wso2.com <sup...@wso2.com>
>>>>>>>>>>> mobile: +94 (0)71 56 91 321
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> *Niranjan Karunanandham*
>>>>>>>>>> Senior Software Engineer - WSO2 Inc.
>>>>>>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> *Niranjan Karunanandham*
>>>>>>>>> Senior Software Engineer - WSO2 Inc.
>>>>>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>>>>>
>>>>>>>>> ___
>>>>>>>>> Dev mailing list
>>>>>>>>> Dev@wso2.org
>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> S.Uthaiyashankar
>>>>>>>> VP Engineering
>>>>>>>> WSO2 Inc.
>>>>>>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>>>>>>
>>>>>>>> Phone: +94 714897591
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> *Niranjan Karunanandham*
>>>>>>> Senior Software Engineer - WSO2 Inc.
>>>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> S.Uthaiyashankar
>>>>>> VP Engineering
>>>>>> WSO2 Inc.
>>>>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>>>>
>>>>>> Phone: +94 714897591
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *Niranjan Karunanandham*
>>>>> Senior Software Engineer - WSO2 Inc.
>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> S.Uthaiyashankar
>>>> VP Engineering
>>>> WSO2 Inc.
>>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>>
>>>> Phone: +94 714897591
>>>>
>>>
>>>
>>>
>>> --
>>> S.Uthaiyashankar
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>
>>> Phone: +94 714897591
>>>
>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> S.Uthaiyashankar
> VP Engineering
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> Phone: +94 714897591
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48
m <
>>>>>>>> niran...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Supun,
>>>>>>>>>
>>>>>>>>> I will look into this. Just now triggered a build in openstack.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Nira
>>>>>>>>>
>>>>>>>>> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga <sup...@wso2.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
>>>>>>>>>> test method fails saying below,
>>>>>>>>>>
>>>>>>>>>> Aruna/ Niranjan can one of you have a look ? This is 4.4.x
>>>>>>>>>> branch.
>>>>>>>>>> fyi, I built 4.4.x last night with all tests and build passed for
>>>>>>>>>> me. May be this is intermittent.
>>>>>>>>>>
>>>>>>>>>> INFO
>>>>>>>>>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
>>>>>>>>>> - [2015-09-11 02:04:44,020] FATAL
>>>>>>>>>> {org.wso2.carbon.utils.dbcreator.DatabaseCreator} - Failed to
>>>>>>>>>> create database tables for registry resource store. Database may be
>>>>>>>>>> already in use: "Locked by another process". Possible solutions:
>>>>>>>>>> close all other connection(s); use the server mode; SQL
>>>>>>>>>> statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b
>>>>>>>>>> [90020-140] (Sanitized)
>>>>>>>>>> INFO
>>>>>>>>>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
>>>>>>>>>> - org.h2.jdbc.JdbcSQLException: Database may be already in use:
>>>>>>>>>> "Locked by another process". Possible solutions: close all other
>>>>>>>>>> connection(s); use the server mode; SQL statement:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/org.wso2.carbon$org.wso2.carbon.kernel.integration.test/48/testReport/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Sep 11, 2015 at 7:47 AM, <cbuil...@wso2.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> See <
>>>>>>>>>>> https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/48/changes>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Supun Malinga,
>>>>>>>>>>
>>>>>>>>>> Senior Software Engineer,
>>>>>>>>>> WSO2 Inc.
>>>>>>>>>> http://wso2.com
>>>>>>>>>> email: sup...@wso2.com <sup...@wso2.com>
>>>>>>>>>> mobile: +94 (0)71 56 91 321
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> *Niranjan Karunanandham*
>>>>>>>>> Senior Software Engineer - WSO2 Inc.
>>>>>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> *Niranjan Karunanandham*
>>>>>>>> Senior Software Engineer - WSO2 Inc.
>>>>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> S.Uthaiyashankar
>>>>>>> VP Engineering
>>>>>>> WSO2 Inc.
>>>>>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>>>>>
>>>>>>> Phone: +94 714897591
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *Niranjan Karunanandham*
>>>>>> Senior Software Engineer - WSO2 Inc.
>>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> S.Uthaiyashankar
>>>>> VP Engineering
>>>>> WSO2 Inc.
>>>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>>>
>>>>> Phone: +94 714897591
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Niranjan Karunanandham*
>>>> Senior Software Engineer - WSO2 Inc.
>>>> WSO2 Inc.: http://www.wso2.com
>>>>
>>>
>>>
>>>
>>> --
>>> S.Uthaiyashankar
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>
>>> Phone: +94 714897591
>>>
>>
>>
>>
>> --
>> S.Uthaiyashankar
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>>
>> Phone: +94 714897591
>>
>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Tenant login failed on wso2am-1.10.0-SNAPSHOT from 1.10.x branch
(AuthenticatorBase.java:504) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:99) at org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47) at org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:57) at org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:62) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:159) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:57) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1739) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1698) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Integration Tests] What is the advantage of Exception being thrown in test methods instead of the specific subclass of it?
Hi Manuri, Even if we throws the sub classes in test methods , no one will handle those exception explicitly. It is handled by TestNg and TestsNg marked them error when exception is thrown from a test method and we can see the actual exception class in test reports. Throwing super class also make sure that the test method will not be broken even exception classes is changed in the method which are used in test methods. Please refer the mail thread "Best Practice in Throwing Exceptions in test methods signature"@dev Thanks, Nuwanw On Tue, Sep 8, 2015 at 11:05 AM, Manuri Amaya Perera <manu...@wso2.com> wrote: > Hi, > > I got to know it is recommended to throw Exception in test methods instead > of the specific sub class of it. But generally in methods the good practice > is to throw the exception of the specific sub class. > > I'd like to know $subject. > > Thank you. > > -- > > *Manuri Amaya Perera* > > *Software Engineer* > > *WSO2 Inc.* > > *Blog: http://manuriamayaperera.blogspot.com > <http://manuriamayaperera.blogspot.com>* > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded
Hi Manuri, There are some test classes which start a new server with a port offset and those port configuration are kept in automation.xml and referred by a name. Ex: if the portOffset is 1, then the config is as bellow. Then the test class refer the post and hot config by referring the name "appServerInstance0002" and generate the server URLs. localhost 9764 9444 Now you have to increase the port offset in this classes to be 100 + portOffset and according to new port offset you have to change the configuration as well. localhost 9864 9544 Thanks, Nuwanw On Thu, Sep 3, 2015 at 12:07 PM, Manuri Amaya Perera <manu...@wso2.com> wrote: > Adding Dev > > On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera <manu...@wso2.com> > wrote: > >> Hi, >> >> At the moment, in automation.xml in test modules, the -DportOffset >> parameter has been set to 100 and the port values in relevant instances >> also have been changed accordingly. >> >> But in the test cases where internally a server is set up, the port >> offset values are being hard coded. These values also need to be moved >> forward by 100. A configuration can be added to automation.xml which can be >> read and used to do this. >> >> I'd like to discuss the best way to address this problem. >> >> Thank you. >> >> -- >> >> *Manuri Amaya Perera* >> >> *Software Engineer* >> >> *WSO2 Inc.* >> >> *Blog: http://manuriamayaperera.blogspot.com >> <http://manuriamayaperera.blogspot.com>* >> > > > > -- > > *Manuri Amaya Perera* > > *Software Engineer* > > *WSO2 Inc.* > > *Blog: http://manuriamayaperera.blogspot.com > <http://manuriamayaperera.blogspot.com>* > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AS] [Tests] Port offset change in test cases where offset values are hardcoded
HI Supun, On Thu, Sep 3, 2015 at 12:29 PM, Supun Malinga <sup...@wso2.com> wrote: > > > On Thu, Sep 3, 2015 at 12:24 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Manuri, >> There are some test classes which start a new server with a port offset >> and those port configuration are kept in automation.xml and referred by a >> name. >> > > This is true Nuwan. But the concern is that in the test cases where we use > a offset. We have the offset hardcoded. Instead we need to read it from the > config file (automation.xml). > So what we thought is to put it as a property in the config of the > instances. > eg: > nonBlockingTransportEnabled="false"> > > localhost > > > 9764 > 9444 > > ** > ** > ** > > +1. This is better approach. Then we can read the offset from the config property and set Thanks, Nuwanw > > thanks, > > >> > >> Ex: if the portOffset is 1, then the config is as bellow. Then the test >> class refer the post and hot config by referring the name >> "appServerInstance0002" and generate the server URLs. >> >> > nonBlockingTransportEnabled="false"> >> >> localhost >> >> >> 9764 >> 9444 >> >> >> >> Now you have to increase the port offset in this classes to be 100 + >> portOffset and according to new port offset you have to change the >> configuration as well. >> >> > nonBlockingTransportEnabled="false"> >> >> localhost >> >> >> 9864 >> 9544 >> >> >> >> Thanks, >> Nuwanw >> >> On Thu, Sep 3, 2015 at 12:07 PM, Manuri Amaya Perera <manu...@wso2.com> >> wrote: >> >>> Adding Dev >>> >>> On Thu, Sep 3, 2015 at 11:50 AM, Manuri Amaya Perera <manu...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> At the moment, in automation.xml in test modules, the -DportOffset >>>> parameter has been set to 100 and the port values in relevant instances >>>> also have been changed accordingly. >>>> >>>> But in the test cases where internally a server is set up, the port >>>> offset values are being hard coded. These values also need to be moved >>>> forward by 100. A configuration can be added to automation.xml which can be >>>> read and used to do this. >>>> >>>> I'd like to discuss the best way to address this problem. >>>> >>>> Thank you. >>>> >>>> -- >>>> >>>> *Manuri Amaya Perera* >>>> >>>> *Software Engineer* >>>> >>>> *WSO2 Inc.* >>>> >>>> *Blog: http://manuriamayaperera.blogspot.com >>>> <http://manuriamayaperera.blogspot.com>* >>>> >>> >>> >>> >>> -- >>> >>> *Manuri Amaya Perera* >>> >>> *Software Engineer* >>> >>> *WSO2 Inc.* >>> >>> *Blog: http://manuriamayaperera.blogspot.com >>> <http://manuriamayaperera.blogspot.com>* >>> >> >> >> >> -- >> Nuwan Wimalasekara >> Senior Software Engineer - Test Automation >> WSO2, Inc.: http://wso2.com >> lean. enterprise. middleware >> >> phone: +94 71 668 4620 >> >> >> >> > > > -- > Supun Malinga, > > Senior Software Engineer, > WSO2 Inc. > http://wso2.com > email: sup...@wso2.com <sup...@wso2.com> > mobile: +94 (0)71 56 91 321 > -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets
Hi Manuri,
in ReadOnlyLDAPUserStoreManagerTestCase, UserStoreManager configuration is
changed in user-mgt.xml for read only user store. user-mgt.xml is kept in
the artifacts/AS/configs/readonlyldap/user-mgt.xml and the LDAP url is hard
coded in this resource.
ldap://localhost:10389
Please change the URL as below since the server is starting with port
offset(100) now. Otherwise it will failed to start the server with read
only user store configuration
ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}
Thanks,
Nuwanw
On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera <manu...@wso2.com>
wrote:
> Hi Nuwan,
>
> According to our offline discussion I set the carbon home system property
> in CarbonServerWithReadWriteLdapUSerStoreExtension inside onExecutionStart
> method. Now the problem in carbon home not being set is solved.
>
> Now, when running the testcase these exceptions occur and build fails.
>
> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
> Time elapsed: 2,284.473 sec <<< FAILURE!
> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
> at
> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
> at
> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>
> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
> Time elapsed: 0.003 sec <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>
> I think these are authorization issues relevant to LDAP. Can you be of any
> help regarding this ?
>
> Thank you.
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> <http://manuriamayaperera.blogspot.com>*
>
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets
Hi Manuri
There is a port bind exception in the log file. Seems the LDAP server is
not shutdown properly. Please kill the process before executing the tests.
ERR_171 Failed to bind an LDAP service (10,489) to the service registry.
Thanks,
Nuwanw
On Thu, Sep 3, 2015 at 6:12 PM, Manuri Amaya Perera <manu...@wso2.com>
wrote:
> Please find the attached logs.
>
> On Thu, Sep 3, 2015 at 6:08 PM, Nuwan Wimalasekara <nuw...@wso2.com>
> wrote:
>
>> Can you please share the full log of the test module tests-ldap-userstore
>>
>> On Thu, Sep 3, 2015 at 6:04 PM, Manuri Amaya Perera <manu...@wso2.com>
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> I changed it but now there is some other exception.
>>>
>>> org.wso2.carbon.user.mgt.stub.UserAdminUserAdminException:
>>> UserAdminUserAdminException
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
>>> at java.lang.Class.newInstance(Class.java:379)
>>> at
>>> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1577)
>>> at
>>> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>>>
>>> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>> Time elapsed: 0.002 sec <<< FAILURE!
>>> java.lang.NullPointerException: null
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>>>
>>> Thank you.
>>>
>>> On Thu, Sep 3, 2015 at 5:29 PM, Nuwan Wimalasekara <nuw...@wso2.com>
>>> wrote:
>>>
>>>> Hi Manuri,
>>>>
>>>> in ReadOnlyLDAPUserStoreManagerTestCase, UserStoreManager
>>>> configuration is changed in user-mgt.xml for read only user store.
>>>> user-mgt.xml is kept in the artifacts/AS/configs/readonlyldap/user-mgt.xml
>>>> and the LDAP url is hard coded in this resource.
>>>>
>>>> ldap://localhost:10389
>>>>
>>>> Please change the URL as below since the server is starting with port
>>>> offset(100) now. Otherwise it will failed to start the server with read
>>>> only user store configuration
>>>>
>>>> >>> name="ConnectionURL">ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}
>>>>
>>>> Thanks,
>>>> Nuwanw
>>>>
>>>> On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera <manu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Nuwan,
>>>>>
>>>>> According to our offline discussion I set the carbon home system
>>>>> property in CarbonServerWithReadWriteLdapUSerStoreExtension
>>>>> inside onExecutionStart method. Now the problem in carbon home not being
>>>>> set is solved.
>>>>>
>>>>> Now, when running the testcase these exceptions occur and build fails.
>>>>>
>>>>> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>>>> Time elapsed: 2,284.473 sec <<< FAILURE!
>>>>> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
>>>>> at
>>>>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
>>>>> at
>>>>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>>>>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>>>>> at
>>>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>>>>> at
>>>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>>>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>>>> at
>>>>> org.apache.axis2.description.OutInAxisOpera
Re: [Dev] org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase testcase failing after changing port offsets
Can you please share the full log of the test module tests-ldap-userstore
On Thu, Sep 3, 2015 at 6:04 PM, Manuri Amaya Perera <manu...@wso2.com>
wrote:
> Hi Nuwan,
>
> I changed it but now there is some other exception.
>
> org.wso2.carbon.user.mgt.stub.UserAdminUserAdminException:
> UserAdminUserAdminException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at java.lang.Class.newInstance(Class.java:379)
> at
> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1577)
> at
> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>
> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
> Time elapsed: 0.002 sec <<< FAILURE!
> java.lang.NullPointerException: null
> at
> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
>
> Thank you.
>
> On Thu, Sep 3, 2015 at 5:29 PM, Nuwan Wimalasekara <nuw...@wso2.com>
> wrote:
>
>> Hi Manuri,
>>
>> in ReadOnlyLDAPUserStoreManagerTestCase, UserStoreManager configuration
>> is changed in user-mgt.xml for read only user store. user-mgt.xml is kept
>> in the artifacts/AS/configs/readonlyldap/user-mgt.xml and the LDAP url is
>> hard coded in this resource.
>>
>> ldap://localhost:10389
>>
>> Please change the URL as below since the server is starting with port
>> offset(100) now. Otherwise it will failed to start the server with read
>> only user store configuration
>>
>> > name="ConnectionURL">ldap://localhost:${Ports.EmbeddedLDAP.LDAPServerPort}
>>
>> Thanks,
>> Nuwanw
>>
>> On Thu, Sep 3, 2015 at 4:48 PM, Manuri Amaya Perera <manu...@wso2.com>
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> According to our offline discussion I set the carbon home system
>>> property in CarbonServerWithReadWriteLdapUSerStoreExtension
>>> inside onExecutionStart method. Now the problem in carbon home not being
>>> set is solved.
>>>
>>> Now, when running the testcase these exceptions occur and build fails.
>>>
>>> configureServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>> Time elapsed: 2,284.473 sec <<< FAILURE!
>>> org.apache.axis2.AxisFault: Transport error: 401 Error: Unauthorized
>>> at
>>> org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:330)
>>> at
>>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:196)
>>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:77)
>>> at
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:451)
>>> at
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:278)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:430)
>>> at
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>>> at
>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>>> at
>>> org.wso2.carbon.user.mgt.stub.UserAdminStub.addUser(UserAdminStub.java:1563)
>>> at
>>> org.wso2.carbon.integration.common.admin.client.UserManagementClient.addUser(UserManagementClient.java:89)
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.configureServer(ReadOnlyLDAPUserStoreManagerTestCase.java:68)
>>>
>>> restoreServer(org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase)
>>> Time elapsed: 0.003 sec <<< FAILURE!
>>> java.lang.NullPointerException: null
>>> at
>>> org.wso2.appserver.integration.tests.readonlyldap.ReadOnlyLDAPUserStoreManagerTestCase.restoreServer(ReadOnlyLDAPUserStoreManagerTestCase.java:225)
&
Re: [Dev] [GREG] Error when adding JaCoco code coverage to test automation
gt;> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:358) >> at >> org.wso2.carbon.automation.engine.frameworkutils.ReportGenerator.analyzeStructure(ReportGenerator.java:144) >> at >> org.wso2.carbon.automation.engine.frameworkutils.ReportGenerator.create(ReportGenerator.java:77) >> at >> org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager.generateCoverageReport(CarbonServerManager.java:333) >> at >> org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager.serverShutdown(CarbonServerManager.java:309) >> at >> org.wso2.carbon.automation.extensions.servers.carbonserver.TestServerManager.stopServer(TestServerManager.java:132) >> at >> org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.onExecutionFinish(CarbonServerExtension.java:61) >> ... 20 more >> org.apache.maven.surefire.util.SurefireReflectionException: >> java.lang.reflect.InvocationTargetException; nested exception is >> java.lang.reflect.InvocationTargetException: null >> java.lang.reflect.InvocationTargetException >> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) >> at >> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) >> at >> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) >> at >> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) >> at >> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) >> Caused by: java.lang.RuntimeException: Error while tear down the >> execution environment >> at >> org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.handleException(TestExecutionListener.java:71) >> at >> org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionFinish(TestExecutionListener.java:65) >> at org.testng.TestNG.runExecutionListeners(TestNG.java:1033) >> at org.testng.TestNG.run(TestNG.java:1013) >> at >> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178) >> at >> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) >> at >> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) >> ... 9 more >> Caused by: java.lang.reflect.InvocationTargetException >> 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.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:75) >> at >> org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionFinish(TestExecutionListener.java:62) >> ... 14 more >> Caused by: java.lang.IncompatibleClassChangeError: class >> org.jacoco.core.internal.flow.ClassProbesVisitor has interface >> org.objectweb.asm.ClassVisitor as super class >> at java.lang.ClassLoader.defineClass1(Native Method) >> at java.lang.ClassLoader.defineClass(ClassLoader.java:800) >> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) >> at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) >> at java.net.URLClassLoader.access$100(URLClassLoader.java:71) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:361) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:355) >> at java.security.AccessController.doPrivileged(Native Method) >> at java.net.URLClassLoader.findClass(URLClassLoader.java:354) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:425) >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:358) >> at >> org.wso2.carbon.automation.engine.frameworkutils.ReportGenerator.analyzeStructure(ReportGenerator.java:144) >> at >> org.wso2.carbon.automation.engine.frameworkutils.ReportGenerator.create(ReportGenerator.java:77) >> at >> org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager.generateCoverag
Re: [Dev] [GREG] Error when adding JaCoco code coverage to test automation
Hi Rajith, I could reproduce the same error in test module cmis-tck. I will have a look on this issue. Thanks, Nuwanw On Wed, Sep 2, 2015 at 12:46 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote: > Hi Rajith, > > I could generate coverage for the test module tests-resources successfully > in GReg 5.0.0-SNAPSHOT. I updated the test framework version to 4.4.2 and > change the pom configuration as the document. Then it generated the > coverage without any issue. > > Which framework version have you used and which test module gives the > above error? > > Thanks, > Nuwanw > > On Wed, Sep 2, 2015 at 11:02 AM, Rajith Roshan <raji...@wso2.com> wrote: > >> Hi all, >> >> Please find the correct doc link in [1] which, I referred when updating >> the test automation >> >> [1] - >> https://docs.google.com/document/d/1pMJGdRH4Kmc4J3rYzgnpGlR5AnSeoC4QL9gMX9tUhYs/edit#heading=h.yemie7ivahbz >> <https://docs.google.com/document/d/1pMJGdRH4Kmc4J3rYzgnpGlR5AnSeoC4QL9gMX9tUhYs/edit#heading=h.yemie7ivahbz> >> >> Thanks! >> Rajith >> >> On Wed, Sep 2, 2015 at 10:57 AM, Rajith Roshan <raji...@wso2.com> wrote: >> >>> Hi Devs, >>> >>> I refer the doc [1] for updating Jacoco code coverage tool for >>> integration tests in product G-Reg. It builds successfully when code >>> coverage is set to false in automation.xml as follows. >>> >>> false >>> >>> Please do find automation.xml, pom.xml and automationlog files for the >>> respective test module in [2] >>> >>> [1] - >>> https://drive.google.com/a/wso2.com/folderview?id=0B8xmd1n2DieYfjk2X0Fnb20yMUF0TnI1X1NIek5zTXFtUmhhU0wxRXFTQ1lCQ19qSlN5RmM=sharing >>> >>> [2] - >>> https://drive.google.com/a/wso2.com/folderview?id=0B8xmd1n2DieYfjk2X0Fnb20yMUF0TnI1X1NIek5zTXFtUmhhU0wxRXFTQ1lCQ19qSlN5RmM=sharing >>> >>> But it gives the following error when code coverage is enabled. Further >>> I excluded "asm" from the jacoco dependency. But it gives the same error. >>> Any help will be appreciated. >>> >>> >>> ERROR >>> [org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener] - >>> Execution error occurred in TestExecutionListener:- >>> java.lang.reflect.InvocationTargetException >>> 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.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:75) >>> at >>> org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionFinish(TestExecutionListener.java:62) >>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1033) >>> at org.testng.TestNG.run(TestNG.java:1013) >>> at >>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178) >>> at >>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) >>> at >>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) >>> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) >>> at >>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) >>> at >>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) >>> at >>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) >>> at >>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) >>> Caused by: java.lang.IncompatibleClassChangeError: class >>> org.jacoco.core.internal.flow.ClassProbesVisitor has interface >>> org.objectweb.asm.ClassVisitor as super class >>> at java.lang.ClassLoader.defineClass1(Native Method) >>> at java.lang.ClassLoader.defineClass(ClassLoader.java:800) >>> at >>> java
Re: [Dev] [GREG] Error when adding JaCoco code coverage to test automation
Hi Rajith, The issue is with the asm dependency. asm dependency should be removed from all dependencies. Please exclude the asm dependency from org.wso2.carbon.registry.activities as well. This will solve above issue. org.wso2.carbon.registry org.wso2.carbon.registry.activities asm asm Thanks, Nuwanw On Wed, Sep 2, 2015 at 1:02 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote: > Hi Rajith, > > I could reproduce the same error in test module cmis-tck. I will have a > look on this issue. > > Thanks, > Nuwanw > > On Wed, Sep 2, 2015 at 12:46 PM, Nuwan Wimalasekara <nuw...@wso2.com> > wrote: > >> Hi Rajith, >> >> I could generate coverage for the test module tests-resources >> successfully in GReg 5.0.0-SNAPSHOT. I updated the test framework version >> to 4.4.2 and change the pom configuration as the document. Then it >> generated the coverage without any issue. >> >> Which framework version have you used and which test module gives the >> above error? >> >> Thanks, >> Nuwanw >> >> On Wed, Sep 2, 2015 at 11:02 AM, Rajith Roshan <raji...@wso2.com> wrote: >> >>> Hi all, >>> >>> Please find the correct doc link in [1] which, I referred when updating >>> the test automation >>> >>> [1] - >>> https://docs.google.com/document/d/1pMJGdRH4Kmc4J3rYzgnpGlR5AnSeoC4QL9gMX9tUhYs/edit#heading=h.yemie7ivahbz >>> <https://docs.google.com/document/d/1pMJGdRH4Kmc4J3rYzgnpGlR5AnSeoC4QL9gMX9tUhYs/edit#heading=h.yemie7ivahbz> >>> >>> Thanks! >>> Rajith >>> >>> On Wed, Sep 2, 2015 at 10:57 AM, Rajith Roshan <raji...@wso2.com> wrote: >>> >>>> Hi Devs, >>>> >>>> I refer the doc [1] for updating Jacoco code coverage tool for >>>> integration tests in product G-Reg. It builds successfully when code >>>> coverage is set to false in automation.xml as follows. >>>> >>>> false >>>> >>>> Please do find automation.xml, pom.xml and automationlog files for the >>>> respective test module in [2] >>>> >>>> [1] - >>>> https://drive.google.com/a/wso2.com/folderview?id=0B8xmd1n2DieYfjk2X0Fnb20yMUF0TnI1X1NIek5zTXFtUmhhU0wxRXFTQ1lCQ19qSlN5RmM=sharing >>>> >>>> [2] - >>>> https://drive.google.com/a/wso2.com/folderview?id=0B8xmd1n2DieYfjk2X0Fnb20yMUF0TnI1X1NIek5zTXFtUmhhU0wxRXFTQ1lCQ19qSlN5RmM=sharing >>>> >>>> But it gives the following error when code coverage is enabled. Further >>>> I excluded "asm" from the jacoco dependency. But it gives the same error. >>>> Any help will be appreciated. >>>> >>>> >>>> ERROR >>>> [org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener] - >>>> Execution error occurred in TestExecutionListener:- >>>> java.lang.reflect.InvocationTargetException >>>> 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.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:75) >>>> at >>>> org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionFinish(TestExecutionListener.java:62) >>>> at org.testng.TestNG.runExecutionListeners(TestNG.java:1033) >>>> at org.testng.TestNG.run(TestNG.java:1013) >>>> at >>>> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178) >>>> at >>>> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) >>>> at >>>> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) >>>> 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.apache.maven.surefire.util.Refl
Re: [Dev] Automated tests to tests Application Server with Apache Ldap as a User Store
On Mon, Jul 27, 2015 at 5:13 PM, KasunG Gajasinghe kas...@wso2.com wrote: Thanks Nuwan for checking into this. On Wed, Jul 22, 2015 at 2:18 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Kasun, Please find the inline answers. On Tue, Jul 21, 2015 at 8:39 PM, KasunG Gajasinghe kas...@wso2.com wrote: Hi Nuwan, Can you please answer following questions regarding this PR? 1. Can you rename to module name tests-with-ldap to tests-ldap-userstores. I believe that's more meaningful. Yes. This is more meaningful. will rename the module 2. Shouldn't the distribution-with-apache-ldap be placed under tests-common module? We need a proper name for this module as well, since for new eyes, the name seems to be less meaningful. How about ldap-installed-wso2as-distribution? Please let me know if you have a better name. :-) As discussed, the module is renamed as ldap-server-feature-installed-wso2as. I do not think the module which build distribution move into tests-common module. tests-common module contains the AS test utilities. Having a new distribution in integration level is fine. I will discuss and put a meaningful name for the module which built AS distribution having Apache Ldap server feature itself 3. What does it mean to have a test case with only a @Factory annotation - ReadWriteLdapUserStoreAdminUserTestCase I did not duplicate the UserManagement Test cases in this test module. I reuse the same user management test cases which are in the tests module already implemented for JDBC user store. So I implement a new class extending the existing class. Then same test methods are executing against the readwrite Ldap user store . In that class We have to implement a constructor with @Factory annotation referring the same data provider in order to execute the test class. 4. The sub-modules should not have the version tag in maven dependencies. The version should be defined in the root pom. Fixed it by removing version. Thanks, Nuwanw Thanks. On Tue, Jul 21, 2015 at 2:53 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi, We have integrate a tests module(tests-with-ldap)[1] in AS integration to test the user management in AS with apache Ldap server as the user store. Ldap server feature is installed on AS by building a distribution with ldap server feature and the built server is used by the tests-with-ldap module throughout the test execution. This module executes 100 test cases with the user store as ReadWrite and ReadOnly modes by changing the user-mgt.xml. All the user management test cases in tests module are executed against the ReadWrite Ldap user store and implemented a test class to test the ReadOnly Ldap functionalities as well. [1] https://github.com/wso2/product-as/pull/152 Please refer the attached surefire-reports.zip for test cases Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automated tests to tests Application Server with Apache Ldap as a User Store
Hi Kasun, Please find the inline answers. On Tue, Jul 21, 2015 at 8:39 PM, KasunG Gajasinghe kas...@wso2.com wrote: Hi Nuwan, Can you please answer following questions regarding this PR? 1. Can you rename to module name tests-with-ldap to tests-ldap-userstores. I believe that's more meaningful. Yes. This is more meaningful. will rename the module 2. Shouldn't the distribution-with-apache-ldap be placed under tests-common module? We need a proper name for this module as well, since for new eyes, the name seems to be less meaningful. How about ldap-installed-wso2as-distribution? Please let me know if you have a better name. :-) I do not think the module which build distribution move into tests-common module. tests-common module contains the AS test utilities. Having a new distribution in integration level is fine. I will discuss and put a meaningful name for the module which built AS distribution having Apache Ldap server feature itself 3. What does it mean to have a test case with only a @Factory annotation - ReadWriteLdapUserStoreAdminUserTestCase I did not duplicate the UserManagement Test cases in this test module. I reuse the same user management test cases which are in the tests module already implemented for JDBC user store. So I implement a new class extending the existing class. Then same test methods are executing against the readwrite Ldap user store . In that class We have to implement a constructor with @Factory annotation referring the same data provider in order to execute the test class. 4. The sub-modules should not have the version tag in maven dependencies. The version should be defined in the root pom. Fixed it by removing version. Thanks, Nuwanw Thanks. On Tue, Jul 21, 2015 at 2:53 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi, We have integrate a tests module(tests-with-ldap)[1] in AS integration to test the user management in AS with apache Ldap server as the user store. Ldap server feature is installed on AS by building a distribution with ldap server feature and the built server is used by the tests-with-ldap module throughout the test execution. This module executes 100 test cases with the user store as ReadWrite and ReadOnly modes by changing the user-mgt.xml. All the user management test cases in tests module are executed against the ReadWrite Ldap user store and implemented a test class to test the ReadOnly Ldap functionalities as well. [1] https://github.com/wso2/product-as/pull/152 Please refer the attached surefire-reports.zip for test cases Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Pull Requests for MQTT Integration tests.
Hi Mahika, Yes. AMQP also available with ActiveMQ server provided from framework. You can parse the TransportConnector with amqp endpoint to start the AMQP in ActiveMQ. Thanks, Nuwanw On Wed, Jul 15, 2015 at 1:30 PM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi Nuwan, On another note, can AMQP also be enabled on ActiveMQ similarly? I am considering the possibility of using ActiveMQ as an AMQP broker. Thanks, Maheeka Maheeka Jayasuriya Software Engineer Mobile : +9450661 On Mon, Jul 13, 2015 at 11:22 AM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi MQTT is supported in test frameword 4.4.1 onward. ActiveMQ embedded server starts with mqtt endpoint. Thanks, Nuwanw On Mon, Jul 13, 2015 at 11:15 AM, Malaka Silva mal...@wso2.com wrote: +1 On Mon, Jul 13, 2015 at 11:14 AM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi Elilmatha/Malaka, In RabbitMQ, we added integration tests as a platform test. Please refer mail thread at [1] for details. Few things to notice : - Tests are added to tests-platform module and skipped to avoid failures in jenkins - RabbitMQBrokerStartupTestCase which will start the server before running tests and stop the server after - Broker location is configured with a property in automation.xml. Thus, in order to run the tests, it's a matter of pointing to a broker instance and enabling tests. This is for adding MQTT support to product-esb test framework. Shall we go ahead with a similar approach? WDYT? [1] [Dev] [TAF] Support for RabbitMQ Thanks, Maheeka Maheeka Jayasuriya Software Engineer Mobile : +9450661 On Mon, Jul 13, 2015 at 10:37 AM, Malaka Silva mal...@wso2.com wrote: Added some comments please check On Mon, Jul 13, 2015 at 10:30 AM, Malaka Silva mal...@wso2.com wrote: comment the test case in testng since framework does not support mqtt currently. Also put a reason mentioning the reason. On Mon, Jul 13, 2015 at 10:00 AM, Elilmatha Sivanesan elilma...@wso2.com wrote: Hi Malaka, Please review and merge PR [1] for MQTT Integration tests. [1] https://github.com/wso2/product-esb/pull/227 https://github.com/wso2/product-esb/pull/227 Thank you. -- *S.Elilmatha* Associate Software Engineer, WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile 0779842221. -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Pull Requests for MQTT Integration tests.
Hi MQTT is supported in test frameword 4.4.1 onward. ActiveMQ embedded server starts with mqtt endpoint. Thanks, Nuwanw On Mon, Jul 13, 2015 at 11:15 AM, Malaka Silva mal...@wso2.com wrote: +1 On Mon, Jul 13, 2015 at 11:14 AM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi Elilmatha/Malaka, In RabbitMQ, we added integration tests as a platform test. Please refer mail thread at [1] for details. Few things to notice : - Tests are added to tests-platform module and skipped to avoid failures in jenkins - RabbitMQBrokerStartupTestCase which will start the server before running tests and stop the server after - Broker location is configured with a property in automation.xml. Thus, in order to run the tests, it's a matter of pointing to a broker instance and enabling tests. This is for adding MQTT support to product-esb test framework. Shall we go ahead with a similar approach? WDYT? [1] [Dev] [TAF] Support for RabbitMQ Thanks, Maheeka Maheeka Jayasuriya Software Engineer Mobile : +9450661 On Mon, Jul 13, 2015 at 10:37 AM, Malaka Silva mal...@wso2.com wrote: Added some comments please check On Mon, Jul 13, 2015 at 10:30 AM, Malaka Silva mal...@wso2.com wrote: comment the test case in testng since framework does not support mqtt currently. Also put a reason mentioning the reason. On Mon, Jul 13, 2015 at 10:00 AM, Elilmatha Sivanesan elilma...@wso2.com wrote: Hi Malaka, Please review and merge PR [1] for MQTT Integration tests. [1] https://github.com/wso2/product-esb/pull/227 https://github.com/wso2/product-esb/pull/227 Thank you. -- *S.Elilmatha* Associate Software Engineer, WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile 0779842221. -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AM][TEST] java.lang.ClassNotFoundException: org.h2.Driver
Hi Chamalee
Then add below to the test module pom.
dependency
groupIdcom.h2database.wso2/groupId
artifactIdh2-database-engine/artifactId
/dependency
Thanks,
Nuwanw
On Thu, Jul 9, 2015 at 3:13 PM, Chamalee De Silva chama...@wso2.com wrote:
Hi,
No. Only in the parent pom.xml of product-apim it has the following
dependency.
dependency
groupIdcom.h2database.wso2/groupId
artifactIdh2-database-engine/artifactId
version${orbit.version.h2.engine}/version
/dependency
On Thu, Jul 9, 2015 at 3:07 PM, Irham Iqbal iq...@wso2.com wrote:
Hi Chamalee,
Can you please make sure whether you have dependency related to org.h2.Driver
in your tests-integration module pom.xml
Thanks,
Iqbal
On Thu, Jul 9, 2015 at 2:57 PM, Chamalee De Silva chama...@wso2.com
wrote:
hi all,
I am writing a test case for WSO2 API Manager to test Read Only External
Stores in java.
I pointed the WSO2CARBON_DB to add Roles and Users.
But when I build it fails with a ClassNotFoundException for the
following. ( java.lang.ClassNotFoundException: org.h2.Driver)
H2DataBaseManager dbmanager = new H2DataBaseManager(jdbc:h2: +
ServerConfigurationManager.getCarbonHome() +
/repository/database/WSO2CARBON_DB, wso2carbon', wso2carbon);
dbmanager.executeUpdate(new
File(ServerConfigurationManager.getCarbonHome() + /dbscripts/h2.sql));
dbmanager.disconnect();
*Error Log : *
java.lang.ClassNotFoundException: org.h2.Driver
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:171)
at
org.wso2.carbon.automation.test.utils.dbutils.H2DataBaseManager.init(H2DataBaseManager.java:39)
at
org.wso2.am.integration.tests.other.ReadOnlyExternalStoreAPITokenGenerationTestCase.setEnvironment(ReadOnlyExternalStoreAPITokenGenerationTestCase.java:94)
PS : I am creating the external store in the environment setup before
the test start to run.
Any ideas to resolve this issue?
--
Thanks Regards,
*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware
Office :- *+94 11 2145345 %2B94%2011%202145345*
mobile :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Irham Iqbal
Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 777888452
--
Thanks Regards,
*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. .:http://wso2.com
lean *.* enterprise *.* middleware
Office :- *+94 11 2145345 %2B94%2011%202145345*
mobile :- *+94 7 %2B94%2077%2027820391 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge the carbon4-kernel integration test commit#287
Hi Carbon Team, Please merge the pull request https://github.com/wso2/carbon4-kernel/pull/287 Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge the carbon4-kernel integration test commit#269
Hi Carbon Team, Please merge the pull request https://github.com/wso2/carbon4-kernel/pull/269 Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge the AS integration test commit#118
Hi AS Team, Please merge the pull request https://github.com/wso2/product-as/pull/118. This will add a test module to execute kernel integration tests on AS. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Best Practice in Throwing Exceptions in test methods signature
Hi Hemika,
It does not matter. You can have expectedExceptions attribute with any
exception class when the method signature throws Exception class. Cause
expectedExceptions will check the instance of thrown exception class with
the exception class defined with expectedExceptions. Below sample test
method will marked as passed.
@Test( expectedExceptions = {*IOException*.class})
public void testMethod() throws *Exception* {
.
throw new *IOException*(File Not Found);
}
Thanks,
Nuwanw
On Thu, Jul 2, 2015 at 6:53 PM, Hemika Kodikara hem...@wso2.com wrote:
Hi Nuwan,
Sorry for barging in like this.
I agree with your statement, but what if we want to pass a test cases only
if a specific exception is thrown. TestNG allows the expectedExceptions
annotation to help this out. See [1]. Else we would have to use a try/catch
to catch the specific exception and then pass or fail the test case using
Assert.fail() method depending on the implementation.
[1] - http://www.tutorialspoint.com/testng/testng_exception_test.htm
Regards,
Hemika
Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com
Mobile : +9477762
On Thu, Jul 2, 2015 at 6:16 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi
It is always better to throw the Exception(super class) as a best
practice when we define a test method rather than throwing the list of
particular exceptions since no one will catch those exception and handle
explicitly. Then it will ensure that the test method will not break once
the methods used within the test method changed and in the test reports It
shows the actual Exception class. So It will ease the test classes
maintainability.
@Test()
public void testMethod() throws *Exception* {
}
Thanks,
Nuwanw
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Integration Tests] Running test cases one by one
Hi Mahesh, You can use -Dtest parameter to define the test classes which need to run. mvn clean install -Dtest=TestClassName Thanks, Nuwanw On Mon, Jun 29, 2015 at 6:13 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi all, Suppose I have declared some test cases in testng.xml file , is there a way that I could run one by one with each time i run mvn clean install. At the moment what we do is comment out rest of the test cases leaving required one enabled. Then run mvn clean install. Repeat the same for all the cases. Is there an another way to do without commenting out test cases in testng.xnl file ? May be giving a parameter or something. mvn clean install -Dsome_parameter_to_specify_test_case thanks. -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automation Test Framework - Copying a database with data into the product
Hi Nirmal, Yes. ExecutionListenerExtension can be used and It will execute before all the test classes execution. Thanks, Nuwanw On Sun, Jun 28, 2015 at 6:20 PM, Nirmal Fernando nir...@wso2.com wrote: Hi All, We have a scenario where we need to populate a pre-generated DB file into the product before the product starts up. What's the method we should follow? If what we need is an ExecutionListenerExtension ( https://docs.wso2.com/display/TA430/Pluggable+Module+Executors) when does it really get executed? Is it after the server start-up? -- Thanks regards, Nirmal Associate Technical Lead - Data Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge the carbon4-kernel integration test commit#252
Hi Carbon Team, Please merge the pull request https://github.com/wso2/carbon4-kernel/pull/252 Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Automated Test cases for Java Security Manager with AS 6.0.0-SNAPSHOT
.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Accessing registry database configurations test *testGetRegistryDBConfigSecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Accessing registry database configurations test *testGetUserManagerDBConfigSecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Accessing user management database configurations *testGetUserManagerDBConfigSecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Accessing user management database configurations *testGettingSystemPropertySecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Accessing System Properties *testGettingSystemPropertySecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Accessing System Properties *testGettingSystemPropertySecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerPolicyTestCase Test method: Accessing System Properties *testGettingSystemPropertySecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerPolicyTestCase Test method: Accessing System Properties *testWritingFileUnderConfDirSecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Creating a file on the server *testWritingFileUnderConfDirSecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerTestCase Test method: Creating a file on the server *testWritingFileUnderConfDirSecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerPolicyTestCase Test method: Creating a file on the server *testWritingFileUnderConfDirSecurity* Test class: org.wso2.carbon.appserver.integration.test.server.security.manager.JavaSecurityManagerPolicyTestCase Test method: Creating a file on the server Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fixed the API Manager 1.9.0-SNAPSHOT Platform Auto Test
Hi I have fixed[1] the existing two platform tests(SingleSignOnTestCase, APIUsageBAMIntegrationTestCase)[2] for SSO Login and Publishing API Runtime Statistics with BAM. Please refer Test Class description for how to run the test classes since API manager and BAM need to be configured accordingly. [1] https://github.com/wso2/product-apim/pull/222 [2] https://github.com/wso2/product-apim/tree/master/modules/integration/tests-platform Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge the AS Integration test commit#76
Hi AS Team, Please merge the pull request https://github.com/wso2/product-as/pull/76. This will enable the jacoco code coverage for the tests modules. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error - Running Integration test for connector with ESB-4.9.0.ALPHA
.carbon.connector:org.wso2.carbon.connector.proworkflow:jar:1.0.0: The following artifacts could not be resolved: org.wso2.carbon:org.wso2.carbon.mediation.library.stub:jar:4.4.1, org.wso2.carbon.automation:org.wso2.carbon.automation.api:jar:4.4.1, org.wso2.carbon.automation:org.wso2.carbon.automation.core:jar:4.4.1, org.wso2.carbon.automation:org.wso2.carbon.automation.utils:jar:4.4.1, org.wso2.carbon:SecVerifier:aar:4.4.1: Failure to find org.wso2.carbon:org.wso2.carbon.mediation.library.stub:jar:4.4.1 in http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException esb:org.wso2.carbon.connector elilmatha$ Can any one suggest me with the proper versions to be changed in the pom [1] -- *S.Elilmatha* Associate Software Engineer, WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile 0779842221. [1] -- *S.Elilmatha* Associate Software Engineer, WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile 0779842221. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *S.Elilmatha* Associate Software Engineer, WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile 0779842221. -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Testing Jacoco based code coverage genration
Hi Ramith,
You can find the documentation from[1]
[1]
https://docs.google.com/document/d/1pMJGdRH4Kmc4J3rYzgnpGlR5AnSeoC4QL9gMX9tUhYs/edit#heading=h.yemie7ivahbz
Thanks,
Nuwanw
On Sat, May 23, 2015 at 4:18 PM, Ramith Jayasinghe ram...@wso2.com wrote:
do we have any documentation on this?
On Wed, May 13, 2015 at 6:58 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi all,
I have redesign Jacoco coverage generation a bit to support for coverage
merging functionality. Now coverage data dump into
$basedir/target/jacoco/coverage directory at the time of report generation,
jacoco coverage data files are merged back to a single file
(jacoco-data-merge.exec) and report will be generated using this merged
data file.
To merge multiple module test coverage data files. You can use pom file
with exec-maven-plugin to execute
org.wso2.carbon.automation.engine.frameworkutils.TestCoverageGenerator
class. This will generate merged report at
$basedir/target/jacoco/coverage/index.html.
I will write a comprehensive document on applying Jacoco coverage to
products.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 10:46 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Nuwan,
You can't use TestCoverageGenerator anymore (We need to remove this
class as well) . The merged report should be generated at the last test
module with got executed as we merge all coverage data to common file.
May be we can think of introducing pom file to do merging. If this
option is not user friendly.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 10:24 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi Krishantha,
I am getting below error when merging the coverage reports.
generateReports implementation is missing in CodeCoverageUtils. report
module use
the org.wso2.carbon.integration.common.utils.coverage.TestCoverageGenerator
to aggregate results.
Exception in thread main java.lang.NoSuchMethodError:
org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.generateReports(Ljava/util/List;)V
at
org.wso2.carbon.integration.common.utils.coverage.TestCoverageGenerator.main(TestCoverageGenerator.java:36)
Thanks,
Nuwanw
On Tue, May 5, 2015 at 9:47 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Yes. The correct implementation
is
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
We will remove the CarbonServerExtension from utils to get rid of
conflicts.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 9:27 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Nuwan,
You should remove
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension
not the
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 9:47 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi
We should
remove
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
from extensions. Then all the tests module should refer the correct
class.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Waruna,
On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com
wrote:
Hi Krishantha,
And we need to update Automation.xml to use following class
instead of one from utils.
Please remove the CarbonServerExtension class at utils. Its was
deprecated in last release and moved to test extensions to support for
carbon kernel startup.
Need to completely get rid of this extension class and its
dependencies.
Thanks,
Krishantha.
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
Thanks
On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara
nuw...@wso2.com wrote:
Hi Krishantha,
I tried generating coverage in ESB. It is working fine and
Coverage reports generated. However the coverage report aggregation
seems
not working when there are multiple tests modules. We need to fix the
issue.
test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT
Thanks,
Nuwanw
On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Correction : Step #1 configuration should be as follows.
execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution
Thanks,
Krishantha.
On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi all,
New coverage implementation using Jacoco has been committed to
master branch of carbon-platform-integration. I tried my best to
adhere to
existing Emma based design and reuse same instrumentation and
filters text
files. Note
[Dev] Please merge AS Integration test commit#65
Hi AS Team, Please merge the pull request https://github.com/wso2/product-as/pull/65 for java security manager test cases. Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge AS Integration test commit#64
Hi AS Team, Please merge the pull request https://github.com/wso2/product-as/pull/64. This will integrate the test module tests-security-manager to verify the java security manager and test the server operations are protected. [1] https://github.com/wso2/product-as/pull/64 Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test Automation Framework Support for MQTT Server
Hi Mohan, We are planning to release the test-automation-framework 4.3.2 by end of tomorrow(Friday). Thanks, Nuwanw On Thu, May 14, 2015 at 12:04 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: By the Nuwan, when you guys planning to release the 4.3.2 automation framework ? Thanks, Mohan On Wed, May 13, 2015 at 5:44 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Thanks Nuwan, I'll check that... Regards, Mohan On Wed, May 13, 2015 at 4:54 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Mohan, We have enabled the MQTT transport in Embedded ActiveMQ server started by Test Framework. Now you can use mqtt transport in integration test. This feature is available in test-automation-framework 4.3.2-SNAPSHOT. Transport is enabled on mqtt://localhost:1883 Use below code to start the server with MQTT transport and TCP transport JMSBrokerController activeMqBroker = new JMSBrokerController(localhost, JMSBrokerConfigurationProvider.getInstance().getTransportConnectors()); activeMqBroker.start() Thanks, Nuwanw On Mon, May 11, 2015 at 5:51 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: On Mon, May 11, 2015 at 3:38 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Mohan, Embedded broker only enable the tcp connector currently. We have to add the mqtt connector when the server is started. I am working on enabling the mqtt for embedded activeMQ server started by test framework. I will update the thread once implementation is done. Great.. Thanks Nuwan for looking into this.. Thanks, Nuwanw On Thu, May 7, 2015 at 10:15 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Thanks Krishantha... @Waruna, please let us know if you found any option.. Thanks, Mohan On Thu, May 7, 2015 at 11:57 AM, Waruna Perera waru...@wso2.com wrote: HI Krishantha, Will check on that. Thanks, On Thu, May 7, 2015 at 11:54 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Waruna, I don't think we have enabled ActiveMQ broker for MQTT. Can you check whether MQTT endpoint is exposed. And any workaround to get it started. The version we used is 5.9.1 and it should support for MQTT. Thanks, Krishantha. On Tue, May 5, 2015 at 6:29 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Hi All, We are planning to ship MQTT event adapter support with CEP 4.0.0. We are done with the implementation but facing some issues in writing integration tests.. To test this functionality, we have used the ActiveMQ as the MQTT server. ActiveMQ version 5.9.0 and upwards contains a mqtt endpoint. Based on [1], Automation framework has activemq 5.9.1 support. But when I am trying-out, I haven't seen a mqtt endpoint. It only has below endpoint, INFO [org.apache.activemq.transport.TransportServerThreadSupport] - Listening for connections at: tcp://localhost:61616 INFO [org.apache.activemq.broker.TransportConnector] - Connector tcp://127.0.0.1:61616 started INFO [org.apache.activemq.broker.BrokerService] - Apache ActiveMQ 5.9.1 (testBroker, ID:mohan-ThinkPad-T530-35747-1430828992894-0:1) started INFO [org.apache.activemq.broker.BrokerService] - For help or more information please see: http://activemq.apache.org By default, ActiveMQ has mqtt endpoint in port 1883.. Can someone from Automation team help on this.. This is a blocker to consider the feature as done-done .. [1] https://wso2.org/jira/browse/TA-901 Thanks, Mohan -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *V. Mohanadarshan* *Senior Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *V. Mohanadarshan* *Senior Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http
Re: [Dev] Test Automation Framework Support for MQTT Server
Hi Mohan, We have enabled the MQTT transport in Embedded ActiveMQ server started by Test Framework. Now you can use mqtt transport in integration test. This feature is available in test-automation-framework 4.3.2-SNAPSHOT. Transport is enabled on mqtt://localhost:1883 Use below code to start the server with MQTT transport and TCP transport JMSBrokerController activeMqBroker = new JMSBrokerController(localhost, JMSBrokerConfigurationProvider.getInstance().getTransportConnectors()); activeMqBroker.start() Thanks, Nuwanw On Mon, May 11, 2015 at 5:51 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: On Mon, May 11, 2015 at 3:38 PM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Mohan, Embedded broker only enable the tcp connector currently. We have to add the mqtt connector when the server is started. I am working on enabling the mqtt for embedded activeMQ server started by test framework. I will update the thread once implementation is done. Great.. Thanks Nuwan for looking into this.. Thanks, Nuwanw On Thu, May 7, 2015 at 10:15 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Thanks Krishantha... @Waruna, please let us know if you found any option.. Thanks, Mohan On Thu, May 7, 2015 at 11:57 AM, Waruna Perera waru...@wso2.com wrote: HI Krishantha, Will check on that. Thanks, On Thu, May 7, 2015 at 11:54 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Waruna, I don't think we have enabled ActiveMQ broker for MQTT. Can you check whether MQTT endpoint is exposed. And any workaround to get it started. The version we used is 5.9.1 and it should support for MQTT. Thanks, Krishantha. On Tue, May 5, 2015 at 6:29 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Hi All, We are planning to ship MQTT event adapter support with CEP 4.0.0. We are done with the implementation but facing some issues in writing integration tests.. To test this functionality, we have used the ActiveMQ as the MQTT server. ActiveMQ version 5.9.0 and upwards contains a mqtt endpoint. Based on [1], Automation framework has activemq 5.9.1 support. But when I am trying-out, I haven't seen a mqtt endpoint. It only has below endpoint, INFO [org.apache.activemq.transport.TransportServerThreadSupport] - Listening for connections at: tcp://localhost:61616 INFO [org.apache.activemq.broker.TransportConnector] - Connector tcp://127.0.0.1:61616 started INFO [org.apache.activemq.broker.BrokerService] - Apache ActiveMQ 5.9.1 (testBroker, ID:mohan-ThinkPad-T530-35747-1430828992894-0:1) started INFO [org.apache.activemq.broker.BrokerService] - For help or more information please see: http://activemq.apache.org By default, ActiveMQ has mqtt endpoint in port 1883.. Can someone from Automation team help on this.. This is a blocker to consider the feature as done-done .. [1] https://wso2.org/jira/browse/TA-901 Thanks, Mohan -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 -- *V. Mohanadarshan* *Senior Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Test Automation Framework Support for MQTT Server
Hi Mohan, Embedded broker only enable the tcp connector currently. We have to add the mqtt connector when the server is started. I am working on enabling the mqtt for embedded activeMQ server started by test framework. I will update the thread once implementation is done. Thanks, Nuwanw On Thu, May 7, 2015 at 10:15 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Thanks Krishantha... @Waruna, please let us know if you found any option.. Thanks, Mohan On Thu, May 7, 2015 at 11:57 AM, Waruna Perera waru...@wso2.com wrote: HI Krishantha, Will check on that. Thanks, On Thu, May 7, 2015 at 11:54 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Waruna, I don't think we have enabled ActiveMQ broker for MQTT. Can you check whether MQTT endpoint is exposed. And any workaround to get it started. The version we used is 5.9.1 and it should support for MQTT. Thanks, Krishantha. On Tue, May 5, 2015 at 6:29 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Hi All, We are planning to ship MQTT event adapter support with CEP 4.0.0. We are done with the implementation but facing some issues in writing integration tests.. To test this functionality, we have used the ActiveMQ as the MQTT server. ActiveMQ version 5.9.0 and upwards contains a mqtt endpoint. Based on [1], Automation framework has activemq 5.9.1 support. But when I am trying-out, I haven't seen a mqtt endpoint. It only has below endpoint, INFO [org.apache.activemq.transport.TransportServerThreadSupport] - Listening for connections at: tcp://localhost:61616 INFO [org.apache.activemq.broker.TransportConnector] - Connector tcp:// 127.0.0.1:61616 started INFO [org.apache.activemq.broker.BrokerService] - Apache ActiveMQ 5.9.1 (testBroker, ID:mohan-ThinkPad-T530-35747-1430828992894-0:1) started INFO [org.apache.activemq.broker.BrokerService] - For help or more information please see: http://activemq.apache.org By default, ActiveMQ has mqtt endpoint in port 1883.. Can someone from Automation team help on this.. This is a blocker to consider the feature as done-done .. [1] https://wso2.org/jira/browse/TA-901 Thanks, Mohan -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] JMS scenario automation
Hi Prabath, You can refer the test case[1] for how to implement above test scenario. However you have to implement below steps to cover the full scenario. 1) Add a method to stop and start the message broker without configuring ESB JMS transport. 2) Implement a axis2 service to count the requests. [1] https://github.com/wso2/product-esb/blob/master/modules/integration/tests-integration/tests-transport/src/test/java/org/wso2/carbon/esb/jms/inbound/transport/test/JMSInboundTransactionTestCase.java [2] https://github.com/wso2/product-esb/blob/master/modules/integration/test-common/integration-test-utils/src/main/java/org/wso2/esb/integration/common/utils/servers/ActiveMQServer.java Thanks, Nuwanw On Thu, May 7, 2015 at 10:10 AM, Amalka Subasinghe ama...@wso2.com wrote: Hi Prabath, You can get the back end call count using tcpmon client https://github.com/wso2/carbon-platform-integration/tree/master/test-automation-framework/org.wso2.carbon.automation.test.utils/src/main/java/org/wso2/carbon/automation/test/utils/tcpmon/client There are some ESB samples you can find out how to use the tcpmon client in tests Amalka On Thu, May 7, 2015 at 9:55 AM, Hemika Kodikara hem...@wso2.com wrote: Hi Prabath, You can restart a server as follows. ServerConfigurationManager serverManager = new ServerConfigurationManager(automationContext); serverManager.restartGracefully(); Have to send the appropriate automation context based on the WSO2 product mentioned in the automation.xml. Regards, Hemika Hemika Kodikara Software Engineer WSO2 Inc. lean . enterprise . middleware http://wso2.com Mobile : +9477762 On Thu, May 7, 2015 at 9:51 AM, Dharshana Warusavitharana dharsha...@wso2.com wrote: Hi Prabath, You can follow Nuwan's blog post on this. Please find blog on [1]. [1]. http://nuwanwimalasekara.blogspot.com/2013/05/how-to-write-wso2-esb-and-jms.html Thank you, Dharshana. On Thu, May 7, 2015 at 9:47 AM, Amalka Subasinghe ama...@wso2.com wrote: Hi, There are some JMS related integration tests in ESB project. Did u follow those? https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration/tests-sample/src/test/java/org/wso2/carbon/esb/samples/test/messaging Thanks Amalka On Thu, May 7, 2015 at 9:13 AM, Prabath Ariyarathna prabat...@wso2.com wrote: Looping to support dev On Thu, May 7, 2015 at 9:11 AM, Prabath Ariyarathna prabat...@wso2.com wrote: Looping to support dev On Tue, May 5, 2015 at 3:07 PM, Prabath Ariyarathna prabat...@wso2.com wrote: Hi Automation team I'm going to automate following scenario for the reported issue[1]. Could you please verify whether this is possible with existing integration test suite capabilities. 1. Start ESB MB(ActiveMQ/Wso2 MB) 2. Send Message 3. Restart MB 4. Start Backend service 5. Get a received messages count by the backend service. [1] = *https://wso2.org/jira/browse/ESBJAVA-3670 https://wso2.org/jira/browse/ESBJAVA-3670* Thanks. -- *Prabath Ariyarathna* *Associate Technical Lead* *WSO2, Inc. * *lean . enterprise . middleware * *Email: prabat...@wso2.com prabat...@wso2.com* *Blog: http://prabu-lk.blogspot.com http://prabu-lk.blogspot.com/* *Flicker : https://www.flickr.com/photos/47759189@N08 https://www.flickr.com/photos/47759189@N08* *Mobile: +94 77 699 4730 * -- *Prabath Ariyarathna* *Associate Technical Lead* *WSO2, Inc. * *lean . enterprise . middleware * *Email: prabat...@wso2.com prabat...@wso2.com* *Blog: http://prabu-lk.blogspot.com http://prabu-lk.blogspot.com* *Flicker : https://www.flickr.com/photos/47759189@N08 https://www.flickr.com/photos/47759189@N08* *Mobile: +94 77 699 4730 * -- *Prabath Ariyarathna* *Associate Technical Lead* *WSO2, Inc. * *lean . enterprise . middleware * *Email: prabat...@wso2.com prabat...@wso2.com* *Blog: http://prabu-lk.blogspot.com http://prabu-lk.blogspot.com* *Flicker : https://www.flickr.com/photos/47759189@N08 https://www.flickr.com/photos/47759189@N08* *Mobile: +94 77 699 4730 * -- Amalka Subasinghe Senior Software Engineer WSO2 Inc. Mobile: +94 77 9401267 -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94770342233 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Amalka Subasinghe Senior Software Engineer WSO2 Inc. Mobile: +94 77 9401267 -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Defining operations in service.xml in axis2 service make in-only operation in-out
Hi If the operations are defined in service.xml in an axis2 service, It make in-only operation in-out. WSDL add the wsdl:output for the operation. once the in-only service is invoked, It send auto generated response back to client. public void operation1(); operation name=operation1/operation However defining the messageReceiver in operation level avoid sending the auto generated response back to client. But WSDL does not changed. It defines the wsdl:output for the operation. messageReceiver mep=http://www.w3.org/2004/08/wsdl/in-only; class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/ [1] https://wso2.org/jira/browse/CARBON-15243 Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Could not run the test-ui testcases - Enterprise Store
Satkunam* *Associate Software Engineer | WSO2* *E:rajeenth...@wso2.com rajeenth...@wso2.com* *M :+94770832823 %2B94770832823 * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Testing Jacoco based code coverage genration
Hi Krishantha,
I tried generating coverage in ESB. It is working fine and Coverage reports
generated. However the coverage report aggregation seems not working when
there are multiple tests modules. We need to fix the issue.
test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT
Thanks,
Nuwanw
On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Correction : Step #1 configuration should be as follows.
execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution
Thanks,
Krishantha.
On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi all,
New coverage implementation using Jacoco has been committed to master
branch of carbon-platform-integration. I tried my best to adhere to
existing Emma based design and reuse same instrumentation and filters text
files. Note that this new coverage implementation was done to support for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly before
the release.
I've done initial testing with AS and everything seems to work.
Automation team will start verifying coverage with products already
migrated JDK 1.7. Specially products with multiple test modules (ESB, G-Reg
BPS)
Lets focus on testing following scenarios before the release.
Test Scenarios for coverage :
1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage numbers.
To get started with Jacoco coverage :
1. Edit your test module pom and replace emma copy dependency execution
configuration with below.
execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution
2. Include jacoco argent as a dependency to root pom.
dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency
jacoco.agent.version0.7.4.201502262128/jacoco.agent.version
3. Remove following system properties from surefire plugin.
emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output
You will find following log entries in console with required details to
view the report once coverage generation completed. Available report
formats are XML, HTML and CSV
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage dump file path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco.exec
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco class file path :
/Users/xxx/product-as/modules/integration/tests-integration/tests/target/wso2as-6.0.0-NAPSHOT/repository/components/plugins
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage report path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco/coverage
Thanks,
Krishantha.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Testing Jacoco based code coverage genration
Hi
We should
remove
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
from extensions. Then all the tests module should refer the correct class.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera krishan...@wso2.com
wrote:
Hi Waruna,
On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com wrote:
Hi Krishantha,
And we need to update Automation.xml to use following class instead of
one from utils.
Please remove the CarbonServerExtension class at utils. Its was deprecated
in last release and moved to test extensions to support for carbon kernel
startup.
Need to completely get rid of this extension class and its dependencies.
Thanks,
Krishantha.
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
Thanks
On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi Krishantha,
I tried generating coverage in ESB. It is working fine and Coverage
reports generated. However the coverage report aggregation seems not
working when there are multiple tests modules. We need to fix the issue.
test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT
Thanks,
Nuwanw
On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Correction : Step #1 configuration should be as follows.
execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution
Thanks,
Krishantha.
On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi all,
New coverage implementation using Jacoco has been committed to master
branch of carbon-platform-integration. I tried my best to adhere to
existing Emma based design and reuse same instrumentation and filters text
files. Note that this new coverage implementation was done to support for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly before
the release.
I've done initial testing with AS and everything seems to work.
Automation team will start verifying coverage with products already
migrated JDK 1.7. Specially products with multiple test modules (ESB,
G-Reg
BPS)
Lets focus on testing following scenarios before the release.
Test Scenarios for coverage :
1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage numbers.
To get started with Jacoco coverage :
1. Edit your test module pom and replace emma copy dependency
execution configuration with below.
execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution
2. Include jacoco argent as a dependency to root pom.
dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency
jacoco.agent.version0.7.4.201502262128/jacoco.agent.version
3. Remove following system properties from surefire plugin.
emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output
You will find following log entries in console with required details
to view the report once coverage generation completed. Available report
formats are XML, HTML and CSV
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage dump file path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco.exec
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco class file path :
/Users/xxx/product-as/modules/integration/tests-integration/tests/target/wso2as-6.0.0-NAPSHOT/repository/components/plugins
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage report path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco/coverage
Thanks,
Krishantha.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2
Re: [Dev] Getting Error
Hi When did you get this error? And please send the full error log Thanks, Nuwanw On Wed, May 6, 2015 at 9:30 AM, Sriashalya Srivathsan asha...@wso2.com wrote: Hi Devs When I run the integration tests for tsheets connector I'm getting following error. setEnvironment(org.wso2.carbon.connector.integration.test.tsheets.TSheetsConnectorIntegrationTest): java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl) cleanUpEsb(org.wso2.carbon.connector.integration.test.tsheets.TSheetsConnectorIntegrationTest) Can any one resolve this? -- S.Sriashalya, Associate Software Engineer, WSO2 *Inc*. lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Testing Jacoco based code coverage genration
Hi Krishantha,
I am getting below error when merging the coverage reports. generateReports
implementation is missing in CodeCoverageUtils. report module use
the org.wso2.carbon.integration.common.utils.coverage.TestCoverageGenerator
to aggregate results.
Exception in thread main java.lang.NoSuchMethodError:
org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.generateReports(Ljava/util/List;)V
at
org.wso2.carbon.integration.common.utils.coverage.TestCoverageGenerator.main(TestCoverageGenerator.java:36)
Thanks,
Nuwanw
On Tue, May 5, 2015 at 9:47 PM, Nuwan Wimalasekara nuw...@wso2.com wrote:
Yes. The correct implementation
is
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
We will remove the CarbonServerExtension from utils to get rid of
conflicts.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 9:27 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Nuwan,
You should remove
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension
not the
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 9:47 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi
We should
remove
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
from extensions. Then all the tests module should refer the correct class.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Waruna,
On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com wrote:
Hi Krishantha,
And we need to update Automation.xml to use following class instead of
one from utils.
Please remove the CarbonServerExtension class at utils. Its was
deprecated in last release and moved to test extensions to support for
carbon kernel startup.
Need to completely get rid of this extension class and its
dependencies.
Thanks,
Krishantha.
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
Thanks
On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi Krishantha,
I tried generating coverage in ESB. It is working fine and Coverage
reports generated. However the coverage report aggregation seems not
working when there are multiple tests modules. We need to fix the issue.
test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT
Thanks,
Nuwanw
On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Correction : Step #1 configuration should be as follows.
execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution
Thanks,
Krishantha.
On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi all,
New coverage implementation using Jacoco has been committed to
master branch of carbon-platform-integration. I tried my best to
adhere to
existing Emma based design and reuse same instrumentation and filters
text
files. Note that this new coverage implementation was done to support
for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly
before
the release.
I've done initial testing with AS and everything seems to work.
Automation team will start verifying coverage with products already
migrated JDK 1.7. Specially products with multiple test modules (ESB,
G-Reg
BPS)
Lets focus on testing following scenarios before the release.
Test Scenarios for coverage :
1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage
numbers.
To get started with Jacoco coverage :
1. Edit your test module pom and replace emma copy dependency
execution configuration with below.
execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution
2. Include jacoco argent as a dependency to root pom.
dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency
jacoco.agent.version0.7.4.201502262128/jacoco.agent.version
3. Remove following system properties from surefire plugin.
emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output
You will find following log entries in console with required
details
Re: [Dev] Testing Jacoco based code coverage genration
Yes. The correct implementation
is
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
We will remove the CarbonServerExtension from utils to get rid of
conflicts.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 9:27 PM, Krishantha Samaraweera krishan...@wso2.com
wrote:
Hi Nuwan,
You should remove
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension
not the
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 9:47 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi
We should
remove
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
from extensions. Then all the tests module should refer the correct class.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Waruna,
On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com wrote:
Hi Krishantha,
And we need to update Automation.xml to use following class instead of
one from utils.
Please remove the CarbonServerExtension class at utils. Its was
deprecated in last release and moved to test extensions to support for
carbon kernel startup.
Need to completely get rid of this extension class and its dependencies.
Thanks,
Krishantha.
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
Thanks
On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi Krishantha,
I tried generating coverage in ESB. It is working fine and Coverage
reports generated. However the coverage report aggregation seems not
working when there are multiple tests modules. We need to fix the issue.
test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT
Thanks,
Nuwanw
On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Correction : Step #1 configuration should be as follows.
execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution
Thanks,
Krishantha.
On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi all,
New coverage implementation using Jacoco has been committed to
master branch of carbon-platform-integration. I tried my best to adhere
to
existing Emma based design and reuse same instrumentation and filters
text
files. Note that this new coverage implementation was done to support
for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly
before
the release.
I've done initial testing with AS and everything seems to work.
Automation team will start verifying coverage with products already
migrated JDK 1.7. Specially products with multiple test modules (ESB,
G-Reg
BPS)
Lets focus on testing following scenarios before the release.
Test Scenarios for coverage :
1. Coverage generation with patches applied.
2. Merge coverage reports in multiple test modules.
3. WebApp class coverage.
4. Coverage generation after restart and impact to coverage numbers.
To get started with Jacoco coverage :
1. Edit your test module pom and replace emma copy dependency
execution configuration with below.
execution
idcopy-emma-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/emma/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsemma
/includeArtifactIds
/configuration
/execution
2. Include jacoco argent as a dependency to root pom.
dependency
groupIdorg.jacoco/groupId
artifactIdorg.jacoco.agent/artifactId
version${jacoco.agent.version}/version
/dependency
jacoco.agent.version0.7.4.201502262128/jacoco.agent.version
3. Remove following system properties from surefire plugin.
emma.home${basedir}/target/emma/emma.home
emma.output${basedir}/target/emma/emma.output
You will find following log entries in console with required details
to view the report once coverage generation completed. Available report
formats are XML, HTML and CSV
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco coverage dump file path :
/Users/krishantha/git/wso2/product-as/modules/integration/tests-integration/tests/target/jacoco.exec
INFO
[org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerManager]
- Jacoco class file path :
/Users/xxx/product-as/modules/integration/tests-integration/tests/target/wso2as-6.0.0-NAPSHOT/repository/components/plugins
INFO
[org.wso2
Re: [Dev] Getting Error
Hi Sriashalya,
As the error log, wso2esb-4.9.0-M7-SNAPSHOT.zip can not be found. Please
make sure to verify whether the ESB distribution is exist before running
the tests. Copy the wso2esb-4.9.0-M7-SNAPSHOT.zip
to
tsheets-connector/tsheets-connector-1.0.0/org.wso2.carbon.connector/repository/
directory and run the test again.
Running TestSuite
[2015-05-06 10:41:24,968] INFO
{org.wso2.carbon.automation.core.PlatformExecutionManager} -
---Test Execution Started --
[2015-05-06 10:41:24,976] INFO
{org.wso2.carbon.automation.core.ServerGroupManager} - Carbon zip file -
/Users/sriashalyasrivathsan/Desktop/gmailThroughREST/esb-connectors/tsheets/tsheets-connector/tsheets-connector-1.0.0/org.wso2.carbon.connector/repository/wso2esb-4.9.0-M7-SNAPSHOT.zip
[2015-05-06 10:41:24,984] ERROR
{org.wso2.carbon.automation.core.utils.fileutils.ArchiveExtractor} - Error
on archive extraction
java.io.FileNotFoundException:
/Users/sriashalyasrivathsan/Desktop/gmailThroughREST/esb-connectors/tsheets/tsheets-connector/tsheets-connector-1.0.0/org.wso2.carbon.connector/repository/wso2esb-4.9.0-M7-SNAPSHOT.zip
(No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.init(FileInputStream.java:120)
at java.io.FileInputStream.init(FileInputStream.java:79)
at
org.wso2.carbon.automation.core.utils.fileutils.ArchiveExtractor.extractFile(ArchiveExtractor.java:43)
at
org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.setUpCarbonHome(ServerUtils.java:177)
Thanks,
Nuwanw
On Wed, May 6, 2015 at 10:49 AM, Sriashalya Srivathsan asha...@wso2.com
wrote:
Hi Nuwan,
I'm getting this error when I run the tsheet connector through ESB. Find
the log below.
On Wed, May 6, 2015 at 10:33 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi
When did you get this error?
And please send the full error log
Thanks,
Nuwanw
On Wed, May 6, 2015 at 9:30 AM, Sriashalya Srivathsan asha...@wso2.com
wrote:
Hi Devs
When I run the integration tests for tsheets connector I'm getting
following error.
setEnvironment(org.wso2.carbon.connector.integration.test.tsheets.TSheetsConnectorIntegrationTest):
java.security.NoSuchAlgorithmException: Error constructing implementation
(algorithm: Default, provider: SunJSSE, class:
com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl)
cleanUpEsb(org.wso2.carbon.connector.integration.test.tsheets.TSheetsConnectorIntegrationTest)
Can any one resolve this?
--
S.Sriashalya,
Associate Software Engineer,
WSO2 *Inc*.
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
--
S.Sriashalya,
Associate Software Engineer,
WSO2 *Inc*.
lean . enterprise . middleware
--
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to assign java agent to carbon servers
Hi Krishantha, Did you find a solution to set the agent without editing the wso2server.sh Thanks, Nuwanw On Wed, Apr 29, 2015 at 1:04 PM, Krishantha Samaraweera krishan...@wso2.com wrote: On Thu, Apr 30, 2015 at 1:31 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi all, I'm trying to assign Jacoco (code coverage) java agent to our products and found it's not OOB supported though command line. So I had to edit the wso2server.sh and set it as JAVA_OPTS argument. sh wso2server.sh -javaagent:/Users/krishantha/xxx/agent/jacocoagent.jar=destfile=/Users/krishantha/xxx/target/jacoco.exec,append=true -* Not working* export JAVA_OPTS=-javaagent:/Users/krishantha/xxx/agent/jacocoagent.jar=destfile=/Users/krishantha/xxx/target/jacoco.exec,append=true sh wso2sever.sh - *Works* Is there any other way to achieve this without editing the shell script or exporting JAVA_OPTS. Since this a VM argument doesn't it need to be supported though command line ? Thanks, Krishantha. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
