You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Joe Bohn <jo...@earthlink.net> on 2006/03/28 20:26:15 UTC
Problems building on windows
I've been encountering a number of problems building on Windows which
seem to be steadily getting worse and I was wondering if anybody else is
experiencing this (and hopefully has some work-arounds).
- Out of Memory Errors. These seem to be related to two different
things:
1) Long file names. If I remember correctly Windows has issues if the
file names exceed 256 bytes. I've been working with multiple levels of
geronimo concurrently and so have had to name the root something other
than simply geronimo. It seems like if I start to get longer than 12
characters or so I begin to hit these problems. I think we may be
getting into trouble here with the depth of our packages and embedded
classes.
2) Extra garbage hanging around in %temp% from previous builds. The
geronimo build leaves a lot of trash in %temp% and when that seems to
cause problems with out of memory errors and subsequent builds.
- File IO errors when running the CRLF plugin. These may be related to
the %temp% storage but I seem to get them at times even when I've just
cleaned out my %temp%. Running back to back I get different results.
Thanks for the help,
Joe
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Problems building on windows
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Joe,
Don't worry, all those problems are fixed in Windows Vista.
Thanks,
Aaron
:)
On 3/28/06, Joe Bohn <jo...@earthlink.net> wrote:
>
> I've been encountering a number of problems building on Windows which
> seem to be steadily getting worse and I was wondering if anybody else is
> experiencing this (and hopefully has some work-arounds).
>
> - Out of Memory Errors. These seem to be related to two different
> things:
> 1) Long file names. If I remember correctly Windows has issues if the
> file names exceed 256 bytes. I've been working with multiple levels of
> geronimo concurrently and so have had to name the root something other
> than simply geronimo. It seems like if I start to get longer than 12
> characters or so I begin to hit these problems. I think we may be
> getting into trouble here with the depth of our packages and embedded
> classes.
> 2) Extra garbage hanging around in %temp% from previous builds. The
> geronimo build leaves a lot of trash in %temp% and when that seems to
> cause problems with out of memory errors and subsequent builds.
>
> - File IO errors when running the CRLF plugin. These may be related to
> the %temp% storage but I seem to get them at times even when I've just
> cleaned out my %temp%. Running back to back I get different results.
>
> Thanks for the help,
> Joe
>
> --
> Joe Bohn
> joe.bohn at earthlink.net
>
> "He is no fool who gives what he cannot keep, to gain what he cannot
> lose." -- Jim Elliot
>
Re: Problems building on windows
Posted by Joe Bohn <jo...@earthlink.net>.
I ran another clean build but this time with the MAVEN_OPTS settings
John mentioned below. I'm not sure yet if it's indicative of a general
solution (since it didn't always fail) but it didn't fail with the out
of memory error this time.
However, this time it did fail with the fileIO exception (actually, it's
a java.io.FileNotFoundException).
assemble:package-assembly:
[echo] Preparing CRLF line endings in text based files for zip
distribution
[zip] Building zip:
C:\geronimo\assemblies\j2ee-tomcat-server\target\geronimo-tomcat-j2ee-1.2-SNAPSHOT.zip
[echo] Preparing LF line endings in text based files for tar.gz
distribution
BUILD FAILED
File...... C:\geronimo\maven.xml
Element... maven:reactor
Line...... 227
Column.... -1
Unable to obtain goal [multiproject:install-callback] -- C:\Documents
and
Settings\Administrator\.maven\cache\geronimo-assembly-plugin-1.2.0-8\plugin.jelly:352:
-1: <ant:fixcrlf> java.io.FileNotFoundException:
C:\geronimo\assemblies\j2ee-tomcat-server\target\geronimo-1.2-SNAPSHOT\config-store\30\geronimo-console-standar
d-1.2-SNAPSHOT.war\WEB-INF\work\org\apache\jsp\WEB_002dINF\view\certmanager\generateCSRNormal_jsp.java
(Access is denied)
Total time : 36 minutes 34 seconds
15:58:36,934 INFO [App] Total time : 36 minutes 34 seconds
The referenced file (generateCSRNormal_jsp.java) does not exist in this
work location (just as the exception indicated). It's the only jsp that
doesn't have both the java and class files in that work location.
However, it makes me wonder if we need to be processing these work files
anyway in the plugin. Do we really need to touch the line endings on
these files (if in fact that is what we're doing at this point in time)?
As a side note: After the build %temp% included about the same number
of test* files as my earlier post (47), only 9 geronimo-deploymentUtil*
files and 11 package*.tmpdir directories.
John Sisson wrote:
> Joe Bohn wrote:
>
>>
>> I've been encountering a number of problems building on Windows which
>> seem to be steadily getting worse and I was wondering if anybody else
>> is experiencing this (and hopefully has some work-arounds).
>>
>> - Out of Memory Errors. These seem to be related to two different
>> things:
>> 1) Long file names. If I remember correctly Windows has issues if
>> the file names exceed 256 bytes. I've been working with multiple
>> levels of geronimo concurrently and so have had to name the root
>> something other than simply geronimo. It seems like if I start to get
>> longer than 12 characters or so I begin to hit these problems. I
>> think we may be getting into trouble here with the depth of our
>> packages and embedded classes.
>
> Yes, it is concerning..
> http://mail-archives.apache.org/mod_mbox/geronimo-dev/200601.mbox/%3C43C45F7B.6070703@gmail.com%3E
>
> I also have had to shorten my directory path I am building in. The long
> file name issue should go way when we move to JDK 1.5_06 but a number of
> other programs on Windows that deal with files also have the issue (e.g.
> Windows File Explorer, WinZip, Visual SourceSafe) so this issue could
> bite us with users complaining that other tools they are using can't
> work with Geronimo's long directory paths.
> Do we have a JIRA for this issue?
>
>> 2) Extra garbage hanging around in %temp% from previous builds. The
>> geronimo build leaves a lot of trash in %temp% and when that seems to
>> cause problems with out of memory errors and subsequent builds.
>>
> See http://issues.apache.org/jira/browse/GERONIMO-777
>
> Are you seeing these problems on trunk, 1.0 or 1.1 branches or all?
> What JDK are you using?
>
> For a long time I have been using the following (from memory I think
> there was something in maven or one of the libraries it uses that had a
> leak - not sure if this still exists)
>
> SET MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m
>
> What command are you using to build? (this could possibly affect what
> code gets invoked and how much memory is used). Do you have MAVEN_OPTS
> environment variables set?
>
> I will try to reproduce with the same JDK level and commands once you
> provide the info.
>
>> - File IO errors when running the CRLF plugin. These may be related to
>> the %temp% storage but I seem to get them at times even when I've just
>> cleaned out my %temp%. Running back to back I get different results.
>
> One thing to try is disabling XP's file indexing (which I have done).
> It looks like this has caused problems for Java elsewhere (see the
> workaround in this bug)..
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5006328
>
> I also found that
> http://www.sysinternals.com/Utilities/ProcessExplorer.html utility is
> good for tracking down processes that have file handles open. Use the
> Find-->Find Handle menu option and specify the file name.
> I had some similar problems for a while and ended up tracking it down my
> incorrectly configured Diskeeper disk defragmenter that had paused
> defragmentation and held file handles open.
> Have you tried with real-time virus checking disabled to check it isn't
> a virus checker causing issues?
> What files are you getting the IO errors on? Can you include the error
> output?
>
> It makes me wonder if we need to have some kind of retry logic for file
> operations if we are possibly competing with file indexers etc so we can
> run on a Windows box without problems. I noticed some of the Ant tasks
> have retry logic for some file operations:
>
> http://svn.apache.org/viewcvs.cgi/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Mkdir.java?view=markup
>
> http://svn.apache.org/viewcvs.cgi/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Delete.java?view=markup
>
>
> Regards,
>
> John
>
>>
>> Thanks for the help,
>> Joe
>>
>
>
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Problems building on windows
Posted by Joe Bohn <jo...@earthlink.net>.
Thanks for the information Kevan.
Kevan Miller wrote:
[snip]
>
> I'd concentrate on the Temp files to begin with... They're more likely
> at the heart of the problem -- they give an explanation for why this is
> only happening on Windoze...
>
> Each open file descriptor is going to be consuming memory. As I recall,
> the delete-on-exit function will also consume memory. How many temp
> files are being created during the course of a build?
It appears that there are about 47 of the test* files, 35 of the
geronimo-deploymentUtil* files, and 31 package*.tmpdir directories
containing a varying number of files each. All together, there are 249
files and 469 directories created in temp as a result of this build attempt.
>
> Around "LDAP Demo for Jetty", my build on Mac OSX is only using ~
> 60megs. By the end of the build, however, I'm using 90 out of 108 megs.
> So, we don't have a lot of headroom. Quite possible that there's a
> memory leak floating around...
>
> --kevan (who is happy to not have this problem, yet... ;-)
>
>
[snip]
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Problems building on windows
Posted by Kevan Miller <ke...@gmail.com>.
On Mar 29, 2006, at 10:58 AM, Joe Bohn wrote:
> I just ran a clean build of trunk and once again received the out
> of memory error. Here are some of the details:
>
> - Whenever I see this problem I also get multiple instances of
> messages issued (14 each in this most recent case). I've attached
> the end of the build messages below.
Aaron raised a jira regarding the multiple messages -- http://
issues.apache.org/jira/browse/GERONIMO-1509
I agree with Aaron that this is caused by logging in our junit tests.
I doubt that this is the root of your OutOfMemory problem. The
redundant logging of messages occurs on all OS's and I just don't see
it consuming large amounts of memory.
>
> - The junk in %temp% typically consists of 3 different type of items:
> 1) A number of geronimo deployment files of the form: geronimo-
> deploymentUtil41110.tmpdir
> 2) A number of package directories which appear to contain the
> deployed configurations of the form: package59537.tmpdir
> 3) A number of test jars of the form: test-2-40867.jar
I'd concentrate on the Temp files to begin with... They're more
likely at the heart of the problem -- they give an explanation for
why this is only happening on Windoze...
Each open file descriptor is going to be consuming memory. As I
recall, the delete-on-exit function will also consume memory. How
many temp files are being created during the course of a build?
Around "LDAP Demo for Jetty", my build on Mac OSX is only using ~
60megs. By the end of the build, however, I'm using 90 out of 108
megs. So, we don't have a lot of headroom. Quite possible that
there's a memory leak floating around...
--kevan (who is happy to not have this problem, yet... ;-)
>
>
>
> Gory details below:
>
> Here's a sample of the build output on the console:
>
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> 09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
> | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> 09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> 09:59:31,323 INFO [ReactorTag]
> +----------------------------------------
> DEPRECATED: the default goal should be specified in the <build>
> section of project.xml instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> DEPRECATED: the default goal should be specified in the <build>
> section of project.xml instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> 09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default
> goal should be specified in the <build> section of project.xml
> instead of maven.xml
> You are working offline so the build will continue, but ldap-
> realm-1.2-SNAPSHOT.car may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out
> of date!
> You are working offline so the build will continue, but geronimo-
> ldap-demo-1.2-SNAPSHOT.war may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> 09:59:31,823 WARN [DependencyVerifier] You are working offline so
> the build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war
> may be out of date!
> build:start:
>
> multiproject:install-callback:
> [echo] Running car:install for LDAP Demo for Jetty
> Generated package C:\geronimo\configs\ldap-demo-jetty\target\ldap-
> demo-jetty-1.2-SNAPSHOT.car
>
> BUILD FAILED
> File...... C:\geronimo\maven.xml
> Element... maven:reactor
> Line...... 222
> Column.... -1
> Unable to obtain goal [multiproject:install-callback] -- C:
> \Documents and Settings\bohn\.maven\cache\maven-artifact-plugin-1.6
> \plugin.jelly:67:-1: <ant:echo> ja
> va.lang.OutOfMemoryError
> Total time : 19 minutes 55 seconds
> car:prepare-plan:
>
> car:package:
>
> car:install:
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> 09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
> Finished at : Wednesday, March 29, 2006 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
> 09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
> 9:59:36 AM EST
>
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
> 09:59:36,042 INFO [App]
>
>
>
> --
> Joe Bohn
> joe.bohn at earthlink.net
>
> "He is no fool who gives what he cannot keep, to gain what he
> cannot lose." -- Jim Elliot
Re: Problems building on windows
Posted by Joe Bohn <jo...@earthlink.net>.
I just ran a clean build of trunk and once again received the out of
memory error. Here are some of the details:
- Whenever I see this problem I also get multiple instances of messages
issued (14 each in this most recent case). I've attached the end of the
build messages below.
- The junk in %temp% typically consists of 3 different type of items:
1) A number of geronimo deployment files of the form:
geronimo-deploymentUtil41110.tmpdir
2) A number of package directories which appear to contain the deployed
configurations of the form: package59537.tmpdir
3) A number of test jars of the form: test-2-40867.jar
Gory details below:
Here's a sample of the build output on the console:
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
| geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
09:59:31,323 INFO [ReactorTag] | geronimo-configs LDAP Demo for Jetty
| Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
09:59:31,323 INFO [ReactorTag] | Memory: 86M/105M
+----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
09:59:31,323 INFO [ReactorTag] +----------------------------------------
DEPRECATED: the default goal should be specified in the <build> section
of project.xml instead of maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
DEPRECATED: the default goal should be specified in the <build> section
of project.xml instead of maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
09:59:31,370 WARN [PluginScriptParser] DEPRECATED: the default goal
should be specified in the <build> section of project.xml instead of
maven.xml
You are working offline so the build will continue, but
ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but ldap-realm-1.2-SNAPSHOT.car may be out of date!
You are working offline so the build will continue, but
geronimo-ldap-demo-1.2-SNAPSHOT.war may be out of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
09:59:31,823 WARN [DependencyVerifier] You are working offline so the
build will continue, but geronimo-ldap-demo-1.2-SNAPSHOT.war may be out
of date!
build:start:
multiproject:install-callback:
[echo] Running car:install for LDAP Demo for Jetty
Generated package
C:\geronimo\configs\ldap-demo-jetty\target\ldap-demo-jetty-1.2-SNAPSHOT.car
BUILD FAILED
File...... C:\geronimo\maven.xml
Element... maven:reactor
Line...... 222
Column.... -1
Unable to obtain goal [multiproject:install-callback] -- C:\Documents
and
Settings\bohn\.maven\cache\maven-artifact-plugin-1.6\plugin.jelly:67:-1:
<ant:echo> ja
va.lang.OutOfMemoryError
Total time : 19 minutes 55 seconds
car:prepare-plan:
car:package:
car:install:
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
09:59:36,026 INFO [App] Total time : 19 minutes 55 seconds
Finished at : Wednesday, March 29, 2006 9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App] Finished at : Wednesday, March 29, 2006
9:59:36 AM EST
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
09:59:36,042 INFO [App]
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Problems building on windows
Posted by Joe Bohn <jo...@earthlink.net>.
John,
First, thanks for the detailed response! I'll have to try out some of
the utilities that you mention, reproduce the problems, and get back
with the details. But I'd like to say how much I appreciate all of the
advice you've provided. More responses in-line.
John Sisson wrote:
> Joe Bohn wrote:
>
>>
>> I've been encountering a number of problems building on Windows which
>> seem to be steadily getting worse and I was wondering if anybody else
>> is experiencing this (and hopefully has some work-arounds).
>>
>> - Out of Memory Errors. These seem to be related to two different
>> things:
>> 1) Long file names. If I remember correctly Windows has issues if
>> the file names exceed 256 bytes. I've been working with multiple
>> levels of geronimo concurrently and so have had to name the root
>> something other than simply geronimo. It seems like if I start to get
>> longer than 12 characters or so I begin to hit these problems. I
>> think we may be getting into trouble here with the depth of our
>> packages and embedded classes.
>
> Yes, it is concerning..
> http://mail-archives.apache.org/mod_mbox/geronimo-dev/200601.mbox/%3C43C45F7B.6070703@gmail.com%3E
>
> I also have had to shorten my directory path I am building in. The long
> file name issue should go way when we move to JDK 1.5_06 but a number of
> other programs on Windows that deal with files also have the issue (e.g.
> Windows File Explorer, WinZip, Visual SourceSafe) so this issue could
> bite us with users complaining that other tools they are using can't
> work with Geronimo's long directory paths.
> Do we have a JIRA for this issue?
I'm not aware of a JIRA for this. I'll search again and if I can't find
one I'll create one. Another tool to add to the list is xcopy.
>
>> 2) Extra garbage hanging around in %temp% from previous builds. The
>> geronimo build leaves a lot of trash in %temp% and when that seems to
>> cause problems with out of memory errors and subsequent builds.
>>
> See http://issues.apache.org/jira/browse/GERONIMO-777
Hmmm ... I had seen this JIRA and all the discussion but somehow I
always only focused on the config-store part of it and I haven't noticed
that problem recently.
>
> Are you seeing these problems on trunk, 1.0 or 1.1 branches or all?
I'm seeing them on 1.0 and trunk for sure. I haven't been keeping
careful tabs on 1.1 but I'd be surprised if it was any different there.
> What JDK are you using?
Sun JDK 1.4.2_08 (build 1.4.2_08-b03)
>
> For a long time I have been using the following (from memory I think
> there was something in maven or one of the libraries it uses that had a
> leak - not sure if this still exists)
>
> SET MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m
>
> What command are you using to build? (this could possibly affect what
> code gets invoked and how much memory is used). Do you have MAVEN_OPTS
> environment variables set?
No, I don't have MAVEN_OPTS set but I'll certainly give that a try. I
build with many different commands and from many different location
depending upon what I'm doing. This problem seems more pronounced when
I do a full clean build with itests .... "maven m:clean new" from
geronimo root.
>
> I will try to reproduce with the same JDK level and commands once you
> provide the info.
>
>> - File IO errors when running the CRLF plugin. These may be related to
>> the %temp% storage but I seem to get them at times even when I've just
>> cleaned out my %temp%. Running back to back I get different results.
>
> One thing to try is disabling XP's file indexing (which I have done).
> It looks like this has caused problems for Java elsewhere (see the
> workaround in this bug)..
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5006328
>
> I also found that
> http://www.sysinternals.com/Utilities/ProcessExplorer.html utility is
> good for tracking down processes that have file handles open. Use the
> Find-->Find Handle menu option and specify the file name.
> I had some similar problems for a while and ended up tracking it down my
> incorrectly configured Diskeeper disk defragmenter that had paused
> defragmentation and held file handles open.
> Have you tried with real-time virus checking disabled to check it isn't
> a virus checker causing issues?
> What files are you getting the IO errors on? Can you include the error
> output?
Thanks for the pointers to utilities. I'll give them a try (including
disabling the real-time virus checker but it seems to happen with too
great a frequency to be this). The FileIO errors are always on files
deep within the config-store when it fails during the CRLF plugin ...
perhaps related to the long file names again.
>
> It makes me wonder if we need to have some kind of retry logic for file
> operations if we are possibly competing with file indexers etc so we can
> run on a Windows box without problems. I noticed some of the Ant tasks
> have retry logic for some file operations:
>
> http://svn.apache.org/viewcvs.cgi/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Mkdir.java?view=markup
>
> http://svn.apache.org/viewcvs.cgi/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Delete.java?view=markup
>
>
> Regards,
>
> John
>
>>
>> Thanks for the help,
>> Joe
>>
>
>
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
Re: Problems building on windows
Posted by John Sisson <jr...@gmail.com>.
Joe Bohn wrote:
>
> I've been encountering a number of problems building on Windows which
> seem to be steadily getting worse and I was wondering if anybody else
> is experiencing this (and hopefully has some work-arounds).
>
> - Out of Memory Errors. These seem to be related to two different
> things:
> 1) Long file names. If I remember correctly Windows has issues if
> the file names exceed 256 bytes. I've been working with multiple
> levels of geronimo concurrently and so have had to name the root
> something other than simply geronimo. It seems like if I start to get
> longer than 12 characters or so I begin to hit these problems. I
> think we may be getting into trouble here with the depth of our
> packages and embedded classes.
Yes, it is concerning..
http://mail-archives.apache.org/mod_mbox/geronimo-dev/200601.mbox/%3C43C45F7B.6070703@gmail.com%3E
I also have had to shorten my directory path I am building in. The long
file name issue should go way when we move to JDK 1.5_06 but a number of
other programs on Windows that deal with files also have the issue (e.g.
Windows File Explorer, WinZip, Visual SourceSafe) so this issue could
bite us with users complaining that other tools they are using can't
work with Geronimo's long directory paths.
Do we have a JIRA for this issue?
> 2) Extra garbage hanging around in %temp% from previous builds. The
> geronimo build leaves a lot of trash in %temp% and when that seems to
> cause problems with out of memory errors and subsequent builds.
>
See http://issues.apache.org/jira/browse/GERONIMO-777
Are you seeing these problems on trunk, 1.0 or 1.1 branches or all?
What JDK are you using?
For a long time I have been using the following (from memory I think
there was something in maven or one of the libraries it uses that had a
leak - not sure if this still exists)
SET MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m
What command are you using to build? (this could possibly affect what
code gets invoked and how much memory is used). Do you have MAVEN_OPTS
environment variables set?
I will try to reproduce with the same JDK level and commands once you
provide the info.
> - File IO errors when running the CRLF plugin. These may be related to
> the %temp% storage but I seem to get them at times even when I've just
> cleaned out my %temp%. Running back to back I get different results.
One thing to try is disabling XP's file indexing (which I have done).
It looks like this has caused problems for Java elsewhere (see the
workaround in this bug)..
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5006328
I also found that
http://www.sysinternals.com/Utilities/ProcessExplorer.html utility is
good for tracking down processes that have file handles open. Use the
Find-->Find Handle menu option and specify the file name.
I had some similar problems for a while and ended up tracking it down my
incorrectly configured Diskeeper disk defragmenter that had paused
defragmentation and held file handles open.
Have you tried with real-time virus checking disabled to check it isn't
a virus checker causing issues?
What files are you getting the IO errors on? Can you include the error
output?
It makes me wonder if we need to have some kind of retry logic for file
operations if we are possibly competing with file indexers etc so we can
run on a Windows box without problems. I noticed some of the Ant tasks
have retry logic for some file operations:
http://svn.apache.org/viewcvs.cgi/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Mkdir.java?view=markup
http://svn.apache.org/viewcvs.cgi/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/Delete.java?view=markup
Regards,
John
>
> Thanks for the help,
> Joe
>