Please commit this. Too many build breaks from API Mgt team in the past few
days. Perhaps, we should have stabilized the existing build without APIMgt
and then added it to the main pom.
On Fri, Mar 30, 2012 at 11:29 AM, Nirmal Fernando nir...@wso2.com wrote:
Hi,
I see $Subject. Following diff
Hi Supun
I'm getting this error on webpage now when running my web app on
StratoesLive App server, but I'm not getting this error on the local App
server. A bug? Although I have debugged on my local machine I can't find
the error.
code- http://paste.org/47396
type Exception report
message
On Fri, Mar 30, 2012 at 11:32 AM, Afkham Azeez az...@wso2.com wrote:
Please commit this. Too many build breaks from API Mgt team in the past few
days. Perhaps, we should have stabilized the existing build without APIMgt
and then added it to the main pom.
Committed in r124497.
On Fri, Mar
Hi,
Looks like you have some file conversion there. From where these files are
being read?. If it needs to access the server file system, security manager
will block this.
Are you running your local setup with security manager enabled?
thanks,
On Fri, Mar 30, 2012 at 11:50 AM, Kasun Perera
RMs,
Please note that you have to send regular updates throughout the day until
the builds pass. By EoD today, all product builds should pass, and code
coverage reports should be available.
Azeez
On Fri, Mar 30, 2012 at 11:49 AM, Afkham Azeez az...@wso2.com wrote:
Folks,
Please note that only
Please attach the webapp if possible.
thanks,
On Fri, Mar 30, 2012 at 12:02 PM, Supun Malinga sup...@wso2.com wrote:
Hi,
Looks like you have some file conversion there. From where these files are
being read?. If it needs to access the server file system, security manager
will block this.
Another issue related to
products/apimgt/modules/jaggery-apps/api-provider-web/pom.xml fixed at
r124498.
On Fri, Mar 30, 2012 at 11:57 AM, Nirmal Fernando nir...@wso2.com wrote:
On Fri, Mar 30, 2012 at 11:32 AM, Afkham Azeez az...@wso2.com wrote:
Please commit this. Too many build breaks from
On Fri, Mar 30, 2012 at 12:02 PM, Supun Malinga sup...@wso2.com wrote:
Hi,
Looks like you have some file conversion there. From where these files are
being read?. If it needs to access the server file system, security manager
will block this.
Are you running your local setup with security
On Fri, Mar 30, 2012 at 12:15 PM, Nirmal Fernando nir...@wso2.com wrote:
Another issue related to
products/apimgt/modules/jaggery-apps/api-provider-web/pom.xml fixed at
r124498.
On Fri, Mar 30, 2012 at 11:57 AM, Nirmal Fernando nir...@wso2.com wrote:
On Fri, Mar 30, 2012 at 11:32 AM, Afkham
Hi all,
I'm looking into the G-Reg test failures right now. I will double check
this on a clean build. The BackwardAssociationHandlerTestCase can only
fail if dropins wont work properly. Anyway that was working fine and the
test was passing till today.
Regards,
Senaka.
On Fri, Mar 30, 2012 at
Senaka,
I don't want to know how to re-configure. Just give me a sample I can run.
You say two things. That it works OOTB and then I can easily re-configure.
I really did not see my artifact moving around in a distributed manner OOTB!
On Fri, Mar 30, 2012 at 12:55 PM, Senaka Fernando
Hi Tharindu,
This is dead obvious.
1. Create a new Service with the ServiceLifecycle as its lifecycle.
2. Promote the service.
3. Go and check inside /_system/governance/branches/..
Please note that as I mentioned in my e-mail this works only for services.
If you want this for any type of
Hi,
I will have a look tonight.
please don't share the pw publicly!. :)
thanks,
On Fri, Mar 30, 2012 at 1:28 PM, Kasun Perera kas...@opensource.lk wrote:
Hi supun
About reading files- I can Access other tables and read data on data
servise server?
What I'm doing here is read a PDF file
Please find the built artifacts in [1]
[1]http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-16/artifact
On Fri, Mar 30, 2012 at 12:09 PM, Bamboo cbuil...@wso2.org wrote:
[image: Failed] WSO2
Carbonhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON/›
Somethings we need to consider for the future in the Stratos SPI will
include the ability to register a custom image/LXC by a tenant. When this
is done, it should appear as a service under that tenant's services list on
the home page, and we should also provide the ability to plugin a
management
Hi all,
From the discussion we had bit earlier, Thilina suggested that a nightly
build at a fixed time in the night would reduce some unpredictability
associated.
How about 9.00PM IST ?
If we can write a script to figure out the last commit to the failed
component, we can send a SMS to the
Someone has commit rights to the frozen trunk, please apply the
following diff at components/apimgt.
Index:
org.wso2.carbon.apimgt.usage/org.wso2.carbon.apimgt.usage.analyzer/pom.xml
===
---
Hi,
how about 12 pm , 1 am. (off-peak).
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Fri, Mar 30, 2012 at 1:47 PM, Afkham Azeez az...@wso2.com wrote:
On Fri, Mar 30, 2012 at 12:43 PM, Nuwan Bandara nu...@wso2.com wrote:
Hi Azeez,
We need to continue work on APIManger, hence we will remove
the relevant components from the build modules. So API product components
wont
+1 for 12 pm.
Regards
Nandika
On Fri, Mar 30, 2012 at 2:31 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
how about 12 pm , 1 am. (off-peak).
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
On Fri, Mar 30, 2012 at 2:32 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
On Fri, Mar 30, 2012 at 1:47 PM, Afkham Azeez az...@wso2.com wrote:
On Fri, Mar 30, 2012 at 12:43 PM, Nuwan Bandara nu...@wso2.com wrote:
Hi Azeez,
We need to continue work on APIManger, hence we will remove
The call from Agent to AgentManagementService should be registerAgent. Not
registerWN.
There is also an autoscaler component in the LB which calls the
AutoscalerService if necessary.
Also, it is still not clear to me how the route addition part works. Is
that depicted in the diagram? Can we have
On Fri, Mar 30, 2012 at 2:57 PM, Damitha Kumarage dami...@wso2.com wrote:
An example of such a custom image could be a mashup of our existing
services for example as/ms etc correct?.
My thoughts were. we provide certain libraries, tools etc. for the user to
create an AMI/LCX etc. and then
---
WSO2 Carbon platform #41 was successful.
---
This build was manually triggered by BambooBuilder.
2069 tests in total.
---
WSO2 Carbon Kernel #143 failed.
---
Code has been updated by amani.
No failed tests found, a possible compilation error.
Hi All,
Please ignore this as we manually stopped the kernel build to run the
products build.
Regards,
SanjayaV.
On Fri, Mar 30, 2012 at 3:09 PM, Bamboo cbuil...@wso2.org wrote:
[image: Failed] WSO2
Carbonhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON/›
Hi,
I am - 0 for this. There are some negative effects of increasing session
timeout.
1) Objects we keep in the session can grow. This will be multiplied by the
number of users with active sessions
2) Security risk is marginally increase.
tx,
dimuthu
On Fri, Mar 30, 2012 at 3:26 PM, Amila
On Thu, Mar 29, 2012 at 10:16 PM, Zana ILHAN zanail...@gmail.com wrote:
Perhaps. I should ask my question like that. Is there a way to create a
proxy service to the discovered services on my ESB server.
http://wso2.org/library/articles/2011/08/rediscover-soa-wso2-carbon-wsdiscovery#iter3
I think Admin Console is most of the time used when doing Demos. In such
cases security is not a problem.
For real production development it has to use Developer Studio.
thanks,
Amila.
On Fri, Mar 30, 2012 at 3:34 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:
Hi,
I am - 0 for this. There
Also to avoid declaring the dependencies and versions multiple times, where
there exists dependencies defined multiple times in a pom with different
versions.
I have already fixed all these maven3 violations. Will commit these after
building with tests. So do *NOT* work on fixing these now. Just
---
WSO2 Carbon Products #17 failed.
---
This build was manually triggered by BambooBuilder.
No failed tests found, a possible compilation error.
Hi all,
Just completed building the whole trunk (after taking updates starting from
Orbit and G-Reg build passes with tests). Looking forward to the next set
of builds.
Thanks,
Senaka.
On Fri, Mar 30, 2012 at 1:34 PM, Charith Wickramarachchi
char...@wso2.comwrote:
Please find the built
Hi,
I get the following error when running integration tests in GS. This
happens in windows environment. I think this has been reported in another
thread. However the products works perfectly in this case.
Tests run: 65, Failures: 1, Errors: 0, Skipped: 64, Time elapsed: 81.246
sec FAILURE!
There is this little known useful feature where you can enable OSGi level
debug logs by doing, wso2server.sh -DenableOsgiDebug. Is this working after
the Tomcat OSGification work?
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation;
So the GS product does not start within 1m 20s. Is that normal? If so you
could try increasing the timeout. Set it to 30.
On Fri, Mar 30, 2012 at 4:57 PM, Dilshan Edirisuriya dils...@wso2.comwrote:
8
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member;
On Fri, Mar 30, 2012 at 1:14 PM, Senaka Fernando sen...@wso2.com wrote:
Hi Tharindu,
This is dead obvious.
:O :) i'll figure it out the next time. Thanks.
1. Create a new Service with the ServiceLifecycle as its lifecycle.
2. Promote the service.
3. Go and check inside
Yes I tried with a higher value like this. In that case it halts for more
time and generates the same error.
On Fri, Mar 30, 2012 at 5:04 PM, Afkham Azeez az...@wso2.com wrote:
So the GS product does not start within 1m 20s. Is that normal? If so
you could try increasing the timeout. Set it
Have you got Emma coverage enabled? Is the kernel up to date? Possible
reasons could be Emma issues dropins not working. Both have been fixed in
the kernel.
On Fri, Mar 30, 2012 at 5:22 PM, Dilshan Edirisuriya dils...@wso2.comwrote:
Yes I tried with a higher value like this. In that case it
Yes I took the latest changes in the kernal according to the previous mail.
Now doing a clean svn up. Hope this resolve the issue.
Thanks.
On Fri, Mar 30, 2012 at 5:31 PM, Afkham Azeez az...@wso2.com wrote:
Have you got Emma coverage enabled? Is the kernel up to date? Possible
reasons could
Hi Subash,
Can you have a look into this? I tried this out with a build starting from
orbit - kernel - platform, and was unable to reproduce.
Thanks,
Senaka.
--
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache
Sorry for the false alarm - this work fine - after taking an up from
service-mgt.. Earlier I took an up from platform level and seems like I
have missed some updates..
Thanks regards,
-Prabath
On Fri, Mar 30, 2012 at 6:13 PM, Prabath Siriwardena prab...@wso2.comwrote:
[ERROR] Failed to
---
WSO2 Carbon Products #18 failed.
---
This build was manually triggered by BambooBuilder.
6/405 tests failed, 2 failures were new.
Hi All,
Here's a summary of test failures
1. *ESB*
There was an issue in esb doc generation. Ishan has already fixed this in
r124510.
2. *GREG *
Seneka has commented out the failures and created
https://wso2.org/jira/browse/REGISTRY-717
3. *BRS*
Ishara has commented out the BRS failures
Hi Senaka,
Should not these failures reported as CARBON jira instead of product
specific JIRA? Have we changed our process of reporting JIRAs in C4
release? Or am I missing something?
Thanks,
Charitha
On Friday, March 30, 2012, Senaka Fernando wrote:
FYI,
Hi Subash, Vijitha,
Please test this on a clean M2 repo, and before you start to compile edit
the POM in the integration tests for G-Reg and make sure you enable the
excluded tests. If we can reproduce this issue, it shouldn't be hard figure
out how this broke.
Thanks,
Senaka.
On Fri, Mar 30,
Hi Tharindu,
:-)... Anyway, could you briefly outline what you expected, so that Janaka
and the others can make sure that the OOTB experience can capture a
requirement similar to the one you had. I believe that we might be having
80% of what you want but the last mile is always the toughest part,
---
Developer-Studio Eclipse-Tools #25 failed.
---
Code has been updated by chathuri.
No failed tests found, a possible compilation error.
Hi Azeez,
According to [1], build is successful. Currently developer studio does not
have test cases implemented. It seems bamboo expecting test cases and
that's why we are getting build fail message. We will try to remove that
option from bamboo for the moment and add test cases in the future.
+1 for nohup.
I used it in our production servers in the university for several weeks
without any problem.
Saludos,
Ing. Jorge Infante Osorio.
J´Dpto Soluciones SOA.
CDAE.
Fac. 5.
UCI.
De: dev-boun...@wso2.org [mailto:dev-boun...@wso2.org] En nombre de Sameera
Jayasoma
Enviado
Nice work Pradeeban. Thanks for taking up this task fixing all these
problems which were lingering for some time.
Thanks
Azeez
On Fri, Mar 30, 2012 at 8:52 PM, Kathiravelu Pradeeban
pradee...@wso2.comwrote:
The attached patch fixes all the maven3 warnings and bad practices found
in
Hi All,
The latest product build is running at [1] and the following products which
were broken in the previous build is now building successfully. Up to this
point
IS, Manager, ESB, AS, GREG, BPS and BRS builds have completed successfully.
[1]
---
WSO2 Carbon Products #21 failed.
---
This build was manually triggered by BambooBuilder.
1/468 tests failed.
Hi DSS RMs,
The dss distribution is failing. I could reproduce this locally as well.
Please have a look. Below is the error log.
[INFO] WSO2 Stratos DSS - Distribution ... FAILURE [28.175s]
[INFO] WSO2 DSS - Integration Tests .. SKIPPED
[INFO] WSO2 DSS -
---
WSO2 Carbon Products #24 was successful.
---
This build was manually triggered by BambooBuilder.
17 tests in total.
Hi Azeez, chathuri,
It's done!
Thanks and Regards,
Harshana
On Mar 30, 2012 12:21 PM, Chathuri Wimalasena chath...@wso2.com wrote:
Hi Azeez,
According to [1], build is successful. Currently developer studio does not
have test cases implemented. It seems bamboo expecting test cases and
Good job everybody! Thanks SanjayaV. Let's keep svn frozen until coverage
framework is integrated we get about 3 successive successful builds.
--
Afkham Azeez
Sent from my phone
On Mar 31, 2012 5:28 AM, Dimuthu Leelarathne dimut...@wso2.com wrote:
Hi all,
This is great. Good job everybody!
Thanks Harshana!
--
Afkham Azeez
Sent from my phone
On Mar 31, 2012 4:40 AM, Harshana Martin harsh...@wso2.com wrote:
Hi Azeez, chathuri,
It's done!
Thanks and Regards,
Harshana
On Mar 30, 2012 12:21 PM, Chathuri Wimalasena chath...@wso2.com wrote:
Hi Azeez,
According to [1], build is
On Fri, Mar 30, 2012 at 9:51 PM, Afkham Azeez az...@wso2.com wrote:
Nice work Pradeeban. Thanks for taking up this task fixing all these
problems which were lingering for some time.
+1. Nice work!!
--Pradeep
___
Dev mailing list
Dev@wso2.org
---
WSO2 Carbon platform #44 failed.
---
Code has been updated by pradeeban, sanjayav.
2/1705 tests failed.
Ok. Own up. Who broke the Synapse test cases? These are Synapse REST API
tests. Udayanga and the API mgt folks - are you guys making changes to
Synapse?
On Sat, Mar 31, 2012 at 8:42 AM, Bamboo cbuil...@wso2.org wrote:
[image: Failed] WSO2
Hi all,
I had an issue while trying CXF handler samples due to javax.xml.soap
package. In Carbon, currently we get javax.xml.soap api from geronimo-saaj
api bundle and the saaj implementation is coming from axis2-saaj. But CXF
works properly only with the JDK implementation of javax.xml.soap.
In
---
WSO2 Carbon Kernel #144 was successful.
---
This build occurred because it is a dependant of
WSO2CARBON-CARBONKERNELBUILD-63.
2790 tests in total.
62 matches
Mail list logo
