WebLogic 8.1 SP2 bug in JDBC Pool creation for IBM Informix Driver - Type 4 XA

Funny business happens when you create a JDBC Connection Pool with IBM's Informix Driver - Type 4 XA under WebLogic 8.1 SP2
I have included the ifxjdbc.jar and ifxjdbcx.jar in the classpath in the the extENV.cmd, but I kept getting errors on connection:
weblogic.common.ResourceException: 0:com.informix.asf.IfxASFException: Attempt to connect to database server (myhost) failed. - with nested exception:
[weblogic.common.ResourceException: com.informix.asf.IfxASFException: Attempt to connect to database server (myhost) failed.]
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1040)
Then I realised the WebLogic console was swapping these properties:
serverName=ol_myserver
ifxIFXHOST=myhost
Terrible forehead-slap!
I rechecked and this what happens:
Informix Server: -> ifxIFXHOST
Host Name: -> serverName
But the URL is correct.
jdbc:informix-sqli://myhost:1543/mydb:informixServer=ol_myserver
Notice that the exception message says:
Attempt to connect to database server (myhost) failed.
Alpha

Alpha Lau wrote:
Funny business happens when you create a JDBC Connection Pool with IBM's
Informix Driver - Type 4 XA under WebLogic 8.1 SP2
I have included the ifxjdbc.jar and ifxjdbcx.jar in the classpath in the
the extENV.cmd, but I kept getting errors on connection:
weblogic.common.ResourceException: 0:com.informix.asf.IfxASFException:
Attempt to connect to database server (myhost) failed. - with nested
exception:
[weblogic.common.ResourceException: com.informix.asf.IfxASFException:
Attempt to connect to database server (myhost) failed.]
at
weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at
weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1040)
Then I realised the WebLogic console was swapping these properties:
serverName=ol_myserver
ifxIFXHOST=myhost
Terrible forehead-slap!
I rechecked and this what happens:
Informix Server: -> ifxIFXHOST
Host Name: -> serverName
But the URL is correct.
jdbc:informix-sqli://myhost:1543/mydb:informixServer=ol_myserver
Notice that the exception message says:
Attempt to connect to database server (myhost) failed.
AlphaHi. If the URL has a particular property value, then don't add the property
redundantly in the pool's properties.
Joe

Similar Messages

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

Weblogic 6.1 sp2 - where i can get pkg for Win

Hi all
I am looking for Weblogic 6.1 sp2 builds for w2k since i am trying to
perform integration with Entrust RA products.
Currently i am using Weblogic 61. sp3, but Entrust recommend on using sp2.
Since i am facing few problems with one of Entrust product, i would like to
work with that version.
Regards.
Yossi Mor

WLS 61 SP2 is not available for public download.
you need to go to http://support.bea.com and download it from there.
Make sure that you have login
Kumar
arielmtest wrote:
Hi all
I am looking for Weblogic 6.1 sp2 builds for w2k since i am trying to
perform integration with Entrust RA products.
Currently i am using Weblogic 61. sp3, but Entrust recommend on using sp2.
Since i am facing few problems with one of Entrust product, i would like to
work with that version.
Regards.
Yossi Mor

Bug in hal video quirks for IBM X30 laptop

With the default settings the radeon quirk is added to quirks causing the system to hard lock as soon as dpms blanks the screen. Adding a match that disables the radeon_off quirk seems to solve the problem but should not be needed. Clearly a bug in the freedesktop fdi file where the X30 with intel 82830 graphics is confused for the X31 with radeon.

Your Adobe ID:[email protected]
Your Case Number:0183213793
Still does not work
I agree. There are bugs. Looks like Flash Player was updated this past April.
I could watch videos prior to this.
I use Vista 64 bit with FireFox 32 bit and Adobe Flash Player version 11 (latest) and it does not work anymore

Bug report with proposed solution for mounting external drives for ftp access

Hello Guys,   I registered to inform you about something I would classify as a bug. I realized this when I used an external drive with my WD My Cloud and trying to access the drive via ftp. It simply was not visible on the ftp, but was accessible as samba share. I digged a bit in the scripts and found this:  /etc/init.d/mountDataVolume.sh   [...]
## initialze bind mount dir (/nfs)
/usr/local/sbin/updateShareBindMntDir.sh --init
[...]  /usr/local/sbin/updateShareBindMntDir.sh  [...]
init_mounts()
mount | grep -q "${SHARE_BIND_MNT_DIR}/"
if [ $? -ne 0 ]; then
# initial clean up of MNT dir
rm -rvf ${SHARE_BIND_MNT_DIR}/*
fi
for D in `find /shares/ -maxdepth 1 -mindepth 1 -type d -not -name ".*"`; do
share_name=$(basename $D)
add_mount "${share_name}"
done
[...]   The init_mounts() function searches /shares for directories (find -type >d<) and bind mounts these to SHARE_BIND_MNT_DIR (default: /nfs) by calling add_mount(). This is the directory where ftp users will drop in after logging in. The problem: find -type d will not find symlinks and external drives are represented by a symlink from /shares to /var/media/EXTERNALDRIVE I propose adding the following code at the end of init_mounts()   for D in `find /shares/ -maxdepth 1 -mindepth 1 -type l -not -name ".*"`; do
share_name=$(basename $D)
add_mount "${share_name}"
done That will look for symlinks in /shares and call add_mount() for each symlink to bind mount it to SHARE_BIND_MNT. I think this is not intended aka a bug because I found this comment for add_mount(): # - If <share_name> is a symlink to an external volume, then create the bind mount
# directly to the external volume.As it seems from this comment add_mount() supports symlinks but init_mounts does not feed it any.   I tried this solution myself and it works flawlessly.   Yours sincerely,schnip

Nice find!

How do I get JDBC Logging with IBM Informix drivers?

I am trying to get JDBC logging working with IBM Informix drivers.
I am using the _g jar files; I have specified TRACE, TRACEFILE,
PROTOCOLTRACE, and PROTOCOLTRACEFILE as properties;
I have enabled JDBC logging and specified a JDBC log file in the
WLS console. Regardless of all these machinations, no logging is
produced.
What else need I do? Thanks for any advice!
: jay

So... a couple weeks later and I've managed to find
out a bit more. My simple program works and produces
output, so the debug drivers are doing their thing.
So, in my simple program, I was using the standard
informix driver. But, with WebLogic, my connection
pool is using the XA datasource which is configured
slightly differently than the driver; in particular,
the URL is left blank as described in
http://e-docs.bea.com/wls/docs70/jdbc/thirdparty.html.
I've actually created another connection pool which
uses the standard driver, and I do get loggging when
I use that pool, so the problem seems to be with the
XA Datasource.
I'm trying to revise my test program to use the
datasource, and we'll go from there. Any thoughts
you have would be appreciated, of course.
: jay
Joe Weinstein wrote:
>
>
Jay Schmidgall wrote:
"Joe Weinstein" <[email protected]> wrote in message
news:[email protected]..
Jay Schmidgall wrote:
I am using the _g jar files; I have specified TRACE, TRACEFILE,
PROTOCOLTRACE, and PROTOCOLTRACEFILE as properties;Odd. Would you please show me a small java program that
sets the properties for the connection so you get your
logging output, and then I'll know what I need for weblogic to do it:I am setting the properties in the weblogic console via the properties
field
on the general configuration tab for the connection pool. That's where I
set all the other properties, so that's where I thought I should set
these.
I've tried it with those properties set individually and as part of
the URL
property.Oh, yes that's where you should be doing it, but a standalone program
will prove exactly what properties are needed by the driver per se.
Ie: the first step is to prove the jdbc driver alone does what we
want, and then we can know how to get weblogic to get the driver to do
the same for it.
Joe
I'll try to cruft up a small program that does this manually, though.
: jay

Weblogic 6.1 sp2 Connection Pool will not connect to oci901 driver

ok, I am trying to get weblogic to connect to the connection pool in solaris. I created
the pool in the console with the following:
URL = jdbc:weblogic:oracle
Driver Class Name = weblogic.jdbc.oci.Driver
Properties = user=sa password=*****
I also set the LD_LIBRARY PATH as directed.
LD_LIBRARY_PATH=/usr/local/wlserver6.1/lib/solaris/oci901_8:ORACLE/lib
Oracle is on a seperate box then the box that Weblogic is installed on so I think
the problem is in my LD_LIBRARY_PATH. Here is the error I am getting. Any help
would be appreciated.
Starting Loading jDriver/Oracle .....
<Jun 7, 2002 9:04:25 AM CDT> <Error> <JDBC> <Cannot startup connection pool "FargoPool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
/usr/local/wlserver6.1/lib/solaris/oci901_8/libweblogicoci37.so: ld.so.1: /home/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
fatal: libclntsh.so.9.0: open failed: No such file or directory
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

"Tim" <[email protected]> wrote:
>
I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request
to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall
in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection
pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable
it ?
2. How do I control the pool size ?
Thanks in advance,
TimDoes anyone from BEA monitor this newsgroup ?
I have also opened up a case (1 week old) with tech support and still do not have
an answer. This is very frustrating considering the cost of owning this environment.
Tim

Bug in Oracle JDBC Pooling Classes - Deadlock

We are utilizing Oracle's connection caching (drivers 10.2.0.1) and have found a deadlock situation. I reviewed the code for the (drivers 10.2.0.3) and I see the same problem could happen.
I searched and have not found this problem identified anywhere. Is this something I should post to Oracle in some way (i.e. Metalink?) or is there a better forum to get this resolved?
We are utilizing an OCI driver with the following setup in the server.xml
<ResourceParams name="cmf_toolbox">
<parameter>
<name>factory</name>
<value>oracle.jdbc.pool.OracleDataSourceFactory</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>oracle.jdbc.driver.OracleDriver</value>
</parameter>
<parameter>
<name>user</name>
<value>hidden</value>
</parameter>
<parameter>
<name>password</name>
<value>hidden</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:oracle:oci:@PTB2</value>
</parameter>
<parameter>
<name>connectionCachingEnabled</name>
<value>true</value>
</parameter>
<parameter>
<name>connectionCacheProperties</name>
<value>(InitialLimit=5,MinLimit=15,MaxLimit=75,ConnectionWaitTimeout=30,InactivityTimeout=300,AbandonedConnectionTimeout=300,ValidateConnection=false)</value>
</parameter>
</ResourceParams>
We get a deadlock situation between two threads and the exact steps are this:
1) thread1 - The OracleImplicitConnectionClassThread class is executing the runAbandonedTimeout method which will lock the OracleImplicitConnectionCache class with a synchronized block. It will then go thru additional steps and finally try to call the LogicalConnection.close method which is already locked by thread2
2) thread2 - This thread is doing a standard .close() on the Logical Connection and when it does this it obtains a lock on the LogicalConnection class. This thread then goes through additional steps till it gets to a point in the OracleImplicitConnectionCache class where it executes the reusePooledConnection method. This method is synchronized.
Actual steps that cause deadlock:
1) thread1 locks OracleImplicitConnectionClass in runAbandonedTimeout method
2) thread2 locks LogicalConnection class in close function.
3) thread1 tries to lock the LogicalConnection and is unable to do this, waits for lock
4) thread2 tries to lock the OracleImplicitConnectionClass and waits for lock.
***DEADLOCK***
Thread Dumps from two threads listed above
thread1
Thread Name : Thread-1 State : Deadlock/Waiting on monitor Owns Monitor Lock on 0x30267fe8 Waiting for Monitor Lock on 0x509190d8 Java Stack at oracle.jdbc.driver.LogicalConnection.close(LogicalConnection.java:214) - waiting to lock 0x509190d8> (a oracle.jdbc.driver.LogicalConnection) at oracle.jdbc.pool.OracleImplicitConnectionCache.closeCheckedOutConnection(OracleImplicitConnectionCache.java:1330) at oracle.jdbc.pool.OracleImplicitConnectionCacheThread.runAbandonedTimeout(OracleImplicitConnectionCacheThread.java:261) - locked 0x30267fe8> (a oracle.jdbc.pool.OracleImplicitConnectionCache) at oracle.jdbc.pool.OracleImplicitConnectionCacheThread.run(OracleImplicitConnectionCacheThread.java:81)
thread2
Thread Name : http-7320-Processor83 State : Deadlock/Waiting on monitor Owns Monitor Lock on 0x509190d8 Waiting for Monitor Lock on 0x30267fe8 Java Stack at oracle.jdbc.pool.OracleImplicitConnectionCache.reusePooledConnection(OracleImplicitConnectionCache.java:1608) - waiting to lock 0x30267fe8> (a oracle.jdbc.pool.OracleImplicitConnectionCache) at oracle.jdbc.pool.OracleConnectionCacheEventListener.connectionClosed(OracleConnectionCacheEventListener.java:71) - locked 0x34d514f8> (a oracle.jdbc.pool.OracleConnectionCacheEventListener) at oracle.jdbc.pool.OraclePooledConnection.callImplicitCacheListener(OraclePooledConnection.java:544) at oracle.jdbc.pool.OraclePooledConnection.logicalCloseForImplicitConnectionCache(OraclePooledConnection.java:459) at oracle.jdbc.pool.OraclePooledConnection.logicalClose(OraclePooledConnection.java:475) at oracle.jdbc.driver.LogicalConnection.closeInternal(LogicalConnection.java:243) at oracle.jdbc.driver.LogicalConnection.close(LogicalConnection.java:214) - locked 0x509190d8> (a oracle.jdbc.driver.LogicalConnection) at com.schoolspecialty.cmf.yantra.OrderDB.updateOrder(OrderDB.java:2022) at com.schoolspecialty.cmf.yantra.OrderFactoryImpl.saveOrder(OrderFactoryImpl.java:119) at com.schoolspecialty.cmf.yantra.OrderFactoryImpl.saveOrder(OrderFactoryImpl.java:67) at com.schoolspecialty.ecommerce.beans.ECommerceUtil.saveOrder(Unknown Source) at com.schoolspecialty.ecommerce.beans.ECommerceUtil.saveOrder(Unknown Source) at com.schoolspecialty.ecommerce.beans.UpdateCartAction.perform(Unknown Source) at com.schoolspecialty.mvc2.ActionServlet.doPost(ActionServlet.java:112) at com.schoolspecialty.ecommerce.servlets.ECServlet.doPostOrGet(Unknown Source) at com.schoolspecialty.ecommerce.servlets.ECServlet.doPost(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at com.schoolspecialty.ecommerce.servlets.filters.EcommerceURLFilter.doFilter(Unknown Source) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534)

We used a documented option to abandon connects in the case of an unforeseen error. The consequence of using this option was not a graceful degradation in performance but a complete lockup of the application. The scenario in which we created a moderate number of abandoned connections was a rare error scenario but a valid test.
How could this not be a bug in the Oracle driver? Is dead-lock a desireable outcome of using an option? Is dead-lock ever an acceptable consequence of using a feature as documented?
Turns out other Oracle options to recover from an unexpected error also incur a similar deadlock (TimeToLiveTimeout).
I did a code review of the decompiled drivers and it clearly shows the issue, confirming the original report of this issue. Perhaps you have evidence to the contrary or better evidence to support your statement "not a bug in Oracle"?
Perhaps you are one of the very few people who have not experience problems with Oracle drivers? I've been using Oracle since 7.3.4 and it seems that I have always been working around Oracle JDBC driver problems.
We are using Tomcat with the OracleDataSourceFactory.

Weblogic 7.0 , MySQL 3.23 JDBC Connection Pools

i am using weblogic 7.0 and MySQL 3.23 and right now my objective is to create,
configure and test a JDBC
connection pool using the Administrative console.
Here is what i have done till now
- set the classpath of the MySQL driver in the startWLS.cmd like this
SET MYSQL_DRIVER=C:\mysqldriver\mysql-connector-java-2.0.14\mysql-connector-java-2.0.14-bin.jar
set CLASSPATH=%MYSQL_DRIVER%;%CLASSPATH%
- using the weblogic administrative console i have created a new connection pool
named as
testpool.
- Here is what i have in the testpool general tab
Name: testpool
URL: jdbc:mysql//localhost:3306/test (test is the name of the database in mysql)
Driver Classname: org.gjt.mm.mysql.Driver
I have not entered any Properties, ACL Name, Password or Open String Password.
- Now i go the the Testing tab and enter a name of a table in my test database
and click on Apply
and on the command window i am getting the following exception
java.sql.SQLException No suitable driver
Thanks in advance,
Ashish

Thanks a lot Slava. After reading your mail and the post i was able to get it working.
"Slava Imeshev" <[email protected]> wrote:
Hi Ashish,
I figured out what's the problem. URL in the connection pool
definition is malformed. It's
jdbc:mysql//localhost:3306/test
while the correct one should have colon after mysql:
jdbc:mysql://localhost:3306/test
Regards,
Slava Imeshev
"Ashish Sureka" <[email protected]> wrote in message
news:[email protected]...
I am sorry, the program that i posted here is not comming properlyformatted but
i am able to run a simple java program that connects to MySQL and alsoa
servlet
that connects to the MySQL. The only problem i am having is includingthe
MySQL
driver jar files to the weblogic server classpath.
Thanks,
Ashish.
"Ashish Sureka" <[email protected]> wrote:
Hello Joseph Weinstein,
Actually, i already tried the same approach that you have mentioned
in
your reply
before i posted my message here. Following is the program that i use
to check
MySQL connection.
import java.sql.*;
public class MySQLConnect
public static void main(String[] args) throws Exception
try {
Class.forName ( "org.gjt.mm.mysql.Driver" );
System.out.println ( "MySQL Driver Found" );
} catch ( java.lang.ClassNotFoundException e ) {
System.out.println("MySQL JDBC Driver not found ... ");
throw ( e );
String url = "";
Connection con = null;
try {
url = "jdbc:mysql://" + "localhost:3306" + "/" + "test";
con = DriverManager.getConnection(url);
System.out.println("Connection established to " + url + "");
} catch ( java.sql.SQLException e ) {
System.out.println("Connection couldn't be established to " + url);
String sqlStatement = "SELECT * FROM testtable";
try {
Statement s = con.createStatement();
s.execute (sqlStatement);
s.close ( );
} catch ( SQLException e ) {
System.out.println ( "Error executing sql statement" );
con.close();
The classpath that i use to run this program is
SET PATH=C:\bea\jdk131_03\bin
SETCLASSPATH=C:\bea\jdk131_03\jre\lib\rt.jar;C:\bea\weblogic700\ebcc\lib\ext\se
rvlet.jar;C:\CSC413\Demos\HelloApp\HelloAppJAR
SET CLASSPATH=%CLASSPATH%;C:\bea\weblogic700\server\lib\weblogic.jar
SETMYSQL_DRIVER=C:\mysqldriver\mysql-connector-java-2.0.14\mysql-connector-java
-2.0.14-bin.jar
set CLASSPATH=.;%MYSQL_DRIVER%;%CLASSPATH%
I have also written a Servlet which checks the MySQL connection. For
the servlet
i added the MySQL driver jar files in the WEB-INF/lib directory ofthe
servlet
web application and it is working fine.
do you want me to attach the startWLS.cmd file that i changed to include
the MySQL
driver classpath.
Thanks for your replies,
Ashish.
Joseph Weinstein <[email protected]> wrote:
Ashish Sureka wrote:
When i start the weblogic server using the command prompt by executingthe startWLS.cmd,
i can see the classpath the server is using on the command window
and
that includes
the jar file for the MySQL driver but still it is throwing a
SQLException
and
saying that No Suitable driver.
How do i include a external library or jar file on the weblogic
server's
classpath.
is there a specific directory where i should put the MySQL driver
jar
file .
Thanks,
Ashish.No. Let's simplfy the problem. Please run a tiny standalone Java
program
that
just makes a JDBC connection to your MySQL DBMS, with no weblogic
code in the picture. When you succeed at this, show me the CLASSPATH
and
PATH of the shell that ran the program successfully, and show methe
few lines
of code that made the connection. Then we will know the problem.It
may
be that
the URL you're passing to the pool is not exactly correct for that
driver.
Joe
Joseph Weinstein <[email protected]> wrote:
Ashish Sureka wrote:
i am using weblogic 7.0 and MySQL 3.23 and right now my objective
is
to create,
configure and test a JDBC
connection pool using the Administrative console.
Here is what i have done till now
- set the classpath of the MySQL driver in the startWLS.cmd
like
this
SET
MYSQL_DRIVER=C:\mysqldriver\mysql-connector-java-2.0.14\mysql-connector-java
-2.0.14-bin.jar
set CLASSPATH=%MYSQL_DRIVER%;%CLASSPATH%
- using the weblogic administrative console i have created anew
connection
pool
named as
testpool.
- Here is what i have in the testpool general tab
Name: testpool
URL: jdbc:mysql//localhost:3306/test (test is the name of
the
database
in mysql)
Driver Classname: org.gjt.mm.mysql.Driver
I have not entered any Properties, ACL Name, Password or
Open
String
Password.
- Now i go the the Testing tab and enter a name of a table in
my
test
database
and click on Apply
and on the command window i am getting the following exception
java.sql.SQLException No suitable driverWatch the first lines that the server prints out when the script
starts
it. The script
shows the classpath that was constructed for the server. It is
likely
that you need
to do something else to ensure your driver is really in the classpath
the server uses.
Joe
Thanks in advance,
Ashish

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.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

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。

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

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
          >

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


          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

WebLogic 8.1 SP2 bug in JDBC Pool creation for IBM Informix Driver - Type 4 XA

Similar Messages

Maybe you are looking for