Hi Jeffrey, This modification [1] was done in master branch and should not affect 4.0.0-incubating-rc3 tag. As I see in the issue you have created you may have cherry picked commits from the master branch to your local branch (may be applied on top of 4.0.0-incubating-rc3 tag).
The problem here is that with this modification the data structure of the topology has changed. If we were to upgrade an existing system (runs on 4.0.0-incubating-rc3) which has some topology information persisted in registry, we will need to do a data migration. [1] https://issues.apache.org/jira/browse/STRATOS-631 Thanks On Thu, May 29, 2014 at 10:11 AM, Imesh Gunaratne <im...@apache.org> wrote: > Hi Jeffery, > > Thanks for reporting this problem. Let me check this in detail and get > back to you soon. > > Thanks > > > On Thu, May 29, 2014 at 5:58 AM, Jeffrey Nguyen (jeffrngu) < > jeffr...@cisco.com> wrote: > >> Hi Devs, >> >> I just filed https://issues.apache.org/jira/browse/STRATOS-657. We're >> experiencing this issue with the code built from 4.0.0 RC3 tag. Please >> see the JIRA description for further details. Basically, it looks like we >> might have some issue with the way port map info is presented in the >> topology update events such as MemberActivatedEvent or >> CompleteTopologyEvent. This causes our topology listener to fail to >> process these event with a java.lang.NumberFormatException. From the >> exception, it seems like the key named "http" should be a string >> representation of an integer instead, e.g. "80". >> >> *Imesh,* >> >> I don't mean to finger pointing. I'm copying you simply >> because I thought you'd have intimate knowledge in this area since you did >> some enhancement on this last time (please see commit reference below) >> >> Could you or someone please verify if this is a valid issue? If so, >> could you give some pointers on how to fix this? >> >> >> *Commit:* e4b15b6f52253b804c5e716fbcf1c1db47111dc2 [e4b15b6] >> *Parents:* a8e3181b1b >> *Author:* Imesh Gunaratne <im...@wso2.com> >> *Date:* April 30, 2014 10:08:21 PM PDT >> >> Updated load balancer port mapping logic to find outgoing port according >> to the incoming port rather than looking at the transport >> >> Thanks, >> -Jeffrey >> > > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PPMC Member, Apache Stratos > -- Imesh Gunaratne Technical Lead, WSO2 Committer & PPMC Member, Apache Stratos
