date:20160919

Re: [Dev] All ESB service calls with data

2016-09-19 Thread Hariprasath Thanarajah

Hi Palani,

Yes it is possible in 4.8.1. You can refer [1] for further details,

[1] - https://docs.wso2.com/display/ESB481/Log+Mediator

On Tue, Sep 20, 2016 at 10:13 AM, Palani Tester 
wrote:

> Hi Team,
>
>
> I'm looking for logs, which should record all ESB service calls, class
> mediator calls and data. Is it possible to get from ESB 4.8.1 version?
> Please let me know, how to configure and what info has to be set...
>
>
>
> Thanks,
>
> Palani
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*Thank you and Regards,**Hariprasath Thanarajah*
Associate Software Engineer | WSO2
E: haripras...@wso2.com
M: +94752806528, 0777216903
Blog: hariwso2.blogspot.com

Skype : hariss636
LinkedIn : https://www.linkedin.com/in/hariprasath-thanarajah-5234b660

WSO2, Inc.
lean . enterprise . middleware

https://wso2.com/signature
http://wso2.com/about/team/hariprashath-thanarajah/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] All ESB service calls with data

2016-09-19 Thread Palani Tester

Hi Team,


I'm looking for logs, which should record all ESB service calls, class mediator 
calls and data. Is it possible to get from ESB 4.8.1 version? Please let me 
know, how to configure and what info has to be set...



Thanks,

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

Re: [Dev] [APIM] Where I can find the source code for Admin Dashboard in API Manager

2016-09-19 Thread Abimaran Kugathasan

Hi Sumedha,


There aren't any reason, we need to create a new feature for admin portal
and move it to there.

On Mon, Sep 19, 2016 at 8:59 PM, Sumedha Kodithuwakku 
wrote:

> Hi Lakmali,
>
> Thanks. Any particular reason for keeping it under store feature.?
>
> Thanks
> SumedhaS
>
>
> On Monday, 19 September 2016, Lakmali Baminiwatta 
> wrote:
>
>> Hi Sumedha,
>>
>> Find the source location of APIM 2.0.0 admin app from [1]
>>
>> [1] https://github.com/wso2/carbon-apimgt/tree/v6.0.4/featur
>> es/apimgt/org.wso2.carbon.apimgt.store.feature/src/main/resources/admin
>>
>> Thanks,
>> Lakmali
>>
>> On 19 September 2016 at 18:43, Sumedha Kodithuwakku 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> $subject.? In product-apim repo there is a jaggery app called
>>> admin-dashboard-web [1], but it is different from the app found in the APIM
>>> 2.0.0 released pack.
>>>
>>> Appriciate if you can share the location of the source code of the admin
>>> dashboard.
>>>
>>> [1] https://github.com/wso2/product-apim/tree/master/modules
>>> /jaggery-apps/admin-dashboard-web/
>>>
>>> Thanks
>>> SumedhaS
>>>
>>> --
>>> *Sumedha Kodithuwakku*
>>> Senior Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> Mobile: +94 71 808 1124
>>> Blog: http://sumedhask.blogspot.com/
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Lakmali Baminiwatta
>> Associate Technical Lead
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> mobile:  +94 71 2335936
>> blog : lakmali.com
>>
>>
>
> --
> *Sumedha Kodithuwakku*
> Senior Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> Mobile: +94 71 808 1124
> Blog: http://sumedhask.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] [APIM] Where I can find the source code for Admin Dashboard in API Manager

2016-09-19 Thread Lakmali Baminiwatta

Hi Sumedha,

Find the source location of APIM 2.0.0 admin app from [1]

[1]
https://github.com/wso2/carbon-apimgt/tree/v6.0.4/features/apimgt/org.wso2.carbon.apimgt.store.feature/src/main/resources/admin

Thanks,
Lakmali

On 19 September 2016 at 18:43, Sumedha Kodithuwakku 
wrote:

> Hi Devs,
>
> $subject.? In product-apim repo there is a jaggery app called
> admin-dashboard-web [1], but it is different from the app found in the APIM
> 2.0.0 released pack.
>
> Appriciate if you can share the location of the source code of the admin
> dashboard.
>
> [1] https://github.com/wso2/product-apim/tree/master/
> modules/jaggery-apps/admin-dashboard-web/
>
> Thanks
> SumedhaS
>
> --
> *Sumedha Kodithuwakku*
> Senior Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> Mobile: +94 71 808 1124
> Blog: http://sumedhask.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Lakmali Baminiwatta
Associate Technical Lead
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware
mobile:  +94 71 2335936
blog : lakmali.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM] Where I can find the source code for Admin Dashboard in API Manager

2016-09-19 Thread Sumedha Kodithuwakku

Hi Devs,

$subject.? In product-apim repo there is a jaggery app called
admin-dashboard-web [1], but it is different from the app found in the APIM
2.0.0 released pack.

Appriciate if you can share the location of the source code of the admin
dashboard.

[1]
https://github.com/wso2/product-apim/tree/master/modules/jaggery-apps/admin-dashboard-web/

Thanks
SumedhaS

-- 
*Sumedha Kodithuwakku*
Senior Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware

Mobile: +94 71 808 1124
Blog: http://sumedhask.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Need documentation for saml-cloud inbound authenticators

2016-09-19 Thread Kanapriya Kuleswararajan

Hi All,

I have tried [1] with wso2-is-5.2.0 and I got the following UI [2] for
saml-cloud. But how can we get started with these inbound authenticator
configurations or how can I test it with these inbound authenticators such
as NetSuite,Amazon,Salesforce and etc.
Is there any related documentation to follow up?

[1]
https://github.com/wso2-extensions/identity-inbound-auth-saml-cloud/tree/5.2.0-M1
[2]


Thanks

Kanapriya Kuleswararajan
Associate Software Engineer
Mobile : - 0774894438
Mail : - kanapr...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager - periodic failure of OAuth2Service for AccessTokens via the publisher API

2016-09-19 Thread Malintha Amarasinghe

Hi,

Can you please share the exact API calls you used to reproduce the issue?

Thanks!

On Mon, Sep 19, 2016 at 4:40 PM, Alan Tucker Spida Solutions <
a...@spidasolutions.com> wrote:

> We are periodically seeing failures when trying to request Access Tokens
> via the APIM publisher API. An instance of APIM will perform correctly
> returning AccessTokens for a time. Occasionally, after restart it will fail
> when requesting access tokens via the publisher API. After subsequent
> restarts the same instance may or may not then return to operating
> correctly. The test scenario in all cases is the same.
>
> Note that if the user (that is being used to request an access token) logs
> into the API store of the APIM instance, subsequent requests via the
> Publisher API will then succeed. This appears to be reproducible.
>
> On failure the typical stack trace below is seen:
>
> [2016-09-19 09:52:31,163]  INFO - TokenMgtDAO Thread pool size for session
> persistent consumer : 100
> [2016-09-19 09:52:31,262]  INFO - OAuthServerConfiguration The default
> OAuth token issuer will be used. No custom token generator is set.
> [2016-09-19 09:52:31,263]  INFO - OAuthServerConfiguration The default
> Identity OAuth token issuer will be used. No custom token generator is set.
> [2016-09-19 09:52:33,516]  WARN - AccessConfiguration Error loading
> properties from file: access-log.properties
> [2016-09-19 09:52:33,594]  INFO - TimeoutHandler This engine will expire
> all callbacks after : 120 seconds, irrespective of the timeout action,
> after the specified or optional timeout
> [2016-09-19 09:52:33,798] ERROR - OAuth2Service Error occurred while
> issuing the access token for Client ID : ***, User ID
> , Scope : [apim:api_create] and Grant Type : password
> java.lang.NullPointerException
> at org.wso2.carbon.apimgt.impl.utils.APIUtil.getRESTAPIScopesFromConfig(
> APIUtil.java:5130)
> at org.wso2.carbon.apimgt.keymgt.ScopesIssuer.setScopes(
> ScopesIssuer.java:100)
> at org.wso2.carbon.apimgt.keymgt.handlers.ExtendedPasswordGrantHandler.
> validateScope(ExtendedPasswordGrantHandler.java:168)
> at org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(
> AccessTokenIssuer.java:226)
> at org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(
> OAuth2Service.java:219)
> at org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.
> getAccessToken(OAuth2TokenEndpoint.java:246)
> at org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.
> issueAccessToken(OAuth2TokenEndpoint.java:110)
>
>
>
>
> [image: Spida Solutions] 
> *Alan Tucker *
> *Spida Solutions *
> London • Bath • UK
> +44 (0)78 0308 4376 <+44-780-308-4376>
> +44 (0)12 4981 5081 <+44-12-4981-5081>
> www.spidasolutions.com 
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Malintha Amarasinghe
Software Engineer
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

Mobile : +94 712383306
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] API Manager - periodic failure of OAuth2Service for AccessTokens via the publisher API

2016-09-19 Thread Alan Tucker Spida Solutions

We are periodically seeing failures when trying to request Access Tokens via 
the APIM publisher API. An instance of APIM will perform correctly returning 
AccessTokens for a time. Occasionally, after restart it will fail when 
requesting access tokens via the publisher API. After subsequent restarts the 
same instance may or may not then return to operating correctly. The test 
scenario in all cases is the same.

Note that if the user (that is being used to request an access token) logs into 
the API store of the APIM instance, subsequent requests via the Publisher API 
will then succeed. This appears to be reproducible.

On failure the typical stack trace below is seen:

[2016-09-19 09:52:31,163]  INFO - TokenMgtDAO Thread pool size for session 
persistent consumer : 100
[2016-09-19 09:52:31,262]  INFO - OAuthServerConfiguration The default OAuth 
token issuer will be used. No custom token generator is set.
[2016-09-19 09:52:31,263]  INFO - OAuthServerConfiguration The default Identity 
OAuth token issuer will be used. No custom token generator is set.
[2016-09-19 09:52:33,516]  WARN - AccessConfiguration Error loading properties 
from file: access-log.properties
[2016-09-19 09:52:33,594]  INFO - TimeoutHandler This engine will expire all 
callbacks after : 120 seconds, irrespective of the timeout action, after the 
specified or optional timeout
[2016-09-19 09:52:33,798] ERROR - OAuth2Service Error occurred while issuing 
the access token for Client ID : ***, User ID 
, Scope : [apim:api_create] and Grant Type : password
java.lang.NullPointerException
at 
org.wso2.carbon.apimgt.impl.utils.APIUtil.getRESTAPIScopesFromConfig(APIUtil.java:5130)
at 
org.wso2.carbon.apimgt.keymgt.ScopesIssuer.setScopes(ScopesIssuer.java:100)
at 
org.wso2.carbon.apimgt.keymgt.handlers.ExtendedPasswordGrantHandler.validateScope(ExtendedPasswordGrantHandler.java:168)
at 
org.wso2.carbon.identity.oauth2.token.AccessTokenIssuer.issue(AccessTokenIssuer.java:226)
at 
org.wso2.carbon.identity.oauth2.OAuth2Service.issueAccessToken(OAuth2Service.java:219)
at 
org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.getAccessToken(OAuth2TokenEndpoint.java:246)
at 
org.wso2.carbon.identity.oauth.endpoint.token.OAuth2TokenEndpoint.issueAccessToken(OAuth2TokenEndpoint.java:110)




    

Alan Tucker 
Spida Solutions 
London • Bath • UK
+44 (0)78 0308 4376 
+44 (0)12 4981 5081 
www.spidasolutions.com 

 

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

Re: [Dev] [puppet] Setting up puppet home from script

2016-09-19 Thread Akila Ravihansa Perera

Hi,

I've improved the Puppet-Home setup script by introducing two map;
product_code_to_name_map and product_name_to_module_repo_map. With this
approach we can handle cases where product name and product code is
different. For eg: API Manager code is "apim" while product name is
"wso2am".

Also I've added platform support for Hiera data as well. You can use
"setup.sh -p  -l " to setup Puppet Home with
Hiera data for a specific platform. If none given it will default to
'default' platform.

The relevant platform repo for the given product should contain a hieradata
directory which will be symlink'd to PUPPET_HOME/hieradata. For eg: wso2esb
kubernetes platform - https://github.com/wso2/kubernetes-esb should contain
a "hieradata" directory at the repo root level; https://github.com/
wso2/kubernetes-esb/tree/master/hieradata

Thanks.

On Thu, Sep 8, 2016 at 9:59 AM, Anuruddha Liyanarachchi  wrote:

> Hi Pubudu,
>
> +1 for the platform support.
> I will add the platform support once we finalized the platform
> hieradata structure.
>
> On Thu, Sep 8, 2016 at 3:44 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Wed, Sep 7, 2016 at 10:09 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>>
>>> I think we need to include the platform as well. If we consider the big
>>> picture, ideally any user should be able to use this script and create a
>>> puppet home for building docker images for Kubernetes, Mesos, or any other
>>> platforms. As we have separate repos for platform hieradata,  we need to
>>> copy those hieradata to the puppet home repo.
>>>
>>
>> +1
>>
>>
>>>
>>> Thank you!
>>>
>>>
>>> On Wed, Sep 7, 2016 at 8:21 PM, Imesh Gunaratne  wrote:
>>>


 On Wed, Sep 7, 2016 at 6:24 PM, Anuruddha Liyanarachchi <
 anurudd...@wso2.com> wrote:

> Hi Imesh,
>
> I have now added the ability to configure multiple products using
> comma separated product list.
> Also included '-p all' option which configures all the products.
>
> Ex: ./setup.sh -p as
> Ex: ./setup.sh -p as,esb,bps
> Ex: ./setup.sh -p all
>

 Great!
 Nice to hear that!

>
> On Wed, Sep 7, 2016 at 12:46 AM, Imesh Gunaratne 
> wrote:
>
>> Great work Anuruddha! The bash script works well!
>>
>> Shall we add the ability to install multiple product modules in one
>> go? Maybe we can use a comma separated product list with -p.
>>
>> Thanks
>>
>> On Tue, Sep 6, 2016 at 6:26 PM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We have  created separate GitHub repos for Puppet modules so that
>>> the Puppet module can be shipped as part of a product release.
>>>
>>> Since modules are distributed we have introduced a script to
>>> generate PUPPET_HOME. The script will work as following.
>>>
>>>  1. Check puppet_home folder exists.
>>>
>>>  2. Create folder structure required for puppet_home.
>>> ├── hiera.yaml
>>> ├── hieradata
>>> ├── manifests
>>> └── modules
>>>
>>> 3.  Create a symlink to manifest/site.pp file.
>>>
>>> 4. Clone wso2base puppet module into  /modules
>>> directory.
>>>
>>> 5. Create a symlink to wso2base common.yaml hiera-file.
>>>
 /modules/wso2base/hieradata/wso2/common.yaml ->
 /hieradata/dev/wso2/
>>>
>>>
>>> 6. Clone wso2 puppet module into  /modules
>>> directory.
>>>
>>> 7. Create a symlink to wso2 hiera-files.
>>>
   /wso2/hieradata/dev/wso2/wso2 ->
 ../hieradata/dev/wso2/
>>>
>>>
>>> Once the setup.sh completes, users can copy product pack and jdk
>>> distribution for relevant folders and run vagrant setup against
>>> above-created puppet home.
>>>
>>> We are planning to automate the copying of product pack, jdk
>>> distribution and starting vagrant setup as well.
>>>
>>> Setup.sh can be found at [1]. Please share your suggestions towards
>>> this approach.
>>>
>>> [1] https://github.com/wso2/puppet-common/blob/master/setup.sh
>>>
>>> --
>>> *Thanks and Regards,*
>>> Anuruddha Lanka Liyanarachchi
>>> Software Engineer - WSO2
>>> Mobile : +94 (0) 712762611
>>> Tel  : +94 112 145 345
>>> a nurudd...@wso2.com
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>



 --
 *Imesh Gunaratne*

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

2016-09-19 Thread Malintha Fernando

Hi all,

Thank you for the inputs. it was RabbitMq running. I was a bit confused
when 1.9 started without an issue.

Thanks,

On Mon, Sep 19, 2016 at 1:08 PM, Abimaran Kugathasan 
wrote:

> I guess, you are running RabbitMQ on your node [1], you need to kill that
> process
>
> [1] : http://stackoverflow.com/questions/12792856/what-ports-
> does-rabbitmq-use
>
> On Mon, Sep 19, 2016 at 1:03 PM, Lakshman Udayakantha 
> wrote:
>
>> Hi Malintha,
>>
>> It says Address already in use. According to exception 5672 port is using
>> some another application. close that application and try again.
>>
>> Thanks
>>
>> On Mon, Sep 19, 2016 at 12:55 PM, Malintha Fernando 
>> wrote:
>>
>>> Hi All,
>>>
>>> Following errors are being thrown when I try to start a wso2am-2.0.0
>>> fresh pack. Tried using port offset but got no success. No other wso2
>>> products were running and wso2am-1.9.1 started without any issues. Are
>>> there any configurations that I need to do prior running APIM 2.0 that I
>>> have missed? I am using Ubuntu 16.04.
>>>
>>> org.wso2.andes.kernel.AndesException: Unable to initialise application
>>> registry
>>> at org.wso2.andes.server.Broker.startupImpl(Broker.java:308)
>>> at org.wso2.andes.server.Broker.startup(Broker.java:110)
>>> at org.wso2.andes.server.Main.startBroker(Main.java:217)
>>> at org.wso2.andes.server.Main.execute(Main.java:206)
>>> at org.wso2.andes.server.Main.(Main.java:54)
>>> at org.wso2.andes.server.Main.main(Main.java:47)
>>> at org.wso2.carbon.andes.internal.QpidServiceComponent.startAnd
>>> esBroker(QpidServiceComponent.java:420)
>>> at org.wso2.carbon.andes.internal.QpidServiceComponent.activate
>>> (QpidServiceComponent.java:165)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:57)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>>> ate(ServiceComponent.java:260)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>>> ctivate(ServiceComponentProp.java:146)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>>> uild(ServiceComponentProp.java:345)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>>> nt(InstanceProcess.java:620)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>>> nts(InstanceProcess.java:197)
>>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>>> r.java:343)
>>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>>> RManager.java:222)
>>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
>>> tener.serviceChanged(FilteredServiceListener.java:107)
>>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
>>> ispatchEvent(BundleContextImpl.java:861)
>>> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
>>> nt(EventManager.java:230)
>>> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv
>>> entSynchronous(ListenerQueue.java:148)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>>> blishServiceEventPrivileged(ServiceRegistry.java:819)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>>> blishServiceEvent(ServiceRegistry.java:771)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistratio
>>> nImpl.register(ServiceRegistrationImpl.java:130)
>>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.re
>>> gisterService(ServiceRegistry.java:214)
>>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>>> egisterService(BundleContextImpl.java:433)
>>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>>> egisterService(BundleContextImpl.java:451)
>>> at org.wso2.carbon.server.admin.internal.ServerAdminServiceComp
>>> onent.activate(ServerAdminServiceComponent.java:106)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:57)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>>> ate(ServiceComponent.java:260)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>>> ctivate(ServiceComponentProp.java:146)
>>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>>> uild(ServiceComponentProp.java:345)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>>> nt(InstanceProcess.java:620)
>>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

2016-09-19 Thread Abimaran Kugathasan

I guess, you are running RabbitMQ on your node [1], you need to kill that
process

[1] :
http://stackoverflow.com/questions/12792856/what-ports-does-rabbitmq-use

On Mon, Sep 19, 2016 at 1:03 PM, Lakshman Udayakantha 
wrote:

> Hi Malintha,
>
> It says Address already in use. According to exception 5672 port is using
> some another application. close that application and try again.
>
> Thanks
>
> On Mon, Sep 19, 2016 at 12:55 PM, Malintha Fernando 
> wrote:
>
>> Hi All,
>>
>> Following errors are being thrown when I try to start a wso2am-2.0.0
>> fresh pack. Tried using port offset but got no success. No other wso2
>> products were running and wso2am-1.9.1 started without any issues. Are
>> there any configurations that I need to do prior running APIM 2.0 that I
>> have missed? I am using Ubuntu 16.04.
>>
>> org.wso2.andes.kernel.AndesException: Unable to initialise application
>> registry
>> at org.wso2.andes.server.Broker.startupImpl(Broker.java:308)
>> at org.wso2.andes.server.Broker.startup(Broker.java:110)
>> at org.wso2.andes.server.Main.startBroker(Main.java:217)
>> at org.wso2.andes.server.Main.execute(Main.java:206)
>> at org.wso2.andes.server.Main.(Main.java:54)
>> at org.wso2.andes.server.Main.main(Main.java:47)
>> at org.wso2.carbon.andes.internal.QpidServiceComponent.startAnd
>> esBroker(QpidServiceComponent.java:420)
>> at org.wso2.carbon.andes.internal.QpidServiceComponent.activate
>> (QpidServiceComponent.java:165)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:57)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>> ate(ServiceComponent.java:260)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>> ctivate(ServiceComponentProp.java:146)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>> uild(ServiceComponentProp.java:345)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nt(InstanceProcess.java:620)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nts(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>> r.java:343)
>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>> RManager.java:222)
>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
>> tener.serviceChanged(FilteredServiceListener.java:107)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d
>> ispatchEvent(BundleContextImpl.java:861)
>> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve
>> nt(EventManager.java:230)
>> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv
>> entSynchronous(ListenerQueue.java:148)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>> blishServiceEventPrivileged(ServiceRegistry.java:819)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.pu
>> blishServiceEvent(ServiceRegistry.java:771)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistratio
>> nImpl.register(ServiceRegistrationImpl.java:130)
>> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.re
>> gisterService(ServiceRegistry.java:214)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>> egisterService(BundleContextImpl.java:433)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.r
>> egisterService(BundleContextImpl.java:451)
>> at org.wso2.carbon.server.admin.internal.ServerAdminServiceComp
>> onent.activate(ServerAdminServiceComponent.java:106)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:57)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponent.activ
>> ate(ServiceComponent.java:260)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.a
>> ctivate(ServiceComponentProp.java:146)
>> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.b
>> uild(ServiceComponentProp.java:345)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nt(InstanceProcess.java:620)
>> at org.eclipse.equinox.internal.ds.InstanceProcess.buildCompone
>> nts(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolve
>> r.java:343)
>> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>> RManager.java:222)
>> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceLis
>>

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

2016-09-19 Thread Thilini Cooray

Hi Malintha,

There is a "Address already in use" detected in the log.
Can you please try after killing the process?

Thanks.

On Mon, Sep 19, 2016 at 12:55 PM, Malintha Fernando 
wrote:

> Hi All,
>
> Following errors are being thrown when I try to start a wso2am-2.0.0 fresh
> pack. Tried using port offset but got no success. No other wso2 products
> were running and wso2am-1.9.1 started without any issues. Are there any
> configurations that I need to do prior running APIM 2.0 that I have missed?
> I am using Ubuntu 16.04.
>
> org.wso2.andes.kernel.AndesException: Unable to initialise application
> registry
> at org.wso2.andes.server.Broker.startupImpl(Broker.java:308)
> at org.wso2.andes.server.Broker.startup(Broker.java:110)
> at org.wso2.andes.server.Main.startBroker(Main.java:217)
> at org.wso2.andes.server.Main.execute(Main.java:206)
> at org.wso2.andes.server.Main.(Main.java:54)
> at org.wso2.andes.server.Main.main(Main.java:47)
> at org.wso2.carbon.andes.internal.QpidServiceComponent.
> startAndesBroker(QpidServiceComponent.java:420)
> at org.wso2.carbon.andes.internal.QpidServiceComponent.
> activate(QpidServiceComponent.java:165)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(
> InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(
> Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
> SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.
> serviceChanged(FilteredServiceListener.java:107)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> dispatchEvent(BundleContextImpl.java:861)
> at org.eclipse.osgi.framework.eventmgr.EventManager.
> dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.
> dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEventPrivileged(ServiceRegistry.java:819)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEvent(ServiceRegistry.java:771)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.
> register(ServiceRegistrationImpl.java:130)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> registerService(ServiceRegistry.java:214)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> registerService(BundleContextImpl.java:433)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> registerService(BundleContextImpl.java:451)
> at org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.
> activate(ServerAdminServiceComponent.java:106)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(
> InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(
> Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
> SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.
> serviceChanged(FilteredServiceListener.java:107)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> dispatchEvent(BundleContextImpl.java:861)
> at org.eclipse.osgi.framework.eventmgr.EventManager.
> dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.
> dispatchEventSynchronous(ListenerQueue.java:148)
> at

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

2016-09-19 Thread Nuwan Dias

Its an address already in use for port 5672. When you offset the server, do
you get the same error for the offsetted port?

Could there be a process that wasn't properly killed earlier which is still
holding up the port?

On Mon, Sep 19, 2016 at 12:55 PM, Malintha Fernando 
wrote:

> Hi All,
>
> Following errors are being thrown when I try to start a wso2am-2.0.0 fresh
> pack. Tried using port offset but got no success. No other wso2 products
> were running and wso2am-1.9.1 started without any issues. Are there any
> configurations that I need to do prior running APIM 2.0 that I have missed?
> I am using Ubuntu 16.04.
>
> org.wso2.andes.kernel.AndesException: Unable to initialise application
> registry
> at org.wso2.andes.server.Broker.startupImpl(Broker.java:308)
> at org.wso2.andes.server.Broker.startup(Broker.java:110)
> at org.wso2.andes.server.Main.startBroker(Main.java:217)
> at org.wso2.andes.server.Main.execute(Main.java:206)
> at org.wso2.andes.server.Main.(Main.java:54)
> at org.wso2.andes.server.Main.main(Main.java:47)
> at org.wso2.carbon.andes.internal.QpidServiceComponent.
> startAndesBroker(QpidServiceComponent.java:420)
> at org.wso2.carbon.andes.internal.QpidServiceComponent.
> activate(QpidServiceComponent.java:165)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(
> InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(
> Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
> SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.
> serviceChanged(FilteredServiceListener.java:107)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> dispatchEvent(BundleContextImpl.java:861)
> at org.eclipse.osgi.framework.eventmgr.EventManager.
> dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.
> dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEventPrivileged(ServiceRegistry.java:819)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEvent(ServiceRegistry.java:771)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.
> register(ServiceRegistrationImpl.java:130)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> registerService(ServiceRegistry.java:214)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> registerService(BundleContextImpl.java:433)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> registerService(BundleContextImpl.java:451)
> at org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.
> activate(ServerAdminServiceComponent.java:106)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(
> InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(
> Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
> SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.
> serviceChanged(FilteredServiceListener.java:107)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> dispatchEvent(BundleContextImpl.java:861)
> at org.eclipse.osgi.framework.eventmgr.EventManager.
> dispatchEvent(EventManager.java:230)
> at

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

2016-09-19 Thread Lakshman Udayakantha

Hi Malintha,

It says Address already in use. According to exception 5672 port is using
some another application. close that application and try again.

Thanks

On Mon, Sep 19, 2016 at 12:55 PM, Malintha Fernando 
wrote:

> Hi All,
>
> Following errors are being thrown when I try to start a wso2am-2.0.0 fresh
> pack. Tried using port offset but got no success. No other wso2 products
> were running and wso2am-1.9.1 started without any issues. Are there any
> configurations that I need to do prior running APIM 2.0 that I have missed?
> I am using Ubuntu 16.04.
>
> org.wso2.andes.kernel.AndesException: Unable to initialise application
> registry
> at org.wso2.andes.server.Broker.startupImpl(Broker.java:308)
> at org.wso2.andes.server.Broker.startup(Broker.java:110)
> at org.wso2.andes.server.Main.startBroker(Main.java:217)
> at org.wso2.andes.server.Main.execute(Main.java:206)
> at org.wso2.andes.server.Main.(Main.java:54)
> at org.wso2.andes.server.Main.main(Main.java:47)
> at org.wso2.carbon.andes.internal.QpidServiceComponent.
> startAndesBroker(QpidServiceComponent.java:420)
> at org.wso2.carbon.andes.internal.QpidServiceComponent.
> activate(QpidServiceComponent.java:165)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(
> InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(
> Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
> SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.
> serviceChanged(FilteredServiceListener.java:107)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> dispatchEvent(BundleContextImpl.java:861)
> at org.eclipse.osgi.framework.eventmgr.EventManager.
> dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.
> dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEventPrivileged(ServiceRegistry.java:819)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> publishServiceEvent(ServiceRegistry.java:771)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.
> register(ServiceRegistrationImpl.java:130)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.
> registerService(ServiceRegistry.java:214)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> registerService(BundleContextImpl.java:433)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> registerService(BundleContextImpl.java:451)
> at org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.
> activate(ServerAdminServiceComponent.java:106)
> 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.eclipse.equinox.internal.ds.model.ServiceComponent.
> activate(ServiceComponent.java:260)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> activate(ServiceComponentProp.java:146)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.
> build(ServiceComponentProp.java:345)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(
> InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(
> InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(
> Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(
> SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.
> serviceChanged(FilteredServiceListener.java:107)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
> dispatchEvent(BundleContextImpl.java:861)
> at org.eclipse.osgi.framework.eventmgr.EventManager.
> dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.
>

[Dev] Exceptions while starting up WSO2 AM 2.0.0

2016-09-19 Thread Malintha Fernando

Hi All,

Following errors are being thrown when I try to start a wso2am-2.0.0 fresh
pack. Tried using port offset but got no success. No other wso2 products
were running and wso2am-1.9.1 started without any issues. Are there any
configurations that I need to do prior running APIM 2.0 that I have missed?
I am using Ubuntu 16.04.

org.wso2.andes.kernel.AndesException: Unable to initialise application
registry
at org.wso2.andes.server.Broker.startupImpl(Broker.java:308)
at org.wso2.andes.server.Broker.startup(Broker.java:110)
at org.wso2.andes.server.Main.startBroker(Main.java:217)
at org.wso2.andes.server.Main.execute(Main.java:206)
at org.wso2.andes.server.Main.(Main.java:54)
at org.wso2.andes.server.Main.main(Main.java:47)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.startAndesBroker(QpidServiceComponent.java:420)
at
org.wso2.carbon.andes.internal.QpidServiceComponent.activate(QpidServiceComponent.java:165)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.server.admin.internal.ServerAdminServiceComponent.activate(ServerAdminServiceComponent.java:106)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at

Re: [Dev] Why not ship creator and publisher roles pre-built in API-M?

2016-09-19 Thread Malintha Amarasinghe

Hi Lahiru,

Thanks for the response.

On Mon, Sep 19, 2016 at 11:27 AM, Lahiru Cooray  wrote:

> Hi Malintha,
> Is there a use case to make these internal roles configurable?
> IMHO, since we are using these internal roles in our code level logics, we
> could make it mandatory (role creation + assignment of default permissions)
> without introducing another config parameter.
>
> Actually we are using internally in code are not role names, but
permissions. So we have the flexibility to change any associated roles with
correct permissions. Permissions are not changed or configurable. Yes
majority would not need to change them and it would add another config..
but in case if someone want to change the default names OR does not want to
create those roles at all etc, he would not have an option if we do not
make it configurable..

Thanks!

>
>
> On Thu, Sep 15, 2016 at 2:54 PM, Malintha Amarasinghe 
> wrote:
>
>> Hi,
>>
>> Adding this by default will give lots of benefits for automation testing
>> as well..
>>
>> Shall we have a config in api-manager.xml to specify these roles? If so
>> are we adding it under  element? However  is
>> where Publisher web app specific configurations resides. But publisher and
>> creator roles are not really specific to Publisher web app as they will be
>> used in REST APIs as well. So what would be the best place to add this
>> configuration? Under  or under a new config.. may be
>> ?
>>
>> Thanks!
>> Malintha
>>
>> On Wed, Sep 14, 2016 at 1:18 PM, Samisa Abeysinghe 
>> wrote:
>>
>>>
>>> On Wed, Sep 14, 2016 at 10:24 AM, Uvindra Dias Jayasinha <
>>> uvin...@wso2.com> wrote:
>>>
 Thats a good point Samisa.

 We have the subscriber role by default because we need it to set the
 permissions for users that sign up from the API store. All other user
 creations need to happen through the carbon admin console anyway so I guess
 we havent added those other roles by default.

 But I see no reason why we cannot have these roles already created to
 make it easier for the end user.

>>>
>>> +1
>>> 
>>>


 On 14 September 2016 at 08:57, Samisa Abeysinghe 
 wrote:

> We ship subscriber role with proper permissions set.
>
> https://docs.wso2.com/display/AM200/Adding+User+Roles describes
> creator and publisher roles.
> But the vanilla product does not have them.
>
> Why not create and ship them with proper permissions pre-set? Why only
> subscriber role?
>
> Thanks,
> Samisa...
>
>
> Samisa Abeysinghe
>
> Vice President Delivery
>
> WSO2 Inc.
> http://wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Regards,
 Uvindra

 Mobile: 33962

>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>



-- 
Malintha Amarasinghe
Software Engineer
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

Mobile : +94 712383306
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Query about the SSO in the WSO

2016-09-19 Thread wenxzhen

Git it. Cheers. 

Kind Regards, Wenxing

-- Original --
From:  "Abimaran Kugathasan";;
Send time: Monday, Sep 19, 2016 2:17 PM
To: "wenxzhen"; 
Cc: "Thusitha Thilina Dayaratne"; "dev"; 
Subject:  Re: [Dev] Query about the SSO in the WSO

Hi Wenxing,

You can use the Java Documentation for carbon kernel 4.4.6 or 4.4.7 [1], since 
there won't be any API changes from 4.4.1 to 4.4.6 or 4.4.7. We don't have Java 
Documentation for 4.4.1 at the moment.

[1] : 
http://product-dist.wso2.com/javadocs/carbon/4.4.6/user-mgt/index.html?overview-summary.html

On Mon, Sep 19, 2016 at 10:56 AM, wenxzhen  wrote:
Hi Thusitha,

I can't open the link: 
http://product-dist.wso2.com/javadocs/carbon/4.4.1/user-mgt/index.html?overview-summary.html.

Is there any API docs for Carbon 4.4.1?

Thanks, Wenxing

-- Original --
From:  "Thusitha Thilina Dayaratne";;
Send time: Monday, Sep 19, 2016 1:48 PM
To: "wenxzhen"; 
Cc: "dev"; 
Subject:  Re: [Dev] Query about the SSO in the WSO

Hi Wenxing,

BTW: I found we have API Java docs for Carbon 4.4.6/4.4.7 
(http://product-dist.wso2.com/javadocs/carbon/4.4.6/user-mgt/index.html?overview-summary.html),
 But I wan't able to find the ones for the older version. Any hints?WSO2 AS 
5.3.0 uses carbon kernel 4.4.1. But you won't be able to find the javadocs for 
the particular carbon kernel version. But since these are patch releases there 
aren't any API changes in the existing API. Therefore ideally you should be 
able to refer the latest docs without any issue.

Please do let us know if you find any issues with that.

Thanks
Thusitha

On Mon, Sep 19, 2016 at 10:36 AM, wenxzhen  wrote:
Thanks to Malith. Will check further what the application have to provide for 
the SSO based authentication.

BTW: I found we have API Java docs for Carbon 4.4.6/4.4.7 
(http://product-dist.wso2.com/javadocs/carbon/4.4.6/user-mgt/index.html?overview-summary.html),
 But I wan't able to find the ones for the older version. Any hints?

Kind Regards, Wenxing

-- Original --
From:  "Malith Munasinghe";;
Send time: Monday, Sep 19, 2016 12:46 PM
To: "wenxzhen"; 
Cc: "dev"; 
Subject:  Re: [Dev] Query about the SSO in the WSO

Hi Wenxing, 

In order to provide SSO based authentication for your applications. You can use 
SAMLSSOValve in WSO2 AS to integrate with WSO2 IS as in the documentation 
provided in [1]

[1] https://docs.wso2.com/display/AS530/Using+SSO+with+Web+Applications

Regards,
Malith

On Mon, Sep 19, 2016 at 7:13 AM, wenxzhen  wrote:
Appreciated if anyone can shed some light on my question.

Thanks,
Wenxing

-- Original --
From:  "wenxzhen";;
Date:  Sep 18, 2016
To:  "dev"; 

Subject:  [Dev] Query about the SSO in the WSO

Dear gurus,

Would like to know more details on the Single Sign On implemented in the WSO2? 
How it's being implemented?

And if I wanna use this feature with the example architecture diagram below, 
what I have to do? 

Thanks for the advice
Regards, Wenxing

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

-- 
Malith Munasinghe | Software Engineer
M: +94 (71) 9401122
E: mali...@wso2.com
W: http://wso2.com

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

-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809

Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina

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

-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820

FBD1D92D@E9E06970.1E7FDF57
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] All ESB service calls with data

[Dev] All ESB service calls with data

Re: [Dev] [APIM] Where I can find the source code for Admin Dashboard in API Manager

Re: [Dev] [APIM] Where I can find the source code for Admin Dashboard in API Manager

[Dev] [APIM] Where I can find the source code for Admin Dashboard in API Manager

[Dev] Need documentation for saml-cloud inbound authenticators

Re: [Dev] API Manager - periodic failure of OAuth2Service for AccessTokens via the publisher API

[Dev] API Manager - periodic failure of OAuth2Service for AccessTokens via the publisher API

Re: [Dev] [puppet] Setting up puppet home from script

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

Re: [Dev] Exceptions while starting up WSO2 AM 2.0.0

[Dev] Exceptions while starting up WSO2 AM 2.0.0

Re: [Dev] Why not ship creator and publisher roles pre-built in API-M?

Re: [Dev] Query about the SSO in the WSO

17 matches

Site Navigation

Mail list logo

Footer information