Re: [Dev] Error logged at INFO level when starting MB integration tests.
We found that above exception occurred due to current testing framework
instrumentation not compatible with Java 7. So we found that it has updated
in mail thread [1] and everything worked fine after following up given
instructions.
[1] [Dev] Testing Jacoco based code coverage genration
On Sat, May 23, 2015 at 12:22 PM, Indika Sampath indi...@wso2.com wrote:
Hi Krishantha/Nuwan,
We see following stack trace logged at INFO level when we run MB
integration test in Java 7. Any idea of what went wrong ?
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
[2015-05-23 12:13:20,159] ERROR
{org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
adding services from bundle : org.wso2.carbon.andes-3.0.0.SNAPSHOT
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
java.lang.ClassFormatError: Illegal local variable table length 19 in
method
org.wso2.carbon.andes.service.ws.QpidAdminService.getClientID()Ljava/lang/String;
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at java.lang.Class.forName0(Native Method)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at java.lang.Class.forName(Class.java:274)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.init(DefaultSchemaGenerator.java:141)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:221)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:91)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at java.lang.reflect.Method.invoke(Method.java:606)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
INFO
[org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] -
at
[Dev] Please Review and Merge
Hi, This is the fix [1] for publich JIRA [2]. Please review and merge. [1] *https://github.com/wso2/carbon-apimgt/pull/465 https://github.com/wso2/carbon-apimgt/pull/465* [2] *https://wso2.org/jira/browse/APIMANAGER-3560 https://wso2.org/jira/browse/APIMANAGER-3560* Thanks. -- Best Regards, *Thilini Cooray* Software Engineer Mobile : +94 (0) 774 570 112 %2B94%20%280%29%20773%20451194 E-mail : thili...@wso2.com WSO2 Inc. www.wso2.com lean.enterprise.middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Error logged at INFO level when starting MB integration tests.
Hi Krishantha/Nuwan,
We see following stack trace logged at INFO level when we run MB
integration test in Java 7. Any idea of what went wrong ?
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- [2015-05-23 12:13:20,159] ERROR
{org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} - Error while
adding services from bundle : org.wso2.carbon.andes-3.0.0.SNAPSHOT
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- java.lang.ClassFormatError: Illegal local variable table length 19 in
method
org.wso2.carbon.andes.service.ws.QpidAdminService.getClientID()Ljava/lang/String;
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at java.lang.Class.forName0(Native Method)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at java.lang.Class.forName(Class.java:274)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator.init(DefaultSchemaGenerator.java:141)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.apache.axis2.deployment.util.Utils.fillAxisService(Utils.java:453)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:397)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:221)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:91)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at java.lang.reflect.Method.invoke(Method.java:606)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
INFO [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
Re: [Dev] Testing Jacoco based code coverage genration
do we have any documentation on this?
On Wed, May 13, 2015 at 6:58 PM, Krishantha Samaraweera krishan...@wso2.com
wrote:
Hi all,
I have redesign Jacoco coverage generation a bit to support for coverage
merging functionality. Now coverage data dump into
$basedir/target/jacoco/coverage directory at the time of report generation,
jacoco coverage data files are merged back to a single file
(jacoco-data-merge.exec) and report will be generated using this merged
data file.
To merge multiple module test coverage data files. You can use pom file
with exec-maven-plugin to execute
org.wso2.carbon.automation.engine.frameworkutils.TestCoverageGenerator
class. This will generate merged report at
$basedir/target/jacoco/coverage/index.html.
I will write a comprehensive document on applying Jacoco coverage to
products.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 10:46 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Nuwan,
You can't use TestCoverageGenerator anymore (We need to remove this
class as well) . The merged report should be generated at the last test
module with got executed as we merge all coverage data to common file.
May be we can think of introducing pom file to do merging. If this option
is not user friendly.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 10:24 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi Krishantha,
I am getting below error when merging the coverage reports.
generateReports implementation is missing in CodeCoverageUtils. report
module use
the org.wso2.carbon.integration.common.utils.coverage.TestCoverageGenerator
to aggregate results.
Exception in thread main java.lang.NoSuchMethodError:
org.wso2.carbon.automation.engine.frameworkutils.CodeCoverageUtils.generateReports(Ljava/util/List;)V
at
org.wso2.carbon.integration.common.utils.coverage.TestCoverageGenerator.main(TestCoverageGenerator.java:36)
Thanks,
Nuwanw
On Tue, May 5, 2015 at 9:47 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Yes. The correct implementation
is
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
We will remove the CarbonServerExtension from utils to get rid of
conflicts.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 9:27 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Nuwan,
You should remove
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension
not the
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension.
Thanks,
Krishantha.
On Wed, May 6, 2015 at 9:47 AM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi
We should
remove
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
from extensions. Then all the tests module should refer the correct
class.
Thanks,
Nuwanw
On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi Waruna,
On Wed, May 6, 2015 at 9:12 AM, Waruna Perera waru...@wso2.com
wrote:
Hi Krishantha,
And we need to update Automation.xml to use following class instead
of one from utils.
Please remove the CarbonServerExtension class at utils. Its was
deprecated in last release and moved to test extensions to support for
carbon kernel startup.
Need to completely get rid of this extension class and its
dependencies.
Thanks,
Krishantha.
org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension
Thanks
On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara nuw...@wso2.com
wrote:
Hi Krishantha,
I tried generating coverage in ESB. It is working fine and
Coverage reports generated. However the coverage report aggregation
seems
not working when there are multiple tests modules. We need to fix the
issue.
test-automation-framework - 4.3.2-SNAPSHOT
carbon-platform-integration-utils - 4.3.1-SNAPSHOT
Thanks,
Nuwanw
On Wed, Apr 29, 2015 at 10:41 PM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Correction : Step #1 configuration should be as follows.
execution
idcopy-jacoco-dependencies/id
phasecompile/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/jacoco/outputDirectory
includeTypesjar/includeTypes
includeArtifactIdsorg.jacoco.agent/includeArtifactIds
/configuration
/execution
Thanks,
Krishantha.
On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Hi all,
New coverage implementation using Jacoco has been committed to
master branch of carbon-platform-integration. I tried my best to
adhere to
existing Emma based design and reuse same instrumentation and
filters text
files. Note that this new coverage implementation was done to
support for
JDK 1.7 and 1.8. We need to test the new implementation thoroughly
before
the release.
I've done initial testing with AS and everything seems to work.
Automation team will start verifying coverage
Re: [Dev] AS cluster registry debsync issue
Hi Udara,
As your worker node has received the cluster message, I assume clustering
works properly in your setup. Can you please check your DepSync
configurations.
And verify whether your new artifact is uploaded to the SVN by your master
node.
Thanks,
Jayanga.
*Jayanga Dissanayake*
Senior Software Engineer
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259
On Sat, May 23, 2015 at 11:01 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
I create a AS 5.2.1 cluster with two nodes as each members is a WKA member
for other members. Member join messages appeared. However when a web app
is deployed to the manager node, it is not propagated to the other node.
However following repo notification message appeared in the worker node.
Note that I have applied the hazelcast patch patch1297 to both nodes.
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
- Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=-1234,
tenantDomain='carbon.super', messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Received
[SynchronizeRepositoryRequest{tenantId=-1234, tenantDomain='carbon.super',
messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}]
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS cluster registry debsync issue
Hi Jayanga,
I tried registry based in order to check weather cluster is working. I will
check svn based deb sync and let you know the results.
On Sun, May 24, 2015 at 9:18 AM, Jayanga Dissanayake jaya...@wso2.com
wrote:
Hi Udara,
As your worker node has received the cluster message, I assume clustering
works properly in your setup. Can you please check your DepSync
configurations.
And verify whether your new artifact is uploaded to the SVN by your master
node.
Thanks,
Jayanga.
*Jayanga Dissanayake*
Senior Software Engineer
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259
On Sat, May 23, 2015 at 11:01 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
I create a AS 5.2.1 cluster with two nodes as each members is a WKA
member for other members. Member join messages appeared. However when a
web app is deployed to the manager node, it is not propagated to the other
node. However following repo notification message appeared in the worker
node.
Note that I have applied the hazelcast patch patch1297 to both nodes.
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
- Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=-1234,
tenantDomain='carbon.super', messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Received
[SynchronizeRepositoryRequest{tenantId=-1234, tenantDomain='carbon.super',
messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}]
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS cluster registry debsync issue
Hi All
The registry based depsync is deprecated. Please try with SVN.
-Ajith
On Sun, May 24, 2015 at 12:54 AM, Manoj Kumara ma...@wso2.com wrote:
Hi Udara,
Did you mounted the registry database between the nodes ? Please follow [1]
[1]
http://emsooriyabandara.blogspot.com/2013/01/registry-based-deployment-synchronizer.html
*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188
On Sat, May 23, 2015 at 11:01 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
I create a AS 5.2.1 cluster with two nodes as each members is a WKA
member for other members. Member join messages appeared. However when a
web app is deployed to the manager node, it is not propagated to the other
node. However following repo notification message appeared in the worker
node.
Note that I have applied the hazelcast patch patch1297 to both nodes.
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
- Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=-1234,
tenantDomain='carbon.super', messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Received
[SynchronizeRepositoryRequest{tenantId=-1234, tenantDomain='carbon.super',
messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}]
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.com
Email : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS cluster registry debsync issue
Hi,
I tried svn based deb sync and got the following issue.
DeploymentSynchronizer
Enabledtrue/Enabled
AutoCommittrue/AutoCommit
AutoCheckouttrue/AutoCheckout
RepositoryTypesvn/RepositoryType
SvnUrlfile:///home/udara/experiments/depsync//SvnUrl
!-- SvnUrlhttp://svnrepo.example.com/repos//SvnUrl --
SvnUserudara/SvnUser
SvnPasswordudara/SvnPassword
SvnUrlAppendTenantIdtrue/SvnUrlAppendTenantId
/DeploymentSynchronizer
Error while attempting to create the directory:
file:///home/udara/experiments/depsync/-1234
org.tigris.subversion.svnclientadapter.SVNClientException:
org.tigris.subversion.javahl.ClientException: svn: Unable to open an
ra_local session to URL
svn: Unable to open repository 'file:///home/udara/experiments/depsync'
svn: Expected FS format between '1' and '4'; found format '6'
at
org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.mkdir(AbstractJhlClientAdapter.java:2524)
at
org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.checkRemoteDirectory(SVNBasedArtifactRepository.java:240)
at
org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.init(SVNBasedArtifactRepository.java:167)
at
org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.newCarbonRepositorySynchronizer(CarbonRepositoryUtils.java:71)
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.initDeploymentSynchronizerForSuperTenant(DeploymentSynchronizerComponent.java:108)
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.activate(DeploymentSynchronizerComponent.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
On Sun, May 24, 2015 at 10:29 AM, Ajith Vitharana aji...@wso2.com wrote:
Hi All
The registry based depsync is deprecated. Please try with SVN.
-Ajith
On Sun, May 24, 2015 at 12:54 AM, Manoj Kumara ma...@wso2.com wrote:
Hi Udara,
Did you mounted the registry database between the nodes ? Please follow
[1]
[1]
http://emsooriyabandara.blogspot.com/2013/01/registry-based-deployment-synchronizer.html
*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188
On Sat, May 23, 2015 at 11:01 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
I create a AS 5.2.1 cluster with two nodes as each members is a WKA
member for other members. Member join messages appeared. However when a
web app is deployed to the manager node, it is not propagated to the other
node. However following repo notification message appeared in the worker
node.
Note that I have applied the hazelcast patch patch1297 to both nodes.
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
- Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=-1234,
tenantDomain='carbon.super', messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Received
[SynchronizeRepositoryRequest{tenantId=-1234, tenantDomain='carbon.super',
messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}]
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.com
Email : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS cluster registry debsync issue
Hi,
Is this due to a version issue. My svn version is 1.8.8 which seems to be
not supported according to [1]
svn --version
svn, version 1.8.8 (r1568071)
[1]
https://docs.wso2.com/display/CLUSTER420/SVN-based+Deployment+Synchronizer
On Sun, May 24, 2015 at 10:51 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
I tried svn based deb sync and got the following issue.
DeploymentSynchronizer
Enabledtrue/Enabled
AutoCommittrue/AutoCommit
AutoCheckouttrue/AutoCheckout
RepositoryTypesvn/RepositoryType
SvnUrlfile:///home/udara/experiments/depsync//SvnUrl
!-- SvnUrlhttp://svnrepo.example.com/repos//SvnUrl --
SvnUserudara/SvnUser
SvnPasswordudara/SvnPassword
SvnUrlAppendTenantIdtrue/SvnUrlAppendTenantId
/DeploymentSynchronizer
Error while attempting to create the directory:
file:///home/udara/experiments/depsync/-1234
org.tigris.subversion.svnclientadapter.SVNClientException:
org.tigris.subversion.javahl.ClientException: svn: Unable to open an
ra_local session to URL
svn: Unable to open repository 'file:///home/udara/experiments/depsync'
svn: Expected FS format between '1' and '4'; found format '6'
at
org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.mkdir(AbstractJhlClientAdapter.java:2524)
at
org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.checkRemoteDirectory(SVNBasedArtifactRepository.java:240)
at
org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.init(SVNBasedArtifactRepository.java:167)
at
org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.newCarbonRepositorySynchronizer(CarbonRepositoryUtils.java:71)
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.initDeploymentSynchronizerForSuperTenant(DeploymentSynchronizerComponent.java:108)
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent.activate(DeploymentSynchronizerComponent.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
On Sun, May 24, 2015 at 10:29 AM, Ajith Vitharana aji...@wso2.com wrote:
Hi All
The registry based depsync is deprecated. Please try with SVN.
-Ajith
On Sun, May 24, 2015 at 12:54 AM, Manoj Kumara ma...@wso2.com wrote:
Hi Udara,
Did you mounted the registry database between the nodes ? Please follow
[1]
[1]
http://emsooriyabandara.blogspot.com/2013/01/registry-based-deployment-synchronizer.html
*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188
On Sat, May 23, 2015 at 11:01 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
I create a AS 5.2.1 cluster with two nodes as each members is a WKA
member for other members. Member join messages appeared. However when a
web app is deployed to the manager node, it is not propagated to the other
node. However following repo notification message appeared in the worker
node.
Note that I have applied the hazelcast patch patch1297 to both nodes.
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
- Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=-1234,
tenantDomain='carbon.super',
messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Received
[SynchronizeRepositoryRequest{tenantId=-1234, tenantDomain='carbon.super',
messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}]
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.com
Email : aji...@wso2.com
Blog: http://vitharana.org
Mobile : +1-812-360-5335
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Tenant Cleanup Interval
Hi Malaka, Tenant configuration was introduced to carbon xml with the tenant eager loading feature. It was intended to allow tenant idle time configuration in the case of tenant lazy loading as well. The issue is that MultitenantServerManager reads the system property tenant.idle.time before TenantLoadingConfig reads the carbon xml and set the tenant idle time as the system property. Hence the IdleTime configuration in carbon xml is not effective ATM. Tenants will be unloaded after the time specified with -Dtenant.idle.time, else, after the default of 30 minutes. Created a public jira [1]. [1] https://wso2.org/jira/browse/CARBON-15253 On Sat, May 23, 2015 at 8:15 AM, Malaka Silva mal...@wso2.com wrote: Thx guys. So the entry in carbon.xml does not work. If so should we remove it? On Fri, May 22, 2015 at 12:04 PM, Shashika Karunatilaka shashi...@wso2.com wrote: Hi Bathiya, Its also the same as in latest kernel versions. Thank you. On Fri, May 22, 2015 at 12:00 PM, Bhathiya Jayasekara bhath...@wso2.com wrote: Hi Malaka, In carbon 4.2.0, it can be done with below argument in wso2server.sh. Not sure about latest kernels. -Dtenant.idle.time=1 \ Thanks, Bhathiya On Fri, May 22, 2015 at 11:31 AM, Malaka Silva mal...@wso2.com wrote: Hi, Can we change the default value for $subject. I tried setting following in carbon.xml. It does not seem to be working. Tenant LoadingPolicy LazyLoading IdleTime1/IdleTime /LazyLoading !-- EagerLoading Include*,!foo.com,!bar.com/Include /EagerLoading-- /LoadingPolicy /Tenant -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Bhathiya Jayasekara* *Senior Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* *Phone: +94715478185 %2B94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax* *Blog: http://movingaheadblog.blogspot.com http://movingaheadblog.blogspot.com/* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Shashika Prabath Karunatilaka, Software Engineer, WSO2, Inc: http://wso2.com/ mobile : +94 77 7487792 -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Kalpa Welivitigoda Software Engineer, WSO2 Inc. http://wso2.com Email: kal...@wso2.com Mobile: +94776509215 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] AS cluster registry debsync issue
Hi Udara,
Did you mounted the registry database between the nodes ? Please follow [1]
[1]
http://emsooriyabandara.blogspot.com/2013/01/registry-based-deployment-synchronizer.html
*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188
On Sat, May 23, 2015 at 11:01 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
I create a AS 5.2.1 cluster with two nodes as each members is a WKA member
for other members. Member join messages appeared. However when a web app
is deployed to the manager node, it is not propagated to the other node.
However following repo notification message appeared in the worker node.
Note that I have applied the hazelcast patch patch1297 to both nodes.
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener}
- Received ClusteringMessage: SynchronizeRepositoryRequest{tenantId=-1234,
tenantDomain='carbon.super', messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Received
[SynchronizeRepositoryRequest{tenantId=-1234, tenantDomain='carbon.super',
messageId=68bd3b2f-598a-423c-b876-bd3eb5e9bd3c}]
[2015-05-23 10:44:35,797] INFO
{org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Updating
repo update required parameter
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
