date:20151205

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC1

2015-12-05 Thread Kalpa Welivitigoda

Hi Darshana,

On Sun, Dec 6, 2015 at 10:12 AM, Darshana Gunawardana 
wrote:

> Hi,
>
> We were able to build IS 5.1.0 on top of kernel 4.4.3. But server start up
> fails in the very beginning by giving the error [1].
>
> We tried to isolate what could be the root cause on this and we observed
> there are two axiom versions (axiom_1.2.11.wso2v10, axiom_1.2.11.wso2v6)
> packed with the distribution. Without the kernel update it used to pack
> only one axiom jar (axiom_1.2.11.wso2v9).
>
> From further investigation we realized that, the issue comes with axiom
> version upgrade of kernel 4.4.3 and the reason is the version number of new
> axiom. As per our observation, OSGI version ordering takes 1.2.11.wso2v10
> as a lower version than 1.2.11.wso2v9 or 1.2.11.wso2v6.
>
> Hence when a bundle try to resolve its import packages, having
> axiom_1.2.11.wso2v10 in the distribution is not sufficient as
> 1.2.11.wso2v10 doesn't lie in the given version range like [2].
>
> To validate above, I changed to axiom version to 1.2.11.wso2v99 (which is
> greater than 1.2.11.wso2v9 or 1.2.11.wso2v6) built the kernel and built a
> IS 5.1.0 pack on top of that and it worked.
>
> This version numbering issue should be a very common case, isn't it? If so
> what is the common practice to get resolved this?
>
>
Yes, we also encountered the same when we were testing axis2
(v1.6.1-wso2v16 in staging) with kernel. The reason is the same you have
mentioned, string comparison in the qualifier in the version. So with [3]
we omitted the qualifier and sticked with only up to the patch number in
the import package version range.

We faced the same issue with neethi, to which we released a new neethi
orbit [4].

The issue and the solution is further described in [5].

I think we need to change the import package version range such that we
omit wos2* qualifier. Better to change all wso2* qualifiers in ranges, not
only for axiom.


> Until we resolve this, i guess any product would not able to test their
> functionalities on top of kernel 4.4.3.
>
> [1] https://gist.github.com/madurangasiriwardena/a4922841d8c1ad0ce037
> log4j:ERROR Could not instantiate class
> [org.wso2.carbon.utils.logging.appenders.CarbonConsoleAppender].
> java.lang.ClassNotFoundException:
> org.wso2.carbon.utils.logging.appenders.CarbonConsoleAppender cannot be
> found by org.wso2.carbon.logging_4.4.3
>
> [2] https://github.com/wso2/carbon-deployment/blob/master/pom.xml#L1340
> [1.2.11.wso2v6, 1.3.0)
>
>
[3]
https://github.com/wso2/wso2-axis2/commit/47a98a045f4ae4af7f4fc326c0d6c4963900eae7#diff-c2e120a22174607823c9e2f32c93a341R343
[4]
https://github.com/wso2/orbit/blob/master/neethi/2.0.4.wso2v5/pom.xml#L84
[5] "Please stage wso2-axiom 1.2.11-wso2v10" in engineering@

Thanks,
>
> On Fri, Dec 4, 2015 at 6:05 PM, Nipuni Perera  wrote:
>
>> Hi Devs,
>>
>> This is the RC1 release candidate of WSO2 Carbon Kernel 4.4.3.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12540
>>
>> Please download and test your products with kernel 4.4.3 RC1 and vote.
>> Vote will be open for 72 hours or as longer as needed.
>>
>> *Source and binary distribution files:*
>> http://svn.wso2.org/repos/wso2/people/nipuni/
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-162/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you
>> Carbon Team
>>
>> --
>> Nipuni Perera
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> Email: nip...@wso2.com
>> Git hub profile: https://github.com/nipuni
>> Blog : http://nipunipererablog.blogspot.com/
>> Mobile: +94 (71) 5626680
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

Kalpa Welivitigoda
Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC1

2015-12-05 Thread Darshana Gunawardana

Hi,

We were able to build IS 5.1.0 on top of kernel 4.4.3. But server start up
fails in the very beginning by giving the error [1].

We tried to isolate what could be the root cause on this and we observed
there are two axiom versions (axiom_1.2.11.wso2v10, axiom_1.2.11.wso2v6)
packed with the distribution. Without the kernel update it used to pack
only one axiom jar (axiom_1.2.11.wso2v9).

>From further investigation we realized that, the issue comes with axiom
version upgrade of kernel 4.4.3 and the reason is the version number of new
axiom. As per our observation, OSGI version ordering takes 1.2.11.wso2v10
as a lower version than 1.2.11.wso2v9 or 1.2.11.wso2v6.

Hence when a bundle try to resolve its import packages, having
axiom_1.2.11.wso2v10 in the distribution is not sufficient as
1.2.11.wso2v10 doesn't lie in the given version range like [2].

To validate above, I changed to axiom version to 1.2.11.wso2v99 (which is
greater than 1.2.11.wso2v9 or 1.2.11.wso2v6) built the kernel and built a
IS 5.1.0 pack on top of that and it worked.

This version numbering issue should be a very common case, isn't it? If so
what is the common practice to get resolved this?

Until we resolve this, i guess any product would not able to test their
functionalities on top of kernel 4.4.3.

[1] https://gist.github.com/madurangasiriwardena/a4922841d8c1ad0ce037
log4j:ERROR Could not instantiate class
[org.wso2.carbon.utils.logging.appenders.CarbonConsoleAppender].
java.lang.ClassNotFoundException:
org.wso2.carbon.utils.logging.appenders.CarbonConsoleAppender cannot be
found by org.wso2.carbon.logging_4.4.3

[2] https://github.com/wso2/carbon-deployment/blob/master/pom.xml#L1340
[1.2.11.wso2v6, 1.3.0)

Thanks,

On Fri, Dec 4, 2015 at 6:05 PM, Nipuni Perera  wrote:

> Hi Devs,
>
> This is the RC1 release candidate of WSO2 Carbon Kernel 4.4.3.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12540
>
> Please download and test your products with kernel 4.4.3 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> *Source and binary distribution files:*
> http://svn.wso2.org/repos/wso2/people/nipuni/
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-162/
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.3-RC1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you
> Carbon Team
>
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Blog : http://nipunipererablog.blogspot.com/
> Mobile: +94 (71) 5626680
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 
Regards,

*Darshana Gunawardana*Senior Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting involved in Governance Registry development - Building from sources

2015-12-05 Thread Arnaud Charpentier

Hello,

We are a group of 3 french engineering students working with Emoxa (WSO2 French 
partner) in order to develop some Governance Registry features.

In that purpose we've built the product as described in the documentation but 
we are facing this issue :
After the build is finished and successful, the shell scripts (and the whole 
bin directory) to launch the software are not existing.

These are the steps we've done :
- Cloning the source from : https://github.com/wso2/product-greg
- Installing all the prerequisites (Maven, JDK, Ant, SVN, ...)
- Building the software with "mvn clean install"

Is there anything we are missing or something we are doing wrong ?
Could you give us more details about how to setup a proper developer 
environment ?


Regards.

Arnaud CHARPENTIER

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

Re: [Dev] PPaaS Artifact Migration Tool

2015-12-05 Thread Isuru Haththotuwa

Hi Malmee and Nishadi,

Good progress in a short time!

Had a glance at the code, couple of things I noticed:

   1. log4j.properties file is available under conf directory as well as
   the resources directory. Ideally should be in conf directory.
   2. In the class OldArtifactLoader [1], the methods are throwing
   IOException in an error scenario. A better approach would be to wrap that
   with a custom exception (ex.: ArtifactLoadingException, etc.) and throw it.
   WDYT? In the class Transformation [2], this approach is followed.

[1].
https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/loader/OldArtifactLoader.java

[2].
https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/src/main/java/org/wso2/ppaas/tools/artifactmigration/Transformation.java

On Sat, Dec 5, 2015 at 10:25 PM, Gayan Gunarathne  wrote:

> Great stuff. This is a really important tool in the case of Private PaaS
> migration.
>
> As per the README[1] it mention as "Add the default values to the
> templates folder, if needed".I am not clear on that? Are we packing the
> 4.1.0 artifacts templates with the artifact migration tool? So user need to
> put the default values for those artifacts?
>
> [1]
> https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README
>
> Thanks,
> Gayan
>
> On Fri, Dec 4, 2015 at 2:51 PM, Nishadi Kirielle  wrote:
>
>> Hi All,
>>
>> Currently,we are engaged in developing an artifact migration tool to be
>> used to fetch the artifact json files from PPaaS 4.0.0 REST API endpoints
>> and convert them to be compatible with PPaaS 4.1.0. [1]
>>
>> We have implemented the conversions for the following artifacts ;
>>- auto scale policy artifacts
>>- network partition list artifacts
>>- deployment policy artifacts
>>- cartridge artifacts
>>
>> Now we are implementing the conversion of cartridge subscription
>> artifacts to application signups and domain mapping subscriptions.
>>
>> Please raise if there are any concerns regarding this work.
>>
>> [1]
>> https://github.com/nishadi/product-private-paas/tree/master/tools/migration/ppaas-artifact-converter
>>
>> Thanks
>> Nishadi
>>
>> --
>> Nishadi Kirielle
>> *Software Engineering Intern*
>> Mobile : +94 (0) 714722148
>> nish...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Gayan Gunarathne
> Technical Lead, WSO2 Inc. (http://wso2.com)
> Committer & PMC Member, Apache Stratos
> email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DSS] dss 3.5.0 Error when sending thousands of requests using request box.

2015-12-05 Thread Irham Iqbal

Hi,

I am using request box to send multiple requests as a single request to
dss. In that there are some request same type of requests[1] .In my
scenario I need to send thousands of above those in one request. When I am
sending thousands of those in a single request I am getting an
exception[2]. It says maximum open cursors exceeded. any idea on this ?

Thanks,
Iqbal

[1] 

  Iqbal

 

 

 John

 

 

 Robart

  

[2] TID: [-1234] [] [2015-12-05 18:59:22,741] ERROR
{org.wso2.carbon.dataservices.core.description.query.SQLQuery} -
ORA-01000: maximum open cursors exceeded_ (Sanitized)
{org.wso2.carbon.dataservices.core.description.query.SQLQuery}

java.sql.SQLException: ORA-01000: maximum open cursors exceeded


at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)

at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)

at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)

at
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208)

at
oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1046)

at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1336)

at
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3613)

at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3694)

at
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1354)

at
org.wso2.carbon.dataservices.core.description.query.SQLQuery.processPreNormalQuery(SQLQuery.java:753)

at
org.wso2.carbon.dataservices.core.description.query.SQLQuery.runPreQuery(SQLQuery.java:2132)

at
org.wso2.carbon.dataservices.core.description.query.Query.execute(Query.java:285)

at
org.wso2.carbon.dataservices.core.engine.CallQuery.executeElement(CallQuery.java:286)

at
org.wso2.carbon.dataservices.core.engine.OutputElement.execute(OutputElement.java:89)

at
org.wso2.carbon.dataservices.core.description.operation.Operation.execute(Operation.java:61)

at
org.wso2.carbon.dataservices.core.engine.DataService.invoke(DataService.java:583)

at
org.wso2.carbon.dataservices.core.engine.DSOMDataSource.execute(DSOMDataSource.java:96)

at
org.wso2.carbon.dataservices.core.engine.DSOMDataSource.serialize(DSOMDataSource.java:107)

at
org.wso2.carbon.dataservices.core.engine.DSOMDataSource.executeInOnly(DSOMDataSource.java:80)

at
org.wso2.carbon.dataservices.core.dispatch.SingleDataServiceRequest.processSingleRequest(SingleDataServiceRequest.java:116)

at
org.wso2.carbon.dataservices.core.dispatch.SingleDataServiceRequest.processRequest(SingleDataServiceRequest.java:67)

at
org.wso2.carbon.dataservices.core.dispatch.DataServiceRequest.dispatch(DataServiceRequest.java:344)

at
org.wso2.carbon.dataservices.core.boxcarring.RequestBox.execute(RequestBox.java:66)

at
org.wso2.carbon.dataservices.core.dispatch.RequestBoxRequest.processRequest(RequestBoxRequest.java:70)

at
org.wso2.carbon.dataservices.core.dispatch.DataServiceRequest.dispatch(DataServiceRequest.java:344)

at
org.wso2.carbon.dataservices.core.DataServiceProcessor.dispatch(DataServiceProcessor.java:41)

at
org.wso2.carbon.dataservices.core.DBInOutMessageReceiver.invokeBusinessLogic(DBInOutMessageReceiver.java:52)

at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)

at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)

at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)

at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)

at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)

at
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)

at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)

at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)

at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)

at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)

at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:

Re: [Dev] PPaaS Artifact Migration Tool

2015-12-05 Thread Gayan Gunarathne

Great stuff. This is a really important tool in the case of Private PaaS
migration.

As per the README[1] it mention as "Add the default values to the templates
folder, if needed".I am not clear on that? Are we packing the 4.1.0
artifacts templates with the artifact migration tool? So user need to put
the default values for those artifacts?

[1]
https://github.com/nishadi/product-private-paas/blob/master/tools/migration/ppaas-artifact-converter/README

Thanks,
Gayan

On Fri, Dec 4, 2015 at 2:51 PM, Nishadi Kirielle  wrote:

> Hi All,
>
> Currently,we are engaged in developing an artifact migration tool to be
> used to fetch the artifact json files from PPaaS 4.0.0 REST API endpoints
> and convert them to be compatible with PPaaS 4.1.0. [1]
>
> We have implemented the conversions for the following artifacts ;
>- auto scale policy artifacts
>- network partition list artifacts
>- deployment policy artifacts
>- cartridge artifacts
>
> Now we are implementing the conversion of cartridge subscription
> artifacts to application signups and domain mapping subscriptions.
>
> Please raise if there are any concerns regarding this work.
>
> [1]
> https://github.com/nishadi/product-private-paas/tree/master/tools/migration/ppaas-artifact-converter
>
> Thanks
> Nishadi
>
> --
> Nishadi Kirielle
> *Software Engineering Intern*
> Mobile : +94 (0) 714722148
> nish...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>

-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC1

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.3 RC1

[Dev] Getting involved in Governance Registry development - Building from sources

Re: [Dev] PPaaS Artifact Migration Tool

[Dev] [DSS] dss 3.5.0 Error when sending thousands of requests using request box.

Re: [Dev] PPaaS Artifact Migration Tool

6 matches

Site Navigation

Mail list logo

Footer information