Re: [stellation-res] Volunteer - Installing the core

[jhoward@xxxxxxxxxxxxxxx]

Hello,

> Yikes. This is bizarre, as I run the tests using 7.2.3 as part of the
> current build process. Before digging too deeply, you might want to try
> an older build, say 2002-12-10, to see if problem shows up there as well.

I tried 2002-12-10 with the same results.  It hangs on test 02 in the
same place.  

> You might want to also conduct some simple tests re add/synchronize. For
> example
>   tsvc create p
>   tsvc checkout p
>   echo "file" > a
>   tsvc add a
>   tsvc ci
>   echo "more" > b
>   tsvc sync
> and so forth. If you get a hang, then rerun with -d3 to get log output.
> For example,
>   tsvc -d3 ci

Well, I started in on this process, and I ran into a problem along the
way.  (Either I'm going to be incredibly helpful in testing, or this
will all trace back to user error and I'll have to put my keyboard
down before I hurt myself.  ;)

In order to conduct these hand tests, I needed to initialize a dabase
in which to work.  According to the core install instructions, the
right command is "svcadmin postgres:stellation stellation
stellation-password".  Because I'm working out of the compiled
build/bin directory with the t* commands, I translated this to
"tsvcadmin postgres:stellation stellation stellation-password"

The error message printed was:

"Error: Invalid command postgres:stellation."

After hunting around a bit, I saw (unfortunately I don't remember
where) something that suggested that I should be using the command
line "svcadmin init postgres:stellation stellation password"

So, trying "tsvcadmin init postgres:stellation stellation password", I saw:

Usage:
  svcadmin init location file
  svcadmin init location admin-name admin-password

I noted in the tests that the location used was
"postgresql:[databasename]" instead of "postgres:[databasename]" as
the documentation is written.  So I tried that and got a usage message
again.  Lastly, I tried using the full command line syntax I'd seen in
the tests:

tsvcadmin init --location postgresql:stellation --username stellation --password password

That worked.  The command ran to completion without trouble.

>   tsvc create p
>   tsvc checkout p
>   echo "file" > a
>   tsvc add a
>   tsvc ci
>   echo "more" > b
>   tsvc sync
> and so forth. If you get a hang, then rerun with -d3 to get log output.
> For example,
>   tsvc -d3 ci

Just running this sequence of commands without anything more
complicated, I got up to tsvc sync. That hung, and I ran the command
again with -d3.  Unfortunately, when I ran it with -d3, everything
terminated normally.  This was very odd, and it made me wonder if
perhaps some state from the uncompleted command had allowed the run
with -d3 to succeed.  I cleaned up from the test, dropped the
database, and started over, this time running -d3 with every command.
And much to my satisfaction, I now have a trace with -d3 when the sync
command froze up.  That trace is...

./tsvc -d3 --location=postgresql:stellation --username=jhoward --password=password sync

0 [main] INFO org.eclipse.stellation.cli.workspace.Workspace  - start xerces read of workspace doc
8 [main] INFO org.eclipse.stellation.cli.workspace.Workspace  - end xerces read of workspace doc
16 [main] INFO org.eclipse.stellation.cli.data.LogManager  - start xerces read log
35 [main] INFO org.eclipse.stellation.cli.data.LogManager  - end xerces read log
107 [main] DEBUG org.eclipse.stellation.cli.workspace.Workspace  - attributes initial size 3
188 [main] DEBUG org.eclipse.stellation.cli.workspace.Change - stateNow 0
1063 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -1
1423 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -2
1805 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -3
2188 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -4

And there the trace stops.  No further progress is reported even after
a substantial amount of time.

> Also, which JRE are you using?

Sun's 1.4.1 JDK.  The full java -version info is:

java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)



Thanks again for all your help,
Jeffrey