Wrong timezone causes TopLink warning in SOA Suite by Cato Aune

From time to time we discovered SOA installations that got this little TopLink warning in the SOA server log every minute:

It happened on some installations, but not on other, and we couldn’t really find any patterns that explained why it did happen on installation A and not on installation B.
After some investigation and with help from Oracle Support, we found that it was a combination of a JDBC bug and that sometimes strange things just happens.

• In the table mediator_containerid_lease, there is a timestamp with timezone column.
• For some strange reason, the JVM believed that the timezone was Atlantic/Jan_Mayen, and used the code for Atlantic/Jan_Mayen in the timestamp with timezone column.
• A bug in the JDBC driver (or some inconsistency between driver versions and DB versions) made method extractTimeZone in TIMESTAMPHelper class get a NULL result instead of the correct timezone.

Solution: Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Facebook Wiki