[Dev] Package Management for Jaggery Front-end components
Hi all,Have we thought about the $subject? Bower.io [1] is a great example of front end package management. Too bad bower has a dependency over npm[2] and node[3].[1] -http://bower.io/[2] -http://npmjs.org/[3] -http://nodejs.org/Peace~---Chan (Dulitha Wijewantha)Software Engineer - Mobile DevelopmentWSO2MobileLean.Enterprise.Mobileware~Email duli...@wso2mobile.com ~Mobile +94712112165 ~Website dulithawijewantha.com ~Blog blog.dulithawijewantha.com ~Twitter @dulitharw___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Package Management for Jaggery Front-end components
Dulitha, Another interesting project is component framework by the same guy who developed the express framework(AFAICR, I mentioned this in a previous thread). Probably, we can set it up by pointing to a WSO2 component repo. [1] https://github.com/component/component On Sun, Nov 17, 2013 at 1:13 PM, Chan duli...@wso2.com wrote: Hi all, Have we thought about the $subject? Bower.io [1] is a great example of front end package management. Too bad bower has a dependency over npm[2] and node[3]. [1] - http://bower.io/ [2] - http://npmjs.org/ [3] - http://nodejs.org/ *Peace~* --- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2mobile.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulithawijewantha.com http://dulithawijewantha.com/* * ~Blog blog.dulithawijewantha.com http://dulichan.github.io/chan/* * ~Twitter @dulitharw https://twitter.com/dulitharw* -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com http://wso2.com* *email: ruch...@wso2.com ruch...@wso2.com, blog: ruchirawageesha.blogspot.com http://ruchirawageesha.blogspot.com, mobile: +94 77 5493444* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Package Management for Jaggery Front-end components
Hi, There is extensions repository for Jaggery[1] in WSO2 Github, where to checkin all jaggery extensions but still there is no extension to be found, So we can added those extenstion/tryout/modules in there such as repo for jaggery extension. (Extension has to be a p2 feature such as caramel[2],simple documentation with sample try out) [1] https://github.com/wso2/jaggery-extensions [2] https://github.com/wso2/caramel On Sun, Nov 17, 2013 at 1:13 PM, Chan duli...@wso2.com wrote: Hi all, Have we thought about the $subject? Bower.io [1] is a great example of front end package management. Too bad bower has a dependency over npm[2] and node[3]. [1] - http://bower.io/ [2] - http://npmjs.org/ [3] - http://nodejs.org/ *Peace~* --- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2mobile.com duli...@wso2mobile.com* * ~Mobile +94712112165 %2B94712112165* * ~Website dulithawijewantha.com http://dulithawijewantha.com/* * ~Blog blog.dulithawijewantha.com http://dulichan.github.io/chan/ * * ~Twitter @dulitharw https://twitter.com/dulitharw* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
Here is requirement list for the $subject,
*Basic things that will be in $subject ( jaggery test framework)*
- Testing Jaggery (.jag) API with function levels (simple as unit test)
- online
- Jaggery module testing under application (app/{appName}/module)
- Changing to any test case then only the test case file needs to be
updated [Script will remain the same]
- Application-independent. Test resource/spec of test will be inside the
application (app/{appName}/test)
- Easy to expand, maintain, and perpetuate. (Try to follow same JS frame
work structure such as *jasmine[1] *)
- Supportable with automation test framework with some configure
changing/pom/ant
- Should have low cost on maintaining
- Easy to write test (less time)
- REST/JSON report Supporting (Console commanding not implemented, As
above discussion)
- HTML Test coverage reporting
*Scopes for Framework*
Application-oriented Framework, Test resources for application will be
inside application
*Test framework type*
It will be 'Hybrid' as It will be following (Script Modularity Framework,
Library Architecture Framework and Structured Framework will be used in
implementation)
*Responsibilities of $subject*
- Defining the format in which to express expectations
- Running the tests which exercise the public interface (REST interfaces)
- Result with interface of JSON
- Interact with platform testing and build time with simple interface
(interface for REST client)
- Calling test suites and skipping test suit with changing test spec
(Test case js/jag )
- Executing the tests (Without console commanding)
- Reporting results of the test HTML interface also
If there I am missing any requirement for $subject, pls add it here,
Here is some more we will consider before writing $subject[2], Some trying
out existing JS test framework[3] for $subject for matter for comparison
and understating design on existing system.
[1] http://pivotal.github.io/jasmine/
[2]
http://madhukaudantha.blogspot.com/2013/11/what-to-be-know-about-test-framework.html
[3] http://madhukaudantha.blogspot.com/search/label/Test%20Framework
Thanks
On Fri, Nov 15, 2013 at 10:57 AM, Madhuka Udantha madh...@wso2.com wrote:
On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Functinalities like Server startup/shutdown, coverage generation and
result generation already implemented in WSO2 Test Automation framework. So
we need to reuse those functionalities in here.
Yap, sure we will be reusing those.
Having a Rest API to call tests scripts embedded in each jaggery app
would be nice addition. In that way we could easily integrate it with our
existing framework and use though out the platform.
And this framework should support for continuous integration. So
everything have to be executed without human interactions. So avoiding
command line test runners etc.. is required.
We will have json/RESTful API for app developer to run the test rather
command line, (No command line (cmd/ jaggery console)). Therefore there
will be html (web interface for app developer to run his/her test in
easily). We will avoid command line testing and will provide web interface
testing.
Thanks
Thanks,
Krishantha
On Thu, Nov 14, 2013 at 11:02 PM, Madhuka Udantha madh...@wso2.comwrote:
On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.comwrote:
Hi all,
While designing the test framework, its good if we can keep in mind
that jaggery2 product also underway.
Any thoughts?
Sure, will think.
Mainly test framework will coming for javascript(jag/js) testing so it
will be written where can be extended.
Regards,
UdaraR
On Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udantha madh...@wso2.comwrote:
Hi Krishantha and test automation team,
I would like to get your opinion on this task regard to
is there standard methodology on current testing framework where we
can added such testing framework or better to go on fully independent
model?
My thinking is,
- As it is application level testing frame work, better to work
with much independent of the current system
- Where application writer (developer) can run test for specific
application rather running all test for platform or product
- It will help to maintain both test framework with low cost
- Each test frame have it's own scope (such as
platform/product/appilcation). if not, complexity of the code and
system
will be increase but there will be API interface for interaction
among the
test framework.
- And I thought to have interface (simple REST interface) in
jaggery test frame work where current test framework also can interact
with
it into some extend.
Thanks
On Tue, Nov 12, 2013 at 5:57 PM, Madhuka Udantha madh...@wso2.comwrote:
Hi,
Still we do not have jaggery test framework even though there are
[Dev] Get the permissions list in carbon
Hi, I want to get the list/tree of permissions that are available in a carbon server(possibly as a tenant). I did check the UM api's and couldn't find anything relevant. Would appreciate any help. thanks, -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB 4.7.0 logs printed in high frequency when Message Broker is down
Heard that Ishara has fixed this for next release.
Thanks.
On Wed, Nov 13, 2013 at 6:43 AM, Lahiru Sandaruwan lahi...@wso2.com wrote:
Hi,
I experience $subject.([1]) I happened when we create a proxy to listen a
queue in Message Broker when the Message Broker is down.
IMO we should handle this better as this can grow log files to GBs in
minutes. Also logs become almost impossible to track for anything.
Thanks.
[1]
[2013-11-13 06:30:24,525] INFO - AMQConnection Unable to connect to
broker at tcp://localhost:5673
org.wso2.andes.transport.TransportException: Could not open connection
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:201)
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:71)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:110)
at
org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:616)
at org.wso2.andes.client.AMQConnection.init(AMQConnection.java:398)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:315)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
at
org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:629)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:824)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:706)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:496)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2013-11-13 06:30:24,527] ERROR - ServiceTaskManager Error acquiring a JMS
connection to : QueueConnectionFactory using JNDI properties :
{java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
java.naming.provider.url=repository/conf/jndi.properties,
transport.jms.ConnectionFactoryType=queue, serviceType=proxy}
javax.jms.JMSException: Error creating connection: Could not open
connection
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:325)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
at
org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:629)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:824)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:706)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:496)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.wso2.andes.AMQConnectionFailureException: Could not open
connection
at org.wso2.andes.client.AMQConnection.init(AMQConnection.java:475)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:315)
... 10 more
Caused by: org.wso2.andes.transport.TransportException: Could not open
connection
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:201)
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:71)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:110)
at
org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:616)
at org.wso2.andes.client.AMQConnection.init(AMQConnection.java:398)
... 11 more
[2013-11-13 06:30:24,529] ERROR - NativeWorkerPool Uncaught exception
org.apache.axis2.transport.jms.AxisJMSException: Error acquiring a JMS
connection to : QueueConnectionFactory using JNDI properties :
{java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
java.naming.provider.url=repository/conf/jndi.properties,
transport.jms.ConnectionFactoryType=queue, serviceType=proxy}
at
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
Peace~---Chan (Dulitha Wijewantha)Software Engineer - Mobile DevelopmentWSO2MobileLean.Enterprise.Mobileware~Email duli...@wso2mobile.com ~Mobile +94712112165 ~Website dulithawijewantha.com ~Blog blog.dulithawijewantha.com ~Twitter @dulitharwOn November 17, 2013 at 8:13:10 PM, Madhuka Udantha (madh...@wso2.com) wrote: Here is requirement list for the $subject,Basic things that will be in $subject ( jaggery test framework)Testing Jaggery (.jag) API with function levels (simple as unit test) - onlineI believe you meant API’s via HTTP - Since Goose.js discourage usage of .jag files to write APIs.Jaggery module testing under application (app/{appName}/module)One of the hard part of testing _javascript_ modules is that when we use closure base privacy everything gets harder to test. Since those members aren’t visible other than the js scope itself we might have to think about our total approach to modules itself.Changing to any test case then only the test case file needs to be updated [Script will remain the same]Application-independent. Test resource/spec of test will be inside the application (app/{appName}/test)I think we need to implement a Jaggery App build process that will neatly package a js app after testing and everything [http://yeoman.io/]. This would allow us to strip away the test suits when going into production.Easy to expand, maintain, and perpetuate. (Try to follow same JS frame work structure such asjasmine[1])Supportable with automation test framework with some configure changing/pom/antShould have low cost on maintainingEasy to write test (less time)REST/JSON report Supporting (Console commanding not implemented, As above discussion)HTML Test coverage reportingScopes for FrameworkApplication-oriented Framework, Test resources for application will be inside applicationTest framework typeIt will be 'Hybrid' as It will be following (Script Modularity Framework, Library Architecture Framework and Structured Framework will be used in implementation)Responsibilities of $subjectDefining the format in which to express expectationsRunning the tests which exercise the public interface (REST interfaces)Result with interface of JSONInteract with platform testing and build time with simple interface (interface for REST client)Calling test suites and skipping test suit with changing test spec (Test case js/jag )Executing the tests (Without console commanding)Reporting results of the test HTML interface alsoIf there I am missing any requirement for $subject, pls add it here,Here is some more we will consider before writing $subject[2], Some trying out existing JS test framework[3] for $subject for matter for comparison and understating design on existing system. [1]http://pivotal.github.io/jasmine/[2]http://madhukaudantha.blogspot.com/2013/11/what-to-be-know-about-test-framework.html[3]http://madhukaudantha.blogspot.com/search/label/Test%20FrameworkThanksOn Fri, Nov 15, 2013 at 10:57 AM, Madhuka Udanthamadh...@wso2.comwrote:On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweerakrishan...@wso2.comwrote:Functinalities like Server startup/shutdown, coverage generation and result generation already implemented in WSO2 Test Automation framework. So we need to reuse those functionalities in here.Yap, sure we will be reusing those.Having a Rest API to call tests scripts embedded in each jaggery app would be nice addition. In that way we could easily integrate it with our existing framework and use though out the platform.And this framework should support for continuous integration. So everything have to be executed without human interactions. So avoiding command line test runners etc.. is required.We will have json/RESTful API for app developer to run the test rather command line, (No command line (cmd/ jaggery console)). Therefore there will be html (web interface for app developer to run his/her test in easily). We will avoid command line testing and will provide web interface testing.ThanksThanks,KrishanthaOn Thu, Nov 14, 2013 at 11:02 PM, Madhuka Udanthamadh...@wso2.comwrote:On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayakeuda...@wso2.comwrote:Hi all,While designing the test framework, its good if we can keep in mind that jaggery2 product also underway.Any thoughts?Sure, will think.Mainly test framework will coming for _javascript_(jag/js) testing so it will be written where can be extended.Regards,UdaraROn Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udanthamadh...@wso2.comwrote:Hi Krishantha and test automation team,I would like to get your opinion on this task regard tois there standard methodology on current testing framework where we can added such testing framework or better to go on fully independent model?My thinking is,As it is application level testing frame work, better to work with much independent of the current systemWhere application writer (developer) can run test for specific application rather running all test for platform or productIt will help to maintain both test framework with low
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
Hi Dulitha,
Please find inline comments in below,
On Mon, Nov 18, 2013 at 9:21 AM, Chan duli...@wso2.com wrote:
*Peace~*
---
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
* ~Email duli...@wso2mobile.com duli...@wso2mobile.com*
* ~Mobile +94712112165 %2B94712112165*
* ~Website dulithawijewantha.com http://dulithawijewantha.com/*
* ~Blog blog.dulithawijewantha.com
http://dulichan.github.io/chan/*
* ~Twitter @dulitharw https://twitter.com/dulitharw*
On November 17, 2013 at 8:13:10 PM, Madhuka Udantha (madh...@wso2.com)
wrote:
Here is requirement list for the $subject,
*Basic things that will be in $subject ( jaggery test framework)*
- Testing Jaggery (.jag) API with function levels (simple as unit
test) - online
I believe you meant API’s via HTTP - Since Goose.js discourage usage of
.jag files to write APIs.
I means both HTTP level APIs as well as function APIs also
-
Jaggery module testing under application (app/{appName}/module)
One of the hard part of testing javascript modules is that when we use
closure base privacy everything gets harder to test.
Yap, some thing planing to cover up.
Since those members aren’t visible other than the js scope itself we might
have to think about our total approach to modules itself.
Testing framework will have consider scope different (js scope/etc..)
regard to testing. BTW js functionality test can be achieved with pure JS
test framework (Such as Jasmine).
In here Module testing refereed for application level modules.
- Changing to any test case then only the test case file needs to be
updated [Script will remain the same]
- Application-independent. Test resource/spec of test will be inside
the application (app/{appName}/test)
I think we need to implement a Jaggery App build process that will neatly
package a js app after testing and everything [http://yeoman.io/].
With interface of testing framework will allow to connect with building
process and executes app test while it is building.
This would allow us to strip away the test suits when going into
production.
Good point.
(To achieve this there can be some script or configuration to set at build
time)
Thanks for your feed back,
- Easy to expand, maintain, and perpetuate. (Try to follow same JS
frame work structure such as *jasmine[1] *)
- Supportable with automation test framework with some configure
changing/pom/ant
- Should have low cost on maintaining
- Easy to write test (less time)
- REST/JSON report Supporting (Console commanding not implemented,
As above discussion)
- HTML Test coverage reporting
*Scopes for Framework*
Application-oriented Framework, Test resources for application will be
inside application
*Test framework type*
It will be 'Hybrid' as It will be following (Script Modularity Framework,
Library Architecture Framework and Structured Framework will be used in
implementation)
*Responsibilities of $subject*
- Defining the format in which to express expectations
- Running the tests which exercise the public interface (REST
interfaces)
- Result with interface of JSON
- Interact with platform testing and build time with simple interface
(interface for REST client)
- Calling test suites and skipping test suit with changing test spec
(Test case js/jag )
- Executing the tests (Without console commanding)
- Reporting results of the test HTML interface also
If there I am missing any requirement for $subject, pls add it here,
Here is some more we will consider before writing $subject[2], Some trying
out existing JS test framework[3] for $subject for matter for comparison
and understating design on existing system.
[1] http://pivotal.github.io/jasmine/
[2]
http://madhukaudantha.blogspot.com/2013/11/what-to-be-know-about-test-framework.html
[3] http://madhukaudantha.blogspot.com/search/label/Test%20Framework
Thanks
On Fri, Nov 15, 2013 at 10:57 AM, Madhuka Udantha madh...@wso2.com
wrote:
On Fri, Nov 15, 2013 at 10:30 AM, Krishantha Samaraweera
krishan...@wso2.com wrote:
Functinalities like Server startup/shutdown, coverage generation and
result generation already implemented in WSO2 Test Automation framework. So
we need to reuse those functionalities in here.
Yap, sure we will be reusing those.
Having a Rest API to call tests scripts embedded in each jaggery app
would be nice addition. In that way we could easily integrate it with our
existing framework and use though out the platform.
And this framework should support for continuous integration. So
everything have to be executed without human interactions. So avoiding
command line test runners etc.. is required.
We will have json/RESTful API for app developer to run the test rather
command line, (No command line (cmd/ jaggery console)). Therefore
Re: [Dev] Dead lock detected in ESB while running integration tests
Thanks Miyuru, I will check the fix too.. On Fri, Nov 15, 2013 at 12:49 PM, Miyuru Wanninayaka miy...@wso2.comwrote: On Fri, Nov 15, 2013 at 12:29 PM, Miyuru Wanninayaka miy...@wso2.comwrote: Seems once proxy service deploy/undploy lock in axis2 config instead of synapse config, no more deadlocks :) I have to -private AxisConfiguration axisConfiguration = null; +private AxisConfiguration axisConfiguration = new AxisConfiguration(); because in MultiXMLConfigurationBuilderTest, it creates a synapse config without axisConfig which will cause NPE in synchronization block. I'm currently running tests with these changes. On Fri, Nov 15, 2013 at 10:37 AM, Miyuru Wanninayaka miy...@wso2.comwrote: May be for proxy service undeployment, synapse can lock on axis2 config instead of synapse config, which will avoid deadlocking. On Fri, Nov 15, 2013 at 10:22 AM, Miyuru Wanninayaka miy...@wso2.comwrote: I have observed this few times even without patch0002. When analyzed deadloak flow it seems hot deployment of main, fault sequences and deleting ESB artifacts from admin services triggers in parallel. in hot deployment, axis2 thread first get a lock of axis2 configuration and then calls synapse deployer.undeploy which will lock on synapse configuration. during admin service call, it will directly call synapse to undeploy artifacts which will first lock on synapse config and in case of proxy, it will cause related axis2 service to undeploy and try to acquire lock of axis2 config which will become a deadlock. I have modified abstract ESBIntegrationTest.cleanup() method to wait few seconds to let main and fault sequence to hot update. Seems deadlock does not happens after that. On Thu, Nov 14, 2013 at 10:17 PM, Miyuru Wanninayaka miy...@wso2.comwrote: Seems patch0002 causing deadlock. Once patch0002 removed from pack, tests are running without any issue. On Thu, Nov 14, 2013 at 9:31 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Integration tests hang at the early stage and following dead lock situation detected in ESB Alpha pack. Name: http-nio-9443-exec-19 State: BLOCKED on org.apache.axis2.engine.AxisConfiguration@510b02daowned by: pool-15-thread-1 Total blocked: 2 Total waited: 29 Stack trace: org.apache.axis2.engine.AxisConfiguration.removeService(AxisConfiguration.java:692) org.apache.synapse.config.SynapseConfiguration.removeProxyService(SynapseConfiguration.java:1037) - locked org.apache.synapse.config.SynapseConfiguration@73e64d34 org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.deleteProxyService(ProxyServiceAdmin.java:398) sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212) org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146) org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java: - Name: pool-15-thread-1 State: BLOCKED on org.apache.synapse.config.SynapseConfiguration@73e64d34 owned by: http-nio-9443-exec-19 Total blocked: 1 Total waited: 17 Stack trace: org.apache.synapse.config.SynapseConfiguration.getDefinedSequences(SynapseConfiguration.java:289) org.apache.synapse.deployers.SequenceDeployer.updateSynapseArtifact(SequenceDeployer.java:120) org.wso2.carbon.sequences.SequenceDeploymentInterceptor.updateSynapseArtifact(SequenceDeploymentInterceptor.java:49) org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.resetDefaultSequence(AbstractSynapseArtifactDeployer.java:584) org.apache.synapse.deployers.SequenceDeployer.updatingFaultAndMainWithOriginal(SequenceDeployer.java:181) org.apache.synapse.deployers.SequenceDeployer.undeploy(SequenceDeployer.java:150) org.apache.axis2.deployment.DeploymentEngine.unDeploy(DeploymentEngine.java:909) - locked org.wso2.carbon.core.CarbonAxisConfigurator@5497eb53 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:143) - locked org.wso2.carbon.core.CarbonAxisConfigurator@5497eb53 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
Re: [Dev] Dead lock detected in ESB while running integration tests
We have committed this fix and now ESB tests running fine. On Mon, Nov 18, 2013 at 10:54 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Thanks Miyuru, I will check the fix too.. On Fri, Nov 15, 2013 at 12:49 PM, Miyuru Wanninayaka miy...@wso2.comwrote: On Fri, Nov 15, 2013 at 12:29 PM, Miyuru Wanninayaka miy...@wso2.comwrote: Seems once proxy service deploy/undploy lock in axis2 config instead of synapse config, no more deadlocks :) I have to -private AxisConfiguration axisConfiguration = null; +private AxisConfiguration axisConfiguration = new AxisConfiguration(); because in MultiXMLConfigurationBuilderTest, it creates a synapse config without axisConfig which will cause NPE in synchronization block. I'm currently running tests with these changes. On Fri, Nov 15, 2013 at 10:37 AM, Miyuru Wanninayaka miy...@wso2.comwrote: May be for proxy service undeployment, synapse can lock on axis2 config instead of synapse config, which will avoid deadlocking. On Fri, Nov 15, 2013 at 10:22 AM, Miyuru Wanninayaka miy...@wso2.comwrote: I have observed this few times even without patch0002. When analyzed deadloak flow it seems hot deployment of main, fault sequences and deleting ESB artifacts from admin services triggers in parallel. in hot deployment, axis2 thread first get a lock of axis2 configuration and then calls synapse deployer.undeploy which will lock on synapse configuration. during admin service call, it will directly call synapse to undeploy artifacts which will first lock on synapse config and in case of proxy, it will cause related axis2 service to undeploy and try to acquire lock of axis2 config which will become a deadlock. I have modified abstract ESBIntegrationTest.cleanup() method to wait few seconds to let main and fault sequence to hot update. Seems deadlock does not happens after that. On Thu, Nov 14, 2013 at 10:17 PM, Miyuru Wanninayaka miy...@wso2.comwrote: Seems patch0002 causing deadlock. Once patch0002 removed from pack, tests are running without any issue. On Thu, Nov 14, 2013 at 9:31 PM, Krishantha Samaraweera krishan...@wso2.com wrote: Integration tests hang at the early stage and following dead lock situation detected in ESB Alpha pack. Name: http-nio-9443-exec-19 State: BLOCKED on org.apache.axis2.engine.AxisConfiguration@510b02daowned by: pool-15-thread-1 Total blocked: 2 Total waited: 29 Stack trace: org.apache.axis2.engine.AxisConfiguration.removeService(AxisConfiguration.java:692) org.apache.synapse.config.SynapseConfiguration.removeProxyService(SynapseConfiguration.java:1037) - locked org.apache.synapse.config.SynapseConfiguration@73e64d34 org.wso2.carbon.proxyadmin.service.ProxyServiceAdmin.deleteProxyService(ProxyServiceAdmin.java:398) sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212) org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110) org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146) org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java: - Name: pool-15-thread-1 State: BLOCKED on org.apache.synapse.config.SynapseConfiguration@73e64d34 owned by: http-nio-9443-exec-19 Total blocked: 1 Total waited: 17 Stack trace: org.apache.synapse.config.SynapseConfiguration.getDefinedSequences(SynapseConfiguration.java:289) org.apache.synapse.deployers.SequenceDeployer.updateSynapseArtifact(SequenceDeployer.java:120) org.wso2.carbon.sequences.SequenceDeploymentInterceptor.updateSynapseArtifact(SequenceDeploymentInterceptor.java:49) org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.resetDefaultSequence(AbstractSynapseArtifactDeployer.java:584) org.apache.synapse.deployers.SequenceDeployer.updatingFaultAndMainWithOriginal(SequenceDeployer.java:181) org.apache.synapse.deployers.SequenceDeployer.undeploy(SequenceDeployer.java:150) org.apache.axis2.deployment.DeploymentEngine.unDeploy(DeploymentEngine.java:909) - locked org.wso2.carbon.core.CarbonAxisConfigurator@5497eb53 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:143) - locked org.wso2.carbon.core.CarbonAxisConfigurator@5497eb53 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
[Dev] Generalizing endpoints in Automation Artifacts
Hi All, In Test Automation scenarios we need to use several types of artifacts to deploy resources to support the automation test. As such the automated tests are focusing different environments and different use cases we are facing some difficulties in reusing the artifacts in different environments due to hard-coded endpoints inside those artifacts. So we need to make all artifacts to be used in automated tests in a general way irrespective of the hard coded end point inside those artifacts. As a example if we have a Synapse which suppose to deploy as a car file we need to deploy the same car file in 1. Integration tests (Localhost based setup in general Integration test) 2. Platform Tests (Tests where executes against predetermined a target environment). In such a scenario we need to identify a method to use the same artifact in both test scenarios. Currently we are using a simple XML structure to look-up the end points in The issue we are facing here is either we need to keep artifacts for each environment separately or manually change each artifact before the test which is not practical. The main reason for that is we need to execute the same test with the same artifact in different environments under different configurations. So it is not practical to keep a separate artifact for each test run. Is there any approach we can come up with to generalize above scenario. Thank You, Dharshana. -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : dharsha...@wso2.com dharsha...@wso2.com Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94772202595 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Default Event Builders Event Formatters are created in CEP
Hi All, I have created two event stream definitions using stream-manager-config.xml file in CEP_HOME/repository/conf. streamDefinition name=stratos.agent.health.stats version=1.0.0 descriptionagent health stats/description nickNameagent health stats/nickName metaData /metaData correlationData /correlationData payloadData property name=health_description type=String/ property name=value type=double/ property name=member_id type=String / /payloadData /streamDefinition streamDefinition name=average_total_memory_stats version=1.0.0 descriptionaverage total memory stats/description nickNameaverage total memory stats/nickName metaData /metaData correlationData /correlationData payloadData property name=member_id type=String/ property name=count type=double/ /payloadData /streamDefinition After that I have created Event Builder, Execution Plan and Event Formatter using configuration files. After start the CEP, it create another two default event builders and one event formatter for newly created stream definitions. I have to delete default event formatter otherwise CEP will run in infinite loop. Any idea why CEP create default event builder and event formatter according to stream definitions ? -- Regards, Manula Chathurika Thantriwatte Software Engineer WSO2 Inc. : http://wso2.com lean . enterprise . middleware email : manu...@wso2.com / man...@apache.org phone : +94 772492511 blog : http://manulachathurika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Default Event Builders Event Formatters are created in CEP
Hi Manula, The behaviour of CEP should be to create a default event builder for a created stream. A default event formatter will be created only when an exported stream is created by the execution plan with 'Default Event Formatter' selected. You can disable automatic creation of an event formatter when specifying the query plan if needed. The reason for CEP creating default event builders, formatters is to make it easier for the user (So that they would not manually need to create event builders, event formatters for a basic usecase and can simply concentrate on the query). This is discussed in architecture@ thread in [1]. However, creation of default builders,formatters should not create an infinite loop unless you are plugging the output of a query to the input stream. Did you get any error when working with the default builders,formatters? If so, can you post it here, to get a better understanding.. :-) [1] http://mail.wso2.org/mailarchive/architecture/2013-October/013609.html Thanks, Lasantha On 18 November 2013 11:11, Manula Chathurika Thantriwatte manu...@wso2.comwrote: Hi All, I have created two event stream definitions using stream-manager-config.xml file in CEP_HOME/repository/conf. streamDefinition name=stratos.agent.health.stats version=1.0.0 descriptionagent health stats/description nickNameagent health stats/nickName metaData /metaData correlationData /correlationData payloadData property name=health_description type=String/ property name=value type=double/ property name=member_id type=String / /payloadData /streamDefinition streamDefinition name=average_total_memory_stats version=1.0.0 descriptionaverage total memory stats/description nickNameaverage total memory stats/nickName metaData /metaData correlationData /correlationData payloadData property name=member_id type=String/ property name=count type=double/ /payloadData /streamDefinition After that I have created Event Builder, Execution Plan and Event Formatter using configuration files. After start the CEP, it create another two default event builders and one event formatter for newly created stream definitions. I have to delete default event formatter otherwise CEP will run in infinite loop. Any idea why CEP create default event builder and event formatter according to stream definitions ? -- Regards, Manula Chathurika Thantriwatte Software Engineer WSO2 Inc. : http://wso2.com lean . enterprise . middleware email : manu...@wso2.com / man...@apache.org phone : +94 772492511 blog : http://manulachathurika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ESB 4.7.0 logs printed in high frequency when Message Broker is down
I've gone through the code. It seems what is fixed when the Message Broker
is down after a deployment of a proxy which use MB.
Thanks.
On Sun, Nov 17, 2013 at 9:14 PM, Lahiru Sandaruwan lahi...@wso2.com wrote:
Heard that Ishara has fixed this for next release.
Thanks.
On Wed, Nov 13, 2013 at 6:43 AM, Lahiru Sandaruwan lahi...@wso2.comwrote:
Hi,
I experience $subject.([1]) I happened when we create a proxy to listen a
queue in Message Broker when the Message Broker is down.
IMO we should handle this better as this can grow log files to GBs in
minutes. Also logs become almost impossible to track for anything.
Thanks.
[1]
[2013-11-13 06:30:24,525] INFO - AMQConnection Unable to connect to
broker at tcp://localhost:5673
org.wso2.andes.transport.TransportException: Could not open connection
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:201)
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:71)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:110)
at
org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:616)
at org.wso2.andes.client.AMQConnection.init(AMQConnection.java:398)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:315)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
at
org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:629)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:824)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:706)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:496)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2013-11-13 06:30:24,527] ERROR - ServiceTaskManager Error acquiring a
JMS connection to : QueueConnectionFactory using JNDI properties :
{java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
java.naming.provider.url=repository/conf/jndi.properties,
transport.jms.ConnectionFactoryType=queue, serviceType=proxy}
javax.jms.JMSException: Error creating connection: Could not open
connection
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:325)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38)
at
org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:629)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.createConnection(ServiceTaskManager.java:824)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.getConnection(ServiceTaskManager.java:706)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.receiveMessage(ServiceTaskManager.java:496)
at
org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:420)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.wso2.andes.AMQConnectionFailureException: Could not open
connection
at org.wso2.andes.client.AMQConnection.init(AMQConnection.java:475)
at
org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:315)
... 10 more
Caused by: org.wso2.andes.transport.TransportException: Could not open
connection
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:201)
at
org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:71)
at
org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:110)
at
org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:616)
at org.wso2.andes.client.AMQConnection.init(AMQConnection.java:398)
... 11 more
[2013-11-13 06:30:24,529] ERROR - NativeWorkerPool Uncaught exception
org.apache.axis2.transport.jms.AxisJMSException: Error acquiring a JMS
connection to : QueueConnectionFactory using JNDI properties :
{java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory,
Re: [Dev] WSO2 ESB 4.8.0 - Alpha Released !
Hi Evanthika et al., Please verify whether the issue reported at thread ESB 4.7.0 logs printed in high frequency when Message Broker is down is fixed in ESB 4.8.0. Thanks. On Fri, Nov 15, 2013 at 8:03 AM, Evanthika Amarasiri evanth...@wso2.comwrote: Yes Subash, This was identified and reported as a bug for this release. https://wso2.org/jira/browse/ESBJAVA-2358 https://wso2.org/jira/browse/ESBJAVA-2359 Evanthika On Thu, Nov 14, 2013 at 9:26 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Evanthika, In M5 packs, noticed that the default BAM mediation data publishing menu goes to a blank page (Refer [Monitor ESB from BAM 1.5.0] Mediation Data Publishing menu goes to a Blank Page !) and this is a blocker for people who wants to monitor ESB through BAM. Please check whether it is also fixed. On Wed, Nov 13, 2013 at 11:00 PM, Evanthika Amarasiri evanth...@wso2.com wrote: Noted Dushan, Evanthika On Wed, Nov 13, 2013 at 10:49 PM, Dushan Abeyruwan dus...@wso2.comwrote: Hi It seems like connectors are not updated correctly with the Alpha pack shared, anyway for QA process for 4.8.0 Alpha please do download the latest connectors from [1] [1]https://svn.wso2.org/repos/wso2/people/shafreen/connectors/ On Wed, Nov 13, 2013 at 8:16 PM, Shafreen Anfar shafr...@wso2.comwrote: Hi, ESB version 4.8.0 Alpha is available at, https://svn.wso2.org/repos/wso2/people/shafreen/ESB480/alpha/wso2esb-4.8.0.zip Connectors can be found in $ESB_HOME/repository/connectors -- Regards, *Shafreen* Software Engineer WSO2 Inc Mobile : 077-556-395-1 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks /subash *Subash Chaturanga* Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SS-1.1.0 pack for QA
Hi all, Please find the latest pack here. https://svn.wso2.org/repos/wso2/scratch/ss-dev/SS-1.1.0-QA/4/wso2ss-1.1.0.zip Reported Cassandra and HDFS bugs are fixed in this pack. Thanks, Bhathiya On Wed, Nov 13, 2013 at 5:14 PM, Bhathiya Jayasekara bhath...@wso2.comwrote: Hi all, Please find the pack URL below. https://svn.wso2.org/repos/wso2/scratch/ss-dev/SS-1.1.0-QA/2/wso2ss-1.1.0.zip Thanks, Bhathiya -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* *Phone: +94715478185 %2B94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax* -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com http://wso2.com* *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj http://www.linkedin.com/in/bhathiyaj* *Twitter: https://twitter.com/bhathiyax https://twitter.com/bhathiyax* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Get the permissions list in carbon
Hi Supun, Is this related to your AS-platform features task ? if so please properly document this one as a limitation and create an issue to track it from AS side. Thanks ! On Sun, Nov 17, 2013 at 11:15 PM, Supun Malinga sup...@wso2.com wrote: Hi Johan, thanks for the input. Since it's a api change we cannot patch it. +1 for doing it for the next kernel version. thanks, On Sun, Nov 17, 2013 at 11:01 PM, Johann Nallathamby joh...@wso2.comwrote: Currently we don't have such an API. Only way to get it would be to patch AuthorizationManager API. If what you want is Carbon permissions i guess this is the only way. Application wise custom permissions is a feature in the Identity Server road map. On Sun, Nov 17, 2013 at 8:59 PM, Supun Malinga sup...@wso2.com wrote: Hi, I want to get the list/tree of permissions that are available in a carbon server(possibly as a tenant). I did check the UM api's and couldn't find anything relevant. Would appreciate any help. thanks, -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Get the permissions list in carbon
Hi Sagara, Yes it is. Will do.. thanks, On Mon, Nov 18, 2013 at 12:52 PM, Sagara Gunathunga sag...@wso2.com wrote: Hi Supun, Is this related to your AS-platform features task ? if so please properly document this one as a limitation and create an issue to track it from AS side. Thanks ! On Sun, Nov 17, 2013 at 11:15 PM, Supun Malinga sup...@wso2.com wrote: Hi Johan, thanks for the input. Since it's a api change we cannot patch it. +1 for doing it for the next kernel version. thanks, On Sun, Nov 17, 2013 at 11:01 PM, Johann Nallathamby joh...@wso2.comwrote: Currently we don't have such an API. Only way to get it would be to patch AuthorizationManager API. If what you want is Carbon permissions i guess this is the only way. Application wise custom permissions is a feature in the Identity Server road map. On Sun, Nov 17, 2013 at 8:59 PM, Supun Malinga sup...@wso2.com wrote: Hi, I want to get the list/tree of permissions that are available in a carbon server(possibly as a tenant). I did check the UM api's and couldn't find anything relevant. Would appreciate any help. thanks, -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 -- Thanks Regards, *Johann Dilantha Nallathamby* Senior Software Engineer Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+9476950* Blog - *http://nallaa.wordpress.com http://nallaa.wordpress.com* -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services;http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How to add business processing logic to WSO2 Data Services Server?
Hello： As far as I know, WSO2 DSS always use stored process to handle business processing logic. However, there are several problems with this approach. If the process involves a variety of databases, it would be difficult to deal with. Even if the process involves only one database, it will will increase the burden on the database. If you replace the database, you need to re-write the stored procedure. Does anyone know how to add business processing logic to WSO2 DSS without stored process? stevegyc___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Configure Puppet master for Private PaaS
Use this as the puppet master (demo) AMI : ami-38fda86a client (carbon base) : ami-40f4a112 Thanks and regards, Thilina Piyasundara Systems Engineer M: 071-775-0006 WSO2, Inc. http://wso2.com/ lean . enterprise . middleware On Sun, Nov 17, 2013 at 11:19 AM, Nirmal Fernando nir...@wso2.com wrote: Thilina, that worked, thanks. But, now it seems like there's an issue with mismatching user-store databases. On Sun, Nov 17, 2013 at 9:08 AM, Thilina Piyasundara thili...@wso2.comwrote: Update the client AMI to : ami-40f4a112 The issue was a SSL conflict as the puppet agent was pre-installed on the client. As a solution I update the bootup script to remove all SSL certs of the puppet agent. When puppet restart after it will regenerate the SSL certs according to new configs. -- Updated - Run the demo AMI which included a puppetmaster in itself. AMI : ami-16cf9a44 User-data : EC2_KEY_PATH=pem_key_path,ACCESS_KEY=access_key,SECRET_KEY=secret_key,OWNER_ID=owner_id,AVAILABILITY_ZONE=availability_zone,SECURITY_GROUP=s2-demo,KEY_PAIR_NAME=keypair_name,DOMAIN=domain Then run the demo.sh it will configure the puppetmaster also. After that get the private_IP of the demo instance and use that IP for the client instances user-data. Client : AMI : ami-40f4a112 user-data : TENANT_RANGE=*,TENANT_ID=1,REPO_INFO_EPR=https://ip_of_the_demo :9445/services/RepositoryInformationService,CARTRIDGE_AGENT_EPR=https:// ip_of_the_demo:9447/services/CartridgeAgentService,PORTS=http:9763:8280|https:9443:8243,MIN=1,MAX=1,SERVICE=appserver,ALARMING_LOWER_RATE=0.2,ALARMING_UPPER_RATE=0.7,MAX_REQUESTS_PER_SEC=5,ROUNDS_TO_AVERAGE=2,SCALE_DOWN_FACTOR=0.25,DOMAIN=same_domain,PUPPETMASTER_IP=ip_of_the_demo When the client startup it should run puppet and install relevant service on the server. Thanks and regards, Thilina Piyasundara Systems Engineer M: 071-775-0006 WSO2, Inc. http://wso2.com/ lean . enterprise . middleware On Sat, Nov 16, 2013 at 4:48 PM, Nirmal Fernando nir...@wso2.com wrote: Hi Thilina, I'm getting following error at the client side log: /var/log/stratos-init.log. * Stopping puppet agent ...done. ^[[0;32minfo: Creating a new SSL key for 150516111345.appserver.paas.wso2.com^[[0m ^[[0;32minfo: Creating a new SSL certificate request for 150516111345.appserver.paas.wso2.com^[[0m ^[[0;32minfo: Certificate Request fingerprint (md5): xxx^[[0m ^[[0;32minfo: Caching certificate for 150516111345.appserver.paas.wso2.com^[[0m ^[[1;35merr: Could not retrieve catalog from remote server: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the time is out of sync on the server or client^[[0m ^[[0;33mwarning: Not using cache on failed catalog^[[0m ^[[1;35merr: Could not retrieve catalog; skipping run^[[0m Can you please check? === Great work Thilina! I'll try this out and will give you feedback. Can you please configure puppet modules for all other Carbon 4.2.0 based released products too? -- Forwarded message -- From: Thilina Piyasundara (JIRA) j...@wso2.org Date: Sat, Nov 16, 2013 at 9:40 AM Subject: [Carbon-jira] [jira] (PAAS-5) Configure Puppet master for Private PaaS To: carbon-j...@wso2.org Thilina Piyasundarahttps://wso2.org/jira/secure/ViewProfile.jspa?name=thilinap%40wso2.comedited a comment on [image: Task] PAAS-5 https://wso2.org/jira/browse/PAAS-5 *Configure Puppet master for Private PaaS*https://wso2.org/jira/browse/PAAS-5 Run the demo AMI which included a puppetmaster in itself. AMI : ami-16cf9a44 User-data : EC2_KEY_PATH=pem_key_path,ACCESS_KEY=access_key,SECRET_KEY=secret_key,OWNER_ID=owner_id,AVAILABILITY_ZONE=availability_zone,SECURITY_GROUP=s2-demo,KEY_PAIR_NAME=keypair_name,DOMAIN=domain Then run the demo.sh it will configure the puppetmaster also. After that get the private_IP of the demo instance and use that IP for the client instances user-data. Client : AMI : ami-14c49146 user-data : TENANT_RANGE=*,TENANT_ID=1,REPO_INFO_EPR=https://ip_of_the_demo :9445/services/RepositoryInformationService,CARTRIDGE_AGENT_EPR= https://lt;ip_of_the_demogt;:9447/services/CartridgeAgentService,PORTS=http:9763:8280|https:9443:8243,MIN=1,MAX=1,SERVICE=appserver,ALARMING_LOWER_RATE=0.2,ALARMING_UPPER_RATE=0.7,MAX_REQUESTS_PER_SEC=5,ROUNDS_TO_AVERAGE=2,SCALE_DOWN_FACTOR=0.25,DOMAIN=same_domain,PUPPETMASTER_IP=ip_of_the_demo When the client startup it should run puppet and install relevant service on the server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ Carbon-jira mailing list
