Permissions Stop Loading

1 view
Skip to first unread message

Philip Weaver

unread,
Apr 4, 2009, 7:07:13 PM4/4/09
to dovetaildb-discuss
A couple of times I have gone to manage permissions and subsequently they don't load. Most recently I think I had issued all permissions for _metadata because I was trying out how to insert and call code. See the log error below. The database continues to operate seemingly normally - I can continue to insert and query data but I can never get back in to manage permissions. I've tried restarting the database, emptying my cache and cookies and restarting my browser - but I can never get back into managing permissions.

I haven't tried restarting my server yet. Any idea about what's going on or how I might prevent this from occuring?

2009-04-04 22:26:48.585::WARN:  /query
dovetaildb.ApiException: Unknown txnId "zw6-zg2Uk7mzkYq4"
at dovetaildb.service.ServiceIndexes.query(ServiceIndexes.java:292)
at dovetaildb.service.ServiceRestartableSorting$1.nextIterator(ServiceRestartableSorting.java:132)
at dovetaildb.iterator.SequenceQueryResultIterator.pullAvailable(SequenceQueryResultIterator.java:43)
at dovetaildb.iterator.Limit$1.pullAvailable(Limit.java:50)
at dovetaildb.util.Util.jsonEncode(Util.java:546)
at dovetaildb.util.Util.jsonEncode(Util.java:514)
at dovetaildb.servlet.ServerServlet.doPost(ServerServlet.java:121)
at dovetaildb.servlet.ServerServlet.doGet(ServerServlet.java:201)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:829)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:488)

Dovetail 0.3.6
Mac OS X 10.5.6
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-
b06-284)
Java HotSpot(TM) Client VM (build 1.5.0_16-133, mixed mode, sharing)

Philip Weaver

unread,
Apr 4, 2009, 8:09:57 PM4/4/09
to dovetaildb-discuss
Upon another review, I had actually generated a new key on _metadata and changed permissions to all and then saved. I tried this because I hadn't been able to get code insertion working. Was that a bad idea to do what I did?

Phil

psch...@gmail.com

unread,
Apr 5, 2009, 2:45:57 AM4/5/09
to dovetaildb-discuss
Hi Phil! Thanks so much for the bug report -- my biggest problem with
DovetailDB is that there aren't enough people using it to exercise it
properly. I was able to replicate the behavior you describe. I
believe there's a regression in the sort feature of 0.3.6. There's a
fix and some extended capabilities in 0.4.0 (including sorting on
weighted combinations of multiple fields): hopefully I can post it in
the next few days. In the meantime, you can edit your local
manage.html file and change this line:
dovetail.query('auth', {db_is:lcl.db.id}, {sort:'create_dt'},
function(perms) {
to this one (to ditch the sort):
dovetail.query('auth', {db_is:lcl.db.id}, {}, function(perms) {

Of course, it's a bigger bummer if your app is trying to use sorts, as
you may encounter the same issue -- again, hopefully I can post
something soon. Please continue to not be shy around here - I very
much want to hear about every little annoying thing.

Also, although I don't believe it's related to your issue, I would shy
away from touching the _metadata database -- create a new database
instead and work there. If _metadata's javascript code breaks for
some reason, everything will stop working, and you won't be able to
use the system enough to be able to fix it. (you may or may not have
noticed that the management interface itself is just a DovetailDB
application that operates on the _metadata database)

Cheers,
Phil S.
Reply all
Reply to author
Forward
0 new messages