SJSAS 8 connection pool settings ignored

I have my connection pool settings set to 200 max connections and a 5 minutes max wait time. But when I run my application I get a "Cannot allocation more connections" exception after only 3 minutes and the database shows that there are less than 100 connections. What's the problem?
Caused by: javax.resource.spi.ResourceAllocationException: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:283)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:147)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:122)
at com.sun.messaging.jms.ra.ConnectionFactoryAdapter.createConnection(ConnectionFactoryAdapter.java:96)
... 30 more
Caused by: com.sun.enterprise.resource.PoolingException: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.
at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:275)
at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:211)
at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:172)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:268)
... 33 more

I face a similar problem.
I'm using Sun Application Server 8.1 and my systems connects to Iplanet LDAP 5.1.
have my connection pool settings set to 100 max connections and a 3 minutes max wait time. But when i run my application, i found that the server never release any of my connection even when the connection expires from the pool. If i run a load test, I get a "Cannot allocation more connections" exception after a while.
If i run the same code in Sun App Server 6.1, it works fine. Is there some problem with Sun Application Server 8.1? Is there a patch for it?

Similar Messages

Ejb MDB Pool Settings ignored?

Hi.
I have a series of MDBs, and have tried to increase performance by setting the InitialSize and MaxSize values of the bean in the ejb-j2ee-engine.xml (not version 3!).
However, it doesnt seem to make any difference and messages seem to be getting processed sequentially, as if there was only one instance of the bean.
Here is the layout of my xml.
<ejb-j2ee-engine
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="ejb-j2ee-engine.xsd">
<description/>
<enterprise-beans>
<enterprise-bean>
<ejb-name>mySimpleMDB</ejb-name>
<jndi-name>jms/myTestQueue</jndi-name>
<message-props>
<destination-name>jms/myTestQueue</destination-name>
<connection-factory-name>jms/queueConnectionFactory</connection-factory-name>
<property>
<property-name>InitialSize</property-name>
<property-value>1</property-value>
</property>
<property>
<property-name>MaxSize</property-name>
<property-value>1</property-value>
</property>
<property>
<property-name>ResizeStep</property-name>
<property-value>1</property-value>
</property>
</message-props>
</enterprise-bean>
</enterprise-beans>
</ejb-j2ee-engine>
Is this the correct location - i am pretty sure it is by looking at the documentation.
regards,
Andrew

Hi Vladimir - here are the relevant XML files:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
 <display-name>TestApp</display-name>
 <message-driven>
 <description>Validates</description>
 <display-name>Validation</display-name>
 <ejb-name>FileValidationMDB</ejb-name>
 <ejb-class>com.test.dts.ejb.FileValidationMDBBean</ejb-class>
 <transaction-type>Container</transaction-type>
 <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
 <message-driven-destination>
 <destination-type>javax.jms.Queue</destination-type>
 </message-driven-destination>
 <env-entry>
 <description/>
 <env-entry-name>ejb/beanRefContext</env-entry-name>
 <env-entry-type>java.lang.String</env-entry-type>
 <env-entry-value>classpath:beanRefContext.xml</env-entry-value>
 </env-entry>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <container-transaction>
 <method>
 <ejb-name>FileValidationMDB</ejb-name>
 <method-name>onMessage</method-name>
 <method-params>
 <method-param>javax.jms.Message</method-param>
 </method-params>
 </method>
 <trans-attribute>Required</trans-attribute>
 </container-transaction>
 </assembly-descriptor>
</ejb-jar>
ejb-j2ee-engine.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<ejb-j2ee-engine
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:noNamespaceSchemaLocation="ejb-j2ee-engine.xsd">
 <description/>
 <enterprise-beans>
 <enterprise-bean>
 <ejb-name>FileValidationMDB</ejb-name>
 <jndi-name>jms/dts/registeredFiles</jndi-name>
 <message-props>
 <destination-name>jms/dts/registeredFiles</destination-name>
 <connection-factory-name>jms/dts/queueConnectionFactory</connection-factory-name>
 <property>
 <property-name>parallel-consumers</property-name>
 <property-value>10</property-value>
 </property>
 <property>
 <property-name>InitialSize</property-name>
 <property-value>10</property-value>
 </property>
 <property>
 <property-name>MaxSize</property-name>
 <property-value>10</property-value>
 </property>
 <property>
 <property-name>ResizeStep</property-name>
 <property-value>1</property-value>
 </property>
 </message-props>
 </enterprise-bean>
 </enterprise-beans>
</ejb-j2ee-engine>
jms-resources.xml
<?xml version="1.0" encoding="UTF-8"?>
<jms-resources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="jms-resources.xsd">
 <connection-factory>
 <name>jms/dts/XAConnectionFactory</name>
 <sap-local-factory-type>
 <type>javax.jms.XAConnectionFactory</type>
 <virtual-provider>default</virtual-provider>
 </sap-local-factory-type>
 </connection-factory>
 <connection-factory>
 <name>jms/dts/queueConnectionFactory</name>
 <sap-local-factory-type>
 <type>javax.jms.XAQueueConnectionFactory</type>
 <virtual-provider>default</virtual-provider>
 </sap-local-factory-type>
 </connection-factory>
 <connection-factory>
 <name>jms/dts/topicConnectionFactory</name>
 <sap-local-factory-type>
 <type>javax.jms.XATopicConnectionFactory</type>
 <virtual-provider>default</virtual-provider>
 </sap-local-factory-type>
 </connection-factory>
 <destination>
 <name>jms/dts/registeredFiles</name>
 <type>javax.jms.Queue</type>
 <sap-local-destination-type>
 <virtual-provider>default</virtual-provider>
 
 <property>
 <description>
 Message Delivery Attempts Limited - We dont limit...
 </description>
 <config-property-name>
 deliveryAttemptsLimited
 </config-property-name>
 <config-property-value>false</config-property-value>
 </property>
 <property>
 <description>Delay in Milliseconds</description>
 <config-property-name>
 deliveryDelayInterval
 </config-property-name>
 <config-property-value>60000</config-property-value>
 </property>
 </sap-local-destination-type>
 </destination>
</jms-resources>
Hope this sheds some light on the subject...
Andrew

How to update Connection pool in Unix environment?

I am trying to come up with a secure way to update the username and password in connection pool. The environment is Unix and we won't have access to Admin tool or database to create Repository Variable. Is there a command in unix to update the rpd connection pool? Any suggestions?

Hi,
I believe there is no command available (see the following link for details).
Changing the Oracle BI Database Connection Pool Settings
http://download.oracle.com/docs/cd/E12096_01/books/AnyInConfig/AnyInConfigDataSource5.html
You may also log a SR and confirm this with Oracle Support.
Regards,
Hussein

Reg:Problem with Connection Pool

Hi all,
I copied DAc analysis RPD from the link (http://www.rittmanmead.com/2009/01/analyzing-bi-apps-etl-runs-using-obiee-and-the-dac-repository/ ) into my existing RPD by changing the connection pool of DAC Analysis RPD to the connection pool settings of my Existing RPD.
W_ETL_DEFN,W_ETL_DEFN_RUN,W_ETL_FOLDER,W_ETL_GROUP_STEP,W_ETL_PHASE,W_ETL_RUN_STEP,W_ETL_STEP,S_ETL_DAY
All these tables are coming from a schema BISchema.. Except S_ETL_DAY table. it is coming from the Usage Tracking tables and all the tables in the Usage tracking are coming from OBIAPP Schema.
In order to know about the ETL Runs Over time we need S_ETL_Day table..
So how do I import S_ETL_Day table to DAC folder..where the Schema of both DAC tables and Usage tracking table is Different.
Need Help....

that you can do but there is a way to use that S_ETL_DAY table in do a double mapping in the BMM layer so that you can those fields in that particular table...

Restart required when I make changes to Connection Pools in Sun App Srv 9

When I make changes to the connection pool settings in Sun Application Server 9, i.e. when I change maximum connections or resize size, do I need to manually restart the domain? Is it a best practice to restart, or is it not needed at all?
Thanks!
Dailysun

no, changing the pool parameters like maxsize, steadypoolsize etc., does not need restart.
http://docs.sun.com/app/docs/doc/819-3658/6n5s5nkld?a=view#ablch
Thanks,
-Jagadish

How to configure connection pooling in tomcat?

how to configure connection pooling in tomcat and how to use the connection pooling in the jsp and servlets?

thanks for the reply, i have configured the connection pool settings in the tomcat.
I created a class with static method, which will return the connection object.
whenever i need the connection object, iam invoking the static method, once its usage is over iam closing thew connection..
is it the right way of using the connection object in the web application.

Problem creating a connection pool for mssql server

Hi
i downloaded the microsoft type 4 driver for JDBC and i have installed it. now i am trying to create a connection pool for MS Sql server but each time i ping i keep getting an error telling me
Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Connection could not be allocated because: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket
please can someone help out on this
Ifeanyichukwu

I assume that you installed the driver correctly. You did go into the app sever admin and set the JVM path? You do this by going to Application Server | JVM Settings | Path Settings and putting in an entry for Classpath Prefix.
If that is done and it's not something basic like your database isn't turned on, then it must be your settings. To to Sun's site and search for dbping. http://developers.sun.com/prodtech/appserver/utilities/dbping/dbping_overview.html
Deploy this program and run it. It is a very simple tool that lets you test different property settings. Play around with different settings until you get a ping.
If that doesn't work post your connect pool settings.
Good luck
Mike

No connection pool with oracle thin driver

Hi all,
whenever I try to set up my server as target for an Oracle connection pool on OPracle
8.1.7, I get the following exception:
java.sql.SQLException: Illegal Arguments
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:857)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:189)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:249)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
The Oracle driver classes12.zip is the very first in my classpath, connection pool
settings are:
<JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
Name="Oracle Connection Pool"
Properties="dll=ocijdbc8;USER=zapper;protocol=thin;PASSWORD=oracle"
TestTableName="CABIN" URL="jdbc:oracle:thin:@192.168.0.2:1521:eins"/>
Do I need any additional software besides the driver and weblogic??
Thx
Christian

You're welcome :)
Regards,
Slava Imeshev
"Christian" <[email protected]> wrote in message
news:[email protected]...
>
That worked!
Thx
"Slava Imeshev" <[email protected]> wrote:
Hi Christian,
There is a couple of problems with the pool definition.
First, the connection pool and datasource names can't
contain spaces. Second, USER and PASSWORD
should be in lower case, i.e. user and password accordingly.
Regards,
Slava Imeshev
"Christian" <[email protected]> wrote in message
news:[email protected]...
Hi all,
whenever I try to set up my server as target for an Oracle connectionpool
on OPracle
8.1.7, I get the following exception:
java.sql.SQLException: Illegal Arguments
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:857)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:189)
at
oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:249)
atoracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
atweblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connection
EnvFactory.java:193)
at
weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connection
EnvFactory.java:134)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
The Oracle driver classes12.zip is the very first in my classpath,connection pool
settings are:
<JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
Name="Oracle Connection Pool"
Properties="dll=ocijdbc8;USER=zapper;protocol=thin;PASSWORD=oracle"
TestTableName="CABIN" URL="jdbc:oracle:thin:@192.168.0.2:1521:eins"/>
Do I need any additional software besides the driver and weblogic??
Thx
Christian

Startup problems with XA connection pools on Oracle and WLS 6.1

I am having starup problems trying to set up a WLS 6.1 connection pool using
XA. When I try to start the server, I get the following exception:
<Nov 19, 2001 3:06:28 PM EST> <Error> <JDBC> <Cannot startup connection pool
"dbdev1XAPool" weblogic.common.ResourceException: java.sql.SQLException:
open failed for XAResource 'dbdev1' with error XAER_RMERR : A resource
manager error has occured in the transaction branch. Check Oracle XA trace
file(s) (if any) for database errors. The Oracle XA trace file(s) are
located at the directory where yo
u start the Weblogic Server, and have names like
xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
at
weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:600)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:194)
at
weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:54)
at
weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
at
weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620
at
weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
The contents of the Oracle trace file:
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
150627.1312:344.344.330727191:
xaoopen:
xa_info=Oracle_XA+Acc=P/cmauser/admin+SesTm=100+DB=dbdev1+Threads=true+LogDi
r=.+DbgFl=0x15,rmid=330727191,flags=0x0
150627.1312:344.344.330727191:
ORA-12560: TNS:protocol adapter error
150627.1312:344.344.330727191:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
150627.1312:344.344.330727191:
xaoopen: return -3
I am running WLS 6.1 and Oracle 8.1.7 on windows (separate machines). The
connection pool settings are:
<JDBCConnectionPool CapacityIncrement="0"
DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="40"
MaxCapacity="40" Name="dbdev1XAPool"
Properties="user=cmauser;password=admin;dataSourceName=dbdev1"
RefreshMinutes="15" ShrinkingEnabled="false" SupportsLocalTransaction="true"
Targets="cmatest" TestTableName="hppcontentsource" />
I have not had any problems connecting to the same database through regular
JDBC connection pools or through the utils.dbping utility.
What am I doing wrong?

This is a dup message. Add "DebugConfigInfo OFF" in httpd.conf.
Jong
[email protected] (Olaf Foellinger) wrote:
>
Hi,
we're trying to setup apache on linux so that it's forwarding all jsp
requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
modules according to the documentation. When apache starts it shows the
following warning:
[Tue Jan 9 13:22:55 2001] [warn] Loaded DSO
/usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
might crash under EAPI! (please recompile it with -DEAPI)
and in fact, when we try to load a jsp page we get
[Tue Jan 9 13:29:14 2001] [notice] child pid 5780 exit signal
Segmentation fault (11)
Does anyone have a working solution ? Can bea provide us with a plugin
compiled with EAPI ?
Greetings Olaf

Configuring JMS Connection Pooling

Hi there,
          as far as I understand, if I use a resource-ref when declaring a JMS connection factory, pooling connections, sessions, and producers is automatically enabled. Is there any way for fine-tuning the way this pool works, e.g. configuring minimum/maximum pool sizes?
          We are using WLS 9.2 MP 1, using WebSphere MQ as remote JMS provider (with com.ibm.mq.jms.MQXAQueueConnectionFactory as factory implementation).
          Best regards
          Martin

Hi Tom,
          thanks for your answer. Assuming that the BEA connection pooling works fine, there is still the IBM ConnectionFactory implementation that provides its own connection pooling.
          Do you know a way to configure this part? I only see the Java API of this class when registering it in the JNDI tree, and it provides no access to connection pooling settings.
          Best regards
          Martin

How is connection pooling done in ias ?

is it the "DataSource Registration' ->'DataSource Pool' ->'MaxPoolSize' or is it 'Data Access Driver'-> 'Cache'-> 'Maximum Connections'
or is it somewhere else ?

The connection pool settings for a particular datasource should be done in Datasource Pool-> MaxPoolSize.
The Driver-> Maximum Connections is the maximum no. of connections to the particular database.
Note the difference between these two, two different datasources could connect to a database using the same database driver.
Hope this helps.
Thanks,
Rakesh.

Strange problem since changing some settings Connection Pool

Since changing the following settings in my connection pool, I have been seeing strange behavior with an application that has been deployed for over a year.
 
The settings I changed were the following:
 
Maximum Capacity: Changed from 25 to 100 
Statement Cache Size: Changed from 10 to 200 
Shrink Frequency: Changed from 900 to 300 
Connection Reserve Timeout: Changed from 10 to 5 
Maximum Waiting for Connection: Changed from 2147483647 to 50
 
I was wondering if anyone had any comments on these settings as well as any insight as to why I am seeing the results of a prepared statement
 
("select count(*) from event where event_id = ?" )
 
come back as 0 for the user that just created a record a few minutes before. At the same time another user can log in to the application and cause the same query to run and they get a count of 1 for the record the other user just created. Then if I restart Weblogic both users get a count of 1
 
Driver 9.0.2.0.0 
Weblogic 8.1.3.0

try
select * from v$session where lower(module) like 'jdbc%';if you don't find .... so... no connection from jdbc...
Because when jdbc pool ... start.... It should create connection ... hold on database.

Has anyone run the connection pooling for mysql & tomcat successfully?

I'm trying to set up connection pooling. I'm following the how-to page at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
But when i test the DBTest/test.jsp file, tomcat displays an error =
could not load jdbc driver class 'null'(msdos)
i have placed all the required .jar files in the tomcat lib.
below is the cofiguration i did to the server.xml file



<Server port="8005" shutdown="SHUTDOWN" debug="0">

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>

<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>


<Service name="Tomcat-Standalone">


<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8080" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="100" debug="0" connectionTimeout="20000"
useURIValidationHack="false" disableUploadTimeout="true" />




<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="8009" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="10" debug="0" connectionTimeout="20000"
useURIValidationHack="false"
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>











<Engine name="Standalone" defaultHost="localhost" debug="0">



<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>


<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>







<Host name="localhost" debug="0" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<Context path="/my-jsp" docBase="c:\JSP-Files" debug="0"
privileged="true" reloadable="true" />
 <Context path="" docBase="c:\Inetpub\wwwroot" debug="0" privileged="true" />
<Context path="/sharon" docBase="C:\Tomcat 4.1\webapps\sharon" debug="0" privileged="true" />





<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
 timestamp="true"/>




<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log." suffix=".txt"
timestamp="true"/>
<Ejb name="ejb/EmplRecord" type="Entity"
home="com.wombat.empl.EmployeeRecordHome"
remote="com.wombat.empl.EmployeeRecord"/>



 
<Environment name="maxExemptions" type="java.lang.Integer"
value="15"/>
<Parameter name="context.param.name" value="context.param.value"
override="false"/>
<Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
type="javax.sql.DataSource"/>
<Resource name="jdbc/TestDB"
 auth="Container"
 type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/TestDB">
<parameter>
 <name>factory</name>
 <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
 </parameter>
 
 <parameter>
 <name>maxActive</name>
 <value>100</value>
 </parameter>
 
 <parameter>
 <name>maxIdle</name>
 <value>30</value>
 </parameter>
 
 <parameter>
 <name>maxWait</name>
 <value>10000</value>
 </parameter>

<parameter>
<name>user</name>
<value>javauser</value>
</parameter>
<parameter>
<name>password</name>
<value>javadude</value>
</parameter>

<parameter>
<name>driverClassName</name>
<value>org.gjt.mm.mysql.Driver</value>
</parameter>

 <parameter>
 <name>url</name>
 <value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
</parameter>
</ResourceParams>
<Resource name="mail/Session" auth="Container"
type="javax.mail.Session"/>
<ResourceParams name="mail/Session">
<parameter>
<name>mail.smtp.host</name>
<value>localhost</value>
</parameter>
</ResourceParams>
<ResourceLink name="linkToGlobalResource"
global="simpleValue"
type="java.lang.Integer"/>
</Context>
</Host>
</Engine>
</Service>



</Server>
Pleas4 help!!!

you have your driver jar in Tomcat\common\lib?
if so, check your classpath, it could be that.

How does Kodo manage DB connection pools?

Hi,
As per the documentation, JDO options MinPool and MaxPool are no longer
part of the specification. I expect this means the JDO implementation is
supposed to manage database connection pools appropriately. Now, I would
like to understand Kodo's approach to this, and whether I have any control
on pool configuration at all via the deprecated MinPool and MaxPool
properties -or are these properties simply ignored.
On a related topic, I am confused about the effects of closing
PersistenceMangers after every use, from a performance point of view (if
the connection pool is not managed by Kodo, am I incurring additional
overhead by not re-using a PersistenceManager?). I have read in different
places in the documentation that it is good to re-use PersistenceManagers
as well as the fact that although PersistenceManagers are
garbage-collected and connection resources freed as a result, it is
recommended to call close() on them anyway. Bottom line, are there any
side-effects to religiously asking the PersistenceManagerFactory (I have
several, one each for the different data sources I use) for a new
PersistenceManager at the beginning of each method and calling close() in
a finally{} clause?
I'm sorry if this has been answered elsewhere - I'd appreciate it if you'd
just point me to the discussion if so.
Thanks.
-Krishna Choppella
Digital Harbor, Inc.

would like to understand Kodo's approach to this, and whether I have any
control on pool configuration at all via the deprecated MinPool and
MaxPool properties -or are these properties simply ignored.Currently, Kodo uses the MinPool and MaxPool properties to configure the
JDBC connection pool. Starting with version 3.0, Kodo will use separate
pooling properties.
Bottom
line, are there any side-effects to religiously asking the
PersistenceManagerFactory (I have several, one each for the different
data sources I use) for a new PersistenceManager at the beginning of
each method and calling close() in a finally{} clause?Well, you miss out on the simple object caching employed by PMs. Each PM
keeps a cache of the objects it manages. Reusing a PM allows it to build
up a bigger cache, and makes calls to getObjectById and 1-1 relation
traversals faster.
Additionally, each cached object maintains state in its persistent fields
(subject to the RetainValues setting and other settings), so retrieving
object state can be faster when the object is already cached and has
already been read.
However, if you employ Kodo's L2 caching plugin (Performance Pack), then
you get all these benefits regardless of whether or not you re-use
individual PMs.

Connection Pool Failure: "No suitable driver"

Hi,
Upon server startup, I get the following result:
<Nov 7, 2001 4:18:32 PM CST> <Error> <JDBC> <Cannot startup connection pool "ora
cleTrufflePool" No suitable driver>
I assumed it was a path problem, but in the startWebLogic.cmd script I've set the PATH and CLASSPATH variables to the same as in a separate command window that can successfully dbping the Oracle db.
One thing I completely don't understand is what the URL value should be for the pool, and I can't see a pattern in the examples and docs I've found on this. Here are my pool settings, at any rate:
Name: oracleTrufflePool
URL: myOracleServerName
Driver Classname: weblogic.jdbc.oci.Driver
Properties:
user=user
password=password
server=myOracleServerName
ACLName: user
Password: password
As you can see, I also don't understand whether the Oracle user name and password must be duplicated in the Properties section, or should they really only be listed in the ACLName and Password fields (in the Server Console UI)?
TIA,
Steve

Hi. The issue is that the URL you give is not the URL the driver (weblogic.jdbc.oci.Driver)
wants. The URL should be "jdbc:webLogic:oci". The properties user, password and server
will be passed to the driver for conenction attempts. The ACL is for who gets to use the
pool, and the other password entry is only if you need the DBMS password to be encrypted
in the XML. If so, set that password value, and don't have it in the driver properties.
Joe
Steve Clark wrote:
>
Hi,
Upon server startup, I get the following result:
<Nov 7, 2001 4:18:32 PM CST> <Error> <JDBC> <Cannot startup connection pool "ora
cleTrufflePool" No suitable driver>
I assumed it was a path problem, but in the startWebLogic.cmd script I've set the PATH and CLASSPATH variables to the same as in a separate command window that can successfully dbping the Oracle db.
One thing I completely don't understand is what the URL value should be for the pool, and I can't see a pattern in the examples and docs I've found on this. Here are my pool settings, at any rate:
Name: oracleTrufflePool
URL: myOracleServerName
Driver Classname: weblogic.jdbc.oci.Driver
Properties:
user=user
password=password
server=myOracleServerName
ACLName: user
Password: password
As you can see, I also don't understand whether the Oracle user name and password must be duplicated in the Properties section, or should they really only be listed in the ACLName and Password fields (in the Server Console UI)?
TIA,
Steve

SJSAS 8 connection pool settings ignored

Similar Messages

Maybe you are looking for