<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>eclipse on karlgrz</title>
    <link>https://karlgrz.com/tags/eclipse/</link>
    <description>Recent content in eclipse on karlgrz</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 26 Jun 2009 15:45:00 +0000</lastBuildDate><atom:link href="https://karlgrz.com/tags/eclipse/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Giving Tomcat More Memory in an Eclipse Development Environment</title>
      <link>https://karlgrz.com/giving-tomcat-more-memory-in-an-eclipse-development-environment/</link>
      <pubDate>Fri, 26 Jun 2009 15:45:00 +0000</pubDate>
      
      <guid>https://karlgrz.com/giving-tomcat-more-memory-in-an-eclipse-development-environment/</guid>
      <description>Sometimes when running tomcat inside eclipse there are processes that throw OutOfMemory errors (creating an extremely large Excel file, for instance) that are not thrown on our production servers.
By default, Eclipse runs tomcat with 64MB of maximum memory, even if you set up Eclipse to use more memory by editing the eclipse.ini file (I have mine set to 1024, and tomcat still runs at 64MB).
Eclipse makes it really easy to pass command line arguments to your Tomcat instance every time it is started.</description>
    </item>
    
  </channel>
</rss>
