Fixed !
Lahiru
On Tue, Jul 27, 2010 at 10:58 AM, Samisa Abeysinghe sam...@wso2.com wrote:
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.wso2.carbon
ArtifactId:
thanks for your help,
but i would like to know if I setup Gadget Server, and Identity Server on
cluster... I will need the amazon EC2 load balancer?
or i can take Load Balancer so the clustering will provide of high
availability and Fail Over following the configuration steps on the blog you
On Tue, Jul 27, 2010 at 11:22 AM, Isuru Suriarachchi is...@wso2.com wrote:
On Tue, Jul 27, 2010 at 11:04 AM, Hiranya Jayathilaka hira...@wso2.comwrote:
Hi Folks,
The 3.0.1 release work can now proceed. The new branching strategy has
been applied to the Carbon core. I was able to get a
We sill use a very old one. Shall we update to the latest stable?
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
It is time that we updated to 3.1.0?
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Hi,
On Tue, Jul 27, 2010 at 12:35 PM, Samisa Abeysinghe sam...@wso2.com wrote:
On Tue, Jul 27, 2010 at 11:22 AM, Isuru Suriarachchi is...@wso2.comwrote:
On Tue, Jul 27, 2010 at 11:04 AM, Hiranya Jayathilaka
hira...@wso2.comwrote:
Hi Folks,
The 3.0.1 release work can now proceed. The
Samisa Abeysinghe wrote:
It is time that we updated to 3.1.0?
+1
Ruwan
Thanks,
Samisa...
Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
We are still using 1.1.112.
And we have 1.2.140 as the latest as per
http://code.google.com/p/h2database/downloads/list
On Tue, Jul 27, 2010 at 12:44 PM, Samisa Abeysinghe sam...@wso2.com wrote:
We sill use a very old one. Shall we update to the latest stable?
Thanks,
Samisa...
Samisa
Hello,
i'm trying to setup a MySQL on registry for Gadget Server and i get this
when i try to start the server with the -Dsetup
vator}
[2010-07-27 14:35:22,594] INFO - Carbon Home : /opt/wso2gs-1.1.0
{org.wso2.carbon.core.internal.CarbonCoreActivator}
[2010-07-27 14:35:22,594] INFO -
this is the registry configuration i use:
dbConfig name=mysql-db
urljdbc:mysql://xxx.xxx.xxx.xxx/regdbGS/url
userNameregadmin/userName
passwordxx/password
driverNamecom.mysql.jdbc.Driver/driverName
maxActive50/maxActive
maxWait6/maxWait
Hi,
Did you do a myserver upgrade recently?. Just checking,
http://bugs.mysql.com/bug.php?id=40360
Dimuthu
2010/7/27 Víctor Álvarez spa...@gmail.com:
this is the registry configuration i use:
dbConfig name=mysql-db
urljdbc:mysql://xxx.xxx.xxx.xxx/regdbGS/url
is plain new installation over ubuntu:
server version: 5.1.41-3ubuntu12.3-log
Thanks. need some help, im really stucked at this.
it only happends if i set the msyql on the registry.xml, no problem to set
it up on the user-mgt.xml
is necessary to configure it on both isn't it?
Thanks
On Tue,
Is it possible to check this on a previous version of MySQL?
eg: v 5.1.28
/sumedha
2010/7/27 Víctor Álvarez spa...@gmail.com
is plain new installation over ubuntu:
server version: 5.1.41-3ubuntu12.3-log
Thanks. need some help, im really stucked at this.
it only happends if i set the
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
I tried building the bam product only on local machine and it failed to
locate the snapshots :(
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1)
Hi Víctor,
When we set up the clustering as described by
http://pathberiya.blogspot.com/2010/05/test.html, that setup does not
include a load balancer, and that only make sure nodes in the cluster
share state. If you need a single endpoint for whole cluster (with
FO), then you need to setup a
Hi Víctor,
My call is that it is OK share the IS database with some other
database. AFAIK, IS has low amount of data compared to registry etc.
Thanks
Srinath
2010/7/26 Víctor Álvarez spa...@gmail.com:
any response pls?
Thanks!
2010/7/23 Víctor Álvarez spa...@gmail.com
Same as on Gadget
Hi Samisa,
Can we do that through a Log4j appender and log4j levels? Basically
adding a new appender which listen to only ERROR or worse log levels.
--Srinath
On Mon, Jul 26, 2010 at 1:38 PM, Samisa Abeysinghe sam...@wso2.com wrote:
Hiranya,
Can you please send the instructions on
On Wed, Jul 28, 2010 at 9:35 AM, Srinath Perera srin...@wso2.com wrote:
Hi Samisa,
Can we do that through a Log4j appender and log4j levels? Basically
adding a new appender which listen to only ERROR or worse log levels.
Yes I think we have done this in the past.
Thanks,
Samisa...
Samisa
Looks like it was a problem in the pom. Did not have wso2 snapshot repo in
there.
On Wed, Jul 28, 2010 at 9:27 AM, Samisa Abeysinghe sam...@wso2.com wrote:
I tried building the bam product only on local machine and it failed to
locate the snapshots :(
[ERROR] BUILD ERROR
[INFO]
Hi Samisa,
On Mon, Jul 26, 2010 at 1:38 PM, Samisa Abeysinghe sam...@wso2.com wrote:
Hiranya,
Can you please send the instructions on $subject?
Here's the entries that need to be added to the log4j.properties file in
order to get a separate error log:
*# the root category is ERROR
I think there's no need to put snapshot repository for all the pom files
since it is not required for our releases, we can simply put our snapshot
repo in to the local ~/.m2/settings.xml and build and ask users to do the
same if they want to build the trunk !
WDYT ?
Lahiru
On Wed, Jul 28, 2010
+1 - Yes IS uses low amount of data.
There are two databases associated with each and every carbon based product.
One is for the user store and the other is for the registry.
In the case of Registry DB - you can share it with any other product -
recommeded to use a MySQL cluster.
BTW how are
On Wed, Jul 28, 2010 at 10:07 AM, Lahiru Gunathilake lah...@wso2.comwrote:
I think there's no need to put snapshot repository for all the pom files
since it is not required for our releases, we can simply put our snapshot
repo in to the local ~/.m2/settings.xml and build and ask users to do
24 matches
Mail list logo