[sip-comm-dev] javac compiler settings in case of "java.lang.OutOfMemoryError"


#1

Hi, dear all,
Recently, as SIPComm is growing bigger, you may suffer a "system is out of
resources" --> "java.lang.OutOfMemoryError: java heap space", especially in
Windows system.
If so, plz update your build.xml at line 208, add: memoryMaximumSize="400M"
fork="true"
If the compiler says "Error in running javac.exe compiler", plz check your
PATH env for java home bin folder. make sure you can use javac command in
cmd.
coz IDE like eclipse may use its own compiler, while javac must be available
externally, when fork="true"

···

--
BR
NIE PIN
TML@HUT, Helsinki, Finland
ANTD@NIST, Gaithersburg, USA
Ph: +1 (301)975-6049


#2

Hi Pin, Emil,

···

On 2008/03/13, at 2:00, pin nie wrote:

Recently, as SIPComm is growing bigger, you may suffer a "system is out of resources" --> "java.lang.OutOfMemoryError: java heap space", especially in Windows system.
If so, plz update your build.xml at line 208, add: memoryMaximumSize="400M" fork="true"

Actually I also recently faced that on MacOSX, so we definitely need to consider this problem.

Cheers,
romain

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Emil,

Did you get a chance try Pin's fix? If it does the job for you then we
should definitely apply it.

I have tried Pin's fix (enclosed) and it works fine on MacOSX. Maybe we should also try it on the Linux and Windows package generator computers to check if it does not introduce errors on those systems? Or shall I just commit the fix and wait for the next packet generation trial?

Cheers,

Romain

--- build.xml (revision 3535)
+++ build.xml (working copy)
@@ -205,7 +205,7 @@
          <!--internal-target- compiles the entire project source tree -->
          <javac classpathref="compile.class.path" debug="true"
              deprecation="true" destdir="${dest}" nowarn="false"
- source="1.5" target="1.5">
+ source="1.5" target="1.5" memoryMaximumSize="400M" fork="true">
              <src path="${src}"/>
              <src path="${src2}"/>
              <include name="**/*.java" />

···

On 2008/03/14, at 6:00, Emil Ivov wrote:


#4

Works for me (Linux). I'll try to test it on windows at some point today
but I see no reason it would not work. Besides, our windows installers
are generated on Linux so you could definitely go ahead and commit.

Thanks!
Emil

Romain KUNTZ написа:

···

Hi Emil,

On 2008/03/14, at 6:00, Emil Ivov wrote:

Did you get a chance try Pin's fix? If it does the job for you then we
should definitely apply it.

I have tried Pin's fix (enclosed) and it works fine on MacOSX. Maybe we
should also try it on the Linux and Windows package generator computers
to check if it does not introduce errors on those systems? Or shall I
just commit the fix and wait for the next packet generation trial?

Cheers,

Romain

--- build.xml (revision 3535)
+++ build.xml (working copy)
@@ -205,7 +205,7 @@
         <!--internal-target- compiles the entire project source tree -->
         <javac classpathref="compile.class.path" debug="true"
             deprecation="true" destdir="\{dest\}&quot; nowarn=&quot;false&quot; \- source=&quot;1\.5&quot; target=&quot;1\.5&quot;&gt; \+ source=&quot;1\.5&quot; target=&quot;1\.5&quot; memoryMaximumSize=&quot;400M&quot; fork=&quot;true&quot;&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;src path=&quot;{src}"/>
             <src path="${src2}"/>
             <include name="**/*.java" />

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net