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 | Jolt | Topic List | Previous | Next | Contents | Index
Using BEA Jolt
Jolt Relay (JRLY) Messages
ERROR
Ignoring syntax error in configuration file line %d
Description
The line in question doesn't contain an equal sign or (in case of the LISTEN and CONNECT tag) is missing the colon.
Action
Verify the syntax of the configuration file at the specified line.
Ignoring unknown tag '%s' in configuration file line %d.
The line in question is does not contain one of the valid tags: LOGDIR, ACCESS_LOG, ERROR_LOG, LISTEN, CONNECT.
MSG_MALLOC: perror().
Memory allocation failed. The relay will exit.
Make more memory available on the machine on which the relay is running. Remove other unnecessary processes that may be running on the same host as the relay. Restart the relay.
Client structure != NULL for file descriptor %ld
An internal error occurred. The relay will continue to run, but a client process may have been disconnected.
None. If this message appears repeatedly and can be reproduced consistently, notify BEA Customer Support.
Invalid file descriptor %ld
None. If this message appears repeatedly and can be reproduced consistently notify BEA Customer Support.
Could not open configuration file %s
The specified configuration file does not exist or is not readable. The relay will exit.
Check the file name and the permissions on the file and the directory.
No log directory specified.
LOGDIR was not specified in the configuration file or no value for it was given.
Verify the entry for the tag LOGDIR in the configuration file. Check that the correct configuration file is being used (-f parameter).
No access log file specified.
ACCESS_LOG was not specified in the configuration file or no value for it was given.
Verify the entry for the tag ACCESS_LOG in the configuration file.Check that the correct configuration file is being used (-f parameter).
No error log file specified.
ERROR_LOG was not specified in the configuration file or no value for it was given.
Verify the entry for the tag ERROR_LOG in the configuration file. Check that the correct configuration file is being used (-f parameter).
No JRLY host specified
The value for the LISTEN tag does not contain the host name or IP address or the relay host, e.g., LISTEN=host:port.
Verify the entry for the tag LISTEN in the configuration file. Check that the correct configuration file is being used (-f parameter).
No JRAD host specified.
The value for the CONNECT tag does not contain the host name or IP address or the JRAD host, for example, CONNECT=host:port.
Verify the entry for the tag CONNECT in the configuration file. Check that the correct configuration file is being used (-f parameter).
No listener port specified or listener port <= 0.
The value for the LISTEN tag does not contain a valid port number on the relay host.
No JRAD port specified or JRAD port <= 0.
The value for the CONNECT tag does not contain a valid port number on the relay host.
Verify the entry for the tag CONNECT in the configuration file.Check that the correct configuration file is being used (-f parameter).
Could not determine IP address of listener host
The relay could not look up the IP address of the host machine.
If the host was specified as a host name replace it with the IP address and restart the relay. If it already was given as IP address make sure that the IP address is correct and that you're trying to start the relay on this host. Note that the address specified must be the address of the host on which the relay is running.
Cannot bind socket
The listener port specified in the configuration file is already being used by another application or still in a final wait state from a previous run of jrly.
Either specify a different port number in the configuration file (and all HTML files containing the IP address and port number of the relay) or wait a few minutes. The command "netstat -a" displays existing connections.
Can't open log file %s
Either the error log file or access log file (or both) could not be opened for writing.
Check the configuration file for correct spelling of the LOGDIR. Make sure you have write permissions on this directory and the files specified. On Windows NT, the directory separators must be back slashes, not forward slashes.
WSAStartup failed (NT only)
The Winsock driver could not initialize. Possible causes:
The underlying network subsystem is not ready for network communication Version 2.0 of Windows Sockets support is not provided by this particular Windows Sockets implementation.
Limit on the number of tasks supported by the Windows Sockets implementation has been reached.
Check the networking software configuration on your system.
Couldn't load Winsock Driver version 2.X. (NT only)
The relay requires Winsock version 2 or higher, but could not load it.
Check the networking software configuration on your system. An older version of Windows Sockets support was detected.
FATAL ERROR: unknown message code %ld.
Internal error. The relay will exit
Restart the relay. If this message appears repeatedly and can be reproduced consistently notify BEA Customer Support.
connect: Connection refused
The relay could not connect to JRAD.
Make sure the relay adapter (JRAD) is running. Check that the CONNECT tag in the relay configuration file identifies the correct host and port on which the JRAD is running.
accept(): accept failed, errno: 24, strerror: Too many open files
The relay tried to open more files/sockets than the system limit.
The default maximum number of open file descriptors for a process is 64 on most UNIX systems. Set this number to at least 1024 (with the limit or ulimit commands).
Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.
