db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Martin <j...@reportmill.com>
Subject Re: Embedded Server *and* client
Date Sat, 11 Jul 2009 00:16:44 GMT
I was thinking that some low level tracing had been enabled, too, but  
I'm confident I haven't enabled it. Perhaps it gets enabled  
automatically when some severe condition is encountered.

My theory is that when I ask for a JDBC connection to the server,  
which is local to my process and listening on port 1527, the  
ClientDriver tries to open the same port and fails. Then it ends up  
using that AutoloadedDriver. Perhaps there's another way to get a JDBC  
connection to a sever running in-process.

Thanks for your response!


On Jul 10, 2009, at 6:06 PM, Bryan Pendleton wrote:

>> Currently I'm using DriverManager.getConnection() locally. This  
>> works, but dumps about half a meg of messages to the DriverManager  
>> log.
> It looks like you've enabled some fairly low-level Derby tracing.
> But I'm confused about the question you're asking:
> - are you trying to figure out how to turn off this tracing, because
>   you don't want the tracing?
> - or are you trying to figure out how to read the tracing, because
>   you think it's revealing information about a problem you're having?
> thanks,
> bryan

View raw message