Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

LIBGW Messages 5300-5399

5300	ERROR: [caller] failed to malloc space for purpose - request discarded
	Description	An attempt to dynamically allocate memory from the operating system using malloc failed while Domains gateway was attempting to process the authorization token for a message.
	Action	Make sure the operating system parameters are set correctly for the amount of me mory on the machine and the amount of memory that can be used by a process. Redu ce the memory usage on the machine or increase the amount of physical memory on the machine.
5301	ERROR: Cannot send service state change to GWADM due to error (val)
	Description	The Domains Gateway library software detected this condition while trying to notify the Domains Gateway administration server, GWADM, that the status of a remote service has changed.
	Action	Take note of the specific error reported in the message. It may be necessary to increase the IPC queue size or the number of messages limit for this operating system, in order to accomodate the service state change notifications.
	See Also	GWADM(5), GWTDOMAIN(5)
5302	WARN: unable to propagate the message priority, GLOBAL or LOCAL_ABSOLUTE
	Description	The message priority could not be set to GLOBAL or LOCAL_ABSOLUTE.
	Action	Check the log for related messages. If the problem persists contact contact your BEA Customer Support
5303	WARN: unable to set the message priority locally, LOCAL_RELATIVE
	Description	The message priority could not be set to LOCAL_RELATIVE.
	Action	Check the log for related messages. If the problem persists contact contact your BEA Customer Support
5304	ERROR: _dmcf_OLD_open failed: Can't open DM_TDOMAIN section
	Description	When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_TDOMAIN section.
	Action	Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.
5305	ERROR: _dmcf_OLD_open failed: Can't open DM_OSITPX section
	Description	When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_OSITP section.
	Action	Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application.