On Thu, Jul 19, 2012 at 10:11 AM, Damitha Kumarage dami...@wso2.com wrote:
Also AliveMemberCount in LB is always 0. Does that mean although there are
successful join messages, in actuality no app server never joined?
No that means how many other LBs are there. That log could make more
Hi,
Recently we had a few issues [1][2] when invoking REST services via
ESB REST API when client sends information with the content type TEXT/XML
(and if BACK END accepts TEXT/XML) so when message receives to ESB if the
content type is defined TEXT/XML by default it will try to build up SOAP
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2:34:52.513s
[INFO] Finished at: Wed Jul 18 23:47:33 IST 2012
[INFO] Final Memory: 909M/1721M
[INFO]
-- Forwarded message --
From: Bamboo cbuil...@wso2.org
Date: Thu, Jul 19, 2012 at 11:59 AM
Subject: [Bamboo-Build] Sonar Reporting Platform #66 has FAILED. Change
made by 16 authors.
To: mahesh...@wso2.com
[image: Failed] Sonar Reporting
Though your observation is correct here actual issue is not related to
MessageBuilders/MessageFormatters instead of not picking correct
MessageBuilder/MessageFormatter combination. Axis2 REST guide contains
following text
if the content type is text/xml and if the SOAPAction Header is missing,
Hi
For an example, in API Manager if you send a POX message with the
text/xml, the query parameters on the URL do not get passed to the backend
server, whereas they will get passed if we use application/xml instead
My thought is,
POX message received with text/xml
This solution will take care of the message parsing issue. But the main
problem is Synapse and Axis2 both associating text/xml with SOAP 1.1.
There's a lot of code written based on this assumption. For instance the
parsing issue can be worked around by using something like the message
relay (we do
On Thu, Jul 19, 2012 at 2:06 PM, Hiranya Jayathilaka hira...@wso2.comwrote:
This solution will take care of the message parsing issue. But the main
problem is Synapse and Axis2 both associating text/xml with SOAP 1.1.
There's a lot of code written based on this assumption. For instance the
This dependency is not valid anymore. Therefore, I removed it from
usage.agent/pom.xml.
Regards,
AmilaM.
On Thu, Jul 19, 2012 at 1:38 PM, Afkham Azeez az...@wso2.com wrote:
[INFO] BUILD FAILURE
[INFO]
[INFO] Total
Now that build failure went away but I am faced with a new failure
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:11.081s
[INFO] Finished at:
Will look into this with deleting jars in my repo (coz you are trying with
a clean repo).
On Thu, Jul 19, 2012 at 2:40 PM, Afkham Azeez az...@wso2.com wrote:
Now that build failure went away but I am faced with a new failure
[INFO]
On Thu, Jul 19, 2012 at 2:04 PM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi
For an example, in API Manager if you send a POX message with the
text/xml, the query parameters on the URL do not get passed to the backend
server, whereas they will get passed if we use application/xml
guys,
are we building the src with a clean repo, in bamboo ?
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Thu, Jul 19, 2012 at 2:54 PM, Pradeep Fernando prad...@wso2.com wrote:
guys,
are we building the src with a clean repo, in bamboo ?
Not all the time. If it is needed only the build goes with clean repo.
--Pradeep
--
*Kishanthan Thangarajah*
Software Engineer,
Development
Hi,
On Thu, Jul 19, 2012 at 2:55 PM, Kishanthan Thangarajah kishant...@wso2.com
wrote:
On Thu, Jul 19, 2012 at 2:54 PM, Pradeep Fernando prad...@wso2.comwrote:
guys,
are we building the src with a clean repo, in bamboo ?
Not all the time. If it is needed only the build goes with clean
I tried with removing uddi jar from my repo. But I do not get the checksum
validation failure error you get. But I don't see the pom for uddi4j-1.0.1
at [1]. But it is there in [2].
[1] http://maven.wso2.org/nexus/content/groups/wso2-public/uddi/uddi4j/1.0.1/
[2]
Hi,
I have a App server cluster of 2 servers (Beta 2 packs) clustered using
'wka' method.
For master node,
AutoCommittrue/AutoCommit
AutoCheckouttrue/AutoCheckout
and slave node,
AutoCommitfalse/AutoCommit
AutoCheckouttrue/AutoCheckout
When i create a new
On Thu, Jul 19, 2012 at 2:59 PM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
On Thu, Jul 19, 2012 at 2:55 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:
On Thu, Jul 19, 2012 at 2:54 PM, Pradeep Fernando prad...@wso2.comwrote:
guys,
are we building the src with a clean repo,
Hi All,
I have mounted two registry instance and i got the following error while
restarting the master node.
chedulerServiceComponent
*[2012-07-19 16:31:34,626] ERROR
{org.wso2.carbon.identity.core.internal.IdentityCoreServiceComponent} -
Error occured while populating identity configuration
Hi Product Teams,
This is to remind you to add Product Categories to our P2 feature
repository.
Currently it only has App Server, DSS and BAM Data Agent as categories.
Please add your Product also as a category. This is important since it will
give users a complete list of product categories when
If this issue is real, then it is a blocking issue for our PHP Cartridge
release.
Thanks,
Damitha
On Thu, Jul 19, 2012 at 3:32 PM, Lahiru Sandaruwan lahi...@wso2.com wrote:
Hi,
I have a App server cluster of 2 servers (Beta 2 packs) clustered using
'wka' method.
For master node,
There is a way to associate a MessageBuilder to a URL. AFAIK this
functionality was implemented for the Nhttp transport. I can't remember the
exact details. But this may be a cleaner approach.
Thanks,
Supun..
On Thu, Jul 19, 2012 at 4:52 AM, Sagara Gunathunga sag...@wso2.com wrote:
On Thu,
Fixed db scripts to match the table name used in the code - which has been
changed recently.
Please take svn up in identity/org.wso2.carbon.identity.core.
Thanks,
Hasini.
On Thu, Jul 19, 2012 at 4:45 PM, Ajith Vitharana aji...@wso2.com wrote:
Hi All,
I have mounted two registry instance and
siddhi has been removed from orbit it seems and not in nexus ?!
[INFO]
[ERROR] Failed to execute goal on project org.wso2.carbon.cep.siddhi: Could
not resolve dependencies for project
Hi Dushan,
I have created following Axis2 JIRA[1] to track this issue. Please comment
about your ESB use cases there.
[1] - https://issues.apache.org/jira/browse/AXIS2-5374
Thanks !
On Thu, Jul 19, 2012 at 3:27 PM, Dushan Abeyruwan dus...@wso2.com wrote:
Hi Sagara,
Yes, Originally I had
Hi,
Tried to parse the following xml chunk.
%
var x= metadata xmlns=http://www.wso2.org/governance/metadata;
application
keytest1/key
descriptiontest1/description
nametest1/name
/application
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2:34:23.650s
[INFO] Finished at: Thu Jul 19 20:53:50 IST 2012
[INFO] Final Memory: 1112M/1927M
[INFO]
On Thu, Jul 19, 2012 at 5:50 PM, Damitha Kumarage dami...@wso2.com wrote:
If this issue is real, then it is a blocking issue for our PHP Cartridge
release.
I have created a blocker for this at [1].
[1] https://wso2.org/jira/browse/CARBON-13662
Thanks.
Thanks,
Damitha
On Thu, Jul 19,
I think your trunk is not up-to-date please build the
dependencies/commons/siddhi
and dependencies/orbit/siddhi
Note as dependencies/commons/siddhi is an svn external and since I have
done an svn move to it,
doing svn up will not fully update the code and hence you might need to
delete the siddhi
If you want to do a namespace aware query, then use [1], else use [2]. You
should use proper E4X queries[3].
/Ruchira
[1]
var ns = http://www.wso2.org/governance/metadata;;
print(x.*::application.*::key.text());
[2]
print(x.ns::application.ns::key.text());
[3]
On Thu, Jul 19, 2012 at 9:47 PM, Suhothayan Sriskandarajah s...@wso2.comwrote:
I think your trunk is not up-to-date please build the
dependencies/commons/siddhi
and dependencies/orbit/siddhi
Note as dependencies/commons/siddhi is an svn external and since I have
done an svn move to it,
Hi,
Better we added those in to jaggery API Documentation (XML Basic) Rather
than just put link for E4X.
Thnaks
On Thu, Jul 19, 2012 at 10:02 PM, Ruchira Wageesha ruch...@wso2.com wrote:
If you want to do a namespace aware query, then use [1], else use [2]. You
should use proper E4X
Folks,
Should replicated caching be enabled with registry mounting? Suppose
/_system/governance space of an ESB instance is mounted (jdbc or ws) to the
same collection of a central G-reg. In that case, should we enable
replicated caching in both ESB and G-reg instances?
Please confirm.
Thanks!
On Thu, Jul 19, 2012 at 11:48 PM, Charitha Kankanamge chari...@wso2.comwrote:
Folks,
Should replicated caching be enabled with registry mounting? Suppose
/_system/governance space of an ESB instance is mounted (jdbc or ws) to the
same collection of a central G-reg. In that case, should we
I thought, he won't be able to wait till we update the doc :P
On Thu, Jul 19, 2012 at 11:31 PM, Madhuka Udantha madh...@wso2.com wrote:
Hi,
Better we added those in to jaggery API Documentation (XML Basic) Rather
than just put link for E4X.
+1 go ahead
Thnaks
On Thu, Jul 19, 2012 at
Hi Devs,
AFAIK, we can register a new host object by modifying the
modules/apistore/module.xml file. but do we have a way to do this via OSGi
services?
Thanks,
Sameera.
--
Sameera Jayasoma
Senior Technical Lead
WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog:
Hi Senaka,
It is better if we can proceed with $subject (i.e where it is jdbc,atom or
ws). We currently only specifying this for ws mounting.
This will add more consistency in mounting configuration and also will be
useful to fix some broken areas of mounting feature.
(And we need to have a schema
Also is it possible to use enableCachetrue/enableCache in ws-api ?
remoteInstance url=https://localhost:9443/registry;
idgovreg/id
usernameadmin/username
passwordadmin/password
typews/type
enableCachetrue/enableCache
/remoteInstance
On Thu, Jul 19,
---
Carbon Snapshot Platform #474 failed.
---
This build occurred because it is a dependant of
WSO2CARBON-CARBONCOREKERNELBUILD-394.
5/2117 tests failed, 2
Hi,
I have configured AS cluster with the LB (with latest trunk packs).
The logs from LB;
[2012-07-20 06:07:06,485] INFO - RpcMembershipRequestHandler Received JOIN
message from 127.0.0.1:4100(wso2.as.domain)
[2012-07-20 06:07:06,486] INFO - MembershipManager Application member
Is this a regression? Did we not test clustering in this cycle? I remember
like we did...
On Fri, Jul 20, 2012 at 6:22 AM, Thilini Ishaka thil...@wso2.com wrote:
Hi,
I have configured AS cluster with the LB (with latest trunk packs).
The logs from LB;
[2012-07-20 06:07:06,485] INFO -
We have not fronted any servers by WSO2 LB yet.
On Friday, July 20, 2012, Samisa Abeysinghe wrote:
Is this a regression? Did we not test clustering in this cycle? I remember
like we did...
On Fri, Jul 20, 2012 at 6:22 AM, Thilini Ishaka
thil...@wso2.comjavascript:_e({}, 'cvml',
If this is an implementation level issue, its a blocker for Appfactory 1.0
M3 release.
--
Thilini
On Fri, Jul 20, 2012 at 6:58 AM, Charitha Kankanamge chari...@wso2.comwrote:
We have not fronted any servers by WSO2 LB yet.
On Friday, July 20, 2012, Samisa Abeysinghe wrote:
Is this a
I remember seeing a mail where Azeez suggested some fix regarding the
offset (I dont remember what was it) and he asked to double check whether
the offset gets added twice. Here it seems the offset is added twice. Can
this be a result of that fix? I'll try to find the mail thread.
Regards,
Found it - [Dev] portOffset doesn't propagate into AxisConfig transportIns.
Is this the reason?
On Fri, Jul 20, 2012 at 7:22 AM, Amila Maha Arachchi ami...@wso2.comwrote:
I remember seeing a mail where Azeez suggested some fix regarding the
offset (I dont remember what was it) and he asked to
On Fri, Jul 20, 2012 at 6:58 AM, Charitha Kankanamge chari...@wso2.comwrote:
We have not fronted any servers by WSO2 LB yet.
Have we tested clustering? Did we test AS/ESB cluster?
On Friday, July 20, 2012, Samisa Abeysinghe wrote:
Is this a regression? Did we not test clustering in this
We have tested AS cluster with multiple nodes specifically to test the
followings and reported many bugs.
- deployment synchronization - both registry based and svn
- session replication of stateful services
We are yet to do;
- web app cluster
- ESB cluster
- product cluster fronted by WSO2 LB
-
Hi,
I'm looking into this. The fix was added to tackle the multicast scheme.
I'll debug and see, what happens in wka scenario.
I think all these comes since we check port offset at a local level and
changing it. We should have made the change at a global level.
On Fri, Jul 20, 2012 at 7:26 AM,
hi,
Better we added those in to jaggery API Documentation (XML Basic) Rather
than just put link for E4X.
+1 go ahead
I will added those basic XML operations in to jaggery API documentation/xml
On Fri, Jul 20, 2012 at 12:17 AM, Ruchira Wageesha ruch...@wso2.com wrote:
I thought, he won't be
Thanks Subash, this is something we have not documented anywhere. We should
update all docs, blogs with this information.
On Friday, July 20, 2012, Subash Chaturanga wrote:
On Thu, Jul 19, 2012 at 11:48 PM, Charitha Kankanamge
chari...@wso2.comjavascript:_e({}, 'cvml', 'chari...@wso2.com');
Hi,
I didn't see valid requirement of setting localMemberBindPort in axis2.xml.
This configurations
looks fine. AFAIK sanjaya setup stratos deployment with latest trunk packs
with load balancer
fronted. Also i have tested recently after alpha release of load balancer
2.0.0. can you please
attach
Hi Sanjeewa,
This issue is introduced by https://wso2.org/jira/browse/CARBON-13613 fix I
suspect.
On Fri, Jul 20, 2012 at 10:22 AM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi,
I didn't see valid requirement of setting localMemberBindPort in
axis2.xml.
Yes, unsetting localMemberBindPort
Subash,
Can I know why this is needed? This was not required earlier so I'd like to
understand why it's needed now?
On Fri, Jul 20, 2012 at 9:49 AM, Charitha Kankanamge chari...@wso2.comwrote:
Thanks Subash, this is something we have not documented anywhere. We
should update all docs, blogs
Hi Thilini,
I've reverted the patch for now. Please check now whether the error still
persist.
I've grepped whole carbon core to see whether it's looking at that
AvoidInitiation parameter, but seems not.
I'll dig further deep and see.
Sorry for the inconvenience caused.
On Fri, Jul 20, 2012 at
On Fri, Jul 20, 2012 at 10:38 AM, Nirmal Fernando nir...@wso2.com wrote:
Hi Thilini,
I've reverted the patch for now. Please check now whether the error still
persist.
I've grepped whole carbon core to see whether it's looking at that
AvoidInitiation parameter, but seems not.
I'll dig
Thanks. +1 for adding these into documentation.
On Fri, Jul 20, 2012 at 9:37 AM, Madhuka Udantha madh...@wso2.com wrote:
hi,
Better we added those in to jaggery API Documentation (XML Basic) Rather
than just put link for E4X.
+1 go ahead
I will added those basic XML operations in to
The dist structure is, LB/module/distribution/product/. This should now be
LB/module/distribution. I have changed this in the trunk. The change needs
to happen in the branch too.
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation;
On Fri, Jul 20, 2012 at 10:56 AM, Afkham Azeez az...@wso2.com wrote:
The dist structure is, LB/module/distribution/product/. This should now be
LB/module/distribution. I have changed this in the trunk. The change needs
to happen in the branch too.
Noted.
--
*Afkham Azeez*
Director of
Folks,
This is a major blocker for me. As you know, the mgt node worker node
separation is a major requirement for this release. That will take care of
most depsync issues etc. To be able to do that, I need a working LB build.
I cannot get that since my build has been failing from time to time at
It builds fine for me. Let me dig into it.
On Fri, Jul 20, 2012 at 10:59 AM, Afkham Azeez az...@wso2.com wrote:
Folks,
This is a major blocker for me. As you know, the mgt node worker node
separation is a major requirement for this release. That will take care of
most depsync issues etc. To
commit this to branch
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
commit this to branch
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
On Fri, Jul 20, 2012 at 11:04 AM, Pradeep Fernando prad...@wso2.com wrote:
commit this to branch
ok.
--Pradeep
--
Thanks regards,
Nirmal
Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
commit this to branch
--Pradeep
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Well the way I built the dist was a bit messed up. I started with a clean
Maven repo. Then there were many build issues. Then I switched back to my
old Maven repo, and built the branch orbit, and continued with an online
build of kernel platform. Finally I got stuck at this place.
On Fri, Jul
On Fri, Jul 20, 2012 at 11:14 AM, Afkham Azeez az...@wso2.com wrote:
Well the way I built the dist was a bit messed up. I started with a clean
Maven repo. Then there were many build issues. Then I switched back to my
old Maven repo, and built the branch orbit, and continued with an online
66 matches
Mail list logo
