SAP J2EE 6.20 DB Connection Pool Strangeness

Has anyone seen a problem with the SAP J2EE dbpool service whereby no matter how big the connection pool is set to be only a single connection ever seems to be used by applications ?
This is clustered SAP J2EE SP18 (67440.20) connection to an AS/400 using the IBM jt400 driver.
Bizarrely similar applications using a different connection pool (but the same driver and back end AS/400) continue to work as normal - creating multiple "used" connections as and when required.
Many thanks for any pointers !!

used SQL tool to migrate.
used SAP note : 1271375

Similar Messages

RFC Connection error in SM59 for SAP J2EE

Hi All,
i am getting the following error description while testing the connection for
SAP J2EE ...
Connection Test SAPJ2EE
Connection Type TCP/IP Connection
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program sapfallback not registered
Error Details LOCATION: SAP-Gateway on host filip / sapgw00
Error Details DETAIL: TP sapfallback not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 1483
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Tue Mar 31 02:44:35 2009
Error Details VERSION: 2
Help me resolve this
Regards,
Mahesh.

Hi,
Please follow this steps:
Creating RFC Destinations in the ABAP and Java Environment
You need to create the following RFC destinations in transaction SM59 (ABAP) and the Visual Administrator (Java):
u2022 AI_RUNTIME_JCOSERVER
u2022 AI_DIRECTORY_JCOSERVER
u2022 LCRSAPRFC
u2022 SAPSLDAPI
Depending on your client settings, it may be necessary to be logged on your SAP Exchange Infrastructure host as SAP system user with the authorization to maintain customizing tables and to release transport orders. Note, that user "SAP*" or "DDIC" does not have these authorizations.
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination: AI_RUNTIME_JCOSERVER
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: AI_RUNTIME_<SID> where <SID> is the SAP system ID of your Integration Server host. Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host. To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in Target System.
8. Save your settings.
9. Repeat the steps 3 u2013 8 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
Program ID: AI_DIRECTORY_<SID>, where <SID> is the SAP system ID of your SAP XI host
LCRSAPRFC
Program ID: LCRSAPRFC_<SID>, where <SID> is the SAP system ID of your SAP XI host.
SAPSLDAPI
Program ID: SAPSLDAPI_<SID>, where <SID> is the SAP system ID of your SAP XI host.
10. Leave the transaction SM59 open for later tests.
J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the J2EE Engine administration tool.
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for AI_RUNTIME_JCOSERVER that you used in the step Maintaining the RFC connection above. Additionally, set the number of processes to 10.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
7. Repeat the steps 3 u2013 6 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
u2022 Corresponding values from SM59
u2022 Number of processes: 10
LCRSAPRFC
u2022 Corresponding values from SM59
u2022 Number of processes: 3
SAPSLDAPI
u2022 Corresponding values from SM59
u2022 Number of processes: 3
Testing the RFC Destination
After you have maintained all RFC destinations in both the ABAP and Java environment, you can check all the connections above as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection. No error should be displayed.
This will solve your problem.
Thanks
Laxmi Bhushan

Connection Pooling in JDBC Adapter

Does anybody know if the JDBC Adapter uses connection pooling? If yes, how can one adjust the pool size etc.
Thanks!

Hi Roland,
Refer this note 831162...
9. J2EE JDBC Connector and Connection Pooling
Q: Does the JDBC Adapter support the use of the SAP WebAS J2EE engine's JDBC Connector and connection pool?
A: Currently, each JDBC channel will create its own JDBC connection. The use of the J2EE engine's JDBC Connector and connection pooling mechanism is not supported.
Regards
Anand

Establishing multiple WLEC connection pools

Running WLS 6.0 communicating with WLE 4.2:
I'm looking at setting up multiple connection pools to communicate with multiple
WLE application domains.
The code fragment below is from the BEA documentation and works fine if you know
the domain(pool) name. My code uses the "lookup" method in the InitialContext
class to get the pool name for single WLEC pool/domain configuration. Is there
a method to return a list of domain(pool) names?
Each WLEC connection pool has a Tobj_Bootstrap object that lets you access the
associated WLE domain. The WLEC component provides an object called BootstrapFactory
which provides access to the Tobj_Bootstrap object for a particular WLE domain.
Include the following code in your WebLogic Server client to connect to a WLE
domain:
Tobj_Bootstrap myBootstrap = Tobj_BootstrapFactory.getClientContext("myPool");
where
The getClientContext() method returns the Tobj_Bootstrap object that is associated
with myPool. If getClientContext() cannot find a WLEC connection pool with this
name, it returns null.
myPool is the name of a WLEC connection pool for the desired WLE domain. This
WLEC connection pool needs to be defined in the Administration Console.

Well ... It boiled down to ACLs.
"Sreeram" <[email protected]> wrote:
>
Hi
I have WLI application ( 7.0 ) and another J2EE appliction configured
on WLS (
7.0 ). If I have multiple jdbc connection pools configured to access
different
( or even the same ) databases, I am unable to get the connection to
execute a
sql query in the J2EE app. The connection pool gets initialized properly
during
the server startup and I can see them in the console but when I try to
acquire
a connection from the pool for execution of a jdbc stmt, I am unable
to obtain
a connection. Did any one succeed in configuring mulitple jdbc connection
pools
and WLI and another J2EE app to run together on WLS 7.0? Any suggestions
are welcome.
Thanks
Sreeram

Multiple JDBC connection pools

Hi
I have WLI application ( 7.0 ) and another J2EE appliction configured on WLS (
7.0 ). If I have multiple jdbc connection pools configured to access different
( or even the same ) databases, I am unable to get the connection to execute a
sql query in the J2EE app. The connection pool gets initialized properly during
the server startup and I can see them in the console but when I try to acquire
a connection from the pool for execution of a jdbc stmt, I am unable to obtain
a connection. Did any one succeed in configuring mulitple jdbc connection pools
and WLI and another J2EE app to run together on WLS 7.0? Any suggestions are welcome.
Thanks
Sreeram

Well ... It boiled down to ACLs.
"Sreeram" <[email protected]> wrote:
>
Hi
I have WLI application ( 7.0 ) and another J2EE appliction configured
on WLS (
7.0 ). If I have multiple jdbc connection pools configured to access
different
( or even the same ) databases, I am unable to get the connection to
execute a
sql query in the J2EE app. The connection pool gets initialized properly
during
the server startup and I can see them in the console but when I try to
acquire
a connection from the pool for execution of a jdbc stmt, I am unable
to obtain
a connection. Did any one succeed in configuring mulitple jdbc connection
pools
and WLI and another J2EE app to run together on WLS 7.0? Any suggestions
are welcome.
Thanks
Sreeram

Datasource Connection Pooling - Per environment or per J2EE node?

Hi all,
I have a question about the JDBC service regarding the connection pooling.
For external datasources, we have specified a max. pool size of 25.
Now, is this value per J2EE server node per Dialog Instance, or is this a global setting?
In other words, say we have 5 dialog instances each with 4 server nodes, do we have pools with a total size of 200 maximum connections, or just 25?
Thanks in advance!
Robin van het Hof

Hi Dagfinn,
The below mentioned exception is thrown the most:
[code]
com.shell.gep.service.employee.jdbc.JDBCEmployeeServiceNew#sap.com/irj#com.shell.gep.service.employee.jdbc.JDBCEmployeeServiceNew#Niels.Dijksman#502#####Thread[PRT-Async 16,5,PRT-Async]##0#0#Fatal##Plain###Unable to execute query: /* com.shell.gep.service.employee.jdbc.JDBCEmployeeServiceNew */SELECT NVL(WWW, 'Y') FROM PROVISIONING.SHELLDETAILS WHERE SAMACCOUNTNAME = ?, cause: Closed Connection#
     at com.shell.gep.service.employee.jdbc.JDBCEmployeeServiceNew.doMasterQuery(JDBCEmployeeServiceNew.java:410)#
     at com.shell.gep.service.employee.jdbc.JDBCEmployeeServiceNew.internalGetProperty(JDBCEmployeeServiceNew.java:361)#
     at com.shell.gep.service.employee.jdbc.JDBCEmployeeServiceNew.getProperty(JDBCEmployeeServiceNew.java:66)#
     at com.shell.gep.service.employee.AggregatedEmployeeService.getProperty(AggregatedEmployeeService.java:153)#
     at com.shell.gep.service.employee.AggregatedEmployeeService.getProperty(AggregatedEmployeeService.java:153)#
     at com.shell.gep.service.employee.EmployeeServiceImpl.getProperty(EmployeeServiceImpl.java:116)#
     at com.shell.gep.news.iviews.dynpage.NewsDynPage.getMyExternal(NewsDynPage.java:143)#
     at com.shell.gep.news.iviews.dynpage.NewsDynPage.doProcessBeforeOutput(NewsDynPage.java:114)#
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)#
     at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)#
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
     at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)#
     at java.security.AccessController.doPrivileged(Native Method)#
     at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)#
     at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)#
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)#
     at java.lang.Thread.run(Thread.java:534)#
java.sql.SQLException: Closed Connection#
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)#
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)#
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)#
     at oracle.jdbc.driver.OracleConnection.privatePrepareStatement(OracleConnection.java:962)#
     at oracle.jdbc.driver.OracleConnection.prepareStatement(OracleConnection.java:869)#
[/code]
So it apears it's an Oracle problem rather than a SAP problem indeed

Configuring JCo3 Connection Pool with single sign on on non SAP Java server

Hi Everyone,
i have configured a connection pool on JBoss as per JCo3 Documentation and is working great.
Now I need help to configure this connection pool with single sign on so that RFc on SAP ECC systems are executed using end users credential rather than using single user name password used to configure JCo connection pool.
On SAP Java stack I am sure its possible within Java WebDynpro and i assume using JCA resource adapter. But what if we don't want to use SAP Java App server.
Any help will be appreciated.
Thanks,
Divyakumar Jain

Eason, 你好！
I have exactly the same problem. Did you find a solution to this problem? If so, please let me know!

A strang problem about Resin database connection pool

I am a beginner，hope somebody can help me.
my web site occured a strange problem after I used the Resin database connection pool instead of
connecting directly
the error message as follows:java.lang.IllegalArgumentException: Request cannot be null
at javax.servlet.ServletRequestWrapper.<init>(ServletRequestWrapper.java:100)
at javax.servlet.http.HttpServletRequestWrapper.<init>(HttpServletRequestWrapper.java:92)
at com.caucho.server.connection.RequestAdapter.<init>(RequestAdapter.java:96)
at com.caucho.server.webapp.DispatchRequest.<init>(DispatchRequest.java:97)
at com.caucho.server.webapp.IncludeDispatchRequest.<init>(IncludeDispatchRequest.java:77)
at com.caucho.server.webapp.IncludeDispatchRequest.createDispatch(IncludeDispatchRequest.java:87)
at com.caucho.server.webapp.RequestDispatcherImpl.include(RequestDispatcherImpl.java:389)
at com.caucho.server.webapp.RequestDispatcherImpl.include(RequestDispatcherImpl.java:345)
at com.caucho.jsp.PageContextImpl.include(PageContextImpl.java:807)
at _jsp._intro__jsp._jspService(/intro.jsp:60)
at com.caucho.jsp.JavaPage.service(JavaPage.java:75)
at com.caucho.jsp.Page.pageservice(Page.java:571)
at com.caucho.server.dispatch.PageFilterChain.doFilter(PageFilterChain.java:155)
at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:211)
at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:177)
at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:221)
at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:263)
at com.caucho.server.port.TcpConnection.run(TcpConnection.java:331)
at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:464)
at com.caucho.util.ThreadPool.run(ThreadPool.java:408)
at java.lang.Thread.run(Thread.java:595)


<resin xmlns="http://caucho.com/ns/resin"
xmlns:resin="http://caucho.com/ns/resin/core">

<log name='' level='info' path='stdout:' timestamp='[%H:%M:%S.%s] '/>
<log name='com.caucho.java' level='config' path='stdout:'
timestamp='[%H:%M:%S.%s] '/>
<log name='com.caucho.loader' level='config' path='stdout:'
timestamp='[%H:%M:%S.%s] '/>

<dependency-check-interval>2s</dependency-check-interval>

<javac compiler="internal" args=""/>



<thread-pool>

<thread-max>128</thread-max>

<spare-thread-min>25</spare-thread-min>
</thread-pool>

<min-free-memory>1M</min-free-memory>
<server>

<class-loader>
<tree-loader path="$resin-home/lib"/>
</class-loader>

<keepalive-max>500</keepalive-max>
<keepalive-timeout>120s</keepalive-timeout>

<http server-id="" host="*" port="8080"/>


<cluster>
<srun server-id="" host="127.0.0.1" port="6802" index="1"/>
</cluster>

<ignore-client-disconnect>true</ignore-client-disconnect>

<cache path="cache" memory-size="10M"/>

<ping>

</ping>

<web-app-default>

<cache-mapping url-pattern="/" expires="5s"/>
<cache-mapping url-pattern="*.gif" expires="60s"/>
<cache-mapping url-pattern="*.jpg" expires="60s"/>

<servlet servlet-name="directory"
servlet-class="com.caucho.servlets.DirectoryServlet"/>
</web-app-default>

<database>
<jndi-name>jdbc/artunion</jndi-name>
<driver type="org.gjt.mm.mysql.Driver">
<url>jdbc:mysql://localhost:3306/union</url>
<user>as</user>
<password>as</password>
</driver>
<prepared-statement-cache-size>8</prepared-statement-cache-size>
<max-connections>20</max-connections>
<max-idle-time>30s</max-idle-time>
</database>

<host-default>
<class-loader>
<compiling-loader path='webapps/WEB-INF/classes'/>
<library-loader path='webapps/WEB-INF/lib'/>
</class-loader>

<access-log path='logs/access.log'
format='%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i"'
rollover-period='1W'/>

<web-app-deploy path='webapps'/>

<ear-deploy path='deploy'>
<ear-default>

</ear-default>
</ear-deploy>

<resource-deploy path='deploy'/>

<web-app-deploy path='deploy'/>
</host-default>

<resin:import path="${resinHome}/conf/app-default.xml"/>

<host id=''>
<document-directory>D:/artunion</document-directory>

<web-app id='/'>

<class-loader>
<simple-loader path="$host-root/xsl"/>
</class-loader>
<servlet-mapping url-pattern="/servlet/*" servlet-name="invoker"/>
</web-app>
</host>
</server>
</resin>
Thank you!

Strange behaviour when using connection pooling with proxy authentication

All
I have developed an ASP.NET 1.1 Web application that uses ODP.NET 9.2.0.4 accessing Oracle Database 8i (which is to be upgraded to 10g in the coming months). I have enabled connection pooling and implemented proxy authentication.
I am observing a strange behaviour in the live environment. If two users (User 1 and User 2) are executing SQL statements at the same time (concurrent threads in IIS), the following is occurring:
* User 1 opens a new connection, executes a SELECT statement, and closes this connection. The audit log, which uses the USER function, shows User 1 executed this statement.
* User 2 opens the same connection (before it is released to the connection pool?), excutes an INSERT statement, and closes this connection. The audit log shows User 1, not User 2, executed this statement.
Is this a known issue when using connection pooling with proxy authentication? I appreciate your help.
Regards,
Chris

Hi Chris,
I tried to reproduce your complaint, but was unable to. I didnt use auditting however, just a series of "select user from dual" with proxy authentication. You might want to see if you can put together a small complete testcase for this and open a sr with support.
Cheers
Greg

Error creating connection pool in j2ee 1.4

i want to create a connection pool in j2ee 1.4 but it is giving an error " sun.jdbc.odbc.JdbcOdbcDriver"
the driver class i enter is sun.jdbc.odbc.JdbcOdbcDriver
please tell me the possible error

now, i have installed j2ee 1.5 bundled version. Now i have tried the same thing. nut it is giving an error "sun.jdbc.odbc.JdbcOdbcDriver canot be cast to javax.sql.XADataSource".
Now, i have downloaded Microsoft jdbc Driver for SQL Server 2000 and set the classpath for those three files that comes under the lib folder. Then i used "com.microsoft.jdbcx.sqlserver.SQLServerDataSource" class, then another error comes "Class not found or classpath is not set for "com.microsoft.jdbcx.sqlserver.SQLServerDataSource" class.
however, this class file is packed in one of those three jar files for which i have set the classpath.
PLEASE HELP

JCO connection tab in disabled mode in sap J2EE engine/webdynpro/local/proj

Dear all,
I'm developing the simple webdynpro object using netweaver developer studio, but when i deploy it to sap J2ee engine and go there to set the JCO connection, I find the jco connectiuon tab in the diabled mode. I need to configure the new jco connection in order to run the project. Please suggest.
thanks,
Anup.

Hi Anup,
You can find service "SLD data supplier" under server->services list.
Refer following links for configuring SLD and JCO connections:
Re: Web Dynpro - Problem with (SLD) JCO Connection
Re: Configuration of SLD
Regards,
Bhavik

Connection Pooling wrong/strange behaviour

Hi
I have ORACLE 10g Instance with many schemas user1, user2, user3 ...
I have IIS Windows 2003 Server with .NET 3.5
I use Oracle.DataAccess, Version 2.102.2.20
Application work in one SITE and one Application Pool
Sameting going wrong with database connection pool.
I use connection strings like this
ConnectionString1=Data Source=aaa;User ID=user1;Password=123;Connection Lifetime=30
ConnectionString2=Data Source=aaa;User ID=user2;Password=123;Connection Lifetime=30
ConnectionString3=Data Source=aaa;User ID=user3;Password=123;Connection Lifetime=30
after sometime of work I have got violation of foreing key
and my surprise I request connection ConnectionString1 and work in user2
when Recycle IIS Application Pool all go ok
that case I have one time for now
Other strange case I have with one stored procedure and problem persist in time
not every day but often
procedure AppLoginBySessionId(iSessionId in out applogins.sessionid%type,
iState out number,
iUserName out bsusers.username%type,
iRoles out varchar2,
iLcid out applogins.lcid%type) as
begin
end;
When all is OK procedure return some values for iState, iUserName, iRoles, iLcid
When going wrong iState, iUserName, iRoles, iLcid are empty
When problem happen I try to modify procedure like this:
procedure AppLoginBySessionId(iSessionId in out applogins.sessionid%type,
iState out number,
iUserName out bsusers.username%type,
iRoles out varchar2,
iLcid out applogins.lcid%type) as
begin
raise_application_error(-20001,'error ... ');
end;
and when application try execute stored procedure for my surprise
no error happend, but parameters are empty (iState, iUserName, iRoles, iLcid)
When in aplication execute OracleConnection.ClearAllPools() all go OK again
or other time I fix problem with "alter system flush shared_pool"
I try to fix problem with ConnectionString parameter Statement Cache Size=0;Statement Cache Purge=true;Min Pool Size=0,
also set database parameter session_cached_cursors=0, and change client to 11g
But problem persist time to time

Hi Chris,
I tried to reproduce your complaint, but was unable to. I didnt use auditting however, just a series of "select user from dual" with proxy authentication. You might want to see if you can put together a small complete testcase for this and open a sr with support.
Cheers
Greg

Error in SAP JCO connection leads to SAP J2EE engine restart

Hi All
i am using SAP Jco 2.0 to connect to backend.The code runs fine for tables but when i try to access fields like
getExportParameterList().getField("EMPLOYEENUMBER").toString(); it leads to j2ee engine restarts.
Is it a bug?
Is it possible for an exception to restarts server even with error?
Regards
Shankar

Hi,
Does your application uses any property files or log files? If so, check if they are available in the specified location.
Check the defaultTrace, you will know why the server is getting restarted. Have a placeholder in the defaultTrace so that you can easily identify the error.
Thanks,
Venkat

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.

SAP JCo3 connection pool instance release

Hi Experts,
I am using SAP JCo3 version to connect SAP from remote Java application.I have created connection pool with JcoDestination.
I want to know how to release a Jcodestination (pool instance)once its finishes with the functionalities so that connection pool can be managed properly.
Thanks In advance.

Hi,
I think we dont need to close the connection. Anyway we define Connection Timeout(ms) while JCO Destionations configurations. I guess that is enough.
Size
Currently used
Maximum used
Max.connections
Max.pool size
Connection Timeout(ms)
Max. wait time(ms)
Timeout Check Period(ms)
See the information about connection closing in below link:
http://www.winfobase.de/lehre/lv_materialien.nsf/intern01/FB09D79A41930E34C125709F0046180C/$FILE/Tips&Tricks_JCo_Programming.pdf
Regards,
Charan

SAP J2EE 6.20 DB Connection Pool Strangeness

Similar Messages

Maybe you are looking for