providing the highest level of communication services

100%CPU

Hi,

more than a question, I am looking for an IDEA?##"

my client starts hanging at 100% cpu, and also the events stop get passing thru; this usually happens after established or cleared event. I see that the server sends the event, but client remains silent...

I am not sure, how or where to look for error; I have a hunch that he somehow remains in the run method... but I dunno how to check it...

server is working fine, after I kill and restart the clients - its ok, until againt it stops receiving events and starts eating my CPU ?

do you have any ideas, where could I look for error, or what could be the cause ?

with br
Kristjan

Hmmmmmm

Interesting...

This problem is really hard to diagnose. It only happens periodically and yes always on the client/comms. I haven't had time to find exactly where it is. It's hard to make fail regularly.

I'm working remotely for a month and this week is a little busy. I'll see if I can set up a test environment with a Siemens dealer.

Chris

very interesting... yes but

very interesting... yes

but the funny thing is, the cpu gets up to a 100, the events stop coming thru, but the call command still goes thru... (its like client->server works, but server -> client: stopped)... so could be a network issue or some socket issue, or a lock... hm...

hope u can set up a test enviroment, maybe this is specific to siemens....
I can give u access to my siemens, if it helps. I have it available till thursday, then I am also without of equipment...:(

with br
Kristjan

I think a test, regardless of

I think a test, regardless of having equipment available needs to be set up. Just create events randomly and send them to the client and see what happens.

I think it's with the network comms, but not 100% yet.

I'll be able to take a better looks once a few things settle down with work here in Australia.

Keep you posted.

maybe just a comment on this

maybe just a comment on this starting side, i noticed that in your CSTATestTool you start thread with
csta.run() ; if I try to start it like this it just blocks loading of everything else... so I changed the starting code to cstaThread.start(). See code below...


csta = new CSTAMulti(this, _props);
csta.RegisterParentApplication(this);
cstaThread = new Thread(csta, "CSTA Thread");
csta.run(); //your way of starting, but then it blocks

//I changed the threadStarting code from csta.run() to:
cstaThread.start()

- could this difference be connected with the loss of events and then hanging - maybe some wrong ref get passed back up?

just thinking out loud...

hope things settle down for you! and to hear from you soon, cause this error is really critical to me... it hangs the whole APP server :(

br
Kristjan

regarding upper post,

regarding upper post, csta.startThread...

my client works, without implementing the run Method, as specified in your SimpleExample...

3. SimpleExample run()

public void run() {
..... code

is this step necesary? or not - i dont have it know...
......

regarding testing....

Do you have a cstaserver build that keeps pushing events to client without the HiPath 3000... like a demo testin server...

tnx
kristjan