Ghost connections "Java(TM) 2 Platform Standard Edition"
We have a server application with multiple threads each using JDBC connections. On the Database server (MS SQL Server 7) we notice more and more connections with the SQLQueryAnalyzer-ProgramName "Java(TM) 2 Platform Standard Edition". But all our (known) connections have custom names or the default name of the JDBC driver (jTDS). The developer of jTDS answered that the driver only have connections that are requested by the application. But we don't have connections named dbc connections "Java(TM) 2 Platform Standard Edition" ... ?
Well then what other architectural components are you using? What application server? Frameworks? Any other third party libraries? How about your own stuff - is your code base small enough that you can be positive that the application isn't obtaining connections in places that you're not familiar with?
Basically if the jTDS guys say it isn't originating in their logic I believe 'em. So it's somewhere on the other side of the fence.
We don't use an application server, it's just a plain Java application. No frameworks and only 3rd party libs that don't handle any database connection - and the JDBC driver jTDS. As one of the developers got very angry about my bug report, because he insists that it's not the fault of jTDS, I have to rule out jTDS. That would mean that it's somewhere in my application. But I just have 1 single class that actually creates a JDBC connection, so it's not hard to debug this. And I can't see any additional connections as all of my connections get specific names and not "Java(TM) 2 Platform Standard Edition".
I searched all source code of the Java SDK, jTDS and my source code for occurences of "Java(TM) 2 Platform Standard Edition" and can't find any. I hoped that somebody knows who is using this string (and when). It sounds like general Java (SDK/JRE) is setting this name, but I haven't found it.
Well, presumably the source code for jTDS is available, so you could add some logic to that and to your own connection aquisition logic and see if there's a one-to-one correspondence.
