Technical data

Problems Fixed in This Release
BEA WebLogic Integration Release Notes 23
CR075098
Memory leak occurs when a transaction is rolled back when using the ebXML protocol.
An ErrorQListenerBean message-driven bean (MDB) was added that deletes the message
store when retries on the eventQueue fail.
If you are using ebXML and you make the MDB transactional so that dequeuing from
eventQueue happens in the same transaction as the rest of the BPM processing, you must
perform certain tasks to ensure that memory cleanup is performed. To perform the cleanup,
an MDB with destination-jndi-name, com.bea.b2b.ErrorQueue has been
added to
ebxml-bpm-plugin.jar. This bean cleans the internal memory structures and
discards the message that was not processed successfully. Edit config.xml as follows to use
this MDB:
1. Specify an error queue with the correct JNDI name, for example:
<JMSQueue JNDIName="com.bea.b2b.ErrorQueue"
Name="B2bErrorQueue"/>
2. Specify the new error queue as the error destination for eventQueue, for example:
<JMSQueue ErrorDestination="B2bErrorQueue"
JNDIName="com.bea.wlpi.EventQueue" Name="eventQueue"
RedeliveryDelayOverride="10000" RedeliveryLimit="2"/>
Specify appropriate values for RedeliveryDelayOverride and
RedeliveryLimit
CR075425
Missing API for full export of WLI.
CR075427
Problem with XML Schema.
CR075432
Test framework Helper.waitForCompletedInstance() is broken. A memory leak
occurs.
CR075797
A memory leak occurs when using ebXML.
CR076261
Delayed reply message causes new workflow to start.
CR076401
Carriage return character is stripped out from response.
CR076512
SQL exceptions with Sybase database.
CR076554
RosettaNet test failed because templates were not marked active.
Table 2. Problems Fixed in BEA WebLogic Integration 2.1 SP2 (Continued)
Change Request
Number
Description