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

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

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

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

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

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:

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

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