Forum Discussion

Jamboh's avatar
Jamboh
New Contributor
14 years ago

LoadUI Agents constantly dropping packets

I've seen another thread with this issue but not a resolution for it!

I have five VMs. One is the 'server' and four agent machines. Two are UK based and two are in Hong Kong. The agents instantly connect to the server machine and also accept the distributed test case with no problems but the test runs never work.

As soon as I try to run a test case and I get the following:

17:56:10,462 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854757801 dropped!
17:56:14,165 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854757807 dropped!
17:56:19,181 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854775595 dropped!
17:56:24,197 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854775126 dropped!
17:56:29,212 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854772638 dropped!
17:56:34,228 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854772343 dropped!
17:56:39,244 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854769479 dropped!
17:56:44,260 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854769106 dropped!
17:56:49,275 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854769094 dropped!
ad infinitum......................

Pings and trace routes work between the machines with no problems just the agents do not!

Any ideas?

3 Replies

  • Jamboh's avatar
    Jamboh
    New Contributor
    14 years ago
    Does anyone have a solution for this issue?

    It seems to me the agents simply do not work!
  • benspop3's avatar
    benspop3
    14 years ago
    I agree. SoapUI seems to be very solid and LoadUI in local mode works pretty reliably as well. The agents, however, do seem to be very flaky--at least in current release. We have 6 test machines, each running an agent. The agents mysteriously come and go as they please. They often seem to be fine until the testing begins, and then they don't run any tests (I know this because they don't report any results to the Table Log. We even see them behave differently depending on who is logged into the test PCs.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    benspop3 wrote:
    I agree. SoapUI seems to be very solid and LoadUI in local mode works pretty reliably as well. The agents, however, do seem to be very flaky--at least in current release. We have 6 test machines, each running an agent. The agents mysteriously come and go as they please. They often seem to be fine until the testing begins, and then they don't run any tests (I know this because they don't report any results to the Table Log. We even see them behave differently depending on who is logged into the test PCs.

    Hi!

    I honestly think that your description is quite spot on. In loadUI 1.0 and 1.5 agent distribution used the non-standard CometD protocol, which has proven to be unstable and not intended for our usecase. In loadUI 2.0 however, we have reimplemented the agent communication, replacing CometD with a ISO-standard SSL/TCP communication used by thousands of applications.

    Our tests shows that this change has resolved the flakyness that could be seen in loadUI 1.5 and older.

    LoadUI 2.0 has been in the works since May and the first beta will be out in 3 weeks.

    Regards

    Henrik
    SmartBear Software