Re: [Dev] Build failure in Chunk-12 [cannot find symbol getCurrentUser() org.wso2.carbon.andes.stub.AndesAdminServiceStub]
Hi Shammi, Noticed this behavior and I have fixed this by getting the current user from our side. On Mon, May 12, 2014 at 9:08 AM, Shammi Jayasinghe sha...@wso2.com wrote: Hi Janaka, Sorry for the inconvenience caused , We have changed the access modifier from public to private since we thought not to expose them via admin service due to security reasons after talking to security team. Please contact MB team if you face any issue with the above change. Apart from that after discussing with Dimuthu, we agreed to keep getAccessToken method with out any change. Thanks Shammi On Sat, May 10, 2014 at 11:48 AM, Janaka Ranabahu jan...@wso2.com wrote: Hi Shammi, Chunk-12 build fails due to the following exception. Did you guys remove this method? [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:15.688s [INFO] Finished at: Sat May 10 11:33:10 IST 2014 [INFO] Final Memory: 238M/1635M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.appfactory.eventing: Compilation failure [ERROR] /home/janaka/work/wso2/carbon/carbon_4/platform/branches/turing/components/appfac/org.wso2.carbon.appfactory.eventing/2.0.0/src/main/java/org/wso2/carbon/appfactory/eventing/jms/AndesAdminServiceClient.java:[59,23] cannot find symbol *[ERROR] symbol : method getCurrentUser()* *[ERROR] location: class org.wso2.carbon.andes.stub.AndesAdminServiceStub* *[ERROR] - [Help 1]* [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :org.wso2.carbon.appfactory.eventing Thanks, Janaka -- *Janaka Ranabahu* Senior Software Engineer; WSO2 Inc.; http://wso2.com * E-mail: jan...@wso2.com http://wso2.com**M: **+94 718370861 %2B94%20718370861* Lean . Enterprise . Middleware -- Best Regards, * Shammi Jayasinghe* Associate Tech Lead WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev Thank You. Ranga. -- Ranga Siriwardena Software Engineer WSO2 Inc. ___ 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
On Mon, May 12, 2014 at 2:00 PM, Pulasthi Supun pulas...@wso2.com wrote: 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 org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124) 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) Regards, Pulasthi -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- *Jasintha Dasanayake* *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/lean . enterprise . middleware* *mobile :- 0711368118* ___ 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
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.comwrote: On Mon, May 12, 2014 at 2:00 PM, Pulasthi Supun pulas...@wso2.com wrote: 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 org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124) 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) Regards, Pulasthi -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- *Jasintha Dasanayake * *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/ lean . enterprise . middleware* *mobile :- 0711368118* -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile:
[Dev] Issue invoking certain Synapse endpoints created in tenant mode
Noticed the following issue with regards to Synapse endpoints created in
tenant mode in the latest unreleased API Manager 1.7.0,
If the endpoint URL is *https://www.google.com
https://www.google.com*invoking this via curl leads to 404 Error.
The wire output looks as follows,
TID: [0] [AM] [2014-05-12 13:05:28,626] DEBUG
{org.apache.synapse.transport.http.wire} - GET /t/
wso2.com/GoogAPI/1.0.0 HTTP/1.1[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,627] DEBUG
{org.apache.synapse.transport.http.wire} - User-Agent:
curl/7.32.0[\r][\n] {org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,628] DEBUG
{org.apache.synapse.transport.http.wire} - Host: 10.100.5.30:8280[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,628] DEBUG
{org.apache.synapse.transport.http.wire} - Accept: */*[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,628] DEBUG
{org.apache.synapse.transport.http.wire} - Authorization: Bearer
e3f51990b78b7cae266ce6d46b62ed9[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,628] DEBUG
{org.apache.synapse.transport.http.wire} - [\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,850] DEBUG
{org.apache.synapse.transport.http.wire} - GET
HTTP/1.1[\r][\n]{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,850] DEBUG
{org.apache.synapse.transport.http.wire} - Accept: */*[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,850] DEBUG
{org.apache.synapse.transport.http.wire} - Host:
www.google.com:80[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,850] DEBUG
{org.apache.synapse.transport.http.wire} - Connection:
Keep-Alive[\r][\n] {org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,851] DEBUG
{org.apache.synapse.transport.http.wire} - User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,851] DEBUG
{org.apache.synapse.transport.http.wire} - [\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,920] DEBUG
{org.apache.synapse.transport.http.wire} - HTTP/1.0 404 Not
Found[\r][\n] {org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:28,921] DEBUG
{org.apache.synapse.transport.http.wire} - Content-Type: text/html;
charset=UTF-8[\r][\n] {org.apache.synapse.transport.http.wire}
if the endpoint URL is *https://www.google.com/maps
https://www.google.com/maps* invocation is successful. The wire output
looks as follows,
TID: [0] [AM] [2014-05-12 13:05:41,304] DEBUG
{org.apache.synapse.transport.http.wire} - GET
/t/wso2.com/maps/1.0.0HTTP/1.1[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,306] DEBUG
{org.apache.synapse.transport.http.wire} - User-Agent:
curl/7.32.0[\r][\n] {org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,306] DEBUG
{org.apache.synapse.transport.http.wire} - Host: 10.100.5.30:8280[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,306] DEBUG
{org.apache.synapse.transport.http.wire} - Accept: */*[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,307] DEBUG
{org.apache.synapse.transport.http.wire} - Authorization: Bearer
e3f51990b78b7cae266ce6d46b62ed9[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,307] DEBUG
{org.apache.synapse.transport.http.wire} - [\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,576] DEBUG
{org.apache.synapse.transport.http.wire} - GET /maps HTTP/1.1[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,576] DEBUG
{org.apache.synapse.transport.http.wire} - Accept: */*[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,577] DEBUG
{org.apache.synapse.transport.http.wire} - Host:
www.google.com:80[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,577] DEBUG
{org.apache.synapse.transport.http.wire} - Connection:
Keep-Alive[\r][\n] {org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,577] DEBUG
{org.apache.synapse.transport.http.wire} - User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,577] DEBUG
{org.apache.synapse.transport.http.wire} - [\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,719] DEBUG
{org.apache.synapse.transport.http.wire} - HTTP/1.1 200 OK[\r][\n]
{org.apache.synapse.transport.http.wire}
TID: [0] [AM] [2014-05-12 13:05:41,719] DEBUG
{org.apache.synapse.transport.http.wire} - X-Frame-Options:
SAMEORIGIN[\r][\n] {org.apache.synapse.transport.http.wire}
TID: [0]
Re: [Dev] Java version problems when creating axis2 services with DevS 3.6 and deploying in AS 5.2.1
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.com wrote: 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.comwrote: 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 org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124) 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) Regards, Pulasthi -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: pulas...@wso2.com Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi -- *Jasintha Dasanayake * *Senior Software
Re: [Dev] BRS 2.1.0 [Ch-11] Testing
Hi, Updated the cluster setup with this pack and verified issue [1] in cluster setup (with WSO2 BRS 2.1.0-9th May pack). No longer get that exception when invoking Rule services. Thanks, Sandapa On Fri, May 9, 2014 at 5:37 PM, Sandapa Handakumbura sand...@wso2.comwrote: Hi, Verified the fix given for [1] in a standalone pack and the issue seems to be fixed. We will update the cluster with this pack to verify the fix in the cluster. [1] https://wso2.org/jira/browse/BRS-74 Thanks, Sandapa On Fri, May 9, 2014 at 3:21 PM, Waruna Jayaweera waru...@wso2.com wrote: Hi Sandapa,Chathurika, Latest pack is available to QA [1]. [1] https://svn.wso2.org/repos/wso2/people/warunaj/pre-release/brs-2.1.0/2014-05-09/wso2brs- 2.1.0.zip -- Regards, Waruna Lakshitha Jayaweera Software Engineer WSO2 Inc; http://wso2.com phone: +94713255198 -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866 -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Renaming APIM workflow-admin appication as admin
Hi all, Please note that 'workflow-admin' jaggery application has been renamed as 'admin'[1], since now it is used to administer non workflow related tasks as well (tenant themes). For the backward compatibility an application with 'workflow-admin' context is still available and it redirects to this new 'admin' application. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/apimgt/admin-web/1.2.2 Thanks, Lakmali -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Java version problems when creating axis2 services with DevS 3.6 and deploying in AS 5.2.1
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.com wrote: 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.com wrote: 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.comwrote: 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 org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124) 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
Re: [Dev] Renaming APIM workflow-admin appication as admin
On Mon, May 12, 2014 at 3:10 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: is Shall we make it admin-console / admin-dashboard ? Just admin does not have that a cool ring to it. :) 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Renaming APIM workflow-admin appication as admin
+1 for something like admin-dashboard. admin-console sounds more like the management console. Thanks, NuwanD. On Mon, May 12, 2014 at 3:26 PM, Ruwan Yatawara ruw...@wso2.com wrote: On Mon, May 12, 2014 at 3:10 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: is Shall we make it admin-console / admin-dashboard ? Just admin does not have that a cool ring to it. :) 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 -- 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] Renaming APIM workflow-admin appication as admin
+1 for 'admin-dashboard'. On Mon, May 12, 2014 at 3:39 PM, Nuwan Dias nuw...@wso2.com wrote: +1 for something like admin-dashboard. admin-console sounds more like the management console. Thanks, NuwanD. On Mon, May 12, 2014 at 3:26 PM, Ruwan Yatawara ruw...@wso2.com wrote: On Mon, May 12, 2014 at 3:10 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: is Shall we make it admin-console / admin-dashboard ? Just admin does not have that a cool ring to it. :) 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 -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Renaming APIM workflow-admin appication as admin
+1. Renamed as admin-dashboard [2]. [2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/apimgt/admin-dashboard-web/1.2.2 On 12 May 2014 15:43, Sumedha Rubasinghe sume...@wso2.com wrote: +1 for 'admin-dashboard'. On Mon, May 12, 2014 at 3:39 PM, Nuwan Dias nuw...@wso2.com wrote: +1 for something like admin-dashboard. admin-console sounds more like the management console. Thanks, NuwanD. On Mon, May 12, 2014 at 3:26 PM, Ruwan Yatawara ruw...@wso2.com wrote: On Mon, May 12, 2014 at 3:10 PM, Lakmali Baminiwatta lakm...@wso2.comwrote: is Shall we make it admin-console / admin-dashboard ? Just admin does not have that a cool ring to it. :) 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 -- Nuwan Dias Associate Tech Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- /sumedha m: +94 773017743 b : bit.ly/sumedha -- Lakmali Baminiwatta Senior Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Clean Nexus Snapshots repo tonight
As following repo[1] contains some old and unused SNAPSHOT dependencies from Carbon 4.3.0 projects I'm planning to clean it tonight LK time. For few hours you may experience dependency missing issue till Jenkins push new SNAPSHOT versions into Nexus again. [1] - http://maven.wso2.org/nexus/content/repositories/snapshots/ Thanks ! -- 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Identity Server 5.0.0 build - 12-05-2014
Hi, Please find the subject at [1] [1] https://svn.wso2.org/repos/wso2/scratch/IS-5.0.0/12-05-2014/wso2is-5.0.0.zip Thanks Regards Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] WSO2 Message Broker - 2.2.0 Beta Released!
WSO2 Message Broker 2.2.0 Beta Released! WSO2 Message Broker team is pleased to announce the release of 2.2.0 Beta version of WSO2 Message Broker. This release is now available at [1], and is built upon r202634. *How to Run* The only prerequisite required to try this release out is an installation of JDK 1.6 (Sun/Oracle JDK 1.6.0_23 or higher recommended) - Download the WSO2 MB 2.2.0- beta release from [1]. - Extract the downloaded archive. - Go to the 'bin' directory and execute wso2server.sh (Unix/Linux) or wso2server.bat (Windows) as appropriate. - Point your web browser to http://localhost:9443/carbon to get started. - Use 'admin/admin' as the default username/password to be logged in. *New Features In this version* - Dead letter channel - Publisher flow control support - Improved queue/topic permission model - Carbon profiles support for Zookeeper and Cassandra profiles - JMS message selectors support - Improved UI with queue/topic subscriptions viewer *Bug Fixes and Improvements* Following bug fixes and improvements are available in the current release[2]. We highly appreciate your feedback on this beta release. Please report any issues at https://wso2.org/jira/browse/MB. If you want to see a particular feature changed or improved, drop us a mail at dev@wso2.org orarchitect...@wso2.org [1] https://svn.wso2.org/repos/wso2/scratch/MB-2.2.0/beta/ [2] https://wso2.org/jira/issues/?filter=11812 Thanks and Regards, ~ WSO2 MB Team ~ -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ http://isharapremadasa.blogspot.com/ Twitter : https://twitter.com/ishadil https://twitter.com/ishadilMobile : +94 714445832 %2B94%20714445832* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fixing Shutdown Errors WSO2 MB.
Hi Hasitha,
The cassandra service related shut down errors are fixed now by Prabath.
However i noticed few more shut down errors occurring from andes side when
gracefully shutting down cluster nodes, as below.
[2014-05-12 12:58:04,856] INFO
{org.wso2.andes.server.cluster.ClusterManager} - Handling cluster gossip:
Node with ID 0 left the cluster
[2014-05-12 12:58:04,856] ERROR
{org.wso2.andes.server.cluster.ClusterManager} - Error while removing node
details
java.lang.RuntimeException: Error accessing Node details to cassandra
database
at
org.wso2.andes.server.store.CassandraMessageStore.deleteNodeData(CassandraMessageStore.java:4817)
at
org.wso2.andes.server.cluster.ClusterManager$NodeExistenceListener.process(ClusterManager.java:609)
at
org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:519)
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:495)
[2014-05-12 14:42:27,481] ERROR
{org.wso2.andes.server.cluster.ClusterManager} - Error in getting
destination queues from store
org.wso2.andes.AMQStoreException: Error in loading queues [error code 541:
internal error]
at
org.wso2.andes.server.store.CassandraMessageStore.getDestinationQueues(CassandraMessageStore.java:4024)
at
org.wso2.andes.server.cluster.ClusterManager.getDestinationQueuesInCluster(ClusterManager.java:805)
at
org.wso2.andes.server.cluster.GlobalQueueWorker.isThisWorkerShouldWork(GlobalQueueWorker.java:216)
at
org.wso2.andes.server.cluster.GlobalQueueWorker.run(GlobalQueueWorker.java:75)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.wso2.andes.server.store.util.CassandraDataAccessException:
Error while getting data from : QueueDetails
at
org.wso2.andes.server.store.util.CassandraDataAccessHelper.getStringTypeColumnsInARow(CassandraDataAccessHelper.java:700)
at
org.wso2.andes.server.store.CassandraMessageStore.getDestinationQueues(CassandraMessageStore.java:4013)
... 6 more
The reason seems to be that, when we close the CassandraMessageStore we are
disconnecting the hector client connection with the cluster.
cluster.getConnectionManager().shutdown();
However after that, there are node existence listeners etc. still get
triggered for the shutdown node and this cause the error logs.
IMO we have to shutdown the connection to cluster after we process all
these operations. Or is there any requirement that we close the hector
client pool in here?
Thanks!
On Thu, May 8, 2014 at 3:38 PM, Ishara Premadasa ish...@wso2.com wrote:
Hi PrabathA et all,
We are still experiencing this issue as reported in [1] when shutting
down. As stated by Hasitha it seems Cassandra message service thread is
shutdown before we perform all data cleaning tasks in MB, as per below
logs.
*[2014-05-08 14:51:15,299] INFO
{org.apache.cassandra.net.MessagingService} - Waiting for messaging
service to quiesce[2014-05-08 14:51:15,303] INFO
{org.apache.cassandra.net.MessagingService} - MessagingService shutting
down server thread.*
[2014-05-08 14:51:15,722] INFO
{org.wso2.andes.server.store.CassandraMessageStore} - Clearing up
Subscription Information
[2014-05-08 14:51:15,722] INFO
{org.wso2.andes.server.cassandra.DefaultClusteringEnabledSubscriptionManager}
- Clearing the Persisted State of Node with ID 0
[2014-05-08 14:51:15,733] ERROR
{org.apache.cassandra.thrift.CustomTThreadPoolServer} - Error occurred
during processing of message.
java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has
shut down
at
org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:61)
Can we please know the progress of fixing this issue, or else can you
please suggest us what might be the reason for cassandra service getting
closed before deactivation of andes tasks are completed?
Thanks!
Ishara
[1] https://wso2.org/jira/browse/MB-301
On Mon, May 5, 2014 at 9:11 PM, Hasitha Hiranya hasit...@wso2.com wrote:
Hi,
Following is prabath's explanation
There's no any impact on Cassandra from the Transport Listener Framework.
Carbon transport listener framework opens up the ports used by the
transports configured upon the Carbon Server. However, here in this
particular scenario, Cassandra daemon is responsible for opening up all the
ports used by a given Cassandra Server. Therefore, Cassandra related ports
are opened up much later after the transport listener framework is
initialised. Similarly, when it comes to shutting down the server, the
Cassandra daemon is stopped before we shut down the listener framework.
So Prabath, how does this affect the OSGI integration of services? How
are we going to hold Cassandra until Andes is closed gracefully?
Thanks
On Sat, May 3, 2014 at 12:59 PM,
[Dev] UES migration to carbon 4.3.0
Hi all, I have created a new branch 1.2.0[1] on UES GitHub repo[2] to work on the $subject. As communicated early[3] we need the logic within org.wso2.stratos.identity.saml2.sso.mgt inside org.wso2.carbon.identity.sso.saml component to have a workable UES pack also. As per the offline chat I had with Chamath, we can expect the above with next IS release. [1] https://github.com/wso2/ues/tree/1.2.0 [2] https://github.com/wso2/ues [3] [Dev] ES 4.3.0 migration status 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
[Dev] Business Rule Server 2.1.0 (Ch-11) - Testing update
Hi All, We have been testing the alpha pack until the latest pack was released on the 9th. There was a major issue [1] in alpha pack that was blocking us from testing Rule service feature and it has been fixed in the 9th May pack. WarunaJ is working on other reported issues. Testing is carried out in a Worker/Manager separated cluster (deployment pattern1) and test cases executed so far, are marked in [2]. We have tested the basic scenarios of Integrating BRS with IS (SSO), BPS and ESB. Planning to do further testing around those integration scenarios. Load / Performance tests are yet to be done. [1] https://wso2.org/jira/browse/BRS-74 [2] https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AnpVKBDCKX9ldERGSzFZaUxJMWFKVlVObEh0akJYRncusp=sharing#gid=1 Thanks, -- Sandapa Handakumbura Associate Technical Lead WSO2.Inc. ; http://wso2.com/ M : +94777115866 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sugarcane release
On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ 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 ___ 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)
Any update on this issue? Thanks, sanjeewa. 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/ -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 http://sanjeewamalalgoda.blogspot.com/blog :http://sanjeewamalalgoda.blogspot.com/http://sanjeewamalalgoda.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ELB Experiment
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.com wrote: 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.com wrote: 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automated test case generation tool
hi, I was little bit busy with my academic work these days. But today onwards i will be able to give more attention to the project. i implemented a simple solution to test web service with robot framework. So i will demonstrate the solution tomorrow on Google hangout. Thanks and regards. On Sun, May 4, 2014 at 9:56 PM, Rukshan Chathuranga rcruksha...@gmail.comwrote: Hi Malintha,Dharshana,Krishantha, I followed the resource you provided.So After eclipse and maven integration, i could implement a solution to test web Service using Robot keyword driven testing. - Project contain the WSDL file and generate the java code - Create a Client class to test the web-service methods using generated code. - Created Client act as Keyword Library to Robot (Client Methods) - Project Contain the .txt file with test cases written in natural language keywords(Client Methods). - that .txt can be run using robot - Each of this step can be execute in one eclipse project. Thanks. -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sugarcane release
Hi, It is 'jaggery-test' and you can added it jaggery-extension. If we have any other repo/org is ready for jaggery modules, you can add it there and get release. [1] https://github.com/wso2/jaggery-extensions On Mon, May 12, 2014 at 6:24 PM, Sagara Gunathunga sag...@wso2.com wrote: On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] High Availability ELB Active- Passive + ESB
Hi!! I have deployed and working a High Availability solution based on one ELB, one Manager, and two worker nodes. The fact now is that, If I want to avoid having one single point of failure, I must go for a solution like the exposed here: https://docs.wso2.org/display/ELB210/Automatic+Failover The question I have is (and sorry if it sounds stupid): Do I need to set different workers and manager nodes to join the passive ELB or I could tell the existent manager and workers to join both ELB's?? I suppose that the second option is the right one but I am not sure that I can do that through the loadbalancer.conf and axis2.xml configuration using WKA. Thank you very much in advance, and best regards. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sugarcane release
Where is jaggery-test? Can't seem to find it.. On Mon, May 12, 2014 at 8:41 PM, madhuka udantha madhukaudan...@gmail.comwrote: Hi, It is 'jaggery-test' and you can added it jaggery-extension. If we have any other repo/org is ready for jaggery modules, you can add it there and get release. [1] https://github.com/wso2/jaggery-extensions On Mon, May 12, 2014 at 6:24 PM, Sagara Gunathunga sag...@wso2.comwrote: On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automated test case generation tool
Hi Rukshan, On Mon, May 12, 2014 at 8:40 PM, Rukshan Chathuranga rcruksha...@gmail.comwrote: hi, I was little bit busy with my academic work these days. But today onwards i will be able to give more attention to the project. i implemented a simple solution to test web service with robot framework. So i will demonstrate the solution tomorrow on Google hangout. Nice to have a demo on your progress. I will join the hangout. Thanks and regards. On Sun, May 4, 2014 at 9:56 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: Hi Malintha,Dharshana,Krishantha, I followed the resource you provided.So After eclipse and maven integration, i could implement a solution to test web Service using Robot keyword driven testing. - Project contain the WSDL file and generate the java code - Create a Client class to test the web-service methods using generated code. - Created Client act as Keyword Library to Robot (Client Methods) - Project Contain the .txt file with test cases written in natural language keywords(Client Methods). - that .txt can be run using robot - Each of this step can be execute in one eclipse project. Thanks. -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- *Malintha Adikari* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: +94 71 2312958 Blog:http://malinthas.blogspot.com Page: http://about.me/malintha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automated test case generation tool
Hi All, Shall we schedule this between 3.30 PM to 6.30PM in any convenient day. Thank you, Dahrshana. On Mon, May 12, 2014 at 8:58 AM, Malintha Adikari malin...@wso2.com wrote: Hi Rukshan, On Mon, May 12, 2014 at 8:40 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: hi, I was little bit busy with my academic work these days. But today onwards i will be able to give more attention to the project. i implemented a simple solution to test web service with robot framework. So i will demonstrate the solution tomorrow on Google hangout. Nice to have a demo on your progress. I will join the hangout. Thanks and regards. On Sun, May 4, 2014 at 9:56 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: Hi Malintha,Dharshana,Krishantha, I followed the resource you provided.So After eclipse and maven integration, i could implement a solution to test web Service using Robot keyword driven testing. - Project contain the WSDL file and generate the java code - Create a Client class to test the web-service methods using generated code. - Created Client act as Keyword Library to Robot (Client Methods) - Project Contain the .txt file with test cases written in natural language keywords(Client Methods). - that .txt can be run using robot - Each of this step can be execute in one eclipse project. Thanks. -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- *Malintha Adikari* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: +94 71 2312958 Blog:http://malinthas.blogspot.com Page: http://about.me/malintha -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Sugarcane release
HI, chan you can get repo in my local git that you was referring. simple just rename it as you adding wso2 repo. On Mon, May 12, 2014 at 8:46 PM, Chan duli...@wso2.com wrote: Where is jaggery-test? Can't seem to find it.. On Mon, May 12, 2014 at 8:41 PM, madhuka udantha madhukaudan...@gmail.com wrote: Hi, It is 'jaggery-test' and you can added it jaggery-extension. If we have any other repo/org is ready for jaggery modules, you can add it there and get release. [1] https://github.com/wso2/jaggery-extensions On Mon, May 12, 2014 at 6:24 PM, Sagara Gunathunga sag...@wso2.comwrote: On Mon, May 12, 2014 at 6:14 PM, Chan duli...@wso2.com wrote: Hi folks, We are using sugarcane[1] testing framework for unit tests. It's currently not released. Can we please get it released and available in nexus repo. Guys, What is sugarcane ? what happen to JaggeryTest module that we agreed to develop. Cheers~ [1] - https://github.com/Madhuka/sugarcane I can't find any licence on above repo also not sure how we (WSO2) can release a product hosted on personal repo. Thanks ! -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- Cheers, Madhuka Udantha http://madhukaudantha.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Application Manager - Latest Build 2014-05-12
Please find the latest build at [1]. [1] http://builder1.us1.wso2.org/~appm/12-05-2014/ Latest Build includes several bug fixes and additional improvements: - Tagging and Rating - SAML SSO Provider configurator - Google analytics integration -- *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] Automated test case generation tool
hi, I'm okay with that time. is it okay to Malintha? thanks. On Mon, May 12, 2014 at 9:37 PM, Dharshana Warusavitharana dharsha...@wso2.com wrote: Hi All, Shall we schedule this between 3.30 PM to 6.30PM in any convenient day. Thank you, Dahrshana. On Mon, May 12, 2014 at 8:58 AM, Malintha Adikari malin...@wso2.comwrote: Hi Rukshan, On Mon, May 12, 2014 at 8:40 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: hi, I was little bit busy with my academic work these days. But today onwards i will be able to give more attention to the project. i implemented a simple solution to test web service with robot framework. So i will demonstrate the solution tomorrow on Google hangout. Nice to have a demo on your progress. I will join the hangout. Thanks and regards. On Sun, May 4, 2014 at 9:56 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: Hi Malintha,Dharshana,Krishantha, I followed the resource you provided.So After eclipse and maven integration, i could implement a solution to test web Service using Robot keyword driven testing. - Project contain the WSDL file and generate the java code - Create a Client class to test the web-service methods using generated code. - Created Client act as Keyword Library to Robot (Client Methods) - Project Contain the .txt file with test cases written in natural language keywords(Client Methods). - that .txt can be run using robot - Each of this step can be execute in one eclipse project. Thanks. -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- *Malintha Adikari* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: +94 71 2312958 Blog:http://malinthas.blogspot.com Page: http://about.me/malintha -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Please merge PR to jaggery-extension
https://github.com/wso2/jaggery-extensions/pull/5 Cheers~ -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Automated test case generation tool
Hi, I am ok for this 15th around 4PM LK time Regards, Malintha On Mon, May 12, 2014 at 10:30 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: hi, I'm okay with that time. is it okay to Malintha? thanks. On Mon, May 12, 2014 at 9:37 PM, Dharshana Warusavitharana dharsha...@wso2.com wrote: Hi All, Shall we schedule this between 3.30 PM to 6.30PM in any convenient day. Thank you, Dahrshana. On Mon, May 12, 2014 at 8:58 AM, Malintha Adikari malin...@wso2.comwrote: Hi Rukshan, On Mon, May 12, 2014 at 8:40 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: hi, I was little bit busy with my academic work these days. But today onwards i will be able to give more attention to the project. i implemented a simple solution to test web service with robot framework. So i will demonstrate the solution tomorrow on Google hangout. Nice to have a demo on your progress. I will join the hangout. Thanks and regards. On Sun, May 4, 2014 at 9:56 PM, Rukshan Chathuranga rcruksha...@gmail.com wrote: Hi Malintha,Dharshana,Krishantha, I followed the resource you provided.So After eclipse and maven integration, i could implement a solution to test web Service using Robot keyword driven testing. - Project contain the WSDL file and generate the java code - Create a Client class to test the web-service methods using generated code. - Created Client act as Keyword Library to Robot (Client Methods) - Project Contain the .txt file with test cases written in natural language keywords(Client Methods). - that .txt can be run using robot - Each of this step can be execute in one eclipse project. Thanks. -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- *Malintha Adikari* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: +94 71 2312958 Blog:http://malinthas.blogspot.com Page: http://about.me/malintha -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware -- Department Of Computer Science Engineering, Faculty Of Engineering, University Of Moratuwa. Sri lanka. WEB: http://rukspot.com/ -- *Malintha Adikari* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: +94 71 2312958 Blog:http://malinthas.blogspot.com Page: http://about.me/malintha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Private PaaS] Cannot access instances (in tenant mode ) via LB after LB restart
This is now fixed!
On Sat, May 10, 2014 at 12:25 AM, Melan Nimesh me...@wso2.com wrote:
Hi,
On Fri, May 9, 2014 at 7:10 PM, Nirmal Fernando nir...@wso2.com wrote:
Hi Melan,
AFAIK there's a complete tenant message too. Isn't LB listens to that at
the start-up?
Yes, there is a listener for CompleteTenantEvent in LB and
TenantSynzhronizerTask is the publisher for CompleteTenantEvent, I guess
there's an issue with setting cluster-Id for subscription in
TenantSynzhronizerTask's code. I did some small changes [1] to that code
and I will test it
[1]
---
a/source/components/org.apache.stratos.manager/src/main/java/org/apache/stratos/manager/publisher/TenantSynzhronizerTask.java
+++
b/source/components/org.apache.stratos.manager/src/main/java/org/apache/stratos/manager/publisher/TenantSynzhronizerTask.java
@@ -75,8 +75,9 @@ public class TenantSynzhronizerTask implements Task {
log.debug(String.format(Tenant subscription
found: [tenant-id] %d [tenant-domain] %s [service] %s,
carbonTenant.getId(),
carbonTenant.getDomain(), cartridgeSubscription.getType()));
}
-Subscription subscription = new
Subscription(cartridgeSubscription.getType(),
-new
HashSetString(cartridgeSubscription.getCluster().getId()));
+HashSetString clusterIds = new
HashSetString();
+
clusterIds.add(String.valueOf(cartridgeSubscription.getCluster().getId()));
+Subscription subscription = new
Subscription(cartridgeSubscription.getType(), clusterIds);
for(SubscriptionDomain subscriptionDomain :
cartridgeSubscription.getSubscriptionDomains()) {
subscription.addSubscriptionDomain(subscriptionDomain.getDomainName(),
subscriptionDomain.getApplicationContext());
}
On Fri, May 9, 2014 at 12:07 PM, Melan Nimesh me...@wso2.com wrote:
Hi All,
I noticed the $subject while testing LB for Private PaaS. Any tenant
created and subscribed before restart of LB cannot be access and getting
404 error *Active application instances not found*. This works fine
if existing session found in request (Such as Admin console requests [1])
and any request pass through via
*requestDelegator.findNextMemberFromHostName().
*I noticed cluster is getting null when calling
LoadBalancerContext.getInstance().getMultiTenantClusterMap().getCluster(hostName,
tenantId) in findNextMemberFromTenantId(). It seems multiTenantClusterMap
not get updated after LB restart. Can we use Complete topology to update
this? what is the best way this fix this?
Thanks,
Melan
[1]
TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
- Existing session found: JSESSIONID=A5E345AEA80006C03F60775E83531DA4
TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
- Updating axis2 member port
TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
- Outgoing request port found: 9443
TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
- Sending request to endpoint:
https://10.144.0.231:9443/t/my.org/carbon/service-mgt/index.jsp?region=region1item=services_list_menu
--
*Melan Nimesh*
Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
--
Thanks regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
--
*Melan Nimesh*
Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
--
*Melan Nimesh*
Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge PR to jaggery-extension
Hi Chan, Could you please redo the pull request by updating new_password, old_password to lower camelcase. That is the naming convention that we follow. This is just to make it consistent. /Ruchira On Mon, May 12, 2014 at 10:32 PM, Chan duli...@wso2.com wrote: https://github.com/wso2/jaggery-extensions/pull/5 Cheers~ -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- *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] Identity Server 5.0.0 nightly build - 12-05-2014
Hi, Please find the subject at [1] [1] https://svn.wso2.org/repos/wso2/scratch/IS-5.0.0/12-05-2014/nightly-build/wso2is-5.0.0.zip Thanks Regards Dulanja -- Dulanja Liyanage WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB Connector Store Icons
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.com wrote: Sure, Dushan. I will provide them by EOD. thanks, Chanaka On Mon, May 12, 2014 at 7:49 AM, Dushan Abeyruwan dus...@wso2.com wrote: 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.comwrote: 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 . 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. -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- 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
[Dev] Please respond to Github issue on android client
Hi Kasun, Please look into https://github.com/wso2/MDM-Android-Agent/issues/6 . Cheers~ -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge PR to jaggery-extension
Hi Ruchira, I have refactored the parameters. Please take a look at the same PR. I'll keep a note to follow the lower camelcase next time. Cheers~ On Tue, May 13, 2014 at 1:01 AM, Ruchira Wageesha ruch...@wso2.com wrote: Hi Chan, Could you please redo the pull request by updating new_password, old_password to lower camelcase. That is the naming convention that we follow. This is just to make it consistent. /Ruchira On Mon, May 12, 2014 at 10:32 PM, Chan duli...@wso2.com wrote: https://github.com/wso2/jaggery-extensions/pull/5 Cheers~ -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- *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 %2B94%2077%205493444* -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Please merge PR to jaggery-extension
Done. On Tue, May 13, 2014 at 7:50 AM, Chan duli...@wso2.com wrote: Hi Ruchira, I have refactored the parameters. Please take a look at the same PR. I'll keep a note to follow the lower camelcase next time. Cheers~ On Tue, May 13, 2014 at 1:01 AM, Ruchira Wageesha ruch...@wso2.comwrote: Hi Chan, Could you please redo the pull request by updating new_password, old_password to lower camelcase. That is the naming convention that we follow. This is just to make it consistent. /Ruchira On Mon, May 12, 2014 at 10:32 PM, Chan duli...@wso2.com wrote: https://github.com/wso2/jaggery-extensions/pull/5 Cheers~ -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- *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 %2B94%2077%205493444* -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* -- *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
Re: [Dev] Please respond to Github issue on android client
Hi Chan, I will look into it. Thanks On 13 May 2014 07:49, Chan duli...@wso2.com wrote: Hi Kasun, Please look into https://github.com/wso2/MDM-Android-Agent/issues/6 . Cheers~ -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulitha.me http://dulitha.me* * ~Twitter @dulitharw https://twitter.com/dulitharw* *~Github @dulichan https://github.com/dulichan* *~SO @chan http://stackoverflow.com/users/813471/chan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Application Manager - Latest Build 2014-05-12
Rating feature is not there yet. It is still under development. On Mon, May 12, 2014 at 10:14 PM, Ravi Undupitiya r...@wso2.com wrote: Please find the latest build at [1]. [1] http://builder1.us1.wso2.org/~appm/12-05-2014/ Latest Build includes several bug fixes and additional improvements: - Tagging and Rating - SAML SSO Provider configurator - Google analytics integration -- *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 -- *Rushmin Fernando* *Technical Lead* WSO2 Inc. http://wso2.com/ - Lean . Enterprise . Middleware email : rush...@wso2.com mobile : +94772310855 ___ 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
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.com wrote: 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.com wrote: 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.comwrote: 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 org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124) 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
Re: [Dev] WSO2 ESB Connector Store Icons
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.com wrote: 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 . 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. -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- 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:
Re: [Dev] WSO2 ESB Connector Store Icons
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.com wrote: 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 . 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. -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com -- Dushan
[Dev] [APPFAC-1862] No indexed columns present error from social component at server startup
Hi Manjula, I can remember we got the same issue early. Since we are moving to the toolbox based stream-def, KS, secondary index creation from next version of the social framework probably we can get rid of these type of issues in future. But I'm not sure whether we can use this immediately since we need to solve toolbox hot-deployment issue discussed here[1]. Could you please let me know whether you see this[2] consistently or only once during the initial server start-up? [1] [DEV]Creating column families though a simple toolbox [2] https://wso2.org/jira/browse/APPFAC-1862 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
[Dev] Invitation: Global cluster cache invalidation code review @ Tue May 13, 2014 3pm - 4pm (am...@wso2.com)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20140513T093000Z DTEND:20140513T103000Z DTSTAMP:20140513T052046Z ORGANIZER;CN=Amal Gunatilake:mailto:am...@wso2.com UID:mc3elqsi06c4de4nrlhdgk5...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=Amal Gunatilake;X-NUM-GUESTS=0:mailto:am...@wso2.com ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE;C N=LK 1st Floor Meeting Room;X-NUM-GUESTS=0:mailto:wso2.com_2d38333735373634 32333...@resource.calendar.google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Sagara Gunathunga;X-NUM-GUESTS=0:mailto:sag...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Afkham Azeez;X-NUM-GUESTS=0:mailto:az...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Subash Chaturanga;X-NUM-GUESTS=0:mailto:sub...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Shazni Nazir;X-NUM-GUESTS=0:mailto:sha...@wso2.com CREATED:20140513T050714Z DESCRIPTION:Global cluster cache invalidation code review\nView your event at http://www.google.com/calendar/event?action=VIEWeid=bWMzZWxxc2kwNmM0ZGU 0bnJsaGRnazV1dDAgZGV2QHdzbzIub3Jntok=MTQjYW1hbGdAd3NvMi5jb21jNzI2Yjc3MjliZ mJhMjM2MTY3MDM4NmQ3NTAyNTJiYmYyN2VhNmRkctz=Asia/Colombohl=en. LAST-MODIFIED:20140513T052046Z LOCATION:LK 1st Floor Meeting Room SEQUENCE:1 STATUS:CONFIRMED SUMMARY:Global cluster cache invalidation code review TRANSP:TRANSPARENT END:VEVENT END:VCALENDAR invite.ics Description: application/ics ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APPFAC-1862] No indexed columns present error from social component at server startup
Hi Udara, We see this issues at server start up intermittently. But the only solution is to delete the Cassandra database and keep on starting until it works. And can you please confirm if we can add this module to turing branch? We need to get AppFactory pack with this bundle. thank you. On Tue, May 13, 2014 at 10:19 AM, Udara Rathnayake uda...@wso2.com wrote: Hi Manjula, I can remember we got the same issue early. Since we are moving to the toolbox based stream-def, KS, secondary index creation from next version of the social framework probably we can get rid of these type of issues in future. But I'm not sure whether we can use this immediately since we need to solve toolbox hot-deployment issue discussed here[1]. Could you please let me know whether you see this[2] consistently or only once during the initial server start-up? [1] [DEV]Creating column families though a simple toolbox [2] https://wso2.org/jira/browse/APPFAC-1862 Regards, UdaraR -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987 ___ 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
On Tue, May 13, 2014 at 11:03 AM, Gayan Yalpathwala gay...@wso2.com wrote: 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 org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at
