Table 3-1 Problems Fixed in BEA WebLogic Integration 9.2 MP3
|
|
|
|
|
After a graceful shutdown and restart, the parent process used to remain in a running state in the Process Monitoring Console. This problem occurred because internal response messages between parent and child processes were missing.
This problem has been resolved.
|
|
|
The build.xml file, generated by the Eclipse IDE, used to fail because all the fields were not marshalled properly at application build time.
This problem has been resolved.
|
|
|
Prior version was getting triggered when a message was published to a message broker channel on which the active process version was listening.
This problem has been resolved.
|
|
|
In a debug mode, an AssertionError was returned when a WLI Java Message Service (JMS) Control was used through a Java Custom Control.
This problem has been resolved.
|
|
|
When creating an RDBMS Event Generator, an incomplete list of queue connection factories was displayed if a DNS name was used as the listen address of the domain.
This problem has been resolved.
|
|
|
When creating new tasks by using the worklist portal or the RemoteWorklistTaskAdminBean from a Java client, the task creation was not using the default settings for Description, Owner, Task Time Estimate and Task Completion Due Date specified in the Task Plan.
This problem has been resolved.
|
|
|
Incorrect method signature was being displayed for CustomCallback. The eventSet was referring to TaskControl.Callback.class instead of TaskControl.CustomCallback.class.
This problem has been resolved.
|
|
|
When publishing a WebLogic Integration application to the server, the application takes a long time to deploy.
This problem has been resolved.
|
|
|
WebLogic Workshop IDE was taking a long time to open JPD files and other WebLogic Integration artifacts.
This problem has been resolved.
|
|
|
When using WebLogic Integration 9.2 MP2 Event Generator for DB2, an invalid SQL statement used to return COM.ibm.db2.jdbc.DB2Exception.
This problem has been resolved.
|
|
|
Creation of JPD proxies by using JpdProxyTask used to fail with FileNotFoundException if the JPD package name contained "jpd".
This problem has been resolved.
|
|
|
Timeout for HTTP control socket (HTTP Control method setTimeout(timeInMillis)) did not work.
This problem has been resolved.
|
|
|
When the same Dynamic Transformation control was called within two different transactions, the second transaction used to fail.
This problem has been resolved.
|
|
|
Applications were attempting to reuse an ebXML control within the same conversation and use the JPD to send several ebXML messages in a row.
This problem has been resolved.
|
|
|
The exception 'java.lang.RuntimeException: Protocol 'http-soap' not available on this operation' used to be returned when a JPD was called. This used to occur in a setup with a JPD and a web service control calling the web services method.
This problem has been resolved.
|
|
|
RDBMSConnMDB.markPolledRows() was being overwritten by DB2ConnMDB and this caused preparedStatement.setObject to receive an incorrect parameter.
This problem has been resolved.
|
|
|
Length of WebLogic Integration message ID of the ebXML message was more than the permitted maximum length (128 bytes).
This problem has been resolved.
|
|
|
When a WebLogic Server EJB client was attempting to retrieve Task data using the Worklist API, the getTask(<taskid>, <boolean (true)>) method used to fail with unmarshall exception.
This problem has been resolved.
|
|
|
When a JMS client program sent a message to the queue, the message was received by the new process version of JPD and used to fail with an error message, even though the message had the correlation ID as the process instance ID of the older process version.
This problem has been resolved.
|
|
|
The T3S protocol could not be used as the domain-wide administration protocol to secure clusters because the DomainMbean.AdministrationProtocol value was not being used to set the defProtocol value.
This problem has been resolved.
|
|
|
When undeploying an application in a WebLogic Integration cluster environment, the DescriptorUpdateFailedException used to be returned.
This problem has been resolved.
|
|
|
After using a JPD to create an array of Java objects and transform them into an XML document, the Java object was not being released. This problem occurred due to memory leaks during the transformation.
This problem has been resolved.
|
|
|
When a custom control has the same method name as in the JMS Control but a different number of arguments, java.lang.ArrayIndexOutOfBoundsException used to be returned. This problem occurred because the control container was retrieving the number of arguments from the base control method and not the extended method.
This problem has been resolved.
|
|
|
Annotation overriding was not working for the control target endpoint of the web service.
This problem has been resolved.
|
|
|
Worklist Tasks could not be created when the Admin Server was shut down. This problem occurred because, to post the task event to any listener, the JMX used to retrieve the Worklist event JMS destination from the Admin Server instead of using the MBeans of the local managed server.
This problem has been resolved.
|
|
|
The query for completed 8.1.x compatible tasks was incorrectly looking for a current Step Name of completed, instead of the Administrative State of Completed.
This problem has been resolved.
|
