Univers Designer : JZ0C1, IOException closed the connection

Hi !
We get a very strange error when we work in Univers Designer (we're in BO 4.1) when we're working with Derived Table.
For some reason when we edit a Derived table in a universe (connected to a Sybase database), we received an error message "JZ0C1" saying that we get an IOException and it's closed the connection.
We get the error message when we click on "Check Syntax" Button in the edit window of the derived table.

This can mean that the target end has already closed without reading all the data you are trying to send.

Similar Messages

  • Difference between closing the connection before and after committing user transaction?

              I was wondering what's the difference between closing the connection before committing
              the transaction versus closing the connection after committing the transaction?...
              for e.g....
              Scenario 1.........
              UserTransaction useretran;
              usertran.begin();
              Connection con = datasource.getCOnnection();
              // do bunch of stuff...
              conn.close();
              usertran.commit()
              Scenario 2...
              UserTransaction useretran;
              usertran.begin();
              Connection con = datasource.getCOnnection();
              // do bunch of stuff...
              usertran.commit()
              conn.close();
              thanks....
              Srini
              

    Hi. As long as you're sure there's a transaction going on, and the connection
    is a transaction-aware object (from a TxDataSource), either will be fine.
    In the first scenario the actual semantics of the close() call are less than
    normal, because we really don't close the connection or return it to the
    pool until the actual transaction commits, and in the second case, we have
    already taken the connection out of your service as of the commit().
    The second scenario is the usual coding style. If there's ever a chance your
    code will get non-transaction-aware connections, it is crucial to close
    connections, and I always recommend putting the close() in a finally block
    so it's guaranteed to happen.
    Joe
    srinivas wrote:
    I was wondering what's the difference between closing the connection before committing
    the transaction versus closing the connection after committing the transaction?...
    for e.g....
    Scenario 1......... UserTransaction useretran; usertran.begin(); Connection con =
    datasource.getCOnnection(); // do bunch of stuff... conn.close(); usertran.commit()
    Scenario 2... UserTransaction useretran; usertran.begin(); Connection con = datasource.getCOnnection();
    // do bunch of stuff... usertran.commit() conn.close();
    thanks....
    Srini

  • Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

    Hi,
    I am using APEX version 4.2.1.00.08 with Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    I've developed an application, that was working fine till 3 days ago...
    At the moment, I can log into the application but when I enter my ID/PW it takes me to my 1st page but then it runs for a mint or so (trying to load charts) and then generates following error message
    No data received
    Unable to load the webpage because the server sent no data.
    Here are some suggestions:
    Reload this webpage later.
    Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
    interestingly, I haven't changed anything within the application
    I've tried it with Chrome Version 27.0.1453.116 m and IE 8.0...
    with IE 8.0, it shows I/O Error in place of my graphs and get's a pop up message that displays "Error - error unknown"
    The only thing that I can recall doing differently is logging via remote desktop connection, but I've used remote desktop in the past as well and it worked.
    Please advice

    anyone...?

  • Gateway unexpectedly closed the connection..

    When I try to Test Connection for the Active Directory Resources it shows the following error
    The gateway unexpectedly closed the connection with an exception, check the gateway trace for more information. ==> java.net.SocketException: Connection reset by peer: socket write error
    Previously it has working fine for me...

    Kannan SB wrote:
    I Have resolved my issue... I had remove the Gateway service and reinstall the service & restart the machine and try it got success...Still I have face the same issue, only it works for sometime I means while we restart the service it will work after some mins it got failed to perform the service.. Please suggest me for that....
    I have migrated Sun Identity Manager 8.1 Patch 7 to Oracle Waveset 8.1.1 Still the issue persists ...

  • The VI closed the connection : error 1074360302 at property node(arg 1)

    hi!
    I'm trying to running a code which apply the control of my myRIO through a VI on my host computer. A video stream of data is also going to be send from myRIO to the Host Computer VI. However, I am getting the "Host Computer VI" closed the connection. I have no idea why.
    And at the Host Computer keep giving out error 1074360302 occured at Property Node (arg 1) in myRIO vi.
    I would be glad if someone could help me.
    Thank you.
    Attachments:
    Picture1.png ‏81 KB

    Hi e_pah,
    Thanks for your response, what sort of camera are you using? This error has been previously seen with a Stingray camera when the IMAQ drivers aren't quite up to date.
    So firstly, we need to make sure the IMAQ drivers are updated.
    Further questions regarding your application:
    Did this VI ever run?
    Does this error occur everytime the VI is run?
    What is the the property node doing?
    Many thanks
    Ingram

  • The remote device closed the connection!!! HELP

    Hi,
    Brought the Ms-6967 Bluetooth USB adapter so I could connect it to my nokia 7650. But have had big problems which failed in me getting anything out of the product.
    For starters every time I reboot my pc, I have to re-install the driver for the Bluetooth dongle? because my operating system (XP) finds this hardware every time I reboot and doesn't seem to remember the last time I install it.
    Plus when I use the software it actually communicates with my Nokia 7650 as in sending a message asking for permission to link pc to phone and when I answer yes on my nokia it replies with " The Bluetooth serial port connection failed: The remote device closed the connection?
    I've wasted so many hours now on this and had no luck. So if anyone has the smallest piece of help to give I would be well happy,
    Cheers,
    DRGonzo247

    Having seen similar symptoms recently you might want to check that you haven't had a browser hijacker installed - check your proxy settings to see if the browser is trying to use a proxy server, or, if you usually use a proxy, check to make sure it hasn't
    been changed. (In IE go to Tools->Internet Options->Connections->Lan Settings.)
    Good luck!

  • RDP to VDI 3 fails with 'Administrative Task closed the connection'

    The RDP to the VDI 3 login page described in the page below would be a really useful feature for us. Unfortunately when I connect using MSTSC (Windows XP SP 3) the screen goes black, then a message pops up with 'The connection was closed by an administrative task' (or words to that effect).
    Any idea on how to resolve this issue?
    http://wikis.sun.com/display/VDI3/Accessing+Desktops+with+Microsoft+RDC
    Thank you in advance for any replies,
    Dono

    Finally worked this one out.
    Turns out I had two pools assigned but it still eludes me how to set one to the default...
    Anyway, what was required was to clear the 'Prompt for credentials' and use the <username>::pool= etc etc to connect to the pool.
    Doesn't render as quickly as using the Sun Ray DTU but it's good enough.
    Many thanks,
    Donovan

  • Closing the Connection object

    I was looking at one of the database examples in a Java book I recently purchased. In their example they establish the connection in the class with the main. ( is this referred to as the Moment Interval? ) Anyway, they pass the private Connection connection object to another class called AddRecord which implements an ActionListener. In this class, the AddRecord Constructor changes the name to con which is also declared as private in this class. What they don't show is how to close the connection object now that it has a new name. How do I close the connection object.
    The example is using an Access mdb and when the appication is closed, the Access.ldb file is still there.
    Is there a better solution?
    Thanks everyone,
    Leo D.

    I'm sorry. I meant to say "Where" do I close the connection? If I close the connection in the AddRecord Class, then I won't be able to add another record. And I can't close the connection in the moment interval because I've declared the connection object in class AddRecord as Private. Should I give the connection object package access?
    Thanks,
    Leo D.

  • Segfault in OCIHandleFree for a statement after closing the connection

    my app has lots of statements allocated at any one time.
    if the oracle connection is lost (due to temporary network problems, etc), my app detects the connection loss. when the connection is lost, the app destroys the old connection, and then tries to create a new connection. once it gets a new connection, the app goes through and destroys its old statements.
    but, sometimes a segfault occurs in the call to OCIHandleFree.
    when the old connection is destroyed, does it also free up all memory allocated for the statement too? so I'm basically doing a double free when I try to call OCIHandleFree on the statements?
    btw, by 'destroy old connection': the app is using the oralib wrapper around the oci library. when an oralib instance is destroyed, it first switches the server handle to OCI_ATTR_NONBLOCKING_MODE, then calls OCISessionEnd, OCIServerDetach, then OCIHandleFree for each of the svc_context, session, error, and server handles.
    after that, a new oralib instance is created, which makes a new connection to oracle.
    then after that, the old statements will all be passed to OCIHandleFree.
    is there any obvious problem with that? thanks!

    It is very important to close them as you might have a resource leak. Many people think that since Java is garbage collected, they don't have to worry about memory. While this is true, it should not be take to the extreme.
    public void method throws SQLException
         Connection conn = DriverManager.getConnection();
         Statement stmnt  = conn.createStatement();
         ResultSet results = stmnt.executeQuery("SELECT * FROM table;");
         results.close();
         stmnt.close();
         conn.close();
    }The above code looks correct, but in fact it is not completely correct. It is not completely correct, because the release of resources is not ensured. If an exception occurs midway, it's possible that the resources will not be properly released.
    Here is the correct code.
    public void method throws SQLException
         Connection conn = null;
         Statement stmnt = null;
         ResultSet results = null;
         try
              conn = DriverManager.getConnection();
              stmnt = conn.createStatement();
              results = stmnt.executeQuery("SELECT * FROM table;");
         finally
              if ( results ! = null )
                   results.close();
              if ( stmnt != null )
                   stmnt.close();
              if ( conn != null )
                   conn.close();
    }The finally block ensures that even if an exception occurs we will release our resources. You have to make sure they're not null to avoid NullPointerExceptions.

  • Closing the Connection

    hi
    what is the best way to close the conenction of JDBC, is it to use con.close() directly or use finalize() method..
    thanks

    the best way is to close the db connection in the finally block:
    try{
    Connection connection ...
    }catch(Exception e){
       e.printStacktrace();
    }finally{
      try{
        if(connection!=null)
                connection.close();
      }catch(Exception ee){
          ee.printStacktrace();
    }

  • Open cursors are NOT closed only by closing the ResultSet or Statement

    I've realised that the open cursors are only closed by closing the connection.
    In my example code I have for-loop with a vector of table-names. For every table-name I start a query to retrieve metainformation (row-size, column-names). Although I close the ResultSet (which automatically closes the PreparedStatement/Statement) I reached after the 150th loop a max-cursor-exception (ora-01000) ?!
    It seems that there is only the workaround to close and re-open the connection at the end of the for-loop. Which is performance-side pretty bad :-(.
    Is there really no other solution?
    Besides: does anyone know WHY the statement.close() also closes the ResultSet?? I think this is a bad design (hence to tight dependency between both classes). What if the garbage collector closes the statement (and hence to the JDOC the statement.close()-method also closes the ResultSet)? For example if a method uses a local Statement and returns a ResultSet (and the Statement-garbage is collected), then the ResultSet would cause an exception?!
    Thanks for the help in advance
    Tai

    I've realised that the open cursors are only closed by
    closing the connection.Or by closing the Statement!
    In my example code I have for-loop with a vector of
    table-names. For every table-name I start a query to
    retrieve metainformation (row-size, column-names).
    Although I close the ResultSet (which automatically
    closes the PreparedStatement/Statement) I reached
    after the 150th loop a max-cursor-exception
    (ora-01000) ?!Closing the ResutSet does not automatically close the PreparedStatement/Statement.
    >
    It seems that there is only the workaround to close
    and re-open the connection at the end of the for-loop.
    Which is performance-side pretty bad :-(.
    Is there really no other solution?
    Just explicitly close the PreparedStatement/Statement!
    Besides: does anyone know WHY the statement.close()
    also closes the ResultSet?? You need to think of a resultset as a live connection to the database.
    Consider SELECT * FROM ABIGTABLE, it would be inefficient to populate the Resultset with all of the rows (could even eat up all memory) so the first n rows are returned ( n = Statement.getFetchSize() ) and the next n rows are returned as needed.
    I think this is a bad
    design (hence to tight dependency between both
    classes). What if the garbage collector closes the
    statement (and hence to the JDOC the
    statement.close()-method also closes the ResultSet)?
    For example if a method uses a local Statement and
    returns a ResultSet (and the Statement-garbage is
    collected), then the ResultSet would cause an
    exception?!You should use a statment and resultset, read all your data into a collection or a CachedRowSet (http://www.javaworld.com/javaworld/jw-02-2001/jw-0202-cachedrow.html) then close the statment as soon as possible. Never return a resultset form your data tier: that is tight coupling between the tiers of your application!

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

    I'm trying to set up connection pooling. I'm following the how-to page at
    http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html
    But when i test the DBTest/test.jsp file, tomcat displays an error =
    could not load jdbc driver class 'null'(msdos)
    i have placed all the required .jar files in the tomcat lib.
    below is the cofiguration i did to the server.xml file
    <!-- Example Server Configuration File -->
    <!-- Note that component elements are nested corresponding to their
    parent-child relationships with each other -->
    <!-- A "Server" is a singleton element that represents the entire JVM,
    which may contain one or more "Service" instances. The Server
    listens for a shutdown command on the indicated port.
    Note: A "Server" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <Server port="8005" shutdown="SHUTDOWN" debug="0">
    <!-- Uncomment these entries to enable JMX MBeans support -->
    <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
    debug="0"/>
    <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
    debug="0"/>
    <!-- Global JNDI resources -->
    <GlobalNamingResources>
    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>
    <!-- Editable user database that can also be used by
    UserDatabaseRealm to authenticate users -->
    <Resource name="UserDatabase" auth="Container"
    type="org.apache.catalina.UserDatabase"
    description="User database that can be updated and saved">
    </Resource>
    <ResourceParams name="UserDatabase">
    <parameter>
    <name>factory</name>
    <value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
    </parameter>
    <parameter>
    <name>pathname</name>
    <value>conf/tomcat-users.xml</value>
    </parameter>
    </ResourceParams>
    </GlobalNamingResources>
    <!-- A "Service" is a collection of one or more "Connectors" that share
    a single "Container" (and therefore the web applications visible
    within that Container). Normally, that Container is an "Engine",
    but this is not required.
    Note: A "Service" is not itself a "Container", so you may not
    define subcomponents such as "Valves" or "Loggers" at this level.
    -->
    <!-- Define the Tomcat Stand-Alone Service -->
    <Service name="Tomcat-Standalone">
    <!-- A "Connector" represents an endpoint by which requests are received
    and responses are returned. Each Connector passes requests on to the
    associated "Container" (normally an Engine) for processing.
    By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
    You can also enable an SSL HTTP/1.1 Connector on port 8443 by
    following the instructions below and uncommenting the second Connector
    entry. SSL support requires the following steps (see the SSL Config
    HOWTO in the Tomcat 4.0 documentation bundle for more detailed
    instructions):
    * Download and install JSSE 1.0.2 or later, and put the JAR files
    into "$JAVA_HOME/jre/lib/ext".
    * Execute:
    %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
    $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
    with a password value of "changeit" for both the certificate and
    the keystore itself.
    By default, DNS lookups are enabled when a web application calls
    request.getRemoteHost(). This can have an adverse impact on
    performance, so you can disable it by setting the
    "enableLookups" attribute to "false". When DNS lookups are disabled,
    request.getRemoteHost() will return the String version of the
    IP address of the remote client.
    -->
    <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -->
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8080" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="100" debug="0" connectionTimeout="20000"
    useURIValidationHack="false" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
    to -1 -->
    <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
    <!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8443" minProcessors="5" maxProcessors="75"
    enableLookups="true"
         acceptCount="100" debug="0" scheme="https" secure="true"
    useURIValidationHack="false" disableUploadTimeout="true">
    <Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
    clientAuth="false" protocol="TLS" />
    </Connector>
    -->
    <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -->
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8009" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0" connectionTimeout="20000"
    useURIValidationHack="false"
    protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <!--
    <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
    port="8009" minProcessors="5" maxProcessors="75"
    acceptCount="10" debug="0"/>
    -->
    <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
    port="8082" minProcessors="5" maxProcessors="75"
    enableLookups="true" disableUploadTimeout="true"
    acceptCount="100" debug="0" connectionTimeout="20000"
    proxyPort="80" useURIValidationHack="false" />
    -->
    <!-- Define a non-SSL legacy HTTP/1.1 Test Connector on port 8083 -->
    <!--
    <Connector className="org.apache.catalina.connector.http.HttpConnector"
    port="8083" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0" />
    -->
    <!-- Define a non-SSL HTTP/1.0 Test Connector on port 8084 -->
    <!--
    <Connector className="org.apache.catalina.connector.http10.HttpConnector"
    port="8084" minProcessors="5" maxProcessors="75"
    enableLookups="true" redirectPort="8443"
    acceptCount="10" debug="0" />
    -->
    <!-- An Engine represents the entry point (within Catalina) that processes
    every request. The Engine implementation for Tomcat stand alone
    analyzes the HTTP headers included with the request, and passes them
    on to the appropriate Host (virtual host). -->
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Standalone" defaultHost="localhost" debug="0">
    <!-- The request dumper valve dumps useful debugging information about
    the request headers and cookies that were received, and the response
    headers and cookies that were sent, for all requests received by
    this instance of Tomcat. If you care only about requests to a
    particular virtual host, or a particular application, nest this
    element inside the corresponding <Host> or <Context> entry instead.
    For a similar mechanism that is portable to all Servlet 2.3
    containers, check out the "RequestDumperFilter" Filter in the
    example application (the source for this filter may be found in
    "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
    Request dumping is disabled by default. Uncomment the following
    element to enable it. -->
    <!--
    <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
    -->
    <!-- Global logger unless overridden at lower levels -->
    <Logger className="org.apache.catalina.logger.FileLogger"
    prefix="catalina_log." suffix=".txt"
    timestamp="true"/>
    <!-- Because this Realm is here, an instance will be shared globally -->
    <!-- This Realm uses the UserDatabase configured in the global JNDI
    resources under the key "UserDatabase". Any edits
    that are performed against this UserDatabase are immediately
    available for use by the Realm. -->
    <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
    debug="0" resourceName="UserDatabase"/>
    <!-- Comment out the old realm but leave here for now in case we
    need to go back quickly -->
    <!--
    <Realm className="org.apache.catalina.realm.MemoryRealm" />
    -->
    <!-- Replace the above Realm with one of the following to get a Realm
    stored in a database and accessed via JDBC -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
    driverName="org.gjt.mm.mysql.Driver"
    connectionURL="jdbc:mysql://localhost/authority"
    connectionName="test" connectionPassword="test"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
    driverName="oracle.jdbc.driver.OracleDriver"
    connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
    connectionName="scott" connectionPassword="tiger"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!--
    <Realm className="org.apache.catalina.realm.JDBCRealm" debug="99"
    driverName="sun.jdbc.odbc.JdbcOdbcDriver"
    connectionURL="jdbc:odbc:CATALINA"
    userTable="users" userNameCol="user_name" userCredCol="user_pass"
    userRoleTable="user_roles" roleNameCol="role_name" />
    -->
    <!-- Define the default virtual host -->
    <Host name="localhost" debug="0" appBase="webapps"
    unpackWARs="true" autoDeploy="true">
    <Context path="/my-jsp" docBase="c:\JSP-Files" debug="0"
    privileged="true" reloadable="true" />
         <Context path="" docBase="c:\Inetpub\wwwroot" debug="0" privileged="true" />
    <Context path="/sharon" docBase="C:\Tomcat 4.1\webapps\sharon" debug="0" privileged="true" />
    <!-- Normally, users must authenticate themselves to each web app
    individually. Uncomment the following entry if you would like
    a user to be authenticated the first time they encounter a
    resource protected by a security constraint, and then have that
    user identity maintained across all web applications contained
    in this virtual host. -->
    <!--
    <Valve className="org.apache.catalina.authenticator.SingleSignOn"
    debug="0"/>
    -->
    <!-- Access log processes all requests for this virtual host. By
    default, log files are created in the "logs" directory relative to
    $CATALINA_HOME. If you wish, you can specify a different
    directory with the "directory" attribute. Specify either a relative
    (to $CATALINA_HOME) or absolute path to the desired directory.
    -->
    <!--
    <Valve className="org.apache.catalina.valves.AccessLogValve"
    directory="logs" prefix="localhost_access_log." suffix=".txt"
    pattern="common" resolveHosts="false"/>
    -->
    <!-- Logger shared by all Contexts related to this virtual host. By
    default (when using FileLogger), log files are created in the "logs"
    directory relative to $CATALINA_HOME. If you wish, you can specify
    a different directory with the "directory" attribute. Specify either a
    relative (to $CATALINA_HOME) or absolute path to the desired
    directory.-->
    <Logger className="org.apache.catalina.logger.FileLogger"
    directory="logs" prefix="localhost_log." suffix=".txt"
         timestamp="true"/>
    <!-- Define properties for each web application. This is only needed
    if you want to set non-default properties, or have web application
    document roots in places other than the virtual host's appBase
    directory. -->
    <!-- Tomcat Root Context -->
    <!--
    <Context path="" docBase="ROOT" debug="0"/>
    -->
    <!-- Tomcat Examples Context -->
    <Context path="/examples" docBase="examples" debug="0"
    reloadable="true" crossContext="true">
    <Logger className="org.apache.catalina.logger.FileLogger"
    prefix="localhost_DBTest_log." suffix=".txt"
    timestamp="true"/>
    <Ejb name="ejb/EmplRecord" type="Entity"
    home="com.wombat.empl.EmployeeRecordHome"
    remote="com.wombat.empl.EmployeeRecord"/>
    <!-- If you wanted the examples app to be able to edit the
    user database, you would uncomment the following entry.
    Of course, you would want to enable security on the
    application as well, so this is not done by default!
    The database object could be accessed like this:
    Context initCtx = new InitialContext();
    Context envCtx = (Context) initCtx.lookup("java:comp/env");
    UserDatabase database =
    (UserDatabase) envCtx.lookup("userDatabase");
    -->
    <!--
    <ResourceLink name="userDatabase" global="UserDatabase"
    type="org.apache.catalina.UserDatabase"/>
    -->
    <!-- PersistentManager: Uncomment the section below to test Persistent
              Sessions.
    saveOnRestart: If true, all active sessions will be saved
    to the Store when Catalina is shutdown, regardless of
    other settings. All Sessions found in the Store will be
    loaded on startup. Sessions past their expiration are
    ignored in both cases.
    maxActiveSessions: If 0 or greater, having too many active
    sessions will result in some being swapped out. minIdleSwap
    limits this. -1 means unlimited sessions are allowed.
    0 means sessions will almost always be swapped out after
    use - this will be noticeably slow for your users.
    minIdleSwap: Sessions must be idle for at least this long
    (in seconds) before they will be swapped out due to
    maxActiveSessions. This avoids thrashing when the site is
    highly active. -1 or 0 means there is no minimum - sessions
    can be swapped out at any time.
    maxIdleSwap: Sessions will be swapped out if idle for this
    long (in seconds). If minIdleSwap is higher, then it will
    override this. This isn't exact: it is checked periodically.
    -1 means sessions won't be swapped out for this reason,
    although they may be swapped out for maxActiveSessions.
    If set to >= 0, guarantees that all sessions found in the
    Store will be loaded on startup.
    maxIdleBackup: Sessions will be backed up (saved to the Store,
    but left in active memory) if idle for this long (in seconds),
    and all sessions found in the Store will be loaded on startup.
    If set to -1 sessions will not be backed up, 0 means they
    should be backed up shortly after being used.
    To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
    and minIdleBackup all to -1, saveOnRestart to false, then restart
    Catalina.
    -->
              <!--
    <Manager className="org.apache.catalina.session.PersistentManager"
    debug="0"
    saveOnRestart="true"
    maxActiveSessions="-1"
    minIdleSwap="-1"
    maxIdleSwap="-1"
    maxIdleBackup="-1">
    <Store className="org.apache.catalina.session.FileStore"/>
    </Manager>
              -->
    <Environment name="maxExemptions" type="java.lang.Integer"
    value="15"/>
    <Parameter name="context.param.name" value="context.param.value"
    override="false"/>
    <Resource name="jdbc/EmployeeAppDb" auth="SERVLET"
    type="javax.sql.DataSource"/>
    <Resource name="jdbc/TestDB"
         auth="Container"
         type="javax.sql.DataSource"/>
    <ResourceParams name="jdbc/TestDB">
    <parameter>
         <name>factory</name>
         <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
         </parameter>
         <!-- Maximum number of dB connections in pool. Make sure you
         configure your mysqld max_connections large enough to handle
         all of your db connections. Set to 0 for no limit.
         -->
         <parameter>
         <name>maxActive</name>
         <value>100</value>
         </parameter>
         <!-- Maximum number of idle dB connections to retain in pool.
         Set to 0 for no limit.
         -->
         <parameter>
         <name>maxIdle</name>
         <value>30</value>
         </parameter>
         <!-- Maximum time to wait for a dB connection to become available
         in ms, in this example 10 seconds. An Exception is thrown if
         this timeout is exceeded. Set to -1 to wait indefinitely.
         -->
         <parameter>
         <name>maxWait</name>
         <value>10000</value>
         </parameter>
    <!-- MySQL dB username and password for dB connections -->
    <parameter>
    <name>user</name>
    <value>javauser</value>
    </parameter>
    <parameter>
    <name>password</name>
    <value>javadude</value>
    </parameter>
    <!-- Class name for mm.mysql JDBC driver -->
    <parameter>
    <name>driverClassName</name>
    <value>org.gjt.mm.mysql.Driver</value>
    </parameter>
    <!-- The JDBC connection url for connecting to your MySQL dB.
         The autoReconnect=true argument to the url makes sure that the
         mm.mysql JDBC Driver will automatically reconnect if mysqld closed the
         connection. mysqld by default closes idle connections after 8 hours.
         -->
         <parameter>
         <name>url</name>
         <value>jdbc:mysql://localhost:3306/javatest?autoReconnect=true</value>
    </parameter>
    </ResourceParams>
    <Resource name="mail/Session" auth="Container"
    type="javax.mail.Session"/>
    <ResourceParams name="mail/Session">
    <parameter>
    <name>mail.smtp.host</name>
    <value>localhost</value>
    </parameter>
    </ResourceParams>
    <ResourceLink name="linkToGlobalResource"
    global="simpleValue"
    type="java.lang.Integer"/>
    </Context>
    </Host>
    </Engine>
    </Service>
    <!-- The MOD_WEBAPP connector is used to connect Apache 1.3 with Tomcat 4.0
    as its servlet container. Please read the README.txt file coming with
    the WebApp Module distribution on how to build it.
    (Or check out the "jakarta-tomcat-connectors/webapp" CVS repository)
    To configure the Apache side, you must ensure that you have the
    "ServerName" and "Port" directives defined in "httpd.conf". Then,
    lines like these to the bottom of your "httpd.conf" file:
    LoadModule webapp_module libexec/mod_webapp.so
    WebAppConnection warpConnection warp localhost:8008
    WebAppDeploy examples warpConnection /examples/
    The next time you restart Apache (after restarting Tomcat, if needed)
    the connection will be established, and all applications you make
    visible via "WebAppDeploy" directives can be accessed through Apache.
    -->
    <!-- Define an Apache-Connector Service -->
    <!--
    <Service name="Tomcat-Apache">
    <Connector className="org.apache.catalina.connector.warp.WarpConnector"
    port="8008" minProcessors="5" maxProcessors="75"
    enableLookups="true" appBase="webapps"
    acceptCount="10" debug="0"/>
    <Engine className="org.apache.catalina.connector.warp.WarpEngine"
    name="Apache" debug="0">
    <Logger className="org.apache.catalina.logger.FileLogger"
    prefix="apache_log." suffix=".txt"
    timestamp="true"/>
    <Realm className="org.apache.catalina.realm.MemoryRealm" />
    </Engine>
    </Service>
    -->
    </Server>
    Pleas4 help!!!

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

  • Reuse of preparedstatements and the connection pool

    It seems useful (for performance reasons) to reuse a prepared statement in
    subsequent calls to the database. In WebLogic, however, after each call we
    return the Connection object to the WebLogic connection pool. A prepared
    statement is created on a specific Connection object. The next time we want
    to use the same query we get a Connection from the pool, which might be
    another instance of the Connection class. Therefor it seems impossible or at
    least dangerous to reuse the same prepared statement. Even in the case this
    would work we're indirectly using the other Connection, which we already
    returned to the pool and which could be retrieved from the pool by someone
    else. So, can't we reuse preparedstatements ?

    Hi Raja,
    Currently the only bullet-proof way to make sure that all statements are
    cached is to set the cache size to a number of possible prepared statements
    in the application.
    The only consequence of increased cache size is growing amount of
    memory required by a server instance.
    Regards,
    Slava Imeshev
    "Rajiv Jauhari" <[email protected]> wrote in message
    news:[email protected]...
    Is there an easy way to tell whether the prepared statement cache size one
    has set is
    appropriate? Some way to monitor cache hit rate or usage count (i.e., the
    actual number of statements cached) while running a load test? I'm using
    Weblogic 6.1sp3 and Oracle 8.1.7.4.
    Another way to think of this question is: is there a negative impact ifthe
    cache size is set too large?
    In the case of Oracle I believe one might run out of cursors, but is there
    any other negative consequence that you know of?
    Thanks,
    Rajiv
    "Joseph Weinstein" <[email protected]> wrote in message
    news:[email protected]...
    Vyas wrote:
    If multiples (of the same statement) can be cached would it not result
    in too many
    prepared statements of the same type in the cache ?
    This could happen
    1. When a load test is done when all the threads start doing exactly
    the
    same work.
    Because of contention everybody gets their own statement copy(theoritically, even
    if in practice it may not exactly happen like that). In such a case
    you
    are going
    to create load on the database in terms of open cursors.Each thread will get it's own connection, and the statement cache isper-connection.
    Cursors, in Oracle's case, do need to be configured to support acache-full of
    retained statements. Alternately, the cache should be set to a smallenough size to
    require only as many cursors as the DBMS will allow per connection.
    Another issue is what happens when the cache limit is hit ?
    In the above example let's say cache limit is 50 and I am doing 50
    user
    load test.
    because of load test let's say the cache gets filled with 50 of the
    same
    statement.
    When load test moves to the next sequence of action requiring a
    diffrent
    statement
    what happens to the cache ?
    thanks
    VyasThe only way a given connection's statement cache will get a duplicatestatement
    is if some single JDBC thread required multiple copies of the samestatement. A
    multi-user test will usually just ensure that each pooled connectioncaches the
    same selection of different statements that the test user used. If thetest user
    just repeatedly makes and uses one statement, the first time they do it,the
    statement will be cached, and every subsequent repeat of the user codewill get
    the same cached statement. The cache will still have 49 empty slotswaiting for
    different statements. Currently the cache is simple-minded. It is a
    fixed
    (configurable)
    size per connection, and the first N prepared/callable statements getcached for the
    life of the pooled connection that created them. All other subsequentstatements will
    be made and closed on a per-connection-use basis. Therefore, it can bethat a startup
    or stress load that runs before standard runtime service, and which usessignificantly
    different a statement profile could populate the cache with rarely-usedwasted statements.
    If I were a customer in this circumstance, I would either prime thecaches, by determining
    which statements I wanted cached, and then running a startup class thatreserved all the
    pool connections, and made these statements on each before closing them.Alternately,
    after startup/stress I would reset the pool, and allow the runtime load
    to
    fill the cache of
    the regenerated pool.
    Joe Weinstein at B.E.A.
    thanks
    Vyas
    Joseph Weinstein <[email protected]> wrote:
    JS wrote:
    It seems useful (for performance reasons) to reuse a prepared
    statement
    in
    subsequent calls to the database. In WebLogic, however, after each
    call
    we
    return the Connection object to the WebLogic connection pool. A
    prepared
    statement is created on a specific Connection object. The next timewe
    want
    to use the same query we get a Connection from the pool, which
    might
    be
    another instance of the Connection class. Therefor it seemsimpossible
    or at
    least dangerous to reuse the same prepared statement. Even in the
    case
    this
    would work we're indirectly using the other Connection, which we
    already
    returned to the pool and which could be retrieved from the pool bysomeone
    else. So, can't we reuse preparedstatements ?We already have you covered! Weblogic caches PreparedStatements along
    with the pooled connection they came from. Every time you obtain a
    pool
    connection and run a prepareStatement() or prepareCall(), we willtransparently
    give you a previously made statement, if the SQL exactly matches, andno
    other place in the current thread stack is using that statement(multiples
    can
    be cached)
    You are correct, of course, that statements you have should only
    be
    useable
    to you while you have the connection from which they came. We have
    you
    covered
    there too. If you were to try to use any prepared statement that
    you'd
    gotten
    from
    a pool connection after you'd put the connection back into the pool,those
    statements
    would throw an exception saying that they had been made inoperable atthe
    time
    you'd closed the connection.
    Joe Weinstein at B.E.A.

  • Significnce of making the Connection object explicitly as null

    Iam using java.sql.Connection object to make connection to DB400 database and in the finally block closing the connection as con.close();
    90% of the time query is executing fine and getting correct results. But some times the updated values in the data base are not getting reflected in the result set. ie: ResultSet object is not refreshing properly(not always but sometimes). After making the code in the finally block as follows I feel it is working fine
    if(con != null)
    con.close();
    con=null;
    Can some one explain the significance of making an object explicitly to null.

    I am facing the same issue again. The resultSet and the stament are getting closed properly but the query is not fetching the updated results. If i execute the same query using a client(WinSQL), then the updated values are reflected. Also if i change any of the where conditions in the query(adding one more 'and' condition or 'or' condition ), then the query is giving correct results. Is there any resultSet caching occurs in websphere

  • Chrome error :Error 324 (net::ERR_EMPTY_RESPONSE) : The server closed the

    hi,
    I have installed Oracle Database Express Edition 11g Release 2.2.0 on Windows 7 Home Premium x64.
    when i click the get started with oracle database 11g Xe destop icon ..i am getting error in chrome
    No data received
    Unable to load the webpage because the server sent no data.
    Here are some suggestions:
    Reload this webpage later.
    Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.
    please help with this error..

    IE error..
    Internet Explorer cannot display the webpage
    This problem can be caused by a variety of issues, including:
    •Internet connectivity has been lost.
    •The website is temporarily unavailable.
    •The Domain Name Server (DNS) is not reachable.
    •The Domain Name Server (DNS) does not have a listing for the website's domain.
    •There might be a typing error in the address.
    •If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.

Maybe you are looking for