Hi all,
When I ran the sample 50 of wso2 esb [1] , I ended up with the following
errors. Following is the error which I got on the axis2Server console.
13/12/18 14:48:04 ERROR engine.AxisEngine: The endpoint reference (EPR) for
the Operation not found is /services/SimpleStockQuoteService and
Hi Dinusha,
Synapse version 2.1.2.wso2v2 builds fine with tests in a clean repo. This
is the version we released in chunk-04 with ESB 4.8.0 release.
It looks like 2.1.2.wso2v3 has branched incorrectly. v3 was not created
from the released revision of the v2.
Please take necessary actions to make
Hi,
Please look in to the $Subject
Documentation link as follows.
[1]
http://docs.wso2.org/display/ESB480/Sample+13%3A+Dual+Channel+Invocation+through+Synapse
file location - ESB_HOME/repository/samples/synapse_sample_*.xml
Thanks
Pubudu.
--
*Pubudu Dissanayake*
Software Engineer
WSO2 Inc.;
Hi Isuru,
On 18 December 2013 15:10, Isuru Udana isu...@wso2.com wrote:
Hi Dinusha,
Synapse version 2.1.2.wso2v2 builds fine with tests in a clean repo. This
is the version we released in chunk-04 with ESB 4.8.0 release.
It looks like 2.1.2.wso2v3 has branched incorrectly. v3 was not
Hi all,
On 18 December 2013 15:21, Lakmali Baminiwatta lakm...@wso2.com wrote:
Hi Isuru,
On 18 December 2013 15:10, Isuru Udana isu...@wso2.com wrote:
Hi Dinusha,
Synapse version 2.1.2.wso2v2 builds fine with tests in a clean repo. This
is the version we released in chunk-04 with ESB
Please report a blocker issue on OT Jira ESB project for this.
Thanks,
Samisa...
Samisa Abeysinghe
Vice President Training
WSO2 Inc.
http://wso2.com
On Wed, Dec 18, 2013 at 3:16 PM, Pubudud Dissanayake pubu...@wso2.comwrote:
Hi,
Please look in to the $Subject
Documentation link as
Looks like this is missing in previous versions as well.
On Wed, Dec 18, 2013 at 4:36 PM, Samisa Abeysinghe sam...@wso2.com wrote:
Please report a blocker issue on OT Jira ESB project for this.
Thanks,
Samisa...
Samisa Abeysinghe
Vice President Training
WSO2 Inc.
http://wso2.com
This was already reported for 4.7.0.
https://wso2.org/jira/browse/DOCUMENTATION-246
However document was not updated for 4.8.0. I updated the doc.
Best Regards,
Malaka
On Wed, Dec 18, 2013 at 4:42 PM, Malaka Silva mal...@wso2.com wrote:
Looks like this is missing in previous versions as
Thank you for your help, much appreciated
On Wed, Dec 18, 2013 at 4:51 PM, Malaka Silva mal...@wso2.com wrote:
This was already reported for 4.7.0.
https://wso2.org/jira/browse/DOCUMENTATION-246
However document was not updated for 4.8.0. I updated the doc.
Best Regards,
Malaka
On
Hi Kernel team,
Can you please commit the patch given in [1].
[1] https://wso2.org/jira/browse/IDENTITY-1974
Thanks,
On Sun, Dec 15, 2013 at 7:31 PM, Manoj Kumara ma...@wso2.com wrote:
Hi,
Committed to patch0004 with 193396.
Thanks,
Manoj
Best Regards..
Manoj Kumara
Software
Hi All
On some occasions if we uncheck the SSO options and re tick then and
check the floor the below error is thrown
[2013-12-18 19:07:35,684] WARN
{org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor}
- Signature validation for Authentication Request failed.
the other error thrown when accessing the sso url after resetting the options
[2013-12-18 19:27:39,679] WARN
{org.wso2.carbon.identity.sso.saml.processors.SPInitSSOAuthnRequestProcessor}
- Signature validation for Authentication Request failed.
[2013-12-18 19:27:39,681] ERROR
On Wed, Dec 18, 2013 at 6:55 PM, Darshana Gunawardana darsh...@wso2.comwrote:
Hi Kernel team,
Can you please commit the patch given in [1].
[1] https://wso2.org/jira/browse/IDENTITY-1974
committed in r193685. Thanks Kishanthan..
Thanks,
On Sun, Dec 15, 2013 at 7:31 PM, Manoj Kumara
Following issues were identified in RC1 pack related to tenant and user
stores.
https://wso2.org/jira/browse/IDENTITY-1983
https://wso2.org/jira/browse/IDENTITY-1982
https://wso2.org/jira/browse/IDENTITY-1979
https://wso2.org/jira/browse/IDENTITY-1977
On Wed, Dec 18, 2013 at 7:31 PM,
Hi Aruna,
Sample 50 synapse configuration seems to be out dated. in order to get the
sample worked, you need to set the SOAPAction transport header before
sending the soap message to backend since the rest message does not send
the SOAPAction header. If you did not set the SOAPAction, axis2 server
Hi Diego,
First of all, I'm sorry for the delay in replying.
I went through you configs.
Do not use host names in your configurations. Please use IP addresses for
now. There is a known issue with Hazelcast. Here is a related JIRA [1].
Use IPs in parameter name=localMemberHost / and members
Hi Nuwan,
Thank you very much for the reply.
However I've acquired a fresh copy Enterprise Service Bus 4.8.0 and ran the
sample 50 again. This time it worked
as it should. I think the errors caused due to the configuration changes
made for the earlier samples.
Regards,
On Wed, Dec 18, 2013
Hi,
Some quick answers.
On Wed, Dec 11, 2013 at 5:09 PM, stevegyc steve...@163.com wrote:
Hi:
Is there a detailed tutorials about how to set up Data Services Server
cluster.
I followed the guide
http://docs.wso2.org/pages/viewpage.action?pageId=29918203, but it is not
Hi,
Can you share configs? loadbalancer.conf and axis2.xml of each instances.
I hope you followed exact steps in the wiki docs.
Each DSS instance should define ELB IP and group_mgt_port in its axis2.xml
members section.
As you can see from last log, when you run in clustered mode, it waits for
I think we should document this if it's not already there. That is, if our
samples cannot be run continuously, we should ask to reset any
configuration changes made before. WDYT?
On Thu, Dec 19, 2013 at 9:35 AM, Aruna Karunarathna ar...@wso2.com wrote:
Hi Nuwan,
Thank you very much for the
Hi,
Use IPs in axis2.xml clustering section properly. For clustering to work,
each node should be in the same network.
So, make sure you add node's IP to localMemberHost and remote members' IPs
to members section.
I hope this helps!
Thanks!
On Mon, Dec 16, 2013 at 1:32 AM, stevegyc
I have a simple application in which I send an array of elements from my
index page to another jaggery script. Now I want to print those elements
from the jaggary script
My Index.jag contains
---
$.get(addOrder.jag, {arr:itmArr,action: add},
function(data){
Hi
Issue occurred when i try to execute the $Subject.
Stack trace as follows
[2013-12-19 10:18:30,841] DEBUG - DynamicLoadbalanceEndpoint Couldn't find
the Cookie header to find the session
[2013-12-19 10:18:30,841] ERROR - Axis2LoadBalanceMembershipHandler A
LoadBalanceEventHandler has not been
Did you enable clustering ?
On Thu, Dec 19, 2013 at 10:27 AM, Pubudud Dissanayake pubu...@wso2.comwrote:
Hi
Issue occurred when i try to execute the $Subject.
Stack trace as follows
[2013-12-19 10:18:30,841] DEBUG - DynamicLoadbalanceEndpoint Couldn't find
the Cookie header to find the
And as an addition, In Sample 51: MTOM and SwA optimizations and
request/response correlation [1], In the last paragraph it says,
By sending this message through TCPMon you would be able to see the actual
message... ,
To use TCPMon I had to change the port in
And you need to have localMemberDomain as 'apache.axis2.application.domain'.
I'm afraid, this page is not helpful for a user at all. Please review.
On Thu, Dec 19, 2013 at 10:32 AM, Jeewantha Dharmaparakrama
jeewan...@wso2.com wrote:
Did you enable clustering ?
On Thu, Dec 19, 2013 at
Yes I did
furthermore XML properties as follows
ESB Clustering ( axis2.xml )
clustering
class=org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent
enable=true
parameter name=AvoidInitiationtrue/parameter
parameter name=membershipSchemewka/parameter
Hi Nirmal,
I also encountered the above error and was unable to find
localMemberDomain you have mentioned, in any of the following documents.
ESB_HOME/repository/conf/axis2/axis2.xml
ESB_HOME/samples/axis2Server/repository/conf/axis2.xml
Regards,
On Thu, Dec 19, 2013 at 10:48 AM, Pubudud
Please change the value of the 'domain' parameter to what I sent earlier.
On Thu, Dec 19, 2013 at 10:48 AM, Pubudud Dissanayake pubu...@wso2.comwrote:
Yes I did
furthermore XML properties as follows
ESB Clustering ( axis2.xml )
clustering
Hi Pubudu,
This issue has been previously raised in the dev mailing list under the
following heading.
[Dev] Running ESB sample 57
You can find the reason for this issue and the workaround.
@Nirmal: If you see something is missing in the document, please correct it
by yourself since you know
Hi Aruna,
You don't need to change the java code to monitor the request and response
through the TCPMon. You just need to point the endpoint of the address uri
to the TCPMon listening port (which you can define from TCPMon itself) and
make the forwarding (sending) port of the TCPMon to 9000. Then
On Thu, Dec 19, 2013 at 10:54 AM, Aruna Karunarathna ar...@wso2.com wrote:
Hi Nirmal,
I also encountered the above error and was unable to find
localMemberDomain you have mentioned, in any of the following documents.
Aruna, sorry, I wrote that off the top of my head. Please set the domain
Hi Chanaka,
On Thu, Dec 19, 2013 at 10:55 AM, Chanaka Fernando chana...@wso2.comwrote:
Hi Pubudu,
This issue has been previously raised in the dev mailing list under the
following heading.
[Dev] Running ESB sample 57
You can find the reason for this issue and the workaround.
Hi Nirmal,
If there is that kind of issue, please be specific and point out the things
you see incorrect or missing. That will help us to fix the issue with the
documentation. :)
On Thu, Dec 19, 2013 at 12:37 AM, Nirmal Fernando nir...@wso2.com wrote:
Hi Chanaka,
On Thu, Dec 19, 2013 at
Hi All,
Please find $subject @ [1].
[1] - http://ec2-107-22-190-5.compute-1.amazonaws.com/chunk-06/19-dec-2013/
Thanks and Regards,
Ruwan Yatawara
Software Engineer,
WSO2 Inc.
lean . enterprise . middleware
email : ruw...@wso2.com
mobile : +94 77 9110413
blog :
Since this is a sample and it requires some values to be there in the
axis2.xml file, can't we simply upload the sample specific axis2.xml file
and point to the clustering document for further information?
On Thu, Dec 19, 2013 at 11:16 AM, Chanaka Fernando chana...@wso2.comwrote:
Hi Nirmal,
Hi Chanaka
And I quote, unquote
Looks like this is an incompatibility issue between two clustering
mechanisms used in axis2Server and within the ESB itself. In the
axis2Server, it is using tribesClustering while ESB 4.8.0 is using
Hazlecast clustering. I have done some debugging on ESB and
Hi All,
Please find the WSO2 Identity Server - 4.6.0 RC2 pack at [1]. The new
feature in this release can be found at [2]. Find the JIRAs fixed for this
release at [3]. Known issue can be found at [4].
[1]
http://ec2-107-22-190-5.compute-1.amazonaws.com/chunk-06/19-dec-2013/wso2is-4.6.0.zip
[2]
Hi Perera:
I have changed group_mgt_port to 4100, Now it is OK!
Thank you for your help!
stevegyc
From: Isuru Perera
Date: 2013-12-19 12:15
To: stevegyc
CC: dev
Subject: Re: [Dev] [DSS]Problem about setting up DSS cluster.
Hi,
Can you share configs? loadbalancer.conf and axis2.xml
39 matches
Mail list logo
