Re: [Dev] PersistenceExceptions in ESB

[Afkham Azeez]

If you do things like securing a proxy service using the Carbon service
security UI, where does that information get persisted?


On Mon, Mar 26, 2012 at 12:19 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Mar 26, 2012 at 12:11 PM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 11:45 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>> We see a lot of persistence exceptions in the latest ESB packs:
>>>
>>> org.wso2.carbon.core.persistence.PersistenceException: A transaction is
>>> already started. Nested transactions are no longer supported in the new
>>> model
>>> at
>>> org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.beginTransaction(ServiceGroupFilePersistenceManager.java:62)
>>> at
>>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.updateParameter(AbstractPersistenceManager.java:136)
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.updateServiceParameter(ServicePersistenceManager.java:775)
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:592)
>>> at
>>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:282)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:336)
>>> at
>>> org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:566)
>>> at
>>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.deployServices(ConfigurationUpdater.java:286)
>>>
>>> What does this mean? Things seem to work find in spite of the exceptions
>>> though.
>>>
>>
>> The way to make sure things work is to restart the server and see whether
>> the changed parameters are still there.
>>
>
> We don't need Axis2 level persistence for proxy services. Synapse has its
> own persistence logic for proxy services, which takes care of saving proxy
> services to the file system.
>
>
>>
>> Does this seen in server startup? If not, please tell me how to reproduce
>> this.
>>
>
> Create a proxy service and then update the ESB configuration from the
> source view.
>
>
>>
>> Thanks,
>> --KasunG
>>
>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Associate Technical Lead;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ___
>>> 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** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>> *
>>  *blog: **http://blog.kasunbg.org* 
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>> *
>> *
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> 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/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] Reporting Admin Services Listed in ESB Service Listing Page

[Sinthuja Ragendran]

Hi,

This services are from reporting component and it's fixed now.

Thanks,
Sinthuja.

On Mon, Mar 26, 2012 at 12:21 PM, Hiranya Jayathilaka wrote:

> Following services are listed in the service listing page of ESB:
>
> DBReportingService
> JrxmlFileUploader
> ReportingResourcesSupplier
> ReportTemplateAdmin
>
> What are these services? Looks like some admin services which are not
> properly secured!
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.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] Update on BAM Task migration

[Tharindu Mathew]

The reason that ntask expects string key value pairs is to be able to
execute tasks in a distributed manner. As part of completing the task, you
should setup a few nodes and check whether tasks are distributed
appropriately and in a fail over manner.

Also, try to expose some MXBeans to check how many tasks are running,
memory/IO per task, etc. We have to think of monitoring the monitor
scenario.

On Mon, Mar 26, 2012 at 12:28 PM, Buddhika Chamith wrote:

>
> On Mon, Mar 26, 2012 at 12:04 PM, Prabath Abeysekera wrote:
>
>> Hi all,
>>
>> I've been working on the $subject and currently there's only one task
>> remaining to be completed. The main intention of this effort is to migrate
>> the existing task implementation of BAM to ntasks which is a quartz based
>> task scheduler component introduced a couple of months back. While working
>> on the aforementioned bit of remaining work, I was confronted with an issue
>> and here's my suggestions to overcome it.
>>
>> In the currently used BAM task implementation, there's a mechanism called
>> DataContext which is used to pass some runtime data to a particular task
>> execution (such as default credentials to log into cassandra, tenant ID,
>> etc) and to populate it with records that are fetched from cassandra (using
>> the GetAnalyser) in memory. Whenever a task is scheduled this object is
>> passed into it which then uses the DataContext object to grab the necessary
>> runtime information required for the task execution. Ntasks being a generic
>> task scheduler component, only accepts a map of string key value pairs as
>> run time properties. In other words, if it is required to pass additional
>> set of properties apart from the ones that are provided by default (for
>> example, cron expression, task count, task interval, etc) then they have to
>> be passed as Strings. Thus, we either need to serialize the DataContext or
>> we need to find some other mechanism to pass those properties in the
>> DataContext to the corresponding task.
>>
>>
> Currently the DataContext is used as a holder for data fetched from
> Cassandra and so the serializing of DataContext is not trivial and not very
> useful as well.
>
> IIUC, I believe it would be more appropriate if it is possible to make the
>> DataContext local to the task execution since a task being a single
>> independent execution unit and the DataContext is also bound to a
>> particular task. To elaborate more on this, the DataContext seems to be
>> effectively used in the task execution phase, so I believe, there's a
>> possibility for us to build it up at the aforementioned phase without
>> initializing it in the task scheduling phase. This way we can even get rid
>> of the usage of the binding of DataContext at the task scheduling phase.
>> And we can also pass the properties of the DataContext as String key value
>> pairs as well.
>>
>
> +1. This decouples run time data and configuration data currently present
> in the DataContext. We can basically use DataContext for holding run time
> data (basically fetched data) which would be specific for the particular
> execution of the task.
>
>
>> Had an offline chat with Tharindu on this and we agreed to proceed with
>> the above suggested mechanism which involves removing the binding of the
>> DataContext object at the task scheduling phase.
>>
>>
>>
>> Regards,
>> --
>> Prabath Abeysekara
>> Software Engineer
>> WSO2 Inc.
>> Email: praba...@wso2.com 
>> Mobile: +94774171471
>>
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
> Regards
> Buddhika
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon > WSO2 MS > #12 has FAILED

[Dilshan Edirisuriya]

Hi,

When running MS and GS integration tests there is a test failure. It says,

"integration\security-verifier\target\SecVerifier.aar does not exist"

This seems to be the issue in Bamboo as well. However have added the
"sec.verifier.dir" as follows like in other products.

${basedir}/../../../integration/security-verifier/

Looking into the issue now.

Regards,

Dilshan


On Mon, Mar 26, 2012 at 11:48 AM, Yumani Ranaweera  wrote:

>
>
> On Sat, Mar 24, 2012 at 12:01 PM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Sat, Mar 24, 2012 at 9:43 AM, Shammi Jayasinghe wrote:
>>
>>> Hi MS RMs,
>>>
>>>  Could you please have a look in to the MS test failures.
>>>
>>
>> I will help MS RMs to overcome this issue.
>>
>> I have few questions.
>> How does web services like sessionTest.js are treated within Carbon? Is
>> that also treated as an AxisService, as same as proxy services, jax-ws
>> services, and real axis2 services are treated? This is a jaggery app,
>> right? If so, what would be the differences of jaggery apps compared to
>> other web service types?  Does sessionisTest.js is a jaggery app? If
>>
>
> MS doesn't have jaggery apps. The .js extension is for JavaScript web
> services.
>
>
>>
>> Further, I see that the names of these test web services are like
>> - admin/upgradeChecker. What does "/" denote?
>> Why these are deployed
>> inside repository/deployment/server/jsservices/admin/ instead
>> of repository/deployment/server/jsservices/ ?
>> This is where the services are deployed -
>> wso2ms-2.3.0-SNAPSHOT/repository/deployment/server/jsservices/admin/sessionTest.js
>>
>
> AFAIU, MS deploys services based on their owners and that's why you get
> admin/sessionTest.js.
>
>
>
>> I know it's a lot of questions, but those will help to understand the
>> IOExceptions in integration tests.
>>
>> Thanks,
>> --KasunG
>>
>>
>>> Thanks
>>>
>>> Shammi
>>>
>>>  On Sat, Mar 24, 2012 at 9:23 AM, Bamboo  wrote:
>>>
  [image: Failed]  WSO2 
 Carbon› WSO2
 MS  ›
 #12 
 failed

 This build was manually triggered by 
 BambooBuilder
 .

 No failed tests found, a possible compilation error.
   Failing 
 Jobs
 Job
 Duration Tests[image: Failed]  Default 
 Job
  (Default
 Stage)  9 minutes  No tests found  
 Logs|
 Artifacts
  View
 Online
 | Add 
 Comments

 This message was sent by Atlassian 
 Bamboo
 .

 If you wish to stop receiving these emails edit your user 
 profileor
  notify
 your 
 administrator
 .

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Best Regards,*
>>>
>>> Shammi Jayasinghe*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
>>> mobile: +94 71 4493085
>>>
>>>
>>>
>>> ___
>>> 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** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>> *
>>  *blog: **http://blog.kasunbg.org* 
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>> *
>> *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Yumani Ranaweera
> Associate Technical Lead - QA
> WSO2, Inc. - http://wso2.org
>
> Email : yum...@wso2.com
> Cell: +94 077 7795242
> Blog   : http://yumani.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] PersistenceExceptions in ESB

[Manjula Rathnayake]

Hi,

I am looking into issue, https://wso2.org/jira/browse/CARBON-12680.

And got following error,
ERROR - RPCInOnlyMessageReceiver Exception occurred while trying to invoke
service method applySecurity
java.lang.NullPointerException
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:616)
at
org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:46)
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.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:54)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
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)

I will check with this latest packs as my source is not sync with the pack,
and update the thread.

Thank you.



On Mon, Mar 26, 2012 at 12:31 PM, Afkham Azeez  wrote:

> If you do things like securing a proxy service using the Carbon service
> security UI, where does that information get persisted?
>
>
> On Mon, Mar 26, 2012 at 12:19 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 12:11 PM, Kasun Gajasinghe wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 11:45 AM, Hiranya Jayathilaka 
>>> wrote:
>>>
 We see a lot of persistence exceptions in the latest ESB packs:

 org.wso2.carbon.core.persistence.PersistenceException: A transaction is
 already started. Nested transactions are no longer supported in the new
 model
 at
 org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.beginTransaction(ServiceGroupFilePersistenceManager.java:62)
 at
 org.wso2.carbon.core.persistence.AbstractPersistenceManager.updateParameter(AbstractPersistenceManager.java:136)
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.updateServiceParameter(ServicePersistenceManager.java:775)
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:592)
 at
 org.wso2.carbon.core.deployment.DeploymentInterceptor.s

[Dev] Infinispan and jgroups printing lots of INFO and WARN during the stratos services start up.

[Kathiravelu Pradeeban]

[2012-03-26 13:05:34,429] ERROR
{org.wso2.carbon.caching.infinispan.InfinispanCacheManager} -  Invalid
cache mode provided. The available values are local, replicated,
distributed and invalidation
[2012-03-26 13:05:34,469]  INFO
{org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
extended standard service  :   StandardService[Catalina]
[2012-03-26 13:05:34,931]  INFO
{org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN78:
Starting JGroups Channel
[2012-03-26 13:05:34,932]  INFO
{org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN88:
Unable to use any JGroups configuration mechanisms provided in properties
{}. Using default JGroups configuration!
[2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send buffer
of socket java.net.DatagramSocket@4edbad67 was set to 640KB, but the OS
only allocated 131.07KB. This might lead to performance problems. Please
set your max send buffer in the OS correctly (e.g. net.core.wmem_max on
Linux)
[2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  receive
buffer of socket java.net.DatagramSocket@4edbad67 was set to 20MB, but the
OS only allocated 131.07KB. This might lead to performance problems. Please
set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on
Linux)
[2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send buffer
of socket java.net.MulticastSocket@40ee1aeb was set to 640KB, but the OS
only allocated 131.07KB. This might lead to performance problems. Please
set your max send buffer in the OS correctly (e.g. net.core.wmem_max on
Linux)
[2012-03-26 13:05:35,207]  WARN {org.jgroups.protocols.UDP} -  receive
buffer of socket java.net.MulticastSocket@40ee1aeb was set to 25MB, but the
OS only allocated 131.07KB. This might lead to performance problems. Please
set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on
Linux)
[2012-03-26 13:05:35,323]  INFO
{org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN94:
Received new cluster view: [localhost-26061|10] [localhost-26061,
localhost-55353, localhost-29930, localhost-19122]
[2012-03-26 13:05:35,326]  INFO
{org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN79:
Cache local address is localhost-19122, physical addresses are
[fe80:0:0:0:250:56ff:fec0:8:34700]
[2012-03-26 13:05:35,334]  INFO
{org.infinispan.factories.GlobalComponentRegistry} -  ISPN000128:
Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL


I am testing the trunk build of Stratos services with a local setup. I am
getting the above logs, when I start a few services (tried with BPS and IS,
and given above is the exact logs copied from BPS). Are these really INFO
and WARN level logs, or just DEBUG?

Thank you.
Regards,
Pradeeban.

-- 
Kathiravelu Pradeeban.
Software Engineer.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update on BAM Task migration

[Prabath Abeysekera]

On Mon, Mar 26, 2012 at 12:45 PM, Tharindu Mathew  wrote:

> The reason that ntask expects string key value pairs is to be able to
> execute tasks in a distributed manner. As part of completing the task, you
> should setup a few nodes and check whether tasks are distributed
> appropriately and in a fail over manner.
>
> Also, try to expose some MXBeans to check how many tasks are running,
> memory/IO per task, etc. We have to think of monitoring the monitor
> scenario.
>
>
+1. I'll work on that.


>
> On Mon, Mar 26, 2012 at 12:28 PM, Buddhika Chamith wrote:
>
>>
>> On Mon, Mar 26, 2012 at 12:04 PM, Prabath Abeysekera 
>> wrote:
>>
>>> Hi all,
>>>
>>> I've been working on the $subject and currently there's only one task
>>> remaining to be completed. The main intention of this effort is to migrate
>>> the existing task implementation of BAM to ntasks which is a quartz based
>>> task scheduler component introduced a couple of months back. While working
>>> on the aforementioned bit of remaining work, I was confronted with an issue
>>> and here's my suggestions to overcome it.
>>>
>>> In the currently used BAM task implementation, there's a mechanism
>>> called DataContext which is used to pass some runtime data to a particular
>>> task execution (such as default credentials to log into cassandra, tenant
>>> ID, etc) and to populate it with records that are fetched from cassandra
>>> (using the GetAnalyser) in memory. Whenever a task is scheduled this object
>>> is passed into it which then uses the DataContext object to grab the
>>> necessary runtime information required for the task execution. Ntasks being
>>> a generic task scheduler component, only accepts a map of string key value
>>> pairs as run time properties. In other words, if it is required to pass
>>> additional set of properties apart from the ones that are provided by
>>> default (for example, cron expression, task count, task interval, etc) then
>>> they have to be passed as Strings. Thus, we either need to serialize the
>>> DataContext or we need to find some other mechanism to pass those
>>> properties in the DataContext to the corresponding task.
>>>
>>>
>> Currently the DataContext is used as a holder for data fetched from
>> Cassandra and so the serializing of DataContext is not trivial and not very
>> useful as well.
>>
>> IIUC, I believe it would be more appropriate if it is possible to make
>>> the DataContext local to the task execution since a task being a single
>>> independent execution unit and the DataContext is also bound to a
>>> particular task. To elaborate more on this, the DataContext seems to be
>>> effectively used in the task execution phase, so I believe, there's a
>>> possibility for us to build it up at the aforementioned phase without
>>> initializing it in the task scheduling phase. This way we can even get rid
>>> of the usage of the binding of DataContext at the task scheduling phase.
>>> And we can also pass the properties of the DataContext as String key value
>>> pairs as well.
>>>
>>
>> +1. This decouples run time data and configuration data currently present
>> in the DataContext. We can basically use DataContext for holding run time
>> data (basically fetched data) which would be specific for the particular
>> execution of the task.
>>
>>
>>> Had an offline chat with Tharindu on this and we agreed to proceed with
>>> the above suggested mechanism which involves removing the binding of the
>>> DataContext object at the task scheduling phase.
>>>
>>>
>>>
>>> Regards,
>>> --
>>> Prabath Abeysekara
>>> Software Engineer
>>> WSO2 Inc.
>>> Email: praba...@wso2.com 
>>> Mobile: +94774171471
>>>
>>> 
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> Regards
>> Buddhika
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
> Tharindu
>
> blog: http://mackiemathew.com/
> M: +9459908
>
>


-- 
Prabath Abeysekara
Software Engineer
WSO2 Inc.
Email: praba...@wso2.com 
Mobile: +94774171471


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Infinispan and jgroups printing lots of INFO and WARN during the stratos services start up.

[Kathiravelu Pradeeban]

On Mon, Mar 26, 2012 at 1:14 PM, Kathiravelu Pradeeban
wrote:

> [2012-03-26 13:05:34,429] ERROR
> {org.wso2.carbon.caching.infinispan.InfinispanCacheManager} -  Invalid
> cache mode provided. The available values are local, replicated,
> distributed and invalidation
> [2012-03-26 13:05:34,469]  INFO
> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
> extended standard service  :   StandardService[Catalina]
> [2012-03-26 13:05:34,931]  INFO
> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN78:
> Starting JGroups Channel
> [2012-03-26 13:05:34,932]  INFO
> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN88:
> Unable to use any JGroups configuration mechanisms provided in properties
> {}. Using default JGroups configuration!
> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send buffer
> of socket java.net.DatagramSocket@4edbad67 was set to 640KB, but the OS
> only allocated 131.07KB. This might lead to performance problems. Please
> set your max send buffer in the OS correctly (e.g. net.core.wmem_max on
> Linux)
> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  receive
> buffer of socket java.net.DatagramSocket@4edbad67 was set to 20MB, but
> the OS only allocated 131.07KB. This might lead to performance problems.
> Please set your max receive buffer in the OS correctly (e.g.
> net.core.rmem_max on Linux)
> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send buffer
> of socket java.net.MulticastSocket@40ee1aeb was set to 640KB, but the OS
> only allocated 131.07KB. This might lead to performance problems. Please
> set your max send buffer in the OS correctly (e.g. net.core.wmem_max on
> Linux)
> [2012-03-26 13:05:35,207]  WARN {org.jgroups.protocols.UDP} -  receive
> buffer of socket java.net.MulticastSocket@40ee1aeb was set to 25MB, but
> the OS only allocated 131.07KB. This might lead to performance problems.
> Please set your max receive buffer in the OS correctly (e.g.
> net.core.rmem_max on Linux)
> [2012-03-26 13:05:35,323]  INFO
> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN94:
> Received new cluster view: [localhost-26061|10] [localhost-26061,
> localhost-55353, localhost-29930, localhost-19122]
> [2012-03-26 13:05:35,326]  INFO
> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN79:
> Cache local address is localhost-19122, physical addresses are
> [fe80:0:0:0:250:56ff:fec0:8:34700]
> [2012-03-26 13:05:35,334]  INFO
> {org.infinispan.factories.GlobalComponentRegistry} -  ISPN000128:
> Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL
>
>
> I am testing the trunk build of Stratos services with a local setup. I am
> getting the above logs, when I start a few services (tried with BPS and IS,
> and given above is the exact logs copied from BPS). Are these really INFO
> and WARN level logs, or just DEBUG?
>

What I meant to ask is, can't we hide these logs from Carbon logs by
default, by setting the log levels to WARN for the respective classes in
log4j.properties?

Regards,
Pradeeban.

>
> Thank you.
> Regards,
> Pradeeban.
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> Cloud Technologies Team.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
> M: +94 776 477 976
>
>


-- 
Kathiravelu Pradeeban.
Software Engineer.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Test failure in core\org.wso2.carbon.core

[Selvaratnam Uthaiyashankar]

This is a windows specific issue and fixed now.

Shankar

On Mon, Mar 26, 2012 at 12:13 PM, Selvaratnam Uthaiyashankar
 wrote:
> Yes, it is up to date. (revision 123861)
>
> Shankar
>
> On Mon, Mar 26, 2012 at 11:54 AM, Kasun Gajasinghe  wrote:
>>
>> Hi Shankar,
>> Let me have a look at that. In the meanwhile, can you make sure your said
>> module is up to date (including test folder)? Current Bamboo builds were
>> successful eight times in a row! [1] Does your setup is different?
>>
>> [1] http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD
>>
>> On Mon, Mar 26, 2012 at 11:37 AM, Selvaratnam Uthaiyashankar
>>  wrote:
>>>
>>> $subject.
>>>
>>>
>>> ---
>>>
>>> Test set: org.wso2.carbon.core.test.persistence.PersistenceManagerTest
>>>
>>>
>>> ---
>>>
>>> Tests run: 14, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.765
>>> sec <<< FAILURE!
>>>
>>> testDeleteServiceGroup(org.wso2.carbon.core.test.persistence.PersistenceManagerTest)
>>>  Time elapsed: 0.011 sec  <<< ERROR!
>>>
>>> org.wso2.carbon.core.persistence.PersistenceException: Could not
>>> delete Service Group resource from Config Registry
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.handleExceptionWithRollback(AbstractPersistenceManager.java:540)
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.ServiceGroupPersistenceManager.deleteServiceGroup(ServiceGroupPersistenceManager.java:155)
>>>
>>>        at
>>> org.wso2.carbon.core.test.persistence.PersistenceManagerTest.testDeleteServiceGroup(PersistenceManagerTest.java:401)
>>>
>>> Caused by: org.wso2.carbon.core.persistence.PersistenceException:
>>> Unable to remove the resource testSVG
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.handleExceptionWithRollback(AbstractPersistenceManager.java:540)
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.removeResource(AbstractPersistenceManager.java:226)
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.ServiceGroupPersistenceManager.deleteServiceGroup(ServiceGroupPersistenceManager.java:137)
>>>
>>>        ... 29 more
>>>
>>> Caused by: org.wso2.carbon.core.persistence.PersistenceException:
>>> Couldn't delete testSVG.xml
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.handleExceptionWithRollback(AbstractFilePersistenceManager.java:178)
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.commitTransaction(ServiceGroupFilePersistenceManager.java:98)
>>>
>>>        at
>>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.removeResource(AbstractPersistenceManager.java:224)
>>>
>>>        ... 30 more
>>>
>>> Caused by: java.lang.Throwable
>>>
>>>        ... 32 more
>>>
>>>
>>>
>>> --
>>> S.Uthaiyashankar
>>> Senior Architect
>>> WSO2 Inc.
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>
>>> Phone: +94 714897591
>>> ___
>>> 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 cell: +94 (77) 678-0813
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://blog.kasunbg.org
>>
>>
>> twitter: http://twitter.com/kasunbg
>>
>>
>>
>
>
>
> --
> S.Uthaiyashankar
> Senior Architect
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> Phone: +94 714897591



-- 
S.Uthaiyashankar
Senior Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

Phone: +94 714897591
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Infinispan and jgroups printing lots of INFO and WARN during the stratos services start up.

[Afkham Azeez]

I think we need to rethink our logging strategy. For example, in Synapse,
unless you explicitly add a logger, the logs don't show up. In Carbon, we
have to explicitly disable the loggers. I think we should follow the
Synapse model.

On Mon, Mar 26, 2012 at 1:19 PM, Kathiravelu Pradeeban
wrote:

>
>
> On Mon, Mar 26, 2012 at 1:14 PM, Kathiravelu Pradeeban  > wrote:
>
>> [2012-03-26 13:05:34,429] ERROR
>> {org.wso2.carbon.caching.infinispan.InfinispanCacheManager} -  Invalid
>> cache mode provided. The available values are local, replicated,
>> distributed and invalidation
>> [2012-03-26 13:05:34,469]  INFO
>> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
>> extended standard service  :   StandardService[Catalina]
>> [2012-03-26 13:05:34,931]  INFO
>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN78:
>> Starting JGroups Channel
>> [2012-03-26 13:05:34,932]  INFO
>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN88:
>> Unable to use any JGroups configuration mechanisms provided in properties
>> {}. Using default JGroups configuration!
>> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send
>> buffer of socket java.net.DatagramSocket@4edbad67 was set to 640KB, but
>> the OS only allocated 131.07KB. This might lead to performance problems.
>> Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max
>> on Linux)
>> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  receive
>> buffer of socket java.net.DatagramSocket@4edbad67 was set to 20MB, but
>> the OS only allocated 131.07KB. This might lead to performance problems.
>> Please set your max receive buffer in the OS correctly (e.g.
>> net.core.rmem_max on Linux)
>> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send
>> buffer of socket java.net.MulticastSocket@40ee1aeb was set to 640KB, but
>> the OS only allocated 131.07KB. This might lead to performance problems.
>> Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max
>> on Linux)
>> [2012-03-26 13:05:35,207]  WARN {org.jgroups.protocols.UDP} -  receive
>> buffer of socket java.net.MulticastSocket@40ee1aeb was set to 25MB, but
>> the OS only allocated 131.07KB. This might lead to performance problems.
>> Please set your max receive buffer in the OS correctly (e.g.
>> net.core.rmem_max on Linux)
>> [2012-03-26 13:05:35,323]  INFO
>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN94:
>> Received new cluster view: [localhost-26061|10] [localhost-26061,
>> localhost-55353, localhost-29930, localhost-19122]
>> [2012-03-26 13:05:35,326]  INFO
>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN79:
>> Cache local address is localhost-19122, physical addresses are
>> [fe80:0:0:0:250:56ff:fec0:8:34700]
>> [2012-03-26 13:05:35,334]  INFO
>> {org.infinispan.factories.GlobalComponentRegistry} -  ISPN000128:
>> Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL
>>
>>
>> I am testing the trunk build of Stratos services with a local setup. I am
>> getting the above logs, when I start a few services (tried with BPS and IS,
>> and given above is the exact logs copied from BPS). Are these really INFO
>> and WARN level logs, or just DEBUG?
>>
>
> What I meant to ask is, can't we hide these logs from Carbon logs by
> default, by setting the log levels to WARN for the respective classes in
> log4j.properties?
>
> Regards,
> Pradeeban.
>
>>
>> Thank you.
>> Regards,
>> Pradeeban.
>>
>> --
>> Kathiravelu Pradeeban.
>> Software Engineer.
>> Cloud Technologies Team.
>> WSO2 Inc.
>>
>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>> M: +94 776 477 976
>>
>>
>
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> Cloud Technologies Team.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
> M: +94 776 477 976
>
>
> ___
> 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/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] Infinispan and jgroups printing lots of INFO and WARN during the stratos services start up.

[Dimuthu Leelarathne]

Hi Azeez,


On Mon, Mar 26, 2012 at 1:42 PM, Afkham Azeez  wrote:

> I think we need to rethink our logging strategy. For example, in Synapse,
> unless you explicitly add a logger, the logs don't show up. In Carbon, we
> have to explicitly disable the loggers. I think we should follow the
> Synapse model.
>
>
+1

I will hide these logs and add these settings as recommendations to the
setup.

thanks,
dimuthu



> On Mon, Mar 26, 2012 at 1:19 PM, Kathiravelu Pradeeban  > wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 1:14 PM, Kathiravelu Pradeeban <
>> pradee...@wso2.com> wrote:
>>
>>> [2012-03-26 13:05:34,429] ERROR
>>> {org.wso2.carbon.caching.infinispan.InfinispanCacheManager} -  Invalid
>>> cache mode provided. The available values are local, replicated,
>>> distributed and invalidation
>>> [2012-03-26 13:05:34,469]  INFO
>>> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
>>> extended standard service  :   StandardService[Catalina]
>>> [2012-03-26 13:05:34,931]  INFO
>>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN78:
>>> Starting JGroups Channel
>>> [2012-03-26 13:05:34,932]  INFO
>>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN88:
>>> Unable to use any JGroups configuration mechanisms provided in properties
>>> {}. Using default JGroups configuration!
>>> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send
>>> buffer of socket java.net.DatagramSocket@4edbad67 was set to 640KB, but
>>> the OS only allocated 131.07KB. This might lead to performance problems.
>>> Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max
>>> on Linux)
>>> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  receive
>>> buffer of socket java.net.DatagramSocket@4edbad67 was set to 20MB, but
>>> the OS only allocated 131.07KB. This might lead to performance problems.
>>> Please set your max receive buffer in the OS correctly (e.g.
>>> net.core.rmem_max on Linux)
>>> [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send
>>> buffer of socket java.net.MulticastSocket@40ee1aeb was set to 640KB,
>>> but the OS only allocated 131.07KB. This might lead to performance
>>> problems. Please set your max send buffer in the OS correctly (e.g.
>>> net.core.wmem_max on Linux)
>>> [2012-03-26 13:05:35,207]  WARN {org.jgroups.protocols.UDP} -  receive
>>> buffer of socket java.net.MulticastSocket@40ee1aeb was set to 25MB, but
>>> the OS only allocated 131.07KB. This might lead to performance problems.
>>> Please set your max receive buffer in the OS correctly (e.g.
>>> net.core.rmem_max on Linux)
>>> [2012-03-26 13:05:35,323]  INFO
>>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN94:
>>> Received new cluster view: [localhost-26061|10] [localhost-26061,
>>> localhost-55353, localhost-29930, localhost-19122]
>>> [2012-03-26 13:05:35,326]  INFO
>>> {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN79:
>>> Cache local address is localhost-19122, physical addresses are
>>> [fe80:0:0:0:250:56ff:fec0:8:34700]
>>> [2012-03-26 13:05:35,334]  INFO
>>> {org.infinispan.factories.GlobalComponentRegistry} -  ISPN000128:
>>> Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL
>>>
>>>
>>> I am testing the trunk build of Stratos services with a local setup. I
>>> am getting the above logs, when I start a few services (tried with BPS and
>>> IS, and given above is the exact logs copied from BPS). Are these really
>>> INFO and WARN level logs, or just DEBUG?
>>>
>>
>> What I meant to ask is, can't we hide these logs from Carbon logs by
>> default, by setting the log levels to WARN for the respective classes in
>> log4j.properties?
>>
>> Regards,
>> Pradeeban.
>>
>>>
>>> Thank you.
>>> Regards,
>>> Pradeeban.
>>>
>>> --
>>> Kathiravelu Pradeeban.
>>> Software Engineer.
>>> Cloud Technologies Team.
>>> WSO2 Inc.
>>>
>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>>> M: +94 776 477 976
>>>
>>>
>>
>>
>> --
>> Kathiravelu Pradeeban.
>> Software Engineer.
>> Cloud Technologies Team.
>> WSO2 Inc.
>>
>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>> M: +94 776 477 976
>>
>>
>> ___
>> 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/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
e

Re: [Dev] [Bamboo-Build] WSO2 Carbon > WSO2 MS > #12 has FAILED

[Kasun Gajasinghe]

On Mon, Mar 26, 2012 at 11:48 AM, Yumani Ranaweera  wrote:

>
>
> On Sat, Mar 24, 2012 at 12:01 PM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Sat, Mar 24, 2012 at 9:43 AM, Shammi Jayasinghe wrote:
>>
>>> Hi MS RMs,
>>>
>>>  Could you please have a look in to the MS test failures.
>>>
>>
>> I will help MS RMs to overcome this issue.
>>
>> I have few questions.
>> How does web services like sessionTest.js are treated within Carbon? Is
>> that also treated as an AxisService, as same as proxy services, jax-ws
>> services, and real axis2 services are treated? This is a jaggery app,
>> right? If so, what would be the differences of jaggery apps compared to
>> other web service types?  Does sessionisTest.js is a jaggery app? If
>>
>
> MS doesn't have jaggery apps. The .js extension is for JavaScript web
> services.
>
>
>>
>> Further, I see that the names of these test web services are like
>> - admin/upgradeChecker. What does "/" denote?
>> Why these are deployed
>> inside repository/deployment/server/jsservices/admin/ instead
>> of repository/deployment/server/jsservices/ ?
>> This is where the services are deployed -
>> wso2ms-2.3.0-SNAPSHOT/repository/deployment/server/jsservices/admin/sessionTest.js
>>
>
> AFAIU, MS deploys services based on their owners and that's why you get
> admin/sessionTest.js.
>

Thanks Yumani. Just what I needed to hear. Current implementation isn't
flexible to handle cases like this where services are persisted in separate
folders of owners. There can be same service between multiple users too
that need to be handled properly, right?
So, as a solution, I'm thinking of persisting these contents by creating
separate folders for owners inside servicesmetafiles.

ex. wso2ms-2.3.0-SNAPSHOT/repository/deployment/server/*
servicemetafiles/admin*/sessionTest.js

For that I need to understand the logic behind how the location is
calculated. Please share if you can point to relevant code segment.

Thanks,
--KasunG


>
>
>
>> I know it's a lot of questions, but those will help to understand the
>> IOExceptions in integration tests.
>>
>> Thanks,
>> --KasunG
>>
>>
>>> Thanks
>>>
>>> Shammi
>>>
>>>  On Sat, Mar 24, 2012 at 9:23 AM, Bamboo  wrote:
>>>
  [image: Failed]  WSO2 
 Carbon› WSO2
 MS  ›
 #12 
 failed

 This build was manually triggered by 
 BambooBuilder
 .

 No failed tests found, a possible compilation error.
   Failing 
 Jobs
 Job
 Duration Tests[image: Failed]  Default 
 Job
  (Default
 Stage)  9 minutes  No tests found  
 Logs|
 Artifacts
  View
 Online
 | Add 
 Comments

 This message was sent by Atlassian 
 Bamboo
 .

 If you wish to stop receiving these emails edit your user 
 profileor
  notify
 your 
 administrator
 .

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Best Regards,*
>>>
>>> Shammi Jayasinghe*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
>>> mobile: +94 71 4493085
>>>
>>>
>>>
>>> ___
>>> 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** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>> *
>>  *blog: **http://blog.kasunbg.org* 
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>> *
>> *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Yumani Ranaweera
> Associate Technical Lead - QA
> WSO2, Inc. - http://wso2.org
>
> Email : yum...@wso2.com
> Cell: +94 077 7795242
> Blog   : http://yumani.blogspot.com/
>
>


-- 
*Kasun Gajasinghe*
Software Engineer; WSO2 Inc.; http://wso2.com

,
*email: 

Re: [Dev] Infinispan and jgroups printing lots of INFO and WARN during the stratos services start up.

[Afkham Azeez]

It just occurred to me that the Synapse log4j.properties approach will not
work for us. We need to log items logged by tenant code. We will have no
idea what those loggers are in order to enable them. So, we will have to go
with the current approach.

On Mon, Mar 26, 2012 at 1:46 PM, Dimuthu Leelarathne wrote:

> Hi Azeez,
>
>
> On Mon, Mar 26, 2012 at 1:42 PM, Afkham Azeez  wrote:
>
>> I think we need to rethink our logging strategy. For example, in Synapse,
>> unless you explicitly add a logger, the logs don't show up. In Carbon, we
>> have to explicitly disable the loggers. I think we should follow the
>> Synapse model.
>>
>>
> +1
>
> I will hide these logs and add these settings as recommendations to the
> setup.
>
> thanks,
> dimuthu
>
>
>
>> On Mon, Mar 26, 2012 at 1:19 PM, Kathiravelu Pradeeban <
>> pradee...@wso2.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 1:14 PM, Kathiravelu Pradeeban <
>>> pradee...@wso2.com> wrote:
>>>
 [2012-03-26 13:05:34,429] ERROR
 {org.wso2.carbon.caching.infinispan.InfinispanCacheManager} -  Invalid
 cache mode provided. The available values are local, replicated,
 distributed and invalidation
 [2012-03-26 13:05:34,469]  INFO
 {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
 extended standard service  :   StandardService[Catalina]
 [2012-03-26 13:05:34,931]  INFO
 {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN78:
 Starting JGroups Channel
 [2012-03-26 13:05:34,932]  INFO
 {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN88:
 Unable to use any JGroups configuration mechanisms provided in properties
 {}. Using default JGroups configuration!
 [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send
 buffer of socket java.net.DatagramSocket@4edbad67 was set to 640KB,
 but the OS only allocated 131.07KB. This might lead to performance
 problems. Please set your max send buffer in the OS correctly (e.g.
 net.core.wmem_max on Linux)
 [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  receive
 buffer of socket java.net.DatagramSocket@4edbad67 was set to 20MB, but
 the OS only allocated 131.07KB. This might lead to performance problems.
 Please set your max receive buffer in the OS correctly (e.g.
 net.core.rmem_max on Linux)
 [2012-03-26 13:05:35,206]  WARN {org.jgroups.protocols.UDP} -  send
 buffer of socket java.net.MulticastSocket@40ee1aeb was set to 640KB,
 but the OS only allocated 131.07KB. This might lead to performance
 problems. Please set your max send buffer in the OS correctly (e.g.
 net.core.wmem_max on Linux)
 [2012-03-26 13:05:35,207]  WARN {org.jgroups.protocols.UDP} -  receive
 buffer of socket java.net.MulticastSocket@40ee1aeb was set to 25MB,
 but the OS only allocated 131.07KB. This might lead to performance
 problems. Please set your max receive buffer in the OS correctly (e.g.
 net.core.rmem_max on Linux)
 [2012-03-26 13:05:35,323]  INFO
 {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN94:
 Received new cluster view: [localhost-26061|10] [localhost-26061,
 localhost-55353, localhost-29930, localhost-19122]
 [2012-03-26 13:05:35,326]  INFO
 {org.infinispan.remoting.transport.jgroups.JGroupsTransport} -  ISPN79:
 Cache local address is localhost-19122, physical addresses are
 [fe80:0:0:0:250:56ff:fec0:8:34700]
 [2012-03-26 13:05:35,334]  INFO
 {org.infinispan.factories.GlobalComponentRegistry} -  ISPN000128:
 Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL


 I am testing the trunk build of Stratos services with a local setup. I
 am getting the above logs, when I start a few services (tried with BPS and
 IS, and given above is the exact logs copied from BPS). Are these really
 INFO and WARN level logs, or just DEBUG?

>>>
>>> What I meant to ask is, can't we hide these logs from Carbon logs by
>>> default, by setting the log levels to WARN for the respective classes in
>>> log4j.properties?
>>>
>>> Regards,
>>> Pradeeban.
>>>

 Thank you.
 Regards,
 Pradeeban.

 --
 Kathiravelu Pradeeban.
 Software Engineer.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976


>>>
>>>
>>> --
>>> Kathiravelu Pradeeban.
>>> Software Engineer.
>>> Cloud Technologies Team.
>>> WSO2 Inc.
>>>
>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>>> M: +94 776 477 976
>>>
>>>
>>> ___
>>> 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/
>> * **
>> email: **az...@wso2.com* * c

Re: [Dev] Reporting Admin Services Listed in ESB Service Listing Page

[Hiranya Jayathilaka]

On Mon, Mar 26, 2012 at 12:42 PM, Sinthuja Ragendran wrote:

> Hi,
>
> This services are from reporting component and it's fixed now.
>

What are the component that need to be updated in my working copy?

Thanks,
Hiranya


>
> Thanks,
> Sinthuja.
>
> On Mon, Mar 26, 2012 at 12:21 PM, Hiranya Jayathilaka wrote:
>
>> Following services are listed in the service listing page of ESB:
>>
>> DBReportingService
>> JrxmlFileUploader
>> ReportingResourcesSupplier
>> ReportTemplateAdmin
>>
>> What are these services? Looks like some admin services which are not
>> properly secured!
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Reporting Admin Services Listed in ESB Service Listing Page

[Sinthuja Ragendran]

You have to take svn up in the reporting component [1].

The changes were made to only two modules.
1. org.wso2.carbon.reporting.core
2. org.wso2.carbon.reporting.template.core

[1]
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/components/reporting

Thanks,
Sinthuja.


On Mon, Mar 26, 2012 at 2:00 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Mar 26, 2012 at 12:42 PM, Sinthuja Ragendran wrote:
>
>> Hi,
>>
>> This services are from reporting component and it's fixed now.
>>
>
> What are the component that need to be updated in my working copy?
>
> Thanks,
>  Hiranya
>
>
>>
>> Thanks,
>> Sinthuja.
>>
>> On Mon, Mar 26, 2012 at 12:21 PM, Hiranya Jayathilaka 
>> wrote:
>>
>>> Following services are listed in the service listing page of ESB:
>>>
>>> DBReportingService
>>> JrxmlFileUploader
>>> ReportingResourcesSupplier
>>> ReportTemplateAdmin
>>>
>>> What are these services? Looks like some admin services which are not
>>> properly secured!
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Associate Technical Lead;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

On Mon, Mar 26, 2012 at 12:11 PM, Kasun Gajasinghe  wrote:

>
>
> On Mon, Mar 26, 2012 at 11:45 AM, Hiranya Jayathilaka wrote:
>
>> We see a lot of persistence exceptions in the latest ESB packs:
>>
>> org.wso2.carbon.core.persistence.PersistenceException: A transaction is
>> already started. Nested transactions are no longer supported in the new
>> model
>> at
>> org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.beginTransaction(ServiceGroupFilePersistenceManager.java:62)
>> at
>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.updateParameter(AbstractPersistenceManager.java:136)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.updateServiceParameter(ServicePersistenceManager.java:775)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:592)
>> at
>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:282)
>> at
>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>> at
>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>> at
>> org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:336)
>> at
>> org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:566)
>> at
>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.deployServices(ConfigurationUpdater.java:286)
>>
>> What does this mean? Things seem to work find in spite of the exceptions
>> though.
>>
>
> The way to make sure things work is to restart the server and see whether
> the changed parameters are still there.
>
> Does this seen in server startup? If not, please tell me how to reproduce
> this.
>

I just noticed that this happens on startup too.


>
> Thanks,
> --KasunG
>
>
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>> ___
>> 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** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
> *
>  *blog: **http://blog.kasunbg.org* 
>
> *
> twitter: **http://twitter.com/kasunbg* 
>
> *
> *
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

Hi,

On a hunch I just tried to engage security on a proxy service. It doesn't
work :( I get an error in the UI saying security cannot be enabled for the
service and I get the following exception on the console:

[2012-03-26 14:09:07,638] ERROR - RPCInOnlyMessageReceiver Service with
name test not found.
org.wso2.carbon.security.SecurityConfigException: Service with name test
not found.
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:610)
at
org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
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.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:60)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
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.apache.axis2.AxisFault: Service with name test not found.
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:739)
... 39 more
Caused by:
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path
/_system/config/repository/axis2/service-groups/test/services/test
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)
at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:118)
at
org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:515)
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:691)
... 39 more

Thanks,
Hiranya


On Mon, Mar 26, 2012 at 2:06 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Mar 26, 2012 at 12:11 PM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 11:45 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>> We see a lot of persistence exceptions in the latest ESB packs:
>>>
>>> org.wso2.carbon.core.persistence.PersistenceException: A transaction is
>>> already started. Nested transactions are no longer supported in t

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

On Mon, Mar 26, 2012 at 2:10 PM, Afkham Azeez  wrote:

>
>
> On Mon, Mar 26, 2012 at 2:05 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:01 PM, Afkham Azeez  wrote:
>>
>>> But you said earlier in this thread
>>>
>>> "We don't need Axis2 level persistence for proxy services. Synapse has
>>> its own persistence logic for proxy services, which takes care of saving
>>> proxy services to the file system."
>>>
>>> But it seems proxy services do need Axis2 level persistence as well
>>> because things like enabling security, engaging modules etc. are handled at
>>> that level.
>>>
>>
>> We need a place to store policies etc. But saving the proxy service
>> configuration is taken care of by our components. What sort of information
>> are written to the file system by this new persistence impl?
>>
>
> Anything that makes changes to an AxisService, ServiceGroup or Axis2
> Module. e.g. engaged modules, enabled policies... basically everything
> related to service-mgt, module-mgt, security-mgt and other such components.
> Everything that used to be stored into registry are now stored in the file
> system.
>

Ok then I guess we need that part too. And I can see that a file has been
created for my proxy service under the metafiles directory (see the
attachment test.xml). Still I'm confused as to why so many
PersistenceExceptions are thrown when updating the configuration or
starting the ESB. Also why can't I enable security on my proxy services?
>From the stacktrace it looks like SecurityConfigAdmin is trying to locate
the service in the registry. Is that behavior correct?


>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> On Mon, Mar 26, 2012 at 1:59 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 1:41 PM, Afkham Azeez  wrote:

>
>
> On Mon, Mar 26, 2012 at 12:50 PM, Hiranya Jayathilaka <
> hira...@wso2.com> wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 12:31 PM, Afkham Azeez wrote:
>>
>>> If you do things like securing a proxy service using the Carbon
>>> service security UI, where does that information get persisted?
>>>
>>
>> Policy is saved to the registry as usual. Service configuration is
>> saved to the same proxy service file:
>>
>> 
>>...
>>
>>
>> 
>>
>>
>
>
> Is this done through an AxisObserver?
>
  Is the security UI handling proxy services in a different way?
>

 We do have an observer, but security (and other QoS stuff) is handled
 the same way as in Axis2 services.


> Is so, we can check for proxy services in the default
> DeploymentInterceptor, and skip those proxy services. The bottom line is,
> proxy service persistence through the DeploymentInterceptor has been
> happening all along.
>

 That's correct, and it was not by accident. Proxy services were also
 stored in the registry along with all other Axis2 services. But Synapse
 loads the services by reading the artifacts in the file system
 (synapse-config directory). So when applying security or some other policy
 we have an observer which persists the relevant changes to the file system.
 So in effect what we had was a hybrid persistence model. The Synapse part
 is stored in the file system and the Axis2 part is stored in the registry.

 Thanks,
 Hiranya


>
>>>
>>> On Mon, Mar 26, 2012 at 12:19 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>


 On Mon, Mar 26, 2012 at 12:11 PM, Kasun Gajasinghe >>> > wrote:

>
>
> On Mon, Mar 26, 2012 at 11:45 AM, Hiranya Jayathilaka <
> hira...@wso2.com> wrote:
>
>> We see a lot of persistence exceptions in the latest ESB packs:
>>
>> org.wso2.carbon.core.persistence.PersistenceException: A
>> transaction is already started. Nested transactions are no longer 
>> supported
>> in the new model
>> at
>> org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.beginTransaction(ServiceGroupFilePersistenceManager.java:62)
>> at
>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.updateParameter(AbstractPersistenceManager.java:136)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.updateServiceParameter(ServicePersistenceManager.java:775)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:592)
>> at
>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:282)
>> at
>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>> at
>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.jav

Re: [Dev] PersistenceExceptions in ESB

[Afkham Azeez]

On Mon, Mar 26, 2012 at 2:16 PM, Hiranya Jayathilaka wrote:\
>
> Ok then I guess we need that part too. And I can see that a file has been
> created for my proxy service under the metafiles directory (see the
> attachment test.xml). Still I'm confused as to why so many
> PersistenceExceptions are thrown when updating the configuration or
> starting the ESB. Also why can't I enable security on my proxy services?
> From the stacktrace it looks like SecurityConfigAdmin is trying to locate
> the service in the registry. Is that behavior correct?
>

It means that the security component still has not been fixed. All
persistence related stuff should strictly be in the file system only.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Kasun Gajasinghe]

On Mon, Mar 26, 2012 at 2:11 PM, Hiranya Jayathilaka wrote:

> Hi,
>
> On a hunch I just tried to engage security on a proxy service. It doesn't
> work :( I get an error in the UI saying security cannot be enabled for the
> service and I get the following exception on the console:
>

Please try setting anything other than security :)
I haven't committed my changes for security yet, because there are
uncertainties about it's behavior. All the relevant code segments in
security are rewritten.

I will check this in a latest ESB release. There hasn't been any time to
test this on proxy services. Only jax-ws, axis2, services and axis2 modules
are tested.


>
> [2012-03-26 14:09:07,638] ERROR - RPCInOnlyMessageReceiver Service with
> name test not found.
> org.wso2.carbon.security.SecurityConfigException: Service with name test
> not found.
>  at
> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
> at
> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
>  at
> org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:610)
> at
> org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>  at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
>  at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
>  at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>  at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
>  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.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
>  at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:60)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
> 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.apache.axis2.AxisFault: Service with name test not found.
> at
> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:739)
>  ... 39 more
> Caused by:
> org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
> Resource does not exist at path
> /_system/config/repository/axis2/service-groups/test/services/test
>  at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)
> at
> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRe

[Dev] Bamboo Status update

[Shammi Jayasinghe]

Hi All,

   From last Monday we had configured bamboo plans for each and every
product. But when building products in separate plans we had
to get a check out of entire platform for each and every products. It means
14 check outs of platform. But this was very time consuming
and consumed huge disk space.

As a solution for this after having off-line discussion with Carbon Team,
we changed the build strategy. In that instead of taking 14 check
outs to build product plans , we used the source checked out for building
platform plan. With this way we could build the products with a
small amount of time compared to earlier build strategy.

But as all of you know, when building products with this way, It generated
failure notice though the product build is executed with tests and
all the modules build successfully. Eg : IS build. This was because, bamboo
was not able to find out the tests reports in the directory we
specified for sure-fire reports. We tried with various combinations of
relative paths and was not success.

So after having an off-line discussion with pradeep (He had discussed with
Azeez and Sameera), we are moving back to the earlier build
strategy until we figure out a proper solution to the above problem.

There will be only four bamboo plans for building entire platform.

1. Orbit
2. Kernel
3. Platform (This will build up to samples)
4. Products.


Thanks
Shammi

-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Lakmali Baminiwatta]

Hi,

I am also experiencing similar issues on DSS product & service. When a
service is saved the following exception occurs.

 ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -
Unable to handle new service addition. Service: H2BasicService
java.lang.NullPointerException
at
org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
at
org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
at
org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
at
org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
at
org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
at
org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
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)

Also when engaging the security on services it fails with the following
exception.

 ERROR {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -  Service
with name H2BasicService not found.
org.wso2.carbon.security.SecurityConfigException: Service with name
H2BasicService not found.
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
at
org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:610)
at
org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.cat

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

I tried enabling caching for the service. It did get applied as expected.
But the change didn't survive a restart. I think this is same for other QoS
modules too (throttling, RM etc).

Thanks,
Hiranya

On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta wrote:

> Hi,
>
> I am also experiencing similar issues on DSS product & service. When a
> service is saved the following exception occurs.
>
>  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -
> Unable to handle new service addition. Service: H2BasicService
> java.lang.NullPointerException
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
> at
> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>
> at
> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
> at
> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
> at
> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>
> 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)
>
> Also when engaging the security on services it fails with the following
> exception.
>
>  ERROR {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
> Service with name H2BasicService not found.
> org.wso2.carbon.security.SecurityConfigException: Service with name
> H2BasicService not found.
>
> at
> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
> at
> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
> at
> org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:610)
> at
> org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
> at
> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
> at
> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
> at
> org.eclipse.equino

Re: [Dev] Unable to locate the stratos configurations file, etc in stratos AS startup

[Kathiravelu Pradeeban]

Hi,
That file is not included in to the services, and is included into the
manager only. Pls take an svn update from the components/stratos/org.wso2.
carbon.stratos.common and products/manager.

The check to see whether the eula.xml is made to log at debug level, since
it won't be configured in services, and the default configuration is used
in case of unavailability.

Thank you.
Regards,
Pradeeban.


On Fri, Mar 23, 2012 at 8:14 PM, Supun Malinga  wrote:

> Hi Sanjeewa,
>
> Still getting,
> [2012-03-23 20:07:50,084] ERROR
> {org.wso2.carbon.stratos.common.util.CommonUtil} -  Unable to locate the
> stratos EULA file. Default value will be used.
>
> eula.xml is not there in conf.
>
> thanks,
>
> On Fri, Mar 23, 2012 at 12:52 PM, Sanjeewa Malalgoda wrote:
>
>> Hi,
>> Added eula.xml file to common feature. Supun please take svn up
>> stratos/common feature build it and then build appserver service.
>> Thanks.
>>
>>
>> On Fri, Mar 23, 2012 at 12:41 PM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> Hi,
>>> cloud-services-desc.xml, identity.xml,  multitenancy-packages.xml,
>>>  stratos.xml,  usage-throttling-agent-config.xml are copying from common
>>> feature. But my problem is so far where that eula.xml file copied. Is it ok
>>> to add it to common feature. Because manager/conf also has same file.
>>>
>>>
>>>
>>> On Fri, Mar 23, 2012 at 12:28 PM, Kathiravelu Pradeeban <
>>> pradee...@wso2.com> wrote:
>>>
 Hi Sanjeewa,
 eula.xml is read and used by the stratos common feature. Hence it
 should also be copied from the same, just like the stratos.xml.

 Thank you.
 Regards,
 Pradeeban.


 On Fri, Mar 23, 2012 at 12:24 PM, Amila Maha Arachchi 
 wrote:

> Hi Sanjeewa,
>
> What about
> 1. usage-throttling-agent-config.xml
> 2. identity.xml
>
> Which are in the stratos common feature. We need those files also,
> right?
>
> Also, please update all the stratos services which you have added the
> stratos common feature into. Also make sure the build is not broken due to
> the changes.
>
> Regards,
> AmilaM.
>
>
> On Fri, Mar 23, 2012 at 12:12 PM, Sanjeewa Malalgoda <
> sanje...@wso2.com> wrote:
>
>> Hi,
>> Added entry to bin.xml file to copy stratos.xml file since it was not
>> there.
>> thanks.
>>
>>
>> On Thu, Mar 22, 2012 at 11:31 PM, Kathiravelu Pradeeban <
>> pradee...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, Mar 22, 2012 at 11:22 PM, Supun Malinga wrote:
>>>
 Hi,

 Error,
 [2012-03-22 23:20:06,439] ERROR
 {org.wso2.carbon.stratos.common.util.CommonUtil} -  Unable to locate 
 the
 stratos configurations file. Default Settings will be used.
  [2012-03-22 23:20:06,439] ERROR
 {org.wso2.carbon.stratos.common.util.CommonUtil} -  Unable to locate 
 the
 stratos EULA file. Default value will be used.
 [2012-03-22 23:20:06,454] ERROR
 {org.wso2.carbon.stratos.common.util.CommonUtil} -  Unable to locate 
 the
 stratos configurations file. Default Settings will be used.

 Also it would be helpful if the error says exactly what file(s)
 missing.

>>>
>>> I guess, it says what files are missing - in a more human-friendly
>>> manner..
>>> stratos.xml (stratos configuration file) and eula.xml (EULA file)
>>> are missing.
>>>
>>> Must be a recent change to read the configurations from the
>>> stratos.common component caused this (?).
>>>
>>> Regards,
>>> Pradeeban.
>>>

 thanks,
 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com 
 mobile - 071 56 91 321


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Kathiravelu Pradeeban.
>>> Software Engineer.
>>> Cloud Technologies Team.
>>> WSO2 Inc.
>>>
>>> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
>>> M: +94 776 477 976
>>>
>>>
>>
>>
>> --
>> *Sanjeewa Malalgoda*
>> Software Engineer
>> **
>> *WSO2, Inc.*
>> lean.enterprise.middleware.
>>
>> mobile : +94 713068779
>> web: http://wso2.com
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>> [image:
>> http://wso2.com/wp-content/themes/wso2ng-v2/images/logos/stratos_logo_h42.gif]
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
>>>

Re: [Dev] PersistenceExceptions in ESB

[Kasun Gajasinghe]

On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka wrote:

> I tried enabling caching for the service. It did get applied as expected.
> But the change didn't survive a restart. I think this is same for other QoS
> modules too (throttling, RM etc).


Does the relevant policy got added to the relevant metafile?

Lakmali, I'll look into this. I've already answered your second issue.
As I've been told earlier, please send the logs as soon as you faced with
an issue related to persistence. At this point of time, this implementation
isn't tested in other products than Kernel, and AppServer.



> Thanks,
> Hiranya
>
>
> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta wrote:
>
>> Hi,
>>
>> I am also experiencing similar issues on DSS product & service. When a
>> service is saved the following exception occurs.
>>
>>  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -
>> Unable to handle new service addition. Service: H2BasicService
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
>> at
>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>>
>> at
>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>> at
>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>> at
>> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
>> at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>> at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>> at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>> at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>> at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>
>> 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)
>>
>> Also when engaging the security on services it fails with the following
>> exception.
>>
>>  ERROR {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
>> Service with name H2BasicService not found.
>> org.wso2.carbon.security.SecurityConfigException: Service with name
>> H2BasicService not found.
>>
>> at
>> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
>> at
>> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
>> at
>> org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:610)
>> at
>> org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at
>> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
>> at
>> org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtil

Re: [Dev] PersistenceExceptions in ESB

[Supun Malinga]

Hi,
On Mon, Mar 26, 2012 at 12:19 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Mar 26, 2012 at 12:11 PM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 11:45 AM, Hiranya Jayathilaka 
>> wrote:
>>
>>> We see a lot of persistence exceptions in the latest ESB packs:
>>>
>>> org.wso2.carbon.core.persistence.PersistenceException: A transaction is
>>> already started. Nested transactions are no longer supported in the new
>>> model
>>> at
>>> org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.beginTransaction(ServiceGroupFilePersistenceManager.java:62)
>>> at
>>> org.wso2.carbon.core.persistence.AbstractPersistenceManager.updateParameter(AbstractPersistenceManager.java:136)
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.updateServiceParameter(ServicePersistenceManager.java:775)
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:592)
>>> at
>>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:282)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:336)
>>> at
>>> org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:566)
>>> at
>>> org.wso2.carbon.mediation.configadmin.ConfigurationUpdater.deployServices(ConfigurationUpdater.java:286)
>>>
>>> What does this mean? Things seem to work find in spite of the exceptions
>>> though.
>>>
>>
>> The way to make sure things work is to restart the server and see whether
>> the changed parameters are still there.
>>
>
> We don't need Axis2 level persistence for proxy services. Synapse has its
> own persistence logic for proxy services, which takes care of saving proxy
> services to the file system.
>

I'm having a concern on this. Does this suggest that proxy services
meta-data are already persisted into file system so that
new persistence model need not handle that?


>
>
>>
>> Does this seen in server startup? If not, please tell me how to reproduce
>> this.
>>
>
> Create a proxy service and then update the ESB configuration from the
> source view.
>
>
>>
>> Thanks,
>> --KasunG
>>
>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Associate Technical Lead;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>> ___
>>> 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** cell: **+94 (77) 678-0813*
>> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
>> *
>>  *blog: **http://blog.kasunbg.org* 
>>
>> *
>> twitter: **http://twitter.com/kasunbg* 
>>
>> *
>> *
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Test Automation Dashboard

[Srinath Perera]

do we have this Dashboard deployed with our Bamboo automation tests?
if so, please send a link.

--Srinath

On Sat, Mar 17, 2012 at 7:54 PM, Amila Maha Arachchi  wrote:
> Nice work!
>
> Regards,
> AmilaM.
>
> On Fri, Mar 16, 2012 at 4:28 PM, Nuwan Wimalasekara  wrote:
>>
>> Hi all,
>>
>> One of main drawback in System test framework was to keep test report
>> history in place where we can see test status and stats. System test
>> framework generate test reports as TestNG result XML files. But those
>> reports only show the result of last test run. So there is no way to find
>> past results by build. Therefore we added new feature to System test
>> framework to parse result XML files and write result data to a database
>> after each test framework execution. Dashboard is capable for display those
>> result in proper manner.
>>
>> Dashboard address the visualization of the test results and history using
>> Charts. Test Automation dashboard is a web application which display test
>> results and history of System test framework builds. Web application is
>> developed using JSP technology. It is bundled as a webapp file and can be
>> deployed on any java application server such as WSO2 App server, Tomcat
>> etc.. We have designed the Dashboard as separate project and integrated to
>> System test framework. Related dashboard DB configuration can be found in
>> framework.properties file in System test framework. So the idea is to reuse
>> the Dashboard with any project which generate TestNG result XML files.
>> Automation dashboard source can be found at [1]
>>
>> How to deploy Dashboard :
>>
>> 1). Check out source of a dashboard from [1]
>> 2). Build the source to generate war file (mvn clean package)
>> 3). Extract a war file and open dbconf.properties in /WEB-INF/classes
>> directory.
>> 4). Configure database connection properties(jdbc url should be same as
>> database configuration in framework.property)
>> 5). Deploy the war fine on a application server.
>> 6). Run System test framework and check results using dashboard
>>
>> It will display all test result and you can navigate result history also.
>>
>> Please refer attached screen shots of Dashboard. DB script and table
>> structure is also attached.
>>
>> Your feedbacks and suggestions are welcome.
>>
>> Thanks Chanaka for the support given for theme design.
>>
>> Thanks,
>> NuwanW /Chamara
>>
>>
>> [1] https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/dashboard/
>> --
>> Nuwan Wimalasekara
>> Software Engineer - Test Automation
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> phone: +94 71 668 4620
>>
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> Amila Maharachchi
> Senior Software Engineer; 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
>



-- 

Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon > WSO2 CSG > #20 has FAILED. Change made by 14 authors.

[Bamboo]

---
WSO2 Carbon > WSO2 CSG > #20 failed.
---
Code has been updated by rajika, dilshan, lalaji, madhuka, amani, damitha, 
shammi, sumedha, supunm, teague, ajithn, isuruw, nirmal, nuwan.
No failed tests found, a possible compilation error.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CSG-20/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.


--
Code Changes
--
damitha (123841):

>Applying the patch sent by Lahiru Sandaruwan for Worker node registration 
>service code. 
>

nuwan (123860):

>changing set to list

rajika (123848):

>Updated the release note.



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Afkham Azeez]

Folks,
The reason for committing this was to get other people also involved in
fixing the relevant components. KasunG cannot find & fix all the affected
components. The component authors have directly manipulated registry
resources bypassing the persisten API. Hence switching the persistence API
which should have been trivial, has become a nightmare. So, we expect all
teams to cooperate and help with testing & fixing these issues.

Azeez

On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe  wrote:

>
>
> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka wrote:
>
>> I tried enabling caching for the service. It did get applied as expected.
>> But the change didn't survive a restart. I think this is same for other QoS
>> modules too (throttling, RM etc).
>
>
>  Does the relevant policy got added to the relevant metafile?
>
> Lakmali, I'll look into this. I've already answered your second issue.
> As I've been told earlier, please send the logs as soon as you faced with
> an issue related to persistence. At this point of time, this implementation
> isn't tested in other products than Kernel, and AppServer.
>
>
>
>> Thanks,
>> Hiranya
>>
>>
>> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta wrote:
>>
>>> Hi,
>>>
>>> I am also experiencing similar issues on DSS product & service. When a
>>> service is saved the following exception occurs.
>>>
>>>  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -
>>> Unable to handle new service addition. Service: H2BasicService
>>> java.lang.NullPointerException
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
>>> at
>>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>>>
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>>> at
>>> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
>>> at
>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>>> at
>>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>>> at
>>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>>> at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>>> at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>> at
>>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>>
>>> 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)
>>>
>>> Also when engaging the security on services it fails with the following
>>> exception.
>>>
>>>  ERROR {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
>>> Service with name H2BasicService not found.
>>> org.wso2.carbon.security.SecurityConfigException: Service with name
>>> H2BasicService not found.
>>>
>>> at
>>> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
>>> at
>>> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
>>> at
>>> org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:610)
>>> at
>>> org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe  wrote:

>
>
> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka wrote:
>
>> I tried enabling caching for the service. It did get applied as expected.
>> But the change didn't survive a restart. I think this is same for other QoS
>> modules too (throttling, RM etc).
>
>
> Does the relevant policy got added to the relevant metafile?
>

Yes it does. I debugged this case a little bit, and I think the problem
occurs because our proxy service observer expects to find the relevant
policies in the registry. But they are no longer stored in the registry.

In the past it was just a matter of updating the proxy service
configuration with a key that points to the appropriate policy in the
registry:



ESB knows how to resolve registry keys. But with the new model I don't know
how the same behavior can be achieved.

Thanks,
Hiranya


>
> Lakmali, I'll look into this. I've already answered your second issue.
> As I've been told earlier, please send the logs as soon as you faced with
> an issue related to persistence. At this point of time, this implementation
> isn't tested in other products than Kernel, and AppServer.
>
>
>
>> Thanks,
>> Hiranya
>>
>>
>> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta wrote:
>>
>>> Hi,
>>>
>>> I am also experiencing similar issues on DSS product & service. When a
>>> service is saved the following exception occurs.
>>>
>>>  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -
>>> Unable to handle new service addition. Service: H2BasicService
>>> java.lang.NullPointerException
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
>>> at
>>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>>>
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>>> at
>>> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
>>> at
>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>>> at
>>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>>> at
>>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>>> at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>>> at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>>> at
>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>> at
>>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>>
>>> 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)
>>>
>>> Also when engaging the security on services it fails with the following
>>> exception.
>>>
>>>  ERROR {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
>>> Service with name H2BasicService not found.
>>> org.wso2.carbon.security.SecurityConfigException: Service with name
>>> H2BasicService not found.
>>>
>>> at
>>> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
>>> at
>>> org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
>>> at
>>> org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:610)
>>> at
>>> org.wso2.carbon.security.config.service.SecurityConfigAdminService.applySecurity(SecurityConfigAdminService.java:45)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMetho

Re: [Dev] [Bamboo-Build] WSO2 Carbon > WSO2 CSG > #20 has FAILED. Change made by 14 authors.

[Shammi Jayasinghe]

This is manually stopped. Pls ignore.

thanks
Shammi

On Mon, Mar 26, 2012 at 2:37 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 
> Carbon› WSO2
> CSG  ›
> #20 
> failed
>
> Code has been updated by 
> rajika,
> dilshan ,
> lalaji ,
> madhuka ,
> amani ,
> damitha ,
> shammi ,
> sumedha ,
> supunm ,
> teague ,
> ajithn ,
> isuruw ,
> nirmal ,
> nuwan .
>
> No failed tests found, a possible compilation error.
>   Failing 
> Jobs
> Job Duration Tests[image: Failed]  Default 
> Job 
> (Default
> Stage)  3 minutes  No tests found  
> Logs|
> Artifacts
>  Code
> Changes
>   View
> all 26 code 
> changes
> sumedha 
> Fixed registerAccessToken method & added a test case  123865
> teague
> updated "M4" in all places  123864
> madhuka
> Search API is Fixed with UI level with jaggery Level  123863   23 more
> changes…
>  View
> Online 
> | Add 
> Comments
>
> This message was sent by Atlassian 
> Bamboo
> .
>
> If you wish to stop receiving these emails edit your user 
> profileor
>  notify
> your 
> administrator
> .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe  wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka wrote:
>>
>>> I tried enabling caching for the service. It did get applied as
>>> expected. But the change didn't survive a restart. I think this is same for
>>> other QoS modules too (throttling, RM etc).
>>
>>
>>  Does the relevant policy got added to the relevant metafile?
>>
>
> Yes it does. I debugged this case a little bit, and I think the problem
> occurs because our proxy service observer expects to find the relevant
> policies in the registry. But they are no longer stored in the registry.
>
> In the past it was just a matter of updating the proxy service
> configuration with a key that points to the appropriate policy in the
> registry:
>
> 
>
> ESB knows how to resolve registry keys. But with the new model I don't
> know how the same behavior can be achieved.
>

This is going to affect all QoS aspects of ESB including security. How do
we solve this problem? Synapse can only load policies from the registry.


>
> Thanks,
> Hiranya
>
>
>>
>> Lakmali, I'll look into this. I've already answered your second issue.
>> As I've been told earlier, please send the logs as soon as you faced with
>> an issue related to persistence. At this point of time, this implementation
>> isn't tested in other products than Kernel, and AppServer.
>>
>>
>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta 
>>> wrote:
>>>
 Hi,

 I am also experiencing similar issues on DSS product & service. When a
 service is saved the following exception occurs.

  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -
 Unable to handle new service addition. Service: H2BasicService
 java.lang.NullPointerException
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
 at
 org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)

 at
 org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
 at
 org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
 at
 org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at
 org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
 at
 org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
 at
 org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
 at
 org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
 at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
 at
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)

 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)

 Also when engaging the security on services it fails with the following
 exception.

  ERROR {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
 Service with name H2BasicService not found.
 org.wso2.carbon.security.SecurityConfigException: Service with name
 H2BasicService not found.

 at
 org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:764)
 at
 org.wso2.carbon.security.config.SecurityConfigAdmin.applyPolicy(SecurityConfigAdmin.java:633)
>>>

Re: [Dev] -DosgiConsole= is not working

[Sameera Jayasoma]

Hi Azeez,

This is working in my machine and checked with Azeez's machine also. And
its working. Might be due to some dropins issue.

Thanks
Sameera.

On Sun, Mar 25, 2012 at 2:25 PM, Pradeep Fernando  wrote:

> Hi,
>
> It worked after our tomcat modifications. The possible break points,
>
> 1. xml config file movements
> 2 refactoring of org.wso2.carbon.server
>
> --Pradeep
>



-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BPEL Monitoring for BAM2

[Srinath Perera]

+1 for the approach for sending custom values

When we send custom values, do we send information about the workflow
and instance ID etc?

I think we should we also have a default  set of monitoring data we
can push from a BPEL workflow to BAM (just like default Service stats)
that can be turned on easily. I think we can do this easily by
extending the ODE workflow event listener to emit workflow monitoring
data. It should send information like services invoked, how long the
instance ran,  .. requests send and received etc.

--Srinath

On Mon, Mar 12, 2012 at 3:28 PM, Nandika Jayawardana  wrote:
> Hi all,
>    We came up with a model to publish business process data to the
> BAM2 server in the following way to monitor Business Process.
> Basically,the idea is to implement an extension activity which would
> publish the process data to BAM. Developer of the business process can
> specify which data should be published to the bam in the following
> way. We took the standard 'from' syntax from bpel for selecting the
> data to be published. Extension activity xml syntax would be as
> follows.
>
> 
>      
>          
>                 
>          +
>      
> 
>
> The value within the from section could be either a variable or an xpath.
> Syntax for publishing from a variable
>
> 
>      
>         
>            
>         
>         
>            
>         
>      
> 
>
> Syntax for publishing from xpath
>
> 
>        
>            
>                
>                         queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
>                
>            
>        
> 
>
> 
>        
>            
>                $input.part/tns:input
>            
>        
> 
>
> Publishing from xpath is not essential as it is possible to extract
> values using xpath in the bam analyzer as well.  BAM server
> configuration data will go into the deploy.xml.
>
> Regards
> Nandika
>
> --
> Nandika Jayawardana
> Technical Lead
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev



-- 

Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] -DosgiConsole= is not working

[Sameera Jayasoma]

On Sun, Mar 25, 2012 at 1:50 PM, Senaka Fernando  wrote:

> Hi all,
>
> This was working fine until very recently. If this is broken, this might
> be due to a fix that was done during the last few days.
>
> By the way, AFAIU, we should be able to write integration tests to
> validate things like this.
>

+1 having an integrations tests..

Sameera.


> Thanks,
> Senaka.
>
> On Sun, Mar 25, 2012 at 12:35 PM, Afkham Azeez  wrote:
>
>> The server does not startup, and simply seems to hang.
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Afkham Azeez]

How do you set the Registry to Synapse? Does it depend on the Registry API?
If so, we can have a Registry implementation which works with the file
system persistence structure.

On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka 
>>> wrote:
>>>
 I tried enabling caching for the service. It did get applied as
 expected. But the change didn't survive a restart. I think this is same for
 other QoS modules too (throttling, RM etc).
>>>
>>>
>>>  Does the relevant policy got added to the relevant metafile?
>>>
>>
>> Yes it does. I debugged this case a little bit, and I think the problem
>> occurs because our proxy service observer expects to find the relevant
>> policies in the registry. But they are no longer stored in the registry.
>>
>> In the past it was just a matter of updating the proxy service
>> configuration with a key that points to the appropriate policy in the
>> registry:
>>
>> 
>>
>> ESB knows how to resolve registry keys. But with the new model I don't
>> know how the same behavior can be achieved.
>>
>
> This is going to affect all QoS aspects of ESB including security. How do
> we solve this problem? Synapse can only load policies from the registry.
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Lakmali, I'll look into this. I've already answered your second issue.
>>> As I've been told earlier, please send the logs as soon as you faced
>>> with an issue related to persistence. At this point of time, this
>>> implementation isn't tested in other products than Kernel, and AppServer.
>>>
>>>
>>>
 Thanks,
 Hiranya


 On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta 
 wrote:

> Hi,
>
> I am also experiencing similar issues on DSS product & service. When a
> service is saved the following exception occurs.
>
>  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager}
> -  Unable to handle new service addition. Service: H2BasicService
> java.lang.NullPointerException
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
> at
> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>
> at
> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
> at
> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
> at
> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>
> 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)
>
> Also when engaging the security on services it fails with the
> following exception.
>
>  ERROR {org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver} -
> Service w

Re: [Dev] Test Automation Dashboard

[Chamara Silva]

On Mon, Mar 26, 2012 at 2:45 PM, Srinath Perera  wrote:

> do we have this Dashboard deployed with our Bamboo automation tests?
> if so, please send a link.
>

If we are going to host it in bamboo, we need to run dashboard FE
in separate machine. shall we use lab machine instance for it?

Thanks,
Chamara Silva

>
> --Srinath
>
> On Sat, Mar 17, 2012 at 7:54 PM, Amila Maha Arachchi 
> wrote:
> > Nice work!
> >
> > Regards,
> > AmilaM.
> >
> > On Fri, Mar 16, 2012 at 4:28 PM, Nuwan Wimalasekara 
> wrote:
> >>
> >> Hi all,
> >>
> >> One of main drawback in System test framework was to keep test report
> >> history in place where we can see test status and stats. System test
> >> framework generate test reports as TestNG result XML files. But those
> >> reports only show the result of last test run. So there is no way to
> find
> >> past results by build. Therefore we added new feature to System test
> >> framework to parse result XML files and write result data to a database
> >> after each test framework execution. Dashboard is capable for display
> those
> >> result in proper manner.
> >>
> >> Dashboard address the visualization of the test results and history
> using
> >> Charts. Test Automation dashboard is a web application which display
> test
> >> results and history of System test framework builds. Web application is
> >> developed using JSP technology. It is bundled as a webapp file and can
> be
> >> deployed on any java application server such as WSO2 App server, Tomcat
> >> etc.. We have designed the Dashboard as separate project and integrated
> to
> >> System test framework. Related dashboard DB configuration can be found
> in
> >> framework.properties file in System test framework. So the idea is to
> reuse
> >> the Dashboard with any project which generate TestNG result XML files.
> >> Automation dashboard source can be found at [1]
> >>
> >> How to deploy Dashboard :
> >>
> >> 1). Check out source of a dashboard from [1]
> >> 2). Build the source to generate war file (mvn clean package)
> >> 3). Extract a war file and open dbconf.properties in /WEB-INF/classes
> >> directory.
> >> 4). Configure database connection properties(jdbc url should be same as
> >> database configuration in framework.property)
> >> 5). Deploy the war fine on a application server.
> >> 6). Run System test framework and check results using dashboard
> >>
> >> It will display all test result and you can navigate result history
> also.
> >>
> >> Please refer attached screen shots of Dashboard. DB script and table
> >> structure is also attached.
> >>
> >> Your feedbacks and suggestions are welcome.
> >>
> >> Thanks Chanaka for the support given for theme design.
> >>
> >> Thanks,
> >> NuwanW /Chamara
> >>
> >>
> >> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/dashboard/
> >> --
> >> Nuwan Wimalasekara
> >> Software Engineer - Test Automation
> >> WSO2, Inc.: http://wso2.com
> >> lean. enterprise. middleware
> >>
> >> phone: +94 71 668 4620
> >>
> >>
> >>
> >>
> >>
> >> ___
> >> Dev mailing list
> >> Dev@wso2.org
> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
> >>
> >
> >
> >
> > --
> > Amila Maharachchi
> > Senior Software Engineer; 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
> >
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>http://www.cs.indiana.edu/~hperera/
>http://srinathsview.blogspot.com/
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Suminda Chamara Silva
WSO2 Inc.
Mobile: +94718302858
blog: http://chamaras.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BPEL Monitoring for BAM2

[Waruna Ranasinghe]

On Mon, Mar 26, 2012 at 2:59 PM, Srinath Perera  wrote:

> +1 for the approach for sending custom values
>
> When we send custom values, do we send information about the workflow
> and instance ID etc?
>
No, but the workflow designer can add the instance ID to the variable he
chose to publish into BAM, if he needs it for the analysis.


>
> I think we should we also have a default  set of monitoring data we
> can push from a BPEL workflow to BAM (just like default Service stats)
> that can be turned on easily. I think we can do this easily by
> extending the ODE workflow event listener to emit workflow monitoring
> data. It should send information like services invoked, how long the
> instance ran,  .. requests send and received etc.
>
+1.
Lets add this to our roadmap

Thanks,
Waruna

>
> --Srinath
>
> On Mon, Mar 12, 2012 at 3:28 PM, Nandika Jayawardana 
> wrote:
> > Hi all,
> >We came up with a model to publish business process data to the
> > BAM2 server in the following way to monitor Business Process.
> > Basically,the idea is to implement an extension activity which would
> > publish the process data to BAM. Developer of the business process can
> > specify which data should be published to the bam in the following
> > way. We took the standard 'from' syntax from bpel for selecting the
> > data to be published. Extension activity xml syntax would be as
> > follows.
> >
> > 
> >  
> >  
> > 
> >  +
> >  
> > 
> >
> > The value within the from section could be either a variable or an xpath.
> > Syntax for publishing from a variable
> >
> > 
> >  
> > 
> >
> > 
> > 
> >
> > 
> >  
> > 
> >
> > Syntax for publishing from xpath
> >
> > 
> >
> >
> >
> > queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
> >
> >
> >
> > 
> >
> > 
> >
> >
> >$input.part/tns:input
> >
> >
> > 
> >
> > Publishing from xpath is not essential as it is possible to extract
> > values using xpath in the bam analyzer as well.  BAM server
> > configuration data will go into the deploy.xml.
> >
> > Regards
> > Nandika
> >
> > --
> > Nandika Jayawardana
> > Technical Lead
> > WSO2 Inc ; http://wso2.com
> > lean.enterprise.middleware
> > ___
> > Dev mailing list
> > Dev@wso2.org
> > http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>http://www.cs.indiana.edu/~hperera/
>http://srinathsview.blogspot.com/
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
-
Waruna Ranasinghe
Senior Software Engineer, WSO2

Mobile: +94 724 318285
BLOG: http://warunapw.blogspot.com

www.wso2.com - "Lean . Enterprise . Middleware"
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:

> How do you set the Registry to Synapse? Does it depend on the Registry
> API? If so, we can have a Registry implementation which works with the file
> system persistence structure.


Synapse accesses WSO2 registry through the Synapse registry API. We can't
have a registry implementation that only works with the file system
(because we need to be able to lookup registry resources too - WSDLs,
endpoints and stuff). If we go along this path we have to come up with an
implementation that can work with both WSO2 registry and local file system
(kind of like a hybrid registry).

Thanks,
Hiranya


>
>
> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:
>>>


 On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka 
 wrote:

> I tried enabling caching for the service. It did get applied as
> expected. But the change didn't survive a restart. I think this is same 
> for
> other QoS modules too (throttling, RM etc).


  Does the relevant policy got added to the relevant metafile?

>>>
>>> Yes it does. I debugged this case a little bit, and I think the problem
>>> occurs because our proxy service observer expects to find the relevant
>>> policies in the registry. But they are no longer stored in the registry.
>>>
>>> In the past it was just a matter of updating the proxy service
>>> configuration with a key that points to the appropriate policy in the
>>> registry:
>>>
>>> 
>>>
>>> ESB knows how to resolve registry keys. But with the new model I don't
>>> know how the same behavior can be achieved.
>>>
>>
>> This is going to affect all QoS aspects of ESB including security. How do
>> we solve this problem? Synapse can only load policies from the registry.
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Lakmali, I'll look into this. I've already answered your second issue.
 As I've been told earlier, please send the logs as soon as you faced
 with an issue related to persistence. At this point of time, this
 implementation isn't tested in other products than Kernel, and AppServer.



> Thanks,
> Hiranya
>
>
> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta  > wrote:
>
>> Hi,
>>
>> I am also experiencing similar issues on DSS product & service. When
>> a service is saved the following exception occurs.
>>
>>  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager}
>> -  Unable to handle new service addition. Service: H2BasicService
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
>> at
>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>>
>> at
>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>> at
>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>> at
>> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
>> at
>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>> at
>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>> at
>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>> at
>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>> at
>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>> at
>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>> at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>> at
>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:75)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>> at
>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoo

Re: [Dev] Bamboo Status update

[Srinath Perera]

+1 .. IMO at least in short term we can live with this.

--Srinath

On Mon, Mar 26, 2012 at 2:31 PM, Shammi Jayasinghe  wrote:
> Hi All,
>
>    From last Monday we had configured bamboo plans for each and every
> product. But when building products in separate plans we had
> to get a check out of entire platform for each and every products. It means
> 14 check outs of platform. But this was very time consuming
> and consumed huge disk space.
>
> As a solution for this after having off-line discussion with Carbon Team, we
> changed the build strategy. In that instead of taking 14 check
> outs to build product plans , we used the source checked out for building
> platform plan. With this way we could build the products with a
> small amount of time compared to earlier build strategy.
>
> But as all of you know, when building products with this way, It generated
> failure notice though the product build is executed with tests and
> all the modules build successfully. Eg : IS build. This was because, bamboo
> was not able to find out the tests reports in the directory we
> specified for sure-fire reports. We tried with various combinations of
> relative paths and was not success.
>
> So after having an off-line discussion with pradeep (He had discussed with
> Azeez and Sameera), we are moving back to the earlier build
> strategy until we figure out a proper solution to the above problem.
>
> There will be only four bamboo plans for building entire platform.
>
> 1. Orbit
> 2. Kernel
> 3. Platform (This will build up to samples)
> 4. Products.
>
>
> Thanks
> Shammi
>
> --
> Best Regards,
>
> Shammi Jayasinghe
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 

Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon kernel server is not successfully starting up

[Sameera Jayasoma]

Hi Azeez,

Are you still getting this error? I started the Carbon core with
-DportOffset=2 and it worked correctly..

Thanks,
Sameera.

On Sun, Mar 25, 2012 at 6:33 AM, Afkham Azeez  wrote:

> This is the portOffset trying to be set as a system property
>
> --
> Afkham Azeez
> Sent from my phone
> On Mar 24, 2012 8:18 PM, "Pradeep Fernando"  wrote:
>
>> Hi,
>>
>> I got this error sometime back. It was a local error. I was trying to set
>> a system property with a null value. Later realized that, i was getting
>> that property from serverConfig, before its getting initialized.
>>
>> the error looks, exactly the same. I can't figure out why this happening
>> now.
>>
>> --Pradeep
>>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Taking too long to deploy a service with WSDL2.0 with Internet

[Nirmal Fernando]

Hi All,

I have a RESTful web service which takes ages to get deployed when I'm
connected to Internet. The WSDL 2.0 is auto-generated using java2wsdl
script of axis2 1.6.1.

I think it tries to access some schemas available via the Internet. WSDL is
attached.

How to get rid of this delay?

-- 

Thanks & regards,
Nirmal

Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/

http://www.w3.org/ns/wsdl"; xmlns:ns1="http://org.apache.axis2/xsd"; xmlns:ns="http://impl.service.agent.autoscaler.carbon.wso2.org"; xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"; xmlns:wrpc="http://www.w3.org/ns/wsdl/rpc"; xmlns:wsoap="http://www.w3.org/ns/wsdl/soap"; xmlns:tns="http://impl.service.agent.autoscaler.carbon.wso2.org"; xmlns:wsdlx="http://www.w3.org/ns/wsdl-extensions"; xmlns:ax21="http://exception.agent.autoscaler.carbon.wso2.org/xsd"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:whttp="http://www.w3.org/ns/wsdl/http"; targetNamespace="http://impl.service.agent.autoscaler.carbon.wso2.org";>

http://exception.agent.autoscaler.carbon.wso2.org/xsd";>










http://exception.agent.autoscaler.carbon.wso2.org/xsd"; attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://impl.service.agent.autoscaler.carbon.wso2.org";>
http://exception.agent.autoscaler.carbon.wso2.org/xsd"/>









































































































http://www.w3.org/ns/wsdl/style/rpc http://www.w3.org/ns/wsdl/style/iri http://www.w3.org/ns/wsdl/style/multipart"; wrpc:signature="return #return " pattern="http://www.w3.org/ns/wsdl/in-out";>




http://www.w3.org/ns/wsdl/style/rpc"; wrpc:signature="instanceId #in return #return " pattern="http://www.w3.org/ns/wsdl/in-out";>





http://www.w3.org/ns/wsdl/style/rpc http://www.w3.org/ns/wsdl/style/iri http://www.w3.org/ns/wsdl/style/multipart"; wrpc:signature="return #return " pattern="http://www.w3.org/ns/wsdl/in-out";>




http://www.w3.org/ns/wsdl/style/rpc"; wrpc:signature="domainName #in instanceId #in return #return " pattern="http://www.w3.org/ns/wsdl/in-out";>






http://www.w3.org/ns/wsdl/style/rpc http://www.w3.org/ns/wsdl/style/iri http://www.w3.org/ns/wsdl/style/multipart"; wrpc:signature="return #return " pattern="http://www.w3.org/ns/wsdl/in-out";>




http://www.w3.org/ns/wsdl/soap"; wsoap:version="1.2">
































http://www.w3.org/ns/wsdl/http";>



  

Re: [Dev] PersistenceExceptions in ESB

[Isuru Suriarachchi]

On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka wrote:

>
>
> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>
>> How do you set the Registry to Synapse? Does it depend on the Registry
>> API? If so, we can have a Registry implementation which works with the file
>> system persistence structure.
>
>
> Synapse accesses WSO2 registry through the Synapse registry API. We can't
> have a registry implementation that only works with the file system
> (because we need to be able to lookup registry resources too - WSDLs,
> endpoints and stuff). If we go along this path we have to come up with an
> implementation that can work with both WSO2 registry and local file system
> (kind of like a hybrid registry).
>

I think for the time being the best option is to store the policies for
proxy services also in the Registry. Hiranya, will it solve the problem or
are there any other failure cases? Is the problem only related to policies?
It's better to identify all such problematic scenarios ASAP and address
those.

However, we have to come up with a better solution in the long run.

Thanks,
~Isuru


>
> Thanks,
> Hiranya
>
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:

>
>
> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka  > wrote:
>
>> I tried enabling caching for the service. It did get applied as
>> expected. But the change didn't survive a restart. I think this is same 
>> for
>> other QoS modules too (throttling, RM etc).
>
>
>  Does the relevant policy got added to the relevant metafile?
>

 Yes it does. I debugged this case a little bit, and I think the problem
 occurs because our proxy service observer expects to find the relevant
 policies in the registry. But they are no longer stored in the registry.

 In the past it was just a matter of updating the proxy service
 configuration with a key that points to the appropriate policy in the
 registry:

 

 ESB knows how to resolve registry keys. But with the new model I don't
 know how the same behavior can be achieved.

>>>
>>> This is going to affect all QoS aspects of ESB including security. How
>>> do we solve this problem? Synapse can only load policies from the registry.
>>>
>>>

 Thanks,
 Hiranya


>
> Lakmali, I'll look into this. I've already answered your second issue.
> As I've been told earlier, please send the logs as soon as you faced
> with an issue related to persistence. At this point of time, this
> implementation isn't tested in other products than Kernel, and AppServer.
>
>
>
>> Thanks,
>> Hiranya
>>
>>
>> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
>> lakm...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I am also experiencing similar issues on DSS product & service. When
>>> a service is saved the following exception occurs.
>>>
>>>  ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager}
>>> -  Unable to handle new service addition. Service: H2BasicService
>>> java.lang.NullPointerException
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
>>> at
>>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>>>
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>>> at
>>> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
>>> at
>>> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
>>> at
>>> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>>> at
>>> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>>> at
>>> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>>> at
>>> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
>>> at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
>>> at
>>> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
>>> at
>>> org.wso2.carbon.core.deploy

Re: [Dev] Test Automation Dashboard

[Krishantha Samaraweera]

Hi Srinath,

We lost automation test plan from bamboo due recent bamboo clean up. Need
to setup the framework again on bamboo and configure it. BTW, last time we
configured the automation framework to run after a successful build.
However the framework got executed only few times as the build was
unsuccessful. I think this is high time for us to setup the framework again
on bamboo machine, will work on it. As the first step, we will include AS,
ESB, G-Reg, DSS and BPS tests.

Will send a link to hosted Dhasboard instance shortly.

Thanks,
Krishantha.


On Mon, Mar 26, 2012 at 2:45 PM, Srinath Perera  wrote:

> do we have this Dashboard deployed with our Bamboo automation tests?
> if so, please send a link.
>
> --Srinath
>
> On Sat, Mar 17, 2012 at 7:54 PM, Amila Maha Arachchi 
> wrote:
> > Nice work!
> >
> > Regards,
> > AmilaM.
> >
> > On Fri, Mar 16, 2012 at 4:28 PM, Nuwan Wimalasekara 
> wrote:
> >>
> >> Hi all,
> >>
> >> One of main drawback in System test framework was to keep test report
> >> history in place where we can see test status and stats. System test
> >> framework generate test reports as TestNG result XML files. But those
> >> reports only show the result of last test run. So there is no way to
> find
> >> past results by build. Therefore we added new feature to System test
> >> framework to parse result XML files and write result data to a database
> >> after each test framework execution. Dashboard is capable for display
> those
> >> result in proper manner.
> >>
> >> Dashboard address the visualization of the test results and history
> using
> >> Charts. Test Automation dashboard is a web application which display
> test
> >> results and history of System test framework builds. Web application is
> >> developed using JSP technology. It is bundled as a webapp file and can
> be
> >> deployed on any java application server such as WSO2 App server, Tomcat
> >> etc.. We have designed the Dashboard as separate project and integrated
> to
> >> System test framework. Related dashboard DB configuration can be found
> in
> >> framework.properties file in System test framework. So the idea is to
> reuse
> >> the Dashboard with any project which generate TestNG result XML files.
> >> Automation dashboard source can be found at [1]
> >>
> >> How to deploy Dashboard :
> >>
> >> 1). Check out source of a dashboard from [1]
> >> 2). Build the source to generate war file (mvn clean package)
> >> 3). Extract a war file and open dbconf.properties in /WEB-INF/classes
> >> directory.
> >> 4). Configure database connection properties(jdbc url should be same as
> >> database configuration in framework.property)
> >> 5). Deploy the war fine on a application server.
> >> 6). Run System test framework and check results using dashboard
> >>
> >> It will display all test result and you can navigate result history
> also.
> >>
> >> Please refer attached screen shots of Dashboard. DB script and table
> >> structure is also attached.
> >>
> >> Your feedbacks and suggestions are welcome.
> >>
> >> Thanks Chanaka for the support given for theme design.
> >>
> >> Thanks,
> >> NuwanW /Chamara
> >>
> >>
> >> [1]
> https://svn.wso2.org/repos/wso2/carbon/platform/trunk/platform-integration/dashboard/
> >> --
> >> Nuwan Wimalasekara
> >> Software Engineer - Test Automation
> >> WSO2, Inc.: http://wso2.com
> >> lean. enterprise. middleware
> >>
> >> phone: +94 71 668 4620
> >>
> >>
> >>
> >>
> >>
> >> ___
> >> Dev mailing list
> >> Dev@wso2.org
> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
> >>
> >
> >
> >
> > --
> > Amila Maharachchi
> > Senior Software Engineer; 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
> >
>
>
>
> --
> 
> Srinath Perera, Ph.D.
>http://www.cs.indiana.edu/~hperera/
>http://srinathsview.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] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

Hi Isuru,

On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi  wrote:

>
>
> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>>
>>> How do you set the Registry to Synapse? Does it depend on the Registry
>>> API? If so, we can have a Registry implementation which works with the file
>>> system persistence structure.
>>
>>
>> Synapse accesses WSO2 registry through the Synapse registry API. We can't
>> have a registry implementation that only works with the file system
>> (because we need to be able to lookup registry resources too - WSDLs,
>> endpoints and stuff). If we go along this path we have to come up with an
>> implementation that can work with both WSO2 registry and local file system
>> (kind of like a hybrid registry).
>>
>
> I think for the time being the best option is to store the policies for
> proxy services also in the Registry. Hiranya, will it solve the problem or
> are there any other failure cases?
>
Is the problem only related to policies? It's better to identify all such
> problematic scenarios ASAP and address those.
>

I'm trying out various scenarios with the ESB. So far this is the only
problematic case I came across. I'll run some more tests and let you know
my findings by EoD today.


>
> However, we have to come up with a better solution in the long run.
>

+1

Thanks,
Hiranya


>
> Thanks,
> ~Isuru
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>> I tried enabling caching for the service. It did get applied as
>>> expected. But the change didn't survive a restart. I think this is same 
>>> for
>>> other QoS modules too (throttling, RM etc).
>>
>>
>>  Does the relevant policy got added to the relevant metafile?
>>
>
> Yes it does. I debugged this case a little bit, and I think the
> problem occurs because our proxy service observer expects to find the
> relevant policies in the registry. But they are no longer stored in the
> registry.
>
> In the past it was just a matter of updating the proxy service
> configuration with a key that points to the appropriate policy in the
> registry:
>
> 
>
> ESB knows how to resolve registry keys. But with the new model I don't
> know how the same behavior can be achieved.
>

 This is going to affect all QoS aspects of ESB including security. How
 do we solve this problem? Synapse can only load policies from the registry.


>
> Thanks,
> Hiranya
>
>
>>
>> Lakmali, I'll look into this. I've already answered your second
>> issue.
>> As I've been told earlier, please send the logs as soon as you faced
>> with an issue related to persistence. At this point of time, this
>> implementation isn't tested in other products than Kernel, and AppServer.
>>
>>
>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
>>> lakm...@wso2.com> wrote:
>>>
 Hi,

 I am also experiencing similar issues on DSS product & service.
 When a service is saved the following exception occurs.

  ERROR
 {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
 Unable to
 handle new service addition. Service: H2BasicService
 java.lang.NullPointerException
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
 at
 org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)

 at
 org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
 at
 org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
 at
 org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
 at

Re: [Dev] PersistenceExceptions in ESB

[Afkham Azeez]

So, in the registry based approach in Synapse/ESB, how was the cluster
synchronization problem solved? If a policy is changed in one node, how
does that get reflected on the rest of the nodes?

With the file system based approach, we were hoping to solve two issues.

1. Improve performance since instead of breaking up an Axis service into
its constituents and storing them separately, we store it as a single entity
2. Deployment Synchronizer will take care of propagating the metadata
changes to all nodes in the cluster.

In the file system based approach, we will need a MetadataDeployer which
will listen for changes in the service metadata, and reload the relevant
Axis2 services. This has to be done in a graceful manner. i.e. If the Axis
service is currently in use, wait until it gets freed before reloading it.

Azeez

On Mon, Mar 26, 2012 at 3:38 PM, Hiranya Jayathilaka wrote:

> Hi Isuru,
>
> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>>>
 How do you set the Registry to Synapse? Does it depend on the Registry
 API? If so, we can have a Registry implementation which works with the file
 system persistence structure.
>>>
>>>
>>> Synapse accesses WSO2 registry through the Synapse registry API. We
>>> can't have a registry implementation that only works with the file system
>>> (because we need to be able to lookup registry resources too - WSDLs,
>>> endpoints and stuff). If we go along this path we have to come up with an
>>> implementation that can work with both WSO2 registry and local file system
>>> (kind of like a hybrid registry).
>>>
>>
>> I think for the time being the best option is to store the policies for
>> proxy services also in the Registry. Hiranya, will it solve the problem or
>> are there any other failure cases?
>>
> Is the problem only related to policies? It's better to identify all such
>> problematic scenarios ASAP and address those.
>>
>
> I'm trying out various scenarios with the ESB. So far this is the only
> problematic case I came across. I'll run some more tests and let you know
> my findings by EoD today.
>
>
>>
>> However, we have to come up with a better solution in the long run.
>>
>
> +1
>
> Thanks,
> Hiranya
>
>
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>


 On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>
 I tried enabling caching for the service. It did get applied as
 expected. But the change didn't survive a restart. I think this is 
 same for
 other QoS modules too (throttling, RM etc).
>>>
>>>
>>>  Does the relevant policy got added to the relevant metafile?
>>>
>>
>> Yes it does. I debugged this case a little bit, and I think the
>> problem occurs because our proxy service observer expects to find the
>> relevant policies in the registry. But they are no longer stored in the
>> registry.
>>
>> In the past it was just a matter of updating the proxy service
>> configuration with a key that points to the appropriate policy in the
>> registry:
>>
>> 
>>
>> ESB knows how to resolve registry keys. But with the new model I
>> don't know how the same behavior can be achieved.
>>
>
> This is going to affect all QoS aspects of ESB including security. How
> do we solve this problem? Synapse can only load policies from the 
> registry.
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Lakmali, I'll look into this. I've already answered your second
>>> issue.
>>> As I've been told earlier, please send the logs as soon as you faced
>>> with an issue related to persistence. At this point of time, this
>>> implementation isn't tested in other products than Kernel, and 
>>> AppServer.
>>>
>>>
>>>
 Thanks,
 Hiranya


 On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
 lakm...@wso2.com> wrote:

> Hi,
>
> I am also experiencing similar issues on DSS product & service.
> When a service is saved the following exception occurs.
>
>  ERROR
> {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
> Unable to
> handle new service addition. Service: H2BasicService
> java.lang.NullPointerException
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>   

[Dev] Data Service Server Startup failed for trunk build by Bamboo

[Nuwan Wimalasekara]

Hi all,
DSS pack is downloaded from Bamboo artifact. Server Start failed.

CARBON_HOME environment variable is set to
/home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
[2012-03-26 15:34:16,275]  INFO {org.wso2.carbon.tomcat.internal.Activator}
-  registering the JNDI stream handler
[2012-03-26 15:34:16,460]  INFO
{org.wso2.carbon.transaction.manager.TransactionFactory} -  Starting
Atomikos Transaction Manager 3.7.0
[2012-03-26 15:34:16,742]  INFO
{org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
extended standard service  :   StandardService[Catalina]
[2012-03-26 15:34:17,510]  INFO
{org.wso2.carbon.user.core.authorization.PermissionTree} -  Newly loaded
permission tree from database for tenant 0
[2012-03-26 15:34:17,963]  INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
to mount at wso2commonregistry in 147ms
[2012-03-26 15:34:18,221]  INFO
{org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
to mount at wso2commonregistry in 0ms
[2012-03-26 15:34:18,290]  INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
 Registry Mode: READ-WRITE
[2012-03-26 15:34:39,076]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
Carbon...
[2012-03-26 15:34:39,076]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Linux 2.6.32-34-generic, amd64
[2012-03-26 15:34:39,076]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
/home/nuwanw/software/java/jdk1.6.0_22/jre
[2012-03-26 15:34:39,076]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.6.0_22
[2012-03-26 15:34:39,076]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 17.1-b03,Sun Microsystems Inc.
[2012-03-26 15:34:39,076]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
/home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
[2012-03-26 15:34:39,077]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
/home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/tmp
[2012-03-26 15:34:39,077]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
nuwanw, en-US, Asia/Colombo
[2012-03-26 15:34:40,875] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:40,938] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:40,996] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,055] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,170] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,292] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,376] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,510] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,566] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,644] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,721] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,793] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,894] ERROR
{org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
Carbon Core bundle, an instance of ServerConfigurationService should be in
existance
[2012-03-26 15:34:41,909]  INFO
{org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService} -
 Coordination service disabled.
[201

Re: [Dev] BPEL Monitoring for BAM2

[Kasun Weranga]

On Mon, Mar 26, 2012 at 3:12 PM, Waruna Ranasinghe  wrote:

>
>
> On Mon, Mar 26, 2012 at 2:59 PM, Srinath Perera  wrote:
>
>> +1 for the approach for sending custom values
>>
>> When we send custom values, do we send information about the workflow
>> and instance ID etc?
>>
> No, but the workflow designer can add the instance ID to the variable he
> chose to publish into BAM, if he needs it for the analysis.
>
>
>>
>> I think we should we also have a default  set of monitoring data we
>> can push from a BPEL workflow to BAM (just like default Service stats)
>> that can be turned on easily. I think we can do this easily by
>> extending the ODE workflow event listener to emit workflow monitoring
>> data. It should send information like services invoked, how long the
>> instance ran,  .. requests send and received etc.
>>
>
+1,  Then later we can provide pre-built gadgets and analyzers for
monitoring BPEL work-flows, if BPEL can provide default set of monitoring
data.

Thanks,
KasunW


> +1.
> Lets add this to our roadmap
>
> Thanks,
> Waruna
>
>>
>> --Srinath
>>
>> On Mon, Mar 12, 2012 at 3:28 PM, Nandika Jayawardana 
>> wrote:
>> > Hi all,
>> >We came up with a model to publish business process data to the
>> > BAM2 server in the following way to monitor Business Process.
>> > Basically,the idea is to implement an extension activity which would
>> > publish the process data to BAM. Developer of the business process can
>> > specify which data should be published to the bam in the following
>> > way. We took the standard 'from' syntax from bpel for selecting the
>> > data to be published. Extension activity xml syntax would be as
>> > follows.
>> >
>> > 
>> >  
>> >  
>> > 
>> >  +
>> >  
>> > 
>> >
>> > The value within the from section could be either a variable or an
>> xpath.
>> > Syntax for publishing from a variable
>> >
>> > 
>> >  
>> > 
>> >
>> > 
>> > 
>> >
>> > 
>> >  
>> > 
>> >
>> > Syntax for publishing from xpath
>> >
>> > 
>> >
>> >
>> >
>> >> queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0">
>> >
>> >
>> >
>> > 
>> >
>> > 
>> >
>> >
>> >$input.part/tns:input
>> >
>> >
>> > 
>> >
>> > Publishing from xpath is not essential as it is possible to extract
>> > values using xpath in the bam analyzer as well.  BAM server
>> > configuration data will go into the deploy.xml.
>> >
>> > Regards
>> > Nandika
>> >
>> > --
>> > Nandika Jayawardana
>> > Technical Lead
>> > WSO2 Inc ; http://wso2.com
>> > lean.enterprise.middleware
>> > ___
>> > Dev mailing list
>> > Dev@wso2.org
>> > http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>http://www.cs.indiana.edu/~hperera/
>>http://srinathsview.blogspot.com/
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> -
> Waruna Ranasinghe
> Senior Software Engineer, WSO2
>
> Mobile: +94 724 318285
> BLOG: http://warunapw.blogspot.com
>
> www.wso2.com - "Lean . Enterprise . Middleware"
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kasun Weranga*
Software Engineer
**
*WSO2, Inc.
*lean.enterprise.middleware.
mobile : +94 772314602
blog
:
http://kasunweranga.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Manjula Rathnayake]

On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi  wrote:

>
>
> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>>
>>> How do you set the Registry to Synapse? Does it depend on the Registry
>>> API? If so, we can have a Registry implementation which works with the file
>>> system persistence structure.
>>
>>
>> Synapse accesses WSO2 registry through the Synapse registry API. We can't
>> have a registry implementation that only works with the file system
>> (because we need to be able to lookup registry resources too - WSDLs,
>> endpoints and stuff). If we go along this path we have to come up with an
>> implementation that can work with both WSO2 registry and local file system
>> (kind of like a hybrid registry).
>>
>
> I think for the time being the best option is to store the policies for
> proxy services also in the Registry. Hiranya, will it solve the problem or
> are there any other failure cases? Is the problem only related to policies?
> It's better to identify all such problematic scenarios ASAP and address
> those.
>

Applying security on services fails in AS too. However this is already
being fixed by KasunG locally, I guess.  Security mgt bundle load policies
from registry. so all service hosting products will get this issue.

Thank you.

>
> However, we have to come up with a better solution in the long run.
>
> Thanks,
> ~Isuru
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>> I tried enabling caching for the service. It did get applied as
>>> expected. But the change didn't survive a restart. I think this is same 
>>> for
>>> other QoS modules too (throttling, RM etc).
>>
>>
>>  Does the relevant policy got added to the relevant metafile?
>>
>
> Yes it does. I debugged this case a little bit, and I think the
> problem occurs because our proxy service observer expects to find the
> relevant policies in the registry. But they are no longer stored in the
> registry.
>
> In the past it was just a matter of updating the proxy service
> configuration with a key that points to the appropriate policy in the
> registry:
>
> 
>
> ESB knows how to resolve registry keys. But with the new model I don't
> know how the same behavior can be achieved.
>

 This is going to affect all QoS aspects of ESB including security. How
 do we solve this problem? Synapse can only load policies from the registry.


>
> Thanks,
> Hiranya
>
>
>>
>> Lakmali, I'll look into this. I've already answered your second
>> issue.
>> As I've been told earlier, please send the logs as soon as you faced
>> with an issue related to persistence. At this point of time, this
>> implementation isn't tested in other products than Kernel, and AppServer.
>>
>>
>>
>>> Thanks,
>>> Hiranya
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
>>> lakm...@wso2.com> wrote:
>>>
 Hi,

 I am also experiencing similar issues on DSS product & service.
 When a service is saved the following exception occurs.

  ERROR
 {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
 Unable to
 handle new service addition. Service: H2BasicService
 java.lang.NullPointerException
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
 at
 org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
 at
 org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)

 at
 org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
 at
 org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
 at
 org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
 at
 org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
 at
 org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
 at
 org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
 at
 org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>>

Re: [Dev] Data Service Server Startup failed for trunk build by Bamboo

[Lakmali Baminiwatta]

Hi,

I'll look into this

Thanks,
Lakmali

On Mon, Mar 26, 2012 at 3:44 PM, Nuwan Wimalasekara  wrote:

> Hi all,
> DSS pack is downloaded from Bamboo artifact. Server Start failed.
>
> CARBON_HOME environment variable is set to
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:16,275]  INFO
> {org.wso2.carbon.tomcat.internal.Activator} -  registering the JNDI stream
> handler
> [2012-03-26 15:34:16,460]  INFO
> {org.wso2.carbon.transaction.manager.TransactionFactory} -  Starting
> Atomikos Transaction Manager 3.7.0
> [2012-03-26 15:34:16,742]  INFO
> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
> extended standard service  :   StandardService[Catalina]
> [2012-03-26 15:34:17,510]  INFO
> {org.wso2.carbon.user.core.authorization.PermissionTree} -  Newly loaded
> permission tree from database for tenant 0
> [2012-03-26 15:34:17,963]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 147ms
> [2012-03-26 15:34:18,221]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 0ms
> [2012-03-26 15:34:18,290]  INFO
> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
>  Registry Mode: READ-WRITE
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 2.6.32-34-generic, amd64
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/nuwanw/software/java/jdk1.6.0_22/jre
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_22
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 17.1-b03,Sun Microsystems Inc.
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/tmp
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> nuwanw, en-US, Asia/Colombo
> [2012-03-26 15:34:40,875] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,938] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,996] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,055] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,170] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,292] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,376] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,510] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,566] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,644] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,721] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,793] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,894] ERROR

Re: [Dev] Data Service Server Startup failed for trunk build by Bamboo

[Nuwan Wimalasekara]

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-DSS


On Mon, Mar 26, 2012 at 3:44 PM, Nuwan Wimalasekara  wrote:

> Hi all,
> DSS pack is downloaded from Bamboo artifact. Server Start failed.
>
> CARBON_HOME environment variable is set to
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:16,275]  INFO
> {org.wso2.carbon.tomcat.internal.Activator} -  registering the JNDI stream
> handler
> [2012-03-26 15:34:16,460]  INFO
> {org.wso2.carbon.transaction.manager.TransactionFactory} -  Starting
> Atomikos Transaction Manager 3.7.0
> [2012-03-26 15:34:16,742]  INFO
> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
> extended standard service  :   StandardService[Catalina]
> [2012-03-26 15:34:17,510]  INFO
> {org.wso2.carbon.user.core.authorization.PermissionTree} -  Newly loaded
> permission tree from database for tenant 0
> [2012-03-26 15:34:17,963]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 147ms
> [2012-03-26 15:34:18,221]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 0ms
> [2012-03-26 15:34:18,290]  INFO
> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
>  Registry Mode: READ-WRITE
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 2.6.32-34-generic, amd64
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/nuwanw/software/java/jdk1.6.0_22/jre
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_22
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 17.1-b03,Sun Microsystems Inc.
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/tmp
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> nuwanw, en-US, Asia/Colombo
> [2012-03-26 15:34:40,875] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,938] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,996] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,055] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,170] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,292] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,376] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,510] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,566] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,644] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,721] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,793] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-2

Re: [Dev] Data Service Server Startup failed for trunk build by Bamboo

[Prabath Abeysekera]

Hi Nuwan,

On Mon, Mar 26, 2012 at 3:44 PM, Nuwan Wimalasekara  wrote:

> Hi all,
> DSS pack is downloaded from Bamboo artifact. Server Start failed.
>

I have a locally built pack (which is up-to-date) and it starts up without
any issue. Are you using the latest packs?


>
> CARBON_HOME environment variable is set to
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:16,275]  INFO
> {org.wso2.carbon.tomcat.internal.Activator} -  registering the JNDI stream
> handler
> [2012-03-26 15:34:16,460]  INFO
> {org.wso2.carbon.transaction.manager.TransactionFactory} -  Starting
> Atomikos Transaction Manager 3.7.0
> [2012-03-26 15:34:16,742]  INFO
> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
> extended standard service  :   StandardService[Catalina]
> [2012-03-26 15:34:17,510]  INFO
> {org.wso2.carbon.user.core.authorization.PermissionTree} -  Newly loaded
> permission tree from database for tenant 0
> [2012-03-26 15:34:17,963]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 147ms
> [2012-03-26 15:34:18,221]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 0ms
> [2012-03-26 15:34:18,290]  INFO
> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
>  Registry Mode: READ-WRITE
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 2.6.32-34-generic, amd64
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/nuwanw/software/java/jdk1.6.0_22/jre
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_22
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 17.1-b03,Sun Microsystems Inc.
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/tmp
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> nuwanw, en-US, Asia/Colombo
> [2012-03-26 15:34:40,875] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,938] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,996] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,055] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,170] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,292] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,376] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,510] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,566] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,644] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,721] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,793] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instanc

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

On Mon, Mar 26, 2012 at 3:42 PM, Afkham Azeez  wrote:

> So, in the registry based approach in Synapse/ESB, how was the cluster
> synchronization problem solved? If a policy is changed in one node, how
> does that get reflected on the rest of the nodes?


Policies are stored in config registry. In a cluster we share the config
registry. So all ESB nodes see the same set of policies.

Besides in many real world scenarios people use custom policies. So for
them this is not a problem at all. In such cases they have the policies in
a shared governance registry.

Thanks,
Hiranya


>
> With the file system based approach, we were hoping to solve two issues.
>
> 1. Improve performance since instead of breaking up an Axis service into
> its constituents and storing them separately, we store it as a single entity
> 2. Deployment Synchronizer will take care of propagating the metadata
> changes to all nodes in the cluster.
>
> In the file system based approach, we will need a MetadataDeployer which
> will listen for changes in the service metadata, and reload the relevant
> Axis2 services. This has to be done in a graceful manner. i.e. If the Axis
> service is currently in use, wait until it gets freed before reloading it.
>
> Azeez
>
>
> On Mon, Mar 26, 2012 at 3:38 PM, Hiranya Jayathilaka wrote:
>
>> Hi Isuru,
>>
>> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:

> How do you set the Registry to Synapse? Does it depend on the Registry
> API? If so, we can have a Registry implementation which works with the 
> file
> system persistence structure.


 Synapse accesses WSO2 registry through the Synapse registry API. We
 can't have a registry implementation that only works with the file system
 (because we need to be able to lookup registry resources too - WSDLs,
 endpoints and stuff). If we go along this path we have to come up with an
 implementation that can work with both WSO2 registry and local file system
 (kind of like a hybrid registry).

>>>
>>> I think for the time being the best option is to store the policies for
>>> proxy services also in the Registry. Hiranya, will it solve the problem or
>>> are there any other failure cases?
>>>
>> Is the problem only related to policies? It's better to identify all such
>>> problematic scenarios ASAP and address those.
>>>
>>
>> I'm trying out various scenarios with the ESB. So far this is the only
>> problematic case I came across. I'll run some more tests and let you know
>> my findings by EoD today.
>>
>>
>>>
>>> However, we have to come up with a better solution in the long run.
>>>
>>
>> +1
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>>

 Thanks,
 Hiranya


>
>
> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
 hira...@wso2.com> wrote:

> I tried enabling caching for the service. It did get applied as
> expected. But the change didn't survive a restart. I think this is 
> same for
> other QoS modules too (throttling, RM etc).


  Does the relevant policy got added to the relevant metafile?

>>>
>>> Yes it does. I debugged this case a little bit, and I think the
>>> problem occurs because our proxy service observer expects to find the
>>> relevant policies in the registry. But they are no longer stored in the
>>> registry.
>>>
>>> In the past it was just a matter of updating the proxy service
>>> configuration with a key that points to the appropriate policy in the
>>> registry:
>>>
>>> 
>>>
>>> ESB knows how to resolve registry keys. But with the new model I
>>> don't know how the same behavior can be achieved.
>>>
>>
>> This is going to affect all QoS aspects of ESB including security.
>> How do we solve this problem? Synapse can only load policies from the
>> registry.
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Lakmali, I'll look into this. I've already answered your second
 issue.
 As I've been told earlier, please send the logs as soon as you
 faced with an issue related to persistence. At this point of time, this
 implementation isn't tested in other products than Kernel, and 
 AppServer.



> Thanks,
> Hiranya
>
>
> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <

Re: [Dev] PersistenceExceptions in ESB

[Kasun Gajasinghe]

On Mon, Mar 26, 2012 at 3:47 PM, Manjula Rathnayake wrote:

>
>
> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>>>
 How do you set the Registry to Synapse? Does it depend on the Registry
 API? If so, we can have a Registry implementation which works with the file
 system persistence structure.
>>>
>>>
>>> Synapse accesses WSO2 registry through the Synapse registry API. We
>>> can't have a registry implementation that only works with the file system
>>> (because we need to be able to lookup registry resources too - WSDLs,
>>> endpoints and stuff). If we go along this path we have to come up with an
>>> implementation that can work with both WSO2 registry and local file system
>>> (kind of like a hybrid registry).
>>>
>>
>> I think for the time being the best option is to store the policies for
>> proxy services also in the Registry. Hiranya, will it solve the problem or
>> are there any other failure cases? Is the problem only related to policies?
>> It's better to identify all such problematic scenarios ASAP and address
>> those.
>>
>
> Applying security on services fails in AS too. However this is already
> being fixed by KasunG locally, I guess.  Security mgt bundle load policies
> from registry. so all service hosting products will get this issue.
>

yep. Implementation is already done. Still need to do the preliminary
testing.


>
> Thank you.
>
>>
>> However, we have to come up with a better solution in the long run.
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>


 On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>
 I tried enabling caching for the service. It did get applied as
 expected. But the change didn't survive a restart. I think this is 
 same for
 other QoS modules too (throttling, RM etc).
>>>
>>>
>>>  Does the relevant policy got added to the relevant metafile?
>>>
>>
>> Yes it does. I debugged this case a little bit, and I think the
>> problem occurs because our proxy service observer expects to find the
>> relevant policies in the registry. But they are no longer stored in the
>> registry.
>>
>> In the past it was just a matter of updating the proxy service
>> configuration with a key that points to the appropriate policy in the
>> registry:
>>
>> 
>>
>> ESB knows how to resolve registry keys. But with the new model I
>> don't know how the same behavior can be achieved.
>>
>
> This is going to affect all QoS aspects of ESB including security. How
> do we solve this problem? Synapse can only load policies from the 
> registry.
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Lakmali, I'll look into this. I've already answered your second
>>> issue.
>>> As I've been told earlier, please send the logs as soon as you faced
>>> with an issue related to persistence. At this point of time, this
>>> implementation isn't tested in other products than Kernel, and 
>>> AppServer.
>>>
>>>
>>>
 Thanks,
 Hiranya


 On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
 lakm...@wso2.com> wrote:

> Hi,
>
> I am also experiencing similar issues on DSS product & service.
> When a service is saved the following exception occurs.
>
>  ERROR
> {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
> Unable to
> handle new service addition. Service: H2BasicService
> java.lang.NullPointerException
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
> at
> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>
> at
> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
> at
> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
> at
> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> a

Re: [Dev] PersistenceExceptions in ESB

[Manjula Rathnayake]

On Mon, Mar 26, 2012 at 4:22 PM, Kasun Gajasinghe  wrote:

>
>
> On Mon, Mar 26, 2012 at 3:47 PM, Manjula Rathnayake wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:

> How do you set the Registry to Synapse? Does it depend on the Registry
> API? If so, we can have a Registry implementation which works with the 
> file
> system persistence structure.


 Synapse accesses WSO2 registry through the Synapse registry API. We
 can't have a registry implementation that only works with the file system
 (because we need to be able to lookup registry resources too - WSDLs,
 endpoints and stuff). If we go along this path we have to come up with an
 implementation that can work with both WSO2 registry and local file system
 (kind of like a hybrid registry).

>>>
>>> I think for the time being the best option is to store the policies for
>>> proxy services also in the Registry. Hiranya, will it solve the problem or
>>> are there any other failure cases? Is the problem only related to policies?
>>> It's better to identify all such problematic scenarios ASAP and address
>>> those.
>>>
>>
>> Applying security on services fails in AS too. However this is already
>> being fixed by KasunG locally, I guess.  Security mgt bundle load policies
>> from registry. so all service hosting products will get this issue.
>>
>
> yep. Implementation is already done. Still need to do the preliminary
> testing.
>
Please share the diff if possible, I will look into this as well.

thank you.

>
>
>>
>> Thank you.
>>
>>>
>>> However, we have to come up with a better solution in the long run.
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>>

 Thanks,
 Hiranya


>
>
> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
 hira...@wso2.com> wrote:

> I tried enabling caching for the service. It did get applied as
> expected. But the change didn't survive a restart. I think this is 
> same for
> other QoS modules too (throttling, RM etc).


  Does the relevant policy got added to the relevant metafile?

>>>
>>> Yes it does. I debugged this case a little bit, and I think the
>>> problem occurs because our proxy service observer expects to find the
>>> relevant policies in the registry. But they are no longer stored in the
>>> registry.
>>>
>>> In the past it was just a matter of updating the proxy service
>>> configuration with a key that points to the appropriate policy in the
>>> registry:
>>>
>>> 
>>>
>>> ESB knows how to resolve registry keys. But with the new model I
>>> don't know how the same behavior can be achieved.
>>>
>>
>> This is going to affect all QoS aspects of ESB including security.
>> How do we solve this problem? Synapse can only load policies from the
>> registry.
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Lakmali, I'll look into this. I've already answered your second
 issue.
 As I've been told earlier, please send the logs as soon as you
 faced with an issue related to persistence. At this point of time, this
 implementation isn't tested in other products than Kernel, and 
 AppServer.



> Thanks,
> Hiranya
>
>
> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
> lakm...@wso2.com> wrote:
>
>> Hi,
>>
>> I am also experiencing similar issues on DSS product & service.
>> When a service is saved the following exception occurs.
>>
>>  ERROR
>> {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
>> Unable to
>> handle new service addition. Service: H2BasicService
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
>> at
>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>>
>> at
>> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
>> at
>>>

Re: [Dev] Data Service Server Startup failed for trunk build by Bamboo

[Nuwan Wimalasekara]

Restarting machine solved above problem. There was something wrong in my
machine.

Thanks
Nuwanw

On Mon, Mar 26, 2012 at 3:54 PM, Prabath Abeysekera wrote:

> Hi Nuwan,
>
> On Mon, Mar 26, 2012 at 3:44 PM, Nuwan Wimalasekara wrote:
>
>> Hi all,
>> DSS pack is downloaded from Bamboo artifact. Server Start failed.
>>
>
> I have a locally built pack (which is up-to-date) and it starts up without
> any issue. Are you using the latest packs?
>
>
>>
>> CARBON_HOME environment variable is set to
>> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
>> [2012-03-26 15:34:16,275]  INFO
>> {org.wso2.carbon.tomcat.internal.Activator} -  registering the JNDI stream
>> handler
>> [2012-03-26 15:34:16,460]  INFO
>> {org.wso2.carbon.transaction.manager.TransactionFactory} -  Starting
>> Atomikos Transaction Manager 3.7.0
>> [2012-03-26 15:34:16,742]  INFO
>> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
>> extended standard service  :   StandardService[Catalina]
>> [2012-03-26 15:34:17,510]  INFO
>> {org.wso2.carbon.user.core.authorization.PermissionTree} -  Newly loaded
>> permission tree from database for tenant 0
>> [2012-03-26 15:34:17,963]  INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>> to mount at wso2commonregistry in 147ms
>> [2012-03-26 15:34:18,221]  INFO
>> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
>> to mount at wso2commonregistry in 0ms
>> [2012-03-26 15:34:18,290]  INFO
>> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
>>  Registry Mode: READ-WRITE
>> [2012-03-26 15:34:39,076]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>> Carbon...
>> [2012-03-26 15:34:39,076]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Linux 2.6.32-34-generic, amd64
>> [2012-03-26 15:34:39,076]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> /home/nuwanw/software/java/jdk1.6.0_22/jre
>> [2012-03-26 15:34:39,076]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.6.0_22
>> [2012-03-26 15:34:39,076]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 17.1-b03,Sun Microsystems Inc.
>> [2012-03-26 15:34:39,076]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
>> [2012-03-26 15:34:39,077]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/tmp
>> [2012-03-26 15:34:39,077]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>> nuwanw, en-US, Asia/Colombo
>> [2012-03-26 15:34:40,875] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:40,938] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:40,996] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,055] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,170] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,292] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,376] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,510] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,566] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,644] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
>> Carbon Core bundle, an instance of ServerConfigurationService should be in
>> existance
>> [2012-03-26 15:34:41,721] ERROR
>> {org.wso2.carbon.core.internal.CarbonCoreD

Re: [Dev] PersistenceExceptions in ESB

[Kasun Gajasinghe]

On Mon, Mar 26, 2012 at 4:24 PM, Manjula Rathnayake wrote:

>
>
> On Mon, Mar 26, 2012 at 4:22 PM, Kasun Gajasinghe  wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 3:47 PM, Manjula Rathnayake wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>>>


 On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>
>> How do you set the Registry to Synapse? Does it depend on the
>> Registry API? If so, we can have a Registry implementation which works 
>> with
>> the file system persistence structure.
>
>
> Synapse accesses WSO2 registry through the Synapse registry API. We
> can't have a registry implementation that only works with the file system
> (because we need to be able to lookup registry resources too - WSDLs,
> endpoints and stuff). If we go along this path we have to come up with an
> implementation that can work with both WSO2 registry and local file system
> (kind of like a hybrid registry).
>

 I think for the time being the best option is to store the policies for
 proxy services also in the Registry. Hiranya, will it solve the problem or
 are there any other failure cases? Is the problem only related to policies?
 It's better to identify all such problematic scenarios ASAP and address
 those.

>>>
>>> Applying security on services fails in AS too. However this is already
>>> being fixed by KasunG locally, I guess.  Security mgt bundle load policies
>>> from registry. so all service hosting products will get this issue.
>>>
>>
>> yep. Implementation is already done. Still need to do the preliminary
>> testing.
>>
> Please share the diff if possible, I will look into this as well.
>

That'll be great. I changed some of the APIs in kernel to supplement some
other requests. I'll commit that fix, and then give you the security diff
first thing in the tomorrow morning if possible.

Thanks,
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Embedded tomcat is not loading the default web.xml in /lib/tomcat/conf

[Kishanthan Thangarajah]

Hi All,
We can fix this issue. I found that when calling the addWebapp API method,
they(tomcat) are explicitly setting 'noDefaultWebXml' for the webapp
context. Since we are not relying on this method, we can change this to use
the default webXml. The global webXml of ours will have some minor
modification. We have to remove the 'default servlet' definition from this
to avoid some duplication errors. Because in embedded mode, default servlet
is automatically added to the webapp.

Also I'm moving this web.xml and context.xml to repo/conf/tomcat directory.

Thanks,
Kishanthan.

On Wed, Mar 21, 2012 at 4:44 PM, Kishanthan Thangarajah  wrote:

> Hi All,
> I checked the $subject on both in trunk and AS-4.1.2. Looks like the issue
> is specific to embedded tomcat. So i think we have to do the same as what
> we did for contextXml loading for webapps.
>
> Thanks,
> Kishanthan.
>
> --
> *Kishanthan Thangarajah*
> Software Engineer,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>
>


-- 
*Kishanthan Thangarajah*
Software Engineer,
Development Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Embedded tomcat is not loading the default web.xml in /lib/tomcat/conf

[Dimuthu Leelarathne]

On Mon, Mar 26, 2012 at 4:44 PM, Kishanthan Thangarajah  wrote:

> Hi All,
> We can fix this issue. I found that when calling the addWebapp API method,
> they(tomcat) are explicitly setting 'noDefaultWebXml' for the webapp
> context. Since we are not relying on this method, we can change this to use
> the default webXml. The global webXml of ours will have some minor
> modification. We have to remove the 'default servlet' definition from this
> to avoid some duplication errors. Because in embedded mode, default servlet
> is automatically added to the webapp.
>
> Also I'm moving this web.xml and context.xml to repo/conf/tomcat
> directory.
>

+1. This will allow us to expire sessions and have other properties of
web.xml.

thanks,
dimuthu


>
> Thanks,
> Kishanthan.
>
> On Wed, Mar 21, 2012 at 4:44 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi All,
>> I checked the $subject on both in trunk and AS-4.1.2. Looks like the
>> issue is specific to embedded tomcat. So i think we have to do the same as
>> what we did for contextXml loading for webapps.
>>
>> Thanks,
>> Kishanthan.
>>
>> --
>> *Kishanthan Thangarajah*
>> Software Engineer,
>> Development Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com*
>> Twitter - *http://twitter.com/kishanthan*
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Software Engineer,
> Development Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Important] New Emma based code coverage framework

[Afkham Azeez]

Please note that Ruby is not a prerequisite for this framework anymore.

On Mon, Mar 26, 2012 at 4:50 PM, Afkham Azeez  wrote:

> Folks,
> Please read [1] and make sure that the coverage framework is properly
> integrated into your products. You will need to take an update of
> https://svn.wso2.org/repos/wso2/carbon/kernel/trunk/distribution/integration
>
>
> https://docs.google.com/a/wso2.com/document/d/1337AOkx5wkhW89obhxgsq3cY8DxGmJQzz5JtmgX_5rc/edit
>
> Once this is done, we can integrate these reports into Bamboo. I have
> already integrated this to org.wso2.carbon.integration.tests, so you can
> take a look at that module if you need more details.
>
> Please let me know if you have any issues. I have tested this only on Mac
> OS X.
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] Data Service Server Startup failed for trunk build by Bamboo

[Afkham Azeez]

This type of error cannot occur anymore since we have integration tests
which make sure that the servers startup.

On Mon, Mar 26, 2012 at 3:44 PM, Nuwan Wimalasekara  wrote:

> Hi all,
> DSS pack is downloaded from Bamboo artifact. Server Start failed.
>
> CARBON_HOME environment variable is set to
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:16,275]  INFO
> {org.wso2.carbon.tomcat.internal.Activator} -  registering the JNDI stream
> handler
> [2012-03-26 15:34:16,460]  INFO
> {org.wso2.carbon.transaction.manager.TransactionFactory} -  Starting
> Atomikos Transaction Manager 3.7.0
> [2012-03-26 15:34:16,742]  INFO
> {org.wso2.carbon.tomcat.ext.service.ExtendedStandardService} -  starting
> extended standard service  :   StandardService[Catalina]
> [2012-03-26 15:34:17,510]  INFO
> {org.wso2.carbon.user.core.authorization.PermissionTree} -  Newly loaded
> permission tree from database for tenant 0
> [2012-03-26 15:34:17,963]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 147ms
> [2012-03-26 15:34:18,221]  INFO
> {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} -  Connected
> to mount at wso2commonregistry in 0ms
> [2012-03-26 15:34:18,290]  INFO
> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
>  Registry Mode: READ-WRITE
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 2.6.32-34-generic, amd64
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/nuwanw/software/java/jdk1.6.0_22/jre
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_22
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 17.1-b03,Sun Microsystems Inc.
> [2012-03-26 15:34:39,076]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /home/nuwanw/svn/deployment-framework/SNAPSHOT/wso2dataservices-2.6.0-SNAPSHOT/tmp
> [2012-03-26 15:34:39,077]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> nuwanw, en-US, Asia/Colombo
> [2012-03-26 15:34:40,875] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,938] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:40,996] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,055] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,170] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,292] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,376] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,510] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,566] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,644] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,721] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigurationService should be in
> existance
> [2012-03-26 15:34:41,793] ERROR
> {org.wso2.carbon.core.internal.CarbonCoreDataHolder} -  Before activating
> Carbon Core bundle, an instance of ServerConfigur

[Dev] Error while building trunk platform components

[Dushan Abeyruwan]

Hi

 I am getting following error while building platform components, took
latest update on orbit/kernel and was build successfully ,
then platform deps/service-stutbs/parent build successfully


[INFO] Finished at: Mon Mar 26 17:14:03 IST 2012
[INFO] Final Memory: 1471M/1854M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
(default-compile) on project org.wso2.carbon.usage.agent: Compilation
failure
[ERROR]
/home/dushan/wso2svntrunk/carbon/platform/trunk/components/stratos/usage/org.wso2.carbon.usage.agent/src/main/java/org/wso2/carbon/usage/agent/util/Util.java:[81,57]
cannot find symbol
[ERROR] symbol  : method getAdvancedCarbonConfigDirPath()
[ERROR] location: class org.wso2.carbon.utils.CarbonUtils
[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.
[ERRO

-- 
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] UnSubscribe from mailing list

[krishna.kolachuru]

Hi,

Please remove me from this mailing list.


Thanks & Regards,
Krishna Kumar Kolachuru


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Charitha Kankanamge]

On Mon, Mar 26, 2012 at 5:06 PM, Hiranya Jayathilaka wrote:

> Hi,
>
> On Mon, Mar 26, 2012 at 4:58 PM, Dimuthu Leelarathne wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 4:54 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 4:50 PM, Dimuthu Leelarathne 
>>> wrote:
>>>
 Hi,

 On Mon, Mar 26, 2012 at 4:47 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 4:38 PM, Dimuthu Leelarathne <
> dimut...@wso2.com> wrote:
>
>> Hi,
>>
>> On Mon, Mar 26, 2012 at 4:01 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:42 PM, Afkham Azeez wrote:
>>>
 So, in the registry based approach in Synapse/ESB, how was the
 cluster synchronization problem solved? If a policy is changed in one 
 node,
 how does that get reflected on the rest of the nodes?
>>>
>>>
>>>  Policies are stored in config registry. In a cluster we share the
>>> config registry. So all ESB nodes see the same set of policies.
>>>
>>> Besides in many real world scenarios people use custom policies. So
>>> for them this is not a problem at all. In such cases they have the 
>>> policies
>>> in a shared governance registry.
>>>
>>>
>> Yes this will work. But I think we need a better approach. We are
>> talking about the problem of sharing the governance space of the registry
>> across all service cluster. This move forces us to step into the opposite
>> direction, i.e. towards more centralization rather than decentralization.
>>
>
> How come having a shared governance registry is a decentralized
> approach? And what is the problem with sharing registry across multiple
> nodes?
>

 What I meant was sharing config registry among a cluster is much better
 approach than using governance registry. When we start putting things that
 should be shared on a cluster only, in governance registry instead of a
 config registry, we are moving in the opposite direction of what we want to
 achieve.

>>>
>>> Ok. Normal practice for setting up a product cluster (eg: an ESB
>>> cluster) is to have a shared config registry and store all cluster-wide
>>> shareable resources in the config registry. So in that case what do we need
>>> a better approach for?
>>>
>>
>> That is the better approach instead of governance registry. I said that
>> because one of the previous mails were talking about using gov registry.
>>
>
> Oh ok :)
>
> I brought up governance registry because sometimes you have multiple
> product clusters (eg: ESB cluster + AS cluster) and you might want to have
> a particular policy file available for all of them. For an example think of
> a scenario where you apply one security policy on all proxy services in ESB
> and all Axis2 services in AS. Right now our solution to that is to have a
> shared governance registry, if I'm not mistaken.
>
>
Yes, this is the recommended registry sharing approach as explained under
"Strategy D" of [1]

[1]
http://wso2.org/library/tutorials/2010/04/sharing-registry-space-across-multiple-product-instances
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB JS Script Mediator samples broken

[Hiranya Jayathilaka]

This is still broken :(

Sameera, what needs to be done to fix this?

[2012-03-26 17:35:10,178] FATAL - ServiceBusInitializer Failed to
initialize ESB due to a fatal error
java.lang.NoClassDefFoundError:
com/sun/phobos/script/javascript/RhinoScriptEngineFactory
at
org.apache.synapse.mediators.bsf.ScriptMediator.initScriptEngine(ScriptMediator.java:404)
at
org.apache.synapse.mediators.bsf.ScriptMediator.(ScriptMediator.java:144)
at
org.apache.synapse.mediators.bsf.ScriptMediatorFactory.createSpecificMediator(ScriptMediatorFactory.java:98)
at
org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
at
org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:190)
at
org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
at
org.apache.synapse.config.xml.InMediatorFactory.createSpecificMediator(InMediatorFactory.java:48)
at
org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
at
org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:190)
at
org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
at
org.apache.synapse.config.xml.SequenceMediatorFactory.createSpecificMediator(SequenceMediatorFactory.java:85)
at
org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
at
org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:190)
at
org.apache.synapse.config.xml.SynapseXMLConfigurationFactory.defineSequence(SynapseXMLConfigurationFactory.java:174)
at
org.apache.synapse.config.xml.SynapseXMLConfigurationFactory.getConfiguration(SynapseXMLConfigurationFactory.java:78)
at
org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.getConfiguration(ConfigurationFactoryAndSerializerFinder.java:161)
at
org.apache.synapse.config.xml.XMLConfigurationBuilder.getConfiguration(XMLConfigurationBuilder.java:48)
at
org.apache.synapse.config.SynapseConfigurationBuilder.getConfiguration(SynapseConfigurationBuilder.java:91)
at
org.apache.synapse.Axis2SynapseController.createSynapseConfiguration(Axis2SynapseController.java:434)
at
org.wso2.carbon.mediation.initializer.CarbonSynapseController.createSynapseConfiguration(CarbonSynapseController.java:150)
at org.apache.synapse.ServerManager.start(ServerManager.java:177)
at
org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:412)
at
org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.event.core.internal.builder.EventBrokerHandler.startEventBroker(EventBrokerHandler.java:57)
at
org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS.activate(EventBrokerBuilderDS.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl

Re: [Dev] ESB JS Script Mediator samples broken

[Hiranya Jayathilaka]

The missing class is actually available in the bsf bundle. But the
synapse-extensions bundle cannot find the package it seems:

synapse-extensions_2.1.0.wso2v6 [439]
  Id=439, Status=RESOLVEDData
Root=/home/hiranya/Projects/java/wso2/carbon/platform/trunk/products/esb/modules/distribution/product/target/wso2esb-4.0.0-SNAPSHOT/repository/components/configuration/org.eclipse.osgi/bundles/439/data
  No registered services.
  No services in use.
  No exported packages
*; version="0.0.0"
*com.sun.phobos.script.javascript; version="0.0.0"*
com.sun.script.groovy; version="0.0.0"
com.sun.script.jruby; version="0.0.0"
org.apache.bsf.xml; version="0.0.0"
  Host bundles
synapse-core_2.1.0.wso2v6 [438]
  No named class spaces
  No required bundles

OSGi experts, we need some help with this please.

Thanks,
Hiranya

On Mon, Mar 26, 2012 at 5:37 PM, Hiranya Jayathilaka wrote:

> This is still broken :(
>
> Sameera, what needs to be done to fix this?
>
> [2012-03-26 17:35:10,178] FATAL - ServiceBusInitializer Failed to
> initialize ESB due to a fatal error
> java.lang.NoClassDefFoundError:
> com/sun/phobos/script/javascript/RhinoScriptEngineFactory
> at
> org.apache.synapse.mediators.bsf.ScriptMediator.initScriptEngine(ScriptMediator.java:404)
>  at
> org.apache.synapse.mediators.bsf.ScriptMediator.(ScriptMediator.java:144)
> at
> org.apache.synapse.mediators.bsf.ScriptMediatorFactory.createSpecificMediator(ScriptMediatorFactory.java:98)
>  at
> org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
> at
> org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:190)
>  at
> org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
> at
> org.apache.synapse.config.xml.InMediatorFactory.createSpecificMediator(InMediatorFactory.java:48)
>  at
> org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
> at
> org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:190)
>  at
> org.apache.synapse.config.xml.AbstractListMediatorFactory.addChildren(AbstractListMediatorFactory.java:41)
> at
> org.apache.synapse.config.xml.SequenceMediatorFactory.createSpecificMediator(SequenceMediatorFactory.java:85)
>  at
> org.apache.synapse.config.xml.AbstractMediatorFactory.createMediator(AbstractMediatorFactory.java:89)
> at
> org.apache.synapse.config.xml.MediatorFactoryFinder.getMediator(MediatorFactoryFinder.java:190)
>  at
> org.apache.synapse.config.xml.SynapseXMLConfigurationFactory.defineSequence(SynapseXMLConfigurationFactory.java:174)
> at
> org.apache.synapse.config.xml.SynapseXMLConfigurationFactory.getConfiguration(SynapseXMLConfigurationFactory.java:78)
>  at
> org.apache.synapse.config.xml.ConfigurationFactoryAndSerializerFinder.getConfiguration(ConfigurationFactoryAndSerializerFinder.java:161)
> at
> org.apache.synapse.config.xml.XMLConfigurationBuilder.getConfiguration(XMLConfigurationBuilder.java:48)
>  at
> org.apache.synapse.config.SynapseConfigurationBuilder.getConfiguration(SynapseConfigurationBuilder.java:91)
> at
> org.apache.synapse.Axis2SynapseController.createSynapseConfiguration(Axis2SynapseController.java:434)
>  at
> org.wso2.carbon.mediation.initializer.CarbonSynapseController.createSynapseConfiguration(CarbonSynapseController.java:150)
> at org.apache.synapse.ServerManager.start(ServerManager.java:177)
>  at
> org.wso2.carbon.mediation.initializer.ServiceBusInitializer.initESB(ServiceBusInitializer.java:412)
> at
> org.wso2.carbon.mediation.initializer.ServiceBusInitializer.activate(ServiceBusInitializer.java:172)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:328)
>  at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:221)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:104)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:23

[Dev] [ESB] Reports Option in Tools Menu

[Hiranya Jayathilaka]

I see a new "Reports" option in the ESB "Tools" menu. Is this necessary for
the ESB? What can an ESB user do with this option?

BTW the Reports > List option gives an empty page.

-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Hiranya Jayathilaka]

Looks like it's only applying policies that's affected by this change. Can
we have some sort of a fix for this as suggested by Isuru?

Thanks,
Hiranya

On Mon, Mar 26, 2012 at 3:38 PM, Hiranya Jayathilaka wrote:

> Hi Isuru,
>
> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>>>
 How do you set the Registry to Synapse? Does it depend on the Registry
 API? If so, we can have a Registry implementation which works with the file
 system persistence structure.
>>>
>>>
>>> Synapse accesses WSO2 registry through the Synapse registry API. We
>>> can't have a registry implementation that only works with the file system
>>> (because we need to be able to lookup registry resources too - WSDLs,
>>> endpoints and stuff). If we go along this path we have to come up with an
>>> implementation that can work with both WSO2 registry and local file system
>>> (kind of like a hybrid registry).
>>>
>>
>> I think for the time being the best option is to store the policies for
>> proxy services also in the Registry. Hiranya, will it solve the problem or
>> are there any other failure cases?
>>
> Is the problem only related to policies? It's better to identify all such
>> problematic scenarios ASAP and address those.
>>
>
> I'm trying out various scenarios with the ESB. So far this is the only
> problematic case I came across. I'll run some more tests and let you know
> my findings by EoD today.
>
>
>>
>> However, we have to come up with a better solution in the long run.
>>
>
> +1
>
> Thanks,
> Hiranya
>
>
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>


 On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>
 I tried enabling caching for the service. It did get applied as
 expected. But the change didn't survive a restart. I think this is 
 same for
 other QoS modules too (throttling, RM etc).
>>>
>>>
>>>  Does the relevant policy got added to the relevant metafile?
>>>
>>
>> Yes it does. I debugged this case a little bit, and I think the
>> problem occurs because our proxy service observer expects to find the
>> relevant policies in the registry. But they are no longer stored in the
>> registry.
>>
>> In the past it was just a matter of updating the proxy service
>> configuration with a key that points to the appropriate policy in the
>> registry:
>>
>> 
>>
>> ESB knows how to resolve registry keys. But with the new model I
>> don't know how the same behavior can be achieved.
>>
>
> This is going to affect all QoS aspects of ESB including security. How
> do we solve this problem? Synapse can only load policies from the 
> registry.
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Lakmali, I'll look into this. I've already answered your second
>>> issue.
>>> As I've been told earlier, please send the logs as soon as you faced
>>> with an issue related to persistence. At this point of time, this
>>> implementation isn't tested in other products than Kernel, and 
>>> AppServer.
>>>
>>>
>>>
 Thanks,
 Hiranya


 On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
 lakm...@wso2.com> wrote:

> Hi,
>
> I am also experiencing similar issues on DSS product & service.
> When a service is saved the following exception occurs.
>
>  ERROR
> {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
> Unable to
> handle new service addition. Service: H2BasicService
> java.lang.NullPointerException
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
> at
> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>
> at
> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:652)
> at
> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:406)
> at
> org.wso2.carbon.dataservices.core.DBDeployer.deploy(DBDeployer.java:180)
> at
> org.apache.axis2.deployment.repository.util.Deploymen

Re: [Dev] Error while building trunk platform components

[Subash Chaturanga]

Hi,
I'am also getting the same failure. Has this fixed now ?

On Mon, Mar 26, 2012 at 5:17 PM, Dushan Abeyruwan  wrote:

> Hi
>
>  I am getting following error while building platform components, took
> latest update on orbit/kernel and was build successfully ,
> then platform deps/service-stutbs/parent build successfully
>
>
> [INFO] Finished at: Mon Mar 26 17:14:03 IST 2012
> [INFO] Final Memory: 1471M/1854M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
> (default-compile) on project org.wso2.carbon.usage.agent: Compilation
> failure
> [ERROR]
> /home/dushan/wso2svntrunk/carbon/platform/trunk/components/stratos/usage/org.wso2.carbon.usage.agent/src/main/java/org/wso2/carbon/usage/agent/util/Util.java:[81,57]
> cannot find symbol
> [ERROR] symbol  : method getAdvancedCarbonConfigDirPath()
> [ERROR] location: class org.wso2.carbon.utils.CarbonUtils
> [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.
> [ERRO
>
> --
> Dushan Abeyruwan
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com

email - sub...@wso2.com
phone - 077 2225922
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while building trunk platform components

[Dushan Abeyruwan]

Hi
  Any response ?

On Mon, Mar 26, 2012 at 6:37 PM, Subash Chaturanga  wrote:

> Hi,
> I'am also getting the same failure. Has this fixed now ?
>
> On Mon, Mar 26, 2012 at 5:17 PM, Dushan Abeyruwan  wrote:
>
>> Hi
>>
>>  I am getting following error while building platform components, took
>> latest update on orbit/kernel and was build successfully ,
>> then platform deps/service-stutbs/parent build successfully
>>
>>
>> [INFO] Finished at: Mon Mar 26 17:14:03 IST 2012
>> [INFO] Final Memory: 1471M/1854M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
>> (default-compile) on project org.wso2.carbon.usage.agent: Compilation
>> failure
>> [ERROR]
>> /home/dushan/wso2svntrunk/carbon/platform/trunk/components/stratos/usage/org.wso2.carbon.usage.agent/src/main/java/org/wso2/carbon/usage/agent/util/Util.java:[81,57]
>> cannot find symbol
>> [ERROR] symbol  : method getAdvancedCarbonConfigDirPath()
>> [ERROR] location: class org.wso2.carbon.utils.CarbonUtils
>> [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.
>> [ERRO
>>
>> --
>> Dushan Abeyruwan
>> *Senior Software Engineer*
>>  *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com/*
>> *Mobile:(+94)714408632*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Subash Chaturanga
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> email - sub...@wso2.com
> phone - 077 2225922
>
>


-- 
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error when enabling the deployment synchronizer

[Thilini Ishaka]

I get below exception on ESB console when enabling the deployment
synchronizer in the latest trunk build.

[2012-03-26 18:36:27,754] ERROR - RPCInOnlyMessageReceiver Exception
occurred while trying to invoke service method
enableSynchronizerForCarbonRepository
java.lang.NullPointerException
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizationManager.scheduleSynchronizationTask(DeploymentSynchronizationManager.java:162)
 at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer.start(DeploymentSynchronizer.java:107)
at
org.wso2.carbon.deployment.synchronizer.services.DeploymentSynchronizerAdmin.enableSynchronizerForCarbonRepository(DeploymentSynchronizerAdmin.java:49)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
 at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at
org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:66)
 at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
 at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
 at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
 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.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
 at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:60)
 at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
 at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
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)


Thanks
Thilni

-- 
*Regards*

*Thilini Ishaka*
*Platform & Cloud Technologies*
***WSO2 Inc. http://wso2.com
*
*Mobile: +94 71 840 8171 *
*+94 77 211 8797*
*Bolg: thiliniishaka.blogspot.com*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while building trunk platform components

[Sanjeewa Malalgoda]

Hi All,
Ajanthan is looking in to this issue.
Thanks.
On Mon, Mar 26, 2012 at 6:41 PM, Dushan Abeyruwan  wrote:

> Hi
>   Any response ?
>
>
> On Mon, Mar 26, 2012 at 6:37 PM, Subash Chaturanga wrote:
>
>> Hi,
>> I'am also getting the same failure. Has this fixed now ?
>>
>> On Mon, Mar 26, 2012 at 5:17 PM, Dushan Abeyruwan wrote:
>>
>>> Hi
>>>
>>>  I am getting following error while building platform components, took
>>> latest update on orbit/kernel and was build successfully ,
>>> then platform deps/service-stutbs/parent build successfully
>>>
>>>
>>> [INFO] Finished at: Mon Mar 26 17:14:03 IST 2012
>>> [INFO] Final Memory: 1471M/1854M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
>>> (default-compile) on project org.wso2.carbon.usage.agent: Compilation
>>> failure
>>> [ERROR]
>>> /home/dushan/wso2svntrunk/carbon/platform/trunk/components/stratos/usage/org.wso2.carbon.usage.agent/src/main/java/org/wso2/carbon/usage/agent/util/Util.java:[81,57]
>>> cannot find symbol
>>> [ERROR] symbol  : method getAdvancedCarbonConfigDirPath()
>>> [ERROR] location: class org.wso2.carbon.utils.CarbonUtils
>>> [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.
>>> [ERRO
>>>
>>> --
>>> Dushan Abeyruwan
>>> *Senior Software Engineer*
>>>  *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com/*
>>> *Mobile:(+94)714408632*
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Subash Chaturanga
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>>
>> email - sub...@wso2.com
>> phone - 077 2225922
>>
>>
>
>
> --
> Dushan Abeyruwan
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sanjeewa Malalgoda*
Software Engineer
**
*WSO2, Inc.*
lean.enterprise.middleware.

mobile : +94 713068779
web: http://wso2.com
 blog
:http://sanjeewamalalgoda.blogspot.com/

[image:
http://wso2.com/wp-content/themes/wso2ng-v2/images/logos/stratos_logo_h42.gif]
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Platform-Build] Identifier conflict in bam and bam2

[Denis Weerasiri]

Hi,
Getting this error.

[ERROR] Two or more projects in the reactor have the same identifier,
please make sure that :: is unique for each
project:
{org.wso2.carbon:org.wso2.carbon.bam.core:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/components/bam/org.wso2.carbon.bam.core/pom.xml,
/opt/installations/wso2/trunk/carbon/platform/trunk/components/bam2/org.wso2.carbon.bam.core/pom.xml],
org.wso2.carbon:bam:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/components/bam/pom.xml,
/opt/installations/wso2/trunk/carbon/platform/trunk/components/bam2/pom.xml],
org.wso2.carbon:org.wso2.carbon.bam.feature:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam/org.wso2.carbon.bam.feature/pom.xml,
/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam2/org.wso2.carbon.bam.feature/pom.xml],
org.wso2.carbon:org.wso2.carbon.bam.ui.feature:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam/org.wso2.carbon.bam.ui.feature/pom.xml,
/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam2/org.wso2.carbon.bam.ui.feature/pom.xml],
org.wso2.carbon:bam-feature:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam/pom.xml,
/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam2/pom.xml]}
-> [Help 1]


-- 
Thanks,
Denis
--
*Denis Weerasiri*
Software Engineer
Integration Technologies Team, WSO2 Inc.; http://wso2.com,
*email: denis ** [AT] wso2.com *
*phone: +94117639629
*
*site: 
**https://sites.google.com/site/ddweerasiri/*
*blog: **http://ddweerasiri.blogspot.com* 
*
twitter: **http://twitter.com/ddweerasiri* *
linked-in: 
**http://lk.linkedin.com/in/ddweerasiri*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [System-test-framework]Data service auto deployment issues when there are multiple data source configs

[Charitha Kankanamge]

Test automation folks,

The automatic deployment of data services through the configuration given
in testconfig.xml is having some issues.

1. Deployer assumes there is one data source config in dbs (see
/home/charitha/projects/system-test-framework-trunk/system-test-framework/core/org.wso2.automation.platform.core/src/main/java/org/wso2/platform/test/core/utils/dssutils/SqlDataSourceUtil.java#createArtifact).
Therefore, if there are multiple data source configurations such as jdbc,
csv, gspread etc.. we cannot use auto deployer OOTB.
2. In testconfig.xml, we can have only one dependency_location for a
particular data service. Therefore, when we have data services with
multiple data source configs, all dependent resources have to be included
in one artifact directory. In a way, this seems to be valid but we may need
to look if there is a better approach.

On a separate note, we should have a JIRA project to report
issues/improvements related to Clarity (system-test-framework).

Thanks!
Charitha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon-dev] Merge Products & Stratos Services

[Amila Suriarachchi]

On Thu, Mar 1, 2012 at 6:42 PM, Afkham Azeez  wrote:

> During a discussion last week, the idea of merging the two into a single
> binary came up. That is, instead of Carbon AppServer & Stratos AppServer,
> we will have a single AppServer binary which contains the relevant
> components that can make it run in multi-tenant mode.  Actually,
> multi-tenancy is at the core of Carbon, and we do not expose it to the
> user. The Stratos counterparts of the respective products is mainly tested
> by the Stratos/Cloud team, and hence the issues may get uncovered late in
> the release cycle. This will also reduce the number of binaries that have
> to go through QA.
>
> Is this a feasible option? Thoughts welcome.
>

+1 for the idea.

What about the java security policy configurations which only use in
Stratos versions?

thanks,
Amila.



>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Carbon-dev mailing list
> carbon-...@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Amila Suriarachchi*

Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 71 3082805
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon-dev] Merge Products & Stratos Services

[Afkham Azeez]

On Mon, Mar 26, 2012 at 7:18 PM, Amila Suriarachchi  wrote:

>
>
> On Thu, Mar 1, 2012 at 6:42 PM, Afkham Azeez  wrote:
>
>> During a discussion last week, the idea of merging the two into a single
>> binary came up. That is, instead of Carbon AppServer & Stratos AppServer,
>> we will have a single AppServer binary which contains the relevant
>> components that can make it run in multi-tenant mode.  Actually,
>> multi-tenancy is at the core of Carbon, and we do not expose it to the
>> user. The Stratos counterparts of the respective products is mainly tested
>> by the Stratos/Cloud team, and hence the issues may get uncovered late in
>> the release cycle. This will also reduce the number of binaries that have
>> to go through QA.
>>
>> Is this a feasible option? Thoughts welcome.
>>
>
> +1 for the idea.
>
> What about the java security policy configurations which only use in
> Stratos versions?
>

That should be disabled by default, and should be enabled during testing &
production deployment.


>
> thanks,
> Amila.
>
>
>
>>
>>  --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>> ___
>> Carbon-dev mailing list
>> carbon-...@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
>
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
>
> ___
> 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/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Testing

[Dhanushka Ranasinghe]

-- 
Dhanushka Ranasinghe,
WSO2 lnc  http://wso2.com
E-mail : dhanush...@wso2.com
Mobile : +94771928269
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Commits] [Carbon-kernel] svn commit r123874 - carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v5/modules/kernel/src/org/apache/axis2/util

[Afkham Azeez]

Please commit this to Apache trunk as well.

On Mon, Mar 26, 2012 at 1:02 PM,  wrote:

> Author: shankar
> Date: Mon Mar 26 03:32:26 2012
> New Revision: 123874
> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=123874
>
> Log:
> Closing the streams properly so that it will close all file handles.
>
> Modified:
>
> carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v5/modules/kernel/src/org/apache/axis2/util/XMLPrettyPrinter.java
>
> Modified:
> carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v5/modules/kernel/src/org/apache/axis2/util/XMLPrettyPrinter.java
> URL:
> http://wso2.org/svn/browse/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v5/modules/kernel/src/org/apache/axis2/util/XMLPrettyPrinter.java?rev=123874&r1=123873&r2=123874&view=diff
>
> ==
> ---
> carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v5/modules/kernel/src/org/apache/axis2/util/XMLPrettyPrinter.java
>  (original)
> +++
> carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v5/modules/kernel/src/org/apache/axis2/util/XMLPrettyPrinter.java
>  Mon Mar 26 03:32:26 2012
> @@ -58,7 +58,9 @@
> FileOutputStream outputStream = null;
> byte[] byteArray = null;
> try {
> -byteArray = IOUtils.getStreamAsByteArray(new
> FileInputStream(file));
> +FileInputStream fin = new FileInputStream(file);
> +byteArray = IOUtils.getStreamAsByteArray(fin);
> +fin.close();
> inputStream = new ByteArrayInputStream(byteArray);
> outputStream = new FileOutputStream(file);
>
> @@ -88,6 +90,18 @@
> log.debug("Pretty printed file : " + file);
> } catch (Throwable t) {
> log.debug("Exception occurred while trying to pretty print
> file " + file, t);
> +
> +/* if outputStream is already created, close them, because we
> are going reassign
> + * different value to that. It will leak the file handle
> (specially in windows, since
> + * deleting is going to be an issue)
> + */
> +if (outputStream != null) {
> +try {
> +outputStream.close();
> +} catch (IOException e) {
> +log.debug(e.getMessage(), e);
> +}
> +}
> try {
> if (byteArray != null) {
> outputStream = new FileOutputStream(file);
> ___
> Commits mailing list
> comm...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/commits
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] [Platform-Build] Identifier conflict in bam and bam2

[Sinthuja Ragendran]

Hi,

This is fixed in r123969. Take svn up.

Thanks,
Sinthuja.

On Mon, Mar 26, 2012 at 7:00 PM, Denis Weerasiri  wrote:

> Hi,
> Getting this error.
>
> [ERROR] Two or more projects in the reactor have the same identifier,
> please make sure that :: is unique for each
> project:
> {org.wso2.carbon:org.wso2.carbon.bam.core:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/components/bam/org.wso2.carbon.bam.core/pom.xml,
> /opt/installations/wso2/trunk/carbon/platform/trunk/components/bam2/org.wso2.carbon.bam.core/pom.xml],
> org.wso2.carbon:bam:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/components/bam/pom.xml,
> /opt/installations/wso2/trunk/carbon/platform/trunk/components/bam2/pom.xml],
> org.wso2.carbon:org.wso2.carbon.bam.feature:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam/org.wso2.carbon.bam.feature/pom.xml,
> /opt/installations/wso2/trunk/carbon/platform/trunk/features/bam2/org.wso2.carbon.bam.feature/pom.xml],
> org.wso2.carbon:org.wso2.carbon.bam.ui.feature:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam/org.wso2.carbon.bam.ui.feature/pom.xml,
> /opt/installations/wso2/trunk/carbon/platform/trunk/features/bam2/org.wso2.carbon.bam.ui.feature/pom.xml],
> org.wso2.carbon:bam-feature:4.0.0-SNAPSHOT=[/opt/installations/wso2/trunk/carbon/platform/trunk/features/bam/pom.xml,
> /opt/installations/wso2/trunk/carbon/platform/trunk/features/bam2/pom.xml]}
> -> [Help 1]
>
>
> --
> Thanks,
> Denis
> --
> *Denis Weerasiri*
> Software Engineer
> Integration Technologies Team, WSO2 Inc.; http://wso2.com,
> *email: denis ** [AT] wso2.com *
> *phone: +94117639629
> *
> *site: 
> **https://sites.google.com/site/ddweerasiri/*
> *blog: **http://ddweerasiri.blogspot.com*
> *
> twitter: **http://twitter.com/ddweerasiri*
> *
> linked-in: 
> **http://lk.linkedin.com/in/ddweerasiri*
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Framework Convention Violation] CarbonTomcatServiceHolder should be singleton

[Afkham Azeez]

org.wso2.carbon.tomcat.ext.internal.CarbonTomcatServiceHolder contains all
static methods. Please fix.

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] [Framework Convention Violation] CarbonTomcatServiceHolder should be singleton

[Pradeep Fernando]

Hi azeez,

I even discussed this convention with sameera,  (after URL mapper code
review).  We couldn't come up with any reason to follow this convention.

Why we are making it singleton ?

--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] axis2.xml not found in repository/conf

[Pradeep Fernando]

Hi,

I'm getting this erro while building carbon-kernel

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (2-dist)
on project wso2carbon: Failed to create assembly: File to filter not found:
/home/maven3/checkout/carbon/kernel/distribution/product/modules/distribution/target/wso2carbon-core-4.0.0-SNAPSHOT/repository/conf/axis2/axis2.xml
(No such file or directory) -> [Help 1]

--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Framework Convention Violation] CarbonTomcatServiceHolder should be singleton

[Afkham Azeez]

This is to avoid FindBugs warnings. There was a rationale behind it but now
I can't immediately recall it. Since mid 2010, we decided to adopt this as
a convention. http://wso2.org/svn/browse/wso2?revision=72106&view=revisionis
one of the first commits which was done after the FindBugs hackathon
to
fix these issues.

On Mon, Mar 26, 2012 at 8:27 PM, Pradeep Fernando  wrote:

> Hi azeez,
>
> I even discussed this convention with sameera,  (after URL mapper code
> review).  We couldn't come up with any reason to follow this convention.
>
> Why we are making it singleton ?
>
> --Pradeep
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] [Framework Convention Violation] CarbonTomcatServiceHolder should be singleton

[Afkham Azeez]

A related thread on StackOverflow

http://stackoverflow.com/questions/4457042/best-practice-for-updating-writing-to-static-variable

On Mon, Mar 26, 2012 at 8:49 PM, Afkham Azeez  wrote:

> Ah! Found it!
>
> " "Write to static field  and  from instance method
> someClassMethod"
>
> ServiceComponents are instances, and we are setting static values. Please
> religiously follow framework best practices that have been in existence.
> These best practices have been learnt over the past few years, so there is
> a reason that they have become best practices.
>
> Azeez
>
>
> On Mon, Mar 26, 2012 at 8:46 PM, Afkham Azeez  wrote:
>
>> This is to avoid FindBugs warnings. There was a rationale behind it but
>> now I can't immediately recall it. Since mid 2010, we decided to adopt this
>> as a convention.
>> http://wso2.org/svn/browse/wso2?revision=72106&view=revision is one of
>> the first commits which was done after the FindBugs hackathon to fix these
>> issues.
>>
>>
>> On Mon, Mar 26, 2012 at 8:27 PM, Pradeep Fernando wrote:
>>
>>> Hi azeez,
>>>
>>> I even discussed this convention with sameera,  (after URL mapper code
>>> review).  We couldn't come up with any reason to follow this convention.
>>>
>>> Why we are making it singleton ?
>>>
>>> --Pradeep
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] [Framework Convention Violation] CarbonTomcatServiceHolder should be singleton

[Afkham Azeez]

Ah! Found it!

" "Write to static field  and  from instance method
someClassMethod"

ServiceComponents are instances, and we are setting static values. Please
religiously follow framework best practices that have been in existence.
These best practices have been learnt over the past few years, so there is
a reason that they have become best practices.

Azeez


On Mon, Mar 26, 2012 at 8:46 PM, Afkham Azeez  wrote:

> This is to avoid FindBugs warnings. There was a rationale behind it but
> now I can't immediately recall it. Since mid 2010, we decided to adopt this
> as a convention.
> http://wso2.org/svn/browse/wso2?revision=72106&view=revision is one of
> the first commits which was done after the FindBugs hackathon to fix these
> issues.
>
>
> On Mon, Mar 26, 2012 at 8:27 PM, Pradeep Fernando wrote:
>
>> Hi azeez,
>>
>> I even discussed this convention with sameera,  (after URL mapper code
>> review).  We couldn't come up with any reason to follow this convention.
>>
>> Why we are making it singleton ?
>>
>> --Pradeep
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] [Framework Convention Violation] CarbonTomcatServiceHolder should be singleton

[Afkham Azeez]

I managed to locate the archived mail from 2010
http://wso2.org/mailarchive/carbon-dev/2010-August/042360.html



On Mon, Mar 26, 2012 at 8:50 PM, Afkham Azeez  wrote:

> A related thread on StackOverflow
>
>
> http://stackoverflow.com/questions/4457042/best-practice-for-updating-writing-to-static-variable
>
>
> On Mon, Mar 26, 2012 at 8:49 PM, Afkham Azeez  wrote:
>
>> Ah! Found it!
>>
>> " "Write to static field  and  from instance method
>> someClassMethod"
>>
>> ServiceComponents are instances, and we are setting static values. Please
>> religiously follow framework best practices that have been in existence.
>> These best practices have been learnt over the past few years, so there is
>> a reason that they have become best practices.
>>
>> Azeez
>>
>>
>> On Mon, Mar 26, 2012 at 8:46 PM, Afkham Azeez  wrote:
>>
>>> This is to avoid FindBugs warnings. There was a rationale behind it but
>>> now I can't immediately recall it. Since mid 2010, we decided to adopt this
>>> as a convention.
>>> http://wso2.org/svn/browse/wso2?revision=72106&view=revision is one of
>>> the first commits which was done after the FindBugs hackathon to fix these
>>> issues.
>>>
>>>
>>> On Mon, Mar 26, 2012 at 8:27 PM, Pradeep Fernando wrote:
>>>
 Hi azeez,

 I even discussed this convention with sameera,  (after URL mapper code
 review).  We couldn't come up with any reason to follow this convention.

 Why we are making it singleton ?

 --Pradeep

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] axis2.xml not found in repository/conf

[Afkham Azeez]

Ajanthan has moved the conf files into the agreed upon structure (r 123879).
Perhaps some stuff did not get into the commit?

On Mon, Mar 26, 2012 at 8:35 PM, Pradeep Fernando  wrote:

> Hi,
>
> I'm getting this erro while building carbon-kernel
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (2-dist)
> on project wso2carbon: Failed to create assembly: File to filter not found:
> /home/maven3/checkout/carbon/kernel/distribution/product/modules/distribution/target/wso2carbon-core-4.0.0-SNAPSHOT/repository/conf/axis2/axis2.xml
> (No such file or directory) -> [Help 1]
>
> --Pradeep
>
> ___
> 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/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] [Commits] [Carbon-kernel] svn commit r123973 - carbon/kernel/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/component/xml

[Afkham Azeez]

Constant interface is an anti-pattern. The proper fix would be to make this
interface into a "final class" and then use the classname qualified
constant, or static imports.

On Mon, Mar 26, 2012 at 8:44 PM,  wrote:

> Author: samisa
> Date: Mon Mar 26 11:14:29 2012
> New Revision: 123973
> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=123973
>
> Log:
> More Sonar reported issues fixed
>
> Modified:
>
> carbon/kernel/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/component/xml/ComponentConstants.java
>
> Modified:
> carbon/kernel/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/component/xml/ComponentConstants.java
> URL:
> http://wso2.org/svn/browse/wso2/carbon/kernel/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/component/xml/ComponentConstants.java?rev=123973&r1=123972&r2=123973&view=diff
>
> ==
> ---
> carbon/kernel/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/component/xml/ComponentConstants.java
>(original)
> +++
> carbon/kernel/trunk/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/component/xml/ComponentConstants.java
>Mon Mar 26 11:14:29 2012
> @@ -18,24 +18,24 @@
>  public interface ComponentConstants {
>
> //OMElement local names
> -public static final String ELE_DEPLOYERS = "deployers";
> -public static final String ELE_DEPLOYER = "deployer";
> -public static final String ELE_DIRECTORY = "directory";
> -public static final String ELE_EXTENSION = "extension";
> -
> -public static final String ELE_HTTP_GET_REQUEST_PROCESSORS =
> "httpGetRequestProcessors";
> -public static final String ELE_PROCESSOR = "processor";
> -public static final String ELE_ITEM = "item";
> -
> -public static final String ELE_COMPONENT_BUILDERS =
> "componentBuilders";
> -public static final String ELE_COMPONENT_BUILDER = "componentBuilder";
> -public static final String ELE_CLASS = "class";
> -public static final String ELE_ID = "id";
> +String ELE_DEPLOYERS = "deployers";
> +String ELE_DEPLOYER = "deployer";
> +String ELE_DIRECTORY = "directory";
> +String ELE_EXTENSION = "extension";
> +
> +String ELE_HTTP_GET_REQUEST_PROCESSORS = "httpGetRequestProcessors";
> +String ELE_PROCESSOR = "processor";
> +String ELE_ITEM = "item";
> +
> +String ELE_COMPONENT_BUILDERS = "componentBuilders";
> +String ELE_COMPONENT_BUILDER = "componentBuilder";
> +String ELE_CLASS = "class";
> +String ELE_ID = "id";
>
> //namespaces
> -public final static String NS_WSO2CARBON = "
> http://products.wso2.org/carbon";;
> +String NS_WSO2CARBON = "http://products.wso2.org/carbon";;
>
> -public static final String DEPLOYER_CONFIG = ELE_DEPLOYERS;
> -public static final String HTTP_GET_REQUEST_PROCESSORS =
> ELE_HTTP_GET_REQUEST_PROCESSORS;
> +String DEPLOYER_CONFIG = ELE_DEPLOYERS;
> +String HTTP_GET_REQUEST_PROCESSORS = ELE_HTTP_GET_REQUEST_PROCESSORS;
>
>  }
> ___
> Commits mailing list
> comm...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/commits
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] axis2.xml not found in repository/conf

[Afkham Azeez]

Yes, I'm also getting this error. In fact, Carbon kernel integration tests
are failing. Ajanthan, did you run tests before committing?

On Mon, Mar 26, 2012 at 9:05 PM, Afkham Azeez  wrote:

> Ajanthan has moved the conf files into the agreed upon structure (r
>  123879). Perhaps some stuff did not get into the commit?
>
> On Mon, Mar 26, 2012 at 8:35 PM, Pradeep Fernando wrote:
>
>> Hi,
>>
>> I'm getting this erro while building carbon-kernel
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (2-dist)
>> on project wso2carbon: Failed to create assembly: File to filter not found:
>> /home/maven3/checkout/carbon/kernel/distribution/product/modules/distribution/target/wso2carbon-core-4.0.0-SNAPSHOT/repository/conf/axis2/axis2.xml
>> (No such file or directory) -> [Help 1]
>>
>> --Pradeep
>>
>> ___
>> 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/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **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] PersistenceExceptions in ESB

[Isuru Suriarachchi]

On Mon, Mar 26, 2012 at 6:08 PM, Hiranya Jayathilaka wrote:

> Looks like it's only applying policies that's affected by this change. Can
> we have some sort of a fix for this as suggested by Isuru?


Sure, will provide a fix ASAP.. KasunG, please go ahead with this as
discussed offline..

Thanks,
~Isuru


>
> Thanks,
> Hiranya
>
>
> On Mon, Mar 26, 2012 at 3:38 PM, Hiranya Jayathilaka wrote:
>
>> Hi Isuru,
>>
>> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:

> How do you set the Registry to Synapse? Does it depend on the Registry
> API? If so, we can have a Registry implementation which works with the 
> file
> system persistence structure.


 Synapse accesses WSO2 registry through the Synapse registry API. We
 can't have a registry implementation that only works with the file system
 (because we need to be able to lookup registry resources too - WSDLs,
 endpoints and stuff). If we go along this path we have to come up with an
 implementation that can work with both WSO2 registry and local file system
 (kind of like a hybrid registry).

>>>
>>> I think for the time being the best option is to store the policies for
>>> proxy services also in the Registry. Hiranya, will it solve the problem or
>>> are there any other failure cases?
>>>
>> Is the problem only related to policies? It's better to identify all such
>>> problematic scenarios ASAP and address those.
>>>
>>
>> I'm trying out various scenarios with the ESB. So far this is the only
>> problematic case I came across. I'll run some more tests and let you know
>> my findings by EoD today.
>>
>>
>>>
>>> However, we have to come up with a better solution in the long run.
>>>
>>
>> +1
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>>

 Thanks,
 Hiranya


>
>
> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka  > wrote:
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe 
>>> wrote:
>>>


 On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
 hira...@wso2.com> wrote:

> I tried enabling caching for the service. It did get applied as
> expected. But the change didn't survive a restart. I think this is 
> same for
> other QoS modules too (throttling, RM etc).


  Does the relevant policy got added to the relevant metafile?

>>>
>>> Yes it does. I debugged this case a little bit, and I think the
>>> problem occurs because our proxy service observer expects to find the
>>> relevant policies in the registry. But they are no longer stored in the
>>> registry.
>>>
>>> In the past it was just a matter of updating the proxy service
>>> configuration with a key that points to the appropriate policy in the
>>> registry:
>>>
>>> 
>>>
>>> ESB knows how to resolve registry keys. But with the new model I
>>> don't know how the same behavior can be achieved.
>>>
>>
>> This is going to affect all QoS aspects of ESB including security.
>> How do we solve this problem? Synapse can only load policies from the
>> registry.
>>
>>
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Lakmali, I'll look into this. I've already answered your second
 issue.
 As I've been told earlier, please send the logs as soon as you
 faced with an issue related to persistence. At this point of time, this
 implementation isn't tested in other products than Kernel, and 
 AppServer.



> Thanks,
> Hiranya
>
>
> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
> lakm...@wso2.com> wrote:
>
>> Hi,
>>
>> I am also experiencing similar issues on DSS product & service.
>> When a service is saved the following exception occurs.
>>
>>  ERROR
>> {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
>> Unable to
>> handle new service addition. Service: H2BasicService
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>> at
>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:192)
>> at
>> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:280)
>>
>> at
>> org.apac

Re: [Dev] axis2.xml not found in repository/conf

[Ajanthan Balachandran]

Fixed at revision 123974.

On Mon, Mar 26, 2012 at 9:25 PM, Afkham Azeez  wrote:

> Yes, I'm also getting this error. In fact, Carbon kernel integration tests
> are failing. Ajanthan, did you run tests before committing?
>
>
> On Mon, Mar 26, 2012 at 9:05 PM, Afkham Azeez  wrote:
>
>> Ajanthan has moved the conf files into the agreed upon structure (r
>>  123879). Perhaps some stuff did not get into the commit?
>>
>> On Mon, Mar 26, 2012 at 8:35 PM, Pradeep Fernando wrote:
>>
>>> Hi,
>>>
>>> I'm getting this erro while building carbon-kernel
>>>
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (2-dist)
>>> on project wso2carbon: Failed to create assembly: File to filter not found:
>>> /home/maven3/checkout/carbon/kernel/distribution/product/modules/distribution/target/wso2carbon-core-4.0.0-SNAPSHOT/repository/conf/axis2/axis2.xml
>>> (No such file or directory) -> [Help 1]
>>>
>>> --Pradeep
>>>
>>> ___
>>> 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/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
ajanthan
-- 
Ajanthan Balachandiran
Software Engineer; WSO2, Inc.;  http://wso2.com/
email: ajanthan @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

Re: [Dev] Error while building trunk platform components

[Nirmal Fernando]

On Mon, Mar 26, 2012 at 5:17 PM, Dushan Abeyruwan  wrote:

> Hi
>
>  I am getting following error while building platform components, took
> latest update on orbit/kernel and was build successfully ,
> then platform deps/service-stutbs/parent build successfully
>
>
> [INFO] Finished at: Mon Mar 26 17:14:03 IST 2012
> [INFO] Final Memory: 1471M/1854M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile
> (default-compile) on project org.wso2.carbon.usage.agent: Compilation
> failure
> [ERROR]
> /home/dushan/wso2svntrunk/carbon/platform/trunk/components/stratos/usage/org.wso2.carbon.usage.agent/src/main/java/org/wso2/carbon/usage/agent/util/Util.java:[81,57]
> cannot find symbol
> [ERROR] symbol  : method getAdvancedCarbonConfigDirPath()
> [ERROR] location: class org.wso2.carbon.utils.CarbonUtils
>

Seems like someone missed a commit to CarbonUtils!


> [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.
> [ERRO
>
> --
> Dushan Abeyruwan
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks & regards,
Nirmal

Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Running some code when installing a feature for C4

[Tharindu Mathew]

Hi,

Is $subject possible?

-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Documentation Generation Issues in Carbon Kernel

[Senaka Fernando]

Hi all,

Please fix.

Thanks,
Senaka.

-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #125 has FAILED (1 tests failed). Change made by 8 authors.

[Bamboo]

---
WSO2 Carbon > Kernel > #125 failed.
---
This build occurred because it is a dependant of 
WSO2CARBON-CARBONKERNELBUILD-55.
1/2777 tests failed.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-125/


--
Failing Jobs
--
  - Default Job (Default Stage): 1 of 2777 tests failed.


--
Code Changes
--
azeez (123921):

>Adding the new Emma based code coverage framework
>
>

ajanthan (123928):

>fixing CARBON-12674

pradeep (123877):

>code cleanup



--
Tests
--
New Test Failures (1)
   - CarbonTestServerManager: Start server

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Thousands of Warnings when building from Platform top-level

[Senaka Fernando]

Hi all,

There is an almost unending list of warnings when building the entire
platform reported from Maven 3, about bad practices, missing declarations
etc. We should start working towards zeroing that. Please note.

Thanks,
Senaka.

-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running some code when installing a feature for C4

[Pradeep Fernando]

Hi,

yes, it should be possible. The rationale is,

when installing features, we already do things such as file-copying,
extracting, etc. Those are implemented as eclipse touchpoint actions. We
can come up with our own touchpoint implementations.

within the framework hook of the touchpoint implementation, we should be
able to do whatever we want. :)

then again, why we want this ? can you please explain the scenario.

--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Running some code when installing a feature for C4

[Tharindu Mathew]

I have configs stored in the registry. Easiest option is to run some code
to call the admin services. Otherwise, I have to look at file system based
configuration.

Can I do this without changing carbon core, i.e. within the
component/feature code? Meaning, is it possible to extend the touch point
for a new feature I'm going to implement without changing anything else

On Mon, Mar 26, 2012 at 10:21 PM, Pradeep Fernando  wrote:

> Hi,
>
> yes, it should be possible. The rationale is,
>
> when installing features, we already do things such as file-copying,
> extracting, etc. Those are implemented as eclipse touchpoint actions. We
> can come up with our own touchpoint implementations.
>
> within the framework hook of the touchpoint implementation, we should be
> able to do whatever we want. :)
>
> then again, why we want this ? can you please explain the scenario.
>
> --Pradeep
>



-- 
Regards,

Tharindu

blog: http://mackiemathew.com/
M: +9459908
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] axis2.xml not found in repository/conf

[Pradeep Fernando]

Hi,

Thanks, now its working. But the management console does not get rendered
properly. :(

--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] PersistenceExceptions in ESB

[Kasun Gajasinghe]

On Mon, Mar 26, 2012 at 9:28 PM, Isuru Suriarachchi  wrote:

>
>
> On Mon, Mar 26, 2012 at 6:08 PM, Hiranya Jayathilaka wrote:
>
>> Looks like it's only applying policies that's affected by this change.
>> Can we have some sort of a fix for this as suggested by Isuru?
>
>
> Sure, will provide a fix ASAP.. KasunG, please go ahead with this as
> discussed offline..
>
>
Sure.


> Thanks,
> ~Isuru
>
>
>>
>> Thanks,
>> Hiranya
>>
>>
>> On Mon, Mar 26, 2012 at 3:38 PM, Hiranya Jayathilaka wrote:
>>
>>> Hi Isuru,
>>>
>>> On Mon, Mar 26, 2012 at 3:34 PM, Isuru Suriarachchi wrote:
>>>


 On Mon, Mar 26, 2012 at 3:13 PM, Hiranya Jayathilaka 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 3:04 PM, Afkham Azeez  wrote:
>
>> How do you set the Registry to Synapse? Does it depend on the
>> Registry API? If so, we can have a Registry implementation which works 
>> with
>> the file system persistence structure.
>
>
> Synapse accesses WSO2 registry through the Synapse registry API. We
> can't have a registry implementation that only works with the file system
> (because we need to be able to lookup registry resources too - WSDLs,
> endpoints and stuff). If we go along this path we have to come up with an
> implementation that can work with both WSO2 registry and local file system
> (kind of like a hybrid registry).
>

 I think for the time being the best option is to store the policies for
 proxy services also in the Registry. Hiranya, will it solve the problem or
 are there any other failure cases?

>>> Is the problem only related to policies? It's better to identify all
 such problematic scenarios ASAP and address those.

>>>
>>> I'm trying out various scenarios with the ESB. So far this is the only
>>> problematic case I came across. I'll run some more tests and let you know
>>> my findings by EoD today.
>>>
>>>

 However, we have to come up with a better solution in the long run.

>>>
>>> +1
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>

 Thanks,
 ~Isuru


>
> Thanks,
> Hiranya
>
>
>>
>>
>> On Mon, Mar 26, 2012 at 2:51 PM, Hiranya Jayathilaka <
>> hira...@wso2.com> wrote:
>>
>>>
>>>
>>> On Mon, Mar 26, 2012 at 2:48 PM, Hiranya Jayathilaka <
>>> hira...@wso2.com> wrote:
>>>


 On Mon, Mar 26, 2012 at 2:39 PM, Kasun Gajasinghe 
 wrote:

>
>
> On Mon, Mar 26, 2012 at 2:34 PM, Hiranya Jayathilaka <
> hira...@wso2.com> wrote:
>
>> I tried enabling caching for the service. It did get applied as
>> expected. But the change didn't survive a restart. I think this is 
>> same for
>> other QoS modules too (throttling, RM etc).
>
>
>  Does the relevant policy got added to the relevant metafile?
>

 Yes it does. I debugged this case a little bit, and I think the
 problem occurs because our proxy service observer expects to find the
 relevant policies in the registry. But they are no longer stored in the
 registry.

 In the past it was just a matter of updating the proxy service
 configuration with a key that points to the appropriate policy in the
 registry:

 

 ESB knows how to resolve registry keys. But with the new model I
 don't know how the same behavior can be achieved.

>>>
>>> This is going to affect all QoS aspects of ESB including security.
>>> How do we solve this problem? Synapse can only load policies from the
>>> registry.
>>>
>>>

 Thanks,
 Hiranya


>
> Lakmali, I'll look into this. I've already answered your second
> issue.
> As I've been told earlier, please send the logs as soon as you
> faced with an issue related to persistence. At this point of time, 
> this
> implementation isn't tested in other products than Kernel, and 
> AppServer.
>
>
>
>> Thanks,
>> Hiranya
>>
>>
>> On Mon, Mar 26, 2012 at 2:32 PM, Lakmali Baminiwatta <
>> lakm...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I am also experiencing similar issues on DSS product & service.
>>> When a service is saved the following exception occurs.
>>>
>>>  ERROR
>>> {org.wso2.carbon.core.persistence.AbstractPersistenceManager} -  
>>> Unable to
>>> handle new service addition. Service: H2BasicService
>>> java.lang.NullPointerException
>>> at
>>> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewBindingAddition(ServicePersistenceManager.java:344)
>>> at
>>> org.wso2.carbon.core.p