Release Notes

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Oracle Complex Event Processing Known and Resolved Issues

The following sections describe release information about Oracle Complex Event Processing (or Oracle CEP for short) 3.0.

For instructions on installing Oracle CEP 3.0, see Installing Oracle CEP.

For additional information about the features and capabilities of Oracle CEP, see the Oracle CEP Getting Started Guide.


Known Issues

The following section describes known problems in Version 3.0 of Oracle CEP, along with workarounds where possible.

Change Request Number
Description and Workaround
When you start a server in a domain with no deployed applications, the Server STARTED message may not appear in the command window from which you ran the server start script, even though the server has successfully started.


Resolved Issues

The following section describes problems that were found in Oracle CEP 2.0 and are now fixed.

Change Request Number
Description and Workaround
JDBC drivers must support the getMetadata feature to work correctly with Oracle CEP; however, Oracle's thin driver does not fully support this feature.
Packages exported using the MANIFEST.MF's Export-Package entry cannot be redeployed withouth re-starting server.
The <wlevs:instance-property> tag in the EPN assembly file supports only primitive types.
Using the wlevs.Admin GET command with the -property option may return unexpected results.
In order to execute a Java user-defined function in an EPL statement, you must put the Java class in the server’s boot CLASSPATH.
In order to use the wlevs.admin GETRULE command, you must have the administrator role, even though this is a read-only command.
When invoking the stopwlevs.cmd script to stop a running Oracle CEP in a domain, you must specify a URL because the default value is not valid.
Before starting an Oracle CEP instance in the helloworld_domain, you must manually ensure that the wlevs.domain.home variable in the startwlevs.cmd script is set correctly for your particular environment.
If you register an event type with an arbitrary name and then try to look up the event type in the repository based on an instance of the event, the event isn't found and a null value is returned.
If you configure a pass through stream by setting max-size=0 and max-threads=0 in the stream component XML file, then enable monitoring on the stream, and then enable either the average throughput or average latency monitors, both of these monitors will consistently report a metric value of zero even when the stream is under significant load.

  Back to Top       Previous  Next