You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Umakanth Srinivasan <ka...@dhyanit.com> on 2007/05/10 17:19:16 UTC
Product Id issue
I have a strange problem, before posting I failed finding similiar
reportings.....
I am starting the Derby DB in embeded mode.
Inconsistently during some startups, the derby server throws the below
exception
Code:
con =
DriverManager.getConnection(dbDetails.getURL(),dbDetails.getUserName(),dbDetails.getPassword());
Exception:
java.lang.StringIndexOutOfBoundsException: String index out of range: 7
at java.lang.String.substring(Unknown Source)
at org.apache.derby.client.am.ProductLevel.<init>(Unknown Source)
at org.apache.derby.client.net.NetDatabaseMetaData.<init>(Unknown Source)
at
org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetDatabaseMetaData(Unknown
Source)
at org.apache.derby.client.net.NetConnection.newDatabaseMetaData_(Unknown
Source)
at org.apache.derby.client.am.Connection.completeConnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.completeConnect(Unknown
Source)
at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
at
org.apache.derby.client.net.ClientJDBCObjectFactoryImpl.newNetConnection(Unknown
Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
When traced inside the code it was the problem with the product id being
different whenever this issue occurs, I found three different product id's
generated by derby on different startups.
1. CSS10020
2. CSS020 -- When the product id has this value, it throws exceptions.
I printed the product id inside ProductLevel file of Derby. And eeven with
"networkservercontrol sysinfo" command it differed
About my setup:
--------- Derby Network Server Information --------
Version: CSS10020/10.2.2.0 - (485682) Build: 485682 DRDA Product Id:
CSS10020
-- listing properties --
derby.drda.traceDirectory=C:\LocalReposCVS\BTI\BTI_EMS_Windows\...
derby.drda.maxThreads=0
derby.drda.keepAlive=true
derby.drda.minThreads=0
derby.drda.portNumber=1527
derby.drda.logConnections=false
derby.drda.timeSlice=0
derby.drda.startNetworkServer=false
derby.drda.host=localhost
derby.drda.traceAll=false
------------------ Java Information ------------------
Java Version: 1.5.0_10
Java Vendor: Sun Microsystems Inc.
Java home: C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\jre1.5.0_10
Java classpath:
;C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\bin\\..\jre1.5.0_10\lib\tools.jar;C:\LocalReposCVS\BTI\BTI_EM
calReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\bin\\..\bin\startup.jar;C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\bin\\..\bin\mig
EMS_Windows\BTI\EMS\bin\\..\server\ems\lib\mysql-connector-java-3.0.17-ga-bin.jar;C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\E
r;C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\bin\\..\server\ems\lib\derbyclient.jar;C:\LocalReposCVS\BTI\BTI_EMS_Windows\B
et.jar;C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\bin\\..\server\ems\lib\sqljdbc.jar;C:\LocalReposCVS\BTI\BTI_EMS_Windows\
ix32.jar
OS name: Windows XP
OS architecture: x86
OS version: 5.1
Java user name: umakanth
Java user home: C:\Documents and Settings\umakanth
Java user dir: C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\bin
java.specification.name: Java Platform API Specification
java.specification.version: 1.5
--------- Derby Information --------
JRE - JDBC: J2SE 5.0 - JDBC 3.0
[C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\server\ems\lib\derby.jar]
10.2.2.0 - (485682)
[C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\server\ems\lib\derbynet.jar]
10.2.2.0 - (485682)
[C:\LocalReposCVS\BTI\BTI_EMS_Windows\BTI\EMS\server\ems\lib\derbyclient.jar]
10.2.2.0 - (485682)
Any help would be appreciated
--
View this message in context: http://www.nabble.com/Product-Id-issue-tf3722284.html#a10415553
Sent from the Apache Derby Developers mailing list archive at Nabble.com.
Re: Product Id issue
Posted by Umakanth Srinivasan <ka...@dhyanit.com>.
On further analysis of the code I found that the server is started in Network
mode. And network mode has this issue. I switched to embeded mode and
everything works as expected. Sorry for anyone's time on this.
--
View this message in context: http://www.nabble.com/Product-Id-issue-tf3722284.html#a10547906
Sent from the Apache Derby Developers mailing list archive at Nabble.com.