[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC/EDI |
| Notice: | DEC/EDI V2.1 - see note 2002 |
| Moderator: | METSYS::BABER |
|
| Created: | Wed Jun 06 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3150 |
| Total number of notes: | 13466 |
3054.0. "Connection Timed out and extended areas and defunct" by UTRTSC::SMEETS (Workgroup support) Wed Mar 12 1997 19:56
Hi,
One of my favorites.....
Customer running DEC/EDI V3.1A with Oracle RDB V6.1-... and OBB V2.6-07 sees a
lot of the following messages in the DEC/EDI errorlog:
Mon Mar 10 10:19:32 1997 PID = 2693 NAME = Post/Fetch Server (CORBA)
DECEDI_ORBSTATMSG (i), Objectbroker status message = OBB_INV_TRNSERR (e),
Transport error '$TransportError$'.
-OBB_INV_TRANSERR (e), Transport error 'Connection timed out'.
DECEDI__ORBERROR (e), error encountered while calling the Objectbroker routine
CORBA_BOA_deactivate_obj
Mon Mar 10 10:19:34 1997 PID = 2693 NAME = Post/Fetch Server (CORBA)
DECEDI__ORBSRVSHTDWN (i), a server for handling client requests has been shut
down
Mon Mar 10 10:30:32 1997 PID = 3853 NAME = Post/Fetch Server (CORBA)
DECEDI__ORBSRVSTARTED (i), a server for handling client request has been started
The only explanation I could think of is in combination with the MAR and MAA
areas being extended. Althought these areas of an UNIFORM type and thus being
extended should not be a problem, after I performed secondary archiving the
problems didn't show up anymore. which ofcourse could be a coincidence.
The other thing I observed with the above PID 2693 was that there was a
<defunct> process whose parent pointed to PID 2693....
Martin
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3054.1 | Why is it being shut down | METSYS::HELLIAR | http://samedi.reo.dec.com/ | Thu Mar 13 1997 08:11 | 8 |
| Martin,
The messages imply someone shutting down either DEC/EDI or the
objectbroker methods. On trying to shutdown, the Post/Fetch Server
appears to get the request but then has problems (maybe because of a
memory leak).
Graham
|
| 3054.2 | How can we determine this... | UTRTSC::SMEETS | Workgroup support | Thu Mar 13 1997 10:29 | 11 |
| Hi Graham,
>> The messages imply someone shutting down either DEC/EDI or the
>> objectbroker methods. On trying to shutdown, the Post/Fetch Server
>> appears to get the request but then has problems (maybe because of a
>> memory leak).
I think the trigger in this scenario is the TRADE FETCH/TRADE POST operation
which time-out's for some reason after which the server proces dieds...
Martin
|