Miscellaneous Error Messages
| Code | 100000 |
| Severity | Critical |
| Message | Platform(): Out of memory at source file {0}, line {1} |
| Description | Contact your system administrator to either increase the per-process memory usage limits or add physical memory to the machine. |
| Code | 100001 |
| Severity | Info |
| Message | ---------------------------------------------------------------------- |
| Description | This is a separator used to make the log easier to read. |
| Code | 100002 |
| Severity | Warning |
| Message | Platform(): Error detected on file '{0}': {1} |
| Description | The Sybase Event Stream Processor has experienced an error when trying to read or write a file. Check whether the path exists and if the permissions are correct. If the path is relative, make sure that the Sybase Event Stream Processor's current directory is correct. |
| Code | 100003 |
| Severity | Warning |
| Message | Platform(): Requested operation on stream '{0}', no such stream. |
| Description | An XMLRPC command (from esp_client or from your custom binary) requested an operation on a non-existing stream. Make sure your command is correct. |
| Code | 100004 |
| Severity | Warning |
| Message | Internal error: {0} |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 100005 |
| Severity | Error |
| Message | {0} |
| Description | A general error message without an assigned error number. It should be self-explanatory. |
| Code | 100006 |
| Severity | Warning |
| Message | Environment: {0} is set to {1}, causing SLOW strcoll() behavior. |
| Description | The check of LC_ALL, LC_COLLATE, and LANG yielded a non-posix locale collating sequence. this means the strcoll() function will run SLOW. |
| Code | 100007 |
| Severity | Debug |
| Message | Environment: {0} is set to {1}, causing FAST strcoll() behavior. |
| Description | The check of LC_ALL, LC_COLLATE, and LANG yielded a posix locale collating sequence. this means the strcoll() function will run FAST. |
| Code | 100008 |
| Severity | Debug |
| Message | LC_ALL, LC_COLLATE, and LANG are all unset, causing FAST strcoll() behavior. |
| Description | The values of LC_ALL, LC_COLLATE, and LANG are all NULL which is the same a a posix collating sequence, this means the strcoll() function will run FAST. |
| Code | 101000 |
| Severity | Critical |
| Message | CommandControl(): could not get ephemeral port for xmlrpc server (abyss). |
| Description | An attempt to find an unused port number for XMLRPC service has failed. It is likely that there is a major issue in the machine's networking configuration. There is also the possibility of a rare failure if two instances of the Sybase Event Stream Processor or a similar program are trying to allocate unused port numbers at the same time. |
| Code | 101002 |
| Severity | Info |
| Message | CommandControl::execute(): starting xmlrpc server (abyss) with log file {0} on port {1} |
| Description | An informational message about starting the XMLRPC service. Shows the port number that may have been specified with option -c or chosen automatically with the parameter -c 0. Lack of this message may mean that the option -c was not specified and the XMLRPC service was not started. |
| Code | 101003 |
| Severity | Info |
| Message | CommandControl::execute(): server (abyss) exited. |
| Description | An informational message that the XMLRPC service has exited. It lets you track the stages when the Sybase Event Stream Processor stops. |
| Code | 101004 |
| Severity | Error |
| Message | CommandControl::authenticate(): invalid authentication token. |
| Description | A client tried to execute an XMLRPC request but presented an invalid authentication token. Possibly the server was restarted since this client has logged in, and it tries to present the old token to the new server. Restart the offending client. |
| Code | 101005 |
| Severity | Error |
| Message | CommandControl()::<various>: could not access GatewayServer. |
| Description | An XMLRPC command (from esp_client or from your custom binary) requested an operation that involves the gateway interface but the gateway is not available. This situation may happen if the Sybase Event Stream Processor is being shut down. |
| Code | 101006 |
| Severity | Error |
| Message | CommandControl::get_stream_definition(): Stream {0} not found. |
| Description | An XMLRPC command (from esp_client or from your custom binary) requested an operation on a non-existing stream. Make sure your command is correct. |
| Code | 101007 |
| Severity | Error |
| Message | CommandControl::get_stream_definition(): a null stream name is invalid. |
| Description | A client has sent an XMLRPC request to execute an operation on a stream but provided no stream name. Probably a wrong stream name parameter was given to that client. |
| Code | 101008 |
| Severity | Debug |
| Message | CommandControl::<various>(): entering call ({0}) |
| Description | An informational message about the start of processing of an XMLRPC call. |
| Code | 101009 |
| Severity | Debug |
| Message | CommandControl()::<various>: returning from call ({0}). |
| Description | An informational message about the end of processing an XMLRPC call. |
| Code | 101010 |
| Severity | Info |
| Message | CommandControl::execute(): wait on stream initialization before bringing up interfaces. |
| Description | Information about the internal stages of initialization. |
| Code | 101011 |
| Severity | Info |
| Message | CommandControl::execute(): stream initialization complete, CnC & Gateway interfaces initializing. |
| Description | Information about the internal stages of initialization. |
| Code | 101012 |
| Severity | Critical |
| Message | CommandServer()::load_config(): loading config from '{0}', flags '{1}'. |
| Description | Information about a received XMLRPC call for a dynamic modification. |
| Code | 101013 |
| Severity | Critical |
| Message | CommandServer()::load_config(): missing arguments. |
| Description | An XMLRPC call for a dynamic modification that has some arguments missing. |
| Code | 101014 |
| Severity | Critical |
| Message | CommandServer()::load_config(): new configuration contains incompatible changes. |
| Description | See the Administrator's Guide for the information on the Dynamic Services. You can either use the option "nocompat" to permit the application of incompatible changes or check your new model for the unintentionally introduced incompatible changes. |
| Code | 101015 |
| Severity | Critical |
| Message | CommandServer()::load_config(): new configuration contains errors. |
| Description | The model that was requested to be loaded dynamically contains errors. Look at the preceding messages for the detailed information about the errors. |
| Code | 101016 |
| Severity | Critical |
| Message | CommandServer()::load_config(): successfully loaded from '{0}'. |
| Description | Informational message that the dynamic modification request has been successfully completed. |
| Code | 101017 |
| Severity | Critical |
| Message | CommandServer()::load_config(): Dynamic configuration modifications are not supported in clustered mode. |
| Description | See the Administrator's Guide for the information on the Dynamic Services. The dynamic modifications may not be applied to an instance of Sybase Event Stream Processor that is a part of a cluster. |
| Code | 101018 |
| Severity | Error |
| Message | CommandControl::get_stream_handle_definition(): Stream handle {0} not found. |
| Description | An XMLRPC command (from esp_client or from your custom binary) requested an operation on a non-existing numeric stream id. This could happen due to an incorrect command or dynamic modification to the model. If a stream was dynamically modified in an incompatible way, the same stream name will become associated with a new numeric id. If a command has looked up the id by name before the dynamic modification and an operation was executed on this id after the modification has occurred, this error occurs. It should be treated as an intermittent error by the client program, with a retry of the lookup and execution of the operations. |
| Code | 101019 |
| Severity | Critical |
| Message | CommandServer()::load_config(): Creating the data conversion Sybase Event Stream Processor. |
| Description | Information about stages of the dynamic service modifications. |
| Code | 101020 |
| Severity | Critical |
| Message | CommandServer()::load_config(): Starting the data conversion Sybase Event Stream Processor. |
| Description | Information about stages of the dynamic service modifications. |
| Code | 101021 |
| Severity | Critical |
| Message | CommandServer()::load_config(): The data conversion Sybase Event Stream Processor has completed successfully. |
| Description | Information about stages of the dynamic service modifications. |
| Code | 101022 |
| Severity | Critical |
| Message | CommandServer()::load_config(): The data conversion Sybase Event Stream Processor has failed. |
| Description | The data conversion model specified for a dynamic modification is incorrect. See the preceding messages for the details of the errors. |
| Code | 101023 |
| Severity | Critical |
| Message | CommandServer()::load_config(): The option 'conv' may not be used together with an inlined conversion model. |
| Description | The data conversion model for a dynamic modification may be specified in one of two ways, inline or in a server-side file specified by the option 'conv'. But you cannot specify both at the same time so you must select one. |
| Code | 101024 |
| Severity | Info |
| Message | CommandServer()::load_config(): Disposing of the data conversion Sybase Event Stream Processor. |
| Description | Information about stages of the dynamic service modifications. |
| Code | 101025 |
| Severity | Info |
| Message | CommandServer()::load_config(): Disposing of the temporary Sybase Event Stream Processor instance. |
| Description | During the dynamic service modification, the new model is loaded into a temporary instance of the Sybase Event Stream Processor, within the same Sybase Event Stream Processor process. This instance is then analyzed for differences from the currently running model, and the modifications are applied to the currently running model. After modification is finished, the temporary instance is disposed. |
| Code | 101026 |
| Severity | Info |
| Message | CommandServer()::kill_client(): Killed client {0} on user request. |
| Description | The administrator has terminated a client connection through the XMLRPC interface command. |
| Code | 101027 |
| Severity | Info |
| Message | CommandServer()::kill_client(): User request to kill the client {0}, client not found. |
| Description | The administrator has requested to terminate a non-existing client connection. Possibly the client id argument was mistyped or the client had already disconnected by itself. |
| Code | 101028 |
| Severity | Info |
| Message | CommandServer()::run_control(): Unknown subcommand '{0}'. |
| Description | The XMLRPC command run_control has a number of subcommands identifying the exact action. The Pubsub API takes care of wrapping the subcommands into the individual calls. This error may mean that a new client program is trying to execute the new commands in an old version of the Sybase Event Stream Processor or a general corruption in the client program. |
| Code | 101029 |
| Severity | Info |
| Message | CommandServer()::run_control(): subcmd '{0}' arg '{1}'. |
| Description | Informational message about the subcommand of an XMLRPC call. The XMLRPC command run_control has a number of subcommands identifying the exact action. |
| Code | 101030 |
| Severity | Error |
| Message | CommandServer(): Could not parse XMLRPC call args: {0}: {1} |
| Description | An XMLRPC request with unparseable arguments was received. This error may mean that a new client program is trying to execute the incompatible commands in an old version of the Sybase Event Stream Processor, or a general corruption in the client program. |
| Code | 101031 |
| Severity | Critical |
| Message | CommandServer(): IMMEDIATE EXIT REQUESTED, EXITING |
| Description | Informational message the the XMLRPC command "immediate exit" was received and executed. The Sybase Event Stream Processor exits abruptly after this message. |
| Code | 101032 |
| Severity | Info |
| Message | CommandControl::execute(): waiting for the GatewayServer to exit. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 101033 |
| Severity | Info |
| Message | CommandControl::execute(): the GatewayServer exited. |
| Description | Informational message about the stages of Sybase Event Stream Processor shutdown. |
| Code | 101034 |
| Severity | Error |
| Message | CommandControl()::<various>: could not access Kerberos Server. |
| Description | You should either use a different authentication method or ask the system administrator to configure Kerberos. Contact your system administrator. |
| Code | 101035 |
| Severity | Error |
| Message | CommandControl()::execute: could not initialize the SASL library. |
| Description | This message appears when either Kerberos is not configured, the service "sp" is not registered or the Kerberos library has experienced some other error. |
| Code | 101036 |
| Severity | Error |
| Message | CommandControl()::checkCredentialsPAM, trying to login via PAM, but server not using PAM authentication. |
| Description | The client is trying to use a different kind of authentication than what is configured for the server. Check the server and client arguments and use the same authentication method for both. |
| Code | 101037 |
| Severity | Error |
| Message | CommandControl()::checkCredentialsRSA, trying to login via RSA, but server not using RSA authentication. |
| Description | The client is trying to use a different kind of authentication than what is configured for the server. Check the server and client arguments and use the same authentication method for both. |
| Code | 101038 |
| Severity | Error |
| Message | CommandControl()::checkCredentialsKERBV5, trying to login via SASL/Kerberos V5, but server not using SASL/Kerberos V5 authentication. |
| Description | The client is trying to use a different kind of authentication than what is configured for the server. Check the server and client arguments and use the same authentication method for both. |
| Code | 101039 |
| Severity | Error |
| Message | CommandControl()::login[_key,_kerberos]()], Authentication rejected for user ({0}). |
| Description | A client tried to log into XMLRPC service with a wrong password or unknown RSA key. If you believe that the password is correct and PAM authentication method is used, contact your system administrator to check the PAM configuration. If you believe that the RSA key is correct and the RSA authentication is used, check whether the matching public key is installed in the server's RSA public key directory. Make sure that the client uses the secret key file and the server has the public key file, not the other way around. See the Administrator's Guide for details. |
| Code | 101040 |
| Severity | Notice |
| Message | CommandControl()::login[_key,_kerberos]()], Authentication successful for user ({0}). |
| Description | A user has logged in successfully. |
| Code | 101041 |
| Severity | Error |
| Message | CommandControl::authenticate(): attempt at a control call from user without permissions. |
| Description | An user without administrative privileges has tried to execute an Sybase Event Stream Processor control request. Check the user name, and either grant the control role or use a different name. The control role may be granted using the attribute restrictAccess of the <Platform> node. |
| Code | 102002 |
| Severity | Critical |
| Message | RowInternal2::pack() critical error. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 104000 |
| Severity | Error |
| Message | Primop: Primitive operation '{0}' not yet implemented. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 104001 |
| Severity | Warning |
| Message | Function '{0}': Calendar file {1} not found. |
| Description | A non-existing calendar file was given as an argument to a calendar function. Check whether the path exists and whether the permissions are correct. If the path is relative, check that the Sybase Event Stream Processor's current directory is correct. |
| Code | 104002 |
| Severity | Warning |
| Message | Function 'business': Illegal offset of 0. |
| Description | Check your expressions. Probably an illegal argument was passed to a function. |
| Code | 104003 |
| Severity | Error |
| Message | Error in function '{0}': {1} |
| Description | Check your expressions. Probably an illegal argument was passed to a function. |
| Code | 107000 |
| Severity | Error |
| Message | {0}({1})::safeRead(): Read error {2} |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107001 |
| Severity | Debug |
| Message | {0}({1})::processData(): Starting FileReader. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107002 |
| Severity | Critical |
| Message | {0}({1})::processData(): Record has zero size. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107003 |
| Severity | Critical |
| Message | {0}({1})::processData(): Short read on record. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107004 |
| Severity | Warning |
| Message | {0}({1})::execute() record is for a different stream. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107005 |
| Severity | Critical |
| Message | {0}({1})::execute() error in reading record. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107006 |
| Severity | Debug |
| Message | {0}({1})::execute(): Exiting FileReader. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107007 |
| Severity | Warning |
| Message | {0}({1}): out of memory allocating a record of size {2}, skipping this record. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107008 |
| Severity | Critical |
| Message | Filereader(fd={0}) {1}({2}): got unknown stream handle {3}, stopped reading |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107009 |
| Severity | Critical |
| Message | {0}({1})::processData(): Record of {2} bytes is too large, probably a wrong byte order. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 107010 |
| Severity | Critical |
| Message | {0}({1})::processData(): A record is corrupted. |
| Description | Message from the File Reader that is used internally in the ESP test infrastructure. Should not occur in the normal customer usage. |
| Code | 108000 |
| Severity | Debug |
| Message | GatewayClient(:{0})::safeIO::execute(): {1} |
| Description | Information about a client disconnecting from the gateway. The message describes the exact reason. It may be a normal close, an abruptly closed socket causing an exception or a protocol error where a subscriber client tries to send more commands to the gateway interface. |
| Code | 108001 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::~GatewayClient() destroyed (auto). |
| Description | Information about a client being fully disconnected from the Sybase Event Stream Processor gateway and all information about this client being disposed. |
| Code | 108002 |
| Severity | Notice |
| Message | GatewayClient({0}:{1})::execute() Client successfully authenticated: mode ({2}), user ({3}). |
| Description | Informational message about a successful login to the gateway service. |
| Code | 108003 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::execute() Client failed authentication: mode ({2}), user ({3}). |
| Description | A client tried to log in to the gateway service with a wrong password or unknown RSA key. If you believe that the password is correct, and PAM authentication method is used, contact your system administrator to check the PAM configuration. If you believe that the RSA key is correct, and the RSA authentication is used, check whether the matching public key is installed in the server's RSA public key directory. Make sure that the client uses the secret key file and the server has the public key file, not the other way around. See the Administrator's Guide for details. |
| Code | 108004 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::execute() Switching to secure socket. |
| Description | Informational message that the client has requested the SSL encryption on the gateway connection, and the Sybase Event Stream Processor is configured to support it. |
| Code | 108005 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::execute() Server could not give client a secure connection. |
| Description | The client has requested the SSL encryption on the gateway connection but the Sybase Event Stream Processor is not configured to support it. Either configure the Sybase Event Stream Processor for the SSL support or change the client to not request it. |
| Code | 108006 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::execute() First command must be AUTHENTICATE_CLIENT. |
| Description | The client program hasn't followed the correct protocol. If it happens with an ESP-provided program, contact the Sybase support. Otherwise check your program. |
| Code | 108007 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::execute() REQUEST_SSL_MODE must be the first request from client. |
| Description | The client program hasn't followed the correct protocol. If it happens with an ESP-provided program, contact the Sybase support. Otherwise check your program. |
| Code | 108008 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::execute() Client closed/dropped connection. |
| Description | Information about a client disconnecting from the gateway. |
| Code | 108009 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::{2} Caught exception: {3} |
| Description | An informational message that may happen on certain socket errors. Probably, the client has dropped the connection at an unexpected time. It's also possible that the client program has crashed. |
| Code | 108010 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::execute() SUBSCRIBE_LOSSY |
| Description | Informational message that a client has requested the lossy subscription mode. |
| Code | 108011 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::execute() SUBSCRIBE_NOBASE |
| Description | Informational message that a client has requested the subscription without receiving the base contents of the stream. |
| Code | 108012 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::execute() Exiting. |
| Description | Informational message that a per-client gateway thread in the Sybase Event Stream Processor has exited. |
| Code | 108013 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::S_processMessage() Error exporting record (transactional). |
| Description | The gateway has failed to write a transaction data to the socket, and it's likely that the client has dropped the connection in the meantime. |
| Code | 108014 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::S_processMessage() Error exporting record (base). |
| Description | The gateway has failed to write the stream base data record to the socket, and it's likely the client has dropped the connection in the meantime. |
| Code | 108015 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::S_processMessage() Got an unknown message type. |
| Description | Some self-testing assertion in the Sybase Event Stream Processor has failed, which should never happen. Contact Sybase support if this message appears. |
| Code | 108016 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::S_:postWithQueueCheck() dropping data. |
| Description | Client has subscribed in a lossy mode, but is not receiving fast enough to keep up with the incoming data. |
| Code | 108017 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::S_postWithQueueCheck() resuming, dropped since last resume ({2}), total dropped ({3}). |
| Description | Client has subscribed in a lossy mode and caught up with receiving the data after some was dropped. |
| Code | 108018 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::S_postWithQueueCheck() fill {2} percent. |
| Description | Informational message about the fill level of the client's output queue. The high level of fill shows that the client is not keeping up with the data rate and soon may either block the Sybase Event Stream Processor (with the normal subscription mode) or have its data dropped (with the lossy subscription mode) or connection dropped (with the droppable subscription mode). |
| Code | 108019 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::P_doRecord() received record for unknown stream. Index: {2} |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 108020 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::G_getCommand() failed to malloc buffer during authentication or encryption, aborting. |
| Description | Contact your system administrator to either increase the per-process memory usage limits or add physical memory to the machine. |
| Code | 108021 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::{2} failed to malloc buffer during record command, size {3} |
| Description | Contact your system administrator to either increase the per-process memory usage limits or add physical memory to the machine. |
| Code | 108022 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::{2} detected large or too small, possibly bad message from client of size {3} |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 108023 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::execute() SUBSCRIBE_DISTRIBUTED |
| Description | Informational message showing that this client is another instance of the Sybase Event Stream Processor that is a part of the same cluster. |
| Code | 108024 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::S_registerSqlStream() could not parse SQL statement {{2}}. |
| Description | The SQL statement given in an SQL subscription is incorrect. Check its syntax and names of the streams and fields it refers to. |
| Code | 108025 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::S_registerSqlStream() could not resolve input stream for SQL statement {{2}}. |
| Description | The SQL statement given in an SQL subscription is incorrect. Check its syntax and names of the streams and fields it refers to. |
| Code | 108026 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::S_registerSqlStream() could not compile the SQL statement {{2}}, error:{{3}}. |
| Description | The SQL statement given in an SQL subscription is incorrect. Check its syntax and names of the streams and fields it refers to. |
| Code | 108027 |
| Severity | Warning |
| Message | GatewayClient({0}:{1}): {2} access control denied, stream '{3}' |
| Description | The client doesn't have permission to connect to the Sybase Event Stream Processor. Check the user name and then either grant the connect role or use a different user name. |
| Code | 108028 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::execute() Secure socket handshake failed, see preceding messages for details. |
| Description | The SSL protocol error. Check the client program call. Possibly the option enabling SSL was missed so it is trying to connect with a plain-text protocol to a secure port. |
| Code | 108029 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::execute() SUBSCRIBE_DROPPABLE |
| Description | Informational message that a client has requested the subscription that may be dropped (disconnected) if the client doesn't keep up with the data rate. |
| Code | 108030 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::S_postWithQueueCheck() client cannot keep up, queue full, dropping client connection. |
| Description | The client has subscribed with the droppable option and could not keep up with the flow of data. |
| Code | 108031 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::P_doRecord() caught exception reading record of size: {2} |
| Description | An informational message that may happen on certain socket errors. Probably, the client has dropped the connection at an unexpected time. It's also possible that the client program has crashed. |
| Code | 108032 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::G_getCommand failed, returned error code: {2} |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 108033 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::execute() SUBSCRIBE_PULSED |
| Description | Informational message that a client has requested the subscription in the pulse mode. In this mode, the data is sent periodically with the multiple modifications of the same record during the period collapsed into one. |
| Code | 108036 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::S_processSubscribeQueue() stream {2} pulsing {3} records to client. |
| Description | Informational message that the pulse update to this client is happening now. |
| Code | 108038 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::~GatewayClient() lossy subscribe: dropped since last resume ({2}), total dropped ({3}). |
| Description | The statistics of the dropped data at the end of a lossy subscription. |
| Code | 108040 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::P_doRecord() - max(size(block)) changed from {2} to {3} |
| Description | The statistics about the highest block size received so far from this client. |
| Code | 108041 |
| Severity | Debug |
| Message | GatewayClient({0}:{1})::execute() SUBSCRIBE_PRESERVE_BLOCKS |
| Description | Informational message that a client has requested the subscription with preservation of the transaction boundaries. |
| Code | 108042 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::initFinalizer() could not parse finalizer statement '{2}'; error {3} |
| Description | The SQL statement given in a finalizer is incorrect. Check its syntax and names of the streams and fields referred to. |
| Code | 108043 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::initFinalizer() access control denied for {2} '{3}' |
| Description | The SQL statement given in a finalizer is incorrect. Check its syntax and names of the streams and fields referred to. |
| Code | 108044 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::initFinalizer() finalizer references non-source stream '{2}' |
| Description | The SQL statement given in a finalizer is incorrect. Check its syntax and names of the streams and fields referred to. |
| Code | 108045 |
| Severity | Info |
| Message | GatewayClient({0}:{1}) Finalizer succeeded: {2} |
| Description | Informational message that the finalizer registered by this client had successfully executed. |
| Code | 108046 |
| Severity | Error |
| Message | GatewayClient({0}:{1}) Finalizer() failed with run-time code {2}: {3} |
| Description | The SQL statement given in a finalizer is incorrect. Check its syntax and names of the streams and fields referred to. Another reason could be that the Sybase Event Stream Processor was already shut down when the finalizer attempted to run. |
| Code | 108047 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::S_registerSqlStream() SQL statement {{2}}. |
| Description | Informational message reporting the statement used by this client for an SQL subscription. |
| Code | 108048 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::G_tryAuthenticationKERBV5() Client successfully authenticated. |
| Description | Informational message that a client has successfully logged in using the Kerberos authentication. |
| Code | 108049 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::G_tryAuthenticationKERBV5() generated a fault, error message: {2} |
| Description | A client has failed to authenticate with Kerberos. The error message contains the more detailed reason. Probably Kerberos is not properly configured. Consult your system administrator. |
| Code | 108050 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::G_tryAuthenticationKERBV5() failed, error message: {2} |
| Description | A client failed to authenticate through Kerberos. Check that the client's Kerberos ticket has not expired. |
| Code | 108051 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::G_tryAuthenticationPAM(), trying to login via PAM, but server not using PAM authentication. |
| Description | The client is trying to use a different kind of authentication than what is configured for the server. Check the server and client arguments and use the same authentication method for both. |
| Code | 108052 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::G_tryAuthenticationRSA(), trying to login via RSA, but server not using PAM authentication. |
| Description | The client is trying to use a different kind of authentication than what is configured for the server. Check the server and client arguments and use the same authentication method for both. |
| Code | 108053 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::G_tryAuthenticationKERBV5(), trying to login via SASL/Kerberos V5, but server not using SASL/Kerberos V5 authentication. |
| Description | The client is trying to use a different kind of authentication than what is configured for the server. Check the server and client arguments and use the same authentication method for both. |
| Code | 108054 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::G_setTerminator(), will exit without heartbeat of {2} ms. |
| Description | Informational message that a client has requested the Sybase Event Stream Processor to exit if the client stops generating the heartbeat or the connection to this client ever gets dropped for any reason. |
| Code | 108055 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::S_setQueueMax(), setting queue depth to {2} rows. |
| Description | Informational message that a client has requested its gateway queue size limit set to the reported value. |
| Code | 108056 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::S_setQueueMax(), argument of {2} rows is less than minimum value of 1000. |
| Description | Informational message that a client has requested its gateway queue size limit set to a value lower than the lowest one supported. |
| Code | 108057 |
| Severity | Warning |
| Message | GatewayClient({0}:{1})::execute(), ignoring request for shine through, a SQL subscription is incompatible with shine through. |
| Description | Informational message that a client has requested the shine-through option on an unsupported SQL subscription. |
| Code | 108058 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::execute(), setting shine through optimization on subscription. |
| Description | Informational message that a client has requested the shine-through option on subscription to reduce the volume of data. |
| Code | 108059 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::execute(), setting EXIT on a dropped connection. |
| Description | Informational message that a client has requested the Sybase Event Stream Processor to exit if the connection to this client ever gets dropped by any reason. |
| Code | 108060 |
| Severity | Warning |
| Message | GatewayClient::S_post({0}:{1}) queue at 99% of limit. |
| Description | Informational message about the fill level of the client's output queue. The high level of fill shows that the client is not keeping up well with the data rate and soon may either block the Sybase Event Stream Processor (with the normal subscription mode), have its data dropped (with the lossy subscription mode) or have its connection dropped (with the droppable subscription mode). This message means that the queue has gotten very close to being full and the stoppage or dropping is imminent. |
| Code | 108061 |
| Severity | Warning |
| Message | GatewayClient::S_post({0}:{1}) queue dropped below 51% of limit. |
| Description | Informational message about the fill level of the client's output queue. It shows that the client has restarted the consumption of data, and the queue has drained from completely filled to less than half-filled. |
| Code | 108062 |
| Severity | Warning |
| Message | GatewayClient::GatewayClient({0}:{1}) host:[{2}] has initiated a connection. |
| Description | Informational message about the origin of a newly received gateway connection. |
| Code | 108063 |
| Severity | Critical |
| Message | GatewayClient::postToSubscriberQueue({0}:{1}) time to drain base data {2} ms exceeded limit {3} ms, dropping client connection. |
| Description | The client took too long to read the base contents of the stream. The Sybase Event Stream Processor has stopped sending data to this client to avoid blocking the other clients. If the stream contents is large, you may want to increase the time limit that can be set individually by each client. |
| Code | 108064 |
| Severity | Info |
| Message | GatewayClient({0}:{1})::S_setBaseDrainTime(), setting base drain time from {2} ms to {3} ms. |
| Description | Informational message that a client has set an alternative time limit for receiving the stream base contents. |
| Code | 108065 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::P_doRecord() received an envelope with a record offset beyond its size (record {2}/{3}). |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 108066 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::P_doRecord() received a transaction with a record offset beyond its size (record {2}/{3}). |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 108067 |
| Severity | Error |
| Message | GatewayClient({0}:{1})::P_doRecord() received a record with offset beyond its size. |
| Description | There is something wrong with either the client program or the data it's trying to upload. Possibly the binary data was converted for a different model or machine with a different byte order (such as Intel vs Sun SPARC) or the data file was simply corrupted. |
| Code | 108068 |
| Severity | Critical |
| Message | GatewayClient({0}:{1})::~GatewayClient() forcing system shutdown, exitOnDrop or exitNoBeat is set. |
| Description | Information about a client being fully disconnected from the Sybase Event Stream Processor gateway and all information about this client being disposed. |
| Code | 108069 |
| Severity | Warning |
| Message | GatewayClient({0}:{1}):: publishing to a non-input stream is not allowed. Index: {2}. |
| Description | Client is attempting to publish data to a LOCAL or OUTPUT stream, which is not allowed. |
| Code | 108070 |
| Severity | Warning |
| Message | GatewayClient({0}:{1}):: attempting to publish or subscribe to a local stream. Index: {2}. |
| Description | Client is attempting to publish or subscribe to a LOCAL stream, which is not allowed. |
| Code | 108071 |
| Severity | Warning |
| Message | GatewayClient::S_outputData({0}:{1}) Discarding large row/transaction of size {2} with {3} rows. |
| Description | The ESP Server and ESP client cannot handle transaction sizes larger than 2147483647 bytes. |
| Code | 108072 |
| Severity | Debug |
| Message | GatewayClient. Dumped {0} rows to badrecord file. |
| Description | Logging for dumping the rows from large, bad, transactions. |
| Code | 109000 |
| Severity | Critical |
| Message | GatewayServer({0}): Could not bind port {1} |
| Description | The explicit port specified with the command line option -g is already taken by another program or another copy of the server already running. Check with your system administrator. |
| Code | 109001 |
| Severity | Info |
| Message | GatewayServer({0}): Started on port {1} |
| Description | An informational message showing the port where the gateway service has started. |
| Code | 109002 |
| Severity | Critical |
| Message | GatewayServer({0}): Failed to spawn new connection, exception: {1} |
| Description | Probably the limit of threads or TCP/IP sockets per process is exhausted. Consult your system administrator. Check for runaway processes that may be creating the rogue connections. |
| Code | 109003 |
| Severity | Critical |
| Message | GatewayServer({0}): canonical hostname({1}) empty. |
| Description | The symbolic host name is not set on the machine. Consult your system administrator. |
| Code | 109004 |
| Severity | Warning |
| Message | GatewayServer::GatewayServer() ephemeral port chosen: {0} |
| Description | An informational message showing the automatically selected port number chosen for the gateway service. |
| Code | 109005 |
| Severity | Warning |
| Message | GatewayServer::GatewayServer() using passed port: {0} |
| Description | An informational message showing the port number specified for the gateway service with the command-line option -g. |