JDBC connection to Teradata

[Scott Smith]

I am using a Teradata type 2 driver on Solaris, and I have a java command-line application
that connects to our Teradata DB through the driver just fine. When I try to execute
the same code in a Servlet through weblogic using the same user account on the same
box, I get an error from the driver (see stack trace below). I also tried this on
Tomcat 4.0.3 and it still failed. Anyone have any ideas? I have written lots of
Servlet code and JDBC code in the past and I am pretty sure my code is good, but
I am open to suggestions.....please let me know if you have an idea.

java.sql.SQLException: [NCR][Teradata CLIv2] : MTDP: EM_NETCONN(207): Error in doing
a network connect.
at com.ncr.teradata.ComUtil.ThrowExcp(Unknown Source)
at com.ncr.teradata.TeraDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at com.hallmark.bricksclicks.Concept.getConnection(Concept.java:535)
at com.hallmark.bricksclicks.Concept.execQuery1(Concept.java:331)
at com.hallmark.bricksclicks.TeraServlet.doPost(TeraServlet.java:98)
at com.hallmark.bricksclicks.TeraServlet.doGet(TeraServlet.java:57)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

[Joseph Weinstein]

It is possibly that the teradata driver is not threadsafe.

[Larry Presswood]

I have done some work with NCR teradata's jdbc driver about a 1.5 yrs ago and
it was not thread safe. We had to do our own connection pool based upon its
limitations.

Perhaps if you turn off statement caching etc on the weblogic pools that might
work. The guys at BEA would be able to tell what if anything you can do
from a configuration standpoint to deal with drivers which are not threadsafe.