I've noticed recently that the SystemDatabase/ directory and derby.log
files are being created in the current working directory (the
directory from which I start the server from using java -jar ..) and
not in the installation directory of Geronimo. I'm not sure if that's
new or
IIRC, the derby.log was always in the bin directory. But then again, I
could be wrong.
Cheers
Prasad
On 3/2/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:
I've noticed recently that the SystemDatabase/ directory and derby.log
files are being created in the current working directory (th
.
Cheers
Prasad
On 3/2/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:
I've noticed recently that the SystemDatabase/ directory and derby.log
files are being created in the current working directory (the
directory from which I start the server from using java -jar ..) and
not in the i
The SystemDatabase and the original derby.log is in var/derby for
rev 513298. Did you use DBManager or database pool wizard? I have
another derby.log and a derby.backup in var after I
deployed/undeployed database pools few times.
Thanks
Anita
--- Jarek Gawor <[EMAIL PROTECTED]>
A correction...
My last message was for 2.0-M3. There is no var/derby for rev
513298. The SystemDatabase and derby.log are in g-home dir.
Thanks
Anita
--- Anita Kulshreshtha <[EMAIL PROTECTED]> wrote:
>The SystemDatabase and the original derby.log is in var/derby for
> rev
Eh... thats broke...
--jason
On Mar 2, 2007, at 12:08 PM, Anita Kulshreshtha wrote:
A correction...
My last message was for 2.0-M3. There is no var/derby for rev
513298. The SystemDatabase and derby.log are in g-home dir.
Thanks
Anita
--- Anita Kulshreshtha <[EMAIL PROTECTED]>
On Mar 2, 2007, at 3:08 PM, Anita Kulshreshtha wrote:
A correction...
My last message was for 2.0-M3. There is no var/derby for rev
513298. The SystemDatabase and derby.log are in g-home dir.
I'm not following you, Anita. If derby log and systemdatabase are not
in var/derby,
rby for rev
> > 513298. The SystemDatabase and derby.log are in g-home dir.
>
> I'm not following you, Anita. If derby log and systemdatabase are not
>
> in var/derby, would someone please create a jira? looks g
Hello!
To connect to the SystemDatabase, and be able to continue with the cmp deployment, just follow these steps: (Windows)
1º STEP a folder with these 3 jars inside:
1. db2jcc.jar2. db2jcc_license_c.jar
you download from IBM site:
Derby does not currently provide a network JDBC driver
Katia,
This is great information. Can you add it to the wiki so others can
find it easily?
Thanks,
-dain
--
Dain Sundstrom
Chief Architect
Gluecode Software
On Apr 16, 2005, at 5:50 PM, Katia Aresti Gonzalez wrote:
Hello!
To connect to the SystemDatabase, and be able to continue with the cmp
I dont know how to do it :-(
>From: Dain Sundstrom <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: Connecting to SystemDatabase and create table
>Date: Mon, 18 Apr 2005 08:57:12 -0700
>
>Katia,
>
>This is great information
wrote:
I dont know how to do it :-(
>From: Dain Sundstrom <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: Connecting to SystemDatabase and create table
>Date: Mon, 18 Apr 2005 08:57:12 -0700
>
>Katia,
>
>This is great information
Enabling authentication for Derby renders DB Viewer portlet unusable for all
db's except SystemDatabase
---
Key: GERONIMO-3875
URL: https://issues.apache.org
name.
Option 2: Require the user to enter credentials for db authentication, say once
per session.
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except
of Option1 from above. Patch created
against branches\2.1.
Comments? Suggestions??
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except Sys
work with non-derby databases?
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
> Key: GER
now. We can revisit/change the intent of this
portlet in trunk via a different JIRA...
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except
4 in branches\2.1
At revision: 641795 in trunk
o Enables using DB portlet for databases with connection pools defined.
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except
tion for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
> Key: GERONIMO-3875
> URL: https://issues.apache.o
doesn't look like it will make 2.1.1
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
>
this in branches/2.1 (2.1.2).Can
this be closed?
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
>
work necessary . so I guess I'll
move it to 2.1.3
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
s is used)
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
> Key: GERONIMO-3875
>
)
2.1.4
Assignee: Donald Woods
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
>
probably will not get fixed for 2.1.4.
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
>
DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
> Key: GERONIMO-3875
> URL: https://issues.apache.org/ji
.
> Enabling authentication for Derby renders DB Viewer portlet unusable for all
> db's except SystemDatabase
> ---
>
> Key: GERONIMO-3875
>
27 matches
Mail list logo
