Technical data

30 BEA WebLogic Integration Release Notes
9 CR053242
Problem
The WebLogic Integration Studio does not handle time zones correctly. For example, the
client may send a local date/time string to the server, which then parses the string in its
own time zone. This procedure creates ambiguities when the server and client are in
different time zones.
The following areas are affected:
Any entity associated with a date value expressed as a string in which the time zone is
implicit (for example, workload and statistics queries, and the effective and expiration
dates for a template definition).
Any date/time value that the client rounds up or down (for example, task reroutes and the
effective and expiration dates for a template definition).
Platforms
All
Workaround
Use GMT for all time values when clients and server span multiple time zones.
10 CR055652
Problem
The Application View connection values for initial and maximum cannot be the same
number due to a limitation in WebLogic JCA.
Platforms
All
Workaround
None
11 CR055967
Problem
If you log off from one server and log on to another, the following JMSException is
thrown. The topic session for the notifier is not released during logoff.
The server was unable to complete your request.
JMSException: Connection not found
Start server side stack trace:
weblogic.jms.common.JMSException: Connection not found
Platforms
All
Workaround
None