Message Class 0013 - EntireX Java

This page describes messages with message class 0013. The messages have the format:

0013nnnn

where 0013 is the message class, and
nnnn are the error numbers grouped as follows:
01nn EntireX Java ACI Errors
02nn EntireX Java RPC Errors
03nn Errors in the Transport Layer
04nn SSL Errors
09nn Errors for Broker Agent

This document covers the following topics:

Overview of Messages

00130100 | 00130101 | 00130102 | 00130103 | 00130104 | 00130105 | 00130106 | 00130107 | 00130108 | 00130109 | 00130110 | 00130111 | 00130112 | 00130113 | 00130114 | 00130115 | 00130116 | 00130117 | 00130118 | 00130119 | 00130120 | 00130121 | 00130200 | 00130201 | 00130202 | 00130203 | 00130204 | 00130205 | 00130206 | 00130207 | 00130208 | 00130209 | 00130210 | 00130211 | 00130212 | 00130213 | 00130214 | 00130215 | 00130216 | 00130217 | 00130218 | 00130219 | 00130220 | 00130221 | 00130222 | 00130223 | 00130300 | 00130301 | 00130302 | 00130303 | 00130304 | 00130305 | 00130306 | 00130307 | 00130308 | 00130309 | 00130310 | 00130311 | 00130312 | 00130313 | 00130314 | 00130315 | 00130316 | 00130317 | 00130318 | 00130319 | 00130320 | 00130321 | 00130322 | 00130323 | 00130324 | 00130325 | 00130326 | 00130327 | 00130328 | 00130331 | 00130332 | 00130333 | 00130334 | 00130400 | 00130401 | 00130402 | 00130403 | 00130404 | 00130405 | 00130406 | 00130407 | 00130408 | 00130900 | 00130901 | 00130902 | 00130903 | 00130904
00130100 Register/RegisterAttach invalid for generic Service
Explanation

Register or RegisterAttach has been called for a generic service (server address contains at least one asterisk). These methods are applicable to real services only.

Action

Correct your application.
00130101 Send invalid for generic service
Explanation

A send using a generic service was attempted.

Action

Correct your application.
00130102 SendReceive invalid for generic service
Explanation

A sendReceive using a generic service was attempted.

Action

Correct your application.
00130103 Service.receive: Service returned by Broker not found
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130104 Service.receive: found old conversation
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130105 Service.receive: found wrong conversation
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130106 Service.receive: got UnitofWork
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130107 addConv: convID already found
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130108 delConv: convID not found
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130109 findUnitofWork: no UnitofWork
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130110 findConversation: no Conversation
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130111 endConversation: no conversation
Explanation

The endConversation method has been called on either a newly created conversation or an already closed conversation.

Action

Correct your application.
00130112 undo: no conversation
Explanation

The undo method has been called on either a newly created conversation or an already closed conversation.

Action

Correct your application.
00130113 send/sendReceive: got wrong convID, expected=:1:,received=:2:
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130114 receive: got wrong convID, expected=:1:,received=:2:
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130115 :1:: no running UnitofWork
Explanation

The specified UnitofWork method (first parameter) has been called on a non-active UnitofWork.

Action

Correct your application.
00130116 Codepage support for Broker :1: requires version 5.2 or higher
Explanation

Codepage support has been requested for an EntireX Broker version 5.1 or lower.

Action

Disable codepage support for previous versions of EntireX Broker or use a Broker version 5.2 or higher.

00130117 Requested call invalid for attach server
Explanation

A method different from receiveAttachInfo has been called on an attach server.

Action

Only the receiveAttachInfo method can be used for an attach server.

00130118 Encryption level support for Broker :1: requires version 6.1 or higher
Explanation

Encryption level support has been requested for an EntireX Broker version 5.3 or lower.

Action

Do not use encryption level for previous versions of EntireX Broker or use Broker version 6.1 or higher.

Note:
For encrypted transport we strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.

00130119 Security object already set
Explanation

For a Broker object, you are only allowed to set the security object once.

Action

Correct your application.
00130120 Data compression support for Broker broker ID requires version 7.1 or higher
Explanation

The broker in use does not support data compression. For data compression you need a broker version 7.1 or higher.

Action

Check your compression level settings or upgrade the broker.
00130121 Encoding encoding name not supported
Explanation

The Java Runtime Environment in use does not support this encoding.
Action

Check your Java Runtime Environment for the supported character encodings.

00130200 rpcCall: length of SendBuffer is :1: instead of :2:
Explanation

An internal inconsistency in the Java RPC has been detected.
Action

Contact Software AG Support.
00130201 rpcCall: unexpected end of conversation
Explanation

The RPC server returns an end of conversation indication which is unexpected by the client.

Action

Check the conversation logic of your RPC client application.
00130202 rpcCall: length of received buffer too small, length = :1:
Explanation

The RPC server returned a reply with an illegal length.
Action

Check that your application is communicating with an RPC server. If the problem is reproducible, contact Software AG Support.

00130203 rpcCall: wrong RPC version returned = :1:
Explanation

The reply returned from the RPC server uses a different RPC protocol version.

Action

Check that the RPC server can handle the same protocol version the client requests. Possible reasons could be that your client requests compression or Natural Security and the RPC server does not support these functionalities.

00130204 rpcCall: error returned from RPC server: :1:
Explanation

The RPC server returned the indicated error response.
Action

Depends on the error response. Check the RPC server's log for more information.

00130205 rpcCall: program :1: not found in library :2:
Explanation

The RPC server could not locate the requested (remote) program in the specified library.

Action

Check the location of the remote program.
00130206 rpcCall: internal error :1:
Explanation

The RPC server returned an error response for an internal error.
Action

Depends on the error response. Check the RPC server's log for more information.

00130207 rpcCall: error returned from server application for program :6:: number = :1: in line :2: of program :3: status=:4:, level=:5:
Explanation

This error usually indicates a problem in the Natural server application. If the error is in the range 6970 to 6979 it is a problem in the Natural RPC Server.

Action

Check your server application.
00130208 rpcCall: receive length :1: does not match expected length :2:
Explanation

The data which has been received from the RPC server caused an internal inconsistency in the Java RPC.

Action

Check if your application is communicating with an EntireX/Natural RPC Server. If the problem is reproducible, contact Software AG Support.

00130209 rpcCall: numeric value :1: does not fit in :2:.:3:
Explanation

The value of a N/P parameter exceeds the format specification. For example, the value is 123.12 and the format is N2.2.

Action

Application problem.
00130210 rpcCall: Natural Security requires non blank UserId, Password and Library
Explanation

When NaturalLogon is enabled, non-blank values for Library, UserId, and Password have to be provided.

Action

Provide all necessary data in the RPC client application.
00130211 rpcCall: ISO 8859_1 codepage not available
Explanation

Conversion from a Java String to a byte array based on the codepage ISO 8859_1 failed.

Action

Check your Java installation. The standard codepage ISO 8859_1 should be supported.

00130212 rpcCall: exponent of floating-point number :1: greater than 99
Explanation

The exponent of a floating-point number used as input to an RPC request is greater than 99. This is not supported by EntireX RPC.

Action

Application problem.
00130213 rpcCall: server does not support required version :1:
Explanation

The request issued by the RPC client cannot be processed. Required functionality is missing in target RPC-based Components or EntireX Broker.

Action

  • If you are using one of the following codepages or codepage styles:

    Check the version of the EntireX Broker and the RPC server in use. Upgrade the EntireX Broker and the RPC server to the latest version available.

  • If you are not using one of the codepages or codepage styles listed above:

    Check the version of the RPC server in use. Upgrade the RPC server to the latest version available.

See also Supported RPC Protocols in the EntireX RPC Programming documentation.

00130214 rpcCall: error:1: returned from server application for program :2: in library :3:
Explanation

This error usually indicates a problem in the server application.
Action

Check your server application.
00130215 No Broker instance or server address specified
Explanation

The generated proxy has been instantiated without a Broker instance or server address specified. This necessary information was not supplied before calling a method of the proxy.

Action

Use the setBroker and setServerAddress methods to specify the missing information.

00130216 Attempt to change the Broker instance or the server address during a conversation
Explanation

Either the method setBroker or setServerAddress has been called during a conversation, which is not possible.

Action

Correct your application.
00130217 rpcCall: malformed string buffer, offset=<offset>, length=<length>
Explanation

The RPC response from the server is not well formed. This may happen when RPC client and RPC server are not compatible.

Action

Contact Software AG Support.
00130218 rpcCall: invalid length in buffer: <part of buffer>, length: <length>, digits: <number of digits>
Explanation

The RPC response from the server is not well formed. This may happen when RPC client and RPC server are not compatible. The <part of buffer> contains the part of the buffer that should be a length, <length> is the length computed from the buffer part, <number of digits> is the number of digits parsed for the length.

Action

Contact Software AG Support.
00130219 rpcCall: Failed to create change password message
Explanation

The Java Runtime was unable to create a message for the RPC password change. This is used for Natural RPC Servers running with Natural Security.

Action

Contact Software AG Support.
00130220 rpcCall: Failed to create change password message: <exception detail>
Explanation

The Java Runtime was unable to create a message for the RPC password change. This is used for Natural RPC Servers running with Natural Security. See <exception detail> for the reason.

Action

Contact Software AG Support.
00130221 rpcCall: Reliable RPC supports only IN parameters. INOUT <inout-length>, OUT <out-length>
Explanation

Reliable RPC allows only IDL direction IN parameters. The length of all INOUT parameters sent is given in <inout-length>. The length of all OUT parameters sent is given in <out-length>.

Action

Update your IDL, that is, remove any OUT and INOUT parameters, possibly re-generate your interface object and/or update your application, then retry the RPC call.

00130222 rpcCall: No item found in mixed password cache for <item> where one is expected
Explanation

An internal inconsistency in the Java RPC has been detected.
Action

Contact Software AG Support.
00130223 rpcCall: client runtime does not support required version :1: (client runtime version is :2:)
Explanation

The request issued by the RPC client cannot be processed because the RPC client runtime does not support the required RPC functionality.

Action

Check the version of the RPC client runtime in use. Upgrade the RPC client runtime to the latest version available. See also Supported RPC Protocols in the EntireX RPC Programming documentation.

00130300 Unknown character set, value for left brace=:1:
Explanation

The EntireX Java ACI was unable to determine the native character set on the machine where it is running.

Action

Contact Software AG Support.
00130301 Unknown character set, value for blank=:1:
Explanation

The EntireX Java ACI was unable to determine the native character set on the machine where it is running.

Action

Contact Software AG Support.
00130302 Invalid ETB reply, length=:1:
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Check if your application is communicating with an EntireX broker. If the problem is reproducible, contact Software AG Support.

00130303 Reply signature (*ANS) not found
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Check if your application is communicating with an EntireX broker. If the problem is reproducible, contact Software AG Support.

00130304 No API string returned from BROKER length={}
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Check if your application is communicating with an EntireX broker. If the problem is reproducible, contact Software AG Support.

00130305 BROKER return length (:1:) differs from communication layer length(:2:)
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Check if your application is communicating with an EntireX broker. If the problem is reproducible, contact Software AG Support.

00130306 Unknown ACI binary key :1:
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Contact Software AG Support.
00130307 Unknown ACI string keyword :1:
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Contact Software AG Support.
00130308 Wrong length for TEXT: :1:
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Contact Software AG Support.
00130309 Broker call: uniqueId must be a 28 byte array, actual length=:1:
Explanation

An internal inconsistency in the EntireX Java ACI has been detected.

Action

Contact Software AG Support.
00130310 Broker call failed: Invalid TCP header received, length = :1:
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Check if your application is communicating with an EntireX broker. If the problem is reproducible, contact Software AG Support.

00130311 Connection to :1: failed: :2:
Explanation

An exception occurred when trying to establish a network connection to an EntireX broker.

Action

Check the error message returned from the Java networking class.
00130312 Socket connect failed due to Java security restrictions for :1:::2: (:3:)
Explanation

A security exception occurred during the open of a socket connection to an EntireX broker. A Java security manager is active which refused to open this socket connection.

Action

The most common reason for this exception is that a Java applet is trying to establish a connection to a Broker which is running on a machine which is not the same as the Web server the applet has been downloaded from. Your Broker has to run on the Web server machine or you have to use the Broker Agent. To get the correct IP address of the Web server machine use the getCodeBase().getHost() method call from the applet class.

00130313 Send/receive failed for :1: (:2:)
Explanation

An exception occurred during the transfer of data to an EntireX broker through a network connection.

Action

Check the error message returned from the Java networking class.
00130314 Socket connect failed: :1: unknown (:2:)
Explanation

The specified Broker ID could not be resolved to an IP address.
Action

Specify a valid Broker ID. Non-numeric IDs must be registered with the Domain Name System (DNS).

00130315 Socket connect failed for :1:::2: (:3:)
Explanation

Connection to the EntireX Broker failed. This means that the remote host could be reached, but is not responding.

Action

Check if a Broker is running on the specified machine and is listening on the specified port.

00130316 Transport Timeout exceeded (:1:)
Explanation

The timeout specified in the entirex.timeout property has elapsed. It is also possible that this error is caused by an interruption of the Java thread which is executing the Broker call. Check the additional error message for details.

Action

Check availability of the EntireX Broker in case of a timeout. Expected behavior in case of an interrupt.

00130317 Invalid Transport Timeout <value of entirex.timeout>
Explanation

An invalid value for the entirex.timeout property has been specified.

Action

Use 0 for an infinite timeout or a value of 1 or above for a finite timeout in seconds.

00130318 Socket connect failed: :1:::2: unreachable (:3:)
Explanation

The socket could not be connected to the remote host because the host could not be contacted. This means that some link in the network between the local machine and the remote host is down, or that the host is behind a firewall.

Action

Check your network configuration and status.
00130319 TCP Reply signature (EBCF) not found
Explanation

The data which has been received from the Broker caused an internal inconsistency in the EntireX Java ACI.

Action

Contact Software AG Support.
00130320 Broker HTTP(S) Agent returned Error: :1:
Explanation

Either the Web server or the Broker HTTP(S) Agent returned the indicated error response.

Action

If an HTTP error is returned, the most likely reason is that the Web server or the Broker HTTP(S) Agent is not configured correctly. Otherwise, the connection from the Broker HTTP(S) Agent to the EntireX Broker could have failed.

Note:
Broker HTTP(S) Agent was formerly referred to as "Tunnel Servlet".

00130321 Call to :1: failed: :2:
Explanation

An IOException occurred when calling EntireX via the Broker HTTP(S) Agent.

Action

Check the error message.
00130322 EntireX Broker returned an illegal physical user ID: ":1:"
Explanation

The data which has been received from the broker caused an internal inconsistency in the EntireX Java ACI.

Action

Contact Software AG Support.
00130323 EntireX communication error: :1:
Explanation

Either the EntireX Broker, the Broker Agent, or the Broker HTTP(S) Agent returned an unexpected communication error.

Action

Contact Software AG Support.
00130324 HTTP Server returned response code :1:
Explanation

The HTTP server which serves the request to the EntireX Broker HTTP(S) Agent returned an HTTP response code that is different from HTTP response code 200.

Action

Check the error code and error message. Verify that the URL specified is correct and addresses the Broker HTTP(S) Agent. Verify that both the Web server and the servlet machine are up and running. Access to the Broker HTTP(S) Agent can be also be checked using a Web browser.

00130325 Java Runtime does not support https (:1:)
Explanation

The Java Runtime does not support the HTTPS protocol. HTTPS implementations are available with the Java plug-in and the Java Secure Socket Extension (JSSE).

Action

Check if an HTTPS implementation is installed. Using an HTTPS implementation might require you to set the java.protocol.handler.pkgs system property.

00130326 EntireX Broker returned communicator error: :1:
Explanation

The EntireX Broker returned a low-level communication error. Typical reasons include memory allocation problems in the EntireX Broker.

Action

Check the error message. Additional information might be obtained by checking the log files of the communicator component of the EntireX Broker. See error codes 02150126, 02150128, 02150129. The Broker issued one of these error codes depending on the detailed error text.

00130327 EntireX Broker HTTP(S) Agent returned error: :1:
Explanation

The Broker HTTP(S) Agent returned an error. Typical reasons include unavailability of the EntireX Broker.

Action

Check the error message. Additional information might be obtained by checking the diagnostic output of the Broker HTTP(S) Agent.

00130328 EntireX BrokerAgent returned error: :1:
Explanation

The EntireX Broker Agent returned an error. Typical reasons include unavailability of the EntireX Broker.

Action

Check the error message. Additional information might be obtained by checking the diagnostic output of the Broker Agent.

00130331 Error compressing send data: <detailed description>
Explanation

An exception is thrown while compressing data before send.
Action

Contact Software AG Support with detailed description.
00130332 Error decompressing received data: <detailed description>
Explanation

An exception is thrown while decompressing data after receive or the decompression is incomplete and results in inconsistent data.

Action

Contact Software AG Support with detailed description.
00130333 All sockets in socket pool for <Broker ID> are in use (size: <n> sockets)
Explanation

All sockets in the socket pool for the given Broker ID are in use. n is the maximum number of sockets in this pool.

Action

Check size of socket pool and check connection to the Broker.
00130334 Broker returned <returned number> bytes, more than RETL = <expected number> specifies
Explanation

An internal inconsistency in the response from the EntireX Broker has been detected. The Broker returned a larger payload than expected. <returned number> is the number of bytes in the payload. <expected number> is the number of bytes expected (return length).

Action

Contact Software AG Support.
00130400 Error processing SSL KeyStore or TrustStore: :1:
Explanation

The Java keystore that was specified by the trust_store or key_store parameter is invalid or corrupt.

Action

Check the specified keystore. See also SSL/TLS Parameters for SSL Clients.

00130401 Error during SSL handshake: :1:
Explanation

An SSL exception occurred during the SSL handshake between the SSL client and the SSL server. The most common case is an "untrusted server certificate chain" error.

Action

Check the error message for details. In case of an "untrusted server certificate chain" error, specify using the trust_store parameter a keystore that contains a trusted certificate entry for the issuer of the SSL server's certificate. See also SSL/TLS Parameters for SSL Clients.

00130402 Server certificate issued for ":1:" instead of ":2:"
Explanation

The certificate received from the SSL server contains a common name that is different from the hostname specified in the BrokerID. This is an indication that the SSL client is not communicating with the right SSL server. This error can only appear when verify_server=yes has been specified.

Action

Check that the host name matches the name in the server's certificate. See also SSL/TLS Parameters for SSL Clients.

00130403 Invalid server certificate: :1:
Explanation

The certificate received from the SSL server is syntactically invalid.

Action

Check the server's certificate. See also SSL/TLS Parameters for SSL Clients.

00130404 SSL Transport could not be instantiated: :1:
Explanation

The constructor of the SSL implementation class has thrown an exception.

Action

Check the error message for details.
00130405 SSL Transport could not be loaded: :1:
Explanation

A Java class used by the SSL implementation does not exist.
Action

Check your Java SSL installation.
00130406 SSL Transport class :1: not found
Explanation

The EntireX Java SSL implementation class does not exist.
Action

Check that the named class exists and can be loaded via the classpath.

00130407 SSL Transport class could not be loaded: :1:
Explanation

Something is wrong with the SSL implementation class.
Action

Check that the named class is correct.
00130408 Class :1: is not an SSL Transport class
Explanation

The named class is not recognized by EntireX Java as an SSL transport class.

Action

Check your installation. If the Java system property entirex.ssltransport has been specified, verify that it references an EntireX Java SSL transport class.

00130900 Call rejected, BrokerAgent is shutting down
Explanation

New connections are not accepted by the Broker Agent during shutdown processing.

Action

Restart Broker Agent.
00130901 BrokerAgent: create socket failed: :1:
Explanation

An exception occurred when opening a socket connection to an EntireX Broker.

Action

Check the error message returned from the Java socket class.
00130902 BrokerAgent: read/write failed: :1:
Explanation

An exception occurred during the transfer of data to an EntireX broker through a socket connection.

Action

Check the error message returned from the Java socket class.
00130903 BrokerAgent: unknown :1:::2:
Explanation

The Broker Agent received a request for a Broker ID it is not serving.

Action

Check configuration of the Broker Agent(s).
00130904 BrokerAgent: invalid request format
Explanation

The Broker Agent received a request in an invalid format.
Action

Check the application which is using the Broker Agent. If the problem is reproducible, contact Software AG Support.