Re: [Dev] Communication Error between Active and Passive nodes.

[Thilina Manamgoda]

Hi Vasanthan,

You have to configure the "host" to pod's IP as follow,

deployment.config:
  type: ha
  eventSyncServer:
host: ${NODE_IP}

here the "NODE_IP" is an environment variable and you can define it in the
Kubernetes deployment yaml as the pod's IP. Otherwise, the active node and
the passive node cannot identify each other's IP. Please find a similar
configuration here[1].

[1]
https://github.com/ThilinaManamgoda/kubernetes-is/blob/8d627f905de2f8ff94cd25ea330da6c668f4dd10/is-with-analytics/confs/is-analytics-1/conf/worker/deployment.yaml#L572

Thanks,
Thilina.

On Fri, Sep 21, 2018 at 7:38 PM Damith Wickramasinghe 
wrote:

> Hi vasanthan,
>
> It seems active node cannot create a tcp connection to passive node.
> Please make sure above advertisedHost value should be the host of own node.
> Not the host of other node.  If they are correct then try to telnet to
> passive node {passive node host} 9893 from active node.  I think you may
> need a host mapping too.
>
> Adding thilina since he did a same setup with new HA.
>
>
> Regards,
> Damith.
>
> On Fri, Sep 21, 2018 at 1:35 PM Vasanthan Sivalingam 
> wrote:
>
>>
>> Hi Sp team,
>>
>> With the latest 4.3.0 release an HA deployment was done with kubernetes.
>> the deployment configurations has been done as [1] and [2]. It was noticed
>> that the active node is not communicating with the passive node with the
>> following logs.
>>
>> ...
>> [2018-09-21 11:54:32,435]  INFO
>> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
>> Setting SinksHandlers of TestSiddhiApp to Active
>> [2018-09-21 11:54:32,436]  INFO
>> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
>> Setting RecordTableHandlers of TestSiddhiApp to Active
>> [2018-09-21 11:54:32,436]  INFO
>> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
>> Siddhi App TestSiddhiApp deployed successfully
>> [2018-09-21 11:54:32,446]  INFO
>> {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 Stream
>> Processor started in 6.922 sec
>> [*2018-09-21 11:54:33,377] ERROR
>> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
>> Error in getting a connection to the Passive node. null*
>> [2018-09-21 11:54:33,379] DEBUG
>> {org.wso2.carbon.stream.processor.core.ha.HACoordinationSourceHandler} -
>> Active Node: Saving state of Source Handler with Id TestSiddhiApp-1 with
>> timestamp 0
>> [2018-09-21 11:54:33,395] ERROR
>> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
>> Error in getting the TCP connection to the passive node. Hence not sending
>> the control message to the passive node
>> [2018-09-21 11:55:31,531]  INFO
>> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
>> siddhi Apps are persisted successfully.
>> ...
>>
>> The deployment config was done as below,
>>
>> deployment.config:
>>   type: ha
>>   eventSyncServer:
>> host: localhost
>> port: 9893
>> advertisedHost: sp-ha-node-1
>> advertisedPort: 9893
>> bossThreads: 10
>> workerThreads: 10
>>   eventSyncClientPool:
>> maxActive: 10
>> maxTotal: 10
>> maxIdle: 10
>> maxWait: 6
>> minEvictableIdleTimeMillis: 12
>>
>> Attached the log file.
>> Can you please suggest a method to make this communication work between
>> active node and the passive node.
>>
>> [1]
>> https://github.com/sameerawickramasekara/product-sp/blob/master/modules/integration/tests-kubernetes-integration/src/test/resources/artifacts/docker-files/deployment-ha-node-1.yaml
>> [2]
>> https://github.com/sameerawickramasekara/product-sp/blob/master/modules/integration/tests-kubernetes-integration/src/test/resources/artifacts/docker-files/deployment-ha-node-2.yaml
>>
>> Thanks,
>> Vasanth
>>
>
>
> --
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> 
> lean.enterprise.middleware
>
> mobile: *+94728671315*
>
>

-- 
Regards,
*Thilina Manamgoda*
*Software Engineer*


*WSO2*
*Mobile : +94 770-445855 <+94%2077%20767%201807>*

[image: http://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Communication Error between Active and Passive nodes.

[Damith Wickramasinghe]

Hi vasanthan,

It seems active node cannot create a tcp connection to passive node. Please
make sure above advertisedHost value should be the host of own node. Not
the host of other node.  If they are correct then try to telnet to passive
node {passive node host} 9893 from active node.  I think you may need a
host mapping too.

Adding thilina since he did a same setup with new HA.


Regards,
Damith.

On Fri, Sep 21, 2018 at 1:35 PM Vasanthan Sivalingam 
wrote:

>
> Hi Sp team,
>
> With the latest 4.3.0 release an HA deployment was done with kubernetes.
> the deployment configurations has been done as [1] and [2]. It was noticed
> that the active node is not communicating with the passive node with the
> following logs.
>
> ...
> [2018-09-21 11:54:32,435]  INFO
> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
> Setting SinksHandlers of TestSiddhiApp to Active
> [2018-09-21 11:54:32,436]  INFO
> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
> Setting RecordTableHandlers of TestSiddhiApp to Active
> [2018-09-21 11:54:32,436]  INFO
> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
> Siddhi App TestSiddhiApp deployed successfully
> [2018-09-21 11:54:32,446]  INFO
> {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 Stream
> Processor started in 6.922 sec
> [*2018-09-21 11:54:33,377] ERROR
> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
> Error in getting a connection to the Passive node. null*
> [2018-09-21 11:54:33,379] DEBUG
> {org.wso2.carbon.stream.processor.core.ha.HACoordinationSourceHandler} -
> Active Node: Saving state of Source Handler with Id TestSiddhiApp-1 with
> timestamp 0
> [2018-09-21 11:54:33,395] ERROR
> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
> Error in getting the TCP connection to the passive node. Hence not sending
> the control message to the passive node
> [2018-09-21 11:55:31,531]  INFO
> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
> siddhi Apps are persisted successfully.
> ...
>
> The deployment config was done as below,
>
> deployment.config:
>   type: ha
>   eventSyncServer:
> host: localhost
> port: 9893
> advertisedHost: sp-ha-node-1
> advertisedPort: 9893
> bossThreads: 10
> workerThreads: 10
>   eventSyncClientPool:
> maxActive: 10
> maxTotal: 10
> maxIdle: 10
> maxWait: 6
> minEvictableIdleTimeMillis: 12
>
> Attached the log file.
> Can you please suggest a method to make this communication work between
> active node and the passive node.
>
> [1]
> https://github.com/sameerawickramasekara/product-sp/blob/master/modules/integration/tests-kubernetes-integration/src/test/resources/artifacts/docker-files/deployment-ha-node-1.yaml
> [2]
> https://github.com/sameerawickramasekara/product-sp/blob/master/modules/integration/tests-kubernetes-integration/src/test/resources/artifacts/docker-files/deployment-ha-node-2.yaml
>
> Thanks,
> Vasanth
>


-- 
Senior Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

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

Re: [Dev] Upgrading C4 OSGi to support Java 10

[Tharindu Wijewardane]

Hi all,

I was able to fix the previous issue (some osgi services were not found) by
changing tycho/sisu p2 dependency versions of carbon p2 plugin to the
versions used in carbon feature plugin.
Then there were issues installing features which includes bundles from
identity server related dependencies
(carbon-identity, carbon-identity-framework, ...). I have to upgrade the
osgi platform of those as well but I commented out those features for now
(only 3 feature groups) and went ahead trying to get the APIM server
started first.

I could start the APIM framework on java 10 without those features but the
mgt console URL was not accessible possibly due to incompatibilities of
tomcat7 with java 10. Also there wasn't any error logs printed. As Ruwan
has previously mentioned in another mail thread, existing logging mechanism
in C4 is not compatible with java 10. As his instructions I will try to get
the logger working first.

Thanks

On Wed, Sep 12, 2018 at 12:44 PM Tharindu Wijewardane 
wrote:

> Hi all,
>
> I am trying to build APIM 2.x branch with modified versions of following
> dependencies (with upgraded osgi and some plugins)
>
>
> carbon-apimgt  version 6.4.27 (6.x branch)
>
> carbon-kernel version 4.4.35 (4.4.x branch)
>
> carbon-metrics version 1.2.4 (1.x.x branch)
> carbon p2 plugin version 1.6.1
>
> Originally APIM 2.x branch depended on carbon-apimgt 6.4.17 and carbon-metrics
> 1.2.3 and carbon p2 plugin 1.5.4.
> I chose the above branches because they had artifact versions closer to
> the existing versions and for avoiding build errors I got when trying out
> different branches.
> Please let me know if there is a better way to select the branches.
>
> Currently I am having issues building P2 profile generation module of
> APIM. Please see the following error.
>
>
> *Cannot complete the install because one or more required items could not
> be found. Software being installed: WSO2 Carbon - API Publisher Feature
> 6.4.27.1 (org.wso2.carbon.apimgt.publisher.feature.group 6.4.27.1) Missing
> requirement: org.wso2.carbon.apimgt.hostobjects 6.4.27.1
> (org.wso2.carbon.apimgt.hostobjects 6.4.27.1) requires 'osgi.service;
> (objectClass=org.wso2.carbon.user.core.service.RealmService)' but it could
> not be found Cannot satisfy dependency:  From: WSO2 Carbon - API Publisher
> Feature 6.4.27.1 (org.wso2.carbon.apimgt.publisher.feature.group 6.4.27.1)
> To: org.eclipse.equinox.p2.iu; org.wso2.carbon.apimgt.hostobjects
> [6.4.27.1,6.4.27.1]*
>
>
> Some features cannot be installed due to missing osgi services according
> to the error. But those are available in the relevant dependent libraries
> and also references can be found in osgi meta data.
>
> Any help is appreciated.
>
> Thanks
>
> On Mon, Sep 10, 2018 at 2:15 PM, Tharindu Wijewardane 
> wrote:
>
>> clarification:
>> I am trying to build APIM using java 8 (with the other upgraded
>> dependencies built with java 8) and run on java 10 as Shankar instructed.
>>
>> On Mon, Sep 10, 2018 at 1:45 PM, Tharindu Wijewardane > > wrote:
>>
>>> Hi,
>>>
>>> Finally I got the carbon kernel to build using java 10. It can be
>>> started on java 10 too. However,
>>> The last fix I did was to add "--add-modules=java.activation" jvm
>>> argument to maven ant run plugin for generating stub classes from wsdl
>>> files.
>>> Since Java 9, access to some javax* modules has been disabled. Therefore
>>> in order to use javax.activation* classes we have to manually add them.
>>> But with that change it will not compile on java 8. Further, with java
>>> 11, those deprecated modules may be removed from jdk and we may have to
>>> find another solution.
>>>
>>> I modified APIM (2.x branch) to use the upgraded carbon kernel and osgi
>>> dependencies. Then the other dependencies of APIM (carbon metrics, carbon
>>> apimgt, ..) are being incompatible. I will have to upgrade those as well.
>>> Currently I am looking into it.
>>>
>>> Thanks
>>>
>>>
>>> On Thu, Sep 6, 2018 at 6:39 PM, Selvaratnam Uthaiyashankar <
>>> shan...@wso2.com> wrote:
>>>
 Then, can you get APIM to build using JDK8, but run on JDK 10 please?
 We'll see how to proceed after doing that.

 On Thu, Sep 6, 2018 at 2:29 PM Tharindu Wijewardane 
 wrote:

> Hi all,
>
> As KasunG suggested I tried to get the carbon kernel (built with java
> 8) to run on java 10 first. Followings are the things I tried/found out.
>
>
>- Existing carbon 4 cannot be run on java 10 as the equinox
>version Kepler is not compatible with java 9 or 10. There are known 
> issues
>they did not fix on Kepler.
>
>
>- Earlier I have upgraded the equinox version to Photon (latest)
>and I have been trying to build with java 10 and was able to fix some
>issues but still I came across some issues even when building with 
> java 8.
>
>
> *Cannot complete the install because one or more required items could
> not be found.*
>

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.4.0 RC1

[Thishani Lucas]

Hi All,

Thank you for testing WSO2 Enterprise Integrator 6.4.0 - RC1.

Since this vote has passed with 14 +1s and 0 -1s, we're hereby closing this
vote and proceeding with the Enterprise Integrator 6.4.0 GA release.

Thanks,
Thishani

On Fri, Sep 21, 2018 at 11:50 AM, Asma Jabir  wrote:

> Hi all
>
> We have tested the wso2ei-6.4.0-RC-1 distribution on TestGrid and please
> find the test results in mail threads [1] and [2].
>
> Subsequent to the execution results, the product team had further tested
> the failing test cases manually and based on the results they have shared,
> 5 out of the failed tests are passing, 4 of them are invalid and the rest
> are due to issues in test cases. A summary of the test results is as
> follows:
>
> DBlookupMediatorTestCase#dbLookupTestStoredProcedures
>
> Invalid
>
> DBlookupMediatorTestCase#dbLookupMediatorTestWithMultipleResults
>
> Invalid
>
> BPMNRestVariableTestCase#init
>
> Invalid
>
> DBlookupMediatorTestCase#dbLookupTestStoredFunctions
>
> Invalid
>
> HumanTaskXpathExtensionsTest#testNumberFunctions
>
> Passed
>
> HumanTaskXpathExtensionsTest#testStringFunctions
>
> Passed
>
> BPELRPCPartnerInvocationTest#invokeRPCClientProcess
>
> Passed
>
> BpelVersioningTest#checkVersion
>
> Passed
>
> SendIntegrationTestCase#testSendingFailOverEndpoint_Receivin
> g_Sequence_Dynamic_BM
>
> Passed
>
> HttpAccessLogTestCase#init
>
> Test Issue
>
> ContentTypeTestCase#testReturnContentType#data_provider_1
>
> Test Issue
>
> ContentTypeTestCase#testReturnContentType#data_provider_6
>
> Test Issue
>
> BPMNRestDeploymentsTestCase#testGetDeployments
>
> Test Issue
>
> JMSEndpointTestCase#testJMSProxy
>
> Test Issue
>
> ESBJAVA3336HostHeaderValuePortCheckTestCase#setEnvironment
>
> Test Issue
>
> HTTPResponseCodeTestCase#testReturnResponseCode#data_provider_2
>
> Test Issue
>
> SingleServiceGeneratorTestCase#testServiceGeneration
>
> Test Issue
>
> PropertyPersistenceDeletingAndAddingTstCase#testMediationPer
> sistenceDeletingAndAdding
>
> Test Issue
>
> CarbonApplicationReDeploymentTestCase#carReDeploymentTest
>
> Test Issue
>
> BPMNUserSubstitutionTestCase#testAddSubstitute
>
> Test Issue
>
> MultipleServicesGeneratorTestCase#testServiceGeneration
>
> Test Issue
>
> Based on the above observation, TestGrid can proceed with the release vote
> as,
>
> [+] Stable - Go ahead and release
>
>
> [1] 'wso2ei-intg' Integration Test Failure! #(19)
> [2] 'wso2ei-intg' Integration Test Failure! #(22)
>
> Thank you
>
> Regards
> Asma
>
> On Fri, Sep 21, 2018 at 9:40 AM, Prabushi Samarakoon 
> wrote:
>
>> Hi All,
>>
>> I tested the following, and no issues found.
>>
>>- Template creation with new template dashboard
>>- Mediator project creation
>>- Synapse artifacts creation including proxy service, rest API,
>>sequence, local entry, etc.
>>- CApp creation
>>- Add/ use connectors within the mediation flow
>>- Error validation on source view
>>- Data mapper diagram view
>>- Add WSO2 EI 6.4.0 server and deploy artifacts
>>
>> [+] Stable - Go ahead and release
>>
>>
>> Thanks,
>> Prabushi
>>
>> On Thu, Sep 20, 2018 at 7:37 PM, Tharindu Edirisinghe > > wrote:
>>
>>> Reviewed the security scanning reports (static and dynamic) and +1 from
>>> the Platform Security Team for proceeding with the release.
>>>
>>> On Thu, Sep 20, 2018 at 7:10 PM Asanka Abeyweera 
>>> wrote:
>>>
 Hi All,

 I verified the basic functionality of a 2 node message broker cluster
 using MySQL as the RDBMS.

- Distributed Queues
- Multi-node subscription and publisher scenarios
- Multi-node topic scenarios

 [+] Stable - Go ahead and release

 On Thu, Sep 20, 2018 at 5:36 PM Nandika Jayawardana 
 wrote:

> Hi All,
>
> I verified the following functionality and found no issues.
>
> 1. BPMN process execution
> 2. Human Task execution
> 3. Micro Integrator execution with Apis, Endpoints, Datamapper in
> Docker containers
> 4. EI Tooling -> creating EI artifacts and Importing EI Artifacts.
> 5. Profile creator tool.
> 6. EI Analytics
>
> [+] Stable - Go ahead and release
>
> Regards
> Nandika
>
> On Thu, Sep 20, 2018 at 11:28 AM, Nirothipan Megalingham <
> nirothi...@wso2.com> wrote:
>
>> Hi all,
>>
>> I have tested the following and found no issues
>>
>>- Creating ESB Solution Projects and Templates in EI Tooling.
>>- Adding Server/Remote server in tooling and deploying the
>>artifacts.
>>- Creating Sample DSS projects.
>>- Creating Registry Resource / Connector exporter projects in
>>tooling.
>>- Deploying class mediators the server.
>>- Deploying sample schedule tasks with Micro Integrator profile.
>>
>>
>> +1 for the release.
>>
>> Thanks
>> Nirothipan
>>
>>
>> On Thu, Sep 20, 2018 at 10:23 AM Danushka Madhuranga <
>> 

Re: [Dev] [Architecture] [VOTE] Release of WSO2 Identity Server Analytics 5.7.0 RC3

[Nuwandi Wickramasinghe]

Hi all,

Thank you for testing WSO2 Identity Server Analytics 5.7.0.

Since the vote received 16 +1s and 0 -1 votes over 3 days, we are closing
this vote and proceeding with the WSO2 Identity Server Analytics 5.7.0 GA
release.

Thanks
Nuwandi

On Tue, Sep 18, 2018 at 11:16 PM Sahan Gunathilaka  wrote:

> Hi all,
>
> I have tested following and no issues were found.
>
>- Successful local login
>- Failed local login with incorrect credentials
>- Suspicious login alerts
>
>
> [+] Stable - go ahead and release
>
> Thanks!
> Best Regards!
>
> On Tue, Sep 18, 2018 at 6:14 PM, Thisaru Guruge  wrote:
>
>> Hi all,
>>
>> I have tested following:
>>
>>- Login Attempts Summary
>>- Overall Login Attempts
>>- Local Login Attempts
>>- Federated Login Attempts
>>
>> No issues found.
>>
>> [+] Stable - go ahead and release.
>>
>> On Tue, Sep 18, 2018 at 5:54 PM Mevan Karunanayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested following scenarios on WSO2 IS Analytics 5.7.0-RC3.
>>>
>>>- Suspicious login attempts dashboard.
>>>- Risk based adaptive authentication.
>>>- Federated login dashboard.
>>>- Overall logins dashboard.
>>>
>>> No blocking issues were found.
>>>
>>> *[+] Stable - go head and release.*
>>>
>>> Regards,
>>>
>>>
>>> On Tue, 18 Sep 2018, 17:33 Thumilan Mikunthan, 
>>> wrote:
>>>
 Hi all,

 I tested the following on WSO2 Identity Server Analytics 5.7.0 RC3 and
 no  issues were found.

- Local login attempts dashboard
- Suspicious login alerts

 [+] Stable - go ahead and release.

 Regards.
 M.Thumilan

 On Tue, Sep 18, 2018 at 5:30 PM Chuhaashanan Nagenthiran <
 chuhaasha...@wso2.com> wrote:

> Hi All,
>
> I have tested following and no issues were found.
>
>- Suspicious login attempts dashboard
>- Overall login attempts dashboard
>
> [+] Stable - go ahead and release.
>
> Regards,
> Chuhaashanan
>
> On Tue, Sep 18, 2018 at 5:25 PM Anuradha Karunarathna <
> anurad...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested the following and no issues were found.
>> Suspicious login attempts dashboard
>> Overall login attempts dashboard
>> Configuring risk-based Adaptive Authentication
>>
>>
>> [+] Stable - go ahead and release
>>
>>
>> *Anuradha Karunarathna*
>> Intern-Software Engineering | WSO2,inc.
>>
>>
>>
>> On Tue, Sep 18, 2018 at 5:21 PM, Tharindu Bandara > > wrote:
>>
>>> Hi all,
>>>
>>> I have tested the followings on WSO2 Identity Server Analytics 5.7.0
>>> RC3.
>>>
>>>- Risk based adaptive authentication.
>>>- Successful local login attempt.
>>>- Failed local login attempt.
>>>- Suspicious login attempt.
>>>
>>> No blocking issues were found.
>>>
>>> *[+] Stable - go ahead and release*
>>>
>>> Thanks,
>>> Tharindu
>>>
>>> On Tue, Sep 18, 2018 at 5:07 PM Chamath Samarawickrama <
>>> chama...@wso2.com> wrote:
>>>
 Hi,

 I have tested the following on WSO2 Identity Server Analytics 5.7.0
 RC3.

- Overall login attempts dashboard
- Suspicious login attempts dashboard
- Login sessions dashboard
- Configuring risk-based Adaptive Authentication

 No blocking issues were found.

 *[+] Stable - go ahead and release*

 Thanks,
 Chamath

 On Tue, Sep 18, 2018 at 3:42 PM Nuwandi Wickramasinghe <
 nuwan...@wso2.com> wrote:

> Hi All,
>
>
> We are pleased to announce the third release candidate of WSO2
> Identity Server Analytics 5.7.0.
>
>
> This release fixes the following issues,
>
>
>
>- 5.7.0-RC3 Fixes
>
>- 5.7.0-RC2 Fixes
>
>- 5.7.0-RC1 Fixes
>
>
>
>
> Source and distribution,
>
>
>- https://github.com/wso2/analytics-is/releases/v5.7.0-rc3
>
>
>
> Please download, test the product and vote.
>
>
>[+] Stable - go ahead and release
>
>[-] Broken - do not release (explain why)
>
>
>
> Thanks,
>
> - WSO2 Identity and Access Management Team -
>
> --
>
> Best Regards,
>
> Nuwandi Wickramasinghe
>
> Senior Software Engineer
>
> WSO2 Inc.
>
> Web : http://wso2.com
>
> 

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.4.0 RC1

[Asma Jabir]

Hi all

We have tested the wso2ei-6.4.0-RC-1 distribution on TestGrid and please
find the test results in mail threads [1] and [2].

Subsequent to the execution results, the product team had further tested
the failing test cases manually and based on the results they have shared,
5 out of the failed tests are passing, 4 of them are invalid and the rest
are due to issues in test cases. A summary of the test results is as
follows:

DBlookupMediatorTestCase#dbLookupTestStoredProcedures

Invalid

DBlookupMediatorTestCase#dbLookupMediatorTestWithMultipleResults

Invalid

BPMNRestVariableTestCase#init

Invalid

DBlookupMediatorTestCase#dbLookupTestStoredFunctions

Invalid

HumanTaskXpathExtensionsTest#testNumberFunctions

Passed

HumanTaskXpathExtensionsTest#testStringFunctions

Passed

BPELRPCPartnerInvocationTest#invokeRPCClientProcess

Passed

BpelVersioningTest#checkVersion

Passed

SendIntegrationTestCase#testSendingFailOverEndpoint_Receivin
g_Sequence_Dynamic_BM

Passed

HttpAccessLogTestCase#init

Test Issue

ContentTypeTestCase#testReturnContentType#data_provider_1

Test Issue

ContentTypeTestCase#testReturnContentType#data_provider_6

Test Issue

BPMNRestDeploymentsTestCase#testGetDeployments

Test Issue

JMSEndpointTestCase#testJMSProxy

Test Issue

ESBJAVA3336HostHeaderValuePortCheckTestCase#setEnvironment

Test Issue

HTTPResponseCodeTestCase#testReturnResponseCode#data_provider_2

Test Issue

SingleServiceGeneratorTestCase#testServiceGeneration

Test Issue

PropertyPersistenceDeletingAndAddingTstCase#testMediationPer
sistenceDeletingAndAdding

Test Issue

CarbonApplicationReDeploymentTestCase#carReDeploymentTest

Test Issue

BPMNUserSubstitutionTestCase#testAddSubstitute

Test Issue

MultipleServicesGeneratorTestCase#testServiceGeneration

Test Issue

Based on the above observation, TestGrid can proceed with the release vote
as,

[+] Stable - Go ahead and release


[1] 'wso2ei-intg' Integration Test Failure! #(19)
[2] 'wso2ei-intg' Integration Test Failure! #(22)

Thank you

Regards
Asma

On Fri, Sep 21, 2018 at 9:40 AM, Prabushi Samarakoon 
wrote:

> Hi All,
>
> I tested the following, and no issues found.
>
>- Template creation with new template dashboard
>- Mediator project creation
>- Synapse artifacts creation including proxy service, rest API,
>sequence, local entry, etc.
>- CApp creation
>- Add/ use connectors within the mediation flow
>- Error validation on source view
>- Data mapper diagram view
>- Add WSO2 EI 6.4.0 server and deploy artifacts
>
> [+] Stable - Go ahead and release
>
>
> Thanks,
> Prabushi
>
> On Thu, Sep 20, 2018 at 7:37 PM, Tharindu Edirisinghe 
> wrote:
>
>> Reviewed the security scanning reports (static and dynamic) and +1 from
>> the Platform Security Team for proceeding with the release.
>>
>> On Thu, Sep 20, 2018 at 7:10 PM Asanka Abeyweera 
>> wrote:
>>
>>> Hi All,
>>>
>>> I verified the basic functionality of a 2 node message broker cluster
>>> using MySQL as the RDBMS.
>>>
>>>- Distributed Queues
>>>- Multi-node subscription and publisher scenarios
>>>- Multi-node topic scenarios
>>>
>>> [+] Stable - Go ahead and release
>>>
>>> On Thu, Sep 20, 2018 at 5:36 PM Nandika Jayawardana 
>>> wrote:
>>>
 Hi All,

 I verified the following functionality and found no issues.

 1. BPMN process execution
 2. Human Task execution
 3. Micro Integrator execution with Apis, Endpoints, Datamapper in
 Docker containers
 4. EI Tooling -> creating EI artifacts and Importing EI Artifacts.
 5. Profile creator tool.
 6. EI Analytics

 [+] Stable - Go ahead and release

 Regards
 Nandika

 On Thu, Sep 20, 2018 at 11:28 AM, Nirothipan Megalingham <
 nirothi...@wso2.com> wrote:

> Hi all,
>
> I have tested the following and found no issues
>
>- Creating ESB Solution Projects and Templates in EI Tooling.
>- Adding Server/Remote server in tooling and deploying the
>artifacts.
>- Creating Sample DSS projects.
>- Creating Registry Resource / Connector exporter projects in
>tooling.
>- Deploying class mediators the server.
>- Deploying sample schedule tasks with Micro Integrator profile.
>
>
> +1 for the release.
>
> Thanks
> Nirothipan
>
>
> On Thu, Sep 20, 2018 at 10:23 AM Danushka Madhuranga <
> danush...@wso2.com> wrote:
>
>> Hi All,
>>
>> I have tested the following,
>>
>> User interface stability in the management console
>> Sequence creating editing and deleting using the management console
>> Mediators (All the mediators) adding editing and deleting using the
>> management console
>> Endpoints (All the endpoints) creating editing and deleting using the
>> management console
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks,
>>
>>
>> On Thu, Sep 20, 2018 at 9:27 AM,