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, 

[Dev] [carbon-jndi] Name not bound to Context exception for rmi in NamingContext

[Asma Jabir]

Hi,

When trying to bind rmi for JMXConnectorServer with carbon-jndi a
*javax.naming.NameNotFoundException:
Name [rmi://127.0.0.1:/jmxrmi ] is not
bound in this Context. Unable to find [rmi:]* throws.

This is thrown by the org.wso2.carbon.jndi.internal.impl.NamingContext  from
the method
 protected void bind(Name name, Object obj, boolean rebind) throws
NamingException {}

after execution of line

NamingEntry entry = (NamingEntry)this.bindings.get(name.get(0));

This is because the if(name.size() > 1) is true and subsequently  if(entry
== null) also becomes true since the binding aren't put to the bindings map
yet [1].

Ideally, shouldn't it be that if the entry is null, the object is wrapped
with a new NamingEntry [2] ?

[1]
 
https://github.com/wso2/carbon-jndi/blob/v1.0.2/components/org.wso2.carbon.jndi/src/main/java/org/wso2/carbon/jndi/internal/impl/NamingContext.java#L818

[2]
https://github.com/wso2/carbon-jndi/blob/v1.0.2/components/org.wso2.carbon.jndi/src/main/java/org/wso2/carbon/jndi/internal/impl/NamingContext.java#L833


Thank you

Regards,
Asma

-- 
Asma Zinneera Jabir
Software Engineer
WSO2 Inc: http://wso2.com/
Contact No: +94 77 332 4752
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Findings] JMX access control : readOnly and readWrite access

[Asma Jabir]

Hi,

You can try out the sample in the github repo [1].

[1] https://github.com/azinneera/JMX-access-control

Thank you

Regards,
Asma

On Fri, Mar 31, 2017 at 9:15 AM, Imesh Gunaratne <im...@wso2.com> wrote:

> On Thu, Mar 30, 2017 at 3:02 PM, Asma Jabir <as...@wso2.com> wrote:
>
>> Hi
>>
>> I have been looking into the $subject issue in the github c5 repo [1] and
>> following is the summary of the findings till date.
>>
>> - There is a simple inbuilt authentication and authorization mechanism in
>> JMX using password and access files. Roles can be specified with either
>> readOnly or readWrite privileges [2].
>>
>>- *readOnly* does not allow to change values or to invoke operations
>>but can monitor
>>- *readWrite *gives the total control over the server which allows to
>>change values and invoke operations
>>
>> Great work Asma!
> ​Will you be able to share the sample application that you implemented for
> verifying this functionality?
>
> Thanks
> Imesh
>
>
>> - Both password and access files are properties based text files for
>> specifying username/password pairs and username/access pairs respectively.
>>
>> - The password and access files could reside anywhere in the server and
>> should be provided upon server startup.
>>
>> - SSL is enabled by default for remote monitoring and thus the SSL should
>> be configured properly after setting up a digital certificate. System
>> properties for keystore and truststore should be set in the server.
>>
>> [1] https://github.com/wso2/carbon-kernel/issues/1247
>> [2] http://docs.oracle.com/javase/7/docs/technotes/guides/ma
>> nagement/agent.html
>> <http://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html>
>>
>>
>> Thanks.
>>
>> Regards,
>> Asma
>> --
>> Asma Zinneera Jabir
>> Software Engineer
>> WSO2 Inc: http://wso2.com/
>> Contact No: +94 77 332 4752 <+94%2077%20332%204752>
>>
>>
>>
>
>
> --
> *Imesh Gunaratne*
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057>
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>


-- 
Asma Zinneera Jabir
Software Engineer
WSO2 Inc: http://wso2.com/
Contact No: +94 77 332 4752 <+94%2077%20332%204752>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Findings] JMX access control : readOnly and readWrite access

[Asma Jabir]

Hi

I have been looking into the $subject issue in the github c5 repo [1] and
following is the summary of the findings till date.

- There is a simple inbuilt authentication and authorization mechanism in
JMX using password and access files. Roles can be specified with either
readOnly or readWrite privileges [2].

   - *readOnly* does not allow to change values or to invoke operations but
   can monitor
   - *readWrite *gives the total control over the server which allows to
   change values and invoke operations

- Both password and access files are properties based text files for
specifying username/password pairs and username/access pairs respectively.

- The password and access files could reside anywhere in the server and
should be provided upon server startup.

- SSL is enabled by default for remote monitoring and thus the SSL should
be configured properly after setting up a digital certificate. System
properties for keystore and truststore should be set in the server.

[1] https://github.com/wso2/carbon-kernel/issues/1247
[2] http://docs.oracle.com/javase/7/docs/technotes/
guides/management/agent.html



Thanks.

Regards,
Asma
-- 
Asma Zinneera Jabir
Software Engineer
WSO2 Inc: http://wso2.com/
Contact No: +94 77 332 4752 <+94%2077%20332%204752>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev