[Dev] Merge changes to PEP Proxy - https://wso2.org/jira/browse/IDENTITY-4987

[Lahiru Cooray]

Hi,
Could you please review and merge the PR [1]

[1]
https://github.com/wso2-extensions/identity-agent-entitlement-proxy/pull/15

-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.9 RC2

[Kasun Bandara]

Hi Kalpa,

When we running the IS integration tests, we encountered the following
issue upon restarting the sever. This is reproducible with the following
sequence in a fresh pack which built top of kernel 4.4.9.

1) Start up the server
2) Shutdown the server
3) Restart the server

2016-08-25 11:31:35,677] ERROR {org.wso2.carbon.user.core.util.DatabaseUtil}
-  Database Error - Unique index or primary key violation: "PRIMARY KEY ON
.PAGE_INDEX"; SQL statement:
ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
[23505-176]
org.h2.jdbc.JdbcSQLException: Unique index or primary key violation:
"PRIMARY KEY ON .PAGE_INDEX"; SQL statement:
ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
[23505-176]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
at org.h2.message.DbException.get(DbException.java:178)
at org.h2.message.DbException.get(DbException.java:154)
at org.h2.index.PageDataIndex.getNewDuplicateKeyException(
PageDataIndex.java:166)
at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
at org.h2.store.PageStore.addMeta(PageStore.java:1808)
at org.h2.index.PageBtreeIndex.(PageBtreeIndex.java:64)
at org.h2.table.RegularTable.addIndex(RegularTable.java:235)
at org.h2.command.ddl.AlterTableAddConstraint.createIndex(
AlterTableAddConstraint.java:280)
at org.h2.command.ddl.AlterTableAddConstraint.tryUpdate(
AlterTableAddConstraint.java:205)
at org.h2.command.ddl.AlterTableAddConstraint.update(
AlterTableAddConstraint.java:73)
at org.h2.engine.MetaRecord.execute(MetaRecord.java:59)
at org.h2.engine.Database.open(Database.java:719)
at org.h2.engine.Database.openDatabase(Database.java:260)
at org.h2.engine.Database.(Database.java:254)
at org.h2.engine.Engine.openSession(Engine.java:57)
at org.h2.engine.Engine.openSession(Engine.java:164)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:142)
at org.h2.engine.Engine.createSession(Engine.java:125)
at org.h2.engine.Engine.createSession(Engine.java:27)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(
SessionRemote.java:331)
at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:107)
at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:91)
at org.h2.Driver.connect(Driver.java:74)
at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(
PooledConnection.java:278)
at org.apache.tomcat.jdbc.pool.PooledConnection.connect(
PooledConnection.java:182)
at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(
ConnectionPool.java:701)
at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
ConnectionPool.java:635)
at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(
ConnectionPool.java:188)
at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(
DataSourceProxy.java:127)
at org.wso2.carbon.user.core.claim.dao.ClaimDAO.
getDialectCount(ClaimDAO.java:158)
at org.wso2.carbon.user.core.common.DefaultRealm.
populateProfileAndClaimMaps(DefaultRealm.java:448)
at org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRealm.java:124)
at org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(
DefaultRealmService.java:263)
at org.wso2.carbon.user.core.common.DefaultRealmService.<
init>(DefaultRealmService.java:100)
at org.wso2.carbon.user.core.common.DefaultRealmService.<
init>(DefaultRealmService.java:113)
at org.wso2.carbon.user.core.internal.Activator.
startDeploy(Activator.java:68)
at org.wso2.carbon.user.core.internal.BundleCheckActivator.
start(BundleCheckActivator.java:61)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(
BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.
startActivator(BundleContextImpl.java:702)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(
BundleContextImpl.java:683)
at org.eclipse.osgi.framework.internal.core.BundleHost.
startWorker(BundleHost.java:381)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.
resume(AbstractBundle.java:390)
at org.eclipse.osgi.framework.internal.core.Framework.
resumeBundle(Framework.java:1176)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(
StartLevelManager.java:559)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(
StartLevelManager.java:544)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(
StartLevelManager.java:457)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.
doSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(
StartLevelManager.java:438)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(
StartLevelManager.java:1)
at org.ecli

Re: [Dev] My GSoC experience - GSoC students please read!

[Dinanjana Gunaratne]

Hello all,
Since this thread is discussing GSOC experience with WSO2 , I thought of
sharing mine as well. First of all this is my 1st GSOC event. I am a final
year undergraduate. My proposal for "Proposal 7: Improve production system
debugging capabilities of WSO2 ESB" got selected for this year GSOC
program. I have being working on the project for last 3 months and my
mentors were pretty helpful. True they are sometimes very busy with their
work but they are doing a full time job along with mentoring. So I guess we
should cut some slack for them. I too was pretty busy most of the time
since I had to mange both university work and project work together. I
guess communication between the student and the mentor is pretty vital
since it helps understand the situation of student as well as mentor. That
has been the case for me for this whole period. So with respect to my
experience, the GSOC experience offered by WSO2 is good.

On Tue, Aug 23, 2016 at 12:43 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Thanks Imesh.
>
> Sincerely appreciate the response. The same guide also talks about
> MENTORING [1]. Specifically and I quote
>
> "*Don't Be That Guy*: No one likes dictators.  Work with your student on
> the development of expectations, rather then barking out orders."
>
> On my last call with Chamila, this is exactly what happened. He literally
> shouted at me and threatened to fail me on the project. Forget mentorship,
> is this even professional? I sent you PM to address this situation but you
> never cared to reply it. You were creating Github issues even after that,
> but you simply ignored my email.
>
> The goal of the project never included K8 and I have evidence to support
> it (design doc, project proposal and community bonding conversation).
> However, when community asked about it, I started working on addressing
> that, I was very close to complete it. I was pretty much done with that
> work, when I started getting these chats and issues from Chamila about
> changing names and params and so many things that were completely out of
> the scope considering the timeline. The code in question had been in github
> for about 2 months and no one ever cared to bring it up until 2 days before
> the deadline. Is this how software projects are managed ?
>
> I was always willing to work on everything, and was very interested to
> work even after GSoC period. My biggest problem is the way Chamila talked
> to me, it was completely unprofessional and disrespectful.
>
> Anyways, there is no point arguing over it, since at some point its going
> to become my voice against your voice and nothing productive will come out
> of it.  I just hope that I will receive an honest evaluation of my work!
>
> [1]. http://write.flossmanuals.net/gsoc-mentoring/setting-expectations/
>
> On Mon, Aug 22, 2016 at 7:59 PM, Imesh Gunaratne  wrote:
>
>> Hi Abhishek,
>>
>> Thanks for your feedback! We are really sorry to hear what you
>> experienced.
>>
>> We at WSO2, participated in GSoC for many years now with the intention of
>> giving students opportunities to contribute to open source projects for the
>> benefit of the entire community. This allows students to learn how open
>> source communities work, new technologies related to their academic
>> pursuits, give exposure to real world software development processes, etc.
>> In the open source world, there is no labour concept, no one is paid for
>> doing open source work. If someone is willing to contribute, they are most
>> welcome to share their ideas and send contributions. GSoC program is trying
>> to give opportunities for students to experience this and be a part of it
>> [3]. If you do not like that idea, you should have opted out of this
>> project at the very early stages.
>>
>> The GSoC Student Guide [4] has explained clearly how students should work
>> with mentors and what to expect from them. Mentors are voluntarily
>> contributing their time to GSoC projects with the intention of adding value
>> to open source projects. They do this while working on many other things.
>> Therefore delays in meetings and such occurrences may happen due to
>> unavoidable circumstances. Please accept our apologies for any
>> inconveniences caused in that regard. Please feel free to refer [5], [6],
>> [7], [8], [9], [10] on how WSO2 community and your mentors have appreciated
>> your contributions then and there.
>>
>> Changing requirements is part and parcel of software projects and
>> software world. However we believe that we did our very best to keep the
>> high level requirements of the project fixed. On high level, the main goal
>> of this project was to implement a test framework to invoke bash scripts
>> provided in WSO2 Dockerfiles and K8S Artifacts repositories for verifying
>> WSO2 container images. As we believe that is a straightforward goal and
>> nothing much need to be changed at the middle of the project except for
>> refinements.
>>
>> [3] http://write.flo

Re: [Dev] Installing APIM features to IS 5.2.0 beta2 pack says No features to be installed

[Jayanga Dissanayake]

Hi Abimaran,

The carbon-feature-repository is a common repository contributed by all the
product people, and there is a considerable amount of effort going on to
keep it cleaner as possible. PR verification is one part of it. The reason
for your PR[1] to get delayed is basically, it doesn't show up in the
online Github diff, as it has a considerable amount of commits. which
needed some additional effort to go one by one and identify the issues
(which I replied earlier), which caused the verification harder and time
consuming. Please refer PR[50] which is a clean PR, which makes the
verification much faster and easier. The person who verifies it can
identify the changes just looking at the diff.

We expect products teams to verify the changes first and send a clean PR,
So, it won't bounce back and forth for corrections.

[1] https://github.com/wso2/carbon-feature-repository/pull/49/files
[2] https://github.com/wso2/carbon-feature-repository/pull/50/files

Thanks,
Jayanga.

*Jayanga Dissanayake*
Associate Technical Lead
WSO2 Inc. - http://wso2.com/
lean . enterprise . middleware
email: jaya...@wso2.com
mobile: +94772207259


On Thu, Aug 25, 2016 at 12:08 PM, Abimaran Kugathasan 
wrote:

> Hi Jayanga,
>
> I have reordered the features based on alphabet, also, fixed the merge
> conflicts.
>
> Can you please merge it soon?
>
> PS : Why can't we merge the PRs based on when they sent? I had nearly more
> than 70 merge conflicts to resolve since PR 50 was merged before PR 49
> merged.
>
> On Thu, Aug 25, 2016 at 11:23 AM, Jayanga Dissanayake 
> wrote:
>
>> Hi Abimaran,
>>
>> In your PR, following entries are in wrong places.
>> 1. org.wso2.carbon.apimgt:org.wso2.apimgt.publisher.category.feature
>> 2. org.wso2.carbon.apimgt:org.wso2.apimgt.store.category.feature
>>
>> Please correct the entries and resend the PR.
>>
>> Thanks,
>> Jayanga.
>>
>> *Jayanga Dissanayake*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.com/
>> lean . enterprise . middleware
>> email: jaya...@wso2.com
>> mobile: +94772207259
>> 
>>
>> On Thu, Aug 25, 2016 at 10:38 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> [Adding Jayanga]
>>>
>>> Hi Jayanga,
>>>
>>> Can you look into this?
>>>
>>> Regards,
>>> Nira
>>>
>>> On Thu, Aug 25, 2016 at 10:35 AM, Abimaran Kugathasan >> > wrote:
>>>
 Hi Kavitha,

 API Key Manager 5.0.3 isn't compatible with IS 5.2.0. I have sent PR
 [1] with relevant features of APIM 2.0 which yet to be merged.

 @Niranjan,

 Can you please merge it soon possible?

 [1] : https://github.com/wso2/carbon-feature-repository/pull/49

 On Thu, Aug 25, 2016 at 10:24 AM, Kavitha Subramaniyam <
 kavi...@wso2.com> wrote:

> Hi Harsha/ Darshana,
>
> The reason I tried 5.0.3 feature is the given repository[1] listed
> only the 'API Key Manager 5.0.3' feature after added to IS server. Do I
> need to get the repo from different location?
>
> [1] http://product-dist.wso2.com/p2/carbon/releases/wilkes/
>
> Thanks,
>
> On Thu, Aug 25, 2016 at 7:21 AM, Darshana Gunawardana <
> darsh...@wso2.com> wrote:
>
>> Hi Harsha,
>>
>> Sorry, my understanding was APIM 2.0.0 KM version is 5.0.3. As per
>> your above reply it seems to be 6.0.4.
>>
>> IS 5.2.0 should compatible with APIM 2.0.0 for KM installation. So we
>> should try KM 6.0.4 feature installation in IS 5.2.0. @Kavitha : Can
>> you please try that.
>>
>> Thanks,
>>
>> On Wed, Aug 24, 2016 at 11:47 PM, Harsha Kumara 
>> wrote:
>>
>>> Hi Darshana,
>>>
>>> It was due to version ranges of dependent feature that we specified
>>> in the key manager features doesn't match with feature version in IS
>>> 5.2.0-beta. We also haven't had a deep look on installing 5.0.3 version 
>>> on
>>> IS 5.2.0 releases.
>>>
>>> @kavitha Any reason we going to try 5.0.3 features with IS 5.2.0
>>> beta instead of trying latest APIM feature versions which is 6.0.4. 
>>> During
>>> the latest release we installed 6.0.4 features on IS 5.2.0 release.
>>>
>>> Thanks,
>>> Harsha
>>>
>>> On Wed, Aug 24, 2016 at 11:10 PM, Darshana Gunawardana <
>>> darsh...@wso2.com> wrote:
>>>
 Hi Harsha,

 Can you bit explain what was the issue?

 Thanks,

 On Wed, Aug 24, 2016 at 11:03 PM, Harsha Kumara 
 wrote:

> Hi Kavitha,
>
> We won't be able to install 5.0.3 features on top of IS 5.2.0-beta
> due to dependency issues.
>
> Thanks,
> Harsha
>
> On Wed, Aug 24, 2016 at 5:52 PM, Kavitha Subramaniyam <
> kavi...@wso2.com> wrote:
>
>> Thanks Kasun.
>>
>> On Wed, Aug 24, 2016 at 5:50 PM, Kavitha Subramaniyam <
>> kavi...@wso2.com> wrot

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.9 RC2

[Kalpa Welivitigoda]

Hi Kasun,

We have updated h2 database from 1.2.140 to 1.3.176 and that would be the
root cause for the exception. We need to dig a bit and look into the schema
restrictions introduced in h2.

@Manuri, thanks for the clarification.
@Madhawa, sorry I misunderstood your point at the first place.

On Thu, Aug 25, 2016 at 12:47 PM, Kasun Bandara  wrote:

> Hi Kalpa,
>
> When we running the IS integration tests, we encountered the following
> issue upon restarting the sever. This is reproducible with the following
> sequence in a fresh pack which built top of kernel 4.4.9.
>
> 1) Start up the server
> 2) Shutdown the server
> 3) Restart the server
>
> 2016-08-25 11:31:35,677] ERROR {org.wso2.carbon.user.core.util.DatabaseUtil}
> -  Database Error - Unique index or primary key violation: "PRIMARY KEY ON
> .PAGE_INDEX"; SQL statement:
> ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
> PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
> PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
> [23505-176]
> org.h2.jdbc.JdbcSQLException: Unique index or primary key violation:
> "PRIMARY KEY ON .PAGE_INDEX"; SQL statement:
> ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
> PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
> PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
> [23505-176]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
> at org.h2.message.DbException.get(DbException.java:178)
> at org.h2.message.DbException.get(DbException.java:154)
> at org.h2.index.PageDataIndex.getNewDuplicateKeyException(PageD
> ataIndex.java:166)
> at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
> at org.h2.store.PageStore.addMeta(PageStore.java:1808)
> at org.h2.index.PageBtreeIndex.(PageBtreeIndex.java:64)
> at org.h2.table.RegularTable.addIndex(RegularTable.java:235)
> at org.h2.command.ddl.AlterTableAddConstraint.createIndex(Alter
> TableAddConstraint.java:280)
> at org.h2.command.ddl.AlterTableAddConstraint.tryUpdate(AlterTa
> bleAddConstraint.java:205)
> at org.h2.command.ddl.AlterTableAddConstraint.update(AlterTable
> AddConstraint.java:73)
> at org.h2.engine.MetaRecord.execute(MetaRecord.java:59)
> at org.h2.engine.Database.open(Database.java:719)
> at org.h2.engine.Database.openDatabase(Database.java:260)
> at org.h2.engine.Database.(Database.java:254)
> at org.h2.engine.Engine.openSession(Engine.java:57)
> at org.h2.engine.Engine.openSession(Engine.java:164)
> at org.h2.engine.Engine.createSessionAndValidate(Engine.java:142)
> at org.h2.engine.Engine.createSession(Engine.java:125)
> at org.h2.engine.Engine.createSession(Engine.java:27)
> at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionR
> emote.java:331)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:107)
> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:91)
> at org.h2.Driver.connect(Driver.java:74)
> at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(
> PooledConnection.java:278)
> at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledC
> onnection.java:182)
> at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(
> ConnectionPool.java:701)
> at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
> ConnectionPool.java:635)
> at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(Con
> nectionPool.java:188)
> at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(Da
> taSourceProxy.java:127)
> at org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount
> (ClaimDAO.java:158)
> at org.wso2.carbon.user.core.common.DefaultRealm.populateProfil
> eAndClaimMaps(DefaultRealm.java:448)
> at org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRe
> alm.java:124)
> at org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(
> DefaultRealmService.java:263)
> at org.wso2.carbon.user.core.common.DefaultRealmService.(
> DefaultRealmService.java:100)
> at org.wso2.carbon.user.core.common.DefaultRealmService.(
> DefaultRealmService.java:113)
> at org.wso2.carbon.user.core.internal.Activator.startDeploy(
> Activator.java:68)
> at org.wso2.carbon.user.core.internal.BundleCheckActivator.star
> t(BundleCheckActivator.java:61)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(
> BundleContextImpl.java:711)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s
> tartActivator(BundleContextImpl.java:702)
> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(
> BundleContextImpl.java:683)
> at org.eclipse.osgi.framework.internal.core.BundleHost.startWor
> ker(BundleHost.java:381)
> at org.eclipse.osgi.framework.internal.core.AbstractBundle.resu
> me(AbstractBundle.java:390)
> at org.eclipse.osgi.framework.internal.core.Framework.resumeBun
> dle(Framework.java:1176)
> at org.eclipse.osgi.framework.internal.core.StartLevelManager.r
> esumeBundles(StartLevelManager.java:559)
>

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Vinod Kavinda]

Hi,
I verified,

   - Substitution feature.
   - BPMN Explorer.
   - Human Task Explorer.
   - Migration from 3.5.1.

[+] Stable - go ahead and release.

Regards,
Vinod

On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera  wrote:

> Hi All,
>
> This is the 1st Release Candidate of WSO2 Business Process Server 3.6.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> *Source and distribution*
>
> *Run-time* : https://github.com/wso2/product-bps/releases/tag/v3.6.0-RC1
> *Tooling*  : https://github.com/wso2/devstudio-tooling-bps/
> releases/tag/Released-release-3.6.0-RC1-2016-08-24-114818
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> ~ WSO2 BPS Team ~
>
> --
> Milinda Perera
> Senior Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>


-- 
Vinod Kavinda
Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

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

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Milinda Perera]

Hi APIM and IS team,

Could you please tryout your features with BPS with 3.6.0 RC1.

Thanks,
Milinda

On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda  wrote:

> Hi,
> I verified,
>
>- Substitution feature.
>- BPMN Explorer.
>- Human Task Explorer.
>- Migration from 3.5.1.
>
> [+] Stable - go ahead and release.
>
> Regards,
> Vinod
>
> On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera  wrote:
>
>> Hi All,
>>
>> This is the 1st Release Candidate of WSO2 Business Process Server 3.6.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> *Source and distribution*
>>
>> *Run-time* : https://github.com/wso2/product-bps/releases/tag/v3.6.0-RC1
>> *Tooling*  : https://github.com/wso2/devstudio-tooling-bps/releases/tag/
>> Released-release-3.6.0-RC1-2016-08-24-114818
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> ~ WSO2 BPS Team ~
>>
>> --
>> Milinda Perera
>> Senior Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>
>
> --
> Vinod Kavinda
> Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>


-- 
Milinda Perera
Senior Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.9 RC2

[Kalpa Welivitigoda]

Hi Kasun,

I came across [1] which matches with your observations with IS (Starting,
shutdown and restart the server). According to [1] this is a bug in 1.3.176
and is fixed in 1.4.179 Beta [2].

[1] https://groups.google.com/forum/#!topic/h2-database/5LZlZ_jC4QI
[2] http://www.h2database.com/html/changelog.html


On Thu, Aug 25, 2016 at 2:58 PM, Kalpa Welivitigoda  wrote:

> Hi Kasun,
>
> We have updated h2 database from 1.2.140 to 1.3.176 and that would be the
> root cause for the exception. We need to dig a bit and look into the schema
> restrictions introduced in h2.
>
> @Manuri, thanks for the clarification.
> @Madhawa, sorry I misunderstood your point at the first place.
>
> On Thu, Aug 25, 2016 at 12:47 PM, Kasun Bandara  wrote:
>
>> Hi Kalpa,
>>
>> When we running the IS integration tests, we encountered the following
>> issue upon restarting the sever. This is reproducible with the following
>> sequence in a fresh pack which built top of kernel 4.4.9.
>>
>> 1) Start up the server
>> 2) Shutdown the server
>> 3) Restart the server
>>
>> 2016-08-25 11:31:35,677] ERROR {org.wso2.carbon.user.core.util.DatabaseUtil}
>> -  Database Error - Unique index or primary key violation: "PRIMARY KEY ON
>> .PAGE_INDEX"; SQL statement:
>> ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
>> PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
>> PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
>> [23505-176]
>> org.h2.jdbc.JdbcSQLException: Unique index or primary key violation:
>> "PRIMARY KEY ON .PAGE_INDEX"; SQL statement:
>> ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
>> PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
>> PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
>> [23505-176]
>> at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
>> at org.h2.message.DbException.get(DbException.java:178)
>> at org.h2.message.DbException.get(DbException.java:154)
>> at org.h2.index.PageDataIndex.getNewDuplicateKeyException(PageD
>> ataIndex.java:166)
>> at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
>> at org.h2.store.PageStore.addMeta(PageStore.java:1808)
>> at org.h2.index.PageBtreeIndex.(PageBtreeIndex.java:64)
>> at org.h2.table.RegularTable.addIndex(RegularTable.java:235)
>> at org.h2.command.ddl.AlterTableAddConstraint.createIndex(Alter
>> TableAddConstraint.java:280)
>> at org.h2.command.ddl.AlterTableAddConstraint.tryUpdate(AlterTa
>> bleAddConstraint.java:205)
>> at org.h2.command.ddl.AlterTableAddConstraint.update(AlterTable
>> AddConstraint.java:73)
>> at org.h2.engine.MetaRecord.execute(MetaRecord.java:59)
>> at org.h2.engine.Database.open(Database.java:719)
>> at org.h2.engine.Database.openDatabase(Database.java:260)
>> at org.h2.engine.Database.(Database.java:254)
>> at org.h2.engine.Engine.openSession(Engine.java:57)
>> at org.h2.engine.Engine.openSession(Engine.java:164)
>> at org.h2.engine.Engine.createSessionAndValidate(Engine.java:142)
>> at org.h2.engine.Engine.createSession(Engine.java:125)
>> at org.h2.engine.Engine.createSession(Engine.java:27)
>> at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionR
>> emote.java:331)
>> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:107)
>> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:91)
>> at org.h2.Driver.connect(Driver.java:74)
>> at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(
>> PooledConnection.java:278)
>> at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledC
>> onnection.java:182)
>> at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(
>> ConnectionPool.java:701)
>> at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
>> ConnectionPool.java:635)
>> at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(Con
>> nectionPool.java:188)
>> at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(Da
>> taSourceProxy.java:127)
>> at org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount
>> (ClaimDAO.java:158)
>> at org.wso2.carbon.user.core.common.DefaultRealm.populateProfil
>> eAndClaimMaps(DefaultRealm.java:448)
>> at org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRe
>> alm.java:124)
>> at org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(
>> DefaultRealmService.java:263)
>> at org.wso2.carbon.user.core.common.DefaultRealmService.(
>> DefaultRealmService.java:100)
>> at org.wso2.carbon.user.core.common.DefaultRealmService.(
>> DefaultRealmService.java:113)
>> at org.wso2.carbon.user.core.internal.Activator.startDeploy(Act
>> ivator.java:68)
>> at org.wso2.carbon.user.core.internal.BundleCheckActivator.star
>> t(BundleCheckActivator.java:61)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(
>> BundleContextImpl.java:711)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s
>> tartActivator(BundleContextImpl.java:702)
>> at org.ecl

[Dev] Hieradata location for puppet modules

[Anuruddha Liyanarachchi]

Hi Devs,

We are in the process of restructuring and splitting the puppet modules per
product. As per the initial discussions, we have created separate
repositories per product puppet module and one common repository for puppet
base module.

In order to publish puppet modules to puppet forge, we have decoupled
hieradata from puppet modules using profiles. Now the puppet modules are
capable of running without hieradata for the default profile.

However, it is easier to do deployment using hieradata. The intention of
this mail is to discuss and finalize hieradata location.

Appreciate your feedback on selecting an available option.

Following are the available options:

*1. Use one repository to keep all product hieradata.*
Pros:
- Easy to manage since all the hieradata are in one place.
- No data duplication

Cons:
- Releasing hieradata with a product is not possible.
- Difficult to track changes.


*2. Keep hieradata with platform specific artifact repositories.
(kubernetes, mesos )*
Pros:
- Hieradata can be released with a product.

Cons:
- Possible data duplication.
- Hieradata is a part of puppet and it is not related to mesos or kubernetes
- Have to create repositories to store default hieradata.


*3. Create separate repositories per product to store hieradata. *
Pros:
- Product level hieradata separation.
- Easier to release and track changes.

Cons:
- No of repositories are high.
- User experience will be not good as users will have to clone from
multiple locations.



*4. Keep hieradata in the product puppet module repos with
.pmtignore file. *Pros:
- Minimum changes required.
- Can be released with product puppet modules.

Cons:
- Most of the puppet repos don't contain hieradata
- Puppet recommends keeping  hieradata separately from modules.



-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error in AM 2.0 gateway

[Abimaran Kugathasan]

Hi Supun,

Same issue was reported here [1] as well, Can you try what Bhathiya has
responded or separate Key Manager from Store?

[1] :
http://stackoverflow.com/questions/39101064/error-on-api-manager-2-0-0-gateway-worker-on-start-up

On Mon, Aug 22, 2016 at 12:50 PM, Supun Malinga  wrote:

> Diagram :
> ​
>  am-2.0-pattern-4.png
> 
> ​
>
> On Mon, Aug 22, 2016 at 12:47 PM, Supun Malinga  wrote:
>
>> Hi,
>>
>> Getting the following exception in gateway worker. Any idea what could be
>> causing this ?.
>> This is in a distributed cluster with store and KM in same node.
>> I can provide any configurations required..
>>
>> ​
>>  am-2.0-pattern-4
>> 
>> ​
>>
>>
>> gateway-worker | [2016-08-16 09:35:09,422]  INFO - API Destroying
>> API: _WSO2AMTokenAPI_
>> gateway-worker | [2016-08-16 09:35:09,426]  INFO - API Initializing
>> API: _WSO2AMUserInfoAPI_
>> gateway-worker | [2016-08-16 09:35:09,426]  INFO - DependencyTracker
>> API : _WSO2AMUserInfoAPI_ was updated from the Synapse configuration
>> successfully
>> gateway-worker | [2016-08-16 09:35:09,426]  INFO - APIDeployer API:
>> _WSO2AMUserInfoAPI_ has been updated from the file:
>> /mnt/wso2am-2.0.0/repository/deployment/server/synapse-confi
>> gs/default/api/_UserInfoAPI_.xml
>> gateway-worker | [2016-08-16 09:35:11,427]  INFO - API Destroying
>> API: _WSO2AMUserInfoAPI_
>> gateway-worker | [2016-08-16 09:35:25,783] ERROR -
>> KeyTemplateRetriever Exception when retrieving throttling data from remote
>> endpoint
>> gateway-worker | Unexpected character (<) at position 0.
>> gateway-worker | at org.json.simple.parser.Yylex.yylex(Unknown
>> Source)
>> gateway-worker | at org.json.simple.parser.JSONParser.nextToken(Unknown
>> Source)
>> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
>> Source)
>> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
>> Source)
>> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
>> Source)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.KeyTemplateRetriever.retrieveKeyTemplateDat
>> a(KeyTemplateRetriever.java:100)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
>> bService(KeyTemplateRetriever.java:111)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
>> gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
>> gateway-worker | at java.util.TimerThread.run(Timer.java:505)
>> gateway-worker | Exception in thread "Timer-6"
>> java.lang.NullPointerException
>> gateway-worker | at java.util.Arrays$ArrayList.> it>(Arrays.java:2842)
>> gateway-worker | at java.util.Arrays.asList(Arrays.java:2828)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
>> bService(KeyTemplateRetriever.java:111)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
>> gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
>> gateway-worker | at java.util.TimerThread.run(Timer.java:505)
>> gateway-worker | Exception in thread "Timer-5"
>> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
>> Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
>> gateway-worker | at com.google.gson.internal.bind.
>> ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdap
>> terFactory.java:221)
>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:861)
>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:826)
>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:775)
>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:747)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.BlockingConditionRetriever.retrieveBlockCon
>> ditionsData(BlockingConditionRetriever.java:96)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.BlockingConditionRetriever.loadBlockingCond
>> itionsFromWebService(BlockingConditionRetriever.java:105)
>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>> .throttling.util.BlockingConditionRetriever.run(BlockingCond
>> itionRetriever.java:51)
>> gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
>> gateway-worker | at java.util.TimerThread.run(Timer.java:505)
>> gateway-worker | Caused by: java.lang.IllegalStateException:
>> Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
>> gateway-worker | at com.google.gson.stream.JsonRea
>> der.beginObject(JsonReader.java:388)
>> gateway-

Re: [Dev] Error in AM 2.0 gateway

[Harsha Kumara]

Hi Supun,

Did you setup the cluster with old throttling implementation? If it's with
new throttling implementation, please check your key manager
configuration.  Basically gateway try to fetch initial block conditions
details from the key manager.

Thanks,
Harsha

On Thu, Aug 25, 2016 at 3:58 PM, Abimaran Kugathasan 
wrote:

> Hi Supun,
>
> Same issue was reported here [1] as well, Can you try what Bhathiya has
> responded or separate Key Manager from Store?
>
> [1] : http://stackoverflow.com/questions/39101064/error-on-
> api-manager-2-0-0-gateway-worker-on-start-up
>
> On Mon, Aug 22, 2016 at 12:50 PM, Supun Malinga  wrote:
>
>> Diagram :
>> ​
>>  am-2.0-pattern-4.png
>> 
>> ​
>>
>> On Mon, Aug 22, 2016 at 12:47 PM, Supun Malinga  wrote:
>>
>>> Hi,
>>>
>>> Getting the following exception in gateway worker. Any idea what could
>>> be causing this ?.
>>> This is in a distributed cluster with store and KM in same node.
>>> I can provide any configurations required..
>>>
>>> ​
>>>  am-2.0-pattern-4
>>> 
>>> ​
>>>
>>>
>>> gateway-worker | [2016-08-16 09:35:09,422]  INFO - API Destroying
>>> API: _WSO2AMTokenAPI_
>>> gateway-worker | [2016-08-16 09:35:09,426]  INFO - API Initializing
>>> API: _WSO2AMUserInfoAPI_
>>> gateway-worker | [2016-08-16 09:35:09,426]  INFO - DependencyTracker
>>> API : _WSO2AMUserInfoAPI_ was updated from the Synapse configuration
>>> successfully
>>> gateway-worker | [2016-08-16 09:35:09,426]  INFO - APIDeployer API:
>>> _WSO2AMUserInfoAPI_ has been updated from the file:
>>> /mnt/wso2am-2.0.0/repository/deployment/server/synapse-confi
>>> gs/default/api/_UserInfoAPI_.xml
>>> gateway-worker | [2016-08-16 09:35:11,427]  INFO - API Destroying
>>> API: _WSO2AMUserInfoAPI_
>>> gateway-worker | [2016-08-16 09:35:25,783] ERROR -
>>> KeyTemplateRetriever Exception when retrieving throttling data from remote
>>> endpoint
>>> gateway-worker | Unexpected character (<) at position 0.
>>> gateway-worker | at org.json.simple.parser.Yylex.yylex(Unknown
>>> Source)
>>> gateway-worker | at org.json.simple.parser.JSONParser.nextToken(Unknown
>>> Source)
>>> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
>>> Source)
>>> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
>>> Source)
>>> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
>>> Source)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.KeyTemplateRetriever.retrieveKeyTemplateDat
>>> a(KeyTemplateRetriever.java:100)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
>>> bService(KeyTemplateRetriever.java:111)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
>>> gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
>>> gateway-worker | at java.util.TimerThread.run(Timer.java:505)
>>> gateway-worker | Exception in thread "Timer-6"
>>> java.lang.NullPointerException
>>> gateway-worker | at java.util.Arrays$ArrayList.>> it>(Arrays.java:2842)
>>> gateway-worker | at java.util.Arrays.asList(Arrays.java:2828)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
>>> bService(KeyTemplateRetriever.java:111)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
>>> gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
>>> gateway-worker | at java.util.TimerThread.run(Timer.java:505)
>>> gateway-worker | Exception in thread "Timer-5"
>>> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
>>> Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
>>> gateway-worker | at com.google.gson.internal.bind.
>>> ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdap
>>> terFactory.java:221)
>>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:861)
>>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:826)
>>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:775)
>>> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:747)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.BlockingConditionRetriever.retrieveBlockCon
>>> ditionsData(BlockingConditionRetriever.java:96)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.BlockingConditionRetriever.loadBlockingCond
>>> itionsFromWebService(BlockingConditionRetriever.java:105)
>>> gateway-worker | at org.wso2.carbon.apimgt.gateway
>>> .throttling.util.BlockingConditionRetriev

Re: [Dev] Error in AM 2.0 gateway

[Supun Malinga]

Hi,

Actually I resolved the issue. It was due to throttle data war not been
deployed at the time server try to retrieve data. Fix was done by delaying
server starting time + depsync improvements (deleting apps from workers to
reduce startup time and avoid redeployment when depsync kick in).

On Thu, Aug 25, 2016 at 4:34 PM, Harsha Kumara  wrote:

> Hi Supun,
>
> Did you setup the cluster with old throttling implementation? If it's with
> new throttling implementation, please check your key manager
> configuration.  Basically gateway try to fetch initial block conditions
> details from the key manager.
>
> Thanks,
> Harsha
>
> On Thu, Aug 25, 2016 at 3:58 PM, Abimaran Kugathasan 
> wrote:
>
>> Hi Supun,
>>
>> Same issue was reported here [1] as well, Can you try what Bhathiya has
>> responded or separate Key Manager from Store?
>>
>> [1] : http://stackoverflow.com/questions/39101064/error-on-api-
>> manager-2-0-0-gateway-worker-on-start-up
>>
>> On Mon, Aug 22, 2016 at 12:50 PM, Supun Malinga  wrote:
>>
>>> Diagram :
>>> ​
>>>  am-2.0-pattern-4.png
>>> 
>>> ​
>>>
>>> On Mon, Aug 22, 2016 at 12:47 PM, Supun Malinga  wrote:
>>>
 Hi,

 Getting the following exception in gateway worker. Any idea what could
 be causing this ?.
 This is in a distributed cluster with store and KM in same node.
 I can provide any configurations required..

 ​
  am-2.0-pattern-4
 
 ​


 gateway-worker | [2016-08-16 09:35:09,422]  INFO - API Destroying
 API: _WSO2AMTokenAPI_
 gateway-worker | [2016-08-16 09:35:09,426]  INFO - API Initializing
 API: _WSO2AMUserInfoAPI_
 gateway-worker | [2016-08-16 09:35:09,426]  INFO -
 DependencyTracker API : _WSO2AMUserInfoAPI_ was updated from the Synapse
 configuration successfully
 gateway-worker | [2016-08-16 09:35:09,426]  INFO - APIDeployer API:
 _WSO2AMUserInfoAPI_ has been updated from the file:
 /mnt/wso2am-2.0.0/repository/deployment/server/synapse-confi
 gs/default/api/_UserInfoAPI_.xml
 gateway-worker | [2016-08-16 09:35:11,427]  INFO - API Destroying
 API: _WSO2AMUserInfoAPI_
 gateway-worker | [2016-08-16 09:35:25,783] ERROR -
 KeyTemplateRetriever Exception when retrieving throttling data from remote
 endpoint
 gateway-worker | Unexpected character (<) at position 0.
 gateway-worker | at org.json.simple.parser.Yylex.yylex(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.nextToken(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
 Source)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.retrieveKeyTemplateDat
 a(KeyTemplateRetriever.java:100)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
 bService(KeyTemplateRetriever.java:111)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
 gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
 gateway-worker | at java.util.TimerThread.run(Timer.java:505)
 gateway-worker | Exception in thread "Timer-6"
 java.lang.NullPointerException
 gateway-worker | at java.util.Arrays$ArrayList.>>> it>(Arrays.java:2842)
 gateway-worker | at java.util.Arrays.asList(Arrays.java:2828)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
 bService(KeyTemplateRetriever.java:111)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
 gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
 gateway-worker | at java.util.TimerThread.run(Timer.java:505)
 gateway-worker | Exception in thread "Timer-5"
 com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
 Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
 gateway-worker | at com.google.gson.internal.bind.
 ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdap
 terFactory.java:221)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:861)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:826)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:775)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:747)

Re: [Dev] Error in AM 2.0 gateway

[Supun Malinga]

On Thu, Aug 25, 2016 at 4:34 PM, Harsha Kumara  wrote:

> Hi Supun,
>
> Did you setup the cluster with old throttling implementation? If it's with
> new throttling implementation, please check your key manager
> configuration.  Basically gateway try to fetch initial block conditions
> details from the key manager.
>

I know. Found by debugging :). Replied in the SO as well..

>
> Thanks,
> Harsha
>
> On Thu, Aug 25, 2016 at 3:58 PM, Abimaran Kugathasan 
> wrote:
>
>> Hi Supun,
>>
>> Same issue was reported here [1] as well, Can you try what Bhathiya has
>> responded or separate Key Manager from Store?
>>
>> [1] : http://stackoverflow.com/questions/39101064/error-on-api-
>> manager-2-0-0-gateway-worker-on-start-up
>>
>> On Mon, Aug 22, 2016 at 12:50 PM, Supun Malinga  wrote:
>>
>>> Diagram :
>>> ​
>>>  am-2.0-pattern-4.png
>>> 
>>> ​
>>>
>>> On Mon, Aug 22, 2016 at 12:47 PM, Supun Malinga  wrote:
>>>
 Hi,

 Getting the following exception in gateway worker. Any idea what could
 be causing this ?.
 This is in a distributed cluster with store and KM in same node.
 I can provide any configurations required..

 ​
  am-2.0-pattern-4
 
 ​


 gateway-worker | [2016-08-16 09:35:09,422]  INFO - API Destroying
 API: _WSO2AMTokenAPI_
 gateway-worker | [2016-08-16 09:35:09,426]  INFO - API Initializing
 API: _WSO2AMUserInfoAPI_
 gateway-worker | [2016-08-16 09:35:09,426]  INFO -
 DependencyTracker API : _WSO2AMUserInfoAPI_ was updated from the Synapse
 configuration successfully
 gateway-worker | [2016-08-16 09:35:09,426]  INFO - APIDeployer API:
 _WSO2AMUserInfoAPI_ has been updated from the file:
 /mnt/wso2am-2.0.0/repository/deployment/server/synapse-confi
 gs/default/api/_UserInfoAPI_.xml
 gateway-worker | [2016-08-16 09:35:11,427]  INFO - API Destroying
 API: _WSO2AMUserInfoAPI_
 gateway-worker | [2016-08-16 09:35:25,783] ERROR -
 KeyTemplateRetriever Exception when retrieving throttling data from remote
 endpoint
 gateway-worker | Unexpected character (<) at position 0.
 gateway-worker | at org.json.simple.parser.Yylex.yylex(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.nextToken(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
 Source)
 gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
 Source)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.retrieveKeyTemplateDat
 a(KeyTemplateRetriever.java:100)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
 bService(KeyTemplateRetriever.java:111)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
 gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
 gateway-worker | at java.util.TimerThread.run(Timer.java:505)
 gateway-worker | Exception in thread "Timer-6"
 java.lang.NullPointerException
 gateway-worker | at java.util.Arrays$ArrayList.>>> it>(Arrays.java:2842)
 gateway-worker | at java.util.Arrays.asList(Arrays.java:2828)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
 bService(KeyTemplateRetriever.java:111)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriever.java:54)
 gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
 gateway-worker | at java.util.TimerThread.run(Timer.java:505)
 gateway-worker | Exception in thread "Timer-5"
 com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
 Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
 gateway-worker | at com.google.gson.internal.bind.
 ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdap
 terFactory.java:221)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:861)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:826)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:775)
 gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:747)
 gateway-worker | at org.wso2.carbon.apimgt.gateway
 .throttling.util.BlockingConditionRetriever.retrieveBlockCon
 ditionsData(BlockingConditionRetriever.java:96)
 gateway-worker | at org.wso2.carbon.apimgt.gate

Re: [Dev] WSO2 Committers += Charitha Goonatileke

[Rasika Perera]

Congratulations Charitha !!!

On Thu, Aug 25, 2016 at 10:37 AM, Ruwan Yatawara  wrote:

> Hi All,
>
> It's my pleasure to announce Charitha Goonatileke as a WSO2 Committer.
> Charitha has been a valuable contributor to IoT Server and EMM products and
> in recognition of his contributions, He has been voted as a WSO2 Committer.
>
> Congratulations Charitha and keep up the good work!
>
> Thanks and Regards,
>
> Ruwan Yatawara
>
> Associate Technical Lead,
> WSO2 Inc.
>
> email : ruw...@wso2.com
> mobile : +94 77 9110413
> blog : http://ruwansrants.blogspot.com/
>   https://500px.com/ruwan_ace
> www: :http://wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
With Regards,

*Rasika Perera*
Software Engineer
LinkedIn: http://lk.linkedin.com/in/rasika90

[image: wso2-signature-general.png] 

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Charitha Goonatileke

[SajithAR Ariyarathna]

Congratulations!

On Thu, Aug 25, 2016 at 5:08 PM, Rasika Perera  wrote:

> Congratulations Charitha !!!
>
> On Thu, Aug 25, 2016 at 10:37 AM, Ruwan Yatawara  wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce Charitha Goonatileke as a WSO2 Committer.
>> Charitha has been a valuable contributor to IoT Server and EMM products and
>> in recognition of his contributions, He has been voted as a WSO2 Committer.
>>
>> Congratulations Charitha and keep up the good work!
>>
>> Thanks and Regards,
>>
>> Ruwan Yatawara
>>
>> Associate Technical Lead,
>> WSO2 Inc.
>>
>> email : ruw...@wso2.com
>> mobile : +94 77 9110413
>> blog : http://ruwansrants.blogspot.com/
>>   https://500px.com/ruwan_ace
>> www: :http://wso2.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> [image: wso2-signature-general.png] 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/

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

Re: [Dev] [APIM] Problem with integrating Event Stream OSGi Service

[Mohanadarshan Vivekanandalingam]

On Thu, Aug 25, 2016 at 11:33 AM, Malintha Amarasinghe 
wrote:

> Hi,
>
> On Wed, Aug 24, 2016 at 11:02 AM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> HI Malintha/Nuwan,
>>
>> I have few queries and like to provide few clarifications on this..
>>
>> Actually most of the points that you guys raised are discussed before and
>> changed based on some experiences..
>>
>> - Defining stream from client side  : We had this in old datapublisher
>> component and removed due to various complications.. As Srinath mentioned
>> this was done after many rounds of discussions..
>>
>> - Having single configuration file to add DAS endpoint : In past, we had
>> two level of configs (one for adapter which deals with transport and one
>> for event formatting which deals with stream). That means we can use one
>> event adapter for multiple streams.. But, there were some complaints saying
>> it is not user friendly and should have one config to publish events..
>>
>> And also, event publisher is also another deployable artifact like other
>> synapse files.. In APIM, we are configuring key manager url in multiple api
>> configs (revoke api and etc.. ), event publisher is also similar to that..
>>
>> But, I do understand that your points are valid and think we have two
>> options..
>>
>> - Have a global property in output-adapter-config.xml and use that in
>> Thrift event publisher (if that property exists)..
>>
>
@All, I have incorporated above fix by introducing a global default
property in master branch

Thanks,
Mohan


>

> - Allow to keep the DAS endpoint as a registry resource and use that..
>>
>> Thanks for the response. It would be great to have above in order to
> mitigate the duplicated configuration issues.
>


> Thanks!
> Malintha
>
>> Thanks,
>> Mohan
>>
>>
>> On Wed, Aug 24, 2016 at 10:05 AM, Nuwan Dias  wrote:
>>
>>> Hi,
>>>
>>> I spoke with Srinath regarding this too. It would be ideal to have a
>>> global config which can override the per-stream configs so that we won't
>>> have to maintain the DAS configs in multiple places. In all cases we've
>>> come across so far we've only seen people use a single DAS (or cluster) and
>>> publish all streams to that DAS cluster. So at least as of now I don't see
>>> much value in having per stream config files.
>>>
>>> It would also be good if we can omit the necessity of having to define
>>> the streams on the client side (because they're already defined on the
>>> server). I see two main problems of having to define them on the clients.
>>>
>>> 1. When we have multiple event generators (a gateway cluster), the
>>> streams will have to be defined on all nodes. Do we use dep-sync to sync up
>>> the configs on the clients? Even if we do, I think its better to not depend
>>> on dep-sync for the new stuff we're developing because we're moving away
>>> from dep-sync soon.
>>>
>>> 2. Problems in upgrading to newer product versions. When upgrading the
>>> product version, if a schema change has occurred, currently we only have to
>>> worry about changing the schema on the server side. With the above
>>> limitation, we now have to worry about changing the clients too.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Tue, Aug 23, 2016 at 10:16 PM, Malintha Amarasinghe <
>>> malint...@wso2.com> wrote:
>>>
 Hi All,

 Currently APIM is using an internal APIM specific configuration resides
 in api-manager.xml which include DAS server URL, username, password etc.
 Those configuration are used to instantiate an org.wso2.carbon.databridge.
 agent.DataPublisher object, which is then used to publish events
 directly to streams in DAS.

 As it is an APIM specific configuration, it is not reusable by other
 non-APIM features. Also org.wso2.carbon.databridge.agent.DataPublisher is
 intended to be used in non-carbon environments, for carbon environments,
 the recommended way is to use the Event Stream OSGi Service.

 So we were trying to re-structure APIM data publishing code to use new
 Event Stream OSGi service explained in [1].

 1. Create all the streams defined in DAS in APIM.
 2. Create an *event publisher per each stream *which takes data from
 the stream and publish to DAS.
 3. In each event publisher we need to configure DAS specific
 configuration.

 Ex:
 
 http://wso2.org/carbon/eventpublisher";>
   
   
   
 admin
 thrift
 non-blocking
 0
 tcp://localhost:7611
 
   
 

 But we are facing a small problem here; in APIM there are many event
 streams being used. If there's a change happen to DAS configuration, we
 need to change it in all the event publishers which makes it difficult to
 maintain. As per the offline chat with DAS team, this is a current
 limitation.

 Are we going to move forward with the existing implementation?

 Thanks,
 Malintha

 [1

Re: [Dev] Error in AM 2.0 gateway

[Bhathiya Jayasekara]

On Thu, Aug 25, 2016 at 4:45 PM, Supun Malinga  wrote:

>
>
> On Thu, Aug 25, 2016 at 4:34 PM, Harsha Kumara  wrote:
>
>> Hi Supun,
>>
>> Did you setup the cluster with old throttling implementation? If it's
>> with new throttling implementation, please check your key manager
>> configuration.  Basically gateway try to fetch initial block conditions
>> details from the key manager.
>>
>
> I know. Found by debugging :). Replied in the SO as well..
>

That SO deployment was strange. It has been done for a demo, and they said
they don't have a key manager at all. Hence the error. :)

Thanks,
Bhathiya


>
>> Thanks,
>> Harsha
>>
>> On Thu, Aug 25, 2016 at 3:58 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Supun,
>>>
>>> Same issue was reported here [1] as well, Can you try what Bhathiya has
>>> responded or separate Key Manager from Store?
>>>
>>> [1] : http://stackoverflow.com/questions/39101064/error-on-api-m
>>> anager-2-0-0-gateway-worker-on-start-up
>>>
>>> On Mon, Aug 22, 2016 at 12:50 PM, Supun Malinga  wrote:
>>>
 Diagram :
 ​
  am-2.0-pattern-4.png
 
 ​

 On Mon, Aug 22, 2016 at 12:47 PM, Supun Malinga 
 wrote:

> Hi,
>
> Getting the following exception in gateway worker. Any idea what could
> be causing this ?.
> This is in a distributed cluster with store and KM in same node.
> I can provide any configurations required..
>
> ​
>  am-2.0-pattern-4
> 
> ​
>
>
> gateway-worker | [2016-08-16 09:35:09,422]  INFO - API Destroying
> API: _WSO2AMTokenAPI_
> gateway-worker | [2016-08-16 09:35:09,426]  INFO - API
> Initializing API: _WSO2AMUserInfoAPI_
> gateway-worker | [2016-08-16 09:35:09,426]  INFO -
> DependencyTracker API : _WSO2AMUserInfoAPI_ was updated from the Synapse
> configuration successfully
> gateway-worker | [2016-08-16 09:35:09,426]  INFO - APIDeployer
> API: _WSO2AMUserInfoAPI_ has been updated from the file:
> /mnt/wso2am-2.0.0/repository/deployment/server/synapse-confi
> gs/default/api/_UserInfoAPI_.xml
> gateway-worker | [2016-08-16 09:35:11,427]  INFO - API Destroying
> API: _WSO2AMUserInfoAPI_
> gateway-worker | [2016-08-16 09:35:25,783] ERROR -
> KeyTemplateRetriever Exception when retrieving throttling data from remote
> endpoint
> gateway-worker | Unexpected character (<) at position 0.
> gateway-worker | at org.json.simple.parser.Yylex.yylex(Unknown
> Source)
> gateway-worker | at 
> org.json.simple.parser.JSONParser.nextToken(Unknown
> Source)
> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
> Source)
> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
> Source)
> gateway-worker | at org.json.simple.parser.JSONParser.parse(Unknown
> Source)
> gateway-worker | at org.wso2.carbon.apimgt.gateway
> .throttling.util.KeyTemplateRetriever.retrieveKeyTemplateDat
> a(KeyTemplateRetriever.java:100)
> gateway-worker | at org.wso2.carbon.apimgt.gateway
> .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
> bService(KeyTemplateRetriever.java:111)
> gateway-worker | at org.wso2.carbon.apimgt.gateway
> .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriev
> er.java:54)
> gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
> gateway-worker | at java.util.TimerThread.run(Timer.java:505)
> gateway-worker | Exception in thread "Timer-6"
> java.lang.NullPointerException
> gateway-worker | at java.util.Arrays$ArrayList. it>(Arrays.java:2842)
> gateway-worker | at java.util.Arrays.asList(Arrays.java:2828)
> gateway-worker | at org.wso2.carbon.apimgt.gateway
> .throttling.util.KeyTemplateRetriever.loadKeyTemplatesFromWe
> bService(KeyTemplateRetriever.java:111)
> gateway-worker | at org.wso2.carbon.apimgt.gateway
> .throttling.util.KeyTemplateRetriever.run(KeyTemplateRetriev
> er.java:54)
> gateway-worker | at java.util.TimerThread.mainLoop(Timer.java:555)
> gateway-worker | at java.util.TimerThread.run(Timer.java:505)
> gateway-worker | Exception in thread "Timer-5"
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
> Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
> gateway-worker | at com.google.gson.internal.bind.
> ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdap
> terFactory.java:221)
> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:861)
> gateway-worker | at com.google.gson.Gson.fromJson(Gson.java:826)
> gateway-worker | at com.g

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Nandika Jayawardana]

Tested BPMN, BPEL and HumanTasks samples in mysql based bps cluster.
Tested against Oracle and MSSQL databases.
Tested the human tasks and bpmn tooling.
Verified migration from BPS 3.5.1 to BPS 3.6.0
Reported few minor issues found in tooling and samples.

[+] Stable - go ahead and release.


Regards
Nandika


On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda  wrote:

> Hi,
> I verified,
>
>- Substitution feature.
>- BPMN Explorer.
>- Human Task Explorer.
>- Migration from 3.5.1.
>
> [+] Stable - go ahead and release.
>
> Regards,
> Vinod
>
> On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera  wrote:
>
>> Hi All,
>>
>> This is the 1st Release Candidate of WSO2 Business Process Server 3.6.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> *Source and distribution*
>>
>> *Run-time* : https://github.com/wso2/product-bps/releases/tag/v3.6.0-RC1
>> *Tooling*  : https://github.com/wso2/devstudio-tooling-bps/releases/tag/
>> Released-release-3.6.0-RC1-2016-08-24-114818
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> ~ WSO2 BPS Team ~
>>
>> --
>> Milinda Perera
>> Senior Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>
>
> --
> Vinod Kavinda
> Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Amal Gunatilake]

Hi,

Verified the following.

   - BPMN basic functionalities.
   - BPMN Rest Task improvements.
   - Humantask deployments + basic functionalities.
   - BPEL sample deployments + basic functionalities.
   - BPEL process instance cleanup tool.
   - Tested DB2 compatibility for BPEL and Humantask.
   - Oracle compatibility.
   - Tested Substitution feature + Oracle

[+] Stable - go ahead and release.

Best regards,
Amal.

On Thu, Aug 25, 2016 at 3:41 PM, Milinda Perera  wrote:

> Hi APIM and IS team,
>
> Could you please tryout your features with BPS with 3.6.0 RC1.
>
> Thanks,
> Milinda
>
> On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda  wrote:
>
>> Hi,
>> I verified,
>>
>>- Substitution feature.
>>- BPMN Explorer.
>>- Human Task Explorer.
>>- Migration from 3.5.1.
>>
>> [+] Stable - go ahead and release.
>>
>> Regards,
>> Vinod
>>
>> On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera 
>> wrote:
>>
>>> Hi All,
>>>
>>> This is the 1st Release Candidate of WSO2 Business Process Server 3.6.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> *Source and distribution*
>>>
>>> *Run-time* : https://github.com/wso2/product-bps/releases/tag/v3.6.0-RC1
>>> *Tooling*  : https://github.com/wso2/devstu
>>> dio-tooling-bps/releases/tag/Released-release-3.6.0-RC1-2016
>>> -08-24-114818
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> ~ WSO2 BPS Team ~
>>>
>>> --
>>> Milinda Perera
>>> Senior Software Engineer;
>>> WSO2 Inc. http://wso2.com ,
>>> Mobile: (+94) 714 115 032
>>>
>>>
>>
>>
>> --
>> Vinod Kavinda
>> Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware .*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>> [image: http://wso2.com/signature]
>> 
>>
>>
>
>
> --
> Milinda Perera
> Senior Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amal Gunatilake*
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

mobile: (+94) 773561195
blog: amalg-blogs.blogspot.com; twitter: @daag123
linkedIn: https://www.linkedin.com/in/amalgunatilake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Milinda Perera]

Tested and following:

Setups : Cluster with MySql + DepSync enabled + fronted by NGINX
Cluster with Oracle + DepSync enabled + fronted by NGINX

Tested following:

   - Basic functionalities of BPMN, BPEL, WS-Humantask
   - BPMN, BPEL and WS-Humantask versioning
   - Smoke test on BPMN-Explorer and Humantask-Explorer
   - Verify XML and JSON variable types usage
   - BPMN, BPEL and WS-Humantask package deployement in tenants with
DepSync

[+] Stable - go ahead and release.


Thanks,
Milinda

On Thu, Aug 25, 2016 at 11:23 PM, Amal Gunatilake  wrote:

> Hi,
>
> Verified the following.
>
>- BPMN basic functionalities.
>- BPMN Rest Task improvements.
>- Humantask deployments + basic functionalities.
>- BPEL sample deployments + basic functionalities.
>- BPEL process instance cleanup tool.
>- Tested DB2 compatibility for BPEL and Humantask.
>- Oracle compatibility.
>- Tested Substitution feature + Oracle
>
> [+] Stable - go ahead and release.
>
> Best regards,
> Amal.
>
> On Thu, Aug 25, 2016 at 3:41 PM, Milinda Perera  wrote:
>
>> Hi APIM and IS team,
>>
>> Could you please tryout your features with BPS with 3.6.0 RC1.
>>
>> Thanks,
>> Milinda
>>
>> On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda  wrote:
>>
>>> Hi,
>>> I verified,
>>>
>>>- Substitution feature.
>>>- BPMN Explorer.
>>>- Human Task Explorer.
>>>- Migration from 3.5.1.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Regards,
>>> Vinod
>>>
>>> On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera 
>>> wrote:
>>>
 Hi All,

 This is the 1st Release Candidate of WSO2 Business Process Server 3.6.0

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.

 *Source and distribution*

 *Run-time* : https://github.com/wso2/produc
 t-bps/releases/tag/v3.6.0-RC1
 *Tooling*  : https://github.com/wso2/devstu
 dio-tooling-bps/releases/tag/Released-release-3.6.0-RC1-2016
 -08-24-114818

 Please vote as follows.
 [+] Stable - go ahead and release
 [-] Broken - do not release (explain why)

 Thanks,
 ~ WSO2 BPS Team ~

 --
 Milinda Perera
 Senior Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


>>>
>>>
>>> --
>>> Vinod Kavinda
>>> Software Engineer
>>> *WSO2 Inc. - lean . enterprise . middleware .*
>>> Mobile : +94 (0) 712 415544
>>> Blog : http://soatechflicks.blogspot.com/
>>> [image: http://wso2.com/signature]
>>> 
>>>
>>>
>>
>>
>> --
>> Milinda Perera
>> Senior Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amal Gunatilake*
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> mobile: (+94) 773561195
> blog: amalg-blogs.blogspot.com; twitter: @daag123
> linkedIn: https://www.linkedin.com/in/amalgunatilake
>



-- 
Milinda Perera
Senior Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Error in running a sample provided in the doc

[Jagath Sisirakumara Ariyarathne]

Hi Nadeesha,

Seems the payload received to the ESB '{name:WSO2}'does not contain double
quotes. Correct payload should be '{"name":"WSO2"}'.

Lets check wire logs to get it confirmed that ESB received correct payload.

Thanks.

On Wed, Aug 24, 2016 at 12:07 PM, Nadeesha Gamage  wrote:

> Hi all,
> I am referring to the following document [1], and have deployed the CAR
> file provided [2]. When I try to invoke the API using the provided curl
> command I get the following error. Can someone help to get this resolved.
>
> curl -X POST http://localhost:8280/stockquote/getQuote -d
> '{"name":"WSO2"}' -H "Content-Type:application/json"
>
>
> TID: [-1234] [] [2016-08-24 11:56:57,576]  INFO
> {org.apache.synapse.mediators.builtin.LogMediator} -  To:
> /stockquote/getQuote, MessageID: 
> urn:uuid:a688b5fd-4db3-46b2-9a7d-78797558de89,
> Direction: request, Payload: '{name:WSO2}' {org.apache.synapse.mediators.
> builtin.LogMediator}
> TID: [-1234] [] [2016-08-24 11:56:57,585] ERROR 
> {org.apache.synapse.util.xpath.SynapseJsonPath}
> -  #stringValueOf. Error evaluating JSON Path <$.name>. Returning empty
> result. Error>>> Invalid container object {org.apache.synapse.util.
> xpath.SynapseJsonPath}
> TID: [-1234] [] [2016-08-24 11:56:57,595] ERROR 
> {org.apache.axiom.om.impl.llom.OMSourcedElementImpl}
> -  Could not get parser from data source for element jsonObject
> {org.apache.axiom.om.impl.llom.OMSourcedElementImpl}
> javax.xml.stream.XMLStreamException
> at org.apache.synapse.commons.staxon.core.base.AbstractXMLStreamReader.
> initialize(AbstractXMLStreamReader.java:245)
> at org.apache.synapse.commons.staxon.core.json.JsonXMLStreamReader.(
> JsonXMLStreamReader.java:66)
> at org.apache.synapse.commons.staxon.core.json.JsonXMLInputFactory.
> createXMLStreamReader(JsonXMLInputFactory.java:165)
> at org.apache.synapse.commons.json.JsonUtil.getReader(JsonUtil.java:302)
> at org.apache.synapse.commons.json.JsonDataSource.getReader(
> JsonDataSource.java:153)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getDirectReader(
> OMSourcedElementImpl.java:225)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(
> OMSourcedElementImpl.java:254)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getChildren(
> OMSourcedElementImpl.java:859)
> at org.apache.synapse.commons.json.JsonUtil.removeIndentations(JsonUtil.
> java:417)
> at org.apache.synapse.commons.json.JsonUtil.removeIndentations(JsonUtil.
> java:425)
> at org.apache.synapse.commons.json.JsonUtil.removeJsonPayload(JsonUtil.
> java:731)
> at org.apache.synapse.mediators.transform.PayloadFactoryMediator.mediate(
> PayloadFactoryMediator.java:163)
> at org.apache.synapse.mediators.transform.PayloadFactoryMediator.mediate(
> PayloadFactoryMediator.java:104)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:89)
> at org.apache.synapse.mediators.AbstractListMediator.mediate(
> AbstractListMediator.java:59)
> at org.apache.synapse.mediators.base.SequenceMediator.mediate(
> SequenceMediator.java:158)
> at org.apache.synapse.rest.Resource.process(Resource.java:343)
> at org.apache.synapse.rest.API.process(API.java:399)
> at org.apache.synapse.rest.RESTRequestHandler.apiProcess(
> RESTRequestHandler.java:120)
> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(
> RESTRequestHandler.java:101)
> at org.apache.synapse.rest.RESTRequestHandler.process(
> RESTRequestHandler.java:69)
> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(
> Axis2SynapseEnvironment.java:304)
> at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(
> SynapseMessageReceiver.java:75)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processNonEntityEnclosingRESTHandler(ServerWorker.java:325)
> at org.apache.synapse.transport.passthru.ServerWorker.
> processEntityEnclosingRequest(ServerWorker.java:371)
> at org.apache.synapse.transport.passthru.ServerWorker.run(
> ServerWorker.java:151)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> TID: [-1234] [] [2016-08-24 11:56:57,613] ERROR
> {org.apache.synapse.mediators.base.SequenceMediator} -  Error obtaining
> parser from data source:null {org.apache.synapse.mediators.
> base.SequenceMediator}
> java.lang.RuntimeException: Error obtaining parser from data source:null
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getDirectReader(
> OMSourcedElementImpl.java:230)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(
> OMSourcedElementImpl.java:254)
> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getChildren(
> OMSourcedElementImpl.java:859)
> at org.apache.synapse.commons.jso

Re: [Dev] WSO2 Committers += Charitha Goonatileke

[Liangfei.Su]

Congratulations!

On Thu, Aug 25, 2016 at 7:42 PM, SajithAR Ariyarathna 
wrote:

> Congratulations!
>
> On Thu, Aug 25, 2016 at 5:08 PM, Rasika Perera  wrote:
>
>> Congratulations Charitha !!!
>>
>> On Thu, Aug 25, 2016 at 10:37 AM, Ruwan Yatawara  wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to announce Charitha Goonatileke as a WSO2 Committer.
>>> Charitha has been a valuable contributor to IoT Server and EMM products and
>>> in recognition of his contributions, He has been voted as a WSO2 Committer.
>>>
>>> Congratulations Charitha and keep up the good work!
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Associate Technical Lead,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>>   https://500px.com/ruwan_ace
>>> www: :http://wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> [image: wso2-signature-general.png] 
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC2016-Contact Development Team Feature

[Nathiesha Maddage]

Hi all,

Thank you for the suggestions. I changed the template of the blog, so now
the contents are more visible to the user.

Regarding the email address, In the preference page [1], a user can set 2
email addresses. The first is under contact information. That should be the
user's email address. That is used in case the development team wants to
contact the user regarding the issue posted. Entering that is optional.

Secondly there is another email address to be entered under email
information. That should be the recipient email. If the user wants to email
the error report, he can enter the recipient email address here.

Then we have created a separate Micro Service to handle the email
publishing and Jira publishing tasks, which is hosted in App cloud. The
email address which is used to send the email to the recipient and it's
credentials are stored in the cloud, as environment variables. It is not
visible to the Developer Studio user and that can be configured externally
by the Development team as they wish.

One reason we added the email feature to the project is to give user an
opportunity to email the error report to his preferred email address.But
that is quite unlikely to be used. Another reason is to create a way to use
the error reports to any other purpose later, other than just getting them
published in Jira. If we consider it that way, the recipient email should
also be given by the development team, to get the error report emailed to
any of their preferred addresses. If so I can change the recipient email to
be an un-editable field.

Regarding the url, I will try with a different organization name and the
custom url feature.

Thanks and regards

Nathiesha

On Wed, Aug 24, 2016 at 8:47 AM, Awanthika Senarath <
awanthikarasanjaleesenar...@gmail.com> wrote:

> Hello Susinda,
>
> If the email address is configured by us to send the reports, it is true
> that we should not allow the user to edit it, since it may prevent us
> getting the reports,
>
> But the user should be able to see it. we can leave it visible
> un-editable. WDYT? Given the deadlines, aren't we too late to be discussing
> this anyway?
>
> Anyways Nathiesha good work, the blog posts were great! I felt the same as
> Jasintha, please replace the background image so that your content is more
> visible to the reader :)
>
> Regards
> Awanthika
>
> On Wed, Aug 24, 2016 at 12:43 PM, Susinda Perera  wrote:
>
>>
>>
>> On Wed, Aug 24, 2016 at 8:03 AM, Danushka Fernando 
>> wrote:
>>
>>> Hi
>>> test4475 is the organization name. You can either try with some other
>>> organization name or you can use the custom url feature in App Cloud. But
>>> you will need to add a cname entry in a name service provider.
>>>
>>> Thanks & Regards
>>> Danushka Fernando
>>> Senior Software Engineer
>>> WSO2 inc. http://wso2.com/
>>> Mobile : +94716332729
>>>
>>> On Wed, Aug 24, 2016 at 7:52 AM, Nathiesha Maddage <
>>> nathieshamadd...@gmail.com> wrote:
>>>
 Hi,

 Regarding the app cloud URL, the URL I got was "
 http://test4475-error-publisher-4-0-0.wso2apps.com/";. I can change the
 "error-publisher" part in the URL. But I cannot edit the "test4475" part. I
 will inquire from the App Cloud team regarding that and see if it is
 possible to get a new URL. Since I created a WSO2 app cloud account for
 temporary testing purposes, that URL was added to the preferences page and
 added the screenshot of it for demonstration purposes.

 I removed the "devstu...@gmail.com" email address and added a new
 screenshot to the blog post.

>>> Hi Nathesha
>> What i mean was, we dont need to let this information to be edited by
>> users, Isnt it?, This may be a mail address that we configured which is to
>> be used in sending reports. Souser may not need to see this or edit this.
>>
>>>
 I made the submission to GSOC Final Evaluation. But I can update the
 blog post contents where necessary.
 Thank you for the support and guidance given through out this period.


 Thanks and regards

 Nathiesha



 On Tue, Aug 23, 2016 at 10:38 AM, Susinda Perera 
 wrote:

> In the [2], Cant we get some other url from wso2apss.com, Also I dont
> think that we need to show the devstu...@gmail.com mail address
> [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
> use-of-error-reporting.html
>
> On Tue, Aug 23, 2016 at 10:27 AM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> Blog post looks good enough and it provides enough information about
>> the work you have done.
>>
>> Please let us know if you find any issues related to submission.
>> Since tomorrow is the last day for your submission, we can have a meeting
>> today or tomorrow to clear out any issues.
>>
>> Please let us know.
>>
>> Thanks,
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.

Re: [Dev] Hieradata location for puppet modules

[Rasanjaya Subasinghe]

Hi all,

The option 2 would be good for do the MC deployment. And other users  can
be used default profile with released puppet forge module.

Thanks

On Thursday, August 25, 2016, Anuruddha Liyanarachchi 
wrote:

> Hi Devs,
>
> We are in the process of restructuring and splitting the puppet modules
> per product. As per the initial discussions, we have created separate
> repositories per product puppet module and one common repository for puppet
> base module.
>
> In order to publish puppet modules to puppet forge, we have decoupled
> hieradata from puppet modules using profiles. Now the puppet modules are
> capable of running without hieradata for the default profile.
>
> However, it is easier to do deployment using hieradata. The intention of
> this mail is to discuss and finalize hieradata location.
>
> Appreciate your feedback on selecting an available option.
>
> Following are the available options:
>
> *1. Use one repository to keep all product hieradata.*
> Pros:
> - Easy to manage since all the hieradata are in one place.
> - No data duplication
>
> Cons:
> - Releasing hieradata with a product is not possible.
> - Difficult to track changes.
>
>
> *2. Keep hieradata with platform specific artifact repositories.
> (kubernetes, mesos )*
> Pros:
> - Hieradata can be released with a product.
>
> Cons:
> - Possible data duplication.
> - Hieradata is a part of puppet and it is not related to mesos or
> kubernetes
> - Have to create repositories to store default hieradata.
>
>
> *3. Create separate repositories per product to store hieradata. *
> Pros:
> - Product level hieradata separation.
> - Easier to release and track changes.
>
> Cons:
> - No of repositories are high.
> - User experience will be not good as users will have to clone from
> multiple locations.
>
>
>
> *4. Keep hieradata in the product puppet module repos with
> .pmtignore file. *Pros:
> - Minimum changes required.
> - Can be released with product puppet modules.
>
> Cons:
> - Most of the puppet repos don't contain hieradata
> - Puppet recommends keeping  hieradata separately from modules.
>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
> 
>


-- 
-
Rasanjaya Subasinghe
Software Engineer, Dev/Ops, WSO2 Inc.
+94772250358
rasanj...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Sudharma Subasinghe]

Verified the following.
 - BPMN Explorer functionalities and multi-tenant support
 - BPEL deployment, execution and clustering with MySql
 - MySql compatibility
 - BPS process cleanup tools with MySql

[+] Stable - go ahead and release.

Thanks
Sudharma

On Fri, Aug 26, 2016 at 12:45 AM, Milinda Perera  wrote:

> Tested and following:
>
> Setups : Cluster with MySql + DepSync enabled + fronted by NGINX
> Cluster with Oracle + DepSync enabled + fronted by NGINX
>
> Tested following:
>
>- Basic functionalities of BPMN, BPEL, WS-Humantask
>- BPMN, BPEL and WS-Humantask versioning
>- Smoke test on BPMN-Explorer and Humantask-Explorer
>- Verify XML and JSON variable types usage
>- BPMN, BPEL and WS-Humantask package deployement in tenants with
> DepSync
>
> [+] Stable - go ahead and release.
>
>
> Thanks,
> Milinda
>
> On Thu, Aug 25, 2016 at 11:23 PM, Amal Gunatilake  wrote:
>
>> Hi,
>>
>> Verified the following.
>>
>>- BPMN basic functionalities.
>>- BPMN Rest Task improvements.
>>- Humantask deployments + basic functionalities.
>>- BPEL sample deployments + basic functionalities.
>>- BPEL process instance cleanup tool.
>>- Tested DB2 compatibility for BPEL and Humantask.
>>- Oracle compatibility.
>>- Tested Substitution feature + Oracle
>>
>> [+] Stable - go ahead and release.
>>
>> Best regards,
>> Amal.
>>
>> On Thu, Aug 25, 2016 at 3:41 PM, Milinda Perera 
>> wrote:
>>
>>> Hi APIM and IS team,
>>>
>>> Could you please tryout your features with BPS with 3.6.0 RC1.
>>>
>>> Thanks,
>>> Milinda
>>>
>>> On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda  wrote:
>>>
 Hi,
 I verified,

- Substitution feature.
- BPMN Explorer.
- Human Task Explorer.
- Migration from 3.5.1.

 [+] Stable - go ahead and release.

 Regards,
 Vinod

 On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera 
 wrote:

> Hi All,
>
> This is the 1st Release Candidate of WSO2 Business Process Server 3.6.0
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
>
> *Source and distribution*
>
> *Run-time* : https://github.com/wso2/produc
> t-bps/releases/tag/v3.6.0-RC1
> *Tooling*  : https://github.com/wso2/devstu
> dio-tooling-bps/releases/tag/Released-release-3.6.0-RC1-2016
> -08-24-114818
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> ~ WSO2 BPS Team ~
>
> --
> Milinda Perera
> Senior Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>


 --
 Vinod Kavinda
 Software Engineer
 *WSO2 Inc. - lean . enterprise . middleware .*
 Mobile : +94 (0) 712 415544
 Blog : http://soatechflicks.blogspot.com/
 [image: http://wso2.com/signature]
 


>>>
>>>
>>> --
>>> Milinda Perera
>>> Senior Software Engineer;
>>> WSO2 Inc. http://wso2.com ,
>>> Mobile: (+94) 714 115 032
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Amal Gunatilake*
>> WSO2 Inc.; http://wso2.com
>> Lean . Enterprise . Middleware
>>
>> mobile: (+94) 773561195
>> blog: amalg-blogs.blogspot.com; twitter: @daag123
>> linkedIn: https://www.linkedin.com/in/amalgunatilake
>>
>
>
>
> --
> Milinda Perera
> Senior Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sudharma Subasinghe,
Software Engineer,
WSO2 Inc.
Email: sudhar...@wso2.com 
Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC2016-Contact Development Team Feature

[Awanthika Senarath]

Hello Nathiesha,

According to your explanation, the second email address could be useful for
a company for internal auditing purposes. Hence I think we should leave it
editable.


Regards
Awanthika

On Fri, Aug 26, 2016 at 12:25 PM, Nathiesha Maddage <
nathieshamadd...@gmail.com> wrote:

> Hi all,
>
> Thank you for the suggestions. I changed the template of the blog, so now
> the contents are more visible to the user.
>
> Regarding the email address, In the preference page [1], a user can set 2
> email addresses. The first is under contact information. That should be the
> user's email address. That is used in case the development team wants to
> contact the user regarding the issue posted. Entering that is optional.
>
> Secondly there is another email address to be entered under email
> information. That should be the recipient email. If the user wants to email
> the error report, he can enter the recipient email address here.
>
> Then we have created a separate Micro Service to handle the email
> publishing and Jira publishing tasks, which is hosted in App cloud. The
> email address which is used to send the email to the recipient and it's
> credentials are stored in the cloud, as environment variables. It is not
> visible to the Developer Studio user and that can be configured externally
> by the Development team as they wish.
>
> One reason we added the email feature to the project is to give user an
> opportunity to email the error report to his preferred email address.But
> that is quite unlikely to be used. Another reason is to create a way to use
> the error reports to any other purpose later, other than just getting them
> published in Jira. If we consider it that way, the recipient email should
> also be given by the development team, to get the error report emailed to
> any of their preferred addresses. If so I can change the recipient email to
> be an un-editable field.
>
> Regarding the url, I will try with a different organization name and the
> custom url feature.
>
> Thanks and regards
>
> Nathiesha
>
> On Wed, Aug 24, 2016 at 8:47 AM, Awanthika Senarath <
> awanthikarasanjaleesenar...@gmail.com> wrote:
>
>> Hello Susinda,
>>
>> If the email address is configured by us to send the reports, it is true
>> that we should not allow the user to edit it, since it may prevent us
>> getting the reports,
>>
>> But the user should be able to see it. we can leave it visible
>> un-editable. WDYT? Given the deadlines, aren't we too late to be discussing
>> this anyway?
>>
>> Anyways Nathiesha good work, the blog posts were great! I felt the same
>> as Jasintha, please replace the background image so that your content is
>> more visible to the reader :)
>>
>> Regards
>> Awanthika
>>
>> On Wed, Aug 24, 2016 at 12:43 PM, Susinda Perera 
>> wrote:
>>
>>>
>>>
>>> On Wed, Aug 24, 2016 at 8:03 AM, Danushka Fernando 
>>> wrote:
>>>
 Hi
 test4475 is the organization name. You can either try with some other
 organization name or you can use the custom url feature in App Cloud. But
 you will need to add a cname entry in a name service provider.

 Thanks & Regards
 Danushka Fernando
 Senior Software Engineer
 WSO2 inc. http://wso2.com/
 Mobile : +94716332729

 On Wed, Aug 24, 2016 at 7:52 AM, Nathiesha Maddage <
 nathieshamadd...@gmail.com> wrote:

> Hi,
>
> Regarding the app cloud URL, the URL I got was "
> http://test4475-error-publisher-4-0-0.wso2apps.com/";. I can change
> the "error-publisher" part in the URL. But I cannot edit the "test4475"
> part. I will inquire from the App Cloud team regarding that and see if it
> is possible to get a new URL. Since I created a WSO2 app cloud account for
> temporary testing purposes, that URL was added to the preferences page and
> added the screenshot of it for demonstration purposes.
>
> I removed the "devstu...@gmail.com" email address and added a new
> screenshot to the blog post.
>
 Hi Nathesha
>>> What i mean was, we dont need to let this information to be edited by
>>> users, Isnt it?, This may be a mail address that we configured which is to
>>> be used in sending reports. Souser may not need to see this or edit this.
>>>

> I made the submission to GSOC Final Evaluation. But I can update the
> blog post contents where necessary.
> Thank you for the support and guidance given through out this period.
>
>
> Thanks and regards
>
> Nathiesha
>
>
>
> On Tue, Aug 23, 2016 at 10:38 AM, Susinda Perera 
> wrote:
>
>> In the [2], Cant we get some other url from wso2apss.com, Also I
>> dont think that we need to show the devstu...@gmail.com mail address
>> [2]. http://nathiesha.blogspot.com/2016/08/how-to-make-best-
>> use-of-error-reporting.html
>>
>> On Tue, Aug 23, 2016 at 10:27 AM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Nathiesha,
>>>
>>> Blog post looks go

Re: [Dev] Hieradata location for puppet modules

[Akila Ravihansa Perera]

Hi,

There is one catch with option 2; we need to track which Hiera distribution
(in platform specific artifacts repo) goes with which Puppet release. This
won't be a big issue but just wanted point out.

Thanks.

On Fri, Aug 26, 2016 at 9:05 AM, Rasanjaya Subasinghe 
wrote:

> Hi all,
>
> The option 2 would be good for do the MC deployment. And other users  can
> be used default profile with released puppet forge module.
>
> Thanks
>
>
> On Thursday, August 25, 2016, Anuruddha Liyanarachchi 
> wrote:
>
>> Hi Devs,
>>
>> We are in the process of restructuring and splitting the puppet modules
>> per product. As per the initial discussions, we have created separate
>> repositories per product puppet module and one common repository for puppet
>> base module.
>>
>> In order to publish puppet modules to puppet forge, we have decoupled
>> hieradata from puppet modules using profiles. Now the puppet modules are
>> capable of running without hieradata for the default profile.
>>
>> However, it is easier to do deployment using hieradata. The intention of
>> this mail is to discuss and finalize hieradata location.
>>
>> Appreciate your feedback on selecting an available option.
>>
>> Following are the available options:
>>
>> *1. Use one repository to keep all product hieradata.*
>> Pros:
>> - Easy to manage since all the hieradata are in one place.
>> - No data duplication
>>
>> Cons:
>> - Releasing hieradata with a product is not possible.
>> - Difficult to track changes.
>>
>>
>> *2. Keep hieradata with platform specific artifact repositories.
>> (kubernetes, mesos )*
>> Pros:
>> - Hieradata can be released with a product.
>>
>> Cons:
>> - Possible data duplication.
>> - Hieradata is a part of puppet and it is not related to mesos or
>> kubernetes
>> - Have to create repositories to store default hieradata.
>>
>>
>> *3. Create separate repositories per product to store hieradata. *
>> Pros:
>> - Product level hieradata separation.
>> - Easier to release and track changes.
>>
>> Cons:
>> - No of repositories are high.
>> - User experience will be not good as users will have to clone from
>> multiple locations.
>>
>>
>>
>> *4. Keep hieradata in the product puppet module repos with
>> .pmtignore file. *Pros:
>> - Minimum changes required.
>> - Can be released with product puppet modules.
>>
>> Cons:
>> - Most of the puppet repos don't contain hieradata
>> - Puppet recommends keeping  hieradata separately from modules.
>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> anurudd...@wso2.com
>>
>
>
> --
> -
> Rasanjaya Subasinghe
> Software Engineer, Dev/Ops, WSO2 Inc.
> +94772250358
> rasanj...@wso2.com
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Heshitha Hettihewa]

Hi all.

Tested and verified the following

   - Human Tasks
   - Human Task Explorer functionalities with multi tenancy
   - BPS Tooling
   - BPEL basic functionalities

[+] Stable - go ahead and release.
Thanks.

On Fri, Aug 26, 2016 at 9:30 AM, Sudharma Subasinghe 
wrote:

> Verified the following.
>  - BPMN Explorer functionalities and multi-tenant support
>  - BPEL deployment, execution and clustering with MySql
>  - MySql compatibility
>  - BPS process cleanup tools with MySql
>
> [+] Stable - go ahead and release.
>
> Thanks
> Sudharma
>
> On Fri, Aug 26, 2016 at 12:45 AM, Milinda Perera 
> wrote:
>
>> Tested and following:
>>
>> Setups : Cluster with MySql + DepSync enabled + fronted by NGINX
>> Cluster with Oracle + DepSync enabled + fronted by NGINX
>>
>> Tested following:
>>
>>- Basic functionalities of BPMN, BPEL, WS-Humantask
>>- BPMN, BPEL and WS-Humantask versioning
>>- Smoke test on BPMN-Explorer and Humantask-Explorer
>>- Verify XML and JSON variable types usage
>>- BPMN, BPEL and WS-Humantask package deployement in tenants with
>> DepSync
>>
>> [+] Stable - go ahead and release.
>>
>>
>> Thanks,
>> Milinda
>>
>> On Thu, Aug 25, 2016 at 11:23 PM, Amal Gunatilake  wrote:
>>
>>> Hi,
>>>
>>> Verified the following.
>>>
>>>- BPMN basic functionalities.
>>>- BPMN Rest Task improvements.
>>>- Humantask deployments + basic functionalities.
>>>- BPEL sample deployments + basic functionalities.
>>>- BPEL process instance cleanup tool.
>>>- Tested DB2 compatibility for BPEL and Humantask.
>>>- Oracle compatibility.
>>>- Tested Substitution feature + Oracle
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Best regards,
>>> Amal.
>>>
>>> On Thu, Aug 25, 2016 at 3:41 PM, Milinda Perera 
>>> wrote:
>>>
 Hi APIM and IS team,

 Could you please tryout your features with BPS with 3.6.0 RC1.

 Thanks,
 Milinda

 On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda  wrote:

> Hi,
> I verified,
>
>- Substitution feature.
>- BPMN Explorer.
>- Human Task Explorer.
>- Migration from 3.5.1.
>
> [+] Stable - go ahead and release.
>
> Regards,
> Vinod
>
> On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera 
> wrote:
>
>> Hi All,
>>
>> This is the 1st Release Candidate of WSO2 Business Process Server
>> 3.6.0
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>>
>> *Source and distribution*
>>
>> *Run-time* : https://github.com/wso2/produc
>> t-bps/releases/tag/v3.6.0-RC1
>> *Tooling*  : https://github.com/wso2/devstu
>> dio-tooling-bps/releases/tag/Released-release-3.6.0-RC1-2016
>> -08-24-114818
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> ~ WSO2 BPS Team ~
>>
>> --
>> Milinda Perera
>> Senior Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>
>
> --
> Vinod Kavinda
> Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>


 --
 Milinda Perera
 Senior Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


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


>>>
>>>
>>> --
>>> *Amal Gunatilake*
>>> WSO2 Inc.; http://wso2.com
>>> Lean . Enterprise . Middleware
>>>
>>> mobile: (+94) 773561195
>>> blog: amalg-blogs.blogspot.com; twitter: @daag123
>>> linkedIn: https://www.linkedin.com/in/amalgunatilake
>>>
>>
>>
>>
>> --
>> Milinda Perera
>> Senior Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sudharma Subasinghe,
> Software Engineer,
> WSO2 Inc.
> Email: sudhar...@wso2.com 
> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Heshitha Hettihewa
*Software Engineer*
Mobile : +94716866386
<%2B94%20%280%29%20773%20451194>
heshit...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Nandika Jayawardana]

Tested the user signup workflow with APIM 2.0.0 against the RC pack and its
working fine as well.

Regards
Nandika

On Fri, Aug 26, 2016 at 9:49 AM, Heshitha Hettihewa 
wrote:

> Hi all.
>
> Tested and verified the following
>
>- Human Tasks
>- Human Task Explorer functionalities with multi tenancy
>- BPS Tooling
>- BPEL basic functionalities
>
> [+] Stable - go ahead and release.
> Thanks.
>
> On Fri, Aug 26, 2016 at 9:30 AM, Sudharma Subasinghe 
> wrote:
>
>> Verified the following.
>>  - BPMN Explorer functionalities and multi-tenant support
>>  - BPEL deployment, execution and clustering with MySql
>>  - MySql compatibility
>>  - BPS process cleanup tools with MySql
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks
>> Sudharma
>>
>> On Fri, Aug 26, 2016 at 12:45 AM, Milinda Perera 
>> wrote:
>>
>>> Tested and following:
>>>
>>> Setups : Cluster with MySql + DepSync enabled + fronted by NGINX
>>> Cluster with Oracle + DepSync enabled + fronted by NGINX
>>>
>>> Tested following:
>>>
>>>- Basic functionalities of BPMN, BPEL, WS-Humantask
>>>- BPMN, BPEL and WS-Humantask versioning
>>>- Smoke test on BPMN-Explorer and Humantask-Explorer
>>>- Verify XML and JSON variable types usage
>>>- BPMN, BPEL and WS-Humantask package deployement in tenants with
>>> DepSync
>>>
>>> [+] Stable - go ahead and release.
>>>
>>>
>>> Thanks,
>>> Milinda
>>>
>>> On Thu, Aug 25, 2016 at 11:23 PM, Amal Gunatilake 
>>> wrote:
>>>
 Hi,

 Verified the following.

- BPMN basic functionalities.
- BPMN Rest Task improvements.
- Humantask deployments + basic functionalities.
- BPEL sample deployments + basic functionalities.
- BPEL process instance cleanup tool.
- Tested DB2 compatibility for BPEL and Humantask.
- Oracle compatibility.
- Tested Substitution feature + Oracle

 [+] Stable - go ahead and release.

 Best regards,
 Amal.

 On Thu, Aug 25, 2016 at 3:41 PM, Milinda Perera 
 wrote:

> Hi APIM and IS team,
>
> Could you please tryout your features with BPS with 3.6.0 RC1.
>
> Thanks,
> Milinda
>
> On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda  wrote:
>
>> Hi,
>> I verified,
>>
>>- Substitution feature.
>>- BPMN Explorer.
>>- Human Task Explorer.
>>- Migration from 3.5.1.
>>
>> [+] Stable - go ahead and release.
>>
>> Regards,
>> Vinod
>>
>> On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera 
>> wrote:
>>
>>> Hi All,
>>>
>>> This is the 1st Release Candidate of WSO2 Business Process Server
>>> 3.6.0
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>>
>>> *Source and distribution*
>>>
>>> *Run-time* : https://github.com/wso2/produc
>>> t-bps/releases/tag/v3.6.0-RC1
>>> *Tooling*  : https://github.com/wso2/devstu
>>> dio-tooling-bps/releases/tag/Released-release-3.6.0-RC1-2016
>>> -08-24-114818
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> ~ WSO2 BPS Team ~
>>>
>>> --
>>> Milinda Perera
>>> Senior Software Engineer;
>>> WSO2 Inc. http://wso2.com ,
>>> Mobile: (+94) 714 115 032
>>>
>>>
>>
>>
>> --
>> Vinod Kavinda
>> Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware .*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>> [image: http://wso2.com/signature]
>> 
>>
>>
>
>
> --
> Milinda Perera
> Senior Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Amal Gunatilake*
 WSO2 Inc.; http://wso2.com
 Lean . Enterprise . Middleware

 mobile: (+94) 773561195
 blog: amalg-blogs.blogspot.com; twitter: @daag123
 linkedIn: https://www.linkedin.com/in/amalgunatilake

>>>
>>>
>>>
>>> --
>>> Milinda Perera
>>> Senior Software Engineer;
>>> WSO2 Inc. http://wso2.com ,
>>> Mobile: (+94) 714 115 032
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sudharma Subasinghe,
>> Software Engineer,
>> WSO2 Inc.
>> Email: sudhar...@wso2.com 
>> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Heshitha Hett

Re: [Dev] [VOTE][RC1] Release - WSO2 Business Process Server 3.6.0 RC1

[Malintha Adikari]

Hi all,

Tested and verified process analytics publishing.

[+] Stable - go ahead and release.

Regards,
Malintha

On Fri, Aug 26, 2016 at 9:55 AM, Nandika Jayawardana 
wrote:

> Tested the user signup workflow with APIM 2.0.0 against the RC pack and
> its working fine as well.
>
> Regards
> Nandika
>
> On Fri, Aug 26, 2016 at 9:49 AM, Heshitha Hettihewa 
> wrote:
>
>> Hi all.
>>
>> Tested and verified the following
>>
>>- Human Tasks
>>- Human Task Explorer functionalities with multi tenancy
>>- BPS Tooling
>>- BPEL basic functionalities
>>
>> [+] Stable - go ahead and release.
>> Thanks.
>>
>> On Fri, Aug 26, 2016 at 9:30 AM, Sudharma Subasinghe 
>> wrote:
>>
>>> Verified the following.
>>>  - BPMN Explorer functionalities and multi-tenant support
>>>  - BPEL deployment, execution and clustering with MySql
>>>  - MySql compatibility
>>>  - BPS process cleanup tools with MySql
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks
>>> Sudharma
>>>
>>> On Fri, Aug 26, 2016 at 12:45 AM, Milinda Perera 
>>> wrote:
>>>
 Tested and following:

 Setups : Cluster with MySql + DepSync enabled + fronted by NGINX
 Cluster with Oracle + DepSync enabled + fronted by NGINX

 Tested following:

- Basic functionalities of BPMN, BPEL, WS-Humantask
- BPMN, BPEL and WS-Humantask versioning
- Smoke test on BPMN-Explorer and Humantask-Explorer
- Verify XML and JSON variable types usage
- BPMN, BPEL and WS-Humantask package deployement in tenants
 with DepSync

 [+] Stable - go ahead and release.


 Thanks,
 Milinda

 On Thu, Aug 25, 2016 at 11:23 PM, Amal Gunatilake 
 wrote:

> Hi,
>
> Verified the following.
>
>- BPMN basic functionalities.
>- BPMN Rest Task improvements.
>- Humantask deployments + basic functionalities.
>- BPEL sample deployments + basic functionalities.
>- BPEL process instance cleanup tool.
>- Tested DB2 compatibility for BPEL and Humantask.
>- Oracle compatibility.
>- Tested Substitution feature + Oracle
>
> [+] Stable - go ahead and release.
>
> Best regards,
> Amal.
>
> On Thu, Aug 25, 2016 at 3:41 PM, Milinda Perera 
> wrote:
>
>> Hi APIM and IS team,
>>
>> Could you please tryout your features with BPS with 3.6.0 RC1.
>>
>> Thanks,
>> Milinda
>>
>> On Thu, Aug 25, 2016 at 3:34 PM, Vinod Kavinda 
>> wrote:
>>
>>> Hi,
>>> I verified,
>>>
>>>- Substitution feature.
>>>- BPMN Explorer.
>>>- Human Task Explorer.
>>>- Migration from 3.5.1.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Regards,
>>> Vinod
>>>
>>> On Wed, Aug 24, 2016 at 2:30 PM, Milinda Perera 
>>> wrote:
>>>
 Hi All,

 This is the 1st Release Candidate of WSO2 Business Process Server
 3.6.0

 Please download, test the product and vote. Vote will be open for
 72 hours or as needed.

 *Source and distribution*

 *Run-time* : https://github.com/wso2/produc
 t-bps/releases/tag/v3.6.0-RC1
 *Tooling*  : https://github.com/wso2/devstu
 dio-tooling-bps/releases/tag/Released-release-3.6.0-RC1-2016
 -08-24-114818

 Please vote as follows.
 [+] Stable - go ahead and release
 [-] Broken - do not release (explain why)

 Thanks,
 ~ WSO2 BPS Team ~

 --
 Milinda Perera
 Senior Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


>>>
>>>
>>> --
>>> Vinod Kavinda
>>> Software Engineer
>>> *WSO2 Inc. - lean . enterprise . middleware .*
>>> Mobile : +94 (0) 712 415544
>>> Blog : http://soatechflicks.blogspot.com/
>>> [image: http://wso2.com/signature]
>>> 
>>>
>>>
>>
>>
>> --
>> Milinda Perera
>> Senior Software Engineer;
>> WSO2 Inc. http://wso2.com ,
>> Mobile: (+94) 714 115 032
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Amal Gunatilake*
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> mobile: (+94) 773561195
> blog: amalg-blogs.blogspot.com; twitter: @daag123
> linkedIn: https://www.linkedin.com/in/amalgunatilake
>



 --
 Milinda Perera
 Senior Software Engineer;
 WSO2 Inc. http://wso2.com ,
 Mobile: (+94) 714 115 032


 ___
 Dev mailing list
 Dev@wso2.org
>>

Re: [Dev] [ESB] Error in running a sample provided in the doc

[Nadeesha Gamage]

Hi Jagath,
Yes this seems to be the issue, I just tried with a REST client and its
able to send the request correctly. Curl seems to be dropping out the "
sign from the message payload.


Thank you,
Nadeesha

On Fri, Aug 26, 2016 at 1:40 AM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi Nadeesha,
>
> Seems the payload received to the ESB '{name:WSO2}'does not contain
> double quotes. Correct payload should be '{"name":"WSO2"}'.
>
> Lets check wire logs to get it confirmed that ESB received correct payload.
>
> Thanks.
>
> On Wed, Aug 24, 2016 at 12:07 PM, Nadeesha Gamage 
> wrote:
>
>> Hi all,
>> I am referring to the following document [1], and have deployed the CAR
>> file provided [2]. When I try to invoke the API using the provided curl
>> command I get the following error. Can someone help to get this resolved.
>>
>> curl -X POST http://localhost:8280/stockquote/getQuote -d
>> '{"name":"WSO2"}' -H "Content-Type:application/json"
>>
>>
>> TID: [-1234] [] [2016-08-24 11:56:57,576]  INFO
>> {org.apache.synapse.mediators.builtin.LogMediator} -  To:
>> /stockquote/getQuote, MessageID: 
>> urn:uuid:a688b5fd-4db3-46b2-9a7d-78797558de89,
>> Direction: request, Payload: '{name:WSO2}' {org.apache.synapse.mediators.
>> builtin.LogMediator}
>> TID: [-1234] [] [2016-08-24 11:56:57,585] ERROR
>> {org.apache.synapse.util.xpath.SynapseJsonPath} -  #stringValueOf. Error
>> evaluating JSON Path <$.name>. Returning empty result. Error>>> Invalid
>> container object {org.apache.synapse.util.xpath.SynapseJsonPath}
>> TID: [-1234] [] [2016-08-24 11:56:57,595] ERROR
>> {org.apache.axiom.om.impl.llom.OMSourcedElementImpl} -  Could not get
>> parser from data source for element jsonObject
>> {org.apache.axiom.om.impl.llom.OMSourcedElementImpl}
>> javax.xml.stream.XMLStreamException
>> at org.apache.synapse.commons.staxon.core.base.AbstractXMLStrea
>> mReader.initialize(AbstractXMLStreamReader.java:245)
>> at org.apache.synapse.commons.staxon.core.json.JsonXMLStreamRea
>> der.(JsonXMLStreamReader.java:66)
>> at org.apache.synapse.commons.staxon.core.json.JsonXMLInputFact
>> ory.createXMLStreamReader(JsonXMLInputFactory.java:165)
>> at org.apache.synapse.commons.json.JsonUtil.getReader(JsonUtil.java:302)
>> at org.apache.synapse.commons.json.JsonDataSource.getReader(Jso
>> nDataSource.java:153)
>> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getDirect
>> Reader(OMSourcedElementImpl.java:225)
>> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpa
>> nd(OMSourcedElementImpl.java:254)
>> at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getChildr
>> en(OMSourcedElementImpl.java:859)
>> at org.apache.synapse.commons.json.JsonUtil.removeIndentations(
>> JsonUtil.java:417)
>> at org.apache.synapse.commons.json.JsonUtil.removeIndentations(
>> JsonUtil.java:425)
>> at org.apache.synapse.commons.json.JsonUtil.removeJsonPayload(
>> JsonUtil.java:731)
>> at org.apache.synapse.mediators.transform.PayloadFactoryMediato
>> r.mediate(PayloadFactoryMediator.java:163)
>> at org.apache.synapse.mediators.transform.PayloadFactoryMediato
>> r.mediate(PayloadFactoryMediator.java:104)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:89)
>> at org.apache.synapse.mediators.AbstractListMediator.mediate(Ab
>> stractListMediator.java:59)
>> at org.apache.synapse.mediators.base.SequenceMediator.mediate(S
>> equenceMediator.java:158)
>> at org.apache.synapse.rest.Resource.process(Resource.java:343)
>> at org.apache.synapse.rest.API.process(API.java:399)
>> at org.apache.synapse.rest.RESTRequestHandler.apiProcess(RESTRe
>> questHandler.java:120)
>> at org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RES
>> TRequestHandler.java:101)
>> at org.apache.synapse.rest.RESTRequestHandler.process(RESTReque
>> stHandler.java:69)
>> at org.apache.synapse.core.axis2.Axis2SynapseEnvironment.inject
>> Message(Axis2SynapseEnvironment.java:304)
>> at org.apache.synapse.core.axis2.SynapseMessageReceiver.receive
>> (SynapseMessageReceiver.java:75)
>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>> at org.apache.synapse.transport.passthru.ServerWorker.processNo
>> nEntityEnclosingRESTHandler(ServerWorker.java:325)
>> at org.apache.synapse.transport.passthru.ServerWorker.processEn
>> tityEnclosingRequest(ServerWorker.java:371)
>> at org.apache.synapse.transport.passthru.ServerWorker.run(Serve
>> rWorker.java:151)
>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.
>> run(NativeWorkerPool.java:172)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>> Executor.java:1110)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>> lExecutor.java:603)
>> at java.lang.Thread.run(Thread.java:722)
>> TID: [-1234] [] [2016-08-24 11:56:57,613] ERROR
>> {org.apache.synapse.mediators.base.SequenceMediator} -  Error obtaining
>> parser from data source:null {org.apache.synapse.mediators.
>> base.SequenceMediator}
>> java.lang.Runtim

Re: [Dev] [ESB] Enable debug logs for proxies and apis

[Nadeeshaan Gunasinghe]

Hi Udara,

You  can achieve this by adding the following property

*log4j.category.org.apache.synapse.mediators.builtin.LogMediator=DEBUG*

Thanks,

*Nadeeshaan Gunasinghe*
Software Engineer, WSO2 Inc. http://wso2.com
+94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe <#>

  

Get a signature like this: Click here!


On Tue, Jul 26, 2016 at 10:40 AM, Udara Liyanage  wrote:

> Hi Elilmatha,
>
> 1) I want to enable it for every proxy and api, otherwise we have to add
> log4j configs every time we add a proxy and api which is not practical
> where there are 10+ proxies
>
> 2) Below is my api config and log4j config. Still debug logs are not
> printed.
>
> http://ws.apache.org/ns/synapse"; name="*getUsers*"
> context="/users">
>
>   
>  
> 
>  
>  
> 
>  
> 
>   
>   
>
> 
>
>
> # Configure the service logger at INFO level. Writes only
> run-time/mediation-time audit messages
> log4j.category.SERVICE_LOGGER.*getUsers*=DEBUG, SERVICE_APPENDER
> log4j.additivity.SERVICE_LOGGER=false
> log4j.appender.SERVICE_APPENDER=org.apache.log4j.RollingFileAppender
> #log4j.appender.SERVICE_APPENDER.File=${carbon.home}/
> repository/logs/${instance.log}/wso2-esb-service${instance.log}.log
> log4j.appender.SERVICE_APPENDER.File=${carbon.home}/
> repository/logs/${instance.log}/wso2-esb-*get-users*${instance.log}.log
> log4j.appender.SERVICE_APPENDER.MaxFileSize=1000KB
> log4j.appender.SERVICE_APPENDER.MaxBackupIndex=10
> log4j.appender.SERVICE_APPENDER.layout=org.apache.log4j.PatternLayout
> log4j.appender.SERVICE_APPENDER.layout.ConversionPattern=%d{ISO8601}
> [%X{ip}-%X{host}] [%t] %5p %c{1} %m%n
>
> On Tue, Jul 26, 2016 at 10:17 AM, Elilmatha Sivanesan 
> wrote:
>
>> Hi Udara,
>>
>> Can you try by adding the following entries into your log4j.properties
>> file ,In this way, you might need to add separate blocks of configuration
>> for all configured proxies.(assumes a proxy service named TestProxy):
>>
>> log4j.category.SERVICE_LOGGER.TestProxy= 
>> DEBUG,PROXY_APPENDERlog4j.additivity.PROXY_APPENDER=falselog4j.appender.PROXY_APPENDER=org.apache.log4j.DailyRollingFileAppenderlog4j.appender.PROXY_APPENDER.File=${carbon.home}/repository/logs/${instance.log}/wso2-esb-test-proxy${instance.log}.loglog4j.appender.PROXY_APPENDER.Append=truelog4j.appender.PROXY_APPENDER.layout=org.apache.log4j.PatternLayoutlog4j.appender.PROXY_APPENDER.layout.ConversionPattern=%d{HH:mm:ss,SSS}
>>  [%X{ip}-%X{host}] [%t] %5p %c{1} %m%
>>
>>
>> Thanks
>>
>> On Tue, Jul 26, 2016 at 9:33 AM, Udara Liyanage  wrote:
>>
>>> Hi,
>>>
>>> I want to set some logs to debug in log mediator. When I set log
>>> category to DEBUG and enable DEBUG in SERVICE_LOGGER, I don't see any logs
>>> in any of the file inside logs folder. How do we enable debug logs for APIs
>>> and proxies?
>>>
>>>  
>>> 
>>>  
>>>  
>>> 
>>>  
>>>
>>> log4j.category.SERVICE_LOGGER=*DEBUG*, SERVICE_APPENDER
>>> log4j.additivity.SERVICE_LOGGER=false
>>> log4j.appender.SERVICE_APPENDER=org.apache.log4j.RollingFileAppender
>>> log4j.appender.SERVICE_APPENDER.File=${carbon.home}/
>>> repository/logs/${instance.log}/wso2-esb-service${instance.log}.log
>>> log4j.appender.SERVICE_APPENDER.File=${carbon.home}/
>>> repository/logs/${instance.log}/wso2-esb-get-users${instance.log}.log
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> Blog: http://udaraliyanage.wordpress.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *S.Elilmatha*
>> Software Engineer,
>>
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile 0779842221.
>>
>>
>
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> Blog: http://udaraliyanage.wordpress.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.9 RC2

[Thusitha Thilina Dayaratne]

Hi All,

Due to the issue reported by IS team, we will call off this vote. And as
the fix, we will downgrade the h2 version to 1.3.175 and do a RC3 release
as soon as possible.

Thanks
Thusitha

On Thu, Aug 25, 2016 at 3:42 PM, Kalpa Welivitigoda  wrote:

> Hi Kasun,
>
> I came across [1] which matches with your observations with IS (Starting,
> shutdown and restart the server). According to [1] this is a bug in 1.3.176
> and is fixed in 1.4.179 Beta [2].
>
> [1] https://groups.google.com/forum/#!topic/h2-database/5LZlZ_jC4QI
> [2] http://www.h2database.com/html/changelog.html
>
>
> On Thu, Aug 25, 2016 at 2:58 PM, Kalpa Welivitigoda 
> wrote:
>
>> Hi Kasun,
>>
>> We have updated h2 database from 1.2.140 to 1.3.176 and that would be the
>> root cause for the exception. We need to dig a bit and look into the schema
>> restrictions introduced in h2.
>>
>> @Manuri, thanks for the clarification.
>> @Madhawa, sorry I misunderstood your point at the first place.
>>
>> On Thu, Aug 25, 2016 at 12:47 PM, Kasun Bandara  wrote:
>>
>>> Hi Kalpa,
>>>
>>> When we running the IS integration tests, we encountered the following
>>> issue upon restarting the sever. This is reproducible with the following
>>> sequence in a fresh pack which built top of kernel 4.4.9.
>>>
>>> 1) Start up the server
>>> 2) Shutdown the server
>>> 3) Restart the server
>>>
>>> 2016-08-25 11:31:35,677] ERROR {org.wso2.carbon.user.core.util.DatabaseUtil}
>>> -  Database Error - Unique index or primary key violation: "PRIMARY KEY ON
>>> .PAGE_INDEX"; SQL statement:
>>> ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
>>> PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
>>> PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
>>> [23505-176]
>>> org.h2.jdbc.JdbcSQLException: Unique index or primary key violation:
>>> "PRIMARY KEY ON .PAGE_INDEX"; SQL statement:
>>> ALTER TABLE PUBLIC.IDN_OAUTH2_ACCESS_TOKEN_SCOPE ADD CONSTRAINT
>>> PUBLIC.CONSTRAINT_B1A FOREIGN KEY(TOKEN_ID) REFERENCES
>>> PUBLIC.IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE NOCHECK
>>> [23505-176]
>>> at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
>>> at org.h2.message.DbException.get(DbException.java:178)
>>> at org.h2.message.DbException.get(DbException.java:154)
>>> at org.h2.index.PageDataIndex.getNewDuplicateKeyException(PageD
>>> ataIndex.java:166)
>>> at org.h2.index.PageDataIndex.add(PageDataIndex.java:144)
>>> at org.h2.store.PageStore.addMeta(PageStore.java:1808)
>>> at org.h2.index.PageBtreeIndex.(PageBtreeIndex.java:64)
>>> at org.h2.table.RegularTable.addIndex(RegularTable.java:235)
>>> at org.h2.command.ddl.AlterTableAddConstraint.createIndex(Alter
>>> TableAddConstraint.java:280)
>>> at org.h2.command.ddl.AlterTableAddConstraint.tryUpdate(AlterTa
>>> bleAddConstraint.java:205)
>>> at org.h2.command.ddl.AlterTableAddConstraint.update(AlterTable
>>> AddConstraint.java:73)
>>> at org.h2.engine.MetaRecord.execute(MetaRecord.java:59)
>>> at org.h2.engine.Database.open(Database.java:719)
>>> at org.h2.engine.Database.openDatabase(Database.java:260)
>>> at org.h2.engine.Database.(Database.java:254)
>>> at org.h2.engine.Engine.openSession(Engine.java:57)
>>> at org.h2.engine.Engine.openSession(Engine.java:164)
>>> at org.h2.engine.Engine.createSessionAndValidate(Engine.java:142)
>>> at org.h2.engine.Engine.createSession(Engine.java:125)
>>> at org.h2.engine.Engine.createSession(Engine.java:27)
>>> at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionR
>>> emote.java:331)
>>> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:107)
>>> at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:91)
>>> at org.h2.Driver.connect(Driver.java:74)
>>> at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(
>>> PooledConnection.java:278)
>>> at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledC
>>> onnection.java:182)
>>> at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(
>>> ConnectionPool.java:701)
>>> at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(
>>> ConnectionPool.java:635)
>>> at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(Con
>>> nectionPool.java:188)
>>> at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(Da
>>> taSourceProxy.java:127)
>>> at org.wso2.carbon.user.core.claim.dao.ClaimDAO.getDialectCount
>>> (ClaimDAO.java:158)
>>> at org.wso2.carbon.user.core.common.DefaultRealm.populateProfil
>>> eAndClaimMaps(DefaultRealm.java:448)
>>> at org.wso2.carbon.user.core.common.DefaultRealm.init(DefaultRe
>>> alm.java:124)
>>> at org.wso2.carbon.user.core.common.DefaultRealmService.initializeRealm(
>>> DefaultRealmService.java:263)
>>> at org.wso2.carbon.user.core.common.DefaultRealmService.(
>>> DefaultRealmService.java:100)
>>> at org.wso2.carbon.user.core.common.DefaultRealmService.(
>>> DefaultRealmService.java:113)
>>> at org.wso2.carbon.user.core.internal.Activator.startDeploy(Act
>>> ivator.java:68)
>>> at org.wso2.carbon.user.c