Hi Peter & John (Thompson),
[ I apologize for the delayed response. My Linux server was hacked and I've
been working in my spare time to re-install w/ the latest RedHat. I've been
running into hardware conflicts, so my Enhydra / instantDB development is on
hold for the moment. Fortunately I didn't lose anything of value except my
time. ]
I was able to access the idb db from JDBCmain. Another reason I believe the
problem is Enhydra-related rather than idb is that I tried with postgresql
and had the same response. This was shortly before the hacking incident.
Thanks again,
-Randy
-----Original Message-----
From: owner-instantDB@Enhydra.ORG [mailto:owner-instantDB@Enhydra.ORG]On
Behalf Of Peter Hearty
Sent: Thursday, April 27, 2000 3:30 AM
To: instantdb@enhydra.org
Subject: Re: InstantDB: FW: instantDB connection problem
Randy
Agreed - it sounds like InstantDB isn't even getting started. It's not a
permissions failure though. InstantDB doesn't have multiple usernames and
priviliges. Any username and password passed to it are just ignored.
Are you able to access the database OK from outside Enhydra - say using
JDBCmain?
Regards
Peter Hearty
Lutris Technologies UK Ltd.
-----Original Message-----
From: Randy Schnedler <schnedlr@satx.rr.com>
To: instantDB@enhydra.org <instantDB@enhydra.org>
Date: 26 April 2000 18:28
Subject: RE: InstantDB: FW: instantDB connection problem
>Hi Peter,
>
>Thanks for the quick response. Unfortunately, I already have the trace*
>options set. In fact, I have traceLevel=2047, which I imagine would cause
>loads of debug info. But I don't see anything at all.
>
>The error is happening when I start up the Enhydra server, which itself
>handles connecting to the database. Since at this point, I'm not executing
>any of my app's code, I can't add the .setLogStream without getting into
>Enhydra's source. :(
>
>If this is a permissions failure (with the idb security name/password),
>would something still be logged in the idb log? At this point, NOTHING is
>getting logged by idb. It's as if idb is never gets off the ground.
>
>Thx again,
>-Randy
>
>-----Original Message-----
>From: owner-instantDB@Enhydra.ORG [mailto:owner-instantDB@Enhydra.ORG]On
>Behalf Of Peter Hearty
>Sent: Wednesday, April 26, 2000 11:58 AM
>To: instantDB@enhydra.org
>Subject: RE: InstantDB: FW: instantDB connection problem
>
>
>Randy
>
>One possibility is that it's InstantDB that's failing. Try adding some
>tracing by editing your InstantDB database's properties file and adding
>something like:
>
>traceConsole=1
>traceFile=trace.log
>traceLevel=2
>
>You could also try adding:
>
>java.sql.DriverManager.setLogStream(java.lang.System.out);
>
>somewhere in your code to see if the InstantDB driver is getting properly
>loaded.
>
>Hopefully
>
>Regards
>
>Peter Hearty
>Lutris Technologies UK
>
>
>-----Original Message-----
>From: owner-instantDB@Enhydra.ORG [mailto:owner-instantDB@Enhydra.ORG]On
>Behalf Of Randy Schnedler
>Sent: 26 April 2000 17:28
>To: instantdb@enhydra.org
>Subject: InstantDB: FW: instantDB connection problem
>
>
>Hi folks.... I sent this message to the Enhydra list and haven't received
>any responses. Maybe I'm being too impatient, but maybe this is an
>instantDB problem anyway, so I thought I'd send it to this list.
>
>Any help would be greatly appreciated. Note that I'm running Linux 6.1
with
>Enhydra 3.0.1.
>
>Thanks,
>-Randy
>
>-----Original Message-----
>From: Randy Schnedler [mailto:schnedlr@satx.rr.com]
>Sent: Monday, April 24, 2000 11:10 PM
>To: enhydra@enhydra.org
>Subject: instantDB connection problem
>
>
>Hi all,
>
>First off, I'll warn you that I am still somewhat an Enhydra newbie, but am
>enjoying the learning process. I am grateful for Enhydra itself and all
the
>work of the Enhydra community.
>
>I am working on a database-driven ASP-based site to deliver to a client,
and
>thought it would be a good learning experience to develop an Enhydra
>version. I have installed instantDB (v3.13 and v3.14b5), and set up the db
>schema with DODS successfully. However, when I "./start" the application,
I
>get a NullPointerException. Below are excerpts from my .conf and the
>Enhydra log. Nothing at all is logged or changed within the database
>folder/files. The database name is "ranches".
>
>My questions:
>-------------
>- Obviously, what am I doing wrong to get the NullPointerException?
> (Does it have to do with the username/password? I don't know how to set
>this up in instantDB. Accessing the db with "java JDBCmain" seems to work
>fine though.)
>
>- Are all the ".Connection." entries necessary in the .conf? (Besides the
>URL, of course.)
>
>Thanks for the help!
>-Randy
>
>
>
>FROM .CONF:
>-----------
>DatabaseManager.Databases[] = "ranches"
>DatabaseManager.DefaultDatabase = "ranches"
>DatabaseManager.Debug = "true"
>DatabaseManager.DB.ranches.ClassType = "Standard"
>DatabaseManager.DB.ranches.JdbcDriver = "jdbc.idbDriver"
>DatabaseManager.DB.ranches.Connection.Url="jdbc:idb:/usr/local/instantDB/db
s
>/ranches.prp"
>DatabaseManager.DB.ranches.Connection.User = ""
>DatabaseManager.DB.ranches.Connection.Password = ""
>DatabaseManager.DB.ranches.Connection.Logging = "true"
>DatabaseManager.DB.ranches.Connection.MaxPreparedStatements = 10
>DatabaseManager.DB.ranches.Connection.MaxPoolSize = 30
>DatabaseManager.DB.ranches.Connection.AllocationTimeout = 10000
>DatabaseManager.DB.ranches.Connection.ObjectID.CacheSize = 20
>DatabaseManager.DB.ranches.Connection.ObjectID.MinValue = 1
>
>FROM ENHYDRA .LOG:
>------------------
>2000.04.24 21:45:00: Multiserver,ERROR: Unable to change application to
>running state: Could not create logical database ranches:
>java.lang.NullPointerException: Could not create logical database ranches:
>java.lang.NullPointerException
>2000.04.24 21:45:00: Multiserver,ERROR+
>com.lutris.appserver.server.ApplicationException: Could not create logical
>database ranches: java.lang.NullPointerException: Could not create logical
>database ranches: java.lang.NullPointerException
>2000.04.24 21:45:00: Multiserver,ERROR+ at
>com.lutris.appserver.server.StandardApplication.createDatabaseManager(Stand
a
>rdApplication.java:259)
>
>[...]
>
>
>---------------------------------------------------------------------------
-
>-
>To unsubscribe from this mailing list, send email to majordomo@enhydra.org
>with the text "unsubscribe instantdb" in the body of the email.
>If you have other questions regarding this mailing list, send email to
>the list admin at owner-instantdb@enhydra.org.
>
>---------------------------------------------------------------------------
-
>-
>To unsubscribe from this mailing list, send email to majordomo@enhydra.org
>with the text "unsubscribe instantdb" in the body of the email.
>If you have other questions regarding this mailing list, send email to
>the list admin at owner-instantdb@enhydra.org.
>
>---------------------------------------------------------------------------
--
>To unsubscribe from this mailing list, send email to majordomo@enhydra.org
>with the text "unsubscribe instantdb" in the body of the email.
>If you have other questions regarding this mailing list, send email to
>the list admin at owner-instantdb@enhydra.org.
----------------------------------------------------------------------------
-
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
----------------------------------------------------------------------------
-
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|