Uploaded image for project: 'AdMax'
  1. AdMax
  2. ADMAX-2762

Maven: Getting exceptions in event-listener logs while running V2 playback script

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: BM Maven
    • Fix Version/s: BM Maven
    • Component/s: Event Listener
    • Labels:
      None
    • Environment:

      /usr/local/tsa/Bid_Manager_-_Mavenized/38/tsa-build-bidmgr-2011-08-01-p38-r30134 on staging-xml1

      Description

      While running V2playback we are getting exceptions in event-listener.log

      1)Start event-listener-mgr

      ./event-listener-mgr.sh start

      2) tail -150f /var/local/tsa/log/event-listener.log

      3)Run ./v2pixel_playback.sh -d 3 -a 17 2>&1| tee /tmp/pixelplayback4.log

      .

      .

      .

      2011-07-25 03:27:40.988 (2) [P1T1]: commitToWaypointLog completed: 0.101s

      2011-07-25 03:27:40.989 (0) [P1T1]: Processed 3 Log Lines / 3 Hits Imported / Total Time: 12.197s (885 lines/hour, 885 hits/hour) [ 2011-06-02-1000-35.tsv ]

      2011-07-25 03:27:41.080 (3) [P1T1]: queueDayCompleteMessage: date[ 5/16/11 12:00 AM ], site: 35

      2011-07-25 03:27:41.081 (2) [P1T1]: Moved Pixel Log File: [2011-06-02-1000-35.tsv] To: [/usr/local/share/tsa/logs/spike-v2/done/35/2011-06-02-1000-35.tsv]

      2011-07-25 03:27:46.992 (3) [main]: ------------Pixel Log Playback done

      2011-07-25 03:27:47.044 (3) [main]: Connecting using URL: failover:(tcp://event-msg-broker-01:61616,tcp://event-msg-broker-02:61616)?randomize=false&jms.prefetchPolicy.all=1 to topic tsa.data.events

      Jul 25, 2011 3:27:50 AM org.apache.activemq.transport.failover.FailoverTransport doReconnect

      INFO: Successfully connected to tcp://event-msg-broker-01:61616

      2011-07-25 03:27:52.968 (3) [main]: PlaybackStatusMessageQueue.Dispatcher::sendDayCompleteMessage PixelPlaybackDone:[ AccountIDs: 17 SiteIDs: 35 Date: Mon May 16 00:00:00 PDT 2011 ] : 5.931s

      2011-07-25 03:27:52.968 (3) [main]: PlaybackStatus.Dispatcher::sendDayCompleteMessage complete: 5.932s

      4) Check the logs

      2011-07-25 03:28:31.255 (1) [main]: Exception [Error processing message]:com.thoughtworks.xstream.mapper.CannotResolveClassException: setDataAvailability : setDataAvailability

      at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68)

      at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)

      at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71)

      at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)

      at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)

      at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)

      at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:86)

      at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)

      Check the detailed log as attached.

        Attachments

          Activity

            People

            • Assignee:
              jason.stedman Jason Stedman (Inactive)
              Reporter:
              atul.sanagar Atul Sanagar (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: