Re: [Carbon-dev] Errors with latest build of BAM (Dashboard/Unable to handle new service addition.)

2010-02-25 Thread Nuwan Bandara 
This seems to be an error produced when we have two versions of
google-collections, So far we got this for bam (Since they use Data Services
and Shindig both). we will update the orbit google-collections bundle to the
latest version and test this issue.

Regards
/Nuwan

On Thu, Feb 25, 2010 at 12:47 PM, Ruwan Janapriya wrote:

> Hi Nuwan,
>
> Please see inline comments.
>
> Seems its not a dashboard related issue. Seems One of the resources you are
>> trying to access in not in the registry. (Resource does not exist at path
>> /_system/config/repository/axis2/service-groups/echo/services/echo/operations/echo).
>>
>
> Yup this is not dashboard related. This issue is fixed with the fix
> provided by Lahiru.
>
>
>> btw. The tab 0 error can also come, if your request url contains a param
>> called name= this should be compatible with the registry
>> resource name. i.e : /_system/config/repository/dashboards/bam then the
>> name should be "bam". if this is not in place the error can occur.
>>
>
> Now the issue is reduced to show correct Tabs. However gadgets are missing.
> Please note earlier and now the url contained the "name=bam" correctly.
>
> I am still getting the error (related to shindig)
> http://pastebin.com/S1ENjMXm just after server start.
>
> regards,
>
> Janapriya.
>
>
>> Regards
>> /Nuwan
>>
>>
>> On Thu, Feb 25, 2010 at 12:18 PM, Lahiru Gunathilake wrote:
>>
>>> Fixed ! Please update core. (registry.core and carbon.utils).
>>>
>>> Lahiru
>>>
>>> On Thu, Feb 25, 2010 at 12:05 PM, Ruwan Janapriya wrote:
>>>
 During startup of the latest build[1] I get the following[2] errors.

 There are errors related to Dashboard as well. Once logged in, the
 dashboard doesn't show BAM related tabs and gadgets. Shows the loading
 screen with the tab - "Tab 0"

 regards,

 Janapriya.

 [1]
 http://builder.wso2.org/~carbon/releases/carbon/3.0.0/Thu%20Feb%2025%2005:09:18%20UTC%202010/
 [2] http://pastebin.com/yn6uKhKj

 --
 Ruwan Janapriya
 Technical Lead - WSO2 Inc.

 http://wso2.com/ - "lean . enterprise . middleware"

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev


>>>
>>>
>>> --
>>> Lahiru Gunathilake
>>> Software Engineer - WSO2 Inc.
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Nuwan Bandara
>> WSO2 Inc. | http://www.wso2.com
>> email: nu...@wso2.com
>> mob: +94 772 907 484
>> blog: http://www.nuwanbando.com
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Ruwan Janapriya
> Technical Lead - WSO2 Inc.
>
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Nuwan Bandara
WSO2 Inc. | http://www.wso2.com
email: nu...@wso2.com
mob: +94 772 907 484
blog: http://www.nuwanbando.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Errors with latest build of BAM (Dashboard/Unable to handle new service addition.)

2010-02-25 Thread Anjana Fernando 
Hello,

I've upgraded the google-collections version to 1.0. The new version
of the google-collect orbit bundle is '1.0.0.wso2v2'. The usages of
the bundle are also changed accordingly.

Cheers,
Anjana.

On Thu, Feb 25, 2010 at 1:31 PM, Nuwan Bandara  wrote:
> This seems to be an error produced when we have two versions of
> google-collections, So far we got this for bam (Since they use Data Services
> and Shindig both). we will update the orbit google-collections bundle to the
> latest version and test this issue.
>
> Regards
> /Nuwan
>
> On Thu, Feb 25, 2010 at 12:47 PM, Ruwan Janapriya 
> wrote:
>>
>> Hi Nuwan,
>> Please see inline comments.
>>>
>>> Seems its not a dashboard related issue. Seems One of the resources you
>>> are trying to access in not in the registry. (Resource does not exist at
>>> path
>>> /_system/config/repository/axis2/service-groups/echo/services/echo/operations/echo).
>>
>> Yup this is not dashboard related. This issue is fixed with the fix
>> provided by Lahiru.
>>
>>>
>>> btw. The tab 0 error can also come, if your request url contains a param
>>> called name= this should be compatible with the registry
>>> resource name. i.e : /_system/config/repository/dashboards/bam then the name
>>> should be "bam". if this is not in place the error can occur.
>>
>> Now the issue is reduced to show correct Tabs. However gadgets are
>> missing. Please note earlier and now the url contained the "name=bam"
>> correctly.
>> I am still getting the error (related to
>> shindig) http://pastebin.com/S1ENjMXm just after server start.
>>
>> regards,
>> Janapriya.
>>>
>>> Regards
>>> /Nuwan
>>>
>>> On Thu, Feb 25, 2010 at 12:18 PM, Lahiru Gunathilake 
>>> wrote:

 Fixed ! Please update core. (registry.core and carbon.utils).
 Lahiru

 On Thu, Feb 25, 2010 at 12:05 PM, Ruwan Janapriya 
 wrote:
>
> During startup of the latest build[1] I get the following[2] errors.
> There are errors related to Dashboard as well. Once logged in, the
> dashboard doesn't show BAM related tabs and gadgets. Shows the loading
> screen with the tab - "Tab 0"
> regards,
> Janapriya.
>
> [1] http://builder.wso2.org/~carbon/releases/carbon/3.0.0/Thu%20Feb%2025%2005:09:18%20UTC%202010/
> [2] http://pastebin.com/yn6uKhKj
> --
> Ruwan Janapriya
> Technical Lead - WSO2 Inc.
>
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



 --
 Lahiru Gunathilake
 Software Engineer - WSO2 Inc.

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

>>>
>>>
>>>
>>> --
>>> Nuwan Bandara
>>> WSO2 Inc. | http://www.wso2.com
>>> email: nu...@wso2.com
>>> mob: +94 772 907 484
>>> blog: http://www.nuwanbando.com
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>
>>
>>
>> --
>> Ruwan Janapriya
>> Technical Lead - WSO2 Inc.
>>
>> http://wso2.com/ - "lean . enterprise . middleware"
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Nuwan Bandara
> WSO2 Inc. | http://www.wso2.com
> email: nu...@wso2.com
> mob: +94 772 907 484
> blog: http://www.nuwanbando.com
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>

___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] R: Simple routing logic with two nested "send"

2010-02-25 Thread Ruwan Linton 
Hi Roberto,

Message chaining seems to have a limitation which permits it being used 
in your case, let me propose an alternate approach to the callout 
in-order to get this working;

Please note that there are 2 proxy services and the out sequence of the 
proxy1 has been externalized in order to get the aggregation working 
properly. You might need to have a look at the aggregate mediator syntax 
to get this working properly.


 
 
   
 
  
   1. [...extract source IP address from request for validation]
   2.[create a new request for a a validation service]
  

 

   
   
  
  
 



  

  // here you have both the cloned original message and the response 
from the validation service on the same message context aggregated
  3. [retrieve the original request]
  4. [transform the original request adding the response of the 
validation service]
  
  
 
  




 
 
   // will not be called in this particular scenario
   
  
  

  
 


Hope this will help.

Thanks,
Ruwan


Cappa Roberto wrote:
> Any news about an example of chaining model?
>
> Thanks
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>   


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org

Lean . Enterprise . Middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Errors with latest build of BAM (Dashboard/Unable to handle new service addition.)

2010-02-25 Thread Nuwan Bandara 
Hi Guys,

I have made the necessary changes in the shindig and dashboard features as
well.

please take and up of

[1] carbon/orbit/
[2] online build orbit/google-collect
[3] build orbit/shindig
[4] take an svn up of carbon/features/dashboard and build it.
[5] build BAM and test it.

lets hope all will work fine (I test it with GS and the new changes applied
without an issue)

Thanks and regards
/Nuwan

On Thu, Feb 25, 2010 at 3:38 PM, Anjana Fernando  wrote:

> Hello,
>
> I've upgraded the google-collections version to 1.0. The new version
> of the google-collect orbit bundle is '1.0.0.wso2v2'. The usages of
> the bundle are also changed accordingly.
>
> Cheers,
> Anjana.
>
> On Thu, Feb 25, 2010 at 1:31 PM, Nuwan Bandara  wrote:
> > This seems to be an error produced when we have two versions of
> > google-collections, So far we got this for bam (Since they use Data
> Services
> > and Shindig both). we will update the orbit google-collections bundle to
> the
> > latest version and test this issue.
> >
> > Regards
> > /Nuwan
> >
> > On Thu, Feb 25, 2010 at 12:47 PM, Ruwan Janapriya 
> > wrote:
> >>
> >> Hi Nuwan,
> >> Please see inline comments.
> >>>
> >>> Seems its not a dashboard related issue. Seems One of the resources you
> >>> are trying to access in not in the registry. (Resource does not exist
> at
> >>> path
> >>>
> /_system/config/repository/axis2/service-groups/echo/services/echo/operations/echo).
> >>
> >> Yup this is not dashboard related. This issue is fixed with the fix
> >> provided by Lahiru.
> >>
> >>>
> >>> btw. The tab 0 error can also come, if your request url contains a
> param
> >>> called name= this should be compatible with the registry
> >>> resource name. i.e : /_system/config/repository/dashboards/bam then the
> name
> >>> should be "bam". if this is not in place the error can occur.
> >>
> >> Now the issue is reduced to show correct Tabs. However gadgets are
> >> missing. Please note earlier and now the url contained the "name=bam"
> >> correctly.
> >> I am still getting the error (related to
> >> shindig) http://pastebin.com/S1ENjMXm just after server start.
> >>
> >> regards,
> >> Janapriya.
> >>>
> >>> Regards
> >>> /Nuwan
> >>>
> >>> On Thu, Feb 25, 2010 at 12:18 PM, Lahiru Gunathilake 
> >>> wrote:
> 
>  Fixed ! Please update core. (registry.core and carbon.utils).
>  Lahiru
> 
>  On Thu, Feb 25, 2010 at 12:05 PM, Ruwan Janapriya  >
>  wrote:
> >
> > During startup of the latest build[1] I get the following[2] errors.
> > There are errors related to Dashboard as well. Once logged in, the
> > dashboard doesn't show BAM related tabs and gadgets. Shows the
> loading
> > screen with the tab - "Tab 0"
> > regards,
> > Janapriya.
> >
> > [1]
> http://builder.wso2.org/~carbon/releases/carbon/3.0.0/Thu%20Feb%2025%2005:09:18%20UTC%202010/
> > [2] http://pastebin.com/yn6uKhKj
> > --
> > Ruwan Janapriya
> > Technical Lead - WSO2 Inc.
> >
> > http://wso2.com/ - "lean . enterprise . middleware"
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> 
> 
> 
>  --
>  Lahiru Gunathilake
>  Software Engineer - WSO2 Inc.
> 
>  ___
>  Carbon-dev mailing list
>  Carbon-dev@wso2.org
>  https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> 
> >>>
> >>>
> >>>
> >>> --
> >>> Nuwan Bandara
> >>> WSO2 Inc. | http://www.wso2.com
> >>> email: nu...@wso2.com
> >>> mob: +94 772 907 484
> >>> blog: http://www.nuwanbando.com
> >>>
> >>> ___
> >>> Carbon-dev mailing list
> >>> Carbon-dev@wso2.org
> >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Ruwan Janapriya
> >> Technical Lead - WSO2 Inc.
> >>
> >> http://wso2.com/ - "lean . enterprise . middleware"
> >>
> >> ___
> >> Carbon-dev mailing list
> >> Carbon-dev@wso2.org
> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>
> >
> >
> >
> > --
> > Nuwan Bandara
> > WSO2 Inc. | http://www.wso2.com
> > email: nu...@wso2.com
> > mob: +94 772 907 484
> > blog: http://www.nuwanbando.com
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Nuwan Bandara
WSO2 Inc. | http://www.wso2.com
email: nu...@wso2.com
mob: +94 772 907 484
blog: http://www.nuwanbando.com
___
Carbo

Re: [Carbon-dev] Errors with latest build of BAM (Dashboard/Unable to handle new service addition.)

2010-02-25 Thread ratha 



Ruwan Janapriya wrote:
> During startup of the latest build[1] I get the following[2] errors.
>
> There are errors related to Dashboard as well. Once logged in, the 
> dashboard doesn't show BAM related tabs and gadgets. Shows the loading 
> screen with the tab - "Tab 0"
>
> regards,
>
> Janapriya.
>
> [1] 
> http://builder.wso2.org/~carbon/releases/carbon/3.0.0/Thu%20Feb%2025%2005:09:18%20UTC%202010/
>  
> 
> [2] http://pastebin.com/yn6uKhKj
>

Adding to this,
I couldn't add any of the server to monitor.
Polling server
-
[2010-02-25 17:31:14,531] ERROR -  Error while adding the new monitored 
server e
ntry
org.apache.axis2.AxisFault: addTenant failed for tenantId: 0
at 
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.j
ava:508)
at 
org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOutOnly
OperationClient.handleResponse(RobustOutOnlyAxisOperation.java:91)
at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO
peration.java:421)
at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(Out
InAxisOperation.java:229)
at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:
165)
at 
org.wso2.carbon.bam.mgt.ui.stub.bamconfig.BAMConfigAdminServiceStub.a
ddServer(BAMConfigAdminServiceStub.java:1033)
at 
org.wso2.carbon.bam.mgt.ui.client.BAMConfigAdminServiceClient.addServ
er(BAMConfigAdminServiceClient.java:46)
at 
org.apache.jsp.bam.add_005fserver_jsp._jspService(add_005fserver_jsp.

Eventing server
---
2010-02-25 17:33:09,875]  INFO -  Retrying request
[2010-02-25 17:33:09,875]  INFO -  Unable to sendViaPost to 
url[https://192.168.
1.3:9443/services/BAMServerUserDefinedStatPublisherService]
org.apache.axis2.AxisFault: Connection has been shutdown: 
javax.net.ssl.SSLHands
hakeException: sun.security.validator.ValidatorException: PKIX path 
building fai
led: sun.security.provider.certpath.SunCertPathBuilderException: unable 
to find
valid certification path to requested target
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at 
org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMess
ageFormatter.java:83)
at 
org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRe
questEntity.java:84)
at 
org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequ
estBody(EntityEnclosingMethod.java:499)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodB
ase.java:2114)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.j
ava:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Htt
pMethodDirector.java:398)

thanks.
-Ratha.

> -- 
> Ruwan Janapriya
> Technical Lead - WSO2 Inc.
>
> http://wso2.com/ - "lean . enterprise . middleware"
> 
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Carbon 3.0.0 - Iridium - Alpha2 builds

2010-02-25 Thread Samisa Abeysinghe 
Available here:
http://builder.wso2.org/~carbon/releases/carbon/3.0.0/1Alpha2/

These packs
are provided as is.
Please do a smoke test.

Samisa...
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] ESB 2.1.1 Proxy - Security lost when redeploy

2010-02-25 Thread Cappa Roberto 
Hi. On ESB 2.1.1, when a proxy is redeployed using the console link "redeploy", 
 security policies are lost. It is very dangerous for services exposed on 
internet. Is that a known bug?

Thanks.


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] ESB 2.1.1 Proxy - Security lost when redeploy

2010-02-25 Thread Samisa Abeysinghe 
On Thu, Feb 25, 2010 at 7:42 PM, Cappa Roberto <
roberto.ca...@guest.telecomitalia.it> wrote:

> Hi. On ESB 2.1.1, when a proxy is redeployed using the console link
> "redeploy",  security policies are lost. It is very dangerous for services
> exposed on internet. Is that a known bug?
>

Yes. Please try with 2.1.3

Samisa...


>
> Thanks.
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://wso2.com/ - "lean . enterprise . middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Branching dependencies for the Iridium release

2010-02-25 Thread Samisa Abeysinghe 
Shall we proceed with this?

And we should really deploy to repos when the branches are done.

Thanks,
Samisa...

On Tue, Feb 23, 2010 at 3:21 AM, Ruwan Linton  wrote:

> Samisa Abeysinghe wrote:
> > I think it is time that we did $subject
> >
> > Thoughts?
> How about Thursday?
> >
> > Any volunteers please :)
> I'll do this.
>
> Thanks,
> Ruwan
> >
> > Samisa...
> >
> > --
> > Samisa Abeysinghe
> > Director, Engineering - WSO2 Inc.
> >
> > http://wso2.com/ - "lean . enterprise . middleware"
> > 
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://wso2.com/ - "lean . enterprise . middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Branching dependencies for the Iridium release

2010-02-25 Thread Ruwan Linton 
Samisa Abeysinghe wrote:
> Shall we proceed with this?
>
> And we should really deploy to repos when the branches are done.
We can branch today, but cannot deploy, since there could be minor fixes 
for those branches.

Thanks,
Ruwan
>
> Thanks,
> Samisa...
>
> On Tue, Feb 23, 2010 at 3:21 AM, Ruwan Linton  > wrote:
>
> Samisa Abeysinghe wrote:
> > I think it is time that we did $subject
> >
> > Thoughts?
> How about Thursday?
> >
> > Any volunteers please :)
> I'll do this.
>
> Thanks,
> Ruwan
> >
> > Samisa...
> >
> > --
> > Samisa Abeysinghe
> > Director, Engineering - WSO2 Inc.
> >
> > http://wso2.com/ - "lean . enterprise . middleware"
> >
> 
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org 
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2  Inc.; http://wso2.org
> email: ru...@wso2.com ; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org 
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
> -- 
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://wso2.com/ - "lean . enterprise . middleware"
> 
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org

Lean . Enterprise . Middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Branching dependencies for the Iridium release

2010-02-25 Thread Samisa Abeysinghe 
On Thu, Feb 25, 2010 at 9:27 PM, Ruwan Linton  wrote:

> Samisa Abeysinghe wrote:
> > Shall we proceed with this?
> >
> > And we should really deploy to repos when the branches are done.
> We can branch today, but cannot deploy, since there could be minor fixes
> for those branches.
>

We can re-deploy in case of fixes.

Samisa...


>
> Thanks,
> Ruwan
> >
> > Thanks,
> > Samisa...
> >
> > On Tue, Feb 23, 2010 at 3:21 AM, Ruwan Linton  > > wrote:
> >
> > Samisa Abeysinghe wrote:
> > > I think it is time that we did $subject
> > >
> > > Thoughts?
> > How about Thursday?
> > >
> > > Any volunteers please :)
> > I'll do this.
> >
> > Thanks,
> > Ruwan
> > >
> > > Samisa...
> > >
> > > --
> > > Samisa Abeysinghe
> > > Director, Engineering - WSO2 Inc.
> > >
> > > http://wso2.com/ - "lean . enterprise . middleware"
> > >
> >
> 
> > >
> > > ___
> > > Carbon-dev mailing list
> > > Carbon-dev@wso2.org 
> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> > >
> >
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> > WSO2  Inc.; http://wso2.org
> > email: ru...@wso2.com ; cell: +94 77 341 3097
> > blog: http://blog.ruwan.org
> >
> > Lean . Enterprise . Middleware
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org 
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
> >
> >
> > --
> > Samisa Abeysinghe
> > Director, Engineering - WSO2 Inc.
> >
> > http://wso2.com/ - "lean . enterprise . middleware"
> > 
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://wso2.com/ - "lean . enterprise . middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Branching dependencies for the Iridium release

2010-02-25 Thread Senaka Fernando 
On Thu, Feb 25, 2010 at 9:31 PM, Samisa Abeysinghe  wrote:

>
>
> On Thu, Feb 25, 2010 at 9:27 PM, Ruwan Linton  wrote:
>
>> Samisa Abeysinghe wrote:
>> > Shall we proceed with this?
>> >
>> > And we should really deploy to repos when the branches are done.
>> We can branch today, but cannot deploy, since there could be minor fixes
>> for those branches.
>>
>
> We can re-deploy in case of fixes.
>

Btw, do we also need to change the versions of these?

Thanks,
Senaka.

>
> Samisa...
>
>
>>
>> Thanks,
>> Ruwan
>> >
>> > Thanks,
>> > Samisa...
>> >
>> > On Tue, Feb 23, 2010 at 3:21 AM, Ruwan Linton > > > wrote:
>> >
>> > Samisa Abeysinghe wrote:
>> > > I think it is time that we did $subject
>> > >
>> > > Thoughts?
>> > How about Thursday?
>> > >
>> > > Any volunteers please :)
>> > I'll do this.
>> >
>> > Thanks,
>> > Ruwan
>> > >
>> > > Samisa...
>> > >
>> > > --
>> > > Samisa Abeysinghe
>> > > Director, Engineering - WSO2 Inc.
>> > >
>> > > http://wso2.com/ - "lean . enterprise . middleware"
>> > >
>> >
>> 
>> > >
>> > > ___
>> > > Carbon-dev mailing list
>> > > Carbon-dev@wso2.org 
>> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> > >
>> >
>> >
>> > --
>> > Ruwan Linton
>> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> > WSO2  Inc.; http://wso2.org
>> > email: ru...@wso2.com ; cell: +94 77 341
>> 3097
>> > blog: http://blog.ruwan.org
>> >
>> > Lean . Enterprise . Middleware
>> >
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org 
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> >
>> >
>> >
>> > --
>> > Samisa Abeysinghe
>> > Director, Engineering - WSO2 Inc.
>> >
>> > http://wso2.com/ - "lean . enterprise . middleware"
>> > 
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>>
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2  Inc.; http://wso2.org
>> email: ru...@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>>
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Senaka Fernando
Software Engineer
WSO2 Inc.
E-mail: senaka AT wso2.com;  Mobile: +94 77 322 1818

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

Re: [Carbon-dev] Branching dependencies for the Iridium release

2010-02-25 Thread Ruwan Linton 
-1 for re-deploying.

If we do not change the version, that causes a lot of issues, since 
maven doesn't update the release artifacts from the repo.
If we are to change the versions, then it is going to be a mess with 
different minor versions.

Thanks,
Ruwan

Senaka Fernando wrote:
>
>
> On Thu, Feb 25, 2010 at 9:31 PM, Samisa Abeysinghe  > wrote:
>
>
>
> On Thu, Feb 25, 2010 at 9:27 PM, Ruwan Linton  > wrote:
>
> Samisa Abeysinghe wrote:
> > Shall we proceed with this?
> >
> > And we should really deploy to repos when the branches are done.
> We can branch today, but cannot deploy, since there could be
> minor fixes
> for those branches.
>
>
> We can re-deploy in case of fixes. 
>
>
> Btw, do we also need to change the versions of these?
>
> Thanks,
> Senaka.
>
>
> Samisa...
>  
>
>
> Thanks,
> Ruwan
> >
> > Thanks,
> > Samisa...
> >
> > On Tue, Feb 23, 2010 at 3:21 AM, Ruwan Linton
> mailto:ru...@wso2.com>
> > >> wrote:
> >
> > Samisa Abeysinghe wrote:
> > > I think it is time that we did $subject
> > >
> > > Thoughts?
> > How about Thursday?
> > >
> > > Any volunteers please :)
> > I'll do this.
> >
> > Thanks,
> > Ruwan
> > >
> > > Samisa...
> > >
> > > --
> > > Samisa Abeysinghe
> > > Director, Engineering - WSO2 Inc.
> > >
> > > http://wso2.com/ - "lean . enterprise . middleware"
> > >
> >
> 
> 
> > >
> > > ___
> > > Carbon-dev mailing list
> > > Carbon-dev@wso2.org 
> >
> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> > >
> >
> >
> > --
> > Ruwan Linton
> > Technical Lead & Product Manager; WSO2 ESB;
> http://wso2.org/esb
> > WSO2  Inc.; http://wso2.org
> > email: ru...@wso2.com 
> >; cell: +94 77
> 341 3097
> > blog: http://blog.ruwan.org
> >
> > Lean . Enterprise . Middleware
> >
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org 
> >
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
> >
> >
> >
> > --
> > Samisa Abeysinghe
> > Director, Engineering - WSO2 Inc.
> >
> > http://wso2.com/ - "lean . enterprise . middleware"
> >
> 
> 
> >
> > ___
> > Carbon-dev mailing list
> > Carbon-dev@wso2.org 
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2  Inc.; http://wso2.org
> email: ru...@wso2.com ; cell: +94 77
> 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org 
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
> -- 
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://wso2.com/ - "lean . enterprise . middleware"
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org 
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
> -- 
> Senaka Fernando
> Software Engineer
> WSO2 Inc.
> E-mail: senaka AT wso2.com ;  Mobile: +94 77 322 1818
>
> http://www.wso2.com/ - "Lean . Enterprise . Middleware"
> 
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>

[Carbon-dev] [ATTENTION] Branching the dependencies

2010-02-25 Thread Ruwan Linton 
Folks,

We are currently branching all the dependencies, please refrain from 
committing to the dependencies till I inform the new branch information.

Thanks,
Ruwan

-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org

Lean . Enterprise . Middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [ATTENTION] Branching the dependencies

2010-02-25 Thread Samisa Abeysinghe 
On Thu, Feb 25, 2010 at 10:03 PM, Ruwan Linton  wrote:

> Folks,
>
> We are currently branching all the dependencies, please refrain from
> committing to the dependencies till I inform the new branch information.
>

I hope the one checkout will still work after branching, as we are
using externs from within dependencies folder. ?

Samisa...


>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://wso2.com/ - "lean . enterprise . middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [ATTENTION] Branching the dependencies

2010-02-25 Thread Ruwan Linton 
Samisa Abeysinghe wrote:
>
>
> On Thu, Feb 25, 2010 at 10:03 PM, Ruwan Linton  > wrote:
>
> Folks,
>
> We are currently branching all the dependencies, please refrain from
> committing to the dependencies till I inform the new branch
> information.
>
>
> I hope the one checkout will still work after branching, as we are 
> using externs from within dependencies folder. ?
One checkout will work,

I have created the carbon/3.0.0 branch and in the process of branching 
all the dependencies. Once the branching has been done, I will delete 
the existing dependencies directory and add an svn external to the newly 
branched dependencies root, so that the trunk will work as it was, but 
taking dependencies from the 3.0.0 branch.

Thanks,
Ruwan
>
> Samisa...
>  
>
>
> Thanks,
> Ruwan
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2  Inc.; http://wso2.org
> email: ru...@wso2.com ; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org 
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
>
>
> -- 
> Samisa Abeysinghe
> Director, Engineering - WSO2 Inc.
>
> http://wso2.com/ - "lean . enterprise . middleware"
> 
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>   


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org

Lean . Enterprise . Middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [ATTENTION] Branching the dependencies

2010-02-25 Thread Ruwan Linton 
Ruwan Linton wrote:
> Samisa Abeysinghe wrote:
>>
>>
>> On Thu, Feb 25, 2010 at 10:03 PM, Ruwan Linton > > wrote:
>>
>> Folks,
>>
>> We are currently branching all the dependencies, please refrain from
>> committing to the dependencies till I inform the new branch
>> information.
>>
>>
>> I hope the one checkout will still work after branching, as we are 
>> using externs from within dependencies folder. ?
> One checkout will work,
>
> I have created the carbon/3.0.0 branch and in the process of branching 
> all the dependencies. Once the branching has been done, I will delete 
> the existing dependencies directory and add an svn external to the 
> newly branched dependencies root, so that the trunk will work as it 
> was, but taking dependencies from the 3.0.0 branch.
I wont delete the dependencies trunk, rather will add externals to all 
the dependencies from trunk to the branch, because that way it is easy 
to switch the trunk back to the open development once we have branched 
full carbon structure.

Thanks,
Ruwan
>
> Thanks,
> Ruwan
>>
>> Samisa...
>>  
>>
>>
>> Thanks,
>> Ruwan
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2  Inc.; http://wso2.org
>> email: ru...@wso2.com ; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>>
>> Lean . Enterprise . Middleware
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org 
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>>
>>
>> -- 
>> Samisa Abeysinghe
>> Director, Engineering - WSO2 Inc.
>>
>> http://wso2.com/ - "lean . enterprise . middleware"
>> 
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>   
>
>


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org

Lean . Enterprise . Middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] -Dsetup is not working

2010-02-25 Thread Krishantha Samaraweera 
the same Issue seems to be there in Alpha2 build. I tried to start the
server with oracle and got the same error. Placing driver jars at
/lib/endorsed doesn't work either.

Thanks,
Krishantha.

On Wed, Feb 24, 2010 at 3:04 PM, Charitha Kankanamge  wrote:
> Apparently this seems to be an issue with loading jars placed at
> repository/components/lib directory. When I copied the driver to
> lib/endorsed, I was able to connect to registry DB.
> Please have a look.
>
> Regards
> Charitha
>
> Charitha Kankanamge
> WSO2 Inc.
> http://wso2.org
> email: chari...@wso2.com
> cell: +94 718 359 265
> blog: http://charithaka.blogspot.com
>
>
> On Wed, Feb 24, 2010 at 2:59 PM, Charitha Kankanamge 
> wrote:
>>
>> I cannot connect to registry DB even after setting up DB using mysql.sql
>> script. I always get "Cannot load JDBC driver class 'com.mysql.jdbc.Driver'
>> " error at the server startup. mysql driver
>> (mysql-connector-java-5.1.7-bin.jar) was placed at
>> repository/components/lib.
>>
>> ERROR -  Cannot start User Manager Core bundle
>> org.wso2.carbon.user.core.UserStoreException: Database Error - Cannot load
>> JDBC driver class 'com.mysql.jdbc.Driver'
>>     at
>> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:151)
>>     at
>> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:132)
>>     at
>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:94)
>>     at
>> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:34)
>>     at
>> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:50)
>>     at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
>>     at java.security.AccessController.doPrivileged(Native Method)
>>     at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
>>     at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
>>     at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
>>     at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
>>     at
>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
>>     at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
>>     at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
>>     at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
>>     at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
>>     at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>>     at
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
>> Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC
>> driver class 'com.mysql.jdbc.Driver'
>>     at
>> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1136)
>>     at
>> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
>>     at
>> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:141)
>>     ... 17 more
>> Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
>>     at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
>>     at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
>>     at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
>>     at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
>>     at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>>     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
>>     at java.lang.Class.forName0(Native Method)
>>     at java.lang.Class.forName(Class.java:169)
>>     at
>> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1130)
>>     ... 19 more
>>
>>
>> Charitha Kankanamge
>> WSO2 Inc.
>> http://wso2.org
>> email: chari...@wso2.com
>> cell: +94 718 359 265
>> blog: http://charithaka.blogspot.com
>>
>>
>> On Tue, Feb 23, 2010 at 10:56 AM, Senaka Fernando  wrote:
>>>
>>> It has been working for me since yesterday. I wonder what went wrong
>>> within a day??
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> On Tue, Feb 23, 2010 at 7:48 AM, Sumedha Rubasinghe 
>>> wrote:

 Folks,
 Looks like -Dsetup is no longer working on trunk. Has anyone touched the
 started up parameter area recently?

 /sumedha

 ___
 Carbon-dev mailing list
 Carbon-dev@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

>>>
>>>
>

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Krishantha Samaraweera 
Since it will take time to setup perf tests with embedded registry,
APP based perf tests have been executed with alpha2 build using
Oracle. Following dead lock situation occurred just after starting the
worker1 class with 500 iterations and 20 concurrent users. Please
refer to [1] detail error log.

[2010-02-25 22:39:25,171] ERROR -  A SQLException error has occurred
when trying to close result set or prepared statement
java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource

at 
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at 
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at 
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
at 
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
at 
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
at 
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
at 
org.wso2.carbon.registry.core.jdbc.dao.ResourceDAO.deleteContentStream(ResourceDAO.java:658)
at 
org.wso2.carbon.registry.core.jdbc.dao.ResourceVersionDAO.versionResource(ResourceVersionDAO.java:1052)
at 
org.wso2.carbon.registry.core.jdbc.VersionRepository.createVersionForResource(VersionRepository.java:191)
at 
org.wso2.carbon.registry.core.jdbc.VersionRepository.createSnapshot(VersionRepository.java:77)
at 
org.wso2.carbon.registry.core.jdbc.Repository.deleteSubTree(Repository.java:471)
at 
org.wso2.carbon.registry.core.jdbc.Repository.delete(Repository.java:403)
at 
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.delete(EmbeddedRegistry.java:805)
at 
org.wso2.carbon.registry.core.session.UserRegistry.delete(UserRegistry.java:625)
at 
org.wso2.carbon.registry.app.RegistryAdapter.processDeleteRequest(RegistryAdapter.java:602)
at 
org.wso2.carbon.registry.app.RegistryAdapter.extensionRequest(RegistryAdapter.java:124)
at 
org.apache.abdera.protocol.server.impl.AbstractProvider.processExtensionRequest(AbstractProvider.java:196)
at 
org.apache.abdera.protocol.server.impl.AbstractProvider.process(AbstractProvider.java:137)
at 
org.apache.abdera.protocol.server.FilterChain.next(FilterChain.java:42)
at 
org.apache.abdera.protocol.server.servlet.AbderaServlet.service(AbderaServlet.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
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:802)
at org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:135)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
at 
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:619)

Thanks,
Krishantha.

[1] http://pastebin.com/Wi5RADvm


On Wed, Feb 24, 2010 at 1:08 PM, Krishantha Samaraweera
 wrote:
> On Wed, Feb 24, 2010 at 12:18 PM, Dimuthu Gamage  wrote:
>> +1 for running perf tests. We can't re

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Senaka Fernando 
Hi Krishantha,

Thanks for the information.

Regards,
Senaka.

On Fri, Feb 26, 2010 at 12:51 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> On Fri, Feb 26, 2010 at 12:03 AM, Senaka Fernando  wrote:
>
>> I wonder whether the changes made by Sumedha went into alpha2. Anyway, the
>> results don't seem very informative to understand what actually happened.
>> Can you do the same tests on H2 and paste any issues you see.
>>
>
> AFAIK, H2 doesn't support for higher concurrency. Hence I run with minimal
> load. It was 100 iterations with 10 concurrent users.
>
> [2010-02-26 00:31:35,494] ERROR -  Failed to add resource to path
> /test/thread_T29/resourceZ9. Deadlock detected. The current transaction was
> rolled back. Details:
> Session #312 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_CONTENT while
> locking PUBLIC.REG_CONTENT_HISTORY (exclusive), PUBLIC.REG_RESOURCE_HISTORY
> (exclusive), PUBLIC.REG_RESOURCE (exclusive).
> Session #309 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_RESOURCE
> while locking PUBLIC.REG_CONTENT (exclusive).; SQL statement:
> INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
> REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
> REG_DESCRIPTION, REG_CONTENT_ID, REG_TENANT_ID) VALUES (?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?) [40001-112]
>
> org.h2.jdbc.JdbcSQLException: Deadlock detected. The current transaction
> was rolled back. Details:
> Session #312 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_CONTENT while
> locking PUBLIC.REG_CONTENT_HISTORY (exclusive), PUBLIC.REG_RESOURCE_HISTORY
> (exclusive), PUBLIC.REG_RESOURCE (exclusive).
> Session #309 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_RESOURCE
> while locking PUBLIC.REG_CONTENT (exclusive).; SQL statement:
> INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
> REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
> REG_DESCRIPTION, REG_CONTENT_ID, REG_TENANT_ID) VALUES (?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?) [40001-112]
>
> at org.h2.message.Message.getSQLException(Message.java:107)
> at org.h2.message.Message.getSQLException(Message.java:118)
> at org.h2.message.Message.getSQLException(Message.java:77)
> at org.h2.table.TableData.doLock(TableData.java:428)
> at org.h2.table.TableData.lock(TableData.java:375)
> at org.h2.command.dml.Insert.update(Insert.java:99)
> at org.h2.command.CommandContainer.update(CommandContainer.java:71)
> at org.h2.command.Command.executeUpdate(Command.java:207)
> at
> org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:139)
> at
> org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:128)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
>  at
> org.wso2.carbon.registry.core.jdbc.dao.ResourceDAO.addResource(ResourceDAO.java:1267)
> at
> org.wso2.carbon.registry.core.jdbc.dao.ResourceDAO.add(ResourceDAO.java:573)
> at
> org.wso2.carbon.registry.core.jdbc.Repository.add(Repository.java:933)
> at
> org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:287)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:711)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:599)
> at
> org.wso2.carbon.registry.app.RegistryAdapter.postEntry(RegistryAdapter.java:1184)
> at
> org.wso2.carbon.registry.app.RegistryAdapter.postEntry(RegistryAdapter.java:52)
> at
> org.apache.abdera.protocol.server.impl.AbstractEntityCollectionAdapter.createNonMediaEntry(AbstractEntityCollectionAdapter.java:665)
> at
> org.apache.abdera.protocol.server.impl.AbstractEntityCollectionAdapter.postEntry(AbstractEntityCollectionAdapter.java:122)
> at
> org.wso2.carbon.registry.app.RegistryAdapter.postEntry(RegistryAdapter.java:1028)
> at
> org.apache.abdera.protocol.server.processors.CollectionRequestProcessor.processCollection(CollectionRequestProcessor.java:47)
> at
> org.apache.abdera.protocol.server.processors.CollectionRequestProcessor.process(CollectionRequestProcessor.java:38)
> at
> org.apache.abdera.protocol.server.impl.AbstractProvider.process(AbstractProvider.java:136)
>
> at
> org.apache.abdera.protocol.server.FilterChain.next(FilterChain.java:42)
> at
> org.apache.abdera.protocol.server.servlet.AbderaServlet.service(AbderaServlet.java:90)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> 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.ser

Re: [Carbon-dev] -Dsetup is not working

2010-02-25 Thread Senaka Fernando 
Hi Krishantha,

This works at times and don't at times isn't it? Its not an issue with
-Dsetup, but an issue in the way in how we place the jars on the classpath.
If it doesn't work, it shouldn't work at all.

Sameera, what is the correct answer regarding where to place these driver
jars?

Thanks,
Senaka.

On Thu, Feb 25, 2010 at 10:59 PM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> the same Issue seems to be there in Alpha2 build. I tried to start the
> server with oracle and got the same error. Placing driver jars at
> /lib/endorsed doesn't work either.
>
> Thanks,
> Krishantha.
>
> On Wed, Feb 24, 2010 at 3:04 PM, Charitha Kankanamge 
> wrote:
> > Apparently this seems to be an issue with loading jars placed at
> > repository/components/lib directory. When I copied the driver to
> > lib/endorsed, I was able to connect to registry DB.
> > Please have a look.
> >
> > Regards
> > Charitha
> >
> > Charitha Kankanamge
> > WSO2 Inc.
> > http://wso2.org
> > email: chari...@wso2.com
> > cell: +94 718 359 265
> > blog: http://charithaka.blogspot.com
> >
> >
> > On Wed, Feb 24, 2010 at 2:59 PM, Charitha Kankanamge 
> > wrote:
> >>
> >> I cannot connect to registry DB even after setting up DB using mysql.sql
> >> script. I always get "Cannot load JDBC driver class
> 'com.mysql.jdbc.Driver'
> >> " error at the server startup. mysql driver
> >> (mysql-connector-java-5.1.7-bin.jar) was placed at
> >> repository/components/lib.
> >>
> >> ERROR -  Cannot start User Manager Core bundle
> >> org.wso2.carbon.user.core.UserStoreException: Database Error - Cannot
> load
> >> JDBC driver class 'com.mysql.jdbc.Driver'
> >> at
> >>
> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:151)
> >> at
> >>
> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:132)
> >> at
> >>
> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:94)
> >> at
> >>
> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:34)
> >> at
> >>
> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:50)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
> >> at java.security.AccessController.doPrivileged(Native Method)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
> >> at
> >>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
> >> at
> >>
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> >> at
> >>
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
> >> Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC
> >> driver class 'com.mysql.jdbc.Driver'
> >> at
> >>
> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1136)
> >> at
> >>
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
> >> at
> >>
> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:141)
> >> ... 17 more
> >> Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
> >> at
> >>
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
> >> at
> >>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
> >> at
> >>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
> >> at
> >>
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> >> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> >> at java.lang.Class.forName0(Native Method)
> >> at java.lang.Class.forName(Class.java:169)
> >> at
> >>
> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1130)
> >> ... 19 more
> >>
> >>
> >> Charitha Kankanamge
> >> WSO2 Inc.
> >> http://wso2.org
> >> email: chari...@wso2.com
> >> cell: +94 718

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Krishantha Samaraweera 
On Fri, Feb 26, 2010 at 12:03 AM, Senaka Fernando  wrote:

> I wonder whether the changes made by Sumedha went into alpha2. Anyway, the
> results don't seem very informative to understand what actually happened.
> Can you do the same tests on H2 and paste any issues you see.
>

AFAIK, H2 doesn't support for higher concurrency. Hence I run with minimal
load. It was 100 iterations with 10 concurrent users.

[2010-02-26 00:31:35,494] ERROR -  Failed to add resource to path
/test/thread_T29/resourceZ9. Deadlock detected. The current transaction was
rolled back. Details:
Session #312 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_CONTENT while
locking PUBLIC.REG_CONTENT_HISTORY (exclusive), PUBLIC.REG_RESOURCE_HISTORY
(exclusive), PUBLIC.REG_RESOURCE (exclusive).
Session #309 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_RESOURCE while
locking PUBLIC.REG_CONTENT (exclusive).; SQL statement:
INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
REG_DESCRIPTION, REG_CONTENT_ID, REG_TENANT_ID) VALUES (?, ?, ?, ?, ?, ?, ?,
?, ?, ?) [40001-112]
org.h2.jdbc.JdbcSQLException: Deadlock detected. The current transaction was
rolled back. Details:
Session #312 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_CONTENT while
locking PUBLIC.REG_CONTENT_HISTORY (exclusive), PUBLIC.REG_RESOURCE_HISTORY
(exclusive), PUBLIC.REG_RESOURCE (exclusive).
Session #309 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_RESOURCE while
locking PUBLIC.REG_CONTENT (exclusive).; SQL statement:
INSERT INTO REG_RESOURCE (REG_PATH_ID, REG_NAME, REG_MEDIA_TYPE,
REG_CREATOR, REG_CREATED_TIME, REG_LAST_UPDATOR, REG_LAST_UPDATED_TIME,
REG_DESCRIPTION, REG_CONTENT_ID, REG_TENANT_ID) VALUES (?, ?, ?, ?, ?, ?, ?,
?, ?, ?) [40001-112]
at org.h2.message.Message.getSQLException(Message.java:107)
at org.h2.message.Message.getSQLException(Message.java:118)
at org.h2.message.Message.getSQLException(Message.java:77)
at org.h2.table.TableData.doLock(TableData.java:428)
at org.h2.table.TableData.lock(TableData.java:375)
at org.h2.command.dml.Insert.update(Insert.java:99)
at org.h2.command.CommandContainer.update(CommandContainer.java:71)
at org.h2.command.Command.executeUpdate(Command.java:207)
at
org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:139)
at
org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:128)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
at
org.wso2.carbon.registry.core.jdbc.dao.ResourceDAO.addResource(ResourceDAO.java:1267)
at
org.wso2.carbon.registry.core.jdbc.dao.ResourceDAO.add(ResourceDAO.java:573)
at
org.wso2.carbon.registry.core.jdbc.Repository.add(Repository.java:933)
at
org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:287)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:711)
at
org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:599)
at
org.wso2.carbon.registry.app.RegistryAdapter.postEntry(RegistryAdapter.java:1184)
at
org.wso2.carbon.registry.app.RegistryAdapter.postEntry(RegistryAdapter.java:52)
at
org.apache.abdera.protocol.server.impl.AbstractEntityCollectionAdapter.createNonMediaEntry(AbstractEntityCollectionAdapter.java:665)
at
org.apache.abdera.protocol.server.impl.AbstractEntityCollectionAdapter.postEntry(AbstractEntityCollectionAdapter.java:122)
at
org.wso2.carbon.registry.app.RegistryAdapter.postEntry(RegistryAdapter.java:1028)
at
org.apache.abdera.protocol.server.processors.CollectionRequestProcessor.processCollection(CollectionRequestProcessor.java:47)
at
org.apache.abdera.protocol.server.processors.CollectionRequestProcessor.process(CollectionRequestProcessor.java:38)
at
org.apache.abdera.protocol.server.impl.AbstractProvider.process(AbstractProvider.java:136)
at
org.apache.abdera.protocol.server.FilterChain.next(FilterChain.java:42)
at
org.apache.abdera.protocol.server.servlet.AbderaServlet.service(AbderaServlet.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
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:802)
at
org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:135)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
o

Re: [Carbon-dev] -Dsetup is not working

2010-02-25 Thread Krishantha Samaraweera 
On Thu, Feb 25, 2010 at 11:57 PM, Senaka Fernando  wrote:
> Hi Krishantha,
>
> This works at times and don't at times isn't it? Its not an issue with
> -Dsetup, but an issue in the way in how we place the jars on the
classpath.
> If it doesn't work, it shouldn't work at all.

Yes for alpha1, but with alpha2 it failed to load the driver jar at first
time. I haven't played much with alpha2, so I cannot tell it doesn't work at
all.

Thanks,
Krishantha.

>
> Sameera, what is the correct answer regarding where to place these driver
> jars?
>
> Thanks,
> Senaka.
>
> On Thu, Feb 25, 2010 at 10:59 PM, Krishantha Samaraweera
>  wrote:
>>
>> the same Issue seems to be there in Alpha2 build. I tried to start the
>> server with oracle and got the same error. Placing driver jars at
>> /lib/endorsed doesn't work either.
>>
>> Thanks,
>> Krishantha.
>>
>> On Wed, Feb 24, 2010 at 3:04 PM, Charitha Kankanamge 
>> wrote:
>> > Apparently this seems to be an issue with loading jars placed at
>> > repository/components/lib directory. When I copied the driver to
>> > lib/endorsed, I was able to connect to registry DB.
>> > Please have a look.
>> >
>> > Regards
>> > Charitha
>> >
>> > Charitha Kankanamge
>> > WSO2 Inc.
>> > http://wso2.org
>> > email: chari...@wso2.com
>> > cell: +94 718 359 265
>> > blog: http://charithaka.blogspot.com
>> >
>> >
>> > On Wed, Feb 24, 2010 at 2:59 PM, Charitha Kankanamge 
>> > wrote:
>> >>
>> >> I cannot connect to registry DB even after setting up DB using
>> >> mysql.sql
>> >> script. I always get "Cannot load JDBC driver class
>> >> 'com.mysql.jdbc.Driver'
>> >> " error at the server startup. mysql driver
>> >> (mysql-connector-java-5.1.7-bin.jar) was placed at
>> >> repository/components/lib.
>> >>
>> >> ERROR -  Cannot start User Manager Core bundle
>> >> org.wso2.carbon.user.core.UserStoreException: Database Error - Cannot
>> >> load
>> >> JDBC driver class 'com.mysql.jdbc.Driver'
>> >> at
>> >>
>> >>
org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:151)
>> >> at
>> >>
>> >>
org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:132)
>> >> at
>> >>
>> >>
org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:94)
>> >> at
>> >>
>> >>
org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:34)
>> >> at
>> >>
>> >>
org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:50)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
>> >> at java.security.AccessController.doPrivileged(Native Method)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>> >> at
>> >>
>> >>
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
>> >> Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot load
JDBC
>> >> driver class 'com.mysql.jdbc.Driver'
>> >> at
>> >>
>> >>
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1136)
>> >> at
>> >>
>> >>
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
>> >> at
>> >>
>> >>
org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:141)
>> >> ... 17 more
>> >> Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
>> >> at
>> >>
>> >>
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
>> >> at
>> >>
>> >>
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
>> >> at
>> >>
>> >>
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
>> >> at
>> >>
>> >>
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
>> >> at java.lang.ClassLoader.loadClass(C

Re: [Carbon-dev] Errors with latest build of BAM (Dashboard/Unable to handle new service addition.)

2010-02-25 Thread Ruwan Janapriya 
Thanks guys, the fix worked. Now, I don't get all those exceptions.

regards,

Janapriya

On Thu, Feb 25, 2010 at 5:35 PM, Nuwan Bandara  wrote:

> Hi Guys,
>
> I have made the necessary changes in the shindig and dashboard features as
> well.
>
> please take and up of
>
> [1] carbon/orbit/
> [2] online build orbit/google-collect
> [3] build orbit/shindig
> [4] take an svn up of carbon/features/dashboard and build it.
> [5] build BAM and test it.
>
> lets hope all will work fine (I test it with GS and the new changes applied
> without an issue)
>
> Thanks and regards
>  /Nuwan
>
>
> On Thu, Feb 25, 2010 at 3:38 PM, Anjana Fernando  wrote:
>
>> Hello,
>>
>> I've upgraded the google-collections version to 1.0. The new version
>> of the google-collect orbit bundle is '1.0.0.wso2v2'. The usages of
>> the bundle are also changed accordingly.
>>
>> Cheers,
>> Anjana.
>>
>> On Thu, Feb 25, 2010 at 1:31 PM, Nuwan Bandara  wrote:
>> > This seems to be an error produced when we have two versions of
>> > google-collections, So far we got this for bam (Since they use Data
>> Services
>> > and Shindig both). we will update the orbit google-collections bundle to
>> the
>> > latest version and test this issue.
>> >
>> > Regards
>> > /Nuwan
>> >
>> > On Thu, Feb 25, 2010 at 12:47 PM, Ruwan Janapriya 
>> > wrote:
>> >>
>> >> Hi Nuwan,
>> >> Please see inline comments.
>> >>>
>> >>> Seems its not a dashboard related issue. Seems One of the resources
>> you
>> >>> are trying to access in not in the registry. (Resource does not exist
>> at
>> >>> path
>> >>>
>> /_system/config/repository/axis2/service-groups/echo/services/echo/operations/echo).
>> >>
>> >> Yup this is not dashboard related. This issue is fixed with the fix
>> >> provided by Lahiru.
>> >>
>> >>>
>> >>> btw. The tab 0 error can also come, if your request url contains a
>> param
>> >>> called name= this should be compatible with the registry
>> >>> resource name. i.e : /_system/config/repository/dashboards/bam then
>> the name
>> >>> should be "bam". if this is not in place the error can occur.
>> >>
>> >> Now the issue is reduced to show correct Tabs. However gadgets are
>> >> missing. Please note earlier and now the url contained the "name=bam"
>> >> correctly.
>> >> I am still getting the error (related to
>> >> shindig) http://pastebin.com/S1ENjMXm just after server start.
>> >>
>> >> regards,
>> >> Janapriya.
>> >>>
>> >>> Regards
>> >>> /Nuwan
>> >>>
>> >>> On Thu, Feb 25, 2010 at 12:18 PM, Lahiru Gunathilake > >
>> >>> wrote:
>> 
>>  Fixed ! Please update core. (registry.core and carbon.utils).
>>  Lahiru
>> 
>>  On Thu, Feb 25, 2010 at 12:05 PM, Ruwan Janapriya <
>> janapr...@wso2.com>
>>  wrote:
>> >
>> > During startup of the latest build[1] I get the following[2] errors.
>> > There are errors related to Dashboard as well. Once logged in, the
>> > dashboard doesn't show BAM related tabs and gadgets. Shows the
>> loading
>> > screen with the tab - "Tab 0"
>> > regards,
>> > Janapriya.
>> >
>> > [1]
>> http://builder.wso2.org/~carbon/releases/carbon/3.0.0/Thu%20Feb%2025%2005:09:18%20UTC%202010/
>> > [2] http://pastebin.com/yn6uKhKj
>> > --
>> > Ruwan Janapriya
>> > Technical Lead - WSO2 Inc.
>> >
>> > http://wso2.com/ - "lean . enterprise . middleware"
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >
>> 
>> 
>> 
>>  --
>>  Lahiru Gunathilake
>>  Software Engineer - WSO2 Inc.
>> 
>>  ___
>>  Carbon-dev mailing list
>>  Carbon-dev@wso2.org
>>  https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> 
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Nuwan Bandara
>> >>> WSO2 Inc. | http://www.wso2.com
>> >>> email: nu...@wso2.com
>> >>> mob: +94 772 907 484
>> >>> blog: http://www.nuwanbando.com
>> >>>
>> >>> ___
>> >>> Carbon-dev mailing list
>> >>> Carbon-dev@wso2.org
>> >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Ruwan Janapriya
>> >> Technical Lead - WSO2 Inc.
>> >>
>> >> http://wso2.com/ - "lean . enterprise . middleware"
>> >>
>> >> ___
>> >> Carbon-dev mailing list
>> >> Carbon-dev@wso2.org
>> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Nuwan Bandara
>> > WSO2 Inc. | http://www.wso2.com
>> > email: nu...@wso2.com
>> > mob: +94 772 907 484
>> > blog: http://www.nuwanbando.com
>> >
>> > ___
>> > Carbon-dev mailing list
>> > Carbon-dev@wso2.org
>> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-d

[Carbon-dev] -DosgiConsole ?

2010-02-25 Thread Ruwan Janapriya 
Hi All,

I've tried to get the osgi console with *wso2server.bat -DosgiConsole*

But I am *not* getting the prompt. I tried pressing enter too. Encountered
this on BAM.

regards,

-- 
Ruwan Janapriya
Technical Lead - WSO2 Inc.

http://wso2.com/ - "lean . enterprise . middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Senaka Fernando 
I wonder whether the changes made by Sumedha went into alpha2. Anyway, the
results don't seem very informative to understand what actually happened.
Can you do the same tests on H2 and paste any issues you see.

Thanks,
Senaka.

On Thu, Feb 25, 2010 at 11:16 PM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Since it will take time to setup perf tests with embedded registry,
> APP based perf tests have been executed with alpha2 build using
> Oracle. Following dead lock situation occurred just after starting the
> worker1 class with 500 iterations and 20 concurrent users. Please
> refer to [1] detail error log.
>
> [2010-02-25 22:39:25,171] ERROR -  A SQLException error has occurred
> when trying to close result set or prepared statement
> java.sql.SQLException: ORA-00060: deadlock detected while waiting for
> resource
>
>at
> oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
>at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
>at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
>at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
>at
> oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
>at
> oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
>at
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
>at
> oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
>at
> oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
> at
> org.wso2.carbon.registry.core.jdbc.dao.ResourceDAO.deleteContentStream(ResourceDAO.java:658)
>at
> org.wso2.carbon.registry.core.jdbc.dao.ResourceVersionDAO.versionResource(ResourceVersionDAO.java:1052)
>at
> org.wso2.carbon.registry.core.jdbc.VersionRepository.createVersionForResource(VersionRepository.java:191)
>at
> org.wso2.carbon.registry.core.jdbc.VersionRepository.createSnapshot(VersionRepository.java:77)
>at
> org.wso2.carbon.registry.core.jdbc.Repository.deleteSubTree(Repository.java:471)
> at
> org.wso2.carbon.registry.core.jdbc.Repository.delete(Repository.java:403)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.delete(EmbeddedRegistry.java:805)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.delete(UserRegistry.java:625)
> at
> org.wso2.carbon.registry.app.RegistryAdapter.processDeleteRequest(RegistryAdapter.java:602)
>at
> org.wso2.carbon.registry.app.RegistryAdapter.extensionRequest(RegistryAdapter.java:124)
>at
> org.apache.abdera.protocol.server.impl.AbstractProvider.processExtensionRequest(AbstractProvider.java:196)
>at
> org.apache.abdera.protocol.server.impl.AbstractProvider.process(AbstractProvider.java:137)
>at
> org.apache.abdera.protocol.server.FilterChain.next(FilterChain.java:42)
>at
> org.apache.abdera.protocol.server.servlet.AbderaServlet.service(AbderaServlet.java:90)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>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:802)
>at
> org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:135)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
>at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
>at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
>at
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>at
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>at
> org.apache.tomcat.util.net.LeaderFoll

Re: [Carbon-dev] -Dsetup is not working

2010-02-25 Thread Samisa Abeysinghe 
On Thu, Feb 25, 2010 at 11:57 PM, Senaka Fernando  wrote:

> Hi Krishantha,
>
> This works at times and don't at times isn't it? Its not an issue with
> -Dsetup, but an issue in the way in how we place the jars on the classpath.


hmmm. This sounds like a serious bug to me.

Please try to get to the bottom of the problem soon.

Samisa...



> If it doesn't work, it shouldn't work at all.
>
> Sameera, what is the correct answer regarding where to place these driver
> jars?
>
> Thanks,
> Senaka.
>
>
> On Thu, Feb 25, 2010 at 10:59 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> the same Issue seems to be there in Alpha2 build. I tried to start the
>> server with oracle and got the same error. Placing driver jars at
>> /lib/endorsed doesn't work either.
>>
>> Thanks,
>> Krishantha.
>>
>> On Wed, Feb 24, 2010 at 3:04 PM, Charitha Kankanamge 
>> wrote:
>> > Apparently this seems to be an issue with loading jars placed at
>> > repository/components/lib directory. When I copied the driver to
>> > lib/endorsed, I was able to connect to registry DB.
>> > Please have a look.
>> >
>> > Regards
>> > Charitha
>> >
>> > Charitha Kankanamge
>> > WSO2 Inc.
>> > http://wso2.org
>> > email: chari...@wso2.com
>> > cell: +94 718 359 265
>> > blog: http://charithaka.blogspot.com
>> >
>> >
>> > On Wed, Feb 24, 2010 at 2:59 PM, Charitha Kankanamge > >
>> > wrote:
>> >>
>> >> I cannot connect to registry DB even after setting up DB using
>> mysql.sql
>> >> script. I always get "Cannot load JDBC driver class
>> 'com.mysql.jdbc.Driver'
>> >> " error at the server startup. mysql driver
>> >> (mysql-connector-java-5.1.7-bin.jar) was placed at
>> >> repository/components/lib.
>> >>
>> >> ERROR -  Cannot start User Manager Core bundle
>> >> org.wso2.carbon.user.core.UserStoreException: Database Error - Cannot
>> load
>> >> JDBC driver class 'com.mysql.jdbc.Driver'
>> >> at
>> >>
>> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:151)
>> >> at
>> >>
>> org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(DefaultRealmService.java:132)
>> >> at
>> >>
>> org.wso2.carbon.user.core.common.DefaultRealmService.(DefaultRealmService.java:94)
>> >> at
>> >>
>> org.wso2.carbon.user.core.internal.Activator.startDeploy(Activator.java:34)
>> >> at
>> >>
>> org.wso2.carbon.user.core.internal.BundleCheckActivator.start(BundleCheckActivator.java:50)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
>> >> at java.security.AccessController.doPrivileged(Native Method)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
>> >> at
>> >>
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
>> >> at
>> >>
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>> >> at
>> >>
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)
>> >> Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot load JDBC
>> >> driver class 'com.mysql.jdbc.Driver'
>> >> at
>> >>
>> org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1136)
>> >> at
>> >>
>> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
>> >> at
>> >>
>> org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount(ClaimDAO.java:141)
>> >> ... 17 more
>> >> Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
>> >> at
>> >>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
>> >> at
>> >>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
>> >> at
>> >>
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
>> >> at
>> >>
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
>> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>> >> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
>> >> at java.lang.

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Amila Suriarachchi 
On Wed, Feb 24, 2010 at 12:03 PM, Sumedha Rubasinghe wrote:

>
> On Wed, Feb 24, 2010 at 11:57 AM, Ruwan Linton  wrote:
>
>> Senaka Fernando wrote:
>> > This could be due to overlapping transactions in this particular
>> > component that attempts to write to the registry at once.
>> So does this mean that Registry cannot handle concurrent connections to
>> a particular registry resource/collection? Well, even in that case it
>> shouldn't deadlock :-(
>>
>
> If an insert (write) happens the database locks the table allowing only
> read. So the only option available for us is to speed up write operation.
> working on it..
>

hi Sumedha,

What is the transaction isolation level you use for these transactions?

Amila.

>
> /sumedha
>
>
>> Thanks,
>> Ruwan
>> >
>> > Thanks,
>> > Senaka.
>> >
>> > On Wed, Feb 24, 2010 at 11:28 AM, Hiranya Jayathilaka
>> > mailto:hira...@wso2.com>> wrote:
>> >
>> > Following exception encountered in the ESB while updating a proxy
>> > service:
>> >
>> >
>> > Exception in thread "Thread-23"
>> >
>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>> > Error while saving mediation configuration changes
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.handleException(MediationPersistenceManager.java:278)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1200(MediationPersistenceManager.java:48)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:320)
>> > Caused by:
>> >
>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>> > Unable to persist the proxy service in the path :
>> > /repository/synapse/proxy-services/FooProxy
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.handleException(AbstractRegistryStore.java:101)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:72)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.saveToRegistry(AbstractStore.java:154)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.save(AbstractStore.java:82)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:335)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1000(MediationPersistenceManager.java:48)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:314)
>> > Caused by:
>> > org.wso2.carbon.registry.core.exceptions.RegistryException: Unable
>> > to persist element
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.persistElement(AbstractRegistryStore.java:95)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:69)
>> > ... 5 more
>> > Caused by:
>> > org.wso2.carbon.registry.core.exceptions.RegistryException: Failed
>> > to add log entry for resource
>> > /_system/config/repository/synapse/proxy-services. Deadlock
>> > detected. The current transaction was rolled back. Details:
>> > Session #9 (user: WSO2CARBON) is waiting to lock
>> > PUBLIC.REG_RESOURCE while locking PUBLIC.REG_ASSOCIATION
>> > (exclusive), PUBLIC.REG_LOG (exclusive).
>> > Session #12 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_LOG
>> > while locking PUBLIC.REG_CONTENT_HISTORY (exclusive),
>> > PUBLIC.REG_RESOURCE_HISTORY (exclusive), PUBLIC.REG_RESOURCE
>> > (exclusive), PUBLIC.REG_CONTENT (exclusive), PUBLIC.REG_SNAPSHOT
>> > (exclusive).; SQL statement:
>> > INSERT INTO REG_LOG (REG_PATH, REG_USER_ID, REG_LOGGED_TIME,
>> > REG_ACTION, REG_ACTION_DATA, REG_TENANT_ID) VALUES (?, ?, ?, ?, ?,
>> > ?) [40001-112]
>> > at
>> >
>> org.wso2.carbon.registry.core.jdbc.dao.LogsDAO.addLog(LogsDAO.java:79)
>> > at
>> >
>> org.wso2.carbon.registry.core.jdbc.Repository.update(Repository.java:966)
>> > at
>> >
>> org.wso2.carbon.registry.core.jdbc.Repository.updateParent(Repository.java:947)
>> > at
>> >
>> org.wso2.carbon.registry.core.jdbc.Repository.delete(Repository.java:403)
>> > at
>> >
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.delete(EmbeddedRegistry.java:807)
>> > at
>> >
>> org.wso2.carbon.registry.core.session.UserRegistry.delete(UserRegistry.java:625)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.persistElement(AbstractRegistryStore.java:79

Re: [Carbon-dev] Carbon 3.0.0 - Iridium - Alpha2 builds

2010-02-25 Thread Yumani Ranaweera 
Hi,

There are errors in Is startup. Please see the attached log.txt.

Thanks,
Yumani



On Thu, Feb 25, 2010 at 6:03 PM, Samisa Abeysinghe  wrote:

> Available here:
> http://builder.wso2.org/~carbon/releases/carbon/3.0.0/1Alpha2/
>
> These
> packs are provided as is.
> Please do a smoke test.
>
> Samisa...
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Yumani Ranaweera
WSO2, Inc. - http://wso2.org
Email : yum...@wso2.com
Cell: +94 077 7795242
Blog   : http://yumani.blogspot.com/
[2010-02-26 08:08:18,953] ERROR -  errorInChangingSecurityConfiguration
java.lang.NullPointerException
at java.util.Arrays.sort(Arrays.java:1078)
at edu.emory.mathcs.backport.java.util.Arrays.sort(Arrays.java:76)
at 
org.wso2.carbon.security.config.SecurityConfigAdmin.applySecurity(SecurityConfigAdmin.java:328)
at 
org.wso2.carbon.identity.sts.mgt.admin.STSConfigAdmin.configureService(STSConfigAdmin.java:165)
at 
org.wso2.carbon.identity.sts.mgt.internal.IdentitySTSMgtServiceComponent.initialize(IdentitySTSMgtServiceComponent.java:215)
at 
org.wso2.carbon.identity.sts.mgt.internal.IdentitySTSMgtServiceComponent.activate(IdentitySTSMgtServiceComponent.java:94)
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:230)
at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
at 
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
at 
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
at 
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:930)
at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
at 
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:757)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:712)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:129)
at 
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:206)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:506)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:524)
at 
org.wso2.carbon.identity.provider.internal.IdentityProviderServiceComponent.activate(IdentityProviderServiceComponent.java:81)
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:230)
at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:140)
at 
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:330)
at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:560)
at 
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:182)
at 
org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:292)
at 
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:226)
at 
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:124)
at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatc

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Dimuthu Gamage 
On Fri, Feb 26, 2010 at 7:50 AM, Amila Suriarachchi  wrote:

>
>
> On Wed, Feb 24, 2010 at 12:03 PM, Sumedha Rubasinghe wrote:
>
>>
>> On Wed, Feb 24, 2010 at 11:57 AM, Ruwan Linton  wrote:
>>
>>> Senaka Fernando wrote:
>>> > This could be due to overlapping transactions in this particular
>>> > component that attempts to write to the registry at once.
>>> So does this mean that Registry cannot handle concurrent connections to
>>> a particular registry resource/collection? Well, even in that case it
>>> shouldn't deadlock :-(
>>>
>>
>> If an insert (write) happens the database locks the table allowing only
>> read. So the only option available for us is to speed up write operation.
>> working on it..
>>
>
> hi Sumedha,
>
> What is the transaction isolation level you use for these transactions?
>

It is read committed.
Thanks
Dimuthu

>
> Amila.
>
>>
>> /sumedha
>>
>>
>>> Thanks,
>>> Ruwan
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >
>>> > On Wed, Feb 24, 2010 at 11:28 AM, Hiranya Jayathilaka
>>> > mailto:hira...@wso2.com>> wrote:
>>> >
>>> > Following exception encountered in the ESB while updating a proxy
>>> > service:
>>> >
>>> >
>>> > Exception in thread "Thread-23"
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>>> > Error while saving mediation configuration changes
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.handleException(MediationPersistenceManager.java:278)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1200(MediationPersistenceManager.java:48)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:320)
>>> > Caused by:
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>>> > Unable to persist the proxy service in the path :
>>> > /repository/synapse/proxy-services/FooProxy
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.handleException(AbstractRegistryStore.java:101)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:72)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.saveToRegistry(AbstractStore.java:154)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.save(AbstractStore.java:82)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:335)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1000(MediationPersistenceManager.java:48)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:314)
>>> > Caused by:
>>> > org.wso2.carbon.registry.core.exceptions.RegistryException: Unable
>>> > to persist element
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.persistElement(AbstractRegistryStore.java:95)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:69)
>>> > ... 5 more
>>> > Caused by:
>>> > org.wso2.carbon.registry.core.exceptions.RegistryException: Failed
>>> > to add log entry for resource
>>> > /_system/config/repository/synapse/proxy-services. Deadlock
>>> > detected. The current transaction was rolled back. Details:
>>> > Session #9 (user: WSO2CARBON) is waiting to lock
>>> > PUBLIC.REG_RESOURCE while locking PUBLIC.REG_ASSOCIATION
>>> > (exclusive), PUBLIC.REG_LOG (exclusive).
>>> > Session #12 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_LOG
>>> > while locking PUBLIC.REG_CONTENT_HISTORY (exclusive),
>>> > PUBLIC.REG_RESOURCE_HISTORY (exclusive), PUBLIC.REG_RESOURCE
>>> > (exclusive), PUBLIC.REG_CONTENT (exclusive), PUBLIC.REG_SNAPSHOT
>>> > (exclusive).; SQL statement:
>>> > INSERT INTO REG_LOG (REG_PATH, REG_USER_ID, REG_LOGGED_TIME,
>>> > REG_ACTION, REG_ACTION_DATA, REG_TENANT_ID) VALUES (?, ?, ?, ?, ?,
>>> > ?) [40001-112]
>>> > at
>>> >
>>> org.wso2.carbon.registry.core.jdbc.dao.LogsDAO.addLog(LogsDAO.java:79)
>>> > at
>>> >
>>> org.wso2.carbon.registry.core.jdbc.Repository.update(Repository.java:966)
>>> > at
>>> >
>>> org.wso2.carbon.registry.core.jdbc.Repository.updateParent(Repository.java:947)
>>> > at
>>> >
>>> org.wso2.carbon.registry.core.jdbc.Repository.delete(Repository.java:403)
>>> > at
>>> >
>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.delete(EmbeddedRegistry.java:807)
>>> > at
>>

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Amila Suriarachchi 
On Fri, Feb 26, 2010 at 8:21 AM, Dimuthu Gamage  wrote:

>
>
> On Fri, Feb 26, 2010 at 7:50 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Wed, Feb 24, 2010 at 12:03 PM, Sumedha Rubasinghe wrote:
>>
>>>
>>> On Wed, Feb 24, 2010 at 11:57 AM, Ruwan Linton  wrote:
>>>
 Senaka Fernando wrote:
 > This could be due to overlapping transactions in this particular
 > component that attempts to write to the registry at once.
 So does this mean that Registry cannot handle concurrent connections to
 a particular registry resource/collection? Well, even in that case it
 shouldn't deadlock :-(

>>>
>>> If an insert (write) happens the database locks the table allowing only
>>> read. So the only option available for us is to speed up write operation.
>>> working on it..
>>>
>>
>> hi Sumedha,
>>
>> What is the transaction isolation level you use for these transactions?
>>
>
> It is read committed.
>
Do you know why this deadlocks occur?. At this isolation level transactions
do not have to lock the tables isn't it?

Amila.


> Thanks
> Dimuthu
>
>>
>> Amila.
>>
>>>
>>> /sumedha
>>>
>>>
 Thanks,
 Ruwan
 >
 > Thanks,
 > Senaka.
 >
 > On Wed, Feb 24, 2010 at 11:28 AM, Hiranya Jayathilaka
 > mailto:hira...@wso2.com>> wrote:
 >
 > Following exception encountered in the ESB while updating a proxy
 > service:
 >
 >
 > Exception in thread "Thread-23"
 >
 org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
 > Error while saving mediation configuration changes
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.handleException(MediationPersistenceManager.java:278)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1200(MediationPersistenceManager.java:48)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:320)
 > Caused by:
 >
 org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
 > Unable to persist the proxy service in the path :
 > /repository/synapse/proxy-services/FooProxy
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.handleException(AbstractRegistryStore.java:101)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:72)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.AbstractStore.saveToRegistry(AbstractStore.java:154)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.AbstractStore.save(AbstractStore.java:82)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:335)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1000(MediationPersistenceManager.java:48)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:314)
 > Caused by:
 > org.wso2.carbon.registry.core.exceptions.RegistryException: Unable
 > to persist element
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.persistElement(AbstractRegistryStore.java:95)
 > at
 >
 org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:69)
 > ... 5 more
 > Caused by:
 > org.wso2.carbon.registry.core.exceptions.RegistryException: Failed
 > to add log entry for resource
 > /_system/config/repository/synapse/proxy-services. Deadlock
 > detected. The current transaction was rolled back. Details:
 > Session #9 (user: WSO2CARBON) is waiting to lock
 > PUBLIC.REG_RESOURCE while locking PUBLIC.REG_ASSOCIATION
 > (exclusive), PUBLIC.REG_LOG (exclusive).
 > Session #12 (user: WSO2CARBON) is waiting to lock PUBLIC.REG_LOG
 > while locking PUBLIC.REG_CONTENT_HISTORY (exclusive),
 > PUBLIC.REG_RESOURCE_HISTORY (exclusive), PUBLIC.REG_RESOURCE
 > (exclusive), PUBLIC.REG_CONTENT (exclusive), PUBLIC.REG_SNAPSHOT
 > (exclusive).; SQL statement:
 > INSERT INTO REG_LOG (REG_PATH, REG_USER_ID, REG_LOGGED_TIME,
 > REG_ACTION, REG_ACTION_DATA, REG_TENANT_ID) VALUES (?, ?, ?, ?, ?,
 > ?) [40001-112]
 > at
 >
 org.wso2.carbon.registry.core.jdbc.dao.LogsDAO.addLog(LogsDAO.java:79)
 > at
 >
 org.wso2.carbon.registry.core.jdbc.Repository.update(Repository.java:966)
 >

[Carbon-dev] summary data generating problem ?

2010-02-25 Thread Ajith Vitharana 
Hi dumindu ,


service data and mediation data reports are generating with the latest BAM
build.
but summary data does not contain in bam_db  to view the analytics reports.

Thanks
ajithn
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Dimuthu Gamage 
Hi,

I think What 'READ_COMMITED' do is, in a case of doing reading, it will
continue reading the commited data from the tables locked by others. So I
think what 'READ_COMMITED' guarantee is , if all the operation are 'READ'
then it will not dead lock. But Apparently we are doing some 'WRITE'
operations in that test case. so deadlocks are possible.

I'm trying to list the sequence of database accesses for simple GET, PUT,
DELETE registry operations at here[1]. So we can identify which operation
can cause the deadlocks.

Thanks
Dimuthu

[1]
https://spreadsheets.google.com/a/wso2.com/ccc?key=tX5iHIbwTIDDuyF8uwsERiw&hl=en

On Fri, Feb 26, 2010 at 9:14 AM, Amila Suriarachchi  wrote:

>
>
> On Fri, Feb 26, 2010 at 8:21 AM, Dimuthu Gamage  wrote:
>
>>
>>
>> On Fri, Feb 26, 2010 at 7:50 AM, Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Wed, Feb 24, 2010 at 12:03 PM, Sumedha Rubasinghe 
>>> wrote:
>>>

 On Wed, Feb 24, 2010 at 11:57 AM, Ruwan Linton  wrote:

> Senaka Fernando wrote:
> > This could be due to overlapping transactions in this particular
> > component that attempts to write to the registry at once.
> So does this mean that Registry cannot handle concurrent connections to
> a particular registry resource/collection? Well, even in that case it
> shouldn't deadlock :-(
>

 If an insert (write) happens the database locks the table allowing only
 read. So the only option available for us is to speed up write operation.
 working on it..

>>>
>>> hi Sumedha,
>>>
>>> What is the transaction isolation level you use for these transactions?
>>>
>>
>> It is read committed.
>>
> Do you know why this deadlocks occur?. At this isolation level transactions
> do not have to lock the tables isn't it?
>
> Amila.
>
>
>> Thanks
>> Dimuthu
>>
>>>
>>> Amila.
>>>

 /sumedha


> Thanks,
> Ruwan
> >
> > Thanks,
> > Senaka.
> >
> > On Wed, Feb 24, 2010 at 11:28 AM, Hiranya Jayathilaka
> > mailto:hira...@wso2.com>> wrote:
> >
> > Following exception encountered in the ESB while updating a proxy
> > service:
> >
> >
> > Exception in thread "Thread-23"
> >
> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
> > Error while saving mediation configuration changes
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.handleException(MediationPersistenceManager.java:278)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1200(MediationPersistenceManager.java:48)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:320)
> > Caused by:
> >
> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
> > Unable to persist the proxy service in the path :
> > /repository/synapse/proxy-services/FooProxy
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.handleException(AbstractRegistryStore.java:101)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:72)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.saveToRegistry(AbstractStore.java:154)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.save(AbstractStore.java:82)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:335)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1000(MediationPersistenceManager.java:48)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:314)
> > Caused by:
> > org.wso2.carbon.registry.core.exceptions.RegistryException:
> Unable
> > to persist element
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.persistElement(AbstractRegistryStore.java:95)
> > at
> >
> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:69)
> > ... 5 more
> > Caused by:
> > org.wso2.carbon.registry.core.exceptions.RegistryException:
> Failed
> > to add log entry for resource
> > /_system/config/repository/synapse/proxy-services. Deadlock
> > detected. The current transaction was rolled back. Details:
> > Session #9 (user: WSO2CARBON) is waiting to lock

Re: [Carbon-dev] Carbon 3.0.0 - Iridium - Alpha2 builds

2010-02-25 Thread Thilina Mahesh Buddhika 
On Fri, Feb 26, 2010 at 8:18 AM, Yumani Ranaweera  wrote:

> Hi,
>
> There are errors in Is startup. Please see the attached log.txt.
>


Will look into this.

Thanks.
/thilina


>
> Thanks,
> Yumani
>
>
>
> On Thu, Feb 25, 2010 at 6:03 PM, Samisa Abeysinghe wrote:
>
>> Available here:
>> http://builder.wso2.org/~carbon/releases/carbon/3.0.0/1Alpha2/
>>
>> These
>> packs are provided as is.
>> Please do a smoke test.
>>
>> Samisa...
>>
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Yumani Ranaweera
>
> WSO2, Inc. - http://wso2.org
> Email : yum...@wso2.com
> Cell: +94 077 7795242
> Blog   : http://yumani.blogspot.com/
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Thilina Mahesh Buddhika
WSO2 Inc. ; http://wso2.com
http://blog.thilinamb.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Senaka Fernando 
Hi Dimuthu,

On Fri, Feb 26, 2010 at 9:38 AM, Dimuthu Gamage  wrote:

> Hi,
>
> I think What 'READ_COMMITED' do is, in a case of doing reading, it will
> continue reading the commited data from the tables locked by others. So I
> think what 'READ_COMMITED' guarantee is , if all the operation are 'READ'
> then it will not dead lock. But Apparently we are doing some 'WRITE'
> operations in that test case. so deadlocks are possible.
>
> I'm trying to list the sequence of database accesses for simple GET, PUT,
> DELETE registry operations at here[1]. So we can identify which operation
> can cause the deadlocks.
>

Since we support transactions spanning across multiple operations, this
could be theoretically any N number of operations. What we should be doing
here, is defining a protocol to handle situations causing a deadlock. This
shouldn't result in a performance overhead if this is properly designed and
well written. Also, the benefits are that we will not be loosing
transactions, by means of a retrying logic.

Thanks,
Senaka.

>
> Thanks
> Dimuthu
>
> [1]
> https://spreadsheets.google.com/a/wso2.com/ccc?key=tX5iHIbwTIDDuyF8uwsERiw&hl=en
>
>
> On Fri, Feb 26, 2010 at 9:14 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Fri, Feb 26, 2010 at 8:21 AM, Dimuthu Gamage  wrote:
>>
>>>
>>>
>>> On Fri, Feb 26, 2010 at 7:50 AM, Amila Suriarachchi wrote:
>>>


 On Wed, Feb 24, 2010 at 12:03 PM, Sumedha Rubasinghe 
 wrote:

>
> On Wed, Feb 24, 2010 at 11:57 AM, Ruwan Linton  wrote:
>
>> Senaka Fernando wrote:
>> > This could be due to overlapping transactions in this particular
>> > component that attempts to write to the registry at once.
>> So does this mean that Registry cannot handle concurrent connections
>> to
>> a particular registry resource/collection? Well, even in that case it
>> shouldn't deadlock :-(
>>
>
> If an insert (write) happens the database locks the table allowing only
> read. So the only option available for us is to speed up write operation.
> working on it..
>

 hi Sumedha,

 What is the transaction isolation level you use for these transactions?

>>>
>>> It is read committed.
>>>
>> Do you know why this deadlocks occur?. At this isolation level
>> transactions do not have to lock the tables isn't it?
>>
>> Amila.
>>
>>
>>> Thanks
>>> Dimuthu
>>>

 Amila.

>
> /sumedha
>
>
>> Thanks,
>> Ruwan
>> >
>> > Thanks,
>> > Senaka.
>> >
>> > On Wed, Feb 24, 2010 at 11:28 AM, Hiranya Jayathilaka
>> > mailto:hira...@wso2.com>> wrote:
>> >
>> > Following exception encountered in the ESB while updating a
>> proxy
>> > service:
>> >
>> >
>> > Exception in thread "Thread-23"
>> >
>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>> > Error while saving mediation configuration changes
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.handleException(MediationPersistenceManager.java:278)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1200(MediationPersistenceManager.java:48)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:320)
>> > Caused by:
>> >
>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>> > Unable to persist the proxy service in the path :
>> > /repository/synapse/proxy-services/FooProxy
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.handleException(AbstractRegistryStore.java:101)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:72)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.saveToRegistry(AbstractStore.java:154)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.save(AbstractStore.java:82)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:335)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1000(MediationPersistenceManager.java:48)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:314)
>> > Caused by:
>> > org.wso2.carbon.registry.core.exceptions.RegistryException:
>> Unable
>> > to persist element
>> > at
>> >
>> org.wso2.ca

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Dimuthu Gamage 
On Fri, Feb 26, 2010 at 9:52 AM, Senaka Fernando  wrote:

> Hi Dimuthu,
>
> On Fri, Feb 26, 2010 at 9:38 AM, Dimuthu Gamage  wrote:
>
>> Hi,
>>
>> I think What 'READ_COMMITED' do is, in a case of doing reading, it will
>> continue reading the commited data from the tables locked by others. So I
>> think what 'READ_COMMITED' guarantee is , if all the operation are 'READ'
>> then it will not dead lock. But Apparently we are doing some 'WRITE'
>> operations in that test case. so deadlocks are possible.
>>
>> I'm trying to list the sequence of database accesses for simple GET, PUT,
>> DELETE registry operations at here[1]. So we can identify which operation
>> can cause the deadlocks.
>>
>
> Since we support transactions spanning across multiple operations, this
> could be theoretically any N number of operations. What we should be doing
> here, is defining a protocol to handle situations causing a deadlock. This
> shouldn't result in a performance overhead if this is properly designed and
> well written. Also, the benefits are that we will not be loosing
> transactions, by means of a retrying logic.
>

+1. If we can guarantee for all the atomic registry operations the
frequently accessed tables like REG_RESOURCE, REG_CONTENT and probably
REG_RESOURCE_HISTORY and REG_CONTENT_HISTORY are writing in the same order
we will be able to guarantee the deadlocks happens minimum even combining
many registry operations. So we will start with that.

Thanks
Dimuthu

>
> Thanks,
> Senaka.
>
>>
>> Thanks
>> Dimuthu
>>
>> [1]
>> https://spreadsheets.google.com/a/wso2.com/ccc?key=tX5iHIbwTIDDuyF8uwsERiw&hl=en
>>
>>
>> On Fri, Feb 26, 2010 at 9:14 AM, Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Fri, Feb 26, 2010 at 8:21 AM, Dimuthu Gamage wrote:
>>>


 On Fri, Feb 26, 2010 at 7:50 AM, Amila Suriarachchi wrote:

>
>
> On Wed, Feb 24, 2010 at 12:03 PM, Sumedha Rubasinghe  > wrote:
>
>>
>> On Wed, Feb 24, 2010 at 11:57 AM, Ruwan Linton wrote:
>>
>>> Senaka Fernando wrote:
>>> > This could be due to overlapping transactions in this particular
>>> > component that attempts to write to the registry at once.
>>> So does this mean that Registry cannot handle concurrent connections
>>> to
>>> a particular registry resource/collection? Well, even in that case it
>>> shouldn't deadlock :-(
>>>
>>
>> If an insert (write) happens the database locks the table allowing
>> only read. So the only option available for us is to speed up write
>> operation. working on it..
>>
>
> hi Sumedha,
>
> What is the transaction isolation level you use for these transactions?
>

 It is read committed.

>>> Do you know why this deadlocks occur?. At this isolation level
>>> transactions do not have to lock the tables isn't it?
>>>
>>> Amila.
>>>
>>>
 Thanks
 Dimuthu

>
> Amila.
>
>>
>> /sumedha
>>
>>
>>> Thanks,
>>> Ruwan
>>> >
>>> > Thanks,
>>> > Senaka.
>>> >
>>> > On Wed, Feb 24, 2010 at 11:28 AM, Hiranya Jayathilaka
>>> > mailto:hira...@wso2.com>> wrote:
>>> >
>>> > Following exception encountered in the ESB while updating a
>>> proxy
>>> > service:
>>> >
>>> >
>>> > Exception in thread "Thread-23"
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>>> > Error while saving mediation configuration changes
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.handleException(MediationPersistenceManager.java:278)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1200(MediationPersistenceManager.java:48)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:320)
>>> > Caused by:
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>>> > Unable to persist the proxy service in the path :
>>> > /repository/synapse/proxy-services/FooProxy
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.handleException(AbstractRegistryStore.java:101)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:72)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.saveToRegistry(AbstractStore.java:154)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.save(AbstractStore.java:82)
>>> > at
>>> >
>>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElemen

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Samisa Abeysinghe 
On Fri, Feb 26, 2010 at 12:03 AM, Senaka Fernando  wrote:

> I wonder whether the changes made by Sumedha went into alpha2.


It did

Samisa...



> Anyway, the results don't seem very informative to understand what actually
> happened. Can you do the same tests on H2 and paste any issues you see.
>
> Thanks,
> Senaka.
>
>
> On Thu, Feb 25, 2010 at 11:16 PM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Since it will take time to setup perf tests with embedded registry,
>> APP based perf tests have been executed with alpha2 build using
>> Oracle. Following dead lock situation occurred just after starting the
>> worker1 class with 500 iterations and 20 concurrent users. Please
>> refer to [1] detail error log.
>>
>> [2010-02-25 22:39:25,171] ERROR -  A SQLException error has occurred
>> when trying to close result set or prepared statement
>> java.sql.SQLException: ORA-00060: deadlock detected while waiting for
>> resource
>>
>>at
>> oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
>>at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
>>at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
>>at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
>>at
>> oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
>>at
>> oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
>>at
>> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
>>at
>> oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
>>at
>> oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
>> at
>> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
>> at
>> org.wso2.carbon.registry.core.jdbc.dao.ResourceDAO.deleteContentStream(ResourceDAO.java:658)
>>at
>> org.wso2.carbon.registry.core.jdbc.dao.ResourceVersionDAO.versionResource(ResourceVersionDAO.java:1052)
>>at
>> org.wso2.carbon.registry.core.jdbc.VersionRepository.createVersionForResource(VersionRepository.java:191)
>>at
>> org.wso2.carbon.registry.core.jdbc.VersionRepository.createSnapshot(VersionRepository.java:77)
>>at
>> org.wso2.carbon.registry.core.jdbc.Repository.deleteSubTree(Repository.java:471)
>> at
>> org.wso2.carbon.registry.core.jdbc.Repository.delete(Repository.java:403)
>> at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.delete(EmbeddedRegistry.java:805)
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.delete(UserRegistry.java:625)
>> at
>> org.wso2.carbon.registry.app.RegistryAdapter.processDeleteRequest(RegistryAdapter.java:602)
>>at
>> org.wso2.carbon.registry.app.RegistryAdapter.extensionRequest(RegistryAdapter.java:124)
>>at
>> org.apache.abdera.protocol.server.impl.AbstractProvider.processExtensionRequest(AbstractProvider.java:196)
>>at
>> org.apache.abdera.protocol.server.impl.AbstractProvider.process(AbstractProvider.java:137)
>>at
>> org.apache.abdera.protocol.server.FilterChain.next(FilterChain.java:42)
>>at
>> org.apache.abdera.protocol.server.servlet.AbderaServlet.service(AbderaServlet.java:90)
>>at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>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:802)
>>at
>> org.wso2.carbon.bridge.BridgeServlet.service(BridgeServlet.java:135)
>>at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>>at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
>>at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>>at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
>>at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>>at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>>at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>>at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
>>at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
>>at
>> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.process

Re: [Carbon-dev] Registry Deadlock Encountered

2010-02-25 Thread Amila Suriarachchi 
On Fri, Feb 26, 2010 at 9:38 AM, Dimuthu Gamage  wrote:

> Hi,
>
> I think What 'READ_COMMITED' do is, in a case of doing reading, it will
> continue reading the commited data from the tables locked by others.

Again the question is why others have to lock. Are they in higher
transaction levels?


> So I think what 'READ_COMMITED' guarantee is , if all the operation are
> 'READ' then it will not dead lock. But Apparently we are doing some 'WRITE'
> operations in that test case. so deadlocks are possible.
>
> I'm trying to list the sequence of database accesses for simple GET, PUT,
> DELETE registry operations at here[1]. So we can identify which operation
> can cause the deadlocks.
>

I think writing a sample app with two threads to check the explanation we
provide may helpful as well. i.e. we
can control the event happening order using some sleeps.

Amila.

>
> Thanks
> Dimuthu
>
> [1]
> https://spreadsheets.google.com/a/wso2.com/ccc?key=tX5iHIbwTIDDuyF8uwsERiw&hl=en
>
>
> On Fri, Feb 26, 2010 at 9:14 AM, Amila Suriarachchi wrote:
>
>>
>>
>> On Fri, Feb 26, 2010 at 8:21 AM, Dimuthu Gamage  wrote:
>>
>>>
>>>
>>> On Fri, Feb 26, 2010 at 7:50 AM, Amila Suriarachchi wrote:
>>>


 On Wed, Feb 24, 2010 at 12:03 PM, Sumedha Rubasinghe 
 wrote:

>
> On Wed, Feb 24, 2010 at 11:57 AM, Ruwan Linton  wrote:
>
>> Senaka Fernando wrote:
>> > This could be due to overlapping transactions in this particular
>> > component that attempts to write to the registry at once.
>> So does this mean that Registry cannot handle concurrent connections
>> to
>> a particular registry resource/collection? Well, even in that case it
>> shouldn't deadlock :-(
>>
>
> If an insert (write) happens the database locks the table allowing only
> read. So the only option available for us is to speed up write operation.
> working on it..
>

 hi Sumedha,

 What is the transaction isolation level you use for these transactions?

>>>
>>> It is read committed.
>>>
>> Do you know why this deadlocks occur?. At this isolation level
>> transactions do not have to lock the tables isn't it?
>>
>> Amila.
>>
>>
>>> Thanks
>>> Dimuthu
>>>

 Amila.

>
> /sumedha
>
>
>> Thanks,
>> Ruwan
>> >
>> > Thanks,
>> > Senaka.
>> >
>> > On Wed, Feb 24, 2010 at 11:28 AM, Hiranya Jayathilaka
>> > mailto:hira...@wso2.com>> wrote:
>> >
>> > Following exception encountered in the ESB while updating a
>> proxy
>> > service:
>> >
>> >
>> > Exception in thread "Thread-23"
>> >
>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>> > Error while saving mediation configuration changes
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.handleException(MediationPersistenceManager.java:278)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1200(MediationPersistenceManager.java:48)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:320)
>> > Caused by:
>> >
>> org.wso2.carbon.mediation.initializer.persistence.ServiceBusPersistenceException:
>> > Unable to persist the proxy service in the path :
>> > /repository/synapse/proxy-services/FooProxy
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.handleException(AbstractRegistryStore.java:101)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.ProxyServiceRegistryStore.persistElement(ProxyServiceRegistryStore.java:72)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.saveToRegistry(AbstractStore.java:154)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.AbstractStore.save(AbstractStore.java:82)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.persistElement(MediationPersistenceManager.java:335)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager.access$1000(MediationPersistenceManager.java:48)
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.MediationPersistenceManager$MediationPersistenceWorker.run(MediationPersistenceManager.java:314)
>> > Caused by:
>> > org.wso2.carbon.registry.core.exceptions.RegistryException:
>> Unable
>> > to persist element
>> > at
>> >
>> org.wso2.carbon.mediation.initializer.persistence.registry.AbstractRegistryStore.persistElement(AbstractRegistryStore.java:95)
>> > at
>> >
>> org.wso2.carbon.mediatio

Re: [Carbon-dev] [ATTENTION] Branching the dependencies [DONE]

2010-02-25 Thread Ruwan Linton 
Folks,

Branching of all the dependencies are done, and all the external 
dependency sources are branched at [1]. I have added an svn:external to 
the trunk so that the one checkout continues to work.

The bad side is, you will need to delete the dependencies and update the 
carbon so that the new dependency locations will be checked out.

[1] - https://svn.wso2.org/repos/wso2/branches/carbon/3.0.0/dependencies/

Thanks,
Ruwan

Ruwan Linton wrote:
> Ruwan Linton wrote:
>> Samisa Abeysinghe wrote:
>>>
>>>
>>> On Thu, Feb 25, 2010 at 10:03 PM, Ruwan Linton >> > wrote:
>>>
>>> Folks,
>>>
>>> We are currently branching all the dependencies, please refrain 
>>> from
>>> committing to the dependencies till I inform the new branch
>>> information.
>>>
>>>
>>> I hope the one checkout will still work after branching, as we are 
>>> using externs from within dependencies folder. ?
>> One checkout will work,
>>
>> I have created the carbon/3.0.0 branch and in the process of 
>> branching all the dependencies. Once the branching has been done, I 
>> will delete the existing dependencies directory and add an svn 
>> external to the newly branched dependencies root, so that the trunk 
>> will work as it was, but taking dependencies from the 3.0.0 branch.
> I wont delete the dependencies trunk, rather will add externals to all 
> the dependencies from trunk to the branch, because that way it is easy 
> to switch the trunk back to the open development once we have branched 
> full carbon structure.
>
> Thanks,
> Ruwan
>>
>> Thanks,
>> Ruwan
>>>
>>> Samisa...
>>>  
>>>
>>>
>>> Thanks,
>>> Ruwan
>>>
>>> --
>>> Ruwan Linton
>>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>>> WSO2  Inc.; http://wso2.org
>>> email: ru...@wso2.com ; cell: +94 77 341 
>>> 3097
>>> blog: http://blog.ruwan.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org 
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>>
>>>
>>> -- 
>>> Samisa Abeysinghe
>>> Director, Engineering - WSO2 Inc.
>>>
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>  
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>   
>>
>>
>
>


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ru...@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org

Lean . Enterprise . Middleware


___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Carbon 3.0.0 - Iridium - Alpha2 builds

2010-02-25 Thread Thilina Mahesh Buddhika 
Fixed as of revision 56492.

Thanks.
/thilina

On Fri, Feb 26, 2010 at 9:43 AM, Thilina Mahesh Buddhika
wrote:

> On Fri, Feb 26, 2010 at 8:18 AM, Yumani Ranaweera  wrote:
>
>> Hi,
>>
>> There are errors in Is startup. Please see the attached log.txt.
>>
>
>
> Will look into this.
>
> Thanks.
> /thilina
>
>
>>
>> Thanks,
>> Yumani
>>
>>
>>
>> On Thu, Feb 25, 2010 at 6:03 PM, Samisa Abeysinghe wrote:
>>
>>> Available here:
>>> http://builder.wso2.org/~carbon/releases/carbon/3.0.0/1Alpha2/
>>>
>>> These
>>> packs are provided as is.
>>> Please do a smoke test.
>>>
>>> Samisa...
>>>
>>>
>>> ___
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> Yumani Ranaweera
>>
>> WSO2, Inc. - http://wso2.org
>> Email : yum...@wso2.com
>> Cell: +94 077 7795242
>> Blog   : http://yumani.blogspot.com/
>>
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
>
> --
> Thilina Mahesh Buddhika
> WSO2 Inc. ; http://wso2.com
> http://blog.thilinamb.com
>



-- 
Thilina Mahesh Buddhika
WSO2 Inc. ; http://wso2.com
http://blog.thilinamb.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [ATTENTION] Branching the dependencies [DONE]

2010-02-25 Thread Samisa Abeysinghe 
Great! Thanks!!

Samisa...

On Fri, Feb 26, 2010 at 10:56 AM, Ruwan Linton  wrote:

> Folks,
>
> Branching of all the dependencies are done, and all the external
> dependency sources are branched at [1]. I have added an svn:external to
> the trunk so that the one checkout continues to work.
>
> The bad side is, you will need to delete the dependencies and update the
> carbon so that the new dependency locations will be checked out.
>
> [1] - https://svn.wso2.org/repos/wso2/branches/carbon/3.0.0/dependencies/
>
> Thanks,
> Ruwan
>
> Ruwan Linton wrote:
> > Ruwan Linton wrote:
> >> Samisa Abeysinghe wrote:
> >>>
> >>>
> >>> On Thu, Feb 25, 2010 at 10:03 PM, Ruwan Linton  >>> > wrote:
> >>>
> >>> Folks,
> >>>
> >>> We are currently branching all the dependencies, please refrain
> >>> from
> >>> committing to the dependencies till I inform the new branch
> >>> information.
> >>>
> >>>
> >>> I hope the one checkout will still work after branching, as we are
> >>> using externs from within dependencies folder. ?
> >> One checkout will work,
> >>
> >> I have created the carbon/3.0.0 branch and in the process of
> >> branching all the dependencies. Once the branching has been done, I
> >> will delete the existing dependencies directory and add an svn
> >> external to the newly branched dependencies root, so that the trunk
> >> will work as it was, but taking dependencies from the 3.0.0 branch.
> > I wont delete the dependencies trunk, rather will add externals to all
> > the dependencies from trunk to the branch, because that way it is easy
> > to switch the trunk back to the open development once we have branched
> > full carbon structure.
> >
> > Thanks,
> > Ruwan
> >>
> >> Thanks,
> >> Ruwan
> >>>
> >>> Samisa...
> >>>
> >>>
> >>>
> >>> Thanks,
> >>> Ruwan
> >>>
> >>> --
> >>> Ruwan Linton
> >>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> >>> WSO2  Inc.; http://wso2.org
> >>> email: ru...@wso2.com ; cell: +94 77 341
> >>> 3097
> >>> blog: http://blog.ruwan.org
> >>>
> >>> Lean . Enterprise . Middleware
> >>>
> >>>
> >>> ___
> >>> Carbon-dev mailing list
> >>> Carbon-dev@wso2.org 
> >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Samisa Abeysinghe
> >>> Director, Engineering - WSO2 Inc.
> >>>
> >>> http://wso2.com/ - "lean . enterprise . middleware"
> >>>
> 
> >>>
> >>>
> >>> ___
> >>> Carbon-dev mailing list
> >>> Carbon-dev@wso2.org
> >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> >>>
> >>
> >>
> >
> >
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ru...@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
>
> Lean . Enterprise . Middleware
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>



-- 
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.

http://wso2.com/ - "lean . enterprise . middleware"
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev