PageRenderTime 164ms CodeModel.GetById 42ms RepoModel.GetById 11ms app.codeStats 0ms

/plugins/com.aptana.ide.documentation/html/gettingstarted/Troubleshooting_Aptana_Studio_Issues.html

https://github.com/hotrhino/ide_core
HTML | 164 lines | 155 code | 6 blank | 3 comment | 0 complexity | ecc3c4d160d7003f4a0acd37dce44049 MD5 | raw file
    

  1. <html>
    2. 

  2.    <head>
    3. 

  3.       <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    4. 

  4.       <title>Troubleshooting Aptana Studio Issues</title>
    5. 

  5.       <link rel="stylesheet" href="../../content/shared.css" type="text/css">
    6. 

  6. 	  <!--<script type="text/javascript" src="http://www.aptana.com/docs/help.js"></script>-->
    7. 

  7. 	  <!--<script type="text/javascript" src="http://www.aptana.com/docs/index.php?title=Troubleshooting_Aptana_Studio_Issues&action=raw&gen=js">-->
    8. 

  8. 	  <link rel="stylesheet" href="http://www.aptana.com/docs/" type="text/css">      
    9. 

  9. 	  	<script>
    10. 

  10. 	  var lastModifiedClient = "";
    11. 

  11. 	  var fullUrl = "";
    12. 

  12. 	  try
    13. 

  13. 	  {
    14. 

  14. 	     if(lastModifiedServer)
    15. 

  15. 	        notifyUpdatedSource(lastModifiedClient, lastModifiedServer, fullUrl);
    16. 

  16. 	  }
    17. 

  17. 	  catch(e) {}	  
    18. 

  18. 	</script>
    19. 

  19. 	
    20. 

  20.    </head>
    21. 

  21.    <body>
    22. 

  22.       <div class="classBlock">		    <a href="http://www.aptana.com/" target="_blank"><img src="../../content/aptana.gif" border="0" hspace="21" vspace="7"></img></a><h1>Troubleshooting Aptana Studio Issues [<a href="http://www.aptana.com/docs/index.php?title=Troubleshooting_Aptana_Studio_Issues&action=edit">edit</a>]</h1>
    23. 

  23.          <div class="content">
    24. 

  24.             
    25. 

  25. 					<p>If the answers here don't fix the problem for you, please <a href="http://support.aptana.com/asap" class="external text" title="http://support.aptana.com/asap" rel="nofollow">file a support request in ASAP</a>--your bug reports help us improve Aptana Studio and our other offerings.
    26. 

  26. </p><p>You can get directly to ASAP from the Help menu in Aptana Studio by choosing Submit Aptana Bug or Feedback from the Aptana Troubleshooting submenu.
    27. 

  27. </p>
    28. 

  28. <table id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Contents</h2></div>
    29. 

  29. <ul>
    30. 

  30. <li class="toclevel-1"><a href="#Accessing_the_Error_Log"><span class="tocnumber">1</span> <span class="toctext">Accessing the Error Log</span></a>
    31. 

  31. <ul>
    32. 

  32. <li class="toclevel-2"><a href="#Accessing_the_log_from_Studio.2FEclipse"><span class="tocnumber">1.1</span> <span class="toctext">Accessing the log from Studio/Eclipse</span></a></li>
    33. 

  33. <li class="toclevel-2"><a href="#Accessing_the_log_manually"><span class="tocnumber">1.2</span> <span class="toctext">Accessing the log manually</span></a></li>
    34. 

  34. </ul>
    35. 

  35. </li>
    36. 

  36. <li class="toclevel-1"><a href="#After_a_crash.2C_the_splash_screen_appears_briefly_and_disappears"><span class="tocnumber">2</span> <span class="toctext">After a crash, the splash screen appears briefly and disappears</span></a></li>
    37. 

  37. <li class="toclevel-1"><a href="#How_do_I_install_Studio_updates.2C_with_error:_Network_connection_problems_encountered_during_search.3F"><span class="tocnumber">3</span> <span class="toctext">How do I install Studio updates, with error: Network connection problems encountered during search?</span></a></li>
    38. 

  38. <li class="toclevel-1"><a href="#Can_I_request_a_new_or_changed_feature.3F"><span class="tocnumber">4</span> <span class="toctext">Can I request a new or changed feature?</span></a></li>
    39. 

  39. <li class="toclevel-1"><a href="#JVM_Terminated"><span class="tocnumber">5</span> <span class="toctext">JVM Terminated</span></a></li>
    40. 

  40. <li class="toclevel-1"><a href="#Using_the_Aptana_Studio_Console"><span class="tocnumber">6</span> <span class="toctext">Using the Aptana Studio Console</span></a></li>
    41. 

  41. <li class="toclevel-1"><a href="#How_do_I_repair_my_Aptana_Studio_installation.3F"><span class="tocnumber">7</span> <span class="toctext">How do I repair my Aptana Studio installation?</span></a></li>
    42. 

  42. <li class="toclevel-1"><a href="#How_do_I_stop_Studio_from_loading_a_problem_file.3F"><span class="tocnumber">8</span> <span class="toctext">How do I stop Studio from loading a problem file?</span></a></li>
    43. 

  43. <li class="toclevel-1"><a href="#Tips_for_Getting_Better_Results_from_Bug_and_Feature_Request_Tickets"><span class="tocnumber">9</span> <span class="toctext">Tips for Getting Better Results from Bug and Feature Request Tickets</span></a></li>
    44. 

  44. </ul>
    45. 

  45. </td></tr></table><script type="text/javascript"> if (window.showTocToggle) { var tocShowText = "show"; var tocHideText = "hide"; showTocToggle(); } </script>
    46. 

  46. <a name="Accessing_the_Error_Log"></a><h2> <span class="mw-headline">Accessing the Error Log </span></h2>
    47. 

  47. <p>The Aptana .log file records most application exceptions that occur while you are using the Aptana application. The .log file can be helpful to the Aptana development team in troubleshooting bugs that you may encounter during normal usage. You can access your log either through the Help menu in Aptana or manually through the file system on your computer.
    48. 

  48. </p>
    49. 

  49. <a name="Accessing_the_log_from_Studio.2FEclipse"></a><h3> <span class="mw-headline">Accessing the log from Studio/Eclipse</span></h3>
    50. 

  50. <p>The Aptana Troubleshooting menu on the Studio/Eclipse Help menu has an option to view the log file. Choosing it opens the log in an editor window, which you can save to a separate file in order to attach it to an ASAP ticket.
    51. 

  51. </p>
    52. 

  52. <a name="Accessing_the_log_manually"></a><h3> <span class="mw-headline">Accessing the log manually</span></h3>
    53. 

  53. <p>Your current .log file is located in a <b>.metadata</b> folder in your current <b>workspace</b> directory.
    54. 

  54. </p>
    55. 

  55. <ul><li> Windows XP: C:\Documents and Settings\username\aptana\workspace\.metadata\.log
    56. 

  56. </li><li> Windows Vista: C:\Users\username\Documents\Aptana Studio\.metadata\.log
    57. 

  57. </li><li> Mac OS X: ~/aptana/workspace/.metadata/.log  (this is often in the folder for your username)
    58. 

  58. </li><li> Linux: ~/aptana/workspace/.metadata/.log
    59. 

  59. </li></ul>
    60. 

  60. <p>If you changed your workspace from the default location (see <a href="Switching_your_workspace.html" title="Switching your workspace">Switching your workspace</a>), the .log file will be in a <b>.metadata</b> directory in your <b>workspace</b> directory.
    61. 

  61. </p>
    62. 

  62. <a name="After_a_crash.2C_the_splash_screen_appears_briefly_and_disappears"></a><h2> <span class="mw-headline">After a crash, the splash screen appears briefly and disappears</span></h2>
    63. 

  63. <p>We've seen this issue periodically with Windows users. If you experience this issue, try the following workaround:
    64. 

  64. </p>
    65. 

  65. <ol><li> Navigate to the folder where you have Aptana Studio installed (usually under C:\ Program Files), and find the jre folder
    66. 

  66. </li><li> Rename the jre folder to jre.old
    67. 

  67. </li><li> If you have another instance of the latest JRE installed on your machine, skip to the last step
    68. 

  68. </li><li> Download and install a new instance of the JRE from <a href="http://www.java.com/en/download/index.jsp" class="external text" title="http://www.java.com/en/download/index.jsp" rel="nofollow">Sun</a>
    69. 

  69. </li><li> Start Aptana Studio.
    70. 

  70. </li></ol>
    71. 

  71. <a name="How_do_I_install_Studio_updates.2C_with_error:_Network_connection_problems_encountered_during_search.3F"></a><h2> <span class="mw-headline">How do I install Studio updates, with error: Network connection problems encountered during search?</span></h2>
    72. 

  72. <p>Follow the instructions at the <a href="https://pro.aptana.com/install/pro/3.2/" class="external text" title="https://pro.aptana.com/install/pro/3.2/" rel="nofollow">Aptana Studio Update Site</a>.
    73. 

  73. </p>
    74. 

  74. <a name="Can_I_request_a_new_or_changed_feature.3F"></a><h2> <span class="mw-headline">Can I request a new or changed feature?</span></h2>
    75. 

  75. <p>Absolutely! This helps us plan and prioritize features to include in upcoming product releases. To let us know what you want <a href="http://support.aptana.com/asap" class="external text" title="http://support.aptana.com/asap" rel="nofollow">open an enhancement request ticket for the appropriate product in ASAP</a>
    76. 

  76. </p>
    77. 

  77. <a name="JVM_Terminated"></a><h2> <span class="mw-headline"> JVM Terminated </span></h2>
    78. 

  78. <p>When this happens, you'll see a rectangular dialog with a title of <i>JVM Terminated</i> on your screen and Aptana Studio will disappear. This indicates Java itself has crashed but it creates a log file in the process.
    79. 

  79. </p><p>By default, the crash file should be in either the Aptana Studio program directory, or in the system temp directory, most likely with an extension of *.hs. If you still cannot locate it, follow the directions here:
    80. 

  80. </p>
    81. 

  81. <ul><li> <a href="http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/felog.html#felog" class="external text" title="http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/felog.html#felog" rel="nofollow">Finding your Error Log</a>
    82. 

  82. </li><li> On the Macintosh, the location is ~/Library/Logs/Java/*.crash.log or ~/Library/Logs/CrashReporter and the file will have the word <i>java</i> in its name.
    83. 

  83. </li></ul>
    84. 

  84. <p>You can also find some more troubleshooting ideas here:
    85. 

  85. </p>
    86. 

  86. <ul><li> <a href="http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/crashes.html" class="external text" title="http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/crashes.html" rel="nofollow">Troubleshooting System Crashes</a>
    87. 

  87. </li></ul>
    88. 

  88. <p>Please attach this log if you submit a ticket in <a href="http://support.aptana.com/asap/secure/Dashboard.jspa" class="external text" title="http://support.aptana.com/asap/secure/Dashboard.jspa" rel="nofollow">ASAP</a>.
    89. 

  89. </p>
    90. 

  90. <a name="Using_the_Aptana_Studio_Console"></a><h2> <span class="mw-headline">Using the Aptana Studio Console </span></h2>
    91. 

  91. <p>If Aptana does not appear to work properly, you can try and use the console to figure out what is happening.
    92. 

  92. </p>
    93. 

  93. <ol><li> Add -console to the launch arguments for Aptana or Eclipse
    94. 

  94. <ol><li> On Windows, you can create a shortcut and add that to the shortcut properties.
    95. 

  95. </li><li> On OS X, follow these instructions:
    96. 

  96. <ol><li> Navigate to the /Applications/Aptana Studio folder in Finder.
    97. 

  97. </li><li> Right-click (or control-click) on AptanaStudio.app and choose <i>Show package contents</i>.
    98. 

  98. </li><li> In the new Finder window navigate to Contents/MacOS.
    99. 

  99. </li><li> Edit AptanaStudio.ini: insert a new first line with only <i>-console</i> on it and save the file.
    100. 

  100. </li><li> You can follow the same procedures on Eclipse. The folder structure will be identical but the file to edit is eclipse.ini. 
    101. 

  101. </li></ol>
    102. 

  102. </li><li> On Linux, we recommend that you start Studio/Eclipse from the command line and add <i>-console</i> as an argument.
    103. 

  103. </li></ol>
    104. 

  104. </li><li> After the application launches you'll see a separate console window start. Type <i>ss</i> at the command prompt in this window and you'll get a list of bundles.
    105. 

  105. </li><li> Pick the one which is not starting. If you don't see any Studio features at all, you might pick com.aptana.ide.core.ui; note the bundle number. See if the bundle says "Started".
    106. 

  106. </li><li> If not, type <i>start #</i>, replacing # with the number you just saw above. Note any error message displayed and log that with a ticket in ASAP.
    107. 

  107. </li></ol>
    108. 

  108. <a name="How_do_I_repair_my_Aptana_Studio_installation.3F"></a><h2> <span class="mw-headline">How do I repair my Aptana Studio installation?</span></h2>
    109. 

  109. <p>If you've just reinstalled Aptana Studio after uninstalling an older version and you get an error in your log file that looks like the following excerpt, you need to repair your installation.
    110. 

  110. </p>
    111. 

  111. <pre>!SESSION 2007-06-05 18:03:17.484 -----------------------------------------------
    112. 

  112. eclipse.buildId=unknown
    113. 

  113. java.version=1.6.0_01
    114. 

  114. java.vendor=Sun Microsystems Inc.
    115. 

  115. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
    116. 

  116. Framework arguments: C:\Program Files\Aptana\Aptana IDE Beta\Aptana.exe
    117. 

  117. Command-line arguments: -os win32 -ws win32 -arch x86 C:\Program Files\Aptana\Aptana IDE Beta\Aptana.exe 
    118. 

    119. 

  119. !ENTRY org.eclipse.core.runtime 2007-06-05 18:03:19.640
    120. 

  120. !MESSAGE Product com.aptana.ide.rcp.product could not be found.
    121. 

    122. 

  122. !ENTRY org.eclipse.osgi 4 0 2007-06-05 18:03:19.671
    123. 

  123. !MESSAGE Application error
    124. 

  124. !STACK 1
    125. 

  125. java.lang.RuntimeException: No application id has been found. 
    126. 

  126. </pre>
    127. 

  127. <p>Repair your Aptana installation:
    128. 

  128. </p>
    129. 

  129. <ul><li> <b>Windows:</b> Navigate to C:\Documents and Settings\Username\Application Data\Aptana\Aptana Studio and rename the configuration folder under Aptana Studio to configuration.bak or another temp name. 
    130. 

  130. </li><li> <b>OS X:</b> Navigate to ~/Library/Application Support/Aptana/Aptana Studio and rename the configuration folder under Aptana Studio to configuration.bak or another temp name.
    131. 

  131. </li></ul>
    132. 

  132. <p>If that still doesn't work, you'll need to delete and reinstall Aptana Studio.
    133. 

  133. </p>
    134. 

  134. <a name="How_do_I_stop_Studio_from_loading_a_problem_file.3F"></a><h2> <span class="mw-headline">How do I stop Studio from loading a problem file?</span></h2>
    135. 

  135. <p>A file might be causing trouble when Aptana Studio is restarted because it's very large or in some way corrupted.
    136. 

  136. </p>
    137. 

  137. <ul><li> Rename the problem file, which will mean Studio cannot find it and so ignore the file on restart
    138. 

  138. </li><li> Delete the &lt;Aptana_workspace&gt;\.metadata\.plugins\org.eclipse.ui.workbench\workbench.xml file, where the state of workbench when exiting is saved. This means Studio will not preload <i>any</i> files that were open on the last exit.
    139. 

  139. </li></ul>
    140. 

  140. <a name="Tips_for_Getting_Better_Results_from_Bug_and_Feature_Request_Tickets"></a><h2> <span class="mw-headline">Tips for Getting Better Results from Bug and Feature Request Tickets</span></h2>
    141. 

  141. <ul><li> Search the bug database to see if someone has already filed a similar ticket--having one ticket for a particular issue allows us to keep everyone up to date as to status and increases our engineering efficiency.
    142. 

  142. </li><li> Fill out the new ticket form with as much detail as possible: product version/build number, the operating system you're using, standalone or Eclipse plugin version (if the ticket is for Studio), did this work previously and if so when did it stop working?
    143. 

  143. </li><li> Steps to reproduce the problem. Please be as exact as possible. Code samples, screenshots and screencasts are great! We love them.
    144. 

  144. </li><li> Attach the log file if at all possible
    145. 

  145. </li></ul>
    146. 

    147. 

  147. <!-- Saved in parser cache with key wikidb-aptana_:pcache:idhash:2531-0!1!0!!en!2!edit=0 and timestamp 20090201225951 -->
    148. 

  148. <div class="printfooter">
    149. 

  149. Retrieved from "<a href="http://aptana.com/docs/index.php/Troubleshooting_Aptana_Studio_Issues">http://aptana.com/docs/index.php/Troubleshooting_Aptana_Studio_Issues</a>"</div>
    150. 

  150. 										<script>
    151. 

  151. 						var lastModifiedClient = "";
    152. 

  152. 						var fullUrl = "";
    153. 

  153. 						try
    154. 

  154. 						{
    155. 

  155. 						   if(lastModifiedServer)
    156. 

  156. 						      notifyUpdatedSource(lastModifiedClient, lastModifiedServer, fullUrl);
    157. 

  157. 						}
    158. 

  158. 						catch(e) {}
    159. 

  159. 					</script>
    160. 

  160. 					 
    161. 

  161.          </div>
    162. 

  162.       </div>
    163. 

  163.    </body>
    164. 

  164. </html> 
    165. 

    166.