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.

5306

INFO: Unable to send msg-type message - queue block condition, dropping message!

Description

When GWTDOMAIN attempted to forward an incoming request/reply to a local server/client process, GWTDOMAIN encountered a full request/reply message queue.

Action

Monitor IPC message queues to identify server/client that is unable to keep up with the GWTDOMAIN's throughput.

5307

WARN: Secondary/Backup RDOM %s in ON_DEMAND mode, removed from service service-name!

Description

The GWTDOMAIN configuration of the connection policy for the remote TDomain is ON_DEMAND. When remote TDomain has connection policy set as ON_DEMAND it is not allowed to be the secondary or backup role for an imported service.

Action

Correct the configuration of the remote TDomain to have connection policy set to either ON_STARTUP or INCOMING_ONLY if the failover behavior is required. Otherwise remove the remote domain from the list supporting the imported service.

5308

ERROR: Cannot initialize synchronization structure for Timer Object!

Description

The gateway failed to initialize the mutex and conditional variable that are required internally for accessing shared resources.

Action

Check the OS configuration, and make sure it supports thread.

5309

ERROR: Cannot initialize synchronization structure for Timer Object!

Description

The gateway failed to initialize the mutex and conditional variable that are required internally for accessing shared resources.

Action

Check the OS configuration, and make sure it supports thread.

5310

ERROR: Failed to create timer object thread

Description

The gateway failed to create a thread to handle timer object request.

Action

Check the OS configuration, make sure it not only support thread but also allows enough threads per process.

5311

ERROR: Internal Timer Object Manager already created!

Description

Gateway initialization error and cause it to create timer object manager more than once.

Action

Internal error. Contact your BEA Customer Support.

5312

ERROR: Timer Object Memory allocation failure!

Description

Memory allocation failure while creating timer object.

Action

Check you DMCONFIG configuration file, and the computer system configuration. Reduce number of remote domains that requires DMKEEPALIVE, or increase system memory. If problem persists, contact your BEA Customer Support.

5313

WARN: multiple RDOMs not allowed on REMOTE_SERVICES in ON_DEMAND mode

Description

Multiple RDOMs for the REMOTE_SERVICES is for domain failover. Only when connection policy is either ON_STARTUP, or INCOMING_ONLY will the failover be allowed. The failover is not supported in ON_DEMAND mode.

Action

Correct the domain configuation.

5314

WARN: Only the first RDOM for service service-name will be used

Description

The ON_DEMAND connection policy does not support failover.

Action

Remove the extra RDOMs from the RDOM list or change the connection policy to either ON_STARTUP or INCOMING_ONLY.