Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sig.rinde@gmail.com designates
 209.85.218.210 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type
         :content-transfer-encoding;
        b=Bk0pUrU8Uydk9qkZD5bOYuqT1Ds1gRLQNc0HVlWnIcsL3f/hgezgC7C2aj+Kr3FTsW
         fkgi8Q8OJ1TEfgJmNO57fVEjoO0/sF0l8ygj91OTr7ge1CRABIbttiq4dmtj0hjYuMnE
         TWsPAw7iTz2yg99XEskQFFUVpWIshv/u3yAks=
MIME-Version: 1.0
Sender: sig.rinde@gmail.com
In-Reply-To: <fa2d9f451001260615l23f2b587p2069e8a6d7e4ab3b@mail.gmail.com>
References: <9cbd74ac1001241040h32eed541wad74ce2cf51c84ee@mail.gmail.com>
	<fa2d9f451001242300h74bd2302t30ae751210065890@mail.gmail.com>
	<9cbd74ac1001250027y5f34e253ja5950992a2d786f8@mail.gmail.com>
	<68f4a0e81001251426x6b2e2727pc8d9c7c4e9eaf957@mail.gmail.com>
	<9cbd74ac1001260155o7b274a37k37ac8b8fc2594a0c@mail.gmail.com>
	<68f4a0e81001260515w6650711cyf1c994a5cdaf5122@mail.gmail.com>
	<9cbd74ac1001260525w7e260226w6d3ea69cc5dd5de@mail.gmail.com>
	<fa2d9f451001260547l7932e217gf6eeef6658e6d311@mail.gmail.com>
	<9cbd74ac1001260551h3f16875fn9d8054f63209baa0@mail.gmail.com>
	<fa2d9f451001260615l23f2b587p2069e8a6d7e4ab3b@mail.gmail.com>
From: Sig Rinde <sig@rinde.com>
Date: Tue, 26 Jan 2010 15:33:46 +0100
Message-ID: <9cbd74ac1001260633t36e642cbwf18fe3b46a75947e@mail.gmail.com>
Subject: Re: Wee error
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <hirsch.dick@gmail.com>:
> RE plug-in: I remember.
>
> I think something else (Scala, lift, etc.) might have changed. =A0Has any=
thing
> 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
>> =A0 =A0 =A0 =A0at
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.printSourceNumber=
(JavaScriptCompressor.java:299)
>> =A0 =A0 =A0 =A0at
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.parse(JavaScriptC=
ompressor.java:335)
>> =A0 =A0 =A0 =A0at
>> com.yahoo.platform.yui.compressor.JavaScriptCompressor.<init>(JavaScript=
Compressor.java:532)
>> =A0 =A0 =A0 =A0at
>> net.sf.alchim.mojo.yuicompressor.YuiCompressorMojo.processFile(YuiCompre=
ssorMojo.java:178)
>> =A0 =A0 =A0 =A0at
>> 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 <hirsch.dick@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-zer=
o
>> >> value:1
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default=
LifecycleExecutor.java:579)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec=
ycle(DefaultLifecycleExecutor.java:499)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle=
(DefaultLifecycleExecutor.java:924)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Defaul=
tLifecycleExecutor.java:767)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default=
LifecycleExecutor.java:529)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa=
l(DefaultLifecycleExecutor.java:512)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL=
ifecycleExecutor.java:482)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle=
Failures(DefaultLifecycleExecutor.java:330)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(=
DefaultLifecycleExecutor.java:291)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec=
ycleExecutor.java:142)
>> >> =A0 =A0 =A0 =A0at org.apache.maven.DefaultMaven.doExecute(DefaultMave=
n.java:336)
>> >> =A0 =A0 =A0 =A0at org.apache.maven.DefaultMaven.execute(DefaultMaven.=
java:129)
>> >> =A0 =A0 =A0 =A0at org.apache.maven.cli.MavenCli.main(MavenCli.java:28=
7)
>> >> =A0 =A0 =A0 =A0at sun.reflect.NativeMethodAccessorImpl.invoke0(Native=
 Method)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav=
a:57)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor=
Impl.java:43)
>> >> =A0 =A0 =A0 =A0at java.lang.reflect.Method.invoke(Method.java:616)
>> >> =A0 =A0 =A0 =A0at
>> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >> =A0 =A0 =A0 =A0at org.codehaus.classworlds.Launcher.launch(Launcher.j=
ava:255)
>> >> =A0 =A0 =A0 =A0at
>> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >> =A0 =A0 =A0 =A0at org.codehaus.classworlds.Launcher.main(Launcher.jav=
a:375)
>> >> Caused by: org.apache.maven.plugin.MojoFailureException: command line
>> >> returned non-zero value:1
>> >> =A0 =A0 =A0 =A0at org.scala_tools.maven.JavaCommand.run(JavaCommand.j=
ava:196)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSupport.=
java:124)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSuppor=
t.java:54)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java:208=
)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSupport.=
java:29)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.scala_tools.maven.ScalaTestCompileMojo.execute(ScalaTestCompileMojo.=
java:58)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa=
nager.java:451)
>> >> =A0 =A0 =A0 =A0at
>> >>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default=
LifecycleExecutor.java:558)
>> >> =A0 =A0 =A0 =A0... 20 more
>> >>
>> >>
>> >>
>> >> 2010/1/26 Ethan Jewett <esjewett@gmail.com>:
>> >> > Hi Sig,
>> >> >
>> >> > Can you give the full stack trace - I don't think this once goes de=
ep
>> >> > 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? mv=
n
>> >> > 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 fr=
esh
>> >> >> 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] =A0 =A0 =A0 at
>> >> scala.tools.nsc.symtab.Symbols$ClassSymbol.owner(Symbols.scala:1563)
>> >> >> [WARNING] =A0 =A0 =A0 at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:940=
)
>> >> >> [WARNING] =A0 =A0 =A0 at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942=
)
>> >> >> [WARNING] =A0 =A0 =A0 at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942=
)
>> >> >> [WARNING] =A0 =A0 =A0 at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942=
)
>> >> >> [WARNING] =A0 =A0 =A0 at
>> >> scala.tools.nsc.symtab.Symbols$Symbol.toplevelClass(Symbols.scala:942=
)
>> >> >> ...
>> >> >>
>> >> >> So what did I forget this time :)
>> >> >>
>> >> >> S
>> >> >>
>> >> >> 2010/1/25 Ethan Jewett <esjewett@gmail.com>:
>> >> >>> Hi Sig,
>> >> >>>
>> >> >>> Thanks for doing all that detective work. Unfortunately I don't h=
ave
>> >> >>> an Ubuntu box to test on. :-(
>> >> >>>
>> >> >>> I wonder if there is some place that I pull in the setting for th=
e
>> >> >>> 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 use=
r
>> >> >>> 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 roo=
t,
>> say
>> >> >>>> "hosturl:8080/auth_view/" then no problem.
>> >> >>>> 3. If I log out and log on as api_test in root same problem on a=
ll
>> >> browsers.
>> >> >>>> 4. This only for the aws instance, not for my local instance. (a=
ws
>> 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.
>> >> >>>>
>> >> >>>
>> >> >>
>> >> >
>> >>
>> >
>>
>