Re: [Dev] Kernel Commits required to patch0002
Hi, I applied [1]. But on [2] you have added new public method called removeObserver so this will change the API. Need to check this with the team. [1] https://wso2.org/jira/browse/CARBON-14545 [2] https://wso2.org/jira/browse/CARBON-14546 Thanks, Manoj Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188 On Wed, Nov 20, 2013 at 10:10 AM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, Please apply the patches attached to below Jiras. [1] https://wso2.org/jira/browse/CARBON-14545 [2] https://wso2.org/jira/browse/CARBON-14546 Thanks, Lakmali -- Lakmali Baminiwatta 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] Kernel Commits required to patch0002
Hi Manoj, On 20 November 2013 14:58, Manoj Kumara ma...@wso2.com wrote: Hi, I applied [1]. Thanks Manoj. But on [2] you have added new public method called removeObserver so this will change the API. Need to check this with the team. Sure. FYI , This added method is only reffered inside kernel [1]. So this will not cause build issues in platform level. Thanks, Lakmali [1] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.2.0/dependencies/transports/1.1.0-wso2v9/modules/base/src/main/java/org/apache/axis2/transport/base/tracker/AxisServiceTracker.java [1] https://wso2.org/jira/browse/CARBON-14545 [2] https://wso2.org/jira/browse/CARBON-14546 Thanks, Manoj Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188 On Wed, Nov 20, 2013 at 10:10 AM, Lakmali Baminiwatta lakm...@wso2.comwrote: Hi, Please apply the patches attached to below Jiras. [1] https://wso2.org/jira/browse/CARBON-14545 [2] https://wso2.org/jira/browse/CARBON-14546 Thanks, Lakmali -- Lakmali Baminiwatta Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware mobile: +94 71 2335936 blog : lakmali.com -- Lakmali Baminiwatta 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] Active Development in Trunk
Hi Lasantha, Trunk is not updated with fixes that the teams have done for the Turing release. If you are going to work on the platform trunk, then you guys have to first update the trunk with the latest changes. Platform trunk should depend on the Kernel 4.2.0(with the latest patch). Btw, can you explain why you guys need to work on the trunk? Thanks, Sameera. On Tue, Nov 19, 2013 at 4:44 PM, Lasantha Fernando lasan...@wso2.comwrote: Hi devs, How should we proceed with active development after a product gets released? Currently, the kernel of the trunk is in version 5.0.0-SNAPSHOT and active development is not happening for 4.2.0-SNAPSHOT AFAIK. However, most components in trunk still point to a 4.2.0-SNAPSHOT version of the kernel. Also, I don't think product teams has had time to integrate changes back to trunk after developing on turing branch. So the components in the trunk itself does not have the latest code. So should we develop continue development on the turing branch itself? Ideas/thoughts? Thanks, Lasantha -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ESB 4.8.0 Worker/ Manager setup - Observed ERROR {org.wso2.carbon.caching.impl.CacheCleanupTask} - Error occurred while running CacheCleanupTask {org.wso2.carbon.caching.impl.CacheCleanupTask}
Hi,
We have ESB 4.8.0 worker/ manager setup with one worker running on
linux box and another worker running on windows machine:
Observed following error time to time and disconnected windows server
from the domain.
TID: [0] [ESB] [2013-11-20 16:34:42,035] ERROR
{org.wso2.carbon.caching.impl.CacheCleanupTask} - Error occurred
while running CacheCleanupTask
{org.wso2.carbon.caching.impl.CacheCleanupTask}
com.hazelcast.core.OperationTimeoutException: No response for 12
ms. Aborting invocation! InvocationFuture{invocation=InvocationImpl{
serviceName='hz:impl:mapService',
op=com.hazelcast.map.operation.MapEntrySetOperation@4eb884e3,
partitionId=0, replicaIndex=0, tryCount=250, tryPauseMillis=500,
invokeCount=1, callTimeout=6, target=Address[10.10.10.234]:4300},
done=false}
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.waitForResponse(InvocationImpl.java:376)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:291)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:283)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnPartitions(OperationServiceImpl.java:495)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnAllPartitions(OperationServiceImpl.java:424)
at
com.hazelcast.map.proxy.MapProxySupport.entrySetInternal(MapProxySupport.java:564)
at com.hazelcast.map.proxy.MapProxyImpl.entrySet(MapProxyImpl.java:410)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.entrySet(HazelcastDistributedMapProvider.java:167)
at org.wso2.carbon.caching.impl.CacheImpl.syncCaches(CacheImpl.java:236)
at org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
at -- End remote and begin local stack-trace --.(Unknown Source)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.resolveResponse(InvocationImpl.java:405)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:291)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:283)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnPartitions(OperationServiceImpl.java:495)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnAllPartitions(OperationServiceImpl.java:424)
at
com.hazelcast.map.proxy.MapProxySupport.entrySetInternal(MapProxySupport.java:564)
at com.hazelcast.map.proxy.MapProxyImpl.entrySet(MapProxyImpl.java:410)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.entrySet(HazelcastDistributedMapProvider.java:167)
at org.wso2.carbon.caching.impl.CacheImpl.syncCaches(CacheImpl.java:236)
at org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [ESB] [2013-11-20 16:39:22,057] ERROR
{org.wso2.carbon.caching.impl.CacheCleanupTask} - Error occurred
while running CacheCleanupTask
{org.wso2.carbon.caching.impl.CacheCleanupTask}
com.hazelcast.core.OperationTimeoutException: No response for 12
ms. Aborting invocation! InvocationFuture{invocation=InvocationImpl{
serviceName='hz:impl:mapService',
op=com.hazelcast.map.operation.MapEntrySetOperation@459408e3,
partitionId=0, replicaIndex=0, tryCount=250, tryPauseMillis=500,
invokeCount=1, callTimeout=6, target=Address[10.10.10.234]:4300},
done=false}
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.waitForResponse(InvocationImpl.java:376)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:291)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:283)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnPartitions(OperationServiceImpl.java:495)
at
[Dev] 回复: Re: When the source of DSS v.3.1.0 will be released?
Hi : Thank you very much! It works! stevegyc 发件人： Chanika Geeganage 发送时间： 2013-11-20 14:46 收件人： stevegyc 抄送： dev 主题： Re: Re: [Dev] When the source of DSS v.3.1.0 will be released? Hi, It is because the pom.xml located in tags/turing-chunk01/products is not in your checkout. Therefore you have to take a checkout from [1] and then build the product dss 3.1.0. [1] https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk01/products/ Thanks On Wed, Nov 20, 2013 at 8:02 AM, stevegyc steve...@163.com wrote: Hi : I have built the source of DSS 3.1.0, but some errors occur as following: [INFO] [INFO] Reactor Summary: [INFO] [INFO] WSO2 DataServices Parent .. SUCCESS [2.782s] [INFO] WSO2 DataServices Styles Parent ... SUCCESS [0.059s] [INFO] DataServices UI styles SUCCESS [40.970s] [INFO] WSO2 Stratos DSS - UI styles .. SUCCESS [4.191s] [INFO] WSO2 DataServices Samples Parent .. SUCCESS [0.861s] [INFO] DataServices Clients .. SUCCESS [1:04.394s] [INFO] WSO2 DataServices Features Parent . SUCCESS [0.039s] [INFO] WSO2 DataServices - Style Features SUCCESS [7.961s] [INFO] WSO2 Stratos DSS - Style Features . SUCCESS [0.816s] [INFO] WSO2 Stratos DSS - Login User Interface ... SUCCESS [14.569s] [INFO] WSO2 Stratos DSS - Deployment Features SUCCESS [1.211s] [INFO] WSO2 Stratos Data Services Server - Dashboard UI .. SUCCESS [6.013s] [INFO] WSO2 Stratos DSS - Dashboard UI Features .. SUCCESS [1.550s] [INFO] WSO2 Stratos DSS - Features Aggregator Module . SUCCESS [0.064s] [INFO] WSO2 DataServices - DataServices Profile Generation SUCCESS [7:31.169s] [INFO] WSO2 Data Services Server Distribution FAILURE [6:16.031s] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 16:21.132s [INFO] Finished at: Wed Nov 20 10:20:12 CST 2013 [INFO] Final Memory: 29M/81M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (dist) on project wso2dss: Failed to create assembly: File to filter not found: D:\project\wso2\dss3.1.0_src\modules\distribution\..\..\..\..\pom.xml (系统找不到指定的文件。) - [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/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :wso2dss Does anyone know about it? stevegyc From: Chanika Geeganage Date: 2013-11-19 16:39 To: stevegyc CC: dev Subject: Re: [Dev] When the source of DSS v.3.1.0 will be released? Hi, You can find the svn location of DSS 3.1.0 from [1] [1] https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk01/products/dss/3.1.0/ Thanks On Tue, Nov 19, 2013 at 12:49 PM, stevegyc steve...@163.com wrote: Hi: Does Anyone know when the source of DSS v.3.1.0 will be released? stevegyc ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com -- Best Regards.. Chanika Geeganage Software Engineer WSO2, Inc.; http://wso2.com___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue in deployment synchronization in ESB 4.8.0 alpha cluster setup when updating a sequence in GIT and SVN
Following exception can be seen in worker nodes when updating the sequence. Issue is reported in [1]. Pls have a look. [1] https://wso2.org/jira/browse/ESBJAVA-2721T In GIT : [2013-11-20 19:13:08,648] ERROR - AbstractSynapseArtifactDeployer Deployment of synapse artifact failed. Error reading /home/ushani/Downloads/Products/ESB/4.8.0_Release/18_Nov/wrk1/wso2esb-4.8.0/repository/deployment/server/synapse-configs/default/sequences/seq1.xml : Sequence Deployment from the file : /home/ushani/Downloads/Products/ESB/4.8.0_Release/18_Nov/wrk1/wso2esb-4.8.0/repository/deployment/server/synapse-configs/default/sequences/seq1.xml : Failed. org.apache.axis2.deployment.DeploymentException: Sequence Deployment from the file : /home/ushani/Downloads/Products/ESB/4.8.0_Release/18_Nov/wrk1/wso2esb-4.8.0/repository/deployment/server/synapse-configs/default/sequences/seq1.xml : Failed. at org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:228) 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:79) at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124) 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: org.apache.synapse.deployers.SynapseArtifactDeploymentException: Sequence Deployment from the file : /home/ushani/Downloads/Products/ESB/4.8.0_Release/18_Nov/wrk1/wso2esb-4.8.0/repository/deployment/server/synapse-configs/default/sequences/seq1.xml : Failed. at org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.handleSynapseArtifactDeploymentError(AbstractSynapseArtifactDeployer.java:503) at org.apache.synapse.deployers.SequenceDeployer.deploySynapseArtifact(SequenceDeployer.java:83) at org.wso2.carbon.sequences.SequenceDeploymentInterceptor.deploySynapseArtifact(SequenceDeploymentInterceptor.java:42) at org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:221) ... 19 more Caused by: org.apache.synapse.SynapseException: Duplicate sequence definition for key : seq1 at org.apache.synapse.config.SynapseConfiguration.handleException(SynapseConfiguration.java:1516) at org.apache.synapse.config.SynapseConfiguration.assertAlreadyExists(SynapseConfiguration.java:1830) at org.apache.synapse.config.SynapseConfiguration.addSequence(SynapseConfiguration.java:217) at org.apache.synapse.deployers.SequenceDeployer.deploySynapseArtifact(SequenceDeployer.java:71) ... 21 more In SVN : [2013-11-20 19:21:27,414] ERROR - SynapseConfiguration Duplicate sequence definition for key : fault [2013-11-20 19:21:27,430] ERROR - SequenceDeploymentInterceptor Sequence Deployment from the file : D:\ESB-480\Wrk1\wso2esb-4.8.0\ repository\deployment\server\synapse-configs\default\sequences\fault.xml : Failed. org.apache.synapse.SynapseException: Duplicate sequence definition for key : fault at org.apache.synapse.config.SynapseConfiguration.handleException(SynapseConfiguration.java:1516) at org.apache.synapse.config.SynapseConfiguration.assertAlreadyExists(SynapseConfiguration.java:1830) at org.apache.synapse.config.SynapseConfiguration.addSequence(SynapseConfiguration.java:217) at org.apache.synapse.deployers.SequenceDeployer.deploySynapseArtifact(SequenceDeployer.java:71) at
[Dev] [AF][Devs Integration][STS] Server cant process the security headers when accessing the STS service as tenant.
Hi I am trying to access the sts service using a STS client which is deployed inside a tenant. There I am having an issue that server cannot read the security headers thats set by the client. Any idea why this could happen? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AF][Devs Integration][STS] Server cant process the security headers when accessing the STS service as tenant.
What is the exception you see..? We basically deploy different instances of STS in each tenant.. Thanks regards, -Prabath On Wed, Nov 20, 2013 at 8:19 PM, Danushka Fernando danush...@wso2.comwrote: Hi I am trying to access the sts service using a STS client which is deployed inside a tenant. There I am having an issue that server cannot read the security headers thats set by the client. Any idea why this could happen? Thanks Regards Danushka Fernando Software Engineer WSO2 inc. http://wso2.com/ Mobile : +94716332729 -- Thanks Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Active Development in Trunk
Hi, On Wed, Nov 20, 2013 at 4:07 PM, Sameera Jayasoma same...@wso2.com wrote: Hi Lasantha, Trunk is not updated with fixes that the teams have done for the Turing release. If you are going to work on the platform trunk, then you guys have to first update the trunk with the latest changes. Yes, We have updated the necessary CEP changes to the trunk as soon as after the release... Platform trunk should depend on the Kernel 4.2.0(with the latest patch). Btw, can you explain why you guys need to work on the trunk? We have thought that after the release process, we need to merge the code changes to trunk and continue active development on trunk.. Since we have not decided a specific date for out next release, we thought, better to start the development (not adding features) on trunk since we are doing some bug fixes (clearing carbon jira) and committing some patches which are contributed by the community.. Is there any wrong in our process, Please correct us if anything wrong... Thanks Regards, Mohan Thanks, Sameera. On Tue, Nov 19, 2013 at 4:44 PM, Lasantha Fernando lasan...@wso2.comwrote: Hi devs, How should we proceed with active development after a product gets released? Currently, the kernel of the trunk is in version 5.0.0-SNAPSHOT and active development is not happening for 4.2.0-SNAPSHOT AFAIK. However, most components in trunk still point to a 4.2.0-SNAPSHOT version of the kernel. Also, I don't think product teams has had time to integrate changes back to trunk after developing on turing branch. So the components in the trunk itself does not have the latest code. So should we develop continue development on the turing branch itself? Ideas/thoughts? Thanks, Lasantha -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 -- Sameera Jayasoma, Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com http://wso2.com * *lean.enterprise.middleware.* email: mo...@wso2.com phone:(+94) 771117673 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] What does this file? CEP Activity Search Report.jrxml
ok, Thanks !! Mohan Regards, Andrés Gómez -- View this message in context: http://wso2-oxygen-tank.10903.n7.nabble.com/Dev-What-does-this-file-CEP-Activity-Search-Report-jrxml-tp88645p88687.html Sent from the WSO2 Development mailing list archive at Nabble.com. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Developer Studio 3.3.0 Alpha 3 Released!
What is the plan to test all mediators for basic functionality for 3.3.0? I understand that some mediators were badly broken in 3.2.0 release e.g. XACML. Can we make use of the auto test framework to ensure that there are no absolute blockers in any mediator out of the full mediator lot. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Mon, Nov 18, 2013 at 3:49 PM, Asanka Sanjeewa asan...@wso2.com wrote: Hi All, We have WSO2 Developer Studio 3.3.0 Alpha 3 version ready to be downloaded at [1]. Installed eclipse distributions available at [2]. This release includes following new feature, improvements and bug fixes. New Feature - [TOOLS-1855 https://wso2.org/jira/browse/TOOLS-1855] - Cloud connector support Improvements - [TOOLS-1870 https://wso2.org/jira/browse/TOOLS-1870] - Enabling Jaggery Editor Auto-Complete even without typing a character - [TOOLS-2085 https://wso2.org/jira/browse/TOOLS-2085] - There is no way to rename a GReg artifact. - [TOOLS-2106 https://wso2.org/jira/browse/TOOLS-2106] - Adding perspective login change icon into toolbar - [TOOLS-2107 https://wso2.org/jira/browse/TOOLS-2107] - Login window should not pop-up when resetting the perspective and should pop-up for new perspective Only Bug Fixes - [TOOLS-1337 https://wso2.org/jira/browse/TOOLS-1337] - There is no way to add include block inside Script Mediator - [TOOLS-1694 https://wso2.org/jira/browse/TOOLS-1694] - AF perspective detais view not filling all the feilds - [TOOLS-1719 https://wso2.org/jira/browse/TOOLS-1719] - [Dev Studio-3.2] - Logging not consistent with WSO2 Standards - [TOOLS-1722 https://wso2.org/jira/browse/TOOLS-1722] - Dev Studio fails to create Registry resource without file extension - [TOOLS-1731 https://wso2.org/jira/browse/TOOLS-1731] - Dev Studio fails to rename a resource correctly. - [TOOLS-1737 https://wso2.org/jira/browse/TOOLS-1737] - [Dev Studio 3.2] End Point Connection Issues - [TOOLS-1738 https://wso2.org/jira/browse/TOOLS-1738] - [Dev Studio 3.2] - Null Argument error for Clone Mediator - [TOOLS-1743 https://wso2.org/jira/browse/TOOLS-1743] - [Dev Studio 3.2] - Exceptions Creating EndPoint (JMS) - [TOOLS-1746 https://wso2.org/jira/browse/TOOLS-1746] - [Dev Studio-3.2] - Argument not valid Exception in Opening with Registry Info Editor - [TOOLS-1747 https://wso2.org/jira/browse/TOOLS-1747] - [Dev Studio-3.2] -Edit and saving resources to registy not possible - [TOOLS-1757 https://wso2.org/jira/browse/TOOLS-1757] - Create new Axis2 Service Project - wrong directory - [TOOLS-1945 https://wso2.org/jira/browse/TOOLS-1945] - NPE when trying to run ELB 2.0.2 from Dev Studio - [TOOLS-1948 https://wso2.org/jira/browse/TOOLS-1948] - When A/F login failed there is no way to re-login wihtout closing it - [TOOLS-1951 https://wso2.org/jira/browse/TOOLS-1951] - Trying to get versions from A/F application with just a developer role throws an Internal Error - [TOOLS-1952 https://wso2.org/jira/browse/TOOLS-1952] - Updating an app with Data Sources throws an error - [TOOLS-1975 https://wso2.org/jira/browse/TOOLS-1975] - Esb graphical editor allows to delete proxy service - [TOOLS-1976 https://wso2.org/jira/browse/TOOLS-1976] - When pasted or moved a artifact between folders the artifact.xml doesn't updated corectly - [TOOLS-1996 https://wso2.org/jira/browse/TOOLS-1996] - Error occurs while trying to open an imported synapse configuration - [TOOLS-2027 https://wso2.org/jira/browse/TOOLS-2027] - CApp POM editor does not save property changes - [TOOLS-2039 https://wso2.org/jira/browse/TOOLS-2039] - Cloud connector operation parameters doesn't get displayed in properties view properly - [TOOLS-2082 https://wso2.org/jira/browse/TOOLS-2082] - ESB project is created inside GReg project - [TOOLS-2083 https://wso2.org/jira/browse/TOOLS-2083] - Resources Editor window can not be opened once closed - [TOOLS-2084 https://wso2.org/jira/browse/TOOLS-2084] - Duplicate resource files do not trigger error - [TOOLS-2088 https://wso2.org/jira/browse/TOOLS-2088] - [Dev Studio]When you create custom folders inside synapse config, Dev Studio will give errors while importing it in to Dev Studio. - [TOOLS-2089 https://wso2.org/jira/browse/TOOLS-2089] - Resource Key Editor dialog displays incorrect workspace Registry keys - [TOOLS-2092 https://wso2.org/jira/browse/TOOLS-2092] - Error while deserializing HTTP endpoint - [TOOLS-2093 https://wso2.org/jira/browse/TOOLS-2093] - DevS removes the target sequence from the Iterate mediator - [TOOLS-2094 https://wso2.org/jira/browse/TOOLS-2094] - Remove Create New Synapse Config option in wizard since new editor does not support - [TOOLS-2103
[Dev] Invitation: Code review and Design review of secure JNDI resources an... @ Tue Nov 26, 2013 3:30pm - 4:30pm (ajant...@wso2.com)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20131126T10Z DTEND:20131126T11Z DTSTAMP:20131121T041338Z ORGANIZER;CN=ajant...@wso2.com:mailto:ajant...@wso2.com UID:kj10g39b189rlbmt9fnqnqe...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=ajant...@wso2.com;X-NUM-GUESTS=0:mailto:ajant...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Punnadi Gunarathna;X-NUM-GUESTS=0:mailto:punn...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Manisha Gayathri;X-NUM-GUESTS=0:mailto:mani...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Ramith Jayasinghe;X-NUM-GUESTS=0:mailto:ram...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Manjula Rathnayake;X-NUM-GUESTS=0:mailto:manju...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Danushka Fernando;X-NUM-GUESTS=0:mailto:danush...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Waruna De Silva;X-NUM-GUESTS=0:mailto:waru...@wso2.com ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR UE;CN=LK 6th Floor Meeting Room - Dijkstra;X-NUM-GUESTS=0:mailto:wso2.com_3 7373634303139362d333...@resource.calendar.google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Harsha Thirimanna;X-NUM-GUESTS=0:mailto:hars...@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=Gayan Dhanushka;X-NUM-GUESTS=0:mailto:gay...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Janaka Ranabahu;X-NUM-GUESTS=0:mailto:jan...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Shiroshica Kulatilake;X-NUM-GUESTS=0:mailto:sh...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Anjana Fernando;X-NUM-GUESTS=0:mailto:anj...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Dimuthu Leelarathne;X-NUM-GUESTS=0:mailto:dimut...@wso2.com CREATED:20131121T040505Z DESCRIPTION:View your event at http://www.google.com/calendar/event?action= VIEWeid=a2oxMGczOWIxODlybGJtdDlmbnFucWUwNW8gZGV2QHdzbzIub3Jntok=MTcjYWphb nRoYW5Ad3NvMi5jb20yYjEwMGE5YWM1N2RiM2M0M2Y5MmJhY2IwMjhiM2JmMWY4OWFjNDcyctz =Asia/Colombohl=en. LAST-MODIFIED:20131121T041338Z LOCATION:LK 6th Floor Meeting Room - Dijkstra SEQUENCE:1 STATUS:CONFIRMED SUMMARY:Code review and Design review of secure JNDI resources and datasour ces in AppFactory TRANSP:OPAQUE 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] Missing synapse configs of samples in ESB 4.7.0 pack
Please read the item 1 under Building the Sample Sample 13 uses sample config 0 and sample 12 uses 1 On Tue, Nov 19, 2013 at 7:40 PM, Dulanja Liyanage dula...@wso2.com wrote: Hi All, I was trying to follow [1] and found out synapse config for Sample 13 does not exist in wso2esb-4.7.0/repository/samples/. Same with Sample 12. Haven't the docs been properly updated? or are we missing an artifact which should exist in the pack. [1] http://docs.wso2.org/display/ESB470/Sample+13%3A+Dual+Channel+Invocation+through+Synapse Thanks Regards, Dulanja -- Dulanja Liyanage Senior Software Engineer - WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Missing synapse configs of samples in ESB 4.7.0 pack
My bad! I have missed that part. Sorry for the noise. Thanks Dulanja On Thu, Nov 21, 2013 at 10:02 AM, Miyuru Wanninayaka miy...@wso2.comwrote: Please read the item 1 under Building the Sample Sample 13 uses sample config 0 and sample 12 uses 1 On Tue, Nov 19, 2013 at 7:40 PM, Dulanja Liyanage dula...@wso2.comwrote: Hi All, I was trying to follow [1] and found out synapse config for Sample 13 does not exist in wso2esb-4.7.0/repository/samples/. Same with Sample 12. Haven't the docs been properly updated? or are we missing an artifact which should exist in the pack. [1] http://docs.wso2.org/display/ESB470/Sample+13%3A+Dual+Channel+Invocation+through+Synapse Thanks Regards, Dulanja -- Dulanja Liyanage Senior Software Engineer - WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda -- Dulanja Liyanage Senior Software Engineer - WSO2 Inc. M: +94776764717 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB 4.8.0 - Alpha Released !
Hi Lahiru, We are still observing above issue on ESB 480 alpha and reported under[1]. And i have raised two more concerns regarding the logging with related to the MS and Mp functionality under [2] and [3] [1] https://wso2.org/jira/browse/ESBJAVA-2724 [2] https://wso2.org/jira/browse/ESBJAVA-2699 [3] https://wso2.org/jira/browse/ESBJAVA-2603 On Mon, Nov 18, 2013 at 11:39 AM, Lahiru Sandaruwan lahi...@wso2.comwrote: Hi Evanthika et al., Please verify whether the issue reported at thread ESB 4.7.0 logs printed in high frequency when Message Broker is down is fixed in ESB 4.8.0. Thanks. On Fri, Nov 15, 2013 at 8:03 AM, Evanthika Amarasiri evanth...@wso2.comwrote: Yes Subash, This was identified and reported as a bug for this release. https://wso2.org/jira/browse/ESBJAVA-2358 https://wso2.org/jira/browse/ESBJAVA-2359 Evanthika On Thu, Nov 14, 2013 at 9:26 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Evanthika, In M5 packs, noticed that the default BAM mediation data publishing menu goes to a blank page (Refer [Monitor ESB from BAM 1.5.0] Mediation Data Publishing menu goes to a Blank Page !) and this is a blocker for people who wants to monitor ESB through BAM. Please check whether it is also fixed. On Wed, Nov 13, 2013 at 11:00 PM, Evanthika Amarasiri evanth...@wso2.com wrote: Noted Dushan, Evanthika On Wed, Nov 13, 2013 at 10:49 PM, Dushan Abeyruwan dus...@wso2.comwrote: Hi It seems like connectors are not updated correctly with the Alpha pack shared, anyway for QA process for 4.8.0 Alpha please do download the latest connectors from [1] [1]https://svn.wso2.org/repos/wso2/people/shafreen/connectors/ On Wed, Nov 13, 2013 at 8:16 PM, Shafreen Anfar shafr...@wso2.comwrote: Hi, ESB version 4.8.0 Alpha is available at, https://svn.wso2.org/repos/wso2/people/shafreen/ESB480/alpha/wso2esb-4.8.0.zip Connectors can be found in $ESB_HOME/repository/connectors -- Regards, *Shafreen* Software Engineer WSO2 Inc Mobile : 077-556-395-1 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Asanka Vithanage Senior Software Engineer -QA Mobile: +94 0716286708 Email: asan...@wso2.com WSO2 Inc. www.wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [AF][STS] Problems when invoking sts in tenant
Looping in
Thanks Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Thu, Nov 21, 2013 at 11:32 AM, Danushka Fernando danush...@wso2.comwrote:
Hi,
I am trying to invoke the sts service in a tenant. When I do that I could
see the following exception in the server side.
How ever I debugged the Axis2Engine and RampartReciver. There I found that
error is about rampart is not engaged in server side. I attached a
screenshot here which shows that rampart is engaged in tenant.
So any idea whats going wrong here?
[2013-11-21 11:20:53,484] DEBUG {org.apache.axis2.engine.AxisEngine} -
MustUnderstand header not processed or registered as understood{
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}Security
[2013-11-21 11:20:53,510] ERROR {org.apache.axis2.engine.AxisEngine} -
Must Understand check failed for header
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd:
Security
org.apache.axis2.AxisFault: Must Understand check failed for header
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd:
Security
at
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:104)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.continueInvocation(CompositeValve.java:178)
at
org.wso2.carbon.tomcat.ext.valves.CarbonTomcatValve$1.invoke(CarbonTomcatValve.java:47)
at
org.wso2.carbon.webapp.mgt.TenantLazyLoaderValve.invoke(TenantLazyLoaderValve.java:62)
at
org.wso2.carbon.tomcat.ext.valves.TomcatValveContainer.invokeValves(TomcatValveContainer.java:47)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
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)
Thanks Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB 4.8.0 Worker/ Manager setup - Observed ERROR {org.wso2.carbon.caching.impl.CacheCleanupTask} - Error occurred while running CacheCleanupTask {org.wso2.carbon.caching.impl.CacheCleanupTa
Hi,
Issue already reported at [1]:
https://wso2.org/jira/browse/CARBON-14552
Thanks,
Shashika
Shashika Ubhayaratne
Associate Technical Lead - QA
WSO2 Inc: http://www.wso2.com/
Mobile: +94773383831
On Wed, Nov 20, 2013 at 5:07 PM, Shashika Ubhayaratne shash...@wso2.com wrote:
Hi,
We have ESB 4.8.0 worker/ manager setup with one worker running on
linux box and another worker running on windows machine:
Observed following error time to time and disconnected windows server
from the domain.
TID: [0] [ESB] [2013-11-20 16:34:42,035] ERROR
{org.wso2.carbon.caching.impl.CacheCleanupTask} - Error occurred
while running CacheCleanupTask
{org.wso2.carbon.caching.impl.CacheCleanupTask}
com.hazelcast.core.OperationTimeoutException: No response for 12
ms. Aborting invocation! InvocationFuture{invocation=InvocationImpl{
serviceName='hz:impl:mapService',
op=com.hazelcast.map.operation.MapEntrySetOperation@4eb884e3,
partitionId=0, replicaIndex=0, tryCount=250, tryPauseMillis=500,
invokeCount=1, callTimeout=6, target=Address[10.10.10.234]:4300},
done=false}
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.waitForResponse(InvocationImpl.java:376)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:291)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:283)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnPartitions(OperationServiceImpl.java:495)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnAllPartitions(OperationServiceImpl.java:424)
at
com.hazelcast.map.proxy.MapProxySupport.entrySetInternal(MapProxySupport.java:564)
at com.hazelcast.map.proxy.MapProxyImpl.entrySet(MapProxyImpl.java:410)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.entrySet(HazelcastDistributedMapProvider.java:167)
at org.wso2.carbon.caching.impl.CacheImpl.syncCaches(CacheImpl.java:236)
at org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
at -- End remote and begin local stack-trace --.(Unknown Source)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.resolveResponse(InvocationImpl.java:405)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:291)
at
com.hazelcast.spi.impl.InvocationImpl$InvocationFuture.get(InvocationImpl.java:283)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnPartitions(OperationServiceImpl.java:495)
at
com.hazelcast.spi.impl.OperationServiceImpl.invokeOnAllPartitions(OperationServiceImpl.java:424)
at
com.hazelcast.map.proxy.MapProxySupport.entrySetInternal(MapProxySupport.java:564)
at com.hazelcast.map.proxy.MapProxyImpl.entrySet(MapProxyImpl.java:410)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.entrySet(HazelcastDistributedMapProvider.java:167)
at org.wso2.carbon.caching.impl.CacheImpl.syncCaches(CacheImpl.java:236)
at org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
TID: [0] [ESB] [2013-11-20 16:39:22,057] ERROR
{org.wso2.carbon.caching.impl.CacheCleanupTask} - Error occurred
while running CacheCleanupTask
{org.wso2.carbon.caching.impl.CacheCleanupTask}
com.hazelcast.core.OperationTimeoutException: No response for 12
ms. Aborting invocation! InvocationFuture{invocation=InvocationImpl{
serviceName='hz:impl:mapService',
op=com.hazelcast.map.operation.MapEntrySetOperation@459408e3,
partitionId=0, replicaIndex=0, tryCount=250, tryPauseMillis=500,
invokeCount=1, callTimeout=6, target=Address[10.10.10.234]:4300},
done=false}
at
[Dev] Upate state across different WSO2 cluster nodes is synchronous or asynchronous?
Hi: In http://wso2.com/library/articles/clustering-landscape-wso2-stack;, it tells if cluster nodes share state, and they are not stored in same shared persistent media like a database, all changes done at each node have to be disseminated to all other nodes in the cluster. There are two choices whether updates are synchronous or asynchronous, where in the former case, the request does not return till all the replicas of the system are updated, whereas the latter updates the replicas in the background. In the latter case, there may be a delay before values are reflected in the other nodes. Does anyone know how setting to make the updating synchronous and how setting to make updating asynchronous? stevegyc___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Is there a interface for the manager to manage the cluster
Hi: I want to know in worker/manager separated cluster, is there a interface for the manager to manage the cluster, including monitor the number of the worker nodes and the status of them, restart or stop the selected worker nodes. stevegyc___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
