Webspeed agent hangs on startup

Posted by jmls on 01-Jun-2009 07:11

I have a problem where all of my webspeed agents hang on startup. I know there's a bug, but don't quite know where. I have extended logging on both agent and broker but hasn't helped much in identifying the source of the problem.

Is there a startup parameter or option I have give to have each line excecuted logged so I can trace the program flow without having to modify the source code ?

TIA

OpenEdge Development - Forum

All Replies

Posted by Admin on 01-Jun-2009 07:30

Add 4GLTrace:4 to the agent logging options.

Posted by jmls on 01-Jun-2009 07:59

Hmm, had tried that, and double-checked to make sure. The client log file does not get updated with anything useful. The broker log file shows the following:

creating server input stream ...

[09/06/01@13:55:39.861+0100] P-001980 T-L-3065 2 UB Debug      waiting for admin rsp at L-3065

[09/06/01@13:55:41.017+0100] P-001980 T-S-0001 2 UB Debug      private listening socket connected= 4658

[09/06/01@13:55:41.017+0100] P-001980 T-S-0001 2 UB Debug      ServerSocketIPC create: portnum= 0 rcvtimeout= 3000

[09/06/01@13:55:41.017+0100] P-001980 T-S-0001 2 UB UBNET      connected to agent at 90.0.0.4:4659

[09/06/01@13:55:41.033+0100] P-001980 T-S-0001 2 UB Debug      S-0001 : reading serverIPC for server port and pid ...

[09/06/01@13:55:41.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg()

[09/06/01@13:55:41.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  mark() : markpos=0

[09/06/01@13:55:44.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg() : java.net.SocketTimeoutException: Read timed out
[09/06/01@13:55:44.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg()

[09/06/01@13:55:44.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  mark() : markpos=0

[09/06/01@13:55:47.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg() : java.net.SocketTimeoutException: Read timed out

[09/06/01@13:55:47.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg()

[09/06/01@13:55:47.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  mark() : markpos=0

[09/06/01@13:55:50.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg() : java.net.SocketTimeoutException: Read timed out

[09/06/01@13:55:50.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg()

[09/06/01@13:55:50.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  mark() : markpos=0

[09/06/01@13:55:53.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg() : java.net.SocketTimeoutException: Read timed out

[09/06/01@13:55:53.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg()

[09/06/01@13:55:53.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  mark() : markpos=0

[09/06/01@13:55:56.033+0100] P-001980 T-S-0001 2 UB S-MsgStrm  readMsg() : java.net.SocketTimeoutException: Read timed out

as you can see, every three seconds there is a issue. The client never responds and I have to terminate the process

Posted by jmls on 01-Jun-2009 08:00

Heh, is it just my browser, or have all our "self portrait" pictures gotten, urm, fatter ?

Posted by Peter Judge on 01-Jun-2009 08:06

Heh, is it just my browser, or have all our "self portrait" pictures gotten, urm, fatter ?

Well, you started out "normal" at the beginning of this thread, and then you became a more rounded individual, shall we say. Maybe we all need to get out more.

(ie I'm also seeing this)

-- peter

Posted by Admin on 01-Jun-2009 08:06

me too. (running Chrome 2).

Posted by jmls on 01-Jun-2009 08:08

crap. Think I found my problem.

The database server had died

This thread is closed