db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1190) Network Server reports wrong product name when logging connections to derby.log
Date Fri, 07 Apr 2006 11:26:25 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1190?page=comments#action_12373624 ] 

John H. Embretsen commented on DERBY-1190:
------------------------------------------

Below is an example derby.log with 'DERBY-1190_v1.diff' applied to current trunk. The only
change is that "Cloudscape" is replaced with "Apache Derby" in the connection log text
.

======= derby.log START ================ 

Apache Derby Network Server - 10.2.0.0 alpha started and ready to accept connections on port
1527 at 2006-04-07 09:14:20.258 GMT
Connection number: 1.
----------------------------------------------------------------
2006-04-07 09:16:32.804 GMT:
 Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.0.0 alpha - (392214M):
instance c013800d-010a-73a1-6ed3-000000149b70
on database directory /export/home/tmp/test/testDB

Database Class Loader started - derby.database.classpath=''
2006-04-07 09:16:34.051 GMT Thread[DRDAConnThread_3,5,main] (DATABASE = testDB), (DRDAID =
{1}), Apache Derby Network Server connected to database testDB;create=true

======= derby.log END ================ 


> Network Server reports wrong product name when logging connections to derby.log
> -------------------------------------------------------------------------------
>
>          Key: DERBY-1190
>          URL: http://issues.apache.org/jira/browse/DERBY-1190
>      Project: Derby
>         Type: Bug

>   Components: Network Server
>     Versions: 10.1.2.1, 10.2.0.0
>  Environment: Derby client/server environments
>     Reporter: John H. Embretsen
>     Assignee: John H. Embretsen
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: DERBY-1190_v1.diff, DERBY-1190_v1.stat
>
> The Derby Network Server is symptomatic of dissociative identity disorder when derby.drda.logConnections=true.
At startup and shutdown the network server correctly recognizes itself as "Apache Derby".
When logging connections, however, it thinks it is "Cloudscape". 
> See the following derby.log for an example:
> ======= derby.log  START ================
> Apache Derby Network Server - 10.2.0.0 alpha started and ready to accept connections
on port 1527 at 2006-04-07 09:09:22.766 GMT
> Connection number: 1.
> ----------------------------------------------------------------
> 2006-04-07 09:10:02.054 GMT:
>  Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.0.0 alpha
- (392214): instance c013800d-010a-739c-e4bf-0000001109c8
> on database directory /export/home/tmp/test/testDB
> Database Class Loader started - derby.database.classpath=''
> 2006-04-07 09:10:03.287 GMT Thread[DRDAConnThread_3,5,main] (DATABASE = testDB), (DRDAID
= {1}), Cloudscape Network Server connected to database testDB;create=true
> ======= derby.log  END ================
> To reproduce, do the following:
> 1. Start the network server with the property derby.drda.logConnections set to true.
An example follows:
> bash-3.00 $ java -Dderby.drda.logConnections=true -jar ${DERBY_CURRENT}/derbyrun.jar
NetworkServerControl start
> Apache Derby Network Server - 10.2.0.0 alpha started and ready to accept connections
on port 1527 at 2006-04-07 09:09:22.766 GMT
> Connection number: 1.
> 2. Use the client driver to connect to the server. An example follows (using IJ):
> bash-3.00 $ java -jar ${DERBY_CURRENT}/derbyrun.jar ij
> ij version 10.2
> ij> connect 'jdbc:derby://localhost:1527/testDB;create=true';
> ij> exit;

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message