[Dev] URL Mapping for Applications on tenant - WSO2 AS
Hi All, I saw some documentation on URL mapping for applications on tenant mode in AS 5.0.1 [1]https://docs.wso2.org/display/AS501/URL+Mapping+for+Applications and seems it has been removed on latest version - 5.2.1. Is there any possible way to implement it on 5.2.1? I tried on p2 and couldn't found any related feature. Thank you, [1] https://docs.wso2.org/display/AS501/URL+Mapping+for+Applications *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Java version problems when creating axis2 services with DevS 3.6 and deploying in AS 5.2.1
Thanks Gayan and Kasun. I have updated the page [1]. Please have a look. [1] https://docs.wso2.org/display/DVS360/FAQ#FAQ-HowcanIavoidJavaversionproblemswhencreatingaxis2servicesanddeployinginAS ? Thanks, Tania On Tue, May 13, 2014 at 11:11 AM, Kasun Gajasinghe kas...@wso2.com wrote: On Tue, May 13, 2014 at 11:03 AM, Gayan Yalpathwala gay...@wso2.comwrote: Hi Tania, Thanks for updating the doc. I think this answer can be modified to include the following, so that it would be more descriptive and understandable. *Current version of Developer studio runs on Java 1.7 and Application server 5.2.1 runs on Java 1.6 or later. This can lead to Java compliance issues during runtime if you're using different Java versions for Developer studio and Application Server. To solve this, follow below steps when building artifacts using Developer studio.* *Right click the Axis2 service project and go to properties window.* *In Java Compiler tab, set compiler compliance level to Java version that Application Server runs on.* IMO, it is not good to ask the user to change the java version that AS runs on. Instead, defining the compiler compliance level from within eclipse is the correct approach. +1. We could also mention the first few lines of the stack trace. Thanks, On Tue, May 13, 2014 at 9:14 AM, Tania Mahanama ta...@wso2.com wrote: Hi, I have added this to the FAQ section [1] after discussing with AsankaS. Please let me know if there are any changes to be made. [1] https://docs.wso2.org/display/DVS360/FAQ#FAQ-HowcanIavoidJavaversionproblemswhencreatingaxis2servicesanddeployinginAS ? Thanks, Tania On Mon, May 12, 2014 at 3:13 PM, Kasun Gajasinghe kas...@wso2.comwrote: Hi Pulasthi/Jasintha, +1 to get this added to the documentation. Running AS with JDK 1.7 would 'fix' the problem, but carbon products support JDK 1.6. So, the artifacts developed via DevS also need to comply with JDK 1.6 runtime. Thanks, KasunG On Mon, May 12, 2014 at 2:43 PM, Pulasthi Supun pulas...@wso2.comwrote: Hi Jasintha, As you pointed out over chat my AS server was running on a 1.6 JVM since i only changed my java version to 1.7 to run eclipse. starting the server with 1.7 solved the problem. Regards, Pulasthi On Mon, May 12, 2014 at 2:20 PM, Pulasthi Supun pulas...@wso2.comwrote: Hi Jasintha, This documentation only mentions that it requires java 1.7 to use DevS 3.6. That is not the concern i raised in here. i am referring to a different problem. That happens due to compiler compliance levels. please correct me if am wrong but i did not see such a point mentioned in the documentation Regards, Pulasthi On Mon, May 12, 2014 at 2:10 PM, Jasintha Dasanayake jasin...@wso2.com wrote: On Mon, May 12, 2014 at 2:00 PM, Pulasthi Supun pulas...@wso2.comwrote: Hi All, Came across $subject. This happened because Eclipse Kepler which is used with DevS 3.6 requires java 1.7. so by default the JRE version used will be java 1.7 and the java compiler compliance level will be 1.7 .But if you create a simple Axis2 service and try to deploy on AS i get the following error. This can be solved by changing the compiler compliance level in project settings to 1.6. But i think it should be mentioned in the documentation to avoid any future confusion. Yes, we have already mention that in the documentation[1] [1] - https://docs.wso2.org/display/DVS360/Installation /Jasintha Error: java.lang.UnsupportedClassVersionError: org/wso2/arvosample/AvroPublisher : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.apache.axis2.deployment.DeploymentClassLoader.findClass(DeploymentClassLoader.java:78) at org.apache.axis2.deployment.DeploymentClassLoader.loadClass(DeploymentClassLoader.java:278) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.apache.axis2.util.Loader.loadClass(Loader.java:218) at org.apache.axis2.util.Utils.getServiceClass(Utils.java:799) at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:430) at org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397) at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:101) at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:143) at
[Dev] Please merge ESB Integration test commit#12 pull request
Hi ESB Team, Please apply the pull request - https://github.com/wso2-dev/product-esb/pull/12 Thanks, Nuwanw -- Nuwan Wimalasekara Senior Software Engineer - Test Automation WSO2, Inc.: http://wso2.com lean. enterprise. middleware phone: +94 71 668 4620 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] No Dev repo found for carbon-utils
https://github.com/wso2/carbon-utils -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB Connector Store Icons
For Dev Studio we have to keep a consistent look for a given set of icons for a given category. Ex: Endpoints, Extension etc... That's why they all are in the same color. We can keep these icons for Dev Studio and color up the icons that you guys need for the connector store to make them sync up with the banners images. thanks, Chanaka On Tue, May 13, 2014 at 10:14 AM, Malaka Silva mal...@wso2.com wrote: I also agree. It's less attractive. I still think salesforce logo looks different in the following. I'm ok with others they look nice :) https://drive.google.com/a/wso2.com/folderview?id=0B_CCkDYHWyB9VGlJc0MzWnRpYkUusp=sharing#grid On Tue, May 13, 2014 at 10:03 AM, Dushan Abeyruwan dus...@wso2.comwrote: HI Chanaka, Can't we have more closer (i.e similar to connector store icons banners), for me devs icons almost in same color. Cheers, Dushan On Tue, May 13, 2014 at 6:06 AM, Chanaka Jayasena chan...@wso2.comwrote: Hi Dushan, upload those images to Drive under Dev Studio Icons. thanks, Chanaka On Mon, May 12, 2014 at 9:51 AM, Chanaka Jayasena chan...@wso2.comwrote: Sure, Dushan. I will provide them by EOD. thanks, Chanaka On Mon, May 12, 2014 at 7:49 AM, Dushan Abeyruwan dus...@wso2.comwrote: Hi Chanaka, Additionally, we need icon for devloper studio as well ref https://github.com/dushansachinda/esb-connectors/tree/master/salesforce/1.0.0/src/main/resources/icon can we get icons as well for all the connectors (other than, salesfoce,googlesh,twitter,twilio,jira) Cheers, Dushan On Thu, May 8, 2014 at 11:23 AM, Chanaka Jayasena chan...@wso2.comwrote: 580 x 300 banner 220 x 200 icon thumb thanks, Chanaka On Thu, May 8, 2014 at 8:49 AM, Malaka Silva mal...@wso2.com wrote: Hi Chanaka, What is the resolution you have used for log and banner. We may need to use the same for other connectors? Best Regards, Malaka On Sun, May 4, 2014 at 11:26 AM, Chanaka Jayasena chan...@wso2.comwrote: Hi Dushan, the Google drive is updated with the latest. thanks, Chanaka On Fri, May 2, 2014 at 5:35 PM, Chanaka Jayasena chan...@wso2.comwrote: Noted. I will update and provide you with the remaining connector icons as well. Thanks, Chanaka On Fri, May 2, 2014 at 1:20 PM, Dushan Abeyruwan dus...@wso2.comwrote: Hi ChanakaJ On Fri, May 2, 2014 at 9:00 AM, Malaka Silva mal...@wso2.comwrote: Hi All, IMO we should not modify the backgroung color and layout outside what vendors(Third parties) are using. Eg: - Salesforce logo is in green color whereas standard is blue. Yes, I feel the same as we should not modify exiting vendors layout colors, overall felt only salesforce has such issue. meantime, can we get the remaining connector images as well [1] shows you the connectors we have at the moment https://github.com/wso2-dev/esb-connectors we should add, facebook,gmail.amazon s3,google drive,suvaymonkey, sugerCRM. Best Regards, Malaka On Fri, May 2, 2014 at 8:08 AM, Chanaka Jayasena chan...@wso2.com wrote: Hi Dushan, [1] contains the images you requested for the Connector Store. Amazon s3 and Survey Monkey icons are missing. I will upload those ones they are done. 1 - https://drive.google.com/a/wso2.com/folderview?id=0B_CCkDYHWyB9VGlJc0MzWnRpYkUusp=sharing#grid thanks, Chanaka -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Dushan Abeyruwan | Associate Tech Lead Integration Technologies Team PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:http://dushansview.blogspot.com/ Mobile:(0094)713942042 -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise .
Re: [Dev] No Dev repo found for carbon-utils
carbon-utils repo should be merged with carbon-commons. On Tue, May 13, 2014 at 1:30 PM, Malaka Silva mal...@wso2.com wrote: https://github.com/wso2/carbon-utils -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Synapse Hot Deployment and Undeployment ?
Hi, For inbound endpoint hot deployment [1] class is being used. However when I touch the file updateSynapseArtifact() is not called. Also undeploySynapseArtifact() is not called when file is deleted. Anything else we need to do to support hot deployments? Do we need to register this? 1) https://github.com/wso2-dev/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/deployers/InboundEndpointDeployer.java Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Synapse Hot Deployment and Undeployment ?
All new deployers should be registered with Axis2 deployment engine before it can be used. I think in synapse case, all the artifact deployers are registered via the ServiceBusInitializer. On Tue, May 13, 2014 at 2:52 PM, Malaka Silva mal...@wso2.com wrote: Hi, For inbound endpoint hot deployment [1] class is being used. However when I touch the file updateSynapseArtifact() is not called. Also undeploySynapseArtifact() is not called when file is deleted. Anything else we need to do to support hot deployments? Do we need to register this? 1) https://github.com/wso2-dev/wso2-synapse/blob/master/modules/core/src/main/java/org/apache/synapse/deployers/InboundEndpointDeployer.java Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [DEV][GREG]Cannot build Endpoint Look-up Sample
Hi, I couldn't build the Endpoint Look-up Sample alone. Only after I built the product 4.6.0 I was able to build it. Following is the build failure. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 13:25.574s [INFO] Finished at: Tue May 13 14:12:32 IST 2014 [INFO] Final Memory: 14M/1015M [INFO] [ERROR] Failed to execute goal on project org.wso2.carbon.registry.samples.handler: Could not resolve dependencies for project org.wso2.governance:org.wso2.carbon.registry.samples.handler:bundle:4.6.0: Failed to collect dependencies for [org.apache.ws.commons.axiom.wso2:axiom:jar:1.2.11.wso2v2 (compile), org.wso2.carbon:org.wso2.carbon.governance.api:jar:4.2.1 (compile), org.wso2.carbon:org.wso2.carbon.registry.core:jar:4.2.0 (compile)]: Failed to read artifact descriptor for uddi:uddi4j:jar:1.0.1: Could not transfer artifact uddi:uddi4j:pom:1.0.1 from/to wso2-nexus ( http://maven.wso2.org/nexus/content/groups/wso2-public/): Checksum validation failed, no checksums available from the repository - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException Thanks Gayan Gayan Dhanuska Software Engineer http://wso2.com/ Lean Enterprise Middleware Mobile 071 666 2327 Office Tel : 94 11 214 5345 Fax : 94 11 214 5300 Twitter : https://twitter.com/gayanlggd ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Global cache invalidation meeting notes
Hi All, Following updates has been discussed on $subject. 1) The isCoordinator check is not necessary for publishing the cache invalidation message. 2) Separate the implementation of publisher and subscriber into 2 classes. 3) Alter the implementation to support, when the isCoordinator node goes down; the next coordinator node should get auto subscribe to the topic. The 3rd point was discussed to implement as follows: The osgi service implementation bundle will be present at all nodes. So it will check whether Am I the coordinator? in a given time interval (This time interval can be configured in cache.xml). When one node goes down then the next coordinator will become the coordinator. At this point Am I the coordinator? will get the response and it will subscribe it-self to the topic. Please update the thread if there are any further updates. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Patch for IDENTITY-2385
Hi Manoj, Please apply the patch attached in [1] to the location in [2] (patch0008). @Asela/@Prabath, would be great if you could review this fix as well please. [1] - https://wso2.org/jira/browse/IDENTITY-2385 [2] - https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/patches/patch0008/core/org.wso2.carbon.user.core/4.2.0 Thanks, NuwanD. -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Global cache invalidation meeting notes
Hi Shazni, I have updated the code with aforesaid changes in my git fork [1]https://github.com/amalhub/carbon4-kernel/commit/7d1711a6de7ebf04e22ec1e9634e88088b954c4f . Please run the tests on your clustered setup. [1] https://github.com/amalhub/carbon4-kernel/commit/7d1711a6de7ebf04e22ec1e9634e88088b954c4f Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Tue, May 13, 2014 at 4:30 PM, Amal Gunatilake am...@wso2.com wrote: Hi All, Following updates has been discussed on $subject. 1) The isCoordinator check is not necessary for publishing the cache invalidation message. 2) Separate the implementation of publisher and subscriber into 2 classes. 3) Alter the implementation to support, when the isCoordinator node goes down; the next coordinator node should get auto subscribe to the topic. The 3rd point was discussed to implement as follows: The osgi service implementation bundle will be present at all nodes. So it will check whether Am I the coordinator? in a given time interval (This time interval can be configured in cache.xml). When one node goes down then the next coordinator will become the coordinator. At this point Am I the coordinator? will get the response and it will subscribe it-self to the topic. Please update the thread if there are any further updates. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Global cache invalidation meeting notes
On Tue, May 13, 2014 at 4:30 PM, Amal Gunatilake am...@wso2.com wrote: Hi All, Following updates has been discussed on $subject. 1) The isCoordinator check is not necessary for publishing the cache invalidation message. 2) Separate the implementation of publisher and subscriber into 2 classes. 3) Alter the implementation to support, when the isCoordinator node goes down; the next coordinator node should get auto subscribe to the topic. The 3rd point was discussed to implement as follows: The osgi service implementation bundle will be present at all nodes. So it will check whether Am I the coordinator? in a given time interval (This time interval can be configured in cache.xml). When one node goes down then the next coordinator will become the coordinator. At this point Am I the coordinator? will get the response and it will subscribe it-self to the topic. There is a better way of implementing this. When a node becomes a coordinator, it would notify all OSGi services which implement that interface. I already have this implemented in C5 kernel (must check). We need to bring that back in. Rather than have a task that checks whether I am the coordinator, we should use this notification based mechanism. Please update the thread if there are any further updates. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 blog: **http://blog.afkham.org*http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Global cache invalidation meeting notes
Hi Amal, Messages are not getting received after this modification. I noticed very less number of messages getting published too. No modification on registry kernel side is made. Shazni Nazeer Senior Software Engineer Mob : +94 715 440 607 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Tue, May 13, 2014 at 6:04 PM, Afkham Azeez az...@wso2.com wrote: On Tue, May 13, 2014 at 4:30 PM, Amal Gunatilake am...@wso2.com wrote: Hi All, Following updates has been discussed on $subject. 1) The isCoordinator check is not necessary for publishing the cache invalidation message. 2) Separate the implementation of publisher and subscriber into 2 classes. 3) Alter the implementation to support, when the isCoordinator node goes down; the next coordinator node should get auto subscribe to the topic. The 3rd point was discussed to implement as follows: The osgi service implementation bundle will be present at all nodes. So it will check whether Am I the coordinator? in a given time interval (This time interval can be configured in cache.xml). When one node goes down then the next coordinator will become the coordinator. At this point Am I the coordinator? will get the response and it will subscribe it-self to the topic. There is a better way of implementing this. When a node becomes a coordinator, it would notify all OSGi services which implement that interface. I already have this implemented in C5 kernel (must check). We need to bring that back in. Rather than have a task that checks whether I am the coordinator, we should use this notification based mechanism. Please update the thread if there are any further updates. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ELB Experiment
After changing the cert in the ELB we were able to achieve the mutual auth between ELB and AS. But the requirement was to get the auth working between ESB and the AS (bypassing the ELb). For this, the ideal solution would be SSL Tunneling. So I'll investigate on that topic and see what we can do. Thanks. On Mon, May 12, 2014 at 8:17 PM, Amila Maha Arachchi ami...@wso2.comwrote: Hi Nalin, Good. We need to do one more thing. That is, to change the certificate of the ELB and then see what needs to be done to get mutual auth working. On Mon, May 12, 2014 at 6:12 PM, Nalin Chandraratne na...@wso2.comwrote: Hi Shariq, Seems like the experiment is successful. I put the mutualAuthenticator jar to the AS and invoked an admin service of AS, fronted by ELB, from a proxy service of ESB. I set the soap header as following in the request. inSequence header m:UserName xmlns:m=http://mutualssl.carbon.wso2.org admin/m:UserName /header send endpoint address uri= https://localhost:8245/services/ServiceAdmin/ /endpoint /send /inSequence By doing the above, I was able to successfully invoke the admin service. Further, I remote debugged the MutualSSLAuthenticator class as you mentioned and verified that isAuthenticated() method returns true. Thanks. On Fri, May 9, 2014 at 6:00 PM, Nalin Chandraratne na...@wso2.comwrote: Hi Amila, I'm still in the process of doing the $subject. As per the discussion had with Shariq, even though we enabled the ClientAuth=true in AS, it doesn't do what we expect. It uses a Rampart Authenticator and what we want is the MutualSSLAuthenticator class to get used. So we have changed the experiment. Now what we are trying to do is, invoke an admin service in the AS from an ESB service. Because as shariq mentioned, this call should invoke the above mentioned MutualSSLAuthenticator class. Only after setting this environment properly, I can proceed with the ELB experiment. Thanks. -- Nalin Chamara Software Engineer 071-56-147-56 -- Nalin Chamara Software Engineer 071-56-147-56 -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 -- Nalin Chamara Software Engineer 071-56-147-56 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Turing - Chunk 11 build failure: org.wso2.carbon.apimgt.startup.publisher.feature
Hi, Getting the following. [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon:product-releases-features:4.2.0-chunk11 (/home/dulanja/work/repos/svn/carbon/platform/branches/turing/product-releases/chunk-11/features/pom.xml) has 1 error [ERROR] Child module /home/dulanja/work/repos/svn/carbon/platform/branches/turing/product-releases/chunk-11/features/../../../apimgt/org.wso2.carbon.apimgt.startup.publisher.feature/4.2.2 of /home/dulanja/work/repos/svn/carbon/platform/branches/turing/product-releases/chunk-11/features/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. [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 Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Turing - Chunk 11 build failure: org.wso2.carbon.apimgt.startup.publisher.feature
Thanks Ruwan! On Tue, May 13, 2014 at 6:38 PM, Ruwan Yatawara ruw...@wso2.com wrote: Hi Dulanja, This should be fixed now. Please take an update. Thanks and Regards, Ruwan Yatawara WSO2 Inc. email : ruw...@wso2.com mobile : +94 77 9110413 blog : http://thoughts.ruwan-ace.com/ www: :http://wso2.com On Tue, May 13, 2014 at 6:32 PM, Dulanja Liyanage dula...@wso2.comwrote: Hi, Getting the following. [ERROR] The build could not read 1 project - [Help 1] [ERROR] [ERROR] The project org.wso2.carbon:product-releases-features:4.2.0-chunk11 (/home/dulanja/work/repos/svn/carbon/platform/branches/turing/product-releases/chunk-11/features/pom.xml) has 1 error [ERROR] Child module /home/dulanja/work/repos/svn/carbon/platform/branches/turing/product-releases/chunk-11/features/../../../apimgt/org.wso2.carbon.apimgt.startup.publisher.feature/4.2.2 of /home/dulanja/work/repos/svn/carbon/platform/branches/turing/product-releases/chunk-11/features/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. [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 Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in invoking APIs with POST request (with different content types)
Hello all, Isuru and I had a look at this, and we found the reason for this behaviour is to do with the isRest property not being set to true - by default when we send text/xml we assume that the invocation is not rest and therefor is a SOAP service invocation. The problem with this is that a valid REST invocation can also look like a SOAP invocation when the deciding factor is only the content type. To work around this the address endpoints have the format attribute where we can set format=rest. HTTP Endpoints don't have a mechanism to set the format at present. Shall we include the ability to set the format in HTTP Endpoint? Is this a correct fix? Thanks On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Hi, We observed following behavior in API Manager 1.7.0 which built on top of synapse 2.1.2.wso2v5. We sent same request to API created by fronting basic jaxrs service. Only difference is setting 2 content types. Backend service support both content types and we can invoke it without any issue. 01. Content-Type: text/xml [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1 02. Content-Type: application/xml [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers/ *customerservice/customers* HTTP/1.1 When content type is text/xml we can see part of the request is dropping. It send request directly to the endpoint defined in API without appending other things in client request url. Any idea what went wrong? Here is my API api name=admin--jaxrs context=/jaxrs version=1.0.0 version-type=url resource methods=POST GET DELETE OPTIONS PUT uri-template=/* inSequence property name=POST_TO_URI value=true scope=axis2/ filter source=$ctx:AM_KEY_TYPE regex=PRODUCTION then send endpoint name=admin--jaxrs_APIproductionEndpoint_0 http uri-template= http://10.100.1.65:9764/jaxrs_basic/services/customers; timeout duration3/duration responseActionfault/responseAction /timeout suspendOnFailure errorCodes-1/errorCodes initialDuration0/initialDuration progressionFactor1.0/progressionFactor maximumDuration0/maximumDuration /suspendOnFailure markForSuspension errorCodes-1/errorCodes /markForSuspension /http /endpoint /send /then else sequence key=_sandbox_key_error_/ /else /filter /inSequence outSequence send/ /outSequence /resource handlers handler class=org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler/ handler class=org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler property name=id value=A/ property name=policyKey value=gov:/apimgt/applicationdata/tiers.xml/ /handler handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler/ handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler handler class=org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler/ /handlers /api Thanks, sanjeewa. -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712* Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in invoking APIs with POST request (with different content types)
Hi guys, Looks like format support is already there for HTTP Endpoint - just not in the UI. We can add the attribute format=rest to solve this issue. :) Thanks On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya r...@wso2.com wrote: Hello all, Isuru and I had a look at this, and we found the reason for this behaviour is to do with the isRest property not being set to true - by default when we send text/xml we assume that the invocation is not rest and therefor is a SOAP service invocation. The problem with this is that a valid REST invocation can also look like a SOAP invocation when the deciding factor is only the content type. To work around this the address endpoints have the format attribute where we can set format=rest. HTTP Endpoints don't have a mechanism to set the format at present. Shall we include the ability to set the format in HTTP Endpoint? Is this a correct fix? Thanks On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Hi, We observed following behavior in API Manager 1.7.0 which built on top of synapse 2.1.2.wso2v5. We sent same request to API created by fronting basic jaxrs service. Only difference is setting 2 content types. Backend service support both content types and we can invoke it without any issue. 01. Content-Type: text/xml [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1 02. Content-Type: application/xml [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers/ *customerservice/customers* HTTP/1.1 When content type is text/xml we can see part of the request is dropping. It send request directly to the endpoint defined in API without appending other things in client request url. Any idea what went wrong? Here is my API api name=admin--jaxrs context=/jaxrs version=1.0.0 version-type=url resource methods=POST GET DELETE OPTIONS PUT uri-template=/* inSequence property name=POST_TO_URI value=true scope=axis2/ filter source=$ctx:AM_KEY_TYPE regex=PRODUCTION then send endpoint name=admin--jaxrs_APIproductionEndpoint_0 http uri-template= http://10.100.1.65:9764/jaxrs_basic/services/customers; timeout duration3/duration responseActionfault/responseAction /timeout suspendOnFailure errorCodes-1/errorCodes initialDuration0/initialDuration progressionFactor1.0/progressionFactor maximumDuration0/maximumDuration /suspendOnFailure markForSuspension errorCodes-1/errorCodes /markForSuspension /http /endpoint /send /then else sequence key=_sandbox_key_error_/ /else /filter /inSequence outSequence send/ /outSequence /resource handlers handler class=org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler/ handler class=org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler property name=id value=A/ property name=policyKey value=gov:/apimgt/applicationdata/tiers.xml/ /handler handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler/ handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler handler class=org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler/ /handlers /api Thanks, sanjeewa. -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712 %2B94%C2%A0772%20930%20712* Lean . Enterprise . Middleware -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712* Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in invoking APIs with POST request (with different content types)
On Tue, May 13, 2014 at 6:55 PM, Ravi Undupitiya r...@wso2.com wrote: Hi guys, Looks like format support is already there for HTTP Endpoint - just not in the UI. We can add the attribute format=rest to solve this issue. :) I think we can include this in the http endpoint getting created for API configs of API Manager. Thanks On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya r...@wso2.com wrote: Hello all, Isuru and I had a look at this, and we found the reason for this behaviour is to do with the isRest property not being set to true - by default when we send text/xml we assume that the invocation is not rest and therefor is a SOAP service invocation. The problem with this is that a valid REST invocation can also look like a SOAP invocation when the deciding factor is only the content type. To work around this the address endpoints have the format attribute where we can set format=rest. HTTP Endpoints don't have a mechanism to set the format at present. Shall we include the ability to set the format in HTTP Endpoint? Is this a correct fix? Thanks On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Hi, We observed following behavior in API Manager 1.7.0 which built on top of synapse 2.1.2.wso2v5. We sent same request to API created by fronting basic jaxrs service. Only difference is setting 2 content types. Backend service support both content types and we can invoke it without any issue. 01. Content-Type: text/xml [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1 02. Content-Type: application/xml [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers/ *customerservice/customers* HTTP/1.1 When content type is text/xml we can see part of the request is dropping. It send request directly to the endpoint defined in API without appending other things in client request url. Any idea what went wrong? Here is my API api name=admin--jaxrs context=/jaxrs version=1.0.0 version-type=url resource methods=POST GET DELETE OPTIONS PUT uri-template=/* inSequence property name=POST_TO_URI value=true scope=axis2/ filter source=$ctx:AM_KEY_TYPE regex=PRODUCTION then send endpoint name=admin--jaxrs_APIproductionEndpoint_0 http uri-template= http://10.100.1.65:9764/jaxrs_basic/services/customers; timeout duration3/duration responseActionfault/responseAction /timeout suspendOnFailure errorCodes-1/errorCodes initialDuration0/initialDuration progressionFactor1.0/progressionFactor maximumDuration0/maximumDuration /suspendOnFailure markForSuspension errorCodes-1/errorCodes /markForSuspension /http /endpoint /send /then else sequence key=_sandbox_key_error_/ /else /filter /inSequence outSequence send/ /outSequence /resource handlers handler class=org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler/ handler class=org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler property name=id value=A/ property name=policyKey value=gov:/apimgt/applicationdata/tiers.xml/ /handler handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler/ handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler handler class=org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler/ /handlers /api Thanks, sanjeewa. -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712 %2B94%C2%A0772%20930%20712* Lean . Enterprise . Middleware -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712
Re: [Dev] Issue in invoking APIs with POST request (with different content types)
-1 HTTP EP is designed for outbound REST calls. So putting format=rest, is meaningless and hinders its whole purpose. We need to find a better alternative. May be we have to filter-out SOAP vs POX at the Axis2FlexibleMEPClient level ? On Wed, May 14, 2014 at 1:25 AM, Ravi Undupitiya r...@wso2.com wrote: Hi guys, Looks like format support is already there for HTTP Endpoint - just not in the UI. We can add the attribute format=rest to solve this issue. :) Thanks On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya r...@wso2.com wrote: Hello all, Isuru and I had a look at this, and we found the reason for this behaviour is to do with the isRest property not being set to true - by default when we send text/xml we assume that the invocation is not rest and therefor is a SOAP service invocation. The problem with this is that a valid REST invocation can also look like a SOAP invocation when the deciding factor is only the content type. To work around this the address endpoints have the format attribute where we can set format=rest. HTTP Endpoints don't have a mechanism to set the format at present. Shall we include the ability to set the format in HTTP Endpoint? Is this a correct fix? Thanks On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Hi, We observed following behavior in API Manager 1.7.0 which built on top of synapse 2.1.2.wso2v5. We sent same request to API created by fronting basic jaxrs service. Only difference is setting 2 content types. Backend service support both content types and we can invoke it without any issue. 01. Content-Type: text/xml [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1 02. Content-Type: application/xml [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers/ *customerservice/customers* HTTP/1.1 When content type is text/xml we can see part of the request is dropping. It send request directly to the endpoint defined in API without appending other things in client request url. Any idea what went wrong? Here is my API api name=admin--jaxrs context=/jaxrs version=1.0.0 version-type=url resource methods=POST GET DELETE OPTIONS PUT uri-template=/* inSequence property name=POST_TO_URI value=true scope=axis2/ filter source=$ctx:AM_KEY_TYPE regex=PRODUCTION then send endpoint name=admin--jaxrs_APIproductionEndpoint_0 http uri-template= http://10.100.1.65:9764/jaxrs_basic/services/customers; timeout duration3/duration responseActionfault/responseAction /timeout suspendOnFailure errorCodes-1/errorCodes initialDuration0/initialDuration progressionFactor1.0/progressionFactor maximumDuration0/maximumDuration /suspendOnFailure markForSuspension errorCodes-1/errorCodes /markForSuspension /http /endpoint /send /then else sequence key=_sandbox_key_error_/ /else /filter /inSequence outSequence send/ /outSequence /resource handlers handler class=org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler/ handler class=org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler property name=id value=A/ property name=policyKey value=gov:/apimgt/applicationdata/tiers.xml/ /handler handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler/ handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler handler class=org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler/ /handlers /api Thanks, sanjeewa. -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ -- *Ravi Undupitiya* Software Engineer; WSO2 Inc.; http://wso2.com *E-mail: r...@wso2.com http://wso2.com**M: **+94 772 930 712 %2B94%C2%A0772%20930%20712* Lean . Enterprise . Middleware
Re: [Dev] Issue in invoking APIs with POST request (with different content types)
Hi Kasun, At present the Axis2FlexibleMEPClient detects a REST request by checking the HTTP method used and if the content type belongs to any of the following: application/xml application/x-www-form-urlencoded multipart/form-data application/json If the HTTP method is anything other than POST - then the request is assumed to be REST. If it is a POST, it checks to see if the messageType is one of the above. IMO these criteria aren't enough to decide if a request is REST. I'll look into see if we can find a better way to do this. Thanks On Tue, May 13, 2014 at 7:18 PM, Kasun Indrasiri ka...@wso2.com wrote: -1 HTTP EP is designed for outbound REST calls. So putting format=rest, is meaningless and hinders its whole purpose. We need to find a better alternative. May be we have to filter-out SOAP vs POX at the Axis2FlexibleMEPClient level ? On Wed, May 14, 2014 at 1:25 AM, Ravi Undupitiya r...@wso2.com wrote: Hi guys, Looks like format support is already there for HTTP Endpoint - just not in the UI. We can add the attribute format=rest to solve this issue. :) Thanks On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya r...@wso2.com wrote: Hello all, Isuru and I had a look at this, and we found the reason for this behaviour is to do with the isRest property not being set to true - by default when we send text/xml we assume that the invocation is not rest and therefor is a SOAP service invocation. The problem with this is that a valid REST invocation can also look like a SOAP invocation when the deciding factor is only the content type. To work around this the address endpoints have the format attribute where we can set format=rest. HTTP Endpoints don't have a mechanism to set the format at present. Shall we include the ability to set the format in HTTP Endpoint? Is this a correct fix? Thanks On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Hi, We observed following behavior in API Manager 1.7.0 which built on top of synapse 2.1.2.wso2v5. We sent same request to API created by fronting basic jaxrs service. Only difference is setting 2 content types. Backend service support both content types and we can invoke it without any issue. 01. Content-Type: text/xml [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1 02. Content-Type: application/xml [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers/ *customerservice/customers* HTTP/1.1 When content type is text/xml we can see part of the request is dropping. It send request directly to the endpoint defined in API without appending other things in client request url. Any idea what went wrong? Here is my API api name=admin--jaxrs context=/jaxrs version=1.0.0 version-type=url resource methods=POST GET DELETE OPTIONS PUT uri-template=/* inSequence property name=POST_TO_URI value=true scope=axis2/ filter source=$ctx:AM_KEY_TYPE regex=PRODUCTION then send endpoint name=admin--jaxrs_APIproductionEndpoint_0 http uri-template= http://10.100.1.65:9764/jaxrs_basic/services/customers; timeout duration3/duration responseActionfault/responseAction /timeout suspendOnFailure errorCodes-1/errorCodes initialDuration0/initialDuration progressionFactor1.0/progressionFactor maximumDuration0/maximumDuration /suspendOnFailure markForSuspension errorCodes-1/errorCodes /markForSuspension /http /endpoint /send /then else sequence key=_sandbox_key_error_/ /else /filter /inSequence outSequence send/ /outSequence /resource handlers handler class=org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler/ handler class=org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler property name=id value=A/ property name=policyKey value=gov:/apimgt/applicationdata/tiers.xml/ /handler handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtUsageHandler/ handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler
Re: [Dev] Issue in invoking APIs with POST request (with different content types)
I think at axis2 level we already do this (identifying soap vs pox based on Action). Can't we do the same? On Wed, May 14, 2014 at 2:05 AM, Ravi Undupitiya r...@wso2.com wrote: Hi Kasun, At present the Axis2FlexibleMEPClient detects a REST request by checking the HTTP method used and if the content type belongs to any of the following: application/xml application/x-www-form-urlencoded multipart/form-data application/json If the HTTP method is anything other than POST - then the request is assumed to be REST. If it is a POST, it checks to see if the messageType is one of the above. IMO these criteria aren't enough to decide if a request is REST. I'll look into see if we can find a better way to do this. Thanks On Tue, May 13, 2014 at 7:18 PM, Kasun Indrasiri ka...@wso2.com wrote: -1 HTTP EP is designed for outbound REST calls. So putting format=rest, is meaningless and hinders its whole purpose. We need to find a better alternative. May be we have to filter-out SOAP vs POX at the Axis2FlexibleMEPClient level ? On Wed, May 14, 2014 at 1:25 AM, Ravi Undupitiya r...@wso2.com wrote: Hi guys, Looks like format support is already there for HTTP Endpoint - just not in the UI. We can add the attribute format=rest to solve this issue. :) Thanks On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya r...@wso2.com wrote: Hello all, Isuru and I had a look at this, and we found the reason for this behaviour is to do with the isRest property not being set to true - by default when we send text/xml we assume that the invocation is not rest and therefor is a SOAP service invocation. The problem with this is that a valid REST invocation can also look like a SOAP invocation when the deciding factor is only the content type. To work around this the address endpoints have the format attribute where we can set format=rest. HTTP Endpoints don't have a mechanism to set the format at present. Shall we include the ability to set the format in HTTP Endpoint? Is this a correct fix? Thanks On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Hi, We observed following behavior in API Manager 1.7.0 which built on top of synapse 2.1.2.wso2v5. We sent same request to API created by fronting basic jaxrs service. Only difference is setting 2 content types. Backend service support both content types and we can invoke it without any issue. 01. Content-Type: text/xml [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1 02. Content-Type: application/xml [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers/ *customerservice/customers* HTTP/1.1 When content type is text/xml we can see part of the request is dropping. It send request directly to the endpoint defined in API without appending other things in client request url. Any idea what went wrong? Here is my API api name=admin--jaxrs context=/jaxrs version=1.0.0 version-type=url resource methods=POST GET DELETE OPTIONS PUT uri-template=/* inSequence property name=POST_TO_URI value=true scope=axis2/ filter source=$ctx:AM_KEY_TYPE regex=PRODUCTION then send endpoint name=admin--jaxrs_APIproductionEndpoint_0 http uri-template= http://10.100.1.65:9764/jaxrs_basic/services/customers; timeout duration3/duration responseActionfault/responseAction /timeout suspendOnFailure errorCodes-1/errorCodes initialDuration0/initialDuration progressionFactor1.0/progressionFactor maximumDuration0/maximumDuration /suspendOnFailure markForSuspension errorCodes-1/errorCodes /markForSuspension /http /endpoint /send /then else sequence key=_sandbox_key_error_/ /else /filter /inSequence outSequence send/ /outSequence /resource handlers handler class=org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler/ handler class=org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler property name=id value=A/ property name=policyKey value=gov:/apimgt/applicationdata/tiers.xml/ /handler
Re: [Dev] Issue in invoking APIs with POST request (with different content types)
Hi Kasun, On Tue, May 13, 2014 at 7:35 PM, Ravi Undupitiya r...@wso2.com wrote: Hi Kasun, At present the Axis2FlexibleMEPClient detects a REST request by checking the HTTP method used and if the content type belongs to any of the following: application/xml application/x-www-form-urlencoded multipart/form-data application/json If the HTTP method is anything other than POST - then the request is assumed to be REST. If it is a POST, it checks to see if the messageType is one of the above. IMO these criteria aren't enough to decide if a request is REST. I'll look into see if we can find a better way to do this. Thanks On Tue, May 13, 2014 at 7:18 PM, Kasun Indrasiri ka...@wso2.com wrote: -1 HTTP EP is designed for outbound REST calls. Don't we want to support SOAP calls with HttpEndpoint ? If not we can simply make rest=true at the HttpEndpoint code level. So putting format=rest, is meaningless and hinders its whole purpose. We need to find a better alternative. May be we have to filter-out SOAP vs POX at the Axis2FlexibleMEPClient level ? On Wed, May 14, 2014 at 1:25 AM, Ravi Undupitiya r...@wso2.com wrote: Hi guys, Looks like format support is already there for HTTP Endpoint - just not in the UI. We can add the attribute format=rest to solve this issue. :) Thanks On Tue, May 13, 2014 at 6:51 PM, Ravi Undupitiya r...@wso2.com wrote: Hello all, Isuru and I had a look at this, and we found the reason for this behaviour is to do with the isRest property not being set to true - by default when we send text/xml we assume that the invocation is not rest and therefor is a SOAP service invocation. The problem with this is that a valid REST invocation can also look like a SOAP invocation when the deciding factor is only the content type. To work around this the address endpoints have the format attribute where we can set format=rest. HTTP Endpoints don't have a mechanism to set the format at present. Shall we include the ability to set the format in HTTP Endpoint? Is this a correct fix? Thanks On Wed, May 7, 2014 at 6:59 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote: Hi, We observed following behavior in API Manager 1.7.0 which built on top of synapse 2.1.2.wso2v5. We sent same request to API created by fronting basic jaxrs service. Only difference is setting 2 content types. Backend service support both content types and we can invoke it without any issue. 01. Content-Type: text/xml [2014-05-07 18:36:31,114] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers HTTP/1.1 02. Content-Type: application/xml [2014-05-07 18:36:11,805] DEBUG - headers http-outgoing-6 POST http://10.100.1.65:9764/jaxrs_basic/services/customers/ *customerservice/customers* HTTP/1.1 When content type is text/xml we can see part of the request is dropping. It send request directly to the endpoint defined in API without appending other things in client request url. Any idea what went wrong? Here is my API api name=admin--jaxrs context=/jaxrs version=1.0.0 version-type=url resource methods=POST GET DELETE OPTIONS PUT uri-template=/* inSequence property name=POST_TO_URI value=true scope=axis2/ filter source=$ctx:AM_KEY_TYPE regex=PRODUCTION then send endpoint name=admin--jaxrs_APIproductionEndpoint_0 http uri-template= http://10.100.1.65:9764/jaxrs_basic/services/customers; timeout duration3/duration responseActionfault/responseAction /timeout suspendOnFailure errorCodes-1/errorCodes initialDuration0/initialDuration progressionFactor1.0/progressionFactor maximumDuration0/maximumDuration /suspendOnFailure markForSuspension errorCodes-1/errorCodes /markForSuspension /http /endpoint /send /then else sequence key=_sandbox_key_error_/ /else /filter /inSequence outSequence send/ /outSequence /resource handlers handler class=org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler/ handler class=org.wso2.carbon.apimgt.gateway.handlers.throttling.APIThrottleHandler property name=id value=A/ property name=policyKey value=gov:/apimgt/applicationdata/tiers.xml/
Re: [Dev] Product repo naming in GitHub
On Fri, Apr 25, 2014 at 3:26 PM, Sagara Gunathunga sag...@wso2.com wrote:
On Wed, Apr 23, 2014 at 1:03 PM, Madhuka Udantha madh...@wso2.com wrote:
On Tue, Apr 22, 2014 at 11:43 AM, Udara Rathnayake uda...@wso2.comwrote:
Hi all,
At the moment we do have our products within GitHub[1][2]. Since we need
to move in to the Git organizational model with repos in both wso2 and
wso2-dev organizations we can,
i) Rename existing repos within wso2 into product-{name}
ii) Create new repos and move existing source
By following the 1st approach we can keep our history
+1, for renaming repo.
We need to follow the same naming convention across the platform for the
simplicity, use of carbon/product prefix make it clear the purpose of
each project. If there is no objection I can rename those projects.
+1, you can rename those.
Thanks !
It help to track commit history
if we follow (ii), we can have issue in forks, externals,clones.
Therefore we have try (i)
(but we are going to work in wso2-dev fresh repo after this move) and
GitHub will redirect existing information to the new name[3]. Anyway we
have to create new repos within wso2-dev organization.
[1] https://github.com/wso2/enterprise-store
[2] https://github.com/wso2/ues
[3] https://help.github.com/articles/renaming-a-repository
Regards,
UdaraR
--
*Udara Rathnayake*
Software Engineer
WSO2 Inc. : http://wso2.com
Mobile : +94 772207239
Twitter : http://twitter.com/udarakr
Blog: http://udarakr.blogspot.com
--
*Madhuka* Udantha
Senior Software Engineer
Development Technologies
WSO2 Inc. : http://wso2.com
*Mobile*: +94774066336
*Blog*: http://madhukaudantha.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Sagara Gunathunga
Senior Technical Lead; WSO2, Inc.; http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ; http://ssagara.blogspot.com
--
*Ruchira Wageesha**Associate Technical Lead*
*WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com*
*email: ruch...@wso2.com ruch...@wso2.com, blog:
ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com,
mobile: +94 77 5493444*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error at SM while tenant is creating
TID: [0] [SCC] [2014-05-13 20:54:52,103] ERROR
{org.wso2.carbon.transaction.manager.TransactionManagerComponent} - Error
in binding transaction manager for tenant: 12
{org.wso2.carbon.transaction.manager.TransactionManagerComponent}
java.lang.RuntimeException: An error occurred while creating the initial
context for tenant: 12
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:908)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:951)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.wso2.carbon.transaction.manager.TransactionManagerComponent.bindTransactionManagerWithJNDIForTenant(TransactionManagerComponent.java:166)
at
org.wso2.carbon.transaction.manager.TransactionManagerAxis2ConfigurationContextObserver.createdConfigurationContext(TransactionManagerAxis2ConfigurationContextObserver.java:34)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:344)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
at
org.apache.stratos.rest.endpoint.services.AbstractAdmin.getConfigContext(AbstractAdmin.java:46)
at
org.apache.stratos.rest.endpoint.services.StratosAdmin.subscribe(StratosAdmin.java:363)
at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
Re: [Dev] Error at SM while tenant is creating
Hi,
On Tue, May 13, 2014 at 8:55 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
TID: [0] [SCC] [2014-05-13 20:54:52,103] ERROR
{org.wso2.carbon.transaction.manager.TransactionManagerComponent} - Error
in binding transaction manager for tenant: 12
{org.wso2.carbon.transaction.manager.TransactionManagerComponent}
This is a known issue and there is no bad impact on functionality of tenant
creation process or functionality of SM. I guess we can simply ignore it
Thanks,
Melan
java.lang.RuntimeException: An error occurred while creating the initial
context for tenant: 12
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:908)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:951)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.wso2.carbon.transaction.manager.TransactionManagerComponent.bindTransactionManagerWithJNDIForTenant(TransactionManagerComponent.java:166)
at
org.wso2.carbon.transaction.manager.TransactionManagerAxis2ConfigurationContextObserver.createdConfigurationContext(TransactionManagerAxis2ConfigurationContextObserver.java:34)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:344)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
at
org.apache.stratos.rest.endpoint.services.AbstractAdmin.getConfigContext(AbstractAdmin.java:46)
at
org.apache.stratos.rest.endpoint.services.StratosAdmin.subscribe(StratosAdmin.java:363)
at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
[Dev] [DEV][ES]Discovery Service failed attempt to connect CassandraHost
Hi all,
Noticed following error after adding the toolbox deployment feature plus
latest BAM publisher dependencies in to the social framework. I'm using
embedded Cassandra node within ES.
ERROR {me.prettyprint.cassandra.connection.NodeDiscovery} - Discovery
Service failed attempt to connect CassandraHost
java.lang.NullPointerException
at
me.prettyprint.cassandra.connection.NodeDiscovery.discoverNodes(NodeDiscovery.java:79)
at
me.prettyprint.cassandra.connection.NodeDiscovery.doAddNodes(NodeDiscovery.java:52)
at
me.prettyprint.cassandra.connection.NodeAutoDiscoverService.doAddNodes(NodeAutoDiscoverService.java:45)
at
me.prettyprint.cassandra.connection.NodeAutoDiscoverService$QueryRing.run(NodeAutoDiscoverService.java:51)
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)
Following is my cassandra-component.xml(using default configuration)
Cassandra
Cluster
NameTest Cluster/Name
DefaultPort9160/DefaultPort
!--Nodeslocalhost:9160/Nodes--
AutoDiscovery disable=true delay=1000/
/Cluster
/Cassandra
After setting following within log4j.properties file as a workaround, now I
dont see this error.
log4j.category.me.prettyprint.cassandra.connection.NodeDiscovery=OFF
But how can I actually solve this? What am I missing in my configs?
Regards,
UdaraR
--
*Udara Rathnayake*
Software Engineer
WSO2 Inc. : http://wso2.com
Mobile : +94 772207239
Twitter : http://twitter.com/udarakr
Blog: http://udarakr.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][ES]Discovery Service failed attempt to connect CassandraHost
Hi Udara,
This is a known bug in Hector. It's a missing null check. But we don't have
to worry about it, because this does not impact anything. And this is fixed
in next version of Hector. For now, as a workaround you can change the log
level. Better to make it FATAL rather than OFF.
Thanks,
Bhathiya
On Tue, May 13, 2014 at 12:26 PM, Udara Rathnayake uda...@wso2.com wrote:
Hi all,
Noticed following error after adding the toolbox deployment feature plus
latest BAM publisher dependencies in to the social framework. I'm using
embedded Cassandra node within ES.
ERROR {me.prettyprint.cassandra.connection.NodeDiscovery} - Discovery
Service failed attempt to connect CassandraHost
java.lang.NullPointerException
at
me.prettyprint.cassandra.connection.NodeDiscovery.discoverNodes(NodeDiscovery.java:79)
at
me.prettyprint.cassandra.connection.NodeDiscovery.doAddNodes(NodeDiscovery.java:52)
at
me.prettyprint.cassandra.connection.NodeAutoDiscoverService.doAddNodes(NodeAutoDiscoverService.java:45)
at
me.prettyprint.cassandra.connection.NodeAutoDiscoverService$QueryRing.run(NodeAutoDiscoverService.java:51)
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)
Following is my cassandra-component.xml(using default configuration)
Cassandra
Cluster
NameTest Cluster/Name
DefaultPort9160/DefaultPort
!--Nodeslocalhost:9160/Nodes--
AutoDiscovery disable=true delay=1000/
/Cluster
/Cassandra
After setting following within log4j.properties file as a workaround, now
I dont see this error.
log4j.category.me.prettyprint.cassandra.connection.NodeDiscovery=OFF
But how can I actually solve this? What am I missing in my configs?
Regards,
UdaraR
--
*Udara Rathnayake*
Software Engineer
WSO2 Inc. : http://wso2.com
Mobile : +94 772207239
Twitter : http://twitter.com/udarakr
Blog: http://udarakr.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Bhathiya Jayasekara*
*Software Engineer,*
*WSO2 inc., http://wso2.com http://wso2.com*
*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
http://www.linkedin.com/in/bhathiyaj*
*Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax*
*Blog: http://movingaheadblog.blogspot.com
http://movingaheadblog.blogspot.com/*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error at SM while tenant is creating
On Tue, May 13, 2014 at 9:19 PM, Melan Nimesh me...@wso2.com wrote:
Hi,
On Tue, May 13, 2014 at 8:55 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
TID: [0] [SCC] [2014-05-13 20:54:52,103] ERROR
{org.wso2.carbon.transaction.manager.TransactionManagerComponent} - Error
in binding transaction manager for tenant: 12
{org.wso2.carbon.transaction.manager.TransactionManagerComponent}
This is a known issue and there is no bad impact on functionality of
tenant creation process or functionality of SM. I guess we can simply
ignore it
Yes, its a known issue https://issues.apache.org/jira/browse/STRATOS-574.
We are planning to fix in a future release.
Thanks,
Melan
java.lang.RuntimeException: An error occurred while creating the initial
context for tenant: 12
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:908)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:951)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at
org.wso2.carbon.transaction.manager.TransactionManagerComponent.bindTransactionManagerWithJNDIForTenant(TransactionManagerComponent.java:166)
at
org.wso2.carbon.transaction.manager.TransactionManagerAxis2ConfigurationContextObserver.createdConfigurationContext(TransactionManagerAxis2ConfigurationContextObserver.java:34)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:344)
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:135)
at
org.apache.stratos.rest.endpoint.services.AbstractAdmin.getConfigContext(AbstractAdmin.java:46)
at
org.apache.stratos.rest.endpoint.services.StratosAdmin.subscribe(StratosAdmin.java:363)
at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:194)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:100)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:57)
at
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:93)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:271)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at
org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at
org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:223)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:203)
at
org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:137)
at
org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:159)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at
org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:262)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:56)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
[Dev] [APIM] Build failure
Hi, I am getting the following build failure. [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ org.wso2.carbon.apimgt.impl --- [INFO] Compiling 102 source files to /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[362,59] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[476,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,76] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,31] operator + cannot be applied to int,org.wso2.carbon.registry.core.pagination.PaginationContext.getLength [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,43] incompatible types found : nulltype required: int [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[1181,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [INFO] 6 errors [INFO] - [INFO] [INFO] BUILD FAILURE -- Thanks and Regards *,Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Build failure
What is your Java version? Try using Oracle JDK 6? On Tue, May 13, 2014 at 3:21 PM, Shani Ranasinghe sh...@wso2.com wrote: Hi, I am getting the following build failure. [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ org.wso2.carbon.apimgt.impl --- [INFO] Compiling 102 source files to /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[362,59] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[476,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,76] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,31] operator + cannot be applied to int,org.wso2.carbon.registry.core.pagination.PaginationContext.getLength [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,43] incompatible types found : nulltype required: int [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[1181,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [INFO] 6 errors [INFO] - [INFO] [INFO] BUILD FAILURE -- Thanks and Regards *, Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Build failure
Hi, yes, I am building a development branch. the latest version for the component. Java version 1.7 On Tue, May 13, 2014 at 3:23 PM, Isuru Perera isu...@wso2.com wrote: What is your Java version? Try using Oracle JDK 6? On Tue, May 13, 2014 at 3:21 PM, Shani Ranasinghe sh...@wso2.com wrote: Hi, I am getting the following build failure. [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ org.wso2.carbon.apimgt.impl --- [INFO] Compiling 102 source files to /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[362,59] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[476,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,76] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,31] operator + cannot be applied to int,org.wso2.carbon.registry.core.pagination.PaginationContext.getLength [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,43] incompatible types found : nulltype required: int [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[1181,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [INFO] 6 errors [INFO] - [INFO] [INFO] BUILD FAILURE -- Thanks and Regards *, Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ 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 -- Thanks and Regards *,Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Build failure
Same error is mentioned here in *API Manager build failure in 4.2.0 support branch* which should be solved by building the kernel patch. Thanks, Bhathiya On Tue, May 13, 2014 at 3:25 PM, Shani Ranasinghe sh...@wso2.com wrote: Hi, yes, I am building a development branch. the latest version for the component. Java version 1.7 On Tue, May 13, 2014 at 3:23 PM, Isuru Perera isu...@wso2.com wrote: What is your Java version? Try using Oracle JDK 6? On Tue, May 13, 2014 at 3:21 PM, Shani Ranasinghe sh...@wso2.com wrote: Hi, I am getting the following build failure. [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ org.wso2.carbon.apimgt.impl --- [INFO] Compiling 102 source files to /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[362,59] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[476,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,76] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,31] operator + cannot be applied to int,org.wso2.carbon.registry.core.pagination.PaginationContext.getLength [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,43] incompatible types found : nulltype required: int [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[1181,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [INFO] 6 errors [INFO] - [INFO] [INFO] BUILD FAILURE -- Thanks and Regards *, Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ 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 -- Thanks and Regards *, Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax* *Blog: http://movingaheadblog.blogspot.com http://movingaheadblog.blogspot.com/* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Build failure
Hi Bhathiya, Yes as mentioned in the mail it was the kernel patch, which was not correctly built. Thanks for pointing this out. On Tue, May 13, 2014 at 3:31 PM, Shani Ranasinghe sh...@wso2.com wrote: Thanks Bhathiya. Will check. On Tue, May 13, 2014 at 3:28 PM, Bhathiya Jayasekara bhath...@wso2.comwrote: Same error is mentioned here in *API Manager build failure in 4.2.0 support branch* which should be solved by building the kernel patch. Thanks, Bhathiya On Tue, May 13, 2014 at 3:25 PM, Shani Ranasinghe sh...@wso2.com wrote: Hi, yes, I am building a development branch. the latest version for the component. Java version 1.7 On Tue, May 13, 2014 at 3:23 PM, Isuru Perera isu...@wso2.com wrote: What is your Java version? Try using Oracle JDK 6? On Tue, May 13, 2014 at 3:21 PM, Shani Ranasinghe sh...@wso2.comwrote: Hi, I am getting the following build failure. [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ org.wso2.carbon.apimgt.impl --- [INFO] Compiling 102 source files to /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[362,59] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[476,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,76] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,31] operator + cannot be applied to int,org.wso2.carbon.registry.core.pagination.PaginationContext.getLength [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[532,43] incompatible types found : nulltype required: int [ERROR] /home/shani/sranasinghe/carbon/platform/branches/turing/components/apimgt/org.wso2.carbon.apimgt.impl/1.2.2/src/main/java/org/wso2/carbon/apimgt/impl/APIConsumerImpl.java:[1181,61] cannot find symbol symbol : method getLength() location: class org.wso2.carbon.registry.core.pagination.PaginationContext [INFO] 6 errors [INFO] - [INFO] [INFO] BUILD FAILURE -- Thanks and Regards *, Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ 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 -- Thanks and Regards *, Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* *Phone: +94715478185 %2B94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax* *Blog: http://movingaheadblog.blogspot.com http://movingaheadblog.blogspot.com/* -- Thanks and Regards *,Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab -- Thanks and Regards *,Shani Ranasinghe* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273555 linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab ___ Dev
Re: [Dev] [DEV][ES]Discovery Service failed attempt to connect CassandraHost
sent from my nexus4, ignore any typos
On May 14, 2014 2:27 AM, Bhathiya Jayasekara bhath...@wso2.com wrote:
Hi Udara,
This is a known bug in Hector. It's a missing null check. But we don't
have to worry about it, because this does not impact anything. And this is
fixed in next version of Hector. For now, as a workaround you can change
the log level. Better to make it FATAL rather than OFF.
+1, thanks bhathiya for this information.
Thanks,
Bhathiya
On Tue, May 13, 2014 at 12:26 PM, Udara Rathnayake uda...@wso2.com
wrote:
Hi all,
Noticed following error after adding the toolbox deployment feature plus
latest BAM publisher dependencies in to the social framework. I'm using
embedded Cassandra node within ES.
ERROR {me.prettyprint.cassandra.connection.NodeDiscovery} - Discovery
Service failed attempt to connect CassandraHost
java.lang.NullPointerException
at
me.prettyprint.cassandra.connection.NodeDiscovery.discoverNodes(NodeDiscovery.java:79)
at
me.prettyprint.cassandra.connection.NodeDiscovery.doAddNodes(NodeDiscovery.java:52)
at
me.prettyprint.cassandra.connection.NodeAutoDiscoverService.doAddNodes(NodeAutoDiscoverService.java:45)
at
me.prettyprint.cassandra.connection.NodeAutoDiscoverService$QueryRing.run(NodeAutoDiscoverService.java:51)
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)
Following is my cassandra-component.xml(using default configuration)
Cassandra
Cluster
NameTest Cluster/Name
DefaultPort9160/DefaultPort
!--Nodeslocalhost:9160/Nodes--
AutoDiscovery disable=true delay=1000/
/Cluster
/Cassandra
After setting following within log4j.properties file as a workaround,
now I dont see this error.
log4j.category.me.prettyprint.cassandra.connection.NodeDiscovery=OFF
But how can I actually solve this? What am I missing in my configs?
Regards,
UdaraR
--
Udara Rathnayake
Software Engineer
WSO2 Inc. : http://wso2.com
Mobile : +94 772207239
Twitter : http://twitter.com/udarakr
Blog: http://udarakr.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Bhathiya Jayasekara
Software Engineer,
WSO2 inc., http://wso2.com
Phone: +94715478185
LinkedIn: http://www.linkedin.com/in/bhathiyaj
Twitter: https://twitter.com/bhathiyax
Blog: http://movingaheadblog.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk 11 - Nightly Build Packs (13/05/2014)
Hi All, Please find the $subject at: http://ec2-54-198-211-48.compute-1.amazonaws.com/chunk11/13-05-2014/ Built from revision: 202760. Thanks Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Global cache invalidation meeting notes
Hi Shazni, Let's go with the notification based mechanism as Azeez suggested. Hi Azeez, Please let me know where is the interface located and which dataholder holds the osgi service. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Tue, May 13, 2014 at 6:07 PM, Shazni Nazeer sha...@wso2.com wrote: Hi Amal, Messages are not getting received after this modification. I noticed very less number of messages getting published too. No modification on registry kernel side is made. Shazni Nazeer Senior Software Engineer Mob : +94 715 440 607 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Tue, May 13, 2014 at 6:04 PM, Afkham Azeez az...@wso2.com wrote: On Tue, May 13, 2014 at 4:30 PM, Amal Gunatilake am...@wso2.com wrote: Hi All, Following updates has been discussed on $subject. 1) The isCoordinator check is not necessary for publishing the cache invalidation message. 2) Separate the implementation of publisher and subscriber into 2 classes. 3) Alter the implementation to support, when the isCoordinator node goes down; the next coordinator node should get auto subscribe to the topic. The 3rd point was discussed to implement as follows: The osgi service implementation bundle will be present at all nodes. So it will check whether Am I the coordinator? in a given time interval (This time interval can be configured in cache.xml). When one node goes down then the next coordinator will become the coordinator. At this point Am I the coordinator? will get the response and it will subscribe it-self to the topic. There is a better way of implementing this. When a node becomes a coordinator, it would notify all OSGi services which implement that interface. I already have this implemented in C5 kernel (must check). We need to bring that back in. Rather than have a task that checks whether I am the coordinator, we should use this notification based mechanism. Please update the thread if there are any further updates. Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
