Retrying Pool Connections

Hello,
I'm trying to make my JDBCConnectionPools retry connecting to the database if
the initial attempt fails but I have not been successful. I have set ConnectionCreationRetryFrequencySeconds="30"
in the config.xml. I have started WLS when the database server was still recovering
databases, and received the connection exceptions but saw no attempt to reconnect.
Resetting the pools via the console did not establish a connection. Is there
some other setting that I'm missing?
Thanks,
Bob

Joseph Weinstein wrote:
Bob Stevenson wrote:
Hello,
I'm trying to make my JDBCConnectionPools retry connecting to the database if
the initial attempt fails but I have not been successful. I have set ConnectionCreationRetryFrequencySeconds="30"
in the config.xml. I have started WLS when the database server was still recovering
databases, and received the connection exceptions but saw no attempt to reconnect.
Resetting the pools via the console did not establish a connection. Is there
some other setting that I'm missing?
Hi again. I', wrong. This property is as advertised, and should have the pool continue trying to
make connections if it fails initially. COuld you turn on JDBC logging and tell me if you see any SQLExceptions
as the pool starts up, and then later as it should be continuing to connect?
thanks,
Joe
>
>>
Thanks,
BobHi. I am researching this new parameter, and it's looking to me like it means the same as
LoginDelaySeconds, ie: it just has to do with when the pool is creating connections,
some DBMSes can't handle lots of new connection requests in a tight loop, so we offer
a configurable delay. This has nothing to do with retrying to make a given connection.
One easy thing to do is to configure the pool to have an initial size of zero, so it doesn't
try to make any connections at startup. When the pool is used by applications, it will
make connections to populate itself as needed. Note though that some EJB deployments
etc do need connections to be available at startup...
Joe

Similar Messages

IOException (SQLWarning) while creating pool connection

Folks,
I see the following warning in the weblogic jdbc.log every time
a database pool connection is made. This is not causing any
problem but it is very annoying. How do we stop this. Is there
any sybase setting that needs to be fixed. Any help is
appreciated.
Regards,
Mohan.
Here is the definition for the pool:
weblogic.jdbc.connectionPool.MOSpool=\
url=jdbc:sybase:Tds:xx.xx.xx.xx:XXXX,\
driver=com.sybase.jdbc2.jdbc.SybDriver,\
loginDelaySecs=1,\
initialCapacity=20,\
maxCapacity=50,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=5,\
testTable=sysobjects,\
refreshMinutes=30,\
testConnsOnReserve=true,\
testConnsOnRelease=true,\
props=user=xxx;password=xxx,\
allow=guest
SQLWarning: reason(010SM: This database does not support the initial proposed
se
t of capabilities, retrying.) SQLState(010SM)
SQLWarning: reason(010SM: This database does not support the initial proposed
se
t of capabilities, retrying.) SQLstate(010SM) vendor code(0)
java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0EM:
En
d of data.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:423)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:2781)
at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:1744)
at com.sybase.jdbc2.tds.Tds.logout(Tds.java:550)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:360)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:213)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java
:190)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:169)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:122)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:175)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:146)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:817)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:416)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:330)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:106)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java
:62)
SQLException: SQLState(JZ006)

Hi Mohan. This is a sybase-only issue. If you set the drivermanager's
log stream to system.out, and make a connection in a simple standalone
program, you'll see the same output. The issue may be that the driver
is submitting what it expects is it's local character set, and the
DBMS is saying that the cheracter set is not installed in the DBMS.
You should ask this in the sybase public newsgroups. The workaround may
be as simple as having your DBA install the charset the driver wants.
Joe
"E.R.Mohan" wrote:
>
Folks,
I see the following warning in the weblogic jdbc.log every time
a database pool connection is made. This is not causing any
problem but it is very annoying. How do we stop this. Is there
any sybase setting that needs to be fixed. Any help is
appreciated.
Regards,
Mohan.
Here is the definition for the pool:
weblogic.jdbc.connectionPool.MOSpool=\
url=jdbc:sybase:Tds:xx.xx.xx.xx:XXXX,\
driver=com.sybase.jdbc2.jdbc.SybDriver,\
loginDelaySecs=1,\
initialCapacity=20,\
maxCapacity=50,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=5,\
testTable=sysobjects,\
refreshMinutes=30,\
testConnsOnReserve=true,\
testConnsOnRelease=true,\
props=user=xxx;password=xxx,\
allow=guest
SQLWarning: reason(010SM: This database does not support the initial proposed
se
t of capabilities, retrying.) SQLState(010SM)
SQLWarning: reason(010SM: This database does not support the initial proposed
se
t of capabilities, retrying.) SQLstate(010SM) vendor code(0)
java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0EM:
En
d of data.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:423)
at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:2781)
at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:1744)
at com.sybase.jdbc2.tds.Tds.logout(Tds.java:550)
at com.sybase.jdbc2.tds.Tds.login(Tds.java:360)
at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:213)
at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java
:190)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:169)
at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:122)
at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:175)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:146)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:817)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:416)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:330)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:106)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:220)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java
:62)
SQLException: SQLState(JZ006)

Pool Connection detection

All,
I want to see what is the best/fastest way to determine whether a DB
pool connection if invalid. The problem with the way I am doing now is
that there is at least a 2 minutes delay prior Weblogic throwing
SQLException when the connection is bad because of the refresh retry.
Here are my steps of processing:
1. geDBConnection
2. If SQLException then
doSomething else
Again, my problem is that at least 2 minutes when I made the call and
catching of the SQLException due to the fact that WL is trying to
refresh the connection. Is there another way to cut down this timing?
or a better way in general?
Thanks in advance
Minh Huynh

Hi Minh,
What you need is to turn on TestOnReserve in the connection pool definition.
Having this setting on, weblogic will test (and refresh) connections before
returning them to the client. That should solve you problem.
Regards,
Slava Imeshev
"Minh Huynh" <[email protected]> wrote in message
news:[email protected]..
All,
I want to see what is the best/fastest way to determine whether a DB
pool connection if invalid. The problem with the way I am doing now is
that there is at least a 2 minutes delay prior Weblogic throwing
SQLException when the connection is bad because of the refresh retry.
Here are my steps of processing:
1. geDBConnection
2. If SQLException then
doSomething else
Again, my problem is that at least 2 minutes when I made the call and
catching of the SQLException due to the fact that WL is trying to
refresh the connection. Is there another way to cut down this timing?
or a better way in general?
Thanks in advance
Minh Huynh

Failure in ORACLE POOL connection

Hi friends,
I have worked as a developer, My platform front-end is .net and back end is oracle, this product live chat, My problem is I have receive a problem from server that’s is, mysql POOL connection is automatically cut from the connection, I have try to fix that bug but unexpectedly I cannot fix that, Anybody say some suggestion about that.
Thanks in advance for your help.
Regards,
Gilbertsavier.
Live chat By mioot

You missed the following
1. Oracle Version
2. OS
3. Error Number
4. Error Message
Please Fill the above details.
Regards,

Closing pooled connections?? one at a time?

I've got an interesting need;
I've writen a custom UserManager for form based authentication.
class ValidateLoginManager extends AbstractUserManager
Authentication is to a legacy DB (Oracle) where all users have
been added as
Oracle users. So I've created a separate JNDI data source in
data-sources.xml
for pooling connections that I'll only use for authentication
(just a gut decission).
The container calls:
boolean checkPasswd (username, passwd) {
boolean authenticated = false;
try {
dbConnection = this.datasource.getConnection(username,
passwd);
authenticated = true;
} finally {
if (dbConnection != null)
dbConnection.close();
return authenticated;
This works great, since Oracle authenticates the connection
against it's user DB.
But the conn.close() does not close the session on the DB and
soon all MTS tasks are used up in idle sessions.
Any thoughts on forcing the connection to drop open sessions?
thanks, curt

Hi Curt,
For my custom usermanager I use a datasource specified in my data-sources.xml like this:
<data-source
 class="com.evermind.sql.DriverManagerDataSource"
 name="xyz"
 location="jdbc/OracleSecurityDS"
 xa-location="jdbc/xa/OracleXADS"
 ejb-location="jdbc/OracleDS"
 connection-driver="oracle.jdbc.driver.OracleDriver"
 url="jdbc:oracle:thin:@127.0.0.0:1521:xyz"
 inactivity-timeout="30"
/>
When you lookup the datasource using JNDI, make sure you use the name bound to the location specified in the "location" attribute and not the "ejb-location" attribute (as you usually do in your Ejbs).
I hope this helps.
- nik.
I've got an interesting need;
I've writen a custom UserManager for form based authentication.
class ValidateLoginManager extends AbstractUserManager
Authentication is to a legacy DB (Oracle) where all users have
been added as
Oracle users. So I've created a separate JNDI data source in
data-sources.xml
for pooling connections that I'll only use for authentication
(just a gut decission).
The container calls:
boolean checkPasswd (username, passwd) {
boolean authenticated = false;
try {
dbConnection = this.datasource.getConnection(username,
passwd);
authenticated = true;
} finally {
if (dbConnection != null)
dbConnection.close();
return authenticated;
This works great, since Oracle authenticates the connection
against it's user DB.
But the conn.close() does not close the session on the DB and
soon all MTS tasks are used up in idle sessions.
Any thoughts on forcing the connection to drop open sessions?
thanks, curt

SharePoint - Error_1_Error occurred in deployment step 'Add Solution': Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was rea

Hi,
I am Shanmugavel, SharePoint developer,
I am facing the below SharePoint 2013 deployment issue while deploying using VS2012.
If i will deploy the same wsp or existing wsp
(last build) using direct powershell deployment, the solution adding properly, but the same timeout exception coming while activation the features. Please find the below error.
I tried the below activists:
1. Restarted my dev server, DB server.
2. tried the same solution id different server
3. tried existing wsp file (last build version)
4. Deactivated all the features, including project Active deployment configuration.... but still i am facing the same issue.
I hope this is not coding level issue, because still my code is not start running, before that some problem coming.
Please help me any one..... Last two days i am struck because of this...

What you need to understand is the installation of a WSP does not do much. It just makes sure that you relevant solution files are deployed to the SharePoint farm.
Next comes the point when you activate the features. It is when the code which you have written to "Activate" certain features for your custom solution.
Regarding the error you are getting, it typically means that you have more connections (default is I guess 100) open for a SQL database then you are allowed to.
If you have a custom database and you are opening a connection, make sure you close it as well.
Look at the similar discussion here:
The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool
size was reached[^]
I would suggest further to look at the
ULS logs[^] to get better insight.
Manas Bhardwaj's Stream : www.manasbhardwaj.net

What are the correct parameter names for a JDBC pool connection?

Looking in the admin console I notice the differences in the properties name (type casting) of PointBasePool and __TimerPool pool connections properties and the create wizard properties.
PointBasePool and __TimerPool uses this name parameters: User,Password, and DatabaseName.
Create wizard uses these: databaseName, user, password.
So, then, what is the standard names for a connection in SOA8? What is the standard for JDBC?
For example, Tomcat 4 uses username, password, url, driverClassName as parameters names.
Please help,
This is getting more and more confising,
Thanks,
Lorenzo Jimenez

The properties that you specify when creating the connection pool are unique to the vendor.
Any or the properties that you specify user,password, url...etc we expect to have setters (setUser, setPassword, setUrl)
let me know if need more info

Best practice for auditing a SP 2010 BCS scenario with a SQL Server pooled connection.

I'm using SP 2010 BCS to connect to a SQL Server db. For this, I've used SSS and am passing SQL credentials to take advantage of pooled connections. I'd like to pass the user context (user ID/User name) to the database so that I can do auditing, such as
created by and last modified by. What is the best approach to make this work while still using a pooled connection?
I've thought about modifying the external list forms so that I capture and pass down user context info, however, I'd like not to rely on this in case the external content type is consumed by another consumer such as an Office product, etc.

Hi,
There is no good way to do it.
You can set the created by and modified by columns as input parameters for the create and update operations and using ajax to set values for both of columns.
http://troyscott.ca/2010/07/17/creating-an-update-operation-for-an-external-content-type/
Regards,
Seven

Could not create pool connection with MySql

When starting weblogic server I obtain the following error message when the conection
pool for a MySql database should be established. What's the mistake I am doing? #The
examples in the weblogic.properties put a "server=DEMO to the props. What is this
server related to the MySql RDBMS? Is it mandatory? After the error message produced
by Weblogic you'll find some information about the MySql setup (my.ini) I have made.
Mi Mai 01 01:33:50 CEST 2002: <WebLogicServer> Invoking main-style startup weblogic.jdbc.common.internal.JdbcStartup
weblogic.jdbc.common.internal.JdbcStartup
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Creating connection pool ejbTestPool
with:
{aclName=weblogic.jdbc.connectionPool.ejbTestPool, maxCapacity=2, initialCapacity=1,
url=jdbc:mysql://Blizzard:3306/ejbTest, props=user=du-it;password=du-it;server=3.23.4
9-nt, capacityIncrement=1, driver=org.gjt.mm.mysql.Driver, poolName=ejbTestPool}
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Sleeping in createResource()
Mi Mai 01 01:33:51 CEST 2002:<E> <JDBC Pool> Failed to create connection pool "ejbTes
tPool"
weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Invalid authorization specification: Access denied for user:
du-it@blizzard' (Using password: YES)
at org.gjt.mm.mysql.MysqlIO.init(MysqlIO.java:278)
at org.gjt.mm.mysql.Connection.<init>(Connection.java:230)
at org.gjt.mm.mysql.Driver.connect(Driver.java:126)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:146)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:154)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:124)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
MySql:
#This File was made using the WinMySQLAdmin 1.4 Tool
#29.04.2002 14:46:57
#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions
[mysqld]
basedir=D:/db/mysql
#bind-address=169.254.102.136
datadir=D:/db/mysql/data
#anguage=D:/db/mysql/share/german
#slow query log#=
#tmpdir#=
port=3306
#set-variable=key_buffer=16M
[WinMySQLadmin]
Server=D:/db/mysql/bin/mysqld-nt.exe
user=du-it
password=du-it

When starting weblogic server I obtain the following error message when the conection
pool for a MySql database should be established. What's the mistake I am doing? #The
examples in the weblogic.properties put a "server=DEMO to the props. What is this
server related to the MySql RDBMS? Is it mandatory? After the error message produced
by Weblogic you'll find some information about the MySql setup (my.ini) I have made.
Mi Mai 01 01:33:50 CEST 2002: <WebLogicServer> Invoking main-style startup weblogic.jdbc.common.internal.JdbcStartup
weblogic.jdbc.common.internal.JdbcStartup
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Creating connection pool ejbTestPool
with:
{aclName=weblogic.jdbc.connectionPool.ejbTestPool, maxCapacity=2, initialCapacity=1,
url=jdbc:mysql://Blizzard:3306/ejbTest, props=user=du-it;password=du-it;server=3.23.4
9-nt, capacityIncrement=1, driver=org.gjt.mm.mysql.Driver, poolName=ejbTestPool}
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Sleeping in createResource()
Mi Mai 01 01:33:51 CEST 2002:<E> <JDBC Pool> Failed to create connection pool "ejbTes
tPool"
weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Invalid authorization specification: Access denied for user:
du-it@blizzard' (Using password: YES)
at org.gjt.mm.mysql.MysqlIO.init(MysqlIO.java:278)
at org.gjt.mm.mysql.Connection.<init>(Connection.java:230)
at org.gjt.mm.mysql.Driver.connect(Driver.java:126)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:146)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:154)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:124)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
MySql:
#This File was made using the WinMySQLAdmin 1.4 Tool
#29.04.2002 14:46:57
#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions
[mysqld]
basedir=D:/db/mysql
#bind-address=169.254.102.136
datadir=D:/db/mysql/data
#anguage=D:/db/mysql/share/german
#slow query log#=
#tmpdir#=
port=3306
#set-variable=key_buffer=16M
[WinMySQLadmin]
Server=D:/db/mysql/bin/mysqld-nt.exe
user=du-it
password=du-it

There was a problem connecting to the Server. Touch Retry to connect again, or OK to Exit" HELP!

There was a problem connecting to the Server. Touch Retry to connect again, or OK to Exit."
I have a newer model HP Photosmart Plus (Print/Scan/Copy/Web)
Keep getting this error message. Have pressed Retry, have exited and tried again. No results. Have shut off/unplugged/restarted printer and computer several times, but this keeps popping up as soon as I press "Apps". All I can access is "quick forms", and they don't print correctly (layouts are strange). Anyone know how to fix this?

Hope you are doing well TFam5;
Are you having this problem constantly?
I want to help but in order to do so I will need more information in regards your devices and configuration, please include all this,.
What is the operating system that your system utilizes?
Use this example as a guide Windows 7 home premium 64 bits. The reason we ask your Operating system in all post in due to the fact that I want provide you with detailed suggestion and in other to accomplish some of the instructions that we will provide are operating system dependent or different in different versions of the OS, in short words if you want me to guide thru the process I will need the operating system, the version and the intructiosn width (32 or 64 bits)
What is the complete printer model?
HP Photosmart Plus All-in-One Printer - B209a ›
HP Photosmart Plus e-All-in-One Printer - B210a ›
HP Photosmart Plus e-All-in-One Printer - B210b ›
HP Photosmart Plus e-All-in-One Printer - B210c ›
HP Photosmart Plus e-All-in-One Printer - B210e ›
Some printer models have as much as 6 different versions is important to know which version exactly do you own in order for me to provide accurate links for your product If you are having issues with your finding the complete version of your product please visit this site. http://h10025.www1.hp.com/ewfrf/wc/document?tmp_renderType=findModel&cc=us&dlc=en&docname=bpy21016&l...
Provide this info and I will do my best to help you.
Regards.
RobertoR
▼
You can say THANKS by clicking the KUDOS STAR. If my suggestion resolves your issue Mark as a "SOLUTION" this way others can benefit Thanks in Advance!

Getting Pooled Connection with username and password

hi,
I am facing problems in getting pooled connections to MYSQL
database.I am using Tomcat server.
I tried the example given in Tomcat doc "JNDI how to", it
works fine with one set of username and password which is
given in server.xml. Now can anybody guide me thru the steps
to get pooled connections to the same database with multiple
username and passwords.
Thankyou all in advance

Now can anybody guide me thru the steps to get pooled
connections to the same database with multiple
username and passwords.Nope. Can't be done -- at least not that I've seen yet.
Database/JDBC driver vendors seem unconcerned, or don't
care about this scenario. I ragged on Informix years
ago for this very feature. It should would make database
admins jobs a lot easier if they could know "who" that
connection belonged to that is running the outrageous
SQL query without having to divine it by way of tracing
socket/IP connections back thru the network to some machine.
The only way I've seen to do it is to create your own
connection pool code that handles user/password connections.
-- but then the problem becomes you have a collection of
mini-pools for each user. i.e. if you have 200 users, you
end up with 200 connection pools with a couple/few connections
in each sub-pool. Kinda defeats the purpse.
So, apparently, everybody just deals with the single
"generic" user/password connection pool.

Pooled Connection not supported in oracle forms 11g

Dear all,
I am using oracle from builder (11.1.1.4) and oracle database 11g Release 2. I can connect to the database from oracle forms 11g, when I use a dedicated or shared server connection mentioned in the tnsnames.ora file . But I want to use the oracle database 11g's new feature DRCP (Database Resident Connection Polling).
To do this a made a another POOLED connection (SERVER=POOLED) in the tnsnames.ora.I can connect to the 11g r2 database server from sqlplus using POOLED connection. But when I try it from form builder (11.1.1.1.4) it gives error with some unknown characters.
Then I tried it in linux frmcmp the message i got in terminal is can not *"Cannot obtain ORACLE version number"*
I have googled and also checked in metalink. But I got nothing.Thanks in advance for your help.

I don't think this feature is feasible for forms.
Quoting the documentation from
http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/manproc002.htm
Database Resident Connection Pooling (DRCP) provides a connection pool in the database server for typical Web application usage scenarios where the application acquires a database connection, works on it for a relatively short duration, and then releases it.
Forms keeps a permanent connection to the database, so a connection pool isn't gonna help you in any way.
cheers

Could not create pool connection. The DBMS driver exception was:java.sql.SQLException: ORA-01017: invalid username/password

Could not create pool connection.The DBMS driver exception was:java.sql.SQLException:
ORA-01017: invalid username/password
Even though I could able to connect to Oracle database using correct userid,password
and HostString using OracleClient, I couldnt able to do with connectionpool. Here
is the error message..
<Jan 21, 2003 2:27:50 AM PST> <Notice> <WebLogicServer> <Starting WebLogic Admin
Server "examplesServer" for domain "examples">
Starting Loading jDriver/Oracle .....
---------- LOGIN ERROR CODE: 1017
---------- LOGIN ERROR CODE: 1017
<Jan 21, 2003 2:28:06 AM PST> <Error> <JDBC> <Cannot startup connection pool "or
aclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: ORA-01017: invalid username/password; logon denied - (Obj
ectel/********@ora8i)
at weblogic.db.oci.OciConnection.getLDAException(OciConnection.java:164)
at weblogic.jdbc.oci.Driver.connect(Driver.java:112)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Jan 21, 2003 2:28:14 AM PST> <Notice> <Management> <Application Poller started
for development server.>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <ListenThread listening
on port 7001>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <SSLListenThread listeni
ng on port 7002>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <Management> <Starting discovery of Manag
ed Server... This feature is on by default, you may turn this off by passing -Dw
eblogic.management.discover=false>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogic Admin
Server "examplesServer" for domain "examples" running in Development Mode>

URL=jdbc:weblogic:oracle:oracle8i(server)
Driver Classname=weblogic.jdbc.oci.Driver
AClname=weblogic.jdbc.connectionPool.oraclePool
intialcapacity=1
MaximumCapacity=10
Capacity Increment=2
Login Delay Seconds=1sec
Refresh Period=15 Minutes
Supports Local Transaction=No
Allow Shrinking=No
Shrink Period=15
Prepared Statement Cache Size=10
TargetServer=ExamplesServer
Properties
user=Objectel
password=superman
Test table=yes
Test Reserved Connections=yes
Test Released Connections=Yes
I could able to connect to oracledataBase if I use
user=scott
password=tiger
with any other database user Iam getting the following error
Could not create pool connection. The DBMS driver exception was:java.sql.SQLException:
ORA-01017: invalid username/password
"Neo Gigs" <[email protected]> wrote:
By end of the error you shown:
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogicAdmin
Server "examplesServer" for domain "examples" running in DevelopmentMode>
You are running the Examples application shipped with WLS, which I guest
the
correct DB to connect with is Cloudscape yet to Oracle, unless you make
changes to the original ConnectionPool in the examples. Anyhow, please
show
us your configuration of the ConnectionPool used when this error pops.
"Raj" <[email protected]> wrote in message
news:[email protected]...
Could not create pool connection.The DBMS driver exceptionwas:java.sql.SQLException:
ORA-01017: invalid username/password
Even though I could able to connect to Oracle database using correctuserid,password
and HostString using OracleClient, I couldnt able to do withconnectionpool. Here
is the error message..
<Jan 21, 2003 2:27:50 AM PST> <Notice> <WebLogicServer> <Starting WebLogicAdmin
Server "examplesServer" for domain "examples">
Starting Loading jDriver/Oracle .....
---------- LOGIN ERROR CODE: 1017
---------- LOGIN ERROR CODE: 1017
<Jan 21, 2003 2:28:06 AM PST> <Error> <JDBC> <Cannot startup connectionpool "or
aclePool" weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: ORA-01017: invalid username/password; logondenied - (Obj
ectel/********@ora8i)
atweblogic.db.oci.OciConnection.getLDAException(OciConnection.java:164)
at weblogic.jdbc.oci.Driver.connect(Driver.java:112)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:193)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub
start(ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
nectionEnvFactory.java:209)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
nectionEnvFactory.java:134)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllo
cator.java:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.j
ava:282)
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
ava:623)
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy45.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeplo
yments(ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
java:621)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub
start(ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Jan 21, 2003 2:28:14 AM PST> <Notice> <Management> <Application Pollerstarted
for development server.>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <ListenThreadlistening
on port 7001>
<Jan 21, 2003 2:28:19 AM PST> <Notice> <WebLogicServer> <SSLListenThreadlisteni
ng on port 7002>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <Management> <Starting discoveryof
Manag
ed Server... This feature is on by default, you may turn this off bypassing -Dw
eblogic.management.discover=false>
<Jan 21, 2003 2:28:20 AM PST> <Notice> <WebLogicServer> <Started WebLogicAdmin
Server "examplesServer" for domain "examples" running in DevelopmentMode>

Error on DS creation (ResourceException: Could not create pool connection)

Hi,
When trying to create a DS on a WLS 10.3 on Windows Vista to connect to an Oracle 10.2.0.4 RAC database, I am getting the exception below. I use the OCI driver. Everything's fine when I use the thin driver though.
<Jan 31, 2009 9:56:56 AM AST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "EPDVDS":
<Jan 31, 2009 9:56:57 AM AST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with I
D '1233385014499' for task 'weblogic.deploy.configChangeTask.0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:289)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver excep
tion was:
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
Truncated. see log file for complete stacktrace
<Jan 31, 2009 9:56:57 AM AST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating activate task for ap
plication 'EPDVDS'.>
<Jan 31, 2009 9:56:57 AM AST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:289)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver excep
tion was:
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
Truncated. see log file for complete stacktrace
<Jan 31, 2009 9:56:58 AM AST> <Error> <Console> <BEA-240003> <Console encountered the following error weblogic.application.Mo
duleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:289)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.jav
a:197)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:216)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentRece
iverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallba
ckDeliverer.java:40)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceiver
s(AwaitingContextUpdateCompletion.java:164)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuc
cess(AwaitingContextUpdateCompletion.java:66)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(Awaitin
gContextUpdateCompletion.java:32)
at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService
.java:225)
at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:189)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS d
river exception was:
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:146)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:385)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:326)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:251)

Hi,
I am also using OCI driver, as some of the functions for XMLType are not supported by thin driver.
I am getting similar error, as mentioned in the thread as
<BEA-001129> <Received exception while creating connection for pool "11g_Connection": >
oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
INFO: Cleaning up application state
weblogic.application.ModuleException:
 at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:289)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
 Truncated. see log file for complete stacktrace
weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was:
 at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
 at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
 at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
 at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
 at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
 Truncated. see log file for complete stacktrace
I have already tested with a standalone program and it works, but error is thrown with weblogic server.
My connection string is jdbc:oracle:oci:@//localhost:1521/orcl11
Any ideas on how this error can be avoided?
Thanks
Raji

Could not create pool connection

After running the server, when I am continously firing queries on the server. The server is giving this error for some of the queries. But it is working for other cases. Any idea why this error is coming?
database : informix
<Jul 12, 2005 9:02:46 PM IST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8881, ip address 23.248.10.15>
<Jul 12, 2005 9:02:46 PM IST> <Notice> <Cluster> <BEA-000102> <Joining cluster GREFCluster on 237.0.0.1:7001>
<Jul 12, 2005 9:02:46 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "grefMaintManaged2" for domain "gref203" running in Production Mode>
<Jul 12, 2005 9:02:46 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Jul 12, 2005 9:45:55 PM IST> <Debug> <Common> <BEA-000610> < > RP(GrefConnPool):parseExceptionMsg (10) msg = 19:Could not create pool connection. The DBMS driver exception was: null>
<Jul 12, 2005 9:45:56 PM IST> <Debug> <Common> <BEA-000610> < < RP(GrefConnPool):parseExceptionMsg (100) count = 19>
<Jul 12, 2005 9:46:00 PM IST> <Debug> <Common> <BEA-000610> < > RP(GrefConnPool):parseExceptionMsg (10) msg = 19:Could not create pool connection. The DBMS driver exception was: Message text will be provided in later releases java.lang.NullPointerException>
<Jul 12, 2005 9:46:00 PM IST> <Debug> <Common> <BEA-000610> < < RP(GrefConnPool):parseExceptionMsg (100) count = 19>
<Jul 12, 2005 10:01:00 PM IST> <Debug> <Common> <BEA-000610> < > RP(GrefConnPool):parseExceptionMsg (10) msg = 19:Could not create pool connection. The DBMS driver exception was: null>
<Jul 12, 2005 10:01:00 PM IST> <Debug> <Common> <BEA-000610> < < RP(GrefConnPool):parseExceptionMsg (100) count = 19>

Hi Anish. Very odd. What versio of weblogic are you running, and what Informix
driver are you using?
Joe
Anish Mathur wrote:
After running the server, when I am continously firing queries on the server. The server is giving this error for some of the queries. But it is working for other cases. Any idea why this error is coming?
database : informix
<Jul 12, 2005 9:02:46 PM IST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8881, ip address 23.248.10.15>
<Jul 12, 2005 9:02:46 PM IST> <Notice> <Cluster> <BEA-000102> <Joining cluster GREFCluster on 237.0.0.1:7001>
<Jul 12, 2005 9:02:46 PM IST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "grefMaintManaged2" for domain "gref203" running in Production Mode>
<Jul 12, 2005 9:02:46 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Jul 12, 2005 9:45:55 PM IST> <Debug> <Common> <BEA-000610> < > RP(GrefConnPool):parseExceptionMsg (10) msg = 19:Could not create pool connection. The DBMS driver exception was: null>
<Jul 12, 2005 9:45:56 PM IST> <Debug> <Common> <BEA-000610> < < RP(GrefConnPool):parseExceptionMsg (100) count = 19>
<Jul 12, 2005 9:46:00 PM IST> <Debug> <Common> <BEA-000610> < > RP(GrefConnPool):parseExceptionMsg (10) msg = 19:Could not create pool connection. The DBMS driver exception was: Message text will be provided in later releases java.lang.NullPointerException>
<Jul 12, 2005 9:46:00 PM IST> <Debug> <Common> <BEA-000610> < < RP(GrefConnPool):parseExceptionMsg (100) count = 19>
<Jul 12, 2005 10:01:00 PM IST> <Debug> <Common> <BEA-000610> < > RP(GrefConnPool):parseExceptionMsg (10) msg = 19:Could not create pool connection. The DBMS driver exception was: null>
<Jul 12, 2005 10:01:00 PM IST> <Debug> <Common> <BEA-000610> < < RP(GrefConnPool):parseExceptionMsg (100) count = 19>

Retrying Pool Connections

Similar Messages

Maybe you are looking for