Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

2018-06-16 Thread Nirothipan Mehalingam
Hi all,

I have tested the following,

   - Adding a new user and log in using newly created user.
   - Deploying a simple custom class mediator as an OSGi bundle and
   validating the flow.
   - Enabling debug logs via the management console.
   - Adding scheduled task via management console and via carbon apps.
   - Deploying carbon apps in micro-integrator profile and validating the
   deployments and the artifacts.
   - Adding inline throttle policy and validating the flow.


[+] Stable - go ahead and release

Thanks.
Nirothipan


On Sat, Jun 16, 2018 at 12:57 PM, Isuru Udana  wrote:

> Hi All,
>
> Did basic tests of all artifact types in both Integrator and Micro
> Integrator profiles using artifacts created from EI Tooling.
>
> [+] Stable - go ahead and release
>
> Thanks.
>
>
> On Sat, Jun 16, 2018 at 12:07 PM Thishani Lucas  wrote:
>
>> Hi All,
>>
>> Tested the following in both ESB profile and Micro Integrator profile.
>>
>>- Store and forward with scheduled forwarding processor and JMS
>>message store in the Broker profile.
>>- Sampling message processor.
>>- JMS inbound endpoint.
>>- File inbound endpoint (vfs).
>>- Mail-To transport using a listener proxy.
>>- Constructing and sending multipart form data.
>>- Publishing stats to the Analytics profile.
>>- Basic functionalities of some mediators and endpoints.
>>
>> [+] Stable - Go ahead and release.
>>
>> Thanks,
>> Thishani
>>
>> On Sat, Jun 16, 2018 at 11:46 AM Lahiru Madushanka 
>> wrote:
>>
>>> Hi all,
>>>
>>> Tested the following
>>>
>>> Ubuntu Windows
>>> Test EI micro-integrator EI + MI
>>> JMS inbound endpoint ✓ ✓ ✓
>>> JMS listener proxy ✓ ✓ ✓
>>> JMS publisher proxy ✓ ✓ ✓
>>> JMS message Store ✓ ✓ ✓
>>> JMS transaction and rollback ✓ ✓
>>> Message sampling processor ✓ ✓ ✓
>>> Class mediator ✓ ✓ ✓
>>> Data Mapper mediator (using CAPP) ✓ ✓
>>>
>>> Smoke test management console of all profiles in windows
>>> ✓
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>> Lahiru
>>>
>>> On Sat, Jun 16, 2018 at 1:11 AM Malaka Gangananda 
>>> wrote:
>>>
 Hi All,

 We are pleased to announce the second release candidate of WSO2
 Enterprise Integrator 6.3.0.

 Known issues: https://github.com/wso2/product-ei/issues

 Source and binary distribution files: https://github.com/wso2/produc
 t-ei/releases/tag/v6.3.0-rc2

 The tag to be voted upon: https://github.com/wso2/produc
 t-ei/tree/v6.3.0-rc2

 Please vote as follows:
 [+] Stable - go ahead and release
 [-] Broken - do not release (explain why)

 ~The WSO2 Integration Team~

 Thanks,


 --
 Malaka.
 --
 Malaka Gangananda - Software Engineer | WSO2
 Email : mala...@wso2.com
 Mobile : +94713564340
 Web : http://wso2.com
   
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev

>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> *Thishani Lucas*
>> *Software Engineer*
>> *WSO2 Lanka (Private) Limited**: http://wso2.com *
>> *lean.enterprise.middle-ware*
>>
>> *Tel: +94 77 2556931 *
>>
>> *LinkedIn: https://www.linkedin.com/in/thishani-lucas/
>> *
>>
>>
>> 
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> *Isuru Udana*
> Senior Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

M.Nirothipan
Software Engineer
WSO2 Inc. http://wso2.com ,
*Mobile : +94 77 2172692*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Duplicate Context Value

2018-06-08 Thread Nirothipan Mehalingam
Hi Shib,

If you are using embedded H2 DB you may follow
https://docs.wso2.com/display/ADMIN44x/Browsing+the+H2+Database.

Thanks
Nirothipan

On Fri, Jun 8, 2018 at 2:09 PM, shibsankar  wrote:

> How do I connect to this DB and view the rows of the mentioned table?
>  Can it be viewed from API management web-UI?
>
> Regards
> Shib
>
> On Fri, Jun 8, 2018 at 1:50 PM, Dinusha Dissanayake 
> wrote:
>
>> Hi Shib,
>>
>> Probably there should be an database entry of the same "context" you are
>> defining here. As above replies explain, this could be due to partially
>> deleted APIs.
>> Could you please check AM_API table in AM_DB and see whether there is a
>> CONTEXT_TEMPLATE with the same context you are trying to define here?
>>
>> Thanks,
>> DinushaD.
>>
>>
>> On Fri, Jun 8, 2018 at 12:50 PM, shibsankar  wrote:
>>
>>> There is no API  in publisher application.
>>>
>>> I'm still getting * Duplicate Context Value *when trying to add a new
>>> API  in Design page.
>>>
>>> Please see the screenshot attached.
>>>
>>> Regards
>>> Shib
>>>
>>>
>>> On Fri, Jun 8, 2018 at 10:51 AM, Dushani Wellappili 
>>> wrote:
>>>
 Hi Shib,

 If you have deleted the API from the management console, then it is
 likely you are getting this issue since deleting api in the management
 console does not delete the whole api. It removes the data in the registry
 (meta data). To delete api use publisher application.

 Thank you.

 Regards,

 *Dushani Wellappili*
 Software Engineer - WSO2

 Email : dusha...@wso2.com
 Mobile : +94779367571
 Web : https://wso2.com/




 On Fri, Jun 8, 2018 at 10:01 AM Krishan Wijesena 
 wrote:

>
>
> On Thu, Jun 7, 2018 at 6:50 PM, shibsankar  wrote:
>
>> Hi,
>> I have *deleted *published API, subscribed API  from WSO2. Now there
>> is no more API  in WSO2.
>> You cannot delete API if active subscriptions exists, which apporach
>> did you used to delete the API?
>>
> because basically this error occur if previous API have same
> context value and it's partally deleted.
>
>>
>> Restarted the WSO2 server.
>>
>>
>> Now when I  try to add a New API ,  I'm still getting *Duplicate
>> context value *in API  design page.
>>
>> Why is this happening? How to fix this?
>>
>> Please see the screenshot attached.
>>
>> WSo2 version is 2.1
>>
>> Regards
>> Shib
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Krishan Wijesena*
> Software Engineer | WSO2
>
> Email : krish...@wso2.com
> Mobile : +94776219923
> WSO2 Inc : http://wso2.com
> [image: http://wso2.com/signature] 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>

>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dinusha Dissanayake
>> Software Engineer
>> WSO2 Inc
>> Mobile: +94712939439
>> 
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

M.Nirothipan
Software Engineer
WSO2 Inc. http://wso2.com ,
*Mobile : +94 77 2172692*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] SMB on WSO2 EI 6.2.0 VFS

2018-05-05 Thread Nirothipan Mehalingam
Hi Norberto,

Th issue [1] you identified is the related one.We will release a WUM update
for EI 6.2.0 with this fix. Then you can update EI 6.2.0 and get this issue
sorted.
But please note that Updates published through WSO2 Update are NOT open
source – they are released under the WSO2 Update EULA 2.0
. Updates can be used in
PRODUCTION only under a paid WSO2 Subscription [2].


[1] - https://github.com/wso2/product-ei/issues/2150
[2] - https://wso2.com/updates/wum

Thanks
Nirothipan

On Sat, May 5, 2018 at 2:28 PM, Fernandes, Norberto <
nfern...@jaguarlandrover.com> wrote:

> Hi Devs,
>
> https://github.com/wso2/product-ei/issues/2150
>
> Found this issue that I think is related to this. The issue is closed and
> there a new jar added to the orbit project.
> How can I get this jar into my installation?
>
> Thanks in advance.
> Norberto
>
> On 4 May 2018 at 17:49, Fernandes, Norberto 
> wrote:
>
>> Hi Devs,
>>
>> I am trying to use VFS to read and write files to a SMB location. I try
>> to configure a proxy to access SMB share but I always get an error
>> reporting unknown protocol smb.
>>
>> ...
>>
>> Caused by: java.net.MalformedURLException: unknown protocol: smb
>>
>> at java.net.URL.(URL.java:600)
>>
>> at java.net.URL.(URL.java:490)
>>
>> at java.net.URL.(URL.java:439)
>>
>> at org.apache.commons.vfs2.provider.url.UrlFileProvider.findFil
>> e(UrlFileProvider.java:60)
>> ..
>>
>> I had a look into the vfs-providers.xml file
>> at commons-vfs2_2.2.0.wso2v1.jar and it refers to
>> org.apache.commons.vfs2.provider.smb.SmbFileProvider class.
>>
>> I tried to find this class in all jars in the 6.2.0 distribution and
>> could not find it.
>>
>> Could you please indicate if this class should be present or if smb
>> should work without it?
>>
>> Norberto
>> JLR
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*M.Nirothipan*
*Software Engineer | WSO2*
*Mobile : +94 77 2172692*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.2.0 RC2

2018-03-17 Thread Nirothipan Mehalingam
Hi all,

I have tested the following with EI RC 2 pack

1 - Configuring analytics profile and publishing data for proxy services.
2 - Configuring broker profile and sending messages to a queue.
3 - Creating WSO2MB & JMS Inbound endpoints and fetching messages from the
queue.
4 - Deploying data service samples.

I have found no blockers so far.

+1 for release.

Thanks
Nirothipan

On Sat, Mar 17, 2018 at 9:10 PM, Riyafa Abdul Hameed 
wrote:

> Hi,
>
> *EI pack*
> I tested the cache mediator which is a rewrite in EI 6.2.0.
>
>- Tested if all the settings are working as expected in positive cases
>- Tested if they are behaving appropriately if the configurations are
>not set properly.
>- Tested some known issues in cache mediator on json payload
>
> [+] Stable - to release the EI pack
>
> *Devstudio-cache mediator tooling*
> I tested the dev-studio tooling for the same. I was trying to set the
> cache collector to true and false and didn't find any UI config to do so:
>
>
>
> I think it is very important to have this. I can set it in the source and
> when I set collector= true in the source I get the following:
>
>
>
> There's no way to change it to false in the tooling.
> [-1] for releasing the tooling with cache mediator because it is important
> to be able to specify collector=true or false.
>
> Correct me if I am mistaken in any of the above tests.
>
> Further some implementation of configs are missing[1], but it will be
> released as updates which is fine.
>
> *Devstudio installation instruction*
> Further we need to mention in docs that we need to enable the following[2]
> when installing devstudio in a gnome system:
>
> #Export Following
>
> export SWT_GTK3=0
>
>
> This is because Ubuntu 18.04 LTS would be in gnome.
>
> *WSO2 EI Documentation*
> I think that we need to update the EI 6.2.0 documentation[3] with the
> available new configs: *enableCacheControl* and *includeAgeHeader* before
> the release.
>
>
> [1] https://github.com/wso2/devstudio-tooling-ei/issues/158
> [2] http://yasassriratnayake.blogspot.com/2016/12/how-to-
> get-rid-of-gtk3-errors-when.html
> [3] https://docs.wso2.com/display/EI620/Cache+Mediator
>
> Thanks,
> Riyafa
>
>
> On Sat, Mar 17, 2018 at 1:28 PM, Thishani Lucas  wrote:
>
>> Hi All,
>>
>> I've tested the following.
>>
>> [1] Message routing through MSMP using in-memory store and scheduled
>> forwarding processor.
>> [2] Using store mediator passing store name dynamically.
>> [3] Using a reply-sequence in the message processor to handle response
>> sent by the backend.
>> [4] Creation of proxy services.
>> [5] Try-It tool for proxy services.
>>
>> [+] Stable - Go ahead and release
>>
>> Thanks,
>> Thishani
>>
>> On Sat, Mar 17, 2018 at 12:37 PM, Mathuriga Thavarajah <
>> mathur...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> I have tested Quick Start Guide up to Business Process Profile.
>>>
>>> [+1] Stable - go ahead and release.
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Mathuriga.
>>>
>>>
>>>
>>> On Sat, Mar 17, 2018 at 11:12 AM, Nandika Jayawardana 
>>> wrote:
>>>
 Hi All

 I tested the following.

 [1] Carbon application creation for dev studio, and sample project with
 artefact deployment in Integrator profile
 [2] Business Process profile BPMN / BPMN / UI
 [3] Basic functionalities for all profiles.
 [4] readme files and release notes.

 [+] Stable - go ahead and release.

 Regards
 Nandika


 On Sat, Mar 17, 2018 at 10:47 AM, Malaka Gangananda 
 wrote:

> Hi All,
>
> I have tested following,
>
> VFS transport with following scenarios:
>
>- VFS transfer with file types  ascii and binary,
>- VFS absolute path test with sftp server
>- VFS SFTP server using passphrase protected keys
>
> Auto ACK/ Client ACK, Durable subscriptions , DTX related scenarios
> with broker profile
>
> Kafka Inbound Protocol with latest Kafka version
>
> [+] Stable - go ahead and release.
>
> Thanks,
>
> On Sat, Mar 17, 2018 at 6:20 AM, Himasha Guruge 
> wrote:
>
>> Hi All,
>>
>> We are pleased to announce the second release candidate of WSO2
>> Enterprise Integrator 6.2.0.
>>
>> *Known issues*: https://github.com/wso2/product-ei/issues
>>
>> *Source and binary distribution files*:
>> *https://github.com/wso2/product-ei/releases/tag/v6.2.0-rc2
>> *
>>
>> *The tag to be voted upon*: 
>> *https://github.com/wso2/product-ei/tree/v6.2.0-rc2
>> *
>>
>> Please vote as follows:
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> ~The WSO2 Integration 

Re: [Dev] Issue with EI 6.1.1 update 22 and 24.

2018-03-14 Thread Nirothipan Mehalingam
Hi Jorge,

On Thu, Mar 15, 2018 at 12:07 AM, Jorge  wrote:

> Thanks Madhawa.
>
> It will be available in the update 25?
>

We will  releasing an 6.2.0 RC with these changes soon.

Thanks
Nirothipan

>
> Regards,
>Jorge.
>
> 2018-03-14 14:35 GMT-04:00 Madhawa Gunasekara :
>
>> Hi Jorge,
>>
>> We have fixed this regression issue, It will be available in upcoming
>> release.
>>
>> Thanks,
>> Madhawa
>>
>> On Mar 14, 2018 11:16 PM, "Jorge"  wrote:
>>
>>> Hi all.
>>>
>>> If I have a data service with a resources like this one:
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> When I call it I get this error:
>>>
>>> TID: [-1234] [] [2018-03-12 00:01:13,570] ERROR {
>>> org.apache.axis2.json.gson.GsonXMLStreamReader} -  Value type miss
>>> match, Expected value type - 'null', but found - 'STRING' {
>>> org.apache.axis2.json.gson.GsonXMLStreamReader}
>>> TID: [-1234] [] [2018-03-12 00:01:13,584] ERROR
>>> {org.apache.synapse.transport.passthru.ServerWorker} -  Error
>>> processing POST request for : /services/DataAccountService/insertClient.
>>> Error detail: Value type miss match, Expected value type - 'null', but
>>> found - 'STRING'.  {org.apache.synapse.transport.passthru.ServerWorker}
>>> java.lang.IllegalArgumentException: Value type miss match, Expected
>>> value type - 'null', but found - 'STRING'
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.nextValue(Gso
>>> nXMLStreamReader.java:737)
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.readValue(Gso
>>> nXMLStreamReader.java:626)
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.stateTransiti
>>> on(GsonXMLStreamReader.java:532)
>>> at org.apache.axis2.json.gson.GsonXMLStreamReader.next(GsonXMLS
>>> treamReader.java:178)
>>> at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(St
>>> AXOMBuilder.java:681)
>>> at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBu
>>> ilder.java:214)
>>> at org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSer
>>> ializableImpl.java:78)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementI
>>> mpl.java:722)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElement
>>> Impl.java:700)
>>> at org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImp
>>> l.java:105)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMEleme
>>> ntImpl.java:296)
>>> at org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMEleme
>>> ntImpl.java:212)
>>> at org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBo
>>> dyImpl.java:231)
>>> at org.apache.axis2.json.gson.JSONMessageHandler.invoke(JSONMes
>>> sageHandler.java:84)
>>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
>>> at org.apache.synapse.transport.passthru.ServerWorker.processNo
>>> nEntityEnclosingRESTHandler(ServerWorker.java:331)
>>> at org.apache.synapse.transport.passthru.ServerWorker.processEn
>>> tityEnclosingRequest(ServerWorker.java:377)
>>> at org.apache.synapse.transport.passthru.ServerWorker.run(Serve
>>> rWorker.java:149)
>>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.r
>>> un(NativeWorkerPool.java:172)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>> Executor.java:1142)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>> lExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>> The same dataservice work fine with DSS 3.5.1 and with the first EI
>>> 6.1.1.
>>>
>>> Any idea?
>>>
>>> Regards,
>>> Jorge.
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>


-- 


*M.Nirothipan*
Software Engineer
*Mobile : +94 77 2172692*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev