Database connection - API layer?

I'm just doing a quote for a job, and the potential client has sent me over a 20 page document produced by someone else quoting, with a very detailed scope of the project.
Way more detailed and flowery than anything I would do, but just wanted to ask about one thing.
Its a database site, and will use mySQL for that.
In the document it has a little diagram referencing:
- the solution (i.e. the website I guess)
- the database
And between the two, an API Layer.
To me, all that really happens is that a connection file is created which connects the site to the database using a bit of PHP.
Am I missing something, not doing more than I maybe should be doing, or is this just a typical way of presenting something that looks a bit more techie and involved than it perhaps is?
Any comments welcome! Thanks.

I had a look on Google, and found some stuff on database abstraction layers, which I must admit is a new one on me.
Is this something that people would recommend doing as a matter of course, or something that would be surplus to requirements most of the time?

Similar Messages

JApplet + database connection

hey all...
i'm double posting here a little but i posted this in JApplet forum and i got no answer )):
hey all!!
i'm fairly new to java.... what i'm trying to do is a application build into a web page. java applet, i've been doing it for a while and everything is ok. have had some problems alogn the way but he java API is a great resource and i have worked out pretty much everything i needed so far. i have forms in the applet and different kinds of tables with updatable values. i source most of the values straight from mysql database and it is all good.... well not really... i've been running the applet on my desktop and it is all good but today i tried to run it from a different computer via apache server and then i find out that i can NOT connect to the database ))): then i realized that java applets run in the browser so i understand why not. simply because everything that the applet is supposed to find (different classes) are not there. actually it can see the objects since my gui is spead over a few custom build packages. since it brings the gui up then i has to access the objects ok but connection to database is not existent??? i have also read on the internet that applet should be able to connect to its source (my desktop in this case) but it didn't say how to do that.
could anybody point me to the right direction??? advice or a tutorial would be appreciated
thanks
v.v.

hey!!!
thanks for your reply!!! well i have already solved it (i think at least).
actually i do connect to 'application server'... sort of. we have to implement 3-tier architecture. so one tier for database and its connection one for sql queries and one for front-end. since my resources are limited i have got all this running on a single computer like this
(object) gui -> connects to -> (object) sql queries -> conncets to -> singleton connection object. -> connect to mysql
what i needed to do to get it work is this
1. step one in data layer (1 st tier) in JavaDetails.java which gives me my login credentials
private String url = "jdbc:mysql://10.10.10.4:3306/sumtec"; //change 127.0.0.1 to an actual ip addr
2. step two
comment out bind-address in my.cnf
3. step three
add user, which credetials i connect with, to mysql.user table and give him password
i have used '%' for host so this user can connect from anywhere on my home network or anywhere in the world in fact
4. step four
restart mysql
and that's about it... i feel that this is not the best thing to do. creating applets with database connection is just no the right thing to do, but i didn't know at the time i have decided on this design and now i have quite a bit done so i have to finish it.
i use this project just to practice java anyway so i think it will be helpful... to me at least ((:
thanks
v.v.

Database connection in a WebDynpro Application - urgent

Hi
I am facing a problem with database connection. I am trying to develop a normal webdynpro application.
I want to retrieve data from a table and show it.
But my query is not giving the expected output. It is not even raising errors.
Please give me an answer
Thanks & regards
Aparnna

Connection con=null;
Statement st=null;
ResultSet rs=null;
public void wdDoInit()
    //@@begin wdDoInit()
try
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con = DriverManager.getConnection("jdbc:odbc:erdsn","root","enteg123");
st=con.createStatement();
    catch(Exception e){
    //@@end
public void onActiononClickLogin(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActiononClickLogin(ServerEvent)
     String desig=null;
try{
rs = st.executeQuery("select * from Login where Empid like uid and Pword like pw");
    if(rs.next()){
           desig=rs.getString("Designation");
     wdComponentAPI.getComponent().getMessageManager().reportSuccess(desig);
    if(desig.equalsIgnoreCase("Employee")){
          wdThis.wdFirePlugEmpOutPlug();
     else
     wdComponentAPI.getComponent().getMessageManager().reportWarning("Invalid input!");
      }catch(Exception e){

How can I use SQL TOOLKIT concurrently with Database Connectivity ?

I have installed LabVIEW 6.1 with the Database Connectivity Toolkit and the SQL Compatibility Toolkit (e.g. _SQL folder). I am trying to make the transition from the SQL Toolkit VIs to the Database Connectivity toolkits, but for compatability with existing systems I would like to be able to run the two sets of VIs concurrently (but not in the same app).
When I read into 6.1 a connection VI that I wrote with LabVIEW 6.0 and the SQL toolkit the connection reference type gets changed from a number to type connection (see attachments) . Does compatbility mean that my SQL toolkit VIs are converted to a form compatible with the new ADO ?
Can I use the SQL Toolkit VIs or the Database connectivit
y VIs in the same installation of 6.1 ?
Can I have the SQL Toolkit VIs appear on the functions pallette and function as they did when only the SQL toolkit was installed ?
Attachments:
CNNCT.vi ‏20 KB
CNNCT.vi ‏22 KB

In response to your #2 below:
Actually it is possible to have the old SQL Toolkit and new Database
connectivity in the same installation of LabVIEW. I have only tried it on
6i, but don't see why it wouldn't work on 6.1. The trick is not to install
the SQL toolkit compatabitily VI's. The old SQL toolkit uses the Intersolve
dll through ODBC while the new Database connectivity uses ADO so it is
possible to use both methods not only in the same LabVIEW install, but it
the same running application. It has been a while since I originally did
this, so I am posting only to mention that it is possible and not exactly
how to do it. If anyone is interested in more details just respond.
Brian
"Jeff B" wrote in message
news:[email protected]...
> First, direct answers to your direct questions:
>
> 1. Does compatbility mean that my SQL toolkit VIs are converted to a
> form compatible with the new ADO ?
>
> Yes
>
> 2. Can I use the SQL Toolkit VIs or the Database connectivity VIs in
> the same installation of 6.1 ?
>
> No
>
> 3. Can I have the SQL Toolkit VIs appear on the functions pallette
> and function as they did when only the SQL toolkit was installed ?
>
> No
>
>
> Now an elaboration:
>
> Having the old SQL Toolkit and the new Database Connectivity Toolset
> installed on the same version of LabVIEW on the same computer is not
> supported.
>
> Once you install the Database Connectivity Toolset, any VIs written
> with the SQL Toolkit will run, but with the ADO layer, as you
> suspected.
>
> Internally, the only way we can have both the SQL Toolkit and the
> Database Connectivity Toolset installed on the same computer for
> troubleshooting customer issues is to have them installed on different
> versions of LabVIEW. I, for example, have LabVIEW 5.1.2, 6.0.3, and
> 6.1 all installed on my computer, and I have the SQL Toolkit install
> on LabVIEW 5.1.2, and the Database Connectivity Toolset installed on
> LabVIEW 6.0.3. In this configuration I can still run SQL Toolkit VIs
> independent of the Database Connectivity Toolset if I open and run
> them in LabVIEW 5.1.2.

Using database connection in a servlet and get errors after 8 hours

Hey,
I'm running a poker script using applet/servlets and it works great. But for some reason about about 8 hours that database layer stops working. At first I thought it was the connections to mySQL that were timing out (because im using connection pooling) but after turning pooling off (I now create the connection each time) I'm still seeing that same error (I can create a connection but when I do an action ex. like a select statment I get an error). What i'm wondering could it be that the driver I load with Class.forName() some how unloads it's self after x amount of time not being used? Not sure if that is it but if anyone could give me some insight that would be great. The Error i recieve is below:
INFO: Database Event:DatabaseController: Error executing database query.
ERROR: Communications link failure due to underlying exception:
** BEGIN NESTED EXCEPTION **
java.net.SocketException
MESSAGE: Software caused connection abort: recv failed
STACKTRACE:
java.net.SocketException: Software caused connection abort: recv failed
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(Unknown Source)
     at com.mysql.jdbc.util.ReadAheadInputStream.fill(ReadAheadInputStream.java:104)
     at com.mysql.jdbc.util.ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(ReadAheadInputStream.java:144)
     at com.mysql.jdbc.util.ReadAheadInputStream.read(ReadAheadInputStream.java:172)
     at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1839)
     at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2288)
     at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2784)
     at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1531)
     at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1622)
     at com.mysql.jdbc.Connection.execSQL(Connection.java:2370)
     at com.mysql.jdbc.Connection.execSQL(Connection.java:2297)
     at com.mysql.jdbc.Statement.executeQuery(Statement.java:1183)
     at com.softnet.database.DatabaseController.executeDatabaseQuery(DatabaseController.java:190)
     at com.softnet.games.GameServer.validateUser(GameServer.java:438)
     at com.softnet.games.GameServer.handleData(GameServer.java:113)
     at com.softnet.network.HttpConnectionThread.run(HttpServletListener.java:191)
** END NESTED EXCEPTION **
I know the query is good because it works all other times just not after about 8 hours.
--Z3r0CooL

Hey,
Thanks for the responces. For the connection pooling I would open 5 connections and keep them open. So i though maybe after 8 hours after not being used they would timeout. Thats why i turned off conection pooling and create a new connection each time. Anyways i'll post the code below incase i made a mistake somewhere.
package com.softnet.database;
/************************ DatabaseControler **************************/
import java.sql.*;
import java.util.*;
import com.softnet.database.DatabaseConnectionPool;
import com.softnet.database.DatabaseSettings;
public class DatabaseController
implements DatabaseListener
     //Used to make sure the database driver is loaded
     private boolean databaseDriverState = false;
     //Used to store a database connection
     private Connection databaseConnection = null;
     //If to user connection pooling or not
     private boolean useConnectionPooling = false;
     //Used to hold the connection pool varible
     private DatabaseConnectionPool connectionPool = null;
     //Used to store database settings
     private DatabaseSettings databaseSettings;
     //Used to hold the DatabaseController listeners
     private List databaseControllerListeners = new ArrayList();
     //min number of connections for connection pool
     private int minNumberOfConnections = 1;
     //max number of connections for connection pool -1 is unlimited
     private int maxNumberOfConnections = -1;
     //DatabaseController Constructors
     public DatabaseController(DatabaseSettings databaseSettings)
          this.databaseSettings = databaseSettings;
          databaseDriverState = loadDatabaseDriver(databaseSettings.getDatabaseDriver());
     public DatabaseController(DatabaseSettings databaseSettings, boolean useConnectionPooling, int minNumberOfConnections, int maxNumberOfConnections)
          this.databaseSettings = databaseSettings;
          this.useConnectionPooling = useConnectionPooling;
          this.minNumberOfConnections = minNumberOfConnections;
          this.maxNumberOfConnections = maxNumberOfConnections;
          if(useConnectionPooling == true)
               connectionPool = new DatabaseConnectionPool(databaseSettings, minNumberOfConnections, maxNumberOfConnections);
               connectionPool.addDatabaseListener(this);
          else
               databaseDriverState = loadDatabaseDriver(databaseSettings.getDatabaseDriver());
     public DatabaseController() {}
     //Database Settings Get/Set
     public DatabaseSettings getDatabaseSettings()
          return databaseSettings;
     public void setDatabaseSettings(DatabaseSettings databaseSettings)
          this.databaseSettings = databaseSettings;
     //Connection Pooling Get/Set
     public boolean getConnectionPooling()
          return useConnectionPooling;
     public void setConnectionPooling(boolean useConnectionPooling, int minNumberOfConnections, int maxNumberOfConnections)
          this.useConnectionPooling = useConnectionPooling;
          this.minNumberOfConnections = minNumberOfConnections;
          this.maxNumberOfConnections = maxNumberOfConnections;
          if(useConnectionPooling == true)
               if(connectionPool == null)
                    connectionPool = new DatabaseConnectionPool(databaseSettings, minNumberOfConnections, maxNumberOfConnections);
                    connectionPool.addDatabaseListener(this);
          else
               if(connectionPool != null)
                    connectionPool.destroyConnections();
                    connectionPool.removeDatabaseListener(this);
                    connectionPool = null;
     //Return if there connected
     public boolean isConnected()
          boolean isConnected;
          if(databaseConnection != null)
               isConnected = true;
          else
               isConnected = false;
          return isConnected;
     //Used to connect to database or get a connection for the connection pool
     public void connect()
          if(databaseDriverState == false)
               databaseDriverState = loadDatabaseDriver(databaseSettings.getDatabaseDriver());
          //If we dont have a current connection, make one
          if(databaseConnection == null && databaseDriverState == true)
               if(useConnectionPooling == false)
                    try
                         databaseConnection = DriverManager.getConnection(databaseSettings.getDatabaseURL(), databaseSettings.getUserName(), databaseSettings.getUserPassword());
                    catch (SQLException sqle)
                         //Raise event
                         raiseDatabaseEvent("DatabaseController: Error connecting to database. \nERROR: " + sqle.getMessage());
                         databaseConnection = null;
               else
                    databaseConnection = connectionPool.getConnection();
     //Used to disconnect from the database or give back the connection to the connection pool
     public void disconnect()
          if(databaseConnection != null)
               if(useConnectionPooling == false)
                    try
                         //Close DB Connection
                         databaseConnection.close();
                    catch(SQLException ignore) {}
                    finally
                         databaseConnection = null;
               else
                    connectionPool.returnConnection(databaseConnection);
                    databaseConnection = null;
     public ResultSet executeDatabaseQuery(String sSQL)
          ResultSet databaseResult = null;
          if(databaseConnection != null)
               try
                    Statement databaseStatement = databaseConnection.createStatement();
                    databaseResult = databaseStatement.executeQuery(sSQL);
               catch(SQLException sqle)
                    //Raise event
                    raiseDatabaseEvent("DatabaseController: Error executing database query.\nSQL: " + sSQL + "\nERROR: " + sqle.getMessage());
          return databaseResult;
     public int executeDatabaseUpdate(String sSQL)
          int rowsAffected = -1;
          if(databaseConnection != null)
               try
                    Statement databaseStatement = databaseConnection.createStatement();
                    rowsAffected = databaseStatement.executeUpdate(sSQL);
               catch(SQLException sqle)
                    //Raise event
                    raiseDatabaseEvent("DatabaseController: Error executing database update.\nSQL: " + sSQL + "\nERROR: " + sqle.getMessage());
          return rowsAffected;
     //Used to load the Database Driver
     private boolean loadDatabaseDriver(String databaseDriver)
          boolean driverLoaded;
          if(databaseDriver.equals("") == false)
               try
                    //Load Database Driver
                    Class.forName(databaseDriver).newInstance();
                    driverLoaded = true;
               catch (Exception e)
                    //Raise event
                    raiseDatabaseEvent("DatabaseController: Error loading database driver. \nERROR: " + e.getMessage());
                    driverLoaded = false;
          else
               driverLoaded = false;
          return driverLoaded;
     //Wrap the DatabaseConnectionPool Error to the DatabaseController
     public void databaseEventOccurred(DatabaseEvent de)
          raiseDatabaseEvent(de.getErrorMessage());
     //Event Handling Code
     //Used to add database listeners (Its sync'd so you can change the listeners when firing an event)
public synchronized void addDatabaseListener(DatabaseListener databaseControllerListener)
databaseControllerListeners.add(databaseControllerListener);
//Used to remove a listener from the list (Its sync'd so you can change the listeners when firing an event)
public synchronized void removeDatabaseListener(DatabaseListener databaseControllerListener)
databaseControllerListeners.remove(databaseControllerListener);
//Used to send the raise event to the listeners
private synchronized void raiseDatabaseEvent(String databaseError)
DatabaseEvent databaseEvent = new DatabaseEvent(this, databaseError);
Iterator listeners = databaseControllerListeners.iterator();
while(listeners.hasNext())
     DatabaseListener listener = (DatabaseListener) listeners.next();
listener.databaseEventOccurred(databaseEvent);
/********************* DatabaseConnectionPool **************/
package com.softnet.database;
import java.io.*;
import java.sql.*;
import java.util.*;
import com.softnet.database.*;
import com.softnet.database.DatabaseSettings;
public class DatabaseConnectionPool
     //min number of connections
     private int minNumberOfConnections = 1;
     //max number of connections -1 is unlimited
     private int maxNumberOfConnections = -1;
     //Store the connections
     protected Hashtable databaseConnections = null;
     //Database Info
     protected DatabaseSettings databaseSettings;
     //to hold Driver state
     private boolean databaseDriverState = false;
     //To hold connection checker
     private DatabaseConnectionCheck connectionChecker = null;
     //Used to hold the DatabaseConnectionPool listeners
     private List databaseConnectionPoolListeners = new ArrayList();
     public DatabaseConnectionPool(DatabaseSettings databaseSettings, int minNumberOfConnections, int maxNumberOfConnections)
          this.databaseSettings = databaseSettings;
          this.minNumberOfConnections = minNumberOfConnections;
          this.maxNumberOfConnections = maxNumberOfConnections;
          //Load Driver
          databaseDriverState = loadDatabaseDriver(databaseSettings.getDatabaseDriver());
          //Create connection
          createConnections();
     public DatabaseConnectionPool(int minNumberOfConnections, int maxNumberOfConnections)
          this.minNumberOfConnections = minNumberOfConnections;
          this.maxNumberOfConnections = maxNumberOfConnections;
     //Database Settings Get/Set
     public DatabaseSettings getDatabaseSettings()
          return databaseSettings;
     public void setDatabaseSettings(DatabaseSettings databaseSettings)
          this.databaseSettings = databaseSettings;
     //Driver State Get
     public boolean getDatabaseDriverState()
          return databaseDriverState;
     public void createConnections()
          if(databaseDriverState == false)
               databaseDriverState = loadDatabaseDriver(databaseSettings.getDatabaseDriver());
          //Create all connections and load the minimum in the Hashtable
          if(databaseConnections == null)
               if(databaseDriverState == true && minNumberOfConnections != 0)
                    databaseConnections = new Hashtable();
                    for(int i = 0; i < minNumberOfConnections; i++)
                         try
                              databaseConnections.put(DriverManager.getConnection(databaseSettings.getDatabaseURL(), databaseSettings.getUserName(), databaseSettings.getUserPassword()), Boolean.FALSE);
                         catch(SQLException sqle)
                              //Problem break loop and destroy any connections
                              destroyConnections();
                              //Raise event
                              raiseDatabaseEvent("DatabaseConnectionPool: Error creating database connections. \nERROR: " + sqle.getMessage());
                              break;
          //If no connection check exists create one
          if(connectionChecker == null)
               connectionChecker = new DatabaseConnectionCheck(this);
               connectionChecker.start();
     public Connection getConnection()
          Connection connection = null;
          boolean errorWithConnection = false;
          Enumeration connections = databaseConnections.keys();
          synchronized (databaseConnections)
               while(connections.hasMoreElements())
                    errorWithConnection = false;
                    connection = (Connection) connections.nextElement();
                    Boolean state = (Boolean) databaseConnections.get(connection);
                    //If connection is not used, use it.
                    if(state == Boolean.FALSE)
                         try
                              connection.setAutoCommit(true);
                         catch(SQLException e)
                              //Problem with connection remove connection and replace it
                              databaseConnections.remove(connection);
                              try
                                   connection = DriverManager.getConnection(databaseSettings.getDatabaseURL(), databaseSettings.getUserName(), databaseSettings.getUserPassword());
                              catch(SQLException sqle)
                                   errorWithConnection = true;
                         if(errorWithConnection == false)
                              // Update the Hashtable to show this one's taken
                              databaseConnections.put(connection, Boolean.TRUE);
                              // Return the connection
                              return connection;
               //All connections being used check to max to see if we can make a new one
               if(maxNumberOfConnections == -1 || maxNumberOfConnections > databaseConnections.size())
                    try
                         connection = DriverManager.getConnection(databaseSettings.getDatabaseURL(), databaseSettings.getUserName(), databaseSettings.getUserPassword());
                    catch(SQLException sqle)
                         errorWithConnection = true;
                    if(errorWithConnection == false)
                         databaseConnections.put(connection, Boolean.TRUE);
                         return connection;
          //If not connections free and max connections reached wait for a free connection
          return getConnection();
     public void returnConnection(Connection connection)
          boolean errorWithConnection = false;
          //Make sure connection still works
          try
               connection.setAutoCommit(true);
          catch(SQLException e)
               //Problem with connection remove connection and replace it
               databaseConnections.remove(connection);
               try
                    connection = DriverManager.getConnection(databaseSettings.getDatabaseURL(), databaseSettings.getUserName(), databaseSettings.getUserPassword());
               catch(SQLException sqle)
                    errorWithConnection = true;
          if(errorWithConnection == false)
               databaseConnections.put(connection, Boolean.FALSE);
     public void destroyConnections()
          Connection connection = null;
          if(databaseConnections != null)
               //Close all connections
               Enumeration connections = databaseConnections.keys();
               while (connections.hasMoreElements())
                    connection = (Connection) connections.nextElement();
                    try
                         connection.close();
                    catch(SQLException ignore) {}
               //Free up hashtable
               databaseConnections = null;
     private boolean loadDatabaseDriver(String databaseDriver)
          boolean driverLoaded;
          if(databaseDriver.equals("") == false)
               try
                    //Load Database Driver
                    Class.forName(databaseDriver);
                    driverLoaded = true;
               catch (ClassNotFoundException cnfe)
                    //Raise event
                    raiseDatabaseEvent("DatabaseController: Error loading database driver. \nERROR: " + cnfe.getMessage());
                    driverLoaded = false;
          else
               driverLoaded = false;
          return driverLoaded;
     //Event Handling Code
     //Used to add database listeners (Its sync'd so you can change the listeners when firing an event)
public synchronized void addDatabaseListener(DatabaseListener databaseConnectionPoolListener)
databaseConnectionPoolListeners.add(databaseConnectionPoolListener);
//Used to remove a listener from the list (Its sync'd so you can change the listeners when firing an event)
public synchronized void removeDatabaseListener(DatabaseListener databaseConnectionPoolListener)
databaseConnectionPoolListeners.remove(databaseConnectionPoolListener);
//Used to send the raise event to the listeners
private synchronized void raiseDatabaseEvent(String databaseError)
DatabaseEvent databaseEvent = new DatabaseEvent(this, databaseError);
Iterator listeners = databaseConnectionPoolListeners.iterator();
while(listeners.hasNext())
     DatabaseListener listener = (DatabaseListener) listeners.next();
listener.databaseEventOccurred(databaseEvent);
class DatabaseConnectionCheck extends Thread
     private DatabaseConnectionPool connectionPool;
     DatabaseConnectionCheck(DatabaseConnectionPool connectionPool)
          this.connectionPool = connectionPool;
     public void run()
          try
               while(true)
                    //check threads every 30 seconds
                    this.sleep(300000);
                    if(connectionPool.databaseConnections != null)
                         Connection connection = null;
                         Enumeration connections = connectionPool.databaseConnections.keys();
                         synchronized (connectionPool.databaseConnections)
                              while(connections.hasMoreElements())
                                   connection = (Connection) connections.nextElement();
                                   Boolean state = (Boolean) connectionPool.databaseConnections.get(connection);
                                   //If connection is not used, use it.
                                   if(state == Boolean.FALSE)
                                        try
                                             connection.setAutoCommit(true);
                                        catch(SQLException e)
                                             //Problem with connection remove connection and replace it
                                             connectionPool.databaseConnections.remove(connection);
                                             try
                                                  connection = DriverManager.getConnection(connectionPool.databaseSettings.getDatabaseURL(), connectionPool.databaseSettings.getUserName(), connectionPool.databaseSettings.getUserPassword());
                                             catch(SQLException sqle)
                                                  connection = null;
                                             // Update the Hashtable with new connection if its not null
                                             if(connection != null)
                                                  connectionPool.databaseConnections.put(connection, Boolean.FALSE);
          catch(InterruptedException ignored) {}
Basicly the why it works is the connection pool hold the database connections. When the user needs a connection they use the database controller to request a connection (By create a instance and called the connect() method) and the connection is either created or grabed from the connection pool. After the user is done with the connection they call the disconnect() method which closes the connection or returns it to the connection pool.
--Z3r0CooL

Could not load library for database connection LCA

Hi,
I am facing RFC connection prblem while connectiong to database. I have installed SCM5.1 and live cache in single server
Please find the logs.
Work process log:
B Mon Jul 20 11:19:13 2009
B create_con (con_name=LCA)
B Loading DB library 'E:\usr\sap\SC7\DVEBMGS03\exe\dbsdbslib.dll' ...
M *** ERROR => DlLoadLib: LoadLibrary(E:\usr\sap\SC7\DVEBMGS03\exe\dbsdbslib.dll) Error 126 [dlnt.c       241]
M          Error 126 = "The specified module could not be found."
B *** ERROR => Couldn't load library 'E:\usr\sap\SC7\DVEBMGS03\exe\dbsdbslib.dll'
[dbcon.c      4731]
B ***LOG BYG=> could not load library for database connection LCA        [dbds#1 @ 1035] [dbds    1035 ]
A
A Mon Jul 20 11:21:58 2009
A GENER starting remote generation: /SAPAPO/OM_SYNC_LC_DB (requested by W1).
B
SM21:
No shared library found for the database with ID LCA|
No shared library found for the database with ID LCA
/SAPAPO/OM17|/SAPAPO/OM_SYNC_LC_DB|K |SAP Web AS Problem|SBAC   |
Documentation for system log message BY G :
As well as the standard connection, an attempt was made to set up
another database connection, under the specified ID. The Shared Library
for this second database could not be found.
The Shared Library is usually found in the the Executable
directory (profile parameter DIR_LIBRARY) under the name dbs
<dbs>slib<os_ext>. <dbs> stands for the database type and <os_ext>
stands for the operating system-specific extension of the Shared
Libraries.
The database type is determined from the entry that corresponds to the
specified DB ID in the table DBDCON. Check whether the data in this
entry is correct.
ST22
Runtime Errors         DBIF_DSQL2_CONNECTERR
Exception              CX_SY_NATIVE_SQL_ERROR
Date and Time          20.07.2009 11:22:21
Short text
Error setting up a secondary database connection
What happened?
Connection to database system not possible with identifier "LCA".
|----
System environment
SAP-Release 700
Application server... "
Network address...... "
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 8
Shortdump setting.... "full"
Database server... "
Database type..... "ORACLE"
Database name..... "SC7"
Database user ID.. "SAPSC7"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 701
created (date)... "Jul 6 2009 23:47:55"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 50
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Information on where terminated
Termination occurred in the ABAP program "SAPLSLCAPPS" - in
"LCA_EXISTS_LCA_ROUTINE".
The main program was "/SAPAPO/TS_BATCH_RUN ".
In the source code you have the termination point in line 23
of the (Include) program "LSLCAPPSU05".
The program "SAPLSLCAPPS" was started as a background job.
Job Name....... "MACROS"
Job Initiator.. "SC7GEN"
Job Number..... 10222002
The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
in
procedure "LCA_EXISTS_LCA_ROUTINE" "(FUNCTION)", but it was neither handled
locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLSLCAPPS "; its source code begins in line
1 of the (Include program "LSLCAPPSU05 ".
Please help me to resolve the issue.
Suraj

Hi Natalia Khlopina,
I have raised OSS message to SAP.
Below is the information
E:\usr\sap\SC7\SYS\exe\uc\Copy_ of_NTAMD64_15062009>sdbregview -l
Server Utilities    e:/sapdb/programs      7.7.02.08     64 bit    valid
DB Analyzer         e:/sapdb/programs      7.7.02.08     64 bit    valid
PCR 7301            e:/sapdb/programs      7.3.01.21               valid
PCR 7500            e:/sapdb/programs      7.5.00.42     64 bit    valid
SAP Utilities       e:/sapdb/programs      7.7.02.08     64 bit    valid
APO LC APPS         f:/sapdb/lcs/db/sap    6.00.004      64 bit    valid
Redist Python       e:/sapdb/programs      7.7.02.08     64 bit    valid
Base                e:/sapdb/programs      7.7.02.08     64 bit    valid
JDBC                e:/sapdb/programs      7.6.03.02               valid
Messages            e:/sapdb/programs      MSG 0.5010              valid
ODBC                e:/sapdb/programs      7.7.02.08     64 bit    valid
SQLDBC 77           e:/sapdb/programs      7.7.02.08     64 bit    valid
Database Kernel     f:/sapdb/lcs/db        7.7.02.08     64 bit    valid
Loader              e:/sapdb/programs      7.7.02.08     64 bit    valid
SQLDBC              e:/sapdb/programs      7.7.02.08     64 bit    valid
SQLDBC 76           e:/sapdb/programs      7.6.01.15     64 bit    valid
Fastload API        e:/sapdb/programs      7.7.02.08     64 bit    valid
C:\Documents and Settings\sc7adm>disp+work
disp+work information
kernel release                701
kernel make variant           701_REL
compiled on                   NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00
compiled for                  64 BIT
compilation mode              UNICODE
compile time                  Jul 6 2009 23:47:55
update level                  0
patch number                  50
source id                     0.050
supported environment
database (SAP, table SVERS)   700
                              701
operating system
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2
Windows NT 6.0
Thanks for quick responce.
Suraj

Tomcat JDBC Realm Database Connection Error

Hello all,
I am trying to edit the server.xml file on Tomcat so I can use the JDBC Realm instead of the MemoryRealm. Hence, I will be able to read users, passwords and roles from a relational database instead of from the tomcat-users.xml.
I have tried following all the guides on the net I can find, my server.xml looks as follows (after making changes to allow it to use JDBC realm). The only problem is, when I try to run the application the server outputs the following: (after all of these errors have been kicked up a pop-up box then appears titled "Tomcat Manager Application", it asks for a User Name and Password. I have tried the standard user name of "ide" and the password next to it in tomcat-users.xml but it won't accept it. (I am using the netbeans IDE)).
Please could someone suggest any ideas of how I can get the server.xml to work with JDBC realm?
Using CATALINA_BASE:   C:\Documents and Settings\Administrator\.netbeans\5.0beta\jakarta-tomcat-5.5.7_base
Using CATALINA_HOME:   C:\Program Files\netbeans-5.0beta\enterprise2\jakarta-tomcat-5.5.7
Using CATALINA_TMPDIR: C:\Documents and Settings\Administrator\.netbeans\5.0beta\jakarta-tomcat-5.5.7_base\temp
Using JAVA_HOME:       C:\j2sdk1.4.2_08
Created MBeanServer with ID: 1f934ad:107444b1d2b:-8000:ravinder-rdnzoa:1
31-Oct-2005 01:29:33 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8084
31-Oct-2005 01:29:34 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8443
31-Oct-2005 01:29:34 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2174 ms
31-Oct-2005 01:29:34 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
31-Oct-2005 01:29:34 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.7
31-Oct-2005 01:29:34 org.apache.catalina.realm.JDBCRealm start
SEVERE: Exception opening database connection
java.sql.SQLException: org.gjt.mm.mysql.Driver
        at org.apache.catalina.realm.JDBCRealm.open(JDBCRealm.java:646)
        at org.apache.catalina.realm.JDBCRealm.start(JDBCRealm.java:720)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1003)
        at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:440)
        at org.apache.catalina.core.StandardService.start(StandardService.java:450)
        at org.apache.catalina.core.StandardServer.start(StandardServer.java:683)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:537)
        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:324)
        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409)
31-Oct-2005 01:29:34 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
31-Oct-2005 01:29:36 org.apache.catalina.startup.ContextConfig validateSecurityRoles
INFO: WARNING: Security role name IBM used in an <auth-constraint> without being defined in a <security-role>
31-Oct-2005 01:29:36 org.apache.catalina.startup.ContextConfig validateSecurityRoles
INFO: WARNING: Security role name Auditor used in an <auth-constraint> without being defined in a <security-role>
31-Oct-2005 01:29:37 org.apache.struts.tiles.TilesPlugin initDefinitionsFactory
INFO: Tiles definition factory loaded for module ''.
31-Oct-2005 01:29:37 org.apache.struts.validator.ValidatorPlugIn initResources
INFO: Loading validation rules file from '/WEB-INF/validator-rules.xml'
31-Oct-2005 01:29:37 org.apache.struts.validator.ValidatorPlugIn initResources
INFO: Loading validation rules file from '/WEB-INF/validation.xml'
31-Oct-2005 01:29:38 org.apache.catalina.startup.ContextConfig validateSecurityRoles
INFO: WARNING: Security role name IBM used in an <auth-constraint> without being defined in a <security-role>
31-Oct-2005 01:29:38 org.apache.struts.tiles.TilesPlugin initDefinitionsFactory
INFO: Tiles definition factory loaded for module ''.
31-Oct-2005 01:29:38 org.apache.struts.validator.ValidatorPlugIn initResources
INFO: Loading validation rules file from '/WEB-INF/validator-rules.xml'
31-Oct-2005 01:29:38 org.apache.struts.validator.ValidatorPlugIn initResources
INFO: Loading validation rules file from '/WEB-INF/validation.xml'
31-Oct-2005 01:29:39 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8084
31-Oct-2005 01:29:39 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8443
31-Oct-2005 01:29:40 org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
31-Oct-2005 01:29:40 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/60 config=null
31-Oct-2005 01:29:40 org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
31-Oct-2005 01:29:40 org.apache.catalina.startup.Catalina start
INFO: Server startup in 5738 ms
31-Oct-2005 01:29:40 org.apache.catalina.realm.JDBCRealm authenticate
SEVERE: Exception performing authentication
java.sql.SQLException: org.gjt.mm.mysql.Driver
        at org.apache.catalina.realm.JDBCRealm.open(JDBCRealm.java:646)
        at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:344)
        at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:181)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:534)
31-Oct-2005 01:29:40 org.apache.catalina.realm.JDBCRealm authenticate
SEVERE: Exception performing authentication
java.sql.SQLException: org.gjt.mm.mysql.Driver
        at org.apache.catalina.realm.JDBCRealm.open(JDBCRealm.java:646)
        at org.apache.catalina.realm.JDBCRealm.authenticate(JDBCRealm.java:344)
        at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:181)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:534)The server.xml looks as follows:
<?xml version="1.0" encoding="UTF-8"?>



<Server port="8025" shutdown="SHUTDOWN">
    
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"/>
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>
    <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
    
    <GlobalNamingResources>
        
        <Environment name="simpleValue" type="java.lang.Integer" value="30"/>
        
   
    </GlobalNamingResources>
    
    
    <Service name="Catalina">
        
        
        <Connector port="8084" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="utf-8"/>
        
        
        
        <Connector port="8443"
        maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
        enableLookups="false" disableUploadTimeout="true"
        acceptCount="100" scheme="https" secure="true"
        clientAuth="false" sslProtocol="TLS" />
        
        <Connector port="8009" enableLookups="false" redirectPort="8443" protocol="AJP/1.3"/>
        
        
        
        
        
        
        <Engine name="Catalina" defaultHost="localhost">
            
            
            
            
            
            
            
            
            <Realm className="org.apache.catalina.realm.JDBCRealm"
            driverName="org.gjt.mm.mysql.Driver"
            connectionURL="jdbc:mysql://localhost:3306/tomcatusers"
            connectionName="root" connectionPassword="sikhism1"
            userTable="users" userNameCol="user_name" userCredCol="user_pass"
            userRoleTable="user_roles" roleNameCol="role_name" />
            
            
            
            <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="false" xmlValidation="false" xmlNamespaceAware="false">
                
                
                
                
                
                
                
                
                
                
                
            </Host>
        </Engine>
    </Service>
</Server>Many thanks, and apologies for "dumping" all of the code here.

So looking through the java api docs, I found that the tcUtilJDBCOperations has a connect string for the database. Below is the info it outlines. The questions I have it this. How do you specify the psdriver and URL along with do I need to do this as a persistent instance then add my selectstatement as a part of this or can I just specify this and the select statement will use this connection? Any help you can give would be appreciated.
tcUtilJDBCOperations
public tcUtilJDBCOperations(java.lang.String psDriver,
java.lang.String psUrl,
java.lang.String psUsername,
java.lang.String psPassword)Contructor that sets the parameters for connecting to a database
Parameters:
psDriver - The class name of the jdbc driver
psUrl - The URL of the database
psUsername - The username required to access the database
psPassword - The password for the above username
Nick

Why the err Invalid database Connection -CR 11 version in Visual studio 1.1

Hai all,
I am new to using the Crystal report with Visual studio 2003.I am facing Invalid database connection problem. My objective is tyring to upgrade CR 8 to CR11 with VS 1.1 framework(VC++ in .NET 2003).All things like ODBC connection with MS SQL server 2005,generating report going fine with CR8 version but invalid database connection error comes with CR11 version. The configuration details and Code snippet are below for your ref,
Upgrading CR8 to CR11 with VS .NET 2003.
Application framework - VS 1.1 framework
CR                            - 11 Version
DB                            - MS SQL server 2005
Connection                - ODBC
DLL                          - CRPE32 DLL (Version11)
Code snippet:
CODBCDatabase * pDatabase = pApp->GetDatabase();
BOOL bRes;
bRes = ::PELogOnSQLServerWithPrivateInfo(_T("pdsodbc.DLL"), pDatabase->m_hdbc);
Note: pdsodbc dll not found in local and anywhere.But it supports CR 8 but not CR 11.So i downloaded and put it in appropriate place exe path\system32\system and tested.Used and tested p2sodbc dll also but "Invalid DataBase connection" err came.Followed some instruction like changing the Data source name,DSN path,re installing CR 11 version and all but same problem coming.
::PELogOnSQLServerWithPrivateInfo() declation is in the following link
http://www.arcaretentores.com.br/FTP/Format/Report/ProgramF/SEAGAT~1/CRW/DEV/Help/HTML/12a_0708.htm
Thanks in advance
Regards
SatheeshKumar
India.

Thanks for your reply
   The API i have given is not available in Crystal report 11.So i tried with the PELogonServer API of version 11.It also failed.
I am unable to understand the suggestions you gave to me 1) The Report Designer Component (RDC)
2) The CR Assemblies for .NET.
Can you give any link that have related samples or articles to implement the above topics please?
Thanks again,
Satheesh Kumar.D

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!

KIMYONG : Applications Database Connection Pool 관련 parameter 설명

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

Purpose
JVM 이 과도한 CPU / Memory를 사용하게 되어 Application Performance에 영향을 미칠때가 있으며 이럴경우 Connection Pool 관련하여 Parameter Tunning을 해야 할때가 있습니다. 이때 사용되는 Parameter들의 의미를 설명하고자 합니다.
The Applications Database Connection Pool is a pool of JDBC database connections that are shared among java applications. Applications obtain connections from the pool by using the getJDBCConnection(...) methods of AppsContext.
Essentially, each AppsContext has a single database connection associated with it at all times.
The AOL/J layer internally borrows and returns this connection to the pool as needed to maintain connection reference that is properly initialized for the current Java tier AOL security context and NLS state.
FND_MAX_JDBC_CONNECTIONS
============================
The maximum pool size is the maximum allowed sum of the number of available connections and thenumber of locked connections. If the pool reaches the maximum size and all connections are locked, new clients will not be able to borrow a connection until one of the current clients has returned one. The default setting for this parameter is essentially unlimited (about 2 billion).
FND_JDBC_BUFFER_MIN
======================
The buffer minimum is the minimum number of connections that the pool should try to maintain in the available list. When the buffer size falls below the buffer minimum, the pool maintenance thread will be notified to create new connections. When notified, the thread will immediately attempt to create the number of connections to fill the difference. New connections will not be created if the pool is already at its maximum size. When creating new connections the thread uses the attributes of the most recent client request that resulted in a new connection being created.
Setting this parameter to "0" will disable maintenance of the buffer minimum.
However, the buffer maximum will still be maintained.
Setting this parameter to a number greater than the maximum pool size(FND_MAX_JDBC_CONNECTIONS) will disable all buffer maintenance.
FND_JDBC_BUFFER_MAX
======================
The buffer maximum is the maximum number of connections that the pool should try to maintain in the available list. During heavy usage, the buffer may exceed this maximum. However, during periods of low usage, the maintenance thread will decrease the buffer size until the buffer maximum is reached.
If the value of this parameter is an integer, (for example "20") the buffer maximum is static. If the value is a percent (for example, "20%"), the buffer maximum is not constant but instead is calculated dynamically as a percent of total pool size. The buffer minimum is also taken into account when
determining a dynamic buffer maximum.
The exact expression used is:
maximum(t) = buffer minimum + ( (FND_JDBC_BUFFER_MAX/100) * size(t) )
where maximum(t) and size(t) are the buffer maximum and pool size at some time t.
The thread is configured to periodically check the buffer size. If the buffer size is greater than the maximum, the thread will remove either the number of available connections specified by FND_JDBC_BUFFER_DECAY_SIZE or the number of connections in excess of the buffer minimum, whichever is smaller. When connections are removed from the available list, the least recently used ones are removed first.
Setting this parameter to100%, or to a number equal to FND_MAXIMUM_JDBC_CONNECTIONS, or to a number less than or equal to FND_JDBC_BUFFER_MIN will effectively prevent the maintenance thread from ever removing any connections.
FND_JDBC_BUFFER_DECAY_INTERVAL
===================================
The buffer decay interval specifies how often the connection pool maintenance thread should check the buffer size. The thread will check the buffer size at most once every FND_JDBC_BUFFER_DECAY_INTERVAL seconds. The actual time between consecutive thread cycles will vary somewhat depending on the JVM load.
This parameter, along with FND_JDBC_BUFFER_DECAY_SIZE, allows the buffer decay rate to be tuned. For example, if the buffer decay size is 2 and the buffer decay interval is one minute, the buffer decay rate will never exceed two connections per minute. When connections are removed, the least recently used ones are removed first.
FND_JDBC_BUFFER_DECAY_SIZE
=============================
The buffer decay size specifies the maximum number of connections that should be removed during any single thread cycle during which the number of available connections is greater than the buffer size. This parameter, along with FND_JDBC_BUFFER_DECAY_INTERVAL, allows the buffer decay rate to be tuned.
FND_JDBC_MAX_WAIT_TIME
=========================
The maximum wait time specifies how much time a client should spend trying to get a connection. The borrow algorithm, used to borrow an object from the pool, contains check points at which the elapsed time is compared to the maximum wait time. If it exceeds the maximum wait time, then a null object will be returned to the client. The pre-configured value for the maximum wait time is
10 seconds.
FND_JDBC_SELECTION_POLICY
============================
The selection policy determines how a connection is selected from the list of available connections for a particular client. The connection pool is pre-configured to use a cost-based selection algorithm, which selects the connection that will require the smallest amount of initialization to match the
client's context.
FND_JDBC_USABLE_CHECK
===========================
The FND_JDBC_USABLE_CHECK parameter governs whether a pl/sql query is performed before giving a connection to a client. The pool checks whether a connection is usable before handing it to a client. This always involves checking that the connection is not null and is not closed. If FND_JDBC_USABLE_CHECK is set to true, then it also verifies that the connection can be used to perform a simple PL/SQL query. (This parameter may have to be set to "true" in order to clean up
connections to a database that has been restarted.)
FND_JDBC_CONTEXT_CHECK
==========================
The FND_JDBC_CONTEXT_CHECK parameter governs whether the AOL security context and NLS state is obtained from the database when the connection is returned to the pool. If FND_JDBC_CONTEXT_CHECK is "true", when the connection is returned to the pool, the AOL security context and NLS state will be obtained from the database. (This is implemented in the DBConnObj.isReusable() method). This check must be done when the connection is returned (rather than when it is borrowed) so that the selection matching algorithm has access to the actual
session context of the connections in the available list.
FND_JDBC_PLSQL_RESET
========================
The PL/SQL reset flag, set using the variable FND_JDBC_PLSQL_RESET, governs whether the PL/SQL state associated with a connection should be freed before the pool hands the connection to the client. By default this flag is false.
If the flag is set by true, by including the line "FND_JDBC_PLSQL_RESET=true" in the .dbc file, each connection to the database will have its PL/SQL state cleared before the pool returns the connection to the client.
This is how it works. After the pool selects a connection from the available list for a client, it initializes the connection. One of the things initialization does is to set a flag that is later used by SessionManager to determine if the apps initialization routine needs to be performed for the connection. When FND_JDBC_PLSQL_RESET has been set to "true", this flag will always be set to true. After the pool initializes the connection, it also checks whether the connection is usable. In this case, this check will include a call to DBMS_SESSION.RESET_PACKAGE, which frees the PL/SQL state. The table below summaries the affect of FND_JDBC_PLSQL_RESET and the other safety check parameters on borrowing a connection from the pool.
The FND_JDBC_PLSQL_RESET parameter has been added to only to address the case where production PL/SQL global bugs are known to exist. The performance of the pool is reduced by setting this flag to true.
Reference : Note 264599.1

Opening multiple reports in Crystal Reports for VS causes database connect limit to be reached. Seems to be no way to force Crystal Reports to close database connection (other than exiting application)

I am working on upgrading an application that has been in use for many years. The application is written in VB6 and I have been tasked with upgrading the current application to Crystal Reports for Visual Studio. I am using Crystal Reports for VS Version 13.0.12.1494. The system's database is a Sybase SQL Anywhere 16 database with an ODBC connection using integrated login. Each of the reports has the database connection set up from within the report. There is only once database server, so each of the reports are pointing to the same DB. The database server is currently installed as a "Personal Server" with a limit of 10 connections.
I have implemented the CR viewer as part of a COM-callable wrapper that exposes a COM interface for VB6 to interact with. Inside of my viewer component is a Winform that embeds the Crystal's Report viewer. The COM interface basically maps the basic Crystal apis to methods that the VB6 can call (i.e., Load Report, Set Field Text, Update SQL Query, etc). This architecture is working as designed and the reports are displaying correctly and responding correctly to changes in queries, etc.
The issue is that after I open 9 reports, the tenth one will respond with an error indicating that the database connection limit has been reached. The database connections used by the reports aren't released until after the application is closed. The application is designed for a secure environment that prohibits the non-administrative user from accessing the systems desktop, so asking the user tor restart the application after 10 reports isn't a viable option.
I have checked and database connection pooling is turned off for the SQL Anywhere 16 driver.
I have been digging on this for a few days and have tried adding code in the FormClosed event to close and dispose of the Report Document as follows:
ReportDocument reportDoc= (ReportDocument) crystalReportViewer1.ReportSource;
reportDoc.Close();
reportDoc.Dispose();
GC.Collect();       // Force garbage collection on disposed items
I have also tried the following (as well as maybe 20 or so other permutations) trying to fix the issue with no success.
ReportDocument reportDoc= (ReportDocument) crystalReportViewer1.ReportSource;
foreach (Table table in reportDoc.Database.Tables)
     table.Dispose();
crystalReportViewer1.ReportSource = null;
reportDoc.Database.Dispose();
reportDoc.Close();
reportDoc.Dispose();
reportDoc = (ReportDocument)crystalReportViewer1.ReportSource;
GC.Collect();       // Force garabe collection on disposed items
Any ideas or suggestions would be greatly appreciated. I have been pulling my hair out on this one!

Hi Ludek,
Thanks so much for the quick reply. Unfortunately I did not have time to work on the reporting project Friday afternoon, but did a quick test this morning with some interesting results. I'm hoping if I describe what I'm doing, you can show me the error of my ways. This is really my first major undertaking with Crystal Reports.
If I simply load the report, then close and dispose, I don't hit the limit of 10 files. Note that I do not logon manually in my code as the logon parameters are all defined within the reports themselves. The logon happens when you actually view the report. Loading the report doesn't seem to actually log in to the DB.
What I did was create a very simple form with a single button that creates the WinForm class which contains the Crystal Viewer. It then loads the report, sets the ReportSource property on the CrystalReportsViewer object contained in the WInForm and shows the report. The report does show correctly, until the 10 reports limit is reached.
The relevant code is shown below. More than I wanted to post, but i want to be as complete and unambiguous as possible.
This code displays the same behavior as my earlier post (after 10 reports we are unable to create another connection to the DB).
// Initial Form that simply has a button
public partial class SlectReport : form
        public SelectReport()
            InitializeComponent();
        private void button1_Click(object sender, EventArgs e)
            ReportDocument rd = new ReportDocument();
            ReportForm report = new ReportForm();
            try
                rd.Load(@"Test.rpt");
                report.ReportSource = rd;
                report.Show();
         catch (Exception ex)
              MessageBox.Show(ex.Message);
// The WinForm containing the Crystal Reports Viewer
    public partial class ReportForm : Form
        public ReportForm()
            InitializeComponent();
        private void Form1_Load(object sender, EventArgs e)
            this.crystalReportViewer1.RefreshReport();
            this.FormClosed += new FormClosedEventHandler(ReportForm_FormClosed);
        void ReportForm_FormClosed(object sender, FormClosedEventArgs e)
            ReportDocument rd;
            rd = (ReportDocument)crystalReportViewer1.ReportSource;
            rd.Close();
            rd.Dispose();
        public object ReportSource
            set { crystalReportViewer1.ReportSource = value; }
Again, any guidance would be greatly appreciated.

Database connectivity timeout problem

I am using struts framework for my web application and in between just for a test I have used spring framework database connectivity too in few files. I have deployed my application on tomcat 5.5 server on linux machine. Application is running fine, but sometimes this application shutdown by itself and I have to restart tomcat again (like 3-4 times a month). I wan to run this application continuously. I am getting this error in my log files
1 Error: DAO.SpringInformDAO[ERROR](SpringInformDAO.java:loadTypelessNameIDListProduct:246)org.springframework.dao.DataAccessResourceFailureException: StatementCallback;
2.Caused by: com.mysql.jdbc.CommunicationsException: The last packet successfully received from the server was40524 seconds ago.The last packet sent successfully to the server was 40524 seconds ago, which is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
3. Caused by: java.net.SocketException: Broken pipe
Does someone has any idea how to solve this problem?? It would be great help
Thanks

mantoo wrote:
Thanks for reply. Ok let me explain again, may I was using wrong words. Actually, my web application stops automatically after few hours, I don't know know what is the reason, whether it is tomcat or sql sever. What I concluded from various Google search that it might be because of sql server waiting time and connection ideal time difference does not match. By default SQL server's wait_time is 8 hours, so after that this errors occurs. For dealing this I put following attributes in my resource tag in context.xml.
(testWhileIdle="true" timeBetweenEvictionRunsMillis="10000" minEvictableIdleTimeMillis = "60000" )
After doing this I am not getting those errors which I have written in my previous post, but now it is showing this :
ERROR: transport error 202: handshake failed - received >GET http://www< - excepted >JDWP-Handshake< ["transport.c",L41]
JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or fatal errorListening for transport dt_socket at address: 8000So the real problem is that tomcat is exiting. It isn't crashing, just exiting.
Database problems would not cause that. Excluding the possibility that the driver is calling System.exit() - in which case you would be using a non-standard driver.
Other reasons for application exit.
1. Your code, or some library that you use is calling System.exit().
2. Your JNI code or some library that uses JNI code has a library in C/C++ that is calling the OS application exit in that code.
3. Tomcat probably has some API that allows you to stop it - some place the java code is calling it
4. Some other process outside of tomcat is terminating the application.
Greping can potentially eliminate some of the possibilities above.
As for 4 you can analyze the shutdown time to determine if it shuts down at the same time or after the same amount of time.

Date dimension fragmentation from 2 different database connections

Hi Everyone,
In obiee 10g, is it possible to implement fragmentation on a date dimension from 2 different physical database connections (not schemas)?
For example:
Physical connection & dimension 1: physical1.obiee_rpd.w_mcal_day_d.date
physical connection & dimension 2: physical2.obia_rpd.w_mcal_day_d.date
the fact table will be: physical1.obiee_rpd.w_fact_f.fact
The 2 physical dimension tables will be joined to the 1 fact table in the physical layer.
I then create a BMM with 2 LTS : physical1.obiee_rpd.w_mcal_day_d and physical2.obia_rpd.w_mcal_day_d.
I then create 1 logical column in that BMM which sources both physical1.obiee_rpd.w_mcal_day_d.date and physical2.obia_rpd.w_mcal_day_d.date.
Then, i set up fragmentation to use physical1.obiee_rpd.w_mcal_day_d.date when physical1.obiee_rpd.w_mcal_day_d.date < '04/30/2012' and use physical2.obiee_rpd.w_mcal_day_d.date when physical1.obiee_rpd.w_mcal_day_d.date >= '05/01/2012'.
The problem is that the query that answers generates always uses physical1.obieerpd.w_mcal_day_d.date , regardless of the date filter applied!_
Any tips?
Thanks!

Hy,
Can you try the following.
Define:
- one logical date dimension with two logical table sources (physical1.obiee_rpd.w_mcal_day_d.date and physical2.obia_rpd.w_mcal_day_d.date)
- one logical fact table with two Logical Table Source (LTS). And in each LTS, define the same logical level in the content tab and don't forget to check the checkbox "This source should be combined with other sources at this level".
Cheers
Nico
Edited by: gerardnico on Jun 25, 2012 4:23 PM Date and not datum (Dutch)

Different database connections at runtime

How can I change different database connections at runtime on the same Application Module ?
I use BC4J as business layer and uiXml as presentation layer.

Does anyone know how to do this?
I need the same, but i couldn't find any documentation about it.
Looking forward to hearing good news.....

LabView database connectivity toolkit 1.0.1 compatibility with MS-ACCESS 2010 / Labview report generation toolkit for Office 1.1.3 compatibility with Office 2010

In the very near future we will be forced to upgrade to Office 2010 Company wide and I am a little concerned with some of our older test platforms that have applications built in LabView 8.2.1. These applications save data to MS-ACCESS 2000 databases using the LabView database connectivity toolkit 1.0.1. Office 2003 is also loaded on these test platforms with all test reports generated using the LabView report generation toolkit for Office 1.1.3.
I have not gotten my hands on a copy of Office 2010 yet to see if there will be any compatibility issues. Does anyone have any experience in this area?

The MS-Access part is fairly well isolated through the ADO interface LabVIEW uses. The only possible problems there IMHO are difficulties with possible Acess compatibilities itself such as an example, SQL statement you may have invoked directly through the ADO interface. Maybe you did use a depreciated command back then that has since been removed. As long as the only thing you do are simple INSERT and SELECT statements only, I would expect it to just keep working.
The Report Generation interface is a different beast. Microsoft manages to change the Automation interface with every version of office in a way that strongly binding applications like LabVIEW break on. There is no good way around that except not changing those methods, but that is a cause that has been lost already. You will certainly have to verify the version dependant Report Generation API VIs to still work with Office 2010 and most likely you will have to make some changes to those VIs to make them work again with the modified ActiveX interface of Office 2010. Note, that I have no experience with porting report generation to Office 2010 but I have had some headaches from porting that between Office 97, 2000, 2003, and 2007.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Database connection - API layer?

Similar Messages

Maybe you are looking for