All trials were with mvn jetty:run.
Thanks for the pointer: every database is separate.
I just noticed that each, whether I'm using it or not, has a db.lck

I just ran an experiment: removed the db.lck file in the 1.2 distribution (I don't know that much about Derby) and now it refuses to respond to the Sign On button.

Still fiddling.

Jack

On 7/28/2011 7:46 PM, Richard Hirsch wrote:
If you are using the integrated derby database, then you are probably
using it for multiple versions - which might not be a good thing. I
haven't tried it yet. Look for a folder called esme_db.

If you are using tomcat, try a clean build and then run esme with
jetty:run to see if the problem still exists. You may also want to
delete your browser cookies. That might be a problem as well.

D.


On Fri, Jul 29, 2011 at 4:39 AM, Jack Park<[email protected]>  wrote:
What I mean is that the timelines stopped working entirely, but the tags
that were visible (this is the 1.2 distribution tarball).

I shut the system down and built the 1.3 rc-1 distribution tarball and ran
that only to discover that tags were not working there.  I then went back to
the original 1.2 distro, booted it, noted my two users could still log in,
but there are no timelines visible. Sending messages do not appear anywhere.

I then went and booted the subversion 1.2 rc-1 tag; no tags, and adding a
user to a pool fails.

I then went and booted the subversion trunk. Same issues.

All that to say that I had active timelines in the 1.2 distribution until I
started running other distributions.  By way of weak inference, I have to
wonder if there is anything like a shared database among those builds.

Jack

On 7/28/2011 7:33 PM, Richard Hirsch wrote:

What do you mean by " no messages sent from it show up anywhere"?
There are no messages in the timeline? Tagged messages?

D.

On Thu, Jul 28, 2011 at 8:21 PM, Jack Park<[email protected]>
  wrote:

I returned to 1.2 and found, now, that it remembers the tags, but not any
of
the messages. In fact, no messages sent from it show up anywhere. Time
for
some coffee, I suppose.

On 7/28/2011 11:10 AM, Richard Hirsch wrote:

I just tried it on the stax instance and added the user "acmebob" to a
pool and it worked.

Regarding the "Edit" button for pools. Right now it is not correctly
labeled, because you can just add users. But we plan to be able to
change other parts of the group (rename, etc) and then hopefully the
"edit" label will be correct.

D.

On Thu, Jul 28, 2011 at 8:06 PM, Jack Park<[email protected]>
  wrote:

Where the messages never stop!
Went back to 1.2 with what I learned playing with 1.3.
1.2 lets me add "joe" as a user to my pool.
So, I suspect 1.3 is broken in terms of adding users to pools.

Jack

On 7/28/2011 10:59 AM, Jack Park wrote:

Slight update. What I know about pools came from 1.2. In 1.3, pools
behave a bit differently, or so it seems. I found that the (misnamed?)
Edit button lets me add a member. I tried adding the other user
("joe").
Clicking add user does nothing. "joe" is a real user visible in the
user's list.

I hope to learn what you can do when you have a pool. Can you assign
messages to the pool? Can pools be private?

Jack

On 7/28/2011 10:39 AM, Jack Park wrote:

Now that I've got your attention, may I ask for links to explanations
about pools and, while we're at it, tokens? I have some hints about
tokens, but absolutely no clue about pools. I created one, thinking
it
might be a "group" (a feature I want), but when I came in as a
different
user, I was not able to "join" that pool.

Thanks
Jack



Reply via email to