Performanceproblem with WL6.1 JDBC and Oracle

Question

Hi!
I have a big performance-problem using wl6.1, jdbc and oracle.
My Server is sending a Vector with NodeBeans via JDBC to a OracleDB. The answer
comes immediately with the timeout.
Why is the EJB waiting for the timeout?
Is it a problem of configuration?
Thanks
Thomas

Answer 1

Hi Sree,
here I send You the class with the main problem. The call queryDataSet.refresh();
is the timeconsuming part.
We are using WL6.1sp2, Oracle 8.1.7 with classes12. In our environment we can
not use connectionpools.
It comes back with a timeout AND the data. Calling it again immediately it takes
2/3 of the time the timeout is set.
Do You have a fine solution?
Thanks
Thomas
package ppif.db;
import java.rmi.*;
import ppif.bo.*;
import java.util.*;
import com.borland.dx.dataset.*;
import com.borland.dx.sql.dataset.*;
import java.math.*;
public class connector {
     private ppif.mapping.NodeDescriptions nodeDescriptions;
     public connector(ppif.mapping.NodeDescriptions nodeDescriptions) {
          this.nodeDescriptions = nodeDescriptions;
     public connector() {
          this.nodeDescriptions = nodeDescriptions;
     public Vector fetchNodes(ppif.bo.Node filterNode) throws RemoteException {
          String childClassName = null;
          Vector nodeVector = new Vector();
          Node node = null;
          if (nodeDescriptions == null) throw new RemoteException("nodeDescriptions ==
null");
          // childClassName zu gegebenen filterNode ermitteln
          if (filterNode.getClassName().equals("DefaultRoot")) childClassName = "ST";
          if (filterNode.getClassName().equals("PrismaProjectsRoot")) childClassName =
"PrismaProjects";
          if (childClassName == null) throw new RemoteException("Zum übergebenen filterNode
wurde kein chlidClassName gefunden.");
          if (nodeDescriptions.getNodeDescription(childClassName) == null) throw new RemoteException("Für
die ChildClass "+childClassName+" ist kein Mapping definiert.");
          // Vector mit Child-Knoten erzeugen durch DB-Zugriff
          ppif.mapping.NodeDescription nodeDescription = nodeDescriptions.getNodeDescription(childClassName);
Database database = new Database();
ParameterRow parameterRow = null;
Column column = null;
QueryDataSet queryDataSet = new QueryDataSet();
// DB-Connect generieren
database.setConnection(new com.borland.dx.sql.dataset.ConnectionDescriptor(nodeDescription.dbUrl,
nodeDescription.dbUser, nodeDescription.dbPassword, false, "oracle.jdbc.driver.OracleDriver"));
int queryCount = 0;
// Schleife über alle queries der childKlasse, gemäss Mapping
for (Iterator it = nodeDescription.mappingQueries.iterator(); it.hasNext();
               ppif.mapping.MappingQuery mappingQuery = (ppif.mapping.MappingQuery)it.next();
               String queryString = mappingQuery.getQueryString();
               parameterRow = mappingQuery.getParameterRow();
               // ParameterRow mit Input-Werten füllen
               for (int i=0; i<parameterRow.getColumnCount(); i++) {
                    String columnName = parameterRow.getColumn(i).getColumnName();
                    String filterAttributeName = columnName;
                    Object filterAttributeValue = filterNode.getAttribute(filterAttributeName).getVal1();
                    switch (parameterRow.getColumn(i).getDataType()) {
                         case com.borland.dx.dataset.Variant.BIGDECIMAL:
                              BigDecimal val = (BigDecimal)filterAttributeValue;
                              parameterRow.setBigDecimal(i, val);
                              break;
                         case com.borland.dx.dataset.Variant.STRING:
                              parameterRow.setString(i, (String)filterAttributeValue);
                              break;
                         default:
                              throw new RemoteException("Unbekannter Datentyp");
               // Query generieren
               queryDataSet.setQuery(new com.borland.dx.sql.dataset.QueryDescriptor(database,
queryString, parameterRow, false, Load.ALL));
               // DB-Verbindung öffnen
               queryDataSet.open();
               // Rolle setzen
               if (nodeDescription.dbRole != null) {
                    java.sql.Statement setRole;
                    String roleName = nodeDescription.dbRole;
                    String rolePwd = nodeDescription.dbRolePassword;
                    try {
                         java.sql.Connection jdbcConnection = database.getJdbcConnection();
                         setRole = jdbcConnection.createStatement();
                         setRole.execute("SET ROLE " + roleName + " IDENTIFIED BY " + rolePwd);
                    } catch (java.sql.SQLException exception) {
                         throw new RemoteException(exception.getMessage());
                    } catch (Exception exception) {
                         throw new RemoteException(exception.getMessage());
               // Query ausführen
               queryDataSet.refresh();
               // Datensätze in Node-Objekte umwandeln
               int columnCount = queryDataSet.getColumnCount();
               String columnArray[];
               columnArray = queryDataSet.getColumnNames(columnCount);
               for(queryDataSet.first(); queryDataSet.inBounds(); queryDataSet.next()) {
                    Node rNode = nodeDescriptions.createNodeInstance(childClassName);
                    // Abfrageergebnissen in eine Attributliste übertragen
                    for (int i=0; i<columnCount; i++) {
                    nodeVector.add(rNode);
               queryCount++;
          return nodeVector;
     public ppif.mapping.NodeDescriptions getNodeDescriptions() {
          return nodeDescriptions;
     public void setNodeDescriptions(ppif.mapping.NodeDescriptions nodeDescriptions)
          this.nodeDescriptions = nodeDescriptions;
"Sree Bodapati" <[email protected]> wrote:
hi Thomas,
please post more detail on what your code is doing. if possible a code
snippet/error messages/thread dump
sree
"Thomas Eberhard" <[email protected]> wrote in message
news:[email protected]...
Hi!
I have a big performance-problem using wl6.1, jdbc and oracle.
My Server is sending a Vector with NodeBeans via JDBC to a OracleDB.
The
answer
comes immediately with the timeout.
Why is the EJB waiting for the timeout?
Is it a problem of configuration?
Thanks
Thomas