topic Re: SQLNonTransientConnectionException connecting to Derby in Talend Studio

SQLNonTransientConnectionException connecting to Derby

Anonymous — Fri, 31 Jan 2014 22:32:09 GMT

Hi,
I'm trying to set up my first migration job, moving the contents of a single table from Derby v 1.5 to MS SQL server.
The table schemas are the same. I can connect to Derby with the Client driver, and retrieve the table schema without error. All of the steps in configuring the job seem to work perfectly, including setting-up the tMap.
I originally tried this with v 5.3.2, and tried today with 5.4.1 with the same result. I have tried swapping (known good) Derby drivers into the system, but nothing seems to have any effect.
Every time I try to run the job, I get
Starting job migrate at 16:39 31/01/2014.
connecting to socket on port 3931
connected
Apache Derby Network Server - 10.4.1.3 - (648739) started and ready to accept connections on port 1527 at 2014-01-31 21:39:50.672 GMT
Exception in component tJavaDBInput_1
java.sql.SQLNonTransientConnectionException: The connection was refused because the database CMDB was not found.
at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(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)
at cm1migration.migrate_0_1.migrate.tJavaDBInput_1Process(migrate.java:1781)
at cm1migration.migrate_0_1.migrate.runJobInTOS(migrate.java:3179)
at cm1migration.migrate_0_1.migrate.main(migrate.java:3044)
Caused by: org.apache.derby.client.am.DisconnectException: The connection was refused because the database CMDB was not found.
at org.apache.derby.client.net.NetConnectionReply.parseRDBNFNRM(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(Unknown Source)
disconnected
at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(Unknown Source)
at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)
at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown Source)
... 6 more
Job migrate ended at 16:39 31/01/2014.
I'd be grateful for any tips.
Thanks!

Re: SQLNonTransientConnectionException connecting to Derby

Anonymous — Fri, 31 Jan 2014 22:51:08 GMT

The error message does not point to a problem caused by a version mismatch. It looks like the connection parameters are not OK. If you export+import a job sometimes you can run into trouble because of the not correct transfer of context parameters. Setup the tJavaDBInput component for the test by hand with the correct values and test the connection again.

Re: SQLNonTransientConnectionException connecting to Derby

Anonymous — Tue, 04 Feb 2014 17:04:33 GMT

Thanks for taking the time to reply, Jlolling.
I have set-up the component by hand each time (many times.) In fact, I have not tried exporting/importing a job config.
With the configuration I'm using, I can connect and retrieve the schema, configure a tMap and tConvertType component, and everything appears to work properly. But when I run the job, I get the error above.
I have repeated this process many times, setting-up the job by hand, from scratch, each time.
Do you have any other suggestions? I've attached a screenshot of my DB Connection config.
Thanks again,
cleger

Re: SQLNonTransientConnectionException connecting to Derby

Anonymous — Thu, 20 Feb 2014 21:21:55 GMT

Once more, for what it's worth... as you can see, I can connect sufficient to retrieve the schema, and it appears when running the job, it connects initially.
I'd appreciate any thoughts.
Thanks!
cjl