AnsweredAssumed Answered

Odd Test execution error

Question asked by sdetweil2 on Mar 28, 2016
Latest reply on Apr 5, 2016 by sdetweil2

We migrated to a production database past week, from our Derby deployment, mostly cause we ran out of disk space due to a mis configued testcase in terms of data reporting.

 

we rebooted the system and restarted the runtime components.

 

Anyhow,  since then,   one testcase doesn't work anymore

 

| Message: Error executing single test: Unexpected reference to target tcp://152.144.6.112:2011/8B42A7F2F4FE11E5B836005056AA0A0C lost making call hasTestErrorFired known soft targets: [brokerServices, PERF-Coordinator] dying targets: [metrics8B42A7F2F4FE11E5B836005056AA0A0C, metrics43BBCDA0F4FE11E5B836005056AA0A0C, metrics1FF7C527F4FE11E5B836005056AA0A0C, metrics8B408511F4FE11E5B836005056AA0A0C] hard targets: [metrics8B42A7F2F4FE11E5B836005056AA0A0C, metrics43BBCDA0F4FE11E5B836005056AA0A0C, metrics1FF7C527F4FE11E5B836005056AA0A0C, metrics8B408511F4FE11E5B836005056AA0A0C, brokerServices, PERF-Coordinator] colocated: [metrics8B42A7F2F4FE11E5B836005056AA0A0C, metrics43BBCDA0F4FE11E5B836005056AA0A0C, metrics1FF7C527F4FE11E5B836005056AA0A0C, metrics8B408511F4FE11E5B836005056AA0A0C, brokerServices, PERF-Coordinator]

 

the target address  tcp://152.144.6.112:2011  IS the same machine..

 

this testcase has run successfully for months.

 

where can I look for the cause of this problem?

Outcomes