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 |
VMS V6.1 DECedi V2.1c I have a customer that has a problem with stuck documents that is currently being worked on by engineering. To workaround the stuck documents they have written a routine that goes through a track list (list of available docs) and makes sure that all documents can be fetched. The routines they have written are all in Cobol and a 'C' interface has been written so that they can communicate with DECedi V2.1c. Sometimes they receive the following errors in the DECedi Error log file: DECEDI-I-ORBSTATMSG, Object Broker satus message = %OBB-E-INV_NOTAUTHORIS, client user is not authorised to access server DECEDI-E-ORBERROR, An error was encountered calling the Object Broker routine CORBA_BOA_activate_obj, decedi condition logged DECEDI-I-ORBSTATMSG, %OBB-E-INV_SRVNOTREG, server is not registered. DECEDI-E-ORBERROR, An error was encountered calling the Object Broker routine OBB_BOA_DISPATCH decedi condition logged DECEDI-I-ORBSTATMSG, %OBB-E-INV_SRVNOTREG, server is not registered. DECEDI-E-ORBERROR, An error was encountered calling the Object Broker routine OBB_BOA_IMPL_UNREGISTER This then kills their API programs. They then stop DECedi. All the OBB_pid processes do not close down and so have to be deleted by hand. They then start DECedi up again and it all works again. This problem appears to occur when they have 60/70 docs being stuck at any one time. Could it be that the max no of server instances has been reached? He says that at any one time 2 or 4 copies of the server could be be going through their tests and hammering Object Broker. Also on separate occasions they see the following problem: %DECEDI-I-ORBSTATMSG, Object Broker status message= %OBB-E-COM_BADUUID, Bad UUID '<NIL>' failure OBB dispatch OBB_BOA_DISPATCH decedi condition logged Any ideas? Richard Simpson.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3083.1 | KERNEL::SIMPSONR | fred | Wed Apr 23 1997 10:42 | 51 | |
The problem is still with them even though the stuck documents problem has been resolved. I rang the customer and he said that the problem is still occurring. They get an extra error that now mentions deactivate instead of activate: DECEDI-I-ORBSTATMSG, Object Broker status message = %OBB-E-INV_NOTAUTHORIS, client user is not authorised to access server DECEDI-E-ORBERROR, An error was encountered calling the Object Broker routine CORBA_BOA_deactivate_obj, decedi condition logged Then he gets the following errors logged after the DECEDI$ERROR log errors in a file called DECEDI.ERR. This file is found in SYS$LOGIN of the detached server that is using Objectbroker. Module : DECEDI_API_FETCH , %OBB-E-BOA_OBJNOTACTIV, The Object Reference is Not Active. Module : DECEDI_API_FETCH , %ACAS-E-INV_HOSTNOTFND, A host node could not be found to execute the request. -ACAS-E-INV_NOTAUTHORIZ, CLient user is not authorized to access server. Module : DECEDI_API_TRACK , %ACAS-E-INV_HOSTNOTFND, A host node could not be found to execute the request. -ACAS-E-INV_NOTAUTHORIZ, CLient user is not authorized to access server. Module : DECEDI_API_FETCH , %ACAS-E-INV_HOSTNOTFND, A host node could not be found to execute the request. -ACAS-E-INV_NOTAUTHORIZ, CLient user is not authorized to access server. Module : DECEDI_API_TRACK , %ACAS-E-INV_HOSTNOTFND, A host node could not be found to execute the request. -ACAS-F-COM_INSUFVM, Insufficient Memory Module : DECEDI_API_TRACK , %ACAS-E-INV_HOSTNOTFND, A host node could not be found to execute the request. -ACAS-E-INV_DISCONN, The connection has been disconnected. -ACAS-E-INV_TRANSERR, Transport error 'broken pipe'. Module : DECEDI_API_TRACK , %ACAS-E-INV_HOSTNOTFND, A host node could not be found to execute the request. Module : DECEDI_API_FETCH , %ACAS-E-INV_HOSTNOTFND, A host node could not be found to execute the request. -ACAS-F-COM_INSUFVM, Insufficient Memory Please can someone have a look at this problem and provide some ideas as to what information is required to further this problem, Cheers, Richard. | |||||
3083.2 | Seems a weird mix | SYSTEM::HELLIAR | http://samedi.reo.dec.com/ | Wed Apr 23 1997 14:52 | 11 |
Richard, Why are there ACAS errors? Either the user is using the CORBA interface in which case all errors will be CORBA*,OBB* etc or he is using the ACAS interface, in which case they will be ACAS*. So, what interfaces do they thing they are using, and that OBB ands ACAS versions are installed on the system? Graham | |||||
3083.3 | METSYS::THOMPSON | Wed Apr 23 1997 15:02 | 5 | ||
fyi: we've advised customer directly how to switch to CORBA. We're waiting to see if that makes a difference. M |