You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Sig Rinde <si...@rinde.com> on 2010/01/24 19:40:07 UTC
Wee error
When trying to get into urltohost:8080 I get this (just the upper part
of a ton):
Exception occured while processing/
Message: java.lang.UnsupportedOperationException: unsuitable as hash key
scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
scala.xml.Utility$.hashCode(Utility.scala:263)
scala.xml.Elem.hashCode(Elem.scala:64)
scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
scala.Iterator$class.foldLeft(Iterator.scala:520)
Latest per svn, jetty:run behaved... server seems to be running,
although I'm suspecting some pool issues... that's what I wanted to
check.
Sig
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Think I would challenge that conclusion: The esme built on January 5th
from files svn'd that day was built on Ubuntu 9.04 as well, and starts
today on two different Ubuntu 9.04's.
Anyway, I started all over again this morning, meticulously doing each
step without any glitches, precisely same setup as yesterday Ubuntu
9.04 with all packages upgraded, latest svn from ESME. (This just to
double test that I did nothing wrong yesterday):
Exact same result, same error messages.
Ok, next stab: I'm now doing exact same with a 9.10 release, results coming.
But if anybody is willing to tinker I can give access to any of the
two instances - free to do anything! It's just a click of a button and
it goes poof so... :)
2010/1/27 Richard Hirsch <hi...@gmail.com>:
> Thanks.
>
> It must be Ubuntu 9.04 specific then.
>
> Does anyone else have a Ubuntu 9.04 environment where we could verify the
> bug?
>
> D.
>
>
> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> OK, switcehd to Sun jdk (I think(:
>>
>> java version "1.6.0_16"
>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>
>> Same result....
>>
>>
>>
>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>> > mvn -U clean jetty:run did nothing here...
>> >
>> > But why try another JDK when we know the esme built on Jan 5 still
>> > works, on both servers - while the one built today stubbornly will not
>> > build?
>> >
>> > Must be some file changes to what the svn delivers in that timespan or
>> what?
>> >
>> >
>> >
>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >> Yep. I agree.
>> >>
>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>> >> course, this a windows box....
>> >>
>> >> Could be based on OpenJDK or Ubuntu 9.04?
>> >>
>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>> >>
>> >>
>> >>
>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>> >>
>> >>> Aye aye capt'n, will do! Done:
>> >>>
>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>> >>> thing not pulled was the esme_db folder, assume that is created anew
>> >>> at start up).
>> >>>
>> >>> Result: Ya, that started!
>> >>>
>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>> >>>
>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>> >>>
>> >>> So something happened with whatever the svn fetches after Jan 5....
>> >>> would be my educated guess.
>> >>>
>> >>>
>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>> 26
>> >>> in
>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>> the
>> >>> > packages that it uses may have changed. Of interest would be to move
>> the
>> >>> > original files from Server A to Server B to see if they build
>> correctly.
>> >>> >
>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>> >>> >
>> >>> >> No differences as far as I can see. The two:
>> >>> >>
>> >>> >> Server A: Esme built w/o problems Jan 5
>> >>> >> Server B: Esme build error Jan 26
>> >>> >>
>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>> >>> >>
>> >>> >> JDK same.
>> >>> >>
>> >>> >> Basically same-same :)
>> >>> >>
>> >>> >>
>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> >>> >> > What are the other differences on the two servers Sig?
>> >>> >> >
>> >>> >> > /Anne Kathrine
>> >>> >> > Sent from my iPhone
>> >>> >> >
>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>> >>> >> >
>> >>> >> >> I have, on the other server that runs ok (except that original
>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>> >>> >> >> same... (I'm sure that did not help much LOL)
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> >>> >> >>>
>> >>> >> >>> I don't think anything has changed. Just that no one has used
>> >>> openJDK
>> >>> >> >>> since
>> >>> >> >>> then.
>> >>> >> >>>
>> >>> >> >>> /Anne Kathrine
>> >>> >> >>> Sent from my iPhone
>> >>> >> >>>
>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>> hirsch.dick@gmail.com>
>> >>> >> wrote:
>> >>> >> >>>
>> >>> >> >>>> But what has changed so that the problem now occurs?
>> >>> >> >>>>
>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>> >>> >> >>>> <yo...@gmail.com>wrote:
>> >>> >> >>>>
>> >>> >> >>>>> Yay! :-)
>> >>> >> >>>>>
>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>> >>> >> >>>>>
>> >>> >> >>>>>> Aha :)
>> >>> >> >>>>>>
>> >>> >> >>>>>> java version "1.6.0_0"
>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>> >>> (6b14-1.4.1-0ubuntu12)
>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>> >>> >> >>>>>>
>> >>> >> >>>>>> Sig
>> >>> >> >>>>>>
>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> We've had this before:
>> >>> >> >>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>> >>> >> suggestion
>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>> (or
>> >>> was
>> >>> >> >>>>>>> it?)
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>> >>> openjdk-6,
>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> Vassil
>> >>> >> >>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>> >>> >> >>>>>>> <hi...@gmail.com>
>> >>> >> >>>>>
>> >>> >> >>>>> wrote:
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>> >>> wrote:
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>> >>> up-to-date
>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>> >>> starting
>> >>> >> up
>> >>> >> >>>>>>>>> a
>> >>> >> >>>>>>>>> fresh image.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then:
>> >>> >> >>>>>>>>> apt-get install subversion
>> >>> >> >>>>>>>>> apt-get install maven2
>> >>> >> >>>>>>>>> apt-get install jetty
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then:
>> >>> >> >>>>>>>>> svn checkout
>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then fixing the two files.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then problem :)
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>> was
>> >>> >> that
>> >>> >> >>>>>>>>> I
>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>> mvn...
>> >>> so
>> >>> >> >>>>>>>>> now
>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Nope, exact same error.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>> dies
>> >>> >> >>>>>>>>> after
>> >>> >> >>>>>>>>> a
>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>> No
>> >>> other
>> >>> >> >>>>>>>>> clues.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>> >>> changed.
>> >>> >> >>>>>>>>>> Has
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> anything
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> else changed in the environment?
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>> >>> problem,
>> >>> >> >>>>>
>> >>> >> >>>>> because
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>> >>> weeks.
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>> sig@rinde.com>
>> >>> >> wrote:
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>>> Then I get this:
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>> >>> >> >>>>>>>>>>> [INFO]
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> ------------------------------------------------------------------------
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> [INFO] null
>> >>> >> >>>>>>>>>>> [INFO]
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> ------------------------------------------------------------------------
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> [INFO] Trace
>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>> then
>> >>> >> all
>> >>> >> >>>>>>>>>>> was
>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>> sig@rinde.com>
>> >>> >> >>>>>>>>>>>> wrote:
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> Ethan,
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>> >>> jetty:run"
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> Prior to that:
>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>> >>> returned
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> non-zero
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> value:1
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> >>> >> >>>>>>>>>>>>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >>> >> >>>>>
>> >>> >> >>>>> Method)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> java.lang.reflect.Method.invoke(Method.java:616)
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>
>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>
>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>
>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>
>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> Caused by:
>> org.apache.maven.plugin.MojoFailureException:
>> >>> >> >>>>>>>>>>>>> command
>> >>> >> >>>>>
>> >>> >> >>>>> line
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>
>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> ... 20 more
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>> this
>> >>> once
>> >>> >> >>>>>>>>>>>>>> goes
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> deep
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>> somewhere
>> >>> >> >>>>>>>>>>>>>> else?
>> >>> >> >>>>>
>> >>> >> >>>>> And
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>> this
>> >>> >> >>>>>>>>>>>>>> error?
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> mvn
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> clean install?
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> Thanks,
>> >>> >> >>>>>>>>>>>>>> Ethan
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>> >>> sig@rinde.com>
>> >>> >> >>>>>
>> >>> >> >>>>> wrote:
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>> created a
>> >>> new
>> >>> >> >>>>>>>>>>>>>>> and
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> fresh
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>> one),
>> >>> >> >>>>>>>>>>>>>>> apt-get
>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>> commented
>> >>> out
>> >>> >> >>>>>>>>>>>>>>> the
>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>> pom.xml
>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>> /home/files/esme/server/src/test/scala/../scala
>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>> >>> >> >>>>>
>> >>> >> >>>>> java.lang.StackOverflowError
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>
>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> ...
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> S
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>> Unfortunately
>> >>> I
>> >>> >> >>>>>>>>>>>>>>>> don't
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> have
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>> >>> setting
>> >>> >> >>>>>>>>>>>>>>>> for
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> the
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>> >>> >> >>>>>>>>>>>>>>>> Definitely
>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>> line
>> >>> in
>> >>> >> >>>>>>>>>>>>>>>> the
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> property
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>> >>> does
>> >>> >> >>>>>>>>>>>>>>>> that
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> user
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>> >>> >> >>>>>>>>>>>>>>>> Ethan
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>> >>> sig@rinde.com
>> >>> >> >
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> wrote:
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>> >>> anything
>> >>> >> >>>>>>>>>>>>>>>>> but
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> root,
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> say
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>> same
>> >>> >> problem
>> >>> >> >>>>>>>>>>>>>>>>> on
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> all
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> browsers.
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>> local
>> >>> >> >>>>>>>>>>>>>>>>> instance.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> (aws
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> is
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>> webapp
>> >>> >> >>>>>>>>>>>>>>>>> folders
>> >>> >> >>>>>
>> >>> >> >>>>> and
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> found
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>> >>> removed
>> >>> >> >>>>>>>>>>>>>>>>> after
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> first
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> try).
>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>> found
>> >>> no
>> >>> >> >>>>>>>>>>>>>>>>> diff
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> except
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>> named
>> >>> >> >>>>>
>> >>> >> >>>>> .gitignore.
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>> in
>> >>> >> there
>> >>> >> >>>>>>>>>>>>>>>>> so
>> >>> >> >>>>>
>> >>> >> >>>>> I
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> can
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>> >>> later
>> >>> >> new
>> >>> >> >>>>>
>> >>> >> >>>>> and
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> fresh
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> >>> >> >>>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>> browsers.
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>
>> >>> >> >
>> >>> >>
>> >>> >
>> >>>
>> >>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
Maybe it was also associated with the api_test scala file, since it also
uses the same api_test user.
D.
On Wed, Jan 27, 2010 at 1:31 PM, Sig Rinde <si...@rinde.com> wrote:
> What about an explanation why the original login issue suddenly
> disappeared? Luck, for sure? :-)
>
>
> 2010/1/27 Vassil Dichev <vd...@apache.org>:
> > No such thing as luck ;-)
> >
> > I have actually removed the parameter for the increasing the stack
> > size and did a quick refactoring of the tests, the same tests seem to
> > fail.
> >
> >
> > On Wed, Jan 27, 2010 at 1:34 PM, Sig Rinde <si...@rinde.com> wrote:
> >> Well, somebody has done a good job somewhere - or been very lucky!
> >>
> >> Same environment as before. OpenJDK, Ubuntu 9.04 etc
> >>
> >> Version 903607 of esme
> >>
> >> And it built without commenting out any files!
> >>
> >> Thanks :)
> >>
> >>
> >>
> >> 2010/1/27 Richard Hirsch <hi...@gmail.com>:
> >>> On Wed, Jan 27, 2010 at 11:57 AM, Vassil Dichev <vd...@apache.org>
> wrote:
> >>>
> >>>> I thought initially that this is some sort of infinite loop, but it
> seems
> >>>> not.
> >>>>
> >>>> The specs I suspected are "AddAction" and "AddActionNeg". Each one of
> >>>> these contains a monstrous for comprehension. If I delete a couple of
> >>>> lines from these, it works even without tuning the stack size.
> >>>>
> >>>> I think this is unnecessarily pushing the limits of the compiler. In
> >>>> the first part of the for comprehensions every line depends on the
> >>>> previous, so the compiler has to check every new line in the context
> >>>> of new variables bound by the previous lines.
> >>>>
> >>>> I don't think every new test line depends on the others, right?
> >>>> Probably this is the case for login and pools, but otherwise the
> >>>> compile will be unnecessarily slow, even when it manages to build.
> >>>>
> >>>> Can we refactor the test based on actual dependencies in the execution
> >>>> of API calls?
> >>>
> >>>
> >>> Of course. Probably easier to have multiple small tests rather than one
> >>> large test. You can probably comment the two tests and I'll break it
> down
> >>> into smaller tests later.
> >>>
> >>>
> >>>>
> >>>> Vassil
> >>>>
> >>>
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
What about an explanation why the original login issue suddenly
disappeared? Luck, for sure? :-)
2010/1/27 Vassil Dichev <vd...@apache.org>:
> No such thing as luck ;-)
>
> I have actually removed the parameter for the increasing the stack
> size and did a quick refactoring of the tests, the same tests seem to
> fail.
>
>
> On Wed, Jan 27, 2010 at 1:34 PM, Sig Rinde <si...@rinde.com> wrote:
>> Well, somebody has done a good job somewhere - or been very lucky!
>>
>> Same environment as before. OpenJDK, Ubuntu 9.04 etc
>>
>> Version 903607 of esme
>>
>> And it built without commenting out any files!
>>
>> Thanks :)
>>
>>
>>
>> 2010/1/27 Richard Hirsch <hi...@gmail.com>:
>>> On Wed, Jan 27, 2010 at 11:57 AM, Vassil Dichev <vd...@apache.org> wrote:
>>>
>>>> I thought initially that this is some sort of infinite loop, but it seems
>>>> not.
>>>>
>>>> The specs I suspected are "AddAction" and "AddActionNeg". Each one of
>>>> these contains a monstrous for comprehension. If I delete a couple of
>>>> lines from these, it works even without tuning the stack size.
>>>>
>>>> I think this is unnecessarily pushing the limits of the compiler. In
>>>> the first part of the for comprehensions every line depends on the
>>>> previous, so the compiler has to check every new line in the context
>>>> of new variables bound by the previous lines.
>>>>
>>>> I don't think every new test line depends on the others, right?
>>>> Probably this is the case for login and pools, but otherwise the
>>>> compile will be unnecessarily slow, even when it manages to build.
>>>>
>>>> Can we refactor the test based on actual dependencies in the execution
>>>> of API calls?
>>>
>>>
>>> Of course. Probably easier to have multiple small tests rather than one
>>> large test. You can probably comment the two tests and I'll break it down
>>> into smaller tests later.
>>>
>>>
>>>>
>>>> Vassil
>>>>
>>>
>>
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
No such thing as luck ;-)
I have actually removed the parameter for the increasing the stack
size and did a quick refactoring of the tests, the same tests seem to
fail.
On Wed, Jan 27, 2010 at 1:34 PM, Sig Rinde <si...@rinde.com> wrote:
> Well, somebody has done a good job somewhere - or been very lucky!
>
> Same environment as before. OpenJDK, Ubuntu 9.04 etc
>
> Version 903607 of esme
>
> And it built without commenting out any files!
>
> Thanks :)
>
>
>
> 2010/1/27 Richard Hirsch <hi...@gmail.com>:
>> On Wed, Jan 27, 2010 at 11:57 AM, Vassil Dichev <vd...@apache.org> wrote:
>>
>>> I thought initially that this is some sort of infinite loop, but it seems
>>> not.
>>>
>>> The specs I suspected are "AddAction" and "AddActionNeg". Each one of
>>> these contains a monstrous for comprehension. If I delete a couple of
>>> lines from these, it works even without tuning the stack size.
>>>
>>> I think this is unnecessarily pushing the limits of the compiler. In
>>> the first part of the for comprehensions every line depends on the
>>> previous, so the compiler has to check every new line in the context
>>> of new variables bound by the previous lines.
>>>
>>> I don't think every new test line depends on the others, right?
>>> Probably this is the case for login and pools, but otherwise the
>>> compile will be unnecessarily slow, even when it manages to build.
>>>
>>> Can we refactor the test based on actual dependencies in the execution
>>> of API calls?
>>
>>
>> Of course. Probably easier to have multiple small tests rather than one
>> large test. You can probably comment the two tests and I'll break it down
>> into smaller tests later.
>>
>>
>>>
>>> Vassil
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Well, somebody has done a good job somewhere - or been very lucky!
Same environment as before. OpenJDK, Ubuntu 9.04 etc
Version 903607 of esme
And it built without commenting out any files!
Thanks :)
2010/1/27 Richard Hirsch <hi...@gmail.com>:
> On Wed, Jan 27, 2010 at 11:57 AM, Vassil Dichev <vd...@apache.org> wrote:
>
>> I thought initially that this is some sort of infinite loop, but it seems
>> not.
>>
>> The specs I suspected are "AddAction" and "AddActionNeg". Each one of
>> these contains a monstrous for comprehension. If I delete a couple of
>> lines from these, it works even without tuning the stack size.
>>
>> I think this is unnecessarily pushing the limits of the compiler. In
>> the first part of the for comprehensions every line depends on the
>> previous, so the compiler has to check every new line in the context
>> of new variables bound by the previous lines.
>>
>> I don't think every new test line depends on the others, right?
>> Probably this is the case for login and pools, but otherwise the
>> compile will be unnecessarily slow, even when it manages to build.
>>
>> Can we refactor the test based on actual dependencies in the execution
>> of API calls?
>
>
> Of course. Probably easier to have multiple small tests rather than one
> large test. You can probably comment the two tests and I'll break it down
> into smaller tests later.
>
>
>>
>> Vassil
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
On Wed, Jan 27, 2010 at 11:57 AM, Vassil Dichev <vd...@apache.org> wrote:
> I thought initially that this is some sort of infinite loop, but it seems
> not.
>
> The specs I suspected are "AddAction" and "AddActionNeg". Each one of
> these contains a monstrous for comprehension. If I delete a couple of
> lines from these, it works even without tuning the stack size.
>
> I think this is unnecessarily pushing the limits of the compiler. In
> the first part of the for comprehensions every line depends on the
> previous, so the compiler has to check every new line in the context
> of new variables bound by the previous lines.
>
> I don't think every new test line depends on the others, right?
> Probably this is the case for login and pools, but otherwise the
> compile will be unnecessarily slow, even when it manages to build.
>
> Can we refactor the test based on actual dependencies in the execution
> of API calls?
Of course. Probably easier to have multiple small tests rather than one
large test. You can probably comment the two tests and I'll break it down
into smaller tests later.
>
> Vassil
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
I thought initially that this is some sort of infinite loop, but it seems not.
The specs I suspected are "AddAction" and "AddActionNeg". Each one of
these contains a monstrous for comprehension. If I delete a couple of
lines from these, it works even without tuning the stack size.
I think this is unnecessarily pushing the limits of the compiler. In
the first part of the for comprehensions every line depends on the
previous, so the compiler has to check every new line in the context
of new variables bound by the previous lines.
I don't think every new test line depends on the others, right?
Probably this is the case for login and pools, but otherwise the
compile will be unnecessarily slow, even when it manages to build.
Can we refactor the test based on actual dependencies in the execution
of API calls?
Vassil
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
Can you try to update from Subversion again? I have tuned the Java
stack size, it helps here.
I think we can blame the OpenJDK for the login error though ;-)
On Wed, Jan 27, 2010 at 11:34 AM, Sig Rinde <si...@rinde.com> wrote:
> Good to hear :)
>
> And yes, the login error trace is identical.
>
> And I thought this was an old, yet to be fixed, issue as per the jira
> message from David. The error is exact same as today.
>
>
> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>> Debugging the ApiTest right now- we shouldn't just remove it, Ethan
>> put a lot of effort in it.
>>
>> As for the login error, it would be interesting to see- is the stack
>> trace the same? I kinda felt this was not the whole story, as most
>> people don't see this error at all.
>>
>>
>> On Wed, Jan 27, 2010 at 11:24 AM, Sig Rinde <si...@rinde.com> wrote:
>>> Yep, that took the cork out of the bottle - it built now!
>>>
>>> So would that mess up something else or could you guys remove it or something?
>>>
>>> Original (login) issue is still there though :)
>>>
>>>
>>> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>>>> By same problem you mean, of course, the StackOverflowError, which my
>>>> commit wasn't trying to fix (it was for the
>>>> UnsupportedOperationException).
>>>>
>>>> Anyway, what I currently found out is that the task that eventually fails is
>>>>
>>>> mvn scala:testCompile
>>>>
>>>> and if you remove ApiTest.scala, the error goes away.
>>>>
>>>>
>>>> On Wed, Jan 27, 2010 at 10:54 AM, Sig Rinde <si...@rinde.com> wrote:
>>>>> Did update now:
>>>>>
>>>>> root@ip-10-224-67-146:/home/files# svn checkout
>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>>> U esme/server/src/main/scala/org/apache/esme/model/Privilege.scala
>>>>> U esme/server/src/main/scala/org/apache/esme/actor/UserActor.scala
>>>>>
>>>>> Still same problem / error
>>>>>
>>>>>
>>>>> 2010/1/27 Sig Rinde <si...@rinde.com>:
>>>>>> When did you commit? Seconds before you sent this mail? If so I'll do
>>>>>> another svn etc...
>>>>>>
>>>>>> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>>>>>>> OK, I get the same error (StackOverflowError) on Windows, too.
>>>>>>>
>>>>>>> Meanwhile I have attempted to fix the UnsupportedOperationException
>>>>>>> and committed, but we won't know if it works before we are able to
>>>>>>> build.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> It must be Ubuntu 9.04 specific then.
>>>>>>>>
>>>>>>>> Does anyone else have a Ubuntu 9.04 environment where we could verify the
>>>>>>>> bug?
>>>>>>>>
>>>>>>>> D.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>
>>>>>>>>> OK, switcehd to Sun jdk (I think(:
>>>>>>>>>
>>>>>>>>> java version "1.6.0_16"
>>>>>>>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>>>>>>>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>>>>>>>>
>>>>>>>>> Same result....
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>>>>>>>>> > mvn -U clean jetty:run did nothing here...
>>>>>>>>> >
>>>>>>>>> > But why try another JDK when we know the esme built on Jan 5 still
>>>>>>>>> > works, on both servers - while the one built today stubbornly will not
>>>>>>>>> > build?
>>>>>>>>> >
>>>>>>>>> > Must be some file changes to what the svn delivers in that timespan or
>>>>>>>>> what?
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>> >> Yep. I agree.
>>>>>>>>> >>
>>>>>>>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>>>>>>>>> >> course, this a windows box....
>>>>>>>>> >>
>>>>>>>>> >> Could be based on OpenJDK or Ubuntu 9.04?
>>>>>>>>> >>
>>>>>>>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>> >>
>>>>>>>>> >>> Aye aye capt'n, will do! Done:
>>>>>>>>> >>>
>>>>>>>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>>>>>>>> >>> thing not pulled was the esme_db folder, assume that is created anew
>>>>>>>>> >>> at start up).
>>>>>>>>> >>>
>>>>>>>>> >>> Result: Ya, that started!
>>>>>>>>> >>>
>>>>>>>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>>>>>>>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>>>>>>> >>>
>>>>>>>>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>>>>>>>> >>>
>>>>>>>>> >>> So something happened with whatever the svn fetches after Jan 5....
>>>>>>>>> >>> would be my educated guess.
>>>>>>>>> >>>
>>>>>>>>> >>>
>>>>>>>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>>>>>>>>> 26
>>>>>>>>> >>> in
>>>>>>>>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>>>>>>>>> the
>>>>>>>>> >>> > packages that it uses may have changed. Of interest would be to move
>>>>>>>>> the
>>>>>>>>> >>> > original files from Server A to Server B to see if they build
>>>>>>>>> correctly.
>>>>>>>>> >>> >
>>>>>>>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>> >>> >
>>>>>>>>> >>> >> No differences as far as I can see. The two:
>>>>>>>>> >>> >>
>>>>>>>>> >>> >> Server A: Esme built w/o problems Jan 5
>>>>>>>>> >>> >> Server B: Esme build error Jan 26
>>>>>>>>> >>> >>
>>>>>>>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>>>>>>>>> >>> >>
>>>>>>>>> >>> >> JDK same.
>>>>>>>>> >>> >>
>>>>>>>>> >>> >> Basically same-same :)
>>>>>>>>> >>> >>
>>>>>>>>> >>> >>
>>>>>>>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>>>>> >>> >> > What are the other differences on the two servers Sig?
>>>>>>>>> >>> >> >
>>>>>>>>> >>> >> > /Anne Kathrine
>>>>>>>>> >>> >> > Sent from my iPhone
>>>>>>>>> >>> >> >
>>>>>>>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>> >>> >> >
>>>>>>>>> >>> >> >> I have, on the other server that runs ok (except that original
>>>>>>>>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>>>>>>>> >>> >> >> same... (I'm sure that did not help much LOL)
>>>>>>>>> >>> >> >>
>>>>>>>>> >>> >> >>
>>>>>>>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>>>>> >>> >> >>>
>>>>>>>>> >>> >> >>> I don't think anything has changed. Just that no one has used
>>>>>>>>> >>> openJDK
>>>>>>>>> >>> >> >>> since
>>>>>>>>> >>> >> >>> then.
>>>>>>>>> >>> >> >>>
>>>>>>>>> >>> >> >>> /Anne Kathrine
>>>>>>>>> >>> >> >>> Sent from my iPhone
>>>>>>>>> >>> >> >>>
>>>>>>>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>>>>>>>>> hirsch.dick@gmail.com>
>>>>>>>>> >>> >> wrote:
>>>>>>>>> >>> >> >>>
>>>>>>>>> >>> >> >>>> But what has changed so that the problem now occurs?
>>>>>>>>> >>> >> >>>>
>>>>>>>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>>>>>> >>> >> >>>> <yo...@gmail.com>wrote:
>>>>>>>>> >>> >> >>>>
>>>>>>>>> >>> >> >>>>> Yay! :-)
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>> Aha :)
>>>>>>>>> >>> >> >>>>>>
>>>>>>>>> >>> >> >>>>>> java version "1.6.0_0"
>>>>>>>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>>>>>>> >>> (6b14-1.4.1-0ubuntu12)
>>>>>>>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>>>> >>> >> >>>>>>
>>>>>>>>> >>> >> >>>>>> Sig
>>>>>>>>> >>> >> >>>>>>
>>>>>>>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>>> We've had this before:
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>>>>>>>>> >>> >> suggestion
>>>>>>>>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>>>>>>>>> (or
>>>>>>>>> >>> was
>>>>>>>>> >>> >> >>>>>>> it?)
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>>>>>>>> >>> openjdk-6,
>>>>>>>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>>> Vassil
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>>>> >>> >> >>>>>>> <hi...@gmail.com>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> wrote:
>>>>>>>>> >>> >> >>>>>>>>
>>>>>>>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>>> >>> >> >>>>>>>>
>>>>>>>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>> >>> wrote:
>>>>>>>>> >>> >> >>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>>>>>>>> >>> up-to-date
>>>>>>>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>>>>>>> >>> starting
>>>>>>>>> >>> >> up
>>>>>>>>> >>> >> >>>>>>>>> a
>>>>>>>>> >>> >> >>>>>>>>> fresh image.
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Then:
>>>>>>>>> >>> >> >>>>>>>>> apt-get install subversion
>>>>>>>>> >>> >> >>>>>>>>> apt-get install maven2
>>>>>>>>> >>> >> >>>>>>>>> apt-get install jetty
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Then:
>>>>>>>>> >>> >> >>>>>>>>> svn checkout
>>>>>>>>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Then fixing the two files.
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Then problem :)
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>>>>>>>>> was
>>>>>>>>> >>> >> that
>>>>>>>>> >>> >> >>>>>>>>> I
>>>>>>>>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>>>>>>>>> mvn...
>>>>>>>>> >>> so
>>>>>>>>> >>> >> >>>>>>>>> now
>>>>>>>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Nope, exact same error.
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>>>>>>> dies
>>>>>>>>> >>> >> >>>>>>>>> after
>>>>>>>>> >>> >> >>>>>>>>> a
>>>>>>>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>>>>>>>>> No
>>>>>>>>> >>> other
>>>>>>>>> >>> >> >>>>>>>>> clues.
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>>>>>> >>> changed.
>>>>>>>>> >>> >> >>>>>>>>>> Has
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> anything
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>> else changed in the environment?
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>>>>>>> >>> problem,
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> because
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>>>>>>>> >>> weeks.
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>>>>>>>>> sig@rinde.com>
>>>>>>>>> >>> >> wrote:
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> Then I get this:
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> [INFO] null
>>>>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> [INFO] Trace
>>>>>>>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>>>>>>> then
>>>>>>>>> >>> >> all
>>>>>>>>> >>> >> >>>>>>>>>>> was
>>>>>>>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>>>>>>>>> sig@rinde.com>
>>>>>>>>> >>> >> >>>>>>>>>>>> wrote:
>>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> Ethan,
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>>>>>>> >>> jetty:run"
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> Prior to that:
>>>>>>>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>>>>>>>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>>>>>>> >>> returned
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> non-zero
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> value:1
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> Method)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> Caused by:
>>>>>>>>> org.apache.maven.plugin.MojoFailureException:
>>>>>>>>> >>> >> >>>>>>>>>>>>> command
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> line
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >>
>>>>>>>>> >>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> ... 20 more
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>>>>>>>>> this
>>>>>>>>> >>> once
>>>>>>>>> >>> >> >>>>>>>>>>>>>> goes
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> deep
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>>>>>>>> somewhere
>>>>>>>>> >>> >> >>>>>>>>>>>>>> else?
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> And
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>>>>>>>>> this
>>>>>>>>> >>> >> >>>>>>>>>>>>>> error?
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> mvn
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>> clean install?
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>> Thanks,
>>>>>>>>> >>> >> >>>>>>>>>>>>>> Ethan
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>>>>>>>> >>> sig@rinde.com>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> wrote:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>>>>>>>>> created a
>>>>>>>>> >>> new
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> and
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> fresh
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>>>>>>>>> one),
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> apt-get
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>>>>>>>>> commented
>>>>>>>>> >>> out
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> the
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>>>>>>>>> pom.xml
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>>>>>>>>> /home/files/esme/server/src/test/scala/../scala
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> java.lang.StackOverflowError
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> ...
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> S
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>>>>>>> Unfortunately
>>>>>>>>> >>> I
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> don't
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> have
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>>>>>> >>> setting
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> for
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> the
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Definitely
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>>>>>>>>> line
>>>>>>>>> >>> in
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> the
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> property
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>>>>>>>> >>> does
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> that
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> user
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Ethan
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>>>>>>>> >>> sig@rinde.com
>>>>>>>>> >>> >> >
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> wrote:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>>>>>> >>> anything
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> but
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> root,
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> say
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>>>>>>>>> same
>>>>>>>>> >>> >> problem
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> on
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> all
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>> browsers.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>>>>>>>>> local
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> instance.
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>> (aws
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> is
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>>>>>>>>> webapp
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> folders
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> and
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> found
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>>>>>>> >>> removed
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> after
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> first
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> try).
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>>>>>>>>> found
>>>>>>>>> >>> no
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> diff
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> except
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>>>>>>>>> named
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> .gitignore.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>>>>>>>>> in
>>>>>>>>> >>> >> there
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> so
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> I
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> can
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>>>>>>>> >>> later
>>>>>>>>> >>> >> new
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>> and
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>> fresh
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>>>>>>>>> browsers.
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>>> >>> >> >>>>>>>>
>>>>>>>>> >>> >> >>>>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>>>
>>>>>>>>> >>> >> >>>
>>>>>>>>> >>> >> >
>>>>>>>>> >>> >>
>>>>>>>>> >>> >
>>>>>>>>> >>>
>>>>>>>>> >>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Good to hear :)
And yes, the login error trace is identical.
And I thought this was an old, yet to be fixed, issue as per the jira
message from David. The error is exact same as today.
2010/1/27 Vassil Dichev <vd...@apache.org>:
> Debugging the ApiTest right now- we shouldn't just remove it, Ethan
> put a lot of effort in it.
>
> As for the login error, it would be interesting to see- is the stack
> trace the same? I kinda felt this was not the whole story, as most
> people don't see this error at all.
>
>
> On Wed, Jan 27, 2010 at 11:24 AM, Sig Rinde <si...@rinde.com> wrote:
>> Yep, that took the cork out of the bottle - it built now!
>>
>> So would that mess up something else or could you guys remove it or something?
>>
>> Original (login) issue is still there though :)
>>
>>
>> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>>> By same problem you mean, of course, the StackOverflowError, which my
>>> commit wasn't trying to fix (it was for the
>>> UnsupportedOperationException).
>>>
>>> Anyway, what I currently found out is that the task that eventually fails is
>>>
>>> mvn scala:testCompile
>>>
>>> and if you remove ApiTest.scala, the error goes away.
>>>
>>>
>>> On Wed, Jan 27, 2010 at 10:54 AM, Sig Rinde <si...@rinde.com> wrote:
>>>> Did update now:
>>>>
>>>> root@ip-10-224-67-146:/home/files# svn checkout
>>>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>> U esme/server/src/main/scala/org/apache/esme/model/Privilege.scala
>>>> U esme/server/src/main/scala/org/apache/esme/actor/UserActor.scala
>>>>
>>>> Still same problem / error
>>>>
>>>>
>>>> 2010/1/27 Sig Rinde <si...@rinde.com>:
>>>>> When did you commit? Seconds before you sent this mail? If so I'll do
>>>>> another svn etc...
>>>>>
>>>>> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>>>>>> OK, I get the same error (StackOverflowError) on Windows, too.
>>>>>>
>>>>>> Meanwhile I have attempted to fix the UnsupportedOperationException
>>>>>> and committed, but we won't know if it works before we are able to
>>>>>> build.
>>>>>>
>>>>>>
>>>>>> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>> Thanks.
>>>>>>>
>>>>>>> It must be Ubuntu 9.04 specific then.
>>>>>>>
>>>>>>> Does anyone else have a Ubuntu 9.04 environment where we could verify the
>>>>>>> bug?
>>>>>>>
>>>>>>> D.
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>
>>>>>>>> OK, switcehd to Sun jdk (I think(:
>>>>>>>>
>>>>>>>> java version "1.6.0_16"
>>>>>>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>>>>>>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>>>>>>>
>>>>>>>> Same result....
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>>>>>>>> > mvn -U clean jetty:run did nothing here...
>>>>>>>> >
>>>>>>>> > But why try another JDK when we know the esme built on Jan 5 still
>>>>>>>> > works, on both servers - while the one built today stubbornly will not
>>>>>>>> > build?
>>>>>>>> >
>>>>>>>> > Must be some file changes to what the svn delivers in that timespan or
>>>>>>>> what?
>>>>>>>> >
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>> >> Yep. I agree.
>>>>>>>> >>
>>>>>>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>>>>>>>> >> course, this a windows box....
>>>>>>>> >>
>>>>>>>> >> Could be based on OpenJDK or Ubuntu 9.04?
>>>>>>>> >>
>>>>>>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>> >>
>>>>>>>> >>> Aye aye capt'n, will do! Done:
>>>>>>>> >>>
>>>>>>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>>>>>>> >>> thing not pulled was the esme_db folder, assume that is created anew
>>>>>>>> >>> at start up).
>>>>>>>> >>>
>>>>>>>> >>> Result: Ya, that started!
>>>>>>>> >>>
>>>>>>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>>>>>>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>>>>>> >>>
>>>>>>>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>>>>>>> >>>
>>>>>>>> >>> So something happened with whatever the svn fetches after Jan 5....
>>>>>>>> >>> would be my educated guess.
>>>>>>>> >>>
>>>>>>>> >>>
>>>>>>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>>>>>>>> 26
>>>>>>>> >>> in
>>>>>>>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>>>>>>>> the
>>>>>>>> >>> > packages that it uses may have changed. Of interest would be to move
>>>>>>>> the
>>>>>>>> >>> > original files from Server A to Server B to see if they build
>>>>>>>> correctly.
>>>>>>>> >>> >
>>>>>>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>> >>> >
>>>>>>>> >>> >> No differences as far as I can see. The two:
>>>>>>>> >>> >>
>>>>>>>> >>> >> Server A: Esme built w/o problems Jan 5
>>>>>>>> >>> >> Server B: Esme build error Jan 26
>>>>>>>> >>> >>
>>>>>>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>>>>>>>> >>> >>
>>>>>>>> >>> >> JDK same.
>>>>>>>> >>> >>
>>>>>>>> >>> >> Basically same-same :)
>>>>>>>> >>> >>
>>>>>>>> >>> >>
>>>>>>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>>>> >>> >> > What are the other differences on the two servers Sig?
>>>>>>>> >>> >> >
>>>>>>>> >>> >> > /Anne Kathrine
>>>>>>>> >>> >> > Sent from my iPhone
>>>>>>>> >>> >> >
>>>>>>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>> >>> >> >
>>>>>>>> >>> >> >> I have, on the other server that runs ok (except that original
>>>>>>>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>>>>>>> >>> >> >> same... (I'm sure that did not help much LOL)
>>>>>>>> >>> >> >>
>>>>>>>> >>> >> >>
>>>>>>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>>>> >>> >> >>>
>>>>>>>> >>> >> >>> I don't think anything has changed. Just that no one has used
>>>>>>>> >>> openJDK
>>>>>>>> >>> >> >>> since
>>>>>>>> >>> >> >>> then.
>>>>>>>> >>> >> >>>
>>>>>>>> >>> >> >>> /Anne Kathrine
>>>>>>>> >>> >> >>> Sent from my iPhone
>>>>>>>> >>> >> >>>
>>>>>>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>>>>>>>> hirsch.dick@gmail.com>
>>>>>>>> >>> >> wrote:
>>>>>>>> >>> >> >>>
>>>>>>>> >>> >> >>>> But what has changed so that the problem now occurs?
>>>>>>>> >>> >> >>>>
>>>>>>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>>>>> >>> >> >>>> <yo...@gmail.com>wrote:
>>>>>>>> >>> >> >>>>
>>>>>>>> >>> >> >>>>> Yay! :-)
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>> Aha :)
>>>>>>>> >>> >> >>>>>>
>>>>>>>> >>> >> >>>>>> java version "1.6.0_0"
>>>>>>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>>>>>> >>> (6b14-1.4.1-0ubuntu12)
>>>>>>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>>> >>> >> >>>>>>
>>>>>>>> >>> >> >>>>>> Sig
>>>>>>>> >>> >> >>>>>>
>>>>>>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>>> We've had this before:
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>>>>>>>> >>> >> suggestion
>>>>>>>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>>>>>>>> (or
>>>>>>>> >>> was
>>>>>>>> >>> >> >>>>>>> it?)
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>>>>>>> >>> openjdk-6,
>>>>>>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>>> Vassil
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>>> >>> >> >>>>>>> <hi...@gmail.com>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> wrote:
>>>>>>>> >>> >> >>>>>>>>
>>>>>>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>> >>> >> >>>>>>>>
>>>>>>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>>>>>> >>> wrote:
>>>>>>>> >>> >> >>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>>>>>>> >>> up-to-date
>>>>>>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>>>>>> >>> starting
>>>>>>>> >>> >> up
>>>>>>>> >>> >> >>>>>>>>> a
>>>>>>>> >>> >> >>>>>>>>> fresh image.
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Then:
>>>>>>>> >>> >> >>>>>>>>> apt-get install subversion
>>>>>>>> >>> >> >>>>>>>>> apt-get install maven2
>>>>>>>> >>> >> >>>>>>>>> apt-get install jetty
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Then:
>>>>>>>> >>> >> >>>>>>>>> svn checkout
>>>>>>>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Then fixing the two files.
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Then problem :)
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>>>>>>>> was
>>>>>>>> >>> >> that
>>>>>>>> >>> >> >>>>>>>>> I
>>>>>>>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>>>>>>>> mvn...
>>>>>>>> >>> so
>>>>>>>> >>> >> >>>>>>>>> now
>>>>>>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Nope, exact same error.
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>>>>>> dies
>>>>>>>> >>> >> >>>>>>>>> after
>>>>>>>> >>> >> >>>>>>>>> a
>>>>>>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>>>>>>>> No
>>>>>>>> >>> other
>>>>>>>> >>> >> >>>>>>>>> clues.
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>>>>> >>> changed.
>>>>>>>> >>> >> >>>>>>>>>> Has
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> anything
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>> else changed in the environment?
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>>>>>> >>> problem,
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> because
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>>>>>>> >>> weeks.
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>>>>>>>> sig@rinde.com>
>>>>>>>> >>> >> wrote:
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> Then I get this:
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> [INFO] null
>>>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> [INFO] Trace
>>>>>>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>>>>>> then
>>>>>>>> >>> >> all
>>>>>>>> >>> >> >>>>>>>>>>> was
>>>>>>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>>>>>>>> sig@rinde.com>
>>>>>>>> >>> >> >>>>>>>>>>>> wrote:
>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> Ethan,
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>>>>>> >>> jetty:run"
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> Prior to that:
>>>>>>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>>>>>>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>>>>>>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>>>>>>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>>>>>> >>> returned
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> non-zero
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> value:1
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> Method)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> Caused by:
>>>>>>>> org.apache.maven.plugin.MojoFailureException:
>>>>>>>> >>> >> >>>>>>>>>>>>> command
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> line
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >>
>>>>>>>> >>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> ... 20 more
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>>>>>>>> this
>>>>>>>> >>> once
>>>>>>>> >>> >> >>>>>>>>>>>>>> goes
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> deep
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>>>>>>> somewhere
>>>>>>>> >>> >> >>>>>>>>>>>>>> else?
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> And
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>>>>>>>> this
>>>>>>>> >>> >> >>>>>>>>>>>>>> error?
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> mvn
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>> clean install?
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>> Thanks,
>>>>>>>> >>> >> >>>>>>>>>>>>>> Ethan
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>>>>>>> >>> sig@rinde.com>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> wrote:
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>>>>>>>> created a
>>>>>>>> >>> new
>>>>>>>> >>> >> >>>>>>>>>>>>>>> and
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> fresh
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>>>>>>>> one),
>>>>>>>> >>> >> >>>>>>>>>>>>>>> apt-get
>>>>>>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>>>>>>>> commented
>>>>>>>> >>> out
>>>>>>>> >>> >> >>>>>>>>>>>>>>> the
>>>>>>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>>>>>>>> pom.xml
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>>>>>>>> /home/files/esme/server/src/test/scala/../scala
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> java.lang.StackOverflowError
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> ...
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> S
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>>>>>> Unfortunately
>>>>>>>> >>> I
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> don't
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> have
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>>>>> >>> setting
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> for
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> the
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Definitely
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>>>>>>>> line
>>>>>>>> >>> in
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> the
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> property
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>>>>>>> >>> does
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> that
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> user
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> Ethan
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>>>>>>> >>> sig@rinde.com
>>>>>>>> >>> >> >
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> wrote:
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>>>>> >>> anything
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> but
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> root,
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> say
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>>>>>>>> same
>>>>>>>> >>> >> problem
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> on
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> all
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>> browsers.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>>>>>>>> local
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> instance.
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>> (aws
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> is
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>>>>>>>> webapp
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> folders
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> and
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> found
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>>>>>> >>> removed
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> after
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> first
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> try).
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>>>>>>>> found
>>>>>>>> >>> no
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> diff
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> except
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>>>>>>>> named
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> .gitignore.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>>>>>>>> in
>>>>>>>> >>> >> there
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> so
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> I
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> can
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>>>>>>> >>> later
>>>>>>>> >>> >> new
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>> and
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>> fresh
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>>>>>>>> browsers.
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>>
>>>>>>>> >>> >> >>>>>>>>
>>>>>>>> >>> >> >>>>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>>>
>>>>>>>> >>> >> >>>
>>>>>>>> >>> >> >
>>>>>>>> >>> >>
>>>>>>>> >>> >
>>>>>>>> >>>
>>>>>>>> >>
>>>>>>>> >
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
Debugging the ApiTest right now- we shouldn't just remove it, Ethan
put a lot of effort in it.
As for the login error, it would be interesting to see- is the stack
trace the same? I kinda felt this was not the whole story, as most
people don't see this error at all.
On Wed, Jan 27, 2010 at 11:24 AM, Sig Rinde <si...@rinde.com> wrote:
> Yep, that took the cork out of the bottle - it built now!
>
> So would that mess up something else or could you guys remove it or something?
>
> Original (login) issue is still there though :)
>
>
> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>> By same problem you mean, of course, the StackOverflowError, which my
>> commit wasn't trying to fix (it was for the
>> UnsupportedOperationException).
>>
>> Anyway, what I currently found out is that the task that eventually fails is
>>
>> mvn scala:testCompile
>>
>> and if you remove ApiTest.scala, the error goes away.
>>
>>
>> On Wed, Jan 27, 2010 at 10:54 AM, Sig Rinde <si...@rinde.com> wrote:
>>> Did update now:
>>>
>>> root@ip-10-224-67-146:/home/files# svn checkout
>>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>> U esme/server/src/main/scala/org/apache/esme/model/Privilege.scala
>>> U esme/server/src/main/scala/org/apache/esme/actor/UserActor.scala
>>>
>>> Still same problem / error
>>>
>>>
>>> 2010/1/27 Sig Rinde <si...@rinde.com>:
>>>> When did you commit? Seconds before you sent this mail? If so I'll do
>>>> another svn etc...
>>>>
>>>> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>>>>> OK, I get the same error (StackOverflowError) on Windows, too.
>>>>>
>>>>> Meanwhile I have attempted to fix the UnsupportedOperationException
>>>>> and committed, but we won't know if it works before we are able to
>>>>> build.
>>>>>
>>>>>
>>>>> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>> Thanks.
>>>>>>
>>>>>> It must be Ubuntu 9.04 specific then.
>>>>>>
>>>>>> Does anyone else have a Ubuntu 9.04 environment where we could verify the
>>>>>> bug?
>>>>>>
>>>>>> D.
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>
>>>>>>> OK, switcehd to Sun jdk (I think(:
>>>>>>>
>>>>>>> java version "1.6.0_16"
>>>>>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>>>>>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>>>>>>
>>>>>>> Same result....
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>>>>>>> > mvn -U clean jetty:run did nothing here...
>>>>>>> >
>>>>>>> > But why try another JDK when we know the esme built on Jan 5 still
>>>>>>> > works, on both servers - while the one built today stubbornly will not
>>>>>>> > build?
>>>>>>> >
>>>>>>> > Must be some file changes to what the svn delivers in that timespan or
>>>>>>> what?
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>> >> Yep. I agree.
>>>>>>> >>
>>>>>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>>>>>>> >> course, this a windows box....
>>>>>>> >>
>>>>>>> >> Could be based on OpenJDK or Ubuntu 9.04?
>>>>>>> >>
>>>>>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>>>>>>> >>
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>> >>
>>>>>>> >>> Aye aye capt'n, will do! Done:
>>>>>>> >>>
>>>>>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>>>>>> >>> thing not pulled was the esme_db folder, assume that is created anew
>>>>>>> >>> at start up).
>>>>>>> >>>
>>>>>>> >>> Result: Ya, that started!
>>>>>>> >>>
>>>>>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>>>>>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>>>>> >>>
>>>>>>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>>>>>> >>>
>>>>>>> >>> So something happened with whatever the svn fetches after Jan 5....
>>>>>>> >>> would be my educated guess.
>>>>>>> >>>
>>>>>>> >>>
>>>>>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>>>>>>> 26
>>>>>>> >>> in
>>>>>>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>>>>>>> the
>>>>>>> >>> > packages that it uses may have changed. Of interest would be to move
>>>>>>> the
>>>>>>> >>> > original files from Server A to Server B to see if they build
>>>>>>> correctly.
>>>>>>> >>> >
>>>>>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>> >>> >
>>>>>>> >>> >> No differences as far as I can see. The two:
>>>>>>> >>> >>
>>>>>>> >>> >> Server A: Esme built w/o problems Jan 5
>>>>>>> >>> >> Server B: Esme build error Jan 26
>>>>>>> >>> >>
>>>>>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>>>>>>> >>> >>
>>>>>>> >>> >> JDK same.
>>>>>>> >>> >>
>>>>>>> >>> >> Basically same-same :)
>>>>>>> >>> >>
>>>>>>> >>> >>
>>>>>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>>> >>> >> > What are the other differences on the two servers Sig?
>>>>>>> >>> >> >
>>>>>>> >>> >> > /Anne Kathrine
>>>>>>> >>> >> > Sent from my iPhone
>>>>>>> >>> >> >
>>>>>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>>>>>> >>> >> >
>>>>>>> >>> >> >> I have, on the other server that runs ok (except that original
>>>>>>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>>>>>> >>> >> >> same... (I'm sure that did not help much LOL)
>>>>>>> >>> >> >>
>>>>>>> >>> >> >>
>>>>>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>>> >>> >> >>>
>>>>>>> >>> >> >>> I don't think anything has changed. Just that no one has used
>>>>>>> >>> openJDK
>>>>>>> >>> >> >>> since
>>>>>>> >>> >> >>> then.
>>>>>>> >>> >> >>>
>>>>>>> >>> >> >>> /Anne Kathrine
>>>>>>> >>> >> >>> Sent from my iPhone
>>>>>>> >>> >> >>>
>>>>>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>>>>>>> hirsch.dick@gmail.com>
>>>>>>> >>> >> wrote:
>>>>>>> >>> >> >>>
>>>>>>> >>> >> >>>> But what has changed so that the problem now occurs?
>>>>>>> >>> >> >>>>
>>>>>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>>>> >>> >> >>>> <yo...@gmail.com>wrote:
>>>>>>> >>> >> >>>>
>>>>>>> >>> >> >>>>> Yay! :-)
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>> Aha :)
>>>>>>> >>> >> >>>>>>
>>>>>>> >>> >> >>>>>> java version "1.6.0_0"
>>>>>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>>>>> >>> (6b14-1.4.1-0ubuntu12)
>>>>>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>> >>> >> >>>>>>
>>>>>>> >>> >> >>>>>> Sig
>>>>>>> >>> >> >>>>>>
>>>>>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>>> We've had this before:
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>>>>>>> >>> >> suggestion
>>>>>>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>>>>>>> (or
>>>>>>> >>> was
>>>>>>> >>> >> >>>>>>> it?)
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>>>>>> >>> openjdk-6,
>>>>>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>>> Vassil
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>> >>> >> >>>>>>> <hi...@gmail.com>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> wrote:
>>>>>>> >>> >> >>>>>>>>
>>>>>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>> >>> >> >>>>>>>>
>>>>>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>>>>> >>> wrote:
>>>>>>> >>> >> >>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>>>>>> >>> up-to-date
>>>>>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>>>>> >>> starting
>>>>>>> >>> >> up
>>>>>>> >>> >> >>>>>>>>> a
>>>>>>> >>> >> >>>>>>>>> fresh image.
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Then:
>>>>>>> >>> >> >>>>>>>>> apt-get install subversion
>>>>>>> >>> >> >>>>>>>>> apt-get install maven2
>>>>>>> >>> >> >>>>>>>>> apt-get install jetty
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Then:
>>>>>>> >>> >> >>>>>>>>> svn checkout
>>>>>>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Then fixing the two files.
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Then problem :)
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>>>>>>> was
>>>>>>> >>> >> that
>>>>>>> >>> >> >>>>>>>>> I
>>>>>>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>>>>>>> mvn...
>>>>>>> >>> so
>>>>>>> >>> >> >>>>>>>>> now
>>>>>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Nope, exact same error.
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>>>>> dies
>>>>>>> >>> >> >>>>>>>>> after
>>>>>>> >>> >> >>>>>>>>> a
>>>>>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>>>>>>> No
>>>>>>> >>> other
>>>>>>> >>> >> >>>>>>>>> clues.
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>>>> >>> changed.
>>>>>>> >>> >> >>>>>>>>>> Has
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> anything
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>> else changed in the environment?
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>>>>> >>> problem,
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> because
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>>>>>> >>> weeks.
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>>>>>>> sig@rinde.com>
>>>>>>> >>> >> wrote:
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> Then I get this:
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> ------------------------------------------------------------------------
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> [INFO] null
>>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> ------------------------------------------------------------------------
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> [INFO] Trace
>>>>>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>>>>> then
>>>>>>> >>> >> all
>>>>>>> >>> >> >>>>>>>>>>> was
>>>>>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>>>>>>> sig@rinde.com>
>>>>>>> >>> >> >>>>>>>>>>>> wrote:
>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> Ethan,
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>>>>> >>> jetty:run"
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> Prior to that:
>>>>>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>>>>>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>>>>>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>>>>>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>>>>> >>> returned
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> non-zero
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> value:1
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> Method)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> Caused by:
>>>>>>> org.apache.maven.plugin.MojoFailureException:
>>>>>>> >>> >> >>>>>>>>>>>>> command
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> line
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >>
>>>>>>> >>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> ... 20 more
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>>>>>>> this
>>>>>>> >>> once
>>>>>>> >>> >> >>>>>>>>>>>>>> goes
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> deep
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>>>>>> somewhere
>>>>>>> >>> >> >>>>>>>>>>>>>> else?
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> And
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>>>>>>> this
>>>>>>> >>> >> >>>>>>>>>>>>>> error?
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> mvn
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>> clean install?
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>> Thanks,
>>>>>>> >>> >> >>>>>>>>>>>>>> Ethan
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>>>>>> >>> sig@rinde.com>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> wrote:
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>>>>>>> created a
>>>>>>> >>> new
>>>>>>> >>> >> >>>>>>>>>>>>>>> and
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> fresh
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>>>>>>> one),
>>>>>>> >>> >> >>>>>>>>>>>>>>> apt-get
>>>>>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>>>>>>> commented
>>>>>>> >>> out
>>>>>>> >>> >> >>>>>>>>>>>>>>> the
>>>>>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>>>>>>> pom.xml
>>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>>>>>>> /home/files/esme/server/src/test/scala/../scala
>>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> java.lang.StackOverflowError
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> ...
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> S
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>>>>> Unfortunately
>>>>>>> >>> I
>>>>>>> >>> >> >>>>>>>>>>>>>>>> don't
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> have
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>>>> >>> setting
>>>>>>> >>> >> >>>>>>>>>>>>>>>> for
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> the
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>>>> >>> >> >>>>>>>>>>>>>>>> Definitely
>>>>>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>>>>>>> line
>>>>>>> >>> in
>>>>>>> >>> >> >>>>>>>>>>>>>>>> the
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> property
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>>>>>> >>> does
>>>>>>> >>> >> >>>>>>>>>>>>>>>> that
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> user
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>>>>>>> >>> >> >>>>>>>>>>>>>>>> Ethan
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>>>>>> >>> sig@rinde.com
>>>>>>> >>> >> >
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> wrote:
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>>>> >>> anything
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> but
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> root,
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> say
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>>>>>>> same
>>>>>>> >>> >> problem
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> on
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> all
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>> browsers.
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>>>>>>> local
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> instance.
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>> (aws
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> is
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>>>>>>> webapp
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> folders
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> and
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> found
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>>>>> >>> removed
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> after
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> first
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> try).
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>>>>>>> found
>>>>>>> >>> no
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> diff
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> except
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>>>>>>> named
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> .gitignore.
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>>>>>>> in
>>>>>>> >>> >> there
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> so
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> I
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> can
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>>>>>> >>> later
>>>>>>> >>> >> new
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>> and
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>> fresh
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>>>>>>> browsers.
>>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>>
>>>>>>> >>> >> >>>>>>>>>
>>>>>>> >>> >> >>>>>>>>
>>>>>>> >>> >> >>>>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>>>
>>>>>>> >>> >> >>>
>>>>>>> >>> >> >
>>>>>>> >>> >>
>>>>>>> >>> >
>>>>>>> >>>
>>>>>>> >>
>>>>>>> >
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Yep, that took the cork out of the bottle - it built now!
So would that mess up something else or could you guys remove it or something?
Original (login) issue is still there though :)
2010/1/27 Vassil Dichev <vd...@apache.org>:
> By same problem you mean, of course, the StackOverflowError, which my
> commit wasn't trying to fix (it was for the
> UnsupportedOperationException).
>
> Anyway, what I currently found out is that the task that eventually fails is
>
> mvn scala:testCompile
>
> and if you remove ApiTest.scala, the error goes away.
>
>
> On Wed, Jan 27, 2010 at 10:54 AM, Sig Rinde <si...@rinde.com> wrote:
>> Did update now:
>>
>> root@ip-10-224-67-146:/home/files# svn checkout
>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>> U esme/server/src/main/scala/org/apache/esme/model/Privilege.scala
>> U esme/server/src/main/scala/org/apache/esme/actor/UserActor.scala
>>
>> Still same problem / error
>>
>>
>> 2010/1/27 Sig Rinde <si...@rinde.com>:
>>> When did you commit? Seconds before you sent this mail? If so I'll do
>>> another svn etc...
>>>
>>> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>>>> OK, I get the same error (StackOverflowError) on Windows, too.
>>>>
>>>> Meanwhile I have attempted to fix the UnsupportedOperationException
>>>> and committed, but we won't know if it works before we are able to
>>>> build.
>>>>
>>>>
>>>> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>>> Thanks.
>>>>>
>>>>> It must be Ubuntu 9.04 specific then.
>>>>>
>>>>> Does anyone else have a Ubuntu 9.04 environment where we could verify the
>>>>> bug?
>>>>>
>>>>> D.
>>>>>
>>>>>
>>>>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>
>>>>>> OK, switcehd to Sun jdk (I think(:
>>>>>>
>>>>>> java version "1.6.0_16"
>>>>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>>>>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>>>>>
>>>>>> Same result....
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>>>>>> > mvn -U clean jetty:run did nothing here...
>>>>>> >
>>>>>> > But why try another JDK when we know the esme built on Jan 5 still
>>>>>> > works, on both servers - while the one built today stubbornly will not
>>>>>> > build?
>>>>>> >
>>>>>> > Must be some file changes to what the svn delivers in that timespan or
>>>>>> what?
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>> >> Yep. I agree.
>>>>>> >>
>>>>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>>>>>> >> course, this a windows box....
>>>>>> >>
>>>>>> >> Could be based on OpenJDK or Ubuntu 9.04?
>>>>>> >>
>>>>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>> >>
>>>>>> >>> Aye aye capt'n, will do! Done:
>>>>>> >>>
>>>>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>>>>> >>> thing not pulled was the esme_db folder, assume that is created anew
>>>>>> >>> at start up).
>>>>>> >>>
>>>>>> >>> Result: Ya, that started!
>>>>>> >>>
>>>>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>>>>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>>>> >>>
>>>>>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>>>>> >>>
>>>>>> >>> So something happened with whatever the svn fetches after Jan 5....
>>>>>> >>> would be my educated guess.
>>>>>> >>>
>>>>>> >>>
>>>>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>>>>>> 26
>>>>>> >>> in
>>>>>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>>>>>> the
>>>>>> >>> > packages that it uses may have changed. Of interest would be to move
>>>>>> the
>>>>>> >>> > original files from Server A to Server B to see if they build
>>>>>> correctly.
>>>>>> >>> >
>>>>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>> >>> >
>>>>>> >>> >> No differences as far as I can see. The two:
>>>>>> >>> >>
>>>>>> >>> >> Server A: Esme built w/o problems Jan 5
>>>>>> >>> >> Server B: Esme build error Jan 26
>>>>>> >>> >>
>>>>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>>>>>> >>> >>
>>>>>> >>> >> JDK same.
>>>>>> >>> >>
>>>>>> >>> >> Basically same-same :)
>>>>>> >>> >>
>>>>>> >>> >>
>>>>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>> >>> >> > What are the other differences on the two servers Sig?
>>>>>> >>> >> >
>>>>>> >>> >> > /Anne Kathrine
>>>>>> >>> >> > Sent from my iPhone
>>>>>> >>> >> >
>>>>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>>>>> >>> >> >
>>>>>> >>> >> >> I have, on the other server that runs ok (except that original
>>>>>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>>>>> >>> >> >> same... (I'm sure that did not help much LOL)
>>>>>> >>> >> >>
>>>>>> >>> >> >>
>>>>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> I don't think anything has changed. Just that no one has used
>>>>>> >>> openJDK
>>>>>> >>> >> >>> since
>>>>>> >>> >> >>> then.
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> /Anne Kathrine
>>>>>> >>> >> >>> Sent from my iPhone
>>>>>> >>> >> >>>
>>>>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>>>>>> hirsch.dick@gmail.com>
>>>>>> >>> >> wrote:
>>>>>> >>> >> >>>
>>>>>> >>> >> >>>> But what has changed so that the problem now occurs?
>>>>>> >>> >> >>>>
>>>>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>>> >>> >> >>>> <yo...@gmail.com>wrote:
>>>>>> >>> >> >>>>
>>>>>> >>> >> >>>>> Yay! :-)
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>> Aha :)
>>>>>> >>> >> >>>>>>
>>>>>> >>> >> >>>>>> java version "1.6.0_0"
>>>>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>>>> >>> (6b14-1.4.1-0ubuntu12)
>>>>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>> >>> >> >>>>>>
>>>>>> >>> >> >>>>>> Sig
>>>>>> >>> >> >>>>>>
>>>>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>>> We've had this before:
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>>>>>> >>> >> suggestion
>>>>>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>>>>>> (or
>>>>>> >>> was
>>>>>> >>> >> >>>>>>> it?)
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>>>>> >>> openjdk-6,
>>>>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>>> Vassil
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>> >>> >> >>>>>>> <hi...@gmail.com>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> wrote:
>>>>>> >>> >> >>>>>>>>
>>>>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>> >>> >> >>>>>>>>
>>>>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>>>> >>> wrote:
>>>>>> >>> >> >>>>>>>>
>>>>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>>>>> >>> up-to-date
>>>>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>>>> >>> starting
>>>>>> >>> >> up
>>>>>> >>> >> >>>>>>>>> a
>>>>>> >>> >> >>>>>>>>> fresh image.
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> Then:
>>>>>> >>> >> >>>>>>>>> apt-get install subversion
>>>>>> >>> >> >>>>>>>>> apt-get install maven2
>>>>>> >>> >> >>>>>>>>> apt-get install jetty
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> Then:
>>>>>> >>> >> >>>>>>>>> svn checkout
>>>>>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> Then fixing the two files.
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> Then problem :)
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>>>>>> was
>>>>>> >>> >> that
>>>>>> >>> >> >>>>>>>>> I
>>>>>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>>>>>> mvn...
>>>>>> >>> so
>>>>>> >>> >> >>>>>>>>> now
>>>>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> Nope, exact same error.
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>>>> dies
>>>>>> >>> >> >>>>>>>>> after
>>>>>> >>> >> >>>>>>>>> a
>>>>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>>>>>> No
>>>>>> >>> other
>>>>>> >>> >> >>>>>>>>> clues.
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>>> >>> changed.
>>>>>> >>> >> >>>>>>>>>> Has
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> anything
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>> else changed in the environment?
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>>>> >>> problem,
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> because
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>>>>> >>> weeks.
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>>>>>> sig@rinde.com>
>>>>>> >>> >> wrote:
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> Then I get this:
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> ------------------------------------------------------------------------
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> [INFO] null
>>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> ------------------------------------------------------------------------
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> [INFO] Trace
>>>>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>>>>>> >>> >> >>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>>>> then
>>>>>> >>> >> all
>>>>>> >>> >> >>>>>>>>>>> was
>>>>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>> >>> >> >>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>> >>> >> >>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>>>>>> sig@rinde.com>
>>>>>> >>> >> >>>>>>>>>>>> wrote:
>>>>>> >>> >> >>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> Ethan,
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>>>> >>> jetty:run"
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> Prior to that:
>>>>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>>>>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>>>>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>>>>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>>>> >>> returned
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> non-zero
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> value:1
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> Method)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> java.lang.reflect.Method.invoke(Method.java:616)
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> Caused by:
>>>>>> org.apache.maven.plugin.MojoFailureException:
>>>>>> >>> >> >>>>>>>>>>>>> command
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> line
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >>
>>>>>> >>>
>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> ... 20 more
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>>>>>> this
>>>>>> >>> once
>>>>>> >>> >> >>>>>>>>>>>>>> goes
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> deep
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>>>>> somewhere
>>>>>> >>> >> >>>>>>>>>>>>>> else?
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> And
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>>>>>> this
>>>>>> >>> >> >>>>>>>>>>>>>> error?
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> mvn
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>> clean install?
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>> Thanks,
>>>>>> >>> >> >>>>>>>>>>>>>> Ethan
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>>>>> >>> sig@rinde.com>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> wrote:
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>>>>>> created a
>>>>>> >>> new
>>>>>> >>> >> >>>>>>>>>>>>>>> and
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> fresh
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>>>>>> one),
>>>>>> >>> >> >>>>>>>>>>>>>>> apt-get
>>>>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>>>>>> commented
>>>>>> >>> out
>>>>>> >>> >> >>>>>>>>>>>>>>> the
>>>>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>>>>>> pom.xml
>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>>>>>> /home/files/esme/server/src/test/scala/../scala
>>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> java.lang.StackOverflowError
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> ...
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> S
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>>>> Unfortunately
>>>>>> >>> I
>>>>>> >>> >> >>>>>>>>>>>>>>>> don't
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> have
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>>> >>> setting
>>>>>> >>> >> >>>>>>>>>>>>>>>> for
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> the
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>>> >>> >> >>>>>>>>>>>>>>>> Definitely
>>>>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>>>>>> line
>>>>>> >>> in
>>>>>> >>> >> >>>>>>>>>>>>>>>> the
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> property
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>>>>> >>> does
>>>>>> >>> >> >>>>>>>>>>>>>>>> that
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> user
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>>>>>> >>> >> >>>>>>>>>>>>>>>> Ethan
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>>>>> >>> sig@rinde.com
>>>>>> >>> >> >
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> wrote:
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>>> >>> anything
>>>>>> >>> >> >>>>>>>>>>>>>>>>> but
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> root,
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> say
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>>>>>> same
>>>>>> >>> >> problem
>>>>>> >>> >> >>>>>>>>>>>>>>>>> on
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> all
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>> browsers.
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>>>>>> local
>>>>>> >>> >> >>>>>>>>>>>>>>>>> instance.
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>> (aws
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> is
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>>>>>> webapp
>>>>>> >>> >> >>>>>>>>>>>>>>>>> folders
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> and
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> found
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>>>> >>> removed
>>>>>> >>> >> >>>>>>>>>>>>>>>>> after
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> first
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> try).
>>>>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>>>>>> found
>>>>>> >>> no
>>>>>> >>> >> >>>>>>>>>>>>>>>>> diff
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> except
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>>>>>> named
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> .gitignore.
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>>>>>> in
>>>>>> >>> >> there
>>>>>> >>> >> >>>>>>>>>>>>>>>>> so
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> I
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> can
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>>>>> >>> later
>>>>>> >>> >> new
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>> and
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>> fresh
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>> >>> >> >>>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>>>>>> browsers.
>>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>>
>>>>>> >>> >> >>>>>>>>>
>>>>>> >>> >> >>>>>>>>
>>>>>> >>> >> >>>>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>>>
>>>>>> >>> >> >>>
>>>>>> >>> >> >
>>>>>> >>> >>
>>>>>> >>> >
>>>>>> >>>
>>>>>> >>
>>>>>> >
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
APITest is from me not Ethan...
You can remove it if desired... would still be curious what it broke.
D.
On Wed, Jan 27, 2010 at 10:05 AM, Vassil Dichev <vd...@apache.org> wrote:
> By same problem you mean, of course, the StackOverflowError, which my
> commit wasn't trying to fix (it was for the
> UnsupportedOperationException).
>
> Anyway, what I currently found out is that the task that eventually fails
> is
>
> mvn scala:testCompile
>
> and if you remove ApiTest.scala, the error goes away.
>
>
> On Wed, Jan 27, 2010 at 10:54 AM, Sig Rinde <si...@rinde.com> wrote:
> > Did update now:
> >
> > root@ip-10-224-67-146:/home/files# svn checkout
> > http://svn.apache.org/repos/asf/incubator/esme/trunk esme
> > U esme/server/src/main/scala/org/apache/esme/model/Privilege.scala
> > U esme/server/src/main/scala/org/apache/esme/actor/UserActor.scala
> >
> > Still same problem / error
> >
> >
> > 2010/1/27 Sig Rinde <si...@rinde.com>:
> >> When did you commit? Seconds before you sent this mail? If so I'll do
> >> another svn etc...
> >>
> >> 2010/1/27 Vassil Dichev <vd...@apache.org>:
> >>> OK, I get the same error (StackOverflowError) on Windows, too.
> >>>
> >>> Meanwhile I have attempted to fix the UnsupportedOperationException
> >>> and committed, but we won't know if it works before we are able to
> >>> build.
> >>>
> >>>
> >>> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <
> hirsch.dick@gmail.com> wrote:
> >>>> Thanks.
> >>>>
> >>>> It must be Ubuntu 9.04 specific then.
> >>>>
> >>>> Does anyone else have a Ubuntu 9.04 environment where we could verify
> the
> >>>> bug?
> >>>>
> >>>> D.
> >>>>
> >>>>
> >>>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
> >>>>
> >>>>> OK, switcehd to Sun jdk (I think(:
> >>>>>
> >>>>> java version "1.6.0_16"
> >>>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> >>>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
> >>>>>
> >>>>> Same result....
> >>>>>
> >>>>>
> >>>>>
> >>>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
> >>>>> > mvn -U clean jetty:run did nothing here...
> >>>>> >
> >>>>> > But why try another JDK when we know the esme built on Jan 5 still
> >>>>> > works, on both servers - while the one built today stubbornly will
> not
> >>>>> > build?
> >>>>> >
> >>>>> > Must be some file changes to what the svn delivers in that timespan
> or
> >>>>> what?
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>> >> Yep. I agree.
> >>>>> >>
> >>>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it
> worked. Of
> >>>>> >> course, this a windows box....
> >>>>> >>
> >>>>> >> Could be based on OpenJDK or Ubuntu 9.04?
> >>>>> >>
> >>>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
> >>>>> >>
> >>>>> >>
> >>>>> >>
> >>>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
> >>>>> >>
> >>>>> >>> Aye aye capt'n, will do! Done:
> >>>>> >>>
> >>>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B
> (only
> >>>>> >>> thing not pulled was the esme_db folder, assume that is created
> anew
> >>>>> >>> at start up).
> >>>>> >>>
> >>>>> >>> Result: Ya, that started!
> >>>>> >>>
> >>>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
> >>>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
> >>>>> >>>
> >>>>> >>> Result: Oops that did not work as it's unversioned, duh... ah
> well etc
> >>>>> >>>
> >>>>> >>> So something happened with whatever the svn fetches after Jan
> 5....
> >>>>> >>> would be my educated guess.
> >>>>> >>>
> >>>>> >>>
> >>>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>> >>> > But we really don't know what changes happened between Jan 5
> and Jan
> >>>>> 26
> >>>>> >>> in
> >>>>> >>> > the packages pulled by maven. ESME might not have changed
> (much) but
> >>>>> the
> >>>>> >>> > packages that it uses may have changed. Of interest would be to
> move
> >>>>> the
> >>>>> >>> > original files from Server A to Server B to see if they build
> >>>>> correctly.
> >>>>> >>> >
> >>>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com>
> wrote:
> >>>>> >>> >
> >>>>> >>> >> No differences as far as I can see. The two:
> >>>>> >>> >>
> >>>>> >>> >> Server A: Esme built w/o problems Jan 5
> >>>>> >>> >> Server B: Esme build error Jan 26
> >>>>> >>> >>
> >>>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
> >>>>> >>> >>
> >>>>> >>> >> JDK same.
> >>>>> >>> >>
> >>>>> >>> >> Basically same-same :)
> >>>>> >>> >>
> >>>>> >>> >>
> >>>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> >>>>> >>> >> > What are the other differences on the two servers Sig?
> >>>>> >>> >> >
> >>>>> >>> >> > /Anne Kathrine
> >>>>> >>> >> > Sent from my iPhone
> >>>>> >>> >> >
> >>>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com>
> wrote:
> >>>>> >>> >> >
> >>>>> >>> >> >> I have, on the other server that runs ok (except that
> original
> >>>>> >>> >> >> api_test login issue) it's same OpenJDK, basically
> everything is
> >>>>> >>> >> >> same... (I'm sure that did not help much LOL)
> >>>>> >>> >> >>
> >>>>> >>> >> >>
> >>>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> >>>>> >>> >> >>>
> >>>>> >>> >> >>> I don't think anything has changed. Just that no one has
> used
> >>>>> >>> openJDK
> >>>>> >>> >> >>> since
> >>>>> >>> >> >>> then.
> >>>>> >>> >> >>>
> >>>>> >>> >> >>> /Anne Kathrine
> >>>>> >>> >> >>> Sent from my iPhone
> >>>>> >>> >> >>>
> >>>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
> >>>>> hirsch.dick@gmail.com>
> >>>>> >>> >> wrote:
> >>>>> >>> >> >>>
> >>>>> >>> >> >>>> But what has changed so that the problem now occurs?
> >>>>> >>> >> >>>>
> >>>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
> >>>>> >>> >> >>>> <yo...@gmail.com>wrote:
> >>>>> >>> >> >>>>
> >>>>> >>> >> >>>>> Yay! :-)
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>> Aha :)
> >>>>> >>> >> >>>>>>
> >>>>> >>> >> >>>>>> java version "1.6.0_0"
> >>>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
> >>>>> >>> (6b14-1.4.1-0ubuntu12)
> >>>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
> >>>>> >>> >> >>>>>>
> >>>>> >>> >> >>>>>> Sig
> >>>>> >>> >> >>>>>>
> >>>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>>> We've had this before:
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>>> The interesting part is that noone has implemented
> David's
> >>>>> >>> >> suggestion
> >>>>> >>> >> >>>>>>> to date, and still the problem seems to have been
> resolved
> >>>>> (or
> >>>>> >>> was
> >>>>> >>> >> >>>>>>> it?)
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of
> problems on
> >>>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to
> pull
> >>>>> >>> openjdk-6,
> >>>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>>> Vassil
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
> >>>>> >>> >> >>>>>>> <hi...@gmail.com>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> wrote:
> >>>>> >>> >> >>>>>>>>
> >>>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my
> laptop
> >>>>> >>> >> >>>>>>>>
> >>>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <
> sig@rinde.com>
> >>>>> >>> wrote:
> >>>>> >>> >> >>>>>>>>
> >>>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is
> absolutely
> >>>>> >>> up-to-date
> >>>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade
> after
> >>>>> >>> starting
> >>>>> >>> >> up
> >>>>> >>> >> >>>>>>>>> a
> >>>>> >>> >> >>>>>>>>> fresh image.
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> Then:
> >>>>> >>> >> >>>>>>>>> apt-get install subversion
> >>>>> >>> >> >>>>>>>>> apt-get install maven2
> >>>>> >>> >> >>>>>>>>> apt-get install jetty
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> Then:
> >>>>> >>> >> >>>>>>>>> svn checkout
> >>>>> >>> >> >>>>>>>>>
> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> Then fixing the two files.
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> Then problem :)
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only
> mishap
> >>>>> was
> >>>>> >>> >> that
> >>>>> >>> >> >>>>>>>>> I
> >>>>> >>> >> >>>>>>>>> lost contact with the server at some point during
> first
> >>>>> mvn...
> >>>>> >>> so
> >>>>> >>> >> >>>>>>>>> now
> >>>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see
> now:
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> Nope, exact same error.
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages,
> then
> >>>>> dies
> >>>>> >>> >> >>>>>>>>> after
> >>>>> >>> >> >>>>>>>>> a
> >>>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8
> packages.
> >>>>> No
> >>>>> >>> other
> >>>>> >>> >> >>>>>>>>> clues.
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might
> have
> >>>>> >>> changed.
> >>>>> >>> >> >>>>>>>>>> Has
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> anything
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>> else changed in the environment?
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a
> maven-related
> >>>>> >>> problem,
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> because
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the
> last few
> >>>>> >>> weeks.
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
> >>>>> sig@rinde.com>
> >>>>> >>> >> wrote:
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> Then I get this:
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
> >>>>> >>> >> >>>>>>>>>>> [INFO]
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>>
> ------------------------------------------------------------------------
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> [INFO] null
> >>>>> >>> >> >>>>>>>>>>> [INFO]
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>>
> ------------------------------------------------------------------------
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> [INFO] Trace
> >>>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
> >>>>> >>> >> >>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last
> time, and
> >>>>> then
> >>>>> >>> >> all
> >>>>> >>> >> >>>>>>>>>>> was
> >>>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>> >>> >> >>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
> >>>>> >>> >> >>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
> >>>>> sig@rinde.com>
> >>>>> >>> >> >>>>>>>>>>>> wrote:
> >>>>> >>> >> >>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> Ethan,
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using
> "mvn
> >>>>> >>> jetty:run"
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> Prior to that:
> >>>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
> >>>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
> >>>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
> >>>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command
> line
> >>>>> >>> returned
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> non-zero
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> value:1
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> Method)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> java.lang.reflect.Method.invoke(Method.java:616)
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>>
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>>
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> Caused by:
> >>>>> org.apache.maven.plugin.MojoFailureException:
> >>>>> >>> >> >>>>>>>>>>>>> command
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> line
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >>
> >>>>> >>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> ... 20 more
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't
> think
> >>>>> this
> >>>>> >>> once
> >>>>> >>> >> >>>>>>>>>>>>>> goes
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> deep
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
> >>>>> somewhere
> >>>>> >>> >> >>>>>>>>>>>>>> else?
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> And
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that
> results in
> >>>>> this
> >>>>> >>> >> >>>>>>>>>>>>>> error?
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> mvn
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>> clean install?
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>> Thanks,
> >>>>> >>> >> >>>>>>>>>>>>>> Ethan
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
> >>>>> >>> sig@rinde.com>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> wrote:
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
> >>>>> created a
> >>>>> >>> new
> >>>>> >>> >> >>>>>>>>>>>>>>> and
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> fresh
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other
> live
> >>>>> one),
> >>>>> >>> >> >>>>>>>>>>>>>>> apt-get
> >>>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
> >>>>> commented
> >>>>> >>> out
> >>>>> >>> >> >>>>>>>>>>>>>>> the
> >>>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion
> from
> >>>>> pom.xml
> >>>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
> >>>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
> >>>>> /home/files/esme/server/src/test/scala/../scala
> >>>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> java.lang.StackOverflowError
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>>
> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >>
> >>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >>
> >>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >>
> >>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >>
> >>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >>
> >>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> ...
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> S
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
> >>>>> Unfortunately
> >>>>> >>> I
> >>>>> >>> >> >>>>>>>>>>>>>>>> don't
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> have
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull
> in the
> >>>>> >>> setting
> >>>>> >>> >> >>>>>>>>>>>>>>>> for
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> the
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2
> code.
> >>>>> >>> >> >>>>>>>>>>>>>>>> Definitely
> >>>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add
> another
> >>>>> line
> >>>>> >>> in
> >>>>> >>> >> >>>>>>>>>>>>>>>> the
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> property
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration
> admin,
> >>>>> >>> does
> >>>>> >>> >> >>>>>>>>>>>>>>>> that
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> user
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
> >>>>> >>> >> >>>>>>>>>>>>>>>> Ethan
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
> >>>>> >>> sig@rinde.com
> >>>>> >>> >> >
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> wrote:
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
> >>>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out
> in
> >>>>> >>> anything
> >>>>> >>> >> >>>>>>>>>>>>>>>>> but
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> root,
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> say
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
> >>>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in
> root
> >>>>> same
> >>>>> >>> >> problem
> >>>>> >>> >> >>>>>>>>>>>>>>>>> on
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> all
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>> browsers.
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for
> my
> >>>>> local
> >>>>> >>> >> >>>>>>>>>>>>>>>>> instance.
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>> (aws
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> is
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
> >>>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and
> aws)
> >>>>> webapp
> >>>>> >>> >> >>>>>>>>>>>>>>>>> folders
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> and
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> found
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff
> which I
> >>>>> >>> removed
> >>>>> >>> >> >>>>>>>>>>>>>>>>> after
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> first
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> try).
> >>>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories
> and
> >>>>> found
> >>>>> >>> no
> >>>>> >>> >> >>>>>>>>>>>>>>>>> diff
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> except
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a
> file
> >>>>> named
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> .gitignore.
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how
> to get
> >>>>> in
> >>>>> >>> >> there
> >>>>> >>> >> >>>>>>>>>>>>>>>>> so
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> I
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> can
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away
> with a
> >>>>> >>> later
> >>>>> >>> >> new
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>> and
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>> fresh
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <
> hirsch.dick@gmail.com>:
> >>>>> >>> >> >>>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
> >>>>> browsers.
> >>>>> >>> >> >>>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>>
> >>>>> >>> >> >>>>>>>>>
> >>>>> >>> >> >>>>>>>>
> >>>>> >>> >> >>>>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>>>
> >>>>> >>> >> >>>
> >>>>> >>> >> >
> >>>>> >>> >>
> >>>>> >>> >
> >>>>> >>>
> >>>>> >>
> >>>>> >
> >>>>>
> >>>>
> >>>
> >>
> >
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
By same problem you mean, of course, the StackOverflowError, which my
commit wasn't trying to fix (it was for the
UnsupportedOperationException).
Anyway, what I currently found out is that the task that eventually fails is
mvn scala:testCompile
and if you remove ApiTest.scala, the error goes away.
On Wed, Jan 27, 2010 at 10:54 AM, Sig Rinde <si...@rinde.com> wrote:
> Did update now:
>
> root@ip-10-224-67-146:/home/files# svn checkout
> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
> U esme/server/src/main/scala/org/apache/esme/model/Privilege.scala
> U esme/server/src/main/scala/org/apache/esme/actor/UserActor.scala
>
> Still same problem / error
>
>
> 2010/1/27 Sig Rinde <si...@rinde.com>:
>> When did you commit? Seconds before you sent this mail? If so I'll do
>> another svn etc...
>>
>> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>>> OK, I get the same error (StackOverflowError) on Windows, too.
>>>
>>> Meanwhile I have attempted to fix the UnsupportedOperationException
>>> and committed, but we won't know if it works before we are able to
>>> build.
>>>
>>>
>>> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> Thanks.
>>>>
>>>> It must be Ubuntu 9.04 specific then.
>>>>
>>>> Does anyone else have a Ubuntu 9.04 environment where we could verify the
>>>> bug?
>>>>
>>>> D.
>>>>
>>>>
>>>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>
>>>>> OK, switcehd to Sun jdk (I think(:
>>>>>
>>>>> java version "1.6.0_16"
>>>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>>>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>>>>
>>>>> Same result....
>>>>>
>>>>>
>>>>>
>>>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>>>>> > mvn -U clean jetty:run did nothing here...
>>>>> >
>>>>> > But why try another JDK when we know the esme built on Jan 5 still
>>>>> > works, on both servers - while the one built today stubbornly will not
>>>>> > build?
>>>>> >
>>>>> > Must be some file changes to what the svn delivers in that timespan or
>>>>> what?
>>>>> >
>>>>> >
>>>>> >
>>>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>> >> Yep. I agree.
>>>>> >>
>>>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>>>>> >> course, this a windows box....
>>>>> >>
>>>>> >> Could be based on OpenJDK or Ubuntu 9.04?
>>>>> >>
>>>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>> >>
>>>>> >>> Aye aye capt'n, will do! Done:
>>>>> >>>
>>>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>>>> >>> thing not pulled was the esme_db folder, assume that is created anew
>>>>> >>> at start up).
>>>>> >>>
>>>>> >>> Result: Ya, that started!
>>>>> >>>
>>>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>>>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>>> >>>
>>>>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>>>> >>>
>>>>> >>> So something happened with whatever the svn fetches after Jan 5....
>>>>> >>> would be my educated guess.
>>>>> >>>
>>>>> >>>
>>>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>>>>> 26
>>>>> >>> in
>>>>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>>>>> the
>>>>> >>> > packages that it uses may have changed. Of interest would be to move
>>>>> the
>>>>> >>> > original files from Server A to Server B to see if they build
>>>>> correctly.
>>>>> >>> >
>>>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>> >>> >
>>>>> >>> >> No differences as far as I can see. The two:
>>>>> >>> >>
>>>>> >>> >> Server A: Esme built w/o problems Jan 5
>>>>> >>> >> Server B: Esme build error Jan 26
>>>>> >>> >>
>>>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>>>>> >>> >>
>>>>> >>> >> JDK same.
>>>>> >>> >>
>>>>> >>> >> Basically same-same :)
>>>>> >>> >>
>>>>> >>> >>
>>>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>> >>> >> > What are the other differences on the two servers Sig?
>>>>> >>> >> >
>>>>> >>> >> > /Anne Kathrine
>>>>> >>> >> > Sent from my iPhone
>>>>> >>> >> >
>>>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>>>> >>> >> >
>>>>> >>> >> >> I have, on the other server that runs ok (except that original
>>>>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>>>> >>> >> >> same... (I'm sure that did not help much LOL)
>>>>> >>> >> >>
>>>>> >>> >> >>
>>>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>>> >>> >> >>>
>>>>> >>> >> >>> I don't think anything has changed. Just that no one has used
>>>>> >>> openJDK
>>>>> >>> >> >>> since
>>>>> >>> >> >>> then.
>>>>> >>> >> >>>
>>>>> >>> >> >>> /Anne Kathrine
>>>>> >>> >> >>> Sent from my iPhone
>>>>> >>> >> >>>
>>>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>>>>> hirsch.dick@gmail.com>
>>>>> >>> >> wrote:
>>>>> >>> >> >>>
>>>>> >>> >> >>>> But what has changed so that the problem now occurs?
>>>>> >>> >> >>>>
>>>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>> >>> >> >>>> <yo...@gmail.com>wrote:
>>>>> >>> >> >>>>
>>>>> >>> >> >>>>> Yay! :-)
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>> Aha :)
>>>>> >>> >> >>>>>>
>>>>> >>> >> >>>>>> java version "1.6.0_0"
>>>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>>> >>> (6b14-1.4.1-0ubuntu12)
>>>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>> >>> >> >>>>>>
>>>>> >>> >> >>>>>> Sig
>>>>> >>> >> >>>>>>
>>>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>>> We've had this before:
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>>>>> >>> >> suggestion
>>>>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>>>>> (or
>>>>> >>> was
>>>>> >>> >> >>>>>>> it?)
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>>>> >>> openjdk-6,
>>>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>>> Vassil
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>> >>> >> >>>>>>> <hi...@gmail.com>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> wrote:
>>>>> >>> >> >>>>>>>>
>>>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>> >>> >> >>>>>>>>
>>>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>>> >>> wrote:
>>>>> >>> >> >>>>>>>>
>>>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>>>> >>> up-to-date
>>>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>>> >>> starting
>>>>> >>> >> up
>>>>> >>> >> >>>>>>>>> a
>>>>> >>> >> >>>>>>>>> fresh image.
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> Then:
>>>>> >>> >> >>>>>>>>> apt-get install subversion
>>>>> >>> >> >>>>>>>>> apt-get install maven2
>>>>> >>> >> >>>>>>>>> apt-get install jetty
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> Then:
>>>>> >>> >> >>>>>>>>> svn checkout
>>>>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> Then fixing the two files.
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> Then problem :)
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>>>>> was
>>>>> >>> >> that
>>>>> >>> >> >>>>>>>>> I
>>>>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>>>>> mvn...
>>>>> >>> so
>>>>> >>> >> >>>>>>>>> now
>>>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> Nope, exact same error.
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>>> dies
>>>>> >>> >> >>>>>>>>> after
>>>>> >>> >> >>>>>>>>> a
>>>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>>>>> No
>>>>> >>> other
>>>>> >>> >> >>>>>>>>> clues.
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>> >>> changed.
>>>>> >>> >> >>>>>>>>>> Has
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> anything
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>> else changed in the environment?
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>>> >>> problem,
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> because
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>>>> >>> weeks.
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>>>>> sig@rinde.com>
>>>>> >>> >> wrote:
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> Then I get this:
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> ------------------------------------------------------------------------
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> [INFO] null
>>>>> >>> >> >>>>>>>>>>> [INFO]
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> ------------------------------------------------------------------------
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> [INFO] Trace
>>>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>>>>> >>> >> >>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>>> then
>>>>> >>> >> all
>>>>> >>> >> >>>>>>>>>>> was
>>>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>> >>> >> >>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>> >>> >> >>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>>>>> sig@rinde.com>
>>>>> >>> >> >>>>>>>>>>>> wrote:
>>>>> >>> >> >>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> Ethan,
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>>> >>> jetty:run"
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> Prior to that:
>>>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>>>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>>>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>>>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>>> >>> returned
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> non-zero
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> value:1
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> Method)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> java.lang.reflect.Method.invoke(Method.java:616)
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> Caused by:
>>>>> org.apache.maven.plugin.MojoFailureException:
>>>>> >>> >> >>>>>>>>>>>>> command
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> line
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >>
>>>>> >>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> ... 20 more
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>>>>> this
>>>>> >>> once
>>>>> >>> >> >>>>>>>>>>>>>> goes
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> deep
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>>>> somewhere
>>>>> >>> >> >>>>>>>>>>>>>> else?
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> And
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>>>>> this
>>>>> >>> >> >>>>>>>>>>>>>> error?
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> mvn
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>> clean install?
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>> Thanks,
>>>>> >>> >> >>>>>>>>>>>>>> Ethan
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>>>> >>> sig@rinde.com>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> wrote:
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>>>>> created a
>>>>> >>> new
>>>>> >>> >> >>>>>>>>>>>>>>> and
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> fresh
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>>>>> one),
>>>>> >>> >> >>>>>>>>>>>>>>> apt-get
>>>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>>>>> commented
>>>>> >>> out
>>>>> >>> >> >>>>>>>>>>>>>>> the
>>>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>>>>> pom.xml
>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>>>>> /home/files/esme/server/src/test/scala/../scala
>>>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> java.lang.StackOverflowError
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >>
>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >>
>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >>
>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >>
>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >>
>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> ...
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> S
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>>> Unfortunately
>>>>> >>> I
>>>>> >>> >> >>>>>>>>>>>>>>>> don't
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> have
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>> >>> setting
>>>>> >>> >> >>>>>>>>>>>>>>>> for
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> the
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>> >>> >> >>>>>>>>>>>>>>>> Definitely
>>>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>>>>> line
>>>>> >>> in
>>>>> >>> >> >>>>>>>>>>>>>>>> the
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> property
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>>>> >>> does
>>>>> >>> >> >>>>>>>>>>>>>>>> that
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> user
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>>>>> >>> >> >>>>>>>>>>>>>>>> Ethan
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>>>> >>> sig@rinde.com
>>>>> >>> >> >
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> wrote:
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>> >>> anything
>>>>> >>> >> >>>>>>>>>>>>>>>>> but
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> root,
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> say
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>>>>> same
>>>>> >>> >> problem
>>>>> >>> >> >>>>>>>>>>>>>>>>> on
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> all
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>> browsers.
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>>>>> local
>>>>> >>> >> >>>>>>>>>>>>>>>>> instance.
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>> (aws
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> is
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>>>>> webapp
>>>>> >>> >> >>>>>>>>>>>>>>>>> folders
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> and
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> found
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>>> >>> removed
>>>>> >>> >> >>>>>>>>>>>>>>>>> after
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> first
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> try).
>>>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>>>>> found
>>>>> >>> no
>>>>> >>> >> >>>>>>>>>>>>>>>>> diff
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> except
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>>>>> named
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> .gitignore.
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>>>>> in
>>>>> >>> >> there
>>>>> >>> >> >>>>>>>>>>>>>>>>> so
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> I
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> can
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>>>> >>> later
>>>>> >>> >> new
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>> and
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>> fresh
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>> >>> >> >>>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>>>>> browsers.
>>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>>
>>>>> >>> >> >>>>>>>>>>
>>>>> >>> >> >>>>>>>>>
>>>>> >>> >> >>>>>>>>
>>>>> >>> >> >>>>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>>>
>>>>> >>> >> >>>
>>>>> >>> >> >
>>>>> >>> >>
>>>>> >>> >
>>>>> >>>
>>>>> >>
>>>>> >
>>>>>
>>>>
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Did update now:
root@ip-10-224-67-146:/home/files# svn checkout
http://svn.apache.org/repos/asf/incubator/esme/trunk esme
U esme/server/src/main/scala/org/apache/esme/model/Privilege.scala
U esme/server/src/main/scala/org/apache/esme/actor/UserActor.scala
Still same problem / error
2010/1/27 Sig Rinde <si...@rinde.com>:
> When did you commit? Seconds before you sent this mail? If so I'll do
> another svn etc...
>
> 2010/1/27 Vassil Dichev <vd...@apache.org>:
>> OK, I get the same error (StackOverflowError) on Windows, too.
>>
>> Meanwhile I have attempted to fix the UnsupportedOperationException
>> and committed, but we won't know if it works before we are able to
>> build.
>>
>>
>> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
>>> Thanks.
>>>
>>> It must be Ubuntu 9.04 specific then.
>>>
>>> Does anyone else have a Ubuntu 9.04 environment where we could verify the
>>> bug?
>>>
>>> D.
>>>
>>>
>>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>>>
>>>> OK, switcehd to Sun jdk (I think(:
>>>>
>>>> java version "1.6.0_16"
>>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>>>
>>>> Same result....
>>>>
>>>>
>>>>
>>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>>>> > mvn -U clean jetty:run did nothing here...
>>>> >
>>>> > But why try another JDK when we know the esme built on Jan 5 still
>>>> > works, on both servers - while the one built today stubbornly will not
>>>> > build?
>>>> >
>>>> > Must be some file changes to what the svn delivers in that timespan or
>>>> what?
>>>> >
>>>> >
>>>> >
>>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>> >> Yep. I agree.
>>>> >>
>>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>>>> >> course, this a windows box....
>>>> >>
>>>> >> Could be based on OpenJDK or Ubuntu 9.04?
>>>> >>
>>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>> >>
>>>> >>> Aye aye capt'n, will do! Done:
>>>> >>>
>>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>>> >>> thing not pulled was the esme_db folder, assume that is created anew
>>>> >>> at start up).
>>>> >>>
>>>> >>> Result: Ya, that started!
>>>> >>>
>>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>> >>>
>>>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>>> >>>
>>>> >>> So something happened with whatever the svn fetches after Jan 5....
>>>> >>> would be my educated guess.
>>>> >>>
>>>> >>>
>>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>>>> 26
>>>> >>> in
>>>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>>>> the
>>>> >>> > packages that it uses may have changed. Of interest would be to move
>>>> the
>>>> >>> > original files from Server A to Server B to see if they build
>>>> correctly.
>>>> >>> >
>>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>>> >>> >
>>>> >>> >> No differences as far as I can see. The two:
>>>> >>> >>
>>>> >>> >> Server A: Esme built w/o problems Jan 5
>>>> >>> >> Server B: Esme build error Jan 26
>>>> >>> >>
>>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>>>> >>> >>
>>>> >>> >> JDK same.
>>>> >>> >>
>>>> >>> >> Basically same-same :)
>>>> >>> >>
>>>> >>> >>
>>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>> >>> >> > What are the other differences on the two servers Sig?
>>>> >>> >> >
>>>> >>> >> > /Anne Kathrine
>>>> >>> >> > Sent from my iPhone
>>>> >>> >> >
>>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>>> >>> >> >
>>>> >>> >> >> I have, on the other server that runs ok (except that original
>>>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>>> >>> >> >> same... (I'm sure that did not help much LOL)
>>>> >>> >> >>
>>>> >>> >> >>
>>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>> >>> >> >>>
>>>> >>> >> >>> I don't think anything has changed. Just that no one has used
>>>> >>> openJDK
>>>> >>> >> >>> since
>>>> >>> >> >>> then.
>>>> >>> >> >>>
>>>> >>> >> >>> /Anne Kathrine
>>>> >>> >> >>> Sent from my iPhone
>>>> >>> >> >>>
>>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>>>> hirsch.dick@gmail.com>
>>>> >>> >> wrote:
>>>> >>> >> >>>
>>>> >>> >> >>>> But what has changed so that the problem now occurs?
>>>> >>> >> >>>>
>>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>> >>> >> >>>> <yo...@gmail.com>wrote:
>>>> >>> >> >>>>
>>>> >>> >> >>>>> Yay! :-)
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>> Aha :)
>>>> >>> >> >>>>>>
>>>> >>> >> >>>>>> java version "1.6.0_0"
>>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>> >>> (6b14-1.4.1-0ubuntu12)
>>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>> >>> >> >>>>>>
>>>> >>> >> >>>>>> Sig
>>>> >>> >> >>>>>>
>>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>>> We've had this before:
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>>>> >>> >> suggestion
>>>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>>>> (or
>>>> >>> was
>>>> >>> >> >>>>>>> it?)
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>>> >>> openjdk-6,
>>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>>> Vassil
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>> >>> >> >>>>>>> <hi...@gmail.com>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> wrote:
>>>> >>> >> >>>>>>>>
>>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>> >>> >> >>>>>>>>
>>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>> >>> wrote:
>>>> >>> >> >>>>>>>>
>>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>>> >>> up-to-date
>>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>> >>> starting
>>>> >>> >> up
>>>> >>> >> >>>>>>>>> a
>>>> >>> >> >>>>>>>>> fresh image.
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> Then:
>>>> >>> >> >>>>>>>>> apt-get install subversion
>>>> >>> >> >>>>>>>>> apt-get install maven2
>>>> >>> >> >>>>>>>>> apt-get install jetty
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> Then:
>>>> >>> >> >>>>>>>>> svn checkout
>>>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> Then fixing the two files.
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> Then problem :)
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>>>> was
>>>> >>> >> that
>>>> >>> >> >>>>>>>>> I
>>>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>>>> mvn...
>>>> >>> so
>>>> >>> >> >>>>>>>>> now
>>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> Nope, exact same error.
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>> dies
>>>> >>> >> >>>>>>>>> after
>>>> >>> >> >>>>>>>>> a
>>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>>>> No
>>>> >>> other
>>>> >>> >> >>>>>>>>> clues.
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>> >>> changed.
>>>> >>> >> >>>>>>>>>> Has
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> anything
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>> else changed in the environment?
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>> >>> problem,
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> because
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>>> >>> weeks.
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>>>> sig@rinde.com>
>>>> >>> >> wrote:
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> Then I get this:
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>>> >>> >> >>>>>>>>>>> [INFO]
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> ------------------------------------------------------------------------
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> [INFO] null
>>>> >>> >> >>>>>>>>>>> [INFO]
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> ------------------------------------------------------------------------
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> [INFO] Trace
>>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>>>> >>> >> >>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>> then
>>>> >>> >> all
>>>> >>> >> >>>>>>>>>>> was
>>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>> >>> >> >>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>> >>> >> >>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>>>> sig@rinde.com>
>>>> >>> >> >>>>>>>>>>>> wrote:
>>>> >>> >> >>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> Ethan,
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>> >>> jetty:run"
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> Prior to that:
>>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>> >>> returned
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> non-zero
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> value:1
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>> >>> >> >>>>>>>>>>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> Method)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> java.lang.reflect.Method.invoke(Method.java:616)
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> Caused by:
>>>> org.apache.maven.plugin.MojoFailureException:
>>>> >>> >> >>>>>>>>>>>>> command
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> line
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >>
>>>> >>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> ... 20 more
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>>>> this
>>>> >>> once
>>>> >>> >> >>>>>>>>>>>>>> goes
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> deep
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>>> somewhere
>>>> >>> >> >>>>>>>>>>>>>> else?
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> And
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>>>> this
>>>> >>> >> >>>>>>>>>>>>>> error?
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> mvn
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>> clean install?
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>> Thanks,
>>>> >>> >> >>>>>>>>>>>>>> Ethan
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>>> >>> sig@rinde.com>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> wrote:
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>>>> created a
>>>> >>> new
>>>> >>> >> >>>>>>>>>>>>>>> and
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> fresh
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>>>> one),
>>>> >>> >> >>>>>>>>>>>>>>> apt-get
>>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>>>> commented
>>>> >>> out
>>>> >>> >> >>>>>>>>>>>>>>> the
>>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>>>> pom.xml
>>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>>>> /home/files/esme/server/src/test/scala/../scala
>>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> java.lang.StackOverflowError
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>
>>>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> ...
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> S
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>> Unfortunately
>>>> >>> I
>>>> >>> >> >>>>>>>>>>>>>>>> don't
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> have
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>> >>> setting
>>>> >>> >> >>>>>>>>>>>>>>>> for
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> the
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>> >>> >> >>>>>>>>>>>>>>>> Definitely
>>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>>>> line
>>>> >>> in
>>>> >>> >> >>>>>>>>>>>>>>>> the
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> property
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>>> >>> does
>>>> >>> >> >>>>>>>>>>>>>>>> that
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> user
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>>>> >>> >> >>>>>>>>>>>>>>>> Ethan
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>>> >>> sig@rinde.com
>>>> >>> >> >
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> wrote:
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>> >>> anything
>>>> >>> >> >>>>>>>>>>>>>>>>> but
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> root,
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> say
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>>>> same
>>>> >>> >> problem
>>>> >>> >> >>>>>>>>>>>>>>>>> on
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> all
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>> browsers.
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>>>> local
>>>> >>> >> >>>>>>>>>>>>>>>>> instance.
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>> (aws
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> is
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>>>> webapp
>>>> >>> >> >>>>>>>>>>>>>>>>> folders
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> and
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> found
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>> >>> removed
>>>> >>> >> >>>>>>>>>>>>>>>>> after
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> first
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> try).
>>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>>>> found
>>>> >>> no
>>>> >>> >> >>>>>>>>>>>>>>>>> diff
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> except
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>>>> named
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> .gitignore.
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>>>> in
>>>> >>> >> there
>>>> >>> >> >>>>>>>>>>>>>>>>> so
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> I
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> can
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>>> >>> later
>>>> >>> >> new
>>>> >>> >> >>>>>
>>>> >>> >> >>>>> and
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>> fresh
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>> >>> >> >>>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>>>> browsers.
>>>> >>> >> >>>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>>
>>>> >>> >> >>>>>>>>>>
>>>> >>> >> >>>>>>>>>
>>>> >>> >> >>>>>>>>
>>>> >>> >> >>>>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>>>
>>>> >>> >> >>>
>>>> >>> >> >
>>>> >>> >>
>>>> >>> >
>>>> >>>
>>>> >>
>>>> >
>>>>
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
When did you commit? Seconds before you sent this mail? If so I'll do
another svn etc...
2010/1/27 Vassil Dichev <vd...@apache.org>:
> OK, I get the same error (StackOverflowError) on Windows, too.
>
> Meanwhile I have attempted to fix the UnsupportedOperationException
> and committed, but we won't know if it works before we are able to
> build.
>
>
> On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
>> Thanks.
>>
>> It must be Ubuntu 9.04 specific then.
>>
>> Does anyone else have a Ubuntu 9.04 environment where we could verify the
>> bug?
>>
>> D.
>>
>>
>> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>>
>>> OK, switcehd to Sun jdk (I think(:
>>>
>>> java version "1.6.0_16"
>>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>>
>>> Same result....
>>>
>>>
>>>
>>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>>> > mvn -U clean jetty:run did nothing here...
>>> >
>>> > But why try another JDK when we know the esme built on Jan 5 still
>>> > works, on both servers - while the one built today stubbornly will not
>>> > build?
>>> >
>>> > Must be some file changes to what the svn delivers in that timespan or
>>> what?
>>> >
>>> >
>>> >
>>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> >> Yep. I agree.
>>> >>
>>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>>> >> course, this a windows box....
>>> >>
>>> >> Could be based on OpenJDK or Ubuntu 9.04?
>>> >>
>>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>>> >>
>>> >>
>>> >>
>>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>> >>
>>> >>> Aye aye capt'n, will do! Done:
>>> >>>
>>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>> >>> thing not pulled was the esme_db folder, assume that is created anew
>>> >>> at start up).
>>> >>>
>>> >>> Result: Ya, that started!
>>> >>>
>>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>> >>>
>>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>> >>>
>>> >>> So something happened with whatever the svn fetches after Jan 5....
>>> >>> would be my educated guess.
>>> >>>
>>> >>>
>>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>>> 26
>>> >>> in
>>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>>> the
>>> >>> > packages that it uses may have changed. Of interest would be to move
>>> the
>>> >>> > original files from Server A to Server B to see if they build
>>> correctly.
>>> >>> >
>>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>> >>> >
>>> >>> >> No differences as far as I can see. The two:
>>> >>> >>
>>> >>> >> Server A: Esme built w/o problems Jan 5
>>> >>> >> Server B: Esme build error Jan 26
>>> >>> >>
>>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>>> >>> >>
>>> >>> >> JDK same.
>>> >>> >>
>>> >>> >> Basically same-same :)
>>> >>> >>
>>> >>> >>
>>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>> >>> >> > What are the other differences on the two servers Sig?
>>> >>> >> >
>>> >>> >> > /Anne Kathrine
>>> >>> >> > Sent from my iPhone
>>> >>> >> >
>>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>> >>> >> >
>>> >>> >> >> I have, on the other server that runs ok (except that original
>>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>> >>> >> >> same... (I'm sure that did not help much LOL)
>>> >>> >> >>
>>> >>> >> >>
>>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>> >>> >> >>>
>>> >>> >> >>> I don't think anything has changed. Just that no one has used
>>> >>> openJDK
>>> >>> >> >>> since
>>> >>> >> >>> then.
>>> >>> >> >>>
>>> >>> >> >>> /Anne Kathrine
>>> >>> >> >>> Sent from my iPhone
>>> >>> >> >>>
>>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>>> hirsch.dick@gmail.com>
>>> >>> >> wrote:
>>> >>> >> >>>
>>> >>> >> >>>> But what has changed so that the problem now occurs?
>>> >>> >> >>>>
>>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>> >>> >> >>>> <yo...@gmail.com>wrote:
>>> >>> >> >>>>
>>> >>> >> >>>>> Yay! :-)
>>> >>> >> >>>>>
>>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>> >>> >> >>>>>
>>> >>> >> >>>>>> Aha :)
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> java version "1.6.0_0"
>>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>> >>> (6b14-1.4.1-0ubuntu12)
>>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> Sig
>>> >>> >> >>>>>>
>>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> We've had this before:
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>>> >>> >> suggestion
>>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>>> (or
>>> >>> was
>>> >>> >> >>>>>>> it?)
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>> >>> openjdk-6,
>>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> Vassil
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>> >>> >> >>>>>>> <hi...@gmail.com>
>>> >>> >> >>>>>
>>> >>> >> >>>>> wrote:
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>> >>> wrote:
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>> >>> up-to-date
>>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>> >>> starting
>>> >>> >> up
>>> >>> >> >>>>>>>>> a
>>> >>> >> >>>>>>>>> fresh image.
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Then:
>>> >>> >> >>>>>>>>> apt-get install subversion
>>> >>> >> >>>>>>>>> apt-get install maven2
>>> >>> >> >>>>>>>>> apt-get install jetty
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Then:
>>> >>> >> >>>>>>>>> svn checkout
>>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Then fixing the two files.
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Then problem :)
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>>> was
>>> >>> >> that
>>> >>> >> >>>>>>>>> I
>>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>>> mvn...
>>> >>> so
>>> >>> >> >>>>>>>>> now
>>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Nope, exact same error.
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>> dies
>>> >>> >> >>>>>>>>> after
>>> >>> >> >>>>>>>>> a
>>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>>> No
>>> >>> other
>>> >>> >> >>>>>>>>> clues.
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>> >>> changed.
>>> >>> >> >>>>>>>>>> Has
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> anything
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> else changed in the environment?
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>> >>> problem,
>>> >>> >> >>>>>
>>> >>> >> >>>>> because
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>> >>> weeks.
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>>> sig@rinde.com>
>>> >>> >> wrote:
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>>> Then I get this:
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>> >>> >> >>>>>>>>>>> [INFO]
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> ------------------------------------------------------------------------
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> [INFO] null
>>> >>> >> >>>>>>>>>>> [INFO]
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> ------------------------------------------------------------------------
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> [INFO] Trace
>>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>>> >>> >> >>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>> then
>>> >>> >> all
>>> >>> >> >>>>>>>>>>> was
>>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> >>> >> >>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>> >>> >> >>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>>> sig@rinde.com>
>>> >>> >> >>>>>>>>>>>> wrote:
>>> >>> >> >>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> Ethan,
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>> >>> jetty:run"
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> Prior to that:
>>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>> >>> returned
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> non-zero
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> value:1
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>> >>> >> >>>>>>>>>>>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> >>> >> >>>>>
>>> >>> >> >>>>> Method)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> java.lang.reflect.Method.invoke(Method.java:616)
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>
>>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>
>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>
>>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>
>>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> Caused by:
>>> org.apache.maven.plugin.MojoFailureException:
>>> >>> >> >>>>>>>>>>>>> command
>>> >>> >> >>>>>
>>> >>> >> >>>>> line
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>
>>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >>
>>> >>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> ... 20 more
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>>> this
>>> >>> once
>>> >>> >> >>>>>>>>>>>>>> goes
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> deep
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>> somewhere
>>> >>> >> >>>>>>>>>>>>>> else?
>>> >>> >> >>>>>
>>> >>> >> >>>>> And
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>>> this
>>> >>> >> >>>>>>>>>>>>>> error?
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> mvn
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>> clean install?
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>> Thanks,
>>> >>> >> >>>>>>>>>>>>>> Ethan
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>> >>> sig@rinde.com>
>>> >>> >> >>>>>
>>> >>> >> >>>>> wrote:
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>>> created a
>>> >>> new
>>> >>> >> >>>>>>>>>>>>>>> and
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> fresh
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>>> one),
>>> >>> >> >>>>>>>>>>>>>>> apt-get
>>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>>> commented
>>> >>> out
>>> >>> >> >>>>>>>>>>>>>>> the
>>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>>> pom.xml
>>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>>> /home/files/esme/server/src/test/scala/../scala
>>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>> >>> >> >>>>>
>>> >>> >> >>>>> java.lang.StackOverflowError
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>
>>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> ...
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> S
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>> Unfortunately
>>> >>> I
>>> >>> >> >>>>>>>>>>>>>>>> don't
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> have
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>> >>> setting
>>> >>> >> >>>>>>>>>>>>>>>> for
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> the
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>> >>> >> >>>>>>>>>>>>>>>> Definitely
>>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>>> line
>>> >>> in
>>> >>> >> >>>>>>>>>>>>>>>> the
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> property
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>> >>> does
>>> >>> >> >>>>>>>>>>>>>>>> that
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> user
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>>> >>> >> >>>>>>>>>>>>>>>> Ethan
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>> >>> sig@rinde.com
>>> >>> >> >
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> wrote:
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>> >>> anything
>>> >>> >> >>>>>>>>>>>>>>>>> but
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> root,
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> say
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>>> same
>>> >>> >> problem
>>> >>> >> >>>>>>>>>>>>>>>>> on
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> all
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>> browsers.
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>>> local
>>> >>> >> >>>>>>>>>>>>>>>>> instance.
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>> (aws
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> is
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>>> webapp
>>> >>> >> >>>>>>>>>>>>>>>>> folders
>>> >>> >> >>>>>
>>> >>> >> >>>>> and
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> found
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>> >>> removed
>>> >>> >> >>>>>>>>>>>>>>>>> after
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> first
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> try).
>>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>>> found
>>> >>> no
>>> >>> >> >>>>>>>>>>>>>>>>> diff
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> except
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>>> named
>>> >>> >> >>>>>
>>> >>> >> >>>>> .gitignore.
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>>> in
>>> >>> >> there
>>> >>> >> >>>>>>>>>>>>>>>>> so
>>> >>> >> >>>>>
>>> >>> >> >>>>> I
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> can
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>> >>> later
>>> >>> >> new
>>> >>> >> >>>>>
>>> >>> >> >>>>> and
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>> fresh
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>> >>> >> >>>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>>> browsers.
>>> >>> >> >>>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>>
>>> >>> >> >>>>>>>>>>>
>>> >>> >> >>>>>>>>>>
>>> >>> >> >>>>>>>>>
>>> >>> >> >>>>>>>>
>>> >>> >> >>>>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>>>
>>> >>> >> >>>
>>> >>> >> >
>>> >>> >>
>>> >>> >
>>> >>>
>>> >>
>>> >
>>>
>>
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
OK, I get the same error (StackOverflowError) on Windows, too.
Meanwhile I have attempted to fix the UnsupportedOperationException
and committed, but we won't know if it works before we are able to
build.
On Wed, Jan 27, 2010 at 10:31 AM, Richard Hirsch <hi...@gmail.com> wrote:
> Thanks.
>
> It must be Ubuntu 9.04 specific then.
>
> Does anyone else have a Ubuntu 9.04 environment where we could verify the
> bug?
>
> D.
>
>
> On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> OK, switcehd to Sun jdk (I think(:
>>
>> java version "1.6.0_16"
>> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
>> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>>
>> Same result....
>>
>>
>>
>> 2010/1/26 Sig Rinde <si...@rinde.com>:
>> > mvn -U clean jetty:run did nothing here...
>> >
>> > But why try another JDK when we know the esme built on Jan 5 still
>> > works, on both servers - while the one built today stubbornly will not
>> > build?
>> >
>> > Must be some file changes to what the svn delivers in that timespan or
>> what?
>> >
>> >
>> >
>> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >> Yep. I agree.
>> >>
>> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>> >> course, this a windows box....
>> >>
>> >> Could be based on OpenJDK or Ubuntu 9.04?
>> >>
>> >> @Sig: Maybe you could try the "normal" Sun JDK.
>> >>
>> >>
>> >>
>> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>> >>
>> >>> Aye aye capt'n, will do! Done:
>> >>>
>> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>> >>> thing not pulled was the esme_db folder, assume that is created anew
>> >>> at start up).
>> >>>
>> >>> Result: Ya, that started!
>> >>>
>> >>> 2. Looking for changes in esme svn I did the full svn checkout
>> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>> >>>
>> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>> >>>
>> >>> So something happened with whatever the svn fetches after Jan 5....
>> >>> would be my educated guess.
>> >>>
>> >>>
>> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>> > But we really don't know what changes happened between Jan 5 and Jan
>> 26
>> >>> in
>> >>> > the packages pulled by maven. ESME might not have changed (much) but
>> the
>> >>> > packages that it uses may have changed. Of interest would be to move
>> the
>> >>> > original files from Server A to Server B to see if they build
>> correctly.
>> >>> >
>> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>> >>> >
>> >>> >> No differences as far as I can see. The two:
>> >>> >>
>> >>> >> Server A: Esme built w/o problems Jan 5
>> >>> >> Server B: Esme build error Jan 26
>> >>> >>
>> >>> >> Ubuntu 9.04 - both updated before installing ESME.
>> >>> >>
>> >>> >> JDK same.
>> >>> >>
>> >>> >> Basically same-same :)
>> >>> >>
>> >>> >>
>> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> >>> >> > What are the other differences on the two servers Sig?
>> >>> >> >
>> >>> >> > /Anne Kathrine
>> >>> >> > Sent from my iPhone
>> >>> >> >
>> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>> >>> >> >
>> >>> >> >> I have, on the other server that runs ok (except that original
>> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>> >>> >> >> same... (I'm sure that did not help much LOL)
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> >>> >> >>>
>> >>> >> >>> I don't think anything has changed. Just that no one has used
>> >>> openJDK
>> >>> >> >>> since
>> >>> >> >>> then.
>> >>> >> >>>
>> >>> >> >>> /Anne Kathrine
>> >>> >> >>> Sent from my iPhone
>> >>> >> >>>
>> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
>> hirsch.dick@gmail.com>
>> >>> >> wrote:
>> >>> >> >>>
>> >>> >> >>>> But what has changed so that the problem now occurs?
>> >>> >> >>>>
>> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>> >>> >> >>>> <yo...@gmail.com>wrote:
>> >>> >> >>>>
>> >>> >> >>>>> Yay! :-)
>> >>> >> >>>>>
>> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>> >>> >> >>>>>
>> >>> >> >>>>>> Aha :)
>> >>> >> >>>>>>
>> >>> >> >>>>>> java version "1.6.0_0"
>> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>> >>> (6b14-1.4.1-0ubuntu12)
>> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>> >>> >> >>>>>>
>> >>> >> >>>>>> Sig
>> >>> >> >>>>>>
>> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> We've had this before:
>> >>> >> >>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> The interesting part is that noone has implemented David's
>> >>> >> suggestion
>> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
>> (or
>> >>> was
>> >>> >> >>>>>>> it?)
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>> >>> openjdk-6,
>> >>> >> >>>>>>> which was not mature enough to run bug-free.
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> Vassil
>> >>> >> >>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>> >>> >> >>>>>>> <hi...@gmail.com>
>> >>> >> >>>>>
>> >>> >> >>>>> wrote:
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>> >>> wrote:
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>> >>> up-to-date
>> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>> >>> starting
>> >>> >> up
>> >>> >> >>>>>>>>> a
>> >>> >> >>>>>>>>> fresh image.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then:
>> >>> >> >>>>>>>>> apt-get install subversion
>> >>> >> >>>>>>>>> apt-get install maven2
>> >>> >> >>>>>>>>> apt-get install jetty
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then:
>> >>> >> >>>>>>>>> svn checkout
>> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then fixing the two files.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Then problem :)
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Now: rm -rf esme and started over
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
>> was
>> >>> >> that
>> >>> >> >>>>>>>>> I
>> >>> >> >>>>>>>>> lost contact with the server at some point during first
>> mvn...
>> >>> so
>> >>> >> >>>>>>>>> now
>> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Nope, exact same error.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>> dies
>> >>> >> >>>>>>>>> after
>> >>> >> >>>>>>>>> a
>> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
>> No
>> >>> other
>> >>> >> >>>>>>>>> clues.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> RE plug-in: I remember.
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>> >>> changed.
>> >>> >> >>>>>>>>>> Has
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> anything
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> else changed in the environment?
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>> >>> problem,
>> >>> >> >>>>>
>> >>> >> >>>>> because
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>> >>> weeks.
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
>> sig@rinde.com>
>> >>> >> wrote:
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>>> Then I get this:
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>> >>> >> >>>>>>>>>>> [INFO]
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> ------------------------------------------------------------------------
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> [INFO] null
>> >>> >> >>>>>>>>>>> [INFO]
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> ------------------------------------------------------------------------
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> [INFO] Trace
>> >>> >> >>>>>>>>>>> java.lang.RuntimeException
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>> then
>> >>> >> all
>> >>> >> >>>>>>>>>>> was
>> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
>> sig@rinde.com>
>> >>> >> >>>>>>>>>>>> wrote:
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> Ethan,
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>> >>> jetty:run"
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> Prior to that:
>> >>> >> >>>>>>>>>>>>> 1. svn the full esme
>> >>> >> >>>>>>>>>>>>> 2. add line to default.props
>> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> [INFO] Trace
>> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>> >>> returned
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> non-zero
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> value:1
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> >>> >> >>>>>>>>>>>>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >>> >> >>>>>
>> >>> >> >>>>> Method)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> java.lang.reflect.Method.invoke(Method.java:616)
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>
>> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>
>> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>
>> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>
>> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> Caused by:
>> org.apache.maven.plugin.MojoFailureException:
>> >>> >> >>>>>>>>>>>>> command
>> >>> >> >>>>>
>> >>> >> >>>>> line
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> returned non-zero value:1
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>
>> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >>
>> >>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> ... 20 more
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> Hi Sig,
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
>> this
>> >>> once
>> >>> >> >>>>>>>>>>>>>> goes
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> deep
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>> somewhere
>> >>> >> >>>>>>>>>>>>>> else?
>> >>> >> >>>>>
>> >>> >> >>>>> And
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
>> this
>> >>> >> >>>>>>>>>>>>>> error?
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> mvn
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> clean install?
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> Thanks,
>> >>> >> >>>>>>>>>>>>>> Ethan
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>> >>> sig@rinde.com>
>> >>> >> >>>>>
>> >>> >> >>>>> wrote:
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
>> created a
>> >>> new
>> >>> >> >>>>>>>>>>>>>>> and
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> fresh
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
>> one),
>> >>> >> >>>>>>>>>>>>>>> apt-get
>> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> New svn from esme.
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
>> commented
>> >>> out
>> >>> >> >>>>>>>>>>>>>>> the
>> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
>> pom.xml
>> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>> >>> >> >>>>>>>>>>>>>>> [ERROR]
>> /home/files/esme/server/src/test/scala/../scala
>> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>> >>> >> >>>>>
>> >>> >> >>>>> java.lang.StackOverflowError
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>
>> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> ...
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> S
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>> Unfortunately
>> >>> I
>> >>> >> >>>>>>>>>>>>>>>> don't
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> have
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>> >>> setting
>> >>> >> >>>>>>>>>>>>>>>> for
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> the
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>> >>> >> >>>>>>>>>>>>>>>> Definitely
>> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
>> line
>> >>> in
>> >>> >> >>>>>>>>>>>>>>>> the
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> property
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>> >>> does
>> >>> >> >>>>>>>>>>>>>>>> that
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> user
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> Thanks,
>> >>> >> >>>>>>>>>>>>>>>> Ethan
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>> >>> sig@rinde.com
>> >>> >> >
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> wrote:
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>> >>> anything
>> >>> >> >>>>>>>>>>>>>>>>> but
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> root,
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> say
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
>> same
>> >>> >> problem
>> >>> >> >>>>>>>>>>>>>>>>> on
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> all
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>> browsers.
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
>> local
>> >>> >> >>>>>>>>>>>>>>>>> instance.
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>> (aws
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> is
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
>> webapp
>> >>> >> >>>>>>>>>>>>>>>>> folders
>> >>> >> >>>>>
>> >>> >> >>>>> and
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> found
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>> >>> removed
>> >>> >> >>>>>>>>>>>>>>>>> after
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> first
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> try).
>> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
>> found
>> >>> no
>> >>> >> >>>>>>>>>>>>>>>>> diff
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> except
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
>> named
>> >>> >> >>>>>
>> >>> >> >>>>> .gitignore.
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
>> in
>> >>> >> there
>> >>> >> >>>>>>>>>>>>>>>>> so
>> >>> >> >>>>>
>> >>> >> >>>>> I
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> can
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>> >>> later
>> >>> >> new
>> >>> >> >>>>>
>> >>> >> >>>>> and
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>> fresh
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> install... :)
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> >>> >> >>>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
>> browsers.
>> >>> >> >>>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>>
>> >>> >> >>>>>>>>>>>
>> >>> >> >>>>>>>>>>
>> >>> >> >>>>>>>>>
>> >>> >> >>>>>>>>
>> >>> >> >>>>>>>
>> >>> >> >>>>>
>> >>> >> >>>>>
>> >>> >> >>>
>> >>> >> >
>> >>> >>
>> >>> >
>> >>>
>> >>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
Thanks.
It must be Ubuntu 9.04 specific then.
Does anyone else have a Ubuntu 9.04 environment where we could verify the
bug?
D.
On Tue, Jan 26, 2010 at 6:47 PM, Sig Rinde <si...@rinde.com> wrote:
> OK, switcehd to Sun jdk (I think(:
>
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
>
> Same result....
>
>
>
> 2010/1/26 Sig Rinde <si...@rinde.com>:
> > mvn -U clean jetty:run did nothing here...
> >
> > But why try another JDK when we know the esme built on Jan 5 still
> > works, on both servers - while the one built today stubbornly will not
> > build?
> >
> > Must be some file changes to what the svn delivers in that timespan or
> what?
> >
> >
> >
> > 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >> Yep. I agree.
> >>
> >> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
> >> course, this a windows box....
> >>
> >> Could be based on OpenJDK or Ubuntu 9.04?
> >>
> >> @Sig: Maybe you could try the "normal" Sun JDK.
> >>
> >>
> >>
> >> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
> >>
> >>> Aye aye capt'n, will do! Done:
> >>>
> >>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
> >>> thing not pulled was the esme_db folder, assume that is created anew
> >>> at start up).
> >>>
> >>> Result: Ya, that started!
> >>>
> >>> 2. Looking for changes in esme svn I did the full svn checkout
> >>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
> >>>
> >>> Result: Oops that did not work as it's unversioned, duh... ah well etc
> >>>
> >>> So something happened with whatever the svn fetches after Jan 5....
> >>> would be my educated guess.
> >>>
> >>>
> >>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>> > But we really don't know what changes happened between Jan 5 and Jan
> 26
> >>> in
> >>> > the packages pulled by maven. ESME might not have changed (much) but
> the
> >>> > packages that it uses may have changed. Of interest would be to move
> the
> >>> > original files from Server A to Server B to see if they build
> correctly.
> >>> >
> >>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
> >>> >
> >>> >> No differences as far as I can see. The two:
> >>> >>
> >>> >> Server A: Esme built w/o problems Jan 5
> >>> >> Server B: Esme build error Jan 26
> >>> >>
> >>> >> Ubuntu 9.04 - both updated before installing ESME.
> >>> >>
> >>> >> JDK same.
> >>> >>
> >>> >> Basically same-same :)
> >>> >>
> >>> >>
> >>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> >>> >> > What are the other differences on the two servers Sig?
> >>> >> >
> >>> >> > /Anne Kathrine
> >>> >> > Sent from my iPhone
> >>> >> >
> >>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
> >>> >> >
> >>> >> >> I have, on the other server that runs ok (except that original
> >>> >> >> api_test login issue) it's same OpenJDK, basically everything is
> >>> >> >> same... (I'm sure that did not help much LOL)
> >>> >> >>
> >>> >> >>
> >>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> >>> >> >>>
> >>> >> >>> I don't think anything has changed. Just that no one has used
> >>> openJDK
> >>> >> >>> since
> >>> >> >>> then.
> >>> >> >>>
> >>> >> >>> /Anne Kathrine
> >>> >> >>> Sent from my iPhone
> >>> >> >>>
> >>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <
> hirsch.dick@gmail.com>
> >>> >> wrote:
> >>> >> >>>
> >>> >> >>>> But what has changed so that the problem now occurs?
> >>> >> >>>>
> >>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
> >>> >> >>>> <yo...@gmail.com>wrote:
> >>> >> >>>>
> >>> >> >>>>> Yay! :-)
> >>> >> >>>>>
> >>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
> >>> >> >>>>>
> >>> >> >>>>>> Aha :)
> >>> >> >>>>>>
> >>> >> >>>>>> java version "1.6.0_0"
> >>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
> >>> (6b14-1.4.1-0ubuntu12)
> >>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
> >>> >> >>>>>>
> >>> >> >>>>>> Sig
> >>> >> >>>>>>
> >>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
> >>> >> >>>>>>>
> >>> >> >>>>>>> We've had this before:
> >>> >> >>>>>>>
> >>> >> >>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
> >>> >> >>>>>>>
> >>> >> >>>>>>> The interesting part is that noone has implemented David's
> >>> >> suggestion
> >>> >> >>>>>>> to date, and still the problem seems to have been resolved
> (or
> >>> was
> >>> >> >>>>>>> it?)
> >>> >> >>>>>>>
> >>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
> >>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
> >>> openjdk-6,
> >>> >> >>>>>>> which was not mature enough to run bug-free.
> >>> >> >>>>>>>
> >>> >> >>>>>>> Vassil
> >>> >> >>>>>>>
> >>> >> >>>>>>>
> >>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
> >>> >> >>>>>>> <hi...@gmail.com>
> >>> >> >>>>>
> >>> >> >>>>> wrote:
> >>> >> >>>>>>>>
> >>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
> >>> >> >>>>>>>>
> >>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
> >>> wrote:
> >>> >> >>>>>>>>
> >>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
> >>> up-to-date
> >>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
> >>> starting
> >>> >> up
> >>> >> >>>>>>>>> a
> >>> >> >>>>>>>>> fresh image.
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Then:
> >>> >> >>>>>>>>> apt-get install subversion
> >>> >> >>>>>>>>> apt-get install maven2
> >>> >> >>>>>>>>> apt-get install jetty
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Then:
> >>> >> >>>>>>>>> svn checkout
> >>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Then fixing the two files.
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Then problem :)
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Now: rm -rf esme and started over
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> One never knows where I could have messed up, only mishap
> was
> >>> >> that
> >>> >> >>>>>>>>> I
> >>> >> >>>>>>>>> lost contact with the server at some point during first
> mvn...
> >>> so
> >>> >> >>>>>>>>> now
> >>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Nope, exact same error.
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then
> dies
> >>> >> >>>>>>>>> after
> >>> >> >>>>>>>>> a
> >>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages.
> No
> >>> other
> >>> >> >>>>>>>>> clues.
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> RE plug-in: I remember.
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
> >>> changed.
> >>> >> >>>>>>>>>> Has
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> anything
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> else changed in the environment?
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
> >>> problem,
> >>> >> >>>>>
> >>> >> >>>>> because
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
> >>> weeks.
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <
> sig@rinde.com>
> >>> >> wrote:
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>>> Then I get this:
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
> >>> >> >>>>>>>>>>> [INFO]
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> ------------------------------------------------------------------------
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> [INFO] null
> >>> >> >>>>>>>>>>> [INFO]
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> ------------------------------------------------------------------------
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> [INFO] Trace
> >>> >> >>>>>>>>>>> java.lang.RuntimeException
> >>> >> >>>>>>>>>>> at
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> at
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> at
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> at
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> at
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and
> then
> >>> >> all
> >>> >> >>>>>>>>>>> was
> >>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>> >> >>>>>>>>>>>>
> >>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
> >>> >> >>>>>>>>>>>>
> >>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <
> sig@rinde.com>
> >>> >> >>>>>>>>>>>> wrote:
> >>> >> >>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> Ethan,
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
> >>> jetty:run"
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> Prior to that:
> >>> >> >>>>>>>>>>>>> 1. svn the full esme
> >>> >> >>>>>>>>>>>>> 2. add line to default.props
> >>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> using -e gave this at the end:
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> [INFO] Trace
> >>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
> >>> returned
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> non-zero
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> value:1
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> >>> >> >>>>>>>>>>>>> at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>> >> >>>>>
> >>> >> >>>>> Method)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> java.lang.reflect.Method.invoke(Method.java:616)
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>
> >>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>
> >>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>
> >>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>
> >>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> Caused by:
> org.apache.maven.plugin.MojoFailureException:
> >>> >> >>>>>>>>>>>>> command
> >>> >> >>>>>
> >>> >> >>>>> line
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> returned non-zero value:1
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>
> >>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >>
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> ... 20 more
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>> Hi Sig,
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think
> this
> >>> once
> >>> >> >>>>>>>>>>>>>> goes
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> deep
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or
> somewhere
> >>> >> >>>>>>>>>>>>>> else?
> >>> >> >>>>>
> >>> >> >>>>> And
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>> exactly what command are you running that results in
> this
> >>> >> >>>>>>>>>>>>>> error?
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> mvn
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>> clean install?
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>> Thanks,
> >>> >> >>>>>>>>>>>>>> Ethan
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
> >>> sig@rinde.com>
> >>> >> >>>>>
> >>> >> >>>>> wrote:
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> Thanks Ethan,
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I
> created a
> >>> new
> >>> >> >>>>>>>>>>>>>>> and
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> fresh
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live
> one),
> >>> >> >>>>>>>>>>>>>>> apt-get
> >>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> New svn from esme.
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and
> commented
> >>> out
> >>> >> >>>>>>>>>>>>>>> the
> >>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from
> pom.xml
> >>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
> >>> >> >>>>>>>>>>>>>>> [ERROR]
> /home/files/esme/server/src/test/scala/../scala
> >>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
> >>> >> >>>>>
> >>> >> >>>>> java.lang.StackOverflowError
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>
> >>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> [WARNING] at
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> ...
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> S
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> Hi Sig,
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work.
> Unfortunately
> >>> I
> >>> >> >>>>>>>>>>>>>>>> don't
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> have
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
> >>> setting
> >>> >> >>>>>>>>>>>>>>>> for
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> the
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
> >>> >> >>>>>>>>>>>>>>>> Definitely
> >>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another
> line
> >>> in
> >>> >> >>>>>>>>>>>>>>>> the
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> property
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
> >>> does
> >>> >> >>>>>>>>>>>>>>>> that
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> user
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> Thanks,
> >>> >> >>>>>>>>>>>>>>>> Ethan
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
> >>> sig@rinde.com
> >>> >> >
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> wrote:
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
> >>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
> >>> anything
> >>> >> >>>>>>>>>>>>>>>>> but
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> root,
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> say
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
> >>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root
> same
> >>> >> problem
> >>> >> >>>>>>>>>>>>>>>>> on
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> all
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>> browsers.
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my
> local
> >>> >> >>>>>>>>>>>>>>>>> instance.
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>> (aws
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> is
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
> >>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws)
> webapp
> >>> >> >>>>>>>>>>>>>>>>> folders
> >>> >> >>>>>
> >>> >> >>>>> and
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> found
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
> >>> removed
> >>> >> >>>>>>>>>>>>>>>>> after
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> first
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> try).
> >>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and
> found
> >>> no
> >>> >> >>>>>>>>>>>>>>>>> diff
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> except
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file
> named
> >>> >> >>>>>
> >>> >> >>>>> .gitignore.
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get
> in
> >>> >> there
> >>> >> >>>>>>>>>>>>>>>>> so
> >>> >> >>>>>
> >>> >> >>>>> I
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> can
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
> >>> later
> >>> >> new
> >>> >> >>>>>
> >>> >> >>>>> and
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>> fresh
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> install... :)
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
> >>> >> >>>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those
> browsers.
> >>> >> >>>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>>
> >>> >> >>>>>>>>>>>>
> >>> >> >>>>>>>>>>>
> >>> >> >>>>>>>>>>
> >>> >> >>>>>>>>>
> >>> >> >>>>>>>>
> >>> >> >>>>>>>
> >>> >> >>>>>
> >>> >> >>>>>
> >>> >> >>>
> >>> >> >
> >>> >>
> >>> >
> >>>
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
OK, switcehd to Sun jdk (I think(:
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
Same result....
2010/1/26 Sig Rinde <si...@rinde.com>:
> mvn -U clean jetty:run did nothing here...
>
> But why try another JDK when we know the esme built on Jan 5 still
> works, on both servers - while the one built today stubbornly will not
> build?
>
> Must be some file changes to what the svn delivers in that timespan or what?
>
>
>
> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> Yep. I agree.
>>
>> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
>> course, this a windows box....
>>
>> Could be based on OpenJDK or Ubuntu 9.04?
>>
>> @Sig: Maybe you could try the "normal" Sun JDK.
>>
>>
>>
>> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>
>>> Aye aye capt'n, will do! Done:
>>>
>>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>>> thing not pulled was the esme_db folder, assume that is created anew
>>> at start up).
>>>
>>> Result: Ya, that started!
>>>
>>> 2. Looking for changes in esme svn I did the full svn checkout
>>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>
>>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>>
>>> So something happened with whatever the svn fetches after Jan 5....
>>> would be my educated guess.
>>>
>>>
>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> > But we really don't know what changes happened between Jan 5 and Jan 26
>>> in
>>> > the packages pulled by maven. ESME might not have changed (much) but the
>>> > packages that it uses may have changed. Of interest would be to move the
>>> > original files from Server A to Server B to see if they build correctly.
>>> >
>>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>>> >
>>> >> No differences as far as I can see. The two:
>>> >>
>>> >> Server A: Esme built w/o problems Jan 5
>>> >> Server B: Esme build error Jan 26
>>> >>
>>> >> Ubuntu 9.04 - both updated before installing ESME.
>>> >>
>>> >> JDK same.
>>> >>
>>> >> Basically same-same :)
>>> >>
>>> >>
>>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>> >> > What are the other differences on the two servers Sig?
>>> >> >
>>> >> > /Anne Kathrine
>>> >> > Sent from my iPhone
>>> >> >
>>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>>> >> >
>>> >> >> I have, on the other server that runs ok (except that original
>>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>>> >> >> same... (I'm sure that did not help much LOL)
>>> >> >>
>>> >> >>
>>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>> >> >>>
>>> >> >>> I don't think anything has changed. Just that no one has used
>>> openJDK
>>> >> >>> since
>>> >> >>> then.
>>> >> >>>
>>> >> >>> /Anne Kathrine
>>> >> >>> Sent from my iPhone
>>> >> >>>
>>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
>>> >> wrote:
>>> >> >>>
>>> >> >>>> But what has changed so that the problem now occurs?
>>> >> >>>>
>>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>> >> >>>> <yo...@gmail.com>wrote:
>>> >> >>>>
>>> >> >>>>> Yay! :-)
>>> >> >>>>>
>>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>> >> >>>>>
>>> >> >>>>>> Aha :)
>>> >> >>>>>>
>>> >> >>>>>> java version "1.6.0_0"
>>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>> (6b14-1.4.1-0ubuntu12)
>>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>> >> >>>>>>
>>> >> >>>>>> Sig
>>> >> >>>>>>
>>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>> >> >>>>>>>
>>> >> >>>>>>> We've had this before:
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>> >> >>>>>>>
>>> >> >>>>>>> The interesting part is that noone has implemented David's
>>> >> suggestion
>>> >> >>>>>>> to date, and still the problem seems to have been resolved (or
>>> was
>>> >> >>>>>>> it?)
>>> >> >>>>>>>
>>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>>> openjdk-6,
>>> >> >>>>>>> which was not mature enough to run bug-free.
>>> >> >>>>>>>
>>> >> >>>>>>> Vassil
>>> >> >>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>> >> >>>>>>> <hi...@gmail.com>
>>> >> >>>>>
>>> >> >>>>> wrote:
>>> >> >>>>>>>>
>>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>>> >> >>>>>>>>
>>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>> wrote:
>>> >> >>>>>>>>
>>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>>> up-to-date
>>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>> starting
>>> >> up
>>> >> >>>>>>>>> a
>>> >> >>>>>>>>> fresh image.
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Then:
>>> >> >>>>>>>>> apt-get install subversion
>>> >> >>>>>>>>> apt-get install maven2
>>> >> >>>>>>>>> apt-get install jetty
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Then:
>>> >> >>>>>>>>> svn checkout
>>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Then fixing the two files.
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Then problem :)
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Now: rm -rf esme and started over
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> One never knows where I could have messed up, only mishap was
>>> >> that
>>> >> >>>>>>>>> I
>>> >> >>>>>>>>> lost contact with the server at some point during first mvn...
>>> so
>>> >> >>>>>>>>> now
>>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Nope, exact same error.
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>>> >> >>>>>>>>> after
>>> >> >>>>>>>>> a
>>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages. No
>>> other
>>> >> >>>>>>>>> clues.
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> RE plug-in: I remember.
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>> changed.
>>> >> >>>>>>>>>> Has
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> anything
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> else changed in the environment?
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>>> problem,
>>> >> >>>>>
>>> >> >>>>> because
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>> weeks.
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
>>> >> wrote:
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>>> Then I get this:
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>>> >> >>>>>>>>>>> [INFO]
>>> >> >>>>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> ------------------------------------------------------------------------
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> [INFO] null
>>> >> >>>>>>>>>>> [INFO]
>>> >> >>>>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> ------------------------------------------------------------------------
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> [INFO] Trace
>>> >> >>>>>>>>>>> java.lang.RuntimeException
>>> >> >>>>>>>>>>> at
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> at
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> at
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> at
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> at
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and then
>>> >> all
>>> >> >>>>>>>>>>> was
>>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> >> >>>>>>>>>>>>
>>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>>> >> >>>>>>>>>>>>
>>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>> >> >>>>>>>>>>>> wrote:
>>> >> >>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> Ethan,
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>> jetty:run"
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> Prior to that:
>>> >> >>>>>>>>>>>>> 1. svn the full esme
>>> >> >>>>>>>>>>>>> 2. add line to default.props
>>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> using -e gave this at the end:
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> [INFO] Trace
>>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>> returned
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> non-zero
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> value:1
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>> >> >>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>> >> >>>>>
>>> >> >>>>> Method)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>
>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>
>>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>
>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>
>>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
>>> >> >>>>>>>>>>>>> command
>>> >> >>>>>
>>> >> >>>>> line
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> returned non-zero value:1
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>
>>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> ... 20 more
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>> Hi Sig,
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think this
>>> once
>>> >> >>>>>>>>>>>>>> goes
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> deep
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere
>>> >> >>>>>>>>>>>>>> else?
>>> >> >>>>>
>>> >> >>>>> And
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>> exactly what command are you running that results in this
>>> >> >>>>>>>>>>>>>> error?
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> mvn
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>> clean install?
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>> Thanks,
>>> >> >>>>>>>>>>>>>> Ethan
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>>> sig@rinde.com>
>>> >> >>>>>
>>> >> >>>>> wrote:
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a
>>> new
>>> >> >>>>>>>>>>>>>>> and
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> fresh
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
>>> >> >>>>>>>>>>>>>>> apt-get
>>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> New svn from esme.
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and commented
>>> out
>>> >> >>>>>>>>>>>>>>> the
>>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>> >> >>>>>
>>> >> >>>>> java.lang.StackOverflowError
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>
>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> [WARNING] at
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>>
>>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> ...
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> S
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> Hi Sig,
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately
>>> I
>>> >> >>>>>>>>>>>>>>>> don't
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> have
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>> setting
>>> >> >>>>>>>>>>>>>>>> for
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> the
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>> >> >>>>>>>>>>>>>>>> Definitely
>>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another line
>>> in
>>> >> >>>>>>>>>>>>>>>> the
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> property
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>> does
>>> >> >>>>>>>>>>>>>>>> that
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> user
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> Thanks,
>>> >> >>>>>>>>>>>>>>>> Ethan
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>>> sig@rinde.com
>>> >> >
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> wrote:
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>> anything
>>> >> >>>>>>>>>>>>>>>>> but
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> root,
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> say
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
>>> >> problem
>>> >> >>>>>>>>>>>>>>>>> on
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> all
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>> browsers.
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
>>> >> >>>>>>>>>>>>>>>>> instance.
>>> >> >>>>>>>>>
>>> >> >>>>>>>>> (aws
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> is
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>> >> >>>>>>>>>>>>>>>>> folders
>>> >> >>>>>
>>> >> >>>>> and
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> found
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>> removed
>>> >> >>>>>>>>>>>>>>>>> after
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> first
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> try).
>>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found
>>> no
>>> >> >>>>>>>>>>>>>>>>> diff
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> except
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>> >> >>>>>
>>> >> >>>>> .gitignore.
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get in
>>> >> there
>>> >> >>>>>>>>>>>>>>>>> so
>>> >> >>>>>
>>> >> >>>>> I
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> can
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>> later
>>> >> new
>>> >> >>>>>
>>> >> >>>>> and
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>> fresh
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> install... :)
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>> >> >>>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>> >> >>>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>>
>>> >> >>>>>>>>>>>>
>>> >> >>>>>>>>>>>
>>> >> >>>>>>>>>>
>>> >> >>>>>>>>>
>>> >> >>>>>>>>
>>> >> >>>>>>>
>>> >> >>>>>
>>> >> >>>>>
>>> >> >>>
>>> >> >
>>> >>
>>> >
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
mvn -U clean jetty:run did nothing here...
But why try another JDK when we know the esme built on Jan 5 still
works, on both servers - while the one built today stubbornly will not
build?
Must be some file changes to what the svn delivers in that timespan or what?
2010/1/26 Richard Hirsch <hi...@gmail.com>:
> Yep. I agree.
>
> By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
> course, this a windows box....
>
> Could be based on OpenJDK or Ubuntu 9.04?
>
> @Sig: Maybe you could try the "normal" Sun JDK.
>
>
>
> On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> Aye aye capt'n, will do! Done:
>>
>> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
>> thing not pulled was the esme_db folder, assume that is created anew
>> at start up).
>>
>> Result: Ya, that started!
>>
>> 2. Looking for changes in esme svn I did the full svn checkout
>> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>
>> Result: Oops that did not work as it's unversioned, duh... ah well etc
>>
>> So something happened with whatever the svn fetches after Jan 5....
>> would be my educated guess.
>>
>>
>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> > But we really don't know what changes happened between Jan 5 and Jan 26
>> in
>> > the packages pulled by maven. ESME might not have changed (much) but the
>> > packages that it uses may have changed. Of interest would be to move the
>> > original files from Server A to Server B to see if they build correctly.
>> >
>> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>> >
>> >> No differences as far as I can see. The two:
>> >>
>> >> Server A: Esme built w/o problems Jan 5
>> >> Server B: Esme build error Jan 26
>> >>
>> >> Ubuntu 9.04 - both updated before installing ESME.
>> >>
>> >> JDK same.
>> >>
>> >> Basically same-same :)
>> >>
>> >>
>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> >> > What are the other differences on the two servers Sig?
>> >> >
>> >> > /Anne Kathrine
>> >> > Sent from my iPhone
>> >> >
>> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>> >> >
>> >> >> I have, on the other server that runs ok (except that original
>> >> >> api_test login issue) it's same OpenJDK, basically everything is
>> >> >> same... (I'm sure that did not help much LOL)
>> >> >>
>> >> >>
>> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> >> >>>
>> >> >>> I don't think anything has changed. Just that no one has used
>> openJDK
>> >> >>> since
>> >> >>> then.
>> >> >>>
>> >> >>> /Anne Kathrine
>> >> >>> Sent from my iPhone
>> >> >>>
>> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
>> >> wrote:
>> >> >>>
>> >> >>>> But what has changed so that the problem now occurs?
>> >> >>>>
>> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>> >> >>>> <yo...@gmail.com>wrote:
>> >> >>>>
>> >> >>>>> Yay! :-)
>> >> >>>>>
>> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>> >> >>>>>
>> >> >>>>>> Aha :)
>> >> >>>>>>
>> >> >>>>>> java version "1.6.0_0"
>> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>> (6b14-1.4.1-0ubuntu12)
>> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>> >> >>>>>>
>> >> >>>>>> Sig
>> >> >>>>>>
>> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>> >> >>>>>>>
>> >> >>>>>>> We've had this before:
>> >> >>>>>>>
>> >> >>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>> >> >>>>>>>
>> >> >>>>>>> The interesting part is that noone has implemented David's
>> >> suggestion
>> >> >>>>>>> to date, and still the problem seems to have been resolved (or
>> was
>> >> >>>>>>> it?)
>> >> >>>>>>>
>> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>> >> >>>>>>> Debian/Ubuntu because package management decided to pull
>> openjdk-6,
>> >> >>>>>>> which was not mature enough to run bug-free.
>> >> >>>>>>>
>> >> >>>>>>> Vassil
>> >> >>>>>>>
>> >> >>>>>>>
>> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>> >> >>>>>>> <hi...@gmail.com>
>> >> >>>>>
>> >> >>>>> wrote:
>> >> >>>>>>>>
>> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>> >> >>>>>>>>
>> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>> wrote:
>> >> >>>>>>>>
>> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
>> up-to-date
>> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>> starting
>> >> up
>> >> >>>>>>>>> a
>> >> >>>>>>>>> fresh image.
>> >> >>>>>>>>>
>> >> >>>>>>>>> Then:
>> >> >>>>>>>>> apt-get install subversion
>> >> >>>>>>>>> apt-get install maven2
>> >> >>>>>>>>> apt-get install jetty
>> >> >>>>>>>>>
>> >> >>>>>>>>> Then:
>> >> >>>>>>>>> svn checkout
>> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>> >> >>>>>>>>>
>> >> >>>>>>>>> Then fixing the two files.
>> >> >>>>>>>>>
>> >> >>>>>>>>> Then problem :)
>> >> >>>>>>>>>
>> >> >>>>>>>>> Now: rm -rf esme and started over
>> >> >>>>>>>>>
>> >> >>>>>>>>> One never knows where I could have messed up, only mishap was
>> >> that
>> >> >>>>>>>>> I
>> >> >>>>>>>>> lost contact with the server at some point during first mvn...
>> so
>> >> >>>>>>>>> now
>> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>> >> >>>>>>>>>
>> >> >>>>>>>>> Nope, exact same error.
>> >> >>>>>>>>>
>> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>> >> >>>>>>>>> after
>> >> >>>>>>>>> a
>> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages. No
>> other
>> >> >>>>>>>>> clues.
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> RE plug-in: I remember.
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
>> changed.
>> >> >>>>>>>>>> Has
>> >> >>>>>>>>>
>> >> >>>>>>>>> anything
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> else changed in the environment?
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
>> problem,
>> >> >>>>>
>> >> >>>>> because
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
>> weeks.
>> >> >>>>>>>>>>
>> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
>> >> wrote:
>> >> >>>>>>>>>>
>> >> >>>>>>>>>>> Then I get this:
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> [ERROR] FATAL ERROR
>> >> >>>>>>>>>>> [INFO]
>> >> >>>>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> ------------------------------------------------------------------------
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> [INFO] null
>> >> >>>>>>>>>>> [INFO]
>> >> >>>>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> ------------------------------------------------------------------------
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> [INFO] Trace
>> >> >>>>>>>>>>> java.lang.RuntimeException
>> >> >>>>>>>>>>> at
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> at
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> at
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> at
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> at
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and then
>> >> all
>> >> >>>>>>>>>>> was
>> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>> >> >>>>>>>>>>>> wrote:
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>>> Ethan,
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>> jetty:run"
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> Prior to that:
>> >> >>>>>>>>>>>>> 1. svn the full esme
>> >> >>>>>>>>>>>>> 2. add line to default.props
>> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> using -e gave this at the end:
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> [INFO] Trace
>> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>> returned
>> >> >>>>>>>>>
>> >> >>>>>>>>> non-zero
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> value:1
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>
>> >> >>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>
>> >> >>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> >> >>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >> >>>>>
>> >> >>>>> Method)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>
>> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>
>> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
>> >> >>>>>>>>>>>>> command
>> >> >>>>>
>> >> >>>>> line
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> returned non-zero value:1
>> >> >>>>>>>>>>>>> at
>> >> >>>>>
>> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>>>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> ... 20 more
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>> Hi Sig,
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think this
>> once
>> >> >>>>>>>>>>>>>> goes
>> >> >>>>>>>>>
>> >> >>>>>>>>> deep
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere
>> >> >>>>>>>>>>>>>> else?
>> >> >>>>>
>> >> >>>>> And
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>> exactly what command are you running that results in this
>> >> >>>>>>>>>>>>>> error?
>> >> >>>>>>>>>
>> >> >>>>>>>>> mvn
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>> clean install?
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>> Thanks,
>> >> >>>>>>>>>>>>>> Ethan
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
>> sig@rinde.com>
>> >> >>>>>
>> >> >>>>> wrote:
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> Thanks Ethan,
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a
>> new
>> >> >>>>>>>>>>>>>>> and
>> >> >>>>>>>>>
>> >> >>>>>>>>> fresh
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
>> >> >>>>>>>>>>>>>>> apt-get
>> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> New svn from esme.
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and commented
>> out
>> >> >>>>>>>>>>>>>>> the
>> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>> >> >>>>>
>> >> >>>>> java.lang.StackOverflowError
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >> >>>>>>>>>>>>>
>> >> >>>>>
>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> [WARNING] at
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>>
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> ...
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> So what did I forget this time :)
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> S
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> Hi Sig,
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately
>> I
>> >> >>>>>>>>>>>>>>>> don't
>> >> >>>>>>>>>
>> >> >>>>>>>>> have
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>> setting
>> >> >>>>>>>>>>>>>>>> for
>> >> >>>>>>>>>
>> >> >>>>>>>>> the
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>> >> >>>>>>>>>>>>>>>> Definitely
>> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another line
>> in
>> >> >>>>>>>>>>>>>>>> the
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> property
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>> does
>> >> >>>>>>>>>>>>>>>> that
>> >> >>>>>>>>>
>> >> >>>>>>>>> user
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> Thanks,
>> >> >>>>>>>>>>>>>>>> Ethan
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
>> sig@rinde.com
>> >> >
>> >> >>>>>>>>>
>> >> >>>>>>>>> wrote:
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>> anything
>> >> >>>>>>>>>>>>>>>>> but
>> >> >>>>>>>>>
>> >> >>>>>>>>> root,
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> say
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
>> >> problem
>> >> >>>>>>>>>>>>>>>>> on
>> >> >>>>>>>>>
>> >> >>>>>>>>> all
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>> browsers.
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
>> >> >>>>>>>>>>>>>>>>> instance.
>> >> >>>>>>>>>
>> >> >>>>>>>>> (aws
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> is
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>> >> >>>>>>>>>>>>>>>>> folders
>> >> >>>>>
>> >> >>>>> and
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> found
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>> removed
>> >> >>>>>>>>>>>>>>>>> after
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> first
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> try).
>> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found
>> no
>> >> >>>>>>>>>>>>>>>>> diff
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> except
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>> >> >>>>>
>> >> >>>>> .gitignore.
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get in
>> >> there
>> >> >>>>>>>>>>>>>>>>> so
>> >> >>>>>
>> >> >>>>> I
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> can
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>> later
>> >> new
>> >> >>>>>
>> >> >>>>> and
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>> fresh
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> install... :)
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> >> >>>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>> >> >>>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>>
>> >> >>>>>>>>>>>>>
>> >> >>>>>>>>>>>>
>> >> >>>>>>>>>>>
>> >> >>>>>>>>>>
>> >> >>>>>>>>>
>> >> >>>>>>>>
>> >> >>>>>>>
>> >> >>>>>
>> >> >>>>>
>> >> >>>
>> >> >
>> >>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
Yep. I agree.
By the way, It did a "mvn -U clean jetty:run" locally and it worked. Of
course, this a windows box....
Could be based on OpenJDK or Ubuntu 9.04?
@Sig: Maybe you could try the "normal" Sun JDK.
On Tue, Jan 26, 2010 at 5:25 PM, Sig Rinde <si...@rinde.com> wrote:
> Aye aye capt'n, will do! Done:
>
> 1. Copied full esme folder from A to B and mvn jetty:run on B (only
> thing not pulled was the esme_db folder, assume that is created anew
> at start up).
>
> Result: Ya, that started!
>
> 2. Looking for changes in esme svn I did the full svn checkout
> http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>
> Result: Oops that did not work as it's unversioned, duh... ah well etc
>
> So something happened with whatever the svn fetches after Jan 5....
> would be my educated guess.
>
>
> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> > But we really don't know what changes happened between Jan 5 and Jan 26
> in
> > the packages pulled by maven. ESME might not have changed (much) but the
> > packages that it uses may have changed. Of interest would be to move the
> > original files from Server A to Server B to see if they build correctly.
> >
> > On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
> >
> >> No differences as far as I can see. The two:
> >>
> >> Server A: Esme built w/o problems Jan 5
> >> Server B: Esme build error Jan 26
> >>
> >> Ubuntu 9.04 - both updated before installing ESME.
> >>
> >> JDK same.
> >>
> >> Basically same-same :)
> >>
> >>
> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> >> > What are the other differences on the two servers Sig?
> >> >
> >> > /Anne Kathrine
> >> > Sent from my iPhone
> >> >
> >> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
> >> >
> >> >> I have, on the other server that runs ok (except that original
> >> >> api_test login issue) it's same OpenJDK, basically everything is
> >> >> same... (I'm sure that did not help much LOL)
> >> >>
> >> >>
> >> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> >> >>>
> >> >>> I don't think anything has changed. Just that no one has used
> openJDK
> >> >>> since
> >> >>> then.
> >> >>>
> >> >>> /Anne Kathrine
> >> >>> Sent from my iPhone
> >> >>>
> >> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
> >> wrote:
> >> >>>
> >> >>>> But what has changed so that the problem now occurs?
> >> >>>>
> >> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
> >> >>>> <yo...@gmail.com>wrote:
> >> >>>>
> >> >>>>> Yay! :-)
> >> >>>>>
> >> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
> >> >>>>>
> >> >>>>>> Aha :)
> >> >>>>>>
> >> >>>>>> java version "1.6.0_0"
> >> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
> (6b14-1.4.1-0ubuntu12)
> >> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
> >> >>>>>>
> >> >>>>>> Sig
> >> >>>>>>
> >> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
> >> >>>>>>>
> >> >>>>>>> We've had this before:
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
> >> >>>>>>>
> >> >>>>>>> The interesting part is that noone has implemented David's
> >> suggestion
> >> >>>>>>> to date, and still the problem seems to have been resolved (or
> was
> >> >>>>>>> it?)
> >> >>>>>>>
> >> >>>>>>> BTW what JDK are you using? I've had my share of problems on
> >> >>>>>>> Debian/Ubuntu because package management decided to pull
> openjdk-6,
> >> >>>>>>> which was not mature enough to run bug-free.
> >> >>>>>>>
> >> >>>>>>> Vassil
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
> >> >>>>>>> <hi...@gmail.com>
> >> >>>>>
> >> >>>>> wrote:
> >> >>>>>>>>
> >> >>>>>>>> I'm going to try it locally to see if it works on my laptop
> >> >>>>>>>>
> >> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
> wrote:
> >> >>>>>>>>
> >> >>>>>>>>> Nothing I can see has changed, this one is absolutely
> up-to-date
> >> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
> starting
> >> up
> >> >>>>>>>>> a
> >> >>>>>>>>> fresh image.
> >> >>>>>>>>>
> >> >>>>>>>>> Then:
> >> >>>>>>>>> apt-get install subversion
> >> >>>>>>>>> apt-get install maven2
> >> >>>>>>>>> apt-get install jetty
> >> >>>>>>>>>
> >> >>>>>>>>> Then:
> >> >>>>>>>>> svn checkout
> >> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
> >> >>>>>>>>>
> >> >>>>>>>>> Then fixing the two files.
> >> >>>>>>>>>
> >> >>>>>>>>> Then problem :)
> >> >>>>>>>>>
> >> >>>>>>>>> Now: rm -rf esme and started over
> >> >>>>>>>>>
> >> >>>>>>>>> One never knows where I could have messed up, only mishap was
> >> that
> >> >>>>>>>>> I
> >> >>>>>>>>> lost contact with the server at some point during first mvn...
> so
> >> >>>>>>>>> now
> >> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
> >> >>>>>>>>>
> >> >>>>>>>>> Nope, exact same error.
> >> >>>>>>>>>
> >> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
> >> >>>>>>>>> after
> >> >>>>>>>>> a
> >> >>>>>>>>> bit, and when trying again it says compiling 8 packages. No
> other
> >> >>>>>>>>> clues.
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >> >>>>>>>>>>
> >> >>>>>>>>>> RE plug-in: I remember.
> >> >>>>>>>>>>
> >> >>>>>>>>>> I think something else (Scala, lift, etc.) might have
> changed.
> >> >>>>>>>>>> Has
> >> >>>>>>>>>
> >> >>>>>>>>> anything
> >> >>>>>>>>>>
> >> >>>>>>>>>> else changed in the environment?
> >> >>>>>>>>>>
> >> >>>>>>>>>> It is all very strange. It is obviously a maven-related
> problem,
> >> >>>>>
> >> >>>>> because
> >> >>>>>>>>>>
> >> >>>>>>>>>> ESME's code hasn't really changed at all in the last few
> weeks.
> >> >>>>>>>>>>
> >> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
> >> wrote:
> >> >>>>>>>>>>
> >> >>>>>>>>>>> Then I get this:
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> [ERROR] FATAL ERROR
> >> >>>>>>>>>>> [INFO]
> >> >>>>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> ------------------------------------------------------------------------
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> [INFO] null
> >> >>>>>>>>>>> [INFO]
> >> >>>>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> ------------------------------------------------------------------------
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> [INFO] Trace
> >> >>>>>>>>>>> java.lang.RuntimeException
> >> >>>>>>>>>>> at
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> at
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> at
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> at
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> at
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and then
> >> all
> >> >>>>>>>>>>> was
> >> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
> >> >>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> what happens if you don't comment out the plug-in
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
> >> >>>>>>>>>>>> wrote:
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>>> Ethan,
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn
> jetty:run"
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> Prior to that:
> >> >>>>>>>>>>>>> 1. svn the full esme
> >> >>>>>>>>>>>>> 2. add line to default.props
> >> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> using -e gave this at the end:
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> [INFO] Trace
> >> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
> returned
> >> >>>>>>>>>
> >> >>>>>>>>> non-zero
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> value:1
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>
> >> >>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>
> >> >>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> >> >>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> >>>>>
> >> >>>>> Method)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>
> >> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>
> >> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
> >> >>>>>>>>>>>>> command
> >> >>>>>
> >> >>>>> line
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> returned non-zero value:1
> >> >>>>>>>>>>>>> at
> >> >>>>>
> >> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> ... 20 more
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>> Hi Sig,
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think this
> once
> >> >>>>>>>>>>>>>> goes
> >> >>>>>>>>>
> >> >>>>>>>>> deep
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere
> >> >>>>>>>>>>>>>> else?
> >> >>>>>
> >> >>>>> And
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>> exactly what command are you running that results in this
> >> >>>>>>>>>>>>>> error?
> >> >>>>>>>>>
> >> >>>>>>>>> mvn
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>> clean install?
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>> Thanks,
> >> >>>>>>>>>>>>>> Ethan
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <
> sig@rinde.com>
> >> >>>>>
> >> >>>>> wrote:
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> Thanks Ethan,
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a
> new
> >> >>>>>>>>>>>>>>> and
> >> >>>>>>>>>
> >> >>>>>>>>> fresh
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
> >> >>>>>>>>>>>>>>> apt-get
> >> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> New svn from esme.
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> Added new api_test user in default.props and commented
> out
> >> >>>>>>>>>>>>>>> the
> >> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> Then fired it up and got this error:
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
> >> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
> >> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
> >> >>>>>
> >> >>>>> java.lang.StackOverflowError
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [WARNING] at
> >> >>>>>>>>>>>>>
> >> >>>>>
> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [WARNING] at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [WARNING] at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [WARNING] at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [WARNING] at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> [WARNING] at
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>>
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> ...
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> So what did I forget this time :)
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> S
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> Hi Sig,
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately
> I
> >> >>>>>>>>>>>>>>>> don't
> >> >>>>>>>>>
> >> >>>>>>>>> have
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
> setting
> >> >>>>>>>>>>>>>>>> for
> >> >>>>>>>>>
> >> >>>>>>>>> the
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
> >> >>>>>>>>>>>>>>>> Definitely
> >> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> Question if you have the time: If you add another line
> in
> >> >>>>>>>>>>>>>>>> the
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> property
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> file and assign a second user as integration admin,
> does
> >> >>>>>>>>>>>>>>>> that
> >> >>>>>>>>>
> >> >>>>>>>>> user
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> stop working in the web interface as well?
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> Thanks,
> >> >>>>>>>>>>>>>>>> Ethan
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <
> sig@rinde.com
> >> >
> >> >>>>>>>>>
> >> >>>>>>>>> wrote:
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
> >> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
> anything
> >> >>>>>>>>>>>>>>>>> but
> >> >>>>>>>>>
> >> >>>>>>>>> root,
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> say
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
> >> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
> >> problem
> >> >>>>>>>>>>>>>>>>> on
> >> >>>>>>>>>
> >> >>>>>>>>> all
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>> browsers.
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
> >> >>>>>>>>>>>>>>>>> instance.
> >> >>>>>>>>>
> >> >>>>>>>>> (aws
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> is
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
> >> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
> >> >>>>>>>>>>>>>>>>> folders
> >> >>>>>
> >> >>>>> and
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> found
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
> removed
> >> >>>>>>>>>>>>>>>>> after
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> first
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> try).
> >> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found
> no
> >> >>>>>>>>>>>>>>>>> diff
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> except
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
> >> >>>>>
> >> >>>>> .gitignore.
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get in
> >> there
> >> >>>>>>>>>>>>>>>>> so
> >> >>>>>
> >> >>>>> I
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> can
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
> later
> >> new
> >> >>>>>
> >> >>>>> and
> >> >>>>>>>>>>>
> >> >>>>>>>>>>> fresh
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> install... :)
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
> >> >>>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
> >> >>>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>>
> >> >>>>>>>>>>>>>
> >> >>>>>>>>>>>>
> >> >>>>>>>>>>>
> >> >>>>>>>>>>
> >> >>>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>
> >> >
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Aye aye capt'n, will do! Done:
1. Copied full esme folder from A to B and mvn jetty:run on B (only
thing not pulled was the esme_db folder, assume that is created anew
at start up).
Result: Ya, that started!
2. Looking for changes in esme svn I did the full svn checkout
http://svn.apache.org/repos/asf/incubator/esme/trunk esme
Result: Oops that did not work as it's unversioned, duh... ah well etc
So something happened with whatever the svn fetches after Jan 5....
would be my educated guess.
2010/1/26 Richard Hirsch <hi...@gmail.com>:
> But we really don't know what changes happened between Jan 5 and Jan 26 in
> the packages pulled by maven. ESME might not have changed (much) but the
> packages that it uses may have changed. Of interest would be to move the
> original files from Server A to Server B to see if they build correctly.
>
> On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> No differences as far as I can see. The two:
>>
>> Server A: Esme built w/o problems Jan 5
>> Server B: Esme build error Jan 26
>>
>> Ubuntu 9.04 - both updated before installing ESME.
>>
>> JDK same.
>>
>> Basically same-same :)
>>
>>
>> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> > What are the other differences on the two servers Sig?
>> >
>> > /Anne Kathrine
>> > Sent from my iPhone
>> >
>> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>> >
>> >> I have, on the other server that runs ok (except that original
>> >> api_test login issue) it's same OpenJDK, basically everything is
>> >> same... (I'm sure that did not help much LOL)
>> >>
>> >>
>> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> >>>
>> >>> I don't think anything has changed. Just that no one has used openJDK
>> >>> since
>> >>> then.
>> >>>
>> >>> /Anne Kathrine
>> >>> Sent from my iPhone
>> >>>
>> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
>> wrote:
>> >>>
>> >>>> But what has changed so that the problem now occurs?
>> >>>>
>> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>> >>>> <yo...@gmail.com>wrote:
>> >>>>
>> >>>>> Yay! :-)
>> >>>>>
>> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>> >>>>>
>> >>>>>> Aha :)
>> >>>>>>
>> >>>>>> java version "1.6.0_0"
>> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>> >>>>>>
>> >>>>>> Sig
>> >>>>>>
>> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>> >>>>>>>
>> >>>>>>> We've had this before:
>> >>>>>>>
>> >>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>> >>>>>>>
>> >>>>>>> The interesting part is that noone has implemented David's
>> suggestion
>> >>>>>>> to date, and still the problem seems to have been resolved (or was
>> >>>>>>> it?)
>> >>>>>>>
>> >>>>>>> BTW what JDK are you using? I've had my share of problems on
>> >>>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>> >>>>>>> which was not mature enough to run bug-free.
>> >>>>>>>
>> >>>>>>> Vassil
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>> >>>>>>> <hi...@gmail.com>
>> >>>>>
>> >>>>> wrote:
>> >>>>>>>>
>> >>>>>>>> I'm going to try it locally to see if it works on my laptop
>> >>>>>>>>
>> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>> >>>>>>>>
>> >>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting
>> up
>> >>>>>>>>> a
>> >>>>>>>>> fresh image.
>> >>>>>>>>>
>> >>>>>>>>> Then:
>> >>>>>>>>> apt-get install subversion
>> >>>>>>>>> apt-get install maven2
>> >>>>>>>>> apt-get install jetty
>> >>>>>>>>>
>> >>>>>>>>> Then:
>> >>>>>>>>> svn checkout
>> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>> >>>>>>>>>
>> >>>>>>>>> Then fixing the two files.
>> >>>>>>>>>
>> >>>>>>>>> Then problem :)
>> >>>>>>>>>
>> >>>>>>>>> Now: rm -rf esme and started over
>> >>>>>>>>>
>> >>>>>>>>> One never knows where I could have messed up, only mishap was
>> that
>> >>>>>>>>> I
>> >>>>>>>>> lost contact with the server at some point during first mvn... so
>> >>>>>>>>> now
>> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
>> >>>>>>>>>
>> >>>>>>>>> Nope, exact same error.
>> >>>>>>>>>
>> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>> >>>>>>>>> after
>> >>>>>>>>> a
>> >>>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>> >>>>>>>>> clues.
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>>>>>>>>>
>> >>>>>>>>>> RE plug-in: I remember.
>> >>>>>>>>>>
>> >>>>>>>>>> I think something else (Scala, lift, etc.) might have changed.
>> >>>>>>>>>> Has
>> >>>>>>>>>
>> >>>>>>>>> anything
>> >>>>>>>>>>
>> >>>>>>>>>> else changed in the environment?
>> >>>>>>>>>>
>> >>>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>> >>>>>
>> >>>>> because
>> >>>>>>>>>>
>> >>>>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>> >>>>>>>>>>
>> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>>> Then I get this:
>> >>>>>>>>>>>
>> >>>>>>>>>>> [ERROR] FATAL ERROR
>> >>>>>>>>>>> [INFO]
>> >>>>>>>>>>>
>> >>>>>
>> >>>>>
>> ------------------------------------------------------------------------
>> >>>>>>>>>>>
>> >>>>>>>>>>> [INFO] null
>> >>>>>>>>>>> [INFO]
>> >>>>>>>>>>>
>> >>>>>
>> >>>>>
>> ------------------------------------------------------------------------
>> >>>>>>>>>>>
>> >>>>>>>>>>> [INFO] Trace
>> >>>>>>>>>>> java.lang.RuntimeException
>> >>>>>>>>>>> at
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>> >>>>>>>>>>>
>> >>>>>>>>>>> at
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>> >>>>>>>>>>>
>> >>>>>>>>>>> at
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>> >>>>>>>>>>>
>> >>>>>>>>>>> at
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>> >>>>>>>>>>>
>> >>>>>>>>>>> at
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>> >>>>>>>>>>>
>> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and then
>> all
>> >>>>>>>>>>> was
>> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> what happens if you don't comment out the plug-in
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>> >>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> Ethan,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Prior to that:
>> >>>>>>>>>>>>> 1. svn the full esme
>> >>>>>>>>>>>>> 2. add line to default.props
>> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> using -e gave this at the end:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> [INFO] Trace
>> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>> >>>>>>>>>
>> >>>>>>>>> non-zero
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> value:1
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>
>> >>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>
>> >>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> >>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >>>>>
>> >>>>> Method)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>
>> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>
>> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
>> >>>>>>>>>>>>> command
>> >>>>>
>> >>>>> line
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> returned non-zero value:1
>> >>>>>>>>>>>>> at
>> >>>>>
>> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> at
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> ... 20 more
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Hi Sig,
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think this once
>> >>>>>>>>>>>>>> goes
>> >>>>>>>>>
>> >>>>>>>>> deep
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere
>> >>>>>>>>>>>>>> else?
>> >>>>>
>> >>>>> And
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> exactly what command are you running that results in this
>> >>>>>>>>>>>>>> error?
>> >>>>>>>>>
>> >>>>>>>>> mvn
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> clean install?
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>> Ethan
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>> >>>>>
>> >>>>> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Thanks Ethan,
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new
>> >>>>>>>>>>>>>>> and
>> >>>>>>>>>
>> >>>>>>>>> fresh
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
>> >>>>>>>>>>>>>>> apt-get
>> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> New svn from esme.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Added new api_test user in default.props and commented out
>> >>>>>>>>>>>>>>> the
>> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Then fired it up and got this error:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>> >>>>>
>> >>>>> java.lang.StackOverflowError
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [WARNING] at
>> >>>>>>>>>>>>>
>> >>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [WARNING] at
>> >>>>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [WARNING] at
>> >>>>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [WARNING] at
>> >>>>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [WARNING] at
>> >>>>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> [WARNING] at
>> >>>>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> ...
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> So what did I forget this time :)
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> S
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Hi Sig,
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>> >>>>>>>>>>>>>>>> don't
>> >>>>>>>>>
>> >>>>>>>>> have
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting
>> >>>>>>>>>>>>>>>> for
>> >>>>>>>>>
>> >>>>>>>>> the
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>> >>>>>>>>>>>>>>>> Definitely
>> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Question if you have the time: If you add another line in
>> >>>>>>>>>>>>>>>> the
>> >>>>>>>>>>>
>> >>>>>>>>>>> property
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> file and assign a second user as integration admin, does
>> >>>>>>>>>>>>>>>> that
>> >>>>>>>>>
>> >>>>>>>>> user
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> stop working in the web interface as well?
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>>>> Ethan
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <sig@rinde.com
>> >
>> >>>>>>>>>
>> >>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything
>> >>>>>>>>>>>>>>>>> but
>> >>>>>>>>>
>> >>>>>>>>> root,
>> >>>>>>>>>>>
>> >>>>>>>>>>> say
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
>> problem
>> >>>>>>>>>>>>>>>>> on
>> >>>>>>>>>
>> >>>>>>>>> all
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> browsers.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
>> >>>>>>>>>>>>>>>>> instance.
>> >>>>>>>>>
>> >>>>>>>>> (aws
>> >>>>>>>>>>>
>> >>>>>>>>>>> is
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>> >>>>>>>>>>>>>>>>> folders
>> >>>>>
>> >>>>> and
>> >>>>>>>>>>>
>> >>>>>>>>>>> found
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I removed
>> >>>>>>>>>>>>>>>>> after
>> >>>>>>>>>>>
>> >>>>>>>>>>> first
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> try).
>> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no
>> >>>>>>>>>>>>>>>>> diff
>> >>>>>>>>>>>
>> >>>>>>>>>>> except
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>> >>>>>
>> >>>>> .gitignore.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get in
>> there
>> >>>>>>>>>>>>>>>>> so
>> >>>>>
>> >>>>> I
>> >>>>>>>>>>>
>> >>>>>>>>>>> can
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a later
>> new
>> >>>>>
>> >>>>> and
>> >>>>>>>>>>>
>> >>>>>>>>>>> fresh
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> install... :)
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> >>>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>
>> >>>>>
>> >>>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
But we really don't know what changes happened between Jan 5 and Jan 26 in
the packages pulled by maven. ESME might not have changed (much) but the
packages that it uses may have changed. Of interest would be to move the
original files from Server A to Server B to see if they build correctly.
On Tue, Jan 26, 2010 at 4:24 PM, Sig Rinde <si...@rinde.com> wrote:
> No differences as far as I can see. The two:
>
> Server A: Esme built w/o problems Jan 5
> Server B: Esme build error Jan 26
>
> Ubuntu 9.04 - both updated before installing ESME.
>
> JDK same.
>
> Basically same-same :)
>
>
> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> > What are the other differences on the two servers Sig?
> >
> > /Anne Kathrine
> > Sent from my iPhone
> >
> > On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
> >
> >> I have, on the other server that runs ok (except that original
> >> api_test login issue) it's same OpenJDK, basically everything is
> >> same... (I'm sure that did not help much LOL)
> >>
> >>
> >> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> >>>
> >>> I don't think anything has changed. Just that no one has used openJDK
> >>> since
> >>> then.
> >>>
> >>> /Anne Kathrine
> >>> Sent from my iPhone
> >>>
> >>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
> wrote:
> >>>
> >>>> But what has changed so that the problem now occurs?
> >>>>
> >>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
> >>>> <yo...@gmail.com>wrote:
> >>>>
> >>>>> Yay! :-)
> >>>>>
> >>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
> >>>>>
> >>>>>> Aha :)
> >>>>>>
> >>>>>> java version "1.6.0_0"
> >>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
> >>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
> >>>>>>
> >>>>>> Sig
> >>>>>>
> >>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
> >>>>>>>
> >>>>>>> We've had this before:
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>>>
> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
> >>>>>>>
> >>>>>>> The interesting part is that noone has implemented David's
> suggestion
> >>>>>>> to date, and still the problem seems to have been resolved (or was
> >>>>>>> it?)
> >>>>>>>
> >>>>>>> BTW what JDK are you using? I've had my share of problems on
> >>>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
> >>>>>>> which was not mature enough to run bug-free.
> >>>>>>>
> >>>>>>> Vassil
> >>>>>>>
> >>>>>>>
> >>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
> >>>>>>> <hi...@gmail.com>
> >>>>>
> >>>>> wrote:
> >>>>>>>>
> >>>>>>>> I'm going to try it locally to see if it works on my laptop
> >>>>>>>>
> >>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
> >>>>>>>>
> >>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
> >>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting
> up
> >>>>>>>>> a
> >>>>>>>>> fresh image.
> >>>>>>>>>
> >>>>>>>>> Then:
> >>>>>>>>> apt-get install subversion
> >>>>>>>>> apt-get install maven2
> >>>>>>>>> apt-get install jetty
> >>>>>>>>>
> >>>>>>>>> Then:
> >>>>>>>>> svn checkout
> >>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
> >>>>>>>>>
> >>>>>>>>> Then fixing the two files.
> >>>>>>>>>
> >>>>>>>>> Then problem :)
> >>>>>>>>>
> >>>>>>>>> Now: rm -rf esme and started over
> >>>>>>>>>
> >>>>>>>>> One never knows where I could have messed up, only mishap was
> that
> >>>>>>>>> I
> >>>>>>>>> lost contact with the server at some point during first mvn... so
> >>>>>>>>> now
> >>>>>>>>> I did & and logged out leaving it alone... lets see now:
> >>>>>>>>>
> >>>>>>>>> Nope, exact same error.
> >>>>>>>>>
> >>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
> >>>>>>>>> after
> >>>>>>>>> a
> >>>>>>>>> bit, and when trying again it says compiling 8 packages. No other
> >>>>>>>>> clues.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>>>>>>>
> >>>>>>>>>> RE plug-in: I remember.
> >>>>>>>>>>
> >>>>>>>>>> I think something else (Scala, lift, etc.) might have changed.
> >>>>>>>>>> Has
> >>>>>>>>>
> >>>>>>>>> anything
> >>>>>>>>>>
> >>>>>>>>>> else changed in the environment?
> >>>>>>>>>>
> >>>>>>>>>> It is all very strange. It is obviously a maven-related problem,
> >>>>>
> >>>>> because
> >>>>>>>>>>
> >>>>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
> >>>>>>>>>>
> >>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Then I get this:
> >>>>>>>>>>>
> >>>>>>>>>>> [ERROR] FATAL ERROR
> >>>>>>>>>>> [INFO]
> >>>>>>>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>>>>>>>>
> >>>>>>>>>>> [INFO] null
> >>>>>>>>>>> [INFO]
> >>>>>>>>>>>
> >>>>>
> >>>>>
> ------------------------------------------------------------------------
> >>>>>>>>>>>
> >>>>>>>>>>> [INFO] Trace
> >>>>>>>>>>> java.lang.RuntimeException
> >>>>>>>>>>> at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> >>>>>>>>>>>
> >>>>>>>>>>> at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> >>>>>>>>>>>
> >>>>>>>>>>> at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> >>>>>>>>>>>
> >>>>>>>>>>> at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> >>>>>>>>>>>
> >>>>>>>>>>> at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
> >>>>>>>>>>>
> >>>>>>>>>>> BTW, it was you who suggested doing this last time, and then
> all
> >>>>>>>>>>> was
> >>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>>>>>>>>>
> >>>>>>>>>>>> what happens if you don't comment out the plug-in
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
> >>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Ethan,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Prior to that:
> >>>>>>>>>>>>> 1. svn the full esme
> >>>>>>>>>>>>> 2. add line to default.props
> >>>>>>>>>>>>> 3. comment out plugin in pom.xml
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> using -e gave this at the end:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> [INFO] Trace
> >>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
> >>>>>>>>>
> >>>>>>>>> non-zero
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> value:1
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>
> >>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>
> >>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> >>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >>>>>
> >>>>> Method)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>
> >>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>
> >>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
> >>>>>>>>>>>>> command
> >>>>>
> >>>>> line
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> returned non-zero value:1
> >>>>>>>>>>>>> at
> >>>>>
> >>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> at
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>
> >>>>>
> >>>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> ... 20 more
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hi Sig,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Can you give the full stack trace - I don't think this once
> >>>>>>>>>>>>>> goes
> >>>>>>>>>
> >>>>>>>>> deep
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere
> >>>>>>>>>>>>>> else?
> >>>>>
> >>>>> And
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> exactly what command are you running that results in this
> >>>>>>>>>>>>>> error?
> >>>>>>>>>
> >>>>>>>>> mvn
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> clean install?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>> Ethan
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
> >>>>>
> >>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Thanks Ethan,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new
> >>>>>>>>>>>>>>> and
> >>>>>>>>>
> >>>>>>>>> fresh
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
> >>>>>>>>>>>>>>> apt-get
> >>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> New svn from esme.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Added new api_test user in default.props and commented out
> >>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>> compression plug-in in pom.xml.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Then fired it up and got this error:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
> >>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
> >>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> /home/files/esme/server/target/test-classes
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
> >>>>>
> >>>>> java.lang.StackOverflowError
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [WARNING] at
> >>>>>>>>>>>>>
> >>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [WARNING] at
> >>>>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [WARNING] at
> >>>>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [WARNING] at
> >>>>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [WARNING] at
> >>>>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> [WARNING] at
> >>>>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> ...
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> So what did I forget this time :)
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> S
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hi Sig,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
> >>>>>>>>>>>>>>>> don't
> >>>>>>>>>
> >>>>>>>>> have
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting
> >>>>>>>>>>>>>>>> for
> >>>>>>>>>
> >>>>>>>>> the
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> integration test user other than in the API2 code.
> >>>>>>>>>>>>>>>> Definitely
> >>>>>>>>>>>>>>>> possible. I will try to look in to it.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Question if you have the time: If you add another line in
> >>>>>>>>>>>>>>>> the
> >>>>>>>>>>>
> >>>>>>>>>>> property
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> file and assign a second user as integration admin, does
> >>>>>>>>>>>>>>>> that
> >>>>>>>>>
> >>>>>>>>> user
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> stop working in the web interface as well?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>> Ethan
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <sig@rinde.com
> >
> >>>>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Morning creative sleuth work:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
> >>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything
> >>>>>>>>>>>>>>>>> but
> >>>>>>>>>
> >>>>>>>>> root,
> >>>>>>>>>>>
> >>>>>>>>>>> say
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
> >>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
> problem
> >>>>>>>>>>>>>>>>> on
> >>>>>>>>>
> >>>>>>>>> all
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> browsers.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
> >>>>>>>>>>>>>>>>> instance.
> >>>>>>>>>
> >>>>>>>>> (aws
> >>>>>>>>>>>
> >>>>>>>>>>> is
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> ubuntu, local is OS X)
> >>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
> >>>>>>>>>>>>>>>>> folders
> >>>>>
> >>>>> and
> >>>>>>>>>>>
> >>>>>>>>>>> found
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I removed
> >>>>>>>>>>>>>>>>> after
> >>>>>>>>>>>
> >>>>>>>>>>> first
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> try).
> >>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no
> >>>>>>>>>>>>>>>>> diff
> >>>>>>>>>>>
> >>>>>>>>>>> except
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
> >>>>>
> >>>>> .gitignore.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> The server works though, and now I know how to get in
> there
> >>>>>>>>>>>>>>>>> so
> >>>>>
> >>>>> I
> >>>>>>>>>>>
> >>>>>>>>>>> can
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a later
> new
> >>>>>
> >>>>> and
> >>>>>>>>>>>
> >>>>>>>>>>> fresh
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> install... :)
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
No differences as far as I can see. The two:
Server A: Esme built w/o problems Jan 5
Server B: Esme build error Jan 26
Ubuntu 9.04 - both updated before installing ESME.
JDK same.
Basically same-same :)
2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> What are the other differences on the two servers Sig?
>
> /Anne Kathrine
> Sent from my iPhone
>
> On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
>
>> I have, on the other server that runs ok (except that original
>> api_test login issue) it's same OpenJDK, basically everything is
>> same... (I'm sure that did not help much LOL)
>>
>>
>> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>
>>> I don't think anything has changed. Just that no one has used openJDK
>>> since
>>> then.
>>>
>>> /Anne Kathrine
>>> Sent from my iPhone
>>>
>>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com> wrote:
>>>
>>>> But what has changed so that the problem now occurs?
>>>>
>>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>> <yo...@gmail.com>wrote:
>>>>
>>>>> Yay! :-)
>>>>>
>>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>
>>>>>> Aha :)
>>>>>>
>>>>>> java version "1.6.0_0"
>>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>
>>>>>> Sig
>>>>>>
>>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>>
>>>>>>> We've had this before:
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>>
>>>>>>> The interesting part is that noone has implemented David's suggestion
>>>>>>> to date, and still the problem seems to have been resolved (or was
>>>>>>> it?)
>>>>>>>
>>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>>>>> which was not mature enough to run bug-free.
>>>>>>>
>>>>>>> Vassil
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>> <hi...@gmail.com>
>>>>>
>>>>> wrote:
>>>>>>>>
>>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>>
>>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>
>>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up
>>>>>>>>> a
>>>>>>>>> fresh image.
>>>>>>>>>
>>>>>>>>> Then:
>>>>>>>>> apt-get install subversion
>>>>>>>>> apt-get install maven2
>>>>>>>>> apt-get install jetty
>>>>>>>>>
>>>>>>>>> Then:
>>>>>>>>> svn checkout
>>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>>
>>>>>>>>> Then fixing the two files.
>>>>>>>>>
>>>>>>>>> Then problem :)
>>>>>>>>>
>>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>>
>>>>>>>>> One never knows where I could have messed up, only mishap was that
>>>>>>>>> I
>>>>>>>>> lost contact with the server at some point during first mvn... so
>>>>>>>>> now
>>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>>
>>>>>>>>> Nope, exact same error.
>>>>>>>>>
>>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>>>>>>>>> after
>>>>>>>>> a
>>>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>>>>> clues.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>> RE plug-in: I remember.
>>>>>>>>>>
>>>>>>>>>> I think something else (Scala, lift, etc.) might have changed.
>>>>>>>>>> Has
>>>>>>>>>
>>>>>>>>> anything
>>>>>>>>>>
>>>>>>>>>> else changed in the environment?
>>>>>>>>>>
>>>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>>>>>
>>>>> because
>>>>>>>>>>
>>>>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Then I get this:
>>>>>>>>>>>
>>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> [INFO] null
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>>>>>>
>>>>>>>>>>> BTW, it was you who suggested doing this last time, and then all
>>>>>>>>>>> was
>>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>
>>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Ethan,
>>>>>>>>>>>>>
>>>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>>>>
>>>>>>>>>>>>> Prior to that:
>>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>>>
>>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>>>>>
>>>>>>>>> non-zero
>>>>>>>>>>>>>
>>>>>>>>>>>>> value:1
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>
>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>
>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>
>>>>> Method)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>
>>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>
>>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>>>>>>>
>>>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
>>>>>>>>>>>>> command
>>>>>
>>>>> line
>>>>>>>>>>>>>
>>>>>>>>>>>>> returned non-zero value:1
>>>>>>>>>>>>> at
>>>>>
>>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>>>>>>>
>>>>>>>>>>>>> ... 20 more
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Can you give the full stack trace - I don't think this once
>>>>>>>>>>>>>> goes
>>>>>>>>>
>>>>>>>>> deep
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere
>>>>>>>>>>>>>> else?
>>>>>
>>>>> And
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> exactly what command are you running that results in this
>>>>>>>>>>>>>> error?
>>>>>>>>>
>>>>>>>>> mvn
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> clean install?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>>
>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks Ethan,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new
>>>>>>>>>>>>>>> and
>>>>>>>>>
>>>>>>>>> fresh
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
>>>>>>>>>>>>>>> apt-get
>>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Added new api_test user in default.props and commented out
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>>
>>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>
>>>>> java.lang.StackOverflowError
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> S
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>>>>>>>>>>>>>>>> don't
>>>>>>>>>
>>>>>>>>> have
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting
>>>>>>>>>>>>>>>> for
>>>>>>>>>
>>>>>>>>> the
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>>>>>>>>>>>>> Definitely
>>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Question if you have the time: If you add another line in
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>
>>>>>>>>>>> property
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> file and assign a second user as integration admin, does
>>>>>>>>>>>>>>>> that
>>>>>>>>>
>>>>>>>>> user
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>
>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything
>>>>>>>>>>>>>>>>> but
>>>>>>>>>
>>>>>>>>> root,
>>>>>>>>>>>
>>>>>>>>>>> say
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem
>>>>>>>>>>>>>>>>> on
>>>>>>>>>
>>>>>>>>> all
>>>>>>>>>>>>>
>>>>>>>>>>>>> browsers.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
>>>>>>>>>>>>>>>>> instance.
>>>>>>>>>
>>>>>>>>> (aws
>>>>>>>>>>>
>>>>>>>>>>> is
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>>>>> folders
>>>>>
>>>>> and
>>>>>>>>>>>
>>>>>>>>>>> found
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I removed
>>>>>>>>>>>>>>>>> after
>>>>>>>>>>>
>>>>>>>>>>> first
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> try).
>>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no
>>>>>>>>>>>>>>>>> diff
>>>>>>>>>>>
>>>>>>>>>>> except
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>>
>>>>> .gitignore.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> The server works though, and now I know how to get in there
>>>>>>>>>>>>>>>>> so
>>>>>
>>>>> I
>>>>>>>>>>>
>>>>>>>>>>> can
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>>>
>>>>> and
>>>>>>>>>>>
>>>>>>>>>>> fresh
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>
>
Re: Wee error
Posted by Anne Kathrine Petterøe <yo...@gmail.com>.
What are the other differences on the two servers Sig?
/Anne Kathrine
Sent from my iPhone
On 26. jan. 2010, at 16.09, Sig Rinde <si...@rinde.com> wrote:
> I have, on the other server that runs ok (except that original
> api_test login issue) it's same OpenJDK, basically everything is
> same... (I'm sure that did not help much LOL)
>
>
> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> I don't think anything has changed. Just that no one has used
>> openJDK since
>> then.
>>
>> /Anne Kathrine
>> Sent from my iPhone
>>
>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
>> wrote:
>>
>>> But what has changed so that the problem now occurs?
>>>
>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>> <yo...@gmail.com>wrote:
>>>
>>>> Yay! :-)
>>>>
>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>
>>>>> Aha :)
>>>>>
>>>>> java version "1.6.0_0"
>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>>> (6b14-1.4.1-0ubuntu12)
>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>
>>>>> Sig
>>>>>
>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>
>>>>>> We've had this before:
>>>>>>
>>>>>>
>>>>
>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>
>>>>>> The interesting part is that noone has implemented David's
>>>>>> suggestion
>>>>>> to date, and still the problem seems to have been resolved (or
>>>>>> was
>>>>>> it?)
>>>>>>
>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>> Debian/Ubuntu because package management decided to pull
>>>>>> openjdk-6,
>>>>>> which was not mature enough to run bug-free.
>>>>>>
>>>>>> Vassil
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>>>> >
>>>>
>>>> wrote:
>>>>>>>
>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-
>>>>>>>> date
>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>>>>>> starting up a
>>>>>>>> fresh image.
>>>>>>>>
>>>>>>>> Then:
>>>>>>>> apt-get install subversion
>>>>>>>> apt-get install maven2
>>>>>>>> apt-get install jetty
>>>>>>>>
>>>>>>>> Then:
>>>>>>>> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>
>>>>>>>> Then fixing the two files.
>>>>>>>>
>>>>>>>> Then problem :)
>>>>>>>>
>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>
>>>>>>>> One never knows where I could have messed up, only mishap was
>>>>>>>> that I
>>>>>>>> lost contact with the server at some point during first
>>>>>>>> mvn... so now
>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>
>>>>>>>> Nope, exact same error.
>>>>>>>>
>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>>>>>> dies after
>>>>>>>> a
>>>>>>>> bit, and when trying again it says compiling 8 packages. No
>>>>>>>> other
>>>>>>>> clues.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>
>>>>>>>>> RE plug-in: I remember.
>>>>>>>>>
>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>>>>>> changed. Has
>>>>>>>>
>>>>>>>> anything
>>>>>>>>>
>>>>>>>>> else changed in the environment?
>>>>>>>>>
>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>>>>>>> problem,
>>>>
>>>> because
>>>>>>>>>
>>>>>>>>> ESME's code hasn't really changed at all in the last few
>>>>>>>>> weeks.
>>>>>>>>>
>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Then I get this:
>>>>>>>>>>
>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>> ---
>>>> ---
>>>> ------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> [INFO] null
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>> ---
>>>> ---
>>>> ------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> [INFO] Trace
>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(
>>>> JavaScriptCompressor.java:299)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse
>>>> (JavaScriptCompressor.java:335)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>
>>>> (JavaScriptCompressor.java:532)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile
>>>> (YuiCompressorMojo.java:178)
>>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir
>>>> (MojoSupport.java:151)
>>>>>>>>>>
>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>>>>>>>> then all
>>>>>>>>>> was
>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Ethan,
>>>>>>>>>>>>
>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>>>>>>>>>> jetty:run"
>>>>>>>>>>>>
>>>>>>>>>>>> Prior to that:
>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>>
>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>>>>>>>>>> returned
>>>>>>>>
>>>>>>>> non-zero
>>>>>>>>>>>>
>>>>>>>>>>>> value:1
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>>>> (DefaultLifecycleExecutor.java:579)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
>>>> DefaultLifecycleExecutor.java:499)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(
>>>> DefaultLifecycleExecutor.java:924)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle
>>>> (DefaultLifecycleExecutor.java:767)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>>>> (DefaultLifecycleExecutor.java:529)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
>>>> DefaultLifecycleExecutor.java:512)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
>>>> (DefaultLifecycleExecutor.java:482)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>>>> DefaultLifecycleExecutor.java:330)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>>>> DefaultLifecycleExecutor.java:291)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
>>>> (DefaultLifecycleExecutor.java:142)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>
>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>
>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>>>>
>>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:
>>>>>>>>>>>> 287)
>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>
>>>> Method)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke
>>>> (NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke
>>>> (DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>>
>>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>
>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:
>>>> 430)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>
>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>>>>>>
>>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
>>>>>>>>>>>> command
>>>>
>>>> line
>>>>>>>>>>>>
>>>>>>>>>>>> returned non-zero value:1
>>>>>>>>>>>> at
>>>>
>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.compile
>>>> (ScalaCompilerSupport.java:124)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute
>>>> (ScalaCompilerSupport.java:54)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>> org.scala_tools.maven.ScalaMojoSupport.execute
>>>> (ScalaMojoSupport.java:208)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.execute
>>>> (ScalaCompilerSupport.java:29)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute
>>>> (ScalaTestCompileMojo.java:58)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo
>>>> (DefaultPluginManager.java:451)
>>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>>>> (DefaultLifecycleExecutor.java:558)
>>>>>>>>>>>>
>>>>>>>>>>>> ... 20 more
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you give the full stack trace - I don't think this
>>>>>>>>>>>>> once goes
>>>>>>>>
>>>>>>>> deep
>>>>>>>>>>>>>
>>>>>>>>>>>>> enough for us to see if the error is in ESME or
>>>>>>>>>>>>> somewhere else?
>>>>
>>>> And
>>>>>>>>>>>>>
>>>>>>>>>>>>> exactly what command are you running that results in
>>>>>>>>>>>>> this error?
>>>>>>>>
>>>>>>>> mvn
>>>>>>>>>>>>>
>>>>>>>>>>>>> clean install?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>
>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks Ethan,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a
>>>>>>>>>>>>>> new and
>>>>>>>>
>>>>>>>> fresh
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
>>>>>>>>>>>>>> apt-get
>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Added new api_test user in default.props and commented
>>>>>>>>>>>>>> out the
>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>
>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>
>>>> java.lang.StackOverflowError
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>
>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:
>>>> 1563)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>> (Symbols.scala:940)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>> (Symbols.scala:942)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>> (Symbols.scala:942)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>> (Symbols.scala:942)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>> (Symbols.scala:942)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> S
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>>>>>>>>>>>>> Unfortunately I
>>>>>>>>>>>>>>> don't
>>>>>>>>
>>>>>>>> have
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>>>>>>>>>>>> setting for
>>>>>>>>
>>>>>>>> the
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>>>>>>>>>>>> Definitely
>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Question if you have the time: If you add another line
>>>>>>>>>>>>>>> in the
>>>>>>>>>>
>>>>>>>>>> property
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> file and assign a second user as integration admin,
>>>>>>>>>>>>>>> does that
>>>>>>>>
>>>>>>>> user
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <sig@rinde.com
>>>>>>>>>>>>>>> >
>>>>>>>>
>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>>>>>>>>>>>>> anything but
>>>>>>>>
>>>>>>>> root,
>>>>>>>>>>
>>>>>>>>>> say
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>> on
>>>>>>>>
>>>>>>>> all
>>>>>>>>>>>>
>>>>>>>>>>>> browsers.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
>>>>>>>>>>>>>>>> instance.
>>>>>>>>
>>>>>>>> (aws
>>>>>>>>>>
>>>>>>>>>> is
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>>>> folders
>>>>
>>>> and
>>>>>>>>>>
>>>>>>>>>> found
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>>>>>>>>>>>>>> removed
>>>>>>>>>>>>>>>> after
>>>>>>>>>>
>>>>>>>>>> first
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> try).
>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found
>>>>>>>>>>>>>>>> no diff
>>>>>>>>>>
>>>>>>>>>> except
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>
>>>> .gitignore.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The server works though, and now I know how to get in
>>>>>>>>>>>>>>>> there
>>>>>>>>>>>>>>>> so
>>>>
>>>> I
>>>>>>>>>>
>>>>>>>>>> can
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> live with problem and assume it'll go away with a
>>>>>>>>>>>>>>>> later new
>>>>
>>>> and
>>>>>>>>>>
>>>>>>>>>> fresh
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>>
>>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
I have, on the other server that runs ok (except that original
api_test login issue) it's same OpenJDK, basically everything is
same... (I'm sure that did not help much LOL)
2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> I don't think anything has changed. Just that no one has used openJDK since
> then.
>
> /Anne Kathrine
> Sent from my iPhone
>
> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com> wrote:
>
>> But what has changed so that the problem now occurs?
>>
>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>> <yo...@gmail.com>wrote:
>>
>>> Yay! :-)
>>>
>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>
>>>> Aha :)
>>>>
>>>> java version "1.6.0_0"
>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>
>>>> Sig
>>>>
>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>
>>>>> We've had this before:
>>>>>
>>>>>
>>>
>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>
>>>>> The interesting part is that noone has implemented David's suggestion
>>>>> to date, and still the problem seems to have been resolved (or was
>>>>> it?)
>>>>>
>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>>> which was not mature enough to run bug-free.
>>>>>
>>>>> Vassil
>>>>>
>>>>>
>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hi...@gmail.com>
>>>
>>> wrote:
>>>>>>
>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>
>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>
>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up a
>>>>>>> fresh image.
>>>>>>>
>>>>>>> Then:
>>>>>>> apt-get install subversion
>>>>>>> apt-get install maven2
>>>>>>> apt-get install jetty
>>>>>>>
>>>>>>> Then:
>>>>>>> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>
>>>>>>> Then fixing the two files.
>>>>>>>
>>>>>>> Then problem :)
>>>>>>>
>>>>>>> Now: rm -rf esme and started over
>>>>>>>
>>>>>>> One never knows where I could have messed up, only mishap was that I
>>>>>>> lost contact with the server at some point during first mvn... so now
>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>
>>>>>>> Nope, exact same error.
>>>>>>>
>>>>>>> Noticed that it starts saying compiling 49 packages, then dies after
>>>>>>> a
>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>>> clues.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>
>>>>>>>> RE plug-in: I remember.
>>>>>>>>
>>>>>>>> I think something else (Scala, lift, etc.) might have changed. Has
>>>>>>>
>>>>>>> anything
>>>>>>>>
>>>>>>>> else changed in the environment?
>>>>>>>>
>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>>>
>>> because
>>>>>>>>
>>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>
>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>
>>>>>>>>> Then I get this:
>>>>>>>>>
>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>> [INFO]
>>>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> [INFO] null
>>>>>>>>> [INFO]
>>>>>>>>>
>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> [INFO] Trace
>>>>>>>>> java.lang.RuntimeException
>>>>>>>>> at
>>>>>>>>>
>>>>>>>
>>>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>>
>>>>>>>
>>>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>>
>>>>>>>
>>>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>>
>>>>>>>
>>>
>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>>
>>>>>>>
>>>
>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>>>>
>>>>>>>>> BTW, it was you who suggested doing this last time, and then all
>>>>>>>>> was
>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Ethan,
>>>>>>>>>>>
>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>>
>>>>>>>>>>> Prior to that:
>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>
>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>>>
>>>>>>> non-zero
>>>>>>>>>>>
>>>>>>>>>>> value:1
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>
>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>
>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>>>
>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>
>>> Method)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>>>
>>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>> at
>>>>>>>>>>>
>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>
>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>
>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>>>>>
>>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
>>>
>>> line
>>>>>>>>>>>
>>>>>>>>>>> returned non-zero value:1
>>>>>>>>>>> at
>>>
>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>>>>>
>>>>>>>>>>> ... 20 more
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>
>>>>>>>>>>>> Can you give the full stack trace - I don't think this once goes
>>>>>>>
>>>>>>> deep
>>>>>>>>>>>>
>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere else?
>>>
>>> And
>>>>>>>>>>>>
>>>>>>>>>>>> exactly what command are you running that results in this error?
>>>>>>>
>>>>>>> mvn
>>>>>>>>>>>>
>>>>>>>>>>>> clean install?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Ethan
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>
>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks Ethan,
>>>>>>>>>>>>>
>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new and
>>>>>>>
>>>>>>> fresh
>>>>>>>>>>>>>
>>>>>>>>>>>>> Amazon instance (same base image as the other live one),
>>>>>>>>>>>>> apt-get
>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>
>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Added new api_test user in default.props and commented out the
>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>
>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>
>>> java.lang.StackOverflowError
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>
>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>
>>>>>>>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>
>>>>>>>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>
>>>>>>>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>
>>>>>>>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>
>>>>>>>
>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>>
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>
>>>>>>>>>>>>> S
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>>>>>>>>>>>>>> don't
>>>>>>>
>>>>>>> have
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting for
>>>>>>>
>>>>>>> the
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Question if you have the time: If you add another line in the
>>>>>>>>>
>>>>>>>>> property
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> file and assign a second user as integration admin, does that
>>>>>>>
>>>>>>> user
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>>>
>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything but
>>>>>>>
>>>>>>> root,
>>>>>>>>>
>>>>>>>>> say
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem
>>>>>>>>>>>>>>> on
>>>>>>>
>>>>>>> all
>>>>>>>>>>>
>>>>>>>>>>> browsers.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
>>>>>>>
>>>>>>> (aws
>>>>>>>>>
>>>>>>>>> is
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp folders
>>>
>>> and
>>>>>>>>>
>>>>>>>>> found
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I removed
>>>>>>>>>>>>>>> after
>>>>>>>>>
>>>>>>>>> first
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> try).
>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no diff
>>>>>>>>>
>>>>>>>>> except
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>
>>> .gitignore.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The server works though, and now I know how to get in there
>>>>>>>>>>>>>>> so
>>>
>>> I
>>>>>>>>>
>>>>>>>>> can
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>
>>> and
>>>>>>>>>
>>>>>>>>> fresh
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>>
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
Anyway, I'll try to follow David's recommendations, but meanwhile, is
it an option to use a different JDK? I think we had other problems,
although it might have improved since then.
On Tue, Jan 26, 2010 at 5:29 PM, Sig Rinde <si...@rinde.com> wrote:
> The two should be exactly same - including JDK.
>
> Both using same (bit old now) self built Amazon image, then apt-get
> update and upgrade so they should be identical.
>
>
> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>> First of all, the problem should be the JDK, because if it was Lift,
>> everyone should have the same problem.
>>
>> It's possible that it worked before on the same JDK if ESME was built
>> on a different machine with, let's say, Sun's JDK. Is this possible?
>>
>>
>> On Tue, Jan 26, 2010 at 5:20 PM, Sig Rinde <si...@rinde.com> wrote:
>>> think I'm confusing now so let me sum up the two errors:
>>>
>>> 1.
>>> The original issue is identical to the one that Vassil pointed to. And
>>> that is not new, and is still very much present (but I have a work
>>> around: Hit "about" then log in - the error applies only to "root" for
>>> 8080).
>>>
>>> 2.
>>> The second error here is that I cannot even build any more - much
>>> scala error messages. And that in seemingly identical environment as
>>> the one I installed on Jan 5, then restarted again on 8th - which
>>> worked.
>>>
>>> Was that better or did I confuse even more? :)
>>>
>>>
>>>
>>> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>>> Didn't Sig just change environment?
>>>>
>>>> /Anne Kathrine
>>>> Sent from my iPhone
>>>>
>>>> On 26. jan. 2010, at 16.09, Richard Hirsch <hi...@gmail.com> wrote:
>>>>
>>>>> That is true but I'm assuming that Sig has used OpenJDK since the he
>>>>> started
>>>>> integrating ESME.
>>>>>
>>>>> On Tue, Jan 26, 2010 at 4:05 PM, Anne Kathrine Petterøe
>>>>> <yo...@gmail.com>wrote:
>>>>>
>>>>>> I don't think anything has changed. Just that no one has used openJDK
>>>>>> since
>>>>>> then.
>>>>>>
>>>>>> /Anne Kathrine
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>
>>>>>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>>
>>>>>> But what has changed so that the problem now occurs?
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>>>> <yo...@gmail.com>wrote:
>>>>>>>
>>>>>>> Yay! :-)
>>>>>>>>
>>>>>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>>>>
>>>>>>>> Aha :)
>>>>>>>>>
>>>>>>>>> java version "1.6.0_0"
>>>>>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>>>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>>>>
>>>>>>>>> Sig
>>>>>>>>>
>>>>>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>>>>
>>>>>>>>>> We've had this before:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The interesting part is that noone has implemented David's suggestion
>>>>>>>>>> to date, and still the problem seems to have been resolved (or was
>>>>>>>>>> it?)
>>>>>>>>>>
>>>>>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>>>>>>>> which was not mature enough to run bug-free.
>>>>>>>>>>
>>>>>>>>>> Vassil
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>>>>> <hirsch.dick@gmail.com
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>>>>>>>
>>>>>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up
>>>>>>>>>>>> a
>>>>>>>>>>>> fresh image.
>>>>>>>>>>>>
>>>>>>>>>>>> Then:
>>>>>>>>>>>> apt-get install subversion
>>>>>>>>>>>> apt-get install maven2
>>>>>>>>>>>> apt-get install jetty
>>>>>>>>>>>>
>>>>>>>>>>>> Then:
>>>>>>>>>>>> svn checkout
>>>>>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>>>>>
>>>>>>>>>>>> Then fixing the two files.
>>>>>>>>>>>>
>>>>>>>>>>>> Then problem :)
>>>>>>>>>>>>
>>>>>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>>>>>
>>>>>>>>>>>> One never knows where I could have messed up, only mishap was that
>>>>>>>>>>>> I
>>>>>>>>>>>> lost contact with the server at some point during first mvn... so
>>>>>>>>>>>> now
>>>>>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>>>>>
>>>>>>>>>>>> Nope, exact same error.
>>>>>>>>>>>>
>>>>>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>>>>>>>>>>>> after
>>>>>>>>>>>> a
>>>>>>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>>>>>>>> clues.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>
>>>>>>>>>>>>> RE plug-in: I remember.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I think something else (Scala, lift, etc.) might have changed.
>>>>>>>>>>>>> Has
>>>>>>>>>>>>>
>>>>>>>>>>>> anything
>>>>>>>>>>>>
>>>>>>>>>>>>> else changed in the environment?
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>>>>>>>>>>>>>
>>>>>>>>>>>> because
>>>>>>>>
>>>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Then I get this:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>>> [INFO] null
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>>> [INFO] Trace
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>> BTW, it was you who suggested doing this last time, and then all
>>>>>>>>>>>>>> was
>>>>>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Ethan,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Prior to that:
>>>>>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> non-zero
>>>>>>>>>>>>
>>>>>>>>>>>>> value:1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>>>>
>>>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Method)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>>
>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>>
>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> line
>>>>>>>>
>>>>>>>>> returned non-zero value:1
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>>
>>>>>>>>> ... 20 more
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Can you give the full stack trace - I don't think this once
>>>>>>>>>>>>>>>>> goes
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> deep
>>>>>>>>>>>>
>>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere else?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> And
>>>>>>>>
>>>>>>>>> exactly what command are you running that results in this error?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> mvn
>>>>>>>>>>>>
>>>>>>>>>>>>> clean install?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thanks Ethan,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> fresh
>>>>>>>>>>>>
>>>>>>>>>>>>> Amazon instance (same base image as the other live one), apt-get
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Added new api_test user in default.props and commented out
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> java.lang.StackOverflowError
>>>>>>>>
>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>>
>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>>
>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> S
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>>>>>>>>>>>>>>>>>>> don't
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> have
>>>>>>>>>>>>
>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting
>>>>>>>>>>>>>>>>>>> for
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>
>>>>>>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Question if you have the time: If you add another line in
>>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> property
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> file and assign a second user as integration admin, does that
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> user
>>>>>>>>>>>>
>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything
>>>>>>>>>>>>>>>>>>>> but
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> root,
>>>>>>>>>>>>
>>>>>>>>>>>>> say
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem
>>>>>>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> all
>>>>>>>>>>>>
>>>>>>>>>>>>> browsers.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> (aws
>>>>>>>>>>>>
>>>>>>>>>>>>> is
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>>>>>>>> folders
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> and
>>>>>>>>
>>>>>>>>> found
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> nothing different (except the .svn stuff which I removed after
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> first
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> try).
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no
>>>>>>>>>>>>>>>>>>>> diff
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> except
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> .gitignore.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> The server works though, and now I know how to get in there
>>>>>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I
>>>>>>>>
>>>>>>>>> can
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> and
>>>>>>>>
>>>>>>>>> fresh
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
The two should be exactly same - including JDK.
Both using same (bit old now) self built Amazon image, then apt-get
update and upgrade so they should be identical.
2010/1/26 Vassil Dichev <vd...@apache.org>:
> First of all, the problem should be the JDK, because if it was Lift,
> everyone should have the same problem.
>
> It's possible that it worked before on the same JDK if ESME was built
> on a different machine with, let's say, Sun's JDK. Is this possible?
>
>
> On Tue, Jan 26, 2010 at 5:20 PM, Sig Rinde <si...@rinde.com> wrote:
>> think I'm confusing now so let me sum up the two errors:
>>
>> 1.
>> The original issue is identical to the one that Vassil pointed to. And
>> that is not new, and is still very much present (but I have a work
>> around: Hit "about" then log in - the error applies only to "root" for
>> 8080).
>>
>> 2.
>> The second error here is that I cannot even build any more - much
>> scala error messages. And that in seemingly identical environment as
>> the one I installed on Jan 5, then restarted again on 8th - which
>> worked.
>>
>> Was that better or did I confuse even more? :)
>>
>>
>>
>> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>>> Didn't Sig just change environment?
>>>
>>> /Anne Kathrine
>>> Sent from my iPhone
>>>
>>> On 26. jan. 2010, at 16.09, Richard Hirsch <hi...@gmail.com> wrote:
>>>
>>>> That is true but I'm assuming that Sig has used OpenJDK since the he
>>>> started
>>>> integrating ESME.
>>>>
>>>> On Tue, Jan 26, 2010 at 4:05 PM, Anne Kathrine Petterøe
>>>> <yo...@gmail.com>wrote:
>>>>
>>>>> I don't think anything has changed. Just that no one has used openJDK
>>>>> since
>>>>> then.
>>>>>
>>>>> /Anne Kathrine
>>>>> Sent from my iPhone
>>>>>
>>>>>
>>>>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com> wrote:
>>>>>
>>>>> But what has changed so that the problem now occurs?
>>>>>>
>>>>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>>> <yo...@gmail.com>wrote:
>>>>>>
>>>>>> Yay! :-)
>>>>>>>
>>>>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>>>
>>>>>>> Aha :)
>>>>>>>>
>>>>>>>> java version "1.6.0_0"
>>>>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>>>
>>>>>>>> Sig
>>>>>>>>
>>>>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>>>
>>>>>>>>> We've had this before:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>>
>>>>>>>>
>>>>>>>>> The interesting part is that noone has implemented David's suggestion
>>>>>>>>> to date, and still the problem seems to have been resolved (or was
>>>>>>>>> it?)
>>>>>>>>>
>>>>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>>>>>>> which was not mature enough to run bug-free.
>>>>>>>>>
>>>>>>>>> Vassil
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>>>> <hirsch.dick@gmail.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> wrote:
>>>>>>>
>>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>>>>>>
>>>>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up
>>>>>>>>>>> a
>>>>>>>>>>> fresh image.
>>>>>>>>>>>
>>>>>>>>>>> Then:
>>>>>>>>>>> apt-get install subversion
>>>>>>>>>>> apt-get install maven2
>>>>>>>>>>> apt-get install jetty
>>>>>>>>>>>
>>>>>>>>>>> Then:
>>>>>>>>>>> svn checkout
>>>>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>>>>
>>>>>>>>>>> Then fixing the two files.
>>>>>>>>>>>
>>>>>>>>>>> Then problem :)
>>>>>>>>>>>
>>>>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>>>>
>>>>>>>>>>> One never knows where I could have messed up, only mishap was that
>>>>>>>>>>> I
>>>>>>>>>>> lost contact with the server at some point during first mvn... so
>>>>>>>>>>> now
>>>>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>>>>
>>>>>>>>>>> Nope, exact same error.
>>>>>>>>>>>
>>>>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>>>>>>>>>>> after
>>>>>>>>>>> a
>>>>>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>>>>>>> clues.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>> RE plug-in: I remember.
>>>>>>>>>>>>
>>>>>>>>>>>> I think something else (Scala, lift, etc.) might have changed.
>>>>>>>>>>>> Has
>>>>>>>>>>>>
>>>>>>>>>>> anything
>>>>>>>>>>>
>>>>>>>>>>>> else changed in the environment?
>>>>>>>>>>>>
>>>>>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>>>>>>>>>>>>
>>>>>>>>>>> because
>>>>>>>
>>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Then I get this:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>> [INFO] null
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>> [INFO] Trace
>>>>>>>>>>>>>
>>>>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>>
>>>>>>>>
>>>>>>>>>>>>> BTW, it was you who suggested doing this last time, and then all
>>>>>>>>>>>>> was
>>>>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ethan,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Prior to that:
>>>>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> non-zero
>>>>>>>>>>>
>>>>>>>>>>>> value:1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>>>
>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>>>
>>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Method)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>
>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> line
>>>>>>>
>>>>>>>> returned non-zero value:1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>
>>>>>>>> ... 20 more
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Can you give the full stack trace - I don't think this once
>>>>>>>>>>>>>>>> goes
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> deep
>>>>>>>>>>>
>>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere else?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And
>>>>>>>
>>>>>>>> exactly what command are you running that results in this error?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> mvn
>>>>>>>>>>>
>>>>>>>>>>>> clean install?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks Ethan,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new
>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> fresh
>>>>>>>>>>>
>>>>>>>>>>>> Amazon instance (same base image as the other live one), apt-get
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Added new api_test user in default.props and commented out
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> java.lang.StackOverflowError
>>>>>>>
>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>
>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>>>>
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>>
>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> S
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>>>>>>>>>>>>>>>>>> don't
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> have
>>>>>>>>>>>
>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting
>>>>>>>>>>>>>>>>>> for
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>
>>>>>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Question if you have the time: If you add another line in
>>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> property
>>>>>>>>>>>>>
>>>>>>>>>>>>>> file and assign a second user as integration admin, does that
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> user
>>>>>>>>>>>
>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything
>>>>>>>>>>>>>>>>>>> but
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> root,
>>>>>>>>>>>
>>>>>>>>>>>> say
>>>>>>>>>>>>>
>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem
>>>>>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> all
>>>>>>>>>>>
>>>>>>>>>>>> browsers.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> (aws
>>>>>>>>>>>
>>>>>>>>>>>> is
>>>>>>>>>>>>>
>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>>>>>>> folders
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> and
>>>>>>>
>>>>>>>> found
>>>>>>>>>>>>>
>>>>>>>>>>>>>> nothing different (except the .svn stuff which I removed after
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> first
>>>>>>>>>>>>>
>>>>>>>>>>>>>> try).
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no
>>>>>>>>>>>>>>>>>>> diff
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> except
>>>>>>>>>>>>>
>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> .gitignore.
>>>>>>>
>>>>>>>>
>>>>>>>>>>>>>>>>>>> The server works though, and now I know how to get in there
>>>>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I
>>>>>>>
>>>>>>>> can
>>>>>>>>>>>>>
>>>>>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> and
>>>>>>>
>>>>>>>> fresh
>>>>>>>>>>>>>
>>>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>
>>
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
First of all, the problem should be the JDK, because if it was Lift,
everyone should have the same problem.
It's possible that it worked before on the same JDK if ESME was built
on a different machine with, let's say, Sun's JDK. Is this possible?
On Tue, Jan 26, 2010 at 5:20 PM, Sig Rinde <si...@rinde.com> wrote:
> think I'm confusing now so let me sum up the two errors:
>
> 1.
> The original issue is identical to the one that Vassil pointed to. And
> that is not new, and is still very much present (but I have a work
> around: Hit "about" then log in - the error applies only to "root" for
> 8080).
>
> 2.
> The second error here is that I cannot even build any more - much
> scala error messages. And that in seemingly identical environment as
> the one I installed on Jan 5, then restarted again on 8th - which
> worked.
>
> Was that better or did I confuse even more? :)
>
>
>
> 2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
>> Didn't Sig just change environment?
>>
>> /Anne Kathrine
>> Sent from my iPhone
>>
>> On 26. jan. 2010, at 16.09, Richard Hirsch <hi...@gmail.com> wrote:
>>
>>> That is true but I'm assuming that Sig has used OpenJDK since the he
>>> started
>>> integrating ESME.
>>>
>>> On Tue, Jan 26, 2010 at 4:05 PM, Anne Kathrine Petterøe
>>> <yo...@gmail.com>wrote:
>>>
>>>> I don't think anything has changed. Just that no one has used openJDK
>>>> since
>>>> then.
>>>>
>>>> /Anne Kathrine
>>>> Sent from my iPhone
>>>>
>>>>
>>>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com> wrote:
>>>>
>>>> But what has changed so that the problem now occurs?
>>>>>
>>>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>>> <yo...@gmail.com>wrote:
>>>>>
>>>>> Yay! :-)
>>>>>>
>>>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>>
>>>>>> Aha :)
>>>>>>>
>>>>>>> java version "1.6.0_0"
>>>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>>
>>>>>>> Sig
>>>>>>>
>>>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>>
>>>>>>>> We've had this before:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>>
>>>>>>>
>>>>>>>> The interesting part is that noone has implemented David's suggestion
>>>>>>>> to date, and still the problem seems to have been resolved (or was
>>>>>>>> it?)
>>>>>>>>
>>>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>>>>>> which was not mature enough to run bug-free.
>>>>>>>>
>>>>>>>> Vassil
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>>> <hirsch.dick@gmail.com
>>>>>>>>>
>>>>>>>>
>>>>>>> wrote:
>>>>>>
>>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>>>
>>>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>
>>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>>>>>
>>>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up
>>>>>>>>>> a
>>>>>>>>>> fresh image.
>>>>>>>>>>
>>>>>>>>>> Then:
>>>>>>>>>> apt-get install subversion
>>>>>>>>>> apt-get install maven2
>>>>>>>>>> apt-get install jetty
>>>>>>>>>>
>>>>>>>>>> Then:
>>>>>>>>>> svn checkout
>>>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>>>
>>>>>>>>>> Then fixing the two files.
>>>>>>>>>>
>>>>>>>>>> Then problem :)
>>>>>>>>>>
>>>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>>>
>>>>>>>>>> One never knows where I could have messed up, only mishap was that
>>>>>>>>>> I
>>>>>>>>>> lost contact with the server at some point during first mvn... so
>>>>>>>>>> now
>>>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>>>
>>>>>>>>>> Nope, exact same error.
>>>>>>>>>>
>>>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>>>>>>>>>> after
>>>>>>>>>> a
>>>>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>>>>>> clues.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>>> RE plug-in: I remember.
>>>>>>>>>>>
>>>>>>>>>>> I think something else (Scala, lift, etc.) might have changed.
>>>>>>>>>>> Has
>>>>>>>>>>>
>>>>>>>>>> anything
>>>>>>>>>>
>>>>>>>>>>> else changed in the environment?
>>>>>>>>>>>
>>>>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>>>>>>>>>>>
>>>>>>>>>> because
>>>>>>
>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Then I get this:
>>>>>>>>>>>>
>>>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>> [INFO] null
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO]
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>> [INFO] Trace
>>>>>>>>>>>>
>>>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>
>>>>>>>
>>>>>>>>>>>> BTW, it was you who suggested doing this last time, and then all
>>>>>>>>>>>> was
>>>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>
>>>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ethan,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Prior to that:
>>>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>>>>>>>>>>
>>>>>>>>>>>>> non-zero
>>>>>>>>>>
>>>>>>>>>>> value:1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>>
>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>>
>>>>>>>>>>>>> Method)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>
>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
>>>>>>>>>>>>>>
>>>>>>>>>>>>> line
>>>>>>
>>>>>>> returned non-zero value:1
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>
>>>>>>> at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>
>>>>>>> ... 20 more
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Can you give the full stack trace - I don't think this once
>>>>>>>>>>>>>>> goes
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> deep
>>>>>>>>>>
>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere else?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> And
>>>>>>
>>>>>>> exactly what command are you running that results in this error?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> mvn
>>>>>>>>>>
>>>>>>>>>>> clean install?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Ethan,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new
>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> fresh
>>>>>>>>>>
>>>>>>>>>>> Amazon instance (same base image as the other live one), apt-get
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Added new api_test user in default.props and commented out
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> java.lang.StackOverflowError
>>>>>>
>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>
>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>>>
>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>
>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>
>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>
>>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>>
>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> S
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>>>>>>>>>>>>>>>>> don't
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> have
>>>>>>>>>>
>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting
>>>>>>>>>>>>>>>>> for
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> the
>>>>>>>>>>
>>>>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Question if you have the time: If you add another line in
>>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> property
>>>>>>>>>>>>
>>>>>>>>>>>>> file and assign a second user as integration admin, does that
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> user
>>>>>>>>>>
>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything
>>>>>>>>>>>>>>>>>> but
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> root,
>>>>>>>>>>
>>>>>>>>>>> say
>>>>>>>>>>>>
>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem
>>>>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> all
>>>>>>>>>>
>>>>>>>>>>> browsers.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> (aws
>>>>>>>>>>
>>>>>>>>>>> is
>>>>>>>>>>>>
>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>>>>>> folders
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> and
>>>>>>
>>>>>>> found
>>>>>>>>>>>>
>>>>>>>>>>>>> nothing different (except the .svn stuff which I removed after
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> first
>>>>>>>>>>>>
>>>>>>>>>>>>> try).
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no
>>>>>>>>>>>>>>>>>> diff
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> except
>>>>>>>>>>>>
>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> .gitignore.
>>>>>>
>>>>>>>
>>>>>>>>>>>>>>>>>> The server works though, and now I know how to get in there
>>>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I
>>>>>>
>>>>>>> can
>>>>>>>>>>>>
>>>>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> and
>>>>>>
>>>>>>> fresh
>>>>>>>>>>>>
>>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
think I'm confusing now so let me sum up the two errors:
1.
The original issue is identical to the one that Vassil pointed to. And
that is not new, and is still very much present (but I have a work
around: Hit "about" then log in - the error applies only to "root" for
8080).
2.
The second error here is that I cannot even build any more - much
scala error messages. And that in seemingly identical environment as
the one I installed on Jan 5, then restarted again on 8th - which
worked.
Was that better or did I confuse even more? :)
2010/1/26 Anne Kathrine Petterøe <yo...@gmail.com>:
> Didn't Sig just change environment?
>
> /Anne Kathrine
> Sent from my iPhone
>
> On 26. jan. 2010, at 16.09, Richard Hirsch <hi...@gmail.com> wrote:
>
>> That is true but I'm assuming that Sig has used OpenJDK since the he
>> started
>> integrating ESME.
>>
>> On Tue, Jan 26, 2010 at 4:05 PM, Anne Kathrine Petterøe
>> <yo...@gmail.com>wrote:
>>
>>> I don't think anything has changed. Just that no one has used openJDK
>>> since
>>> then.
>>>
>>> /Anne Kathrine
>>> Sent from my iPhone
>>>
>>>
>>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com> wrote:
>>>
>>> But what has changed so that the problem now occurs?
>>>>
>>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>>> <yo...@gmail.com>wrote:
>>>>
>>>> Yay! :-)
>>>>>
>>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>>
>>>>> Aha :)
>>>>>>
>>>>>> java version "1.6.0_0"
>>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>>
>>>>>> Sig
>>>>>>
>>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>>
>>>>>>> We've had this before:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>>
>>>>>>
>>>>>>> The interesting part is that noone has implemented David's suggestion
>>>>>>> to date, and still the problem seems to have been resolved (or was
>>>>>>> it?)
>>>>>>>
>>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>>>>> which was not mature enough to run bug-free.
>>>>>>>
>>>>>>> Vassil
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch
>>>>>>> <hirsch.dick@gmail.com
>>>>>>>>
>>>>>>>
>>>>>> wrote:
>>>>>
>>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>>
>>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>
>>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>>>>
>>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up
>>>>>>>>> a
>>>>>>>>> fresh image.
>>>>>>>>>
>>>>>>>>> Then:
>>>>>>>>> apt-get install subversion
>>>>>>>>> apt-get install maven2
>>>>>>>>> apt-get install jetty
>>>>>>>>>
>>>>>>>>> Then:
>>>>>>>>> svn checkout
>>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>>
>>>>>>>>> Then fixing the two files.
>>>>>>>>>
>>>>>>>>> Then problem :)
>>>>>>>>>
>>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>>
>>>>>>>>> One never knows where I could have messed up, only mishap was that
>>>>>>>>> I
>>>>>>>>> lost contact with the server at some point during first mvn... so
>>>>>>>>> now
>>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>>
>>>>>>>>> Nope, exact same error.
>>>>>>>>>
>>>>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>>>>>>>>> after
>>>>>>>>> a
>>>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>>>>> clues.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>
>>>>>>>>>> RE plug-in: I remember.
>>>>>>>>>>
>>>>>>>>>> I think something else (Scala, lift, etc.) might have changed.
>>>>>>>>>> Has
>>>>>>>>>>
>>>>>>>>> anything
>>>>>>>>>
>>>>>>>>>> else changed in the environment?
>>>>>>>>>>
>>>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>>>>>>>>>>
>>>>>>>>> because
>>>>>
>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Then I get this:
>>>>>>>>>>>
>>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>> [INFO] null
>>>>>>>>>>>
>>>>>>>>>>> [INFO]
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>> [INFO] Trace
>>>>>>>>>>>
>>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>
>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>
>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>
>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>
>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>
>>>>>>
>>>>>>>>>>> BTW, it was you who suggested doing this last time, and then all
>>>>>>>>>>> was
>>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Ethan,
>>>>>>>>>>>>>
>>>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>>>>
>>>>>>>>>>>>> Prior to that:
>>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>>>
>>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>>>>>>>>>
>>>>>>>>>>>> non-zero
>>>>>>>>>
>>>>>>>>>> value:1
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>
>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>
>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>>
>>>>>>>>>>>> Method)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>
>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>
>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
>>>>>>>>>>>>>
>>>>>>>>>>>> line
>>>>>
>>>>>> returned non-zero value:1
>>>>>>>>>>>>>
>>>>>>>>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>
>>>>>> at
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>
>>>>>> ... 20 more
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Can you give the full stack trace - I don't think this once
>>>>>>>>>>>>>> goes
>>>>>>>>>>>>>>
>>>>>>>>>>>>> deep
>>>>>>>>>
>>>>>>>>>> enough for us to see if the error is in ESME or somewhere else?
>>>>>>>>>>>>>>
>>>>>>>>>>>>> And
>>>>>
>>>>>> exactly what command are you running that results in this error?
>>>>>>>>>>>>>>
>>>>>>>>>>>>> mvn
>>>>>>>>>
>>>>>>>>>> clean install?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>
>>>>>> Thanks Ethan,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> fresh
>>>>>>>>>
>>>>>>>>>> Amazon instance (same base image as the other live one), apt-get
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Added new api_test user in default.props and commented out
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>>
>>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> java.lang.StackOverflowError
>>>>>
>>>>>> [WARNING] at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>
>>>>>> [WARNING] at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>>
>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>
>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>
>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>
>>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>
>>>>>>>>>> ...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> S
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>>>>>>>>>>>>>>>> don't
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> have
>>>>>>>>>
>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting
>>>>>>>>>>>>>>>> for
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> the
>>>>>>>>>
>>>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Question if you have the time: If you add another line in
>>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> property
>>>>>>>>>>>
>>>>>>>>>>>> file and assign a second user as integration admin, does that
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> user
>>>>>>>>>
>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything
>>>>>>>>>>>>>>>>> but
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> root,
>>>>>>>>>
>>>>>>>>>> say
>>>>>>>>>>>
>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem
>>>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> all
>>>>>>>>>
>>>>>>>>>> browsers.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> (aws
>>>>>>>>>
>>>>>>>>>> is
>>>>>>>>>>>
>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>>>>> folders
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> and
>>>>>
>>>>>> found
>>>>>>>>>>>
>>>>>>>>>>>> nothing different (except the .svn stuff which I removed after
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> first
>>>>>>>>>>>
>>>>>>>>>>>> try).
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no
>>>>>>>>>>>>>>>>> diff
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> except
>>>>>>>>>>>
>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> .gitignore.
>>>>>
>>>>>>
>>>>>>>>>>>>>>>>> The server works though, and now I know how to get in there
>>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I
>>>>>
>>>>>> can
>>>>>>>>>>>
>>>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> and
>>>>>
>>>>>> fresh
>>>>>>>>>>>
>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>>>
>
Re: Wee error
Posted by Anne Kathrine Petterøe <yo...@gmail.com>.
Didn't Sig just change environment?
/Anne Kathrine
Sent from my iPhone
On 26. jan. 2010, at 16.09, Richard Hirsch <hi...@gmail.com>
wrote:
> That is true but I'm assuming that Sig has used OpenJDK since the he
> started
> integrating ESME.
>
> On Tue, Jan 26, 2010 at 4:05 PM, Anne Kathrine Petterøe
> <yo...@gmail.com>wrote:
>
>> I don't think anything has changed. Just that no one has used
>> openJDK since
>> then.
>>
>> /Anne Kathrine
>> Sent from my iPhone
>>
>>
>> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
>> wrote:
>>
>> But what has changed so that the problem now occurs?
>>>
>>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>>> <yo...@gmail.com>wrote:
>>>
>>> Yay! :-)
>>>>
>>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>>
>>>> Aha :)
>>>>>
>>>>> java version "1.6.0_0"
>>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1)
>>>>> (6b14-1.4.1-0ubuntu12)
>>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>>
>>>>> Sig
>>>>>
>>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>>
>>>>>> We've had this before:
>>>>>>
>>>>>>
>>>>>>
>>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>
>>>>>
>>>>>> The interesting part is that noone has implemented David's
>>>>>> suggestion
>>>>>> to date, and still the problem seems to have been resolved (or
>>>>>> was
>>>>>> it?)
>>>>>>
>>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>>> Debian/Ubuntu because package management decided to pull
>>>>>> openjdk-6,
>>>>>> which was not mature enough to run bug-free.
>>>>>>
>>>>>> Vassil
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>>>>>
>>>>>>
>>>>> wrote:
>>>>
>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after
>>>>>>>> starting up a
>>>>>>>> fresh image.
>>>>>>>>
>>>>>>>> Then:
>>>>>>>> apt-get install subversion
>>>>>>>> apt-get install maven2
>>>>>>>> apt-get install jetty
>>>>>>>>
>>>>>>>> Then:
>>>>>>>> svn checkout
>>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>>
>>>>>>>> Then fixing the two files.
>>>>>>>>
>>>>>>>> Then problem :)
>>>>>>>>
>>>>>>>> Now: rm -rf esme and started over
>>>>>>>>
>>>>>>>> One never knows where I could have messed up, only mishap was
>>>>>>>> that I
>>>>>>>> lost contact with the server at some point during first
>>>>>>>> mvn... so now
>>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>>
>>>>>>>> Nope, exact same error.
>>>>>>>>
>>>>>>>> Noticed that it starts saying compiling 49 packages, then
>>>>>>>> dies after
>>>>>>>> a
>>>>>>>> bit, and when trying again it says compiling 8 packages. No
>>>>>>>> other
>>>>>>>> clues.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>
>>>>>>>>> RE plug-in: I remember.
>>>>>>>>>
>>>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>>>>>> changed. Has
>>>>>>>>>
>>>>>>>> anything
>>>>>>>>
>>>>>>>>> else changed in the environment?
>>>>>>>>>
>>>>>>>>> It is all very strange. It is obviously a maven-related
>>>>>>>>> problem,
>>>>>>>>>
>>>>>>>> because
>>>>
>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>>
>>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Then I get this:
>>>>>>>>>>
>>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>>>>>> ---
>>>>>>>>>> ---
>>>>>>>>>> ---
>>>>>>>>>> ---
>>>>>>>>>> ------------------------------------------------------------
>>>>
>>>>> [INFO] null
>>>>>>>>>> [INFO]
>>>>>>>>>>
>>>>>>>>>> ---
>>>>>>>>>> ---
>>>>>>>>>> ---
>>>>>>>>>> ---
>>>>>>>>>> ------------------------------------------------------------
>>>>
>>>>> [INFO] Trace
>>>>>>>>>> java.lang.RuntimeException
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(
>>>>>>>> JavaScriptCompressor.java:299)
>>>>
>>>>> at
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse
>>>>>>>> (JavaScriptCompressor.java:335)
>>>>
>>>>> at
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>
>>>>>>>> (JavaScriptCompressor.java:532)
>>>>
>>>>> at
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile
>>>>>>>> (YuiCompressorMojo.java:178)
>>>>
>>>>> at
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir
>>>>>>>> (MojoSupport.java:151)
>>>>
>>>>>
>>>>>>>>>> BTW, it was you who suggested doing this last time, and
>>>>>>>>>> then all
>>>>>>>>>> was
>>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>
>>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Ethan,
>>>>>>>>>>>>
>>>>>>>>>>>> this is a completely new install so I'm using "mvn
>>>>>>>>>>>> jetty:run"
>>>>>>>>>>>>
>>>>>>>>>>>> Prior to that:
>>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>>
>>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>>> org.apache.maven.BuildFailureException: command line
>>>>>>>>>>>> returned
>>>>>>>>>>>>
>>>>>>>>>>> non-zero
>>>>>>>>
>>>>>>>>> value:1
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>>>>>>> DefaultLifecycleExecutor.java:579)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
>>>>>>>> DefaultLifecycleExecutor.java:499)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(
>>>>>>>> DefaultLifecycleExecutor.java:924)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(
>>>>>>>> DefaultLifecycleExecutor.java:767)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>>>>>>> DefaultLifecycleExecutor.java:529)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
>>>>>>>> DefaultLifecycleExecutor.java:512)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>>>>>>>> DefaultLifecycleExecutor.java:482)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>>>>>>>> DefaultLifecycleExecutor.java:330)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>>>>>>>> DefaultLifecycleExecutor.java:291)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
>>>>>>>> (DefaultLifecycleExecutor.java:142)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
>>>>>>>>>>> 336)
>>>>>>>>
>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>
>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>>
>>>>>>>>>>> Method)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke
>>>>>>>> (NativeMethodAccessorImpl.java:57)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke
>>>>>>>> (DelegatingMethodAccessorImpl.java:43)
>>>>
>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>> org.codehaus.classworlds.Launcher.launchEnhanced
>>>>>>>>>>>> (Launcher.java:315)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode
>>>>>>>>>>>> (Launcher.java:430)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>
>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
>>>>>>>>>>>>
>>>>>>>>>>> line
>>>>
>>>>> returned non-zero value:1
>>>>>>>>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile
>>>>>>>> (ScalaCompilerSupport.java:124)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute
>>>>>>>> (ScalaCompilerSupport.java:54)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute
>>>>>>>> (ScalaMojoSupport.java:208)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute
>>>>>>>> (ScalaCompilerSupport.java:29)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute
>>>>>>>> (ScalaTestCompileMojo.java:58)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo
>>>>>>>> (DefaultPluginManager.java:451)
>>>>
>>>>> at
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>>>>>>> DefaultLifecycleExecutor.java:558)
>>>>
>>>>> ... 20 more
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you give the full stack trace - I don't think this
>>>>>>>>>>>>> once goes
>>>>>>>>>>>>>
>>>>>>>>>>>> deep
>>>>>>>>
>>>>>>>>> enough for us to see if the error is in ESME or somewhere
>>>>>>>>> else?
>>>>>>>>>>>>>
>>>>>>>>>>>> And
>>>>
>>>>> exactly what command are you running that results in this error?
>>>>>>>>>>>>>
>>>>>>>>>>>> mvn
>>>>>>>>
>>>>>>>>> clean install?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>
>>>>> Thanks Ethan,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> planned to start over to test all fresh, so I created a
>>>>>>>>>>>>>> new and
>>>>>>>>>>>>>>
>>>>>>>>>>>>> fresh
>>>>>>>>
>>>>>>>>> Amazon instance (same base image as the other live one), apt-
>>>>>>>>> get
>>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Added new api_test user in default.props and commented
>>>>>>>>>>>>>> out the
>>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>>>
>>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>>
>>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>>>>>>>>
>>>>>>>>>>>>> java.lang.StackOverflowError
>>>>
>>>>> [WARNING] at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner
>>>>>>>>>>>> (Symbols.scala:1563)
>>>>
>>>>> [WARNING] at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>>>>>> (Symbols.scala:940)
>>>>>>>>
>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>>>>>> (Symbols.scala:942)
>>>>>>>>
>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>>>>>> (Symbols.scala:942)
>>>>>>>>
>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>>>>>> (Symbols.scala:942)
>>>>>>>>
>>>>>>>>> [WARNING] at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>>>>>>>> (Symbols.scala:942)
>>>>>>>>
>>>>>>>>> ...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> S
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks for doing all that detective work.
>>>>>>>>>>>>>>> Unfortunately I
>>>>>>>>>>>>>>> don't
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> have
>>>>>>>>
>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>>>>>>>>>>>> setting for
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> the
>>>>>>>>
>>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Question if you have the time: If you add another line
>>>>>>>>>>>>>>> in the
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> property
>>>>>>>>>>
>>>>>>>>>>> file and assign a second user as integration admin, does
>>>>>>>>>>> that
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> user
>>>>>>>>
>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <sig@rinde.com
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>>>>>>>>>>>>> anything but
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> root,
>>>>>>>>
>>>>>>>>> say
>>>>>>>>>>
>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
>>>>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> all
>>>>>>>>
>>>>>>>>> browsers.
>>>>>>>>>>>>
>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
>>>>>>>>>>>>> instance.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> (aws
>>>>>>>>
>>>>>>>>> is
>>>>>>>>>>
>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>>>> folders
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> and
>>>>
>>>>> found
>>>>>>>>>>
>>>>>>>>>>> nothing different (except the .svn stuff which I removed
>>>>>>>>>>> after
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> first
>>>>>>>>>>
>>>>>>>>>>> try).
>>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found
>>>>>>>>>>>>>>>> no diff
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> except
>>>>>>>>>>
>>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> .gitignore.
>>>>
>>>>>
>>>>>>>>>>>>>>>> The server works though, and now I know how to get in
>>>>>>>>>>>>>>>> there
>>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I
>>>>
>>>>> can
>>>>>>>>>>
>>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> and
>>>>
>>>>> fresh
>>>>>>>>>>
>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
That is true but I'm assuming that Sig has used OpenJDK since the he started
integrating ESME.
On Tue, Jan 26, 2010 at 4:05 PM, Anne Kathrine Petterøe
<yo...@gmail.com>wrote:
> I don't think anything has changed. Just that no one has used openJDK since
> then.
>
> /Anne Kathrine
> Sent from my iPhone
>
>
> On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com> wrote:
>
> But what has changed so that the problem now occurs?
>>
>> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
>> <yo...@gmail.com>wrote:
>>
>> Yay! :-)
>>>
>>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>>
>>> Aha :)
>>>>
>>>> java version "1.6.0_0"
>>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>>
>>>> Sig
>>>>
>>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>>
>>>>> We've had this before:
>>>>>
>>>>>
>>>>>
>>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>
>>>>
>>>>> The interesting part is that noone has implemented David's suggestion
>>>>> to date, and still the problem seems to have been resolved (or was
>>>>> it?)
>>>>>
>>>>> BTW what JDK are you using? I've had my share of problems on
>>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>>> which was not mature enough to run bug-free.
>>>>>
>>>>> Vassil
>>>>>
>>>>>
>>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>>> >
>>>>>
>>>> wrote:
>>>
>>>> I'm going to try it locally to see if it works on my laptop
>>>>>>
>>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>
>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up a
>>>>>>> fresh image.
>>>>>>>
>>>>>>> Then:
>>>>>>> apt-get install subversion
>>>>>>> apt-get install maven2
>>>>>>> apt-get install jetty
>>>>>>>
>>>>>>> Then:
>>>>>>> svn checkout
>>>>>>> http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>>
>>>>>>> Then fixing the two files.
>>>>>>>
>>>>>>> Then problem :)
>>>>>>>
>>>>>>> Now: rm -rf esme and started over
>>>>>>>
>>>>>>> One never knows where I could have messed up, only mishap was that I
>>>>>>> lost contact with the server at some point during first mvn... so now
>>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>>
>>>>>>> Nope, exact same error.
>>>>>>>
>>>>>>> Noticed that it starts saying compiling 49 packages, then dies after
>>>>>>> a
>>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>>> clues.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>
>>>>>>>> RE plug-in: I remember.
>>>>>>>>
>>>>>>>> I think something else (Scala, lift, etc.) might have changed. Has
>>>>>>>>
>>>>>>> anything
>>>>>>>
>>>>>>>> else changed in the environment?
>>>>>>>>
>>>>>>>> It is all very strange. It is obviously a maven-related problem,
>>>>>>>>
>>>>>>> because
>>>
>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>>
>>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>
>>>>>>>> Then I get this:
>>>>>>>>>
>>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>>> [INFO]
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>
>>>> [INFO] null
>>>>>>>>> [INFO]
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------
>>>
>>>> [INFO] Trace
>>>>>>>>> java.lang.RuntimeException
>>>>>>>>> at
>>>>>>>>>
>>>>>>>>>
>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>
>>>> at
>>>>>>>>>
>>>>>>>>>
>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>
>>>> at
>>>>>>>>>
>>>>>>>>>
>>>>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>
>>>> at
>>>>>>>>>
>>>>>>>>>
>>>>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>
>>>> at
>>>>>>>>>
>>>>>>>>>
>>>>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>
>>>>
>>>>>>>>> BTW, it was you who suggested doing this last time, and then all
>>>>>>>>> was
>>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>
>>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Ethan,
>>>>>>>>>>>
>>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>>
>>>>>>>>>>> Prior to that:
>>>>>>>>>>> 1. svn the full esme
>>>>>>>>>>> 2. add line to default.props
>>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>>
>>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Trace
>>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>>>>>>>
>>>>>>>>>> non-zero
>>>>>>>
>>>>>>>> value:1
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>
>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>
>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>>>>>>>>
>>>>>>>>>> Method)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>
>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
>>>>>>>>>>>
>>>>>>>>>> line
>>>
>>>> returned non-zero value:1
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>>>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>
>>>> at
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>
>>>> ... 20 more
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>
>>>>>>>>>>>> Can you give the full stack trace - I don't think this once goes
>>>>>>>>>>>>
>>>>>>>>>>> deep
>>>>>>>
>>>>>>>> enough for us to see if the error is in ESME or somewhere else?
>>>>>>>>>>>>
>>>>>>>>>>> And
>>>
>>>> exactly what command are you running that results in this error?
>>>>>>>>>>>>
>>>>>>>>>>> mvn
>>>>>>>
>>>>>>>> clean install?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Ethan
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>
>>>> Thanks Ethan,
>>>>>>>>>>>>>
>>>>>>>>>>>>> planned to start over to test all fresh, so I created a new and
>>>>>>>>>>>>>
>>>>>>>>>>>> fresh
>>>>>>>
>>>>>>>> Amazon instance (same base image as the other live one), apt-get
>>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>>
>>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Added new api_test user in default.props and commented out the
>>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>>
>>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>>>>>
>>>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>
>>>>>>>>>>>> [WARNING] Exception in thread "main"
>>>>>>>>>>>>>
>>>>>>>>>>>> java.lang.StackOverflowError
>>>
>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>
>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>
>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>
>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>
>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>
>>>>>>>> [WARNING] at
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>
>>>>>>>> ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>>
>>>>>>>>>>>>> S
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I
>>>>>>>>>>>>>> don't
>>>>>>>>>>>>>>
>>>>>>>>>>>>> have
>>>>>>>
>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I wonder if there is some place that I pull in the setting for
>>>>>>>>>>>>>>
>>>>>>>>>>>>> the
>>>>>>>
>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Question if you have the time: If you add another line in the
>>>>>>>>>>>>>>
>>>>>>>>>>>>> property
>>>>>>>>>
>>>>>>>>>> file and assign a second user as integration admin, does that
>>>>>>>>>>>>>>
>>>>>>>>>>>>> user
>>>>>>>
>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>
>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>>> 2. If I log on as another user, then log out in anything but
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> root,
>>>>>>>
>>>>>>>> say
>>>>>>>>>
>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem
>>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> all
>>>>>>>
>>>>>>>> browsers.
>>>>>>>>>>>
>>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> (aws
>>>>>>>
>>>>>>>> is
>>>>>>>>>
>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp folders
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> and
>>>
>>>> found
>>>>>>>>>
>>>>>>>>>> nothing different (except the .svn stuff which I removed after
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> first
>>>>>>>>>
>>>>>>>>>> try).
>>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found no diff
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> except
>>>>>>>>>
>>>>>>>>>> .svn folders and that esme on aws held a file named
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> .gitignore.
>>>
>>>>
>>>>>>>>>>>>>>> The server works though, and now I know how to get in there
>>>>>>>>>>>>>>> so
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I
>>>
>>>> can
>>>>>>>>>
>>>>>>>>>> live with problem and assume it'll go away with a later new
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> and
>>>
>>>> fresh
>>>>>>>>>
>>>>>>>>>> install... :)
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>>
Re: Wee error
Posted by Anne Kathrine Petterøe <yo...@gmail.com>.
I don't think anything has changed. Just that no one has used openJDK
since then.
/Anne Kathrine
Sent from my iPhone
On 26. jan. 2010, at 16.01, Richard Hirsch <hi...@gmail.com>
wrote:
> But what has changed so that the problem now occurs?
>
> On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
> <yo...@gmail.com>wrote:
>
>> Yay! :-)
>>
>> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>>
>>> Aha :)
>>>
>>> java version "1.6.0_0"
>>> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
>>> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>>>
>>> Sig
>>>
>>> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>>>> We've had this before:
>>>>
>>>>
>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>>>
>>>> The interesting part is that noone has implemented David's
>>>> suggestion
>>>> to date, and still the problem seems to have been resolved (or was
>>>> it?)
>>>>
>>>> BTW what JDK are you using? I've had my share of problems on
>>>> Debian/Ubuntu because package management decided to pull openjdk-6,
>>>> which was not mature enough to run bug-free.
>>>>
>>>> Vassil
>>>>
>>>>
>>>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hirsch.dick@gmail.com
>>>> >
>> wrote:
>>>>> I'm going to try it locally to see if it works on my laptop
>>>>>
>>>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>
>>>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>>>> Ubuntu 9.04 following apt-get update and upgrade after starting
>>>>>> up a
>>>>>> fresh image.
>>>>>>
>>>>>> Then:
>>>>>> apt-get install subversion
>>>>>> apt-get install maven2
>>>>>> apt-get install jetty
>>>>>>
>>>>>> Then:
>>>>>> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunkesme
>>>>>>
>>>>>> Then fixing the two files.
>>>>>>
>>>>>> Then problem :)
>>>>>>
>>>>>> Now: rm -rf esme and started over
>>>>>>
>>>>>> One never knows where I could have messed up, only mishap was
>>>>>> that I
>>>>>> lost contact with the server at some point during first mvn...
>>>>>> so now
>>>>>> I did & and logged out leaving it alone... lets see now:
>>>>>>
>>>>>> Nope, exact same error.
>>>>>>
>>>>>> Noticed that it starts saying compiling 49 packages, then dies
>>>>>> after a
>>>>>> bit, and when trying again it says compiling 8 packages. No other
>>>>>> clues.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>> RE plug-in: I remember.
>>>>>>>
>>>>>>> I think something else (Scala, lift, etc.) might have
>>>>>>> changed. Has
>>>>>> anything
>>>>>>> else changed in the environment?
>>>>>>>
>>>>>>> It is all very strange. It is obviously a maven-related problem,
>> because
>>>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Then I get this:
>>>>>>>>
>>>>>>>> [ERROR] FATAL ERROR
>>>>>>>> [INFO]
>>>>>>>>
>> ---
>> ---------------------------------------------------------------------
>>>>>>>> [INFO] null
>>>>>>>> [INFO]
>>>>>>>>
>> ---
>> ---------------------------------------------------------------------
>>>>>>>> [INFO] Trace
>>>>>>>> java.lang.RuntimeException
>>>>>>>> at
>>>>>>>>
>>>>>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(
>> JavaScriptCompressor.java:299)
>>>>>>>> at
>>>>>>>>
>>>>>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse
>> (JavaScriptCompressor.java:335)
>>>>>>>> at
>>>>>>>>
>>>>>>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>
>> (JavaScriptCompressor.java:532)
>>>>>>>> at
>>>>>>>>
>>>>>>
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile
>> (YuiCompressorMojo.java:178)
>>>>>>>> at
>>>>>>>>
>>>>>>
>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir
>> (MojoSupport.java:151)
>>>>>>>>
>>>>>>>> BTW, it was you who suggested doing this last time, and then
>>>>>>>> all was
>>>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>>>
>>>>>>>>
>>>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>>>
>>>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Ethan,
>>>>>>>>>>
>>>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>>>
>>>>>>>>>> Prior to that:
>>>>>>>>>> 1. svn the full esme
>>>>>>>>>> 2. add line to default.props
>>>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>>>
>>>>>>>>>> using -e gave this at the end:
>>>>>>>>>>
>>>>>>>>>> [INFO] Trace
>>>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>>>> non-zero
>>>>>>>>>> value:1
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>> (DefaultLifecycleExecutor.java:579)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(
>> DefaultLifecycleExecutor.java:499)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(
>> DefaultLifecycleExecutor.java:924)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle
>> (DefaultLifecycleExecutor.java:767)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>> (DefaultLifecycleExecutor.java:529)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
>> DefaultLifecycleExecutor.java:512)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
>> (DefaultLifecycleExecutor.java:482)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(
>> DefaultLifecycleExecutor.java:330)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>> DefaultLifecycleExecutor.java:291)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
>> (DefaultLifecycleExecutor.java:142)
>>>>>>>>>> at
>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>>> at
>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:
>>>>>>>>>> 287)
>>>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.java:57)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl.java:43)
>>>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>>>> at
>>>>>>>>>>
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>>>> at
>> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>>>> at
>>>>>>>>>>
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>>>> at
>> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException:
>>>>>>>>>> command
>> line
>>>>>>>>>> returned non-zero value:1
>>>>>>>>>> at
>> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.scala_tools.maven.ScalaCompilerSupport.compile
>> (ScalaCompilerSupport.java:124)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute
>> (ScalaCompilerSupport.java:54)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.scala_tools.maven.ScalaMojoSupport.execute
>> (ScalaMojoSupport.java:208)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.scala_tools.maven.ScalaCompilerSupport.execute
>> (ScalaCompilerSupport.java:29)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute
>> (ScalaTestCompileMojo.java:58)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo
>> (DefaultPluginManager.java:451)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>>>
>>>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
>> (DefaultLifecycleExecutor.java:558)
>>>>>>>>>> ... 20 more
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>
>>>>>>>>>>> Can you give the full stack trace - I don't think this
>>>>>>>>>>> once goes
>>>>>> deep
>>>>>>>>>>> enough for us to see if the error is in ESME or somewhere
>>>>>>>>>>> else?
>> And
>>>>>>>>>>> exactly what command are you running that results in this
>>>>>>>>>>> error?
>>>>>> mvn
>>>>>>>>>>> clean install?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Ethan
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
>> wrote:
>>>>>>>>>>>> Thanks Ethan,
>>>>>>>>>>>>
>>>>>>>>>>>> planned to start over to test all fresh, so I created a
>>>>>>>>>>>> new and
>>>>>> fresh
>>>>>>>>>>>> Amazon instance (same base image as the other live one),
>>>>>>>>>>>> apt-get
>>>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>>>
>>>>>>>>>>>> New svn from esme.
>>>>>>>>>>>>
>>>>>>>>>>>> Added new api_test user in default.props and commented
>>>>>>>>>>>> out the
>>>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>>>
>>>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>>>
>>>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>>>> [WARNING] Exception in thread "main"
>> java.lang.StackOverflowError
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>
>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>> (Symbols.scala:940)
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>> (Symbols.scala:942)
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>> (Symbols.scala:942)
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>> (Symbols.scala:942)
>>>>>>>>>>>> [WARNING] at
>>>>>>>>>>
>>>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass
>>>>>> (Symbols.scala:942)
>>>>>>>>>>>> ...
>>>>>>>>>>>>
>>>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>>>
>>>>>>>>>>>> S
>>>>>>>>>>>>
>>>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately
>>>>>>>>>>>>> I don't
>>>>>> have
>>>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>>>
>>>>>>>>>>>>> I wonder if there is some place that I pull in the
>>>>>>>>>>>>> setting for
>>>>>> the
>>>>>>>>>>>>> integration test user other than in the API2 code.
>>>>>>>>>>>>> Definitely
>>>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Question if you have the time: If you add another line
>>>>>>>>>>>>> in the
>>>>>>>> property
>>>>>>>>>>>>> file and assign a second user as integration admin, does
>>>>>>>>>>>>> that
>>>>>> user
>>>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Ethan
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>>>> wrote:
>>>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>>>> 2. If I log on as another user, then log out in
>>>>>>>>>>>>>> anything but
>>>>>> root,
>>>>>>>> say
>>>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>>>> 3. If I log out and log on as api_test in root same
>>>>>>>>>>>>>> problem on
>>>>>> all
>>>>>>>>>> browsers.
>>>>>>>>>>>>>> 4. This only for the aws instance, not for my local
>>>>>>>>>>>>>> instance.
>>>>>> (aws
>>>>>>>> is
>>>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp
>>>>>>>>>>>>>> folders
>> and
>>>>>>>> found
>>>>>>>>>>>>>> nothing different (except the .svn stuff which I
>>>>>>>>>>>>>> removed after
>>>>>>>> first
>>>>>>>>>>>>>> try).
>>>>>>>>>>>>>> 6. Did a diff between full esme directories and found
>>>>>>>>>>>>>> no diff
>>>>>>>> except
>>>>>>>>>>>>>> .svn folders and that esme on aws held a file named
>> .gitignore.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The server works though, and now I know how to get in
>>>>>>>>>>>>>> there so
>> I
>>>>>>>> can
>>>>>>>>>>>>>> live with problem and assume it'll go away with a later
>>>>>>>>>>>>>> new
>> and
>>>>>>>> fresh
>>>>>>>>>>>>>> install... :)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
But what has changed so that the problem now occurs?
On Tue, Jan 26, 2010 at 3:52 PM, Anne Kathrine Petterøe
<yo...@gmail.com>wrote:
> Yay! :-)
>
> On 26. jan. 2010, at 15.50, Sig Rinde wrote:
>
> > Aha :)
> >
> > java version "1.6.0_0"
> > OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
> > OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
> >
> > Sig
> >
> > 2010/1/26 Vassil Dichev <vd...@apache.org>:
> >> We've had this before:
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
> >>
> >> The interesting part is that noone has implemented David's suggestion
> >> to date, and still the problem seems to have been resolved (or was
> >> it?)
> >>
> >> BTW what JDK are you using? I've had my share of problems on
> >> Debian/Ubuntu because package management decided to pull openjdk-6,
> >> which was not mature enough to run bug-free.
> >>
> >> Vassil
> >>
> >>
> >> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hi...@gmail.com>
> wrote:
> >>> I'm going to try it locally to see if it works on my laptop
> >>>
> >>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
> >>>
> >>>> Nothing I can see has changed, this one is absolutely up-to-date
> >>>> Ubuntu 9.04 following apt-get update and upgrade after starting up a
> >>>> fresh image.
> >>>>
> >>>> Then:
> >>>> apt-get install subversion
> >>>> apt-get install maven2
> >>>> apt-get install jetty
> >>>>
> >>>> Then:
> >>>> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunkesme
> >>>>
> >>>> Then fixing the two files.
> >>>>
> >>>> Then problem :)
> >>>>
> >>>> Now: rm -rf esme and started over
> >>>>
> >>>> One never knows where I could have messed up, only mishap was that I
> >>>> lost contact with the server at some point during first mvn... so now
> >>>> I did & and logged out leaving it alone... lets see now:
> >>>>
> >>>> Nope, exact same error.
> >>>>
> >>>> Noticed that it starts saying compiling 49 packages, then dies after a
> >>>> bit, and when trying again it says compiling 8 packages. No other
> >>>> clues.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>> RE plug-in: I remember.
> >>>>>
> >>>>> I think something else (Scala, lift, etc.) might have changed. Has
> >>>> anything
> >>>>> else changed in the environment?
> >>>>>
> >>>>> It is all very strange. It is obviously a maven-related problem,
> because
> >>>>> ESME's code hasn't really changed at all in the last few weeks.
> >>>>>
> >>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
> >>>>>
> >>>>>> Then I get this:
> >>>>>>
> >>>>>> [ERROR] FATAL ERROR
> >>>>>> [INFO]
> >>>>>>
> ------------------------------------------------------------------------
> >>>>>> [INFO] null
> >>>>>> [INFO]
> >>>>>>
> ------------------------------------------------------------------------
> >>>>>> [INFO] Trace
> >>>>>> java.lang.RuntimeException
> >>>>>> at
> >>>>>>
> >>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> >>>>>> at
> >>>>>>
> >>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> >>>>>> at
> >>>>>>
> >>>>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> >>>>>> at
> >>>>>>
> >>>>
> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> >>>>>> at
> >>>>>>
> >>>>
> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
> >>>>>>
> >>>>>> BTW, it was you who suggested doing this last time, and then all was
> >>>>>> ok for basically same setup (that was Jan 5th) :)
> >>>>>>
> >>>>>>
> >>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >>>>>>> what happens if you don't comment out the plug-in
> >>>>>>>
> >>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
> >>>>>>>
> >>>>>>>> Ethan,
> >>>>>>>>
> >>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
> >>>>>>>>
> >>>>>>>> Prior to that:
> >>>>>>>> 1. svn the full esme
> >>>>>>>> 2. add line to default.props
> >>>>>>>> 3. comment out plugin in pom.xml
> >>>>>>>>
> >>>>>>>> using -e gave this at the end:
> >>>>>>>>
> >>>>>>>> [INFO] Trace
> >>>>>>>> org.apache.maven.BuildFailureException: command line returned
> >>>> non-zero
> >>>>>>>> value:1
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> >>>>>>>> at
> >>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> >>>>>>>> at
> >>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> >>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> >>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
> >>>>>>>> at
> >>>>>>>>
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>>>>>>> at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >>>>>>>> at
> >>>>>>>>
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>>>>>>> at
> org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command
> line
> >>>>>>>> returned non-zero value:1
> >>>>>>>> at
> org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> >>>>>>>> at
> >>>>>>>>
> >>>>>>
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> >>>>>>>> ... 20 more
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> >>>>>>>>> Hi Sig,
> >>>>>>>>>
> >>>>>>>>> Can you give the full stack trace - I don't think this once goes
> >>>> deep
> >>>>>>>>> enough for us to see if the error is in ESME or somewhere else?
> And
> >>>>>>>>> exactly what command are you running that results in this error?
> >>>> mvn
> >>>>>>>>> clean install?
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> Ethan
> >>>>>>>>>
> >>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com>
> wrote:
> >>>>>>>>>> Thanks Ethan,
> >>>>>>>>>>
> >>>>>>>>>> planned to start over to test all fresh, so I created a new and
> >>>> fresh
> >>>>>>>>>> Amazon instance (same base image as the other live one), apt-get
> >>>>>>>>>> upgrade etc, now running 9.04 all latest.
> >>>>>>>>>>
> >>>>>>>>>> New svn from esme.
> >>>>>>>>>>
> >>>>>>>>>> Added new api_test user in default.props and commented out the
> >>>>>>>>>> compression plug-in in pom.xml.
> >>>>>>>>>>
> >>>>>>>>>> Then fired it up and got this error:
> >>>>>>>>>>
> >>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
> >>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
> >>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
> >>>>>>>>>> [INFO] Compiling 8 source files to
> >>>>>>>> /home/files/esme/server/target/test-classes
> >>>>>>>>>> [WARNING] Exception in thread "main"
> java.lang.StackOverflowError
> >>>>>>>>>> [WARNING] at
> >>>>>>>>
> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >>>>>>>>>> [WARNING] at
> >>>>>>>>
> >>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >>>>>>>>>> [WARNING] at
> >>>>>>>>
> >>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>> [WARNING] at
> >>>>>>>>
> >>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>> [WARNING] at
> >>>>>>>>
> >>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>> [WARNING] at
> >>>>>>>>
> >>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >>>>>>>>>> ...
> >>>>>>>>>>
> >>>>>>>>>> So what did I forget this time :)
> >>>>>>>>>>
> >>>>>>>>>> S
> >>>>>>>>>>
> >>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >>>>>>>>>>> Hi Sig,
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I don't
> >>>> have
> >>>>>>>>>>> an Ubuntu box to test on. :-(
> >>>>>>>>>>>
> >>>>>>>>>>> I wonder if there is some place that I pull in the setting for
> >>>> the
> >>>>>>>>>>> integration test user other than in the API2 code. Definitely
> >>>>>>>>>>> possible. I will try to look in to it.
> >>>>>>>>>>>
> >>>>>>>>>>> Question if you have the time: If you add another line in the
> >>>>>> property
> >>>>>>>>>>> file and assign a second user as integration admin, does that
> >>>> user
> >>>>>>>>>>> stop working in the web interface as well?
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>> Ethan
> >>>>>>>>>>>
> >>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
> >>>> wrote:
> >>>>>>>>>>>> Morning creative sleuth work:
> >>>>>>>>>>>>
> >>>>>>>>>>>> 1. Sorry, no difference between browsers:
> >>>>>>>>>>>> 2. If I log on as another user, then log out in anything but
> >>>> root,
> >>>>>> say
> >>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
> >>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem on
> >>>> all
> >>>>>>>> browsers.
> >>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
> >>>> (aws
> >>>>>> is
> >>>>>>>>>>>> ubuntu, local is OS X)
> >>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp folders
> and
> >>>>>> found
> >>>>>>>>>>>> nothing different (except the .svn stuff which I removed after
> >>>>>> first
> >>>>>>>>>>>> try).
> >>>>>>>>>>>> 6. Did a diff between full esme directories and found no diff
> >>>>>> except
> >>>>>>>>>>>> .svn folders and that esme on aws held a file named
> .gitignore.
> >>>>>>>>>>>>
> >>>>>>>>>>>> The server works though, and now I know how to get in there so
> I
> >>>>>> can
> >>>>>>>>>>>> live with problem and assume it'll go away with a later new
> and
> >>>>>> fresh
> >>>>>>>>>>>> install... :)
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
> >>>>>>>>>>>>> might be a lift-specific problem with those browsers.
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
Re: Wee error
Posted by Anne Kathrine Petterøe <yo...@gmail.com>.
Yay! :-)
On 26. jan. 2010, at 15.50, Sig Rinde wrote:
> Aha :)
>
> java version "1.6.0_0"
> OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
> OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
>
> Sig
>
> 2010/1/26 Vassil Dichev <vd...@apache.org>:
>> We've had this before:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>>
>> The interesting part is that noone has implemented David's suggestion
>> to date, and still the problem seems to have been resolved (or was
>> it?)
>>
>> BTW what JDK are you using? I've had my share of problems on
>> Debian/Ubuntu because package management decided to pull openjdk-6,
>> which was not mature enough to run bug-free.
>>
>> Vassil
>>
>>
>> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> I'm going to try it locally to see if it works on my laptop
>>>
>>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>>
>>>> Nothing I can see has changed, this one is absolutely up-to-date
>>>> Ubuntu 9.04 following apt-get update and upgrade after starting up a
>>>> fresh image.
>>>>
>>>> Then:
>>>> apt-get install subversion
>>>> apt-get install maven2
>>>> apt-get install jetty
>>>>
>>>> Then:
>>>> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>>
>>>> Then fixing the two files.
>>>>
>>>> Then problem :)
>>>>
>>>> Now: rm -rf esme and started over
>>>>
>>>> One never knows where I could have messed up, only mishap was that I
>>>> lost contact with the server at some point during first mvn... so now
>>>> I did & and logged out leaving it alone... lets see now:
>>>>
>>>> Nope, exact same error.
>>>>
>>>> Noticed that it starts saying compiling 49 packages, then dies after a
>>>> bit, and when trying again it says compiling 8 packages. No other
>>>> clues.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>> RE plug-in: I remember.
>>>>>
>>>>> I think something else (Scala, lift, etc.) might have changed. Has
>>>> anything
>>>>> else changed in the environment?
>>>>>
>>>>> It is all very strange. It is obviously a maven-related problem, because
>>>>> ESME's code hasn't really changed at all in the last few weeks.
>>>>>
>>>>> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>
>>>>>> Then I get this:
>>>>>>
>>>>>> [ERROR] FATAL ERROR
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] null
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] Trace
>>>>>> java.lang.RuntimeException
>>>>>> at
>>>>>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>>>>> at
>>>>>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>>>>> at
>>>>>>
>>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>>>>> at
>>>>>>
>>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>>>>> at
>>>>>>
>>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>>>>>
>>>>>> BTW, it was you who suggested doing this last time, and then all was
>>>>>> ok for basically same setup (that was Jan 5th) :)
>>>>>>
>>>>>>
>>>>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>>>>>> what happens if you don't comment out the plug-in
>>>>>>>
>>>>>>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>
>>>>>>>> Ethan,
>>>>>>>>
>>>>>>>> this is a completely new install so I'm using "mvn jetty:run"
>>>>>>>>
>>>>>>>> Prior to that:
>>>>>>>> 1. svn the full esme
>>>>>>>> 2. add line to default.props
>>>>>>>> 3. comment out plugin in pom.xml
>>>>>>>>
>>>>>>>> using -e gave this at the end:
>>>>>>>>
>>>>>>>> [INFO] Trace
>>>>>>>> org.apache.maven.BuildFailureException: command line returned
>>>> non-zero
>>>>>>>> value:1
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>>>>> at
>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>> at
>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>>>>>> at
>>>>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>>>>>>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>>>>>>> at
>>>>>>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>>>>>>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>>>>>> Caused by: org.apache.maven.plugin.MojoFailureException: command line
>>>>>>>> returned non-zero value:1
>>>>>>>> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>>> at
>>>>>>>>
>>>>>>
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>> ... 20 more
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>>>>>>>> Hi Sig,
>>>>>>>>>
>>>>>>>>> Can you give the full stack trace - I don't think this once goes
>>>> deep
>>>>>>>>> enough for us to see if the error is in ESME or somewhere else? And
>>>>>>>>> exactly what command are you running that results in this error?
>>>> mvn
>>>>>>>>> clean install?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Ethan
>>>>>>>>>
>>>>>>>>> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
>>>>>>>>>> Thanks Ethan,
>>>>>>>>>>
>>>>>>>>>> planned to start over to test all fresh, so I created a new and
>>>> fresh
>>>>>>>>>> Amazon instance (same base image as the other live one), apt-get
>>>>>>>>>> upgrade etc, now running 9.04 all latest.
>>>>>>>>>>
>>>>>>>>>> New svn from esme.
>>>>>>>>>>
>>>>>>>>>> Added new api_test user in default.props and commented out the
>>>>>>>>>> compression plug-in in pom.xml.
>>>>>>>>>>
>>>>>>>>>> Then fired it up and got this error:
>>>>>>>>>>
>>>>>>>>>> [INFO] suggestion: remove the scalaVersion from pom.xml
>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala
>>>>>>>>>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>>>>>>>>> [INFO] Compiling 8 source files to
>>>>>>>> /home/files/esme/server/target/test-classes
>>>>>>>>>> [WARNING] Exception in thread "main" java.lang.StackOverflowError
>>>>>>>>>> [WARNING] at
>>>>>>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>>>>>>>>> [WARNING] at
>>>>>>>>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>>>>>>>>> [WARNING] at
>>>>>>>>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>> [WARNING] at
>>>>>>>>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>> [WARNING] at
>>>>>>>>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>> [WARNING] at
>>>>>>>>
>>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>>>>>>>>> ...
>>>>>>>>>>
>>>>>>>>>> So what did I forget this time :)
>>>>>>>>>>
>>>>>>>>>> S
>>>>>>>>>>
>>>>>>>>>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>>>>>>>>>> Hi Sig,
>>>>>>>>>>>
>>>>>>>>>>> Thanks for doing all that detective work. Unfortunately I don't
>>>> have
>>>>>>>>>>> an Ubuntu box to test on. :-(
>>>>>>>>>>>
>>>>>>>>>>> I wonder if there is some place that I pull in the setting for
>>>> the
>>>>>>>>>>> integration test user other than in the API2 code. Definitely
>>>>>>>>>>> possible. I will try to look in to it.
>>>>>>>>>>>
>>>>>>>>>>> Question if you have the time: If you add another line in the
>>>>>> property
>>>>>>>>>>> file and assign a second user as integration admin, does that
>>>> user
>>>>>>>>>>> stop working in the web interface as well?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Ethan
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>>> wrote:
>>>>>>>>>>>> Morning creative sleuth work:
>>>>>>>>>>>>
>>>>>>>>>>>> 1. Sorry, no difference between browsers:
>>>>>>>>>>>> 2. If I log on as another user, then log out in anything but
>>>> root,
>>>>>> say
>>>>>>>>>>>> "hosturl:8080/auth_view/" then no problem.
>>>>>>>>>>>> 3. If I log out and log on as api_test in root same problem on
>>>> all
>>>>>>>> browsers.
>>>>>>>>>>>> 4. This only for the aws instance, not for my local instance.
>>>> (aws
>>>>>> is
>>>>>>>>>>>> ubuntu, local is OS X)
>>>>>>>>>>>> 5. Did a diff between the two (local and aws) webapp folders and
>>>>>> found
>>>>>>>>>>>> nothing different (except the .svn stuff which I removed after
>>>>>> first
>>>>>>>>>>>> try).
>>>>>>>>>>>> 6. Did a diff between full esme directories and found no diff
>>>>>> except
>>>>>>>>>>>> .svn folders and that esme on aws held a file named .gitignore.
>>>>>>>>>>>>
>>>>>>>>>>>> The server works though, and now I know how to get in there so I
>>>>>> can
>>>>>>>>>>>> live with problem and assume it'll go away with a later new and
>>>>>> fresh
>>>>>>>>>>>> install... :)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>>>>>>>>>> might be a lift-specific problem with those browsers.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Aha :)
java version "1.6.0_0"
OpenJDK Runtime Environment (IcedTea6 1.4.1) (6b14-1.4.1-0ubuntu12)
OpenJDK Client VM (build 14.0-b08, mixed mode, sharing)
Sig
2010/1/26 Vassil Dichev <vd...@apache.org>:
> We've had this before:
>
> http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
>
> The interesting part is that noone has implemented David's suggestion
> to date, and still the problem seems to have been resolved (or was
> it?)
>
> BTW what JDK are you using? I've had my share of problems on
> Debian/Ubuntu because package management decided to pull openjdk-6,
> which was not mature enough to run bug-free.
>
> Vassil
>
>
> On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> I'm going to try it locally to see if it works on my laptop
>>
>> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>>
>>> Nothing I can see has changed, this one is absolutely up-to-date
>>> Ubuntu 9.04 following apt-get update and upgrade after starting up a
>>> fresh image.
>>>
>>> Then:
>>> apt-get install subversion
>>> apt-get install maven2
>>> apt-get install jetty
>>>
>>> Then:
>>> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>>
>>> Then fixing the two files.
>>>
>>> Then problem :)
>>>
>>> Now: rm -rf esme and started over
>>>
>>> One never knows where I could have messed up, only mishap was that I
>>> lost contact with the server at some point during first mvn... so now
>>> I did & and logged out leaving it alone... lets see now:
>>>
>>> Nope, exact same error.
>>>
>>> Noticed that it starts saying compiling 49 packages, then dies after a
>>> bit, and when trying again it says compiling 8 packages. No other
>>> clues.
>>>
>>>
>>>
>>>
>>>
>>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> > RE plug-in: I remember.
>>> >
>>> > I think something else (Scala, lift, etc.) might have changed. Has
>>> anything
>>> > else changed in the environment?
>>> >
>>> > It is all very strange. It is obviously a maven-related problem, because
>>> > ESME's code hasn't really changed at all in the last few weeks.
>>> >
>>> > On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>>> >
>>> >> Then I get this:
>>> >>
>>> >> [ERROR] FATAL ERROR
>>> >> [INFO]
>>> >> ------------------------------------------------------------------------
>>> >> [INFO] null
>>> >> [INFO]
>>> >> ------------------------------------------------------------------------
>>> >> [INFO] Trace
>>> >> java.lang.RuntimeException
>>> >> at
>>> >>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>>> >> at
>>> >>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>>> >> at
>>> >>
>>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>>> >> at
>>> >>
>>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>>> >> at
>>> >>
>>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>> >>
>>> >> BTW, it was you who suggested doing this last time, and then all was
>>> >> ok for basically same setup (that was Jan 5th) :)
>>> >>
>>> >>
>>> >> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>>> >> > what happens if you don't comment out the plug-in
>>> >> >
>>> >> > On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>> >> >
>>> >> >> Ethan,
>>> >> >>
>>> >> >> this is a completely new install so I'm using "mvn jetty:run"
>>> >> >>
>>> >> >> Prior to that:
>>> >> >> 1. svn the full esme
>>> >> >> 2. add line to default.props
>>> >> >> 3. comment out plugin in pom.xml
>>> >> >>
>>> >> >> using -e gave this at the end:
>>> >> >>
>>> >> >> [INFO] Trace
>>> >> >> org.apache.maven.BuildFailureException: command line returned
>>> non-zero
>>> >> >> value:1
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>> >> >> at
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>> >> >> at
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>> >> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>> >> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> >> >> at
>>> >> >>
>>> >>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> >> >> at
>>> >> >>
>>> >>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> >> >> at java.lang.reflect.Method.invoke(Method.java:616)
>>> >> >> at
>>> >> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>> >> >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>> >> >> at
>>> >> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>> >> >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>> >> >> Caused by: org.apache.maven.plugin.MojoFailureException: command line
>>> >> >> returned non-zero value:1
>>> >> >> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> >> >> at
>>> >> >>
>>> >>
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> >> >> ... 20 more
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>> >> >> > Hi Sig,
>>> >> >> >
>>> >> >> > Can you give the full stack trace - I don't think this once goes
>>> deep
>>> >> >> > enough for us to see if the error is in ESME or somewhere else? And
>>> >> >> > exactly what command are you running that results in this error?
>>> mvn
>>> >> >> > clean install?
>>> >> >> >
>>> >> >> > Thanks,
>>> >> >> > Ethan
>>> >> >> >
>>> >> >> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
>>> >> >> >> Thanks Ethan,
>>> >> >> >>
>>> >> >> >> planned to start over to test all fresh, so I created a new and
>>> fresh
>>> >> >> >> Amazon instance (same base image as the other live one), apt-get
>>> >> >> >> upgrade etc, now running 9.04 all latest.
>>> >> >> >>
>>> >> >> >> New svn from esme.
>>> >> >> >>
>>> >> >> >> Added new api_test user in default.props and commented out the
>>> >> >> >> compression plug-in in pom.xml.
>>> >> >> >>
>>> >> >> >> Then fired it up and got this error:
>>> >> >> >>
>>> >> >> >> [INFO] suggestion: remove the scalaVersion from pom.xml
>>> >> >> >> [ERROR] /home/files/esme/server/src/test/scala
>>> >> >> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>> >> >> >> [INFO] Compiling 8 source files to
>>> >> >> /home/files/esme/server/target/test-classes
>>> >> >> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
>>> >> >> >> [WARNING] at
>>> >> >> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>> >> >> >> [WARNING] at
>>> >> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>> >> >> >> [WARNING] at
>>> >> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >> >> [WARNING] at
>>> >> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >> >> [WARNING] at
>>> >> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >> >> [WARNING] at
>>> >> >>
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> >> >> ...
>>> >> >> >>
>>> >> >> >> So what did I forget this time :)
>>> >> >> >>
>>> >> >> >> S
>>> >> >> >>
>>> >> >> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>> >> >> >>> Hi Sig,
>>> >> >> >>>
>>> >> >> >>> Thanks for doing all that detective work. Unfortunately I don't
>>> have
>>> >> >> >>> an Ubuntu box to test on. :-(
>>> >> >> >>>
>>> >> >> >>> I wonder if there is some place that I pull in the setting for
>>> the
>>> >> >> >>> integration test user other than in the API2 code. Definitely
>>> >> >> >>> possible. I will try to look in to it.
>>> >> >> >>>
>>> >> >> >>> Question if you have the time: If you add another line in the
>>> >> property
>>> >> >> >>> file and assign a second user as integration admin, does that
>>> user
>>> >> >> >>> stop working in the web interface as well?
>>> >> >> >>>
>>> >> >> >>> Thanks,
>>> >> >> >>> Ethan
>>> >> >> >>>
>>> >> >> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>>> wrote:
>>> >> >> >>>> Morning creative sleuth work:
>>> >> >> >>>>
>>> >> >> >>>> 1. Sorry, no difference between browsers:
>>> >> >> >>>> 2. If I log on as another user, then log out in anything but
>>> root,
>>> >> say
>>> >> >> >>>> "hosturl:8080/auth_view/" then no problem.
>>> >> >> >>>> 3. If I log out and log on as api_test in root same problem on
>>> all
>>> >> >> browsers.
>>> >> >> >>>> 4. This only for the aws instance, not for my local instance.
>>> (aws
>>> >> is
>>> >> >> >>>> ubuntu, local is OS X)
>>> >> >> >>>> 5. Did a diff between the two (local and aws) webapp folders and
>>> >> found
>>> >> >> >>>> nothing different (except the .svn stuff which I removed after
>>> >> first
>>> >> >> >>>> try).
>>> >> >> >>>> 6. Did a diff between full esme directories and found no diff
>>> >> except
>>> >> >> >>>> .svn folders and that esme on aws held a file named .gitignore.
>>> >> >> >>>>
>>> >> >> >>>> The server works though, and now I know how to get in there so I
>>> >> can
>>> >> >> >>>> live with problem and assume it'll go away with a later new and
>>> >> fresh
>>> >> >> >>>> install... :)
>>> >> >> >>>>
>>> >> >> >>>>
>>> >> >> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>> >> >> >>>>> might be a lift-specific problem with those browsers.
>>> >> >> >>>>
>>> >> >> >>>
>>> >> >> >>
>>> >> >> >
>>> >> >>
>>> >> >
>>> >>
>>> >
>>>
>>
>
Re: Wee error
Posted by Vassil Dichev <vd...@apache.org>.
We've had this before:
http://mail-archives.apache.org/mod_mbox/incubator-esme-dev/200910.mbox/%3Ccdbebedf0910282036j6cc888caw93358695c5c6c008@mail.gmail.com%3E
The interesting part is that noone has implemented David's suggestion
to date, and still the problem seems to have been resolved (or was
it?)
BTW what JDK are you using? I've had my share of problems on
Debian/Ubuntu because package management decided to pull openjdk-6,
which was not mature enough to run bug-free.
Vassil
On Tue, Jan 26, 2010 at 4:37 PM, Richard Hirsch <hi...@gmail.com> wrote:
> I'm going to try it locally to see if it works on my laptop
>
> On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> Nothing I can see has changed, this one is absolutely up-to-date
>> Ubuntu 9.04 following apt-get update and upgrade after starting up a
>> fresh image.
>>
>> Then:
>> apt-get install subversion
>> apt-get install maven2
>> apt-get install jetty
>>
>> Then:
>> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>>
>> Then fixing the two files.
>>
>> Then problem :)
>>
>> Now: rm -rf esme and started over
>>
>> One never knows where I could have messed up, only mishap was that I
>> lost contact with the server at some point during first mvn... so now
>> I did & and logged out leaving it alone... lets see now:
>>
>> Nope, exact same error.
>>
>> Noticed that it starts saying compiling 49 packages, then dies after a
>> bit, and when trying again it says compiling 8 packages. No other
>> clues.
>>
>>
>>
>>
>>
>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> > RE plug-in: I remember.
>> >
>> > I think something else (Scala, lift, etc.) might have changed. Has
>> anything
>> > else changed in the environment?
>> >
>> > It is all very strange. It is obviously a maven-related problem, because
>> > ESME's code hasn't really changed at all in the last few weeks.
>> >
>> > On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>> >
>> >> Then I get this:
>> >>
>> >> [ERROR] FATAL ERROR
>> >> [INFO]
>> >> ------------------------------------------------------------------------
>> >> [INFO] null
>> >> [INFO]
>> >> ------------------------------------------------------------------------
>> >> [INFO] Trace
>> >> java.lang.RuntimeException
>> >> at
>> >>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>> >> at
>> >>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>> >> at
>> >>
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>> >> at
>> >>
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>> >> at
>> >>
>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>> >>
>> >> BTW, it was you who suggested doing this last time, and then all was
>> >> ok for basically same setup (that was Jan 5th) :)
>> >>
>> >>
>> >> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> >> > what happens if you don't comment out the plug-in
>> >> >
>> >> > On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>> >> >
>> >> >> Ethan,
>> >> >>
>> >> >> this is a completely new install so I'm using "mvn jetty:run"
>> >> >>
>> >> >> Prior to that:
>> >> >> 1. svn the full esme
>> >> >> 2. add line to default.props
>> >> >> 3. comment out plugin in pom.xml
>> >> >>
>> >> >> using -e gave this at the end:
>> >> >>
>> >> >> [INFO] Trace
>> >> >> org.apache.maven.BuildFailureException: command line returned
>> non-zero
>> >> >> value:1
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> >> >> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> >> >> at
>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> >> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> >> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> >> at
>> >> >>
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >> >> at
>> >> >>
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >> >> at java.lang.reflect.Method.invoke(Method.java:616)
>> >> >> at
>> >> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >> >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >> >> at
>> >> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >> >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> >> >> Caused by: org.apache.maven.plugin.MojoFailureException: command line
>> >> >> returned non-zero value:1
>> >> >> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> >> at
>> >> >>
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>> >> >> at
>> >> >>
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>> >> >> at
>> >> >>
>> >>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>> >> >> at
>> >> >>
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>> >> >> at
>> >> >>
>> >>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> >> >> at
>> >> >>
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> >> >> ... 20 more
>> >> >>
>> >> >>
>> >> >>
>> >> >> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>> >> >> > Hi Sig,
>> >> >> >
>> >> >> > Can you give the full stack trace - I don't think this once goes
>> deep
>> >> >> > enough for us to see if the error is in ESME or somewhere else? And
>> >> >> > exactly what command are you running that results in this error?
>> mvn
>> >> >> > clean install?
>> >> >> >
>> >> >> > Thanks,
>> >> >> > Ethan
>> >> >> >
>> >> >> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
>> >> >> >> Thanks Ethan,
>> >> >> >>
>> >> >> >> planned to start over to test all fresh, so I created a new and
>> fresh
>> >> >> >> Amazon instance (same base image as the other live one), apt-get
>> >> >> >> upgrade etc, now running 9.04 all latest.
>> >> >> >>
>> >> >> >> New svn from esme.
>> >> >> >>
>> >> >> >> Added new api_test user in default.props and commented out the
>> >> >> >> compression plug-in in pom.xml.
>> >> >> >>
>> >> >> >> Then fired it up and got this error:
>> >> >> >>
>> >> >> >> [INFO] suggestion: remove the scalaVersion from pom.xml
>> >> >> >> [ERROR] /home/files/esme/server/src/test/scala
>> >> >> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
>> >> >> >> [INFO] Compiling 8 source files to
>> >> >> /home/files/esme/server/target/test-classes
>> >> >> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
>> >> >> >> [WARNING] at
>> >> >> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >> >> >> [WARNING] at
>> >> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> >> >> >> [WARNING] at
>> >> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> >> [WARNING] at
>> >> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> >> [WARNING] at
>> >> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> >> [WARNING] at
>> >> >>
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> >> ...
>> >> >> >>
>> >> >> >> So what did I forget this time :)
>> >> >> >>
>> >> >> >> S
>> >> >> >>
>> >> >> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> >> >> >>> Hi Sig,
>> >> >> >>>
>> >> >> >>> Thanks for doing all that detective work. Unfortunately I don't
>> have
>> >> >> >>> an Ubuntu box to test on. :-(
>> >> >> >>>
>> >> >> >>> I wonder if there is some place that I pull in the setting for
>> the
>> >> >> >>> integration test user other than in the API2 code. Definitely
>> >> >> >>> possible. I will try to look in to it.
>> >> >> >>>
>> >> >> >>> Question if you have the time: If you add another line in the
>> >> property
>> >> >> >>> file and assign a second user as integration admin, does that
>> user
>> >> >> >>> stop working in the web interface as well?
>> >> >> >>>
>> >> >> >>> Thanks,
>> >> >> >>> Ethan
>> >> >> >>>
>> >> >> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
>> wrote:
>> >> >> >>>> Morning creative sleuth work:
>> >> >> >>>>
>> >> >> >>>> 1. Sorry, no difference between browsers:
>> >> >> >>>> 2. If I log on as another user, then log out in anything but
>> root,
>> >> say
>> >> >> >>>> "hosturl:8080/auth_view/" then no problem.
>> >> >> >>>> 3. If I log out and log on as api_test in root same problem on
>> all
>> >> >> browsers.
>> >> >> >>>> 4. This only for the aws instance, not for my local instance.
>> (aws
>> >> is
>> >> >> >>>> ubuntu, local is OS X)
>> >> >> >>>> 5. Did a diff between the two (local and aws) webapp folders and
>> >> found
>> >> >> >>>> nothing different (except the .svn stuff which I removed after
>> >> first
>> >> >> >>>> try).
>> >> >> >>>> 6. Did a diff between full esme directories and found no diff
>> >> except
>> >> >> >>>> .svn folders and that esme on aws held a file named .gitignore.
>> >> >> >>>>
>> >> >> >>>> The server works though, and now I know how to get in there so I
>> >> can
>> >> >> >>>> live with problem and assume it'll go away with a later new and
>> >> fresh
>> >> >> >>>> install... :)
>> >> >> >>>>
>> >> >> >>>>
>> >> >> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> >> >> >>>>> might be a lift-specific problem with those browsers.
>> >> >> >>>>
>> >> >> >>>
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >
>> >>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
I'm going to try it locally to see if it works on my laptop
On Tue, Jan 26, 2010 at 3:33 PM, Sig Rinde <si...@rinde.com> wrote:
> Nothing I can see has changed, this one is absolutely up-to-date
> Ubuntu 9.04 following apt-get update and upgrade after starting up a
> fresh image.
>
> Then:
> apt-get install subversion
> apt-get install maven2
> apt-get install jetty
>
> Then:
> svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunk esme
>
> Then fixing the two files.
>
> Then problem :)
>
> Now: rm -rf esme and started over
>
> One never knows where I could have messed up, only mishap was that I
> lost contact with the server at some point during first mvn... so now
> I did & and logged out leaving it alone... lets see now:
>
> Nope, exact same error.
>
> Noticed that it starts saying compiling 49 packages, then dies after a
> bit, and when trying again it says compiling 8 packages. No other
> clues.
>
>
>
>
>
> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> > RE plug-in: I remember.
> >
> > I think something else (Scala, lift, etc.) might have changed. Has
> anything
> > else changed in the environment?
> >
> > It is all very strange. It is obviously a maven-related problem, because
> > ESME's code hasn't really changed at all in the last few weeks.
> >
> > On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
> >
> >> Then I get this:
> >>
> >> [ERROR] FATAL ERROR
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] null
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Trace
> >> java.lang.RuntimeException
> >> at
> >>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> >> at
> >>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> >> at
> >>
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> >> at
> >>
> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> >> at
> >>
> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
> >>
> >> BTW, it was you who suggested doing this last time, and then all was
> >> ok for basically same setup (that was Jan 5th) :)
> >>
> >>
> >> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> >> > what happens if you don't comment out the plug-in
> >> >
> >> > On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
> >> >
> >> >> Ethan,
> >> >>
> >> >> this is a completely new install so I'm using "mvn jetty:run"
> >> >>
> >> >> Prior to that:
> >> >> 1. svn the full esme
> >> >> 2. add line to default.props
> >> >> 3. comment out plugin in pom.xml
> >> >>
> >> >> using -e gave this at the end:
> >> >>
> >> >> [INFO] Trace
> >> >> org.apache.maven.BuildFailureException: command line returned
> non-zero
> >> >> value:1
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> >> >> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> >> >> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> >> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> >> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> >> at
> >> >>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> >> at
> >> >>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> >> at java.lang.reflect.Method.invoke(Method.java:616)
> >> >> at
> >> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >> >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >> >> at
> >> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >> >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >> >> Caused by: org.apache.maven.plugin.MojoFailureException: command line
> >> >> returned non-zero value:1
> >> >> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> >> at
> >> >>
> >>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> >> >> at
> >> >>
> >>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> >> >> at
> >> >>
> >>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> >> >> at
> >> >>
> >>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> >> >> at
> >> >>
> >>
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> >> >> at
> >> >>
> >>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> >> >> at
> >> >>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> >> >> ... 20 more
> >> >>
> >> >>
> >> >>
> >> >> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> >> >> > Hi Sig,
> >> >> >
> >> >> > Can you give the full stack trace - I don't think this once goes
> deep
> >> >> > enough for us to see if the error is in ESME or somewhere else? And
> >> >> > exactly what command are you running that results in this error?
> mvn
> >> >> > clean install?
> >> >> >
> >> >> > Thanks,
> >> >> > Ethan
> >> >> >
> >> >> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
> >> >> >> Thanks Ethan,
> >> >> >>
> >> >> >> planned to start over to test all fresh, so I created a new and
> fresh
> >> >> >> Amazon instance (same base image as the other live one), apt-get
> >> >> >> upgrade etc, now running 9.04 all latest.
> >> >> >>
> >> >> >> New svn from esme.
> >> >> >>
> >> >> >> Added new api_test user in default.props and commented out the
> >> >> >> compression plug-in in pom.xml.
> >> >> >>
> >> >> >> Then fired it up and got this error:
> >> >> >>
> >> >> >> [INFO] suggestion: remove the scalaVersion from pom.xml
> >> >> >> [ERROR] /home/files/esme/server/src/test/scala
> >> >> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
> >> >> >> [INFO] Compiling 8 source files to
> >> >> /home/files/esme/server/target/test-classes
> >> >> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
> >> >> >> [WARNING] at
> >> >> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >> >> >> [WARNING] at
> >> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >> >> >> [WARNING] at
> >> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> >> [WARNING] at
> >> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> >> [WARNING] at
> >> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> >> [WARNING] at
> >> >>
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> >> ...
> >> >> >>
> >> >> >> So what did I forget this time :)
> >> >> >>
> >> >> >> S
> >> >> >>
> >> >> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >> >> >>> Hi Sig,
> >> >> >>>
> >> >> >>> Thanks for doing all that detective work. Unfortunately I don't
> have
> >> >> >>> an Ubuntu box to test on. :-(
> >> >> >>>
> >> >> >>> I wonder if there is some place that I pull in the setting for
> the
> >> >> >>> integration test user other than in the API2 code. Definitely
> >> >> >>> possible. I will try to look in to it.
> >> >> >>>
> >> >> >>> Question if you have the time: If you add another line in the
> >> property
> >> >> >>> file and assign a second user as integration admin, does that
> user
> >> >> >>> stop working in the web interface as well?
> >> >> >>>
> >> >> >>> Thanks,
> >> >> >>> Ethan
> >> >> >>>
> >> >> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com>
> wrote:
> >> >> >>>> Morning creative sleuth work:
> >> >> >>>>
> >> >> >>>> 1. Sorry, no difference between browsers:
> >> >> >>>> 2. If I log on as another user, then log out in anything but
> root,
> >> say
> >> >> >>>> "hosturl:8080/auth_view/" then no problem.
> >> >> >>>> 3. If I log out and log on as api_test in root same problem on
> all
> >> >> browsers.
> >> >> >>>> 4. This only for the aws instance, not for my local instance.
> (aws
> >> is
> >> >> >>>> ubuntu, local is OS X)
> >> >> >>>> 5. Did a diff between the two (local and aws) webapp folders and
> >> found
> >> >> >>>> nothing different (except the .svn stuff which I removed after
> >> first
> >> >> >>>> try).
> >> >> >>>> 6. Did a diff between full esme directories and found no diff
> >> except
> >> >> >>>> .svn folders and that esme on aws held a file named .gitignore.
> >> >> >>>>
> >> >> >>>> The server works though, and now I know how to get in there so I
> >> can
> >> >> >>>> live with problem and assume it'll go away with a later new and
> >> fresh
> >> >> >>>> install... :)
> >> >> >>>>
> >> >> >>>>
> >> >> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
> >> >> >>>>> might be a lift-specific problem with those browsers.
> >> >> >>>>
> >> >> >>>
> >> >> >>
> >> >> >
> >> >>
> >> >
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Nothing I can see has changed, this one is absolutely up-to-date
Ubuntu 9.04 following apt-get update and upgrade after starting up a
fresh image.
Then:
apt-get install subversion
apt-get install maven2
apt-get install jetty
Then:
svn checkout http://svn.apache.org/repos/asf/incubator/esme/trunk esme
Then fixing the two files.
Then problem :)
Now: rm -rf esme and started over
One never knows where I could have messed up, only mishap was that I
lost contact with the server at some point during first mvn... so now
I did & and logged out leaving it alone... lets see now:
Nope, exact same error.
Noticed that it starts saying compiling 49 packages, then dies after a
bit, and when trying again it says compiling 8 packages. No other
clues.
2010/1/26 Richard Hirsch <hi...@gmail.com>:
> RE plug-in: I remember.
>
> I think something else (Scala, lift, etc.) might have changed. Has anything
> else changed in the environment?
>
> It is all very strange. It is obviously a maven-related problem, because
> ESME's code hasn't really changed at all in the last few weeks.
>
> On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> Then I get this:
>>
>> [ERROR] FATAL ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] null
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> java.lang.RuntimeException
>> at
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
>> at
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
>> at
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
>> at
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
>> at
>> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>>
>> BTW, it was you who suggested doing this last time, and then all was
>> ok for basically same setup (that was Jan 5th) :)
>>
>>
>> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> > what happens if you don't comment out the plug-in
>> >
>> > On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>> >
>> >> Ethan,
>> >>
>> >> this is a completely new install so I'm using "mvn jetty:run"
>> >>
>> >> Prior to that:
>> >> 1. svn the full esme
>> >> 2. add line to default.props
>> >> 3. comment out plugin in pom.xml
>> >>
>> >> using -e gave this at the end:
>> >>
>> >> [INFO] Trace
>> >> org.apache.maven.BuildFailureException: command line returned non-zero
>> >> value:1
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> at
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> >> at
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> >> at java.lang.reflect.Method.invoke(Method.java:616)
>> >> at
>> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >> at
>> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> >> Caused by: org.apache.maven.plugin.MojoFailureException: command line
>> >> returned non-zero value:1
>> >> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> >> at
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>> >> at
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>> >> at
>> >>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>> >> at
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>> >> at
>> >>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>> >> at
>> >>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> >> at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> >> ... 20 more
>> >>
>> >>
>> >>
>> >> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>> >> > Hi Sig,
>> >> >
>> >> > Can you give the full stack trace - I don't think this once goes deep
>> >> > enough for us to see if the error is in ESME or somewhere else? And
>> >> > exactly what command are you running that results in this error? mvn
>> >> > clean install?
>> >> >
>> >> > Thanks,
>> >> > Ethan
>> >> >
>> >> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
>> >> >> Thanks Ethan,
>> >> >>
>> >> >> planned to start over to test all fresh, so I created a new and fresh
>> >> >> Amazon instance (same base image as the other live one), apt-get
>> >> >> upgrade etc, now running 9.04 all latest.
>> >> >>
>> >> >> New svn from esme.
>> >> >>
>> >> >> Added new api_test user in default.props and commented out the
>> >> >> compression plug-in in pom.xml.
>> >> >>
>> >> >> Then fired it up and got this error:
>> >> >>
>> >> >> [INFO] suggestion: remove the scalaVersion from pom.xml
>> >> >> [ERROR] /home/files/esme/server/src/test/scala
>> >> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
>> >> >> [INFO] Compiling 8 source files to
>> >> /home/files/esme/server/target/test-classes
>> >> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
>> >> >> [WARNING] at
>> >> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >> >> [WARNING] at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> >> >> [WARNING] at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> [WARNING] at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> [WARNING] at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> [WARNING] at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> >> ...
>> >> >>
>> >> >> So what did I forget this time :)
>> >> >>
>> >> >> S
>> >> >>
>> >> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> >> >>> Hi Sig,
>> >> >>>
>> >> >>> Thanks for doing all that detective work. Unfortunately I don't have
>> >> >>> an Ubuntu box to test on. :-(
>> >> >>>
>> >> >>> I wonder if there is some place that I pull in the setting for the
>> >> >>> integration test user other than in the API2 code. Definitely
>> >> >>> possible. I will try to look in to it.
>> >> >>>
>> >> >>> Question if you have the time: If you add another line in the
>> property
>> >> >>> file and assign a second user as integration admin, does that user
>> >> >>> stop working in the web interface as well?
>> >> >>>
>> >> >>> Thanks,
>> >> >>> Ethan
>> >> >>>
>> >> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
>> >> >>>> Morning creative sleuth work:
>> >> >>>>
>> >> >>>> 1. Sorry, no difference between browsers:
>> >> >>>> 2. If I log on as another user, then log out in anything but root,
>> say
>> >> >>>> "hosturl:8080/auth_view/" then no problem.
>> >> >>>> 3. If I log out and log on as api_test in root same problem on all
>> >> browsers.
>> >> >>>> 4. This only for the aws instance, not for my local instance. (aws
>> is
>> >> >>>> ubuntu, local is OS X)
>> >> >>>> 5. Did a diff between the two (local and aws) webapp folders and
>> found
>> >> >>>> nothing different (except the .svn stuff which I removed after
>> first
>> >> >>>> try).
>> >> >>>> 6. Did a diff between full esme directories and found no diff
>> except
>> >> >>>> .svn folders and that esme on aws held a file named .gitignore.
>> >> >>>>
>> >> >>>> The server works though, and now I know how to get in there so I
>> can
>> >> >>>> live with problem and assume it'll go away with a later new and
>> fresh
>> >> >>>> install... :)
>> >> >>>>
>> >> >>>>
>> >> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> >> >>>>> might be a lift-specific problem with those browsers.
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
RE plug-in: I remember.
I think something else (Scala, lift, etc.) might have changed. Has anything
else changed in the environment?
It is all very strange. It is obviously a maven-related problem, because
ESME's code hasn't really changed at all in the last few weeks.
On Tue, Jan 26, 2010 at 2:51 PM, Sig Rinde <si...@rinde.com> wrote:
> Then I get this:
>
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] null
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.RuntimeException
> at
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> at
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> at
> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> at
> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> at
> net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>
> BTW, it was you who suggested doing this last time, and then all was
> ok for basically same setup (that was Jan 5th) :)
>
>
> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
> > what happens if you don't comment out the plug-in
> >
> > On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
> >
> >> Ethan,
> >>
> >> this is a completely new install so I'm using "mvn jetty:run"
> >>
> >> Prior to that:
> >> 1. svn the full esme
> >> 2. add line to default.props
> >> 3. comment out plugin in pom.xml
> >>
> >> using -e gave this at the end:
> >>
> >> [INFO] Trace
> >> org.apache.maven.BuildFailureException: command line returned non-zero
> >> value:1
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> >> at
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> >> at java.lang.reflect.Method.invoke(Method.java:616)
> >> at
> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >> at
> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >> Caused by: org.apache.maven.plugin.MojoFailureException: command line
> >> returned non-zero value:1
> >> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> >> at
> >>
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> >> at
> >>
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> >> at
> >>
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> >> at
> >>
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> >> at
> >>
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> >> at
> >>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> >> ... 20 more
> >>
> >>
> >>
> >> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> >> > Hi Sig,
> >> >
> >> > Can you give the full stack trace - I don't think this once goes deep
> >> > enough for us to see if the error is in ESME or somewhere else? And
> >> > exactly what command are you running that results in this error? mvn
> >> > clean install?
> >> >
> >> > Thanks,
> >> > Ethan
> >> >
> >> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
> >> >> Thanks Ethan,
> >> >>
> >> >> planned to start over to test all fresh, so I created a new and fresh
> >> >> Amazon instance (same base image as the other live one), apt-get
> >> >> upgrade etc, now running 9.04 all latest.
> >> >>
> >> >> New svn from esme.
> >> >>
> >> >> Added new api_test user in default.props and commented out the
> >> >> compression plug-in in pom.xml.
> >> >>
> >> >> Then fired it up and got this error:
> >> >>
> >> >> [INFO] suggestion: remove the scalaVersion from pom.xml
> >> >> [ERROR] /home/files/esme/server/src/test/scala
> >> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
> >> >> [INFO] Compiling 8 source files to
> >> /home/files/esme/server/target/test-classes
> >> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
> >> >> [WARNING] at
> >> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >> >> [WARNING] at
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >> >> [WARNING] at
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> [WARNING] at
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> [WARNING] at
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> [WARNING] at
> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> >> ...
> >> >>
> >> >> So what did I forget this time :)
> >> >>
> >> >> S
> >> >>
> >> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >> >>> Hi Sig,
> >> >>>
> >> >>> Thanks for doing all that detective work. Unfortunately I don't have
> >> >>> an Ubuntu box to test on. :-(
> >> >>>
> >> >>> I wonder if there is some place that I pull in the setting for the
> >> >>> integration test user other than in the API2 code. Definitely
> >> >>> possible. I will try to look in to it.
> >> >>>
> >> >>> Question if you have the time: If you add another line in the
> property
> >> >>> file and assign a second user as integration admin, does that user
> >> >>> stop working in the web interface as well?
> >> >>>
> >> >>> Thanks,
> >> >>> Ethan
> >> >>>
> >> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
> >> >>>> Morning creative sleuth work:
> >> >>>>
> >> >>>> 1. Sorry, no difference between browsers:
> >> >>>> 2. If I log on as another user, then log out in anything but root,
> say
> >> >>>> "hosturl:8080/auth_view/" then no problem.
> >> >>>> 3. If I log out and log on as api_test in root same problem on all
> >> browsers.
> >> >>>> 4. This only for the aws instance, not for my local instance. (aws
> is
> >> >>>> ubuntu, local is OS X)
> >> >>>> 5. Did a diff between the two (local and aws) webapp folders and
> found
> >> >>>> nothing different (except the .svn stuff which I removed after
> first
> >> >>>> try).
> >> >>>> 6. Did a diff between full esme directories and found no diff
> except
> >> >>>> .svn folders and that esme on aws held a file named .gitignore.
> >> >>>>
> >> >>>> The server works though, and now I know how to get in there so I
> can
> >> >>>> live with problem and assume it'll go away with a later new and
> fresh
> >> >>>> install... :)
> >> >>>>
> >> >>>>
> >> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
> >> >>>>> might be a lift-specific problem with those browsers.
> >> >>>>
> >> >>>
> >> >>
> >> >
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Back to no-compress, these are the warnings I get before the long list
of identical messages:
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
[WARNING] at scala.tools.nsc.typechecker.Infer$Inferencer.checkAccessible(Infer.scala:346)
[WARNING] at scala.tools.nsc.typechecker.Typers$Typer.typedSelect$1(Typers.scala:2842)
[WARNING] at scala.tools.nsc.typechecker.Typers$Typer.typed1(Typers.scala:3280)
[WARNING] at scala.tools.nsc.transform.Erasure$Eraser.liftedTree1$1(Erasure.scala:662)
[WARNING] at scala.tools.nsc.transform.Erasure$Eraser.typed1(Erasure.scala:661)
[WARNING] at scala.tools.nsc.typechecker.Typers$Typer.typed(Typers.scala:3358)
[WARNING] at scala.tools.nsc.typechecker.Typers$Typer.typedQualifier(Typers.scala:3415)
[WARNING] at scala.tools.nsc.typechecker.Typers$Typer.typedQualifier(Typers.scala:3417)
[WARNING] at scala.tools.nsc.transform.Erasure$Eraser.adaptMember(Erasure.scala:626)
[WARNING] at scala.tools.nsc.transform.Erasure$Eraser.liftedTree1$1(Erasure.scala:662)
[WARNING] at scala.tools.nsc.transform.Erasure$Eraser.typed1(Erasure.scala:661)
2010/1/26 Sig Rinde <si...@rinde.com>:
> Then I get this:
>
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.RuntimeException
> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
> at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
> at net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
> at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
>
> BTW, it was you who suggested doing this last time, and then all was
> ok for basically same setup (that was Jan 5th) :)
>
>
> 2010/1/26 Richard Hirsch <hi...@gmail.com>:
>> what happens if you don't comment out the plug-in
>>
>> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>>
>>> Ethan,
>>>
>>> this is a completely new install so I'm using "mvn jetty:run"
>>>
>>> Prior to that:
>>> 1. svn the full esme
>>> 2. add line to default.props
>>> 3. comment out plugin in pom.xml
>>>
>>> using -e gave this at the end:
>>>
>>> [INFO] Trace
>>> org.apache.maven.BuildFailureException: command line returned non-zero
>>> value:1
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>> at
>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>>> at
>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>> Caused by: org.apache.maven.plugin.MojoFailureException: command line
>>> returned non-zero value:1
>>> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>>> at
>>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>>> at
>>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>>> at
>>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>>> at
>>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>>> at
>>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> ... 20 more
>>>
>>>
>>>
>>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>>> > Hi Sig,
>>> >
>>> > Can you give the full stack trace - I don't think this once goes deep
>>> > enough for us to see if the error is in ESME or somewhere else? And
>>> > exactly what command are you running that results in this error? mvn
>>> > clean install?
>>> >
>>> > Thanks,
>>> > Ethan
>>> >
>>> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
>>> >> Thanks Ethan,
>>> >>
>>> >> planned to start over to test all fresh, so I created a new and fresh
>>> >> Amazon instance (same base image as the other live one), apt-get
>>> >> upgrade etc, now running 9.04 all latest.
>>> >>
>>> >> New svn from esme.
>>> >>
>>> >> Added new api_test user in default.props and commented out the
>>> >> compression plug-in in pom.xml.
>>> >>
>>> >> Then fired it up and got this error:
>>> >>
>>> >> [INFO] suggestion: remove the scalaVersion from pom.xml
>>> >> [ERROR] /home/files/esme/server/src/test/scala
>>> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
>>> >> [INFO] Compiling 8 source files to
>>> /home/files/esme/server/target/test-classes
>>> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
>>> >> [WARNING] at
>>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>>> >> [WARNING] at
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>>> >> [WARNING] at
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> [WARNING] at
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> [WARNING] at
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> [WARNING] at
>>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>>> >> ...
>>> >>
>>> >> So what did I forget this time :)
>>> >>
>>> >> S
>>> >>
>>> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>> >>> Hi Sig,
>>> >>>
>>> >>> Thanks for doing all that detective work. Unfortunately I don't have
>>> >>> an Ubuntu box to test on. :-(
>>> >>>
>>> >>> I wonder if there is some place that I pull in the setting for the
>>> >>> integration test user other than in the API2 code. Definitely
>>> >>> possible. I will try to look in to it.
>>> >>>
>>> >>> Question if you have the time: If you add another line in the property
>>> >>> file and assign a second user as integration admin, does that user
>>> >>> stop working in the web interface as well?
>>> >>>
>>> >>> Thanks,
>>> >>> Ethan
>>> >>>
>>> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
>>> >>>> Morning creative sleuth work:
>>> >>>>
>>> >>>> 1. Sorry, no difference between browsers:
>>> >>>> 2. If I log on as another user, then log out in anything but root, say
>>> >>>> "hosturl:8080/auth_view/" then no problem.
>>> >>>> 3. If I log out and log on as api_test in root same problem on all
>>> browsers.
>>> >>>> 4. This only for the aws instance, not for my local instance. (aws is
>>> >>>> ubuntu, local is OS X)
>>> >>>> 5. Did a diff between the two (local and aws) webapp folders and found
>>> >>>> nothing different (except the .svn stuff which I removed after first
>>> >>>> try).
>>> >>>> 6. Did a diff between full esme directories and found no diff except
>>> >>>> .svn folders and that esme on aws held a file named .gitignore.
>>> >>>>
>>> >>>> The server works though, and now I know how to get in there so I can
>>> >>>> live with problem and assume it'll go away with a later new and fresh
>>> >>>> install... :)
>>> >>>>
>>> >>>>
>>> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>> >>>>> might be a lift-specific problem with those browsers.
>>> >>>>
>>> >>>
>>> >>
>>> >
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Then I get this:
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.RuntimeException
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber(JavaScriptCompressor.java:299)
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptCompressor.java:335)
at com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScriptCompressor.java:532)
at net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompressorMojo.java:178)
at net.sf.alchim.mojo.yuicompressor.MojoSupport.processDir(MojoSupport.java:151)
BTW, it was you who suggested doing this last time, and then all was
ok for basically same setup (that was Jan 5th) :)
2010/1/26 Richard Hirsch <hi...@gmail.com>:
> what happens if you don't comment out the plug-in
>
> On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> Ethan,
>>
>> this is a completely new install so I'm using "mvn jetty:run"
>>
>> Prior to that:
>> 1. svn the full esme
>> 2. add line to default.props
>> 3. comment out plugin in pom.xml
>>
>> using -e gave this at the end:
>>
>> [INFO] Trace
>> org.apache.maven.BuildFailureException: command line returned non-zero
>> value:1
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by: org.apache.maven.plugin.MojoFailureException: command line
>> returned non-zero value:1
>> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
>> at
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
>> at
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
>> at
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
>> at
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
>> at
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
>> at
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>> ... 20 more
>>
>>
>>
>> 2010/1/26 Ethan Jewett <es...@gmail.com>:
>> > Hi Sig,
>> >
>> > Can you give the full stack trace - I don't think this once goes deep
>> > enough for us to see if the error is in ESME or somewhere else? And
>> > exactly what command are you running that results in this error? mvn
>> > clean install?
>> >
>> > Thanks,
>> > Ethan
>> >
>> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
>> >> Thanks Ethan,
>> >>
>> >> planned to start over to test all fresh, so I created a new and fresh
>> >> Amazon instance (same base image as the other live one), apt-get
>> >> upgrade etc, now running 9.04 all latest.
>> >>
>> >> New svn from esme.
>> >>
>> >> Added new api_test user in default.props and commented out the
>> >> compression plug-in in pom.xml.
>> >>
>> >> Then fired it up and got this error:
>> >>
>> >> [INFO] suggestion: remove the scalaVersion from pom.xml
>> >> [ERROR] /home/files/esme/server/src/test/scala
>> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
>> >> [INFO] Compiling 8 source files to
>> /home/files/esme/server/target/test-classes
>> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
>> >> [WARNING] at
>> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >> [WARNING] at
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> >> [WARNING] at
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> [WARNING] at
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> [WARNING] at
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> [WARNING] at
>> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> >> ...
>> >>
>> >> So what did I forget this time :)
>> >>
>> >> S
>> >>
>> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> >>> Hi Sig,
>> >>>
>> >>> Thanks for doing all that detective work. Unfortunately I don't have
>> >>> an Ubuntu box to test on. :-(
>> >>>
>> >>> I wonder if there is some place that I pull in the setting for the
>> >>> integration test user other than in the API2 code. Definitely
>> >>> possible. I will try to look in to it.
>> >>>
>> >>> Question if you have the time: If you add another line in the property
>> >>> file and assign a second user as integration admin, does that user
>> >>> stop working in the web interface as well?
>> >>>
>> >>> Thanks,
>> >>> Ethan
>> >>>
>> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
>> >>>> Morning creative sleuth work:
>> >>>>
>> >>>> 1. Sorry, no difference between browsers:
>> >>>> 2. If I log on as another user, then log out in anything but root, say
>> >>>> "hosturl:8080/auth_view/" then no problem.
>> >>>> 3. If I log out and log on as api_test in root same problem on all
>> browsers.
>> >>>> 4. This only for the aws instance, not for my local instance. (aws is
>> >>>> ubuntu, local is OS X)
>> >>>> 5. Did a diff between the two (local and aws) webapp folders and found
>> >>>> nothing different (except the .svn stuff which I removed after first
>> >>>> try).
>> >>>> 6. Did a diff between full esme directories and found no diff except
>> >>>> .svn folders and that esme on aws held a file named .gitignore.
>> >>>>
>> >>>> The server works though, and now I know how to get in there so I can
>> >>>> live with problem and assume it'll go away with a later new and fresh
>> >>>> install... :)
>> >>>>
>> >>>>
>> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> >>>>> might be a lift-specific problem with those browsers.
>> >>>>
>> >>>
>> >>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
what happens if you don't comment out the plug-in
On Tue, Jan 26, 2010 at 2:25 PM, Sig Rinde <si...@rinde.com> wrote:
> Ethan,
>
> this is a completely new install so I'm using "mvn jetty:run"
>
> Prior to that:
> 1. svn the full esme
> 2. add line to default.props
> 3. comment out plugin in pom.xml
>
> using -e gave this at the end:
>
> [INFO] Trace
> org.apache.maven.BuildFailureException: command line returned non-zero
> value:1
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: command line
> returned non-zero value:1
> at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
> at
> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
> at
> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
> at
> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
> at
> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
> at
> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 20 more
>
>
>
> 2010/1/26 Ethan Jewett <es...@gmail.com>:
> > Hi Sig,
> >
> > Can you give the full stack trace - I don't think this once goes deep
> > enough for us to see if the error is in ESME or somewhere else? And
> > exactly what command are you running that results in this error? mvn
> > clean install?
> >
> > Thanks,
> > Ethan
> >
> > On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
> >> Thanks Ethan,
> >>
> >> planned to start over to test all fresh, so I created a new and fresh
> >> Amazon instance (same base image as the other live one), apt-get
> >> upgrade etc, now running 9.04 all latest.
> >>
> >> New svn from esme.
> >>
> >> Added new api_test user in default.props and commented out the
> >> compression plug-in in pom.xml.
> >>
> >> Then fired it up and got this error:
> >>
> >> [INFO] suggestion: remove the scalaVersion from pom.xml
> >> [ERROR] /home/files/esme/server/src/test/scala
> >> [ERROR] /home/files/esme/server/src/test/scala/../scala
> >> [INFO] Compiling 8 source files to
> /home/files/esme/server/target/test-classes
> >> [WARNING] Exception in thread "main" java.lang.StackOverflowError
> >> [WARNING] at
> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> >> [WARNING] at
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> >> [WARNING] at
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> [WARNING] at
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> [WARNING] at
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> [WARNING] at
> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> >> ...
> >>
> >> So what did I forget this time :)
> >>
> >> S
> >>
> >> 2010/1/25 Ethan Jewett <es...@gmail.com>:
> >>> Hi Sig,
> >>>
> >>> Thanks for doing all that detective work. Unfortunately I don't have
> >>> an Ubuntu box to test on. :-(
> >>>
> >>> I wonder if there is some place that I pull in the setting for the
> >>> integration test user other than in the API2 code. Definitely
> >>> possible. I will try to look in to it.
> >>>
> >>> Question if you have the time: If you add another line in the property
> >>> file and assign a second user as integration admin, does that user
> >>> stop working in the web interface as well?
> >>>
> >>> Thanks,
> >>> Ethan
> >>>
> >>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
> >>>> Morning creative sleuth work:
> >>>>
> >>>> 1. Sorry, no difference between browsers:
> >>>> 2. If I log on as another user, then log out in anything but root, say
> >>>> "hosturl:8080/auth_view/" then no problem.
> >>>> 3. If I log out and log on as api_test in root same problem on all
> browsers.
> >>>> 4. This only for the aws instance, not for my local instance. (aws is
> >>>> ubuntu, local is OS X)
> >>>> 5. Did a diff between the two (local and aws) webapp folders and found
> >>>> nothing different (except the .svn stuff which I removed after first
> >>>> try).
> >>>> 6. Did a diff between full esme directories and found no diff except
> >>>> .svn folders and that esme on aws held a file named .gitignore.
> >>>>
> >>>> The server works though, and now I know how to get in there so I can
> >>>> live with problem and assume it'll go away with a later new and fresh
> >>>> install... :)
> >>>>
> >>>>
> >>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
> >>>>> might be a lift-specific problem with those browsers.
> >>>>
> >>>
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Ethan,
this is a completely new install so I'm using "mvn jetty:run"
Prior to that:
1. svn the full esme
2. add line to default.props
3. comment out plugin in pom.xml
using -e gave this at the end:
[INFO] Trace
org.apache.maven.BuildFailureException: command line returned non-zero value:1
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:924)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:767)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:529)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: command line
returned non-zero value:1
at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196)
at org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.java:124)
at org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSupport.java:54)
at org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208)
at org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.java:29)
at org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.java:58)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 20 more
2010/1/26 Ethan Jewett <es...@gmail.com>:
> Hi Sig,
>
> Can you give the full stack trace - I don't think this once goes deep
> enough for us to see if the error is in ESME or somewhere else? And
> exactly what command are you running that results in this error? mvn
> clean install?
>
> Thanks,
> Ethan
>
> On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
>> Thanks Ethan,
>>
>> planned to start over to test all fresh, so I created a new and fresh
>> Amazon instance (same base image as the other live one), apt-get
>> upgrade etc, now running 9.04 all latest.
>>
>> New svn from esme.
>>
>> Added new api_test user in default.props and commented out the
>> compression plug-in in pom.xml.
>>
>> Then fired it up and got this error:
>>
>> [INFO] suggestion: remove the scalaVersion from pom.xml
>> [ERROR] /home/files/esme/server/src/test/scala
>> [ERROR] /home/files/esme/server/src/test/scala/../scala
>> [INFO] Compiling 8 source files to /home/files/esme/server/target/test-classes
>> [WARNING] Exception in thread "main" java.lang.StackOverflowError
>> [WARNING] at scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
>> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
>> ...
>>
>> So what did I forget this time :)
>>
>> S
>>
>> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>>> Hi Sig,
>>>
>>> Thanks for doing all that detective work. Unfortunately I don't have
>>> an Ubuntu box to test on. :-(
>>>
>>> I wonder if there is some place that I pull in the setting for the
>>> integration test user other than in the API2 code. Definitely
>>> possible. I will try to look in to it.
>>>
>>> Question if you have the time: If you add another line in the property
>>> file and assign a second user as integration admin, does that user
>>> stop working in the web interface as well?
>>>
>>> Thanks,
>>> Ethan
>>>
>>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
>>>> Morning creative sleuth work:
>>>>
>>>> 1. Sorry, no difference between browsers:
>>>> 2. If I log on as another user, then log out in anything but root, say
>>>> "hosturl:8080/auth_view/" then no problem.
>>>> 3. If I log out and log on as api_test in root same problem on all browsers.
>>>> 4. This only for the aws instance, not for my local instance. (aws is
>>>> ubuntu, local is OS X)
>>>> 5. Did a diff between the two (local and aws) webapp folders and found
>>>> nothing different (except the .svn stuff which I removed after first
>>>> try).
>>>> 6. Did a diff between full esme directories and found no diff except
>>>> .svn folders and that esme on aws held a file named .gitignore.
>>>>
>>>> The server works though, and now I know how to get in there so I can
>>>> live with problem and assume it'll go away with a later new and fresh
>>>> install... :)
>>>>
>>>>
>>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>>> might be a lift-specific problem with those browsers.
>>>>
>>>
>>
>
Re: Wee error
Posted by Ethan Jewett <es...@gmail.com>.
Hi Sig,
Can you give the full stack trace - I don't think this once goes deep
enough for us to see if the error is in ESME or somewhere else? And
exactly what command are you running that results in this error? mvn
clean install?
Thanks,
Ethan
On Tue, Jan 26, 2010 at 4:55 AM, Sig Rinde <si...@rinde.com> wrote:
> Thanks Ethan,
>
> planned to start over to test all fresh, so I created a new and fresh
> Amazon instance (same base image as the other live one), apt-get
> upgrade etc, now running 9.04 all latest.
>
> New svn from esme.
>
> Added new api_test user in default.props and commented out the
> compression plug-in in pom.xml.
>
> Then fired it up and got this error:
>
> [INFO] suggestion: remove the scalaVersion from pom.xml
> [ERROR] /home/files/esme/server/src/test/scala
> [ERROR] /home/files/esme/server/src/test/scala/../scala
> [INFO] Compiling 8 source files to /home/files/esme/server/target/test-classes
> [WARNING] Exception in thread "main" java.lang.StackOverflowError
> [WARNING] at scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> [WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
> ...
>
> So what did I forget this time :)
>
> S
>
> 2010/1/25 Ethan Jewett <es...@gmail.com>:
>> Hi Sig,
>>
>> Thanks for doing all that detective work. Unfortunately I don't have
>> an Ubuntu box to test on. :-(
>>
>> I wonder if there is some place that I pull in the setting for the
>> integration test user other than in the API2 code. Definitely
>> possible. I will try to look in to it.
>>
>> Question if you have the time: If you add another line in the property
>> file and assign a second user as integration admin, does that user
>> stop working in the web interface as well?
>>
>> Thanks,
>> Ethan
>>
>> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
>>> Morning creative sleuth work:
>>>
>>> 1. Sorry, no difference between browsers:
>>> 2. If I log on as another user, then log out in anything but root, say
>>> "hosturl:8080/auth_view/" then no problem.
>>> 3. If I log out and log on as api_test in root same problem on all browsers.
>>> 4. This only for the aws instance, not for my local instance. (aws is
>>> ubuntu, local is OS X)
>>> 5. Did a diff between the two (local and aws) webapp folders and found
>>> nothing different (except the .svn stuff which I removed after first
>>> try).
>>> 6. Did a diff between full esme directories and found no diff except
>>> .svn folders and that esme on aws held a file named .gitignore.
>>>
>>> The server works though, and now I know how to get in there so I can
>>> live with problem and assume it'll go away with a later new and fresh
>>> install... :)
>>>
>>>
>>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>>> might be a lift-specific problem with those browsers.
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Thanks Ethan,
planned to start over to test all fresh, so I created a new and fresh
Amazon instance (same base image as the other live one), apt-get
upgrade etc, now running 9.04 all latest.
New svn from esme.
Added new api_test user in default.props and commented out the
compression plug-in in pom.xml.
Then fired it up and got this error:
[INFO] suggestion: remove the scalaVersion from pom.xml
[ERROR] /home/files/esme/server/src/test/scala
[ERROR] /home/files/esme/server/src/test/scala/../scala
[INFO] Compiling 8 source files to /home/files/esme/server/target/test-classes
[WARNING] Exception in thread "main" java.lang.StackOverflowError
[WARNING] at scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
[WARNING] at scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942)
...
So what did I forget this time :)
S
2010/1/25 Ethan Jewett <es...@gmail.com>:
> Hi Sig,
>
> Thanks for doing all that detective work. Unfortunately I don't have
> an Ubuntu box to test on. :-(
>
> I wonder if there is some place that I pull in the setting for the
> integration test user other than in the API2 code. Definitely
> possible. I will try to look in to it.
>
> Question if you have the time: If you add another line in the property
> file and assign a second user as integration admin, does that user
> stop working in the web interface as well?
>
> Thanks,
> Ethan
>
> On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
>> Morning creative sleuth work:
>>
>> 1. Sorry, no difference between browsers:
>> 2. If I log on as another user, then log out in anything but root, say
>> "hosturl:8080/auth_view/" then no problem.
>> 3. If I log out and log on as api_test in root same problem on all browsers.
>> 4. This only for the aws instance, not for my local instance. (aws is
>> ubuntu, local is OS X)
>> 5. Did a diff between the two (local and aws) webapp folders and found
>> nothing different (except the .svn stuff which I removed after first
>> try).
>> 6. Did a diff between full esme directories and found no diff except
>> .svn folders and that esme on aws held a file named .gitignore.
>>
>> The server works though, and now I know how to get in there so I can
>> live with problem and assume it'll go away with a later new and fresh
>> install... :)
>>
>>
>> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>>> might be a lift-specific problem with those browsers.
>>
>
Re: Wee error
Posted by Ethan Jewett <es...@gmail.com>.
Hi Sig,
Thanks for doing all that detective work. Unfortunately I don't have
an Ubuntu box to test on. :-(
I wonder if there is some place that I pull in the setting for the
integration test user other than in the API2 code. Definitely
possible. I will try to look in to it.
Question if you have the time: If you add another line in the property
file and assign a second user as integration admin, does that user
stop working in the web interface as well?
Thanks,
Ethan
On Mon, Jan 25, 2010 at 3:27 AM, Sig Rinde <si...@rinde.com> wrote:
> Morning creative sleuth work:
>
> 1. Sorry, no difference between browsers:
> 2. If I log on as another user, then log out in anything but root, say
> "hosturl:8080/auth_view/" then no problem.
> 3. If I log out and log on as api_test in root same problem on all browsers.
> 4. This only for the aws instance, not for my local instance. (aws is
> ubuntu, local is OS X)
> 5. Did a diff between the two (local and aws) webapp folders and found
> nothing different (except the .svn stuff which I removed after first
> try).
> 6. Did a diff between full esme directories and found no diff except
> .svn folders and that esme on aws held a file named .gitignore.
>
> The server works though, and now I know how to get in there so I can
> live with problem and assume it'll go away with a later new and fresh
> install... :)
>
>
> 2010/1/25 Richard Hirsch <hi...@gmail.com>:
>> might be a lift-specific problem with those browsers.
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Morning creative sleuth work:
1. Sorry, no difference between browsers:
2. If I log on as another user, then log out in anything but root, say
"hosturl:8080/auth_view/" then no problem.
3. If I log out and log on as api_test in root same problem on all browsers.
4. This only for the aws instance, not for my local instance. (aws is
ubuntu, local is OS X)
5. Did a diff between the two (local and aws) webapp folders and found
nothing different (except the .svn stuff which I removed after first
try).
6. Did a diff between full esme directories and found no diff except
.svn folders and that esme on aws held a file named .gitignore.
The server works though, and now I know how to get in there so I can
live with problem and assume it'll go away with a later new and fresh
install... :)
2010/1/25 Richard Hirsch <hi...@gmail.com>:
> might be a lift-specific problem with those browsers.
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
might be a lift-specific problem with those browsers.
On Sun, Jan 24, 2010 at 10:53 PM, Sig Rinde <si...@rinde.com> wrote:
> Now this is interesting:
>
> Cleaned out cookies so I could log on again.
> Created a new user logged on without any glitch in Chrome, Safari and
> Firefox.
> Logged out.
> Signed on as api_test: Same problem in Chrome (dev version) and Safari
> (latest), but all was OK in Firefox 3.5.5
>
> Repeat and rinse, same each time.
>
> Hmmm...
>
>
>
>
>
> 2010/1/24 Ethan Jewett <es...@gmail.com>:
> > Hi Sig,
> >
> > In the svn repo that user is only set up in test.default.props, which
> > I'm pretty sure is only loaded when run in test mode. You might have
> > added the line in default.props. The idea was for people to take
> > responsibility for creating and setting their own admin users if they
> > are deploying in an integration setting, which it seems is exactly
> > what you've done. No problem there.
> >
> > Ok, so what is causing the problem? The copy of the webapp folder is
> > definitely a possibility. What I'd do if I were you is get everything
> > possible in sync with the trunk svn repo, including deleting the
> > duplicate webapp folder, when doing an "svn status" and reverting
> > ("svn revert path/filename") all changes that are not necessary for
> > your deployment to function. If you see a file listed in "svn status"
> > and you're not sure why it's there, you can do an "svn diff
> > path/filename" and see exactly what differences there are from trunk.
> >
> > Once you're as synced up as you can get, if you are still having
> > issues, can you outline all the differences between your deployment
> > and our trunk so that we can try to recreate your issue?
> >
> > Thanks,
> > Ethan
> >
> > On Sun, Jan 24, 2010 at 2:31 PM, Sig Rinde <si...@rinde.com> wrote:
> >> Only user api_test. All other users are added via api getting tokens
> >> directly (i.e. I do not have a password for those).
> >>
> >> First thing first time the ESME server was started I signed up
> >> api_test in order to create the api_test token that allows the rest to
> >> happen from our side.
> >>
> >> Not entirely sure why 'api_test' was chosen, I assume any user could
> >> be used as long as the default.props file has the user name. Locally
> >> we have no problems using exact same setup with 'api_test' as admin
> >> user.
> >>
> >> Installation is on an Amazon instance, same as where the Thingamy
> >> instances are running.
> >>
> >> Tried server restart, svn anew, the usual, no change.
> >>
> >> OK, have to admit to one (amateur) stunt as follows:
> >>
> >> 1. After having signed up as api_test and produced the token I renamed
> >> webapp folder to disallow any access to admin interface.
> >> 2. Forgot about that when we did an svn up later, which of course
> >> produced a new webapp.
> >>
> >> Could that have messed up?
> >>
> >>
> >> 2010/1/24 Ethan Jewett <es...@gmail.com>:
> >>> Hi Sig,
> >>>
> >>> I am surprised that you are getting this error. When I try to log in
> >>> as api_test, I just get a message that says "Unknown credentials". In
> >>> other words, I can't recreate your error, so we need some more
> >>> information, I think.
> >>>
> >>> A bit of further information: "api_test" is the test user that is
> >>> created for use in the api unit tests. It is created by those tests,
> >>> so if you are running a "mvn jetty:run" that user will not exist.
> >>> Still should not result in that error, but just wanted to be clear
> >>> that this user probably won't help you much.
> >>>
> >>> Ethan
> >>>
> >>> On Sun, Jan 24, 2010 at 2:03 PM, Richard Hirsch <hi...@gmail.com>
> wrote:
> >>>> Is the login problem just api_test or all users?
> >>>>
> >>>> Is the installation local or in the cloud?
> >>>>
> >>>> Tried a server restart to see if problem disappears?
> >>>>
> >>>> D.
> >>>>
> >>>> On Sun, Jan 24, 2010 at 8:15 PM, Sig Rinde <si...@rinde.com> wrote:
> >>>>
> >>>>> (Sorry for not doing all in one :)
> >>>>>
> >>>>> Server works, pools behaving as they should. Only the login messed
> up...
> >>>>>
> >>>>>
> >>>>> 2010/1/24 Sig Rinde <si...@rinde.com>:
> >>>>> > Actually this happened when logging in as 'api_test'
> >>>>> >
> >>>>> > [default.props has this extra line:
> role.api_test=integration-admin]
> >>>>> >
> >>>>> >
> >>>>> > 2010/1/24 Sig Rinde <si...@rinde.com>:
> >>>>> >> When trying to get into urltohost:8080 I get this (just the upper
> part
> >>>>> >> of a ton):
> >>>>> >>
> >>>>> >> Exception occured while processing/
> >>>>> >> Message: java.lang.UnsupportedOperationException: unsuitable as
> hash key
> >>>>> >>
> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
> >>>>> >>
> >>>>> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
> >>>>> >> scala.xml.Utility$.hashCode(Utility.scala:263)
> >>>>> >> scala.xml.Elem.hashCode(Elem.scala:64)
> >>>>> >>
> >>>>>
> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
> >>>>> >>
> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
> >>>>> >>
> >>>>>
> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
> >>>>> >>
> >>>>> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
> >>>>> >> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
> >>>>> >>
> >>>>>
> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
> >>>>> >>
> >>>>>
> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
> >>>>> >> scala.Iterator$class.foldLeft(Iterator.scala:520)
> >>>>> >>
> >>>>> >> Latest per svn, jetty:run behaved... server seems to be running,
> >>>>> >> although I'm suspecting some pool issues... that's what I wanted
> to
> >>>>> >> check.
> >>>>> >>
> >>>>> >> Sig
> >>>>> >>
> >>>>> >
> >>>>>
> >>>>
> >>>
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Now this is interesting:
Cleaned out cookies so I could log on again.
Created a new user logged on without any glitch in Chrome, Safari and Firefox.
Logged out.
Signed on as api_test: Same problem in Chrome (dev version) and Safari
(latest), but all was OK in Firefox 3.5.5
Repeat and rinse, same each time.
Hmmm...
2010/1/24 Ethan Jewett <es...@gmail.com>:
> Hi Sig,
>
> In the svn repo that user is only set up in test.default.props, which
> I'm pretty sure is only loaded when run in test mode. You might have
> added the line in default.props. The idea was for people to take
> responsibility for creating and setting their own admin users if they
> are deploying in an integration setting, which it seems is exactly
> what you've done. No problem there.
>
> Ok, so what is causing the problem? The copy of the webapp folder is
> definitely a possibility. What I'd do if I were you is get everything
> possible in sync with the trunk svn repo, including deleting the
> duplicate webapp folder, when doing an "svn status" and reverting
> ("svn revert path/filename") all changes that are not necessary for
> your deployment to function. If you see a file listed in "svn status"
> and you're not sure why it's there, you can do an "svn diff
> path/filename" and see exactly what differences there are from trunk.
>
> Once you're as synced up as you can get, if you are still having
> issues, can you outline all the differences between your deployment
> and our trunk so that we can try to recreate your issue?
>
> Thanks,
> Ethan
>
> On Sun, Jan 24, 2010 at 2:31 PM, Sig Rinde <si...@rinde.com> wrote:
>> Only user api_test. All other users are added via api getting tokens
>> directly (i.e. I do not have a password for those).
>>
>> First thing first time the ESME server was started I signed up
>> api_test in order to create the api_test token that allows the rest to
>> happen from our side.
>>
>> Not entirely sure why 'api_test' was chosen, I assume any user could
>> be used as long as the default.props file has the user name. Locally
>> we have no problems using exact same setup with 'api_test' as admin
>> user.
>>
>> Installation is on an Amazon instance, same as where the Thingamy
>> instances are running.
>>
>> Tried server restart, svn anew, the usual, no change.
>>
>> OK, have to admit to one (amateur) stunt as follows:
>>
>> 1. After having signed up as api_test and produced the token I renamed
>> webapp folder to disallow any access to admin interface.
>> 2. Forgot about that when we did an svn up later, which of course
>> produced a new webapp.
>>
>> Could that have messed up?
>>
>>
>> 2010/1/24 Ethan Jewett <es...@gmail.com>:
>>> Hi Sig,
>>>
>>> I am surprised that you are getting this error. When I try to log in
>>> as api_test, I just get a message that says "Unknown credentials". In
>>> other words, I can't recreate your error, so we need some more
>>> information, I think.
>>>
>>> A bit of further information: "api_test" is the test user that is
>>> created for use in the api unit tests. It is created by those tests,
>>> so if you are running a "mvn jetty:run" that user will not exist.
>>> Still should not result in that error, but just wanted to be clear
>>> that this user probably won't help you much.
>>>
>>> Ethan
>>>
>>> On Sun, Jan 24, 2010 at 2:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>>> Is the login problem just api_test or all users?
>>>>
>>>> Is the installation local or in the cloud?
>>>>
>>>> Tried a server restart to see if problem disappears?
>>>>
>>>> D.
>>>>
>>>> On Sun, Jan 24, 2010 at 8:15 PM, Sig Rinde <si...@rinde.com> wrote:
>>>>
>>>>> (Sorry for not doing all in one :)
>>>>>
>>>>> Server works, pools behaving as they should. Only the login messed up...
>>>>>
>>>>>
>>>>> 2010/1/24 Sig Rinde <si...@rinde.com>:
>>>>> > Actually this happened when logging in as 'api_test'
>>>>> >
>>>>> > [default.props has this extra line: role.api_test=integration-admin]
>>>>> >
>>>>> >
>>>>> > 2010/1/24 Sig Rinde <si...@rinde.com>:
>>>>> >> When trying to get into urltohost:8080 I get this (just the upper part
>>>>> >> of a ton):
>>>>> >>
>>>>> >> Exception occured while processing/
>>>>> >> Message: java.lang.UnsupportedOperationException: unsuitable as hash key
>>>>> >> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
>>>>> >>
>>>>> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
>>>>> >> scala.xml.Utility$.hashCode(Utility.scala:263)
>>>>> >> scala.xml.Elem.hashCode(Elem.scala:64)
>>>>> >>
>>>>> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
>>>>> >> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
>>>>> >>
>>>>> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
>>>>> >>
>>>>> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
>>>>> >> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
>>>>> >>
>>>>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>>>>> >>
>>>>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>>>>> >> scala.Iterator$class.foldLeft(Iterator.scala:520)
>>>>> >>
>>>>> >> Latest per svn, jetty:run behaved... server seems to be running,
>>>>> >> although I'm suspecting some pool issues... that's what I wanted to
>>>>> >> check.
>>>>> >>
>>>>> >> Sig
>>>>> >>
>>>>> >
>>>>>
>>>>
>>>
>>
>
Re: Wee error
Posted by Ethan Jewett <es...@gmail.com>.
Hi Sig,
In the svn repo that user is only set up in test.default.props, which
I'm pretty sure is only loaded when run in test mode. You might have
added the line in default.props. The idea was for people to take
responsibility for creating and setting their own admin users if they
are deploying in an integration setting, which it seems is exactly
what you've done. No problem there.
Ok, so what is causing the problem? The copy of the webapp folder is
definitely a possibility. What I'd do if I were you is get everything
possible in sync with the trunk svn repo, including deleting the
duplicate webapp folder, when doing an "svn status" and reverting
("svn revert path/filename") all changes that are not necessary for
your deployment to function. If you see a file listed in "svn status"
and you're not sure why it's there, you can do an "svn diff
path/filename" and see exactly what differences there are from trunk.
Once you're as synced up as you can get, if you are still having
issues, can you outline all the differences between your deployment
and our trunk so that we can try to recreate your issue?
Thanks,
Ethan
On Sun, Jan 24, 2010 at 2:31 PM, Sig Rinde <si...@rinde.com> wrote:
> Only user api_test. All other users are added via api getting tokens
> directly (i.e. I do not have a password for those).
>
> First thing first time the ESME server was started I signed up
> api_test in order to create the api_test token that allows the rest to
> happen from our side.
>
> Not entirely sure why 'api_test' was chosen, I assume any user could
> be used as long as the default.props file has the user name. Locally
> we have no problems using exact same setup with 'api_test' as admin
> user.
>
> Installation is on an Amazon instance, same as where the Thingamy
> instances are running.
>
> Tried server restart, svn anew, the usual, no change.
>
> OK, have to admit to one (amateur) stunt as follows:
>
> 1. After having signed up as api_test and produced the token I renamed
> webapp folder to disallow any access to admin interface.
> 2. Forgot about that when we did an svn up later, which of course
> produced a new webapp.
>
> Could that have messed up?
>
>
> 2010/1/24 Ethan Jewett <es...@gmail.com>:
>> Hi Sig,
>>
>> I am surprised that you are getting this error. When I try to log in
>> as api_test, I just get a message that says "Unknown credentials". In
>> other words, I can't recreate your error, so we need some more
>> information, I think.
>>
>> A bit of further information: "api_test" is the test user that is
>> created for use in the api unit tests. It is created by those tests,
>> so if you are running a "mvn jetty:run" that user will not exist.
>> Still should not result in that error, but just wanted to be clear
>> that this user probably won't help you much.
>>
>> Ethan
>>
>> On Sun, Jan 24, 2010 at 2:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>>> Is the login problem just api_test or all users?
>>>
>>> Is the installation local or in the cloud?
>>>
>>> Tried a server restart to see if problem disappears?
>>>
>>> D.
>>>
>>> On Sun, Jan 24, 2010 at 8:15 PM, Sig Rinde <si...@rinde.com> wrote:
>>>
>>>> (Sorry for not doing all in one :)
>>>>
>>>> Server works, pools behaving as they should. Only the login messed up...
>>>>
>>>>
>>>> 2010/1/24 Sig Rinde <si...@rinde.com>:
>>>> > Actually this happened when logging in as 'api_test'
>>>> >
>>>> > [default.props has this extra line: role.api_test=integration-admin]
>>>> >
>>>> >
>>>> > 2010/1/24 Sig Rinde <si...@rinde.com>:
>>>> >> When trying to get into urltohost:8080 I get this (just the upper part
>>>> >> of a ton):
>>>> >>
>>>> >> Exception occured while processing/
>>>> >> Message: java.lang.UnsupportedOperationException: unsuitable as hash key
>>>> >> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
>>>> >>
>>>> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
>>>> >> scala.xml.Utility$.hashCode(Utility.scala:263)
>>>> >> scala.xml.Elem.hashCode(Elem.scala:64)
>>>> >>
>>>> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
>>>> >> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
>>>> >>
>>>> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
>>>> >>
>>>> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
>>>> >> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
>>>> >>
>>>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>>>> >>
>>>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>>>> >> scala.Iterator$class.foldLeft(Iterator.scala:520)
>>>> >>
>>>> >> Latest per svn, jetty:run behaved... server seems to be running,
>>>> >> although I'm suspecting some pool issues... that's what I wanted to
>>>> >> check.
>>>> >>
>>>> >> Sig
>>>> >>
>>>> >
>>>>
>>>
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Only user api_test. All other users are added via api getting tokens
directly (i.e. I do not have a password for those).
First thing first time the ESME server was started I signed up
api_test in order to create the api_test token that allows the rest to
happen from our side.
Not entirely sure why 'api_test' was chosen, I assume any user could
be used as long as the default.props file has the user name. Locally
we have no problems using exact same setup with 'api_test' as admin
user.
Installation is on an Amazon instance, same as where the Thingamy
instances are running.
Tried server restart, svn anew, the usual, no change.
OK, have to admit to one (amateur) stunt as follows:
1. After having signed up as api_test and produced the token I renamed
webapp folder to disallow any access to admin interface.
2. Forgot about that when we did an svn up later, which of course
produced a new webapp.
Could that have messed up?
2010/1/24 Ethan Jewett <es...@gmail.com>:
> Hi Sig,
>
> I am surprised that you are getting this error. When I try to log in
> as api_test, I just get a message that says "Unknown credentials". In
> other words, I can't recreate your error, so we need some more
> information, I think.
>
> A bit of further information: "api_test" is the test user that is
> created for use in the api unit tests. It is created by those tests,
> so if you are running a "mvn jetty:run" that user will not exist.
> Still should not result in that error, but just wanted to be clear
> that this user probably won't help you much.
>
> Ethan
>
> On Sun, Jan 24, 2010 at 2:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> Is the login problem just api_test or all users?
>>
>> Is the installation local or in the cloud?
>>
>> Tried a server restart to see if problem disappears?
>>
>> D.
>>
>> On Sun, Jan 24, 2010 at 8:15 PM, Sig Rinde <si...@rinde.com> wrote:
>>
>>> (Sorry for not doing all in one :)
>>>
>>> Server works, pools behaving as they should. Only the login messed up...
>>>
>>>
>>> 2010/1/24 Sig Rinde <si...@rinde.com>:
>>> > Actually this happened when logging in as 'api_test'
>>> >
>>> > [default.props has this extra line: role.api_test=integration-admin]
>>> >
>>> >
>>> > 2010/1/24 Sig Rinde <si...@rinde.com>:
>>> >> When trying to get into urltohost:8080 I get this (just the upper part
>>> >> of a ton):
>>> >>
>>> >> Exception occured while processing/
>>> >> Message: java.lang.UnsupportedOperationException: unsuitable as hash key
>>> >> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
>>> >>
>>> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
>>> >> scala.xml.Utility$.hashCode(Utility.scala:263)
>>> >> scala.xml.Elem.hashCode(Elem.scala:64)
>>> >>
>>> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
>>> >> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
>>> >>
>>> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
>>> >>
>>> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
>>> >> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
>>> >>
>>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>>> >>
>>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>>> >> scala.Iterator$class.foldLeft(Iterator.scala:520)
>>> >>
>>> >> Latest per svn, jetty:run behaved... server seems to be running,
>>> >> although I'm suspecting some pool issues... that's what I wanted to
>>> >> check.
>>> >>
>>> >> Sig
>>> >>
>>> >
>>>
>>
>
Re: Wee error
Posted by Ethan Jewett <es...@gmail.com>.
Hi Sig,
I am surprised that you are getting this error. When I try to log in
as api_test, I just get a message that says "Unknown credentials". In
other words, I can't recreate your error, so we need some more
information, I think.
A bit of further information: "api_test" is the test user that is
created for use in the api unit tests. It is created by those tests,
so if you are running a "mvn jetty:run" that user will not exist.
Still should not result in that error, but just wanted to be clear
that this user probably won't help you much.
Ethan
On Sun, Jan 24, 2010 at 2:03 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Is the login problem just api_test or all users?
>
> Is the installation local or in the cloud?
>
> Tried a server restart to see if problem disappears?
>
> D.
>
> On Sun, Jan 24, 2010 at 8:15 PM, Sig Rinde <si...@rinde.com> wrote:
>
>> (Sorry for not doing all in one :)
>>
>> Server works, pools behaving as they should. Only the login messed up...
>>
>>
>> 2010/1/24 Sig Rinde <si...@rinde.com>:
>> > Actually this happened when logging in as 'api_test'
>> >
>> > [default.props has this extra line: role.api_test=integration-admin]
>> >
>> >
>> > 2010/1/24 Sig Rinde <si...@rinde.com>:
>> >> When trying to get into urltohost:8080 I get this (just the upper part
>> >> of a ton):
>> >>
>> >> Exception occured while processing/
>> >> Message: java.lang.UnsupportedOperationException: unsuitable as hash key
>> >> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
>> >>
>> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
>> >> scala.xml.Utility$.hashCode(Utility.scala:263)
>> >> scala.xml.Elem.hashCode(Elem.scala:64)
>> >>
>> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
>> >> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
>> >>
>> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
>> >>
>> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
>> >> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
>> >>
>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>> >>
>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>> >> scala.Iterator$class.foldLeft(Iterator.scala:520)
>> >>
>> >> Latest per svn, jetty:run behaved... server seems to be running,
>> >> although I'm suspecting some pool issues... that's what I wanted to
>> >> check.
>> >>
>> >> Sig
>> >>
>> >
>>
>
Re: Wee error
Posted by Richard Hirsch <hi...@gmail.com>.
Is the login problem just api_test or all users?
Is the installation local or in the cloud?
Tried a server restart to see if problem disappears?
D.
On Sun, Jan 24, 2010 at 8:15 PM, Sig Rinde <si...@rinde.com> wrote:
> (Sorry for not doing all in one :)
>
> Server works, pools behaving as they should. Only the login messed up...
>
>
> 2010/1/24 Sig Rinde <si...@rinde.com>:
> > Actually this happened when logging in as 'api_test'
> >
> > [default.props has this extra line: role.api_test=integration-admin]
> >
> >
> > 2010/1/24 Sig Rinde <si...@rinde.com>:
> >> When trying to get into urltohost:8080 I get this (just the upper part
> >> of a ton):
> >>
> >> Exception occured while processing/
> >> Message: java.lang.UnsupportedOperationException: unsuitable as hash key
> >> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
> >>
> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
> >> scala.xml.Utility$.hashCode(Utility.scala:263)
> >> scala.xml.Elem.hashCode(Elem.scala:64)
> >>
> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
> >> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
> >>
> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
> >>
> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
> >> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
> >>
> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
> >>
> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
> >> scala.Iterator$class.foldLeft(Iterator.scala:520)
> >>
> >> Latest per svn, jetty:run behaved... server seems to be running,
> >> although I'm suspecting some pool issues... that's what I wanted to
> >> check.
> >>
> >> Sig
> >>
> >
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
(Sorry for not doing all in one :)
Server works, pools behaving as they should. Only the login messed up...
2010/1/24 Sig Rinde <si...@rinde.com>:
> Actually this happened when logging in as 'api_test'
>
> [default.props has this extra line: role.api_test=integration-admin]
>
>
> 2010/1/24 Sig Rinde <si...@rinde.com>:
>> When trying to get into urltohost:8080 I get this (just the upper part
>> of a ton):
>>
>> Exception occured while processing/
>> Message: java.lang.UnsupportedOperationException: unsuitable as hash key
>> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
>> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
>> scala.xml.Utility$.hashCode(Utility.scala:263)
>> scala.xml.Elem.hashCode(Elem.scala:64)
>> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
>> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
>> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
>> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
>> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
>> scala.Iterator$class.foldLeft(Iterator.scala:520)
>>
>> Latest per svn, jetty:run behaved... server seems to be running,
>> although I'm suspecting some pool issues... that's what I wanted to
>> check.
>>
>> Sig
>>
>
Re: Wee error
Posted by Sig Rinde <si...@rinde.com>.
Actually this happened when logging in as 'api_test'
[default.props has this extra line: role.api_test=integration-admin]
2010/1/24 Sig Rinde <si...@rinde.com>:
> When trying to get into urltohost:8080 I get this (just the upper part
> of a ton):
>
> Exception occured while processing/
> Message: java.lang.UnsupportedOperationException: unsuitable as hash key
> scala.collection.mutable.Buffer$class.hashCode(Buffer.scala:280)
> scala.collection.mutable.ArrayBuffer.hashCode(ArrayBuffer.scala:26)
> scala.xml.Utility$.hashCode(Utility.scala:263)
> scala.xml.Elem.hashCode(Elem.scala:64)
> scala.collection.mutable.FlatHashTable$class.elemHashCode(FlatHashTable.scala:144)
> scala.collection.immutable.HashSet.elemHashCode(HashSet.scala:39)
> scala.collection.mutable.FlatHashTable$class.containsEntry(FlatHashTable.scala:56)
> scala.collection.immutable.HashSet.containsEntry(HashSet.scala:39)
> scala.collection.immutable.HashSet.$plus(HashSet.scala:60)
> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
> scala.collection.immutable.Set$$anonfun$$plus$plus$1.apply(Set.scala:73)
> scala.Iterator$class.foldLeft(Iterator.scala:520)
>
> Latest per svn, jetty:run behaved... server seems to be running,
> although I'm suspecting some pool issues... that's what I wanted to
> check.
>
> Sig
>