Oracle  9.2.0.3 thin with wls 8.1

Hi Folks,
A quick question: we are using wls 8.1 sp2 with oracle 9.2.0.3.
I know that 9.2.0.3 has some problems (leaks for example)and I see that wls 8.1
sp3 will be coming out with 10g driver.
When will SP3 be GA?
can I use 10g driver with oracle 9.2 server?
I will be more then happy to hear any suggestions
or experience with 10g driver and oracle 9.2 server.
Thanks
Yshemi

Hi phcullen,
You are quite right about it; to be honest I didn't apply post-install steps for the
patch. However, I did this installation before on Solaris 8 following the installation
guide from the main application which also includes Oracle installation and didn't
have any issues as such.
It might well be the case that in Solaris 10, I need to run these. Would you recommend me to read through the whole patch document or is there a standard/straight-forward procedure for this ?
Cheers,
ulvi

Similar Messages

  • Exception with WLS 6.1.3 & Oracle 9.2 thin driver

    I'm testing out an upgrade from the Oracle thin driver that ships with WLS
    6.1
    to the Oracle 9.2 thin driver. My database server is running Oracle 8.1.7.
    The only configuration change I made was to put the 9.2 classes12.zip at the
    beginning of ths classpath. The line of my code where the exception is
    being
    throw is the first attempt at performing a resultSet.getLong() call. Has
    anyone
    gotten this combination to work yet? Any ideas on the error? I'd really
    like to test out the native LOB support in the new drivers.
    TIA - Gordon
    <Oct 14, 2002 2:59:02 PM EDT> <Error> <Audit> <- Login failed because
    loginName:
    buyerOrgAdmin1034621942027 was not found.
    com.eoriginal.engine.core.session.bas
    icAccess.OrgUserDataAccessSessionBean_rngrwj_Impl::findUserAccountInfo,
    java.lan
    g.ArrayIndexOutOfBoundsException
    at oracle.sql.NUMBER._fromLnxFmt(NUMBER.java:3181)
    at oracle.sql.LnxLibThin.lnxsni(LnxLibThin.java:6571)
    at oracle.sql.NUMBER.toLong(NUMBER.java:373)
    at
    oracle.jdbc.dbaccess.DBConversion.NumberBytesToLong(DBConversion.java
    :2915)
    at
    oracle.jdbc.driver.OracleStatement.getLongValue(OracleStatement.java:
    4373)
    at
    oracle.jdbc.driver.OracleResultSetImpl.getLong(OracleResultSetImpl.ja
    va:529)
    at
    oracle.jdbc.driver.OracleResultSet.getLong(OracleResultSet.java:1540)
    at weblogic.jdbc.jts.ResultSet.getLong(ResultSet.java:518)
    at
    weblogic.jdbc.rmi.internal.ResultSetImpl.getLong(ResultSetImpl.java:4
    77)
    at
    weblogic.jdbc.rmi.internal.ResultSetStraightReader.getLong(ResultSetS
    traightReader.java:142)
    at
    weblogic.jdbc.rmi.SerialResultSet.getLong(SerialResultSet.java:450)
    at
    com.eoriginal.engine.core.session.basicAccess.OrgUserDataAccessSessio
    nBean.findUserAccountInfo(OrgUserDataAccessSessionBean.java:1272)
    at
    com.eoriginal.engine.core.session.basicAccess.OrgUserDataAccessSessio
    nBean_rngrwj_EOImpl.findUserAccountInfo(OrgUserDataAccessSessionBean_rngrwj_
    EOIm
    pl.java:475)
    at
    com.eoriginal.engine.core.session.basicAccess.LoginSessionBean.valida
    teLogin(LoginSessionBean.java:135)
    at
    com.eoriginal.engine.core.session.basicAccess.LoginSessionBean.valida
    teLogin(LoginSessionBean.java:94)
    at
    com.eoriginal.engine.core.session.basicAccess.LoginSessionBean_moz7fh
    EOImpl.validateLogin(LoginSessionBeanmoz7fh_EOImpl.java:37)
    at
    com.eoriginal.engine.core.session.basicAccess.LoginSessionBean_moz7fh
    EOImplWLSkel.invoke(Unknown Source)
    at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:274)
    at
    weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
    .java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    (com.eoriginal.engine.core.session.basicAccess.LoginSessionBean_moz7fh_Impl:
    :va
    lidateLogin)>

    Have you tried the thick (oci) driver?
    We're looking to upgrade too.
    "Richard" <[email protected]> wrote:
    >
    I try to connect to an Oracle 9.2.0 on Windows XP with the jdbc thin
    driver. I
    use weblogic server 7.0 SP1 (same problem with weblogic server 7.0.0).
    I try direct connection (without pool) or with the weblogic pool, and
    I get the
    same error :
    java.lang.ArrayIndexOutOfBoundsException
    at oracle.security.o3logon.C0.r(C0)
    at oracle.security.o3logon.C0.l(C0)
    at oracle.security.o3logon.C1.c(C1)
    at oracle.security.o3logon.O3LoginClientHelper.getEPasswd(O3LoginClientH
    elper)
    at oracle.jdbc.ttc7.O3log.<init>(O3log.java:289)
    at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:251)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:246)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
    va:365)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Con
    nectionEnvFactory.java:201)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Con
    nectionEnvFactory.java:140)
    at weblogic.jdbc.common.internal.ResourceAllocator.makeResources(Resourc
    eAllocator.java:931)
    at weblogic.jdbc.common.internal.ResourceAllocator.finishInit(ResourceAl
    locator.java:457)
    at weblogic.jdbc.common.internal.ResourceAllocator.<init>(ResourceAlloca
    tor.java:316)
    at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.j
    ava:292)
    at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.
    java:282)
    at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.j
    ava:270)
    The same test works well with an Oracle 9.0 !
    I have already try with this differents drivers :
    8.1.7, 9.0 and 9.2 and I always have the same problem.

  • Error configuring the Oracle 8.1.7 XA Thin driver with WLS 6.1 SP1

    I am trying to configure the Oracle 8.1.7.0 thin driver and am getting an SystemException
    when the pool tries to test the connection at server startup. It looks like the
    start() method is failing. I have put Oracle's Classes12.zip, jndi.zip, and the
    jta.zip on the classpath immediately after the weblogic.jar entry. Is this a
    classpath issue? Can someone that has this working please help me. Thanks in
    advance. Steve
    The following is the JDBC Pool entry in the config.xml file:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="0" LoginDelaySeconds="1" MaxCapacity="20"
    Name="oraclePoolSun3500XAThin" Properties="user=sschaber;url=jdbc:oracle:thin:@199.191.94.4:1521:ORCLT;password=sschaber;dataSourceName=oraclePoolSun3500XAThin"
    RefreshMinutes="5" ShrinkPeriodMinutes="30"
    Targets="memphisserver" TestConnectionsOnRelease="true"
    TestConnectionsOnReserve="true" TestTableName="Dual" URL="jdbc:oracle:thin:@199.191.94.4:1521:ORCLT"/>
    Also, here is the entire exception being thrown:
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null
    at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:998)
    at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1114)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <This
    connection will now be refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC> <Connection for XA pool "oraclePoolSun3500XAThin"
    refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <A connection
    from pool oraclePoolSun3500XAThin was tested during reserve with a select
    count(*) from Dual and failed:>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null at weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo.java:998)
    at weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.java:234)
    at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:374)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:465)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:376)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1103)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin> <This
    connection will now be refreshed.>

    This still does not work for me. I must be missing something here. Any help would
    be appreciated.
    Thanks,
    Steve
    "Sree Bodapati" <[email protected]> wrote:
    Hi Steve,
    I see the initial capacity is set to zero , can you push it up to atleast
    few connections and see if it helps, and Let me know.
    thanks
    sree
    "Steve Schaber" <[email protected]> wrote in message
    news:[email protected]...
    I made sure that we have the latest version of the classes12.zip file(8.1.7).
    Also, moved the classes12.zip, jndi.zip, and the jta.zip file beforethe
    weblogic.jar
    file in the classpath. I am still getting the same error.
    Steve
    "Sree Bodapati" <[email protected]> wrote:
    Put the classes12.zip and other zip files before the weblogic.jar
    file
    in
    the classpath. ensure that you have the latest classes12.zip filefrom
    oracle.
    sree
    "Steve Schaber" <[email protected]> wrote in message
    news:[email protected]...
    I am trying to configure the Oracle 8.1.7.0 thin driver and am gettingan
    SystemException
    when the pool tries to test the connection at server startup. It
    looks
    like the
    start() method is failing. I have put Oracle's Classes12.zip,
    jndi.zip,
    and the
    jta.zip on the classpath immediately after the weblogic.jar entry.Is
    this a
    classpath issue? Can someone that has this working please help
    me.
    Thanks in
    advance. Steve
    The following is the JDBC Pool entry in the config.xml file:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    InitialCapacity="0" LoginDelaySeconds="1" MaxCapacity="20"
    Name="oraclePoolSun3500XAThin"
    Properties="user=sschaber;url=jdbc:oracle:thin:@199.191.94.4:1521:ORCLT;pass
    word=sschaber;dataSourceName=oraclePoolSun3500XAThin"
    RefreshMinutes="5" ShrinkPeriodMinutes="30"
    Targets="memphisserver" TestConnectionsOnRelease="true"
    TestConnectionsOnReserve="true" TestTableName="Dual"URL="jdbc:oracle:thin:@199.191.94.4:1521:ORCLT"/>
    Also, here is the entire exception being thrown:
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null
    at
    weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo..
    java:998)
    at
    weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
    ava:234)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:374)
    atweblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at
    weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:11
    14)
    at
    weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
    er.java:238)
    at
    weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
    :229)
    atweblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:08 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><This
    connection will now be refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC> <Connection for XA pool"oraclePoolSun3500XAThin"
    refreshed.>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><A
    connection
    from pool oraclePoolSun3500XAThin was tested during reserve with
    a
    select
    count(*) from Dual and failed:>
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><javax.transaction.SystemException:
    start() failed on resource 'oracle.jdbc.xa.client.Or
    acleXAResource' null at
    weblogic.transaction.internal.ServerResourceInfo.xaStart(ServerResourceInfo..
    java:998)
    at
    weblogic.transaction.internal.ServerResourceInfo.enlist(ServerResourceInfo.j
    ava:234)
    at
    weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTra
    nsactionImpl.java:374)
    atweblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:915)
    at
    weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:46
    5)
    at
    weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.j
    ava:376)
    at
    weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:11
    03)
    at
    weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigg
    er.java:238)
    at
    weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java
    :229)
    atweblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:65)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    <Apr 5, 2002 1:33:10 PM CST> <Info> <JDBC Pool oraclePoolSun3500XAThin><This
    connection will now be refreshed.>

  • Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

    We are using simplified chinese, after swith to bea jdriver, it messed up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince except webservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error. Is
    there a way to turn off isolation level in workshop? I tried manually edit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

    I did try to change the value in this config file as well, but did not help.
    In fact, the installation default setting is with
    '<transaction-isolation-level>' commented out.
    And when I use bea oracle jdriver, it somehow messed up with database
    character set encoding, so our Chinese characters could not be retrieved
    correctly. And I try to set the encoding of jdriver to 'GBK', it did not
    work.
    "Anurag Pareek" <[email protected]> дÈëÏûÏ¢ÐÂÎÅ
    :[email protected]..
    Hello Ma,
    The transaction isolation level value for EJBs backing the JWS files is
    specified in the <transaction-isolation-level> tag in the
    WEB-INF/weblogic-jws-config.xml file of a Workshop project. You can
    manipulate this value to serve your purpose.
    Please do let me know how it goes.
    Regards,
    Anurag
    Workshop Support
    "Ma Jie" <[email protected]> wrote in message
    news:[email protected]..
    We are using simplified chinese, after swith to bea jdriver, it messed
    up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince exceptwebservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error.Is
    there a way to turn off isolation level in workshop? I tried manuallyedit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

  • ConnectionPool problems with WLS 7.0 and Oracle 9.2

    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
    application on the productive system (and only there) we constantly encounter
    a whole set of SQLExceptions which have all in common that the Connection from
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSet
    - Connection has already been closed
    - Closed Statement
    - Transaction is no longer active - status committing
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()
    There are no special Statements which create these errors. They are spread at
    random across practically every query the application creates, and the same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSets are
    closed immediately after use. As an example, I attached a code snippet and a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrent usern,
    since in the approval tests on an almost identical test system these errors never
    occurred.
    I also followed the advice from Oracle and installed the latest Oracle JDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in the application
    classpath (via a reference in the Manifest file of the application jar), not in
    the system classpath? There has never been a problem with that, but in a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script creates for the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath? If
    it is possible, why is it necessary?
    Best regards,
    Andreas Zehrt
    [CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

    Andreas Zehrt wrote:
    Hi Joe,
    Your hint that there is a threading problem was right:
    On further investigation of the code I found out that the class that passes the
    Connection to the DAO not only stores it as a member at some point (which is not
    a good idea anyway) but is also a singleton - then, of course, it's no surprise
    that the Connection gets invalid in a incalculable way when concurrent threads
    share it.
    The singleton instantiation was not so obvious because the way of instantiation
    is controlled by a configuration parameter that can be overridden at different
    levels.
    I changed it and the productive logfiles indicate that the SQLExceptions related
    to that class have disappeared.I am happy to have helped.
    So, thanks a lot for the advice.
    But I am still wondering why this code has worked for so long a time with WLS
    5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
    approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
    it was multi-user environment.Mo idea.
    I still believe that there is a difference between WLS 5.1 and 7.0 in the way
    it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
    a little more explicit about those changes and possible version incompatabilities
    beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
    effect in this case, I will certainly do what I can to see that our documentation
    is explicit about changes.
    Joe
    Best regards, Andreas
    Joe Weinstein <[email protected]> wrote:
    Hi Andreas.
    Andreas Zehrt wrote:
    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
    application on the productive system (and only there) we constantlyencounter
    a whole set of SQLExceptions which have all in common that the Connectionfrom
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSetThat is typically if the statement that created it is either re-executed
    or closed.
    - Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
    would show
    where it was originally closed.
    - Closed Statementsame as above.
    - Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
    datasource,
    and then later trying to use it after the transaction which it was associated
    with,
    is finished.
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
    There are no special Statements which create these errors. They arespread at
    random across practically every query the application creates, andthe same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSetsare
    closed immediately after use. As an example, I attached a code snippetand a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrentusern,
    since in the approval tests on an almost identical test system theseerrors never
    occurred.
    I also followed the advice from Oracle and installed the latest OracleJDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in theapplication
    classpath (via a reference in the Manifest file of the applicationjar), not in
    the system classpath? There has never been a problem with that, butin a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script createsfor the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath?If
    it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
    We also ship
    an oracle thin driver, which becomes obsolete soon...
    I am concerned that your code creates pool connections to be used later.
    The problems
    can arise if more than one thread ever gets the same connection, or if
    the connection
    is used in the same thread, spanning transactions. It does also seem
    that there may
    be a threading issue, because if two threads each call the code to create
    a connection,
    and two connections are made, but one over-writes the other, the two
    threads can
    end up using the same connection, and closing it. The over-written one
    never gets closed,
    resulting in that leak message you got...
    Joe
    The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
    several classes in the business layer, but not used, until the DAOtakes it to make the query.
    So, the Connection is closed where it was opened, not in the DAO class.
    public class ConcernDAOImpl extends BaseDAO {
         public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
    throws DataAccessException, ConstraintException, ComaParseException{>
    sqlMessage.append(")");
    String sqlStmt = sqlMessage.toString();
    PreparedStatement pstmt = null;
    ResultSet rs = null;
    try {
    pstmt = conn.prepareStatement(sqlStmt);
    rs = pstmt.executeQuery();
    while (rs != null && rs.next()) {
    final Concern concern =
    new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
    concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
    return concerns;
    } catch (SQLException sqle) {
    // Wrapps real SQL exception
    String[] message = new String[]{sqle.getMessage(), sqlStmt};
    throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
    sqle);
    } finally {
    closeAll(rs, pstmt);
    _logger.exitDebug(method);
    Here, the Connection is acquired and finally closed
    public class ComaServiceProviderClassicImpl {
         public void updateComplaint(
    final Request updateRequest,
    final ResponseSingleElement response,
    final Principal principal)
    throws SystemException {
    try {
    logger.info("updateComplaint", "store incident");
    // store the incident in the database
    incidentManager.storeIncident(getConnection(), updateIncident);
    // reload the incident from Cache and / or the databaseto get the ContactReferences.
    Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
    getConnection(), updateIncident.getOID());
    } catch (RemoteException rex) {
    // remote exceptions
    rollbackIfNecessary();
    CoreUtils.unwrapRemoteException(rex, logger);
    } catch (SystemException e) {
    // all other exceptions --> rollback if necessary and rethrow
    rollbackIfNecessary();
    throw e;
    } finally {
    removeConnection();
    logger.exitDebug("updateComplaint");
    This is the resulting StackTrace:
    sql exception: [Closed Statement: next] - sql statement: [select *
         at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
         at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
         at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    ####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
    was detected. A Connection leak occurs when a connection obtained from
    the pool was not closed explicitly by calling close() and then was disposed
    by the garbage collector and returned to the connection pool. The following
    stack trace at create shows where the leaked connection was created.
    Stack trace at connection create:
         at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
         at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
         at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
         at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

  • Oracle wallet(oraclepki.jar) is not working with WLS 10.3.1

    An external application is storing a password in oracle wallet i.e cwallet.sso and ewallet.p12 files using OracleWallet technology (oraclepki.jar).
    I have an web application which uses this password stored in the wallet for internal use, this application works fine if we deploy it in OC4J, but if Install the same application in WLS 10.3.1 application is not able to get the password for wallet.
    Oracle wallet require only oraclepki.jar file and this jar file is bundled in the ear file.
    Can someone guide me so that we can use Oracle wallet with WLS.

    Hi
    For me no error is showing. But the whitespace is not getting removed. But this is working fine in Tomcat6.1.
    Any help is appreciated.
    regards
    jossy.

  • Workaround for using Oracle JDBC extension with WLS pooling

    Reading the newsgroup I saw that many of us encountered the problems
    with ClassCastException when tried to use Oracle JDBC extension
    with WLS pooling. I also had.
    In this case BEA recommends to use dangerous
    method getVendorConnection() which exposes
    the physical connection object to your code.
    Yes it's really dangerous because of unsafe usage may breaks
    WLS pooled connection(s).
    Moreover, this practice will make your JDBC code
    unportable (your JDBC code in addition to Oracle dependence
    became Weblogic dependent):
    void doSmth() {
    Connection con = ...;
    Connection vCon = ((WLConnection)con).getVendorConnection();
    // + mess of usage con in one places and vCon in others
    // (where Oracle extensions are needed)
    // !Don't forget to don't close vCon!
    Sux.
    I found the workaround.
    Introduction
    ============
    Yes the real cause of ClassCastException is that
    in depth of Oracle driver the casting
    to class oracle.jdbc.driver.OracleConnection
    (not to interface oracle.jdbc.OracleConnection)
    is performed.
    Someone can say that this is bug or pure desing.
    Weblogic pooled connection provide dynamic
    implementation for all public interfaces
    which real physical (wrapped) connection object implements.
    Great feature!
    But I guess that all interface methods implemented
    by simple call-delegation to physical (wrapped) connection object.
    In case of oracle.jdbc.OracleConnection interface
    this approach doesn't work for at least one its method:
    public OracleConnection unwrap()
    WLS pooled connection shoudn't implement this method by
    delegation to physical connection object BUT should
    return physical connection object itself!
    // Wrong implementation of unwrap()
    // delegation is used
    public OracleConnection unwrap() {
    return physicalConnection.unwrap();
    // Right implementation of unwrap()
    // physical connection returned
    public OracleConnection unwrap() {
    return physicalConnection;
    Workaround
    ==========
    1. Develop your own OracleConnection wrapper class:
    import oracle.jdbc.OracleConnection;
    import weblogic.jdbc.extensions.WLConnection;
    public class MyOracleConnectionImpl implements OracleConnection {
    private OracleConnection con;
    public MyOracleConnectionImpl(OracleConnection connection)
    throws SQLException
    this.con = connection;
    public OracleConnection unwrap() {
    return (OracleConnection)
    ((WLConnection)con).getVendorConnection();
    /* Implement all other methods by delegation to con object */
    2. Don't get Connections directly from DataSource --
    develop your own simple (may be static) utility
    class which retrives Connections from dataSource
    and returns them wrapped into your MyOracleConnectionImpl
    to your code from some method:
    puclic abstract class MyConnectionSource {
    public static Connection getConnection() {
    Connection con = // get it from DataSource
    return new MyOracleConnectionImpl((OracleConnection)con);
    3. Add attribute RemoveInfectedConnectionsEnabled="false"
    to definition of your JDBCConnectionPool within config.xml
    You may do it because of you `safely` use vendorConnection --
    you don't expose it to application code.
    4. Enjoy the Oracle JDBC extensions in your code!
    Example:
    Connection con = MyConnectionSource.getConnection;
    ArrayDescriptor add =
    ArrayDescriptor.createDescriptor("your_type", con);
    Hope it helps to someone.
    Best regards,
    Eugene Voytitsky

    Hello Eugene Voytitsky,
    Thanks Eugene Voytitsky for your idea
    I have tried the solution suggested by You, but it did not work.
    It still throws ClassCastException.
    I am sorry for posting the whole code of two classes below.
    I did this to give you more clarity.
    I am also indicating the place where the exception was thrown..
    Please let me know if I am doing something wrong.
    OracleConnection Wrapper class
    package ejbTesting;
    // sql imports
    import java.sql.CallableStatement;
    import java.sql.Connection;
    import java.sql.DatabaseMetaData;
    import java.sql.PreparedStatement;
    import java.sql.SQLException;
    import java.sql.SQLWarning;
    import java.sql.Statement;
    // util imports
    import java.util.Map;
    import java.util.Properties;
    // imports from Oracle Driver Classes
    import oracle.jdbc.OracleConnection;
    import oracle.jdbc.OracleOCIFailover;
    import oracle.jdbc.OracleSavepoint;
    // import from Weblogic extensions
    import weblogic.jdbc.extensions.WLConnection;
    public class WeblogicConnectionWrapper implements OracleConnection
         // oracle connection object
         private OracleConnection connection;
         public WeblogicConnectionWrapper (OracleConnection orclConnection)
              try
                   this.connection = orclConnection;
              catch(Exception unexpected )
                   unexpected.printStackTrace();
         public OracleConnection unwrap()
              try
              // The datasource returns a weblogic.jdbc.pool.Connection
              // This needs to be type casted to weblogic.jdbc.extensions.WLConnection
              // Only this weblogic.jdbc.extensions.WLConnection CAN BE type casted
              // to OracleConnection
         return (OracleConnection) ((WLConnection) connection).getVendorConnection();
         catch(Exception sqlException )
              sqlException.printStackTrace ();
              return null;
         /* Implement all other methods by delegation to connection object */      
    public Connection _getPC()
    return connection._getPC();
    public void archive(int i, int j, String s)
    throws SQLException
    connection.archive(i, j, s);
    public void assertComplete()
    throws SQLException
    connection.assertComplete();
    public void clearWarnings()
    throws SQLException
    connection.clearWarnings();
    public void close()
    throws SQLException
    connection.close();
    public void commit()
    throws SQLException
    connection.commit();
    public Statement createStatement()
    throws SQLException
    return connection.createStatement();
    public Statement createStatement(int i, int j)
    throws SQLException
    return connection.createStatement(i, j);
    public boolean getAutoClose()
    throws SQLException
    return connection.getAutoClose();
    public boolean getAutoCommit()
    throws SQLException
    return connection.getAutoCommit();
    public CallableStatement getCallWithKey(String s)
    throws SQLException
    return connection.getCallWithKey(s);
    public String getCatalog()
    throws SQLException
    return connection.getCatalog();
    public boolean getCreateStatementAsRefCursor()
    return connection.getCreateStatementAsRefCursor();
    public int getDefaultExecuteBatch()
    return connection.getDefaultExecuteBatch();
    public int getDefaultRowPrefetch()
    return connection.getDefaultRowPrefetch();
    public Object getDescriptor(String s)
    return connection.getDescriptor(s);
    public boolean getExplicitCachingEnabled()
    throws SQLException
    return connection.getExplicitCachingEnabled();
    public boolean getImplicitCachingEnabled()
    throws SQLException
    return connection.getImplicitCachingEnabled();
    public boolean getIncludeSynonyms()
    return connection.getIncludeSynonyms();
    public Object getJavaObject(String s)
    throws SQLException
    return connection.getJavaObject(s);
    public DatabaseMetaData getMetaData()
    throws SQLException
    return connection.getMetaData();
    public Properties getProperties()
    return connection.getProperties();
    public boolean getRemarksReporting()
    return connection.getRemarksReporting();
    public boolean getRestrictGetTables()
    return connection.getRestrictGetTables();
    public String getSQLType(Object obj)
    throws SQLException
    return connection.getSQLType(obj);
    public String getSessionTimeZone()
    return connection.getSessionTimeZone();
    public int getStatementCacheSize()
    throws SQLException
    return connection.getStatementCacheSize();
    public PreparedStatement getStatementWithKey(String s)
    throws SQLException
    return connection.getStatementWithKey(s);
    public int getStmtCacheSize()
    return connection.getStmtCacheSize();
    public short getStructAttrCsId()
    throws SQLException
    return connection.getStructAttrCsId();
    public boolean getSynchronousMode()
    return connection.getSynchronousMode();
    public int getTransactionIsolation()
    throws SQLException
    return connection.getTransactionIsolation();
    public Map getTypeMap()
    throws SQLException
    return connection.getTypeMap();
    public String getUserName()
    throws SQLException
    return connection.getUserName();
    public boolean getUsingXAFlag()
    return connection.getUsingXAFlag();
    public SQLWarning getWarnings()
    throws SQLException
    return connection.getWarnings();
    public boolean getXAErrorFlag()
    return connection.getXAErrorFlag();
    public boolean isClosed()
    throws SQLException
    return connection.isClosed();
    public boolean isLogicalConnection()
    return connection.isLogicalConnection();
    public boolean isReadOnly()
    throws SQLException
    return connection.isReadOnly();
    public String nativeSQL(String s)
    throws SQLException
    return connection.nativeSQL(s);
    public Object openJoltConnection(String s, short word0, short word1)
    return connection.openJoltConnection(s, word0, word1);
    public void oracleReleaseSavepoint(OracleSavepoint oraclesavepoint)
    throws SQLException
    connection.oracleReleaseSavepoint(oraclesavepoint);
    public void oracleRollback(OracleSavepoint oraclesavepoint)
    throws SQLException
    connection.oracleRollback(oraclesavepoint);
    public OracleSavepoint oracleSetSavepoint()
    throws SQLException
    return connection.oracleSetSavepoint();
    public OracleSavepoint oracleSetSavepoint(String s)
    throws SQLException
    return connection.oracleSetSavepoint(s);
    public int pingDatabase(int i)
    throws SQLException
    return connection.pingDatabase(i);
    public CallableStatement prepareCall(String s)
    throws SQLException
    return connection.prepareCall(s);
    public CallableStatement prepareCall(String s, int i, int j)
    throws SQLException
    return connection.prepareCall(s, i, j);
    public CallableStatement prepareCallWithKey(String s)
    throws SQLException
    return connection.prepareCallWithKey(s);
    public PreparedStatement prepareStatement(String s)
    throws SQLException
    return connection.prepareStatement(s);
    public PreparedStatement prepareStatement(String s, int i, int j)
    throws SQLException
    return connection.prepareStatement(s, i, j);
    public PreparedStatement prepareStatementWithKey(String s)
    throws SQLException
    return connection.prepareStatementWithKey(s);
    public void purgeExplicitCache()
    throws SQLException
    connection.purgeExplicitCache();
    public void purgeImplicitCache()
    throws SQLException
    connection.purgeImplicitCache();
    public void putDescriptor(String s, Object obj)
    throws SQLException
    connection.putDescriptor(s, obj);
    public void registerApiDescription(String s, short word0, short word1, String
    s1)
    connection.registerApiDescription(s, word0, word1, s1);
    public void registerSQLType(String s, Class class1)
    throws SQLException
    connection.registerSQLType(s, class1);
    public void registerSQLType(String s, String s1)
    throws SQLException
    connection.registerSQLType(s, s1);
    public void registerTAFCallback(OracleOCIFailover oracleocifailover, Object
    obj)
    throws SQLException
    connection.registerTAFCallback(oracleocifailover, obj);
    public void rollback()
    throws SQLException
    connection.rollback();
    public void setAutoClose(boolean flag)
    throws SQLException
    connection.setAutoClose(flag);
    public void setAutoCommit(boolean flag)
    throws SQLException
    connection.setAutoCommit(flag);
    public void setCatalog(String s)
    throws SQLException
    connection.setCatalog(s);
    public void setCreateStatementAsRefCursor(boolean flag)
    connection.setCreateStatementAsRefCursor(flag);
    public void setDefaultExecuteBatch(int i)
    throws SQLException
    connection.setDefaultExecuteBatch(i);
    public void setDefaultRowPrefetch(int i)
    throws SQLException
    connection.setDefaultRowPrefetch(i);
    public void setExplicitCachingEnabled(boolean flag)
    throws SQLException
    connection.setExplicitCachingEnabled(flag);
    public void setImplicitCachingEnabled(boolean flag)
    throws SQLException
    connection.setImplicitCachingEnabled(flag);
    public void setIncludeSynonyms(boolean flag)
    connection.setIncludeSynonyms(flag);
    public void setReadOnly(boolean flag)
    throws SQLException
    connection.setReadOnly(flag);
    public void setRemarksReporting(boolean flag)
    connection.setRemarksReporting(flag);
    public void setRestrictGetTables(boolean flag)
    connection.setRestrictGetTables(flag);
    public void setSessionTimeZone(String s)
    throws SQLException
    connection.setSessionTimeZone(s);
    public void setStatementCacheSize(int i)
    throws SQLException
    connection.setStatementCacheSize(i);
    public void setStmtCacheSize(int i)
    throws SQLException
    connection.setStmtCacheSize(i);
    public void setStmtCacheSize(int i, boolean flag)
    throws SQLException
    connection.setStmtCacheSize(i, flag);
    public void setSynchronousMode(boolean flag)
    connection.setSynchronousMode(flag);
    public void setTransactionIsolation(int i)
    throws SQLException
    connection.setTransactionIsolation(i);
    public void setTypeMap(Map map)
    throws SQLException
    connection.setTypeMap(map);
    public void setUsingXAFlag(boolean flag)
    connection.setUsingXAFlag(flag);
    public void setWrapper(OracleConnection oracleconnection)
    connection.setWrapper(oracleconnection);
    public void setXAErrorFlag(boolean flag)
    connection.setXAErrorFlag(flag);
    public void shutdown(int i)
    throws SQLException
    connection.shutdown(i);
    public void startup(String s, int i)
    throws SQLException
    connection.startup(s, i);
    Util class to get Wrapped Connections from
    datasource
    package ejbTesting;
    // j2ee imports
    import javax.naming.InitialContext;
    import javax.sql.DataSource;
    // sql imports
    import java.sql.Connection;
    // imports from Oracle Driver Classes
    import oracle.jdbc.OracleConnection;
    * Wrapper class for the DataSource Connection from Weblogic pool
    public class DataSourceConnectionWrapper
         // datasource variable
         private static transient DataSource datasource = null;
         private static String dbName = "jdbc/workbench";
    * Method that returns the database connection
         public static Connection getConnection()
              try
                   // initialsing the datasource object
                   initialiseDataSource ();
                   // Getting a connection from the datasource
                   Connection con = datasource.getConnection( );
                   // wrapping it custom wrapper class and
                   // returning the connection object
                   return new WeblogicConnectionWrapper((OracleConnection)con);
              catch(Exception exception )
                   exception.printStackTrace();
                   return null;
         private static void initialiseDataSource( ) throws Exception
    if ( datasource == null )
    try
    InitialContext ic = new InitialContext( );
    datasource = (DataSource) ic.lookup( dbName );
    catch (Exception ne )
    throw new Exception( "NamingException while looking up DataSource with
    JNDI name" +
    dbName + ": \n" + ne.getMessage( ) );
    Exception Stack Trace
    The line 46 in DataSourceConnectionWrapper
    corresponds to
    return new WeblogicConnectionWrapper((OracleConnection)con);
    Which I feel is logical as the connection which we get from Weblogic
    datasource cannot be type casted to OracleConnection
    java.lang.ClassCastException: weblogic.jdbc.pool.Connection
    at ejbTesting.DataSourceConnectionWrapper.getConnection(DataSourceConnectionWrapper.java:46)

  • Does Oracle 8.0.5 work with WLS 7.0

    We are having problems with WLS 7.0, Oracle 8.0.5 and CMP.
    Do anybody know a link or anything to help?
    Or do we have to upgrade the database to 8.1.7 (at least)?
    Regards
    Glenn Petersen

    Hi Glenn
    What is the problem you are seeing? any specific exceptions?
    sree
    "Glenn Petersen" <[email protected]> wrote in message
    news:[email protected]..
    >
    We are having problems with WLS 7.0, Oracle 8.0.5 and CMP.
    Do anybody know a link or anything to help?
    Or do we have to upgrade the database to 8.1.7 (at least)?
    Regards
    Glenn Petersen

  • Statement.cancel() no longer works with WLS 8.1?

    Has anyone else had a problem with the cancel() method in oracle.jdbc.OracleCallableStatement
    on WLS 8.1 not doing a very good job of killing the thread in Oracle? We were
    using cancel() with weblogic.jdbc.pool.CallableStatement on WLS 6.1 and it does
    a very good job of killing the query on the Oracle side. But almost all of this
    package has been removed and we've been told we need to use the Oracle vendor
    package to get our stuff to work on 8.1. I decompiled both classes and they each
    have very different implementations of the cancel() method.
    I think I've managed to convert all of our DB access classes to the Oracle vendor
    package successfully, with the exception of this issue. We use cancel() let users
    cancel large queries and to cancel an existing query if a user tries to run a
    new one. Since we implemented it we've had a huge performance boost from the lack
    of runaway queries in the DB. It would be a real pain if we can't find a way to
    get the Oracle version to work. Any help or tales of similar experiences would
    be greatly appreciated.
    thx a lot,
    Matt Savino

    I did a search on Oracle MetaLink. I didn't see any Oracle-confirmed
    bugs related to cancel. I did see one user in the JDBC forum that
    was having a problem with a remote (not on the local machine)
    cancel. At this point, this case will need to be worked through
    support - they will need to generate a reproducer and assuming they
    do, file a tar with Oracle.
    "Stephen Felts" <[email protected]> wrote in message
    news:[email protected]...
    Regarding the wrappers - now I remember discussing this with you in thebeta newsgroup about a month ago.
    The goal was to make it transparent that everything was changed to bepassthrough in 8.1.
    The good news is that you can now use the vendor interface directly andget their extensions
    directly. That means that the wrapper for Oracle will be different fromthe wrapper for DB2.
    Further, any new excentions in the interface will become visible to theapplication.
    >
    The bad news is that this only works when the vendor has a definedinterface; it doesn't work
    if only a class is defined.
    This is a problem for some of the Oracle data type classes that don't havedefined interfaces
    and the reason why weblogic.vendor.oracle interfaces still need to be usedfor these classes.
    That also applies to BEA classes and weblogic.jdbc.pool only had classesdefined, not interfaces.
    >
    We should have documented change.
    Regarding the real problem of cancel(), the WLS JDBC code is not doinganything here
    except passing the cancel call through to the thin driver. My guess isthat this is
    a problem in the thin driver. I haven't had a chance to research this onthe Oracle site yet.
    >
    >
    "Matt Savino" <[email protected]> wrote in message
    news:[email protected]...
    >>
    Thanks a ton for your quick reply on this. On recommendation from yoursupport
    team (case 426562) here is the primary line that we had to change:
    [old] weblogic.jdbc.pool.CallableStatement cStat
    =(weblogic.jdbc.pool.CallableStatement)connection.prepareCall(call);
    >>
    [new] - oracle.jdbc.OracleCallableStatement cStat
    =(oracle.jdbc.OracleCallableStatement)connection.prepareCall(call);
    >>
    (FYI - We need this to take adavantage of some of the advanced Oraclefeatures
    like returning multiple ResultSets. We'd like to avoid using the OCIclient if
    possible, assuming that would even solve this.)
    Further down in the code, here is the cancel() method:
    public void cancelCall() {
    try {
    if (cStat != null) cStat.cancel();
    releaseConnection();
    catch (Exception e){ e.printStackTrace(); }
    In both cases the cancel() call throws no error, but only on the oldversion do
    we actually see the thread die promptly in Oracle.
    Thanks again for your help on this,
    Matt
    "Stephen Felts" <[email protected]> wrote:
    In versions prior to WLS 8.1, each Oracle extension had to be
    individually,
    explicitly wrapped
    (and not all extensions were supported).
    In WLS 8.1, it is a clean passthrough directly of all Oracle interfaces
    using a dynamic proxy so that
    all Oracle extensions show through. The only additional work that WLS
    is doing to to
    ensure that transactions are managed correctly (which shouldn't have
    an impact here).
    Note that in versions prior to WLS 8.1, you were using classes12.zip
    for the client and now you are using ojdbc14.jar. There are
    some big differences in this client implementation.
    Maybe you should try testing this standalone without WLS in the picture
    to see
    if this is a driver problem. WLS doesn't have the code that isresponsible
    for killing the thread in Oracle.
    I'm not sure I understand what code you are changing. The goal was to
    preseve the interfaces
    provided in releases prior to 8.1. Code you show me an old code line
    and what you are
    changing it to? Thanks.
    "Matt Savino" <[email protected]> wrote in message
    news:[email protected]...
    >>>>
    Has anyone else had a problem with the cancel() method inoracle.jdbc.OracleCallableStatement
    on WLS 8.1 not doing a very good job of killing the thread in Oracle?We were
    using cancel() with weblogic.jdbc.pool.CallableStatement on WLS 6.1and it does
    a very good job of killing the query on the Oracle side. But almostall of this
    package has been removed and we've been told we need to use the
    Oracle
    vendor
    package to get our stuff to work on 8.1. I decompiled both classesand they each
    have very different implementations of the cancel() method.
    I think I've managed to convert all of our DB access classes to theOracle vendor
    package successfully, with the exception of this issue. We use
    cancel()
    let users
    cancel large queries and to cancel an existing query if a user triesto run a
    new one. Since we implemented it we've had a huge performance boostfrom the lack
    of runaway queries in the DB. It would be a real pain if we can't
    find
    a way to
    get the Oracle version to work. Any help or tales of similar
    experiences
    would
    be greatly appreciated.
    thx a lot,
    Matt Savino

  • OEPE Release 11gR1 (11.1.1.4.0)  doesn't work with WLS 10.3.4

    Hello All,
    The OSB Release 11gR1 (11.1.1.4.0) doesn't install with WLS 10.0, and it seems to be installed sucessfully with WLS 10.3.4.
    Now, when trying to create a server in OEPE Release 11gR1, it complains as it requires WLS 10.0 binary!!
    Big confusion when you try to use these new versions.
    Any hint, direction?
    Regards,
    Ragae

    The OSB Release 11gR1 (11.1.1.4.0) doesn't install with WLS 10.0, and it seems to be installed sucessfully with WLS 10.3.4.Yes, it is because WLS 10.0 is 10g release and Weblogic 10.3.4 is 11g R1 release. Morever, OSB 11.1.1.4 (OSB 11g R1 PS3) is compatible with Weblogic 11g R1 PS3 (10.3.4) only.
    Now, when trying to create a server in OEPE Release 11gR1, it complains as it requires WLS 10.0 binary!!OEPE supports the following versions of Oracle WebLogic Server:
    11g Release 1 Patch Set 3
    11g Release 1 Patch Set 2
    11g Release 1 Patch Set 1
    11g Release 1
    10g Release 3
    10.0
    9.2
    Note that there is limited support for versions 9.1, 9.0, and 8.1.
    While creating a server in OEPE choose appropriate server version in "Server Type" option.
    Regards,
    Anuj

  • Installation of webgate on Solaris (sparcv9) with WLS 10.3.5 and Apache2

    Problem Description: We have installed IDM 11g and OAM 10.1.4.3 on RHEL5.5 hosts, respectively. We have successfully installed all the components:
    Environment Details:
    - Server1 -- 64 bit Intel RHEL5
    Fusion Middleware Identity Management - 11.1.1.2
    WLS 10.3.2
    ODSM,OID,OVD
    DB 10.2.0.4
    - Server 2 32-bit Intel RHEL5
    OAM 10.1.4.3
    OHS 11.1.1.2
    After successfully installing these hosts, we needed to create a webhost from where we could test our protected resources. This host would have a sparc v9 OS, include WLS 10.3.5, and use apache2 as its web server. These have all been successfully installed by root and are running.
    Our next step was to create the webgate/access gate on the OAM host and setup the necessary policy. This was successful.
    We then copied Oracle_Access_Manager10_1_4_3_0_sparc-s2_APACHE2_WebGate to the host and started the installation. Since the host is headless (just a host -- no keyboard, mouse, or gui attached to it) we have to ssh to the host and execute all the installs from the command line without gui. When we got to entering the webgate id and hit return... the process just ended without any error or logfiles. We are assuming that at that point the webgate software was installed but not configured.
    We went ahead and tried the configureWebGate script:
    ./start_configureWebGate -i /opt/oracle/middleware/webgate -l WebGate
    ld.so.1: configureWebGate: fatal: /opt/oracle/middleware/webgate/access/oblix/tools/configureWebGate/../../../oblix/lib/libstdc++.so.5: wrong ELF data format: ELFDATA2LSB
    Killed
    We have successfully installed OAM and IDM many times and have installed webhosts as well... but the webhosts have always been RHEL5 with WLS and OHS instead of Sparc, wls, and apache. Is there anything special about a sparc or apache install?
    WLS and apache were installed as root... we have tried installing the webgate as root, oracle, even apache... but get the same results. The gcc libs are downloaded and available, but the error we see during configuration seems to indicate that they are not found. We have tried seting the LD_LIBRARY_PATH to include the directory containing the libs.
    Edited by: OldGuy on Jul 7, 2011 4:04 AM

    On another note... is there a Sparc equivalent for the mod_wl_ohs.conf where we would place
    <Location /<deployed app>>
    SetHandler weblogic-handler
    WebLogicHost <weblogichost>
    WebLogicPort 7001
    </Location>
    It appears that this goes into the apache httpd.conf file, correct? Or does the mod_wl_ohs.conf equivalent exist?
    We have just about completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host.
    When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, no logfile entries... just a blank browser.

  • Registering a third party XAResource with WLS TM

    The WebLogic 6.x documentation for registering third party XA resources
              contains the following code snippet: -
              XAResource res = ... // Resource provider's implementation of XAResource
              How do you get a providers implementation?
              Where is this documented?
              

    7.0 is great however there are those of us out here who have spent hundreds of
              thousands of dollars using weblogic 6.x and are struggling through getting 2pc
              to work with different vendors. I would strongly suggest that BEA provide
              detailed documentation which consists of the following for 6.1 and greater and
              not put off till tomorrow solving the problems we as your customers have today
              Detailed setup information for
              1. IBM MQ
              2. Firano
              3. Sybase
              4. Oracle
              5. MS SQL Server
              With examples which work I mean full examples which show the following:
              1. Using JDBC to update a dbms on one connection pool and
              having a message sent to another XA resource which is persistent
              all part of a single transaction
              2. Using two connection pools two different servers doing simple
              updates/inserts using a single transaction
              3. Specific version numbers tested I know for sybase you mention their
              JConnect 5.2.1 but there is only 5.2 with EBF's and 5.5 with EBFs
              which specific sybase server version not just 12.x but 12.x with the
              following
              EBF's applied same for jdbc driver with complete example.
              It seems some of the more complicated operations are the least documented
              which is the inverse of what we as users would expect.
              We have spent probably 8-9 days with our dbas and myself trying to get item
              #2 above to work. Rob Wollen has helped in that it seems my sybase config is
              correct on weblogic but we still havent solved the problem. Perhaps it wont
              work
              with Sybase Jconnect 5.2 or 5.5 with 12.0 version of their product??
              I had also opened up a case back last october which totally was non-productive.
              So please please dont wait on new versions to fix documentation issues which
              are present today.
              thanks Larry
              Priscilla Fung wrote:
              > We have been realizing the lack of documentation for third party vendors who
              > would like to participate in distributed transactions coordinated by WLS TM
              > (similarly for vendors who would like to import foreign distributed
              > transactions into WLS). We are in the process of adding extremely detailed
              > documentation in this area in the ISV guide in the 7.0 release.
              >
              > Regards,
              > Priscilla
              >
              > Robbie Williams <[email protected]> wrote in message
              > news:[email protected]...
              > >
              > > Further more, the WebLogic JTA documentation states that it is 'important'
              > to register
              > > the XAResource before enlisting yet we have found in initial testing that
              > without
              > > registration the third party resource does enlist correctly and partakes
              > in the
              > > 2PC. The BEA white paper jmsjta states that the third party resource
              > 'must' be
              > > registered.
              > >
              > > Neither document gives any explanations as to why third party resources
              > should
              > > be registered and the implications of not doing so - most disappointing.
              > >
              > > Robbie Williams <[email protected]> wrote:
              > > >The WebLogic 6.x documentation for registering third party XA resources
              > > >
              > > >contains the following code snippet: -
              > > >
              > > >XAResource res = ... // Resource provider's implementation of XAResource
              > > >
              > > >How do you get a providers implementation?
              > > >Where is this documented?
              > > >
              > >
              > >
              > >
              

  • Are ADF 12c apps supported on JCS with WLS 12.1.3 instance?

    A customer is interested in JCS Enterprise (not JCS- Sas Ext) with WLS 12.1.3 release. 
    Customer is asking whether ADF 12c apps are supported on JCS and on WLS 12.1.3 instance.
    Thank you.

    Guys,
    Just to close this topic, the answer (that George already got) is:
    "A full JRF is included and preconfigured in both the 11g and 12c choices of WLS on JCS.
    It is ADF 12c (12.1.3) on the WLS 12c (12.1.3) environment.."
    Cheers,
    Bogdan
    #OracleCloud
    https://blogs.oracle.com/oraclecloud4developers/

  • WLI 2.1 sp2 with WLS 6.1 sp3

    Hi,
    I am unable to start the integration server WLI 2.1 sp2 with WLS 6.1 sp3.
    It gives the following errors:
    1.<Aug 1, 2002 10:56:29 AM EDT> <Error> <J2EE> <Error deploying application
    wlpi-ejb.jar:
    Unable to deploy EJB: Audit from wlpi-ejb.jar:
    There is a mismatch between the bean code and generated
    code.com.bea.wlpi.Audit . Please rerun ejbc on the bean code.The error was
    java.lang.NoSuchFieldException
    at java.lang.Class.getField0(Native Method)
    at java.lang.Class.getDeclaredField(Class.java:1113)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBean
    InfoImpl.java:651)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(Client
    DrivenBeanInfoImpl.java:723)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
    Impl.java:823)
    at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
    at weblogic.j2ee.Application.addComponent(Application.java:170)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:360) at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:285)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:239)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:199)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:360) at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy46.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
    ServerMBean_CachingStub.java:2977)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
    icationManager.java:372)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
    r.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:360) at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy68.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
    ApplicationManagerMBean_CachingStub.java:480)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
    at weblogic.management.Admin.finish(Admin.java:644)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
    at weblogic.Server.main(Server.java:35)
    2. <Aug 1, 2002 10:58:09 AM EDT> <Critical> <WebLogicServer> <Failed to
    invoke startup class "TimeProcessor", java.lang.Exception: TimeProcessor
    startup failed! Check arguments.>
    3.<Aug 1, 2002 10:58:13 AM EDT> <Info> <EJB> <EJB Exception during
    invocation from home:
    [email protected]ffc94 threw
    exception: java.lang.IllegalStateException
    java.lang.IllegalStateException
    at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.setState(Unknown Source)
    at com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(Unknown Source)
    at
    com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(PluginMan
    agerCfgBean_gebmxi_EOImpl.java:1428)
    at
    com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl_WLSkel.invoke(
    Unknown Source) at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
    at
    weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
    :93)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:167)
    at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :262)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy109.init(Unknown Source)
    at com.bea.wlpi.server.initlistener.InitListenerBean.onMessage(Unknown
    Source)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:262)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:214)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1865)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    Unable to initialize WebLogic Integration - BPM Server:
    java.rmi.RemoteException: EJB Exception: ; nested exception is:
    java.lang.IllegalStateException
    java.lang.IllegalStateException
    <<no stack trace available>>
    Am I missing something ????? Any help is appreciated.
    Thanks in advance.
    Sangeetha.

    Jim,
    I tried the new upgrade installer (in Windows this time),
    I din't get problem no 3.
    But 2 which seemed to work before after changing the configuration file
    fails. The server automatically shuts down with the following message:
    <Aug 6, 2002 4:33:33 PM EDT> <Emergency> <WebLogicServer> <Server shutdown
    due to fatal exception: w
    eblogic.t3.srvr.FatalStartupException: Can't start server due to startup
    class failure TimeProcessor
    - with nested exception:
    [java.lang.Exception: TimeProcessor startup failed! Check arguments.]>
    <Aug 6, 2002 4:33:33 PM EDT> <Info> <WebLogicServer> <Shutdown has
    completed.>
    Problem no 1 still persists.
    I am also attaching my configuration file.
    Any help is much appreciated.
    Thanks,
    Sangeetha.
    "Jim Hinkey" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sangeetha,
    The Upgrade Installer should be available now on the support downloads.
    -Jim
    Sangeetha Raghavan wrote:
    Hi David,
    I am unable to download the file thru' the ftpserver.
    The download got cancelled with a message like
    'connection closed by the remote server'.
    Please let me know when it is available at the support downloads.
    Thanks.
    Sangeetha.
    "R J David Burke" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sangeetha
    My apologies for the inconvenience you are experiencing. We havediscovered
    a problem with the website for the WLI 2.1 SP2 upgrade installer,providing
    an incorrect file.
    We are working to correct this immediately. In the mean time, the
    proper
    file can be accessed from our FTP server. The details are:
    server: ftpsupport.bea.com
    user: support
    password: xuquoov (expires on Sunday)
    path: /pub/wli21sp2
    files: wlintegration21sp2_upgrade_win.exe - upgrade installer for
    Windows
    wlintegration21sp2_upgrade_unix.zip - upgrade installerfor
    Unix-based platforms
    For security purposes, directory listings are not enabled, so you willneed
    to specify the file by name.
    Regards, David
    "Sangeetha Raghavan" <[email protected]> wrote in message
    news:[email protected]...
    Hi Jim,
    I upgraded from WLI 2.1 sp1 to WLI 2.1 sp2.
    I am not running in a clustered environment.
    Attached is my configutaion file.
    Thanks.
    Sangeetha.
    "Jim Hinkey" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sangeetha,
    Just a few questions...
    Did you upgrade or migrate? From which version did you
    upgrade/migrate?
    Are
    you running in a clustered environment? Can you send your
    config.xml?
    >>>>>
    Thanks,
    Jim
    "Sangeetha.R" wrote:
    Hi Jim,
    I am using Linux and Oracle 8i
    I made the changes in the config.xml and it did solve problem 2.
    Problem 1 and 3 still persists.
    Thanks in Advance.
    Sangeetha.
    "Jim Hinkey" <[email protected]> wrote in message
    news:[email protected]...
    Hi Sangeetha,
    Can you tell me what OS and DB you are using? Also, have you
    implemented
    the
    changes talked about in Release Notes section "Time Services
    Changes
    in
    BPM"? I
    think that is causing problem 2.
    Thanks,
    Jim
    "Sangeetha.R" wrote:
    Hi,
    I am unable to start the integration server WLI 2.1 sp2 with
    WLS
    6.1
    sp3.
    It gives the following errors:
    1.<Aug 1, 2002 10:56:29 AM EDT> <Error> <J2EE> <Error
    deploying
    application
    wlpi-ejb.jar:
    Unable to deploy EJB: Audit from wlpi-ejb.jar:
    There is a mismatch between the bean code and generated
    code.com.bea.wlpi.Audit . Please rerun ejbc on the bean
    code.The
    error
    was
    java.lang.NoSuchFieldException
    at java.lang.Class.getField0(Native Method)
    at java.lang.Class.getDeclaredField(Class.java:1113)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMDField(ClientDrivenBean
    InfoImpl.java:651)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.setMethodDescriptors(Client
    >>>>
    DrivenBeanInfoImpl.java:723)
    at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfo
    Impl.java:823)
    atweblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
    at
    weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
    atweblogic.j2ee.Application.addComponent(Application.java:170)
    atweblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:360) at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
    Target.java:285)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
    eploymentTarget.java:239)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
    entTarget.java:199)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:360) at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    >>>>>>>>
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy46.updateDeployments(Unknown Source)
    at
    weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
    ServerMBean_CachingStub.java:2977)
    at
    weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
    icationManager.java:372)
    at
    weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
    r.java:160)
    at java.lang.reflect.Method.invoke(Native Method)
    at
    weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
    .java:636)
    at
    weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
    21)
    at
    weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
    nImpl.java:360) at
    com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy68.start(Unknown Source)
    at
    weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
    ApplicationManagerMBean_CachingStub.java:480)
    atweblogic.management.Admin.startApplicationManager(Admin.java:1234)
    at weblogic.management.Admin.finish(Admin.java:644)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
    at weblogic.Server.main(Server.java:35)
    >
    2. <Aug 1, 2002 10:58:09 AM EDT> <Critical> <WebLogicServer>
    <Failed
    to
    invoke startup class "TimeProcessor", java.lang.Exception:TimeProcessor
    startup failed! Check arguments.>
    >
    3.<Aug 1, 2002 10:58:13 AM EDT> <Info> <EJB> <EJB Exception
    during
    invocation from home:
    [email protected]ffc94
    threw
    exception: java.lang.IllegalStateException
    java.lang.IllegalStateException
    at
    com.bea.wlpi.server.plugin.PluginManagerCfgImpl.setState(Unknown
    Source)
    at
    com.bea.wlpi.server.plugin.PluginManagerCfgImpl.init(Unknown
    Source)
    at
    com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl.init(PluginMan
    agerCfgBean_gebmxi_EOImpl.java:1428)
    at
    com.bea.wlpi.server.plugin.PluginManagerCfgBean_gebmxi_EOImpl_WLSkel.invoke(
    Unknown Source) at
    weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
    at
    weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
    :93)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
    atweblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:167)
    at
    weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
    atweblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :262)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :229)
    atweblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy109.init(Unknown Source)
    atcom.bea.wlpi.server.initlistener.InitListenerBean.onMessage(Unknown
    Source)
    at
    weblogic.ejb20.internal.MDListener.execute(MDListener.java:262)
    atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:214)
    at
    weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1865)
    at
    weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    atweblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >>>>>>>>>
    Unable to initialize WebLogic Integration - BPM Server:
    java.rmi.RemoteException: EJB Exception: ; nested exceptionis:
    java.lang.IllegalStateException
    java.lang.IllegalStateException
    <<no stack trace available>>--------------------------------------------------------------------------
    >
    Am I missing something ????? Any help is appreciated.
    Thanks in advance.
    Sangeetha.
    [config.xml]

  • Error while installing Oracle Apps server 10.1.3 with Oracle DB 11.2.0.2

    Error while installing Oracle Apps server 10.1.3 with Oracle DB 11.2.0.2 residing in the same server and being used by Apps server as it's metadata.
    bash-3.00$ export ORACLE_HOME=/data/ora11g/app/ora11g/product/11.2.0
    bash-3.00$ cd /data/OAS/install/soa_schemas/irca/
    bash-3.00$ ./irca.sh
    Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
    (c) Copyright 2006 Oracle Corporation. All rights reserved.
    ERROR: Cannot find library - /data/ora11g/app/ora11g/product/11.2.0/jdbc/lib/ojdbc14.jar
    Please verify that the ORACLE_HOME is set correctly.
    bash-3.00$

    Hi Craig,
    Database 11gR2 could be used for Installing Application Server 10.1.3.x but with some limitation.
    So please review the note:-887365.1 Oracle Database 11g Release 2 (11.2) Certification for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4)
    Section :- Oracle Application Server 10g Release 3 (10.1.3)
    Regards,
    Praaksh.

Maybe you are looking for

  • Setting up mail services. Name of server needs to be changed?

    I setup my xserve with snow leopard. By default it was named server.ourcompanyname.private. Here is my problem Im trying to host our company web site along with mail services. Need to bring all this in-house. I have with my web provider 5 dedicated I

  • Iphone 4 askes to setup as new phone when plugged into iTunes

    I have an iPhone 4 that has already been setup using iCloud.  I want to make a backup on my MAC.  When I plug it into iTunes it only gives me options to setup as a new phone or restore from backup.  It will not let me just back up this existing phone

  • PDF created in InDesign -Field Visibility Issues in LifeCycle

    I am working with pdf versions of brochures created in InDesign/Illustrator etc.  I am adding two simple fields to these forms and in the past it has worked easily. I have an image field where a logo can be uploaded and a text field next to it.  Behi

  • Pass parameter to another block

    I try to pass parameter to another block. but i have error message. error:PL/SQL: ORA-00904: "C1DATA_REF"."c": invalid identifier. Would you help me? ___________________________+++my code+++ CREATE OR REPLACE PROCEDURE GETID (a IN TEST.COUNTRY%TYPE,

  • Soft Proofing: may not work on my screen

    First of all: Thanks so much for implementing soft proofing! Especially in such an easy way! I was really hoping you'd do it exactly like that. Anyway, I've got a wide gamut monitor (Thinkpad W520 laptop screen). And I've got an image with a lot of s