Technical support issues, reports, and comments.
We are currently putting the finishing touches on Auto-Tune R1.6. When it is released, we will give you one month of free time and updates so that you can enjoy trying the new C++ capabilities.
Biggest news in this release? Dynamic SQL support for C and C++. You will be able to scan some of your strings for SQL statements and get plans without having to cut and paste into mxci.
We are sorry to say that the test.reconciler plug-in has been removed from the Juno update site for compatibility reasons in the underlying ECLIPSE Compare infrastructure. It is still available in Indigo but will be discontinued when that site is deprecated June 2015. If you have issues with that, please contact us.
Auto-Tune R1.5 is now available. We have created a new and improved Java parser for SQL/MX statements that works with the native ECLIPSE facilities. The parser is available as a separate plug-in under JDT Connectors on the update site. Users can also run SQL statements from existing code. Parameters are managed for you and preserved as part of the plan history data. We have a limited, but representative set of supported data types – Please let us know ASAP if you need one that is not supported, via our Contact form or in a comment here.
ECLIPSE Mars is coming fast, and you know what that means. Juno will become the lowest level of support. Our plan is to certify our products on Mars and then drop the Helios and Indigo sites around 25 June 2015 to coincide with the aging off of those two ECLIPSE releases. NSDEE 4.0 will also become the oldest support level at the same time. Please let us know ASAP if this presents a problem – we have no plans to age off the repository branches for those releases at this time.
Welcome to 2015! Release 1.4 of the SQL/MX Auto-Tune plug-in has come out of our build machine and is now on the update site. We had to make a significant change to the plug-in extension point for this release, but since there are no production extenders, at this point anyway, the impact should be minimal. Please let us know if this is an issue and we can provide a backward compatible version. Note: We normally do not make incompatible interface changes, but this was a functional omission that needed to be corrected.
Connection sharing and profile management are significantly improved with this release and people are encouraged to upgrade.
Eclipse NSDEE build works the first time after a clean then fails with error ‘target pattern contains no ‘%’
Cause: The installed version of make does not support file names of the form C:\… in a dependency file (.d)
Effect: the build fails with the above error
Recovery: Check the version of cygwin make by opening the cygwin terminal and enter the command ‘make —version’ , if the version is between 3.8.1 and 4.0 Install version 3.8.0 of make.exe in cygwin/bin directory from http://geant4.slac.stanford.edu/installation/extras/cygwin/make.exe
Not all browsers will let you download an executable.
The ECLIPSE Indigo Update Site is now officially commissioned. Please use this for all plug-in downloads except for Helios installations.
The update site is at https://www.nexbridge.com/Eclipse/Indigo.
A good bit of news is that we have just done testing with the ECLIPSE standard download with Kelper-RC1 (4.3.1). The problem seems to have been resolved with this release.
See Installing Plug-ins Under Juno for details.
Well, we hoped this one would go away, but even with the latest (JDK 1.7.0_51 as of today), the problem we saw with Indigo and Java 1.7 still exists. This problem results from the way Oracle modified Array.sort() in a threading environment. Unfortunately, as of the day I posted this, the NSDEE 4.0 installation instructions did not include a discussion of how to deal with this problem. You will find a discussion of what the ECLIPSE contributors have done relating to this problem here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=317785.
The problem was further diagnosed as being: https://bugs.eclipse.org/bugs/show_bug.cgi?id=297805 with regards to Mirror Ranking.
So far, we have found two temporary solutions:
config.ini file found in the ECLIPSE configuration directory (eclipse/configuration/config.ini) and add the following parameter:
-Djava.util.Arrays.useLegacyMergeSort=true
This is of particular importance to NSDEE 2.x, NSDEE 3.x, and NSDEE 4.x users that have a large number of dependencies to ECLIPSE CDT components installed in a combination of remote update sites and local archives.
The problem has been either not been resolved for ECLIPSE 3.7.1 and above or was reintroduced. See the Indigo post for the original support note.
As many of you may know, ECLIPSE 3.7 has been out for a while now. So has Java 7. What you may not know is that there is a problem with the ECLIPSE installer in 3.6 and 3.7.0 relating to Java 7. What happened is that Oracle made a change to Array.sort() in Java 7 that changes the way sort() works in a threading environment. You will find a discussion of what the ECLIPSE contributors have done relating to this problem here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=317785.
The problem was further diagnosed as being: https://bugs.eclipse.org/bugs/show_bug.cgi?id=297805 with regards to Mirror Ranking.
So far, we have found two temporary solutions:
config.ini file found in the ECLIPSE configuration directory (eclipse/configuration/config.ini) to add the following parameter:
-Djava.util.Arrays.useLegacyMergeSort=true
This is of particular importance to NSDEE 2.x users who are limited to ECLIPSE 3.6.x with CDT 5.0.0. If you an NSDEE user, we suggest that you stay on Java 6 until you move to NSDEE 3.0 or NSDEE 4.0. [Note: this comment is obsolete]
The problem has been resolved for ECLIPSE 3.7.1. What we don’t know is whether there are any compatibility issues with NSDEE 3.0 and Java 7, although it is unlikely. The fix #1 above should work if there continues to be an issue after ECLIPSE 3.7.1. [Note: this comment is obsolete.]
Updated 21 Jan 2014: The problem continues to exist or has been reintroduced in Juno/Java 1.7.0_51 and has caused some items in this support note to be made obsolete.
Updated 20 Feb 2014: The problem with the installer appears to have been resolved under Kepler. See the updated support note for details.
Updated 25 Feb 2014: Not everyone may see this problem. The issue relates to threading, and is, as a result, timing sensitive.