Hi Chamith,
Did you clean the axis2 repos for tenants, before restarting? The error
Charitha sent suggests an issue with contents in .svn/ folders. So, it's
likely that the working copy in the worker nodes are broken. May be even in
the master node, I'm not sure whether it's applicable in this
On Thu, Oct 25, 2012 at 1:03 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi Chamith,
Did you clean the axis2 repos for tenants, before restarting? The error
Charitha sent suggests an issue with contents in .svn/ folders. So, it's
likely that the working copy in the worker nodes are broken.
Guys have we fixed all the related issues here?
On Thu, Oct 25, 2012 at 1:32 PM, Supun Malinga sup...@wso2.com wrote:
On Thu, Oct 25, 2012 at 1:03 PM, Kasun Gajasinghe kas...@wso2.com wrote:
Hi Chamith,
Did you clean the axis2 repos for tenants, before restarting? The error
Charitha
With proper svn kit, I did not get the svn error. However, the services are
still not synced between worker/manager nodes.
You can see that Axis2Service.aar is not in worker. Checked the logs with
Afkham but could not find any suspicious error.
Tenant 9 services directory of Manager node
You can see this behavior clearly when you deploy a bunch of services
and run a jmeter test for the whole bunch. To get all services deployed
in workers, you need to run the test multiple times. Everything won't
get deployed in the first run.
On 10/24/2012 05:18 PM, Charitha Kankanamge wrote:
@Subject.
1. Created a new tenant in https://stratosdev.private.wso2.com
2. Logged into Application server service
3. Deploy a web service (AAR)
4. Access ?wsdl. You get 404
Check worker logs. You will see the following errors are continuously
thrown.
TID: [0] [AS] [2012-10-24 13:18:15,101]
Looks like we are not using svn kit??
On Wed, Oct 24, 2012 at 10:31 AM, Charitha Kankanamge chari...@wso2.comwrote:
@Subject.
1. Created a new tenant in https://stratosdev.private.wso2.com
2. Logged into Application server service
3. Deploy a web service (AAR)
4. Access ?wsdl. You get 404
It seems we are; but there are multiple svnkit bundles inside dropins.
root@stratosdev007:/mnt/
192.168.4.124/wso2as-5.0.1/repository/components/dropins# ls -la
total 8164
drwxr-xr-x 2 root root4096 Oct 23 17:46 .
drwxr-xr-x 10 root root4096 Oct 23 20:12 ..
-rw-r--r-- 1 root root
It seems the deployment is broken and cluttered all garbage in there.
DevOps please clean the system and get it right.
If this was not broken in products, this cannot be broken in services.
On Wed, Oct 24, 2012 at 10:42 AM, Charitha Kankanamge chari...@wso2.comwrote:
It seems we are; but there
On Wed, Oct 24, 2012 at 10:42 AM, Charitha Kankanamge chari...@wso2.comwrote:
It seems we are; but there are multiple svnkit bundles inside dropins.
root@stratosdev007:/mnt/
192.168.4.124/wso2as-5.0.1/repository/components/dropins# ls -la
total 8164
drwxr-xr-x 2 root root4096 Oct 23
Looks like we have done a rm instead of svn rm and older jars have
restored in the repo somehow. Restarted services with the proper
svnkit-bundle-1.0.0.jar
On 10/24/2012 10:44 AM, Samisa Abeysinghe wrote:
It seems the deployment is broken and cluttered all garbage in there.
DevOps please clean
11 matches
Mail list logo
