Hi Nirmal, All,
I encountered this error for ESB ports(8280, 8243) in AM. Where two AM
nodes are configured in a cluster. Both AM starts with same ports. Have I
missed something to configure?. Please check.
error: Here AM runs with offset of *3*,
TID: [0] [ELB] [2013-05-22 07:28:26,977] ERROR
I've checked the multicast scenario, with a latest appserver packs. It
seems to work properly with a portOffset.
But however when I checked it earlier, it didn't work in trunk, hence the
commit.
And it seems like some commit has fixed the issue and now I could see
portOffset is getting propagated
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,
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
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
15 matches
Mail list logo
