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/08/30 17:36:44 UTC
windows build hell
We've been struggling with build problems on windows for some time now
and things just keep on getting worse.
I'm composing this note to summarize the problems that I'm aware of with
work-arounds and possible solutions. I'm also fishing to see if
anybody else has some ideas on how to resolve these issues.
1) Windows pathlength problem.
Problem:
There are miscellaneous failures that can typically be tracked down to
the windows pathlength problem. The nature of our repository structure
and deployment make this a big problem. It also seems like we're
continuing to add more intermediate elements in path names as we try to
get things more organized and conform to Maven 2 conventions.
Work-around:
The work-around is to keep the windows root path as small as possible.
I now typically build from a root path of c:\g to avoid these problems.
Possible Solution:
For a longer term solution I'm planning to work on a new repository
implementation in 1.2 that that isn't as redundant or verbose.
2) JSP compilation errors
Problem:
Embedded error: Unable to compile class for JSP
Strange error message about JAVA_HOME, etc...
Possible Solution/Work-around:
Update the pom.xml in the root directory to use version 1.4.5-SNAPSHOT
(from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
planning to make 1.4.5 an official release for this. We're not sure why
it gets us around the problem so it may be a red herring.
3) Openejb2 test failures.
Problem:
Caused by: java.lang.NoSuchMethodException:
org.openejb.deployment.DeploymentTestSuite.getName()
Work-around:
After bootstrap failure cd to <root>\target\external\openejb2
"mvn -Dmaven.test.skip=true"
cd back to <root>
"mvn clean install"
Possible solution:
Dain suggested adding the "getName" method to the test. However, when I
attempted this I hit other errors.
http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
I think it would be helpful if we could disable the openejb tests until
this problem is resolved.
4) Blue screen of death (bsod)
Problem:
This has been reported by multiple users on various machines. When
running an M1 or M2 build the user encounters a bsod due to a memory
failure.
PAGE_FAULT_IN_NONPAGED_AREA
*** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B, 0x00000000)
Dump of physical memory
Work-around/Possible Solution:
Haven't found one yet. I've tried updated drivers, replaced hardware,
tried various heap size settings, etc.... At times this can be fairly
frequent (every 3rd build attempt or so). I'm collecting bootstrap.log
files from folks when this happens during a bootstrap to see if there is
a common thread. So far, with the bootstrap logs, it always seems to
happen at about the same place:
Running tests after building a module (usually tomcat.ApplicationTest or
TomcatModuleBuilderTest) and the final lines in the log are always the
Creation of an MBeanServer like this:
[exec] Running org.apache.geronimo.tomcat.ApplicationTest
[exec] Created MBeanServer with ID: 5dcec6:10d5a184aed:-8000:jbohn2:1
Please respond to this note if you are seeing the bsod failures on
windows. At first I thought this was just me and was hardware related.
However, the more I talk to folks on windows the more I hear of other
folks encountering this same problem. I've updated all drivers,
replaced my entire system, and several other folks have reported seeing
this on completely different systems. I think that pretty much rules
out a hardware problem.
ideas welcome!
Joe
Re: windows build hell
Posted by Joe Bohn <jo...@earthlink.net>.
Thanks for the clarification Jeff (and pursuing the vote). Based upon
the most recent discussion on the jspc item I wasn't sure if you and
others were confortable with the fix. It certainly works for me! :-)
Joe
Jeff Genender wrote:
>
> Joe Bohn wrote:
>
>>2) JSP compilation errors
>>Problem:
>>Embedded error: Unable to compile class for JSP
>>Strange error message about JAVA_HOME, etc...
>>
>>Possible Solution/Work-around:
>>Update the pom.xml in the root directory to use version 1.4.5-SNAPSHOT
>>(from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
>>planning to make 1.4.5 an official release for this. We're not sure why
>>it gets us around the problem so it may be a red herring.
>>
>
>
> Its not a red herring. It gets you around the problem because in 1.4.5
> I actually hunt down the tools.jar file...in a similar fashion as done
> in Ant when running the jspc complier from there. i.e.:
>
> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
> <classpath>
> <pathelement location="${java.home}/../lib/tools.jar"/>
> ...
>
> I have to duplicate that in code. That's why 1.4.5 works.
>
> The release is under vote. So far no -1s. I think I will be able to
> release it today as the 72 hours is up. I'll let this list know when I
> have released it.
>
> Jeff
>
>
Re: windows build hell
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/1/06, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
> > Or ping Dain... this issue has been broke for far too long, why
> > doesn't someone from openejb just add this method... Dain?!?!
>
> If I'd known what to add I'd already have done it. Let me know what it
> is and I'll commit it. A jira issue would be of help, too ;-)
Whoohoo! Spot it!
jlaskowski@dev /cygdrive/c/oss/openejb2
$ mvn install
...
log4j: Finished configuring.
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.797 sec
Running org.openejb.deployment.EjbJarModuleDeploymentTest
Retrieving document at 'META-INF/wsdl/test-ejb.wsdl'.
org.apache.maven.surefire.booter.SurefireExecutionException:
org.openejb.deployment.EjbJarModuleDeploymentTest; nested exception is
java.lang.reflect.UndeclaredThrowableException:
null; nested exception is
org.apache.maven.surefire.testset.TestSetFailedException:
org.openejb.deployment.EjbJarModuleDeploymentTest; nested exception is
java.lang.reflect.Undecla
redThrowableException: null
org.apache.maven.surefire.testset.TestSetFailedException:
org.openejb.deployment.EjbJarModuleDeploymentTest; nested exception is
java.lang.reflect.UndeclaredThrowableException: nul
l
java.lang.reflect.UndeclaredThrowableException
at $Proxy0.addError(Unknown Source)
at junit.framework.TestResult.addError(TestResult.java:36)
at junit.framework.TestResult.runProtected(TestResult.java:133)
at org.openejb.deployment.DeploymentTestSuite.run(DeploymentTestSuite.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)
Caused by: java.lang.NoSuchMethodException:
org.openejb.deployment.DeploymentTestSuite.getName()
at java.lang.Class.getMethod(Class.java:986)
at org.apache.maven.surefire.junit.TestListenerInvocationHandler.getStackTraceWriter(TestListenerInvocationHandler.java:171)
at org.apache.maven.surefire.junit.TestListenerInvocationHandler.handleAddError(TestListenerInvocationHandler.java:160)
at org.apache.maven.surefire.junit.TestListenerInvocationHandler.invoke(TestListenerInvocationHandler.java:134)
... 18 more
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
Let me fix it so it won't surface anymore.
http://jira.codehaus.org/browse/OPENEJB-262
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: windows build hell
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 8/31/06, Jason Dillon <ja...@planet57.com> wrote:
> Or ping Dain... this issue has been broke for far too long, why
> doesn't someone from openejb just add this method... Dain?!?!
If I'd known what to add I'd already have done it. Let me know what it
is and I'll commit it. A jira issue would be of help, too ;-)
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: windows build hell
Posted by Sergey Elin <el...@gmail.com>.
Well,
I can't build trunk with bootstrap. There was a lot of strange errors, which
I can't reproduce at last twice. More or less "stable" errors was reported
by me or other people here (like OpenEJB2 error, jspc error, mail
1.3.1build error, etc.). I'm not actually shure my CLASSPATH was the
source of
all my problem, but unsetting this variable before building trunk finished
successfuly without breaking errors (except OpenEJB2's one).
I think It is worse to try build trunk with unsetted CLASSPATH (if it
includes ".") for people with build errors on WIndows and report results
here.
2006/9/1, Joe Bohn <jo...@earthlink.net>:
>
> Sergey,
>
> I'm not sure what problem you are referencing when you speak of having
> to unset classpath variable with "." in it. Can you please clarify?
>
> Thanks,
> Joe
>
>
> Sergey Elin wrote:
> > It seems my hell is over (I hope) then I unset CLASSPATH variable with
> > dot in it.
> > The only problem is OpenEJB with getName() on my Windows box.
> >
> >
> > 2006/9/1, Jason Dillon < jason@planet57.com <mailto:jason@planet57.com
> >>:
> >
> > Dain has already tried adding getName() and he reports it works...
> > though I am not sure what value he returned. Try changing it to
> > return "foo"; and see if it works.
> >
> > Or ping Dain... this issue has been broke for far too long, why
> > doesn't someone from openejb just add this method... Dain?!?!
> >
> > --jason
> >
> >
> > On Aug 31, 2006, at 8:51 AM, Joe Bohn wrote:
> >
> > > Jason,
> > >
> > > I'm not sure just adding getName() will fix the openejb test
> > > problem. See my earlier post:
> > >
> > http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
> > <http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2>
> > >
> > > Joe
> > >
> > > Jason Dillon wrote:
> > >> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
> > >> Can someone with openejb2 commit privs add a getName() to get
> > >> past that other error too?
> > >> --jason
> > >> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
> > >>>
> > >>>
> > >>> Joe Bohn wrote:
> > >>>
> > >>>> 2) JSP compilation errors
> > >>>> Problem:
> > >>>> Embedded error: Unable to compile class for JSP
> > >>>> Strange error message about JAVA_HOME, etc...
> > >>>>
> > >>>> Possible Solution/Work-around:
> > >>>> Update the pom.xml in the root directory to use version 1.4.5-
> > >>>> SNAPSHOT
> > >>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff
> > >>>> Genender is
> > >>>> planning to make 1.4.5 an official release for this. We're
> not
> > >>>> sure why
> > >>>> it gets us around the problem so it may be a red herring.
> > >>>>
> > >>>
> > >>> Its not a red herring. It gets you around the problem because
> > >>> in 1.4.5
> > >>> I actually hunt down the tools.jar file...in a similar fashion
> as
> > >>> done
> > >>> in Ant when running the jspc complier from there. i.e.:
> > >>>
> > >>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
> > >>> <classpath>
> > >>> <pathelement location="${
> > java.home}/../lib/tools.jar"/>
> > >>> ...
> > >>>
> > >>> I have to duplicate that in code. That's why 1.4.5 works.
> > >>>
> > >>> The release is under vote. So far no -1s. I think I will be
> > >>> able to
> > >>> release it today as the 72 hours is up. I'll let this list
> know
> > >>> when I
> > >>> have released it.
> > >>>
> > >>> Jeff
> >
> >
>
Re: windows build hell
Posted by Joe Bohn <jo...@earthlink.net>.
Sergey,
I'm not sure what problem you are referencing when you speak of having
to unset classpath variable with "." in it. Can you please clarify?
Thanks,
Joe
Sergey Elin wrote:
> It seems my hell is over (I hope) then I unset CLASSPATH variable with
> dot in it.
> The only problem is OpenEJB with getName() on my Windows box.
>
>
> 2006/9/1, Jason Dillon < jason@planet57.com <ma...@planet57.com>>:
>
> Dain has already tried adding getName() and he reports it works...
> though I am not sure what value he returned. Try changing it to
> return "foo"; and see if it works.
>
> Or ping Dain... this issue has been broke for far too long, why
> doesn't someone from openejb just add this method... Dain?!?!
>
> --jason
>
>
> On Aug 31, 2006, at 8:51 AM, Joe Bohn wrote:
>
> > Jason,
> >
> > I'm not sure just adding getName() will fix the openejb test
> > problem. See my earlier post:
> >
> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
> <http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2>
> >
> > Joe
> >
> > Jason Dillon wrote:
> >> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
> >> Can someone with openejb2 commit privs add a getName() to get
> >> past that other error too?
> >> --jason
> >> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
> >>>
> >>>
> >>> Joe Bohn wrote:
> >>>
> >>>> 2) JSP compilation errors
> >>>> Problem:
> >>>> Embedded error: Unable to compile class for JSP
> >>>> Strange error message about JAVA_HOME, etc...
> >>>>
> >>>> Possible Solution/Work-around:
> >>>> Update the pom.xml in the root directory to use version 1.4.5-
> >>>> SNAPSHOT
> >>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff
> >>>> Genender is
> >>>> planning to make 1.4.5 an official release for this. We're not
> >>>> sure why
> >>>> it gets us around the problem so it may be a red herring.
> >>>>
> >>>
> >>> Its not a red herring. It gets you around the problem because
> >>> in 1.4.5
> >>> I actually hunt down the tools.jar file...in a similar fashion as
> >>> done
> >>> in Ant when running the jspc complier from there. i.e.:
> >>>
> >>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
> >>> <classpath>
> >>> <pathelement location="${
> java.home}/../lib/tools.jar"/>
> >>> ...
> >>>
> >>> I have to duplicate that in code. That's why 1.4.5 works.
> >>>
> >>> The release is under vote. So far no -1s. I think I will be
> >>> able to
> >>> release it today as the 72 hours is up. I'll let this list know
> >>> when I
> >>> have released it.
> >>>
> >>> Jeff
>
>
Re: windows build hell
Posted by Sergey Elin <el...@gmail.com>.
It seems my hell is over (I hope) then I unset CLASSPATH variable with dot
in it.
The only problem is OpenEJB with getName() on my Windows box.
2006/9/1, Jason Dillon <ja...@planet57.com>:
>
> Dain has already tried adding getName() and he reports it works...
> though I am not sure what value he returned. Try changing it to
> return "foo"; and see if it works.
>
> Or ping Dain... this issue has been broke for far too long, why
> doesn't someone from openejb just add this method... Dain?!?!
>
> --jason
>
>
> On Aug 31, 2006, at 8:51 AM, Joe Bohn wrote:
>
> > Jason,
> >
> > I'm not sure just adding getName() will fix the openejb test
> > problem. See my earlier post:
> > http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
> >
> > Joe
> >
> > Jason Dillon wrote:
> >> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
> >> Can someone with openejb2 commit privs add a getName() to get
> >> past that other error too?
> >> --jason
> >> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
> >>>
> >>>
> >>> Joe Bohn wrote:
> >>>
> >>>> 2) JSP compilation errors
> >>>> Problem:
> >>>> Embedded error: Unable to compile class for JSP
> >>>> Strange error message about JAVA_HOME, etc...
> >>>>
> >>>> Possible Solution/Work-around:
> >>>> Update the pom.xml in the root directory to use version 1.4.5-
> >>>> SNAPSHOT
> >>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff
> >>>> Genender is
> >>>> planning to make 1.4.5 an official release for this. We're not
> >>>> sure why
> >>>> it gets us around the problem so it may be a red herring.
> >>>>
> >>>
> >>> Its not a red herring. It gets you around the problem because
> >>> in 1.4.5
> >>> I actually hunt down the tools.jar file...in a similar fashion as
> >>> done
> >>> in Ant when running the jspc complier from there. i.e.:
> >>>
> >>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
> >>> <classpath>
> >>> <pathelement location="${java.home}/../lib/tools.jar"/>
> >>> ...
> >>>
> >>> I have to duplicate that in code. That's why 1.4.5 works.
> >>>
> >>> The release is under vote. So far no -1s. I think I will be
> >>> able to
> >>> release it today as the 72 hours is up. I'll let this list know
> >>> when I
> >>> have released it.
> >>>
> >>> Jeff
>
>
Re: windows build hell
Posted by Jason Dillon <ja...@planet57.com>.
Dain has already tried adding getName() and he reports it works...
though I am not sure what value he returned. Try changing it to
return "foo"; and see if it works.
Or ping Dain... this issue has been broke for far too long, why
doesn't someone from openejb just add this method... Dain?!?!
--jason
On Aug 31, 2006, at 8:51 AM, Joe Bohn wrote:
> Jason,
>
> I'm not sure just adding getName() will fix the openejb test
> problem. See my earlier post:
> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
>
> Joe
>
> Jason Dillon wrote:
>> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
>> Can someone with openejb2 commit privs add a getName() to get
>> past that other error too?
>> --jason
>> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
>>>
>>>
>>> Joe Bohn wrote:
>>>
>>>> 2) JSP compilation errors
>>>> Problem:
>>>> Embedded error: Unable to compile class for JSP
>>>> Strange error message about JAVA_HOME, etc...
>>>>
>>>> Possible Solution/Work-around:
>>>> Update the pom.xml in the root directory to use version 1.4.5-
>>>> SNAPSHOT
>>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff
>>>> Genender is
>>>> planning to make 1.4.5 an official release for this. We're not
>>>> sure why
>>>> it gets us around the problem so it may be a red herring.
>>>>
>>>
>>> Its not a red herring. It gets you around the problem because
>>> in 1.4.5
>>> I actually hunt down the tools.jar file...in a similar fashion as
>>> done
>>> in Ant when running the jspc complier from there. i.e.:
>>>
>>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
>>> <classpath>
>>> <pathelement location="${java.home}/../lib/tools.jar"/>
>>> ...
>>>
>>> I have to duplicate that in code. That's why 1.4.5 works.
>>>
>>> The release is under vote. So far no -1s. I think I will be
>>> able to
>>> release it today as the 72 hours is up. I'll let this list know
>>> when I
>>> have released it.
>>>
>>> Jeff
Re: windows build hell
Posted by Joe Bohn <jo...@earthlink.net>.
Jason,
I'm not sure just adding getName() will fix the openejb test problem.
See my earlier post:
http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
Joe
Jason Dillon wrote:
> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
>
> Can someone with openejb2 commit privs add a getName() to get past that
> other error too?
>
> --jason
>
>
> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
>
>>
>>
>> Joe Bohn wrote:
>>
>>> 2) JSP compilation errors
>>> Problem:
>>> Embedded error: Unable to compile class for JSP
>>> Strange error message about JAVA_HOME, etc...
>>>
>>> Possible Solution/Work-around:
>>> Update the pom.xml in the root directory to use version 1.4.5- SNAPSHOT
>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
>>> planning to make 1.4.5 an official release for this. We're not sure
>>> why
>>> it gets us around the problem so it may be a red herring.
>>>
>>
>> Its not a red herring. It gets you around the problem because in 1.4.5
>> I actually hunt down the tools.jar file...in a similar fashion as done
>> in Ant when running the jspc complier from there. i.e.:
>>
>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
>> <classpath>
>> <pathelement location="${java.home}/../lib/tools.jar"/>
>> ...
>>
>> I have to duplicate that in code. That's why 1.4.5 works.
>>
>> The release is under vote. So far no -1s. I think I will be able to
>> release it today as the 72 hours is up. I'll let this list know when I
>> have released it.
>>
>> Jeff
>
>
>
>
Re: windows build hell
Posted by Jason Dillon <ja...@planet57.com>.
Done.
--jason
On Aug 30, 2006, at 11:49 PM, Jeff Genender wrote:
> I have released v1.4.5. Feel free to update the pom(s) to use that
> version.
>
> Jeff
>
> Jason Dillon wrote:
>> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
>>
>> Can someone with openejb2 commit privs add a getName() to get past
>> that
>> other error too?
>>
>> --jason
>>
>>
>> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
>>
>>>
>>>
>>> Joe Bohn wrote:
>>>> 2) JSP compilation errors
>>>> Problem:
>>>> Embedded error: Unable to compile class for JSP
>>>> Strange error message about JAVA_HOME, etc...
>>>>
>>>> Possible Solution/Work-around:
>>>> Update the pom.xml in the root directory to use version 1.4.5-
>>>> SNAPSHOT
>>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff
>>>> Genender is
>>>> planning to make 1.4.5 an official release for this. We're not
>>>> sure why
>>>> it gets us around the problem so it may be a red herring.
>>>>
>>>
>>> Its not a red herring. It gets you around the problem because in
>>> 1.4.5
>>> I actually hunt down the tools.jar file...in a similar fashion as
>>> done
>>> in Ant when running the jspc complier from there. i.e.:
>>>
>>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
>>> <classpath>
>>> <pathelement location="${java.home}/../lib/tools.jar"/>
>>> ...
>>>
>>> I have to duplicate that in code. That's why 1.4.5 works.
>>>
>>> The release is under vote. So far no -1s. I think I will be
>>> able to
>>> release it today as the 72 hours is up. I'll let this list know
>>> when I
>>> have released it.
>>>
>>> Jeff
Re: windows build hell
Posted by Jason Dillon <ja...@planet57.com>.
Kay, I'm checking now...
--jason
On Aug 30, 2006, at 11:49 PM, Jeff Genender wrote:
> I have released v1.4.5. Feel free to update the pom(s) to use that
> version.
>
> Jeff
>
> Jason Dillon wrote:
>> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
>>
>> Can someone with openejb2 commit privs add a getName() to get past
>> that
>> other error too?
>>
>> --jason
>>
>>
>> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
>>
>>>
>>>
>>> Joe Bohn wrote:
>>>> 2) JSP compilation errors
>>>> Problem:
>>>> Embedded error: Unable to compile class for JSP
>>>> Strange error message about JAVA_HOME, etc...
>>>>
>>>> Possible Solution/Work-around:
>>>> Update the pom.xml in the root directory to use version 1.4.5-
>>>> SNAPSHOT
>>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff
>>>> Genender is
>>>> planning to make 1.4.5 an official release for this. We're not
>>>> sure why
>>>> it gets us around the problem so it may be a red herring.
>>>>
>>>
>>> Its not a red herring. It gets you around the problem because in
>>> 1.4.5
>>> I actually hunt down the tools.jar file...in a similar fashion as
>>> done
>>> in Ant when running the jspc complier from there. i.e.:
>>>
>>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
>>> <classpath>
>>> <pathelement location="${java.home}/../lib/tools.jar"/>
>>> ...
>>>
>>> I have to duplicate that in code. That's why 1.4.5 works.
>>>
>>> The release is under vote. So far no -1s. I think I will be
>>> able to
>>> release it today as the 72 hours is up. I'll let this list know
>>> when I
>>> have released it.
>>>
>>> Jeff
Re: windows build hell
Posted by Jeff Genender <jg...@apache.org>.
I have released v1.4.5. Feel free to update the pom(s) to use that version.
Jeff
Jason Dillon wrote:
> If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
>
> Can someone with openejb2 commit privs add a getName() to get past that
> other error too?
>
> --jason
>
>
> On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
>
>>
>>
>> Joe Bohn wrote:
>>> 2) JSP compilation errors
>>> Problem:
>>> Embedded error: Unable to compile class for JSP
>>> Strange error message about JAVA_HOME, etc...
>>>
>>> Possible Solution/Work-around:
>>> Update the pom.xml in the root directory to use version 1.4.5-SNAPSHOT
>>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
>>> planning to make 1.4.5 an official release for this. We're not sure why
>>> it gets us around the problem so it may be a red herring.
>>>
>>
>> Its not a red herring. It gets you around the problem because in 1.4.5
>> I actually hunt down the tools.jar file...in a similar fashion as done
>> in Ant when running the jspc complier from there. i.e.:
>>
>> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
>> <classpath>
>> <pathelement location="${java.home}/../lib/tools.jar"/>
>> ...
>>
>> I have to duplicate that in code. That's why 1.4.5 works.
>>
>> The release is under vote. So far no -1s. I think I will be able to
>> release it today as the 72 hours is up. I'll let this list know when I
>> have released it.
>>
>> Jeff
Re: windows build hell
Posted by Jason Dillon <ja...@planet57.com>.
If using 1.4.5-SNAPSHOT fixes things... then lets just use it.
Can someone with openejb2 commit privs add a getName() to get past
that other error too?
--jason
On Aug 30, 2006, at 8:46 AM, Jeff Genender wrote:
>
>
> Joe Bohn wrote:
>> 2) JSP compilation errors
>> Problem:
>> Embedded error: Unable to compile class for JSP
>> Strange error message about JAVA_HOME, etc...
>>
>> Possible Solution/Work-around:
>> Update the pom.xml in the root directory to use version 1.4.5-
>> SNAPSHOT
>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
>> planning to make 1.4.5 an official release for this. We're not
>> sure why
>> it gets us around the problem so it may be a red herring.
>>
>
> Its not a red herring. It gets you around the problem because in
> 1.4.5
> I actually hunt down the tools.jar file...in a similar fashion as done
> in Ant when running the jspc complier from there. i.e.:
>
> <taskdef classname="org.apache.jasper.JspC" name="jasper2" >
> <classpath>
> <pathelement location="${java.home}/../lib/tools.jar"/>
> ...
>
> I have to duplicate that in code. That's why 1.4.5 works.
>
> The release is under vote. So far no -1s. I think I will be able to
> release it today as the 72 hours is up. I'll let this list know
> when I
> have released it.
>
> Jeff
Re: windows build hell
Posted by Jeff Genender <jg...@apache.org>.
Joe Bohn wrote:
> 2) JSP compilation errors
> Problem:
> Embedded error: Unable to compile class for JSP
> Strange error message about JAVA_HOME, etc...
>
> Possible Solution/Work-around:
> Update the pom.xml in the root directory to use version 1.4.5-SNAPSHOT
> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
> planning to make 1.4.5 an official release for this. We're not sure why
> it gets us around the problem so it may be a red herring.
>
Its not a red herring. It gets you around the problem because in 1.4.5
I actually hunt down the tools.jar file...in a similar fashion as done
in Ant when running the jspc complier from there. i.e.:
<taskdef classname="org.apache.jasper.JspC" name="jasper2" >
<classpath>
<pathelement location="${java.home}/../lib/tools.jar"/>
...
I have to duplicate that in code. That's why 1.4.5 works.
The release is under vote. So far no -1s. I think I will be able to
release it today as the 72 hours is up. I'll let this list know when I
have released it.
Jeff
Re: windows build hell
Posted by Kevan Miller <ke...@gmail.com>.
On Aug 30, 2006, at 11:36 AM, Joe Bohn wrote:
>
> We've been struggling with build problems on windows for some time
> now and things just keep on getting worse.
>
> I'm composing this note to summarize the problems that I'm aware of
> with work-arounds and possible solutions. I'm also fishing to see
> if anybody else has some ideas on how to resolve these issues.
>
> 1) Windows pathlength problem.
> Problem:
> There are miscellaneous failures that can typically be tracked down
> to the windows pathlength problem. The nature of our repository
> structure and deployment make this a big problem. It also seems
> like we're continuing to add more intermediate elements in path
> names as we try to get things more organized and conform to Maven 2
> conventions.
>
> Work-around:
> The work-around is to keep the windows root path as small as
> possible. I now typically build from a root path of c:\g to avoid
> these problems.
>
> Possible Solution:
> For a longer term solution I'm planning to work on a new repository
> implementation in 1.2 that that isn't as redundant or verbose.
I agree. Addressing this issue is overdue... I'd just been thinking
about adding it to the 1.2 list, also...
> 3) Openejb2 test failures.
> Problem:
> Caused by: java.lang.NoSuchMethodException:
> org.openejb.deployment.DeploymentTestSuite.getName()
>
> Work-around:
> After bootstrap failure cd to <root>\target\external\openejb2
> "mvn -Dmaven.test.skip=true"
> cd back to <root>
> "mvn clean install"
>
> Possible solution:
> Dain suggested adding the "getName" method to the test. However,
> when I attempted this I hit other errors.
> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
> I think it would be helpful if we could disable the openejb tests
> until this problem is resolved.
It it's really useful, I guess it could be disabled. However, I think
we should live with the workaround. Whatever is causing this problem
needs to be identified and fixed. Is this a windows only problem? Or
a general problem?
>
>
>
> 4) Blue screen of death (bsod)
Building Geronimo may be the cause, but hard to fault Geronimo...
You're on your own with this one... :-P
--kevan
Re: windows build hell
Posted by Jason Dillon <ja...@planet57.com>.
Of course you can create a file with "." as the initial character in
Windows... how do you think the ~/.m2/ directory gets created?
_Windows Explorer_ might not like to allow that... but that does not
mean that it is not possible to do so... its just crappy microsoft
software trying to be intelligent and ending up being dumb as
rocks... again.
--jason
On Aug 30, 2006, at 1:25 PM, Hernan Cunico wrote:
> Windows wont let you create a file with "." as the initial
> character, that's why I'm trying to force it in the command line.
>
> Is there any other alternative in windows?
>
> Cheers!
> Hernan
>
> Bill Dudney wrote:
>> I got rid of the OOME by putting
>> MAVEN_OPTS=-Xmx512m
>> into my ~/.mavenrc file
>> TTFN,
>> -bd-
>> On Aug 30, 2006, at 2:04 PM, Hernan Cunico wrote:
>>> I had experienced all these errors, in addition, the one I get
>>> the most is an annoying out of mem error
>>>
>>> ...
>>> [DEBUG] Trace
>>> java.lang.OutOfMemoryError
>>> [INFO] ------------------------------------------
>>> [INFO] Total time: 38 seconds
>>> [INFO] Finished at: Wed Aug 30 15:50:06 EDT 2006
>>> [INFO] Final Memory: 43M/63M
>>> [INFO] ------------------------------------------
>>>
>>> I tried to increase the mvn heap sz by adding to the command -
>>> DMAVEN_OPTS=-Xmx512m. It does not seem to work, any suggestions?
>>>
>>> Cheers!
>>> Hernan
>>>
>>> Joe Bohn wrote:
>>>> We've been struggling with build problems on windows for some
>>>> time now and things just keep on getting worse.
>>>> I'm composing this note to summarize the problems that I'm aware
>>>> of with work-arounds and possible solutions. I'm also fishing
>>>> to see if anybody else has some ideas on how to resolve these
>>>> issues.
>>>> 1) Windows pathlength problem.
>>>> Problem:
>>>> There are miscellaneous failures that can typically be tracked
>>>> down to the windows pathlength problem. The nature of our
>>>> repository structure and deployment make this a big problem.
>>>> It also seems like we're continuing to add more intermediate
>>>> elements in path names as we try to get things more organized
>>>> and conform to Maven 2 conventions.
>>>> Work-around:
>>>> The work-around is to keep the windows root path as small as
>>>> possible. I now typically build from a root path of c:\g to
>>>> avoid these problems.
>>>> Possible Solution:
>>>> For a longer term solution I'm planning to work on a new
>>>> repository implementation in 1.2 that that isn't as redundant or
>>>> verbose.
>>>> 2) JSP compilation errors
>>>> Problem:
>>>> Embedded error: Unable to compile class for JSP
>>>> Strange error message about JAVA_HOME, etc...
>>>> Possible Solution/Work-around:
>>>> Update the pom.xml in the root directory to use version 1.4.5-
>>>> SNAPSHOT (from 1.4.4) for the jspc-maven-plugin. Not sure if
>>>> Jeff Genender is planning to make 1.4.5 an official release for
>>>> this. We're not sure why it gets us around the problem so it
>>>> may be a red herring.
>>>> 3) Openejb2 test failures.
>>>> Problem:
>>>> Caused by: java.lang.NoSuchMethodException:
>>>> org.openejb.deployment.DeploymentTestSuite.getName()
>>>> Work-around:
>>>> After bootstrap failure cd to <root>\target\external\openejb2
>>>> "mvn -Dmaven.test.skip=true"
>>>> cd back to <root>
>>>> "mvn clean install"
>>>> Possible solution:
>>>> Dain suggested adding the "getName" method to the test.
>>>> However, when I attempted this I hit other errors.
>>>> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
>>>> I think it would be helpful if we could disable the openejb
>>>> tests until this problem is resolved.
>>>> 4) Blue screen of death (bsod)
>>>> Problem:
>>>> This has been reported by multiple users on various machines.
>>>> When running an M1 or M2 build the user encounters a bsod due to
>>>> a memory failure.
>>>> PAGE_FAULT_IN_NONPAGED_AREA
>>>> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B,
>>>> 0x00000000)
>>>> Dump of physical memory
>>>> Work-around/Possible Solution:
>>>> Haven't found one yet. I've tried updated drivers, replaced
>>>> hardware, tried various heap size settings, etc.... At times
>>>> this can be fairly frequent (every 3rd build attempt or so).
>>>> I'm collecting bootstrap.log files from folks when this happens
>>>> during a bootstrap to see if there is a common thread. So far,
>>>> with the bootstrap logs, it always seems to happen at about the
>>>> same place:
>>>> Running tests after building a module (usually
>>>> tomcat.ApplicationTest or TomcatModuleBuilderTest) and the final
>>>> lines in the log are always the Creation of an MBeanServer like
>>>> this:
>>>> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
>>>> [exec] Created MBeanServer with ID:
>>>> 5dcec6:10d5a184aed:-8000:jbohn2:1
>>>> Please respond to this note if you are seeing the bsod failures
>>>> on windows. At first I thought this was just me and was
>>>> hardware related. However, the more I talk to folks on windows
>>>> the more I hear of other folks encountering this same problem.
>>>> I've updated all drivers, replaced my entire system, and several
>>>> other folks have reported seeing this on completely different
>>>> systems. I think that pretty much rules out a hardware problem.
>>>> ideas welcome!
>>>> Joe
Re: windows build hell
Posted by Hernan Cunico <hc...@gmail.com>.
What seems to have worked was to set that value as an environment variable
set MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m
That took care of the OOME -> Thanks Joe !!!
Still having fun with other build errors though.
Cheers!
Hernan
Paul McMahan wrote:
> You can create a filename starting with "." from a command window.
>
> Paul
>
> On 8/30/06, Hernan Cunico <hc...@gmail.com> wrote:
>> Windows wont let you create a file with "." as the initial character,
>> that's why I'm trying to force it in the command line.
>>
>> Is there any other alternative in windows?
>>
>> Cheers!
>> Hernan
>>
>> Bill Dudney wrote:
>> > I got rid of the OOME by putting
>> >
>> > MAVEN_OPTS=-Xmx512m
>> >
>> > into my ~/.mavenrc file
>> >
>> > TTFN,
>> >
>> > -bd-
>> >
>> > On Aug 30, 2006, at 2:04 PM, Hernan Cunico wrote:
>> >
>> >> I had experienced all these errors, in addition, the one I get the
>> >> most is an annoying out of mem error
>> >>
>> >> ...
>> >> [DEBUG] Trace
>> >> java.lang.OutOfMemoryError
>> >> [INFO] ------------------------------------------
>> >> [INFO] Total time: 38 seconds
>> >> [INFO] Finished at: Wed Aug 30 15:50:06 EDT 2006
>> >> [INFO] Final Memory: 43M/63M
>> >> [INFO] ------------------------------------------
>> >>
>> >> I tried to increase the mvn heap sz by adding to the command
>> >> -DMAVEN_OPTS=-Xmx512m. It does not seem to work, any suggestions?
>> >>
>> >> Cheers!
>> >> Hernan
>> >>
>> >> Joe Bohn wrote:
>> >>> We've been struggling with build problems on windows for some time
>> >>> now and things just keep on getting worse.
>> >>> I'm composing this note to summarize the problems that I'm aware of
>> >>> with work-arounds and possible solutions. I'm also fishing to see
>> >>> if anybody else has some ideas on how to resolve these issues.
>> >>> 1) Windows pathlength problem.
>> >>> Problem:
>> >>> There are miscellaneous failures that can typically be tracked down
>> >>> to the windows pathlength problem. The nature of our repository
>> >>> structure and deployment make this a big problem. It also seems
>> >>> like we're continuing to add more intermediate elements in path names
>> >>> as we try to get things more organized and conform to Maven 2
>> >>> conventions.
>> >>> Work-around:
>> >>> The work-around is to keep the windows root path as small as
>> >>> possible. I now typically build from a root path of c:\g to avoid
>> >>> these problems.
>> >>> Possible Solution:
>> >>> For a longer term solution I'm planning to work on a new repository
>> >>> implementation in 1.2 that that isn't as redundant or verbose.
>> >>> 2) JSP compilation errors
>> >>> Problem:
>> >>> Embedded error: Unable to compile class for JSP
>> >>> Strange error message about JAVA_HOME, etc...
>> >>> Possible Solution/Work-around:
>> >>> Update the pom.xml in the root directory to use version
>> >>> 1.4.5-SNAPSHOT (from 1.4.4) for the jspc-maven-plugin. Not sure if
>> >>> Jeff Genender is planning to make 1.4.5 an official release for
>> >>> this. We're not sure why it gets us around the problem so it may be
>> >>> a red herring.
>> >>> 3) Openejb2 test failures.
>> >>> Problem:
>> >>> Caused by: java.lang.NoSuchMethodException:
>> >>> org.openejb.deployment.DeploymentTestSuite.getName()
>> >>> Work-around:
>> >>> After bootstrap failure cd to <root>\target\external\openejb2
>> >>> "mvn -Dmaven.test.skip=true"
>> >>> cd back to <root>
>> >>> "mvn clean install"
>> >>> Possible solution:
>> >>> Dain suggested adding the "getName" method to the test. However,
>> >>> when I attempted this I hit other errors.
>> >>> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
>> >>> I think it would be helpful if we could disable the openejb tests
>> >>> until this problem is resolved.
>> >>> 4) Blue screen of death (bsod)
>> >>> Problem:
>> >>> This has been reported by multiple users on various machines. When
>> >>> running an M1 or M2 build the user encounters a bsod due to a memory
>> >>> failure.
>> >>> PAGE_FAULT_IN_NONPAGED_AREA
>> >>> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B,
>> 0x00000000)
>> >>> Dump of physical memory
>> >>> Work-around/Possible Solution:
>> >>> Haven't found one yet. I've tried updated drivers, replaced
>> >>> hardware, tried various heap size settings, etc.... At times this
>> >>> can be fairly frequent (every 3rd build attempt or so). I'm
>> >>> collecting bootstrap.log files from folks when this happens during a
>> >>> bootstrap to see if there is a common thread. So far, with the
>> >>> bootstrap logs, it always seems to happen at about the same place:
>> >>> Running tests after building a module (usually tomcat.ApplicationTest
>> >>> or TomcatModuleBuilderTest) and the final lines in the log are always
>> >>> the Creation of an MBeanServer like this:
>> >>> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
>> >>> [exec] Created MBeanServer with ID:
>> 5dcec6:10d5a184aed:-8000:jbohn2:1
>> >>> Please respond to this note if you are seeing the bsod failures on
>> >>> windows. At first I thought this was just me and was hardware
>> >>> related. However, the more I talk to folks on windows the more I
>> >>> hear of other folks encountering this same problem. I've updated all
>> >>> drivers, replaced my entire system, and several other folks have
>> >>> reported seeing this on completely different systems. I think that
>> >>> pretty much rules out a hardware problem.
>> >>> ideas welcome!
>> >>> Joe
>> >
>> >
>>
>
Re: windows build hell
Posted by Paul McMahan <pa...@gmail.com>.
You can create a filename starting with "." from a command window.
Paul
On 8/30/06, Hernan Cunico <hc...@gmail.com> wrote:
> Windows wont let you create a file with "." as the initial character,
> that's why I'm trying to force it in the command line.
>
> Is there any other alternative in windows?
>
> Cheers!
> Hernan
>
> Bill Dudney wrote:
> > I got rid of the OOME by putting
> >
> > MAVEN_OPTS=-Xmx512m
> >
> > into my ~/.mavenrc file
> >
> > TTFN,
> >
> > -bd-
> >
> > On Aug 30, 2006, at 2:04 PM, Hernan Cunico wrote:
> >
> >> I had experienced all these errors, in addition, the one I get the
> >> most is an annoying out of mem error
> >>
> >> ...
> >> [DEBUG] Trace
> >> java.lang.OutOfMemoryError
> >> [INFO] ------------------------------------------
> >> [INFO] Total time: 38 seconds
> >> [INFO] Finished at: Wed Aug 30 15:50:06 EDT 2006
> >> [INFO] Final Memory: 43M/63M
> >> [INFO] ------------------------------------------
> >>
> >> I tried to increase the mvn heap sz by adding to the command
> >> -DMAVEN_OPTS=-Xmx512m. It does not seem to work, any suggestions?
> >>
> >> Cheers!
> >> Hernan
> >>
> >> Joe Bohn wrote:
> >>> We've been struggling with build problems on windows for some time
> >>> now and things just keep on getting worse.
> >>> I'm composing this note to summarize the problems that I'm aware of
> >>> with work-arounds and possible solutions. I'm also fishing to see
> >>> if anybody else has some ideas on how to resolve these issues.
> >>> 1) Windows pathlength problem.
> >>> Problem:
> >>> There are miscellaneous failures that can typically be tracked down
> >>> to the windows pathlength problem. The nature of our repository
> >>> structure and deployment make this a big problem. It also seems
> >>> like we're continuing to add more intermediate elements in path names
> >>> as we try to get things more organized and conform to Maven 2
> >>> conventions.
> >>> Work-around:
> >>> The work-around is to keep the windows root path as small as
> >>> possible. I now typically build from a root path of c:\g to avoid
> >>> these problems.
> >>> Possible Solution:
> >>> For a longer term solution I'm planning to work on a new repository
> >>> implementation in 1.2 that that isn't as redundant or verbose.
> >>> 2) JSP compilation errors
> >>> Problem:
> >>> Embedded error: Unable to compile class for JSP
> >>> Strange error message about JAVA_HOME, etc...
> >>> Possible Solution/Work-around:
> >>> Update the pom.xml in the root directory to use version
> >>> 1.4.5-SNAPSHOT (from 1.4.4) for the jspc-maven-plugin. Not sure if
> >>> Jeff Genender is planning to make 1.4.5 an official release for
> >>> this. We're not sure why it gets us around the problem so it may be
> >>> a red herring.
> >>> 3) Openejb2 test failures.
> >>> Problem:
> >>> Caused by: java.lang.NoSuchMethodException:
> >>> org.openejb.deployment.DeploymentTestSuite.getName()
> >>> Work-around:
> >>> After bootstrap failure cd to <root>\target\external\openejb2
> >>> "mvn -Dmaven.test.skip=true"
> >>> cd back to <root>
> >>> "mvn clean install"
> >>> Possible solution:
> >>> Dain suggested adding the "getName" method to the test. However,
> >>> when I attempted this I hit other errors.
> >>> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
> >>> I think it would be helpful if we could disable the openejb tests
> >>> until this problem is resolved.
> >>> 4) Blue screen of death (bsod)
> >>> Problem:
> >>> This has been reported by multiple users on various machines. When
> >>> running an M1 or M2 build the user encounters a bsod due to a memory
> >>> failure.
> >>> PAGE_FAULT_IN_NONPAGED_AREA
> >>> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B, 0x00000000)
> >>> Dump of physical memory
> >>> Work-around/Possible Solution:
> >>> Haven't found one yet. I've tried updated drivers, replaced
> >>> hardware, tried various heap size settings, etc.... At times this
> >>> can be fairly frequent (every 3rd build attempt or so). I'm
> >>> collecting bootstrap.log files from folks when this happens during a
> >>> bootstrap to see if there is a common thread. So far, with the
> >>> bootstrap logs, it always seems to happen at about the same place:
> >>> Running tests after building a module (usually tomcat.ApplicationTest
> >>> or TomcatModuleBuilderTest) and the final lines in the log are always
> >>> the Creation of an MBeanServer like this:
> >>> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
> >>> [exec] Created MBeanServer with ID: 5dcec6:10d5a184aed:-8000:jbohn2:1
> >>> Please respond to this note if you are seeing the bsod failures on
> >>> windows. At first I thought this was just me and was hardware
> >>> related. However, the more I talk to folks on windows the more I
> >>> hear of other folks encountering this same problem. I've updated all
> >>> drivers, replaced my entire system, and several other folks have
> >>> reported seeing this on completely different systems. I think that
> >>> pretty much rules out a hardware problem.
> >>> ideas welcome!
> >>> Joe
> >
> >
>
Re: windows build hell
Posted by Hernan Cunico <hc...@gmail.com>.
Windows wont let you create a file with "." as the initial character,
that's why I'm trying to force it in the command line.
Is there any other alternative in windows?
Cheers!
Hernan
Bill Dudney wrote:
> I got rid of the OOME by putting
>
> MAVEN_OPTS=-Xmx512m
>
> into my ~/.mavenrc file
>
> TTFN,
>
> -bd-
>
> On Aug 30, 2006, at 2:04 PM, Hernan Cunico wrote:
>
>> I had experienced all these errors, in addition, the one I get the
>> most is an annoying out of mem error
>>
>> ...
>> [DEBUG] Trace
>> java.lang.OutOfMemoryError
>> [INFO] ------------------------------------------
>> [INFO] Total time: 38 seconds
>> [INFO] Finished at: Wed Aug 30 15:50:06 EDT 2006
>> [INFO] Final Memory: 43M/63M
>> [INFO] ------------------------------------------
>>
>> I tried to increase the mvn heap sz by adding to the command
>> -DMAVEN_OPTS=-Xmx512m. It does not seem to work, any suggestions?
>>
>> Cheers!
>> Hernan
>>
>> Joe Bohn wrote:
>>> We've been struggling with build problems on windows for some time
>>> now and things just keep on getting worse.
>>> I'm composing this note to summarize the problems that I'm aware of
>>> with work-arounds and possible solutions. I'm also fishing to see
>>> if anybody else has some ideas on how to resolve these issues.
>>> 1) Windows pathlength problem.
>>> Problem:
>>> There are miscellaneous failures that can typically be tracked down
>>> to the windows pathlength problem. The nature of our repository
>>> structure and deployment make this a big problem. It also seems
>>> like we're continuing to add more intermediate elements in path names
>>> as we try to get things more organized and conform to Maven 2
>>> conventions.
>>> Work-around:
>>> The work-around is to keep the windows root path as small as
>>> possible. I now typically build from a root path of c:\g to avoid
>>> these problems.
>>> Possible Solution:
>>> For a longer term solution I'm planning to work on a new repository
>>> implementation in 1.2 that that isn't as redundant or verbose.
>>> 2) JSP compilation errors
>>> Problem:
>>> Embedded error: Unable to compile class for JSP
>>> Strange error message about JAVA_HOME, etc...
>>> Possible Solution/Work-around:
>>> Update the pom.xml in the root directory to use version
>>> 1.4.5-SNAPSHOT (from 1.4.4) for the jspc-maven-plugin. Not sure if
>>> Jeff Genender is planning to make 1.4.5 an official release for
>>> this. We're not sure why it gets us around the problem so it may be
>>> a red herring.
>>> 3) Openejb2 test failures.
>>> Problem:
>>> Caused by: java.lang.NoSuchMethodException:
>>> org.openejb.deployment.DeploymentTestSuite.getName()
>>> Work-around:
>>> After bootstrap failure cd to <root>\target\external\openejb2
>>> "mvn -Dmaven.test.skip=true"
>>> cd back to <root>
>>> "mvn clean install"
>>> Possible solution:
>>> Dain suggested adding the "getName" method to the test. However,
>>> when I attempted this I hit other errors.
>>> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
>>> I think it would be helpful if we could disable the openejb tests
>>> until this problem is resolved.
>>> 4) Blue screen of death (bsod)
>>> Problem:
>>> This has been reported by multiple users on various machines. When
>>> running an M1 or M2 build the user encounters a bsod due to a memory
>>> failure.
>>> PAGE_FAULT_IN_NONPAGED_AREA
>>> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B, 0x00000000)
>>> Dump of physical memory
>>> Work-around/Possible Solution:
>>> Haven't found one yet. I've tried updated drivers, replaced
>>> hardware, tried various heap size settings, etc.... At times this
>>> can be fairly frequent (every 3rd build attempt or so). I'm
>>> collecting bootstrap.log files from folks when this happens during a
>>> bootstrap to see if there is a common thread. So far, with the
>>> bootstrap logs, it always seems to happen at about the same place:
>>> Running tests after building a module (usually tomcat.ApplicationTest
>>> or TomcatModuleBuilderTest) and the final lines in the log are always
>>> the Creation of an MBeanServer like this:
>>> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
>>> [exec] Created MBeanServer with ID: 5dcec6:10d5a184aed:-8000:jbohn2:1
>>> Please respond to this note if you are seeing the bsod failures on
>>> windows. At first I thought this was just me and was hardware
>>> related. However, the more I talk to folks on windows the more I
>>> hear of other folks encountering this same problem. I've updated all
>>> drivers, replaced my entire system, and several other folks have
>>> reported seeing this on completely different systems. I think that
>>> pretty much rules out a hardware problem.
>>> ideas welcome!
>>> Joe
>
>
Re: windows build hell
Posted by Bill Dudney <bd...@apache.org>.
I got rid of the OOME by putting
MAVEN_OPTS=-Xmx512m
into my ~/.mavenrc file
TTFN,
-bd-
On Aug 30, 2006, at 2:04 PM, Hernan Cunico wrote:
> I had experienced all these errors, in addition, the one I get the
> most is an annoying out of mem error
>
> ...
> [DEBUG] Trace
> java.lang.OutOfMemoryError
> [INFO] ------------------------------------------
> [INFO] Total time: 38 seconds
> [INFO] Finished at: Wed Aug 30 15:50:06 EDT 2006
> [INFO] Final Memory: 43M/63M
> [INFO] ------------------------------------------
>
> I tried to increase the mvn heap sz by adding to the command -
> DMAVEN_OPTS=-Xmx512m. It does not seem to work, any suggestions?
>
> Cheers!
> Hernan
>
> Joe Bohn wrote:
>> We've been struggling with build problems on windows for some time
>> now and things just keep on getting worse.
>> I'm composing this note to summarize the problems that I'm aware
>> of with work-arounds and possible solutions. I'm also fishing to
>> see if anybody else has some ideas on how to resolve these issues.
>> 1) Windows pathlength problem.
>> Problem:
>> There are miscellaneous failures that can typically be tracked
>> down to the windows pathlength problem. The nature of our
>> repository structure and deployment make this a big problem. It
>> also seems like we're continuing to add more intermediate elements
>> in path names as we try to get things more organized and conform
>> to Maven 2 conventions.
>> Work-around:
>> The work-around is to keep the windows root path as small as
>> possible. I now typically build from a root path of c:\g to avoid
>> these problems.
>> Possible Solution:
>> For a longer term solution I'm planning to work on a new
>> repository implementation in 1.2 that that isn't as redundant or
>> verbose.
>> 2) JSP compilation errors
>> Problem:
>> Embedded error: Unable to compile class for JSP
>> Strange error message about JAVA_HOME, etc...
>> Possible Solution/Work-around:
>> Update the pom.xml in the root directory to use version 1.4.5-
>> SNAPSHOT (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff
>> Genender is planning to make 1.4.5 an official release for this.
>> We're not sure why it gets us around the problem so it may be a
>> red herring.
>> 3) Openejb2 test failures.
>> Problem:
>> Caused by: java.lang.NoSuchMethodException:
>> org.openejb.deployment.DeploymentTestSuite.getName()
>> Work-around:
>> After bootstrap failure cd to <root>\target\external\openejb2
>> "mvn -Dmaven.test.skip=true"
>> cd back to <root>
>> "mvn clean install"
>> Possible solution:
>> Dain suggested adding the "getName" method to the test. However,
>> when I attempted this I hit other errors.
>> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
>> I think it would be helpful if we could disable the openejb tests
>> until this problem is resolved.
>> 4) Blue screen of death (bsod)
>> Problem:
>> This has been reported by multiple users on various machines.
>> When running an M1 or M2 build the user encounters a bsod due to a
>> memory failure.
>> PAGE_FAULT_IN_NONPAGED_AREA
>> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B,
>> 0x00000000)
>> Dump of physical memory
>> Work-around/Possible Solution:
>> Haven't found one yet. I've tried updated drivers, replaced
>> hardware, tried various heap size settings, etc.... At times this
>> can be fairly frequent (every 3rd build attempt or so). I'm
>> collecting bootstrap.log files from folks when this happens during
>> a bootstrap to see if there is a common thread. So far, with the
>> bootstrap logs, it always seems to happen at about the same place:
>> Running tests after building a module (usually
>> tomcat.ApplicationTest or TomcatModuleBuilderTest) and the final
>> lines in the log are always the Creation of an MBeanServer like this:
>> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
>> [exec] Created MBeanServer with ID:
>> 5dcec6:10d5a184aed:-8000:jbohn2:1
>> Please respond to this note if you are seeing the bsod failures on
>> windows. At first I thought this was just me and was hardware
>> related. However, the more I talk to folks on windows the more I
>> hear of other folks encountering this same problem. I've updated
>> all drivers, replaced my entire system, and several other folks
>> have reported seeing this on completely different systems. I
>> think that pretty much rules out a hardware problem.
>> ideas welcome!
>> Joe
Re: windows build hell
Posted by Joe Bohn <jo...@earthlink.net>.
I can do the individual builds but I'm sure they'll be successful (or at
least successful most, if not all, of the time). The bsod is an
intermittent problem and I suspect that it has to do with high stress
scenarios during the "big" builds (where "big" means either bootstrap or
mvn install from root). I was getting it about every 3-6 attempts on
two different machines. I then got hold of a loaner machine, switched
my drive, and it took me 14 attempts to hit it again. However, after
that I hit it on the second attempt after reboot.
Joe
anita kulshreshtha wrote:
> It would be nice to know if tomcat-builder can be built using
> mvn -o clean install from the following directories after these errors:
> 1. modules directory
> 2. modules/geronimo-tomcat-builder directory
>
> Thanks
> Anita
>
> --- Joe Bohn <jo...@earthlink.net> wrote:
>
>
>
>>If you get a bsod while running a bootstrap please let me see your
>>bootstrap.log (or at least the end of it) to see if the pattern
>>remains
>>consistent. Since I sent this original note out I've heard from Rick
>>
>>McGuire with another bsod in TomcatModuleBuilderTest
>>
>>Joe
>
> .....................................
>
>
>>>>4) Blue screen of death (bsod)
>>>>Problem:
>>>>This has been reported by multiple users on various machines.
>>
>>When
>>
>>>>running an M1 or M2 build the user encounters a bsod due to a
>>
>>memory
>>
>>>>failure.
>>>>PAGE_FAULT_IN_NONPAGED_AREA
>>>> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B,
>>
>>0x00000000)
>>
>>>>Dump of physical memory
>>>>
>>>>Work-around/Possible Solution:
>>>>Haven't found one yet. I've tried updated drivers, replaced
>>
>>hardware,
>>
>>>>tried various heap size settings, etc.... At times this can be
>>
>>fairly
>>
>>>>frequent (every 3rd build attempt or so). I'm collecting
>>>>bootstrap.log files from folks when this happens during a
>>
>>bootstrap to
>>
>>>>see if there is a common thread. So far, with the bootstrap logs,
>>
>>it
>>
>>>>always seems to happen at about the same place:
>>>>Running tests after building a module (usually
>>
>>tomcat.ApplicationTest
>>
>>>>or TomcatModuleBuilderTest) and the final lines in the log are
>>
>>always
>>
>>>>the Creation of an MBeanServer like this:
>>>> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
>>>> [exec] Created MBeanServer with ID:
>>
>>5dcec6:10d5a184aed:-8000:jbohn2:1
>>
>>>>Please respond to this note if you are seeing the bsod failures on
>>
>>>>windows. At first I thought this was just me and was hardware
>>>>related. However, the more I talk to folks on windows the more I
>>
>>hear
>>
>>>>of other folks encountering this same problem. I've updated all
>>>>drivers, replaced my entire system, and several other folks have
>>>>reported seeing this on completely different systems. I think
>>
>>that
>>
>>>>pretty much rules out a hardware problem.
>>>>
>>>>ideas welcome!
>>>>
>>>>Joe
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
Re: windows build hell
Posted by anita kulshreshtha <a_...@yahoo.com>.
It would be nice to know if tomcat-builder can be built using
mvn -o clean install from the following directories after these errors:
1. modules directory
2. modules/geronimo-tomcat-builder directory
Thanks
Anita
--- Joe Bohn <jo...@earthlink.net> wrote:
> If you get a bsod while running a bootstrap please let me see your
> bootstrap.log (or at least the end of it) to see if the pattern
> remains
> consistent. Since I sent this original note out I've heard from Rick
>
> McGuire with another bsod in TomcatModuleBuilderTest
>
> Joe
.....................................
> >> 4) Blue screen of death (bsod)
> >> Problem:
> >> This has been reported by multiple users on various machines.
> When
> >> running an M1 or M2 build the user encounters a bsod due to a
> memory
> >> failure.
> >> PAGE_FAULT_IN_NONPAGED_AREA
> >> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B,
> 0x00000000)
> >> Dump of physical memory
> >>
> >> Work-around/Possible Solution:
> >> Haven't found one yet. I've tried updated drivers, replaced
> hardware,
> >> tried various heap size settings, etc.... At times this can be
> fairly
> >> frequent (every 3rd build attempt or so). I'm collecting
> >> bootstrap.log files from folks when this happens during a
> bootstrap to
> >> see if there is a common thread. So far, with the bootstrap logs,
> it
> >> always seems to happen at about the same place:
> >> Running tests after building a module (usually
> tomcat.ApplicationTest
> >> or TomcatModuleBuilderTest) and the final lines in the log are
> always
> >> the Creation of an MBeanServer like this:
> >> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
> >> [exec] Created MBeanServer with ID:
> 5dcec6:10d5a184aed:-8000:jbohn2:1
> >>
> >> Please respond to this note if you are seeing the bsod failures on
>
> >> windows. At first I thought this was just me and was hardware
> >> related. However, the more I talk to folks on windows the more I
> hear
> >> of other folks encountering this same problem. I've updated all
> >> drivers, replaced my entire system, and several other folks have
> >> reported seeing this on completely different systems. I think
> that
> >> pretty much rules out a hardware problem.
> >>
> >> ideas welcome!
> >>
> >> Joe
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: windows build hell
Posted by Joe Bohn <jo...@earthlink.net>.
Hi Hernan,
I run with the following environment variable set (I think John Sisson
recommended these settings) and it has resolved the OOM errors for me.
I think your specification on the mvn command should have accomplished
the heap setting part but perhaps you need the MaxPermSize too (or
perhaps it isn't picking it up from the command).
MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128m
If you get a bsod while running a bootstrap please let me see your
bootstrap.log (or at least the end of it) to see if the pattern remains
consistent. Since I sent this original note out I've heard from Rick
McGuire with another bsod in TomcatModuleBuilderTest
Joe
Hernan Cunico wrote:
> I had experienced all these errors, in addition, the one I get the most
> is an annoying out of mem error
>
> ...
> [DEBUG] Trace
> java.lang.OutOfMemoryError
> [INFO] ------------------------------------------
> [INFO] Total time: 38 seconds
> [INFO] Finished at: Wed Aug 30 15:50:06 EDT 2006
> [INFO] Final Memory: 43M/63M
> [INFO] ------------------------------------------
>
> I tried to increase the mvn heap sz by adding to the command
> -DMAVEN_OPTS=-Xmx512m. It does not seem to work, any suggestions?
>
> Cheers!
> Hernan
>
> Joe Bohn wrote:
>
>>
>> We've been struggling with build problems on windows for some time now
>> and things just keep on getting worse.
>>
>> I'm composing this note to summarize the problems that I'm aware of
>> with work-arounds and possible solutions. I'm also fishing to see if
>> anybody else has some ideas on how to resolve these issues.
>>
>> 1) Windows pathlength problem.
>> Problem:
>> There are miscellaneous failures that can typically be tracked down to
>> the windows pathlength problem. The nature of our repository
>> structure and deployment make this a big problem. It also seems like
>> we're continuing to add more intermediate elements in path names as we
>> try to get things more organized and conform to Maven 2 conventions.
>>
>> Work-around:
>> The work-around is to keep the windows root path as small as possible.
>> I now typically build from a root path of c:\g to avoid these problems.
>>
>> Possible Solution:
>> For a longer term solution I'm planning to work on a new repository
>> implementation in 1.2 that that isn't as redundant or verbose.
>>
>>
>>
>> 2) JSP compilation errors
>> Problem:
>> Embedded error: Unable to compile class for JSP
>> Strange error message about JAVA_HOME, etc...
>>
>> Possible Solution/Work-around:
>> Update the pom.xml in the root directory to use version 1.4.5-SNAPSHOT
>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
>> planning to make 1.4.5 an official release for this. We're not sure
>> why it gets us around the problem so it may be a red herring.
>>
>>
>>
>> 3) Openejb2 test failures.
>> Problem:
>> Caused by: java.lang.NoSuchMethodException:
>> org.openejb.deployment.DeploymentTestSuite.getName()
>>
>> Work-around:
>> After bootstrap failure cd to <root>\target\external\openejb2
>> "mvn -Dmaven.test.skip=true"
>> cd back to <root>
>> "mvn clean install"
>>
>> Possible solution:
>> Dain suggested adding the "getName" method to the test. However, when
>> I attempted this I hit other errors.
>> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
>> I think it would be helpful if we could disable the openejb tests
>> until this problem is resolved.
>>
>>
>>
>> 4) Blue screen of death (bsod)
>> Problem:
>> This has been reported by multiple users on various machines. When
>> running an M1 or M2 build the user encounters a bsod due to a memory
>> failure.
>> PAGE_FAULT_IN_NONPAGED_AREA
>> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B, 0x00000000)
>> Dump of physical memory
>>
>> Work-around/Possible Solution:
>> Haven't found one yet. I've tried updated drivers, replaced hardware,
>> tried various heap size settings, etc.... At times this can be fairly
>> frequent (every 3rd build attempt or so). I'm collecting
>> bootstrap.log files from folks when this happens during a bootstrap to
>> see if there is a common thread. So far, with the bootstrap logs, it
>> always seems to happen at about the same place:
>> Running tests after building a module (usually tomcat.ApplicationTest
>> or TomcatModuleBuilderTest) and the final lines in the log are always
>> the Creation of an MBeanServer like this:
>> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
>> [exec] Created MBeanServer with ID: 5dcec6:10d5a184aed:-8000:jbohn2:1
>>
>> Please respond to this note if you are seeing the bsod failures on
>> windows. At first I thought this was just me and was hardware
>> related. However, the more I talk to folks on windows the more I hear
>> of other folks encountering this same problem. I've updated all
>> drivers, replaced my entire system, and several other folks have
>> reported seeing this on completely different systems. I think that
>> pretty much rules out a hardware problem.
>>
>> ideas welcome!
>>
>> Joe
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Re: windows build hell
Posted by Hernan Cunico <hc...@gmail.com>.
I had experienced all these errors, in addition, the one I get the most
is an annoying out of mem error
...
[DEBUG] Trace
java.lang.OutOfMemoryError
[INFO] ------------------------------------------
[INFO] Total time: 38 seconds
[INFO] Finished at: Wed Aug 30 15:50:06 EDT 2006
[INFO] Final Memory: 43M/63M
[INFO] ------------------------------------------
I tried to increase the mvn heap sz by adding to the command
-DMAVEN_OPTS=-Xmx512m. It does not seem to work, any suggestions?
Cheers!
Hernan
Joe Bohn wrote:
>
> We've been struggling with build problems on windows for some time now
> and things just keep on getting worse.
>
> I'm composing this note to summarize the problems that I'm aware of with
> work-arounds and possible solutions. I'm also fishing to see if
> anybody else has some ideas on how to resolve these issues.
>
> 1) Windows pathlength problem.
> Problem:
> There are miscellaneous failures that can typically be tracked down to
> the windows pathlength problem. The nature of our repository structure
> and deployment make this a big problem. It also seems like we're
> continuing to add more intermediate elements in path names as we try to
> get things more organized and conform to Maven 2 conventions.
>
> Work-around:
> The work-around is to keep the windows root path as small as possible. I
> now typically build from a root path of c:\g to avoid these problems.
>
> Possible Solution:
> For a longer term solution I'm planning to work on a new repository
> implementation in 1.2 that that isn't as redundant or verbose.
>
>
>
> 2) JSP compilation errors
> Problem:
> Embedded error: Unable to compile class for JSP
> Strange error message about JAVA_HOME, etc...
>
> Possible Solution/Work-around:
> Update the pom.xml in the root directory to use version 1.4.5-SNAPSHOT
> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
> planning to make 1.4.5 an official release for this. We're not sure why
> it gets us around the problem so it may be a red herring.
>
>
>
> 3) Openejb2 test failures.
> Problem:
> Caused by: java.lang.NoSuchMethodException:
> org.openejb.deployment.DeploymentTestSuite.getName()
>
> Work-around:
> After bootstrap failure cd to <root>\target\external\openejb2
> "mvn -Dmaven.test.skip=true"
> cd back to <root>
> "mvn clean install"
>
> Possible solution:
> Dain suggested adding the "getName" method to the test. However, when I
> attempted this I hit other errors.
> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
> I think it would be helpful if we could disable the openejb tests until
> this problem is resolved.
>
>
>
> 4) Blue screen of death (bsod)
> Problem:
> This has been reported by multiple users on various machines. When
> running an M1 or M2 build the user encounters a bsod due to a memory
> failure.
> PAGE_FAULT_IN_NONPAGED_AREA
> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B, 0x00000000)
> Dump of physical memory
>
> Work-around/Possible Solution:
> Haven't found one yet. I've tried updated drivers, replaced hardware,
> tried various heap size settings, etc.... At times this can be fairly
> frequent (every 3rd build attempt or so). I'm collecting bootstrap.log
> files from folks when this happens during a bootstrap to see if there is
> a common thread. So far, with the bootstrap logs, it always seems to
> happen at about the same place:
> Running tests after building a module (usually tomcat.ApplicationTest or
> TomcatModuleBuilderTest) and the final lines in the log are always the
> Creation of an MBeanServer like this:
> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
> [exec] Created MBeanServer with ID: 5dcec6:10d5a184aed:-8000:jbohn2:1
>
> Please respond to this note if you are seeing the bsod failures on
> windows. At first I thought this was just me and was hardware related.
> However, the more I talk to folks on windows the more I hear of other
> folks encountering this same problem. I've updated all drivers,
> replaced my entire system, and several other folks have reported seeing
> this on completely different systems. I think that pretty much rules
> out a hardware problem.
>
> ideas welcome!
>
> Joe
>
>
>
>
>
>
>
>
>
Re: windows build hell
Posted by Jason Dillon <ja...@planet57.com>.
I agree that someone will always ask... and we just point them to the
URL with the docs.
No need to automate anything to complain... I'm not even sure how I
would go about doing that. I think it is fine to force Java 1.4 and
kill the build early if its not what we need... but I think the
directory name where you build from is a bit more user specific
preference.
I'd lean on the documentation here for these windows-specific
issues... or unless you are saying that windows users can't ready :-
P Do we need to make a little dancing paper clip animation to annoy
our users into reading the docs... or maybe even read it to them?
:-P
--jason
On Sep 1, 2006, at 8:56 AM, Jacek Laskowski wrote:
> On 9/1/06, Jason Dillon <ja...@planet57.com> wrote:
>> I would just tell windows users to use c:\g or map a directory to g:\
>> and be done with it.
>
> Yes, but it would help them a bit. No matter how much papers you're
> going to write they'll be some who will ask about it. I don't know how
> hard it would be to do it, but if it's not a big deal, I'd go for it.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.laskowski.net.pl
Re: windows build hell
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/1/06, Jason Dillon <ja...@planet57.com> wrote:
> I would just tell windows users to use c:\g or map a directory to g:\
> and be done with it.
Yes, but it would help them a bit. No matter how much papers you're
going to write they'll be some who will ask about it. I don't know how
hard it would be to do it, but if it's not a big deal, I'd go for it.
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: windows build hell
Posted by Jason Dillon <ja...@planet57.com>.
I would just tell windows users to use c:\g or map a directory to g:\
and be done with it.
No need to automate a check or anything fancy for the ugly OS.
--jason
On Sep 1, 2006, at 5:06 AM, Jacek Laskowski wrote:
> On 8/30/06, anita kulshreshtha <a_...@yahoo.com> wrote:
>
>> In the mean time could we warn our users that if they are using
>> windows, they should use a short root path. If everyone agrees, I
>> would
>> like to edit the M2build page on cwiki.
>
> CWiki is too far from people dev environments especially while they're
> building Geronimo offline (provided M2 is happy with all Geronimo
> deps). Since the Windows pathlength problem breaks the build, we
> should stop the build right away not warning people (as they likely
> disregard it or don't notice it at all). I'd go along the path Jason's
> laid out when the build checks out whether the jvm version is < 1.5.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.laskowski.net.pl
Re: windows build hell
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 8/30/06, anita kulshreshtha <a_...@yahoo.com> wrote:
> In the mean time could we warn our users that if they are using
> windows, they should use a short root path. If everyone agrees, I would
> like to edit the M2build page on cwiki.
CWiki is too far from people dev environments especially while they're
building Geronimo offline (provided M2 is happy with all Geronimo
deps). Since the Windows pathlength problem breaks the build, we
should stop the build right away not warning people (as they likely
disregard it or don't notice it at all). I'd go along the path Jason's
laid out when the build checks out whether the jvm version is < 1.5.
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: windows build hell
Posted by Prasad Kashyap <go...@gmail.com>.
The jspc problem is not limited to windows. It just failed with the
same error on a linux machine.
Cheers
Prasad
On 8/30/06, anita kulshreshtha <a_...@yahoo.com> wrote:
>
>
> --- Jeff Genender <jg...@apache.org> wrote:
>
> >
> >
> > anita kulshreshtha wrote:
> >
> > >> 2) JSP compilation errors
> > >> Problem:
> > >> Embedded error: Unable to compile class for JSP
> > >> Strange error message about JAVA_HOME, etc...
> > >>
> > >> Possible Solution/Work-around:
> > >> Update the pom.xml in the root directory to use version
> > >> 1.4.5-SNAPSHOT
> > >> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender
> > is
> > >>
> > >> planning to make 1.4.5 an official release for this. We're not
> > sure
> > >> why
> > >> it gets us around the problem so it may be a red herring.
> > >>
> > >
> > > I have seen this, but do not yet know why it happens. I would
> > like
> > > to comment out the following lines until the problem is resolved.
> > >
> > > 1. applications/geronimo-examples/pom.xml
> > > <module>geronimo-jsp-examples</module>
> > >
> > > 2. configs/pom.xml
> > > <module>jsp-examples-jetty</module>
> > > <module>jsp-examples-tomcat</module>
> > > These configs are not needed to start the server.
> > >
> >
> > Joe explained the fix and I explain the reason. There is no need to
> > remove compilation...we can move to 1.4.5-SNAPSHOT for the next 24
> > hours
> > if need be.
> >
>
> Thanks Jeff!
>
> Anita
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
Re: windows build hell
Posted by anita kulshreshtha <a_...@yahoo.com>.
--- Jeff Genender <jg...@apache.org> wrote:
>
>
> anita kulshreshtha wrote:
>
> >> 2) JSP compilation errors
> >> Problem:
> >> Embedded error: Unable to compile class for JSP
> >> Strange error message about JAVA_HOME, etc...
> >>
> >> Possible Solution/Work-around:
> >> Update the pom.xml in the root directory to use version
> >> 1.4.5-SNAPSHOT
> >> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender
> is
> >>
> >> planning to make 1.4.5 an official release for this. We're not
> sure
> >> why
> >> it gets us around the problem so it may be a red herring.
> >>
> >
> > I have seen this, but do not yet know why it happens. I would
> like
> > to comment out the following lines until the problem is resolved.
> >
> > 1. applications/geronimo-examples/pom.xml
> > <module>geronimo-jsp-examples</module>
> >
> > 2. configs/pom.xml
> > <module>jsp-examples-jetty</module>
> > <module>jsp-examples-tomcat</module>
> > These configs are not needed to start the server.
> >
>
> Joe explained the fix and I explain the reason. There is no need to
> remove compilation...we can move to 1.4.5-SNAPSHOT for the next 24
> hours
> if need be.
>
Thanks Jeff!
Anita
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: windows build hell
Posted by Jeff Genender <jg...@apache.org>.
anita kulshreshtha wrote:
>> 2) JSP compilation errors
>> Problem:
>> Embedded error: Unable to compile class for JSP
>> Strange error message about JAVA_HOME, etc...
>>
>> Possible Solution/Work-around:
>> Update the pom.xml in the root directory to use version
>> 1.4.5-SNAPSHOT
>> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
>>
>> planning to make 1.4.5 an official release for this. We're not sure
>> why
>> it gets us around the problem so it may be a red herring.
>>
>
> I have seen this, but do not yet know why it happens. I would like
> to comment out the following lines until the problem is resolved.
>
> 1. applications/geronimo-examples/pom.xml
> <module>geronimo-jsp-examples</module>
>
> 2. configs/pom.xml
> <module>jsp-examples-jetty</module>
> <module>jsp-examples-tomcat</module>
> These configs are not needed to start the server.
>
Joe explained the fix and I explain the reason. There is no need to
remove compilation...we can move to 1.4.5-SNAPSHOT for the next 24 hours
if need be.
Re: windows build hell
Posted by anita kulshreshtha <a_...@yahoo.com>.
inline..
--- Joe Bohn <jo...@earthlink.net> wrote:
>
> We've been struggling with build problems on windows for some time
> now
> and things just keep on getting worse.
>
> I'm composing this note to summarize the problems that I'm aware of
> with
> work-arounds and possible solutions. I'm also fishing to see if
> anybody else has some ideas on how to resolve these issues.
>
> 1) Windows pathlength problem.
> Problem:
> There are miscellaneous failures that can typically be tracked down
> to
> the windows pathlength problem. The nature of our repository
> structure
> and deployment make this a big problem. It also seems like we're
> continuing to add more intermediate elements in path names as we try
> to
> get things more organized and conform to Maven 2 conventions.
>
> Work-around:
> The work-around is to keep the windows root path as small as
> possible.
> I now typically build from a root path of c:\g to avoid these
> problems.
>
> Possible Solution:
> For a longer term solution I'm planning to work on a new repository
> implementation in 1.2 that that isn't as redundant or verbose.
+1
In the mean time could we warn our users that if they are using
windows, they should use a short root path. If everyone agrees, I would
like to edit the M2build page on cwiki.
>
>
>
> 2) JSP compilation errors
> Problem:
> Embedded error: Unable to compile class for JSP
> Strange error message about JAVA_HOME, etc...
>
> Possible Solution/Work-around:
> Update the pom.xml in the root directory to use version
> 1.4.5-SNAPSHOT
> (from 1.4.4) for the jspc-maven-plugin. Not sure if Jeff Genender is
>
> planning to make 1.4.5 an official release for this. We're not sure
> why
> it gets us around the problem so it may be a red herring.
>
I have seen this, but do not yet know why it happens. I would like
to comment out the following lines until the problem is resolved.
1. applications/geronimo-examples/pom.xml
<module>geronimo-jsp-examples</module>
2. configs/pom.xml
<module>jsp-examples-jetty</module>
<module>jsp-examples-tomcat</module>
These configs are not needed to start the server.
>
>
> 3) Openejb2 test failures.
> Problem:
> Caused by: java.lang.NoSuchMethodException:
> org.openejb.deployment.DeploymentTestSuite.getName()
>
> Work-around:
> After bootstrap failure cd to <root>\target\external\openejb2
> "mvn -Dmaven.test.skip=true"
> cd back to <root>
> "mvn clean install"
>
> Possible solution:
> Dain suggested adding the "getName" method to the test. However,
> when I
> attempted this I hit other errors.
> http://marc.theaimsgroup.com/?l=geronimo-dev&m=115680051431478&w=2
> I think it would be helpful if we could disable the openejb tests
> until
> this problem is resolved.
+1
>
>
>
> 4) Blue screen of death (bsod)
> Problem:
> This has been reported by multiple users on various machines. When
> running an M1 or M2 build the user encounters a bsod due to a memory
> failure.
> PAGE_FAULT_IN_NONPAGED_AREA
> *** STOP: 0x00000050 (0xBADDB148, 0x00000000, 0x8056C77B,
> 0x00000000)
> Dump of physical memory
>
> Work-around/Possible Solution:
> Haven't found one yet. I've tried updated drivers, replaced
> hardware,
> tried various heap size settings, etc.... At times this can be
> fairly
> frequent (every 3rd build attempt or so). I'm collecting
> bootstrap.log
> files from folks when this happens during a bootstrap to see if there
> is
> a common thread. So far, with the bootstrap logs, it always seems to
>
> happen at about the same place:
> Running tests after building a module (usually tomcat.ApplicationTest
> or
> TomcatModuleBuilderTest) and the final lines in the log are always
> the
> Creation of an MBeanServer like this:
> [exec] Running org.apache.geronimo.tomcat.ApplicationTest
> [exec] Created MBeanServer with ID:
> 5dcec6:10d5a184aed:-8000:jbohn2:1
>
> Please respond to this note if you are seeing the bsod failures on
> windows. At first I thought this was just me and was hardware
> related.
> However, the more I talk to folks on windows the more I hear of
> other
> folks encountering this same problem. I've updated all drivers,
> replaced my entire system, and several other folks have reported
> seeing
> this on completely different systems. I think that pretty much
> rules
> out a hardware problem.
Hmm..., I have never seen this one. I am looking at the code and will
get back to you if I find something strange.
Thanks
Anita
>
> ideas welcome!
>
> Joe
>
>
>
>
>
>
>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com