Regarding the connection pool Error

Hi All,
I am using weblogic10.3. While starting the server we are able to see the below exceptions in the logs which was causing the server to failed state ,even we resume the
server,the server will come to running state but the instance will not be there in the connection pool monitoring tab .once we restart the server again,its working.
can you please let me know why we are getting these errors and any help to remove these.
####<Apr 14, 2010 6:29:29 AM CDT> <Error> <Server-name> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
Kernel>> <> <> <1271244569352> <BEA-149205> <Failed to initialize the application 'dsname' due to error 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)
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.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Io exception: The Network Adapter
could not establish the connection
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)
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.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
Looks like the Database URL may not be correct or may be the TNS name OR some n/w issue between WLS BOX and the DB Box. Please try the following to Double Check it.
Test Number-1 
Step1). Add JDBC Driver also in the Classpath or Better run *"setWLSEnv.sh"*
Step2). Use WLS DB Ping utility:
Syntax:
java -classpath /bea103/wl_server103/server/lib/weblogic.jar utils.dbping ORACLE_THIN <dbUserName> <dbPasswoes> <dbURL>
Example:
java -classpath /bea103/wl_server103/server/lib/weblogic.jar utils.dbping ORACLE_THIN scott tiger databaseHostName:1521:P15215h
Test Number-2
Please run the Following Program from your WLS Server Box:
import java.sql.*;
public class TestConnection
public static void main(String ar[]) throws Exception
System.out.println("\n\t Database URL: "+ar[0]);
System.out.println("\n\t Database UserName: "+ar[1]);
System.out.println("\n\t Database Password: "+ar[2]);
Class.forName("oracle.jdbc.driver.OracleDriver");
System.out.println("\n\t Driver Class Registered and Loaded Successfully...");
System.out.println("\n\n\n\t Trying to Connect to Database....");
Connection con=DriverManager.getConnection(ar[0],ar[1],ar[2]);
System.out.println("\n\n\n\t CONNECTED TO DATABASE SUCCESSFULLY");
To RUN:
java -classpath /opt/app/yourOracelDriverLocation/ojdbc6.jar:.: TestConnection oracelJdbcURL Oracleusername Oraclepassword
if above fails to connect to DataBase ...it simply means Connectivity issue with your database friom the WebLogic Box.
Thanks
Jay SenSharma

Similar Messages

Weblogic server not starting due to connection pool error.

Hi all,
We have some issues with the network due to that, weblog server not able to create the connection pool or make physical connection with the database in the allocated time, we need to increase the timeout so that weblogic can wait and create a connection and then start the apps. How to achieve this?
Currently the server crashes and forcing to shutdown the error listed below
<Oct 10, 2012 5:08:47 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:09:48 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:49 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "oltpDS": IO Error: Socket read timed out>
<Oct 10, 2012 5:10:50 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oltpDS' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
 at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:302)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
 Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out
 at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:276)
 at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1249)
 at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1166)
 at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:249)
 at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1155)
 Truncated. see log file for complete stacktrace
javax.naming.NameNotFoundException: Unable to resolve 'oltpDS'. Resolved ''; remaining name 'oltpDS'
 at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
 at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
 at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
 at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
 at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
 at javax.naming.InitialContext.lookup(InitialContext.java:392)
 at com.healthedge.j2ee.PooledConnectionHelper.addDataSource(PooledConnectionHelper.java:202)
 at com.healthedge.j2ee.PooledConnectionHelper.getSTConnection(PooledConnectionHelper.java:281)
 at com.healthedge.j2ee.PooledConnectionHelper.getConnectionIgnoreTxn(PooledConnectionHelper.java:268)
 at com.healthedge.j2ee.PooledConnectionHelper.getConnection(PooledConnectionHelper.java:251)
 at com.healthedge.query.execution.Query.prepareStatement(Query.java:504)
 at com.healthedge.query.execution.Query.setValue(Query.java:716)
 at com.healthedge.config.util.ReferenceResolutionHelper.setConstraintValues(ReferenceResolutionHelper.java:277)
 at com.healthedge.config.util.ReferenceResolver.getTypeReference(ReferenceResolver.java:232)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:221)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:211)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:187)
 at com.healthedge.config.util.ReferenceResolver.resolveTypeReference(ReferenceResolver.java:156)
 at com.healthedge.config.eval.HicIdentifier.getReference(HicIdentifier.java:58)
 at com.healthedge.startup.StartupService.startup(StartupService.java:56)
 at com.healthedge.startup.wl.WLStartupService.main(WLStartupService.java:13)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployments(ClassDeploymentManager.java:186)
 at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsAfterAppAdminState(ClassDeploymentManager.java:162)
 at weblogic.management.deploy.classdeployment.StartupClassPrelistenService.start(StartupClassPrelistenService.java:13)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
NESTED TRACES DONE
>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Oct 10, 2012 5:11:18 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Oct 10, 2012 5:11:18 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Hi,
It looks like your DB is down for now and that is reason why the server cannot initialize your App while startup.
Check which Data source you are using and make initial capacity as zero and try to restart the server again.
Note: you need to do this changes from JMS module under %Domain_Home% / config / jdbc/
Regards,
Kal

JDev 10.1.3 - running any application results in connection pool error

After creating a new project with a MySQL connection and since removing the project, I receive this error no matter which application I try to run through the local OC4J of JDev 10.1.3.0.4.3673.
I can recreate this issue with a brand new app workspace & project with a single html file.
06/07/06 14:08:19 WARNING: Application.setConfig Application: current-workspace-app is in failed state as initialization failedjava.lang.InstantiationException: Error occurred initializing connectors. Exception is: Exception creating connection pool. Exception: oracle.oc4j.sql.config.DataSourceConfigException: Unable to create : com.mysql.jdbc.Driver
Jul 6, 2006 2:08:19 PM com.evermind.server.Application setConfig
I'm guessing this is a connection pool issue, but I'm not sure how I associated this connection to the pool, or where to remove it. I've reviewed the help files and searched through this forum, and see references to the connection pool on the AS, but not JDev 10.1.3 itself.
Any pointers are appreciated! In the mean time I'm continuing my search!

Can you please clarify the following...
1) Can we run MDB applications within JDeveloper 10.1.3 ? I noticed there is a jms.xml file in embedded OC4J.
2) How can we test MDB applications within JDeveloper linked to a JMS Destination OC4J based ?

How can I use the Connection Pool with DB2

Hi All,
I am facing the problem with the usage for the Connection Pool.
I want to use DB2 via JNDI lookup.
But when starting the Weblogic server, Error occured with the following message.
<Error> <JDBC> <Cannot startup connection pool "MyJDBCPool" Cannot load driver class : com.ibm.db2.jdbc.app.DB2Driver>
DB2 and Weblogic are on the same machine.
In case of the use of remote DB2 database, I also encountered the same error.
Configurations are as follows.
<JDBCConnectionPool DriverName="com.ibm.db2.jdbc.app.DB2Driver"
MaxCapacity="10" Name="MyJDBCPool"
Password="{3DES}gCGsOfD9M6iwOtgL2v/NpA==" Targets="myserver"
TestConnectionsOnReserve="false" TestTableName="test" URL="jdbc:db2://localhost:6789/yongjoo"/>
<SNMPAgent Name="mydomain"/>
<JDBCDataSource JNDIName="acsdb" Name="acsdb" PoolName="MyJDBCPool" Targets="myserver"/>
Could you please give some information about this problem? I will appreciate your kindness.

Hi Joe,
Thanks your help.
Perhaps It's my fault for Weblogic console's setting.
After I reset the target server in console, Error message disappeared.
But, when I call the TestCode, I encountered another error message. The error
is NameNotFoundException.
When lookingup the JNDI name, NameNotFoundException errer occured. I tried to
change my setting and JNDI name, but the results are the same.
Would you please give me some information about this one more time? I will be
appreciated for your help.
Follows are Config.xml
<JDBCConnectionPool DriverName="com.ibm.db2.jdbc.app.DB2Driver" MaxCapacity="10"
Name="MyJDBCPool" Password="{3DES}gCGsOfD9M6iwOtgL2v/NpA==" Targets="myserver"
TestConnectionsOnReserve="false" TestTableName="test"
URL="jdbc:db2://localhost:6789/yongjoo"/> <SNMPAgent Name="mydomain"/>
<JDBCDataSource JNDIName="acsdb" Name="acsdb" PoolName="MyJDBCPool"
Targets="myserver"/>
and follows are TestCode,
url = "t3://localhost:7001"; //default URL
datasource = "jdbc/acsdb";
Context ctx = null;
Hashtable p = new Hashtable();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL, url);
try{
ctx = new InitialContext(p);
System.err.println("initialContext(p)"+ctx); <-- success
ds = (DataSource)ctx.lookup("java:comp/env/jdbc/acsdb");
}catch(NameNotFoundException ne){
throw new ConnectionException(); .
}catch(NamingException ne){
throw new ConnectionException();

The connection pool does not exist?

Can somebody tell what is happening? For some reason the Sun Java Application Server 8 seems to think that there is no connection pool. For a moment everything worked. I did not change the configuration but now I get this message (if I open the admin console and ping the Connection Pool its there). Here is a part of the server.log file:
[#|2006-05-06T19:12:54.453+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise|_ThreadID=10;|UTIL5047: Connection Pool does not exist: [DB2 yhteysConnectionPool]|#]
[#|2006-05-06T19:12:54.453+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise|_ThreadID=10;|UTIL5048: Error Loading Jdbc Resource: [jdbc/aarre]|#]
[#|2006-05-06T19:12:54.453+0300|INFO|sun-appserver-pe8.1_02|javax.enterprise|_ThreadID=10;|Error loading Jdbc Resource:jdbc/aarre. skipping...|#]
[#|2006-05-06T19:12:55.031+0300|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Exception occurred while satisfying optional package dependencies : {0}
java.lang.NullPointerException
     at com.sun.enterprise.deployment.backend.OptionalPkgDependency.satisfyOptionalPackageDependencies(OptionalPkgDependency.java:183)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:270)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:591)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:237)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:284)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]

Hi,
I'm experiencing the same problem.
Did you solve the problem and if yes how ?
Thanks,
EDH

How to Troubleshoot the Connection Pool Exception?

Dear Oracle Gurus, very good afternoon to you.
I'm looking forward for some tips/troubleshoting guide to escape from the below exception, that occres very frequently to one of application that 100+ users will login from different locations & work on and update the data and save their work, where all in sudden they can't acces the application and it gets down.
Most of the times in the server log I observed below.
weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool RemoteDesktop.main to allocate to applications, please increase the size of the pool and retry..
Please help me on, how to overcome this kind of exception.
In Weblogi c server I see below kind of Warnings.
If you set the buffer size to zero in a servlet, it would fail to respond and would initiate an infinite loop in the server. WebLogic Server would ultimately display a Errors:
ExecuteThread: '157' for queue: 'weblogic.kernel.Default' has been busy for "633" seconds working on the request "Http Request: : ../updates/process_manager.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.
I searched over google for this kind of error, See otherusers posted the same kind of errors but didn't have any positive replies to troubleshoot this issue.
I also got Oracle Dev link on Weblogic version upgrade product where they fixed similar kind of error it seems. Which is shown below.
http://docs.oracle.com/cd/E13222_01/wls/docs61/notes/bugfixes2.html -- BUG # CR106186
details:
"Suspend Checker Thread" prio=10 tid=0x23eb90 nid=0xfec runnable
<May 14, 2003 10:53:34 AM PDT> <Warning> <WebLogicServer> <000337>
<ExecuteThread: '10' for queue: 'default' has been busy for "1,181" seconds working on the request "Http Request: servlet_uri", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>
This problem was solved with a code fix.
Looking forward for some help, Thank you inadvance.
FYI..
I'm using oracle thin driver JDBC connection/Weblogic 8.1
Edited by: user1072948 on Apr 26, 2012 11:55 AM

I agree that looking into the number of connections that you have open when you see
weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool RemoteDesktop.main to allocate to applications, please increase the size of the pool and retry..
would be a good idea; but I would suggest that you don't increase without thinking about the consequences. I would look more closely at what the connections to the database are doing, for instance, how long are the connection being left open for? What are the queries that are being run? Should you expect to see all the connections in the connection pool being used? What is the current connection pool limit? Are you simply going to increase the number of connections to find that they are also waiting? What is the load on the database at the time?
It's the other error that you say you see
ExecuteThread: '157' for queue: 'weblogic.kernel.Default' has been busy for "633" seconds working on the request "Http Request: : ../updates/process_manager.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.
What does this JSP do? Why would this be busy for so long? Is it related to the previous exception that you have? I'd ask you delevelopment team to look into this.
In short, it sounds like you have load issues on your server(s) and a careful tuning of the system after a full analysis (thread dumps, heap profiling, connection pool monitoring and code review) would probably be beneficial. It may be that restricting the thread pool may help, it may be that increasing the connection pool would help. I'd not plump for a quick fix here.

Obiee 11g connection pool error

Hai Experts,
Gudmorning.I'm trying to migrate my 10g rpd to 11g.i have given the connection pool details.but it is showing the connection pool failed.
can anyone help me regarding this.??
Thanks in advance,
Chaitanya.

Hi,
Check this..http://siebel-essentials.blogspot.com/2010/09/11-obiee-11g-tips-4-connecting-to.html
http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10540/conn_pool.htm#insertedID0
Even go through the link Saichand gave.
Regards,
Srikanth
Edited by: Srikanth Mandadi on Nov 19, 2010 11:12 PM

Connection Pool error

Hello,
I am getting the following error in Answers while trying to view the results
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 16001] ODBC error state: IM002 code: 0 message: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified. (HY000)
SQL Issued: SELECT reports."YEAR" saw_0, REPORTs."Total " saw_1 FROM sample_prod_pc ORDER BY saw_0
And in the administration tool during the consistency check i am getting the following warning
[39028] The features in the database sample_prod do not match the defaults.This can cause the query problems.
Please let me know where is the problem.
Thanks in Advance.

Hi Kishore,
Thanks for the reply.
I am able to import the metadata from from this datasource like administrationtool->file->import->from database.
Its working fine without any problems.But when i say update row counts its throwing the following errors.
[NQODBC][SQL_STATE:HY000][nqserror: 10058] A general error has occured.
[nqsError :43093]An errror occured while processing the EXECUTE Physical statement.
[nQSError: 17001]Oracle Error Code:12154,message:ORA-12154:TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach.
[nQSerror: 17014] Could not connect to ORacle database.
Is that means no problem with the DSN connection,but the problem is with the connection pool?
Please help me out.
Thanks in advance.

resources connection pool error in weblogic ????!!!!!

I have pl/sql webservice that call from C#.net .
After call webservice in .net the jdbc connection of weblogic do not close
AND in Webloic have resources connection pool error .
then .net can not call this web service ..
Edited by: Esmaiel Soroor on May 31, 2013 8:34 PM

This is the wrong forum for this question.
CM.

Cannot get a connection, pool error Timeout waiting for idle object

my connection pool setting is
maxActive="3" minIdle="2"                maxWait="10000"              removeAbandoed="true" logAbandoned="true"         removeAbandonedTimeout="30"         autoreconnection="true"
we have 7 people hitting the group of search functions ,
about 3 minutes I get
I got error like
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object         at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:104)         at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)         at Deferment.showResult.checStudent(showResult.java:135)         at Deferment.showResult.doPost(showResult.java:99)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)         at org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.java:402)         at org.apache.catalina.servlets.InvokerServlet.doPost(InvokerServlet.java:170)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)         at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
I just wonder
1) Cannot get a connection, pool error Timeout waiting for idle object-> cause by connection pool leaking or other problem.
2) Setting the maxactive to -1 ( suggestion from Google) , if I set my connection to ulimit , waht should I put on minIdle="2"
3) How can I test my connection pool have problem or not ? is
SHOW PROCESSLIST; tolding me someinformation? I use Mysql
Thank you!

I try something like ps2 = conn.prepareStatement(target);
            ps2.setString(1, UNumber); // set input parameter
            rs = ps2.executeQuery();
            sendMail = 0;//how many rows we can find.
            while (rs.next()) {
                sendMail++;
            ps2.close();
            rs.close();
            conn.close();
if ((count1 == 0) || (count2 == 0)) {
                conn.rollback();
            } else {
                conn.commit();
                conn.setAutoCommit(true);
            ps.close();
            calstat2.close();
            conn.close();
calstat = (CallableStatement) conn.prepareCall("{call findStudent}");
            calstat.executeQuery();
            calstat.close();
            conn.close();is that enought? what else I should do to make sure I did close all the connection, after I use it ?
thank you

Where is the connection pooling implemented?

Hi!
I�m a bit curious. Does anybody know where the connection pooling is implemented? Is it in the provider or in the Oracle client?
Best regards,
Mattias Alm�n, Consignit AB

It is implemented in the provider.
Thanks
Martha

Problem: Failed to open the connection. Error Code 0x800002F4 (-2147482892)

Problem: Failed to open the connection. Error Code 0x800002F4 (-2147482892)
This is on two (2) separate machines. These are NEW INSTALLATION development work stations (laptops). One is Vista (Visual Studio 2008 / Crystal Reports 2008), and the other is Windows XP Pro (Visual Studio 2003 / Crystal Reports XI R1).
I am using EXISTING CODE (established over several years), and EXISTING REPORTS (established over several years). Old development station was XP Pro, as above, and still exists, and still works fine.
I can open the report in Crystal, and see the results just fine. Data for the report is obtained via ODBC.
Can someone identity the actual error by the Error Code above, and advise. Thanks You in Advance.

Ok, so let's start at step 1:
SP 1 just released and I'd recommend applying that. The SO is available from here:
https://smpdl.sap-ag.de/~sapidp/012002523100010503722008E/cr2008_sp1.exe
For future reference, msm matching the above SP is here:
https://smpdl.sap-ag.de/~sapidp/012002523100011715292008E/cr121_mm.zip
and msi is here:
https://smpdl.sap-ag.de/~sapidp/012002523100011722132008E/cr121_redist_install.zip
Step 2: a few questions:
a) I am not sure what CR SDK you are using; RDC, .NET? I suspect that you are using the CR assemblies for .NET, but do confirm.
b) what is the database you are connecting to?
c) is this a web or a win app?
Step 3: As the error can mean any number of things (to me it's just means something went wrong during the attempt to connect to the database...), the solution may vary, however the troubleshooting steps remain quite consistent:
1) Do make sure the report is indeed working in the CR 2008 designer (e.g.; make sure "saved data" is not enabled.
2) Try a simple new windows app with one of your reports. See if you have a report with no subreports and use it
3) If that works, use a report with subreports
4) If the above does not work in (1) above, create a new report to the same ODBC connection, do not code any database connection - let the report prompt for the logon parameter (PWD)
5) Run the new report in your new app, enter the PWD when prompted
6) If this works, add your database logon code
7) If that works, add your original report (again, preferably with no subreports)
8) If that fails, ensure that the subreport and main report use the same database connection type (ODBC)
9) If it works, see if you can determine the difference between your old app and the new app.
Ludek

Possible to detect if a connection was fetched from the connection pool?

Is there any way to differentiate between newly opened connections and connections that came from the connection pool? It would have to work without requiring a round trip to the server because I'd only use it to optimize away a procedure call that I now have to do for every connection that is opened.
If the answer is different for the classic provider and the fully managed one, please provide both.

@Op. What you are trying to do can't be done.

How to track the connection pool refresh details

Hi,
Could you please help to track the connection pool refresh details.
Thanks
Panneer

Hi,
I want track connection pool refresh details for oracle application server 10.1.3.4.
Please help me to get this info.
Thanks
Panneer

Infinite loop - A stale JDBC connection was detected in the connection pool

Hello.
I have a simple JSP (no servlets) application with a single Fastlane Reader style view object to back it up. I'm deploying my application under OC4J 10g 9.0.4 using BC4J 9.0.3.11.50 (JDev 9.0.3.3) on RHEL 3.0, j2sdk1.4.2_03.
I run with -Djbo.debugoutput=console
Every so often, intermittently, and totally unpredictably, I see this on stdout for OC4J:
03/12/23 07:42:07 [33326] A stale JDBC connection was detected in the connection pool
03/12/23 07:42:07 [33327] Creating a new pool resource
03/12/23 07:42:07 [33328] Trying connection/2: url='jdbc:oracle:thin:@somedb:1521:somedbsid' info='{user=someuser, password=somepass, dll=ocijdbc9, protocol=thin}' ...
This message occurs over and over ultimately resulting in hundreds upon thousands of failed connections to the database. I have to forcibly restart OC4J to stop it.
The weird thing about it is that it seems to only start doing this on one system (which is our internal deployment site); it works fine under an OC4J running in IDE or on a preproduction machine.
Has anyone experienced this before - or at the very least, can clue me in on getting BC4J to be a little more verbose on the connection failure?
Thanks and Happy Holidays,
Sean

Hi did you find an answer?
if so, could you post it here?
thanks

Regarding the connection pool Error

Similar Messages

Maybe you are looking for