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.
672121

When running on a logical domain (LDOM), the FIX, NYSE Technologies, and Open adapters may fail to start and indicate a licensing error.

Have your authorized representative contact Sybase Customer Service and Support (CS&S) and be prepared to provide this information:

  1. Output of sysamcap default -v on the control domain.
  2. Output of cpuinfo -v on the LDOM.
  3. Output of hostid on the LDOM.
710425

If you start the ESP Server through C shell and then run the Sybase IQ Output adapter, you may encounter issues with the DB connection due to LD_LIBRARY_PATH_64 not being set correctly in the $IQDIR15/IQ-15_4.csh file.

To correct this issue, run the command
set LD_LIBRARY_PATH_64 $LD_LIBRARY_PATH_64/$IQDIR15/lib64:$IQdir15/../OCS-15_0/lib:$IQdir15/../OCS-15_0/lib3p64:$IQdir15/../OCS-15_0/lib3p:
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.
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.
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
748713

For the Socket JSON Input Adapter, the jsonRootpath parameter in the cnxml file is marked as required. The jsonRootpath is not required for the Socket JSON Output Adapter, which makes the two formats incompatible.

To work around this issue:
  1. Edit toolkit_file_json_input.cnxml and change this parameter to optional as follows: 
    <Parameter id="jsonRootpath"
  label="JSON Root Path"
  descr="Specify a rootpath for the JSON data."
  type="string"
  use="optional"
  />
  2. Go to $ESP_HOME/adapters/framework/instances/file_json_input/adapter_config.xml and delete the word entities from the rootPath parameter in the adapter_config.xml file so it looks like:
    <Module type="formatter">
	<InstanceName>MyJsonInFormatter</InstanceName>
	<Name>JsonStringToEspFormatter</Name>
	<Next>MyInStream_Publisher</Next>
	<Parameters>
		<JsonStringToEspFormatterParameters>
			<DateFormat>yyyy-MM-dd HH:mm:ss.SSS</DateFormat>
			<TimestampFormat>yyyy/MM/dd HH:mm:ss</TimestampFormat>
			<ColumnMappings>
				<ColsMapping streamname="" rootpath="">
					<Column>display_text</Column>
					<Column>domain_role</Column>
					<Column>offset</Column>
					<Column>length</Column>
				</ColsMapping>
			</ColumnMappings>
		</JsonStringToEspFormatterParameters>
	</Parameters>
</Module>
748988

For the File/Hadoop CSV Output Adapter, the adapter_config.xml file in $ESP_HOME/adapters/framework/instances/file_csv_output is mislabeled as file_xmllist_output.

Therefore, to see statistics for this adapter when working with the _ESP_Adapter_Statistics metadata stream, look for an adapter with type file_xmllist_output.
749269

If your web page cannot read JSON data created by ESP using the File JSON Output Adapter, you need to manually modify each file created by ESP into a format that your web page can read.
750281

The Adapter Toolkit Blacklist prevents valid projects from running if the command to be executed by the adapter contains any of the following strings: "mv ", " rm ", "del ", "rm ".
Parent topic: Known Issues