WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sample error log
Code Block
[2017-07-10 18:20:13,226] ERROR {org.wso2.carbon.event.processor.admin.EventProcessorAdminService} -  Exception when validating execution plan
org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException: test does not exist in type WindowProcessor in execution plan "SensorDataAnalysis-SensorAnalytics-ssss-realtime1"

[2017-07-10 18:21:55,142] ERROR {org.wso2.carbon.event.processor.admin.EventProcessorAdminService} -  Exception when validating execution plan
org.wso2.carbon.event.processor.core.exception.ExecutionPlanConfigurationException: 'test' is neither a function extension nor an aggregated attribute extension in execution plan "SensorDataAnalysis-SensorAnalytics-ssss-realtime1".
OccurrenceThis occurs when you implement a new extension in WSO2 DAS CEP and try to use it.
Possible reasonsThe custom extension is not properly loaded into the system.
Troubleshooting Options
  • Check whether the extension jar is added to the <DAS<CEP_HOME>/repository/component/dropins directory.
  • Check whether the .siddhiext file is bundled inside the jar. This file is used to get the extension namespace and name that are used to refer to the extension. The file name is used as the extension namespace, and the identifier inside the name is used as the extension name.
  • If both the requirements mentioned above are met, start the server with the -DosgiConsole argument, and check the bundle status. The bundle can be searched via the ss command, and the status can be queried via the diag command.

...