Hi Imesh, I tested with the base 4.0.0 RC3 code (no patches). I saw the exact same problem when the CompleteTopologyEvent event came. I think this issue exists in the release branch. I'll try to cherry pick the changes related to port mapping from master branch and see if this fix the issue I'm seeing.
-Jeffrey On 5/28/14 10:25 PM, "Imesh Gunaratne (JIRA)" <[email protected]> wrote: > > [ >https://issues.apache.org/jira/browse/STRATOS-657?page=com.atlassian.jira. >plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012083#co >mment-14012083 ] > >Imesh Gunaratne commented on STRATOS-657: >----------------------------------------- > >Hi Jeffrey, > >I'm sorry for the inconvenience caused. This modification [1] was done in >master branch and should not affect 4.0.0-incubating-rc3 tag. As I see in >the comments 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. If you do not have any >persisted data, may be all Stratos components were not built properly >(may be some are using previous version of the messaging component). > >Commits of this modification: >e4b15b6f52253b804c5e716fbcf1c1db47111dc2 - >3d3fc9d31199e4b108ec034ca4ab809f998c7e3f > >[1] https://issues.apache.org/jira/browse/STRATOS-631 > >Thanks >Imesh > >> Topology update events failed to be de-serialized due to incorrect port >>mapping format >> >>------------------------------------------------------------------------- >>------------- >> >> Key: STRATOS-657 >> URL: https://issues.apache.org/jira/browse/STRATOS-657 >> Project: Stratos >> Issue Type: Bug >> Components: Cloud Controller, Stratos Manager >> Affects Versions: 4.0.0, 4.0.0 RC1 >> Environment: Apache Stratos 4.0.0 RC3, openstack havana >> Reporter: Jeffrey Nguyen >> >> We have a topology listener component that listens to topology update >>events in activemq. We're seeing exceptions as one shown below when >>events such as MemberActivatedEvent or CompleteTopologyEvent >> In the exception stacktrace below, >>"portMap":{"http":{"protocol":"http","value":22,"proxy":8280}},"memberIp" >>:"1.2.3.4"} should be something like >>"portMap":{"80":{"protocol":"http","value":22,"proxy":8280}},"memberIp":" >>1.2.3.4"} >> 2014-05-28 15:43:45 | DEBUG | TopologyEventsListener:63: Received >>topology message of type: >>org.apache.stratos.messaging.event.topology.MemberActivatedEvent,payload= >>{"serviceName":"cisco-sample-vm","clusterId":"sample-vm.sample-v","networ >>kPartitionId":"N1","partitionId":"RegionOne","memberId":"sample-vm.sample >>-v1e5e272d-1bbe-4a7b-9c4e-92890363abea","portMap":{"http":{"protocol":"ht >>tp","value":22,"proxy":8280}},"memberIp":"1.2.3.4"} >> Exception in thread "Thread-0" com.google.gson.JsonSyntaxException: >>java.lang.NumberFormatException: For input string: "http" >> at >>com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:241) >> at >>com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:231) >> at >>com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdap >>terRuntimeTypeWrapper.java:40) >> at >>com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeA >>dapterFactory.java:186) >> at >>com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeA >>dapterFactory.java:145) >> at >>com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(Reflect >>iveTypeAdapterFactory.java:93) >> at >>com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(R >>eflectiveTypeAdapterFactory.java:172) >> at com.google.gson.Gson.fromJson(Gson.java:803) >> at com.google.gson.Gson.fromJson(Gson.java:768) >> at com.google.gson.Gson.fromJson(Gson.java:717) >> at com.google.gson.Gson.fromJson(Gson.java:689) >> at >>org.apache.stratos.messaging.message.JsonMessage.<init>(JsonMessage.java: >>38) >> at org.apache.stratos.messaging.util.Util.jsonToObject(Util.java:105) >> at >>com.cisco.apache.stratos.topologylistener.TopologyEventsListener.run(Topo >>logyEventsListener.java:100) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: java.lang.NumberFormatException: For input string: "http" >> at >>sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1241) >> at java.lang.Double.parseDouble(Double.java:540) >> at com.google.gson.stream.JsonReader.nextInt(JsonReader.java:1178) >> at >>com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:239) >> ... 14 more > > > >-- >This message was sent by Atlassian JIRA >(v6.2#6252)
