Release Notes

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

WebLogic Event Server Known Issues

The following sections describe release information about WebLogic Event Server 2.0.

For instructions on installing WebLogic Event Server 2.0, see Installing WebLogic Event Server.

For additional information about the features and capabilities of WebLogic Event Server, see the Getting Started With WebLogic Event Server.


Known Problems

The following section describes problems that were found in WebLogic Event Server 2.0.

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.
JDBC drivers must support the getMetadata feature to work correctly with WebLogic Event Server; 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 WebLogic Event Server in a domain, you must specify a URL because the default value is not valid.
Before starting a WebLogic Event Server 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.


Fixed Problems

The following section describes problems that were found in the Beta version of WebLogic Event Server 2.0 and are now fixed.

Change Request Number
Description and Workaround
Pattern matching in the EPL language is not fully supported.
If an adapter of your application uses the com.bea.wlevs.ede.impl.ActiveAdapter abstract class and an exception occurs during event processing, you may need to restart WebLogic Event Server.
In certain circumstances, executing the undeploy, redeploy, or update commands of the com.bea.wlevs.deployment.Deployer utility may leave WebLogic Event Server in an unconsistent state. If this happens, restart the server.
The SHUTDOWN command of the wlevs.Admin utility may sometimes leave WebLogic Event Server in an inconsistent state.
If you run the load generator on a computer different from the one hosting WebLogic Event Server, and the clock on the load generator computer is "ahead" of the clock on the server computer, the latency values calculated by the loadgen adapter will be negative and the adapter will print a ERROR: high negative time warning message for each packet received.
If the config.xml file that describes your WebLogic Event Server domain contains the <exported-jndi-context> element, you will see the following error when you start the server; this error is harmless and you can safely ignore it:
<May 29, 2007 11:27:37 AM PDT> <Error> <Ede> <BEA-000000>
<unexpected element (uri:"", local:"exported-jndi-context").
Expected elements are
The HelloWorld and FX domains, as well as the template domain under user_projects/domains, include this element and show the error when starting the server.

  Back to Top       Previous  Next