Hi All,
Sorry for late reply
As I see it, secondary indexes are not a part of the agent API, which is
about collecting the data.
Secondary index is about analyzing / presenting the data. So if user
need secondary indexes, they will have to go to Cassandra directly, and
define them. I think we
On Wed, Jul 4, 2012 at 12:30 PM, Srinath Perera srin...@wso2.com wrote:
Hi All,
Sorry for late reply
As I see it, secondary indexes are not a part of the agent API, which is
about collecting the data.
Secondary index is about analyzing / presenting the data. So if user
need secondary
I'm seeing $subject for a tenant in AS. Is this a known issue? The error
says I have to configure syslog. What are the changes i need to make in
syslog configuration?
[image: Inline image 1]
Thanks,
Kishanthan.
--
*Kishanthan Thangarajah*
Software Engineer,
Development Technologies Team,
WSO2,
This is a list of all comments for WSDS001-2.
Review Summary: No summary
---
ID: WSDS001-2 http://wso2.org/crucible/cru/WSDS001-2
Title: Fixing TOOLS-980
Statement of Objectives:
State: Approval
Author: Jasintha Dasanayaka
Moderator: Maheshika Goonetilleke
Reviewers: (0 active, 0
Yes this is a known issue. Right now we cant view tenant specific logs
without configuring syslog. However, I am writing a carbonMemory appender
to view tenant aware log events from the memory. So that users can view
most latest logs from the memory. However if you want to view older logs
you
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20120705T083000Z
DTEND:20120705T093000Z
DTSTAMP:20120704T075851Z
ORGANIZER;CN=Harshana Martin:mailto:harsh...@wso2.com
UID:cvk6s5ol2bugbtfbpoh6tt0...@google.com
At one point Sumedha suggested that we should use a single API_ID
everywhere in AM DB. That's how the AM_API table came into existence.
Thanks,
Hiranya
On Tue, Jul 3, 2012 at 11:52 PM, Denis Weerasiri de...@wso2.com wrote:
Hi Hiranya,
Some of the meta data related to API is store in both AM
If you go thru the DB schema you will notice how the API_ID is bring
referenced by other tables.
Thanks,
Hiranya
On Wed, Jul 4, 2012 at 2:13 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
At one point Sumedha suggested that we should use a single API_ID
everywhere in AM DB. That's how the
Hi all,
This seems to be a blocker for us. Looks like a caching issue at mysql
and/or pooling layer. I tried without the following indexing and still get
the same results. I don't think it is a mysql layer because the same SQL is
running on mysql_workbench.
CREATE UNIQUE INDEX
Folks, whats the status of this ? Are we set to release orbit ? when are we
going to branch.
Regards,
/Nuwan
On Mon, Jul 2, 2012 at 5:36 AM, Samisa Abeysinghe sam...@wso2.com wrote:
On Sun, Jul 1, 2012 at 10:15 PM, Pradeep Fernando prad...@wso2.comwrote:
Hi All,
we have decided to
Dimuthu,
I was under the impression this was solved. Thought Anjana had a look @ it.
This cannot be a caching issue @ the database level. Then it should impact
everywhere. I still feel this is an application level concurrency issue.
Let me discuss with Anjana get back to you. Sorry for allowing
will start branching on Thursday, plan is to finish it by monday.
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Any plans for dependencies ?
On Wed, Jul 4, 2012 at 4:22 PM, Pradeep Fernando prad...@wso2.com wrote:
will start branching on Thursday, plan is to finish it by monday.
--Pradeep
--
*Thanks Regards,
Nuwan Bandara
Associate Technical Lead Member, MC, Development Technologies
WSO2 Inc. -
Hi Sumedha,
This is not an application level concurrency issue because how would you
explain,
1) With mysql_workbench while I have paused the program with a debug point.
2) There is concurrency associated with this scenario
3) The reverse works. When domain is given the ID is retrieved
My next
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20120705T103000Z
DTEND:20120705T113000Z
DTSTAMP:20120704T114938Z
ORGANIZER;CN=isu...@wso2.com:mailto:isu...@wso2.com
UID:gh8s770dtuh7ejnv8eggkij...@google.com
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20120705T103000Z
DTEND:20120705T113000Z
DTSTAMP:20120704T114938Z
ORGANIZER;CN=isu...@wso2.com:mailto:isu...@wso2.com
UID:gh8s770dtuh7ejnv8eggkij...@google.com
---
Carbon Snapshot Orbit #123 was successful.
---
This build was manually triggered by Nuwan Bandara.
Hi all,
This is a connection pooling issue. The reason for saying that is as
follows.
Here is the SQL = String sql = SELECT UM_ID FROM UM_TENANT WHERE
UM_DOMAIN_NAME=?
Consider the following control flow.
Control Flow
===
Connection dbConnection1 = getDBConnection();
Connection
Hi folks,
To provide some background, currently in JDBCTenantManager we have two maps
namely tenantIdDomainMap and tenantDomainIdMap to act as a cache when
fetching a tenant's id via domain name or vise-versa. Whenever we try to
obtain the id via domain for example, it first checks if that
Hi,
Reminder! We are using [1] at the moment.
[1] -
http://wso2.org/bamboo/artifact/WSO2CARBON-P2REPO/JOB1/build-143/P2-Repo/p2-repo
Regards,
Evanthika
On Fri, Jun 29, 2012 at 12:36 PM, Charitha Kankanamge chari...@wso2.comwrote:
Hi Dimuthu,
I cannot find the P2-repo associated with these
Tenant deletion is a very rare usecase. So, we need not complicate things
at this moment. Please note that deleted tenant IDs should not be reused.
So, my suggestion is, don't fix this.
On Wed, Jul 4, 2012 at 6:23 PM, Muhammed Shariq sha...@wso2.com wrote:
Hi folks,
To provide some
Hi shariq,
On Wed, Jul 4, 2012 at 6:23 PM, Muhammed Shariq sha...@wso2.com wrote:
Hi folks,
To provide some background, currently in JDBCTenantManager we have two
maps namely tenantIdDomainMap and tenantDomainIdMap to act as a cache when
fetching a tenant's id via domain name or vise-versa.
As for the case of the map filling up, the key value are very simple
string/int. Even millions of entries will result in very low memory
consumption. Millions of entries in this map translates to millions of
active tenants. There can be only one entry per tenant. So, once again, my
suggestion is
Yes, replacing the two maps with a bidimap were fixed about 1 year back.
This improved the efficiency since tenant id- domain domain - tenant id
lookups were earlier resulting in two sets of DB calls. With the bidimap,
we were able to load the info using one set of calls.
On Wed, Jul 4, 2012 at
When we set syncfalse/sync - what parameters can we use to set
threadPoolSize - by default threadPoolSize is one...
--
Thanks Regards,
Prabath
Mobile : +94 71 809 6732
http://blog.facilelogin.com
http://RampartFAQ.com
___
Dev mailing list
Hi,
I tried to create a tenant and then few users to test a scenario using Greg
packs obtained from [1].When i try to login as Tenant admin it fails
with following exception [2].
After that carbon theme comes up not the Greg.
[1]
Hi Dimuthu,
As we talked earlier, did you do the step of querying the same record using
the UM_ID directly, rather than the domain name, using the same connection.
Also, try the scenario with H2. I actually cannot think of a reason how the
connection pooling can have any effect on this, because
Dimuthu,
Can you confirm if the same method is being used in following thread
started by Shelan as well.
'[Dev] Cannot log into product after creating Tennants'.
On Wed, Jul 4, 2012 at 6:02 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi all,
This is a connection pooling issue. The
Hi,
I tried to create a user apart from Admin (this time not in a specific
tenant org but as a normal user). But again cannot log into the system
(Access denied) using newly create user and fails with following exception.
[2012-07-04 21:42:37,401] INFO
Hi Prabath,
The Infinispan Cache Manager that is available by default does not allow
you to configure many things. We have only made it possible to configure
the mandatory settings. Also, please note that the cache manager in Carbon
is pluggable and you also can extend/improve the existing cache
Hi all,
I think that might be inconsistent. Packs from build 255 an P2 Repo from
build 143 might be incompatible isn't it?
Thanks,
Senaka.
On Wed, Jul 4, 2012 at 6:24 PM, Evanthika Amarasiri evanth...@wso2.comwrote:
Hi,
Reminder! We are using [1] at the moment.
[1] -
Yes, unfortunately build 255 does not have p2 repo. That's why we were
repeatedly requesting a compatible repository to continue testing.
At least for next beta, please make sure to host a p2 repo.
On Wednesday, July 4, 2012, Senaka Fernando wrote:
Hi all,
I think that might be inconsistent.
Hi,
Please note $subject. I updated through admin console as well as the log4j
properties and it doesn't work.
Can someone have a look?
--
Regards,
Tharindu
blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
The previous error you got with the tenant admin seems to related to the
activation handler. Please check the product name in the carbon.xml with
the entry in the cloud-desc.xml.
The next error you have seen is due to a permission issue. Please make sure
that the role the 'test' user is assigned
---
Carbon Snapshot Platform #413 failed.
---
Code has been updated by denis, sinthuja, kasung, suho, subash.
No failed tests found, a possible compilation
Hi Charitha,
Triggered a build now. The p2-repo will be there by 8.00 am.
thanks,
dimuthu
On Thu, Jul 5, 2012 at 3:30 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi Charitha,
We will release Beta3 packs with a repo.
thanks,
dimuthu
On Wed, Jul 4, 2012 at 10:33 PM, Charitha
Hi Anjana,
Few minutes ago I recreated the scenario. Then I reverted um.core to use
dbcp pooling and now it works perfectly.
I know ndatasource is fantastic! But looks like there are some issues with
it.
This would be a blocker for our kernel release. Can we use a newer version
of ndatasource?
Hi Prabath,
I see this is a problem. I will work on setting a new parameter.
https://wso2.org/jira/browse/CARBON-13584
Created an issue to keep track of this.
thanks,
dimuthu
On Wed, Jul 4, 2012 at 8:16 PM, Prabath Siriwardena prab...@wso2.comwrote:
When we set syncfalse/sync - what
Hi,
On Wed, Jul 4, 2012 at 6:35 PM, Afkham Azeez az...@wso2.com wrote:
Tenant deletion is a very rare usecase. So, we need not complicate things
at this moment. Please note that deleted tenant IDs should not be reused.
So, my suggestion is, don't fix this.
+1.
thanks,
dimuthu
On Wed,
---
Carbon Snapshot P2-Repo #145 failed.
---
This build was manually triggered by Dimuthu Leelarathne.
No failed tests found, a possible compilation error.
Hi All,
While trying to verify the *API* feature of WSO2 Governance Registry,
realized that we need API-Manager features to be installed. The only
available P2 repo was [1] but in that, the API-Manager features were not
available. I have reported a JIRA at [2] to track this. We hope that these
One thing needs to be confirmed. In the rare case of a new tenant being
created with the ID of a deleted tenant, is there any security risk? I
mean, when we delete the old tenant, do we remove all deployment artifacts,
registry entries and so on? If not, there could be a security issue, where
the
The log level for the logge, and the thresholds of the relevant appenders
need to be set to TRACE for this to work.
On Wed, Jul 4, 2012 at 11:59 PM, Tharindu Mathew thari...@wso2.com wrote:
Hi,
Please note $subject. I updated through admin console as well as the log4j
properties and it
---
Carbon Snapshot Platform #414 was successful.
---
Code has been updated by tharindu, suho.
2002 tests in total.
Hi Dimuthu,
On Thu, Jul 5, 2012 at 4:56 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi Anjana,
Few minutes ago I recreated the scenario. Then I reverted um.core to use
dbcp pooling and now it works perfectly.
I know ndatasource is fantastic! But looks like there are some issues with
I tested this using ESB trunk build (22nd packs) and it works fine. I will
take the latest update and let you know.
On Thu, Jul 5, 2012 at 8:32 AM, Afkham Azeez az...@wso2.com wrote:
The log level for the logge, and the thresholds of the relevant appenders
need to be set to TRACE for this to
Hi Azeez,
On Thu, Jul 5, 2012 at 8:23 AM, Afkham Azeez az...@wso2.com wrote:
One thing needs to be confirmed. In the rare case of a new tenant being
created with the ID of a deleted tenant, is there any security risk? I
mean, when we delete the old tenant, do we remove all deployment
On Thu, Jul 5, 2012 at 9:42 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi Azeez,
On Thu, Jul 5, 2012 at 8:23 AM, Afkham Azeez az...@wso2.com wrote:
One thing needs to be confirmed. In the rare case of a new tenant being
created with the ID of a deleted tenant, is there any security
As shankar suggested ESB BPS are the ones which caused problems with
their internal thread pools.
I tested both CPU time and Thread live time per request per tenant for
Application Server and Data Services Server inside the
CarbonStuckThreadDetectionValve. I created few web services, web apps
and
On Jul 5, 2012 5:06 AM, Dimuthu Leelarathne dimut...@wso2.com wrote:
Hi,
On Wed, Jul 4, 2012 at 6:35 PM, Afkham Azeez az...@wso2.com wrote:
Tenant deletion is a very rare usecase. So, we need not complicate
things at this moment. Please note that deleted tenant IDs should not be
reused. So,
Hi Azeez,
On Thu, Jul 5, 2012 at 9:55 AM, Afkham Azeez az...@wso2.com wrote:
On Thu, Jul 5, 2012 at 9:42 AM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi Azeez,
On Thu, Jul 5, 2012 at 8:23 AM, Afkham Azeez az...@wso2.com wrote:
One thing needs to be confirmed. In the rare case of a
Hi all,
$subject? I tried to follow some articles on how to remotely monitor WSO2
products via JMX (with 3.2.3 packs) and it seems the instructions mentioned
in those articles are not working. One such article is [1]. But there is a
workaround which can be found at [2].
Charitha et al, please
Noted.
On Thu, Jul 5, 2012 at 10:40 AM, Amila Maha Arachchi ami...@wso2.comwrote:
Hi all,
$subject? I tried to follow some articles on how to remotely monitor WSO2
products via JMX (with 3.2.3 packs) and it seems the instructions mentioned
in those articles are not working. One such
What are the steps you followed?
On Thu, Jul 5, 2012 at 9:17 AM, Amani Soysa am...@wso2.com wrote:
I tested this using ESB trunk build (22nd packs) and it works fine. I will
take the latest update and let you know.
On Thu, Jul 5, 2012 at 8:32 AM, Afkham Azeez az...@wso2.com wrote:
The log
To set trace level logs in global level,
Go to - configure -Global Log4J Configuration set the log level to trace.
If you want to enable TRACE_APPENDER send trace level logs to trace.log
file you need to add TRACE_APPENDER to root logger in log4j.properties
file. Or set it from the logging ui
No, I went to Logging.
Searched for my package 'databridge' and changed the log level to TRACE.
This should work.
Azeez, if this does not work, then it's an issue. Following these steps
should just work.
On Thu, Jul 5, 2012 at 11:04 AM, Amani Soysa am...@wso2.com wrote:
To set trace level
On Thu, Jul 5, 2012 at 10:12 AM, Amila Maha Arachchi ami...@wso2.comwrote:
Hi Lasindu,
On Thu, Jul 5, 2012 at 9:56 AM, Lasindu Vidana Pathiranage
lasi...@wso2.com wrote:
As shankar suggested ESB BPS are the ones which caused problems with
their internal thread pools.
I tested both CPU
I tried this to org.apache.axis2 package to Trace and it looks like only
debug level logs are getting printed
On Thu, Jul 5, 2012 at 11:16 AM, Amani Soysa am...@wso2.com wrote:
Yeah I will test it and let you know
On Thu, Jul 5, 2012 at 11:12 AM, Tharindu Mathew thari...@wso2.comwrote:
No,
58 matches
Mail list logo
