Technical data

40 BEA WebLogic Integration Release Notes

40 CR080794,

CR081716

Problem

Installation problems occur on Solaris 8 systems which use a JRE installation as the

default Java installation.

Platforms

Solaris 8

Workaround

Perform a full JDK installation as opposed to a JRE-only installation. This can be done

either with an upgrade or a reinstallation of the JDK.

41 CR080836

Problem

Changes to the BPM time services to allow multiple workflow instances to be processed

simultaneously resulted in a change in the parameters to the BPM startup class. The

following error is reported when the server is started:

<Failed to invoke startup class "TimeProcessor",

java.lang.Exception: TimeProcessor startup failed!

Check arguments.>

Platforms

All

Workaround

Update the WebLogic Server configuration files (config.xml) provided in the samples

domain as follows:

The StartupClass node for TimeProcessor should now read:

<StartupClass

Arguments="url=t3://localhost:7001,

user=wlpisystem,pwd=wlpisystem,

connectionFactory=com.bea.wlpi.QueueConnectionFactory,

queue=com.bea.wlpi.Timer"

ClassName="com.bea.wlpi.server.timeprocessor.TimeProcessor"

FailureIsFatal="true"

Name="TimeProcessor" Targets="myserver"/>

The JMS topic Timer must now be a non-persistent queue: