As you may know already @tcoates, the issue has been fixed as part of issue JCBC-1007, which is currently expected to be fixed in the Java 2.3.4 SDK update, assuming testing goes well.
As you may know already @tcoates, the issue has been fixed as part of issue JCBC-1007, which is currently expected to be fixed in the Java 2.3.4 SDK update, assuming testing goes well.