Known Issues for Event Stream Processor Adapters

Learn about known issues and apply workarounds for adapters supported by Event Stream Processor.

Adapter Issues
CR#	Description
650777	For the Database Input adapter, when data is converted between the database and Event Stream Processor datatypes (numeric) that have different ranges, the JDBC and ODBC drivers may handle these operations differently. For example, the conversion may get rejected or convert into an incorrect value, and so on.
680661	The Platform Input and Platform Output adapters are not supported by Event Stream Processor. The platform_in.cnxml and platform_out.cnxml files are included in the install, but are for internal use only.
684922 and 684945	When running the Reuters OMM adapter in interactive publish mode, you may experience intermittent stability issues when connected directly to rmdstestclient (a Reuters utility bundled with their server).
695586	When using the Database Input adapter and the getData() built-in SPLASH function in the flex stream, there is a compatibility issue between JDK7 and the JDBC driver for MSSQL (3.0.1301.101 and 4.0 CTP3). The problem occurs when mapping a `datetime2` datatype into Event Stream Processor `timestamp` or `string` datatypes as the adapter executes queries such as a SELECT statement. The value that is read in is incorrect. To work around this issue, use the SQL convert() built-in function to cast a `datetime2` column into a `varchar`. For example, modify a SELECT statement like this: select c_bigdatetime from newalltypes into this: select convert(varchar(30), c_bigdatetime, 121) from newalltypes where the third argument value of 121 is the format to which the `datetime2` field will be converted.
714685	You must make a few changes so that Java external adapters from Event Stream Processor 5.0 are compatible with ones from 5.1. For all Java external adapters, due to changes in authentication types between versions, you can use only LDAP, RSA, or Kerberos (not ticket) authentication types if you want compatibility between 5.0 and 5.1 adapters. To make the 5.0 external FIX Input adapter compatible with the 5.1 version, add the maxPubPoolSize parameter to the 5.0 file connectors configuration files. This property was optional in 5.0 but is required in 5.1. If you want to start the 5.0 external FIX Input adapter with the 5.1 configuration file, remove the inputBuffer property from the 5.1 configuration file as this property is not valid in 5.0.
715027	A custom internal adapter that was written using the 5.1 version of the GenericAdapterInterface.h file is not compatible with an adapter that was written using the 5.0 version. To make these adapters compatible in 5.0, change the following function signatures for these files to the 5.1 version: change `int getTotalRowsProcessed(void)` to `int64_t getTotalRowsProcessed(void)` change `int getNumberOfBadRows(void)` to `int64_t getNumberOfBadRows(void)` change `int getNumberOfGoodRows(void)` to `int64_t getNumberOfGoodRows(void)`
715811	When the peer program publishing to the adapter does not close its socket connection cleanly the adapter's state becomes DEAD and it no longer accepts connections. To avoid this issue, ensure that the publisher issues a "close" on the socket connection before exiting.
716339	The CSV Input adapter does not process the last line of the CSV input file. To ensure that all data in the file is processed, add an empty line at the end of the file.
716843	If you stop the Database Input adapter while it is reading data and then start it again, the adapter does not start and therefore, does not complete reading data. To work around this issue, restart the ESP Server, and if you did not configure the adapters to start automatically, then manually start the Database Input adapter.
716844	If you drop the table that the Database Input adapter is polling data against, the adapter crashes. To work around this issue, restart the ESP Server, and if you did not configure the adapters to start automatically, then manually start the Database Input adapter.
721462	If ESP bigdatetime is mapped to timestamp in HANA, deletes or updates are processed in ESP, but not in HANA. This is due to an issue in HANA where the timestamp data type truncates microseconds to milliseconds. Because the original, non-truncated value is not found in the database, the delete or update fails. To work around this, if you insert data into HANA through the HANA adapter, issue deletes or updates outside of the adapter. When constructing your delete or update statements, use millisecond precision.
730001	When using schema discovery for the SAP HANA Output adapter, no schema is discovered if you specify a table name prefixed by its schema name. Also, if you have the same table name appearing under multiple schemas in your target SAP HANA database, schema discovery returns incorrect columns.
734677	If you use schema discovery in Studio to discover BW queries for the SAP RFC Input Adapter, the resulting schema is missing the “cell_value” column. To work around this issue, add the “cell_value” column with the datatype `string` to the resulting schema. For example: CREATE INPUT STREAM InputWindow1 SCHEMA (z_city STRING , z_sales STRING , measures STRING , cell_value string ) ;
736319	If you use schema discovery to create a stream or a window, and then use schema discovery again to assign schema to the connected stream or window, the column names in the resulting schema are incorrect. This issue affects all adapters that support schema discovery. To work around this issue, manually edit the schema.
736995	When using the Web Services (SOAP) Input and Output adapter, if the return values or parameters of a Web service contain a datatype derived from an ABAP `decimal` datatype, the Axis2 framework throws a RuntimeException error message. To work around this issue, convert any ABAP `decimal` datatypes to `string` datatypes, and use `string` datatypes instead of `decimal` datatypes to define a Web service interface.
737158	If the Web server for the Web Services (SOAP) adapter is using X.509 authentication, it requires four specific properties and the adapter_config.xml file does not accept two of these properties ( `javax.net.ssl.keyStore` and `javax.net.ssl.keyStorePassword`). To work around this issue, add `-Djavax.net.ssl.keyStore=$ESP_ADAPTER_HOME/bin/wsclient.jks` and `-Djavax.net.ssl.keyStorePassword=password` to the last command line of the adapter.sh file. For example: $JDK_HOME/bin/java" $ADAPTER_JAVA_FLAG "-Duser.dir=$ESP_ADAPTER_HOME/config" "-Djavax.net.ssl.keyStore=$ESP_ADAPTER_HOME/bin/wsclient.jks" "-Djavax.net.ssl.keyStorePassword=password" -cp "$ADAPTER_CLASSPATH" $ADAPTER_CLASS "$ADAPTER_CONFIG_FILE" $ADAPTER_COMMAND