Cluster with WLS 5.1 and WLS 8.1 servers?

hi all,
we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
I'm now thinking of is: is it possible to run a WLS cluster that has 2
Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
Reason of thinking so, is that want to have the most failsafe configration
as possible during our upgrade.
I searched the BEA docs, but didn't find anything.
any help would be fine.
thanks
Alexander

You can have it but not for fail-safe configuration.
It is not possible to have clusters with different
WLS versions especially between 5.1 & 8.1
Kumar
Alexander von Alkier wrote:
hi all,
we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
I'm now thinking of is: is it possible to run a WLS cluster that has 2
Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
Reason of thinking so, is that want to have the most failsafe configration
as possible during our upgrade.
I searched the BEA docs, but didn't find anything.
any help would be fine.
thanks
Alexander

Similar Messages

  • Cluster with 2 linux machines and ODI console - some questions

    Hello,
    I need to setup domain with ODI plugins (console etc.) on clustered environment. OS is Oracle Linux 6.3.
    I've read this documentation:http://docs.oracle.com/cd/E13222_01/wls/docs81/adminguide/createdomain.html#CreateClusteredDomain and I have some additional questions:
    - I know I need to install weblogic on 2 machines. Should I install Oracle Data Integrator on 2 machines as well?
    - Creating domains, starting domains etc. I assume I should do this on first server? (for example, via ssh). Or I will need to login via cluster ip addres?
    - MultiCast Address: this is not entirely clear for me. Should this ip aldready exist in my environment - should I configure my network interfaces somehow? Or, I simply need to provide any ip from 224.0.0.0 to 239.255.255.255 and this will work?

    MukeshNegi wrote:
    Which version of weblogic you are using ?Weblogic 11g, 64-bit.
    MukeshNegi wrote:
    if you are using shared filesystem between your machines then you don't need to install again on second server, Simply register ORACLE_HOME for ODI and oracle_common with oraInventory on second server.What do you mean "shared file system"? Let's say I have 2 separate physical machines, and they exists in the same LAN network. And I assume ORACLE_HOME is weblogic home directory, but what is "oracle_common"? Can you describe all of this more detailed?
    MukeshNegi wrote:
    Simply go to $ODI_ORACLE_HOME/common/bin on server1
    run config.sh and select following from domain template
    - Oracle Enterprise Manager Plug-in for ODI
    - Oracle Enterprise Manager Plug-in
    - Oracle Data Integrator Console
    - Oracle Data Integrator Agent
    - Oracle JRFShould I do the same on second server machine? If not, how weblogic will know about other physical machine in my network and that it should be available to join my cluster? There is no domain and no admin server set on second server, should not I do this? There are a lot of tutorials describing how to setup cluster via config.sh od enterprise manager console, but:
    - they describe how to add managed server to my cluster, but I need to know about physical machine servers. So, should I create managed server on second machine somehow? What about my domains - they should be re-created the same way on second server? I can't find any information about this, there are only enterprise manager screenshoots showing how to create managed server on the same physical machine and how to join managed servers into one cluster. But all of this don't tell me anything what should I do to complete my scenario.
    - cluster ip addreess. I still don't understand this. End user should be able to access odi console via cluster address, am I right? So, is there any system network configuration required? How this ip addres is created?
    - I have set up all of this (odi/weblogic/domain) on single machine and I have second server with only operating system installed (the same Oracle Linux). What's the simples way to join this second physical machine and make all of this working as clustered environment? Is there any step by step instruction/tutorial etc describing ALL steps should be done?
    Sorry for basic questions, I'm really newbie with this and I hope you are patient enough to answer all of this ;)
    Edited by: 960949 on 2012-12-10 01:36
    Edited by: 960949 on 2012-12-10 01:38
    Edited by: 960949 on 2012-12-10 01:56

  • WLS 6.1 and WLS 6.1 Service Pack1 install clears out registry.xml

    Hi,
    Just thought I'd post this problem and solution in case others came across it.
    I installed WLS 6.1 and then the Service Pack 1 separately. The Service Pack
    1 install clears out registry.xml.
    I then tried to install WLI V2.1 and it would not let me install as it could not
    find WLS 6.1 SP1 the definition of which it gets from registry.xml. The error
    was WLS 6.1 SP1 not detected.
    To get around this I got sent a registry.xml and edited it to be my home machine.
    (Not the safest thing to do but it worked!).
    I think if you download WLS 6.1 and SP1 and install as one rather than separately
    this does not happen.
    Regards,
    Kathryn

    Oyvind,
    I believe using LDAPv2 with that release of Commerce Server is not supported.
    If you would like more information please contact BEA Support.
    Regards,
    Richard Wallace
    Senior Developer Relations Engineer
    BEA Support.
    "Oyvind" <[email protected]> wrote:
    >
    Hi,
    We have a problem with WLS 6.1 and LDAPRealm v2. Our application was
    working with
    WLS 6.0 and the LDAPRealm v2 patch. It is also working with 6.1 and LDAPRealm
    v1.
    When upgrading to WLS 6.1 we experience problems looking up user properties
    from
    LDAP. I put the same properties in the <CustomRealm> properties in config.xml
    as we had in the old ldaprealm.properties file.
    We are using WLCS 3.5 SP2, and we are looking up the user properties
    using the
    <um:getProperty> tag but it always returns null.
    Any idea what's wrong? This could be both a WLCS or a realm problem I
    guess?
    Below is the realm declaration in config.xml
    <CustomRealm
    ConfigurationData="user.dn=ou=People, o=my.com;server.principal=cn=Directory
    Manager;server.credential=adminadmin;user.filter=(&(cn=%u)(objectclass=person));group.dn=ou=Groups,
    o=my.com;group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=aaa.my.com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames))"
    Name="LDAPRealmV2" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
    Any input is appreciated,
    Oyvind

  • Sun Cluster with Netapps - iSCSI quorum and network port

    I am proposing Sun cluster with Netapps 3020C.
    May I know
    1) OS is Solaris 9. The SUN OSP says that we need to obtain an iSCSI license from Netapps. Is this the iSCSI initiator software for Solaris 9 to talk to the NAS quorum? Or do I need to purchased a 3rd party iSCSI initiator ?
    2) We provide 2 network ports for the Netapps private NAS LAN. Is it a must to cater another dedicated network port for the iSCSI communication with the quorum?
    3) If we need purchase a 3rd party iSCSI initiator, where can we get this? I have checked Qlogic and Cisco, they are both not suitable for my solution.
    Appreciate your help

    Hi,
    1) OS is Solaris 9. The SUN OSP says that we need to
    obtain an iSCSI license from Netapps. Is this the
    iSCSI initiator software for Solaris 9 to talk to the
    NAS quorum? Or do I need to purchased a 3rd party
    iSCSI initiator ?Have a look at http://docs.sun.com/app/docs/doc/817-7957/6mn8834r2?a=view
    I read the "Requirements When Configuring NAS Devices as Quorum Devices"
    section as this is the license for the iSCSI inititator software.
    So you need to enable iSCSI on the netapps box and need to install a package from netapps (NTAPclnas) on the cluster nodes.
    2) We provide 2 network ports for the Netapps
    private NAS LAN. Is it a must to cater another
    dedicated network port for the iSCSI communication
    with the quorum?Have a look at http://docs.sun.com/app/docs/doc/819-0580/6n30eahcc?a=view#ch4_quorum-9
    I don't read such a requirement there.
    3) If we need purchase a 3rd party iSCSI initiator,
    where can we get this? I have checked Qlogic and
    Cisco, they are both not suitable for my solution.
    Appreciate your helpI don't thibk you need such a 3rd party iSCSI initiator, unless this is stated in the above docs.
    Greets
    Thorsten

  • What is it with the application "mail" and the Yahoo mail servers that is in conflict all the time. We have reconfigured the settings and done everything possible and the "mail" application is still conflicted.... Running Lion 10.7.4

    I know it is a pretty long question and am unsure if it can be answered, but have had just a lot of trouble with the Yahoo mail servers... Where could a man go and get the mail application, I can not find it in the app store. It is my thought maybe to just replace the app I have with another mail application and reconfigure everything and go from there. But I do not know where the mail application can be found.

    See this blog posting for Yahoo mail set-up details for the Apple Mail.app tool.

  • WLS Cluster with Message Driven Beans and MQSeries on more than one Host

              With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
              a MDB can be
              configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
              is started at the same Host that runs the WLS Server too.
              And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
              In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
              Queuemanager.
              A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
              of this Queue.
              If one of the two WLS Servers fails the other WLS Server with the corresponding
              MDB should get the Messages of the
              MQSeries Queue.
              If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
              and the following Exception is thrown:
              <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
              mdb_deployed
              weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
              exception is:
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
              'btsun1a:TEST'
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
              at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
              I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
              the same Exception when the MDB is deployed.
              The configuration of JMSadmin on both Hosts is the following:
              dis qcf(myQCF2)
              HOSTNAME(btsun1a)
              CCSID(819)
              TRANSPORT(CLIENT)
              PORT(1414)
              TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
              QMANAGER(TEST)
              CHANNEL(JAVA.CHANNEL)
              VERSION(1)
              dis q(myQueue)
              CCSID(819)
              PERSISTENCE(APP)
              TARGCLIENT(JMS)
              QUEUE(MYQUEUE)
              EXPIRY(APP)
              QMANAGER(TEST)
              ENCODING(NATIVE)
              VERSION(1)
              PRIORITY(APP)
              I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
              and a QueueManager on each WLS Server.
              Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?
              

              With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
              a MDB can be
              configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
              is started at the same Host that runs the WLS Server too.
              And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
              In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
              Queuemanager.
              A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
              of this Queue.
              If one of the two WLS Servers fails the other WLS Server with the corresponding
              MDB should get the Messages of the
              MQSeries Queue.
              If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
              and the following Exception is thrown:
              <Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
              mdb_deployed
              weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
              exception is:
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
              'btsun1a:TEST'
              javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
              at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
              I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
              the same Exception when the MDB is deployed.
              The configuration of JMSadmin on both Hosts is the following:
              dis qcf(myQCF2)
              HOSTNAME(btsun1a)
              CCSID(819)
              TRANSPORT(CLIENT)
              PORT(1414)
              TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
              QMANAGER(TEST)
              CHANNEL(JAVA.CHANNEL)
              VERSION(1)
              dis q(myQueue)
              CCSID(819)
              PERSISTENCE(APP)
              TARGCLIENT(JMS)
              QUEUE(MYQUEUE)
              EXPIRY(APP)
              QMANAGER(TEST)
              ENCODING(NATIVE)
              VERSION(1)
              PRIORITY(APP)
              I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
              and a QueueManager on each WLS Server.
              Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?
              

  • Problems with mod_wl on linux and WLS 6.0

    Hi,
    we're trying to setup apache on linux so that it's forwarding all jsp
    requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
    modules according to the documentation. When apache starts it shows the
    following warning:
    [Tue Jan  9 13:22:55 2001] [warn] Loaded DSO
    /usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
    might crash under EAPI! (please recompile it with -DEAPI)
    and in fact, when we try to load a jsp page we get
    [Tue Jan  9 13:29:14 2001] [notice] child pid 5780 exit signal
    Segmentation fault (11)
    Does anyone have a working solution ? Can bea provide us with a plugin
    compiled with EAPI ?
    Greetings Olaf

    This is a dup message. Add "DebugConfigInfo OFF" in httpd.conf.
    Jong
    [email protected] (Olaf Foellinger) wrote:
    >
    Hi,
    we're trying to setup apache on linux so that it's forwarding all jsp
    requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
    modules according to the documentation. When apache starts it shows the
    following warning:
    [Tue Jan  9 13:22:55 2001] [warn] Loaded DSO
    /usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
    might crash under EAPI! (please recompile it with -DEAPI)
    and in fact, when we try to load a jsp page we get
    [Tue Jan  9 13:29:14 2001] [notice] child pid 5780 exit signal
    Segmentation fault (11)
    Does anyone have a working solution ? Can bea provide us with a plugin
    compiled with EAPI ?
    Greetings Olaf

  • 10g: HTTP Server and OC4J on different servers?

    Can anyone assist with configuring HTTP Server and OC4J on different servers?
    I installed AS 10g on both; our application runs fine on one server, with the HTTP Server and OC4J both on the same box.
    I need to also test this with the HTTP Server on a separate box.
    I added this to mod_ocj4.conf:
    Oc4jMount /indox-qa1
    instance://cvodev2:oas_dev2.cvodev2.int.sys.com:indox-qa1
    Oc4jMount /indox-qa1/*
    instance://cvodev2:oas_dev2.cvodev2.int.sys.com:indox-qa1
    But when I try to access something like http://cvodev4/indox-qa1 I get this in the logs:
    [Wed Jul 06 16:54:10 2005] [warn] [client 10.1.1.231] [ecid: 1120683250:192.152.136.127:1248:1544:1,0] MOD_OC4J_0184: Failed to find an oc4j process for destination: instance://cvodev2.int.camsys.com:oas_dev2.cvodev2.int.camsys.com:indor-qa1
    [Wed Jul 06 16:54:10 2005] [error] [client 10.1.1.231] [ecid: 1120683250:192.152.136.127:1248:1544:1,0] MOD_OC4J_0145: There is no oc4j process (for destination: instance://cvodev2.int.camsys.com:oas_dev2.cvodev2.int.camsys.com:indor-qa1) available to service request.
    [Wed Jul 06 16:54:10 2005] [error] [client 10.1.1.231] [ecid: 1120683250:192.152.136.127:1248:1544:1,0] MOD_OC4J_0119: Failed to get an oc4j process for destination: instance://cvodev2.int.camsys.com:oas_dev2.cvodev2.int.camsys.com:indor-qa1
    [Wed Jul 06 16:54:10 2005] [error] [client 10.1.1.231] [ecid: 1120683250:192.152.136.127:1248:1544:1,0] MOD_OC4J_0013: Failed to call destination: instance://cvodev2.int.camsys.com:oas_dev2.cvodev2.int.camsys.com:indor-qa1's service() to service the request.
    I did some ethernet sniffing and it doesn't look to me like the OHS box is even trying to contact the OC4J box.
    Is there more configuration I need to do beyond this?
    Thanks,
    dwh

    hi user11159690
    Maybe this can help:
    "Oracle® HTTP Server Administrator's Guide 10g Release 3 (10.1.3) B25211-02"
    "7.32 mod_oc4j"
    http://download.oracle.com/docs/cd/B25221_04/web.1013/b25211/confmods.htm#i1025739
    Maybe more specifically "Oc4jMount":
    http://download.oracle.com/docs/cd/B25221_04/web.1013/b25211/confmods.htm#CIHJBGFB
    (tip : You can use "Your Control Panel" to make your name visible in forum posts.)
    success
    Jan Vervecken

  • 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)

  • SSO with OID and WLS 8.1 Web App

    Hi,
    I have a web application deployed on WLS 8.1.
    I have set up Oracle Custom Authenticator.
    Some of my users are stored in Oracle LDAP. I want that if user logs in Web Application deployed on WLS 8.1 and clicks on one link (in my web app) which refers him to go to OID interface, in OID interface he should not be authenticated again (as he is already authenticated by WLS). Please let me know how to resolve this issue with Oracle SSO.
    Any help in this regard highly appreciated.
    Thanks
    -Deepak

    Did you find a solution for this problem?
    I have somthing very similar going on where I am currently working.
    Thanks!
    Andy.
    "Simple Guy" <[email protected]> wrote:
    >
    Hi,
    I've a setup with iplanet 6.x webserver using the wls 7.0 sp2 proxy plugin
    to
    route requests to the clustered app server instances (2 of them) that
    are in wls
    6.1 sp3.
    The issue is, I'm noticing that the session is not sticky and is getting
    routed
    onto the other app server instance. The error that I see in the wlproxy.log
    is
    as follows:
    *******Exception type [PROTOCOL_ERROR] raised
    at line 654 of URL.cpp
    Thu Nov 13 11:30:08 2003 failure on sendRequest() w/ recycled connection
    to Instance1:7001, numfailures=1
    Thu Nov 13 11:30:08 2003 Marking Instance1:7001 as bad
    Thu Nov 13 11:30:08 2003 got exception in sendRequest phase:
    PROTOCOL_ERROR [line 654 of URL.cpp]: unexpected EOF
    reading HTTP status at line 1010
    Thu Nov 13 11:30:08 2003 Failing over after sendRequest exception
    Thu Nov 13 11:30:08 2003 attempt #1 out of a max of 5
    Has anyone seen this issue? Can anyone explain why this issue is occuring.?
    Thanks.

  • Problems with WLS 7.0 and NES plug-in

    Hi,
    I am not able to configure NES with weblogic 7.0. I created a domain
    with an admin server and 3 clustered servers. When I tried to configure
    NES it is giving me these errors.
    [06/May/2002:18:41:26] failure ( 1530): Invalid configuration: File
    /data/iasuser2/webserver/https-ias02.mygazoo.com/config/server.x
    ml, line 32, column 15: Error processing obj.conf line 1: init functions
    are not allowed in this objset
    Also below are the lines copied from obj.conf that I added.
    Init fn="load-modules" funcs="wl_proxy,wl_init"\
    shlib=/data/iasuser2/webserver/https-ias02.mygazoo.com/libproxy.so
    Init fn="wl_init"
    <Object name="weblogic" ppath="*/weblogic/*">
    Service fn=wl_proxy \
    WebLogicCluster="localhost:7001,localhost:7002,\
    localhost:7003" PathTrim="/weblogic"
    </Object>
    Is NES plug-in supported with WLS 7.0. My version of iPlanet webserver
    is 6.0 and I am on Solaris 8.
    Shiva.

    Hi,
    I am not able to configure NES with weblogic 7.0. I created a domain
    with an admin server and 3 clustered servers. When I tried to configure
    NES it is giving me these errors.
    [06/May/2002:18:41:26] failure ( 1530): Invalid configuration: File
    /data/iasuser2/webserver/https-ias02.mygazoo.com/config/server.x
    ml, line 32, column 15: Error processing obj.conf line 1: init functions
    are not allowed in this objset
    Also below are the lines copied from obj.conf that I added.
    Init fn="load-modules" funcs="wl_proxy,wl_init"\
    shlib=/data/iasuser2/webserver/https-ias02.mygazoo.com/libproxy.so
    Init fn="wl_init"
    <Object name="weblogic" ppath="*/weblogic/*">
    Service fn=wl_proxy \
    WebLogicCluster="localhost:7001,localhost:7002,\
    localhost:7003" PathTrim="/weblogic"
    </Object>
    Is NES plug-in supported with WLS 7.0. My version of iPlanet webserver
    is 6.0 and I am on Solaris 8.
    Shiva.

  • Startup problems with XA connection pools on Oracle and WLS 6.1

    I am having starup problems trying to set up a WLS 6.1 connection pool using
    XA. When I try to start the server, I get the following exception:
    <Nov 19, 2001 3:06:28 PM EST> <Error> <JDBC> <Cannot startup connection pool
    "dbdev1XAPool" weblogic.common.ResourceException: java.sql.SQLException:
    open failed for XAResource 'dbdev1' with error XAER_RMERR : A resource
    manager error has occured in the transaction branch. Check Oracle XA trace
    file(s) (if any) for database errors. The Oracle XA trace file(s) are
    located at the directory where yo
    u start the Weblogic Server, and have names like
    xa_<pool_name><MMDDYYYY>.trc.
    at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
    at
    weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:600)
    at
    weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
    tionEnvFactory.java:194)
    at
    weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
    tionEnvFactory.java:54)
    at
    weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
    ava:698)
    at
    weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
    at
    weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:620
    at
    weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
    at
    weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
    arget.java:329)
    The contents of the Oracle trace file:
    ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
    150627.1312:344.344.330727191:
    xaoopen:
    xa_info=Oracle_XA+Acc=P/cmauser/admin+SesTm=100+DB=dbdev1+Threads=true+LogDi
    r=.+DbgFl=0x15,rmid=330727191,flags=0x0
    150627.1312:344.344.330727191:
    ORA-12560: TNS:protocol adapter error
    150627.1312:344.344.330727191:
    xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12560.
    150627.1312:344.344.330727191:
    xaoopen: return -3
    I am running WLS 6.1 and Oracle 8.1.7 on windows (separate machines). The
    connection pool settings are:
    <JDBCConnectionPool CapacityIncrement="0"
    DriverName="weblogic.jdbc.oci.xa.XADataSource" InitialCapacity="40"
    MaxCapacity="40" Name="dbdev1XAPool"
    Properties="user=cmauser;password=admin;dataSourceName=dbdev1"
    RefreshMinutes="15" ShrinkingEnabled="false" SupportsLocalTransaction="true"
    Targets="cmatest" TestTableName="hppcontentsource" />
    I have not had any problems connecting to the same database through regular
    JDBC connection pools or through the utils.dbping utility.
    What am I doing wrong?

    This is a dup message. Add "DebugConfigInfo OFF" in httpd.conf.
    Jong
    [email protected] (Olaf Foellinger) wrote:
    >
    Hi,
    we're trying to setup apache on linux so that it's forwarding all jsp
    requests to Bea WLS 6.0 on Solaris. We've installed the mod_wl.so
    modules according to the documentation. When apache starts it shows the
    following warning:
    [Tue Jan  9 13:22:55 2001] [warn] Loaded DSO
    /usr/lib/apache/1.3/mod_wl.so uses plain Apache 1.3 +API, this module
    might crash under EAPI! (please recompile it with -DEAPI)
    and in fact, when we try to load a jsp page we get
    [Tue Jan  9 13:29:14 2001] [notice] child pid 5780 exit signal
    Segmentation fault (11)
    Does anyone have a working solution ? Can bea provide us with a plugin
    compiled with EAPI ?
    Greetings Olaf

  • WebDev Install with JDeveloper and WLS

    I'm familiar with the installation of a JDE WebDev Client and now I've been tasked with a JDeveloper 11.1.1.2 and WLS install. Is there any good guides on how to set this up?
    EnterpriseOne 811
    Tools 8.98.3.1
    Any help would be greatly appreciated.
    Thank you,
    Al

    Hi Al,
    Try this:
    https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1302209.1
    This doc explains what components you need to have on a E1 Client that will be used to build and deploy BSSV Packages to a Bus Services Server. The Combination of JDeveloper and WLS probably indicates that you are intending to setup a Bus Services Server. However, this is only supported as of 811SP1.
    If you are running 811SP1, the process of setting up a Bus Services Server involves:
    - defining a BSSV instance via Server Manager
    - setting up a E1 Client with JDeveloper that will be used to build and deploy a Business Services Package
    The following doc has useful links to the MTRs for Bus Services Server as well as other useful resources on BSSV.
    https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=967281.1
    Edited by: user621397 on 15/04/2012 22:03
    Edited by: user621397 on 15/04/2012 22:04

  • Error message when access WLS: active sockets and socket readers configuration

    Hi,
    I got the following error when I tried to access the WLS using a program to get
    the mbeans data.
    This error happens when I have 3 or more servers running ( 1 admin server, 2 or
    more managed servers). With cluster with more than 2 servers running, this error
    also occurs.
    <Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are: '3' active
    sockets, but the maximum number of socket readers allowed by theconfiguration
    is: '2', you may want alter your configuration.>
    I creased the socket readers from 33% to 66%, but I still got the same error.
    I'm using WLS version 6.0 sp2
    My configuration is:
    Execute Threads = 15,
    Socket Readers = 33% or 66%
    Does anyone know how to fix this ? I am really appreciate for any suggestions.
    thanks,
    Kieu

    thank you, I just found out about setting those sockets using command line options
    an hour ago. But thanks a lot.
    -Kieu
    Kaye Wilcox <[email protected]> wrote:
    Kieu,
    You could try increasing the number of execute threads, you can do this
    via
    the admin console on the <server> --> Tuning tab.
    See http://edocs.bea.com/wls/docs60/perform/WLSTuning.html#1104317 for
    guidelines on setting the thread pool size and the number of socket readers.
    Here is a link that talks about socket communication in a cluster
    http://edocs.bea.com/wls/docs60/cluster/features.html#1007001.

  • Cluster with shared domain folder using OCFS2 and the domain /tmp folder

    I've setup a cluster with two machines and one managed server on each machine. One of the machines also hosts the admin server.
    Initially, both managed servers were running on the same machine. Everything worked well. When I move to having two machines, I didn't want to have to independently maintain the domain folder on each machine.
    So I decided to setup a shared drive between the machines and use OCFS2 to share the domain folder between the two machines.
    Everything started up fine, but when I deployed software to the server I would frequently (but not always) get this error:
    [wldeploy] Target state: deploy failed on Cluster cluster-01
    [wldeploy] weblogic.management.DeploymentException: [Deployer:149189]Attempt to operate 'deploy' on null BasicDeploymentMBean for deployment mylibrary#[email protected]. Operation can not be performed until server is restarted.
    After looking around a bit on google I saw this issue:
    http://download.oracle.com/docs/cd/E11035_01/wls100/issues/known_resolved.html#CR279281
    which says
    Some OS and NFS combinations result in deployment failures or configuration updates with an exception like:
    weblogic.management.DeploymentException: Attempt to operate 'distribute' on null BasicDeploymentMBean
    Workaround or Solution:
    * Run statd() and lockd() processes on every NFS client that accesses a remote NFS volume.
    * If multiple servers that share the same domain root are started with different user Ids of same group, set the correct "umask" for the server processes so that a file created by one server can be opened for read/write by other servers without security exceptions.
    Unfortunately, I wasn't running NFS, so the workaround didn't help me.
    Through dump luck, I tried this:
    I replaced the domainroot/tmp folder with a symbolic link to a folder on each machine's local filesystem. Following that change my deployments work everytime.
    Does anyone know why this change worked? What is the purpose of the /tmp folder in a domain folder?
    Are there any switches I could turn on to get more information about the exact error that causes the deployment mbean to come back null?

    It may not be the same situation, but I had this "deployer:149189" error and it turned out to be mixing WLS 10.0 and 10.3 installations together in the same install directory and not being scrupulous about environment setup. I think the problem was caused by accidentally running a 10.0 domain with Java 1.6.
    Eoin.

Maybe you are looking for