[Dev] Jaggery 2 status update
we are on process of testing node module load system and changing nashorn script engine environment to work with jaggery 2 -- Thanks Best Regards, *Buddhi Nipun Mihara* Software Engineer(intern) WSO2, Inc.:http://wso2.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] UX Patterns Document
I created a document with $subject [1], and review App Factory UI. The result is @ [2]. With this effort I tried to improve the UX of App Factory. So most of the arguments I made @ [2] get's a theoretical backup from [1]. Only 1/8 th of the UI are covered at this point. [1] - https://docs.google.com/a/wso2.com/document/d/1HGOkNm4SNUFs0OJB9dqN9AST-ob0XjUW-WY1GVelfuI/edit#heading=h.j3slp85ydqan [2] - https://docs.google.com/a/wso2.com/document/d/1WUyI_IlAmoF9mfKT3l0oXpjhsJfWNQmBXHW2TZOa_HA/edit thanks, Chanaka -- Chanaka Jayasena Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: chan...@wso2.com; cell: +94 77 785 5565 blog: http://chanaka3d.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
On Thu, Nov 14, 2013 at 12:00 PM, Samuel Gnaniah sam...@wso2.com wrote: Added a note to capture this. http://docs.wso2.org/display/CLUSTER420/Creating+a+Cluster This is not enough. We need to provide a comprehensive guide on how to configure a node to two WK members. This is not documented anywhere at the moment and very few knows how to do it. IsuruW, will you be able to provide instructions to be added to the docs? *Samuel Gnaniah* Senior Technical Writer WSO2 (pvt.) Ltd. Colombo, Sri Lanka (+94) 773131798 On Thu, Nov 14, 2013 at 11:28 AM, Jackie Wheeler jac...@wso2.com wrote: Copying Sam, who is handling the clustering docs. On Wed, Nov 13, 2013 at 8:38 PM, Evanthika Amarasiri evanth...@wso2.comwrote: I'm sorry I did not quite get what Dushan said in the intial email. Yes Dushan, this is a known fact. When ELB is restarted, you will have to restart all other nodes unless you have another WKA member in your cluster. As AmilaM mentioned, this can either be another ELB or a Mgt/Wrk node. Evanthika On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi ami...@wso2.comwrote: You need to have at least one WK member in a given time when you are dealing with hazelcast. If ELB is the only WK member in your setup, when you restart the ELB, others will never join the ELB until they are restarted. To get this working, ELB also should have a WK member (can be the ESB mgt node) and workers should have both ELB and MGT node as WK members. AFAIK QA team is aware of this. If you want, talk to IsuruW. On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan dus...@wso2.comwrote: $subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, 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 -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
You need at least one well-known member to be available for Hazelcast TCP IP mode (WKA) to work. So, when you have only one ELB, and shut it down, there will be issues. We have discussed this in detail several months ago. Search archives. Azeez On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan dus...@wso2.com wrote: $subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/ http://wso2.com/* *Mobile:(+94)714408632 %28%2B94%29714408632* -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 blog: **http://blog.afkham.org*http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
On Thu, Nov 14, 2013 at 9:55 AM, Dushan Abeyruwan dus...@wso2.com wrote: On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi ami...@wso2.comwrote: You need to have at least one WK member in a given time when you are dealing with hazelcast. If ELB is the only WK member in your setup, when you restart the ELB, others will never join the ELB until they are restarted. Is this kind of a norm .. a hard fasten rule we have seutp with the newst WK implementation. ? Wonder I should agree on this or not..assume there is a pool which as larger number of wrks..and Do i need to restart them all? Is that what you trying to emphasis.. l.e assume my prod set has only 1 ELB and 30 works.. :)... so I need to start all 30 if ELB goes down ...woops.. :( Please slow down a bit when typing mail sending them, and read through it once, so that others clearly get your message. You seemed to be getting over excited :) One WK member in a setup is not a recommended approach anyway, since that WKA member will will become the single point of failure. Hazelcast assumes that at least one static (WK) member exists at any given time. So, you will need at least two static members to ensure that cluster membership always works correctly. However, if both those static members fail at the same time, again the whole cluster is affected. To reduce the possibility of this happening, we have to increase the number of static members. Anyway, this is something that I am planning to take up during the Hazelcast consultancy next month. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [dev] ELB 2.1.0 with ESB 4.8.0 Alpha W/M when LB shutdown and restarts Mgt and Wrk Nodes not joining back or taking quite while joining
On Thu, Nov 14, 2013 at 10:08 AM, Evanthika Amarasiri evanth...@wso2.comwrote: I'm sorry I did not quite get what Dushan said in the intial email. Yes Dushan, this is a known fact. When ELB is restarted, you will have to restart all other nodes unless you have another WKA member in your cluster. As AmilaM mentioned, this can either be another ELB or a Mgt/Wrk node. Please don't mention it like that in the docs. That seems to be giving a negative message. What we should be saying is that the system should have at least 2 WKA members in order to work correctly, and to recover from single WKA member failures. Evanthika On Thu, Nov 14, 2013 at 9:50 AM, Amila Maha Arachchi ami...@wso2.comwrote: You need to have at least one WK member in a given time when you are dealing with hazelcast. If ELB is the only WK member in your setup, when you restart the ELB, others will never join the ELB until they are restarted. To get this working, ELB also should have a WK member (can be the ESB mgt node) and workers should have both ELB and MGT node as WK members. AFAIK QA team is aware of this. If you want, talk to IsuruW. On Thu, Nov 14, 2013 at 9:40 AM, Dushan Abeyruwan dus...@wso2.comwrote: $subject, when ELB shutdown and restarts and expecting Mgt's and Wrk's to be rejoined ASAP but seems this not happening(some time it takes while to join,or never joins),but when mgrs's and wrks restarts those will be joining back FYI : QA team please do verify this.. Cheers, 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 -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/* *email: **az...@wso2.com* az...@wso2.com * cell: +94 77 3320919 %2B94%2077%203320919 blog: * *http://blog.afkham.org* http://blog.afkham.org *twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez http://lk.linkedin.com/in/afkhamazeez* *Lean . Enterprise . Middleware* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Carbon Cassandra Authenticator
Hi All, Previously mentioned issue was solved replacing the correct filename. But the patched jar is not properly working due to an OSGi issue regarding package name. For our release we will patch the whole cassandra component jar and in our GA 1.0 we'll get the component from BAM team. Thanks On Thu, Nov 14, 2013 at 12:34 PM, Chan duli...@wso2mobile.com wrote: Hi Bhathiya, I added the patch but the following error comes - java.lang.NullPointerException at org.wso2.carbon.identity.authentication.AuthenticationServiceImpl.authenticate(AuthenticationServiceImpl.java:64) at org.wso2.carbon.cassandra.server.CarbonCassandraAuthenticator.authenticateUser(CarbonCassandraAuthenticator.java:169) at org.wso2.carbon.cassandra.server.CarbonCassandraAuthenticator.authenticate(CarbonCassandraAuthenticator.java:105) at org.apache.cassandra.service.ClientState.login(ClientState.java:124) at org.apache.cassandra.thrift.CassandraServer.login(CassandraServer.java:904) at org.apache.cassandra.thrift.Cassandra$Processor$login.getResult(Cassandra.java:2843) at org.apache.cassandra.thrift.Cassandra$Processor$login.getResult(Cassandra.java:2831) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34) at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) On Wed, Nov 6, 2013 at 2:59 PM, Bhathiya Jayasekara bhath...@wso2.comwrote: Hi Chan, Please find the attached jar for authenticator class. Please put this to dropins directory and change *authenticator* parameter value in *cassandra.yaml* to *org.wso2.carbon.cassandra.server.CarbonCassandraExternalAuthenticator* Let me know if there are any issues. 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* -- 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* -- Chan (Dulitha Wijewantha) Software Engineer - Mobile Development WSO2Mobile Lean.Enterprise.Mobileware * ~Email duli...@wso2mobile.com duli...@wso2mobile.com* * ~Mobile +94712112165* * ~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
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
Hi all, While designing the test framework, its good if we can keep in mind that jaggery2 product also underway. Any thoughts? Regards, UdaraR On Thu, Nov 14, 2013 at 10:15 AM, Madhuka Udantha madh...@wso2.com wrote: 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.com wrote: Hi, Still we do not have jaggery test framework even though there are considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *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 -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Issue with ciphertools.bat -Dconfigure in WIndows
Hi all, Can someone from security team check this JIRA[1] and review the mentioned solution(1st comment) is good enough proceed with? [1] https://wso2.org/jira/browse/CARBON-14543 Regards, UdaraR -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] How to programmatically deactivate axis2 service
Hi All, I am writing some integration tests where it is required to deactivate axis2 service which is deployed in axis2 server programatically. Is there a way to do this? Please advice. Note: I have manually done it using WSO2 AS by deploying the service there and deactivated from UI itself. -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com http://wso2 Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 http://lalajisureshika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to programmatically deactivate axis2 service
U can easily get the required service just looking at that UI bundle in AS I think. On Nov 14, 2013 6:23 PM, Punnadi Gunarathna punn...@wso2.com wrote: Hi All, I am writing some integration tests where it is required to deactivate axis2 service which is deployed in axis2 server programatically. Is there a way to do this? Please advice. Note: I have manually done it using WSO2 AS by deploying the service there and deactivated from UI itself. -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com http://wso2 Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 http://lalajisureshika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 ESB 4.8.0 - Alpha Released !
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.comwrote: 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
[Dev] Dead lock detected in ESB while running integration tests
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@510b02da owned 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@73e64d34owned 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) -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to programmatically deactivate axis2 service
AxisConfiguration.stopservice(), startservice() operations are available. On 14 November 2013 18:42, Harsha Thirimanna hars...@wso2.com wrote: U can easily get the required service just looking at that UI bundle in AS I think. On Nov 14, 2013 6:23 PM, Punnadi Gunarathna punn...@wso2.com wrote: Hi All, I am writing some integration tests where it is required to deactivate axis2 service which is deployed in axis2 server programatically. Is there a way to do this? Please advice. Note: I have manually done it using WSO2 AS by deploying the service there and deactivated from UI itself. -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com http://wso2 Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 http://lalajisureshika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -Ratha mobile: (+94)755906608 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to programmatically deactivate axis2 service
Hi Punnadi, Since you are writing a integration test, you can use the ServiceAdmin admin service. Invoke the changeServiceState operation in ServiceAdmin with serviceName and isActive (set to false) as inputs. Regards, KasunG On Thu, Nov 14, 2013 at 9:59 PM, Vijayaratha Vijayasingam rat...@wso2.comwrote: AxisConfiguration.stopservice(), startservice() operations are available. On 14 November 2013 18:42, Harsha Thirimanna hars...@wso2.com wrote: U can easily get the required service just looking at that UI bundle in AS I think. On Nov 14, 2013 6:23 PM, Punnadi Gunarathna punn...@wso2.com wrote: Hi All, I am writing some integration tests where it is required to deactivate axis2 service which is deployed in axis2 server programatically. Is there a way to do this? Please advice. Note: I have manually done it using WSO2 AS by deploying the service there and deactivated from UI itself. -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com http://wso2 Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 http://lalajisureshika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -Ratha mobile: (+94)755906608 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com http://wso2.com ** cell: **+94 (77) 678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* http://kasunbg.org *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Dead lock detected in ESB while running integration tests
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@73e64d34owned 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) -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How to programmatically deactivate axis2 service
ESB integration tests use simple axis2 server to host backend services. However in this case, we can use ESB to host the service and use ServiceAdmin to deactivate the service. Thanks, Krishantha. On Thu, Nov 14, 2013 at 10:08 PM, Kasun Gajasinghe kas...@wso2.com wrote: Hi Punnadi, Since you are writing a integration test, you can use the ServiceAdmin admin service. Invoke the changeServiceState operation in ServiceAdmin with serviceName and isActive (set to false) as inputs. Regards, KasunG On Thu, Nov 14, 2013 at 9:59 PM, Vijayaratha Vijayasingam rat...@wso2.com wrote: AxisConfiguration.stopservice(), startservice() operations are available. On 14 November 2013 18:42, Harsha Thirimanna hars...@wso2.com wrote: U can easily get the required service just looking at that UI bundle in AS I think. On Nov 14, 2013 6:23 PM, Punnadi Gunarathna punn...@wso2.com wrote: Hi All, I am writing some integration tests where it is required to deactivate axis2 service which is deployed in axis2 server programatically. Is there a way to do this? Please advice. Note: I have manually done it using WSO2 AS by deploying the service there and deactivated from UI itself. -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com http://wso2 Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 http://lalajisureshika.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -Ratha mobile: (+94)755906608 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com , *email: * *kasung AT spamfree wso2.com http://wso2.com ** cell: **+94 (77) 678-0813 %2B94%20%2877%29%20678-0813* *linked-in: *http://lk.linkedin.com/in/gajasinghe *blog: **http://kasunbg.org* http://kasunbg.org *twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.com wrote: 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 considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *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 -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- *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
[Dev] Simple command line client to Balana PDP
I have developed a simple command-line client with the following interface: usage: PDPExec -?,--usage Print usage info -m,--mode arg Mode of response, XML for the full XACML response, or SIMPLE for just 'permit', 'deny', or 'indeterminate' -p,--policyFile argXACML 3.0 policy file -r,--requestFile arg XACML 3.0 request file It takes as input a policy file and a request file, and returns the PDP response (either the entire XML structure, or just permit/deny/indeterminate). Would the project be interested in my submitting this as a patch? I used Commons CLI to help with processing the command-line arguments, which introduced a new dependency in the POM. Thanks. --Scott ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] af carbon errors
hi, all,
I recently confront a error in the AF carbon console, when click the
application matadata button, to check the application info. The page shows
empty on the right, and the log shows:
TID: [0] [] [2013-11-15 07:05:48,397] ERROR
{org.apache.tiles.jsp.taglib.RenderTagSupport} - Error during rendering
{org.apache.tiles.jsp.taglib.RenderTagSupport}
javax.servlet.jsp.JspException: IO Error executing tag: JSPException while
including path '/generic/list.jsp'. ServletException while including page.
at
org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:84)
at
org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at
org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_insertAttribute_7(org.apache.jsp.admin.layout.template_jsp:536)
at
org.apache.jsp.admin.layout.template_jsp._jspService(org.apache.jsp.admin.layout.template_jsp:286)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:403)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:492)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:412)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.forward(ContextPathServletAdaptor.java:362)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.forward(ServletTilesRequestContext.java:198)
at
org.apache.tiles.servlet.context.ServletTilesRequestContext.dispatch(ServletTilesRequestContext.java:185)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:419)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:370)
at org.wso2.carbon.ui.action.ActionHelper.render(ActionHelper.java:52)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
Re: [Dev] WSO2 ESB 4.8.0 - Alpha Released !
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.com wrote: 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.comwrote: 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
Re: [Dev] Dead lock detected in ESB while running integration tests
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@73e64d34owned 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) -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Make the CarbonInitialJNDIContextFactory Implemetation pluggable and Extensible
Hi all, $subject is required to implement a JNDI Context per application in AF and it will be useful whoever wanted to change the default behavior.I have refactored org.wso2.carbon.util package to cater the above requirement in following issue[0]. Can anybody from the kernel team review the patch and commit to patch0002? Thanks. [0]https://wso2.org/jira/browse/CARBON-14544 -- ajanthan -- Ajanthan Balachandiran Senior Software Engineer; Solutions Technologies Team ;WSO2, Inc.; http://wso2.com/ email: ajant...@wso2.com; cell: +94775581497 blog: http://bkayts.blogspot.com/ Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] test-automation-framework build fail
[INFO] Building WSO2 Carbon Automation - Test API 4.2.3 [INFO] [WARNING] The POM for eclipse:validateutility:jar:0.95 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] The POM for uddi:uddi4j:jar:1.0.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] The POM for org.eclipse.core:org.eclipse.core.runtime:jar:3.5.0.v20090429-1800 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [INFO] [INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ org.wso2.carbon.automation.api --- [INFO] Deleting file set: /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/target (included: [**], excluded: []) [INFO] [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ org.wso2.carbon.automation.api --- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ org.wso2.carbon.automation.api --- [INFO] Compiling 189 source files to /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/target/classes [INFO] [INFO] Reactor Summary: [INFO] [INFO] WSO2 Carbon Automation - Parent core project .. SUCCESS [1.027s] [INFO] WSO2 Carbon Automation - Test API . FAILURE [6.942s] [INFO] WSO2 Carbon Automation - Test Core SKIPPED [INFO] WSO2 Carbon Automation - Common Utils . SKIPPED [INFO] WSO2 Carbon Automation - Jmeter Test Runner ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 8.506s [INFO] Finished at: Fri Nov 15 10:28:51 IST 2013 [INFO] Final Memory: 67M/881M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project org.wso2.carbon.automation.api: Compilation failure: Compilation failure: [ERROR] /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/webapp/mgt/WebAppAdminClient.java:[25,51] cannot find symbol [ERROR] symbol : class VersionedWebappMetadata [ERROR] location: package org.wso2.carbon.webapp.mgt.stub.types.carbon [ERROR] [ERROR] /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/webapp/mgt/WebAppAdminClient.java:[25,51] cannot find symbol [ERROR] symbol : class VersionedWebappMetadata [ERROR] location: package org.wso2.carbon.webapp.mgt.stub.types.carbon [ERROR] [ERROR] /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/webapp/mgt/WebAppAdminClient.java:[121,8] cannot find symbol [ERROR] symbol : class VersionedWebappMetadata [ERROR] location: class org.wso2.carbon.automation.api.clients.webapp.mgt.WebAppAdminClient [ERROR] [ERROR] /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/webapp/mgt/WebAppAdminClient.java:[144,8] cannot find symbol [ERROR] symbol : class VersionedWebappMetadata [ERROR] location: class org.wso2.carbon.automation.api.clients.webapp.mgt.WebAppAdminClient [ERROR] [ERROR] /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/webapp/mgt/WebAppAdminClient.java:[147,17] cannot find symbol [ERROR] symbol : class VersionedWebappMetadata [ERROR] location: class org.wso2.carbon.automation.api.clients.webapp.mgt.WebAppAdminClient [ERROR] [ERROR] /home/malaka/work/wso2turing/platform-integration/test-automation-framework/4.2.3/org.wso2.carbon.automation.api/src/main/java/org/wso2/carbon/automation/api/clients/webapp/mgt/WebAppAdminClient.java:[165,8] cannot find symbol [ERROR] symbol : class VersionedWebappMetadata [ERROR] location: class org.wso2.carbon.automation.api.clients.webapp.mgt.WebAppAdminClient [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
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. 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. Thanks, Krishantha On Thu, Nov 14, 2013 at 11:02 PM, Madhuka Udantha madh...@wso2.com wrote: On Thu, Nov 14, 2013 at 5:14 PM, Udara Rathnayake uda...@wso2.com wrote: 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 considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *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 -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Dead lock detected in ESB while running integration tests
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@73e64d34owned 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) -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda -- Miyuru Wanninayaka Technical Lead WSO2 Inc. : http://wso2.com Mobile : +94 77 209 9788 Blog : http://miyurudw.blogspot.com Flickr : http://www.flickr.com/photos/miyuru_daminda
Re: [Dev] Simple command line client to Balana PDP
Hi Scott, Great We could probably add this to Balana samples [1] as command line PEP for Balana. Please provide a patch. On Fri, Nov 15, 2013 at 4:38 AM, Scott Came scott.c...@search.org wrote: I have developed a simple command-line client with the following interface: usage: PDPExec -?,--usage Print usage info -m,--mode arg Mode of response, XML for the full XACML response, or SIMPLE for just 'permit', 'deny', or 'indeterminate' -p,--policyFile argXACML 3.0 policy file -r,--requestFile arg XACML 3.0 request file It takes as input a policy file and a request file, and returns the PDP response (either the entire XML structure, or just permit/deny/indeterminate). Would the project be interested in my submitting this as a patch? I used Commons CLI to help with processing the command-line arguments, which introduced a new dependency in the POM. Yes. Commons CLI is with Apache 2.0 license. It means that it is fine to introduce it to pom file. However, just to let you know, AFAIK, other Balana samples have been developed with java Console and Scanner class. [1] http://svn.wso2.org/repos/wso2/trunk/commons/balana/modules/balana-samples/ Thanks, Asela. Thanks. --Scott ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Regards, Asela ATL Mobile : +94 777 625 933 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Jaggery] [Test] Test framework for jaggery
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 considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there is no JS testing framework under WSO2 Platform. Testing framework will be under application level such as mocha, jasmine. Test frame will be apply to (basically)test. - jaggery API (js functions and arguments ) - REST APIs that are expose under jaggery application - With test coverage reporting We will be evaluating existing JavaScript test frame works regard mocha[1], jasmine[2], Qunit[3], Vows[4], expresso[5], nodeunit[6] and jsunit[7] to $subject. All suggestions are welcome. [1] http://visionmedia.github.io/mocha/ [2] http://pivotal.github.io/jasmine/ [3] http://qunitjs.com/ [4] http://vowsjs.org/ [5] http://visionmedia.github.io/expresso/ [6] https://github.com/caolan/nodeunit [7] https://github.com/pivotal/jsunit Thanks -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- *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 -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com -- *Madhuka* Udantha Senior Software Engineer Development Technologies WSO2 Inc. : http://wso2.com *Mobile*: +94774066336 *Blog*: http://madhukaudantha.blogspot.com/ -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- *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
Re: [Dev] Dead lock detected in ESB while running integration tests
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) -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Miyuru Wanninayaka Technical Lead WSO2 Inc. :
Re: [Dev] Dead lock detected in ESB while running integration tests
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) -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean .
