The only way to properly do this is to write stats to the ConfigRegistry
from time to time. Then again, we have BAM server which shows all the
accumulated statistics, so this will be redundant.
On Tue, Apr 3, 2012 at 10:29 AM, Charitha Kankanamge chari...@wso2.comwrote:
I think this is the
On Tue, Apr 3, 2012 at 4:25 AM, Samisa Abeysinghe sam...@wso2.com wrote:
On Mon, Apr 2, 2012 at 8:38 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
Pre alpha 1 pack of WSO2 API Manager can be downloaded from -
http://people.wso2.com/~sumedha/builds/am/02-04-2012/wso2am-1.0.0-SNAPSHOT.zip
A
The failure is in the Stratos CEP build
On Tue, Apr 3, 2012 at 12:00 PM, Afkham Azeez az...@wso2.com wrote:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (dist)
on project wso2stratos-cep: Failed to create assembly: File to filter not
I am looking into this.
On Tue, Apr 3, 2012 at 12:01 PM, Afkham Azeez az...@wso2.com wrote:
The failure is in the Stratos CEP build
On Tue, Apr 3, 2012 at 12:00 PM, Afkham Azeez az...@wso2.com wrote:
[ERROR] Failed to execute goal
On Tue, Apr 3, 2012 at 12:00 PM, Afkham Azeez az...@wso2.com wrote:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (dist)
on project wso2stratos-cep: Failed to create assembly: File to filter not
found:
On Tue, Apr 3, 2012 at 11:33 AM, Afkham Azeez az...@wso2.com wrote:
The only way to properly do this is to write stats to the ConfigRegistry
from time to time. Then again, we have BAM server which shows all the
accumulated statistics, so this will be redundant.
In current BAM2 we have tested
Don't we have other data like this we lose when the tenant unloads? We
should persist them all as needed. Maybe not in the registry, possibly in
the file system.
If we recover the deployed services through the file system, we also should
have the similar approach of recovery/persistence for any
At some point we need to have a hook out to an approval process to
approve API keys. For example, I apply, but we want to vet users, or
integrate into a marketing campaign and BANT qualify before we approve
their use of our APIs.
When there is an approval process for an API key, there needs to be
Hi all,
We still haven't decided on version for next ESB release which is based on
carbon 4.0.0.
Latest released ESB version is 4.0.3 and next release will not have huge
changes to consider as 5.0.0.
I'm thinking about 4.[1-5].0
WDYT?
--
Thanks,
Miyuru
we are look in to the issue.
Regards,
Chamara Silva
On Tue, Apr 3, 2012 at 3:07 PM, Charitha Kankanamge chari...@wso2.comwrote:
On Tue, Apr 3, 2012 at 2:54 PM, Charitha Kankanamge chari...@wso2.comwrote:
Hi folks,
I executed system test framework against
Hi,
I also got this error in AS pack from
http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-24/. I did not get this
when starting server for the first time, but the second and third time. Did
not get it afterwards. Note that I have created some data services and data
sources in AS.
[2012-04-03
Get this error in AS, with some data services created on it.
[2012-04-03 15:00:46,312] INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent}
- Registry Mode: READ-WRITE
[2012-04-03 15:00:46,475] ERROR {org.wso2.carbon.core.internal.
CarbonCoreDataHolder} - Before
Hi Nirodha,
On Tue, Apr 3, 2012 at 3:29 PM, Nirodha Pramod niro...@wso2.com wrote:
Get this error in AS, with some data services created on it.
Does it function properly without dataservices?? and did you get this issue
in DSS pack as well?
[2012-04-03 15:00:46,312] INFO
Hi,
On Tue, Apr 3, 2012 at 3:31 PM, Aparna Karunarathna apa...@wso2.com wrote:
Hi,
SandeshaModule loading error message can be seen in the GReg when start
the server on second time.
TID: [0] [WSO2 Governance Registry] [2012-04-03 14:09:02,543] ERROR
{org.apache.sandesha2.SandeshaModule}
oauthService mediator seems not working in this ESB
Message in ESB Mgt console:
Problems detected in the provided configuration:
- OAuthProxy [Proxy]: Unknown mediator referenced by configuration element
: {http://ws.apache.org/ns/synapse}oauthService
Remove faulty items and continue?
log:
This is not a Bamboo specific error. I also experienced this when I did a
full build.
On Tue, Apr 3, 2012 at 2:54 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi all,
Bamboo job 32 is failing with the following error. Please find logs at
Any update on P2 repo?
/Charitha
On Tue, Apr 3, 2012 at 4:23 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
please create Carbon JIRAs. you dont have to send mails to this thread.
thanks,
--Pradeep
___
Dev mailing list
Dev@wso2.org
On Tue, Apr 3, 2012 at 11:37 AM, Vijitha Kumara viji...@wso2.com wrote:
Thanks AmilaJ, no worries :)
I'll try the patch locally...
Vijitha, did the patch worked ? Please update the respective GReg
integration failure thread as well.
On Tue, Apr 3, 2012 at 11:29 AM, Amila Jayasekara
Hi,
We are seeing the following warnings at the server startup.
[2012-04-03 17:15:10,222] WARN
{org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator} - We don't
support method overloading. Ignoring [removeTrustedService]
Thanks,
Charitha
Issue fixed. Thanks for the pointing out.
Regards,
Chamara Silva
On Tue, Apr 3, 2012 at 3:08 PM, Chamara Silva cham...@wso2.com wrote:
we are look in to the issue.
Regards,
Chamara Silva
On Tue, Apr 3, 2012 at 3:07 PM, Charitha Kankanamge chari...@wso2.comwrote:
On Tue, Apr 3, 2012 at
Hi,
I need to track the Configuration Context Service inside auto scale
mediator component. I tried with scr reference method and it failed. But i
applied same mechanism for Tenant aware LB Endpoint and it was successful.
How can i track Configuration Context Service inside mediator? Actually i
On 3 April 2012 17:10, Denis Weerasiri de...@wso2.com wrote:
A sample configuration would be
proxy name=TestProxy transports=https http startOnLoad=true
trace=disable
target
inSequence
log level=full/
property name=messageType value=application/xml
Sameera has provided a patch [1] and these test cases already on Axis2
trunk. If you have any additional modification please let me know.
[1] - https://issues.apache.org/jira/browse/AXIS2-5235
Thanks !
On Tue, Apr 3, 2012 at 8:49 PM, Afkham Azeez az...@wso2.com wrote:
Please make sure that
On Tue, Apr 3, 2012 at 6:41 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi,
I need to track the Configuration Context Service inside auto scale
mediator component. I tried with scr reference method and it failed. But i
applied same mechanism for Tenant aware LB Endpoint and it was
This is a test email generated by Bamboo.
If you receive this email, your mail server settings on Bamboo are correct.
Thanks,
Bamboo
http://builder4.us1.wso2.org:/bamboo
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
This is a test email generated by Bamboo.
If you receive this email, your mail server settings on Bamboo are correct.
Thanks,
Bamboo
http://builder4.us1.wso2.org:/bamboo
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Tue, Apr 3, 2012 at 9:34 PM, Charith Wickramarachchi char...@wso2.comwrote:
Hi ,
The Plans in Bamboo are Configured to Send mails for every build failure
and 1st Successful build. Idea is to send the minimal number of mails to
the public mail list.
So in our case now all the plans are
Hi All ,
For Message Broker We use Cassandra feature to startup a Cassandra server
instance with the broker as it uses Cassandra as the underlying storage.
This is fine when broker is running as a standalone broker.
But When we enable clustering we need to disable this. Where using the MB
Hi,
We are experiencing a compilation failure in Kernel (Build #153). Please
have a look. Please be noted that
we have not received the mail from bamboo due to the configuration problem
on the mail server.
http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-153
This is a test email generated by Bamboo.
If you receive this email, your mail server settings on Bamboo are correct.
Thanks,
Bamboo
http://builder4.us1.wso2.org:/bamboo
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Tue, Apr 3, 2012 at 10:46 PM, Charitha Kankanamge chari...@wso2.comwrote:
Btw, I'm on windows.
Getting the same exceptions in Ubuntu also.
Thanks,
Yumani
--
Yumani Ranaweera
Associate Technical Lead - QA
WSO2, Inc. - http://wso2.org
Email : yum...@wso2.com
Cell: +94 077 7795242
Hi,
You cannot get the CarbonContext of other tenants, because this is
considered as a security threat. Can you give more details about your use
case?
thanks,
dimuthu
On Mon, Apr 2, 2012 at 3:48 PM, metin d met...@yahoo.com wrote:
When I call CarbonContext.getCurrentContext(), it returns
This is a test email generated by Bamboo.
If you receive this email, your mail server settings on Bamboo are correct.
Thanks,
Bamboo
http://builder4.us1.wso2.org:/bamboo
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
I am looking into this.
Regards,
Amani
On Tue, Apr 3, 2012 at 7:19 PM, Kasun Weranga kas...@wso2.com wrote:
Hi all,
I am getting this error while building trunk/features/logging-mgt
[INFO] WSO2 Carbon - Logging Management Feature Aggregator Module SUCCESS
[0.484s]
[INFO] WSO2 Carbon -
GReg update.
1. Build status
All registry related carbon kernel and component stuff builds with
tests.
The product builds successfully with all integration tests. * But facing
to sudden and quite rare random integration failures(two of which we have
currently excluded ) .
2. Test status -
Its fixed now.
On Wed, Apr 4, 2012 at 10:09 AM, Amani Soysa am...@wso2.com wrote:
I am looking into this.
Regards,
Amani
On Tue, Apr 3, 2012 at 7:19 PM, Kasun Weranga kas...@wso2.com wrote:
Hi all,
I am getting this error while building trunk/features/logging-mgt
[INFO] WSO2 Carbon -
CSG update.
1. Build status
Product built fine.
2. Test status - any failing commented out tests. Jira links if so
Currently no integration tests are for CSG. Ramith is working on them and I
will also start working on them once my non RD term is over.
3. Code coverage - current coverage
The following test failure is something I have been seeing from time to
time on my machine.
[INFO] Surefire report directory:
/Users/azeez/projects/wso2/org/carbon/platform/trunk/dependencies/synapse/2.1.0-wso2v6/modules/transports/core/nhttp/target/surefire-reports
On Wed, Apr 4, 2012 at 9:43 AM, Yumani Ranaweera yum...@wso2.com wrote:
On Tue, Apr 3, 2012 at 10:46 PM, Charitha Kankanamge chari...@wso2.comwrote:
Btw, I'm on windows.
Getting the same exceptions in Ubuntu also.
But its only async_jaxws that failed for me. jaxrs_basic worked and
1. ESB successfully builds with the integration tests.
Unable to apply security to services. This is the same issue discussed
in the mail thread Can not apply security policies to proxy services in
SLive.
2. Some integration tests have been commented out.
in esb-samples - Sample600Test.
Hi all,
Right now we only have 3 failing test cases and this is constant, so we are
going to unfreeze the SVN now.
Whenever a change is done please run the full build with test cases and
commit.
thanks,
dimuthu
--
Dimuthu Leelarathne
Technical Lead
WSO2, Inc. (http://wso2.com)
email:
On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka miy...@wso2.com wrote:
Hi all,
We still haven't decided on version for next ESB release which is based on
carbon 4.0.0.
Latest released ESB version is 4.0.3 and next release will not have huge
changes to consider as 5.0.0.
I'm thinking
Hi,
On Wed, Apr 4, 2012 at 11:05 AM, Prabath Abeysekera praba...@wso2.comwrote:
DSS Updates:
On Tue, Apr 3, 2012 at 8:41 PM, Afkham Azeez az...@wso2.com wrote:
RMs,
Please send in a report of the current state of your products. This
should include;
1. Build status
DSS (both product
Hi Charith,
On Mon, Apr 2, 2012 at 11:52 PM, char...@wso2.com wrote:
Author: charith
Date: Mon Apr 2 14:22:36 2012
New Revision: 124600
URL: http://wso2.org/svn/browse/wso2?view=revrevision=124600
Log:
commenting SchemaTestCase
When commenting a test, unless there is a very specific
Regarding MB,
1. Build is fine.
2. As the Message Box component was removed from the oncoming release of
MB, most of the tests became irrelevant and was removed. Charith and Shammi
and I are in the process of writing new test cases for new Andes component
and others.
3. Will update the status of
This is a test email generated by Bamboo.
If you receive this email, your mail server settings on Bamboo are correct.
Thanks,
Bamboo
http://builder4.us1.wso2.org:/bamboo
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
BRS update.
1. BRS successfully builds with the integration tests.
2. Some integration tests have been commented out.
GreetingServiceDeploymentTestCase ( Random error occur in Bamboo )
CallChargingTestCase
3. Has posted overall code coverage details in his mail BRS Code Coverage.
4.
47 matches
Mail list logo