Technical data

Problems Fixed in This Release
BEA WebLogic Integration Release Notes 19
CR067130
Set Task Due Date unreliable under load.
CR067534
Locks are not released after business message is sent.
CR067836
WebLogic Integration 2.1 SP1 does not work with WebLogic Server 6.1 SP1.
CR068192
ebXML plug-in code is not thread safe.
CR068291
Start public workflow actions are not executed when public workflow ends.
CR068326
Workflow cannot be modified because it is suspended.
CR068465
Server crashes after sending repeated messages of 5MB in size.
CR068632
BPM process does not recognize the user-defined exception handler.
CR068879
Parent workflow not resuming execution after subworkflows complete.
CR069009
NullPointerException in
com.bea.wlpi.server.workflow.variable.TypedVariable.setValue.
CR069196
Internationalization changes to data integration required to handle escape sequences
correctly.
CR069270
No means of tracking message status at the sender side when ebXML is used.
The ability to track ebXML message status at the sender side has been added as an option,
as described in the following steps:
1. Define an envelope variable when sending an ebXML message.
2. You can retrieve the messageId of the message from the envelope variable after the
message is sent. For example, given the envelope variable
OurEnv, the messageId can
be retrieved and assigned to a string variable using the following:
ToString(XPath("//Envelope/Header/MessageHeader/
MessageData/MessageId/text()", $OutEnv))
3. You can use the messageId to lookup the Message_History table in the database to find
the status. For example:
Select status from Message_History where
messageId='...' and direction='1'
CR069324
An interoperability error occurs when using WebLogic Integration and Vitria over ebXML.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued)
Change Request
Number
Description