Agents Dying On Startup

[Chris Kelleher]

WS 2.1
Unixware 7.0.1
8.3B DBs

I have a startup script that ensures that the broker/agents are restarted
every morning. The agents are started with the -weblogerror switch. The
system is not working from the get-go. As soon as the broker re-starts I'm
getting the following error in the log file:

[Tue Feb 8 06:07:17 2000] === WebSpeed log files started === (5776)
[Tue Feb 8 06:07:19 2000] WTB: Received an error from an agent application.
(57
59)
[Tue Feb 8 06:07:19 2000] WTB: Port #: 3301, Pid #: 12634, Exclusive-id:
WSEU=u
nixware:3300:12634:1. (5760)
[Tue Feb 8 06:07:19 2000] ** Attempt to write to closed stream WebStream.
(1387
)
I looked up 5760 in the WorkShop Messages Function:

/*** begin WS help ***/
Message Description:
----------------------------------------------------------------------------
----

WTB: Port #: , Pid #: , Exclusive-id: . (5760)


m
/*** end WS help ***/

ACK!!! The infamous 'M'!
The knowledge base gives the same, plus:

"No solutions available for this particular error."

Of course, the application doesn't work. The error kills all the agents
off.

Suggestions?

Chad.

********************
Chad R. Thomson
Progress/Webspeed Programmer
FDM4 Development Team
Cutsey Business Systems http://www.fdm4.com
********************
Stress is when you wake up screaming
& you realize you haven't fallen asleep yet

 

[Chris Kelleher]

I have also seen this message (repeated thousands of times) in a WS 3.0
NT environment that I recently visited.

The WebSpeed 3 help sez:
**Attempt to write to closed stream (1387)

You tried to write to a stream that is closed.
M


In this environment it was not really causing any problems. How in the
world is the webstream being closed?

 

[Chris Kelleher]

This I can tell

Not for sure, but I made a library using one of the cgi-script template in
(AppBuilder/UIB and forgot to remove a RUN procedure in the MAIN area. My
intention was only to use this as a Function library that I started within
web-util.w, but since this RUN statement did a RUN output-header I got
trapped with this message.

Could it be something like that?

Anyway, good luck
Best regards,

Geir Otto

 

[Chris Kelleher]

I've seen a similar error at a previous client. It was related
to HTML Mapping WOs. I had to debug the WS provided code to find
the problem, but don't remember exactly where I ended up finding
it (the problem).

They added custom tags to tagmap.dat and called custom event
handlers (.p's) for those tags. When an agent is started
(via web-disp.p), the tagmap.dat file is read in to a TT.
All event handlers listed in this file are run persistently
at this time before the webstream is open for the Agent.
If the event handlers are not found (not in your Propath),
the WS code attempt to {&OUT} a message, but the webstream
isn't open at this point. This resulted in a flurry of
messages logged to the WS Broker Error log when a WS Agent
tried to start up.

Maybe you're experiencing the same thing.

Or maybe not.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
R o b e r t J. M i r r o
rmirro@microserve.net http://www.microserve.net/~rmirro/

I have lost the will to live
Simply nothing more to give
There is nothing more for me
Need the end to set me free
- Metallica
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~