[Dev] carbon-p2-repo 1.4-SNAPSHOT in trunk should 1.5-SNAPSHOT

[Chethiya Abeysinghe]

There is already a version 1.4 in the nexus repo at [1].


[1] -
http://sr5.us1.wso2.com/nexus/content/repositories/wso2-public/org/wso2/maven/carbon-p2-plugin/1.4/

Thanks
-- 
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.;  http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Plans for Rampart 1.6.2 ?

[Suresh Attanayaka]

Hi All,



On Wed, Apr 25, 2012 at 12:05 PM, Sagara Gunathunga  wrote:

> I have just completed Axis2 1.6.2 release. Since Suresh have completed
> testing on Rampart 1.6.2 branch without any issue I will start tasks
> related to Rampart 1.6.2 and Sandesha2 1.6.2 release shortly.
>
> Further Suresh found one issue on Rampart and he will provide a patch for
> it. If Prabath can commit latest Kerberos changes to the trunk we can
> include them into next Rampart version either 1.6.3 or 1.7.0.
>

yes, there are some issue I found in the trunk basically due to WSS4J fixes
and SAML changes. I will provide patches for those.

thanks,


>
> Thanks !
>
> On Tue, Apr 17, 2012 at 6:40 PM, Amila Jayasekara  wrote:
>
>> Suresh is working on verifying Rampart samples. If time permits I will
>> also do some testing. Once samples are verified we can go a head with
>> Rampart release.
>>
>> Prabath, are we going to integrate Kerberos changes to 1.6.2 ?
>> Kerberos is sort of a new feature, not sure whether we should add this
>> to 1.6.2 release. Please advice.
>>
>> Thanks
>> AmilaJ
>>
>>
>>
>> On Tue, Apr 17, 2012 at 5:41 PM, Sagara Gunathunga 
>> wrote:
>> > Guys,
>> >
>> > I have started Axis2 1.6.2 release and will call for vote soon. With our
>> > previous experience delaying Rampart version cause number of version
>> > incompatibility issues hence in IMO we need to release all these stuff
>> > together. In a offline chat I found I need to wait till another 2 days
>> to
>> > see results of ongoing Rampart tests other than that is there any other
>> > issue ?
>> >
>> > Thanks !
>> >
>> > --
>> > Sagara Gunathunga
>> >
>> > Technical Lead; WSO2, Inc.; http://wso2.com
>> > Blog - http://ssagara.blogspot.com
>> >
>> >
>>
>>
>>
>> --
>> Mobile : +94773330538
>>
>
>
>
> --
> Sagara Gunathunga
>
> Technical Lead; WSO2, Inc.; http://wso2.com
> Blog - http://ssagara.blogspot.com
>
>
>


-- 
Suresh Attanayake
Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060,+94770419136,+94710467976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Upgrading to Cassandra 1.1.0

[Kasun Weranga]

Hi all,

Shall we do the $subject. That is because currently we are facing some
issues when trying to integrate Cassandra storage handler (available
externally) into Hive. Since hive uses libthrift 0.7 and Cassandra 1.0.8
(current carbon version) uses libthrift 0.6, but the problem is
cassandra-handler needs to communicate with both hive and cassandra so it
needs to use only one thrift version.
We need to fix this issue before our first milestone coming in few days.
 We can overcome this issue easily by upgrading to new cassandra 1.1.0
version because it uses libthrift 0.7.
Also we can take the advantage of the new improvements coming with the new
Cassandra release.
Shall we do it ?

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

[Dev] Notes on API Manager meeting - April 25th.

[Isabelle Mauny]

Agreed changes for MVP:
- API Manager comes with predefined roles : creator, publisher, consumer.  
admin user has all roles ( to ensure smooth first experience without the 
necessary to create other users)
- Any user in creator role can add an API to the store  
- Any user in creator role can edit an API definition ( even if they have not 
created it).
- Any user in publisher role can see all APIs and promote the API from one API 
cycle state to another ( for example CREATED to PUBLISHED)
- APIs RXT needs to include contact information (Technical Owner, Business 
Owner) , same as Service RXT. This information needs to be reflected into API 
Provider / API Store UIs.

Isabelle.
--
Isabelle Mauny
Director, Product Management; WSO2, Inc.;  http://wso2.com/
email: isabe...@wso2.com - mobile: +34 616050684

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

[Dev] WSO2 Application Server Milestone 3 (wso2as-4.5.0-SNAPSHOT_M3) released

[Kasun Gajasinghe]

Hi folks,

WSO2 is happy announce the release of WSO2 Application Server M3,
The packs are hosted at [1].

New features and improvements in this release include,


   - [WSAS-831 ] - Implement JAX-RS
   support in AS
   - [WSAS-835 ] - Provide complete
   JAX-WS Specification support in AS
   - [WSAS-838 ] - Support for
   Inter-node notifications about services updates in a clustered environment
   - [WSAS-840 ] - UI support for
   JAX-WS services
   - [WSAS-841 ] - UI support for
   JAX-RS services
   - [WSAS-842 ] - Add JAX-WS
   samples of CXF
   - [WSAS-843 ] - Add JAX-RS
   samples of CXF
   - [WSAS-846 ] - Rewrite base
   implementation of artifact persistence logic in org.wso2.carbon.core package
   - [WSAS-847 ] - Rewrite artifact
   persisting logic - Security
   - [WSAS-848 ] - Rewrite artifact
   persisting logic - service-mgt component
   - [WSAS-850 ] - Rewrite artifact
   persisting logic - Throttling component
   - [WSAS-851 ] - Rewrite artifact
   persisting logic - Caching component
   - [WSAS-852 ] - Implement lazy
   loading for Web Applications

Further, the server start-up time is improved.

[1]
http://builder1.us1.wso2.org/~carbontrunk/releases/carbon/wso2as-4.5.0-SNAPSHOT_M3/

Thanks,
WSO2 Development Technologies Team

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

,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe*
*
 *blog: **http://blog.kasunbg.org* 

*
twitter: **http://twitter.com/kasunbg* 

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

[Dev] Jaggery Milestone-4 Released !

[Nuwan Bandara]

*Introducing Jaggery*

Jaggery is a framework to write webapps and HTTP-focused web services for
all aspects of the application: front-end, communication, Server-side logic
and persistence in pure Javascript. One of the intents of this framework is
to reduce the gap between writing web apps and web services.

This Framework uses Mozilla Rhino to process Javascript at the server and
also contains a powerful caching layer with the support of Rhino compiled
scripts; so its as fast as the JVM. As few key features, Jaggery has native
JSON support and also E4X support for XML manipulation.

M4 can be downloaded at
http://dist.wso2.org/products/jaggery/dl/jaggery-1.0.0-SNAPSHOT_M4.zip

Setting up Jaggery

   1. Extract jaggery-1.0.0-SNAPSHOT_M4.zip
   2. The bin folder will contain all the Jaggery execution scripts.
   3. Run sh bin/wso2server.sh (bin/wso2server.bat) command to start the
   server.

*The "Hello World" Jaggery App*

   - Create a directory called helloapp at
   {JAGGERY_HOME}/repository/deployment/server/jaggeryapps/
   - Create a jaggery file helloworld.jag inside the helloapp directory and
   add the following code snippet

<%
var name = 'Jaggery';
print("Hello " + name);
%>


   - Thats it ! point to {http://localhost:9763/helloapp/helloworld.jag}

*Key Features*


   - Compose server side scripts purely in javascript (.jag)
   - Script caching support
   - Script include support
   - Module include support
   - Command line tool for easy development
   - Try-it tool for web based script validation
   - Includes support for,
  - HTTP request/response and session
  - JSON send/receive
  - Server side XMLHttpRequest
  - URIMatcher
  - Web Service invocation
  - File I/O
  - Email
  - Read/write feed
  - Relational database
  - Metadata store
  - Importing 3rd party javascript files

For more information and samples you can refer to Jaggery docs at (http://
{yourip}:9763/docs/documentation.jag) which are shipped with the
distribution

Go through M4 release
notesfor
fixes, improvements and new features.

You can report issues, improvements and suggestions to Jaggery issue
tracker


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

Re: [Dev] Upgrading to Cassandra 1.1.0

[Deependra Ariyadewa]

On Wed, Apr 25, 2012 at 2:23 PM, Kasun Weranga  wrote:

> Hi all,
>
> Shall we do the $subject. That is because currently we are facing some
> issues when trying to integrate Cassandra storage handler (available
> externally) into Hive. Since hive uses libthrift 0.7 and Cassandra 1.0.8
> (current carbon version) uses libthrift 0.6, but the problem is
> cassandra-handler needs to communicate with both hive and cassandra so it
> needs to use only one thrift version.
> We need to fix this issue before our first milestone coming in few days.
>  We can overcome this issue easily by upgrading to new cassandra 1.1.0
> version because it uses libthrift 0.7.
> Also we can take the advantage of the new improvements coming with the new
> Cassandra release.
> Shall we do it ?
>

It is good have the latest Cassandra version with 4.0.0 release.

There are changes done in Cassandra dependency to enable Carbon user
permission scheme which We have to merge with Cassandra 1.1.x. Also we have
to verify dependency library list for possible version conflicts.

It is good to get feed back from MB developers before do this change.

Thanks,

Deependra.



> Thanks,
> KasunW
>
>


-- 
Deependra Ariyadewa
WSO2, Inc. http://wso2.com/ http://wso2.org

email d...@wso2.com; cell +94 71 403 5996 ;
Blog http://risenfall.wordpress.com/
PGP info: KeyID: 'DC627E6F'
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] New property in autoscaler.xml

[Nirmal Fernando]

On Sun, Apr 22, 2012 at 11:43 AM, Afkham Azeez  wrote:

> I prefer to have that under loadbalancer
>
>
I've added them under loadbalancer. Also should we add autoscaler task
interval too in loadbalancer.conf (since autoscaler xml is no longer
there)?

>
> On Sun, Apr 22, 2012 at 11:35 AM, Nirmal Fernando  wrote:
>
>> Hi,
>>
>> On Sun, Apr 22, 2012 at 11:24 AM, Afkham Azeez  wrote:
>>
>>> Somehow, that also needs to go into loadbalancer.conf since sysadmins
>>> will have to configure that. The idea behind having the loadbalancer.conf
>>> file is that sysadmins have to deal with just a single file, and not deal
>>> with synapse XML files, axis2.xml etc.
>>>
>>
>> I see! Will incorporate that to loadbalancer,conf. I can see two possible
>> ways:
>>
>> 1. add a new autoscaler element and put both enable_autoscaler and
>> autoscaler_service_epr properties there.
>> 2. add those two properties to loadbalancer element.
>>
>> WDYT?
>>
>>>
>>>
>>> On Sun, Apr 22, 2012 at 10:39 AM, Nirmal Fernando wrote:
>>>
 Hi,

 Autoscaler Synapse task (which is in LB) needs to know the EPR of the
 Autoscaler Service.

 I propose to add a new property in autoscaler.xml like following,

 
 http://127.0.0.1:9765/services/AutoscalerService/"/>

 Thoughts please?

 --

 Thanks & regards,
 Nirmal

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

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 

Thanks & regards,
Nirmal

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

Re: [Dev] New property in autoscaler.xml

[Afkham Azeez]

On Wed, Apr 25, 2012 at 5:57 PM, Nirmal Fernando  wrote:

>
>
> On Sun, Apr 22, 2012 at 11:43 AM, Afkham Azeez  wrote:
>
>> I prefer to have that under loadbalancer
>>
>>
> I've added them under loadbalancer. Also should we add autoscaler task
> interval too in loadbalancer.conf (since autoscaler xml is no longer
> there)?
>

Yes, it should be possible to configure everything just by using the
loadbalancer.conf. This should ideally include some of the clustering
configuration stuff in the axis2.xml as well.


>
>> On Sun, Apr 22, 2012 at 11:35 AM, Nirmal Fernando wrote:
>>
>>> Hi,
>>>
>>> On Sun, Apr 22, 2012 at 11:24 AM, Afkham Azeez  wrote:
>>>
 Somehow, that also needs to go into loadbalancer.conf since sysadmins
 will have to configure that. The idea behind having the loadbalancer.conf
 file is that sysadmins have to deal with just a single file, and not deal
 with synapse XML files, axis2.xml etc.

>>>
>>> I see! Will incorporate that to loadbalancer,conf. I can see two
>>> possible ways:
>>>
>>> 1. add a new autoscaler element and put both enable_autoscaler and
>>> autoscaler_service_epr properties there.
>>> 2. add those two properties to loadbalancer element.
>>>
>>> WDYT?
>>>


 On Sun, Apr 22, 2012 at 10:39 AM, Nirmal Fernando wrote:

> Hi,
>
> Autoscaler Synapse task (which is in LB) needs to know the EPR of the
> Autoscaler Service.
>
> I propose to add a new property in autoscaler.xml like following,
>
> 
> http://127.0.0.1:9765/services/AutoscalerService/"/>
>
> Thoughts please?
>
> --
>
> Thanks & regards,
> Nirmal
>
> Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>



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


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>



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

[Dev] [Bamboo-Build] WSO2 Carbon > platform > #128 was SUCCESSFUL (with 1988 tests). Change made by 12 authors.

[Bamboo]

---
WSO2 Carbon > platform > #128 was successful.
---
Code has been updated by miyuru, hiranya, denis, madhuka, isharak, charith, 
nuwanw, subash, ajithn, nuwan, chanaka, lalaji.
1988 tests in total.

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


--
Code Changes
--
lalaji (125884):

>Updated new api-provider app site

charith (125895):

>doc changes

lalaji (125881):

>Added default template structure for api-provider 



--
Tests
--
Fixed Tests (3)
   - EndpointTest: Attach endpoints to service
   - EndpointTest: Add service with endpoints
   - EndpointTest: Add wsdl with endpoints

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

Re: [Dev] Notes on API Manager meeting - April 25th.

[Chris Haddad]

+1

/Chris
+1.678.431.1656


On Apr 25, 2012, at 5:21, Isabelle Mauny  wrote:

> Agreed changes for MVP:
> - API Manager comes with predefined roles : creator, publisher, consumer.  
> admin user has all roles ( to ensure smooth first experience without the 
> necessary to create other users)
> - Any user in creator role can add an API to the store  
> - Any user in creator role can edit an API definition ( even if they have not 
> created it).
> - Any user in publisher role can see all APIs and promote the API from one 
> API cycle state to another ( for example CREATED to PUBLISHED)
> - APIs RXT needs to include contact information (Technical Owner, Business 
> Owner) , same as Service RXT. This information needs to be reflected into API 
> Provider / API Store UIs.
> 
> Isabelle.
> --
> Isabelle Mauny
> Director, Product Management; WSO2, Inc.;  http://wso2.com/
> email: isabe...@wso2.com - mobile: +34 616050684
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading to Cassandra 1.1.0

[Srinath Perera]

+1

On Wed, Apr 25, 2012 at 2:23 PM, Kasun Weranga  wrote:

> Hi all,
>
> Shall we do the $subject. That is because currently we are facing some
> issues when trying to integrate Cassandra storage handler (available
> externally) into Hive. Since hive uses libthrift 0.7 and Cassandra 1.0.8
> (current carbon version) uses libthrift 0.6, but the problem is
> cassandra-handler needs to communicate with both hive and cassandra so it
> needs to use only one thrift version.
> We need to fix this issue before our first milestone coming in few days.
>  We can overcome this issue easily by upgrading to new cassandra 1.1.0
> version because it uses libthrift 0.7.
> Also we can take the advantage of the new improvements coming with the new
> Cassandra release.
> Shall we do it ?
>
> Thanks,
> KasunW
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] Upgrading to Cassandra 1.1.0

[Charith Wickramarachchi]

On Wed, Apr 25, 2012 at 5:55 PM, Deependra Ariyadewa  wrote:

>
>
> On Wed, Apr 25, 2012 at 2:23 PM, Kasun Weranga  wrote:
>
>> Hi all,
>>
>> Shall we do the $subject. That is because currently we are facing some
>> issues when trying to integrate Cassandra storage handler (available
>> externally) into Hive. Since hive uses libthrift 0.7 and Cassandra 1.0.8
>> (current carbon version) uses libthrift 0.6, but the problem is
>> cassandra-handler needs to communicate with both hive and cassandra so it
>> needs to use only one thrift version.
>> We need to fix this issue before our first milestone coming in few days.
>>  We can overcome this issue easily by upgrading to new cassandra 1.1.0
>> version because it uses libthrift 0.7.
>> Also we can take the advantage of the new improvements coming with the
>> new Cassandra release.
>> Shall we do it ?
>>
>
> It is good have the latest Cassandra version with 4.0.0 release.
>
> There are changes done in Cassandra dependency to enable Carbon user
> permission scheme which We have to merge with Cassandra 1.1.x. Also we have
> to verify dependency library list for possible version conflicts.
>
> It is good to get feed back from MB developers before do this change.
>

+1

thanks,
Charith


>
> Thanks,
>
> Deependra.
>
>
>
>> Thanks,
>> KasunW
>>
>>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
>


-- 
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

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

Re: [Dev] Upgrading to Cassandra 1.1.0

[Kasun Weranga]

On Wed, Apr 25, 2012 at 5:55 PM, Deependra Ariyadewa  wrote:

>
>
> On Wed, Apr 25, 2012 at 2:23 PM, Kasun Weranga  wrote:
>
>> Hi all,
>>
>> Shall we do the $subject. That is because currently we are facing some
>> issues when trying to integrate Cassandra storage handler (available
>> externally) into Hive. Since hive uses libthrift 0.7 and Cassandra 1.0.8
>> (current carbon version) uses libthrift 0.6, but the problem is
>> cassandra-handler needs to communicate with both hive and cassandra so it
>> needs to use only one thrift version.
>> We need to fix this issue before our first milestone coming in few days.
>>  We can overcome this issue easily by upgrading to new cassandra 1.1.0
>> version because it uses libthrift 0.7.
>> Also we can take the advantage of the new improvements coming with the
>> new Cassandra release.
>> Shall we do it ?
>>
>
> It is good have the latest Cassandra version with 4.0.0 release.
>
> There are changes done in Cassandra dependency to enable Carbon user
> permission scheme which We have to merge with Cassandra 1.1.x. Also we have
> to verify dependency library list for possible version conflicts.
>

I'll start working on this


> It is good to get feed back from MB developers before do this change.
>
> Thanks,
>
> Deependra.
>
>
>
>> Thanks,
>> KasunW
>>
>>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Quartz error when manager is idling

[Supun Malinga]

stack trace,
Looks like occurs after the tenant cleanup.

[2012-04-25 18:00:06,105]  INFO
{org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Cleaned up
tenant supun.org
[2012-04-25 18:18:18,202] ERROR {org.quartz.core.JobRunShell} -  Job
08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
threw an unhandled Exception:
java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected
 at
org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
 at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
[2012-04-25 18:18:18,205] ERROR {org.quartz.core.ErrorLogger} -  Job
(08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See
nested exception: java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected]
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
 at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused by: java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected
 at
org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
 ... 1 more
[2012-04-25 18:28:08,523]  INFO
{org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Running Summary
Generator...
[2012-04-25 18:28:08,533]  INFO
{org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Summary
generation successful ...
[2012-04-25 18:28:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
threw an unhandled Exception:
java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected
 at
org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
 at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
[2012-04-25 18:28:18,190] ERROR {org.quartz.core.ErrorLogger} -  Job
(08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See
nested exception: java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected]
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
 at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused by: java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected
 at
org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
 ... 1 more
[2012-04-25 18:38:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
threw an unhandled Exception:
java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected
at
org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
[2012-04-25 18:38:18,191] ERROR {org.quartz.core.ErrorLogger} -  Job
(08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See
nested exception: java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected]
 at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
Caused by: java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected
at
org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
... 1 more
[2012-04-25 18:48:18,197] ERROR {org.quartz.core.JobRunShell} -  Job
08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
threw an unhandled Exception:
java.lang.IncompatibleClassChangeError: Found class
org.quartz.JobExecutionContext, but interface was expected
at
org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
[2012-04-25 18:48:18,198] ERROR {org.quartz.core.ErrorLogger} -  Job
(08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea8

Re: [Dev] Quartz error when manager is idling

[Amila Maha Arachchi]

Hi Supun,

Can you please create jira for this. Need to check whether this is due to
the new quartz version. At the moment there are two quartz versions used.

AmilaM.

On Wed, Apr 25, 2012 at 7:41 PM, Supun Malinga  wrote:

> stack trace,
> Looks like occurs after the tenant cleanup.
>
> [2012-04-25 18:00:06,105]  INFO
> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Cleaned up
> tenant supun.org
> [2012-04-25 18:18:18,202] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> [2012-04-25 18:18:18,205] ERROR {org.quartz.core.ErrorLogger} -  Job
> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an exception.
> org.quartz.SchedulerException: Job threw an unhandled exception. [See
> nested exception: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> Caused by: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  ... 1 more
> [2012-04-25 18:28:08,523]  INFO
> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Running Summary
> Generator...
> [2012-04-25 18:28:08,533]  INFO
> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Summary
> generation successful ...
> [2012-04-25 18:28:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> [2012-04-25 18:28:18,190] ERROR {org.quartz.core.ErrorLogger} -  Job
> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an exception.
> org.quartz.SchedulerException: Job threw an unhandled exception. [See
> nested exception: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> Caused by: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  ... 1 more
> [2012-04-25 18:38:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
> at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> [2012-04-25 18:38:18,191] ERROR {org.quartz.core.ErrorLogger} -  Job
> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an exception.
> org.quartz.SchedulerException: Job threw an unhandled exception. [See
> nested exception: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected]
>  at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
> at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> Caused by: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
> at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> ... 1 more
> [2012-04-25 18:48:18,197] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecuti

Re: [Dev] Upgrading to Cassandra 1.1.0

[Shammi Jayasinghe]

On Wed, Apr 25, 2012 at 5:55 PM, Deependra Ariyadewa  wrote:

>
>
> On Wed, Apr 25, 2012 at 2:23 PM, Kasun Weranga  wrote:
>
>> Hi all,
>>
>> Shall we do the $subject. That is because currently we are facing some
>> issues when trying to integrate Cassandra storage handler (available
>> externally) into Hive. Since hive uses libthrift 0.7 and Cassandra 1.0.8
>> (current carbon version) uses libthrift 0.6, but the problem is
>> cassandra-handler needs to communicate with both hive and cassandra so it
>> needs to use only one thrift version.
>> We need to fix this issue before our first milestone coming in few days.
>>  We can overcome this issue easily by upgrading to new cassandra 1.1.0
>> version because it uses libthrift 0.7.
>> Also we can take the advantage of the new improvements coming with the
>> new Cassandra release.
>> Shall we do it ?
>>
>
> It is good have the latest Cassandra version with 4.0.0 release.
>
> There are changes done in Cassandra dependency to enable Carbon user
> permission scheme which We have to merge with Cassandra 1.1.x. Also we have
> to verify dependency library list for possible version conflicts.
>
> It is good to get feed back from MB developers before do this change.
>
> +1

Thanks
Shammi

> Thanks,
>
> Deependra.
>
>
>
>> Thanks,
>> KasunW
>>
>>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
>


-- 
Best Regards,*

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

Re: [Dev] Quartz error when manager is idling

[Supun Malinga]

Hi,

https://wso2.org/jira/browse/STRATOS-2029

Also observed that error occurs periodically.

thanks,

On Wed, Apr 25, 2012 at 8:00 PM, Amila Maha Arachchi wrote:

> Hi Supun,
>
> Can you please create jira for this. Need to check whether this is due to
> the new quartz version. At the moment there are two quartz versions used.
>
> AmilaM.
>
> On Wed, Apr 25, 2012 at 7:41 PM, Supun Malinga  wrote:
>
>>  stack trace,
>> Looks like occurs after the tenant cleanup.
>>
>> [2012-04-25 18:00:06,105]  INFO
>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Cleaned up
>> tenant supun.org
>> [2012-04-25 18:18:18,202] ERROR {org.quartz.core.JobRunShell} -  Job
>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an unhandled Exception:
>> java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> [2012-04-25 18:18:18,205] ERROR {org.quartz.core.ErrorLogger} -  Job
>> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an exception.
>> org.quartz.SchedulerException: Job threw an unhandled exception. [See
>> nested exception: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected]
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> Caused by: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  ... 1 more
>> [2012-04-25 18:28:08,523]  INFO
>> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Running Summary
>> Generator...
>> [2012-04-25 18:28:08,533]  INFO
>> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Summary
>> generation successful ...
>> [2012-04-25 18:28:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an unhandled Exception:
>> java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> [2012-04-25 18:28:18,190] ERROR {org.quartz.core.ErrorLogger} -  Job
>> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an exception.
>> org.quartz.SchedulerException: Job threw an unhandled exception. [See
>> nested exception: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected]
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> Caused by: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  ... 1 more
>> [2012-04-25 18:38:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an unhandled Exception:
>> java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>> at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>>  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>> at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> [2012-04-25 18:38:18,191] ERROR {org.quartz.core.ErrorLogger} -  Job
>> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an exception.
>> org.quartz.SchedulerException: Job threw an unhandled exception. [See
>> nested exception: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected]
>>  at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>> at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> Caused by: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>> at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>>  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>> 

Re: [Dev] Quartz error when manager is idling

[Afkham Azeez]

Looks like this task in not shutdown/cancelled when the tenant is unloaded.
You have to implement an OSGi service and handle the throttling component.

On Wed, Apr 25, 2012 at 7:41 PM, Supun Malinga  wrote:

> stack trace,
> Looks like occurs after the tenant cleanup.
>
> [2012-04-25 18:00:06,105]  INFO
> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Cleaned up
> tenant supun.org
> [2012-04-25 18:18:18,202] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> [2012-04-25 18:18:18,205] ERROR {org.quartz.core.ErrorLogger} -  Job
> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an exception.
> org.quartz.SchedulerException: Job threw an unhandled exception. [See
> nested exception: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> Caused by: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  ... 1 more
> [2012-04-25 18:28:08,523]  INFO
> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Running Summary
> Generator...
> [2012-04-25 18:28:08,533]  INFO
> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Summary
> generation successful ...
> [2012-04-25 18:28:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> [2012-04-25 18:28:18,190] ERROR {org.quartz.core.ErrorLogger} -  Job
> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an exception.
> org.quartz.SchedulerException: Job threw an unhandled exception. [See
> nested exception: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected]
> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>  at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> Caused by: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
>  at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>  ... 1 more
> [2012-04-25 18:38:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
> at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> [2012-04-25 18:38:18,191] ERROR {org.quartz.core.ErrorLogger} -  Job
> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an exception.
> org.quartz.SchedulerException: Job threw an unhandled exception. [See
> nested exception: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected]
>  at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
> at
> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
> Caused by: java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but interface was expected
> at
> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> ... 1 more
> [2012-04-25 18:48:18,197] ERROR {org.quartz.core.JobRunShell} -  Job
> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
> threw an unhandled Exception:
> java.lang.IncompatibleClassChangeError: Found class
> org.quartz.JobExecutionContext, but in

[Dev] Autoscaling with LXCs - end to end demo

[Afkham Azeez]

Today we were able to see an end to end demo where the autoscaler talked to
the Tropos controller, and the controller spawned LXC instances! Tropos is
the name we've been using for this 'thing' we are doing with
LXC+autoscaler+LB+agents :) If there is a better name, please come up with
suggestions :)

Some stuff were done manually to get the end to end flow working, but the
team got it working. Good job folks!

Damitha et. al., please schedule another demo for all interested parties
next week. It would be ideal if the manual steps are fixed to be done
automatically with scripts etc.

Thanks
Azeez

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

[Dev] carbon component plugin. Not working for custom group ID

[Pradeep Fernando]

Hi,

If you give a different groupID during the interactive session, the service
stubs building fails. Can you confirm. Am i doing something wrong ?

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

Re: [Dev] HTTP session replication

[Kishanthan Thangarajah]

On Tue, Apr 24, 2012 at 7:31 PM, Isuru Suriarachchi  wrote:

> +1, We've almost completed all the roadmap items for AS 4.5.0. As we've
> not feature freezed yet, we can look into this.
>
> Thanks,
> ~Isuru
>
>
> On Tue, Apr 24, 2012 at 7:15 PM, Afkham Azeez  wrote:
>
>> With the Tomcat OSGification completed, we can finally implement support
>> for HTTP session replication. We could tie into the underlying Tribes
>> framework to do this. I believe we should write a Tomcat
>> HttpSessionReplicationValve which will handle replication of sessions.
>> Kishanthan can you own this? Even though this may look like an AppServer
>> roadmap item, this is something that will get used throughout the platform.
>
>
+1, I will own this.

Thanks,
Kishanthan.

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


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

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

[Dev] WSO2 API Manager 1.0.0-M2 available for download

[Sumedha Rubasinghe]

WSO2 API Manager 1.0.0-M2 can be downloaded from
http://people.wso2.com/~sumedha/builds/am/25-04-2012/wso2am-1.0.0-M2.zip .

*How to run samples?*
Following steps explain how to get samples up and running:

1. Download & extract wso2am-1.0.0-SNAPSHOT.zip
2. Go to 'samples' folder.
3. There are 3 samples, namely:
- TwitterSearch
- YahooPlaceFinder
- YoutubeFeeds
4. README.txt inside each of the sample folder provides complete
instructions on deploying & testing sample scenarios.


 This release includes fixes to following issues.
Bug

   - [APISTORE-71 ] - When
   attempting to add a duplicate API (with same name and version of an
   existing API), No error message given. Instead, a 'successfully added the
   new API' popup message is given.
   - [APISTORE-83 ] - Pagination
   of API listing of API Manager does not work properly
   - [APISTORE-112 ] - readme,
   release-notes, and install does not specify API Manager information
   - [APISTORE-113 ] - how do I
   login to API publisher application?
   - [APISTORE-121 ] - Order of
   the APIs change almost every time you go to APIs page in API store.
   - [APISTORE-149 ] - API
   Publisher login does not work in my safari
   - [APISTORE-152 ] - API
   Provider list screen displays multiple navigation pages (1,2,3,4). even
   though only two services are present
   - [APISTORE-154 ] - API store
   is requiring Admin rights
   - [APISTORE-165 ] - README
   file explains ESB
   - [APISTORE-168 ] -
   release-notes.html is from ESB
   - [APISTORE-171 ] - Login and
   Cancel buttons of apiprovider app misaligned in IE9
   - [APISTORE-172 ] - API
   publisher UI shows pagination even with 0 APIs
   - [APISTORE-173 ] - Fix the
   alignment problems of left menu of API Publisher seen with IE9
   - [APISTORE-175 ] - Add new
   API form in API Provider is confusing on actions
   - [APISTORE-176 ] - API
   Publisher UI does not render right with IE
   - [APISTORE-177 ] - When I
   click on API icon the API info is not shown on IE
   - [APISTORE-178 ] - Search
   function with API Provider is broken
   - [APISTORE-181 ] - Not clear
   how to eun samples 1, 2 & 3
   - [APISTORE-182 ] - Document
   how to use API sore
   - [APISTORE-183 ] - Provide
   docs for API store/manager - at least a quick start guide.
   - [APISTORE-188 ] - API Store
   & Provider does not function as expect on IE9
   - [APISTORE-201 ] - Copy API
   feature is broken
   - [APISTORE-204 ] - Cannot
   add an API doc of type "support forum" due to an NPE
   - [APISTORE-206 ] -
   Intermittent issue in API provider: GovernanceException: Unable to obtain
   governance artifact configuration
   - [APISTORE-207 ] - Cannot
   edit APIs
   - [APISTORE-208 ] - Paginate
   the apps listed in My Applications page in API store
   - [APISTORE-226 ] - Tier does
   not get saved along a subscription
   - [APISTORE-228 ] - API
   Context not getting saved in AM_KEY_CONTEXT_MAPPING table
   - [APISTORE-239 ] - Once an
   API is Updated from API Provider, It's No Longer Accessible
   - [APISTORE-242 ] - NPE When
   Accessing an API with an Invalid Key
   - [APISTORE-245 ] - Frequency
   based throttling is not working
   - [APISTORE-246 ] - Latest
   Published Versions of APIs are Not Listed on API Store
   - [APISTORE-247 ] - API
   Throttling (Tiers) Doesn't Work
   - [APISTORE-248 ] - A Single
   Valid API Key Can be Used to Access Multiple Versions of the Same API

Improvement

   - [APISTORE-9 ] - Add tooltip
   description for services an

[Dev] WSO2 Developer Studio 2.0.0 Beta Released !

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 2.0.0 Beta ready to be downloaded at
[1]
(without dependencies) and
[2]
(with dependencies).

Bug

   - [TOOLS-86 ] - Delete items
   remain in the UI.
   - [TOOLS-148 ] - endpoint name
   that is given by default should change for each artifact created
   - [TOOLS-669 ] - It takes ages
   for Registry Handler UI to load
   - [TOOLS-833 ] - Allocated
   memory for server process is not taken into effect when starting up Carbon
   Server inside Carbon Studio
   - [TOOLS-967 ] - Ctrl+V does not
   paste the contents into the input field
   - [TOOLS-970 ] - Importing .dbs
   as a dependency to a new Carbon project does not allow to create the Carbon
   project
   - [TOOLS-974 ] - Error when
   shutting down a Carbon Server from the Eclipse Console
   - [TOOLS-975 ] - Management
   Console does not show up automatically even when the Carbon server start up
   successfully
   - [TOOLS-977 ] - When we apply
   an 'Ordinal' property on a parameter from the Outline View, it does not
   show up in the DS Editor's Source View
   - [TOOLS-978 ] - All the
   Ordinals automatically turn to 0 when saving the configuration
   - [TOOLS-979 ] - Bug in
   Documentation - ESB Tools
   - [TOOLS-980 ] - Cannot specify
   'localhost' in a Endpoint URL
   - [TOOLS-982 ] - Saving .dbs
   file with serviceNamespace attribute giving an error in data service editor.
   - [TOOLS-983 ] - In proxy
   services editor, Endpoint type is set to Anonymous by default
   - [TOOLS-984 ] - In proxy
   services editor, cannot save configuration if the Endpoint element is
   removed
   - [TOOLS-987 ] - Registry
   resources tree view is not correctly showing the resources to be deployed
   - [TOOLS-988 ] - When deleting
   an ESB Artifact, artifact.xml get corrupted
   - [TOOLS-989 ] - When deleting
   an ESB Artifact, incorrect Warning message is displayed
   - [TOOLS-990 ] - When importing
   a .dbs to a project and if that .dbs already exists in the same project no
   error / warning message is given
   - [TOOLS-991 ] - Add
   "description" to ESB EMF Tree editor
   - [TOOLS-992 ] - While refer a
   WSDL as a registry resource, there should be a way to add external
   resources that are being defined in the WSDL when creating a proxy service
   - [TOOLS-995 ] - When importing
   a Synapse config from file system, it does not generate the separate
   entries for local entries when split the ESB config
   - [TOOLS-996 ] - Registry
   Resource behavior is inconsistent for templates and file system imports
   - [TOOLS-997 ] - Conditional
   Router Mediator serialization error
   - [TOOLS-998 ] - Multiple
   service descriptions can be added when creating a data-service through
   wizard
   - [TOOLS-999 ] - Serialization
   error in the URLRewrite Mediator
   - [TOOLS-1004 ] - Data-source
   listing drop down in query page wont get update with newly added
   data-sources.
   - [TOOLS-1006 ] -
   NullPointerException when adding query properties
   - [TOOLS-1012 ] - When 'Use
   Column Numbers' is set to true in query result, output mappings should use
   'data-source column number' instead of 'data-source column name'.
   - [TOOLS-1015 ] - 'Export Type'
   filed is missing in output mappings.
   - [TOOLS-1019 ] - Error occurs
   when trying to build a library artifact created using a workspace project,
   if the pom already exists
   - [TOOLS-1023 ] - Cannot build
   a CAR p

Re: [Dev] Autoscaling with LXCs - end to end demo

[Sanjiva Weerawarana]

Excellent! I look forward to seeing the next iteration ...

On Wed, Apr 25, 2012 at 9:16 PM, Afkham Azeez  wrote:

> Today we were able to see an end to end demo where the autoscaler talked
> to the Tropos controller, and the controller spawned LXC instances! Tropos
> is the name we've been using for this 'thing' we are doing with
> LXC+autoscaler+LB+agents :) If there is a better name, please come up with
> suggestions :)
>
> Some stuff were done manually to get the end to end flow working, but the
> team got it working. Good job folks!
>
> Damitha et. al., please schedule another demo for all interested parties
> next week. It would be ideal if the manual steps are fixed to be done
> automatically with scripts etc.
>
> Thanks
> Azeez
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

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

Re: [Dev] Autoscaling with LXCs - end to end demo

[Nirmal Fernando]

On Wed, Apr 25, 2012 at 9:16 PM, Afkham Azeez  wrote:

> Today we were able to see an end to end demo where the autoscaler talked
> to the Tropos controller, and the controller spawned LXC instances! Tropos
> is the name we've been using for this 'thing' we are doing with
> LXC+autoscaler+LB+agents :) If there is a better name, please come up with
> suggestions :)
>
> Some stuff were done manually to get the end to end flow working, but the
> team got it working. Good job folks!
>
> Damitha et. al., please schedule another demo for all interested parties
> next week.
>

Sure, will arrange one!


> It would be ideal if the manual steps are fixed to be done automatically
> with scripts etc.
>
>
We'll work on this.

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


-- 

Thanks & regards,
Nirmal

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

[Dev] random error in stratos as login

[Supun Malinga]

Hi,

After a restart (randomly) getting the following error and automatically
get logged in with the last logged in user.
jira : https://wso2.org/jira/browse/STRATOS-2030

[2012-04-25 23:10:13,020] @supun1.org [3] [WSO2 Stratos Application
Server]ERROR {org.wso2.carbon.registry.app.ResourceServlet} -  Error
retrieving the resource
/_system/governance/repository/theme/admin/main.css. Resource does not
exist at path /_system/governance/repository/theme/admin/main.css
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path
/_system/governance/repository/theme/admin/main.css
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)
 at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:118)
at
org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)
 at
org.wso2.carbon.registry.app.ResourceServlet.doGet(ResourceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:471)
 at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:402)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:329)
 at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
at
org.wso2.carbon.redirector.servlet.ui.filters.AllPagesFilter.doFilter(AllPagesFilter.java:145)
 at
org.eclipse.equinox.http.helper.FilterServletAdaptor.service(FilterServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
 at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
 at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
 at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
 at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
 at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:139)
 at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
 at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2012-04-25 23:10:13,026] @supun1.org [3] [WSO2 Stratos Application
Server]ERROR {org.wso2.carbon.registry.app.ResourceServlet} -  Failed to
get resource content. Resource does not exist at path
/_system/governance/repository/theme/admin/main.css
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path
/_system/governance/repository/theme/admin/main.css
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)
 at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:118)

Re: [Dev] Quartz error when manager is idling

[Amila Maha Arachchi]

Hi Azeez,

Throttling rule execution is not a tenant specific task. You don't need a
loaded tenant to run it. This task keeps running when the server is up.

My understanding on this issue is as follows.

ThrottlingJob class implements Job interface from quartz. At the moment
there are two quartz versions available. 1.6 and 2.1. quartz 2.1 get bound
to throttling manager it seems. There are some drastic changes in the
quartz 2.1 implementation. We have to change the code to get it to work
with quartz 2.1. We encountered similar kind of issue (don't remember
whether it was the exact issue) in billing components. Until it is fixed we
applied a workaround to get the quartz 1.6 binded to billing bundle
(importing quartz 1.6 with a specific version 9.9.9 in the pom).

These should be fixed for this release and we have to get rid of quartz 1.6
(no need to keep two jars) and go with 2.1

I created two jiras to track this. STRATOS-2031 and STRATOS-2032.

Regards,
AmilaM.

On Wed, Apr 25, 2012 at 8:55 PM, Afkham Azeez  wrote:

> Looks like this task in not shutdown/cancelled when the tenant is
> unloaded. You have to implement an OSGi service and handle the throttling
> component.
>
> On Wed, Apr 25, 2012 at 7:41 PM, Supun Malinga  wrote:
>
>> stack trace,
>> Looks like occurs after the tenant cleanup.
>>
>> [2012-04-25 18:00:06,105]  INFO
>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Cleaned up
>> tenant supun.org
>> [2012-04-25 18:18:18,202] ERROR {org.quartz.core.JobRunShell} -  Job
>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an unhandled Exception:
>> java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> [2012-04-25 18:18:18,205] ERROR {org.quartz.core.ErrorLogger} -  Job
>> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an exception.
>> org.quartz.SchedulerException: Job threw an unhandled exception. [See
>> nested exception: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected]
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> Caused by: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  ... 1 more
>> [2012-04-25 18:28:08,523]  INFO
>> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Running Summary
>> Generator...
>> [2012-04-25 18:28:08,533]  INFO
>> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Summary
>> generation successful ...
>> [2012-04-25 18:28:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an unhandled Exception:
>> java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> [2012-04-25 18:28:18,190] ERROR {org.quartz.core.ErrorLogger} -  Job
>> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an exception.
>> org.quartz.SchedulerException: Job threw an unhandled exception. [See
>> nested exception: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected]
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>>  at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>> Caused by: java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>>  at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>  ... 1 more
>> [2012-04-25 18:38:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>> threw an unhandled Exception:
>> java.lang.IncompatibleClassChangeError: Found class
>> org.quartz.JobExecutionContext, but interface was expected
>> at
>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>>  at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>> at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(Si

Re: [Dev] Quartz error when manager is idling

[Dinusha Senanayaka]

Hi,

On Thu, Apr 26, 2012 at 12:50 AM, Amila Maha Arachchi wrote:

> Hi Azeez,
>
> Throttling rule execution is not a tenant specific task. You don't need a
> loaded tenant to run it. This task keeps running when the server is up.
>
> My understanding on this issue is as follows.
>
> ThrottlingJob class implements Job interface from quartz. At the moment
> there are two quartz versions available. 1.6 and 2.1. quartz 2.1 get bound
> to throttling manager it seems. There are some drastic changes in the
> quartz 2.1 implementation. We have to change the code to get it to work
> with quartz 2.1. We encountered similar kind of issue (don't remember
> whether it was the exact issue) in billing components. Until it is fixed we
> applied a workaround to get the quartz 1.6 binded to billing bundle
> (importing quartz 1.6 with a specific version 9.9.9 in the pom).
>
> These should be fixed for this release and we have to get rid of quartz
> 1.6 (no need to keep two jars) and go with 2.1
>

There are some major API changes between quartz-1.6 and 2.1 version. So we
need to update the Synapse task code to compatible with quartz-2.1. AFAIK
billing component is also using Synapse task. I have given a Synapse patch
to upgrade quartz version to 2.1. Here is the JIRA [1]. Once this patch is
applied to Synapse trunk, we can get rid of having two quartz versions and
move to 2.1 version.

[1]. https://issues.apache.org/jira/browse/SYNAPSE-837

Regards,
Dinusha.

>
> I created two jiras to track this. STRATOS-2031 and STRATOS-2032.
>
> Regards,
> AmilaM.
>
> On Wed, Apr 25, 2012 at 8:55 PM, Afkham Azeez  wrote:
>
>> Looks like this task in not shutdown/cancelled when the tenant is
>> unloaded. You have to implement an OSGi service and handle the throttling
>> component.
>>
>> On Wed, Apr 25, 2012 at 7:41 PM, Supun Malinga  wrote:
>>
>>> stack trace,
>>> Looks like occurs after the tenant cleanup.
>>>
>>> [2012-04-25 18:00:06,105]  INFO
>>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Cleaned up
>>> tenant supun.org
>>> [2012-04-25 18:18:18,202] ERROR {org.quartz.core.JobRunShell} -  Job
>>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>>> threw an unhandled Exception:
>>> java.lang.IncompatibleClassChangeError: Found class
>>> org.quartz.JobExecutionContext, but interface was expected
>>>  at
>>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>>  at
>>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>>> [2012-04-25 18:18:18,205] ERROR {org.quartz.core.ErrorLogger} -  Job
>>> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>>> threw an exception.
>>> org.quartz.SchedulerException: Job threw an unhandled exception. [See
>>> nested exception: java.lang.IncompatibleClassChangeError: Found class
>>> org.quartz.JobExecutionContext, but interface was expected]
>>> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>>>  at
>>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>>> Caused by: java.lang.IncompatibleClassChangeError: Found class
>>> org.quartz.JobExecutionContext, but interface was expected
>>>  at
>>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>>  ... 1 more
>>> [2012-04-25 18:28:08,523]  INFO
>>> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Running Summary
>>> Generator...
>>> [2012-04-25 18:28:08,533]  INFO
>>> {org.wso2.carbon.bam.core.summary.SummaryGenerationTask} -  Summary
>>> generation successful ...
>>> [2012-04-25 18:28:18,189] ERROR {org.quartz.core.JobRunShell} -  Job
>>> 08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>>> threw an unhandled Exception:
>>> java.lang.IncompatibleClassChangeError: Found class
>>> org.quartz.JobExecutionContext, but interface was expected
>>>  at
>>> org.wso2.carbon.throttling.manager.scheduling.ThrottlingJob.execute(ThrottlingJob.java:43)
>>> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>>>  at
>>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>>> [2012-04-25 18:28:18,190] ERROR {org.quartz.core.ErrorLogger} -  Job
>>> (08645889-cd00-4ecf-bbdf-d9e25808b4d2.b9abae3b-38da-495f-9f72-a51ea851c6c4
>>> threw an exception.
>>> org.quartz.SchedulerException: Job threw an unhandled exception. [See
>>> nested exception: java.lang.IncompatibleClassChangeError: Found class
>>> org.quartz.JobExecutionContext, but interface was expected]
>>> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>>>  at
>>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
>>> Caused by: java.lang.IncompatibleClassChangeError: Found class
>>> org.quartz.JobExecutionContext, but interface was expected
>>>  at
>>> org.wso2.carbon.throttling.manager.sc

Re: [Dev] carbon component plugin. Not working for custom group ID

[Chethiya Abeysinghe]

Hi Pradeep,

It seems generated pom.xml file of the service-stubs doesn't have a
groupId. So it inherits groupId from its parent,
org:wso2:carbon:service-stubs.

I'll correct the archetype of the plugin to include groupId. Meanwhile you
can add the gorupId to the service-stubs pom file manually to build it
correctly.

Thanks,
 - Chethiya

On Wed, Apr 25, 2012 at 9:56 PM, Pradeep Fernando  wrote:

> Hi,
>
> If you give a different groupID during the interactive session, the
> service stubs building fails. Can you confirm. Am i doing something wrong ?
>
> --Pradeep
>



-- 
Chethiya Abeysinghe
Software Engineer; WSO2, Inc.;  http://wso2.com/
email: cheth...@wso2.com phone: +94 777444891
blog: chethiya3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] random error in stratos as login

[Afkham Azeez]

This resource permission thing is something we've been seeing from time to
time for about a year now, but nobody has figured out what is causing this
:(

On Wed, Apr 25, 2012 at 11:24 PM, Supun Malinga  wrote:

> Hi,
>
> After a restart (randomly) getting the following error and automatically
> get logged in with the last logged in user.
> jira : https://wso2.org/jira/browse/STRATOS-2030
>
> [2012-04-25 23:10:13,020] @supun1.org [3] [WSO2 Stratos Application
> Server]ERROR {org.wso2.carbon.registry.app.ResourceServlet} -  Error
> retrieving the resource
> /_system/governance/repository/theme/admin/main.css. Resource does not
> exist at path /_system/governance/repository/theme/admin/main.css
> org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
> Resource does not exist at path
> /_system/governance/repository/theme/admin/main.css
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:532)
>  at
> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:118)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)
>  at
> org.wso2.carbon.registry.app.ResourceServlet.doGet(ResourceServlet.java:86)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:621)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
> at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:471)
>  at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:402)
> at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:329)
>  at
> org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.forward(RequestDispatcherAdaptor.java:30)
> at
> org.wso2.carbon.redirector.servlet.ui.filters.AllPagesFilter.doFilter(AllPagesFilter.java:145)
>  at
> org.eclipse.equinox.http.helper.FilterServletAdaptor.service(FilterServletAdaptor.java:37)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
>  at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:45)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
>  at
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
>  at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
> at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:139)
>  at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
>  at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>  at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:999)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:565)
>  at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1620)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> [2012-04-25 23:10:13,026] @supun1.org [3] [WSO2 Stratos Application
> Server]ERROR {org.wso2.carbon.registry.app.ResourceServlet} -  Failed to
> get resource content. Resource doe

[Dev] Supporting Secured connection to virtual host in tomcat

[Reka Thirunavukkarasu]

Hi,

Since we are going to support virtual host in tomcat, we need to provide
$subject when the user want to have secured connection. At the moment, all
our webaps are deployed under localhost.

Eg: if the virtual host is wso2app.com, when user access "
https://wso2app.com";, we should provide associated certificate of that
virtual host.
FYI: we support named base virtual host that means all hosts associates
with one ip.

The default SSL connection is installed with the CA for localhost in the
product and installed a CA for a wild card (Eg: *.Stratoslive) in stratos.
If we try to access the virtual host with this SSL connection, browser
fails to identify the CA of the virtual host. Because, at the negotiation
to present the certificate, no host name is sent to the browser rather
virtual host sends to the brwoser with the HTTP header after the
negotiation of certificate. Only if the hostname in the browser and the
certificate matches, browser would be able to continue. Otherwise, browser
warnings are displayed [1].

So, using one SSL to support multiple hosts is a limitation in tomcat. But
if we go for supporting ip based virtual host, then creating different
connectors per host basis, we would be able to provide the CA of particular
virtual host. But that wouldn't be much effective to utilize one ip for
each virtual host that needs SSL.

To overcome this issue, we would support appending a wild card always with
the hostname that needs SSL [3] similarly we did for Stratos. But that will
restrict the user having own name for a virtual host. Another solution is
to support SNI (Server Name Indication) [2], [4] in browser and server. Are
we currently supporting SNI? In such case, we can't make sure with the
browser as well.

Please share your thoughts regarding the $subject.

[1]. http://www.mail-archive.com/users@tomcat.apache.org/msg50892.html
[2]. http://www.mail-archive.com/users@tomcat.apache.org/msg93384.html
[3].
http://stackoverflow.com/questions/10173265/using-multiple-ssl-certificates-in-single-tomcat-instance
[4]. http://en.wikipedia.org/wiki/Server_Name_Indication


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