TM 2.0 Known Issues and Workarounds
This page lists the most obvious known issues with TM 2.0 and suggests workarounds. By "most obvious" we mean those issues that many users are likely to encounter. Note that there may be other severe or critical issues not listed here, because they are less likely to occur. See the Bugzilla: TM Major and Critical, P1 and P2 query to show those.
We encourage you to enable Wiki Watch for this page: ensure that you are logged on to the Wiki, then click the little 'watch' tab on top of this page. On your personal "preferences" page (accessible from the top right of your screen) you can also enable E-Mail notifications for changes on this page. This will allow you to get notified when other users find important problems that you might be able to work around.
This is a collaborative page: Every user may edit this page and add bugs he or she has filed, that are very obivious or problematic and that he or she'd like other users to be able to work around to avoid. See the TM Bug Process Page
for queries to get the full list of known bugs out of bugzilla.
Known Problems in TM 2.0
Critical bugs 192741 and 194204 were found in TM 2.0 and fixed in the TM 188.8.131.52 patch release. These could lead to loss of data. All TM / RSE 2.0 Users are encouraged to update. See the TM 184.108.40.206 blog and "Issues Fixed", below, for details.
|(query)||Problems with EFS Integration||Several problems have been reported with the RSE EFS integration, see the bugzilla query (left) for a full list. Some of these issues appear critical, like hanging Eclipse when refreshing a remote folder linked in to a JDT tree; but in many cases we think that the problem is not with the TM/RSE EFS provider but with the clients not being prepared for remote resources through EFS properly. We will continue looking at EFS issues with high priority, and at the same time we encourage all projects to be aware that resources in the workspace are not necessarily fast to access, in the case they actually reside on a remote computer linked in through EFS.|
|181458||Cannot drag&drop / copy&paste from remote to Windows Explorer||We had to take out the "Download on Copy" workaround again because of critical bug 189268. A proper fix will need a fix in SWT. Workaround: Copy&Paste to the RSE "Local" file system instead.|
|153652||Cannot drag&drop from remote into the Project Explorer||We had to take out the "Download on Copy" workaround again because of critical bug 189268. A proper fix will need support for the "PluginTransfer" method in the Project Explorer. Workaround: Open the Resource Navigator in a separate view, then drag&drop to the Resource Navigator instead.|
|190803||Some long-running dstore commands cannot be canceled||When a "list directory" query is extremely slow because of e.g. missing mounted file systems, the dstore server gets unresponsive because it is single-threaded for "list" type queries. Other queries are multi-threaded, so fixing this in the future should not be too hard. Unfortunately, when the client cancels the operation further access to the hanging dstore server may block the UI. Workaround: When a dstore connection hangs, cancel the job in the progress view, then disconnect and reconnect the hanging connection. This will restart the dstore server.|
|179937||(BIDI) File and Path names in files tree do not honor encoding||On dstore, launch the server with proper encoding parameter. Multiple servers may be needed for multiple different encodings on the same host. The host-wide encoding control has been added to RSE but it is not yet functional for file and path names. This will be added as a bug fix in RSE 2.0.1.|
Issues fixed in recent milestones
|Bug #||Fixed in||Description|
||TM 220.127.116.11 / I20070705-0600|| Moving a folder from a ZIP archive fails if > 1 level deep - this could mean loss of data.
A patch is provided with TM 18.104.22.168. See the TM 22.214.171.124 blog for details.
||TM 126.96.36.199 / I20070705-0600||RSE FTP: Renaming Files/Folders moves them sometimes - this could mean loss of data. A patch is provided with TM 188.8.131.52. See the TM 184.108.40.206 blog for details.|