Re: [Dev] Why we can't support multiple versioned car files.
yes, thats exactly what i'm asking. Forget about axis2 services. Even multiple versioned .car files (with manually edited axis2 services) are not working. --Pradeep On Fri, May 24, 2013 at 6:54 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: We already have the building blocks to support CApp versioning, but the thing is, not every artifacts can support versioning as of now. For example, we can add version to a webapp by changing its context (this is what Dev-Studio does), but for an axis2 service, this is not possible unless we change the service name it self with the version. Thanks, Kishanthan On Fri, May 24, 2013 at 7:35 AM, Pradeep Fernando prad...@wso2.comwrote: Hi, Adding versioning support to third party hosting artifacts can be tricky (eg: axis2). However, AFAIK, we don't support multiple versioned .car files as well. We sure can support it IMHO. In the future, during an introduction of new hosting engine to the platform, we have to figure out, at least - tenancy model - versioning model thanks, --Pradeep ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ** -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Urgent][API Manager] Issue when we deploy API to other server
On Thu, May 23, 2013 at 5:37 AM, Afkham Azeez az...@wso2.com wrote: On Thu, May 23, 2013 at 4:05 AM, Shariq Muhammed sha...@wso2.com wrote: On Sun, May 19, 2013 at 8:46 PM, Afkham Azeez az...@wso2.com wrote: On Mon, May 20, 2013 at 8:04 AM, Supun Malinga sup...@wso2.com wrote: Hi Guys, For C5 I think we need to permanently fix the CC related issues. This includes both the API related issues we have and the user level issues that pops up time to time like this. Please make sure we achieve that. This can't wait until C5. It has to be fixed ASAP. Yup true, from what I have seen at time ThreadLocal CC works as expected and other times CC based on MessageContext seems to be the right way. Having toiled with the CC API from time to time, I still am not always quite sure when to use what or if its the correct/expected behavior etc .! During the last Stratos release Sinthuja did some changes to give priority to ThreadLocal CC (after discussing with the team of course) but we ultimately had to revert it because certain aspects were broken (login with Basic Auth - discussion at - [Dev] UserRegistry sends null to JDBCAuthorizationManager). Bottom line is the CC API is not as robust as we would like it to be, we should put some thought into getting the API cleaned up. One major issue when it comes tinkering with CC API is that its crosscutting nature and some issue showing up only for very specific cases. Anyway we need to give it some thought, in C5 at the very least. What I'd like to see is all APIs which create the CC using MessageContext, AxisConfig etc. being removed, and the only way to get the CC should be through the Thread context. Any running thread should have a valid CC associated with it at all times. +1. what is the target release? 4.2 or 4.3 :) --Pradeep ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Urgent][API Manager] Issue when we deploy API to other server
Hi Azeez, Shall we have a review session on CC again ? (like we did in the last time). I would like to get rid of all the msgContext / session based CC retrievals. --Pradeep On Fri, May 24, 2013 at 8:15 AM, Pradeep Fernando prad...@wso2.com wrote: On Thu, May 23, 2013 at 5:37 AM, Afkham Azeez az...@wso2.com wrote: On Thu, May 23, 2013 at 4:05 AM, Shariq Muhammed sha...@wso2.com wrote: On Sun, May 19, 2013 at 8:46 PM, Afkham Azeez az...@wso2.com wrote: On Mon, May 20, 2013 at 8:04 AM, Supun Malinga sup...@wso2.com wrote: Hi Guys, For C5 I think we need to permanently fix the CC related issues. This includes both the API related issues we have and the user level issues that pops up time to time like this. Please make sure we achieve that. This can't wait until C5. It has to be fixed ASAP. Yup true, from what I have seen at time ThreadLocal CC works as expected and other times CC based on MessageContext seems to be the right way. Having toiled with the CC API from time to time, I still am not always quite sure when to use what or if its the correct/expected behavior etc .! During the last Stratos release Sinthuja did some changes to give priority to ThreadLocal CC (after discussing with the team of course) but we ultimately had to revert it because certain aspects were broken (login with Basic Auth - discussion at - [Dev] UserRegistry sends null to JDBCAuthorizationManager). Bottom line is the CC API is not as robust as we would like it to be, we should put some thought into getting the API cleaned up. One major issue when it comes tinkering with CC API is that its crosscutting nature and some issue showing up only for very specific cases. Anyway we need to give it some thought, in C5 at the very least. What I'd like to see is all APIs which create the CC using MessageContext, AxisConfig etc. being removed, and the only way to get the CC should be through the Thread context. Any running thread should have a valid CC associated with it at all times. +1. what is the target release? 4.2 or 4.3 :) --Pradeep -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Urgent][API Manager] Issue when we deploy API to other server
On Fri, May 24, 2013 at 12:49 PM, Pradeep Fernando prad...@wso2.com wrote: Hi Azeez, Shall we have a review session on CC again ? (like we did in the last time). I would like to get rid of all the msgContext / session based CC retrievals. Yes --Pradeep On Fri, May 24, 2013 at 8:15 AM, Pradeep Fernando prad...@wso2.comwrote: On Thu, May 23, 2013 at 5:37 AM, Afkham Azeez az...@wso2.com wrote: On Thu, May 23, 2013 at 4:05 AM, Shariq Muhammed sha...@wso2.comwrote: On Sun, May 19, 2013 at 8:46 PM, Afkham Azeez az...@wso2.com wrote: On Mon, May 20, 2013 at 8:04 AM, Supun Malinga sup...@wso2.comwrote: Hi Guys, For C5 I think we need to permanently fix the CC related issues. This includes both the API related issues we have and the user level issues that pops up time to time like this. Please make sure we achieve that. This can't wait until C5. It has to be fixed ASAP. Yup true, from what I have seen at time ThreadLocal CC works as expected and other times CC based on MessageContext seems to be the right way. Having toiled with the CC API from time to time, I still am not always quite sure when to use what or if its the correct/expected behavior etc .! During the last Stratos release Sinthuja did some changes to give priority to ThreadLocal CC (after discussing with the team of course) but we ultimately had to revert it because certain aspects were broken (login with Basic Auth - discussion at - [Dev] UserRegistry sends null to JDBCAuthorizationManager). Bottom line is the CC API is not as robust as we would like it to be, we should put some thought into getting the API cleaned up. One major issue when it comes tinkering with CC API is that its crosscutting nature and some issue showing up only for very specific cases. Anyway we need to give it some thought, in C5 at the very least. What I'd like to see is all APIs which create the CC using MessageContext, AxisConfig etc. being removed, and the only way to get the CC should be through the Thread context. Any running thread should have a valid CC associated with it at all times. +1. what is the target release? 4.2 or 4.3 :) --Pradeep -- *Pradeep Fernando* Member, Management Committee - Platform Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662 -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why we can't support multiple versioned car files.
On Fri, May 24, 2013 at 12:37 PM, Pradeep Fernando prad...@wso2.com wrote:
yes, thats exactly what i'm asking. Forget about axis2 services. Even
multiple versioned .car files (with manually edited axis2 services) are not
working.
Yes, currently there are two issues arising when deploying CApps with
different versions.
1. When deploying the second CApp (new) with different version, it is
throwing *Carbon Application : AppServerCAPP already exists. Two
applications can't have the same Id. Deployment aborted.*
This is because of a bug in checking the CApp id. It should be checked
against the version aswell. I just tried this. This can be fixed.
2. If we manually edit/rename an old CApp and deploy it with different
version, it is throwing a different error.
[2013-05-24 10:53:16,590] ERROR
{org.wso2.carbon.application.deployer.internal.ApplicationManager} - Error
occurred while deploying Carbon Application
org.wso2.carbon.CarbonException: Error while extracting Carbon Application
: AppServerCAPP_2.0.0.car
at
org.wso2.carbon.application.deployer.AppDeployerUtils.extractCarbonApp(AppDeployerUtils.java:441)
at
org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:196)
at
org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:71)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
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:67)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:112)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.FileNotFoundException:
/home/kicha/checkouts/wso2/carbon/platform/trunk/products/as/modules/distribution/target/wso2as-5.2.0-SNAPSHOT/tmp/carbonapps/1369372899787AppServerCAPP_2.0.0.car/WebAppSample_2.0.0/artifact.xml
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.init(FileOutputStream.java:194)
at java.io.FileOutputStream.init(FileOutputStream.java:84)
at
org.wso2.carbon.application.deployer.AppDeployerUtils.extract(AppDeployerUtils.java:668)
at
org.wso2.carbon.application.deployer.AppDeployerUtils.extractCarbonApp(AppDeployerUtils.java:439)
... 21 more
This is because, even-though we manually edit the CApp, at code level, it
is getting treated as the old CApp. When extracting the file, the zip file
entries listed
in AppDeployerUtils#extract method are the old Capp's entries. This is
already reported [1] as-well.
Thanks,
Kishanthan.
[1] https://wso2.org/jira/browse/CARBON-13599
--Pradeep
On Fri, May 24, 2013 at 6:54 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
We already have the building blocks to support CApp versioning, but the
thing is, not every artifacts can support versioning as of now. For
example, we can add version to a webapp by changing its context (this is
what Dev-Studio does), but for an axis2 service, this is not
possible unless we change the service name it self with the version.
Thanks,
Kishanthan
On Fri, May 24, 2013 at 7:35 AM, Pradeep Fernando prad...@wso2.comwrote:
Hi,
Adding versioning support to third party hosting artifacts can be tricky
(eg: axis2). However, AFAIK, we don't support multiple versioned .car files
as well. We sure can support it IMHO.
In the future, during an introduction of new hosting engine to the
platform, we have to figure out, at least
- tenancy model
- versioning model
thanks,
--Pradeep
[Dev] Two component location for AppFactory in 4.1.0 branch
Hi all What is the correct one we should use and why do we maintain two locations ?? [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/appfac/ [2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/appfactory/ Thanks Ajith -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Why we can't support multiple versioned car files.
Thanks Kishanthan. :)
Harshana shall we work together and fix this for versioned supported
artifacts. Kishanthans , response suggest that this is a carbon level fix.
I would love to see a versioned api + versioned capp working sample.
Axis2 is a seperate thing. May be we should figure out a way to support
versioning at the deployer level. We have integrated number of runtimes to
the platform over the years. We can't add versioning support to each of
those run times.
--Pradeep
sent from my phone
On May 24, 2013 3:20 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
On Fri, May 24, 2013 at 12:37 PM, Pradeep Fernando prad...@wso2.comwrote:
yes, thats exactly what i'm asking. Forget about axis2 services. Even
multiple versioned .car files (with manually edited axis2 services) are not
working.
Yes, currently there are two issues arising when deploying CApps with
different versions.
1. When deploying the second CApp (new) with different version, it is
throwing *Carbon Application : AppServerCAPP already exists. Two
applications can't have the same Id. Deployment aborted.*
This is because of a bug in checking the CApp id. It should be checked
against the version aswell. I just tried this. This can be fixed.
2. If we manually edit/rename an old CApp and deploy it with different
version, it is throwing a different error.
[2013-05-24 10:53:16,590] ERROR
{org.wso2.carbon.application.deployer.internal.ApplicationManager} - Error
occurred while deploying Carbon Application
org.wso2.carbon.CarbonException: Error while extracting Carbon Application
: AppServerCAPP_2.0.0.car
at
org.wso2.carbon.application.deployer.AppDeployerUtils.extractCarbonApp(AppDeployerUtils.java:441)
at
org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:196)
at
org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:71)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
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:67)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:112)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.FileNotFoundException:
/home/kicha/checkouts/wso2/carbon/platform/trunk/products/as/modules/distribution/target/wso2as-5.2.0-SNAPSHOT/tmp/carbonapps/1369372899787AppServerCAPP_2.0.0.car/WebAppSample_2.0.0/artifact.xml
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.init(FileOutputStream.java:194)
at java.io.FileOutputStream.init(FileOutputStream.java:84)
at
org.wso2.carbon.application.deployer.AppDeployerUtils.extract(AppDeployerUtils.java:668)
at
org.wso2.carbon.application.deployer.AppDeployerUtils.extractCarbonApp(AppDeployerUtils.java:439)
... 21 more
This is because, even-though we manually edit the CApp, at code level, it
is getting treated as the old CApp. When extracting the file, the zip file
entries listed
in AppDeployerUtils#extract method are the old Capp's entries. This is
already reported [1] as-well.
Thanks,
Kishanthan.
[1] https://wso2.org/jira/browse/CARBON-13599
--Pradeep
On Fri, May 24, 2013 at 6:54 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
We already have the building blocks to support CApp versioning, but the
thing is, not every artifacts can support versioning as of now. For
example, we can add version to a webapp
Re: [Dev] Need occasional DepSync polling or depsync message replay
On Thu, May 23, 2013 at 2:05 PM, Afkham Azeez az...@wso2.com wrote: There is no guarantee that the cluster message will be reliably delivered to all members. For instance, due to a momentary network delay or delay in the node, other members may detect that a member has left, but in reality, that member may be still running. If a cluster message, such as a DepSync message is sent in such a scenario, the node will not receive that message, and may never update its deployment repo. We could implement one of the following solutions; 1. For selected cluster messages, we could replay them if a new member becomes available. We can't blindly replay all messages, but replaying the depsync message will cause no harm because the depsync operation is idempotent 2. For depsync, we can have periodic polling, but the polling interval should vary from about 1 minute to 5 minutes.r For depsynch problems there was a suggestion to implement svn polling at workers. i.e worker periodically try to check out the code. is this an in efficient method? thanks, Amila. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Build Fail with compilation errors on [Governance - Notifications User Interface]
FYI, this is fixed. On Wed, May 22, 2013 at 2:22 PM, Ananda Manoj Kumara ma...@wso2.com wrote: Hi, When I tried to build component platform/trunk/components I get the following compilations on Governance - Notifications User Interface component. Please check [INFO] BUILD FAILURE [INFO] [INFO] Total time: 6:38.965s [INFO] Finished at: Wed May 22 09:28:02 IST 2013 [INFO] Final Memory: 1067M/1704M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project org.wso2.carbon.governance.notifications.ui: Compilation failure: Compilation failure: [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[134,12] cannot find symbol [ERROR] symbol : class GetAllRolesNamesUserAdminExceptionException [ERROR] location: class org.wso2.carbon.governance.notifications.ui.worklist.HumanTaskClient [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[135,12] cannot find symbol [ERROR] symbol : class GetUserStoreInfoUserAdminExceptionException [ERROR] location: class org.wso2.carbon.governance.notifications.ui.worklist.HumanTaskClient [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[136,12] cannot find symbol [ERROR] symbol : class GetRolesOfCurrentUserUserAdminExceptionException [ERROR] location: class org.wso2.carbon.governance.notifications.ui.worklist.HumanTaskClient [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[134,12] cannot find symbol [ERROR] symbol : class GetAllRolesNamesUserAdminExceptionException [ERROR] location: class org.wso2.carbon.governance.notifications.ui.worklist.HumanTaskClient [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[135,12] cannot find symbol [ERROR] symbol : class GetUserStoreInfoUserAdminExceptionException [ERROR] location: class org.wso2.carbon.governance.notifications.ui.worklist.HumanTaskClient [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[136,12] cannot find symbol [ERROR] symbol : class GetRolesOfCurrentUserUserAdminExceptionException [ERROR] location: class org.wso2.carbon.governance.notifications.ui.worklist.HumanTaskClient [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[149,56] void cannot be dereferenced [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[154,42] getAllRolesNames(java.lang.String,int) in org.wso2.carbon.user.mgt.stub.UserAdminStub cannot be applied to () [ERROR] /media/Carbon/carbon/platform/trunk/components/governance/org.wso2.carbon.governance.notifications.ui/src/main/java/org/wso2/carbon/governance/notifications/ui/worklist/HumanTaskClient.java:[158,52] void cannot be dereferenced Thanks, Manoj Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188 -- Vijitha Kumara Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: viji...@wso2.com Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need occasional DepSync polling or depsync message replay
On Fri, May 24, 2013 at 9:53 PM, Amila Suriarachchi am...@wso2.com wrote: On Thu, May 23, 2013 at 2:05 PM, Afkham Azeez az...@wso2.com wrote: There is no guarantee that the cluster message will be reliably delivered to all members. For instance, due to a momentary network delay or delay in the node, other members may detect that a member has left, but in reality, that member may be still running. If a cluster message, such as a DepSync message is sent in such a scenario, the node will not receive that message, and may never update its deployment repo. We could implement one of the following solutions; 1. For selected cluster messages, we could replay them if a new member becomes available. We can't blindly replay all messages, but replaying the depsync message will cause no harm because the depsync operation is idempotent 2. For depsync, we can have periodic polling, but the polling interval should vary from about 1 minute to 5 minutes.r How about changing polling interval according to the number of nodes in the cluster? For a basic example we can change the polling time t, 2t, 3t as cluster has 1 node, 2 nodes, 3 nodes etc.. If any node found a change in the repository, it send a cluster message. In this way it can be guaranteed that sync is happens in at least in O(n.t) time after a change in repo, where n=number of nodes in the cluster and t=polling time defined by user. Then this can be expanded by making more ordered/organized update by nodes. In that case the we can reduced that time to O(t). For depsynch problems there was a suggestion to implement svn polling at workers. i.e worker periodically try to check out the code. is this an in efficient method? thanks, Amila. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Regards, * Darshana Gunawardana *Software Engineer WSO2 Inc.; http://wso2.com* E-mail: darsh...@wso2.com **Mobile: +94718566859 *Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Need occasional DepSync polling or depsync message replay
On Fri, May 24, 2013 at 9:53 PM, Amila Suriarachchi am...@wso2.com wrote: On Thu, May 23, 2013 at 2:05 PM, Afkham Azeez az...@wso2.com wrote: There is no guarantee that the cluster message will be reliably delivered to all members. For instance, due to a momentary network delay or delay in the node, other members may detect that a member has left, but in reality, that member may be still running. If a cluster message, such as a DepSync message is sent in such a scenario, the node will not receive that message, and may never update its deployment repo. We could implement one of the following solutions; 1. For selected cluster messages, we could replay them if a new member becomes available. We can't blindly replay all messages, but replaying the depsync message will cause no harm because the depsync operation is idempotent 2. For depsync, we can have periodic polling, but the polling interval should vary from about 1 minute to 5 minutes.r For depsynch problems there was a suggestion to implement svn polling at workers. i.e worker periodically try to check out the code. is this an in efficient method? Once a system is in production, I doubt there'll be any regular updates to its artifacts. Therefore IMO it would be an unnecessary overhead to do periodic polling. thanks, Amila. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Amila Suriarachchi* Software Architect WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 71 3082805 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Nuwan Dias Member, Management Committee - Solutions Technology Group Senior Software Engineer - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Dev Studio ESB Mediators in Palette should be in alphabatical order in each catgory
Hi Dev Folks, $subject, it really difficult to find mediators by scrolling here and there should be ordered..please make this as note cheers Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Dev Studio ESB Mediators in Palette should be in alphabatical order in each catgory
Hi Dushan, Yes there is an issue with palette to find relevant mediator quickly. There is a public jira at [1] which describes the same issue. Fix will be available in next releases. Thanks, Viraj. [1] - https://wso2.org/jira/browse/TOOLS-1323 On Sat, May 25, 2013 at 8:32 AM, Dushan Abeyruwan dus...@wso2.com wrote: Hi Dev Folks, $subject, it really difficult to find mediators by scrolling here and there should be ordered..please make this as note cheers Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Patch Release 4.1.3 Build Error
Hi, I'm getting below compilation failure when building from patch release[4.1.3] pom after taking a full svn up of platform. [ERROR] Failed to execute goal on project juddi-core: Could not resolve dependencies for project org.apache.juddi:juddi-core:bundle:3.1.5.wso2v1: Failure to find org.apache.juddi:uddi-tck-base:jar:3.1.5.wso2v1 in http://download.java.net/maven/2 was cached in the local repository, resolution will not be reattempted until the update interval of maven2-repository.dev.java.net has elapsed or updates are forced - [Help 1] Regards, Chandana -- *Chandana Napagoda* Senior Software Engineer WSO2 Inc. - http://wso2.org *Email : chand...@wso2.com **Mobile : +94718169299* *Blog :http://cnapagoda.blogspot.com * ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Two component location for AppFactory in 4.1.0 branch
Hi Ajith, We are using [1] . On Fri, May 24, 2013 at 3:47 PM, Ajith Vitharana aji...@wso2.com wrote: Hi all What is the correct one we should use and why do we maintain two locations ?? [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/appfac/ [2] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/appfactory/ Thanks Ajith -- Ajith Vitharana. Senior Software Engineer, Member,Management Committee, Integration Technologies. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Asanka Dissanayake Software Engineer* *WSO2 Inc. - lean . enterprise . middleware | wso2.com* * email: asan...@wso2.com ruch...@wso2.com, blog: cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com mobile: +94 71 8373821* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
