AnsweredAssumed Answered

Error doing random data sets: Attempting to call method on local object, but object not found in colocated objects - it must have been deregistered:

Question asked by paul.yeung on May 3, 2017
Latest reply on May 8, 2017 by gadpr08

Hi All, sorry about the long title.

 

I'm currently using DevTest Workstation 9.1, and I build a webservice which will access a local MySQL database to access data from tables. I have a bunch of subprocesses which will use the "Read Rows from a JDBC Table" in order to make queries and fetch data for use. My service seems to work great in ITR and work great most of the time when deployed. But after maybe 18 or more transactions I start getting errors. I'll copy and paste a snippet below and just replace the IP address with Xs. 

 

Message:     Error doing random data sets

----------------------------------------------------------------------------

| Trapped Exception: Attempting to call method on local object, but object not found in colocated objects - it must have been deregistered: tcp://***.XX.***.XX:2200/EC1892102E6F11E786D4005056905E9D

| Trapped Message:   java.rmi.RemoteException: Attempting to call method on local object, but object not found in colocated objects - it must have been deregistered: tcp://***.XX.***.XX:2200/EC1892102E6F11E786D4005056905E9D

----------------------------------------------------------------------------

STACK TRACE

java.rmi.RemoteException: Attempting to call method on local object, but object not found in colocated objects - it must have been deregistered: tcp://***.XX.XX.XX:2200/EC1892102E6F11E786D4005056905E9D

      at com.itko.lisa.net.ClientBase.invokeMethod(ClientBase.java:269)

      at com.itko.lisa.net.ClientBase.invokeMethod(ClientBase.java:244)

      at com.itko.lisa.net.DataSetClient.getName(DataSetClient.java:62)

  

I have tried referring to this link:  Virtual Service works in ITR but fails when deployed to VSE which suggests to delete old mar files in vseDeploy and restarting the VSE. I have tried that and the error keeps coming back after a certain number of transactions (usually 18 or more). After a certain number of errors the service ends.

 

Should I raise a ticket for this?

Outcomes