Re: [Dev] Using UES in other products
Hi Pulasthi,
I don't think so, because the UES jaggery apps operate on the root context
and so are not affected by carbon.xml webcontextroot changes. Manuranga
please correct me if I am wrong in this regard.
Thanks,
Gokul.
On 13 September 2013 11:24, Pulasthi Supun pulas...@wso2.com wrote:
Hi Manu,
Since the web context root can also be changed through the carbon.xml. any
configuration that will be done for this would need to consider that also
right?.
Regards,
Pulasthi
On Fri, Sep 13, 2013 at 11:18 AM, Manuranga Perera m...@wso2.com wrote:
by default UES hosts shindig web app at ROOT web context ('/').
since this conflicts with other product’s carbon console context, you may
have to change that.
until a proper configuration is introduced for this, here is a fix that
will do that for the time being.
1) change /modules/distribution/src/assembly/bin.xml file's shindig
output dir (see bin.diff)
2) copy the new shindig.js (attached) file to every place it appears in
jaggery apps.
--
With regards,
*Manu*ranga Perera.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
--
*Balakrishnan Gokulakrishnan*
Software Engineer,
WSO2, Inc.; http://wso2.com
Tel: 0094 11 214 5345 | Fax: 0094 11 214 5300
Twitter: http://twitter.com/gokulbs
Mobile: 0094 77 593 5789
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Using UES in other products
yes gokul, this fix applies only if you don't want to change web context
root via carbon.xml
if you have changed it that way, this problem would not occur in the first
place and you can use UES as is.
On Fri, Sep 13, 2013 at 11:24 AM, Pulasthi Supun pulas...@wso2.com wrote:
Hi Manu,
Since the web context root can also be changed through the carbon.xml. any
configuration that will be done for this would need to consider that also
right?.
Regards,
Pulasthi
On Fri, Sep 13, 2013 at 11:18 AM, Manuranga Perera m...@wso2.com wrote:
by default UES hosts shindig web app at ROOT web context ('/').
since this conflicts with other product’s carbon console context, you may
have to change that.
until a proper configuration is introduced for this, here is a fix that
will do that for the time being.
1) change /modules/distribution/src/assembly/bin.xml file's shindig
output dir (see bin.diff)
2) copy the new shindig.js (attached) file to every place it appears in
jaggery apps.
--
With regards,
*Manu*ranga Perera.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
--
With regards,
*Manu*ranga Perera.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases
Hi Kasun et al, we should try to use one minor ESB version across chunk releases... (2.1.2-wso2v1). ESB team owns the synapse core. Others have to wait till they release.. Hence IMHO, ELB should use, 2.1.2-wso2v1. On Sat, Sep 7, 2013 at 11:08 PM, Vanjikumaran Sivajothy va...@wso2.comwrote: Hi IsuruU, I have reverted back the changes. Best regards, Vanji On Sat, Sep 7, 2013 at 8:22 PM, Isuru Udana isu...@wso2.com wrote: On Sat, Sep 7, 2013 at 7:25 PM, Lasantha Fernando lasan...@wso2.comwrote: Hi all, It seems the features/synapse/pom.xml synapse version has been changed to 2.1.2-wso2v1. But I think features/synapse has already being released with version 2.1.1-wso2v8 for chunk 01 release. Shouldn't we revert that change back as well? Yes. This should be reverted. Vanji, Please revert these changes and set the synapse version only at newly created features, p2-profile . there itself. Also, I guess since chunk 02 is going with synapse-2.1.1-wso2v9, that version should be referred directly within the chunk02 release only and not in anywhere for the already released stuff as IsuruU has already pointed out.. Thanks, Lasantha On 7 September 2013 17:51, Vanjikumaran Sivajothy va...@wso2.comwrote: Hi IsuruP, I have reverted it back to 2.1.1-wso2v8 using r184691. Thank you, Best regards, Vanji On Fri, Sep 6, 2013 at 11:44 PM, Isuru Udana isu...@wso2.com wrote: Hi IsuruP, On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera isu...@wso2.com wrote: Hi, We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1 for chunk-02 product releases. Please note that I committed version to platform parent pom.xml [1] with revision 184661. Parent is already released. So you can't commit to it. Instead of changing the synapse version in the parent pom, change the synapse version within relevant dependency, features, p2-profile there itself. Thanks! Best Regards, [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)777219209** *[image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image: Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]http://www.slideshare.net/vanjikumaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)777219209** *[image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image: Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]http://www.slideshare.net/vanjikumaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pradeep Fernando* Associate Technical Lead;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Using UES in other products
Hi,
ahh ok got it, thanks for the clarification :)
Regards,
Pulasthi
On Fri, Sep 13, 2013 at 11:31 AM, Manuranga Perera m...@wso2.com wrote:
yes gokul, this fix applies only if you don't want to change web context
root via carbon.xml
if you have changed it that way, this problem would not occur in the first
place and you can use UES as is.
On Fri, Sep 13, 2013 at 11:24 AM, Pulasthi Supun pulas...@wso2.comwrote:
Hi Manu,
Since the web context root can also be changed through the carbon.xml.
any configuration that will be done for this would need to consider that
also right?.
Regards,
Pulasthi
On Fri, Sep 13, 2013 at 11:18 AM, Manuranga Perera m...@wso2.com wrote:
by default UES hosts shindig web app at ROOT web context ('/').
since this conflicts with other product’s carbon console context, you
may have to change that.
until a proper configuration is introduced for this, here is a fix that
will do that for the time being.
1) change /modules/distribution/src/assembly/bin.xml file's shindig
output dir (see bin.diff)
2) copy the new shindig.js (attached) file to every place it appears in
jaggery apps.
--
With regards,
*Manu*ranga Perera.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
--
With regards,
*Manu*ranga Perera.
--
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Commits] [Carbon-platform] svn commit r185274 - carbon/platform/branches/4.2.0/product-releases/chunk-02/components
[INFO] Scanning for projects... [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon:product-releases-components:4.2.0-chunk02 (/home/ajith/wso2/build/platform/4.2.0/product-releases/chunk-02/components/pom.xml) has 1 error [ERROR] Child module /home/ajith/wso2/build/platform/4.2.0/product-releases/chunk-02/components/../../../components/stratos/usage/org.wso2.carbon.keystore.mgt/2.2.1 of /home/ajith/wso2/build/platform/4.2.0/product-releases/chunk-02/components/pom.xml does not exist [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. Please update the chunk02 poms properly when you create patch versions. Thanks Ajith On Thu, Sep 12, 2013 at 10:01 PM, danush...@wso2.com wrote: Author: danush...@wso2.com Date: Thu Sep 12 22:01:37 2013 New Revision: 185274 URL: http://wso2.org/svn/browse/wso2?view=revrevision=185274 Log: add keystore new version Modified: carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml Modified: carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml URL: http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml?rev=185274r1=185273r2=185274view=diff == --- carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml (original) +++ carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml Thu Sep 12 22:01:37 2013 @@ -105,6 +105,7 @@ module../../../components/stratos/throttling/org.wso2.carbon.throttling.ui/2.2.0/module module../../../components/stratos/usage/org.wso2.carbon.usage/2.2.0/module module../../../components/stratos/usage/org.wso2.carbon.usage.ui/2.2.0/module + module../../../components/stratos/usage/org.wso2.carbon.keystore.mgt/2.2.1/module module../../../components/transport-mgt/org.wso2.carbon.transport.vfs/4.2.0/module ___ Commits mailing list comm...@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/commits -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] HTTP port -1 HTTPS port -1 ?
On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne chama...@wso2.comwrote: Why this comes when API M joins ELB. (ELB local member port 4000) [2013-09-12 17:31:35,189] INFO - MemberUtils Added member: Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true Is this harmless? What needs to be configured for this to work the correct way? With which products do you get this? 4.2.0 based products or pre-4.2.0 products. -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead 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
[Dev] Some Registry features with version 4.2.1 in chunk-02 which have no released 4.2.0 version
Hi all, In chunk-02 features/pom, the registry features org.wso2.carbon.registry.community.features.feature org.wso2.carbon.governance.metadata.feature are pointing to 4.2.1 version. But they don't seem to have been released with chunk-01 (with a 4.2.0 version). Is there any reason for using 4.2.1 version number? Maybe am missing something here. Thanks, Lasantha -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ELB 2.1.0 with ESB 4.8.0 W/M setup not working
HI Can we know the solution for the given issue, ESB team suppose to run extensive tests for *connectors* in W/M setup, but the reported issue holding us for 2 days..appreciate quick feed-back soon.. Cheers Dushan On Thu, Sep 12, 2013 at 7:28 PM, Isuru Perera isu...@wso2.com wrote: Hi Sameera, I couldn't figure out the problem with clustering. It could be a configuration issue. Appreciate any help on this. Thanks. On Thu, Sep 12, 2013 at 11:06 AM, Dushan Abeyruwan dus...@wso2.comwrote: Hi Sameers, Pls find the attachments Cheers, Dushan On Thu, Sep 12, 2013 at 11:01 AM, Sameera Jayasoma same...@wso2.comwrote: Hi Dushan, Can you attach the configuration file in ESB nodes and the ELB? I.e. configuration files you updated. Thanks, Sameera. On Thu, Sep 12, 2013 at 10:07 AM, Dushan Abeyruwan dus...@wso2.comwrote: $subject, have we done any changers in core recently ?, seems like non of the manager or worker nodes not joining to the cluster, same setup worked for ESB M1 pack released few weeks back. appropriate response ASAP. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk-02 build failure in components/event-processing/event-output-adaptor
[INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:18.445s [INFO] Finished at: Thu Sep 12 23:20:03 PDT 2013 [INFO] Final Memory: 315M/1255M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.event.output.adaptor.manager.ui: Compilation failure: Compilation failure: [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[8,56] package org.wso2.carbon.event.output.adaptor.manager.stub does not exist [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[16,18] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub [ERROR] location: class org.wso2.carbon.event.output.adaptor.manager.ui.OutputEventAdaptorUIUtils [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[25,8] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub [ERROR] location: class org.wso2.carbon.event.output.adaptor.manager.ui.OutputEventAdaptorUIUtils [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[25,61] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com* * * *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Patch for kernel. - chunk02 release.
Hi Ajith, We are working on it, BTW in you case, don't need to create 4.2.1 version of org.wso2.carbon.core only released *platform *components need that version increment. Your change will go with patch0001. Thanks, Shameera. On Fri, Sep 13, 2013 at 11:22 AM, Ajith Vitharana aji...@wso2.com wrote: Hi Carbon team, Please commit the kernel patches. Or grant commits rights :) Thanks On Thu, Sep 12, 2013 at 2:03 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Shameera, Please apply the patch [1] for chunk02 release. [1]https://wso2.org/jira/browse/REGISTRY-1941 Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.orgshame...@apache.org * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases
The main issue here is that ELB/API-M releases go with chunk 2 while ESB is planned for chunk 3. We are doing quite a lot of changes in synapse-core for connector work and that's why we let ELB/API-M to go with 2.1.1v9 version(We are applying all critical fixes for both synapse versions). Ideally, the dependent products should go after an ESB release, but it is not practical I guess. On Fri, Sep 13, 2013 at 11:32 AM, Pradeep Fernando prad...@wso2.com wrote: Hi Kasun et al, we should try to use one minor ESB version across chunk releases... (2.1.2-wso2v1). ESB team owns the synapse core. Others have to wait till they release.. Hence IMHO, ELB should use, 2.1.2-wso2v1. On Sat, Sep 7, 2013 at 11:08 PM, Vanjikumaran Sivajothy va...@wso2.comwrote: Hi IsuruU, I have reverted back the changes. Best regards, Vanji On Sat, Sep 7, 2013 at 8:22 PM, Isuru Udana isu...@wso2.com wrote: On Sat, Sep 7, 2013 at 7:25 PM, Lasantha Fernando lasan...@wso2.comwrote: Hi all, It seems the features/synapse/pom.xml synapse version has been changed to 2.1.2-wso2v1. But I think features/synapse has already being released with version 2.1.1-wso2v8 for chunk 01 release. Shouldn't we revert that change back as well? Yes. This should be reverted. Vanji, Please revert these changes and set the synapse version only at newly created features, p2-profile . there itself. Also, I guess since chunk 02 is going with synapse-2.1.1-wso2v9, that version should be referred directly within the chunk02 release only and not in anywhere for the already released stuff as IsuruU has already pointed out.. Thanks, Lasantha On 7 September 2013 17:51, Vanjikumaran Sivajothy va...@wso2.comwrote: Hi IsuruP, I have reverted it back to 2.1.1-wso2v8 using r184691. Thank you, Best regards, Vanji On Fri, Sep 6, 2013 at 11:44 PM, Isuru Udana isu...@wso2.com wrote: Hi IsuruP, On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera isu...@wso2.comwrote: Hi, We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1 for chunk-02 product releases. Please note that I committed version to platform parent pom.xml [1] with revision 184661. Parent is already released. So you can't commit to it. Instead of changing the synapse version in the parent pom, change the synapse version within relevant dependency, features, p2-profile there itself. Thanks! Best Regards, [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)777219209** *[image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image: Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]http://www.slideshare.net/vanjikumaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)777219209** *[image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image: Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]http://www.slideshare.net/vanjikumaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pradeep Fernando* Associate Technical Lead;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware
Re: [Dev] Chunk-02 build failure in components/event-processing/event-output-adaptor
Hi Bhathiya, Have you got an svn up in the stubs.. If not please take an up and see.. We have done a clean repo build yesterday in builder machine but it is working.. Regards, Mohan.. On Fri, Sep 13, 2013 at 12:05 PM, Bhathiya Jayasekara bhath...@wso2.com wrote: [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:18.445s [INFO] Finished at: Thu Sep 12 23:20:03 PDT 2013 [INFO] Final Memory: 315M/1255M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.event.output.adaptor.manager.ui: Compilation failure: Compilation failure: [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[8,56] package org.wso2.carbon.event.output.adaptor.manager.stub does not exist [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[16,18] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub [ERROR] location: class org.wso2.carbon.event.output.adaptor.manager.ui.OutputEventAdaptorUIUtils [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[25,8] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub [ERROR] location: class org.wso2.carbon.event.output.adaptor.manager.ui.OutputEventAdaptorUIUtils [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[25,61] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub -- Bhathiya Jayasekara Software Engineer, WSO2 inc., http://wso2.com Phone: +94715478185 LinkedIn: http://www.linkedin.com/in/bhathiyaj Twitter: https://twitter.com/bhathiyax ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- 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] Using synapse version 2.1.1-wso2v9 for chunk-02 product releases
Hi Kasun, yes understood the reason, why we are doing this. However, we should also note that this introduces interop issues at feature level. (p2 story) --Pradeep On Fri, Sep 13, 2013 at 12:11 PM, Kasun Indrasiri ka...@wso2.com wrote: The main issue here is that ELB/API-M releases go with chunk 2 while ESB is planned for chunk 3. We are doing quite a lot of changes in synapse-core for connector work and that's why we let ELB/API-M to go with 2.1.1v9 version(We are applying all critical fixes for both synapse versions). Ideally, the dependent products should go after an ESB release, but it is not practical I guess. On Fri, Sep 13, 2013 at 11:32 AM, Pradeep Fernando prad...@wso2.comwrote: Hi Kasun et al, we should try to use one minor ESB version across chunk releases... (2.1.2-wso2v1). ESB team owns the synapse core. Others have to wait till they release.. Hence IMHO, ELB should use, 2.1.2-wso2v1. On Sat, Sep 7, 2013 at 11:08 PM, Vanjikumaran Sivajothy va...@wso2.comwrote: Hi IsuruU, I have reverted back the changes. Best regards, Vanji On Sat, Sep 7, 2013 at 8:22 PM, Isuru Udana isu...@wso2.com wrote: On Sat, Sep 7, 2013 at 7:25 PM, Lasantha Fernando lasan...@wso2.comwrote: Hi all, It seems the features/synapse/pom.xml synapse version has been changed to 2.1.2-wso2v1. But I think features/synapse has already being released with version 2.1.1-wso2v8 for chunk 01 release. Shouldn't we revert that change back as well? Yes. This should be reverted. Vanji, Please revert these changes and set the synapse version only at newly created features, p2-profile . there itself. Also, I guess since chunk 02 is going with synapse-2.1.1-wso2v9, that version should be referred directly within the chunk02 release only and not in anywhere for the already released stuff as IsuruU has already pointed out.. Thanks, Lasantha On 7 September 2013 17:51, Vanjikumaran Sivajothy va...@wso2.comwrote: Hi IsuruP, I have reverted it back to 2.1.1-wso2v8 using r184691. Thank you, Best regards, Vanji On Fri, Sep 6, 2013 at 11:44 PM, Isuru Udana isu...@wso2.com wrote: Hi IsuruP, On Fri, Sep 6, 2013 at 11:22 PM, Isuru Perera isu...@wso2.comwrote: Hi, We will be using synapse version 2.1.1-wso2v9 instead of 2.1.2-wso2v1 for chunk-02 product releases. Please note that I committed version to platform parent pom.xml [1] with revision 184661. Parent is already released. So you can't commit to it. Instead of changing the synapse version in the parent pom, change the synapse version within relevant dependency, features, p2-profile there itself. Thanks! Best Regards, [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/parent/pom.xml -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)777219209** *[image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image: Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]http://www.slideshare.net/vanjikumaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- *Isuru Udana* * * Senior * Software Engineer * WSO2 Inc.; http://wso2.com email: isu...@wso2.com cell: +94 77 3791887 blog: http://mytecheye.blogspot.com/ twitter: http://twitter.com/isudana -- Sivajothy Vanjikumaran *Senior Software Engineer* *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)777219209** *[image: Facebook] https://www.facebook.com/vanjikumaran [image: Twitter] https://twitter.com/vanjikumaran [image: LinkedIn]http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293 [image: Blogger] http://vanjikumaran.blogspot.com/ [image: SlideShare]http://www.slideshare.net/vanjikumaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Pradeep Fernando* Associate Technical Lead;WSO2 Inc.; http://wso2.com blog:
Re: [Dev] org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) method runs twice on single deploy
If would be great if someone from platform team can take a look. Amal is currently working on another bps task. Regards Nandika On Thu, Sep 12, 2013 at 9:10 PM, Nirmal Fernando nir...@wso2.com wrote: Did anyone look after this issue? On Mon, Sep 2, 2013 at 11:58 AM, Amal Gunatilake am...@wso2.com wrote: Please have a look. org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) *method inside the kernel runs twice on single deploy which repeats the same log twice*. This issue was found when tracking the JIRA issue https://wso2.org/jira/browse/BPS-215 - Two error log message are showing when return a one error message When tracking as a BPS issue, it was discovered that it's a common issue for system logs which produces in kernel. Thanks Regards, Amal. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk-02 build failure in components/event-processing/event-output-adaptor
Hi Mohan, On Fri, Sep 13, 2013 at 12:14 PM, Mohanadarshan Vivekanandalingam mo...@wso2.com wrote: Hi Bhathiya, Have you got an svn up in the stubs.. If not please take an up and see.. I just got and update in service stubs but nothing updated. Thanks, Bhathiya We have done a clean repo build yesterday in builder machine but it is working.. Regards, Mohan.. On Fri, Sep 13, 2013 at 12:05 PM, Bhathiya Jayasekara bhath...@wso2.com wrote: [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:18.445s [INFO] Finished at: Thu Sep 12 23:20:03 PDT 2013 [INFO] Final Memory: 315M/1255M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.event.output.adaptor.manager.ui: Compilation failure: Compilation failure: [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[8,56] package org.wso2.carbon.event.output.adaptor.manager.stub does not exist [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[16,18] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub [ERROR] location: class org.wso2.carbon.event.output.adaptor.manager.ui.OutputEventAdaptorUIUtils [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[25,8] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub [ERROR] location: class org.wso2.carbon.event.output.adaptor.manager.ui.OutputEventAdaptorUIUtils [ERROR] /home/wso2/ss-1.1.0/carbon/platform/branches/4.2.0/components/event-processing/event-output-adaptor/org.wso2.carbon.event.output.adaptor.manager.ui/1.0.0/src/main/java/org/wso2/carbon/event/output/adaptor/manager/ui/OutputEventAdaptorUIUtils.java:[25,61] cannot find symbol [ERROR] symbol : class OutputEventAdaptorManagerAdminServiceStub -- Bhathiya Jayasekara Software Engineer, WSO2 inc., http://wso2.com Phone: +94715478185 LinkedIn: http://www.linkedin.com/in/bhathiyaj Twitter: https://twitter.com/bhathiyax ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- V. Mohanadarshan Software Engineer, Data Technologies Team, WSO2, Inc. http://wso2.com lean.enterprise.middleware. email: mo...@wso2.com phone:(+94) 771117673 -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com* * * *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) method runs twice on single deploy
Carbon team FYI. On Fri, Sep 13, 2013 at 12:19 PM, Nandika Jayawardana nand...@wso2.comwrote: If would be great if someone from platform team can take a look. Amal is currently working on another bps task. Regards Nandika On Thu, Sep 12, 2013 at 9:10 PM, Nirmal Fernando nir...@wso2.com wrote: Did anyone look after this issue? On Mon, Sep 2, 2013 at 11:58 AM, Amal Gunatilake am...@wso2.com wrote: Please have a look. org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) *method inside the kernel runs twice on single deploy which repeats the same log twice*. This issue was found when tracking the JIRA issue https://wso2.org/jira/browse/BPS-215 - Two error log message are showing when return a one error message When tracking as a BPS issue, it was discovered that it's a common issue for system logs which produces in kernel. Thanks Regards, Amal. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] HTTP port -1 HTTPS port -1 ?
ELB 2.1.0 10/09/2013 build http://10.100.1.185/packs/sep-10 APIM RC2 12/09/2013 http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/AM/ On Fri, Sep 13, 2013 at 11:46 AM, Amila Maha Arachchi ami...@wso2.comwrote: On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne chama...@wso2.comwrote: Why this comes when API M joins ELB. (ELB local member port 4000) [2013-09-12 17:31:35,189] INFO - MemberUtils Added member: Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true Is this harmless? What needs to be configured for this to work the correct way? With which products do you get this? 4.2.0 based products or pre-4.2.0 products. -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Some Registry features with version 4.2.1 in chunk-02 which have no released 4.2.0 version
On Fri, Sep 13, 2013 at 11:49 AM, Lasantha Fernando lasan...@wso2.comwrote: Hi all, In chunk-02 features/pom, the registry features org.wso2.carbon.registry.community.features.feature org.wso2.carbon.governance.metadata.feature are pointing to 4.2.1 version. But they don't seem to have been released with chunk-01 (with a 4.2.0 version). Is there any reason for using 4.2.1 version number?. Maybe am missing something here. The reason this org.wso2.carbon.registry.eventing.4.2.0 jar is released (bundled with org.wso2.carbon.registry.community.features.feature). Therefore we created new feature version for org.wso2.carbon.registry.eventing.4.2.1 jar , same applied to org.wso2.carbon.governance.metadata.feature as well. Thanks Ajith Thanks, Lasantha -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] G-Reg + AM Integration L1/L2 issues {was: Re: G-REG + AM integration broken in new packs.}
Hi all,
What's the plan for fixing these? We have 2 L1 issues, which doesn't seem
to be getting the right attention. Shall I move to AM?
[1] https://wso2.org/jira/browse/REGISTRY-1862
[2] https://wso2.org/jira/browse/REGISTRY-1861
Thanks,
Senaka.
On Thu, Sep 12, 2013 at 10:10 AM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi,
On 12 September 2013 09:42, Ajith Vitharana aji...@wso2.com wrote:
On Thu, Sep 12, 2013 at 9:30 AM, Nuwan Dias nuw...@wso2.com wrote:
Even after adding the image? Do you see any errors?
Yes. It works after set the values to none.
What is the error that you are getting after adding image to the correct
path?
Thanks,
Lakmali
Thanks
Ajith.
On Thu, Sep 12, 2013 at 9:15 AM, Ajith Vitharana aji...@wso2.comwrote:
On Wed, Sep 11, 2013 at 9:57 PM, Lakmali Baminiwatta
lakm...@wso2.comwrote:
Hi Ajith,
On 11 September 2013 21:33, Ajith Vitharana aji...@wso2.com wrote:
Hi AM team,
I'm getting following exception starting the G-Reg server. And also I
can't see the resouce api is published to publisher app ??
Have you added the images to the location?
Please fix those issues and this is blocking us providing a pack for
QA.
This is not an issue. This is related to the implementation requested
by GREG team [1]. Please add the relevant images to the GREG pack.
Yes, I meant that resouce api (Registry REST API ) is not
automatically publishing to publisher in the latest pack.
[1] https://wso2.org/jira/browse/APIMANAGER-1550
Thanks,
Lakmali
[2013-09-11 21:25:56,359] ERROR
{org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher} -
Error while reading image from icon path
java.io.FileNotFoundException:
/home/ajith/wso2/build/platform/4.2.0/products/greg/4.6.0/modules/distribution/target/wso2greg-4.6.0/./api-images/images.jpg
(No such file or directory)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.init(RandomAccessFile.java:216)
at java.io.RandomAccessFile.init(RandomAccessFile.java:101)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.getImageInputStream(APIManagerStartupPublisher.java:487)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.createAPIModel(APIManagerStartupPublisher.java:231)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.createAPIAtServerStartup(APIManagerStartupPublisher.java:194)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.invoke(APIManagerStartupPublisher.java:172)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:174)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:207)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:284)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.registerThrottlingAgent(ThrottlingAgentServiceComponent.java:123)
at
org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.activate(ThrottlingAgentServiceComponent.java:100)
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:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
[Dev] Carbon Kernel 5.0.0 Milestone Plan
Hi Sameera, Do we have a milestone plan for kernel 5.0.0 release.. If not shall we start building one... IMO a milestone deliverable can be a product distribution or even a finalized design artifact.. It would be better if we try to cover most of the ground level stuff by end of this year... Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] HTTP port -1 HTTPS port -1 ?
Saw this in the APIM big deployment too.
TID: [0] [AM] [2013-09-13 11:43:14,390] INFO
{org.apache.synapse.transport.passthru.PassThroughHttpListener} -
Pass-through HTTP Listener started on 0:0:0:0:0:0:0:0:10280
{org.apache.synapse.transport.passthru.PassThroughHttpListener}
TID: [0] [AM] [2013-09-13 11:43:14,401] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
Cluster domain: gw.am.150.domain
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
TID: [0] [AM] [2013-09-13 11:43:14,401] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
Using wka based membership management scheme
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
TID: [0] [AM] [2013-09-13 11:43:14,403] INFO
{org.wso2.carbon.core.clustering.hazelcast.util.MemberUtils} - Added
member: Host:192.168.18.17, Remote Host:null, Port: 5050, HTTP:-1,
HTTPS:-1, Domain: null, Sub-domain:null, Active:true
{org.wso2.carbon.core.clustering.hazelcast.util.MemberUtils}
TID: [0] [AM] [2013-09-13 11:43:22,819] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
Hazelcast initialized in 8412ms
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
TID: [0] [AM] [2013-09-13 11:43:22,902] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
Local member: [0c8d3a5d-751d-4822-a106-9316a14b1934] - Host:192.168.18.17,
Remote Host:null, Port: 4200, HTTP:10280, HTTPS:10243, Domain:
gw.am.150.domain, Sub-domain:mgt, Active:true
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
TID: [0] [AM] [2013-09-13 11:43:22,925] INFO
{org.wso2.carbon.core.clustering.hazelcast.util.MemberUtils} - Added
member: Host:192.168.18.17, Remote Host:null, Port: 4200, HTTP:10280,
HTTPS:10243, Domain: gw.am.150.domain, Sub-domain:mgt, Active:true
{org.wso2.carbon.core.clustering.hazelcast.util.MemberUtils}
TID: [0] [AM] [2013-09-13 11:43:24,123] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
Cluster initialization completed
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent}
On Fri, Sep 13, 2013 at 12:26 PM, Chamara Ariyarathne chama...@wso2.comwrote:
Note that this is not a full deplyoment. Only one APIM is fronted by ELB.
But two passthrough transports for each http and https are opened in elb
and Ports are mapped.
axis2.xmls are attached.
On Fri, Sep 13, 2013 at 12:22 PM, Chamara Ariyarathne
chama...@wso2.comwrote:
ELB 2.1.0 10/09/2013 build
http://10.100.1.185/packs/sep-10
APIM RC2 12/09/2013
http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/AM/
On Fri, Sep 13, 2013 at 11:46 AM, Amila Maha Arachchi ami...@wso2.comwrote:
On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne chama...@wso2.com
wrote:
Why this comes when API M joins ELB. (ELB local member port 4000)
[2013-09-12 17:31:35,189] INFO - MemberUtils Added member:
Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain:
null, Sub-domain:null, Active:true
Is this harmless? What needs to be configured for this to work the
correct way?
With which products do you get this? 4.2.0 based products or pre-4.2.0
products.
--
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com
Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
--
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
--
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
--
*Chamara Ariyarathne*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; *+94772786766*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] G-Reg + AM Integration L1/L2 issues {was: Re: G-REG + AM integration broken in new packs.}
Reason for [1] is not sharing the API-M database among the two nodes in the
cluster. We have fixed the issue in [2], Aparna is still to confirm whether
it worked (check JiRA comment). Can you please verify these in the latest
build (last night)?
Thanks,
NuwanD.
On Fri, Sep 13, 2013 at 12:21 PM, Senaka Fernando sen...@wso2.com wrote:
Hi all,
What's the plan for fixing these? We have 2 L1 issues, which doesn't seem
to be getting the right attention. Shall I move to AM?
[1] https://wso2.org/jira/browse/REGISTRY-1862
[2] https://wso2.org/jira/browse/REGISTRY-1861
Thanks,
Senaka.
On Thu, Sep 12, 2013 at 10:10 AM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi,
On 12 September 2013 09:42, Ajith Vitharana aji...@wso2.com wrote:
On Thu, Sep 12, 2013 at 9:30 AM, Nuwan Dias nuw...@wso2.com wrote:
Even after adding the image? Do you see any errors?
Yes. It works after set the values to none.
What is the error that you are getting after adding image to the correct
path?
Thanks,
Lakmali
Thanks
Ajith.
On Thu, Sep 12, 2013 at 9:15 AM, Ajith Vitharana aji...@wso2.comwrote:
On Wed, Sep 11, 2013 at 9:57 PM, Lakmali Baminiwatta lakm...@wso2.com
wrote:
Hi Ajith,
On 11 September 2013 21:33, Ajith Vitharana aji...@wso2.com wrote:
Hi AM team,
I'm getting following exception starting the G-Reg server. And also
I can't see the resouce api is published to publisher app ??
Have you added the images to the location?
Please fix those issues and this is blocking us providing a pack for
QA.
This is not an issue. This is related to the implementation
requested by GREG team [1]. Please add the relevant images to the GREG
pack.
Yes, I meant that resouce api (Registry REST API ) is not
automatically publishing to publisher in the latest pack.
[1] https://wso2.org/jira/browse/APIMANAGER-1550
Thanks,
Lakmali
[2013-09-11 21:25:56,359] ERROR
{org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher} -
Error while reading image from icon path
java.io.FileNotFoundException:
/home/ajith/wso2/build/platform/4.2.0/products/greg/4.6.0/modules/distribution/target/wso2greg-4.6.0/./api-images/images.jpg
(No such file or directory)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.init(RandomAccessFile.java:216)
at java.io.RandomAccessFile.init(RandomAccessFile.java:101)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.getImageInputStream(APIManagerStartupPublisher.java:487)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.createAPIModel(APIManagerStartupPublisher.java:231)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.createAPIAtServerStartup(APIManagerStartupPublisher.java:194)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.invoke(APIManagerStartupPublisher.java:172)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:174)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:207)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:284)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.registerThrottlingAgent(ThrottlingAgentServiceComponent.java:123)
at
org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.activate(ThrottlingAgentServiceComponent.java:100)
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
Re: [Dev] HTTP port -1 HTTPS port -1 ?
This logs appear when ELB joins ELB cluster.. I guess its harmless. On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne chama...@wso2.comwrote: Why this comes when API M joins ELB. (ELB local member port 4000) [2013-09-12 17:31:35,189] INFO - MemberUtils Added member: Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain: null, Sub-domain:null, Active:true Is this harmless? What needs to be configured for this to work the correct way? -- *Chamara Ariyarathne* Senior Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; *+94772786766* -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Some Registry features with version 4.2.1 in chunk-02 which have no released 4.2.0 version
Hi Sameera, There are set of registry bundles released with chunk01, but the features which are bundled those jars not released. eg: released registry bundles. moduleorg.wso2.carbon.registry.admin.api/4.2.0/module moduleorg.wso2.carbon.registry.common/4.2.0/module moduleorg.wso2.carbon.registry.common.ui/4.2.0/module moduleorg.wso2.carbon.registry.eventing/4.2.0/module moduleorg.wso2.carbon.registry.indexing/4.2.0/module moduleorg.wso2.carbon.registry.properties.ui/4.2.0/module moduleorg.wso2.carbon.registry.properties/4.2.0/module moduleorg.wso2.carbon.registry.resource.ui/4.2.0/module moduleorg.wso2.carbon.registry.resource/4.2.0/module moduleorg.wso2.carbon.registry.search.ui/4.2.0/module moduleorg.wso2.carbon.registry.search/4.2.0/module moduleorg.wso2.carbon.registry.servlet/4.2.0/module moduleorg.wso2.carbon.registry.profiles/4.2.0/module moduleorg.wso2.carbon.registry.profiles.ui/4.2.0/module released governance bundles: moduleorg.wso2.carbon.governance.api/4.2.0/module Thanks Ajith On Fri, Sep 13, 2013 at 12:27 PM, Ajith Vitharana aji...@wso2.com wrote: On Fri, Sep 13, 2013 at 11:49 AM, Lasantha Fernando lasan...@wso2.comwrote: Hi all, In chunk-02 features/pom, the registry features org.wso2.carbon.registry.community.features.feature org.wso2.carbon.governance.metadata.feature are pointing to 4.2.1 version. But they don't seem to have been released with chunk-01 (with a 4.2.0 version). Is there any reason for using 4.2.1 version number?. Maybe am missing something here. The reason this org.wso2.carbon.registry.eventing.4.2.0 jar is released (bundled with org.wso2.carbon.registry.community.features.feature). Therefore we created new feature version for org.wso2.carbon.registry.eventing.4.2.1 jar , same applied to org.wso2.carbon.governance.metadata.feature as well. Thanks Ajith Thanks, Lasantha -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Commits] [Carbon-platform] svn commit r185274 - carbon/platform/branches/4.2.0/product-releases/chunk-02/components
Hi, I am also getting the same error while trying to build with clean repo. Thanks and Regards, -Ayash On Fri, Sep 13, 2013 at 11:39 AM, Ajith Vitharana aji...@wso2.com wrote: [INFO] Scanning for projects... [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon:product-releases-components:4.2.0-chunk02 (/home/ajith/wso2/build/platform/4.2.0/product-releases/chunk-02/components/pom.xml) has 1 error [ERROR] Child module /home/ajith/wso2/build/platform/4.2.0/product-releases/chunk-02/components/../../../components/stratos/usage/org.wso2.carbon.keystore.mgt/2.2.1 of /home/ajith/wso2/build/platform/4.2.0/product-releases/chunk-02/components/pom.xml does not exist [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. Please update the chunk02 poms properly when you create patch versions. Thanks Ajith On Thu, Sep 12, 2013 at 10:01 PM, danush...@wso2.com wrote: Author: danush...@wso2.com Date: Thu Sep 12 22:01:37 2013 New Revision: 185274 URL: http://wso2.org/svn/browse/wso2?view=revrevision=185274 Log: add keystore new version Modified: carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml Modified: carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml URL: http://wso2.org/svn/browse/wso2/carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml?rev=185274r1=185273r2=185274view=diff == --- carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml (original) +++ carbon/platform/branches/4.2.0/product-releases/chunk-02/components/pom.xml Thu Sep 12 22:01:37 2013 @@ -105,6 +105,7 @@ module../../../components/stratos/throttling/org.wso2.carbon.throttling.ui/2.2.0/module module../../../components/stratos/usage/org.wso2.carbon.usage/2.2.0/module module../../../components/stratos/usage/org.wso2.carbon.usage.ui/2.2.0/module + module../../../components/stratos/usage/org.wso2.carbon.keystore.mgt/2.2.1/module module../../../components/transport-mgt/org.wso2.carbon.transport.vfs/4.2.0/module ___ Commits mailing list comm...@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/commits -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ 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] Carbon Kernel 5.0.0 Milestone Plan
Hi Prabath, We don't have a milestone plan at the moment. We had the initial high level discussions sometime back. The plan is to kick off the low level meetings during the week starting from 23rd of September. I am in support and Azeez is away during the next week. In mean time I will start the subject. We can review the plan and fine-tune during that week. Thanks, Sameera. On Fri, Sep 13, 2013 at 12:34 PM, Prabath Siriwardena prab...@wso2.comwrote: Hi Sameera, Do we have a milestone plan for kernel 5.0.0 release.. If not shall we start building one... IMO a milestone deliverable can be a product distribution or even a finalized design artifact.. It would be better if we try to cover most of the ground level stuff by end of this year... Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) method runs twice on single deploy
Hi, Issue is moved to CARBON project. Will check.. Thanks, Manoj Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188 On Fri, Sep 13, 2013 at 12:21 PM, Nirmal Fernando nir...@wso2.com wrote: Carbon team FYI. On Fri, Sep 13, 2013 at 12:19 PM, Nandika Jayawardana nand...@wso2.comwrote: If would be great if someone from platform team can take a look. Amal is currently working on another bps task. Regards Nandika On Thu, Sep 12, 2013 at 9:10 PM, Nirmal Fernando nir...@wso2.com wrote: Did anyone look after this issue? On Mon, Sep 2, 2013 at 11:58 AM, Amal Gunatilake am...@wso2.com wrote: Please have a look. org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) *method inside the kernel runs twice on single deploy which repeats the same log twice*. This issue was found when tracking the JIRA issue https://wso2.org/jira/browse/BPS-215 - Two error log message are showing when return a one error message When tracking as a BPS issue, it was discovered that it's a common issue for system logs which produces in kernel. Thanks Regards, Amal. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] G-Reg + AM Integration L1/L2 issues {was: Re: G-REG + AM integration broken in new packs.}
Hi Nuwan,
Both the issues were fixed with Ruwan's patch according to Aparna. He has
not resolved since he didn't have time to validate with fresh G-Reg packs.
I marked them as fixed, and Aparna will reopen if it still exists.
Thanks,
Senaka.
On Fri, Sep 13, 2013 at 12:36 PM, Nuwan Dias nuw...@wso2.com wrote:
Reason for [1] is not sharing the API-M database among the two nodes in
the cluster. We have fixed the issue in [2], Aparna is still to confirm
whether it worked (check JiRA comment). Can you please verify these in the
latest build (last night)?
Thanks,
NuwanD.
On Fri, Sep 13, 2013 at 12:21 PM, Senaka Fernando sen...@wso2.com wrote:
Hi all,
What's the plan for fixing these? We have 2 L1 issues, which doesn't seem
to be getting the right attention. Shall I move to AM?
[1] https://wso2.org/jira/browse/REGISTRY-1862
[2] https://wso2.org/jira/browse/REGISTRY-1861
Thanks,
Senaka.
On Thu, Sep 12, 2013 at 10:10 AM, Lakmali Baminiwatta
lakm...@wso2.comwrote:
Hi,
On 12 September 2013 09:42, Ajith Vitharana aji...@wso2.com wrote:
On Thu, Sep 12, 2013 at 9:30 AM, Nuwan Dias nuw...@wso2.com wrote:
Even after adding the image? Do you see any errors?
Yes. It works after set the values to none.
What is the error that you are getting after adding image to the correct
path?
Thanks,
Lakmali
Thanks
Ajith.
On Thu, Sep 12, 2013 at 9:15 AM, Ajith Vitharana aji...@wso2.comwrote:
On Wed, Sep 11, 2013 at 9:57 PM, Lakmali Baminiwatta
lakm...@wso2.com wrote:
Hi Ajith,
On 11 September 2013 21:33, Ajith Vitharana aji...@wso2.com wrote:
Hi AM team,
I'm getting following exception starting the G-Reg server. And also
I can't see the resouce api is published to publisher app ??
Have you added the images to the location?
Please fix those issues and this is blocking us providing a pack
for QA.
This is not an issue. This is related to the implementation
requested by GREG team [1]. Please add the relevant images to the GREG
pack.
Yes, I meant that resouce api (Registry REST API ) is not
automatically publishing to publisher in the latest pack.
[1] https://wso2.org/jira/browse/APIMANAGER-1550
Thanks,
Lakmali
[2013-09-11 21:25:56,359] ERROR
{org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher} -
Error while reading image from icon path
java.io.FileNotFoundException:
/home/ajith/wso2/build/platform/4.2.0/products/greg/4.6.0/modules/distribution/target/wso2greg-4.6.0/./api-images/images.jpg
(No such file or directory)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.init(RandomAccessFile.java:216)
at java.io.RandomAccessFile.init(RandomAccessFile.java:101)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.getImageInputStream(APIManagerStartupPublisher.java:487)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.createAPIModel(APIManagerStartupPublisher.java:231)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.createAPIAtServerStartup(APIManagerStartupPublisher.java:194)
at
org.wso2.carbon.apimgt.startup.publisher.APIManagerStartupPublisher.invoke(APIManagerStartupPublisher.java:172)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.startup(CarbonCoreServiceComponent.java:174)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.completeInitialization(StartupFinalizerServiceComponent.java:207)
at
org.wso2.carbon.core.internal.StartupFinalizerServiceComponent.serviceChanged(StartupFinalizerServiceComponent.java:284)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.registerThrottlingAgent(ThrottlingAgentServiceComponent.java:123)
at
org.wso2.carbon.throttling.agent.internal.ThrottlingAgentServiceComponent.activate(ThrottlingAgentServiceComponent.java:100)
at
Re: [Dev] org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) method runs twice on single deploy
Hi Do you have any customized log4j.properties in your BPS pack? Sometimes, improper configuration of log4j.properties would also cause the same issue. Thanks, Reka On Mon, Sep 2, 2013 at 11:58 AM, Amal Gunatilake am...@wso2.com wrote: Please have a look. org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) *method inside the kernel runs twice on single deploy which repeats the same log twice*. This issue was found when tracking the JIRA issue https://wso2.org/jira/browse/BPS-215 - Two error log message are showing when return a one error message When tracking as a BPS issue, it was discovered that it's a common issue for system logs which produces in kernel. Thanks Regards, Amal. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- 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] org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) method runs twice on single deploy
Hi Nirmal, We really appreciate your reminder and as well as your motivation of going after everything even they are not related to you. We will take this from now on. Thanks, Sameera. On Fri, Sep 13, 2013 at 12:21 PM, Nirmal Fernando nir...@wso2.com wrote: Carbon team FYI. On Fri, Sep 13, 2013 at 12:19 PM, Nandika Jayawardana nand...@wso2.comwrote: If would be great if someone from platform team can take a look. Amal is currently working on another bps task. Regards Nandika On Thu, Sep 12, 2013 at 9:10 PM, Nirmal Fernando nir...@wso2.com wrote: Did anyone look after this issue? On Mon, Sep 2, 2013 at 11:58 AM, Amal Gunatilake am...@wso2.com wrote: Please have a look. org.apache.axis2.engine.AxisConfiguration, notifyObservers(AxisEvent event, AxisService service) *method inside the kernel runs twice on single deploy which repeats the same log twice*. This issue was found when tracking the JIRA issue https://wso2.org/jira/browse/BPS-215 - Two error log message are showing when return a one error message When tracking as a BPS issue, it was discovered that it's a common issue for system logs which produces in kernel. Thanks Regards, Amal. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Commits] [Carbon-kernel] svn commit r183767 - in carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules: clustering/src/org/apache/axis2/clustering/management kernel/src/org/
Hi Sameera,
Can you pls commit this to trunk. I'm getting a build failure..
thanks,
On Sat, Aug 31, 2013 at 5:00 PM, same...@wso2.com wrote:
Author: same...@wso2.com
Date: Sat Aug 31 17:00:02 2013
New Revision: 183767
URL: http://wso2.org/svn/browse/wso2?view=revrevision=183767
Log:
Adding a new API method to GroupMgtAgent. This allows us to add WKA
members externally.
Modified:
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/clustering/src/org/apache/axis2/clustering/management/DefaultGroupManagementAgent.java
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/kernel/src/org/apache/axis2/clustering/management/GroupManagementAgent.java
Modified:
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/clustering/src/org/apache/axis2/clustering/management/DefaultGroupManagementAgent.java
URL:
http://wso2.org/svn/browse/wso2/carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/clustering/src/org/apache/axis2/clustering/management/DefaultGroupManagementAgent.java?rev=183767r1=183766r2=183767view=diff
==
---
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/clustering/src/org/apache/axis2/clustering/management/DefaultGroupManagementAgent.java
(original)
+++
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/clustering/src/org/apache/axis2/clustering/management/DefaultGroupManagementAgent.java
Sat Aug 31 17:00:02 2013
@@ -111,6 +111,10 @@
return members;
}
+public void addMember(Member member){
+ // Nothing to do
+}
+
public void send(GroupManagementCommand command) throws
ClusteringFault {
sender.sendToGroup(command,
membershipManager,
Modified:
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/kernel/src/org/apache/axis2/clustering/management/GroupManagementAgent.java
URL:
http://wso2.org/svn/browse/wso2/carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/kernel/src/org/apache/axis2/clustering/management/GroupManagementAgent.java?rev=183767r1=183766r2=183767view=diff
==
---
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/kernel/src/org/apache/axis2/clustering/management/GroupManagementAgent.java
(original)
+++
carbon/kernel/branches/4.2.0/dependencies/axis2/1.6.1-wso2v10/modules/kernel/src/org/apache/axis2/clustering/management/GroupManagementAgent.java
Sat Aug 31 17:00:02 2013
@@ -84,6 +84,13 @@
*/
ListMember getMembers();
+/**
+ * Add a well-known member
+ *
+ * @param member The well-known member
+ */
+void addMember(Member member);
+
/**
* Send a GroupManagementCommand to the group
___
Commits mailing list
comm...@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/commits
--
Supun Malinga,
Senior Software Engineer,
WSO2 Inc.
http://wso2.com
email: sup...@wso2.com sup...@wso2.com
mobile: +94 (0)71 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ELB 2.1.0 with GREG 4.6.0 clustered setup
Hi, We are unable to test on ELB fronted Greg clustered setup due to timeout issue, because of this issue we are testing the Greg without the ELB. We have reported this issue with chunk01 release as well (Refer mail thread [1]). Therefore we won't be able to release the ELB 2.1.0 with chunk02 release as well. This will be a really big issue customer point of view, because there's no way of using our product with our ELB. Please provide us a testable ELB 2.1.0 pack. [1] [Dev] - Accessing the Management Console after page times out returns a Connection reset error without redirecting to the Login page -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk-02 Nightly Build packs - 12/09/2013
Hi, ELB should be using 2.1.1.wso2v9 and I fixed it in chunk-02 earlier. I will check. Thanks! On Thu, Sep 12, 2013 at 8:01 PM, Ruwan Yatawara ruw...@wso2.com wrote: Hi Isuru, The mediation component which is needed for building ELB is referring to Synapse version 2.1.2.wso2v1, I was not sure whether it was right to revert this back to version 2.1.1.wso2v9 which is what the rest of the chunk-02 products are using. We can proceed with a build once this issue is rectified. Thanks and Regards, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com On Thu, Sep 12, 2013 at 7:25 PM, Isuru Perera isu...@wso2.com wrote: Hi, Why ELB is not listed? On Thu, Sep 12, 2013 at 7:05 PM, Ruwan Yatawara ruw...@wso2.com wrote: QA Team, Packs built off 4.2.0 Branch/Chunk-02 is available at the following locations. API Manager : http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/AM/wso2am-1.5.0_RC2.zip GReg : http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/GREG/wso2greg-4.6.0_N120913.zip CEP : http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/CEP/wso2cep-3.0.0_N120913.zip Thanks and Regards, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Branch 4.2.0 kernel build failure
$subject. This is the error. Seems security verifier pom refers to a wrong parent pom. [ERROR] The project org.wso2.carbon:SecVerifier:4.2.0 (/home/maninda/c/carbon/kernel/branches/4.2.0/distribution/integration/security-verifier/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.wso2.carbon:carbon-products:pom:4.2.0 in http://repo1.maven.org/maven2was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 22, column 13 - [Help 2] [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/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException * Maninda Edirisooriya* Software Engineer *WSO2, Inc. *lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *Phone* : +94 777603226 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
What is the ELB version being used?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
--
Nuwan Dias
Senior 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] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
Geeth,
Did you commit your fixes to trunk which fix this AuthenticationAdmin
requests getting dispatched to ELB issue?
On Fri, Sep 13, 2013 at 3:07 PM, Nuwan Dias nuw...@wso2.com wrote:
What is the ELB version being used?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
--
Nuwan Dias
Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
ELB 2.1.0 from sept10th build.
On Fri, Sep 13, 2013 at 3:09 PM, Nirmal Fernando nir...@wso2.com wrote:
Geeth,
Did you commit your fixes to trunk which fix this AuthenticationAdmin
requests getting dispatched to ELB issue?
On Fri, Sep 13, 2013 at 3:07 PM, Nuwan Dias nuw...@wso2.com wrote:
What is the ELB version being used?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
--
Nuwan Dias
Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
Shouldn't this case hold true for ESB , DSS or any other server that pushes
XML content through Admin service calls?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
Isuru,
This is a blocker for chunk02.
On Fri, Sep 13, 2013 at 3:16 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Shouldn't this case hold true for ESB , DSS or any other server that
pushes XML content through Admin service calls?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
Hi Sumedha,
I will check on this.
On Fri, Sep 13, 2013 at 3:18 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Isuru,
This is a blocker for chunk02.
On Fri, Sep 13, 2013 at 3:16 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Shouldn't this case hold true for ESB , DSS or any other server that
pushes XML content through Admin service calls?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
--
/sumedha
m: +94 773017743
b : bit.ly/sumedha
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB
Hi,
Geeth has already committed related changes. Please see:
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.1.1-wso2v9/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/nhttp/util/RESTUtil.java
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/components/transport-mgt/org.wso2.carbon.transport.nhttp/4.2.0/src/main/java/org/wso2/carbon/transport/nhttp/api/NHttpGetProcessor.java
On Fri, Sep 13, 2013 at 3:09 PM, Nirmal Fernando nir...@wso2.com wrote:
Geeth,
Did you commit your fixes to trunk which fix this AuthenticationAdmin
requests getting dispatched to ELB issue?
On Fri, Sep 13, 2013 at 3:07 PM, Nuwan Dias nuw...@wso2.com wrote:
What is the ELB version being used?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more
--
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
--
Nuwan Dias
Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog:
[Dev] Start up errors - ConcurrentModificationException from CarbonDeploymentSchedulerTask
Hi All,
Observed the following error in the latest pack (G-Reg) - chunk02
[2013-09-13 15:52:39,357] ERROR
{org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} - Error
while running deployment scheduler..
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$EntryIterator.next(HashMap.java:834)
at java.util.HashMap$EntryIterator.next(HashMap.java:832)
at
org.apache.axis2.deployment.RepositoryListener.loadOtherDirectories(RepositoryListener.java:270)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:253)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:65)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:110)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
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)
[2013-09-13 15:52:39,614] INFO
{org.apache.tomcat.util.net.NioSelectorPool} - Using a shared
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Build Failure - mediation/mediation-library component
Hi I'm getting the following error when trying to build mediation-library component. [INFO] - [INFO] [INFO] Reactor Summary: [INFO] [INFO] WSO2 Carbon - Mediation Module SUCCESS [0.164s] [INFO] WSO2 Carbon - Template Editor Aggregator Module ... SUCCESS [0.013s] [INFO] WSO2 Carbon - Template OSGi Service ... SUCCESS [4.277s] [INFO] WSO2 Carbon - Template Editor Common .. SUCCESS [1.013s] [INFO] WSO2 Carbon - Template Editor BE .. SUCCESS [1.636s] [INFO] WSO2 Carbon - Template Editor UI .. SUCCESS [1.061s] [INFO] WSO2 Carbon - Message Store Module SUCCESS [0.006s] [INFO] WSO2 Carbon - Message Store Admin BE .. SUCCESS [1.142s] [INFO] WSO2 Carbon - Message Store Admin UI .. SUCCESS [0.824s] [INFO] WSO2 Carbon - Message Processor Module SUCCESS [0.005s] [INFO] WSO2 Carbon - Message processor Admin BE .. SUCCESS [1.076s] [INFO] WSO2 Carbon - Message processor Admin UI .. SUCCESS [1.110s] [INFO] WSO2 Carbon - Mediation Template Libray Module SUCCESS [0.004s] [INFO] WSO2 Carbon - Mediation Library UI FAILURE [0.687s] [INFO] WSO2 Carbon - Mediation Library ... SKIPPED [INFO] Building wso2 CARBON connectors ... SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Core SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Twitter . SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Jira SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Salesforce .. SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Twilio .. SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Google Spreadsheet SKIPPED [INFO] WSO2 Carbon - Synapse Security Aggregator Module .. SKIPPED [INFO] WSO2 Carbon - Synapse Security SKIPPED [INFO] WSO2 Carbon - Synapse Security-UI . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 13.874s [INFO] Finished at: Fri Sep 13 03:37:52 PDT 2013 [INFO] Final Memory: 147M/1215M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.mediation.library.ui: Compilation failure: Compilation failure: [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[23,65] package org.wso2.carbon.mediation.library.stub.upload.types.carbon does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[24,52] package org.wso2.carbon.mediation.library.stub.upload does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[33,17] cannot find symbol [ERROR] symbol : class LibraryFileItem [ERROR] location: class org.wso2.carbon.mediation.library.ui.fileupload.MediationLibraryUploadClient [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[34,12] cannot find symbol [ERROR] symbol : class MediationLibraryUploaderStub [ERROR] location: class org.wso2.carbon.mediation.library.ui.fileupload.MediationLibraryUploadClient [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/Test.java:[22,58] package org.wso2.carbon.mediation.library.stub.types.carbon does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/LibraryAdminClient.java:[26,45] package org.wso2.carbon.mediation.library.stub does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/LibraryAdminClient.java:[27,45] package org.wso2.carbon.mediation.library.stub does not exist [ERROR]
Re: [Dev] Build Failure - mediation/mediation-library component
Pls make sure you did build the relevant service stubs successfully. On Fri, Sep 13, 2013 at 4:05 PM, Ruwan Yatawara ruw...@wso2.com wrote: Hi I'm getting the following error when trying to build mediation-library component. [INFO] - [INFO] [INFO] Reactor Summary: [INFO] [INFO] WSO2 Carbon - Mediation Module SUCCESS [0.164s] [INFO] WSO2 Carbon - Template Editor Aggregator Module ... SUCCESS [0.013s] [INFO] WSO2 Carbon - Template OSGi Service ... SUCCESS [4.277s] [INFO] WSO2 Carbon - Template Editor Common .. SUCCESS [1.013s] [INFO] WSO2 Carbon - Template Editor BE .. SUCCESS [1.636s] [INFO] WSO2 Carbon - Template Editor UI .. SUCCESS [1.061s] [INFO] WSO2 Carbon - Message Store Module SUCCESS [0.006s] [INFO] WSO2 Carbon - Message Store Admin BE .. SUCCESS [1.142s] [INFO] WSO2 Carbon - Message Store Admin UI .. SUCCESS [0.824s] [INFO] WSO2 Carbon - Message Processor Module SUCCESS [0.005s] [INFO] WSO2 Carbon - Message processor Admin BE .. SUCCESS [1.076s] [INFO] WSO2 Carbon - Message processor Admin UI .. SUCCESS [1.110s] [INFO] WSO2 Carbon - Mediation Template Libray Module SUCCESS [0.004s] [INFO] WSO2 Carbon - Mediation Library UI FAILURE [0.687s] [INFO] WSO2 Carbon - Mediation Library ... SKIPPED [INFO] Building wso2 CARBON connectors ... SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Core SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Twitter . SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Jira SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Salesforce .. SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Twilio .. SKIPPED [INFO] WSO2 Carbon - Cloud Connector For Google Spreadsheet SKIPPED [INFO] WSO2 Carbon - Synapse Security Aggregator Module .. SKIPPED [INFO] WSO2 Carbon - Synapse Security SKIPPED [INFO] WSO2 Carbon - Synapse Security-UI . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 13.874s [INFO] Finished at: Fri Sep 13 03:37:52 PDT 2013 [INFO] Final Memory: 147M/1215M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.mediation.library.ui: Compilation failure: Compilation failure: [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[23,65] package org.wso2.carbon.mediation.library.stub.upload.types.carbon does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[24,52] package org.wso2.carbon.mediation.library.stub.upload does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[33,17] cannot find symbol [ERROR] symbol : class LibraryFileItem [ERROR] location: class org.wso2.carbon.mediation.library.ui.fileupload.MediationLibraryUploadClient [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/fileupload/MediationLibraryUploadClient.java:[34,12] cannot find symbol [ERROR] symbol : class MediationLibraryUploaderStub [ERROR] location: class org.wso2.carbon.mediation.library.ui.fileupload.MediationLibraryUploadClient [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/Test.java:[22,58] package org.wso2.carbon.mediation.library.stub.types.carbon does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/LibraryAdminClient.java:[26,45] package org.wso2.carbon.mediation.library.stub does not exist [ERROR] /home/wso2/4.2.0_branch/platform/components/mediation/mediation-library/org.wso2.carbon.mediation.library.ui/4.2.0/src/main/java/org/wso2/carbon/mediation/library/ui/LibraryAdminClient.java:[27,45] package
Re: [Dev] Preparing ELB 2.1.0 release
Hi, I noticed some of the issueshttps://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+10210+AND+labels+%3D+passthru-transportwere marked as fixed today. Thanks for looking in to those. There are few in open state still. For example, https://wso2.org/jira/browse/LB-88. This is probably the same issue with spinning? Please check the NPEs as well. https://wso2.org/jira/browse/LB-85 https://wso2.org/jira/browse/LB-105 Thanks. On Sun, Sep 8, 2013 at 8:34 PM, Isuru Perera isu...@wso2.com wrote: Hi Ravi, Could you please go through the issues here: https://wso2.org/jira/browse/LB-106?jql=project%20%3D%2010210%20AND%20labels%20%3D%20passthru-transport I created a label for passthru transport related issues. Thanks! On Thu, Sep 5, 2013 at 5:30 PM, Ravi Undupitiya r...@wso2.com wrote: LB-97 https://wso2.org/jira/browse/LB-97 - this has been fixed. LB-106 https://wso2.org/jira/browse/LB-106, LB-75https://wso2.org/jira/browse/LB-75 , LB-90 https://wso2.org/jira/browse/LB-90 and LB-105https://wso2.org/jira/browse/LB-105 - should be due to the spinning issue, i'm re-testing these scenarios with the spinning fix to see if they reoccur on RC8 pack. On Thu, Sep 5, 2013 at 12:05 PM, Isuru Perera isu...@wso2.com wrote: Hi all, I have started working on fixing issues on ELB. Following are some synapse related issues that needs to be fixed. ESB Team, please check these issues and let me know whether those can be fixed. https://wso2.org/jira/browse/LB-74 https://wso2.org/jira/browse/LB-97 https://wso2.org/jira/browse/LB-106 https://wso2.org/jira/browse/LB-75 https://wso2.org/jira/browse/LB-90 https://wso2.org/jira/browse/LB-105 I will check on other issues and update this thread. Thanks! -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com * * *E-mail: r...@wso2.com **M: **+94 772 930 712* * *Lean . Enterprise . Middleware -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] New Stratos common feature version added
Hi Danushka, U have updated the stratos.common.server feature, but not added a new stratos.common feature. I made the necessary changes. Regards, Ruwan Yatawara Software Engineer, WSO2 Inc. lean . enterprise . middleware email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://ruwansrants.blogspot.com/ www: :http://wso2.com On Fri, Sep 13, 2013 at 11:27 AM, Amila Maha Arachchi ami...@wso2.comwrote: FYI. Please update the stratos common feature version in your product. On Fri, Sep 13, 2013 at 11:12 AM, Danushka Fernando danush...@wso2.comwrote: Hi all, I have created new version of keystore.mgt component and a version of stratos.common.server.feature. (2.2.1). Please upgrade your products to have this new version. For the cloud to work with appfactory we need this in API manager next version and Stratos Controller next version. Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 -- *Amila Maharachchi* Senior Technical Lead 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ELB 2.1.0 Release Status
Apart from JIRA issueshttps://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+LB+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%222.1.0%22+ORDER+BY+priority+DESCmode=hide, following are the critical issues for ELB 2.1.0 now. - [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB - https://wso2.org/jira/browse/APIMANAGER-1649 - [Dev] ELB 2.1.0 with GREG 4.6.0 clustered setup - ELB 2.1.0 with ESB 4.8.0 W/M setup not working - dev@ - Need to check (But ESB is not planned for chunk-02) Thanks! -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] Review Integration Test progress weekly { was: Re: Increasing the IS Integration test coverage}
Hi All, I will update with coverage report by Monday for the first week. I have to complete few more things in multiple user store scenarios. Sorry for the delay. Thanks, Pushpalanka Jayawardhana Software Engineer WSO2 Lanka (pvt) Ltd [image: Facebook]http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.facebook.com%2Fpushpalanka [image: Twitter]http://s.wisestamp.com/links?url=http%3A%2F%2Ftwitter.com%2FPushpalanka [image: LinkedIn]http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.linkedin.com%2Fprofile%2Fview%3Fid%3D75175642%26trk%3Dtab_pro [image: Blogger]http://s.wisestamp.com/links?url=http%3A%2F%2Fpushpalankajaya.blogspot.com%2F [image: SlideShare]http://s.wisestamp.com/links?url=http%3A%2F%2Fwww.slideshare.net%2FPushpalanka Mobile: +94779716248 http://s.wisestamp.com/links?url=http%3A%2F%2Fr1.wisestamp.com%2Fr%2Flanding%3Fu%3Dc984892c0c4ca423%26v%3D3.13.2%26t%3D1361257731639%26promo%3D10%26dest%3Dhttp%253A%252F%252Fwww.wisestamp.com%252Femail-install%253Futm_source%253Dextension%2526utm_medium%253Demail%2526utm_campaign%253Dpromo_10 On Fri, Sep 13, 2013 at 1:23 AM, Prabath Siriwardena prab...@wso2.comwrote: Hi Chamath, I guess we need to review of the progress of integration test writing weekly - in terms of code coverage.. That will help us find out where we are and are we in a position to get 60% mark before mid Oct... Thanks regards, -Prabath On Fri, Sep 6, 2013 at 10:34 AM, Chamath Gunawardana chama...@wso2.comwrote: Hi, As we need to increase the integration test coverage of IS for the next release we need identify the priority areas/critical paths that we first need to be covered. Hence your input on this will greatly help. Please pitch in.. Please find below some resources and guidelines that you can get familiar with before we start writing the tests next week. * Krishantha and the Automation team have already written IS tests that we can refer to get started in [1]. * Please make your self familiar with automation framework and guidelines on writing tests in [2] if not already. * Use of the TestNG Annotations properly as Krishantha have mentioned in another mail thread since this will avoid simultaneous test runs which will cause tests to be fail. Also make sure you run the TestNG version 6.1.1. * Make server state consistent by cleaning the data after test. Also please find the IS integration test allocations in [3]. [1] - https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/products/is/4.5.0/modules/integration/src/test/java/org/wso2/identity/integration/tests [2] - http://docs.wso2.org/display/TA100/Best+Practices+for+Writing+Integration+Tests [3] - https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AtS5Oii8ega9dEV4Qy05VVhoZ1Vkb2YzaHJWZGZJV3c#gid=1 Thanks, -- Best Regards, Chamath Gunawardana Technical Lead; WSO2 Inc. Mobile : +94776322240 -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cant assign more than one role to a user.
Hi All, CEP 3.0.0 RC3 pack also contains similar issue... Chathurika has reported this issue in https://wso2.org/jira/browse/CEP-427. Thanks Regards, Mohan On Wed, Aug 7, 2013 at 3:07 PM, Asela Pathberiya as...@wso2.com wrote: We did not found this issue in the AS pack in here[1]. I do not think, QA team also have experienced such issue... [1] http://atuwa.private.wso2.com/Products/releases/05-08-2013/ Thanks, Asela. On Wed, Aug 7, 2013 at 11:53 AM, Nalin Chandraratne na...@wso2.com wrote: Hi, The issue occurs when trying to assign more than one role to a user. This test was done in the pack built on 2013.08.07-10:50:41 [2013-08-07 11:31:40,240] ERROR - DatabaseUtil Unique index or primary key violation: CONSTRAINT_INDEX_BA ON PUBLIC.UM_USER_ROLE(UM_USER_ID, UM_ROLE_ID, UM_TENANT_ID); SQL statement: INSERT INTO UM_USER_ROLE (UM_ROLE_ID, UM_USER_ID, UM_TENANT_ID) VALUES ((SELECT UM_ID FROM UM_ROLE WHERE UM_ROLE_NAME=? AND UM_TENANT_ID=?),(SELECT UM_ID FROM UM_USER WHERE UM_USER_NAME=? AND UM_TENANT_ID=?), ?) [23001-140] org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation: CONSTRAINT_INDEX_BA ON PUBLIC.UM_USER_ROLE(UM_USER_ID, UM_ROLE_ID, UM_TENANT_ID); SQL statement: INSERT INTO UM_USER_ROLE (UM_ROLE_ID, UM_USER_ID, UM_TENANT_ID) VALUES ((SELECT UM_ID FROM UM_ROLE WHERE UM_ROLE_NAME=? AND UM_TENANT_ID=?),(SELECT UM_ID FROM UM_USER WHERE UM_USER_NAME=? AND UM_TENANT_ID=?), ?) [23001-140] at org.h2.jdbc.JdbcPreparedStatement.executeBatch(JdbcPreparedStatement.java:1098) at org.wso2.carbon.user.core.util.DatabaseUtil.udpateUserRoleMappingInBatchMode(DatabaseUtil.java:504) at org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager.doUpdateRoleListOfUser(JDBCUserStoreManager.java:1714) at org.wso2.carbon.user.core.common.AbstractUserStoreManager.updateRoleListOfUser(AbstractUserStoreManager.java:1284) at org.wso2.carbon.user.mgt.UserRealmProxy.updateRolesOfUser(UserRealmProxy.java:1790) at org.wso2.carbon.user.mgt.UserAdmin.addRemoveRolesOfUser(UserAdmin.java:650) 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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212) at org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:169) at org.apache.axis2.transport.local.LocalTransportReceiver.processMessage(LocalTransportReceiver.java:82) at org.wso2.carbon.core.transports.local.CarbonLocalTransportSender.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45) at org.apache.axis2.transport.local.LocalTransportSender.invoke(LocalTransportSender.java:77) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:398) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149) at org.wso2.carbon.user.mgt.stub.UserAdminStub.addRemoveRolesOfUser(UserAdminStub.java:4759) at org.wso2.carbon.user.mgt.ui.UserAdminClient.addRemoveRolesOfUser(UserAdminClient.java:236) at org.apache.jsp.user.edit_002duser_002droles_002dfinish_jsp._jspService(org.apache.jsp.user.edit_002duser_002droles_002dfinish_jsp:172) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155) at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:71) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128) at
[Dev] WSO2 ELB loadbalancer.conf links to blogs
Hi, Currently, the WSO2 ELB loadbalancer.conf has links to following blog articles. - http://nirmalfdo.blogspot.com/2012/06/fronting-wso2-application-server-50.html - http://blog.afkham.org/2011/09/wso2-load-balancer-how-it-works.html - http://nirmalfdo.blogspot.com/2013/01/scale-up-early-scale-down-slowly.html Shall we have links to latest WSO2 Docs? For example, http://docs.wso2.org/display/CLUSTER420/Clustering+WSO2+Products http://docs.wso2.org/display/ELB210/WSO2+Elastic+Load+Balancer+Documentation http://docs.wso2.org/display/ELB210/Auto-Scaling+in+Load+Balancer We should be able use doc links for latest docs. For example: http://docs.wso2.org/elastic-load-balancer Just an idea! Thanks! -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Major performance issues POX Security Handler
Hi Piyum, What was the fix for the issue? I cannot locate a commit mail for this particular issue. I got the same with ELB 2.0.3 as well. Thanks and Regrads, Harshana On Fri, Aug 23, 2013 at 12:05 AM, Piyum Fernando pi...@wso2.com wrote: Hi Ishan, We fixed the issue mentioned in WSAS-1473. I will have a look in to this again. Thanks. On Fri, Aug 23, 2013 at 12:25 PM, Ishan Jayawardena is...@wso2.comwrote: Hi Kasun, I experienced a related issue while running the integration tests. Please see the log below. In this case I am trying to send multiple requests to an HTTPS endpoint in parallel. According to the jira ticket a patch seems to have been applied but I get this error in the latest build. Any idea? == [2013-08-23 11:47:14,882] ERROR - SecurityConfigAdmin Error while reading persisted data org.wso2.carbon.core.persistence.PersistenceException: A transaction is already started for this service group. Nested transactions are no longer supported in this persistence model - StockQuoteProxy at org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.beginTransaction(ServiceGroupFilePersistenceManager.java:71) at org.wso2.carbon.security.config.SecurityConfigAdmin.getCurrentScenario(SecurityConfigAdmin.java:207) at org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:161) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [2013-08-23 11:47:14,884] ERROR - AxisEngine System error org.apache.axis2.AxisFault: System error at org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:260) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.wso2.carbon.security.SecurityConfigException: readingSecurity at org.wso2.carbon.security.config.SecurityConfigAdmin.getCurrentScenario(SecurityConfigAdmin.java:253) at org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:161) ... 10 more [2013-08-23 11:47:14,886] ERROR - ServerWorker Error processing POST request for : /services/StockQuoteProxy org.apache.axis2.AxisFault: System error at org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:260) at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340) at org.apache.axis2.engine.Phase.invoke(Phase.java:313) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: org.wso2.carbon.security.SecurityConfigException: readingSecurity at org.wso2.carbon.security.config.SecurityConfigAdmin.getCurrentScenario(SecurityConfigAdmin.java:253) at org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:161) ... 10 more On Tue, Aug 13, 2013 at 9:00 PM, Kasun Gajasinghe kas...@wso2.comwrote: Hi, I've been going through this issue [1] where I noticed that we are having a massive performance issue with POX security where each POX requests do a file system read!! What happens is that, POXSecurityHandler tries to
Re: [Dev] WSO2 ELB loadbalancer.conf links to blogs
+1, In fact those blogs are now obsolete, we shouldn't use them. Those times, we didn't have any wiki docs and no one could get the essence of clustering without reading blogs. On Sat, Sep 14, 2013 at 1:12 AM, Isuru Perera isu...@wso2.com wrote: Hi, Currently, the WSO2 ELB loadbalancer.conf has links to following blog articles. - http://nirmalfdo.blogspot.com/2012/06/fronting-wso2-application-server-50.html - http://blog.afkham.org/2011/09/wso2-load-balancer-how-it-works.html - http://nirmalfdo.blogspot.com/2013/01/scale-up-early-scale-down-slowly.html Shall we have links to latest WSO2 Docs? For example, http://docs.wso2.org/display/CLUSTER420/Clustering+WSO2+Products http://docs.wso2.org/display/ELB210/WSO2+Elastic+Load+Balancer+Documentation http://docs.wso2.org/display/ELB210/Auto-Scaling+in+Load+Balancer We should be able use doc links for latest docs. For example: http://docs.wso2.org/elastic-load-balancer Just an idea! Thanks! -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Seeing exceptions when trying to deploy an application to S2
Hi Nirmal,
What is the possibility of getting this error actually the members are
live? A network outage?
Thanks and Regards,
Harshana
On Wed, Mar 13, 2013 at 11:13 AM, Nirmal Fernando nir...@wso2.com wrote:
You can ignore this exception. You had a member and it seems to be no more
there: tcp://{50, 16, 150, 216}:4000
On Wed, Mar 13, 2013 at 2:01 PM, Janaka Ranabahu jan...@wso2.com wrote:
Hi,
Im getting the following exception when I try to deploy an existing
application. But I can login to the app server.
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
payload received : 'payload={url:
http://10.2.203.47:8082/git/jagery313/Development/as.git,url:repoUrl,url:repoUrl}'
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
url :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,064] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} -
repository URL received :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - wso2
cartridge.. {org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - Sending
Request to.. wso2.as.dev.domain : __$default
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:16,087] ERROR
{org.apache.axis2.clustering.tribes.ChannelSender} - Could not send
message to some members {org.apache.axis2.clustering.tribes.ChannelSender}
org.apache.catalina.tribes.ChannelException: Operation has timed out(3000
ms.).; Faulty members:tcp://{50, 16, 150, 216}:4000;
at
org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:109)
at
org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:54)
at
org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:79)
at
org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:78)
at
org.apache.catalina.tribes.group.interceptors.OrderInterceptor.sendMessage(OrderInterceptor.java:86)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:89)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.sendMessage(NonBlockingCoordinator.java:493)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:224)
at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:182)
at
org.apache.axis2.clustering.tribes.ChannelSender.sendToGroup(ChannelSender.java:65)
at
org.apache.axis2.clustering.management.DefaultGroupManagementAgent.send(DefaultGroupManagementAgent.java:108)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.createAndSendClusterMessage(RepoNotificationService.java:135)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.handleRepoSynch(RepoNotificationService.java:68)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.synchronize(RepoNotificationService.java:60)
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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
Re: [Dev] Seeing exceptions when trying to deploy an application to S2
On Sat, Sep 14, 2013 at 6:00 AM, Harshana Martin harsh...@wso2.com wrote:
Hi Nirmal,
What is the possibility of getting this error actually the members are
live? A network outage?
Yes, when a sudden n/w outage occur, nodes might detect some nodes as
faulty members.
Thanks and Regards,
Harshana
On Wed, Mar 13, 2013 at 11:13 AM, Nirmal Fernando nir...@wso2.com wrote:
You can ignore this exception. You had a member and it seems to be no
more there: tcp://{50, 16, 150, 216}:4000
On Wed, Mar 13, 2013 at 2:01 PM, Janaka Ranabahu jan...@wso2.com wrote:
Hi,
Im getting the following exception when I try to deploy an existing
application. But I can login to the app server.
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
payload received : 'payload={url:
http://10.2.203.47:8082/git/jagery313/Development/as.git,url:repoUrl,url:repoUrl}'
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,061] INFO
{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet} - repository
url :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.cartridge.mgt.ui.RepoNotificationServlet}
TID: [0] [] [2013-03-13 17:56:11,064] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} -
repository URL received :
http://10.2.203.47:8082/git/jagery313/Development/as.git{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - wso2
cartridge.. {org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:11,075] INFO
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService} - Sending
Request to.. wso2.as.dev.domain : __$default
{org.wso2.carbon.hosting.mgt.service.RepoNotificationService}
TID: [0] [] [2013-03-13 17:56:16,087] ERROR
{org.apache.axis2.clustering.tribes.ChannelSender} - Could not send
message to some members {org.apache.axis2.clustering.tribes.ChannelSender}
org.apache.catalina.tribes.ChannelException: Operation has timed
out(3000 ms.).; Faulty members:tcp://{50, 16, 150, 216}:4000;
at
org.apache.catalina.tribes.transport.nio.ParallelNioSender.sendMessage(ParallelNioSender.java:109)
at
org.apache.catalina.tribes.transport.nio.PooledParallelSender.sendMessage(PooledParallelSender.java:54)
at
org.apache.catalina.tribes.transport.ReplicationTransmitter.sendMessage(ReplicationTransmitter.java:79)
at
org.apache.catalina.tribes.group.ChannelCoordinator.sendMessage(ChannelCoordinator.java:78)
at
org.apache.catalina.tribes.group.interceptors.OrderInterceptor.sendMessage(OrderInterceptor.java:86)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.sendMessage(TcpFailureDetector.java:89)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.NonBlockingCoordinator.sendMessage(NonBlockingCoordinator.java:493)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.sendMessage(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:224)
at
org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:182)
at
org.apache.axis2.clustering.tribes.ChannelSender.sendToGroup(ChannelSender.java:65)
at
org.apache.axis2.clustering.management.DefaultGroupManagementAgent.send(DefaultGroupManagementAgent.java:108)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.createAndSendClusterMessage(RepoNotificationService.java:135)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.handleRepoSynch(RepoNotificationService.java:68)
at
org.wso2.carbon.hosting.mgt.service.RepoNotificationService.synchronize(RepoNotificationService.java:60)
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.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
Re: [Dev] Need urgent help to disable features WSO2 ESB 4.0.3?
Any Help on this. It is big company and if they do not find it secure we have to drop the implementation. Please help. thanks Abhijit On Sep 12, 2013, at 3:39 PM, Abhijit Diwan wrote: Hi All We are in final few steps of WSO2 ESB / Data services implementation at very big company. They love your Data Services, I mean it , love it !! We are trying to pass the Information Security review of our WSO2 ESB implementation. We are using 4.0.3 EAB with 3.2.2 DSS feature. Information security group has objected for following things in default WSO2 ESB 1. QPID / AMQP server listening to 5672 / 8672 ports. Can we disable the default message broker so that QPID will not start. If we disable, will it affect any other functionality? We are NOT using message brokers / any JMS related applications, mainly Data Services. 2. How to block JMX console being started? The JMX console starts at 1 / be default. 3. We have already disabled Admin UI, however is there any way where I can turn the logging levels for individual loggers with out Admin UI and WITHOUT re-starting the ESB? I would be extremely thankful if I can answers for above questions. Please help WSO2 implementation in very prestigious company. WSO2 rocks !!! thanks Abhijit ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need urgent help to disable features WSO2 ESB 4.0.3?
Hi Diwan,
Please see the answers for some of the questions.
On Sat, Sep 14, 2013 at 6:28 AM, Abhijit Diwan adi...@apple.com wrote:
Any Help on this. It is big company and if they do not find it secure we
have to drop the implementation.
Please help.
thanks
Abhijit
On Sep 12, 2013, at 3:39 PM, Abhijit Diwan wrote:
Hi All
We are in final few steps of WSO2 ESB / Data services
implementation at very big company. They love your Data Services, I mean it
, love it !!
We are trying to pass the Information Security review of our WSO2
ESB implementation. We are using 4.0.3 EAB with 3.2.2 DSS feature.
Information security group has objected for following things in
default WSO2 ESB
1. QPID / AMQP server listening to 5672 / 8672 ports. Can
we disable the default message broker so that QPID will not start. If we
disable, will it affect any other functionality? We are
NOT using message brokers / any JMS related applications, mainly Data
Services.
2. How to block JMX console being started? The JMX console
starts at 1 / be default.
In {CARBON-HOME}/repository/conf/advanced/jmx.xml file, you can disable jmx
console.
StartRMIServerfalse/StartRMIServer
3. We have already disabled Admin UI, however is there any
way where I can turn the logging levels for individual loggers with out
Admin UI and WITHOUT re-starting the ESB?
I'm afraid not (AFAIK). The only other way is by editing
{CARBON-HOME}/repository/conf/log4j.properties file, which needs a restart
of the server.
I would be extremely thankful if I can answers for above questions.
Please help WSO2 implementation in very prestigious company.
WSO2 rocks !!!
thanks
Abhijit
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Patch for kernel. - chunk02 release.
Hi All, Please apply this patch as well [2]. You need to apply this to org.wso2.carbon.registry.core The test summary with the patch : Tests run: 173, Failures: 0, Errors: 0, Skipped: 0 [2]https://wso2.org/jira/browse/REGISTRY-1911 Thanks Ajith. On Thu, Sep 12, 2013 at 2:03 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Shameera, Please apply the patch [1] for chunk02 release. [1]https://wso2.org/jira/browse/REGISTRY-1941 Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Patch for kernel. - chunk02 release.
Hi Ajith,
Can you please explain the code in the patch..
+// This is for fixing REGISTRY-1911
+try {
+if (userName == null CurrentSession.getUser() != null
+
!CurrentSession.getUser().equals(CarbonConstants.REGISTRY_SYSTEM_USERNAME))
{
+UserRealm realm = CurrentSession.getUserRealm();
+UserStoreManager reader = realm.getUserStoreManager();
+String[] roles =
reader.getRoleListOfUser(CurrentSession.getUser());
+List list = Arrays.asList(roles);
+
+if
(!list.contains(CurrentSession.getUserRealm().getRealmConfiguration().getAdminRoleName()))
{
+userName = CurrentSession.getUser();
+}
+
+}
+} catch (UserStoreException e) {
+String msg = Failed to get list of roles of user + userName;
+log.error(msg, e);
+throw new RegistryException(msg, e);
+}
Thanks regards,
-Prabath
On Sat, Sep 14, 2013 at 8:05 AM, Ajith Vitharana aji...@wso2.com wrote:
Hi All,
Please apply this patch as well [2]. You need to apply this to
org.wso2.carbon.registry.core
The test summary with the patch : Tests run: 173, Failures: 0, Errors: 0,
Skipped: 0
[2]https://wso2.org/jira/browse/REGISTRY-1911
Thanks
Ajith.
On Thu, Sep 12, 2013 at 2:03 PM, Ajith Vitharana aji...@wso2.com wrote:
Hi Shameera,
Please apply the patch [1] for chunk02 release.
[1]https://wso2.org/jira/browse/REGISTRY-1941
Thanks
Ajith
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94772217350
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Thanks Regards,
Prabath
Mobile : +94 71 809 6732
http://blog.facilelogin.com
http://RampartFAQ.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Patch for kernel. - chunk02 release.
Hi Ajith, I've applied REGISTRY-1941. Sameera. On Thu, Sep 12, 2013 at 2:03 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Shameera, Please apply the patch [1] for chunk02 release. [1]https://wso2.org/jira/browse/REGISTRY-1941 Thanks Ajith -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] What is the use case of EnableJWTCache in AM?
Hi, I need to test JWTCache in AM. Therefore I have enabled GatewayKeyCache and disabled JWTCache in api-manager.xml and invoked an API via an application then changed the application name and invoked again. Then decoded the response. But still the application name is not changed even-though I have disabled the JWTCache property. When I enabled both GatewayKeyCache and JWTCache still the response will be cached. Is this expected or a bug and is this the correct way to test JWTCache in AM or what are the values that will be taken from the JWT cache? Thanks! -- *Ushani Balasooriya* Software Engineer - QA; WSO2 Inc; http://www.wso2.com/. Mobile; +94772636796 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
