Hi Pulasthi,
I don't think so, because the UES jaggery apps operate on the root context
and so are not affected by carbon.xml webcontextroot changes. Manuranga
please correct me if I am wrong in this regard.
Thanks,
Gokul.
On 13 September 2013 11:24, Pulasthi Supun pulas...@wso2.com wrote:
yes gokul, this fix applies only if you don't want to change web context
root via carbon.xml
if you have changed it that way, this problem would not occur in the first
place and you can use UES as is.
On Fri, Sep 13, 2013 at 11:24 AM, Pulasthi Supun pulas...@wso2.com wrote:
Hi Manu,
Since
Hi Kasun et al,
we should try to use one minor ESB version across chunk releases...
(2.1.2-wso2v1).
ESB team owns the synapse core. Others have to wait till they release..
Hence IMHO, ELB should use, 2.1.2-wso2v1.
On Sat, Sep 7, 2013 at 11:08 PM, Vanjikumaran Sivajothy va...@wso2.comwrote:
Hi,
ahh ok got it, thanks for the clarification :)
Regards,
Pulasthi
On Fri, Sep 13, 2013 at 11:31 AM, Manuranga Perera m...@wso2.com wrote:
yes gokul, this fix applies only if you don't want to change web context
root via carbon.xml
if you have changed it that way, this problem would not
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR] The project
org.wso2.carbon:product-releases-components:4.2.0-chunk02
(/home/ajith/wso2/build/platform/4.2.0/product-releases/chunk-02/components/pom.xml)
has 1 error
[ERROR] Child module
On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne chama...@wso2.comwrote:
Why this comes when API M joins ELB. (ELB local member port 4000)
[2013-09-12 17:31:35,189] INFO - MemberUtils Added member:
Host:127.0.0.1, Remote Host:null, Port: 4000, HTTP:-1, HTTPS:-1, Domain:
null,
Hi all,
In chunk-02 features/pom, the registry features
org.wso2.carbon.registry.community.features.feature
org.wso2.carbon.governance.metadata.feature
are pointing to 4.2.1 version. But they don't seem to have been released
with chunk-01 (with a 4.2.0 version). Is there any reason for using
HI
Can we know the solution for the given issue, ESB team suppose to run
extensive tests for *connectors* in W/M setup, but the reported issue
holding us for 2 days..appreciate quick feed-back soon..
Cheers
Dushan
On Thu, Sep 12, 2013 at 7:28 PM, Isuru Perera isu...@wso2.com wrote:
Hi
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:18.445s
[INFO] Finished at: Thu Sep 12 23:20:03 PDT 2013
[INFO] Final Memory: 315M/1255M
[INFO]
[ERROR]
Hi Ajith,
We are working on it, BTW in you case, don't need to create 4.2.1 version
of org.wso2.carbon.core only released *platform *components need that
version increment. Your change will go with patch0001.
Thanks,
Shameera.
On Fri, Sep 13, 2013 at 11:22 AM, Ajith Vitharana aji...@wso2.com
The main issue here is that ELB/API-M releases go with chunk 2 while ESB is
planned for chunk 3. We are doing quite a lot of changes in synapse-core
for connector work and that's why we let ELB/API-M to go with 2.1.1v9
version(We are applying all critical fixes for both synapse versions).
Ideally,
Hi Bhathiya,
Have you got an svn up in the stubs.. If not please take an up and see..
We have done a clean repo build yesterday in builder machine but it is working..
Regards,
Mohan..
On Fri, Sep 13, 2013 at 12:05 PM, Bhathiya Jayasekara bhath...@wso2.com wrote:
[INFO] BUILD FAILURE
[INFO]
Hi Kasun,
yes understood the reason, why we are doing this. However, we should also
note that this introduces interop issues at feature level. (p2 story)
--Pradeep
On Fri, Sep 13, 2013 at 12:11 PM, Kasun Indrasiri ka...@wso2.com wrote:
The main issue here is that ELB/API-M releases go with
If would be great if someone from platform team can take a look. Amal is
currently working on another bps task.
Regards
Nandika
On Thu, Sep 12, 2013 at 9:10 PM, Nirmal Fernando nir...@wso2.com wrote:
Did anyone look after this issue?
On Mon, Sep 2, 2013 at 11:58 AM, Amal Gunatilake
Hi Mohan,
On Fri, Sep 13, 2013 at 12:14 PM, Mohanadarshan Vivekanandalingam
mo...@wso2.com wrote:
Hi Bhathiya,
Have you got an svn up in the stubs.. If not please take an up and see..
I just got and update in service stubs but nothing updated.
Thanks,
Bhathiya
We have done a clean
Carbon team FYI.
On Fri, Sep 13, 2013 at 12:19 PM, Nandika Jayawardana nand...@wso2.comwrote:
If would be great if someone from platform team can take a look. Amal is
currently working on another bps task.
Regards
Nandika
On Thu, Sep 12, 2013 at 9:10 PM, Nirmal Fernando nir...@wso2.com
ELB 2.1.0 10/09/2013 build
http://10.100.1.185/packs/sep-10
APIM RC2 12/09/2013
http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/AM/
On Fri, Sep 13, 2013 at 11:46 AM, Amila Maha Arachchi ami...@wso2.comwrote:
On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne
On Fri, Sep 13, 2013 at 11:49 AM, Lasantha Fernando lasan...@wso2.comwrote:
Hi all,
In chunk-02 features/pom, the registry features
org.wso2.carbon.registry.community.features.feature
org.wso2.carbon.governance.metadata.feature
are pointing to 4.2.1 version. But they don't seem to have
Hi all,
What's the plan for fixing these? We have 2 L1 issues, which doesn't seem
to be getting the right attention. Shall I move to AM?
[1] https://wso2.org/jira/browse/REGISTRY-1862
[2] https://wso2.org/jira/browse/REGISTRY-1861
Thanks,
Senaka.
On Thu, Sep 12, 2013 at 10:10 AM, Lakmali
Hi Sameera,
Do we have a milestone plan for kernel 5.0.0 release.. If not shall we
start building one...
IMO a milestone deliverable can be a product distribution or even a
finalized design artifact.. It would be better if we try to cover most of
the ground level stuff by end of this year...
Saw this in the APIM big deployment too.
TID: [0] [AM] [2013-09-13 11:43:14,390] INFO
{org.apache.synapse.transport.passthru.PassThroughHttpListener} -
Pass-through HTTP Listener started on 0:0:0:0:0:0:0:0:10280
{org.apache.synapse.transport.passthru.PassThroughHttpListener}
TID: [0] [AM]
Reason for [1] is not sharing the API-M database among the two nodes in the
cluster. We have fixed the issue in [2], Aparna is still to confirm whether
it worked (check JiRA comment). Can you please verify these in the latest
build (last night)?
Thanks,
NuwanD.
On Fri, Sep 13, 2013 at 12:21 PM,
This logs appear when ELB joins ELB cluster.. I guess its harmless.
On Thu, Sep 12, 2013 at 11:03 PM, Chamara Ariyarathne chama...@wso2.comwrote:
Why this comes when API M joins ELB. (ELB local member port 4000)
[2013-09-12 17:31:35,189] INFO - MemberUtils Added member:
Host:127.0.0.1,
Hi Sameera,
There are set of registry bundles released with chunk01, but the features
which are bundled those jars not released.
eg: released registry bundles.
moduleorg.wso2.carbon.registry.admin.api/4.2.0/module
Hi,
I am also getting the same error while trying to build with clean repo.
Thanks and Regards,
-Ayash
On Fri, Sep 13, 2013 at 11:39 AM, Ajith Vitharana aji...@wso2.com wrote:
[INFO] Scanning for projects...
[ERROR] The build could not read 1 project - [Help 1]
[ERROR]
[ERROR] The
Hi Prabath,
We don't have a milestone plan at the moment. We had the initial high level
discussions sometime back. The plan is to kick off the low level meetings
during the week starting from 23rd of September. I am in support and Azeez
is away during the next week.
In mean time I will start the
Hi,
Issue is moved to CARBON project. Will check..
Thanks,
Manoj
Best Regards..
Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com
Twitter: http://twitter.com/ManKuma
Mobile: +94713448188
On Fri, Sep 13, 2013 at 12:21 PM, Nirmal Fernando nir...@wso2.com wrote:
Carbon team FYI.
Hi Nuwan,
Both the issues were fixed with Ruwan's patch according to Aparna. He has
not resolved since he didn't have time to validate with fresh G-Reg packs.
I marked them as fixed, and Aparna will reopen if it still exists.
Thanks,
Senaka.
On Fri, Sep 13, 2013 at 12:36 PM, Nuwan Dias
Hi
Do you have any customized log4j.properties in your BPS pack? Sometimes,
improper configuration of log4j.properties would also cause the same issue.
Thanks,
Reka
On Mon, Sep 2, 2013 at 11:58 AM, Amal Gunatilake am...@wso2.com wrote:
Please have a look.
Hi Nirmal,
We really appreciate your reminder and as well as your motivation of going
after everything even they are not related to you. We will take this from
now on.
Thanks,
Sameera.
On Fri, Sep 13, 2013 at 12:21 PM, Nirmal Fernando nir...@wso2.com wrote:
Carbon team FYI.
On Fri, Sep
Hi Sameera,
Can you pls commit this to trunk. I'm getting a build failure..
thanks,
On Sat, Aug 31, 2013 at 5:00 PM, same...@wso2.com wrote:
Author: same...@wso2.com
Date: Sat Aug 31 17:00:02 2013
New Revision: 183767
URL: http://wso2.org/svn/browse/wso2?view=revrevision=183767
Log:
Hi,
We are unable to test on ELB fronted Greg clustered setup due to timeout
issue, because of this issue we are testing the Greg without the ELB. We
have reported this issue with chunk01 release as well (Refer mail thread
[1]).
Therefore we won't be able to release the ELB 2.1.0 with chunk02
Hi,
ELB should be using 2.1.1.wso2v9 and I fixed it in chunk-02 earlier.
I will check.
Thanks!
On Thu, Sep 12, 2013 at 8:01 PM, Ruwan Yatawara ruw...@wso2.com wrote:
Hi Isuru,
The mediation component which is needed for building ELB is referring to
Synapse version 2.1.2.wso2v1, I was
$subject. This is the error. Seems security verifier pom refers to a wrong
parent pom.
[ERROR] The project org.wso2.carbon:SecVerifier:4.2.0
(/home/maninda/c/carbon/kernel/branches/4.2.0/distribution/integration/security-verifier/pom.xml)
has 1 error
[ERROR] Non-resolvable parent POM:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.
https://wso2.org/jira/browse/APIMANAGER-1649
TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
What is the ELB version being used?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in
Geeth,
Did you commit your fixes to trunk which fix this AuthenticationAdmin
requests getting dispatched to ELB issue?
On Fri, Sep 13, 2013 at 3:07 PM, Nuwan Dias nuw...@wso2.com wrote:
What is the ELB version being used?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com
ELB 2.1.0 from sept10th build.
On Fri, Sep 13, 2013 at 3:09 PM, Nirmal Fernando nir...@wso2.com wrote:
Geeth,
Did you commit your fixes to trunk which fix this AuthenticationAdmin
requests getting dispatched to ELB issue?
On Fri, Sep 13, 2013 at 3:07 PM, Nuwan Dias nuw...@wso2.com wrote:
Shouldn't this case hold true for ESB , DSS or any other server that pushes
XML content through Admin service calls?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod niro...@wso2.com wrote:
Hi,
Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems
Isuru,
This is a blocker for chunk02.
On Fri, Sep 13, 2013 at 3:16 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Shouldn't this case hold true for ESB , DSS or any other server that
pushes XML content through Admin service calls?
On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod
Hi Sumedha,
I will check on this.
On Fri, Sep 13, 2013 at 3:18 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Isuru,
This is a blocker for chunk02.
On Fri, Sep 13, 2013 at 3:16 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
Shouldn't this case hold true for ESB , DSS or any other server
Hi,
Geeth has already committed related changes. Please see:
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.2.0/dependencies/synapse/2.1.1-wso2v9/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/nhttp/util/RESTUtil.java
Hi All,
Observed the following error in the latest pack (G-Reg) - chunk02
[2013-09-13 15:52:39,357] ERROR
{org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} - Error
while running deployment scheduler..
java.util.ConcurrentModificationException
at
Hi I'm getting the following error when trying to build mediation-library
component.
[INFO] -
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Carbon - Mediation
Pls make sure you did build the relevant service stubs successfully.
On Fri, Sep 13, 2013 at 4:05 PM, Ruwan Yatawara ruw...@wso2.com wrote:
Hi I'm getting the following error when trying to build mediation-library
component.
[INFO]
Hi,
I noticed some of the
issueshttps://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+10210+AND+labels+%3D+passthru-transportwere
marked as fixed today. Thanks for looking in to those.
There are few in open state still. For example,
https://wso2.org/jira/browse/LB-88.
Hi Danushka,
U have updated the stratos.common.server feature, but not added a new
stratos.common feature.
I made the necessary changes.
Regards,
Ruwan Yatawara
Software Engineer,
WSO2 Inc.
lean . enterprise . middleware
email : ruw...@wso2.com
mobile : +94 77 9110413
blog :
Apart from JIRA
issueshttps://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+LB+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%222.1.0%22+ORDER+BY+priority+DESCmode=hide,
following are the critical issues for ELB 2.1.0 now.
- [Dev] [Blocker] Cannot Publish APIs to
Hi All,
I will update with coverage report by Monday for the first week. I have to
complete few more things in multiple user store scenarios. Sorry for the
delay.
Thanks,
Pushpalanka Jayawardhana
Software Engineer
WSO2 Lanka (pvt) Ltd
[image:
Hi All,
CEP 3.0.0 RC3 pack also contains similar issue... Chathurika has
reported this issue in https://wso2.org/jira/browse/CEP-427.
Thanks Regards,
Mohan
On Wed, Aug 7, 2013 at 3:07 PM, Asela Pathberiya as...@wso2.com wrote:
We did not found this issue in the AS pack in here[1]. I do not
Hi,
Currently, the WSO2 ELB loadbalancer.conf has links to following blog
articles.
-
http://nirmalfdo.blogspot.com/2012/06/fronting-wso2-application-server-50.html
- http://blog.afkham.org/2011/09/wso2-load-balancer-how-it-works.html
-
Hi Piyum,
What was the fix for the issue? I cannot locate a commit mail for this
particular issue.
I got the same with ELB 2.0.3 as well.
Thanks and Regrads,
Harshana
On Fri, Aug 23, 2013 at 12:05 AM, Piyum Fernando pi...@wso2.com wrote:
Hi Ishan,
We fixed the issue mentioned in
+1, In fact those blogs are now obsolete, we shouldn't use them.
Those times, we didn't have any wiki docs and no one could get the essence
of clustering without reading blogs.
On Sat, Sep 14, 2013 at 1:12 AM, Isuru Perera isu...@wso2.com wrote:
Hi,
Currently, the WSO2 ELB loadbalancer.conf
Hi Nirmal,
What is the possibility of getting this error actually the members are
live? A network outage?
Thanks and Regards,
Harshana
On Wed, Mar 13, 2013 at 11:13 AM, Nirmal Fernando nir...@wso2.com wrote:
You can ignore this exception. You had a member and it seems to be no more
there:
On Sat, Sep 14, 2013 at 6:00 AM, Harshana Martin harsh...@wso2.com wrote:
Hi Nirmal,
What is the possibility of getting this error actually the members are
live? A network outage?
Yes, when a sudden n/w outage occur, nodes might detect some nodes as
faulty members.
Thanks and Regards,
Any Help on this. It is big company and if they do not find it secure we have
to drop the implementation.
Please help.
thanks
Abhijit
On Sep 12, 2013, at 3:39 PM, Abhijit Diwan wrote:
Hi All
We are in final few steps of WSO2 ESB / Data services implementation at
very big company.
Hi Diwan,
Please see the answers for some of the questions.
On Sat, Sep 14, 2013 at 6:28 AM, Abhijit Diwan adi...@apple.com wrote:
Any Help on this. It is big company and if they do not find it secure we
have to drop the implementation.
Please help.
thanks
Abhijit
On Sep 12, 2013, at
Hi All,
Please apply this patch as well [2]. You need to apply this to
org.wso2.carbon.registry.core
The test summary with the patch : Tests run: 173, Failures: 0, Errors: 0,
Skipped: 0
[2]https://wso2.org/jira/browse/REGISTRY-1911
Thanks
Ajith.
On Thu, Sep 12, 2013 at 2:03 PM, Ajith
Hi Ajith,
Can you please explain the code in the patch..
+// This is for fixing REGISTRY-1911
+try {
+if (userName == null CurrentSession.getUser() != null
+
!CurrentSession.getUser().equals(CarbonConstants.REGISTRY_SYSTEM_USERNAME))
{
+UserRealm
Hi Ajith,
I've applied REGISTRY-1941.
Sameera.
On Thu, Sep 12, 2013 at 2:03 PM, Ajith Vitharana aji...@wso2.com wrote:
Hi Shameera,
Please apply the patch [1] for chunk02 release.
[1]https://wso2.org/jira/browse/REGISTRY-1941
Thanks
Ajith
--
Ajith Vitharana.
WSO2 Inc. -
Hi,
I need to test JWTCache in AM. Therefore I have enabled GatewayKeyCache
and disabled JWTCache in api-manager.xml and invoked an API via an
application then changed the application name and invoked again. Then
decoded the response. But still the application name is not changed
even-though I
61 matches
Mail list logo
