Repost: ClassNotFoundException: weblogic/jdbc/pool/Driver

          Hi,
          I was able to run the sql example in the jsp\tagext directory. The ConnectionTag tag contains basically code like:
          Class.forName("weblogic.jdbc.pool.Driver").newInstance();
          which works fine.
          Next, I moved the code into a utility package, which I compiled into the public_html\WEB-INF\classes directory. This code is called from within a servlet.
          Strangely enough, when I run the servlet, I get the ClassNotFoundException: weblogic/jdbc/pool/Driver error. It is as if the servlet does not have access to the weblogic.jdbc.pool.Driver class while the tag library does.
          What am I doing wrong?
          Thanks, Vladimir

Similar Messages

ClassNotFoundException: weblogic/jdbc/pool/Driver

          Hi,
          I was able to run the sql example in the jsp\tagext directory.
          The ConnectionTag tag contains basically code like:
          Class.forName("weblogic.jdbc.pool.Driver").newInstance();
          which works fine.
          Next, I moved the code into a utility package, which I
          compiled into the public_html\WEB-INF\classes directory. This
          code is called from within a servlet.
          Strangely enough, when I run the servlet, I get the
          ClassNotFoundException: weblogic/jdbc/pool/Driver error.
          It is as if the servlet does not have access to the
          weblogic.jdbc.pool.Driver class while the tag library does.
          What am I doing wrong?
          Thanks,
          Vladimir


You must include the path to jdbc driver in the script wich you start the
          server.
          WEBLOGIC_CLASSPATH
          vladimir <[email protected]> escribió en el mensaje de noticias
          39bcdf0c$[email protected]..
          >
          > Hi,
          >
          > I was able to run the sql example in the jsp\tagext directory.
          > The ConnectionTag tag contains basically code like:
          >
          > Class.forName("weblogic.jdbc.pool.Driver").newInstance();
          >
          > which works fine.
          >
          > Next, I moved the code into a utility package, which I
          > compiled into the public_html\WEB-INF\classes directory. This
          > code is called from within a servlet.
          >
          > Strangely enough, when I run the servlet, I get the
          > ClassNotFoundException: weblogic/jdbc/pool/Driver error.
          > It is as if the servlet does not have access to the
          > weblogic.jdbc.pool.Driver class while the tag library does.
          >
          > What am I doing wrong?
          >
          > Thanks,
          > Vladimir
          >

Connection Pool using weblogic.jdbc.pool.Driver

I am trying to use connection pooling in my JSP data access classes (which
work fine without connection pooling) on weblogic 4.5.1. I tried using the
weblogic.jdbc.pool.Driver but it exits with the following exception:
java.lang.ClassNotFoundException: weblogic.jdbc.pool.Driver
The path c:\weblogic\classes which contains this driver is specified in the
weblogic.class.path . I can not include it in the java class path because
then weblogic server fails to start at all (with an error message). I would
appreciate any help !
Thanks,
Usamah

Hi. Please don't repost identical posts to different news groups. See a response
in the JDBC group. thanks, joe
Usamah Malik wrote:
I am trying to use connection pooling in my JSP data access classes (which
work fine without connection pooling) on weblogic 4.5.1. I tried using the
weblogic.jdbc.pool.Driver but it exits with the following exception:
java.lang.ClassNotFoundException: weblogic.jdbc.pool.Driver
The path c:\weblogic\classes which contains this driver is specified in the
weblogic.class.path . I can not include it in the java class path because
then weblogic server fails to start at all (with an error message). I would
appreciate any help !
Thanks,
Usamah--
PS: Hey folks, we're hiring Java engineers for our WebLogic
Engineering group in downtown S.F. Send me your resume.
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application Server
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a Component Architecture
http://weblogic.beasys.com/press/awards/index.htm

Java.lang.ClassNotFoundException: weblogic/jdbc/mssqlserver4/Driver

Hello,
I am moving my database from Sybase to SQL Server. I have a program that ran fine with JConnect driver (Sybase) on both unix and windows. But now when I try to use the weblogic driver to connect to SQL Server the program fails. I am 100% positive that the weblogic drive is in the classpath. Whether the weblogic drive is in the classpath or not I get the same error:
Unexpected error:java.lang.ClassNotFoundException: weblogic/jdbc/mssqlserver4/Driver
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:124)
at com.trilogy.tools.core.DBUtil.loadDriver(DBUtil.java:16)
at com.trilogy.loader.core.LoadInitUtil.<init>(Compiled Code)
at com.trilogy.loader.mass.MassInitUtil.<init>(MassInitUtil.java:15)
at com.trilogy.loader.mass.Loader2CLI.execute(Compiled Code)
at com.trilogy.tools.core.CLIBase.execute(CLIBase.java:45)
at com.trilogy.loader.mass.Loader2CLI.main(Loader2CLI.java:805)
java.lang.NullPointerException
at com.trilogy.loader.mass.Loader2CLI.execute(Compiled Code)
at com.trilogy.tools.core.CLIBase.execute(CLIBase.java:45)
at com.trilogy.loader.mass.Loader2CLI.main(Loader2CLI.java:805)
Pease help me fix this problem. I am not sure why the weblogic driver is not working. Thanks.

The error message says it can't find a class named "weblogic.jdbc.mssqlserver4.Driver". That looks rather odd to me.
Are you sure that you defined the connection information correctly in the configuration file?

What jar contains weblogic.jdbc.pool.Driver connection pool class?

Hi all,
I am trying to use the JDeveloper IDE to generate code that I'll deploy on WebLogic
6.1.
I want to add the necessary files to the JDeveloper classpath so that during development
it can use my
weblogic connection pool. I've looked all over and can't seem to find it. It's
not in weblogic.jar. Anyone know
what file contains weblogic.jdbc.pool.Driver?
Thanks in advance,
Norm

Thanks. I don't know how I missed it in the first place.
"Sree Bodapati" <[email protected]> wrote:
weblogic.jar
sree
"Norm Heske" <[email protected]> wrote in message
news:3ba246c2$[email protected]..
Hi all,
I am trying to use the JDeveloper IDE to generate code that I'll deployon
WebLogic
6.1.
I want to add the necessary files to the JDeveloper classpath so thatduring development
it can use my
weblogic connection pool. I've looked all over and can't seem to findit.
It's
not in weblogic.jar. Anyone know
what file contains weblogic.jdbc.pool.Driver?
Thanks in advance,
Norm

Java.io.notSerializableException:weblogic.jdbc.pool.Connection

Hello,
          In my servelts only sometime I get this exception. I am using WLS7.0 jDK
          1.3.1(the one which comes with WLS7.0). I am using Java Beans which are all
          serializable.(I have declared that the classes implements Serilizable)
          Exception is as follows
          <Jan 27, 2003 4:19:09 AM EST> <Error> <HTTP Session> <triton>
          <AccupacServer> <ExecuteThread: '8' for queue: 'default'> <kernel identity>
          <> <100028> <Could not deserialize session data>
          java.io.NotSerializableException: weblogic.jdbc.pool.Connection
          at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
          at
          java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
          at
          java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
          at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1209)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
          at
          weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:9
          1)
          at
          weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:6
          6)
          at
          weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.ja
          va:570)
          at
          weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.ja
          va:552)
          at
          weblogic.servlet.internal.session.SessionData.remove(SessionData.java:734)
          at
          weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(Mem
          orySessionContext.java:51)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator$Invalida
          tionAction.run(SessionContext.java:523)
          at
          weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
          r.java:744)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.cleanupE
          xpiredSessions(SessionContext.java:444)
          at
          weblogic.servlet.internal.session.SessionContext.deleteInvalidSessions(Sessi
          onContext.java:81)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
          SessionContext.java:392)
          at
          weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:181
          at
          weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
          r.java:744)
          at
          weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
          er.java:167)
          at
          weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
          :161)
          at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:38)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
          Any help appreciated.
          Thanks
          Madhu


Hello,
          In my servelts only sometime I get this exception. I am using WLS7.0 jDK
          1.3.1(the one which comes with WLS7.0). I am using Java Beans which are all
          serializable.(I have declared that the classes implements Serilizable)
          Exception is as follows
          <Jan 27, 2003 4:19:09 AM EST> <Error> <HTTP Session> <triton>
          <AccupacServer> <ExecuteThread: '8' for queue: 'default'> <kernel identity>
          <> <100028> <Could not deserialize session data>
          java.io.NotSerializableException: weblogic.jdbc.pool.Connection
          at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
          at
          java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
          at
          java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
          at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1209)
          at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
          at
          weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:9
          1)
          at
          weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:6
          6)
          at
          weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.ja
          va:570)
          at
          weblogic.servlet.internal.session.SessionData.removeAttribute(SessionData.ja
          va:552)
          at
          weblogic.servlet.internal.session.SessionData.remove(SessionData.java:734)
          at
          weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(Mem
          orySessionContext.java:51)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator$Invalida
          tionAction.run(SessionContext.java:523)
          at
          weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
          r.java:744)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.cleanupE
          xpiredSessions(SessionContext.java:444)
          at
          weblogic.servlet.internal.session.SessionContext.deleteInvalidSessions(Sessi
          onContext.java:81)
          at
          weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
          SessionContext.java:392)
          at
          weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:181
          at
          weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
          r.java:744)
          at
          weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
          er.java:167)
          at
          weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
          :161)
          at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:38)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
          Any help appreciated.
          Thanks
          Madhu

Jbuilder & weblogic.jdbc.mssqlserver4.Driver

I use jbuilder8 and jdbc driver " weblogic.jdbc.mssqlserver4.Driver " to connect mssql2000..
when I use database pilot of jbuilder8 to setup a datasource..
I got an error Error " connecting to database: java.lang.NoClassDefFoundError: weblogic/version "
what should I do now ?..

Do you have weblogic.jar in your CLASSPATH?
"owner" <[email protected]> wrote in message news:[email protected]..
I use jbuilder8 and jdbc driver " weblogic.jdbc.mssqlserver4.Driver " to connect mssql2000..
when I use database pilot of jbuilder8 to setup a datasource..
I got an error Error " connecting to database: java.lang.NoClassDefFoundError: weblogic/version "
what should I do now ?..

ClassNotFoundException using jdbc thin driver & JDK 1.2.2

Hi
I have written an applet to connect to an Oracle 8.0 Data Base
using the OracleDriver.class, and compiled it using JDK1.1.8.
However, when I switched to the later JDK1.2.2 (to use the swing
libraries) I found that I could no longer use the Oracle
Driver. I get an error:
java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
I know that my ClassPath is set correctly, so can anyone suggest
the cause?
Regards,
Rich
null

Rich (guest) wrote:
: Hi
: I have written an applet to connect to an Oracle 8.0 Data Base
: using the OracleDriver.class, and compiled it using JDK1.1.8.
: However, when I switched to the later JDK1.2.2 (to use the
swing
: libraries) I found that I could no longer use the Oracle
: Driver. I get an error:
: java.lang.ClassNotFoundException:
oracle.jdbc.driver.OracleDriver
: I know that my ClassPath is set correctly, so can anyone
suggest
: the cause?
: Regards,
: Rich
I had to unzip the file and then it worked.
null

Weblogic Pool Driver doesn't support XA driver

          I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store uses the Oracle
          XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen the JMS server
          starts it gives me the following exception: Weblogic Pool Driver doesn't support
          XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2. THe full error
          trace is shown below:
          <Jan 15, 2004 3:05:09 PM EST> <Alert> <JMS> <BEA-040052> <JMSServer "jmsTestJmsServer1"
          store failed to open java.io.IOException: JMS JDBC store, connection pool = <jmsTestJdbcConnectionPool>,
          prefix = <JMS1>: cannot determine DBMS type
          <java.sql.SQLException: Pool connect failed : java.lang.Exception: Weblogic Pool
          Driver doesn't support XA driver, Please change your config to use a Non-XA driver
          <     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:160)
          <     at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
          <     at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBCIOStream.java:1490)
          <     at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:420)
          <     at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          <     at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          <     at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          <     at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          <     at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
          <     at weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)
          <     at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
          <     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          <     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          <     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          <     at java.lang.reflect.Method.invoke(Method.java:324)
          <     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          <     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          <     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
          <     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          <     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          <     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          <     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          <     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          <     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          <     at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
          <     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
          <     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
          <     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          <     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
          <     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
          <     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
          <     at weblogic.Server.main(Server.java:32)


          It appears that WebLogic 8.1 does not have the "user transactions enabled" flag
          for a connection factory. I see references to this flag in earlier versions of
          WebLogic. The closest thing in WL 8.1 seems to be the "XA Connection Factory Enabled"
          flag.
          Tom Barnes <[email protected]> wrote:
          >Actually, all you normally need to check is "user transactions enabled".
          >The XA versions of the javax.jms interfaces (which are generated
          >via XA connection factories) are not required - except
          >that I think that MDBs make a check for this.
          >
          >Naresh Bhatia wrote:
          >> So I assume that the XA capability is enabled by checking the "XA Connection
          >Factory
          >> Enabled" checkbox for the JMS connection factory.
          >>
          >> Thanks.
          >> Naresh
          >>
          >> Tom Barnes <[email protected]> wrote:
          >>
          >>>Just use a non-XA driver and non-XA pool for JMS JDBC stores.
          >>>WL JMS' XA capability does not come from its JDBC driver.
          >>>
          >>>Naresh Bhatia wrote:
          >>>
          >>>
          >>>>I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store
          >>>
          >>>uses the Oracle
          >>>
          >>>>XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen
          >>>
          >>>the JMS server
          >>>
          >>>>starts it gives me the following exception: Weblogic Pool Driver doesn't
          >>>
          >>>support
          >>>
          >>>>XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2.
          >THe
          >>>
          >>>full error
          >>>
          >>>>trace is shown below:
          >>>>
          >>>><Jan 15, 2004 3:05:09 PM EST> <Alert> <JMS> <BEA-040052> <JMSServer
          >>>
          >>>"jmsTestJmsServer1"
          >>>
          >>>>store failed to open java.io.IOException: JMS JDBC store, connection
          >>>
          >>>pool = <jmsTestJdbcConnectionPool>,
          >>>
          >>>>prefix = <JMS1>: cannot determine DBMS type
          >>>><java.sql.SQLException: Pool connect failed : java.lang.Exception:
          >>>
          >>>Weblogic Pool
          >>>
          >>>>Driver doesn't support XA driver, Please change your config to use
          >>>
          >>>a Non-XA driver
          >>>
          >>>><     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:160)
          >>>><     at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
          >>>><     at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBCIOStream.java:1490)
          >>>><     at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:420)
          >>>><     at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          >>>><     at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          >>>><     at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          >>>><     at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          >>>><     at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
          >>>><     at weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)
          >>>><     at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
          >>>><     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          >>>><     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          >>>><     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          >>>><     at java.lang.reflect.Method.invoke(Method.java:324)
          >>>><     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          >>>><     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          >>>><     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
          >>>><     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          >>>><     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          >>>><     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >>>><     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >>>><     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          >>>><     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >>>><     at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
          >>>><     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
          >>>><     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
          >>>><     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          >>>><     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
          >>>><     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
          >>>><     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
          >>>><     at weblogic.Server.main(Server.java:32)
          >>>>
          >>>
          >>
          >

Web Logic 6.1 JDBC Pooling with the Oracle Thin Driver

Hi,
We're slowly getting through a WebLogic 4.5.1 to 6.1 conversion for a small application
at my company. Initially, we had trouble getting the Oracle thin driver working.
We've finally cracked this nut. Now we're trying to get pooling working, and
cannot find an example of doing this with the Oracle thin driver.
Would anyone be able to provide:
1. the portion of the config.xml that pertains to building a connection pool using
the Oracle thin driver
2. the two lines of code for loading the driver and getting a connection from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Thanks very much!
Jeff Ryan
The Hartford

"Jeff Ryan" <[email protected]> wrote:
>
1. the portion of the config.xml that pertains to building a connection
pool using
the Oracle thin driver
You don't usually edit the config.xml unless it is absolutely necessar. Instead,
you can config the pool in the GUI admin console, quite easily. After you successfully
configed the pool in the console, it is written into the config.xml file for you.
Only thing special when config the pool is the name of the driver and the url.
url: jdbc:oracle:thin@dbhost:dbport:dbinstance
driver: oracle.jdbc.driver.OracleDriver
If you prefer, you can also config the pool from the command line. It is detailed
in the "Weblogic Server Command-line Interface Reference".
2. the two lines of code for loading the driver and getting a connection
from
this pool
i.e.
Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection c = d.connect("jdbc:weblogic:pool:myPool", null);
Again, you don't use the connection directly. Instead, you use "Data Source".
Data source in weblogic is just a connection object factory associated with a
JNDI name. You can therefore lookup the data source with the JNDI name and from
the data source object, you get the connectin object. No need to explicitly load
the driver class.
There are plenty of example codes available in the weblogic examples installed
with 6.1, that uses the data source.
Charles

Error While reading CLOB from Oracle using WebLogic Connection Pool, Works fine with out using pool

PROBLEM DESCRIPTION :
     When I try to read a clob from Oracle, I receive "ORA-03120: two-task
conversion routine: integer overflow" Error.
     This error occurs only for CLOB Type and only if I try to connect to
Oracle using WebLogic JDriver/Oracle POOL.
     IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
connection to ORacle with out any problem.
     Below Please find the JAVA CODE for Both Working and NON Working .
Created a Connection Pool as:
Name: MyJDBCConnectionPool
URL : jdbc:weblogic:oracle
DIRVER:weblogic.jdbc.oci.Driver
NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
Driver myDriver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection mconn =
myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
Driver myDriver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection mconn =
myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
ERROR MESSAGE:
     ORA-03120: two-task conversion routine: integer overflow
I appreciate your help on this problem.

PROBLEM DESCRIPTION :
     When I try to read a clob from Oracle, I receive "ORA-03120: two-task
conversion routine: integer overflow" Error.
     This error occurs only for CLOB Type and only if I try to connect to
Oracle using WebLogic JDriver/Oracle POOL.
     IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
connection to ORacle with out any problem.
     Below Please find the JAVA CODE for Both Working and NON Working .
Created a Connection Pool as:
Name: MyJDBCConnectionPool
URL : jdbc:weblogic:oracle
DIRVER:weblogic.jdbc.oci.Driver
NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
Driver myDriver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection mconn =
myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
Driver myDriver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection mconn =
myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
ERROR MESSAGE:
     ORA-03120: two-task conversion routine: integer overflow
I appreciate your help on this problem.

Connect to WebLogic connection pool externally?

Running Oracle 8i (thin driver) & WL 5.1
I can connect directly to the db using
public class TestDB
     String dbURL = "jdbc:oracle:thin:@p1900:1521:p1900";
     String dbDriver = "oracle.jdbc.driver.OracleDriver";
     public boolean connect()
     Class.forName(this.getDbDriver());
     System.err.println("Driver load ok");
     dbConn = DriverManager.getConnection(this.getDbURL());
     System.err.println("Connected ok");
return true;
but is it possible to connect to WL connection pool from a program
thats not within the WL server (i.e no problem from a servlet)?
This is from weblogic.properties -
weblogic.jdbc.connectionPool.hazardouswaste=\
url=jdbc:oracle:thin:@p1900:1521:p1900,\
driver=oracle.jdbc.driver.OracleDriver,\
initialCapacity=1,\
maxCapacity=1,\
capacityIncrement=1,\
props=user=tact_dev;password=tact_dev,\
allow=guest
How can I get a conection from the hazardouswaste connection pool?
I've tried this but it
String dbURL = "jdbc:weblogic:pool:hazardouswaste";
String dbDriver = "weblogic.jdbc.pool.Driver";
I keep getting this -
return getDbURL - jdbc:weblogic:pool:hazardouswaste
java.sql.SQLException: Pool connect failed: null
at weblogic.jdbcbase.pool.Driver.connect(Driver.java:184)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:199)
at jsp_servlet.TestDB.connect(TestDB.java:62)
at jsp_servlet.Test.main(Test.java:16)
Any ideas
harry

[att1.html]

WebLogic中SQL Server2000的JDBC Pool配置

一、采用Microsoft的JDBC Driver
1 到www.microsoft.com上下载“Microsoft SQL Server 2000 Driver for
JDBC”并安装
2 安装后，在安装的目录中有三个jar文件包
msbase.jar
msutil.jar
mssqlserver.jar
建议将其拷贝出来放置到%WL_HOME%\server\lib目录中（其实随意，但附后的
classpath中要指明）
3 将3个jar包加入到classpath中，改startWLS.cmd，“set CLASSPATH=”后插
入%WL_HOME%\server\lib\msbase.jar;%WL_HOME%\server\lib\msutil.jar;%
WL_HOME%\server\lib\mssqlserver.jar;
4 确认MSSQLServer的端口号（这点比较重要）
And to find the port number where your instance is running, run the
server network utility and select the server instance and select the
TCP/IP. When you click the properties button, it will show the port.
5 启动WebLogic
6 打开IE，在地址栏中输入：http://localhost:7001/console
7 输入用户名和密码
8 在左边的目录树中选中Services->JDBC->Connection Pools，单击右侧的
Configure a new JDBC Connection Pool.，输入以下信息：
Configuration->General页：
Name = MSSQLServerConnectionPool
URL = jdbc:microsoft:sqlserver://localhost:2040 (注意端口号填第5步中
看到的port)
Driver classname =com.microsoft.jdbc.sqlserver.SQLServerDriver
Properties :
databasename= northwind
user = sa
password = <- sa的密码
单击Create建立连接池。
9 Connection属性设置
Configuration->Connections页：
将Initial Capacity由1置为10 （视需求）
将Maximum Capacity由1置为10（视需求）
10 Targets->Server页：
将myserver(服务器名称)移至右侧的列表中，但击单击Apply
11 配置数据源
．在左边的目录树中选中Services->JDBC->Data Sources（或者TXData
Sources），单击右侧的Configure a new JDBC Connection Pool.，输入以下信
息：
Configuration->General页：
Name ＝ SQLServer Tx Data Source
JNDI Name ＝ SQLServer
Pool Name = MSSQLServerConnectionPool
选中Emulate Two-Phase Commit for non-XA Driver和Row Prefetch Enabled
单击Create建立数据源。
12 Targets->Server页：
将myserver(服务器名称)移至右侧的列表中，但击单击Apply，配置完毕。
13 reboot server
二、采用WebLogic的JDBC Driver for SQL Server
1确认MSSQLServer的端口号（这点比较重要）
And to find the port number where your instance is running, run the
server network utility and select the server instance and select the
TCP/IP. When you click the properties button, it will show the port.
2 启动WebLogic
3 打开IE，在地址栏中输入：http://localhost:7001/console
4 输入用户名和密码
5 在左边的目录树中选中Services->JDBC->Connection Pools，单击右侧的
Configure a new JDBC Connection Pool.，输入以下信息：
Configuration->General页：
Name = WLSQLServerConnectionPool
URL = jdbc:weblogic:mssqlserver4:northwind@localhost:2040
Driver classname = weblogic.jdbc.mssqlserver4.Driver
Properties :
user = sa
password = <- sa的密码
单击Create建立连接池。
6 Connection属性设置
Configuration->Connections页：
将Initial Capacity由1置为10 （视需求）
将Maximum Capacity由1置为10（视需求）
7 Targets->Server页：
将myserver(服务器名称)移至右侧的列表中，但击单击Apply
8 配置数据源
．在左边的目录树中选中Services->JDBC->Data Sources（或者TXData
Sources），单击右侧的Configure a new JDBC Connection Pool.，输入以下信
息：
Configuration->General页：
Name ＝ SQLServer Tx Data Source
JNDI Name ＝ SQLServer
Pool Name = WLSQLServerConnectionPool
选中Emulate Two-Phase Commit for non-XA Driver和Row Prefetch Enabled
单击Create建立数据源。
9 Targets->Server页：
将myserver(服务器名称)移至右侧的列表中，但击单击Apply，配置完毕。
10 reboot server
附注：如果你的WebLogic server和sql server2k不在同一台机器的话，sql
server2k的安全认证方式要选成sql server and windows（不选window

上面的配置文档很不错，不过个人建议，在采用 ms sql server数据库的系统，
尽量不要使用weblogic jDriver或ms mssql driver。原因如下：
（1）在以后的版本中，weblogic 将不再对jDriver of mssql server进行支持
（1）ms mssql driver对于Image和text类型（也就是blob和clob类型）的数据
查询，支持不好。
所以，尽量采用第三方的ms sql server driver。

How can i use the weblogic jdbc driver for sqlserver?

hello
i have downloaded and installed the weblogic on my windows2000 server,then i want to use the weblogic jdbc driver for sqlserver2000 outside of the weblogic,as follow:
1 add following string to my classpath environment of the wndows2000: E:\bea\wlserver6.1\lib\mssqlserver4v65.jar
2 then i write a test program as:
import weblogic.jdbc.mssqlserver4.Driver;
import java.sql.*;
public class test{
public static void main(String argv[]){
try{ Class.forName("weblogic.jdbc.mssqlserver4.Driver");
Connection
conn=DriverManager.getConnection"jdbc:weblogic:mssqlserver4:localhost:1433","sa",""); }catch(Exception e){ System.out.println(e.getMessage()); }
4 when i execute it,it throw a exception:
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/version at weblogic.jdbc.mssqlserver4.TdsStatement.getLicenseStr(TdsStatement.java:2665) at weblogic.jdbc.mssqlserver4.TdsStatement.microsoftLogin(TdsStatement.java:2474) at weblogic.jdbc.mssqlserver4.MicrosoftConnection.beginLogin(MicrosoftConnection.java:42) at weblogic.jdbc.mssqlserver4.TdsConnection.login(TdsConnection.java:57) at weblogic.jdbc.mssqlserver4.MicrosoftConnection.login(MicrosoftConnection.java:53) at weblogic.jdbc.mssqlserver4.BaseConnection.prepareConnection(BaseConnection.java:187) at weblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:34) at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:151) at java.sql.DriverManager.getConnection(DriverManager.java:517) at java.sql.DriverManager.getConnection(DriverManager.java:177) at test.main(test.java:7)
who can help me?thank you!

Hi,
Mail me the jar file as I am using Weblogic 6.1 to my email id [email protected]
Else tell me the site from where u have downloaded and i will do the same.
I will test the same and let you know.
Thanks,
Seetesh

Having problems with new WebLogic MS SQL driver WLS 8.1

Hi,
We've recently migrated our application from WLS 6.1 to WLS 8.1. We use an MS SQL database. In 6.1 we used the (now deprecated) weblogic.jdbc.mssqlserver4.Driver driver. In 8.1 we now use the new weblogic.jdbc.sqlserver.SQLServerDriver driver. We now are seeing NullPointerExceptions with the new driver that we never saw when running in 6.1 (with the old driver). The exception is occuring at the driver level. I'll paste some of the stack traces below but here is a quick synopsis of our usage pattern:
-standard get-use-close pattern on the connection for each request (connection is closed in finally block).
-pool size: min 1, max 7, increment 5
-test on reserver enabled
-we are simply reading data (no updates)
-we use a single thread that hits the database so there is only ever one active application thread hitting the DB.
-we are using a stored proc.
-we setTimeout on the statement (initial testing seems to indicate that query timeout seems to be at the root of the problem)
The problem seems to occur when statement timeouts occur. I can recreate the problem by setting the statement timeout to 1 sec and throwing a lot data at the DB. What seems to occur is a query hits the timeout and a SocketException is thrown, subsequent queries then throw a NullPointer in the driver layer. Again, this is the behavior under WLS 8.1 with the new weblogic.jdbc.sqlserver.SQLServerDriver driver. If I use the old driver (weblogic.jdbc.mssqlserver4.Driver) under WLS 8.1 all I get is the SocketException (which is what I want). This application ran under WLS 6.1 with the old driver processing millions of queries without any problems.
We are wondering:
(1) Is this a known problem?
(2) Is there a recommended workaround?
Cheers, and as always thanks in advance for any help.
Stack traces follow.
Thank,
Mich
Here are some failure traces from the WLS 8.1 new driver:
java.sql.SQLException: [BEA][SQLServer JDBC Driver]Execution timeout expired.
     at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
     at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
     at weblogic.jdbc.base.BaseStatement.postProcessExceptionFromCommonExecute(Unknown Source)
     at weblogic.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
     at weblogic.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
     at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)
     at com.our.QueryHandler.execute(QueryHandler.java:79)
THEN WHEN A SUBSEQUENT QUERY IS MADE:
java.lang.NullPointerException
     at weblogic.jdbc.sqlserver.tds.TDSRequest.switchColumnDescriptions(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRequest.processRow(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRPCNonCursorExecuteRequest.submitPrepare(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRPCExecuteRequest.doPrepExec(Unknown Source)
     at weblogic.jdbc.sqlserver.tds.TDSRPCExecuteRequest.execute(Unknown Source)
     at weblogic.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown Source)
     at weblogic.jdbc.base.BaseStatement.commonExecute(Unknown Source)
     at weblogic.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
     at weblogic.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
     at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)
     at com.our.QueryHandler.execute(QueryHandler.java:79)
Just to be complete here is the stacktrace generated by a timeout using the old driver on WLS 8.1 (again, this one behaves as expected):
weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server, java.net.SocketTimeoutException: Read timed out
     at weblogic.jdbc.mssqlserver4.TdsStatement.getMoreResults(TdsStatement.java:813)
     at weblogic.jdbc.mssqlserver4.TdsStatement.execute(TdsStatement.java:210)
     at weblogic.jdbc.mssqlserver4.TdsStatement.executeQuery(TdsStatement.java:54)
     at weblogic.jdbc.mssqlserver4.TdsStatement.executeQuery(TdsStatement.java:1424)
     at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)

Michel Crichton wrote:
Hi,
Thanks for the prompt reply. In answer to your questions:
What I would like to know is the exact code/sequence that causes the subsequent exception. See the sequence of calls at the end of this reply.
Is this in the same thread in the very next call?
I replicated the problem by going through the Web container (5 clients) therefore WebLogic threads are used in this case. I see from the logs 4-5 different execute threads at work (ex. ExecuteThread: '10' for queue: 'weblogic.kernel.Default').
Does it happen all the time?
Although it is tough to tell for sure, once it starts happening it seems to happen most if not all the time.
Is it an attempted re-use of the same statement, or trying to use a different statement?
We do a connection.prepareStatement(QUERY_STRING) call everytime (there is only one per request/response cycle). I believe WLS caches statements behind the scenes though so I suspect at that level there is reuse. There is only one stored proc used (we vary the params per call).
Please show me your pool definition from the config.xml
file, and I will send you instructions to produce some
debug info that will get us to the heart of this matter.
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
MaxCapacity="5" Name="THE POOL"
PasswordEncrypted="XXX"
Properties="user=XXX;portNumber=XXX;databaseName=XX;serverName=X.X.X.X"
Targets="Server"
TestConnectionsOnReserve="true" TestTableName="TEST_TABLE" URL="jdbc:bea:sqlserver://X.X.X.X:XXX"/>Ok, do these things:
1 - Add our spy attribute to your pool definition, like this:
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
MaxCapacity="5" Name="THE POOL"
PasswordEncrypted="XXX"
Properties="user=XXX;portNumber=XXX;databaseName=XX;serverName=X.X.X.X"
Targets="Server"
TestConnectionsOnReserve="true"
TestTableName="TEST_TABLE"
URL="jdbc:bea:sqlserver://X.X.X.X:XXX;spyAttributes=(log=(file)spy.log;timestamp=yes)"/>
2 - Edit the start-weblogic script to add the spy jar (wlspy.jar) to the
classpath that the script creates for the server, eg:
set CLASSPATH=%WL_HOME%\server\lib\wlspy.jar;%CLASSPATH%
3 - Reboot and duplicate the problem as briefly as possible.
4 - In the same directory where you start the server, you will
now find a file named 'spy.log'. Please send it to me. ( j o e AT b e a DOT c o m )
I will try to reproduce the problem.
5 - Ask BEA support for the latest BEA driver package and install it according to
their instructions. Let me know asap if the probem is still there.
thanks
Joe
>
Also, I forgot to post in the original message some of the WLS stdout related logging we see. Here it is (sorry, it's a little messy):
11:38:37 o'clock AM EST> <Error> <JDBC> <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <> <BEA-001131> <Received an exception when closing a cached statement for the pool " THE POOL": java.sql.SQLException: [BEA][SQLServer JDBC Driver]The operation was cancelled at the user's request..>
11:38:37 o'clock AM EST> <Error> <JDBC> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <> <BEA-001131> <Received an exception when closing a cached statement for the pool " THE POOL": java.sql.SQLException: [BEA][SQLServer JDBC Driver]The operation was cancelled at the user's request..>
11:38:37 o'clock AM EST> <Error> <JDBC> <ExecuteThread: '10' for queue: 'weblogic.kernel.Default'> <> <BEA-001131> <Received an exception when closing a cached statement for the pool " THE POOL": java.sql.SQLException: [BEA][SQLServer JDBC Driver]The operation was cancelled at the user's request..>
11:38:38 o'clock AM EST> <Error> <JDBC> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <> <BEA-001112> <Test "select count(*) from TEST_TABLE" set up for pool " THE POOL" failed with exception: "java.sql.SQLException: [BEA][SQLServer JDBC Driver]A problem occurred when attempting to contact the server (Server returned: Connection reset). Please ensure that the server parameters passed to the driver are correct and that the server is running. Also ensure that the maximum number of connections
have not been exceeded for this server.".>
11:38:38 o'clock AM EST> <Info> <JDBC> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <> <BEA-001128> <Connection for pool " THE POOL" closed.>
11:38:38 o'clock AM EST> <Info> <JDBC> <ExecuteThread: '14' for queue: 'weblogic.kernel.Default'> <> <BEA-001067> <Connection for pool " THE POOL" refreshed.>
11:38:40 o'clock AM EST> <Error> <JDBC> <ExecuteThread: '10' for queue: 'weblogic.kernel.Default'> <> <BEA-001112> <Test "select count(*) from TEST_TABLE" set up for pool " THE POOL" failed with exception: "java.sql.SQLException: [BEA][SQLServer JDBC Driver]A problem occurred when attempting to contact the server (Server returned: Connection reset). Please ensure that the server parameters passed to the driver are correct and that the server is running. Also ensure that the maximum number of connections
have not been exceeded for this server.".>
11:38:40 o'clock AM EST> <Info> <JDBC> <ExecuteThread: '10' for queue: 'weblogic.kernel.Default'> <> <BEA-001128> <Connection for pool " THE POOL" closed.>
11:38:40 o'clock AM EST> <Info> <JDBC> <ExecuteThread: '10' for queue: 'weblogic.kernel.Default'> <> <BEA-001067> <Connection for pool " THE POOL" refreshed.>
11:38:41 o'clock AM EST> <Error> <JDBC> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <> <BEA-001131> <Received an exception when closing a cached statement for the pool " THE POOL": java.sql.SQLException: [BEA][SQLServer JDBC Driver]The operation was cancelled at the user's request..>
11:38:41 o'clock AM EST> <Error> <JDBC> <ExecuteThread: '10' for queue: 'weblogic.kernel.Default'> <> <BEA-001131> <Received an exception when closing a cached statement for the pool " THE POOL": java.sql.SQLException: [BEA][SQLServer JDBC Driver]The operation was cancelled at the user's request..>
Here is the sequence of calls we make (notice the statement is closed outside the finally however we assume the connection.close should close associated resources):
PreparedStatement statement = null;
try {
connection = dataSource.getConnection();
statement = connection.prepareStatement(QUERY_STRING);
statement.setString(1, name1);
statement.setString(2, name2);
statement.setQueryTimeout(timeout);
ResultSet resultSet = statement.executeQuery();
//iterate over result set
statement.close();
return result;
} catch (SQLException e1) {
//log
} finally {
try {
if(connection != null)
connection.close();
} catch (SQLException e2) {
//log
Thanks again,
Mich

Repost: ClassNotFoundException: weblogic/jdbc/pool/Driver

Similar Messages

Maybe you are looking for