Re: [Dev] [VOTE] Release WSO2 Identity Server 5.1.0 RC2

[Hasintha Indrajee]

Hi Prabath,

It's available now. Can you please check.

On Mon, Dec 21, 2015 at 10:16 PM, Prabath Siriwardana 
wrote:

>
>
> On Mon, Dec 21, 2015 at 4:59 AM, Hasintha Indrajee 
> wrote:
>
>> Hi Devs,
>>
>> This is the second release candidate of WSO2 Identity Server 5.1.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12586
>>
>> Please download, test and vote.
>>
>> Source & binary distribution files:
>> https://github.com/wso2/product-is/releases/tag/v5.1.0-rc2
>>
>
> Returns 404...
>
> Thanks & regards,
> -Prabath
>
>
>>
>> Maven staging repo:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2is-218/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-is/tree/v5.1.0-rc2
>>
>>
>> [ ]  Stable - go ahead and release
>> [ ]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> WSO2 Identity Server Team.
>>
>> --
>> Hasintha Indrajee
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 771892453
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Twitter : @prabath
> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena
>
> Mobile : +1 650 625 7950
>
> http://blog.facilelogin.com
> http://blog.api-security.org
>



-- 
Hasintha Indrajee
Software Engineer
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC4

[Maheshakya Wijewardena]

Hi Devs,

This is the 4th Release Candidate of WSO2 Machine Learner 1.1.0.

This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12600

Please download, test and vote. Vote will be open for 72 hours or as longer
as needed.

*Binary distribution files:*
https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/wso2ml-1.1.0.zip

*P2 repository*:
https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/p2-repo.zip


*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2ml-224/


*The tag to be voted upon:*
https://github.com/wso2/product-ml/tree/v1.1.0-rc4


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release

Thank you,
Machine Learner Team

-- 
Pruthuvi Maheshakya Wijewardena
mahesha...@wso2.com
+94711228855
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.1.0 RC2

[Prabath Siriwardana]

Thanks.. works fine now...

On Mon, Dec 21, 2015 at 11:41 AM, Hasintha Indrajee 
wrote:

> Hi Prabath,
>
> It's available now. Can you please check.
>
> On Mon, Dec 21, 2015 at 10:16 PM, Prabath Siriwardana 
> wrote:
>
>>
>>
>> On Mon, Dec 21, 2015 at 4:59 AM, Hasintha Indrajee 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the second release candidate of WSO2 Identity Server 5.1.0.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12586
>>>
>>> Please download, test and vote.
>>>
>>> Source & binary distribution files:
>>> https://github.com/wso2/product-is/releases/tag/v5.1.0-rc2
>>>
>>
>> Returns 404...
>>
>> Thanks & regards,
>> -Prabath
>>
>>
>>>
>>> Maven staging repo:
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2is-218/
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-is/tree/v5.1.0-rc2
>>>
>>>
>>> [ ]  Stable - go ahead and release
>>> [ ]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards,
>>> WSO2 Identity Server Team.
>>>
>>> --
>>> Hasintha Indrajee
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile:+94 771892453
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Twitter : @prabath
>> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena
>>
>> Mobile : +1 650 625 7950
>>
>> http://blog.facilelogin.com
>> http://blog.api-security.org
>>
>
>
>
> --
> Hasintha Indrajee
> Software Engineer
> WSO2, Inc.
> Mobile:+94 771892453
>
>


-- 
Thanks & Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +1 650 625 7950

http://blog.facilelogin.com
http://blog.api-security.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.1.0 RC2

[Prabath Siriwardana]

Smoke tested local account mapping feature with..

1. Multiple tenants
2. Multiple user stores (LDAP and MySQL)
3. Add/Delete user operations
4. Activate/Deactivate tenant operations
5. Activate/Deactivate user store operations

All working fine except one minor issue (
https://wso2.org/jira/browse/IDENTITY-4245 - reported as L3).

Will test further on other features and update the status..

Thanks & regards,
-Prabath

On Mon, Dec 21, 2015 at 4:59 AM, Hasintha Indrajee 
wrote:

> Hi Devs,
>
> This is the second release candidate of WSO2 Identity Server 5.1.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12586
>
> Please download, test and vote.
>
> Source & binary distribution files:
> https://github.com/wso2/product-is/releases/tag/v5.1.0-rc2
>
> Maven staging repo:
> http://maven.wso2.org/nexus/content/repositories/orgwso2is-218/
>
> The tag to be voted upon:
> https://github.com/wso2/product-is/tree/v5.1.0-rc2
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
> Thanks and Regards,
> WSO2 Identity Server Team.
>
> --
> Hasintha Indrajee
> Software Engineer
> WSO2, Inc.
> Mobile:+94 771892453
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +1 650 625 7950

http://blog.facilelogin.com
http://blog.api-security.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][Urgent] Getting error while generating access tokens with openid scope

[Maduranga Siriwardena]

Hi,
Ideally this should be fixed in kernel as we mentioned above. But we have
fixed this and released carbon-identity 5.0.7

@Product teams,
Please update your carbon-identity version to 5.0.7

Thanks,
Maduranga.

On Mon, Dec 21, 2015 at 11:58 AM, Sanjeewa Malalgoda 
wrote:

>
>
> On Mon, Dec 21, 2015 at 11:48 AM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Sanjeewa,
>>
>> We tried to reproduce the issue with IS 5.1.0 RC1 and we couldn't
>> reproduce.
>>
>> Further we investigated and observed that the problem seems to be in
>> KeyStoreManager in kernel [1]. In KeyStoreManager, primaryKeyStore is
>> initialized from getPrimaryKeyStore() [2]. For IS getPrimaryKeyStore() is
>> called from one of our components [3] and so primaryKeyStore is getting
>> initialized. But for APIM this is not happening. As a workaround you can do
>> the same from one of your components.
>>
>> [1]
>> https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java
>> [2]
>> https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java#L328
>> [3]
>> https://github.com/wso2/carbon-identity/blob/v5.0.5/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java#L157
>>
>
> If this key store initializing is required for OAuth endpoint and OAuth
> service why don't we initialize from oauth components?
> As i understood this issue is not happening in IS because some other
> component initialize this instead of OAuth endpoint or service.
> Let say we fixed it in our components(APIM), but still if someone
> installed OAuth features into kernal or any other server they still see
> same issue.
> So i think its better to add this to OAuth component itself.
>
>>
>> Thanks,
>> Maduranga.
>>
>> On Mon, Dec 21, 2015 at 10:03 AM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> Hi Team,
>>> While requesting access tokens with openid scope(see curl request[1])
>>> i'm getting following error[2].
>>> I tested this with carbon-identity 5.0.5 based AM build and i don't
>>> think 5.0.6 do not have changes related to this use case.
>>> I tested this with another white listed scopes to confirm this happen
>>> due to white listed scopes or specific to openId.
>>> We were able to get access tokens for normal white listed scopes but not
>>> for openid scope.
>>> Generate access tokens with openid scope is very common use case for all
>>> API manager clients.
>>> Did i missed anything here or we need to fix it (since this is NPE i
>>> think we should fix this)?
>>>
>>> [1]curl -k -d
>>> "grant_type=password=admin=admin=openid" -H
>>> "Authorization: Basic
>>> VUFmMWFmZ3VCTzFaVE5QY0k2d2ZYbXNIQ1hVYTpUWURlT01nQjc3ME5DQ3RraTBZR3BNUVdQT2Nh"
>>> https://10.100.1.65:8243/token
>>>
>>> [2][2015-12-21 09:46:53,812] ERROR - OAuth2Service Error occurred while
>>> issuing the access token for Client ID : UAf1afguBO1ZTNPcI6wfXmsHCXUa, User
>>> ID admin, Scope : [openid] and Grant Type : password
>>> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error while
>>> obtaining private key for super tenant
>>> at
>>> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWTWithRSA(DefaultIDTokenBuilder.java:351)
>>> at
>>> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWT(DefaultIDTokenBuilder.java:514)
>>> at
>>> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.buildIDToken(DefaultIDTokenBuilder.java:237)
>>> at
>>> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:224)
>>> at
>>> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
>>> at
>>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:245)
>>> at
>>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:111)
>>> 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.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
>>> at
>>> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
>>> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
>>> at
>>> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:94)
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
>>> at
>>> 

[Dev] Maintenance Notice for Public Mailing List server (wso2.org) on 2015/12/22 , 5.30 PM (LK Time)

[Chamara Thilina]

HI All,

This is to inform that we will be performing maintenance to wso2.org
Mailing list server tomorrow  during 5.30 - 6.30 PM. As a result mails
publishing to wso2.org will get delayed during the mentioned period.

Sorry for the inconvenience caused.

Thank You,
ChamaraT.

-- 
Chamara Thilina Samarakoon
Senior Systems Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94772929487
blog: http://mageconfig.blogspot.com/
linkedin: https://www.linkedin.com/pub/chamara-samarakoon
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] HTTPS REST Client

[Malmee Weerasinghe]

Hi All,
I have tried with the actual path and I get the same error. AFAIU this have
to be a certificate error. [1]
As Dharshana suggested I would use existing libraries to build the HTTPS
client.

[1] https://github.com/nishadi/product-private-paas/pull/2

Thank you

On Fri, Dec 18, 2015 at 12:25 PM, Kasun Indrasiri  wrote:

> Any reason to building a HTTP client from scratch? Why don't we use
> existing libs such as HTTPClient or Netty?
>
> On Fri, Dec 18, 2015 at 8:51 AM, Harsha Thirimanna 
> wrote:
>
>> Just try to give absolute path first and test. Because as Dharshana
>> mentioned, it should work.
>>
>>
>> *Harsha Thirimanna*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> * *
>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>> *twitter: **http://twitter.com/ *
>> *harshathirimannlinked-in: **http:
>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Thu, Dec 17, 2015 at 5:23 PM, Dharshana Warusavitharana <
>> dharsha...@wso2.com> wrote:
>>
>>> Hi Malmee,
>>>
>>> You have to replace the cert location with actuvel .srt file you have.
>>>
>>> Thank you,
>>> Dharshana
>>>
>>> On Thu, Dec 17, 2015 at 2:32 PM, Malmee Weerasinghe 
>>> wrote:
>>>
 Hi Dharshana,
 I tried with what you suggested. But I still get the same error.
 ppaas-artifact-converter tool doesn't run on Carbon and it runs
 independently. Therefore for "System.getProperty("carbon.home")" it
 returns null. I tried copying this file, "wso2carbon.jks" to the resources
 folder. But I get the same error.
 Thank you.

 On Thu, Dec 17, 2015 at 9:31 AM, Dharshana Warusavitharana <
 dharsha...@wso2.com> wrote:

> Hi Malmee,
>
> The SSL issue comes with the rest client is because you are going to
> invoke HTTPS backend with out proper certificate in path.
>
> you can set keys to the system path using following
>
> String trustStore = System.getProperty("carbon.home") + File.separator + 
> "repository" + File.separator +
> "resources" + File.separator + "security" + 
> File.separator + "wso2carbon.jks";
> System.setProperty("javax.net.ssl.trustStore", trustStore);
> System.setProperty("javax.net.ssl.trustStorePassword", "wso2carbon");
> System.setProperty("javax.net.ssl.trustStoreType", "JKS");
>
>
> In this sample WSO2 carbon keys set as keys to the system path you can 
> use the same.
>
> Apache HTTP client is bit old client instead you can try some thing like 
> JAX-RS 2 or RestEasy client.
>
> In All these clients you need to add above code segment to export keys to 
> call secured HTTP call.
>
>
> Thank you,
>
> Dharshana.
>
>
> On Wed, Dec 16, 2015 at 8:56 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Malmee,
>>
>> If you have used java built in methods, that would mean your tool
>> would not be required to depend on an external library such as Apache 
>> HTTP
>> client as you have mentioned. This is fine for a simple use case. 
>> However,
>> please note if you need more functionality, such as support for all HTTP
>> operations, and other capabilities, etc. it would be advisable to use
>> Apache HTTP client or any other suitable existing library without
>> implementing it again by yourself.
>>
>> For the certificate issue that you are getting, its possible to
>> override the default certificate validation mechanism and plug in your 
>> own
>> implementation which can disable certificate validation (for testing
>> purposes). For HTTP Client 4, please see [1].
>>
>> [1].
>> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-errors-in-apache-httpclient-4-0
>>
>> On Wed, Dec 16, 2015 at 8:29 PM, Malmee Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> We have developed a HTTPS REST client using java in-built methods
>>> which works properly. [1] This method is configured to allow self signed
>>> certificates.
>>>
>>> When using apache http client we get a certificate error :
>>> javax.net.ssl.SSLPeerUnverifiedException: Host name
>>> '192.168.30.227' does not match the certificate subject provided by the
>>> peer (CN=localhost, O=WSO2, L=Mountain View, ST=CA, C=US).
>>>
>>> What would be a good choice? Using apache HTTP client or java in
>>> built methods. Your suggestions are highly appreciated.
>>>
>>> [1]
>>> 

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Yasassri Ratnayake]

Hi,

We were able to successfully start MB without any issue with Java 1.8 and
with Java 1.7 in windows environment. I tested with your exact java version
as well (1.7.0_79). I believe you haven't set your environment variables
properly. As per your error it says "The system cannot find the file
specified.".  I think this is self explanatory.

Please compare with the following logs and check whats missing.

TID: [] [] [2015-12-21 10:23:49,834]  WARN
{org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
determine dialect of the StAX implementation at
bundleresource://13.fwk2427473/
{org.apache.axiom.util.stax.dialect.StAXDialectDetector}
TID: [] [] [2015-12-21 10:23:49,834]  WARN
{org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
determine dialect of the StAX implementation at
bundleresource://13.fwk2427473/
{org.apache.axiom.util.stax.dialect.StAXDialectDetector}
TID: [] [] [2015-12-21 10:23:49,756]  INFO
{org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting BundleContext
in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Windows Server 2012 R2 6.3, amd64
{org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
C:\Program Files\Java\jdk1.7.0_79\jre
{org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
{org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
{org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
{org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
Administrator, en-US, UTC
{org.wso2.carbon.core.internal.CarbonCoreActivator}
TID: [-1234] [] [2015-12-21 10:23:51,694]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
running OS : Windows Server 2012 R2 is not a tested Operating System for
running WSO2 Carbon
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
TID: [-1234] [] [2015-12-21 10:23:51,709]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
 Carbon is configured to use the default keystore (wso2carbon.jks). To
maximize security when deploying to a production environment, configure a
new keystore with a unique password in the production server profile.
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
TID: [] [] [2015-12-21 10:23:51,725]  INFO
{org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
{org.wso2.carbon.databridge.agent.thrift.AgentHolder}
TID: [] [] [2015-12-21 10:23:51,756]  INFO
{org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
deployed Agent Client
{org.wso2.carbon.databridge.agent.thrift.internal.AgentDS}
TID: [-1234] [] [2015-12-21 10:23:54,615]  INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Configured
Registry in 99ms
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
TID: [-1234] [] [2015-12-21 10:23:54,725]  INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
 Registry Mode: READ-WRITE
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent}
TID: [-1234] [] [2015-12-21 10:23:54,881]  INFO
{org.wso2.carbon.metrics.impl.MetricServiceImpl} -  Creating JDBC reporter
for Metrics with source 'oracle12c', data source 'jdbc/WSO2MetricsDB' and
60 seconds polling period {org.wso2.carbon.metrics.impl.MetricServiceImpl}
TID: [-1234] [] [2015-12-21 10:23:54,881]  INFO
{org.wso2.carbon.metrics.impl.reporter.AbstractReporter} -  Started JMX
reporter for Metrics
{org.wso2.carbon.metrics.impl.reporter.AbstractReporter}
TID: [-1234] [] [2015-12-21 10:23:54,897]  INFO
{org.wso2.carbon.metrics.impl.reporter.AbstractReporter} -  Started JDBC
reporter for Metrics
{org.wso2.carbon.metrics.impl.reporter.AbstractReporter}
TID: [-1234] [] [2015-12-21 10:23:55,647]  INFO

[Dev] [VOTE] Release WSO2 Private PaaS 4.1.1 RC2

[Gayan Gunarathne]

 Hi All,

This is the second release candidate of WSO2 Private PaaS 4.1.1.

This release fixes the following issues:
*https://wso2.org/jira/browse/PAAS-305?filter=12582
*

Please download, test and vote. The vote will be open for 72 hours or as
needed.

*​Source and binary distribution files:*
https://svn.wso2.org/repos/wso2/scratch/PPAAS/wso2ppaas-4.1.1-rc2/

*Maven staging repository:*

http://maven.wso2.org/nexus/content/repositories/orgwso2ppaas-217/

*The tag to be voted upon:*
https://github.com/wso2/product-private-paas/tree/v4.1.1-rc2


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release


Thanks,
The WSO2 Private PaaS Team

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Carbon Kernel 5.0.0 Released !!!

[Aruna Karunarathna]

*WSO2 Carbon Kernel 5.0.0 - Released !!!*


We are pleased to announce the release of WSO2 Carbon Kernel 5.0.0. It is
now available to download from here
.
The source and tag location for this release are available here
.

WSO2 Carbon Kernel 5.0.0 is the core of the next-generation WSO2 Carbon
platform. We have completely rearchitected Carbon Kernel from the ground up
with the latest technologies and patterns. Additionally, the Carbon Kernel
is now a lightweight, general-purpose OSGi runtime specializing in hosting
servers, providing key functionality for server developers. The result is a
streamlined and even more powerful middleware platform than ever before.

This release of the WSO2 Carbon Kernel includes the following key features. For
further details please see the documentation
.


Key Features

   - Transport Management Framework
   - Logging Framework with Log4j 2.0 as the Backend
   - Carbon Startup Order Resolver
   - Dropins Support for OSGi Ready Bundles
   - Jar to Bundle Conversion Tool
   - Artifact Deployment Engine
   - Pluggable Runtime Support





Fixed Issues

   - WSO2 Carbon Kernel 5.0.0 - Fixed Issues
   

Known Issues

   - WSO2 Carbon Kernel 5.0.0 - Known Issues
   

How To Contribute

You can find more instructions on how to contribute on our documentation
 site.

If you have any suggestions or are interested in Carbon Kernel 5.0.0
discussions, you can join the dev@wso2.org or architect...@wso2.org mailing
lists.
Reporting Issues

We encourage you to report issues, documentation errors regarding WSO2
Carbon Kernel 5.0.0 through the public issue tracking system
.


Thanks,

WSO2 Carbon Team
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][Urgent] Getting error while generating access tokens with openid scope

[Deependra Ariyadewa]

On Mon, Dec 21, 2015 at 3:09 PM, Maduranga Siriwardena 
wrote:

> Hi,
> Ideally this should be fixed in kernel as we mentioned above. But we have
> fixed this and released carbon-identity 5.0.7
>
> @Product teams,
> Please update your carbon-identity version to 5.0.7
>

ACK

>
> Thanks,
> Maduranga.
>
> On Mon, Dec 21, 2015 at 11:58 AM, Sanjeewa Malalgoda 
> wrote:
>
>>
>>
>> On Mon, Dec 21, 2015 at 11:48 AM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Sanjeewa,
>>>
>>> We tried to reproduce the issue with IS 5.1.0 RC1 and we couldn't
>>> reproduce.
>>>
>>> Further we investigated and observed that the problem seems to be in
>>> KeyStoreManager in kernel [1]. In KeyStoreManager, primaryKeyStore is
>>> initialized from getPrimaryKeyStore() [2]. For IS getPrimaryKeyStore() is
>>> called from one of our components [3] and so primaryKeyStore is getting
>>> initialized. But for APIM this is not happening. As a workaround you can do
>>> the same from one of your components.
>>>
>>> [1]
>>> https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java
>>> [2]
>>> https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java#L328
>>> [3]
>>> https://github.com/wso2/carbon-identity/blob/v5.0.5/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java#L157
>>>
>>
>> If this key store initializing is required for OAuth endpoint and OAuth
>> service why don't we initialize from oauth components?
>> As i understood this issue is not happening in IS because some other
>> component initialize this instead of OAuth endpoint or service.
>> Let say we fixed it in our components(APIM), but still if someone
>> installed OAuth features into kernal or any other server they still see
>> same issue.
>> So i think its better to add this to OAuth component itself.
>>
>>>
>>> Thanks,
>>> Maduranga.
>>>
>>> On Mon, Dec 21, 2015 at 10:03 AM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Hi Team,
 While requesting access tokens with openid scope(see curl request[1])
 i'm getting following error[2].
 I tested this with carbon-identity 5.0.5 based AM build and i don't
 think 5.0.6 do not have changes related to this use case.
 I tested this with another white listed scopes to confirm this happen
 due to white listed scopes or specific to openId.
 We were able to get access tokens for normal white listed scopes but
 not for openid scope.
 Generate access tokens with openid scope is very common use case for
 all API manager clients.
 Did i missed anything here or we need to fix it (since this is NPE i
 think we should fix this)?

 [1]curl -k -d
 "grant_type=password=admin=admin=openid" -H
 "Authorization: Basic
 VUFmMWFmZ3VCTzFaVE5QY0k2d2ZYbXNIQ1hVYTpUWURlT01nQjc3ME5DQ3RraTBZR3BNUVdQT2Nh"
 https://10.100.1.65:8243/token

 [2][2015-12-21 09:46:53,812] ERROR - OAuth2Service Error occurred while
 issuing the access token for Client ID : UAf1afguBO1ZTNPcI6wfXmsHCXUa, User
 ID admin, Scope : [openid] and Grant Type : password
 org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error while
 obtaining private key for super tenant
 at
 org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWTWithRSA(DefaultIDTokenBuilder.java:351)
 at
 org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWT(DefaultIDTokenBuilder.java:514)
 at
 org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.buildIDToken(DefaultIDTokenBuilder.java:237)
 at
 org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:224)
 at
 org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
 at
 org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:245)
 at
 org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:111)
 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.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
 at
 org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
 at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:204)
 at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:101)
 at
 org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
 at
 

Re: [Dev] [DEV][Urgent] Getting error while generating access tokens with openid scope

[Sanjeewa Malalgoda]

ACK.

Thanks,
sanjeewa.

On Mon, Dec 21, 2015 at 3:18 PM, Deependra Ariyadewa  wrote:

>
>
> On Mon, Dec 21, 2015 at 3:09 PM, Maduranga Siriwardena  > wrote:
>
>> Hi,
>> Ideally this should be fixed in kernel as we mentioned above. But we have
>> fixed this and released carbon-identity 5.0.7
>>
>> @Product teams,
>> Please update your carbon-identity version to 5.0.7
>>
>
> ACK
>
>>
>> Thanks,
>> Maduranga.
>>
>> On Mon, Dec 21, 2015 at 11:58 AM, Sanjeewa Malalgoda 
>> wrote:
>>
>>>
>>>
>>> On Mon, Dec 21, 2015 at 11:48 AM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Sanjeewa,

 We tried to reproduce the issue with IS 5.1.0 RC1 and we couldn't
 reproduce.

 Further we investigated and observed that the problem seems to be in
 KeyStoreManager in kernel [1]. In KeyStoreManager, primaryKeyStore is
 initialized from getPrimaryKeyStore() [2]. For IS getPrimaryKeyStore() is
 called from one of our components [3] and so primaryKeyStore is getting
 initialized. But for APIM this is not happening. As a workaround you can do
 the same from one of your components.

 [1]
 https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java
 [2]
 https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java#L328
 [3]
 https://github.com/wso2/carbon-identity/blob/v5.0.5/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java#L157

>>>
>>> If this key store initializing is required for OAuth endpoint and OAuth
>>> service why don't we initialize from oauth components?
>>> As i understood this issue is not happening in IS because some other
>>> component initialize this instead of OAuth endpoint or service.
>>> Let say we fixed it in our components(APIM), but still if someone
>>> installed OAuth features into kernal or any other server they still see
>>> same issue.
>>> So i think its better to add this to OAuth component itself.
>>>

 Thanks,
 Maduranga.

 On Mon, Dec 21, 2015 at 10:03 AM, Sanjeewa Malalgoda  wrote:

> Hi Team,
> While requesting access tokens with openid scope(see curl request[1])
> i'm getting following error[2].
> I tested this with carbon-identity 5.0.5 based AM build and i don't
> think 5.0.6 do not have changes related to this use case.
> I tested this with another white listed scopes to confirm this happen
> due to white listed scopes or specific to openId.
> We were able to get access tokens for normal white listed scopes but
> not for openid scope.
> Generate access tokens with openid scope is very common use case for
> all API manager clients.
> Did i missed anything here or we need to fix it (since this is NPE i
> think we should fix this)?
>
> [1]curl -k -d
> "grant_type=password=admin=admin=openid" -H
> "Authorization: Basic
> VUFmMWFmZ3VCTzFaVE5QY0k2d2ZYbXNIQ1hVYTpUWURlT01nQjc3ME5DQ3RraTBZR3BNUVdQT2Nh"
> https://10.100.1.65:8243/token
>
> [2][2015-12-21 09:46:53,812] ERROR - OAuth2Service Error occurred
> while issuing the access token for Client ID :
> UAf1afguBO1ZTNPcI6wfXmsHCXUa, User ID admin, Scope : [openid] and Grant
> Type : password
> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error while
> obtaining private key for super tenant
> at
> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWTWithRSA(DefaultIDTokenBuilder.java:351)
> at
> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWT(DefaultIDTokenBuilder.java:514)
> at
> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.buildIDToken(DefaultIDTokenBuilder.java:237)
> at
> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:224)
> at
> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:245)
> at
> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:111)
> 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.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:188)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:104)
> at 

Re: [Dev] HTTPS REST Client

[Malmee Weerasinghe]

Hi All,
The method I have built doesn't need any dependencies. That was the main
concern for building it this way. But as Kasun suggests I will use existing
libraries to build the rest client considering the need of more
functionality.
Thank you

On Fri, Dec 18, 2015 at 12:25 PM, Kasun Indrasiri  wrote:

> Any reason to building a HTTP client from scratch? Why don't we use
> existing libs such as HTTPClient or Netty?
>
> On Fri, Dec 18, 2015 at 8:51 AM, Harsha Thirimanna 
> wrote:
>
>> Just try to give absolute path first and test. Because as Dharshana
>> mentioned, it should work.
>>
>>
>> *Harsha Thirimanna*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> * *
>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>> *twitter: **http://twitter.com/ *
>> *harshathirimannlinked-in: **http:
>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Thu, Dec 17, 2015 at 5:23 PM, Dharshana Warusavitharana <
>> dharsha...@wso2.com> wrote:
>>
>>> Hi Malmee,
>>>
>>> You have to replace the cert location with actuvel .srt file you have.
>>>
>>> Thank you,
>>> Dharshana
>>>
>>> On Thu, Dec 17, 2015 at 2:32 PM, Malmee Weerasinghe 
>>> wrote:
>>>
 Hi Dharshana,
 I tried with what you suggested. But I still get the same error.
 ppaas-artifact-converter tool doesn't run on Carbon and it runs
 independently. Therefore for "System.getProperty("carbon.home")" it
 returns null. I tried copying this file, "wso2carbon.jks" to the resources
 folder. But I get the same error.
 Thank you.

 On Thu, Dec 17, 2015 at 9:31 AM, Dharshana Warusavitharana <
 dharsha...@wso2.com> wrote:

> Hi Malmee,
>
> The SSL issue comes with the rest client is because you are going to
> invoke HTTPS backend with out proper certificate in path.
>
> you can set keys to the system path using following
>
> String trustStore = System.getProperty("carbon.home") + File.separator + 
> "repository" + File.separator +
> "resources" + File.separator + "security" + 
> File.separator + "wso2carbon.jks";
> System.setProperty("javax.net.ssl.trustStore", trustStore);
> System.setProperty("javax.net.ssl.trustStorePassword", "wso2carbon");
> System.setProperty("javax.net.ssl.trustStoreType", "JKS");
>
>
> In this sample WSO2 carbon keys set as keys to the system path you can 
> use the same.
>
> Apache HTTP client is bit old client instead you can try some thing like 
> JAX-RS 2 or RestEasy client.
>
> In All these clients you need to add above code segment to export keys to 
> call secured HTTP call.
>
>
> Thank you,
>
> Dharshana.
>
>
> On Wed, Dec 16, 2015 at 8:56 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Malmee,
>>
>> If you have used java built in methods, that would mean your tool
>> would not be required to depend on an external library such as Apache 
>> HTTP
>> client as you have mentioned. This is fine for a simple use case. 
>> However,
>> please note if you need more functionality, such as support for all HTTP
>> operations, and other capabilities, etc. it would be advisable to use
>> Apache HTTP client or any other suitable existing library without
>> implementing it again by yourself.
>>
>> For the certificate issue that you are getting, its possible to
>> override the default certificate validation mechanism and plug in your 
>> own
>> implementation which can disable certificate validation (for testing
>> purposes). For HTTP Client 4, please see [1].
>>
>> [1].
>> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-errors-in-apache-httpclient-4-0
>>
>> On Wed, Dec 16, 2015 at 8:29 PM, Malmee Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> We have developed a HTTPS REST client using java in-built methods
>>> which works properly. [1] This method is configured to allow self signed
>>> certificates.
>>>
>>> When using apache http client we get a certificate error :
>>> javax.net.ssl.SSLPeerUnverifiedException: Host name
>>> '192.168.30.227' does not match the certificate subject provided by the
>>> peer (CN=localhost, O=WSO2, L=Mountain View, ST=CA, C=US).
>>>
>>> What would be a good choice? Using apache HTTP client or java in
>>> built methods. Your suggestions are highly appreciated.
>>>
>>> [1]
>>> 

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Isuru Perera]

Yes! The 32-bit JVM cannot allocate enough memory for the MB.

On Tue, Dec 22, 2015 at 11:14 AM, Jason De Silva  wrote:

> Hi Nadeesha,
>
> As Isuru pointed since you have tried it out with 32 bit JDK which will
> not be able to allocate 2 gb memory [1] whereas MB needs 2 gb memory [2]
> which was the cause for the product to not start on 32 bit JDK.
>
> [1]
> http://www.oracle.com/technetwork/java/hotspotfaq-138619.html#gc_heap_32bit
> [2] https://docs.wso2.com/display/MB300/Installation+Prerequisites
>
> Regards,
>
>
> On Mon, Dec 21, 2015 at 9:20 PM, Nadeesha Meegoda 
> wrote:
>
>> Hi Isuru,
>>
>> Yes I am running MB on the 32-bit JDK. I have installed both 32 bit and
>> 64 bit JDK in my machine. However other products seems to start without any
>> error in both 32bit and 64bit JDK. I also checked MB in 64bit JDK now. MB
>> starts fine with that.
>>
>>
>> Thanks,
>> Nadeesha
>>
>> On Mon, Dec 21, 2015 at 6:13 PM, Isuru Perera  wrote:
>>
>>> Looks like you are running MB on the 32-bit JDK. Can you try with 64-bit
>>> JDK?
>>>
>>> On Mon, Dec 21, 2015 at 5:08 PM, Nadeesha Meegoda 
>>> wrote:
>>>
 Hi Yasassri,

 Thanks. I will investigate on this more. The other products in same
 directory are starting without any issue. That's why I raised the concern.

 Regards,
 Nadeesha

 On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake 
 wrote:

> Hi,
>
> We were able to successfully start MB without any issue with Java 1.8
> and with Java 1.7 in windows environment. I tested with your exact java
> version as well (1.7.0_79). I believe you haven't set your environment
> variables properly. As per your error it says "The system cannot find
> the file specified.".  I think this is self explanatory.
>
> Please compare with the following logs and check whats missing.
>
> TID: [] [] [2015-12-21 10:23:49,834]  WARN
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
> determine dialect of the StAX implementation at
> bundleresource://13.fwk2427473/
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
> TID: [] [] [2015-12-21 10:23:49,834]  WARN
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
> determine dialect of the StAX implementation at
> bundleresource://13.fwk2427473/
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
> TID: [] [] [2015-12-21 10:23:49,756]  INFO
> {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting 
> BundleContext
> in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Windows Server 2012 R2 6.3, amd64
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> C:\Program Files\Java\jdk1.7.0_79\jre
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> Administrator, en-US, UTC
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,694]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  
> The
> running OS : Windows Server 2012 R2 is not a tested Operating System for
> running WSO2 Carbon
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
> TID: [-1234] [] [2015-12-21 10:23:51,709]  WARN
> 

[Dev] WSO2 Committers += Hasanthi Purnima Dissanayake

[Johann Nallathamby]

Hi All,

It's my pleasure to announce Hasanthi Purnima Dissanayake as a WSO2
Committer. Hasanthi has been a valuable contributor for WSO2 Identity
Server product, and in recognition of her contribution to WSO2, she
has been voted as a WSO2 Committer.

Hasanthi, congratulations and keep up the good work!

Thanks & Regards.

-- 

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.1.0 RC2

[Isura Karunaratne]

Hi Devs,

I tested following functionality in both super tenant and tenant mode


** Identity Management*


   1. Set security questions for tenant
   2. Set security questions for user
   3. Account Recovery - using notificaiton
   4. Account Recovery -using security questions
   5. Ask Password
   6. Account locking from wrong credentials
   7. Self User Registraiton
   8. User Identity Management Admin Service - lockUserAccount
   9. User Identity Management Admin Service - unlockUserAccount
   10. User Identity Management Admin Service - resetUserPassword
   11. User Identity Management Admin Service - changeUserPassword
   12. Password Patterns



So here is my vote.
[x] -Stable - go ahead and release

Thanks
Isura

On Tue, Dec 22, 2015 at 5:24 AM, Prabath Siriwardana 
wrote:

> Smoke tested local account mapping feature with..
>
> 1. Multiple tenants
> 2. Multiple user stores (LDAP and MySQL)
> 3. Add/Delete user operations
> 4. Activate/Deactivate tenant operations
> 5. Activate/Deactivate user store operations
>
> All working fine except one minor issue (
> https://wso2.org/jira/browse/IDENTITY-4245 - reported as L3).
>
> Will test further on other features and update the status..
>
> Thanks & regards,
> -Prabath
>
> On Mon, Dec 21, 2015 at 4:59 AM, Hasintha Indrajee 
> wrote:
>
>> Hi Devs,
>>
>> This is the second release candidate of WSO2 Identity Server 5.1.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12586
>>
>> Please download, test and vote.
>>
>> Source & binary distribution files:
>> https://github.com/wso2/product-is/releases/tag/v5.1.0-rc2
>>
>> Maven staging repo:
>> http://maven.wso2.org/nexus/content/repositories/orgwso2is-218/
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-is/tree/v5.1.0-rc2
>>
>>
>> [ ]  Stable - go ahead and release
>> [ ]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>> WSO2 Identity Server Team.
>>
>> --
>> Hasintha Indrajee
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 771892453
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Twitter : @prabath
> LinkedIn : http://www.linkedin.com/in/prabathsiriwardena
>
> Mobile : +1 650 625 7950
>
> http://blog.facilelogin.com
> http://blog.api-security.org
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isura Dilhara Karunaratne
Senior Software Engineer

Mob +94 772 254 810
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC4

[Nethaji Chandrasiri]

Hi,

I've tested and verified all samples.

[x] Stable - go ahead and release.

Thanks

On Tue, Dec 22, 2015 at 11:24 AM, Ashen Weerathunga  wrote:

> Hi all,
>
> I've tested the following,
>
>- Verified both v10 APIs and v11 APIs.
>- UI and both default and tuned samples of Anomaly detection
>algorithms.
>
> Works fine. I didn't encounter any issues.
>
> [x] Stable - go ahead and release
>
> Thanks and Regards,
> Ashen
>
> On Tue, Dec 22, 2015 at 12:11 AM, Maheshakya Wijewardena <
> mahesha...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the 4th Release Candidate of WSO2 Machine Learner 1.1.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12600
>>
>> Please download, test and vote. Vote will be open for 72 hours or as
>> longer as needed.
>>
>> *Binary distribution files:*
>>
>> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/wso2ml-1.1.0.zip
>>
>> *P2 repository*:
>>
>> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/p2-repo.zip
>>
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2ml-224/
>> 
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-ml/tree/v1.1.0-rc4
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you,
>> Machine Learner Team
>>
>> --
>> Pruthuvi Maheshakya Wijewardena
>> mahesha...@wso2.com
>> +94711228855
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94 716042995 <94716042995>
> LinkedIn:
> *http://lk.linkedin.com/in/ashenweerathunga
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nethaji Chandrasiri*
*Software Engineering* *Intern; WSO2, Inc.; http://wso2.com
*
Mobile : +94 (0) 779171059 <%2B94%20%280%29%20778%20800570>
Email  : neth...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Chamin Dias

[Dinesh J Weerakkody]

Congratulations..

Thanks

*Dinesh J. Weerakkody*
Software Engineer
WSO2 Inc.
lean | enterprise | middleware
M : +94 727 868676 | E : dine...@wso2.com | W : www.wso2.com

On Mon, Dec 21, 2015 at 2:26 PM, Nuwan Dias  wrote:

> Hi,
>
> It is with great pleasure we welcome Chamin Dias as a WSO2 Committer. @
> Chamin, congratulations and keep up the good work!
>
> Thanks,
> NuwanD.
>
> --
> 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
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Hasitha Hiranya]

Is this worth mentioning in docs anyway?

On Tue, Dec 22, 2015 at 11:21 AM, Nadeesha Meegoda 
wrote:

> Hi all,
>
> Thanks for figuring this out.
>
> Regards,
> Nadeesha
>
> On Tue, Dec 22, 2015 at 11:19 AM, Isuru Perera  wrote:
>
>> Yes! The 32-bit JVM cannot allocate enough memory for the MB.
>>
>> On Tue, Dec 22, 2015 at 11:14 AM, Jason De Silva  wrote:
>>
>>> Hi Nadeesha,
>>>
>>> As Isuru pointed since you have tried it out with 32 bit JDK which will
>>> not be able to allocate 2 gb memory [1] whereas MB needs 2 gb memory [2]
>>> which was the cause for the product to not start on 32 bit JDK.
>>>
>>> [1]
>>> http://www.oracle.com/technetwork/java/hotspotfaq-138619.html#gc_heap_32bit
>>> [2] https://docs.wso2.com/display/MB300/Installation+Prerequisites
>>>
>>> Regards,
>>>
>>>
>>> On Mon, Dec 21, 2015 at 9:20 PM, Nadeesha Meegoda 
>>> wrote:
>>>
 Hi Isuru,

 Yes I am running MB on the 32-bit JDK. I have installed both 32 bit and
 64 bit JDK in my machine. However other products seems to start without any
 error in both 32bit and 64bit JDK. I also checked MB in 64bit JDK now. MB
 starts fine with that.


 Thanks,
 Nadeesha

 On Mon, Dec 21, 2015 at 6:13 PM, Isuru Perera  wrote:

> Looks like you are running MB on the 32-bit JDK. Can you try with
> 64-bit JDK?
>
> On Mon, Dec 21, 2015 at 5:08 PM, Nadeesha Meegoda 
> wrote:
>
>> Hi Yasassri,
>>
>> Thanks. I will investigate on this more. The other products in same
>> directory are starting without any issue. That's why I raised the 
>> concern.
>>
>> Regards,
>> Nadeesha
>>
>> On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake <
>> yasas...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We were able to successfully start MB without any issue with Java
>>> 1.8 and with Java 1.7 in windows environment. I tested with your exact 
>>> java
>>> version as well (1.7.0_79). I believe you haven't set your environment
>>> variables properly. As per your error it says "The system cannot
>>> find the file specified.".  I think this is self explanatory.
>>>
>>> Please compare with the following logs and check whats missing.
>>>
>>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>>> determine dialect of the StAX implementation at
>>> bundleresource://13.fwk2427473/
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>>> determine dialect of the StAX implementation at
>>> bundleresource://13.fwk2427473/
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>>> TID: [] [] [2015-12-21 10:23:49,756]  INFO
>>> {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting 
>>> BundleContext
>>> in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>>> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System 
>>> :
>>> Windows Server 2012 R2 6.3, amd64
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home
>>> :
>>> C:\Program Files\Java\jdk1.7.0_79\jre
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version 
>>> :
>>> 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  
>>> :
>>> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  
>>> :
>>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir
>>> :
>>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> 

Re: [Dev] [DEV][Urgent] Getting error while generating access tokens with openid scope

[Dumidu Handakumbura]

Created a jira to track the issue.

https://wso2.org/jira/browse/APIMANAGER-4430

On Mon, Dec 21, 2015 at 3:22 PM, Sanjeewa Malalgoda 
wrote:

> ACK.
>
> Thanks,
> sanjeewa.
>
> On Mon, Dec 21, 2015 at 3:18 PM, Deependra Ariyadewa 
> wrote:
>
>>
>>
>> On Mon, Dec 21, 2015 at 3:09 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi,
>>> Ideally this should be fixed in kernel as we mentioned above. But we
>>> have fixed this and released carbon-identity 5.0.7
>>>
>>> @Product teams,
>>> Please update your carbon-identity version to 5.0.7
>>>
>>
>> ACK
>>
>>>
>>> Thanks,
>>> Maduranga.
>>>
>>> On Mon, Dec 21, 2015 at 11:58 AM, Sanjeewa Malalgoda 
>>> wrote:
>>>


 On Mon, Dec 21, 2015 at 11:48 AM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi Sanjeewa,
>
> We tried to reproduce the issue with IS 5.1.0 RC1 and we couldn't
> reproduce.
>
> Further we investigated and observed that the problem seems to be in
> KeyStoreManager in kernel [1]. In KeyStoreManager, primaryKeyStore is
> initialized from getPrimaryKeyStore() [2]. For IS getPrimaryKeyStore() is
> called from one of our components [3] and so primaryKeyStore is getting
> initialized. But for APIM this is not happening. As a workaround you can 
> do
> the same from one of your components.
>
> [1]
> https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java
> [2]
> https://github.com/wso2/carbon-kernel/blob/v4.4.3/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/util/KeyStoreManager.java#L328
> [3]
> https://github.com/wso2/carbon-identity/blob/v5.0.5/components/sts/org.wso2.carbon.sts/src/main/java/org/wso2/carbon/sts/STSDeploymentInterceptor.java#L157
>

 If this key store initializing is required for OAuth endpoint and OAuth
 service why don't we initialize from oauth components?
 As i understood this issue is not happening in IS because some other
 component initialize this instead of OAuth endpoint or service.
 Let say we fixed it in our components(APIM), but still if someone
 installed OAuth features into kernal or any other server they still see
 same issue.
 So i think its better to add this to OAuth component itself.

>
> Thanks,
> Maduranga.
>
> On Mon, Dec 21, 2015 at 10:03 AM, Sanjeewa Malalgoda <
> sanje...@wso2.com> wrote:
>
>> Hi Team,
>> While requesting access tokens with openid scope(see curl request[1])
>> i'm getting following error[2].
>> I tested this with carbon-identity 5.0.5 based AM build and i don't
>> think 5.0.6 do not have changes related to this use case.
>> I tested this with another white listed scopes to confirm this happen
>> due to white listed scopes or specific to openId.
>> We were able to get access tokens for normal white listed scopes but
>> not for openid scope.
>> Generate access tokens with openid scope is very common use case for
>> all API manager clients.
>> Did i missed anything here or we need to fix it (since this is NPE i
>> think we should fix this)?
>>
>> [1]curl -k -d
>> "grant_type=password=admin=admin=openid" -H
>> "Authorization: Basic
>> VUFmMWFmZ3VCTzFaVE5QY0k2d2ZYbXNIQ1hVYTpUWURlT01nQjc3ME5DQ3RraTBZR3BNUVdQT2Nh"
>> https://10.100.1.65:8243/token
>>
>> [2][2015-12-21 09:46:53,812] ERROR - OAuth2Service Error occurred
>> while issuing the access token for Client ID :
>> UAf1afguBO1ZTNPcI6wfXmsHCXUa, User ID admin, Scope : [openid] and Grant
>> Type : password
>> org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error while
>> obtaining private key for super tenant
>> at
>> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWTWithRSA(DefaultIDTokenBuilder.java:351)
>> at
>> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.signJWT(DefaultIDTokenBuilder.java:514)
>> at
>> org.wso2.carbon.identity.openidconnect.DefaultIDTokenBuilder.buildIDToken(DefaultIDTokenBuilder.java:237)
>> at
>> org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:224)
>> at
>> org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:196)
>> at
>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:245)
>> at
>> org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:111)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at 

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Jason De Silva]

Hi Nadeesha,

As Isuru pointed since you have tried it out with 32 bit JDK which will not
be able to allocate 2 gb memory [1] whereas MB needs 2 gb memory [2] which
was the cause for the product to not start on 32 bit JDK.

[1]
http://www.oracle.com/technetwork/java/hotspotfaq-138619.html#gc_heap_32bit
[2] https://docs.wso2.com/display/MB300/Installation+Prerequisites

Regards,


On Mon, Dec 21, 2015 at 9:20 PM, Nadeesha Meegoda 
wrote:

> Hi Isuru,
>
> Yes I am running MB on the 32-bit JDK. I have installed both 32 bit and 64
> bit JDK in my machine. However other products seems to start without any
> error in both 32bit and 64bit JDK. I also checked MB in 64bit JDK now. MB
> starts fine with that.
>
>
> Thanks,
> Nadeesha
>
> On Mon, Dec 21, 2015 at 6:13 PM, Isuru Perera  wrote:
>
>> Looks like you are running MB on the 32-bit JDK. Can you try with 64-bit
>> JDK?
>>
>> On Mon, Dec 21, 2015 at 5:08 PM, Nadeesha Meegoda 
>> wrote:
>>
>>> Hi Yasassri,
>>>
>>> Thanks. I will investigate on this more. The other products in same
>>> directory are starting without any issue. That's why I raised the concern.
>>>
>>> Regards,
>>> Nadeesha
>>>
>>> On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake 
>>> wrote:
>>>
 Hi,

 We were able to successfully start MB without any issue with Java 1.8
 and with Java 1.7 in windows environment. I tested with your exact java
 version as well (1.7.0_79). I believe you haven't set your environment
 variables properly. As per your error it says "The system cannot find
 the file specified.".  I think this is self explanatory.

 Please compare with the following logs and check whats missing.

 TID: [] [] [2015-12-21 10:23:49,834]  WARN
 {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
 determine dialect of the StAX implementation at
 bundleresource://13.fwk2427473/
 {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
 TID: [] [] [2015-12-21 10:23:49,834]  WARN
 {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
 determine dialect of the StAX implementation at
 bundleresource://13.fwk2427473/
 {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
 TID: [] [] [2015-12-21 10:23:49,756]  INFO
 {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting BundleContext
 in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
 Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
 Windows Server 2012 R2 6.3, amd64
 {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
 C:\Program Files\Java\jdk1.7.0_79\jre
 {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
 Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
 {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
 C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
 {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
 C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
 {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
 Administrator, en-US, UTC
 {org.wso2.carbon.core.internal.CarbonCoreActivator}
 TID: [-1234] [] [2015-12-21 10:23:51,694]  WARN
 {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
 running OS : Windows Server 2012 R2 is not a tested Operating System for
 running WSO2 Carbon
 {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
 TID: [-1234] [] [2015-12-21 10:23:51,709]  WARN
 {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
  Carbon is configured to use the default keystore (wso2carbon.jks). To
 maximize security when deploying to a production environment, configure a
 new keystore with a unique password in the production 

Re: [Dev] [API Manager] AsyncDataPublisher connection failed

[Rukshan Premathunga]

Hi Dinusha,

Seems DAS not started or working on expected ports. Can you try to
reconfigure DAS and APIM again?

Thanks.

On Tue, Dec 22, 2015 at 10:41 AM, Dinusha Dissanayake 
wrote:

> Hi all,
>
> I've configured APIM with DAS to study statistics publishing process as
> follows.
>
> Event Receiver Configurations
> url group : tcp://localhost:7612
>
> Data Analyzer Configurations (with offset 1 for DAS)
> URL : https://localhost:9444
>
> When I invoke an API in the store, the console logs the following message:
>
> "[2015-12-22 10:32:12,820] ERROR - add:jag Error occurred while deploying
> artifacts (Cause:org.apache.axis2.AxisFault: Connection refused)
> [2015-12-22 10:32:26,308] ERROR - AsyncDataPublisher Reconnection failed
> for for tcp://localhost:7612"
>
> Then I again tried to change the analytic configurations in the
> admin-dashboard. But it pops the message "
> Error occurred while deploying artifacts
> (Cause:org.apache.axis2.AxisFault: Connection refused)
> "
>
> Can someone please explain the reason for this?
> --
> Regards,
> *Dinusha Dissanayake,*
> Software Engineering intern,
> WSO2 Inc
>



-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Nadeesha Meegoda]

Hi all,

Thanks for figuring this out.

Regards,
Nadeesha

On Tue, Dec 22, 2015 at 11:19 AM, Isuru Perera  wrote:

> Yes! The 32-bit JVM cannot allocate enough memory for the MB.
>
> On Tue, Dec 22, 2015 at 11:14 AM, Jason De Silva  wrote:
>
>> Hi Nadeesha,
>>
>> As Isuru pointed since you have tried it out with 32 bit JDK which will
>> not be able to allocate 2 gb memory [1] whereas MB needs 2 gb memory [2]
>> which was the cause for the product to not start on 32 bit JDK.
>>
>> [1]
>> http://www.oracle.com/technetwork/java/hotspotfaq-138619.html#gc_heap_32bit
>> [2] https://docs.wso2.com/display/MB300/Installation+Prerequisites
>>
>> Regards,
>>
>>
>> On Mon, Dec 21, 2015 at 9:20 PM, Nadeesha Meegoda 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Yes I am running MB on the 32-bit JDK. I have installed both 32 bit and
>>> 64 bit JDK in my machine. However other products seems to start without any
>>> error in both 32bit and 64bit JDK. I also checked MB in 64bit JDK now. MB
>>> starts fine with that.
>>>
>>>
>>> Thanks,
>>> Nadeesha
>>>
>>> On Mon, Dec 21, 2015 at 6:13 PM, Isuru Perera  wrote:
>>>
 Looks like you are running MB on the 32-bit JDK. Can you try with
 64-bit JDK?

 On Mon, Dec 21, 2015 at 5:08 PM, Nadeesha Meegoda 
 wrote:

> Hi Yasassri,
>
> Thanks. I will investigate on this more. The other products in same
> directory are starting without any issue. That's why I raised the concern.
>
> Regards,
> Nadeesha
>
> On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake  > wrote:
>
>> Hi,
>>
>> We were able to successfully start MB without any issue with Java 1.8
>> and with Java 1.7 in windows environment. I tested with your exact java
>> version as well (1.7.0_79). I believe you haven't set your environment
>> variables properly. As per your error it says "The system cannot
>> find the file specified.".  I think this is self explanatory.
>>
>> Please compare with the following logs and check whats missing.
>>
>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>> determine dialect of the StAX implementation at
>> bundleresource://13.fwk2427473/
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>> determine dialect of the StAX implementation at
>> bundleresource://13.fwk2427473/
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>> TID: [] [] [2015-12-21 10:23:49,756]  INFO
>> {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting 
>> BundleContext
>> in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Windows Server 2012 R2 6.3, amd64
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> C:\Program Files\Java\jdk1.7.0_79\jre
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>> Administrator, en-US, UTC
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,694]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  
>> The
>> running 

Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC4

[Ashen Weerathunga]

Hi all,

I've tested the following,

   - Verified both v10 APIs and v11 APIs.
   - UI and both default and tuned samples of Anomaly detection algorithms.

Works fine. I didn't encounter any issues.

[x] Stable - go ahead and release

Thanks and Regards,
Ashen

On Tue, Dec 22, 2015 at 12:11 AM, Maheshakya Wijewardena <
mahesha...@wso2.com> wrote:

> Hi Devs,
>
> This is the 4th Release Candidate of WSO2 Machine Learner 1.1.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12600
>
> Please download, test and vote. Vote will be open for 72 hours or as
> longer as needed.
>
> *Binary distribution files:*
>
> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/wso2ml-1.1.0.zip
>
> *P2 repository*:
> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/p2-repo.zip
>
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2ml-224/
> 
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-ml/tree/v1.1.0-rc4
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you,
> Machine Learner Team
>
> --
> Pruthuvi Maheshakya Wijewardena
> mahesha...@wso2.com
> +94711228855
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ashen Weerathunga*
Software Engineer - Intern
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: +94 716042995 <94716042995>
LinkedIn:
*http://lk.linkedin.com/in/ashenweerathunga
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Machine Learner 1.1.0 RC4

[Fazlan Nazeem]

Hi,

There is an issue in Publish button in compare models section. The popup
does not work.

[x] Broken - Do not release

On Tue, Dec 22, 2015 at 12:19 PM, Nethaji Chandrasiri 
wrote:

> Hi,
>
> I've tested and verified all samples.
>
> [x] Stable - go ahead and release.
>
> Thanks
>
> On Tue, Dec 22, 2015 at 11:24 AM, Ashen Weerathunga 
> wrote:
>
>> Hi all,
>>
>> I've tested the following,
>>
>>- Verified both v10 APIs and v11 APIs.
>>- UI and both default and tuned samples of Anomaly detection
>>algorithms.
>>
>> Works fine. I didn't encounter any issues.
>>
>> [x] Stable - go ahead and release
>>
>> Thanks and Regards,
>> Ashen
>>
>> On Tue, Dec 22, 2015 at 12:11 AM, Maheshakya Wijewardena <
>> mahesha...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 4th Release Candidate of WSO2 Machine Learner 1.1.0.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12600
>>>
>>> Please download, test and vote. Vote will be open for 72 hours or as
>>> longer as needed.
>>>
>>> *Binary distribution files:*
>>>
>>> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/wso2ml-1.1.0.zip
>>>
>>> *P2 repository*:
>>>
>>> https://github.com/wso2/product-ml/releases/download/v1.1.0-rc4/p2-repo.zip
>>>
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2ml-224/
>>> 
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/product-ml/tree/v1.1.0-rc4
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you,
>>> Machine Learner Team
>>>
>>> --
>>> Pruthuvi Maheshakya Wijewardena
>>> mahesha...@wso2.com
>>> +94711228855
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Ashen Weerathunga*
>> Software Engineer - Intern
>> WSO2 Inc.: http://wso2.com
>> lean.enterprise.middleware
>>
>> Email: as...@wso2.com
>> Mobile: +94 716042995 <94716042995>
>> LinkedIn:
>> *http://lk.linkedin.com/in/ashenweerathunga
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Nethaji Chandrasiri*
> *Software Engineering* *Intern; WSO2, Inc.; http://wso2.com
> *
> Mobile : +94 (0) 779171059 <%2B94%20%280%29%20778%20800570>
> Email  : neth...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Chamin Dias

[Nuwan Dias]

Hi,

It is with great pleasure we welcome Chamin Dias as a WSO2 Committer. @
Chamin, congratulations and keep up the good work!

Thanks,
NuwanD.

-- 
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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 5.0.0 RC2

[Kishanthan Thangarajah]

Thank you all.

We are closing this vote and this vote passes with 10 +1 and 0 -1 votes. We
will proceed with publishing the maven artifacts to nexus.

On Mon, Dec 21, 2015 at 2:46 PM, Sameera Jayasoma  wrote:

> Hi Folks,
>
> Verified the directory structure and recent changes the scripts and
> configuration files.
> Tested Startup Order Resolver.
>
> [x] Stable - go ahead and release.
>
> Regards,
> Sameera
>
> On Mon, Dec 21, 2015 at 10:53 AM, Dinusha Boteju 
> wrote:
>
>> Hi all,
>>
>> Started the kernel using openjdk 8.
>> Started the server in windows 7.
>>
>> Tested the Logging framework in both scenarios. No issues found.
>>
>> [x] Stable - go ahead and release.
>>
>> Best regards,
>> Dinusha
>>
>>
>> On Mon, Dec 21, 2015 at 10:07 AM, Samiyuru Senarathne 
>> wrote:
>>
>>> Tested with MSS. No issues were found.
>>>
>>> [x] Stable - go ahead and release.
>>>
>>> Best Regards,
>>> Samiyuru
>>>
>>> On Mon, Dec 21, 2015 at 1:08 AM, Kalpa Welivitigoda 
>>> wrote:
>>>
 Hi all,

 I tested the logging framework and jar-to bundle tool. No issues found.

 [x] Stable - go ahead and release

 On Sun, Dec 20, 2015 at 11:30 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> Tested both startup order resolver functionality and artifact
> deployment engine functionality. No issues encountered.
>
> [x] Stable - go ahead and release.
>
> Thanks,
>
> On Sun, Dec 20, 2015 at 1:22 PM, Nipuni Perera 
> wrote:
>
>> Hi all,
>>
>> I have tested the launcher framework (loading launcher configurations
>> from launcher.properties) with logging. No issues found except[1] which 
>> is
>> already reported and will be fixed in 5.1.0.
>>
>> [1] https://wso2.org/jira/browse/CARBON-15745
>>
>> [x] Stable - go ahead and release
>>
>> Thanks,
>> Nipuni
>>
>> On Sun, Dec 20, 2015 at 12:34 PM, Chiranga Alwis 
>> wrote:
>>
>>> Hi,
>>>
>>> I tested the following aspects:
>>> - jar-to-OSGi-bundle converter
>>> - converted OSGi bundles in dropins folder being  successfully
>>> deployed
>>>
>>> No issues discovered.
>>>
>>> [x] Stable - go ahead and release.
>>>
>>> On Sun, Dec 20, 2015 at 11:27 AM, Senduran Balasubramaniyam <
>>> sendu...@wso2.com> wrote:
>>>
 Hi all,

 I have tested product-gw's basic functionality with this release
 candidate.
 No issues found.

 [x] Stable - go ahead and release

 Regards
 Senduran

 On Sun, Dec 20, 2015 at 10:01 AM, Aruna Karunarathna <
 ar...@wso2.com> wrote:

> I've tested, the following features
>
> 1. Logging framework
> 2. Transport Management
> 3. Jar to bundle conversion
> 4. Dropins bundle deployment
>
> [x] Stable - go ahead and release
>
> Regards,
> Aruna
>
> On Sat, Dec 19, 2015 at 11:50 PM, Manuri Amaya Perera <
> manu...@wso2.com> wrote:
>
>> Hi,
>>
>> I created projects using the available archetypes in staging
>> repository and built and installed via dropins and osgi console and 
>> tested
>> the expected functionality with the kernel 5.0.0 RC2 pack.
>>
>> [x] Stable - go ahead and release.
>>
>> Thank you.
>>
>> On Fri, Dec 18, 2015 at 5:15 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd Release Candidate of WSO2 Carbon Kernel 5.0.0.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12581
>>>
>>> Please download and test your products with kernel 5.0.0 RC2
>>> and vote.
>>>
>>> *​Source and binary distribution files:*
>>>
>>> https://github.com/wso2/carbon-kernel/releases/download/v5.0.0-RC2/wso2carbon-kernel-5.0.0-rc2.zip
>>>
>>> *Maven staging repository:*
>>>
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-210/
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/carbon-kernel/releases/tag/v5.0.0-RC2
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you,
>>> Carbon Team
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Associate Technical Lead,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - 

[Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Nadeesha Meegoda]

Hi all,

Came across the $subject. [1] is the exception I get when starting the
server.

Also did a diff check with IS 5.1.0 wso2server.bat file compared with MB
3.0.0 wso2server.bat file. Please find the mismatches

*MB 3.0.0 *

set CMD_LINE_ARGS=-Xbootclasspath/a:%CARBON_XBOOTCLASSPATH% -Xms1024m
-Xmx2048m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath="%CARBON_HOME%\repository\logs\heap-dump.hprof"
-Dcom.sun.management.jmxremote -classpath %CARBON_CLASSPATH% %JAVA_OPTS%
-Djava.endorsed.dirs=%JAVA_ENDORSED% -DandesConfig=broker.xml
-Dcarbon.registry.root=/ -Dcarbon.home="%CARBON_HOME%"
-Dwso2.server.standalone=true -Djava.command="%JAVA_HOME%\bin\java"
-Djava.opts="%JAVA_OPTS%" -Djava.io.tmpdir="%CARBON_HOME%\tmp"
-Dcatalina.base="%CARBON_HOME%\lib\tomcat"
-Dwso2.carbon.xml=%CARBON_HOME%\repository\conf\carbon.xml
-Dwso2.registry.xml="%CARBON_HOME%\repository\conf\registry.xml"
-Dwso2.user.mgt.xml="%CARBON_HOME%\repository\conf\user-mgt.xml"
-Dwso2.transports.xml="%CARBON_HOME%\repository\conf\mgt-transports.xml"
-Djava.util.logging.config.file="%CARBON_HOME%\repository\conf\log4j.properties"
-Dcarbon.config.dir.path="%CARBON_HOME%\repository\conf"
-Dcarbon.logs.path="%CARBON_HOME%\repository\logs"
-Dcomponents.repo="%CARBON_HOME%\repository\components"
-Dconf.location="%CARBON_HOME%\repository\conf"
-Dcom.atomikos.icatch.file="%CARBON_HOME%\lib\transactions.properties"
-Dcom.atomikos.icatch.hide_init_file_path="true"
-Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
-Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
-Dcom.sun.jndi.ldap.connect.pool.authentication=simple
-Dcom.sun.jndi.ldap.connect.pool.timeout=3000
-Dorg.terracotta.quartz.skipUpdateCheck=true
-Dcarbon.classpath=%CARBON_CLASSPATH% -Dfile.encoding=UTF8

*IS 5.1.0*

set CMD_LINE_ARGS=-Xbootclasspath/a:%CARBON_XBOOTCLASSPATH% -Xms256m
-Xmx1024m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath="%CARBON_HOME%\repository\logs\heap-dump.hprof"
-Dcom.sun.management.jmxremote -classpath %CARBON_CLASSPATH% %JAVA_OPTS%
-Djava.endorsed.dirs=%JAVA_ENDORSED% -Dcarbon.registry.root=/
-Dcarbon.home="%CARBON_HOME%" -Dwso2.server.standalone=true
-Djava.command="%JAVA_HOME%\bin\java" -Djava.opts="%JAVA_OPTS%"
-Djava.io.tmpdir="%CARBON_HOME%\tmp"
-Dcatalina.base="%CARBON_HOME%\lib\tomcat"
-Dwso2.carbon.xml=%CARBON_HOME%\repository\conf\carbon.xml
-Dwso2.registry.xml="%CARBON_HOME%\repository\conf\registry.xml"
-Dwso2.user.mgt.xml="%CARBON_HOME%\repository\conf\user-mgt.xml"
-Dwso2.transports.xml="%CARBON_HOME%\repository\conf\mgt-transports.xml"
-Djava.util.logging.config.file="%CARBON_HOME%\repository\conf\etc\logging-bridge.properties"
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Dcarbon.config.dir.path="%CARBON_HOME%\repository\conf"
-Dcomponents.repo="%CARBON_HOME%\repository\components"
-Dconf.location="%CARBON_HOME%\repository\conf"
-Dcom.atomikos.icatch.file="%CARBON_HOME%\lib\transactions.properties"
-Dcom.atomikos.icatch.hide_init_file_path="true"
-Dorg.apache.jasper.compiler.Parser.STRICT_QUOTE_ESCAPING=false
-Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
-Dcom.sun.jndi.ldap.connect.pool.authentication=simple
-Dcom.sun.jndi.ldap.connect.pool.timeout=3000
-Dorg.terracotta.quartz.skipUpdateCheck=true
-Dcarbon.classpath=%CARBON_CLASSPATH% -Dfile.encoding=UTF8

[1]

The system cannot find the file specified. JAVA_HOME environment variable
is set to C:\Program Files (x86)\Java\jdk1.7.0_79 CARBON_HOME environment
variable is set to D:\Support\WSO2MB~1.0\bin\.. Error occurred during
initialization of VM Could not reserve enough space for object heap Error:
Could not create the Java Virtual Machine. Error: A fatal exception has
occurred. Program will exit.


Thanks,
Nadeesha
-- 
*Nadeesha Meegoda*
Software Engineer - QA
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
email : nadees...@wso2.com
mobile: +94783639540
<%2B94%2077%202273555>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [EMM200] Performance & Load Testing

[Dileesha Rajapakse]

1. Install Jmeter
*sudo apt-get install jmeter*

2. Replace the '*/usr/share/jmeter/lib/*' directory with the 'lib'
directory which could be downloaded from below link. (This file contains
all the necessary library files needed to run test scripts)
https://drive.google.com/file/d/0B1raQ3vGHU8uMjlhZU1EVzR0VGc/view?usp=sharing

3. Download and extract the scripts file
https://drive.google.com/file/d/0B1raQ3vGHU8uaXhULTZzQUQwamc/view?usp=sharing

The above '*EMM200LoadTests.zip*' file contains a total of 5 files.

   - *emm_devices.csv *- Contains information about 50 unique devices
   - *EnrollDevices.jmx* - Enrolls Devices
   - *AddOperations.jmx* - Adds Operations to enrolled devices (2
   operations per each device)
   - *GetPendingOperations.jmx* - Hits the '/mdm-android-agent/operation'
   endpoint which is the most heavily used API of the EMM
   - *MDM2LoadTesting.jmx* - This script contains a sample Jmeter test plan
   which has several additional useful test ThreadGroups which can be used to
   simulate scenarios such as Operation Execution, Policy Creation and Policy
   Monitoring

*[Important]* Make sure the 'emm_devices.csv' file and the script files are
in the same folder.
4. Specify these parameters when running test scripts

*JHOST* --> Server Host
*JPORT* --> Server Port
*JUSERS* --> Number of Users (Concurrency)
*JLOOPCOUNT* --> Number of Iterations per User


Device Enrollment

jmeter -n -JHOST= -JPORT=
-JUSERS= -JLOOPCOUNT= -t EnrollDevices.jmx -l
errors.log


   - To enroll a '*n*' number of devices set the parameters as
follows, *(-JUSERS)*(-JLOOPCOUNT)
   = n*


Add Operations

jmeter -n -JHOST= -JPORT=
-JUSERS= -JLOOPCOUNT= -t AddOperations.jmx -l
errors.log


Get Pending Operations

jmeter -n -JHOST= -JPORT=
-JUSERS= -JLOOPCOUNT= -t
GetPendingOperations.jmx -l errors.log


-- 
Dileesha Rajapakse
*Intern - Engineering*
Mobile : +94 (0) 772 555 933
Tel  : +94 112 741 505
dilee...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM200] Performance & Load Testing

[Prabath Abeysekera]

One of the performance hits identified while analysing the JFR dumps taken
out of EMM 2.0 set-ups is the time taken for token validation. The nature
of the aforesaid token validation is that, a service stub is used to invoke
an admin service deployed as part of EMM's Key Manager profile for token
validation and the stub instances are created per-request to avoid the
impact that is likely to be caused by stubs being less thread-safe. This
pattern proved to be very expensive as it was quite evident that the stub
instantiation is expensive. As a fix, a pool of stubs was introduced to
mitigate the above explained impact with appropriate means to cleanup
metadata just before the pooled stubs are returned to the pool. This helped
doubling the numbers obtained for a properly distributed set-up of EMM 2.0.
Please refer [1] for the source code.

[1]
https://github.com/wso2/carbon-device-mgt/commit/11957f1e478f884cc1f100debb4bbc8290c0901c

Cheers,
Prabath

On Mon, Dec 21, 2015 at 2:44 PM, Dileesha Rajapakse 
wrote:

> 1. Install Jmeter
> *sudo apt-get install jmeter*
>
> 2. Replace the '*/usr/share/jmeter/lib/*' directory with the 'lib'
> directory which could be downloaded from below link. (This file contains
> all the necessary library files needed to run test scripts)
>
> https://drive.google.com/file/d/0B1raQ3vGHU8uMjlhZU1EVzR0VGc/view?usp=sharing
>
> 3. Download and extract the scripts file
>
> https://drive.google.com/file/d/0B1raQ3vGHU8uaXhULTZzQUQwamc/view?usp=sharing
>
> The above '*EMM200LoadTests.zip*' file contains a total of 5 files.
>
>- *emm_devices.csv *- Contains information about 50 unique devices
>- *EnrollDevices.jmx* - Enrolls Devices
>- *AddOperations.jmx* - Adds Operations to enrolled devices (2
>operations per each device)
>- *GetPendingOperations.jmx* - Hits the '/mdm-android-agent/operation'
>endpoint which is the most heavily used API of the EMM
>- *MDM2LoadTesting.jmx* - This script contains a sample Jmeter test
>plan which has several additional useful test ThreadGroups which can be
>used to simulate scenarios such as Operation Execution, Policy Creation and
>Policy Monitoring
>
> *[Important]* Make sure the 'emm_devices.csv' file and the script files
> are in the same folder.
> 4. Specify these parameters when running test scripts
>
> *JHOST* --> Server Host
> *JPORT* --> Server Port
> *JUSERS* --> Number of Users (Concurrency)
> *JLOOPCOUNT* --> Number of Iterations per User
>
>
> Device Enrollment
>
> jmeter -n -JHOST= -JPORT=
> -JUSERS= -JLOOPCOUNT= -t EnrollDevices.jmx -l
> errors.log
>
>
>- To enroll a '*n*' number of devices set the parameters as follows, 
> *(-JUSERS)*(-JLOOPCOUNT)
>= n*
>
>
> Add Operations
>
> jmeter -n -JHOST= -JPORT=
> -JUSERS= -JLOOPCOUNT= -t AddOperations.jmx -l
> errors.log
>
>
> Get Pending Operations
>
> jmeter -n -JHOST= -JPORT=
> -JUSERS= -JLOOPCOUNT= -t
> GetPendingOperations.jmx -l errors.log
>
>
> --
> Dileesha Rajapakse
> *Intern - Engineering*
> Mobile : +94 (0) 772 555 933
> Tel  : +94 112 741 505
> dilee...@wso2.com
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [EMM200] Performance & Load Testing

[Sumedha Rubasinghe]

Prabath,
API Manager has the same setup and it uses a Thrift client for the same (in
the place of using a stub for admin service)
Can't we use the same Thrift server/client pattern?We had a similar
situation in BAM data publisher. There also we used Thrift for performance
reasons.

Stubs are known to have performance problems for high concurrent scenarios
due to marshalling/un-marshalling.



On Mon, Dec 21, 2015 at 3:20 PM, Prabath Abeysekera 
wrote:

> One of the performance hits identified while analysing the JFR dumps taken
> out of EMM 2.0 set-ups is the time taken for token validation. The nature
> of the aforesaid token validation is that, a service stub is used to invoke
> an admin service deployed as part of EMM's Key Manager profile for token
> validation and the stub instances are created per-request to avoid the
> impact that is likely to be caused by stubs being less thread-safe. This
> pattern proved to be very expensive as it was quite evident that the stub
> instantiation is expensive. As a fix, a pool of stubs was introduced to
> mitigate the above explained impact with appropriate means to cleanup
> metadata just before the pooled stubs are returned to the pool. This helped
> doubling the numbers obtained for a properly distributed set-up of EMM 2.0.
> Please refer [1] for the source code.
>
> [1]
> https://github.com/wso2/carbon-device-mgt/commit/11957f1e478f884cc1f100debb4bbc8290c0901c
>
> Cheers,
> Prabath
>
> On Mon, Dec 21, 2015 at 2:44 PM, Dileesha Rajapakse 
> wrote:
>
>> 1. Install Jmeter
>> *sudo apt-get install jmeter*
>>
>> 2. Replace the '*/usr/share/jmeter/lib/*' directory with the 'lib'
>> directory which could be downloaded from below link. (This file contains
>> all the necessary library files needed to run test scripts)
>>
>> https://drive.google.com/file/d/0B1raQ3vGHU8uMjlhZU1EVzR0VGc/view?usp=sharing
>>
>> 3. Download and extract the scripts file
>>
>> https://drive.google.com/file/d/0B1raQ3vGHU8uaXhULTZzQUQwamc/view?usp=sharing
>>
>> The above '*EMM200LoadTests.zip*' file contains a total of 5 files.
>>
>>- *emm_devices.csv *- Contains information about 50 unique devices
>>- *EnrollDevices.jmx* - Enrolls Devices
>>- *AddOperations.jmx* - Adds Operations to enrolled devices (2
>>operations per each device)
>>- *GetPendingOperations.jmx* - Hits the
>>'/mdm-android-agent/operation' endpoint which is the most heavily used API
>>of the EMM
>>- *MDM2LoadTesting.jmx* - This script contains a sample Jmeter test
>>plan which has several additional useful test ThreadGroups which can be
>>used to simulate scenarios such as Operation Execution, Policy Creation 
>> and
>>Policy Monitoring
>>
>> *[Important]* Make sure the 'emm_devices.csv' file and the script files
>> are in the same folder.
>> 4. Specify these parameters when running test scripts
>>
>> *JHOST* --> Server Host
>> *JPORT* --> Server Port
>> *JUSERS* --> Number of Users (Concurrency)
>> *JLOOPCOUNT* --> Number of Iterations per User
>>
>>
>> Device Enrollment
>>
>> jmeter -n -JHOST= -JPORT=
>> -JUSERS= -JLOOPCOUNT= -t EnrollDevices.jmx -l
>> errors.log
>>
>>
>>- To enroll a '*n*' number of devices set the parameters as follows, 
>> *(-JUSERS)*(-JLOOPCOUNT)
>>= n*
>>
>>
>> Add Operations
>>
>> jmeter -n -JHOST= -JPORT=
>> -JUSERS= -JLOOPCOUNT= -t AddOperations.jmx -l
>> errors.log
>>
>>
>> Get Pending Operations
>>
>> jmeter -n -JHOST= -JPORT=
>> -JUSERS= -JLOOPCOUNT= -t
>> GetPendingOperations.jmx -l errors.log
>>
>>
>> --
>> Dileesha Rajapakse
>> *Intern - Engineering*
>> Mobile : +94 (0) 772 555 933
>> Tel  : +94 112 741 505
>> dilee...@wso2.com
>>
>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 5.0.0 RC2

[Sameera Jayasoma]

Hi Folks,

Verified the directory structure and recent changes the scripts and
configuration files.
Tested Startup Order Resolver.

[x] Stable - go ahead and release.

Regards,
Sameera

On Mon, Dec 21, 2015 at 10:53 AM, Dinusha Boteju  wrote:

> Hi all,
>
> Started the kernel using openjdk 8.
> Started the server in windows 7.
>
> Tested the Logging framework in both scenarios. No issues found.
>
> [x] Stable - go ahead and release.
>
> Best regards,
> Dinusha
>
>
> On Mon, Dec 21, 2015 at 10:07 AM, Samiyuru Senarathne 
> wrote:
>
>> Tested with MSS. No issues were found.
>>
>> [x] Stable - go ahead and release.
>>
>> Best Regards,
>> Samiyuru
>>
>> On Mon, Dec 21, 2015 at 1:08 AM, Kalpa Welivitigoda 
>> wrote:
>>
>>> Hi all,
>>>
>>> I tested the logging framework and jar-to bundle tool. No issues found.
>>>
>>> [x] Stable - go ahead and release
>>>
>>> On Sun, Dec 20, 2015 at 11:30 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 Tested both startup order resolver functionality and artifact
 deployment engine functionality. No issues encountered.

 [x] Stable - go ahead and release.

 Thanks,

 On Sun, Dec 20, 2015 at 1:22 PM, Nipuni Perera  wrote:

> Hi all,
>
> I have tested the launcher framework (loading launcher configurations
> from launcher.properties) with logging. No issues found except[1] which is
> already reported and will be fixed in 5.1.0.
>
> [1] https://wso2.org/jira/browse/CARBON-15745
>
> [x] Stable - go ahead and release
>
> Thanks,
> Nipuni
>
> On Sun, Dec 20, 2015 at 12:34 PM, Chiranga Alwis 
> wrote:
>
>> Hi,
>>
>> I tested the following aspects:
>> - jar-to-OSGi-bundle converter
>> - converted OSGi bundles in dropins folder being  successfully
>> deployed
>>
>> No issues discovered.
>>
>> [x] Stable - go ahead and release.
>>
>> On Sun, Dec 20, 2015 at 11:27 AM, Senduran Balasubramaniyam <
>> sendu...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I have tested product-gw's basic functionality with this release
>>> candidate.
>>> No issues found.
>>>
>>> [x] Stable - go ahead and release
>>>
>>> Regards
>>> Senduran
>>>
>>> On Sun, Dec 20, 2015 at 10:01 AM, Aruna Karunarathna >> > wrote:
>>>
 I've tested, the following features

 1. Logging framework
 2. Transport Management
 3. Jar to bundle conversion
 4. Dropins bundle deployment

 [x] Stable - go ahead and release

 Regards,
 Aruna

 On Sat, Dec 19, 2015 at 11:50 PM, Manuri Amaya Perera <
 manu...@wso2.com> wrote:

> Hi,
>
> I created projects using the available archetypes in staging
> repository and built and installed via dropins and osgi console and 
> tested
> the expected functionality with the kernel 5.0.0 RC2 pack.
>
> [x] Stable - go ahead and release.
>
> Thank you.
>
> On Fri, Dec 18, 2015 at 5:15 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the 2nd Release Candidate of WSO2 Carbon Kernel 5.0.0.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12581
>>
>> Please download and test your products with kernel 5.0.0 RC2
>> and vote.
>>
>> *​Source and binary distribution files:*
>>
>> https://github.com/wso2/carbon-kernel/releases/download/v5.0.0-RC2/wso2carbon-kernel-5.0.0-rc2.zip
>>
>> *Maven staging repository:*
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-210/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon-kernel/releases/tag/v5.0.0-RC2
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you,
>> Carbon Team
>>
>> --
>> *Kishanthan Thangarajah*
>> Associate Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan
>> *
>>
>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> 

Re: [Dev] [DS][DAS] Sample for DashboardServer - How to get back-end url, username, password for DAS to invoke DAS rest API from jaggery file

[Rajeenthini Satkunam]

Hi all,

Since it is a sample I am configuring this credentials with analytics.json
under folder of /carbon-dashboards/apps/portal/configs and getting
username,password and url by json file.

{
  "url" :"https://localhost:9465/analytics/search;,
  "username" : "admin",
  "password" : "admin"
}

Thank you for prompt replies.

On Fri, Dec 18, 2015 at 2:38 PM, Isuru Wijesinghe  wrote:

> Hi Rajeenthini,
>
> Can't you hold a configuration file at the back-end side for this ?? Here
> what I mean is something similar to below example. In the url tag you
> should have to keep the base url of the DAS. The rest of the part of the
> url u can append from the code. (Please note that if you keep a property
> file like below, you should have to add secure vault also. It  is used to
> secure plain text password which is contains in configuration  files of
> WSO2 products).  And then you can read it from your jaggery code . (see
> http://jaggeryjs.org/documentation.jag?api=file)
> eg:
> 
> http://wso2.org/pc/config;>
> 
> https://localhost:9445/
> admin
> admin
> 
> 
>
>
> On Fri, Dec 18, 2015 at 12:33 PM, Supun Sethunga  wrote:
>
>> Hi Rajeenthini,
>>
>> Instead of the DAS REST API, you can use the "Analytics javascript API"
>> [1]. This should eliminate the requirement of needing user-credentials. (or
>> doesn't need to send an Authorization header)
>>
>> [1] https://docs.wso2.com/display/DAS300/Analytics+JavaScript+(JS)+API
>>
>> Regards,
>> Supun
>>
>> On Fri, Dec 18, 2015 at 10:41 AM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> Currently I am working on creating sample for dashboard server with DAS
>>> integration.I need to invoke DAS rest API from Jaggery file(sample.jag) to
>>> get some data.As per documentation[1] of DAS rest API we need to send
>>> authorization header along with request to fetch data from DAS. So for
>>> workaround I have hard-coded the username password values to variable and
>>> concatenate them as username + ":" + password and encoded them then send as
>>> a authorization header.Here I need to get server username and
>>> password(credentials).IMHO it is not good practice that hard-coding
>>> credentials of server.
>>> I have shared my Jaggery code below
>>>
>>> try {
>>> var username = "admin";//hard-coded value of username
>>> var password = "admin";//hard-coded value of password
>>> var tableName = request.getParameter("tableName");
>>> var query = request.getParameter("query");
>>> var url = "https://localhost:9465/analytics/search;;
>>> var encoderJavaPkg = Packages.javax.xml.bind.DatatypeConverter;
>>> var bytes = [];
>>> var encodeString = username + ":" + password;
>>> for (var i = 0; i < encodeString.length; ++i) {
>>> bytes.push(encodeString.charCodeAt(i));
>>> }
>>> var authHeader = "Basic " + encoderJavaPkg.printBase64Binary(bytes);
>>> var result = post(url, stringify({
>>> "tableName": tableName,
>>> "start": 0,
>>> "count": 100,
>>> "query": query
>>> }), {"Authorization": authHeader, "Content-Type": "application/json"}, 
>>> "application/json");
>>> print(result.data);
>>> } catch (e) {
>>> log.info(e);
>>> }
>>>
>>> [1] - 
>>> https://docs.wso2.com/display/DAS300/Retrieving+All+Records+Matching+the+Given+Search+Query+via+REST+API
>>>
>>> As for now to start both server (DAS and DS) I have changed offset value 
>>> for DAS as "2" in carbon.xml.I can successfully start both server 
>>> simultaneously.It will be very useful if I can get the back-end URL and 
>>> server credentials of DAS and get rid of hard-coding those values.Can 
>>> anyone please help me and your suggestions mostly appreciate?
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Thank You.*
>>>
>>> *Rajeenthini Satkunam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>>
>>> *E:rajeenth...@wso2.com *
>>>
>>> *M :+94770832823 <%2B94770832823>   *
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Supun Sethunga*
>> Software Engineer
>> WSO2, Inc.
>> http://wso2.com/
>> lean | enterprise | middleware
>> Mobile : +94 716546324
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Wijesinghe
> *Software Engineer*
> WSO2 inc : http://wso2.com
> lean.enterprise.middleware
> Mobile: 0710933706
> isur...@wso2.com
>



-- 

*Thank You.*

*Rajeenthini Satkunam*

*Associate Software Engineer | WSO2*


*E:rajeenth...@wso2.com *

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

Re: [Dev] Orbit bundle for BigQueue

[Aruna Karunarathna]

This is merged. Maheshika Can you please host this bundle?

Regards,
Aruna

On Mon, Dec 21, 2015 at 5:18 PM, Gokul Balakrishnan  wrote:

> Hi Kernel team,
>
> I've sent a PR for a $subject at [1]. Could you please review?
>
> [1] https://github.com/wso2/orbit/pull/160
>
> Thanks,
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>



-- 

*Aruna Sujith Karunarathna *| Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Orbit bundle for BigQueue

[Gokul Balakrishnan]

Hi Kernel team,

I've sent a PR for a $subject at [1]. Could you please review?

[1] https://github.com/wso2/orbit/pull/160

Thanks,

-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Nadeesha Meegoda]

Hi Yasassri,

Thanks. I will investigate on this more. The other products in same
directory are starting without any issue. That's why I raised the concern.

Regards,
Nadeesha

On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake 
wrote:

> Hi,
>
> We were able to successfully start MB without any issue with Java 1.8 and
> with Java 1.7 in windows environment. I tested with your exact java version
> as well (1.7.0_79). I believe you haven't set your environment variables
> properly. As per your error it says "The system cannot find the file
> specified.".  I think this is self explanatory.
>
> Please compare with the following logs and check whats missing.
>
> TID: [] [] [2015-12-21 10:23:49,834]  WARN
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
> determine dialect of the StAX implementation at
> bundleresource://13.fwk2427473/
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
> TID: [] [] [2015-12-21 10:23:49,834]  WARN
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
> determine dialect of the StAX implementation at
> bundleresource://13.fwk2427473/
> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
> TID: [] [] [2015-12-21 10:23:49,756]  INFO
> {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting BundleContext
> in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Windows Server 2012 R2 6.3, amd64
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> C:\Program Files\Java\jdk1.7.0_79\jre
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> Administrator, en-US, UTC
> {org.wso2.carbon.core.internal.CarbonCoreActivator}
> TID: [-1234] [] [2015-12-21 10:23:51,694]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
> running OS : Windows Server 2012 R2 is not a tested Operating System for
> running WSO2 Carbon
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
> TID: [-1234] [] [2015-12-21 10:23:51,709]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Carbon is configured to use the default keystore (wso2carbon.jks). To
> maximize security when deploying to a production environment, configure a
> new keystore with a unique password in the production server profile.
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
> TID: [] [] [2015-12-21 10:23:51,725]  INFO
> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
> {org.wso2.carbon.databridge.agent.thrift.AgentHolder}
> TID: [] [] [2015-12-21 10:23:51,756]  INFO
> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
> deployed Agent Client
> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS}
> TID: [-1234] [] [2015-12-21 10:23:54,615]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Configured
> Registry in 99ms
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
> TID: [-1234] [] [2015-12-21 10:23:54,725]  INFO
> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
>  Registry Mode: READ-WRITE
> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent}
> TID: [-1234] [] [2015-12-21 10:23:54,881]  INFO
> {org.wso2.carbon.metrics.impl.MetricServiceImpl} -  Creating JDBC reporter
> for Metrics with source 'oracle12c', data source 'jdbc/WSO2MetricsDB' and
> 60 seconds polling period {org.wso2.carbon.metrics.impl.MetricServiceImpl}
> TID: [-1234] [] [2015-12-21 10:23:54,881]  

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Isuru Perera]

Looks like you are running MB on the 32-bit JDK. Can you try with 64-bit
JDK?

On Mon, Dec 21, 2015 at 5:08 PM, Nadeesha Meegoda 
wrote:

> Hi Yasassri,
>
> Thanks. I will investigate on this more. The other products in same
> directory are starting without any issue. That's why I raised the concern.
>
> Regards,
> Nadeesha
>
> On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake 
> wrote:
>
>> Hi,
>>
>> We were able to successfully start MB without any issue with Java 1.8 and
>> with Java 1.7 in windows environment. I tested with your exact java version
>> as well (1.7.0_79). I believe you haven't set your environment variables
>> properly. As per your error it says "The system cannot find the file
>> specified.".  I think this is self explanatory.
>>
>> Please compare with the following logs and check whats missing.
>>
>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>> determine dialect of the StAX implementation at
>> bundleresource://13.fwk2427473/
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>> determine dialect of the StAX implementation at
>> bundleresource://13.fwk2427473/
>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>> TID: [] [] [2015-12-21 10:23:49,756]  INFO
>> {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting BundleContext
>> in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Windows Server 2012 R2 6.3, amd64
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> C:\Program Files\Java\jdk1.7.0_79\jre
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>> Administrator, en-US, UTC
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> TID: [-1234] [] [2015-12-21 10:23:51,694]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
>> running OS : Windows Server 2012 R2 is not a tested Operating System for
>> running WSO2 Carbon
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
>> TID: [-1234] [] [2015-12-21 10:23:51,709]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>  Carbon is configured to use the default keystore (wso2carbon.jks). To
>> maximize security when deploying to a production environment, configure a
>> new keystore with a unique password in the production server profile.
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
>> TID: [] [] [2015-12-21 10:23:51,725]  INFO
>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder}
>> TID: [] [] [2015-12-21 10:23:51,756]  INFO
>> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
>> deployed Agent Client
>> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS}
>> TID: [-1234] [] [2015-12-21 10:23:54,615]  INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Configured
>> Registry in 99ms
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService}
>> TID: [-1234] [] [2015-12-21 10:23:54,725]  INFO
>> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
>>  Registry Mode: READ-WRITE
>> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent}
>> TID: [-1234] [] [2015-12-21 10:23:54,881]  INFO
>> 

[Dev] [VOTE] Release WSO2 Identity Server 5.1.0 RC2

[Hasintha Indrajee]

Hi Devs,

This is the second release candidate of WSO2 Identity Server 5.1.0.

This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12586

Please download, test and vote.

Source & binary distribution files:
https://github.com/wso2/product-is/releases/tag/v5.1.0-rc2

Maven staging repo:
http://maven.wso2.org/nexus/content/repositories/orgwso2is-218/

The tag to be voted upon:
https://github.com/wso2/product-is/tree/v5.1.0-rc2


[ ]  Stable - go ahead and release
[ ]  Broken - do not release (explain why)

Thanks and Regards,
WSO2 Identity Server Team.

-- 
Hasintha Indrajee
Software Engineer
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Identity Server 5.1.0 RC2

[Prabath Siriwardana]

On Mon, Dec 21, 2015 at 4:59 AM, Hasintha Indrajee 
wrote:

> Hi Devs,
>
> This is the second release candidate of WSO2 Identity Server 5.1.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12586
>
> Please download, test and vote.
>
> Source & binary distribution files:
> https://github.com/wso2/product-is/releases/tag/v5.1.0-rc2
>

Returns 404...

Thanks & regards,
-Prabath


>
> Maven staging repo:
> http://maven.wso2.org/nexus/content/repositories/orgwso2is-218/
>
> The tag to be voted upon:
> https://github.com/wso2/product-is/tree/v5.1.0-rc2
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
> Thanks and Regards,
> WSO2 Identity Server Team.
>
> --
> Hasintha Indrajee
> Software Engineer
> WSO2, Inc.
> Mobile:+94 771892453
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +1 650 625 7950

http://blog.facilelogin.com
http://blog.api-security.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Orbit bundle for BigQueue

[Maheshika Goonetilleke]

Hi Aruna

Please discard the previous mail.

On Mon, Dec 21, 2015 at 10:20 PM, Maheshika Goonetilleke  wrote:

> Hi Aruna
>
> Staged
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmediation-220/
>
> On Mon, Dec 21, 2015 at 6:20 PM, Aruna Karunarathna 
> wrote:
>
>> This is merged. Maheshika Can you please host this bundle?
>>
>> Regards,
>> Aruna
>>
>> On Mon, Dec 21, 2015 at 5:18 PM, Gokul Balakrishnan 
>> wrote:
>>
>>> Hi Kernel team,
>>>
>>> I've sent a PR for a $subject at [1]. Could you please review?
>>>
>>> [1] https://github.com/wso2/orbit/pull/160
>>>
>>> Thanks,
>>>
>>> --
>>> Gokul Balakrishnan
>>> Senior Software Engineer,
>>> WSO2, Inc. http://wso2.com
>>> Mob: +94 77 593 5789 | +1 650 272 9927
>>>
>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>
>
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Engineering Process Coordinator
>
> *WSO2 Inc*
> *email   : mahesh...@wso2.com *
> *mobile : +94 773 596707 <%2B94%20773%20596707>*
> *www: :http://wso2.com *lean . enterprise . middleware
>
>
>
>
>


-- 

Thanks & Best Regards,

Maheshika Goonetilleke
Engineering Process Coordinator

*WSO2 Inc*
*email   : mahesh...@wso2.com *
*mobile : +94 773 596707*
*www: :http://wso2.com *lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Orbit bundle for BigQueue

[Maheshika Goonetilleke]

Hi Aruna

Staged
http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmediation-220/

On Mon, Dec 21, 2015 at 6:20 PM, Aruna Karunarathna  wrote:

> This is merged. Maheshika Can you please host this bundle?
>
> Regards,
> Aruna
>
> On Mon, Dec 21, 2015 at 5:18 PM, Gokul Balakrishnan 
> wrote:
>
>> Hi Kernel team,
>>
>> I've sent a PR for a $subject at [1]. Could you please review?
>>
>> [1] https://github.com/wso2/orbit/pull/160
>>
>> Thanks,
>>
>> --
>> Gokul Balakrishnan
>> Senior Software Engineer,
>> WSO2, Inc. http://wso2.com
>> Mob: +94 77 593 5789 | +1 650 272 9927
>>
>
>
>
> --
>
> *Aruna Sujith Karunarathna *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



-- 

Thanks & Best Regards,

Maheshika Goonetilleke
Engineering Process Coordinator

*WSO2 Inc*
*email   : mahesh...@wso2.com *
*mobile : +94 773 596707*
*www: :http://wso2.com *lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Orbit bundle for BigQueue

[Maheshika Goonetilleke]

Hi Aruna

Deployed successfully.


On Mon, Dec 21, 2015 at 10:20 PM, Maheshika Goonetilleke  wrote:

> Hi Aruna
>
> Please discard the previous mail.
>
> On Mon, Dec 21, 2015 at 10:20 PM, Maheshika Goonetilleke <
> mahesh...@wso2.com> wrote:
>
>> Hi Aruna
>>
>> Staged
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmediation-220/
>>
>> On Mon, Dec 21, 2015 at 6:20 PM, Aruna Karunarathna 
>> wrote:
>>
>>> This is merged. Maheshika Can you please host this bundle?
>>>
>>> Regards,
>>> Aruna
>>>
>>> On Mon, Dec 21, 2015 at 5:18 PM, Gokul Balakrishnan 
>>> wrote:
>>>
 Hi Kernel team,

 I've sent a PR for a $subject at [1]. Could you please review?

 [1] https://github.com/wso2/orbit/pull/160

 Thanks,

 --
 Gokul Balakrishnan
 Senior Software Engineer,
 WSO2, Inc. http://wso2.com
 Mob: +94 77 593 5789 | +1 650 272 9927

>>>
>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *| Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.wso2.com
>>>
>>>
>>
>>
>>
>> --
>>
>> Thanks & Best Regards,
>>
>> Maheshika Goonetilleke
>> Engineering Process Coordinator
>>
>> *WSO2 Inc*
>> *email   : mahesh...@wso2.com *
>> *mobile : +94 773 596707 <%2B94%20773%20596707>*
>> *www: :http://wso2.com *lean . enterprise . middleware
>>
>>
>>
>>
>>
>
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Engineering Process Coordinator
>
> *WSO2 Inc*
> *email   : mahesh...@wso2.com *
> *mobile : +94 773 596707 <%2B94%20773%20596707>*
> *www: :http://wso2.com *lean . enterprise . middleware
>
>
>
>
>


-- 

Thanks & Best Regards,

Maheshika Goonetilleke
Engineering Process Coordinator

*WSO2 Inc*
*email   : mahesh...@wso2.com *
*mobile : +94 773 596707*
*www: :http://wso2.com *lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "No bam.xml" - Is this required to be present when embedding DAS?

[Sinthuja Ragendran]

Hi,

This is not because of DAS, rather its from Service Stats Publisher
component which engages a global axis2 module to collect the service
requests/response related stats. And from
WSO2_HOME/repository/conf/etc/bam.xml,
you can globally enable/disable this module. Anyhow you can resolve this,
if you add this configuration in the bin.xml to copy from service stats
feature during the product build.

Thanks,
Sinthuja.

On Fri, Dec 18, 2015 at 3:36 PM, Sumedha Rubasinghe 
wrote:

> Getting following error.
>
> [2015-12-18 15:33:57,538]  WARN
> {org.wso2.carbon.bam.service.data.publisher.internal.StatisticsServiceComponent}
> -  No bam.xml found in
> /Volumes/data/projects/wso2/iot-server/src/product-iot-server/modules/distribution/target/wso2iot-1.0.0-SNAPSHOT/repository/conf/etc/bam.xml
> [2015-12-18 15:33:57,538]  WARN
> {org.wso2.carbon.bam.service.data.publisher.internal.StatisticsServiceComponent}
> -  Invalid bam.xml. Disabling service publishing.
>
>
> --
> /sumedha
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sinthuja Rajendran*
Associate Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB 3.0.0 is not starting on Windows 7/Java 1.7

[Nadeesha Meegoda]

Hi Isuru,

Yes I am running MB on the 32-bit JDK. I have installed both 32 bit and 64
bit JDK in my machine. However other products seems to start without any
error in both 32bit and 64bit JDK. I also checked MB in 64bit JDK now. MB
starts fine with that.


Thanks,
Nadeesha

On Mon, Dec 21, 2015 at 6:13 PM, Isuru Perera  wrote:

> Looks like you are running MB on the 32-bit JDK. Can you try with 64-bit
> JDK?
>
> On Mon, Dec 21, 2015 at 5:08 PM, Nadeesha Meegoda 
> wrote:
>
>> Hi Yasassri,
>>
>> Thanks. I will investigate on this more. The other products in same
>> directory are starting without any issue. That's why I raised the concern.
>>
>> Regards,
>> Nadeesha
>>
>> On Mon, Dec 21, 2015 at 4:09 PM, Yasassri Ratnayake 
>> wrote:
>>
>>> Hi,
>>>
>>> We were able to successfully start MB without any issue with Java 1.8
>>> and with Java 1.7 in windows environment. I tested with your exact java
>>> version as well (1.7.0_79). I believe you haven't set your environment
>>> variables properly. As per your error it says "The system cannot find
>>> the file specified.".  I think this is self explanatory.
>>>
>>> Please compare with the following logs and check whats missing.
>>>
>>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>>> determine dialect of the StAX implementation at
>>> bundleresource://13.fwk2427473/
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>>> TID: [] [] [2015-12-21 10:23:49,834]  WARN
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector} -  Unable to
>>> determine dialect of the StAX implementation at
>>> bundleresource://13.fwk2427473/
>>> {org.apache.axiom.util.stax.dialect.StAXDialectDetector}
>>> TID: [] [] [2015-12-21 10:23:49,756]  INFO
>>> {org.wso2.andes.wso2.internal.QpidBundleActivator} -  Setting BundleContext
>>> in PluginManager {org.wso2.andes.wso2.internal.QpidBundleActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>>> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>>> Windows Server 2012 R2 6.3, amd64
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>>> C:\Program Files\Java\jdk1.7.0_79\jre
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>>> 1.7.0_79 {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>>> Java HotSpot(TM) 64-Bit Server VM 24.79-b02,Oracle Corporation
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>>> C:\Users\ADMINI~1\DOWNLO~1\WSO2MB~1.0\WSO2MB~1.0\bin\..\tmp
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,303]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>>> Administrator, en-US, UTC
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>>> TID: [-1234] [] [2015-12-21 10:23:51,694]  WARN
>>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
>>> running OS : Windows Server 2012 R2 is not a tested Operating System for
>>> running WSO2 Carbon
>>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
>>> TID: [-1234] [] [2015-12-21 10:23:51,709]  WARN
>>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>>  Carbon is configured to use the default keystore (wso2carbon.jks). To
>>> maximize security when deploying to a production environment, configure a
>>> new keystore with a unique password in the production server profile.
>>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
>>> TID: [] [] [2015-12-21 10:23:51,725]  INFO
>>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
>>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder}
>>> TID: [] [] [2015-12-21 10:23:51,756]  INFO
>>> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
>>> deployed Agent Client
>>> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS}
>>> TID: [-1234] [] [2015-12-21 10:23:54,615]  INFO
>>> 

Re: [Dev] Orbit bundle for BigQueue

[Gokul Balakrishnan]

Thanks Aruna and Maheshika!

On Monday, 21 December 2015, Maheshika Goonetilleke 
wrote:

> Hi Aruna
>
> Deployed successfully.
>
>
> On Mon, Dec 21, 2015 at 10:20 PM, Maheshika Goonetilleke <
> mahesh...@wso2.com >
> wrote:
>
>> Hi Aruna
>>
>> Please discard the previous mail.
>>
>> On Mon, Dec 21, 2015 at 10:20 PM, Maheshika Goonetilleke <
>> mahesh...@wso2.com >
>> wrote:
>>
>>> Hi Aruna
>>>
>>> Staged
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmediation-220/
>>>
>>> On Mon, Dec 21, 2015 at 6:20 PM, Aruna Karunarathna >> > wrote:
>>>
 This is merged. Maheshika Can you please host this bundle?

 Regards,
 Aruna

 On Mon, Dec 21, 2015 at 5:18 PM, Gokul Balakrishnan > wrote:

> Hi Kernel team,
>
> I've sent a PR for a $subject at [1]. Could you please review?
>
> [1] https://github.com/wso2/orbit/pull/160
>
> Thanks,
>
> --
> Gokul Balakrishnan
> Senior Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>



 --

 *Aruna Sujith Karunarathna *| Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 9040362 | Work: +94 112145345
 Email: ar...@wso2.com 
 | Web: www.wso2.com


>>>
>>>
>>>
>>> --
>>>
>>> Thanks & Best Regards,
>>>
>>> Maheshika Goonetilleke
>>> Engineering Process Coordinator
>>>
>>> *WSO2 Inc*
>>> *email   : mahesh...@wso2.com
>>> *
>>> *mobile : +94 773 596707 <%2B94%20773%20596707>*
>>> *www: :http://wso2.com *lean . enterprise . middleware
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>>
>> Thanks & Best Regards,
>>
>> Maheshika Goonetilleke
>> Engineering Process Coordinator
>>
>> *WSO2 Inc*
>> *email   : mahesh...@wso2.com
>> *
>> *mobile : +94 773 596707 <%2B94%20773%20596707>*
>> *www: :http://wso2.com *lean . enterprise . middleware
>>
>>
>>
>>
>>
>
>
> --
>
> Thanks & Best Regards,
>
> Maheshika Goonetilleke
> Engineering Process Coordinator
>
> *WSO2 Inc*
> *email   : mahesh...@wso2.com
> *
> *mobile : +94 773 596707*
> *www: :http://wso2.com *lean . enterprise . middleware
>
>
>
>
>

-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev