Re: [Dev] Is there a way to switch transport method at API Manager startup?
Hi Ruwan Test automation framework has provided the ability to change the axis2.xml(carbon.xml, etc..) at the time of test execution. You can use ServerConfigurationManager class to do the configuration changes. Following steps can be used to change the axis2.xml file 1) keep your custom axis2.xml file in test resources 2) call the method serverConfigurationManager.applyConfiguration($PATH/axis2.xml) then it will backup the current axis2.xml file and copy your axis2.xml file to the server. then server is restated to get affect of the configuration after that you can execute your test 3) after your test is finished, call serverConfigurationManager.restoreToLastConfiguration(); it will delete the custom axis2.xml and copy the original axis2.xml file and server is restated . then server is in original state. no other test get affected your configurations. Please refer ESB integration test. we have implement many test scenarios with custom axis2.xml files. Thanks, Nuwanw On Tue, Apr 2, 2013 at 10:07 AM, Ruwan Yatawara ruw...@wso2.com wrote: Thannks Azeez! I believe that approach should be feasible for us. @ Krishanthan the reason behind having two axis2.xmls is that at the moement, API Manager multi tenancy is enabled via NIO transport only, but by default we want the API Manager pack to feature Pass-throuh transpgort. Therefore, we want to switch the axis2.xml at server start up before running the Jmeter Automation script to test the multi-tenancy features. Regards, Ruwan On Tue, Apr 2, 2013 at 12:21 AM, Afkham Azeez az...@wso2.com wrote: If you want to maintain multiple axis2.xml files for convenience, then have them named as axis2-pt.xml, axis2-nio.xml and so on, and have a symbolic link names axis2.xml, and switch that link to point to the correct file before starting up the server. Azeez On Mon, Apr 1, 2013 at 7:49 PM, Ruwan Yatawara ruw...@wso2.com wrote: Hi All, We have a requirement to change the transport mechanism for API Manager on start up (I.e. switch from Pass through to NIO), hence is there a way to to specify which axis2.xml to use, when starting up the server? (like there us for synapse.xml) Thanks, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 www: :http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Committers += Amila De Silva
Hi, Thank you very much for this great opportunity and I will continue contributing my best in future too. AmilaD On Tue, Apr 2, 2013 at 10:05 AM, Nuwan Dias nuw...@wso2.com wrote: Hi, All-MC has voted in Amila De Silva as a WSO2 committer. He has been an excellent contributor for the WSO2 API Manager and other related projects over the last few months. AmilaD, welcome aboard and keep up the good work. Thanks, NuwanD. -- Nuwan Dias Software Engineer - 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] Is there a way to switch transport method at API Manager startup?
On Tue, Apr 2, 2013 at 11:32 AM, Nuwan Wimalasekara nuw...@wso2.com wrote: Hi Ruwan Test automation framework has provided the ability to change the axis2.xml(carbon.xml, etc..) at the time of test execution. You can use ServerConfigurationManager class to do the configuration changes. Following steps can be used to change the axis2.xml file 1) keep your custom axis2.xml file in test resources 2) call the method serverConfigurationManager.applyConfiguration($PATH/axis2.xml) then it will backup the current axis2.xml file and copy your axis2.xml file to the server. then server is restated to get affect of the configuration after that you can execute your test 3) after your test is finished, call serverConfigurationManager.restoreToLastConfiguration(); it will delete the custom axis2.xml and copy the original axis2.xml file and server is restated . then server is in original state. no other test get affected your configurations. Please refer ESB integration test. we have implement many test scenarios with custom axis2.xml files. I think this approach is the best way of doing this as this is test specific change. Thanks, Sanjeewa.. Thanks, Nuwanw On Tue, Apr 2, 2013 at 10:07 AM, Ruwan Yatawara ruw...@wso2.com wrote: Thannks Azeez! I believe that approach should be feasible for us. @ Krishanthan the reason behind having two axis2.xmls is that at the moement, API Manager multi tenancy is enabled via NIO transport only, but by default we want the API Manager pack to feature Pass-throuh transpgort. Therefore, we want to switch the axis2.xml at server start up before running the Jmeter Automation script to test the multi-tenancy features. Regards, Ruwan On Tue, Apr 2, 2013 at 12:21 AM, Afkham Azeez az...@wso2.com wrote: If you want to maintain multiple axis2.xml files for convenience, then have them named as axis2-pt.xml, axis2-nio.xml and so on, and have a symbolic link names axis2.xml, and switch that link to point to the correct file before starting up the server. Azeez On Mon, Apr 1, 2013 at 7:49 PM, Ruwan Yatawara ruw...@wso2.com wrote: Hi All, We have a requirement to change the transport mechanism for API Manager on start up (I.e. switch from Pass through to NIO), hence is there a way to to specify which axis2.xml to use, when starting up the server? (like there us for synapse.xml) Thanks, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 www: :http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +14084122175 | +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ANN] WSO2 Developer Studio 3.1.0 Released!
WSO2 Developer Studio team is pleased to announce the general availability (GA) of WSO2 Developer Studio 3.1.0 WSO2 Developer Studio IDE provides a Complete Composite Application Development Tooling Platform for award winning WSO2 Carbon Middleware platform as well as for popular open source projects, Apache Tomcat, Apache Synapse, Apache Axis2, Apache CXF, etc is now available to download at [1]. This release consists with following New features, Improvements and bug fixes. New Feature - [TOOLS-1375 https://wso2.org/jira/browse/TOOLS-1375] - Migrate Dev Studio from Helios SR2 to Juno SR2 Improvements - [TOOLS-1258 https://wso2.org/jira/browse/TOOLS-1258] - Provide a wizard to create JAX-RS services from WADL. - [TOOLS-1592 https://wso2.org/jira/browse/TOOLS-1592] - Implement extension based approach to address ESB artifact creation initialization slowness on Windows. - [TOOLS-1607 https://wso2.org/jira/browse/TOOLS-1607] - Document update for creating Jaxrs service project using wadl Bug fixes - [TOOLS-1223 https://wso2.org/jira/browse/TOOLS-1223] - Double click action does not show the selected visual objects properties. - [TOOLS-1353 https://wso2.org/jira/browse/TOOLS-1353] - arrayName attribute dose not supported in Element mapping element. - [TOOLS-1474 https://wso2.org/jira/browse/TOOLS-1474] - ESB sample 255 does not deserialize since it out path contain address endpoint. - [TOOLS-1151 https://wso2.org/jira/browse/TOOLS-1151] - In cache mediator if no id value is specified, id= is added by default - [TOOLS-1348 https://wso2.org/jira/browse/TOOLS-1348] - Shipped Account service sample cannot be exported as a working Axis2 archive - [TOOLS-1593 https://wso2.org/jira/browse/TOOLS-1593] - Template creation wizard unusable when going to create address endpoint template. - [TOOLS-1594 https://wso2.org/jira/browse/TOOLS-1594] - Can not parameterized templates created by developer studio.(No mechanism to add/edit/remove parameters.) - [TOOLS-1612 https://wso2.org/jira/browse/TOOLS-1612] - Create a New Task Artifact is not allowed to have a trigger count 0 - [TOOLS-1615 https://wso2.org/jira/browse/TOOLS-1615] - BPEL Project contains HelloWorld files for all 3 models in windows - [TOOLS-1616 https://wso2.org/jira/browse/TOOLS-1616] - Always have to clean install when building DevS ESB project with Maven We highly appreciate you feedback on WSO2 Developer Studio! Please report all the issues you find in WSO2 Developer Studio 3.1.0 in Tools Jira at [2] against the version 3.1.0. [1] - http://wso2.com/products/developer-studio/ [2] - https://wso2.org/jira/browse/TOOLS Thanks and Regards, The WSO2 Developer Studio Team. -- *Jasintha Dasanayake **Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware* * * *mobile :- 077 291 6596* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ANN] WSO2 Developer Studio 3.1.0 Released!
So, does this mean Developer Studio 3.1.0 inherently supports Eclipse Indigo too? On Tue, Apr 2, 2013 at 2:48 AM, Jasintha Dasanayake jasin...@wso2.comwrote: WSO2 Developer Studio team is pleased to announce the general availability (GA) of WSO2 Developer Studio 3.1.0 WSO2 Developer Studio IDE provides a Complete Composite Application Development Tooling Platform for award winning WSO2 Carbon Middleware platform as well as for popular open source projects, Apache Tomcat, Apache Synapse, Apache Axis2, Apache CXF, etc is now available to download at [1]. This release consists with following New features, Improvements and bug fixes. New Feature - [TOOLS-1375 https://wso2.org/jira/browse/TOOLS-1375] - Migrate Dev Studio from Helios SR2 to Juno SR2 Improvements - [TOOLS-1258 https://wso2.org/jira/browse/TOOLS-1258] - Provide a wizard to create JAX-RS services from WADL. - [TOOLS-1592 https://wso2.org/jira/browse/TOOLS-1592] - Implement extension based approach to address ESB artifact creation initialization slowness on Windows. - [TOOLS-1607 https://wso2.org/jira/browse/TOOLS-1607] - Document update for creating Jaxrs service project using wadl Bug fixes - [TOOLS-1223 https://wso2.org/jira/browse/TOOLS-1223] - Double click action does not show the selected visual objects properties. - [TOOLS-1353 https://wso2.org/jira/browse/TOOLS-1353] - arrayName attribute dose not supported in Element mapping element. - [TOOLS-1474 https://wso2.org/jira/browse/TOOLS-1474] - ESB sample 255 does not deserialize since it out path contain address endpoint. - [TOOLS-1151 https://wso2.org/jira/browse/TOOLS-1151] - In cache mediator if no id value is specified, id= is added by default - [TOOLS-1348 https://wso2.org/jira/browse/TOOLS-1348] - Shipped Account service sample cannot be exported as a working Axis2 archive - [TOOLS-1593 https://wso2.org/jira/browse/TOOLS-1593] - Template creation wizard unusable when going to create address endpoint template. - [TOOLS-1594 https://wso2.org/jira/browse/TOOLS-1594] - Can not parameterized templates created by developer studio.(No mechanism to add/edit/remove parameters.) - [TOOLS-1612 https://wso2.org/jira/browse/TOOLS-1612] - Create a New Task Artifact is not allowed to have a trigger count 0 - [TOOLS-1615 https://wso2.org/jira/browse/TOOLS-1615] - BPEL Project contains HelloWorld files for all 3 models in windows - [TOOLS-1616 https://wso2.org/jira/browse/TOOLS-1616] - Always have to clean install when building DevS ESB project with Maven We highly appreciate you feedback on WSO2 Developer Studio! Please report all the issues you find in WSO2 Developer Studio 3.1.0 in Tools Jira at [2] against the version 3.1.0. [1] - http://wso2.com/products/developer-studio/ [2] - https://wso2.org/jira/browse/TOOLS Thanks and Regards, The WSO2 Developer Studio Team. -- *Jasintha Dasanayake **Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware* * * *mobile :- 077 291 6596* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ANN] WSO2 Developer Studio 3.1.0 Released!
Hi Nirmal, On Tue, Apr 2, 2013 at 1:23 PM, Nirmal Fernando nir...@wso2.com wrote: So, does this mean Developer Studio 3.1.0 inherently supports Eclipse Indigo too? No. Dev Studio 3.1.0 does not support Helios or Indigo because we have migrated the dependencies to Juno SR2 which are incompatible with Eclipse Helios and Indigo. Thanks and Regards, Harshana On Tue, Apr 2, 2013 at 2:48 AM, Jasintha Dasanayake jasin...@wso2.comwrote: WSO2 Developer Studio team is pleased to announce the general availability (GA) of WSO2 Developer Studio 3.1.0 WSO2 Developer Studio IDE provides a Complete Composite Application Development Tooling Platform for award winning WSO2 Carbon Middleware platform as well as for popular open source projects, Apache Tomcat, Apache Synapse, Apache Axis2, Apache CXF, etc is now available to download at [1]. This release consists with following New features, Improvements and bug fixes. New Feature - [TOOLS-1375 https://wso2.org/jira/browse/TOOLS-1375] - Migrate Dev Studio from Helios SR2 to Juno SR2 Improvements - [TOOLS-1258 https://wso2.org/jira/browse/TOOLS-1258] - Provide a wizard to create JAX-RS services from WADL. - [TOOLS-1592 https://wso2.org/jira/browse/TOOLS-1592] - Implement extension based approach to address ESB artifact creation initialization slowness on Windows. - [TOOLS-1607 https://wso2.org/jira/browse/TOOLS-1607] - Document update for creating Jaxrs service project using wadl Bug fixes - [TOOLS-1223 https://wso2.org/jira/browse/TOOLS-1223] - Double click action does not show the selected visual objects properties. - [TOOLS-1353 https://wso2.org/jira/browse/TOOLS-1353] - arrayName attribute dose not supported in Element mapping element. - [TOOLS-1474 https://wso2.org/jira/browse/TOOLS-1474] - ESB sample 255 does not deserialize since it out path contain address endpoint. - [TOOLS-1151 https://wso2.org/jira/browse/TOOLS-1151] - In cache mediator if no id value is specified, id= is added by default - [TOOLS-1348 https://wso2.org/jira/browse/TOOLS-1348] - Shipped Account service sample cannot be exported as a working Axis2 archive - [TOOLS-1593 https://wso2.org/jira/browse/TOOLS-1593] - Template creation wizard unusable when going to create address endpoint template. - [TOOLS-1594 https://wso2.org/jira/browse/TOOLS-1594] - Can not parameterized templates created by developer studio.(No mechanism to add/edit/remove parameters.) - [TOOLS-1612 https://wso2.org/jira/browse/TOOLS-1612] - Create a New Task Artifact is not allowed to have a trigger count 0 - [TOOLS-1615 https://wso2.org/jira/browse/TOOLS-1615] - BPEL Project contains HelloWorld files for all 3 models in windows - [TOOLS-1616 https://wso2.org/jira/browse/TOOLS-1616] - Always have to clean install when building DevS ESB project with Maven We highly appreciate you feedback on WSO2 Developer Studio! Please report all the issues you find in WSO2 Developer Studio 3.1.0 in Tools Jira at [2] against the version 3.1.0. [1] - http://wso2.com/products/developer-studio/ [2] - https://wso2.org/jira/browse/TOOLS Thanks and Regards, The WSO2 Developer Studio Team. -- *Jasintha Dasanayake **Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware* * * *mobile :- 077 291 6596* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harshana Martin Senior Software Engineer Member, Management Committee - Development Technologies WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error while starting BAM with API-M toolbox.
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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
[Dev] [4.1.1] - Build Error - BPEL Core Component
Hi BPS team I am getting the following error when building on a fresh repo. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 26:26.929s [INFO] Finished at: Tue Apr 02 13:24:49 IST 2013 [INFO] Final Memory: 312M/978M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.bpel: Could not resolve dependencies for project org.wso2.carbon:org.wso2.carbon.bpel:bundle:4.1.1: Failed to collect dependencies for [org.wso2.carbon:org.wso2.carbon.bpel.cluster.notifier:jar:4.1.1 (compile), org.wso2.carbon:org.wso2.carbon.bpel.common:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.attachment.mgt:jar:4.1.1 (compile), org.apache.axis2.wso2:axis2:jar:1.6.1.wso2v9 (compile), org.wso2.carbon:org.wso2.carbon.core:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.application.deployer:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.utils:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.datasource:jar:4.1.0 (compile), org.apache.ode.wso2:ode:jar:1.3.5.wso2v7 (compile), org.wso2.carbon:org.wso2.carbon.security.mgt:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.logging:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.application.deployer.bpel:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.unifiedendpoint.core:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.service.mgt:jar:4.1.0 (compile), org.wso2.carbon:org.wso2.carbon.bpel.skeleton:jar:4.1.0 (compile), hsqldb.wso2:hsqldb:jar:1.8.0.7wso2v1 (compile)]: Failed to read artifact descriptor for org.apache.rampart.wso2:rampart-core:jar:1.6.1.wso2v9: Could not find artifact org.wso2.carbon:carbon-dependents:pom:4.1.0-SNAPSHOT in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -- *Isuru Wimalasundera* Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 77 920 5641 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while starting BAM with API-M toolbox.
More errors when the task runs.
[2013-04-02 14:38:00,004] INFO
{org.wso2.carbon.analytics.hive.task.HiveScriptExecutorTask} - Running
script executor task for script am_stats_analyzer_115. [Tue Apr 02 14:38:00
IST 2013]
Hive history
file=/Users/azeez/software/wso2bam-2.2.0/tmp/hive/wso2-querylogs/hive_job_log_azeez_201304021436_493388221.txt
[2013-04-02 14:38:00,207] ERROR
{org.apache.hadoop.hive.cassandra.CassandraProxyClient} - Error while
trying to connect to cassandra host:127.0.0.1
org.apache.hadoop.hive.cassandra.CassandraException: unable to connect to
server
at
org.apache.hadoop.hive.cassandra.CassandraClientHolder.initClient(CassandraClientHolder.java:57)
at
org.apache.hadoop.hive.cassandra.CassandraClientHolder.init(CassandraClientHolder.java:37)
at
org.apache.hadoop.hive.cassandra.CassandraProxyClient.createConnection(CassandraProxyClient.java:181)
at
org.apache.hadoop.hive.cassandra.CassandraProxyClient.initializeConnection(CassandraProxyClient.java:207)
at
org.apache.hadoop.hive.cassandra.CassandraProxyClient.init(CassandraProxyClient.java:144)
at
org.apache.hadoop.hive.cassandra.CassandraManager.openConnection(CassandraManager.java:113)
at
org.apache.hadoop.hive.cassandra.CassandraStorageHandler.preCreateTable(CassandraStorageHandler.java:168)
at
org.apache.hadoop.hive.metastore.HiveMetaStoreClient.createTable(HiveMetaStoreClient.java:397)
at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:540)
at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:3479)
at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:225)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:133)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1351)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1126)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:934)
at
org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.execute(HiveServer.java:201)
at
org.apache.hadoop.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:187)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:317)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:217)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
Caused by: org.apache.thrift.transport.TTransportException:
java.net.ConnectException: Connection refused
at org.apache.thrift.transport.TSocket.open(TSocket.java:183)
at
org.apache.thrift.transport.TFramedTransport.open(TFramedTransport.java:81)
at
org.apache.hadoop.hive.cassandra.CassandraClientHolder.initClient(CassandraClientHolder.java:54)
... 24 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:432)
at java.net.Socket.connect(Socket.java:529)
at org.apache.thrift.transport.TSocket.open(TSocket.java:178)
... 26 more
FAILED: Error in metadata: java.lang.NullPointerException
[2013-04-02 14:38:00,209] ERROR {org.apache.hadoop.hive.ql.exec.Task} -
FAILED: Error in metadata: java.lang.NullPointerException
org.apache.hadoop.hive.ql.metadata.HiveException:
java.lang.NullPointerException
at org.apache.hadoop.hive.ql.metadata.Hive.createTable(Hive.java:546)
at org.apache.hadoop.hive.ql.exec.DDLTask.createTable(DDLTask.java:3479)
at org.apache.hadoop.hive.ql.exec.DDLTask.execute(DDLTask.java:225)
at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:133)
at
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:57)
at org.apache.hadoop.hive.ql.Driver.launchTask(Driver.java:1351)
at org.apache.hadoop.hive.ql.Driver.execute(Driver.java:1126)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:934)
at
org.apache.hadoop.hive.service.HiveServer$HiveServerHandler.execute(HiveServer.java:201)
at
org.apache.hadoop.hive.jdbc.HiveStatement.executeQuery(HiveStatement.java:187)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:317)
at
org.wso2.carbon.analytics.hive.impl.HiveExecutorServiceImpl$ScriptCallable.call(HiveExecutorServiceImpl.java:217)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
[Dev] BAM: wso2server.sh -DportOffset does not work in BAM?
$subject Looks like we are forced to edit the carbon.xml file and set the offset. Is this crrect? If so why has this platform best practice not been followed? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API-M: Documentation on configuring connecting to BAM?
I am getting the following error while starting API Manager after
configuring API usage monitoring
[2013-04-02 14:54:55,636] ERROR - APIMgtUsageDataBridgeDataPublisher Error
initializing APIMgtUsageDataBridgeDataPublisher
org.wso2.carbon.databridge.agent.thrift.exception.AgentException: Cannot
define type { 'name':'org.wso2.apimgt.statistics.response',
'version':'1.0.0', 'nickName': 'API Manager Reponse Data',
'description': 'Response Data', 'metaData':[
{'name':'clientType','type':'STRING'} ], 'payloadData':[
{'name':'consumerKey','type':'STRING'},
{'name':'context','type':'STRING'},
{'name':'api_version','type':'STRING'},
{'name':'api','type':'STRING'},
{'name':'resource','type':'STRING'},
{'name':'method','type':'STRING'},
{'name':'version','type':'STRING'},
{'name':'response','type':'INT'},
{'name':'responseTime','type':'LONG'},
{'name':'serviceTime','type':'LONG'},
{'name':'userId','type':'STRING'} ]}
at
org.wso2.carbon.databridge.agent.thrift.internal.publisher.client.EventPublisher.defineStream(EventPublisher.java:234)
On Tue, Apr 2, 2013 at 7:48 AM, Lalaji Sureshika lal...@wso2.com wrote:
Hi,
You can find the related wiki documentation from [1] for AM 1.3.1.
Agree,current showing text [when no stats available] will not much help
from users-perspective.Currently Chamath is working on improving Stats
pages of the publisher app.Will take your point,to improve that text while
his effort on improving stats page..
@Chamath -Please note..
Thanks;
[1] http://docs.wso2.org/wiki/display/AM131/Monitoring+and+Statistics
On Mon, Apr 1, 2013 at 11:17 PM, Afkham Azeez az...@wso2.com wrote:
Folks,
Where can I find these docs? What needs to be done to enable API stats.
When you go to stats, there is some text which says that BAM is not
properly setup. It would be more useful if that text also points to the
docs which show how to setup configure BAM for API Manager.
Azeez
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Lalaji Sureshika
Software Engineer; Development Technologies Team;WSO2, Inc.;
http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while starting BAM with API-M toolbox.
Yes we have tested bam 2.0.1 with AM 1.3.1 and worked fine.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 3:13 PM, Afkham Azeez az...@wso2.com wrote:
Yes, BAM 2.2.0. So, if I use an older version of BAM will it work?
On Tue, Apr 2, 2013 at 2:58 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi Azeez,
Its seems you are using BAM 2.2.0. There were known bug in integrating AM
1.4.0 and BAM 2.2.0. BAM team identified the reason for that and they will
fix it for next release. But the errors reported by you are bit different
with what we got. We will investigate more and update thread.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:35 PM, Afkham Azeez az...@wso2.com wrote:
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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] BAM: wso2server.sh -DportOffset does not work in BAM?
Port offset has to be obtained from the CarbonUtil class. There is a method there. If you use that standard method, it will always give the correct portOffset. This is what the well-behaved components have used. Azeez On Tue, Apr 2, 2013 at 3:28 PM, Sinthuja Ragendran sinth...@wso2.comwrote: I tested the BAM 2.2.0 with -DportOffset and seems like only http and https ports are getting changed when starting with -DportOffset and thrift port, cassandra port, etc is not getting changed. After further digging into the code, I see we are getting the port offset from ServerConfigurationService which is set as OSGI service and that is not returning the correct offset value. Is there anything wrong here? Thanks, Sinthuja. On Tue, Apr 2, 2013 at 2:47 PM, Afkham Azeez az...@wso2.com wrote: $subject Looks like we are forced to edit the carbon.xml file and set the offset. Is this crrect? If so why has this platform best practice not been followed? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- *Sinthuja Rajendran* Software Engineer http://wso2.com/ WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955 -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] 4.1.1 Branch - Build Error - Invalid dependency version in rampart-core at Nexus
Hi All In a previous mail [4.1.1] - Build Error - BPEL Core Component , I have reported a build error due to given below reason. Failed to read artifact descriptor for org.apache.rampart.wso2: rampart-core:jar:1.6.1.wso2v9: Could not find artifact org.wso2.carbon:carbon-dependents:pom:4.1.0-SNAPSHOT in wso2-nexus ( http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] Even though this version is correct in branch the dependency version is wrong at http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/rampart/wso2/rampart-core/1.6.1.wso2v9/rampart-core-1.6.1.wso2v9.pom, therefor on a fresh repo with an online build we face this error. Please be kind to correct this. Thanks Isuruw -- *Isuru Wimalasundera* Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 77 920 5641 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] BAM: wso2server.sh -DportOffset does not work in BAM?
When defining any ports in Carbon, there is a recommended way of doing it.
Some time back, we decided that it should be possible for a user to change
all relevant ports from a single location. That is why we have the Ports
section in the carbon.xml file. Once you define a new port, it should be
overridable from the carbon.xml.
Here is the ports section
Ports
106
107 !-- Ports offset. This entry will set the value of the ports
defined below to
108 the define value + Offset.
109 e.g. Offset=2 and HTTPS port=9443 will set the effective HTTPS
port to 9445
110 --
111 Offset0/Offset
112
113 !-- The JMX Ports --
114 JMX
115 !--The port RMI registry is exposed--
116 RMIRegistryPort/RMIRegistryPort
117 !--The port RMI server should be exposed--
118 RMIServerPort1/RMIServerPort
119 /JMX
120
121 !-- Embedded LDAP server specific ports --
122 EmbeddedLDAP
123 !-- Port which embedded LDAP server runs --
124 LDAPServerPort10389/LDAPServerPort
125 !-- Port which KDC (Kerberos Key Distribution Center)
server runs --
126 KDCServerPort8000/KDCServerPort
127 /EmbeddedLDAP
128
129 !-- Embedded Qpid broker ports --
130 EmbeddedQpid
131 !-- Broker TCP Port --
132 BrokerPort5672/BrokerPort
133 !-- SSL Port --
134 BrokerSSLPort8672/BrokerSSLPort
135 /EmbeddedQpid
136
137 !--
138 Override datasources JNDIproviderPort defined in bps.xml
and datasources.properties files
139 --
140 !--JNDIProviderPort2199/JNDIProviderPort--
141 !--Override receive port of thrift based entitlement
service.--
142
ThriftEntitlementReceivePort10500/ThriftEntitlementReceivePort
143
144 /Ports
So, when these ports are defined in the relevant file, you are supposed to
use the keys, e.g. JMX.RMIRegistryPort is defined in the jmx.xml file,
instead of a hard coded port. Now you have to use the below CarbonUtil
method to get the proper port along with the portOffset.
Here is the relevant method in CarbonUtils.
/**
* This is to read the port values defined in other config files,
which are overridden
* from those in carbon.xml.
* @param property
* @return
*/
public static int getPortFromServerConfig(String property) {
String port;
int portNumber = -1;
int indexOfStartingChars = -1;
int indexOfClosingBrace;
ServerConfiguration serverConfiguration =
ServerConfiguration.getInstance();
// The following condition deals with ports specified to be
read from carbon.xml.
// Ports are specified as templates: eg
${Ports.EmbeddedLDAP.LDAPServerPort},
if (indexOfStartingChars property.indexOf(${)
(indexOfStartingChars = property.indexOf(${)) != -1
(indexOfClosingBrace = property.indexOf('}')) != -1) { //
Is this template used?
String portTemplate = property.substring(indexOfStartingChars + 2,
indexOfClosingBrace);
port = serverConfiguration.getFirstProperty(portTemplate);
if (port != null) {
portNumber = Integer.parseInt(port);
}
}
String portOffset = System.getProperty(portOffset,
serverConfiguration.getFirstProperty(Ports.Offset));
//setting up port offset properties as system global property
which allows this
//to available at the other context as required (fix 2011-11-30)
System.setProperty(portOffset, portOffset);
return portOffset == null? portNumber : portNumber +
Integer.parseInt(portOffset);
}
On Tue, Apr 2, 2013 at 3:31 PM, Afkham Azeez az...@wso2.com wrote:
Port offset has to be obtained from the CarbonUtil class. There is a
method there. If you use that standard method, it will always give the
correct portOffset. This is what the well-behaved components have used.
Azeez
On Tue, Apr 2, 2013 at 3:28 PM, Sinthuja Ragendran sinth...@wso2.comwrote:
I tested the BAM 2.2.0 with -DportOffset and seems like only http and
https ports are getting changed when starting with -DportOffset and thrift
port, cassandra port, etc is not getting changed.
After further digging into the code, I see we are getting the port
offset from ServerConfigurationService which is set as OSGI service and
that is not returning the correct offset value. Is there anything wrong
here?
Thanks,
Sinthuja.
On Tue, Apr 2, 2013 at 2:47 PM, Afkham Azeez az...@wso2.com wrote:
$subject
Looks like we are forced to edit the carbon.xml file and set the offset.
Is this crrect? If so why has this platform best practice not been followed?
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
Re: [Dev] BAM: wso2server.sh -DportOffset does not work in BAM?
Thanks for detailed explanation. I'll update all BAM related components
(data-bridge, cassandra) to use the above CarbonUtil method to get the port
offset.
Thanks,
Sinthuja.
On Tue, Apr 2, 2013 at 3:38 PM, Afkham Azeez az...@wso2.com wrote:
When defining any ports in Carbon, there is a recommended way of doing it.
Some time back, we decided that it should be possible for a user to change
all relevant ports from a single location. That is why we have the Ports
section in the carbon.xml file. Once you define a new port, it should be
overridable from the carbon.xml.
Here is the ports section
Ports
106
107 !-- Ports offset. This entry will set the value of the ports
defined below to
108 the define value + Offset.
109 e.g. Offset=2 and HTTPS port=9443 will set the effective
HTTPS port to 9445
110 --
111 Offset0/Offset
112
113 !-- The JMX Ports --
114 JMX
115 !--The port RMI registry is exposed--
116 RMIRegistryPort/RMIRegistryPort
117 !--The port RMI server should be exposed--
118 RMIServerPort1/RMIServerPort
119 /JMX
120
121 !-- Embedded LDAP server specific ports --
122 EmbeddedLDAP
123 !-- Port which embedded LDAP server runs --
124 LDAPServerPort10389/LDAPServerPort
125 !-- Port which KDC (Kerberos Key Distribution Center)
server runs --
126 KDCServerPort8000/KDCServerPort
127 /EmbeddedLDAP
128
129 !-- Embedded Qpid broker ports --
130 EmbeddedQpid
131 !-- Broker TCP Port --
132 BrokerPort5672/BrokerPort
133 !-- SSL Port --
134 BrokerSSLPort8672/BrokerSSLPort
135 /EmbeddedQpid
136
137 !--
138 Override datasources JNDIproviderPort defined in bps.xml
and datasources.properties files
139 --
140 !--JNDIProviderPort2199/JNDIProviderPort--
141 !--Override receive port of thrift based entitlement
service.--
142
ThriftEntitlementReceivePort10500/ThriftEntitlementReceivePort
143
144 /Ports
So, when these ports are defined in the relevant file, you are supposed to
use the keys, e.g. JMX.RMIRegistryPort is defined in the jmx.xml file,
instead of a hard coded port. Now you have to use the below CarbonUtil
method to get the proper port along with the portOffset.
Here is the relevant method in CarbonUtils.
/**
* This is to read the port values defined in other config files, which
are overridden
* from those in carbon.xml.
* @param property
* @return
*/
public static int getPortFromServerConfig(String property) {
String port;
int portNumber = -1;
int indexOfStartingChars = -1;
int indexOfClosingBrace;
ServerConfiguration serverConfiguration =
ServerConfiguration.getInstance();
// The following condition deals with ports specified to be read from
carbon.xml.
// Ports are specified as templates: eg
${Ports.EmbeddedLDAP.LDAPServerPort},
if (indexOfStartingChars property.indexOf(${)
(indexOfStartingChars = property.indexOf(${)) != -1
(indexOfClosingBrace = property.indexOf('}')) != -1) { // Is this
template used?
String portTemplate = property.substring(indexOfStartingChars + 2,
indexOfClosingBrace);
port = serverConfiguration.getFirstProperty(portTemplate);
if (port != null) {
portNumber = Integer.parseInt(port);
}
}
String portOffset = System.getProperty(portOffset,
serverConfiguration.getFirstProperty(Ports.Offset));
//setting up port offset properties as system global property which
allows this
//to available at the other context as required (fix 2011-11-30)
System.setProperty(portOffset, portOffset);
return portOffset == null? portNumber : portNumber +
Integer.parseInt(portOffset);
}
On Tue, Apr 2, 2013 at 3:31 PM, Afkham Azeez az...@wso2.com wrote:
Port offset has to be obtained from the CarbonUtil class. There is a
method there. If you use that standard method, it will always give the
correct portOffset. This is what the well-behaved components have used.
Azeez
On Tue, Apr 2, 2013 at 3:28 PM, Sinthuja Ragendran sinth...@wso2.comwrote:
I tested the BAM 2.2.0 with -DportOffset and seems like only http and
https ports are getting changed when starting with -DportOffset and thrift
port, cassandra port, etc is not getting changed.
After further digging into the code, I see we are getting the port
offset from ServerConfigurationService which is set as OSGI service and
that is not returning the correct offset value. Is there anything wrong
[Dev] Deprecating Jaggery Jira for issue tracking and using GitHub Issue Tracker as the default
Hi All, We will be deprecating Jira [1] and will be using GitHub issue tracker[2] for future jaggery release management work Regards, /Nuwan [1] https://wso2.org/jira/browse/JAGGERY [2] https://github.com/wso2/jaggery/issues/ -- *Thanks Regards, Nuwan Bandara Associate Technical Lead Member, MC, Development Technologies WSO2 Inc. - lean . enterprise . middleware | http://wso2.com blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 9629 * http://www.nuwanbando.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] 4.1.1 Branch - Build Error - Invalid dependency version in rampart-core at Nexus
Hi IsuruW, As I see, the rampart-core point to correct carbon-dependents version which is 4.1.0 not 4.1.0-SNAPSHOTS. In the pom file you have pointed in your mail, I see the below parent pom definition. Can you open the same pom from your local repo and make sure that file contains the same parent definition or another? parent groupIdorg.wso2.carbon/groupId artifactIdcarbon-dependents/artifactId version4.1.0/version relativePath../../../pom.xml/relativePath /parent groupIdorg.apache.rampart.wso2/groupId artifactIdrampart-core/artifactId packagingbundle/packaging On Tue, Apr 2, 2013 at 3:37 PM, Isuru Wimalasundera isu...@wso2.com wrote: Hi All In a previous mail [4.1.1] - Build Error - BPEL Core Component , I have reported a build error due to given below reason. Failed to read artifact descriptor for org.apache.rampart.wso2: rampart-core:jar:1.6.1.wso2v9: Could not find artifact org.wso2.carbon:carbon-dependents:pom:4.1.0-SNAPSHOT in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] Even though this version is correct in branch the dependency version is wrong at http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/rampart/wso2/rampart-core/1.6.1.wso2v9/rampart-core-1.6.1.wso2v9.pom , therefor on a fresh repo with an online build we face this error. Please be kind to correct this. Thanks Isuruw -- Isuru Wimalasundera Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 77 920 5641 -- Kasun Gajasinghe Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , email: kasung AT spamfree wso2.com cell: +94 (77) 678-0813 linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org twitter: http://twitter.com/kasunbg ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] 4.1.1 Branch - Build Error - Invalid dependency version in rampart-core at Nexus
Hi Kasun Yes , as I said inside platform/dependencies/orbit the rampart core pom does have the correct version, But on a fresh repo when building online this refers to http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/rampart/wso2/rampart-core/1.6.1.wso2v9/rampart-core-1.6.1.wso2v9.pomwhich has a SNAPSHOT version. as given below. project xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; parent groupIdorg.wso2.carbon/groupId artifactIdcarbon-dependents/artifactId version4.1.0-SNAPSHOT/version relativePath../../pom.xml/relativePath /parent On Tue, Apr 2, 2013 at 3:46 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi IsuruW, As I see, the rampart-core point to correct carbon-dependents version which is 4.1.0 not 4.1.0-SNAPSHOTS. In the pom file you have pointed in your mail, I see the below parent pom definition. Can you open the same pom from your local repo and make sure that file contains the same parent definition or another? parent groupIdorg.wso2.carbon/groupId artifactIdcarbon-dependents/artifactId version4.1.0/version relativePath../../../pom.xml/relativePath /parent groupIdorg.apache.rampart.wso2/groupId artifactIdrampart-core/artifactId packagingbundle/packaging On Tue, Apr 2, 2013 at 3:37 PM, Isuru Wimalasundera isu...@wso2.com wrote: Hi All In a previous mail [4.1.1] - Build Error - BPEL Core Component , I have reported a build error due to given below reason. Failed to read artifact descriptor for org.apache.rampart.wso2: rampart-core:jar:1.6.1.wso2v9: Could not find artifact org.wso2.carbon:carbon-dependents:pom:4.1.0-SNAPSHOT in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) - [Help 1] Even though this version is correct in branch the dependency version is wrong at http://maven.wso2.org/nexus/content/groups/wso2-public/org/apache/rampart/wso2/rampart-core/1.6.1.wso2v9/rampart-core-1.6.1.wso2v9.pom , therefor on a fresh repo with an online build we face this error. Please be kind to correct this. Thanks Isuruw -- Isuru Wimalasundera Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 77 920 5641 -- Kasun Gajasinghe Software Engineer; Development Technologies Team, WSO2 Inc.; http://wso2.com , email: kasung AT spamfree wso2.com cell: +94 (77) 678-0813 linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org twitter: http://twitter.com/kasunbg -- *Isuru Wimalasundera* Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 77 920 5641 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Is there a way to switch transport method at API Manager startup?
Thnaks Nuwan Sanjeewa, I made the change in the above mentioned manner and added a patch. Thanks for the guidance! Regards, Ruwan On Tue, Apr 2, 2013 at 11:45 AM, Sanjeewa Malalgoda sanje...@wso2.comwrote: On Tue, Apr 2, 2013 at 11:32 AM, Nuwan Wimalasekara nuw...@wso2.comwrote: Hi Ruwan Test automation framework has provided the ability to change the axis2.xml(carbon.xml, etc..) at the time of test execution. You can use ServerConfigurationManager class to do the configuration changes. Following steps can be used to change the axis2.xml file 1) keep your custom axis2.xml file in test resources 2) call the method serverConfigurationManager.applyConfiguration($PATH/axis2.xml) then it will backup the current axis2.xml file and copy your axis2.xml file to the server. then server is restated to get affect of the configuration after that you can execute your test 3) after your test is finished, call serverConfigurationManager.restoreToLastConfiguration(); it will delete the custom axis2.xml and copy the original axis2.xml file and server is restated . then server is in original state. no other test get affected your configurations. Please refer ESB integration test. we have implement many test scenarios with custom axis2.xml files. I think this approach is the best way of doing this as this is test specific change. Thanks, Sanjeewa.. Thanks, Nuwanw On Tue, Apr 2, 2013 at 10:07 AM, Ruwan Yatawara ruw...@wso2.com wrote: Thannks Azeez! I believe that approach should be feasible for us. @ Krishanthan the reason behind having two axis2.xmls is that at the moement, API Manager multi tenancy is enabled via NIO transport only, but by default we want the API Manager pack to feature Pass-throuh transpgort. Therefore, we want to switch the axis2.xml at server start up before running the Jmeter Automation script to test the multi-tenancy features. Regards, Ruwan On Tue, Apr 2, 2013 at 12:21 AM, Afkham Azeez az...@wso2.com wrote: If you want to maintain multiple axis2.xml files for convenience, then have them named as axis2-pt.xml, axis2-nio.xml and so on, and have a symbolic link names axis2.xml, and switch that link to point to the correct file before starting up the server. Azeez On Mon, Apr 1, 2013 at 7:49 PM, Ruwan Yatawara ruw...@wso2.com wrote: Hi All, We have a requirement to change the transport mechanism for API Manager on start up (I.e. switch from Pass through to NIO), hence is there a way to to specify which axis2.xml to use, when starting up the server? (like there us for synapse.xml) Thanks, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 www: :http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Wimalasekara Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +14084122175 | +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Dev Studio 3.2.0 Branch available
Hi All, Please note the $Subject. When committing fixes, please make sure to commit your fixes to both 3.2.0 branch and Trunk. Thanks and Regards, Harshana -- Harshana Martin Senior Software Engineer Member, Management Committee - Development Technologies WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Hi, Great. I have review the patch attached to the Jira and committed as it resolved the XML encoding problem. thanks. On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* -- *Hasitha Abeykoon* Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com* * * * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Hi Ishara, This will be a very useful feature for MB. On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. However, as a topic browser, I'd love to see following information too. * Publisher's IP/port * Subscribers' IP/port, and the subscribers whom not yet received the message. * Message size Also, what is 'delivery mode' attribute? Is it something I configure? Is it possible to use the meaningful string interpretation instead of an integer? Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. MB uses Cassandra, right? Isn't it the right place to store data instead of memory? The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] BAM: wso2server.sh -DportOffset does not work in BAM?
I raised the same concern in dev@ Can't start BAM 2.0.2 server and a MB
2.0.1 server in a single machine (with different port offsets) :-)
Great, if you guys could fix.
On Tue, Apr 2, 2013 at 3:42 PM, Sinthuja Ragendran sinth...@wso2.comwrote:
Thanks for detailed explanation. I'll update all BAM related components
(data-bridge, cassandra) to use the above CarbonUtil method to get the port
offset.
Thanks,
Sinthuja.
On Tue, Apr 2, 2013 at 3:38 PM, Afkham Azeez az...@wso2.com wrote:
When defining any ports in Carbon, there is a recommended way of doing
it. Some time back, we decided that it should be possible for a user to
change all relevant ports from a single location. That is why we have the
Ports section in the carbon.xml file. Once you define a new port, it should
be overridable from the carbon.xml.
Here is the ports section
Ports
106
107 !-- Ports offset. This entry will set the value of the ports
defined below to
108 the define value + Offset.
109 e.g. Offset=2 and HTTPS port=9443 will set the effective
HTTPS port to 9445
110 --
111 Offset0/Offset
112
113 !-- The JMX Ports --
114 JMX
115 !--The port RMI registry is exposed--
116 RMIRegistryPort/RMIRegistryPort
117 !--The port RMI server should be exposed--
118 RMIServerPort1/RMIServerPort
119 /JMX
120
121 !-- Embedded LDAP server specific ports --
122 EmbeddedLDAP
123 !-- Port which embedded LDAP server runs --
124 LDAPServerPort10389/LDAPServerPort
125 !-- Port which KDC (Kerberos Key Distribution Center)
server runs --
126 KDCServerPort8000/KDCServerPort
127 /EmbeddedLDAP
128
129 !-- Embedded Qpid broker ports --
130 EmbeddedQpid
131 !-- Broker TCP Port --
132 BrokerPort5672/BrokerPort
133 !-- SSL Port --
134 BrokerSSLPort8672/BrokerSSLPort
135 /EmbeddedQpid
136
137 !--
138 Override datasources JNDIproviderPort defined in bps.xml
and datasources.properties files
139 --
140 !--JNDIProviderPort2199/JNDIProviderPort--
141 !--Override receive port of thrift based entitlement
service.--
142
ThriftEntitlementReceivePort10500/ThriftEntitlementReceivePort
143
144 /Ports
So, when these ports are defined in the relevant file, you are supposed
to use the keys, e.g. JMX.RMIRegistryPort is defined in the jmx.xml file,
instead of a hard coded port. Now you have to use the below CarbonUtil
method to get the proper port along with the portOffset.
Here is the relevant method in CarbonUtils.
/**
* This is to read the port values defined in other config files, which
are overridden
* from those in carbon.xml.
* @param property
* @return
*/
public static int getPortFromServerConfig(String property) {
String port;
int portNumber = -1;
int indexOfStartingChars = -1;
int indexOfClosingBrace;
ServerConfiguration serverConfiguration =
ServerConfiguration.getInstance();
// The following condition deals with ports specified to be read
from carbon.xml.
// Ports are specified as templates: eg
${Ports.EmbeddedLDAP.LDAPServerPort},
if (indexOfStartingChars property.indexOf(${)
(indexOfStartingChars = property.indexOf(${)) != -1
(indexOfClosingBrace = property.indexOf('}')) != -1) { // Is
this template used?
String portTemplate = property.substring(indexOfStartingChars +
2,
indexOfClosingBrace);
port = serverConfiguration.getFirstProperty(portTemplate);
if (port != null) {
portNumber = Integer.parseInt(port);
}
}
String portOffset = System.getProperty(portOffset,
serverConfiguration.getFirstProperty(Ports.Offset));
//setting up port offset properties as system global property which
allows this
//to available at the other context as required (fix 2011-11-30)
System.setProperty(portOffset, portOffset);
return portOffset == null? portNumber : portNumber +
Integer.parseInt(portOffset);
}
On Tue, Apr 2, 2013 at 3:31 PM, Afkham Azeez az...@wso2.com wrote:
Port offset has to be obtained from the CarbonUtil class. There is a
method there. If you use that standard method, it will always give the
correct portOffset. This is what the well-behaved components have used.
Azeez
On Tue, Apr 2, 2013 at 3:28 PM, Sinthuja Ragendran sinth...@wso2.comwrote:
I tested the BAM 2.2.0 with -DportOffset and seems like only http and
https ports are getting changed when starting with -DportOffset and thrift
port,
[Dev] Kernel trunk - p2 profile build error
Hi Reka, Build failed at kernel/trunk/distribution/product/modules/p2-profile-gen. Looks like it may be due to the changes on multiple profile in kernel distribution. Can you please have a look? Installing org.wso2.carbon.styles.feature.group 4.1.0.SNAPSHOT. Installation failed. An error occurred while installing the items session context was:(profile=WSO2CarbonProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null -- [R]org.wso2.carbon.styles 4.1.0.SNAPSHOT, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). Error while loading manipulator. Caused by: Application failed, log file location: /home/kicha/mvnRepo/m3repo/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1364903487880.log *Error trace form the log file* !ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2013-04-02 17:21:30.952 !MESSAGE Error while loading manipulator. !STACK 0 java.lang.IllegalStateException: The framework persistent data location (/home/kicha/checkouts/wso2/carbon/kernel/trunk/distribution/kernel/target/WSO2Carbon/WSO2CarbonProfile/configuration) is not the same as the framework configuration location (/home/kicha/checkouts/wso2/carbon/kernel/trunk/distribution/product/modules/p2-profile-gen/target/wso2carbon-core-4.1.0-SNAPSHOT/repository/components/WSO2CarbonProfile/configuration). at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65) at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:348) Thanks, Kishanthan. -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Kernel trunk - p2 profile build error
Hi I have fixed it in r169864. Thanks, Reka On Tue, Apr 2, 2013 at 6:45 PM, Kishanthan Thangarajah kishant...@wso2.comwrote: Hi Reka, Build failed at kernel/trunk/distribution/product/modules/p2-profile-gen. Looks like it may be due to the changes on multiple profile in kernel distribution. Can you please have a look? Installing org.wso2.carbon.styles.feature.group 4.1.0.SNAPSHOT. Installation failed. An error occurred while installing the items session context was:(profile=WSO2CarbonProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null -- [R]org.wso2.carbon.styles 4.1.0.SNAPSHOT, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). Error while loading manipulator. Caused by: Application failed, log file location: /home/kicha/mvnRepo/m3repo/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1364903487880.log *Error trace form the log file* !ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2013-04-02 17:21:30.952 !MESSAGE Error while loading manipulator. !STACK 0 java.lang.IllegalStateException: The framework persistent data location (/home/kicha/checkouts/wso2/carbon/kernel/trunk/distribution/kernel/target/WSO2Carbon/WSO2CarbonProfile/configuration) is not the same as the framework configuration location (/home/kicha/checkouts/wso2/carbon/kernel/trunk/distribution/product/modules/p2-profile-gen/target/wso2carbon-core-4.1.0-SNAPSHOT/repository/components/WSO2CarbonProfile/configuration). at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65) at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:348) Thanks, Kishanthan. -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* -- Reka Thirunavukkarasu Software Engineer, WSO2, Inc.:http://wso2.com, ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Moving SubDomainAwareGroupManagementAgent into Axis2?
Hi Azeez, Do you think it's a good idea to move SubDomainAwareGroupManagementAgent into Axis2 (currently it's in lb-endpoint component) ? I felt like we have to use this implementation in various other components than lb-endpoint component for writing test cases etc. and currently we have to add an additional dependency for lb-endpoint component, to get that done. WDYT? -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Bamboo-Build] Developer Studio Eclipse-Tools #888 was SUCCESSFUL. Change made by Harshana Martin.
--- Developer Studio Eclipse-Tools #888 was successful. --- Code has been updated by Harshana Martin. http://wso2.org/bamboo/browse/DS0001-DSET01-888/ -- Code Changes -- Harshana Martin (169866): Reverting the P2 repo for build back to Helios since there are build failures from bpel.common.ui -- This message is automatically generated by Atlassian Bamboo___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Hi Nirmal, On Tue, Apr 2, 2013 at 6:37 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Ishara, This will be a very useful feature for MB. On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. However, as a topic browser, I'd love to see following information too. * Publisher's IP/port * Subscribers' IP/port, and the subscribers whom not yet received the message. * Message size Actually we are working on providing more features support for the MB admin console with the new release. However about a Topic browser, as i understand you can't browse the messages in a topic because they are sent to all subscribers immediately and don't get stored on the broker storage, unlike a queue where the messages are stored when receiver is offline. Therefore i don't think that we are able to get the message content published for a topic. May be Shammi or Hasitha can correct me if i am wrong :) Also, what is 'delivery mode' attribute? Is it something I configure? Is it possible to use the meaningful string interpretation instead of an integer? According to the JMS spec 'delivery mode' is for marking the message as PERSISTENT or NON_PERSISTENT [1]. By default JMS messages are made persistent ( stored in persistent storage to be delivered later if needed). The only accepted values are 1 and 2; 1- Non persistent 2- Persistent Hence we can't use any other value for this attribute when sending a message. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. MB uses Cassandra, right? Isn't it the right place to store data instead of memory? Yes the messages are in the storage. But the queue browser returns an enumeration of the content of a queue [2], in runtime, and if there are larger amount of messages in the queue (say 100,000) the enumeration loads this entire content into memory. This makes the server crashes. By default there are only 200 messages fetched, however if the user increases this value a lot, it fails. I think Hasitha is going to update the configuration documentation with proper 'Warnings' about these outcomes. Ishara [1] http://docs.oracle.com/javaee/6/api/javax/jms/DeliveryMode.html [2] http://docs.oracle.com/javaee/1.4/api/javax/jms/QueueBrowser.html#getEnumeration%28%29 The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Extension hook for deploying custom tenant artifacts
Hi, In any multi-tenanted carbon server, the tenant specific deployment directory structure (Ex: repository/tenants/1/axis2services) is always created when the tenant tries to deploy an artifact for the first time. Is there any possibility of having an extension hook for the deployment directory structure creation so that it could be used to deploy custom artifacts under a chosen directory structure? My use case is that I need to deploy a custom set of sequences under each tenant's synapse-configs/default/sequences directory. Thanks, NuwanD. -- Nuwan Dias Software Engineer - 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] Moving SubDomainAwareGroupManagementAgent into Axis2?
We can't move that. I think it also has tenancy related code. On Tue, Apr 2, 2013 at 7:31 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Azeez, Do you think it's a good idea to move SubDomainAwareGroupManagementAgent into Axis2 (currently it's in lb-endpoint component) ? I felt like we have to use this implementation in various other components than lb-endpoint component for writing test cases etc. and currently we have to add an additional dependency for lb-endpoint component, to get that done. WDYT? -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
On Tue, Apr 2, 2013 at 8:45 PM, Ishara Premadasa ish...@wso2.com wrote: Hi Nirmal, On Tue, Apr 2, 2013 at 6:37 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Ishara, This will be a very useful feature for MB. On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. However, as a topic browser, I'd love to see following information too. * Publisher's IP/port * Subscribers' IP/port, and the subscribers whom not yet received the message. * Message size Hi Nirmal, Thanks for giving us some idea on what the actual user expects from MB admin console. As Ishara mentioned , we ll not be able to implement a topic browser since messages will not be stored in the server when dealing with PUB/SUB mode. Any how we may be able to provide you the above subscriber details and ports. But at the moment we are in a feature freeze state since we are planing to release the product with 4.1.2 platform version. We ll add the above mentioned features in to our road map and they will be available with 3.0.0 version of MB. Thanks Shammi Actually we are working on providing more features support for the MB admin console with the new release. However about a Topic browser, as i understand you can't browse the messages in a topic because they are sent to all subscribers immediately and don't get stored on the broker storage, unlike a queue where the messages are stored when receiver is offline. Therefore i don't think that we are able to get the message content published for a topic. May be Shammi or Hasitha can correct me if i am wrong :) Also, what is 'delivery mode' attribute? Is it something I configure? Is it possible to use the meaningful string interpretation instead of an integer? According to the JMS spec 'delivery mode' is for marking the message as PERSISTENT or NON_PERSISTENT [1]. By default JMS messages are made persistent ( stored in persistent storage to be delivered later if needed). The only accepted values are 1 and 2; 1- Non persistent 2- Persistent Hence we can't use any other value for this attribute when sending a message. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. MB uses Cassandra, right? Isn't it the right place to store data instead of memory? Yes the messages are in the storage. But the queue browser returns an enumeration of the content of a queue [2], in runtime, and if there are larger amount of messages in the queue (say 100,000) the enumeration loads this entire content into memory. This makes the server crashes. By default there are only 200 messages fetched, however if the user increases this value a lot, it fails. I think Hasitha is going to update the configuration documentation with proper 'Warnings' about these outcomes. Ishara [1] http://docs.oracle.com/javaee/6/api/javax/jms/DeliveryMode.html [2] http://docs.oracle.com/javaee/1.4/api/javax/jms/QueueBrowser.html#getEnumeration%28%29 The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org
Re: [Dev] Moving SubDomainAwareGroupManagementAgent into Axis2?
Well, Azeez here's the class.. We can move right?
/**
* This GroupManagementAgent can handle group membership based on cluster
sub-domains.
*/
public class SubDomainAwareGroupManagementAgent extends
DefaultGroupManagementAgent {
private String subDomain;
public SubDomainAwareGroupManagementAgent(String subDomain) {
this.subDomain = subDomain;
}
@Override
public void applicationMemberAdded(Member member) {
String subDomain = member.getProperties().getProperty(subDomain);
if (subDomain == null || subDomain.equals(this.subDomain)) {
super.applicationMemberAdded(member);
}
}
@Override
public void applicationMemberRemoved(Member member) {
String subDomain = member.getProperties().getProperty(subDomain);
if (subDomain == null || subDomain.equals(this.subDomain)) {
super.applicationMemberRemoved(member);
}
}
}
On Tue, Apr 2, 2013 at 9:37 PM, Afkham Azeez az...@wso2.com wrote:
We can't move that. I think it also has tenancy related code.
On Tue, Apr 2, 2013 at 7:31 PM, Nirmal Fernando nir...@wso2.com wrote:
Hi Azeez,
Do you think it's a good idea to move
SubDomainAwareGroupManagementAgent into Axis2 (currently it's in
lb-endpoint component) ?
I felt like we have to use this implementation in various other
components than lb-endpoint component for writing test cases etc. and
currently we have to add an additional dependency for lb-endpoint
component, to get that done.
WDYT?
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Whoops guys... I'm sorry... Somehow I misread queue browser as topic browser, don't ask how :-) On Tue, Apr 2, 2013 at 10:02 PM, Shammi Jayasinghe sha...@wso2.com wrote: On Tue, Apr 2, 2013 at 8:45 PM, Ishara Premadasa ish...@wso2.com wrote: Hi Nirmal, On Tue, Apr 2, 2013 at 6:37 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Ishara, This will be a very useful feature for MB. On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.comwrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. However, as a topic browser, I'd love to see following information too. * Publisher's IP/port * Subscribers' IP/port, and the subscribers whom not yet received the message. * Message size Hi Nirmal, Thanks for giving us some idea on what the actual user expects from MB admin console. As Ishara mentioned , we ll not be able to implement a topic browser since messages will not be stored in the server when dealing with PUB/SUB mode. Any how we may be able to provide you the above subscriber details and ports. But at the moment we are in a feature freeze state since we are planing to release the product with 4.1.2 platform version. We ll add the above mentioned features in to our road map and they will be available with 3.0.0 version of MB. Thanks Shammi Actually we are working on providing more features support for the MB admin console with the new release. However about a Topic browser, as i understand you can't browse the messages in a topic because they are sent to all subscribers immediately and don't get stored on the broker storage, unlike a queue where the messages are stored when receiver is offline. Therefore i don't think that we are able to get the message content published for a topic. May be Shammi or Hasitha can correct me if i am wrong :) Also, what is 'delivery mode' attribute? Is it something I configure? Is it possible to use the meaningful string interpretation instead of an integer? According to the JMS spec 'delivery mode' is for marking the message as PERSISTENT or NON_PERSISTENT [1]. By default JMS messages are made persistent ( stored in persistent storage to be delivered later if needed). The only accepted values are 1 and 2; 1- Non persistent 2- Persistent Hence we can't use any other value for this attribute when sending a message. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. MB uses Cassandra, right? Isn't it the right place to store data instead of memory? Yes the messages are in the storage. But the queue browser returns an enumeration of the content of a queue [2], in runtime, and if there are larger amount of messages in the queue (say 100,000) the enumeration loads this entire content into memory. This makes the server crashes. By default there are only 200 messages fetched, however if the user increases this value a lot, it fails. I think Hasitha is going to update the configuration documentation with proper 'Warnings' about these outcomes. Ishara [1] http://docs.oracle.com/javaee/6/api/javax/jms/DeliveryMode.html [2] http://docs.oracle.com/javaee/1.4/api/javax/jms/QueueBrowser.html#getEnumeration%28%29 The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in :
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Yes, Shammi I understand, thanks for adding that to Road map. On Tue, Apr 2, 2013 at 10:07 PM, Nirmal Fernando nir...@wso2.com wrote: Whoops guys... I'm sorry... Somehow I misread queue browser as topic browser, don't ask how :-) On Tue, Apr 2, 2013 at 10:02 PM, Shammi Jayasinghe sha...@wso2.comwrote: On Tue, Apr 2, 2013 at 8:45 PM, Ishara Premadasa ish...@wso2.com wrote: Hi Nirmal, On Tue, Apr 2, 2013 at 6:37 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Ishara, This will be a very useful feature for MB. On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.comwrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. However, as a topic browser, I'd love to see following information too. * Publisher's IP/port * Subscribers' IP/port, and the subscribers whom not yet received the message. * Message size Hi Nirmal, Thanks for giving us some idea on what the actual user expects from MB admin console. As Ishara mentioned , we ll not be able to implement a topic browser since messages will not be stored in the server when dealing with PUB/SUB mode. Any how we may be able to provide you the above subscriber details and ports. But at the moment we are in a feature freeze state since we are planing to release the product with 4.1.2 platform version. We ll add the above mentioned features in to our road map and they will be available with 3.0.0 version of MB. Thanks Shammi Actually we are working on providing more features support for the MB admin console with the new release. However about a Topic browser, as i understand you can't browse the messages in a topic because they are sent to all subscribers immediately and don't get stored on the broker storage, unlike a queue where the messages are stored when receiver is offline. Therefore i don't think that we are able to get the message content published for a topic. May be Shammi or Hasitha can correct me if i am wrong :) Also, what is 'delivery mode' attribute? Is it something I configure? Is it possible to use the meaningful string interpretation instead of an integer? According to the JMS spec 'delivery mode' is for marking the message as PERSISTENT or NON_PERSISTENT [1]. By default JMS messages are made persistent ( stored in persistent storage to be delivered later if needed). The only accepted values are 1 and 2; 1- Non persistent 2- Persistent Hence we can't use any other value for this attribute when sending a message. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. MB uses Cassandra, right? Isn't it the right place to store data instead of memory? Yes the messages are in the storage. But the queue browser returns an enumeration of the content of a queue [2], in runtime, and if there are larger amount of messages in the queue (say 100,000) the enumeration loads this entire content into memory. This makes the server crashes. By default there are only 200 messages fetched, however if the user increases this value a lot, it fails. I think Hasitha is going to update the configuration documentation with proper 'Warnings' about these outcomes. Ishara [1] http://docs.oracle.com/javaee/6/api/javax/jms/DeliveryMode.html [2] http://docs.oracle.com/javaee/1.4/api/javax/jms/QueueBrowser.html#getEnumeration%28%29 The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ http://nirmalfdo.blogspot.com/ -- Ishara
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Hi Ishara/Shammi, This is really cool addition ! As a MB user I also have list of feature requests for web console :) 1.) Practically I have felt many time if we could have web based sender ( or Try-It) feature with MB. This means there should be web interface to send messages to a destination without creating any JMS client, it just a filling a HTML page with required data. ActiveMQ provide such a web interface[1] and very useful too. As an example take a look at this post[2] how I used ActiveMQ console to test Axis2 JMS transport without writing any client side code. In my POV we need to have similar but better Try-It or sender feature for MB. 2.) I believe we can provide following details per topic, WDYT ? Name Number Of Consumers Messages Enqueued Messages Dequeued 3.) It's better to have some XML indention on message content view. [1] - http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AJ4/qX1nr58yWJk/s1600/1.png [2] - http://ssagara.blogspot.com/2012/04/axis2-jms-transport-and-activemq.html Thanks ! On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Message deletion is a valuable feature too. Can we support it? On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Hi Sagara, On Tue, Apr 2, 2013 at 10:43 PM, Sagara Gunathunga sag...@wso2.com wrote: Hi Ishara/Shammi, This is really cool addition ! As a MB user I also have list of feature requests for web console :) 1.) Practically I have felt many time if we could have web based sender ( or Try-It) feature with MB. This means there should be web interface to send messages to a destination without creating any JMS client, it just a filling a HTML page with required data. ActiveMQ provide such a web interface[1] and very useful too. As an example take a look at this post[2] how I used ActiveMQ console to test Axis2 JMS transport without writing any client side code. In my POV we need to have similar but better Try-It or sender feature for MB. Thank you very much for these suggestions. Actually our next task is adding a 'Test Message Sending' feature for MB admin console[1]. As exactly you had mentioned, we hope to provide the ability to send a sample JMS message with setting the necessary parameters like in ActiveMQ. Hope to start this soon ASAP once we finalize the queue browser. 2.) I believe we can provide following details per topic, WDYT ? Name Number Of Consumers Messages Enqueued Messages Dequeued 3.) It's better to have some XML indention on message content view. Yes, the current message content view doesn't show the XML indentions properly when a user sends XML as content. I will try to fix this and get the proper indentation view. Thanks! [1] https://wso2.org/jira/browse/MB-139 [1] - http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AJ4/qX1nr58yWJk/s1600/1.png [2] - http://ssagara.blogspot.com/2012/04/axis2-jms-transport-and-activemq.html Thanks ! On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
On Tue, Apr 2, 2013 at 10:53 PM, Ishara Premadasa ish...@wso2.com wrote: Hi Sagara, On Tue, Apr 2, 2013 at 10:43 PM, Sagara Gunathunga sag...@wso2.comwrote: Hi Ishara/Shammi, This is really cool addition ! As a MB user I also have list of feature requests for web console :) 1.) Practically I have felt many time if we could have web based sender ( or Try-It) feature with MB. This means there should be web interface to send messages to a destination without creating any JMS client, it just a filling a HTML page with required data. ActiveMQ provide such a web interface[1] and very useful too. As an example take a look at this post[2] how I used ActiveMQ console to test Axis2 JMS transport without writing any client side code. In my POV we need to have similar but better Try-It or sender feature for MB. Thank you very much for these suggestions. Actually our next task is adding a 'Test Message Sending' feature for MB admin console[1]. As exactly you had mentioned, we hope to provide the ability to send a sample JMS message with setting the necessary parameters like in ActiveMQ. Hope to start this soon ASAP once we finalize the queue browser. Great ! Nice to hear that. 2.) I believe we can provide following details per topic, WDYT ? Name Number Of Consumers Messages Enqueued Messages Dequeued 3.) It's better to have some XML indention on message content view. Yes, the current message content view doesn't show the XML indentions properly when a user sends XML as content. I will try to fix this and get the proper indentation view. Thanks! [1] https://wso2.org/jira/browse/MB-139 [1] - http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AJ4/qX1nr58yWJk/s1600/1.png [2] - http://ssagara.blogspot.com/2012/04/axis2-jms-transport-and-activemq.html Thanks ! On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.com wrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Stratos2] Exception in S2 Agent
Any idea of this exception ?
This is occurred in S2 Agent side ...
[2013-04-02 17:42:33,468] ERROR
{org.apache.axis2.clustering.tribes.Axis2GroupChannel} - Unable to
deserialize
message:ClusterData[src=org.apache.catalina.tribes.membership.MemberImpl[tcp://{10,
68, 202, 233}:4000,{10, 68, 202, 233},4000, alive=1364923740091,
securePort=-1, UDP Port=-1, id={0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 },
payload={35 10 35 84 117 101 32 65 112 ...(61)}, command={}, domain={119
115 111 50 46 99 97 114 98 ...(21)}, ]; id={-105 13 38 105 73 43 74 45 -89
94 -73 -65 -66 -101 90 -113 }; sent=2013-04-02 17:42:33.363]
java.lang.ClassNotFoundException:
org.wso2.carbon.mediator.autoscale.lbautoscale.replication.RequestTokenReplicationCommand
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:601)
at
org.apache.catalina.tribes.io.ReplicationStream.resolveClass(ReplicationStream.java:79)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1493)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1729)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.group.RpcMessage.readExternal(RpcMessage.java:64)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1795)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1754)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.io.XByteBuffer.deserialize(XByteBuffer.java:568)
at
org.apache.axis2.clustering.tribes.Axis2GroupChannel.messageReceived(Axis2GroupChannel.java:60)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.messageReceived(NonBlockingCoordinator.java:512)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor.messageReceived(TcpPingInterceptor.java:162)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:113)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.DomainFilterInterceptor.messageReceived(DomainFilterInterceptor.java:45)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:253)
at
org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:287)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:212)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:101)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
--
Regards,
*
*
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.; http://wso2.com*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Stratos2] Exception in S2 Agent
Seems like S2 Agent is not bundled correctly. You need to add
mediator-autoscale bundle in S2 Agent's p2 profile.
On Tue, Apr 2, 2013 at 11:18 PM, Sajith Kariyawasam saj...@wso2.com wrote:
Any idea of this exception ?
This is occurred in S2 Agent side ...
[2013-04-02 17:42:33,468] ERROR
{org.apache.axis2.clustering.tribes.Axis2GroupChannel} - Unable to
deserialize
message:ClusterData[src=org.apache.catalina.tribes.membership.MemberImpl[tcp://{10,
68, 202, 233}:4000,{10, 68, 202, 233},4000, alive=1364923740091,
securePort=-1, UDP Port=-1, id={0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 },
payload={35 10 35 84 117 101 32 65 112 ...(61)}, command={}, domain={119
115 111 50 46 99 97 114 98 ...(21)}, ]; id={-105 13 38 105 73 43 74 45 -89
94 -73 -65 -66 -101 90 -113 }; sent=2013-04-02 17:42:33.363]
java.lang.ClassNotFoundException:
org.wso2.carbon.mediator.autoscale.lbautoscale.replication.RequestTokenReplicationCommand
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:601)
at
org.apache.catalina.tribes.io.ReplicationStream.resolveClass(ReplicationStream.java:79)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1493)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1729)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.group.RpcMessage.readExternal(RpcMessage.java:64)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1795)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1754)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.io.XByteBuffer.deserialize(XByteBuffer.java:568)
at
org.apache.axis2.clustering.tribes.Axis2GroupChannel.messageReceived(Axis2GroupChannel.java:60)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.messageReceived(NonBlockingCoordinator.java:512)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor.messageReceived(TcpPingInterceptor.java:162)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:113)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.DomainFilterInterceptor.messageReceived(DomainFilterInterceptor.java:45)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:253)
at
org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:287)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:212)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:101)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
--
Regards,
*
*
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.; http://wso2.com*
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Providing queue browser support in WSO2 MB admin console
Hi, It is nice to have feed-backs. 1. As Ishara says, tryit feature will be available with MB 2.1.0 release. 2. Message deletion will be nice to have. But JMS spec does not mention about deleting messages. When you get messages from queue with AUTO ACK mode messages will be auto deleted. BTW, Websphere MQ support that feature (selective delete) by their implementation. We will consider on adding that feature for MB 3.0.0. Thanks. On Tue, Apr 2, 2013 at 10:55 PM, Sagara Gunathunga sag...@wso2.com wrote: On Tue, Apr 2, 2013 at 10:53 PM, Ishara Premadasa ish...@wso2.com wrote: Hi Sagara, On Tue, Apr 2, 2013 at 10:43 PM, Sagara Gunathunga sag...@wso2.comwrote: Hi Ishara/Shammi, This is really cool addition ! As a MB user I also have list of feature requests for web console :) 1.) Practically I have felt many time if we could have web based sender ( or Try-It) feature with MB. This means there should be web interface to send messages to a destination without creating any JMS client, it just a filling a HTML page with required data. ActiveMQ provide such a web interface[1] and very useful too. As an example take a look at this post[2] how I used ActiveMQ console to test Axis2 JMS transport without writing any client side code. In my POV we need to have similar but better Try-It or sender feature for MB. Thank you very much for these suggestions. Actually our next task is adding a 'Test Message Sending' feature for MB admin console[1]. As exactly you had mentioned, we hope to provide the ability to send a sample JMS message with setting the necessary parameters like in ActiveMQ. Hope to start this soon ASAP once we finalize the queue browser. Great ! Nice to hear that. 2.) I believe we can provide following details per topic, WDYT ? Name Number Of Consumers Messages Enqueued Messages Dequeued 3.) It's better to have some XML indention on message content view. Yes, the current message content view doesn't show the XML indentions properly when a user sends XML as content. I will try to fix this and get the proper indentation view. Thanks! [1] https://wso2.org/jira/browse/MB-139 [1] - http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AJ4/qX1nr58yWJk/s1600/1.png [2] - http://ssagara.blogspot.com/2012/04/axis2-jms-transport-and-activemq.html Thanks ! On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.comwrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Hasitha Abeykoon* Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* http://abeykoon.blogspot.com* * * *
Re: [Dev] Providing queue browser support in WSO2 MB admin console
On Tue, Apr 2, 2013 at 11:20 PM, Hasitha Hiranya hasit...@wso2.com wrote: Hi, It is nice to have feed-backs. 1. As Ishara says, tryit feature will be available with MB 2.1.0 release. 2. Message deletion will be nice to have. But JMS spec does not mention about deleting messages. When you get messages from queue with AUTO ACK mode messages will be auto deleted. BTW, Websphere MQ support that feature (selective delete) by their implementation. We will consider on adding that feature for MB 3.0.0. +1 ActiveMQ also support message deletion through it's web console. Thanks ! Thanks. On Tue, Apr 2, 2013 at 10:55 PM, Sagara Gunathunga sag...@wso2.comwrote: On Tue, Apr 2, 2013 at 10:53 PM, Ishara Premadasa ish...@wso2.comwrote: Hi Sagara, On Tue, Apr 2, 2013 at 10:43 PM, Sagara Gunathunga sag...@wso2.comwrote: Hi Ishara/Shammi, This is really cool addition ! As a MB user I also have list of feature requests for web console :) 1.) Practically I have felt many time if we could have web based sender ( or Try-It) feature with MB. This means there should be web interface to send messages to a destination without creating any JMS client, it just a filling a HTML page with required data. ActiveMQ provide such a web interface[1] and very useful too. As an example take a look at this post[2] how I used ActiveMQ console to test Axis2 JMS transport without writing any client side code. In my POV we need to have similar but better Try-It or sender feature for MB. Thank you very much for these suggestions. Actually our next task is adding a 'Test Message Sending' feature for MB admin console[1]. As exactly you had mentioned, we hope to provide the ability to send a sample JMS message with setting the necessary parameters like in ActiveMQ. Hope to start this soon ASAP once we finalize the queue browser. Great ! Nice to hear that. 2.) I believe we can provide following details per topic, WDYT ? Name Number Of Consumers Messages Enqueued Messages Dequeued 3.) It's better to have some XML indention on message content view. Yes, the current message content view doesn't show the XML indentions properly when a user sends XML as content. I will try to fix this and get the proper indentation view. Thanks! [1] https://wso2.org/jira/browse/MB-139 [1] - http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AJ4/qX1nr58yWJk/s1600/1.png [2] - http://ssagara.blogspot.com/2012/04/axis2-jms-transport-and-activemq.html Thanks ! On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa ish...@wso2.comwrote: Hi, This is an update on Feature#1207 [1], adding queue browsing ability into MB. The following is the final outcome of the feature implementation and this will be released with the upcoming MB 2.1.0 release. With queue browsing the user is capable of viewing the JMS Messages' details inside particular queue, including message attributes, properties, content type etc. and in addition the complete message body content can be viewed for each message as shown in the screen shots attached below. Due to the performance concerns there will be a maximum message limit of 200, that is displayed in the queue browser UI, even though the given queue may have a larger amount of messages. At the moment this can be configured in the qpid_config.xml if necessary (explained in the documentation). However I would like to know that whether we should allow this is to be configured into a higher amount as there is a possibility of crashing, when loading a big amount of messages into memory. The MB 2.1.0 documentation is updated too [2]. Thanks! Ishara [1] https://redmine.wso2.com/issues/1207 [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Blog ; http://ssagara.blogspot.com Linkedin; http://www.linkedin.com/in/ssagara ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Hasitha Abeykoon*
Re: [Dev] [Stratos2] Exception in S2 Agent
Hi
Will update the agent accordingly...
Thanks,
Reka
On Tue, Apr 2, 2013 at 11:19 PM, Nirmal Fernando nir...@wso2.com wrote:
Seems like S2 Agent is not bundled correctly. You need to add
mediator-autoscale bundle in S2 Agent's p2 profile.
On Tue, Apr 2, 2013 at 11:18 PM, Sajith Kariyawasam saj...@wso2.comwrote:
Any idea of this exception ?
This is occurred in S2 Agent side ...
[2013-04-02 17:42:33,468] ERROR
{org.apache.axis2.clustering.tribes.Axis2GroupChannel} - Unable to
deserialize
message:ClusterData[src=org.apache.catalina.tribes.membership.MemberImpl[tcp://{10,
68, 202, 233}:4000,{10, 68, 202, 233},4000, alive=1364923740091,
securePort=-1, UDP Port=-1, id={0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 },
payload={35 10 35 84 117 101 32 65 112 ...(61)}, command={}, domain={119
115 111 50 46 99 97 114 98 ...(21)}, ]; id={-105 13 38 105 73 43 74 45 -89
94 -73 -65 -66 -101 90 -113 }; sent=2013-04-02 17:42:33.363]
java.lang.ClassNotFoundException:
org.wso2.carbon.mediator.autoscale.lbautoscale.replication.RequestTokenReplicationCommand
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:601)
at
org.apache.catalina.tribes.io.ReplicationStream.resolveClass(ReplicationStream.java:79)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1493)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1729)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.group.RpcMessage.readExternal(RpcMessage.java:64)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1795)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1754)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.io.XByteBuffer.deserialize(XByteBuffer.java:568)
at
org.apache.axis2.clustering.tribes.Axis2GroupChannel.messageReceived(Axis2GroupChannel.java:60)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.messageReceived(NonBlockingCoordinator.java:512)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor.messageReceived(TcpPingInterceptor.java:162)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:113)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.DomainFilterInterceptor.messageReceived(DomainFilterInterceptor.java:45)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:253)
at
org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:287)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:212)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:101)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
--
Regards,
*
*
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.; http://wso2.com*
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
--
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error while starting BAM with API-M toolbox.
Hi Azeez,
The reason for this exception is:
The AM folks assume you will run the BAM ports with offset 1. I assume your
port offset is different? The ports are embedded in the scripts which is
causing the error. The connection refused error is the clue to this.
It would be great if you can log any of these issues as JIRAs as we are
doing a release focused on bug fixes and usability improvements for BAM
2.3.0.
Sanjeewa, this is not the first person who ran into these issues with AM
and BAM. I'm wondering why this wasn't noticed before (not tested?).
Anyways, please shout if anything is not working as breaking compatibility
between minor releases should not happen. I believe we need to fix this for
BAM 2.3.0.
On Tue, Apr 2, 2013 at 2:48 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Yes we have tested bam 2.0.1 with AM 1.3.1 and worked fine.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 3:13 PM, Afkham Azeez az...@wso2.com wrote:
Yes, BAM 2.2.0. So, if I use an older version of BAM will it work?
On Tue, Apr 2, 2013 at 2:58 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi Azeez,
Its seems you are using BAM 2.2.0. There were known bug in integrating
AM 1.4.0 and BAM 2.2.0. BAM team identified the reason for that and they
will fix it for next release. But the errors reported by you are bit
different with what we got. We will investigate more and update thread.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:35 PM, Afkham Azeez az...@wso2.com wrote:
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already
started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
Re: [Dev] Error while starting BAM with API-M toolbox.
On Tue, Apr 2, 2013 at 11:45 PM, Tharindu Mathew thari...@wso2.com wrote:
Hi Azeez,
The reason for this exception is:
The AM folks assume you will run the BAM ports with offset 1. I assume
your port offset is different? The ports are embedded in the scripts which
is causing the error. The connection refused error is the clue to this.
It would be great if you can log any of these issues as JIRAs as we are
doing a release focused on bug fixes and usability improvements for BAM
2.3.0.
Sanjeewa, this is not the first person who ran into these issues with AM
and BAM. I'm wondering why this wasn't noticed before (not tested?).
Anyways, please shout if anything is not working as breaking compatibility
between minor releases should not happen. I believe we need to fix this for
BAM 2.3.0.
Hi Tharindhu,
Noted your point. Instructions about port offset is clearly documented in
statistics readme file. See following instruction[1]. The issue mentioned
by me is not related to port offset and it is still under separate internal
discussion. When we release API manager 1.3.1 we did test with bam 2.0.1
and now for API manager 1.4.0 we started testing with BAM 2.2.0
and uncovered this bug. From here onward we will test toolbox and stats
related operations for BAM releases as well.
[1]
-
Configuring BAM
-
1. Extract the BAM binary distribution to your local file system.
2. Change port offset to 1 by editing the repository/conf/carbon.xml
3. Copy the API_Manager_Analytics.tbox to
repository/deployment/server/bam-toolbox
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:48 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Yes we have tested bam 2.0.1 with AM 1.3.1 and worked fine.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 3:13 PM, Afkham Azeez az...@wso2.com wrote:
Yes, BAM 2.2.0. So, if I use an older version of BAM will it work?
On Tue, Apr 2, 2013 at 2:58 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi Azeez,
Its seems you are using BAM 2.2.0. There were known bug in integrating
AM 1.4.0 and BAM 2.2.0. BAM team identified the reason for that and they
will fix it for next release. But the errors reported by you are bit
different with what we got. We will investigate more and update thread.
Thanks.
Sanjeewa.
On Tue, Apr 2, 2013 at 2:35 PM, Afkham Azeez az...@wso2.com wrote:
[2013-04-02 14:34:01,540] INFO
{org.wso2.carbon.bam.toolbox.deployer.core.BAMToolBoxDeployer} - Deployed
successfully file:
/Users/azeez/software/wso2bam-2.2.0/repository/deployment/server/bam-toolbox/API_Manager_Analytics.tbox
[2013-04-02 14:34:01,549] ERROR
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Error in
scheduling task: The task with name: am_stats_analyzer_115, already
started.
org.wso2.carbon.ntask.common.TaskException: The task with name:
am_stats_analyzer_115, already started.
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:195)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalTask(AbstractQuartzTaskManager.java:183)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleTask(StandaloneTaskManager.java:43)
at
org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager.scheduleLocalAllTasks(AbstractQuartzTaskManager.java:174)
at
org.wso2.carbon.ntask.core.impl.standalone.StandaloneTaskManager.scheduleAllTasks(StandaloneTaskManager.java:38)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.initTaskManagersForType(TaskServiceImpl.java:119)
at
org.wso2.carbon.ntask.core.service.impl.TaskServiceImpl.serverInitialized(TaskServiceImpl.java:154)
at
org.wso2.carbon.ntask.core.TaskStartupHandler.invoke(TaskStartupHandler.java:39)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:169)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:202)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:279)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
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
Re: [Dev] Moving SubDomainAwareGroupManagementAgent into Axis2?
I don't see any rationale to moving this into Axis2. It is not going to be
used in Axis2
On Tuesday, April 2, 2013, Nirmal Fernando wrote:
Well, Azeez here's the class.. We can move right?
/**
* This GroupManagementAgent can handle group membership based on cluster
sub-domains.
*/
public class SubDomainAwareGroupManagementAgent extends
DefaultGroupManagementAgent {
private String subDomain;
public SubDomainAwareGroupManagementAgent(String subDomain) {
this.subDomain = subDomain;
}
@Override
public void applicationMemberAdded(Member member) {
String subDomain = member.getProperties().getProperty(subDomain);
if (subDomain == null || subDomain.equals(this.subDomain)) {
super.applicationMemberAdded(member);
}
}
@Override
public void applicationMemberRemoved(Member member) {
String subDomain = member.getProperties().getProperty(subDomain);
if (subDomain == null || subDomain.equals(this.subDomain)) {
super.applicationMemberRemoved(member);
}
}
}
On Tue, Apr 2, 2013 at 9:37 PM, Afkham Azeez
az...@wso2.comjavascript:_e({}, 'cvml', 'az...@wso2.com');
wrote:
We can't move that. I think it also has tenancy related code.
On Tue, Apr 2, 2013 at 7:31 PM, Nirmal Fernando
nir...@wso2.comjavascript:_e({}, 'cvml', 'nir...@wso2.com');
wrote:
Hi Azeez,
Do you think it's a good idea to move
SubDomainAwareGroupManagementAgent into Axis2 (currently it's in
lb-endpoint component) ?
I felt like we have to use this implementation in various other
components than lb-endpoint component for writing test cases etc. and
currently we have to add an additional dependency for lb-endpoint
component, to get that done.
WDYT?
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com* javascript:_e({}, 'cvml',
'az...@wso2.com');*cell: +94
77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
--
Sent from Gmail Mobile
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Moving SubDomainAwareGroupManagementAgent into Axis2?
Ok, thanks for the input.
On Apr 3, 2013 6:46 AM, Afkham Azeez az...@wso2.com wrote:
I don't see any rationale to moving this into Axis2. It is not going to be
used in Axis2
On Tuesday, April 2, 2013, Nirmal Fernando wrote:
Well, Azeez here's the class.. We can move right?
/**
* This GroupManagementAgent can handle group membership based on cluster
sub-domains.
*/
public class SubDomainAwareGroupManagementAgent extends
DefaultGroupManagementAgent {
private String subDomain;
public SubDomainAwareGroupManagementAgent(String subDomain) {
this.subDomain = subDomain;
}
@Override
public void applicationMemberAdded(Member member) {
String subDomain =
member.getProperties().getProperty(subDomain);
if (subDomain == null || subDomain.equals(this.subDomain)) {
super.applicationMemberAdded(member);
}
}
@Override
public void applicationMemberRemoved(Member member) {
String subDomain =
member.getProperties().getProperty(subDomain);
if (subDomain == null || subDomain.equals(this.subDomain)) {
super.applicationMemberRemoved(member);
}
}
}
On Tue, Apr 2, 2013 at 9:37 PM, Afkham Azeez az...@wso2.com wrote:
We can't move that. I think it also has tenancy related code.
On Tue, Apr 2, 2013 at 7:31 PM, Nirmal Fernando nir...@wso2.com wrote:
Hi Azeez,
Do you think it's a good idea to move
SubDomainAwareGroupManagementAgent into Axis2 (currently it's in
lb-endpoint component) ?
I felt like we have to use this implementation in various other
components than lb-endpoint component for writing test cases etc. and
currently we have to add an additional dependency for lb-endpoint
component, to get that done.
WDYT?
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* http://www.apache.org/**
email: **az...@wso2.com** cell: +94 77 3320919
blog: **http://blog.afkham.org* http://blog.afkham.org*
twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
--
Sent from Gmail Mobile
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Carbon - Component - Andes UI - Build Failure
Hi, I am getting the following build failure when building patch-releases/4.1.2/components. [INFO] WSO2 Carbon - Component - Andes UI FAILURE [4.968s] [INFO] WSO2 Carbon - Patch releases - components - Aggregator Module SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:06.379s [INFO] Finished at: Tue Apr 02 20:07:53 PDT 2013 [INFO] Final Memory: 483M/1679M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.andes.ui: Compilation failure: Compilation failure: [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[20,30] package org.apache.commons.lang does not exist [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[165,23] cannot find symbol [ERROR] symbol : variable StringEscapeUtils [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[187,27] cannot find symbol [ERROR] symbol : variable StringEscapeUtils [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[279,15] cannot find symbol [ERROR] symbol : variable StringEscapeUtils [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.andes.ui Thanks, -- Nuwan Dias Software Engineer - 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] Carbon - Component - Andes UI - Build Failure
Hi Nuwan, This is due to the 'commons-lang-2.6' dependency is not updated into pom file of org.wso2.carbon.andes.ui. Hasitha will be committing it back soon. On Wed, Apr 3, 2013 at 8:37 AM, Nuwan Dias nuw...@wso2.com wrote: Hi, I am getting the following build failure when building patch-releases/4.1.2/components. [INFO] WSO2 Carbon - Component - Andes UI FAILURE [4.968s] [INFO] WSO2 Carbon - Patch releases - components - Aggregator Module SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:06.379s [INFO] Finished at: Tue Apr 02 20:07:53 PDT 2013 [INFO] Final Memory: 483M/1679M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.andes.ui: Compilation failure: Compilation failure: [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[20,30] package org.apache.commons.lang does not exist [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[165,23] cannot find symbol [ERROR] symbol : variable StringEscapeUtils [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[187,27] cannot find symbol [ERROR] symbol : variable StringEscapeUtils [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient [ERROR] /home/wso2/4.1.0/platform/4.1.0/components/andes/org.wso2.carbon.andes.ui/4.1.2/src/main/java/org/wso2/carbon/andes/ui/client/QueueBrowserClient.java:[279,15] cannot find symbol [ERROR] symbol : variable StringEscapeUtils [ERROR] location: class org.wso2.carbon.andes.ui.client.QueueBrowserClient [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.andes.ui Thanks, -- Nuwan Dias Software Engineer - 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 -- Ishara Premasada Software Engineer, Integration Technology Team, WSO2 Inc. http://wso2.com/ *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 Twitter : https://twitter.com/ishadil Mobile : +94 714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Transport Adaptor (Broker) In CEP
Hi Mohan, On Sat, Mar 30, 2013 at 11:43 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Hi, We have started the work of modifying the CEP server. As the first step we have start re-writing the broker module of the CEP. In our next release we are going to have Transport Adaptor module instead of broker module. Transport Adaptor module going to do similar work as broker does. But through the Transport adaptor module we can provide more user friendliness. In the new architecture, same as broker module the core part will be handle by the Transport Adaptor. *Transport Adaptor Core* - Transport Adaptor core contains the base methods to create transportAdaptorDto and to handle transport adaptor configuration details. - It exposes two services, 1) to register a transport adaptor 2) to get the information about transport adaptors. - It allows to write external transport adaptor component and register it easily. - Each and every transport adaptor types (broker types - jms, agent etc...) is written as individual module and registered with this transport adaptor core. Other important module which manages the transport adaptor is transport adaptor manager. This module contains 3 sub components. There are core, admin UI, similar as old broker manager module. But in the new module we have changed some old implementations. *Transport Adaptor Manager Core* - We have remove the registry related configurations of a transport adaptor (broker). and all the transport adaptor information are stored as a xml file like we are handing the bucket. - We have also provided the hot deployment facility for transport adaptor creation. - All the transport adaptor information will store in the file system. - It access the transport adaptor service and get the information regarding the transport adaptors and their properties. - It exposes a service to get the transport adaptor configuration and to store the new transport adaptor configuration. *Transport Adaptor Manager Admin* - It act as an interface between the UI and core. - It exposes an admin service to UI to get the information that needed to create the UI and to store those information This architecture will also provide the flexibility to integrated the CEP with other products easily. We are now moving forward to create the UI component for transport adaptor. One question regarding the UI component, This means that the user is allowed to change the configuration of a particular transport at run-time. So how are you planning to get those changes and plug in to run-time information? Just a thought, you can give a try and use the TransportService for this. Have a look at the JMSTransportService for more info. Thanks, Kishanthan. Hope our new design will provide more flexibility to work with CEP... Any suggestions? Thanks Regards Mohan -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: mo...@wso2.com phone:(+94) 771117673 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Transport Adaptor (Broker) In CEP
Hi Kishanthan, No, we are not changing the UI of a particular transport adaptor at run-time... It can be changed by the user if it is an external transport adaptor which is written by him (not in run time). We are still working on the UI component then we can consider your idea and look about that also... Appreciate your suggestion. Thanks Regards, Mohan On Wed, Apr 3, 2013 at 9:17 AM, Kishanthan Thangarajah kishant...@wso2.comwrote: Hi Mohan, On Sat, Mar 30, 2013 at 11:43 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Hi, We have started the work of modifying the CEP server. As the first step we have start re-writing the broker module of the CEP. In our next release we are going to have Transport Adaptor module instead of broker module. Transport Adaptor module going to do similar work as broker does. But through the Transport adaptor module we can provide more user friendliness. In the new architecture, same as broker module the core part will be handle by the Transport Adaptor. *Transport Adaptor Core* - Transport Adaptor core contains the base methods to create transportAdaptorDto and to handle transport adaptor configuration details. - It exposes two services, 1) to register a transport adaptor 2) to get the information about transport adaptors. - It allows to write external transport adaptor component and register it easily. - Each and every transport adaptor types (broker types - jms, agent etc...) is written as individual module and registered with this transport adaptor core. Other important module which manages the transport adaptor is transport adaptor manager. This module contains 3 sub components. There are core, admin UI, similar as old broker manager module. But in the new module we have changed some old implementations. *Transport Adaptor Manager Core* - We have remove the registry related configurations of a transport adaptor (broker). and all the transport adaptor information are stored as a xml file like we are handing the bucket. - We have also provided the hot deployment facility for transport adaptor creation. - All the transport adaptor information will store in the file system. - It access the transport adaptor service and get the information regarding the transport adaptors and their properties. - It exposes a service to get the transport adaptor configuration and to store the new transport adaptor configuration. *Transport Adaptor Manager Admin* - It act as an interface between the UI and core. - It exposes an admin service to UI to get the information that needed to create the UI and to store those information This architecture will also provide the flexibility to integrated the CEP with other products easily. We are now moving forward to create the UI component for transport adaptor. One question regarding the UI component, This means that the user is allowed to change the configuration of a particular transport at run-time. So how are you planning to get those changes and plug in to run-time information? Just a thought, you can give a try and use the TransportService for this. Have a look at the JMSTransportService for more info. Thanks, Kishanthan. Hope our new design will provide more flexibility to work with CEP... Any suggestions? Thanks Regards Mohan -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: mo...@wso2.com phone:(+94) 771117673 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan* -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: mo...@wso2.com phone:(+94) 771117673 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Stratos2] Exception in S2 Agent
Hi
Agent has been fixed. Thanks Nirmal for the quick fix in auto scaler side...
Thanks,
Reka
On Tue, Apr 2, 2013 at 11:26 PM, Reka Thirunavukkarasu r...@wso2.comwrote:
Hi
Will update the agent accordingly...
Thanks,
Reka
On Tue, Apr 2, 2013 at 11:19 PM, Nirmal Fernando nir...@wso2.com wrote:
Seems like S2 Agent is not bundled correctly. You need to add
mediator-autoscale bundle in S2 Agent's p2 profile.
On Tue, Apr 2, 2013 at 11:18 PM, Sajith Kariyawasam saj...@wso2.comwrote:
Any idea of this exception ?
This is occurred in S2 Agent side ...
[2013-04-02 17:42:33,468] ERROR
{org.apache.axis2.clustering.tribes.Axis2GroupChannel} - Unable to
deserialize
message:ClusterData[src=org.apache.catalina.tribes.membership.MemberImpl[tcp://{10,
68, 202, 233}:4000,{10, 68, 202, 233},4000, alive=1364923740091,
securePort=-1, UDP Port=-1, id={0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 },
payload={35 10 35 84 117 101 32 65 112 ...(61)}, command={}, domain={119
115 111 50 46 99 97 114 98 ...(21)}, ]; id={-105 13 38 105 73 43 74 45 -89
94 -73 -65 -66 -101 90 -113 }; sent=2013-04-02 17:42:33.363]
java.lang.ClassNotFoundException:
org.wso2.carbon.mediator.autoscale.lbautoscale.replication.RequestTokenReplicationCommand
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:249)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:601)
at
org.apache.catalina.tribes.io.ReplicationStream.resolveClass(ReplicationStream.java:79)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1572)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1493)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1729)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.group.RpcMessage.readExternal(RpcMessage.java:64)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1795)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1754)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1326)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at
org.apache.catalina.tribes.io.XByteBuffer.deserialize(XByteBuffer.java:568)
at
org.apache.axis2.clustering.tribes.Axis2GroupChannel.messageReceived(Axis2GroupChannel.java:60)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.messageReceived(NonBlockingCoordinator.java:512)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpPingInterceptor.messageReceived(TcpPingInterceptor.java:162)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:113)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.interceptors.DomainFilterInterceptor.messageReceived(DomainFilterInterceptor.java:45)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:84)
at
org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:253)
at
org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:287)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:212)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:101)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
--
Regards,
*
*
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.; http://wso2.com*
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
http://nirmalfdo.blogspot.com/
--
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,
--
Reka
[Dev] Stratos2 Installation Guide Puppet master configuration section
Hi Lakmal, Isuru W, I guess we don't need all the puppet master configuration stuff included in the doc. Since we have scripts for the settings just mentioning how to execute the script would be enough Damitha -- __ Damitha Kumarage Senior Technical Lead; WSO2 Inc. Oxygenating the Web Service Platform http://www.wso2.com/ blog: http://damithakumarage.wordpress.com/ __ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Invitation: [Code Review] Lifecycle transition using Governance API @ Thu Apr 4, 2013 1:30pm - 2:30pm (dus...@wso2.com)
Hi Guys, Please _ _ *NOTE* _ _ this training is *Mandatory* for all the members in * Integration TG*, FYI : Eranda please make sure that you have covered Sonar, Findbugs prior to the code review which makes your life easier. :) On Wed, Apr 3, 2013 at 10:50 AM, Eranda Sooriyabandara era...@wso2.comwrote: more details »https://www.google.com/calendar/event?action=VIEWeid=Mmp1NDU2dnU2ZnZiY2wxdDdzNTdhNTFyY28gZHVzaGFuQHdzbzIuY29ttok=MTUjZXJhbmRhQHdzbzIuY29tMzBkYTc2ZTRkZjdhMzVkZDYwMmNiN2RlYmM5MjIwNmIzODkzMWQzYQctz=Asia/Colombohl=en [Code Review] Lifecycle transition using Governance API Crusible link - http://wso2.org/crucible/cru/WCP045-1http://www.google.com/url?q=http%3A%2F%2Fwso2.org%2Fcrucible%2Fcru%2FWCP045-1ust=1364973605174000usg=AFQjCNEwCG6ojMQ9tHsepfBJC3K2PB_PZg *When* Thu Apr 4, 2013 1:30pm – 2:30pm Colombo *Where* LK #58 5th Floor - Meeting room (maphttp://maps.google.lk/maps?q=LK+%2358+5th+Floor+-+Meeting+roomhl=en ) *Calendar* dus...@wso2.com *Who* • Eranda Sooriyabandara - organizer • Ajith Vitharana • Chandana Napagoda • Dushan Abeyruwan • Pulasthi Supun • Kasun Indrasiri • Senaka Fernando • Sriragu Arudsothy Going? ***Yeshttps://www.google.com/calendar/event?action=RESPONDeid=Mmp1NDU2dnU2ZnZiY2wxdDdzNTdhNTFyY28gZHVzaGFuQHdzbzIuY29trst=1tok=MTUjZXJhbmRhQHdzbzIuY29tMzBkYTc2ZTRkZjdhMzVkZDYwMmNiN2RlYmM5MjIwNmIzODkzMWQzYQctz=Asia/Colombohl=en- Maybehttps://www.google.com/calendar/event?action=RESPONDeid=Mmp1NDU2dnU2ZnZiY2wxdDdzNTdhNTFyY28gZHVzaGFuQHdzbzIuY29trst=3tok=MTUjZXJhbmRhQHdzbzIuY29tMzBkYTc2ZTRkZjdhMzVkZDYwMmNiN2RlYmM5MjIwNmIzODkzMWQzYQctz=Asia/Colombohl=en- Nohttps://www.google.com/calendar/event?action=RESPONDeid=Mmp1NDU2dnU2ZnZiY2wxdDdzNTdhNTFyY28gZHVzaGFuQHdzbzIuY29trst=2tok=MTUjZXJhbmRhQHdzbzIuY29tMzBkYTc2ZTRkZjdhMzVkZDYwMmNiN2RlYmM5MjIwNmIzODkzMWQzYQctz=Asia/Colombohl=en ***more options »https://www.google.com/calendar/event?action=VIEWeid=Mmp1NDU2dnU2ZnZiY2wxdDdzNTdhNTFyY28gZHVzaGFuQHdzbzIuY29ttok=MTUjZXJhbmRhQHdzbzIuY29tMzBkYTc2ZTRkZjdhMzVkZDYwMmNiN2RlYmM5MjIwNmIzODkzMWQzYQctz=Asia/Colombohl=en Invitation from Google Calendar https://www.google.com/calendar/ You are receiving this email at the account dus...@wso2.com because you are subscribed for invitations on calendar dus...@wso2.com. To stop receiving these notifications, please log in to https://www.google.com/calendar/ and change your notification settings for this calendar. -- Dushan Abeyruwan *Senior Software Engineer* *Integration Technologies Team* *Member of Integration MC* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
