Losing session with WLS 7.02 in cluster env

          PROBLEM: We are losing our session when running in our app in a clustered environment.
          The user can use the app for a while, but then weird stuff starts happening. In
          some cases, the login check that we do at the begining of each request fails,
          because it tries to check for a login token in the session, and the session has
          been wiped out. The user gets forwarded to the login page.
          Our configuration is:
          WLS 7.0.2 (OS = Windows 2000)
          Admin Server and a managed server A at APP1 (physical machine), another managed
          server B
          at APP2 (physical machine), A and B is in one cluster. We had 6 Apache Servers
          2.0.45 (OS = Linux) and each works together with Weblogic Plugin. The weblogic
          plugin has the following configuration:
          <Location /sample>
          SetHandler weblogic-handler
          WeblogicCluster 10.1.1.11:7010,10.1.1.12:7010
          Idempotent ON
          CookieName JSESSIONID
          </Location>
          The server A and B use round-robin loadblancing, and we have a hardware loadblancer
          infront of Apache to do loadblancing for our 6 web servers.
          In weblogic.xml we config our application to use replicated for session failover.
          Losing session is randomly happened.
          Anyone of you have any idea?
          Thanks in advance.
          Harry
          

To verify that it is WL and not your app logic, try using a different
          session replication implementation for testing, such as the one that comes
          with Coherence for Servlet 2.3 containers:
          http://www.tangosol.com/coherence.jsp
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Harry Yu" <[email protected]> wrote in message
          news:[email protected]...
          >
          > PROBLEM: We are losing our session when running in our app in a clustered
          environment.
          > The user can use the app for a while, but then weird stuff starts
          happening. In
          > some cases, the login check that we do at the begining of each request
          fails,
          > because it tries to check for a login token in the session, and the
          session has
          > been wiped out. The user gets forwarded to the login page.
          >
          > Our configuration is:
          > WLS 7.0.2 (OS = Windows 2000)
          > Admin Server and a managed server A at APP1 (physical machine), another
          managed
          > server B
          > at APP2 (physical machine), A and B is in one cluster. We had 6 Apache
          Servers
          > 2.0.45 (OS = Linux) and each works together with Weblogic Plugin. The
          weblogic
          > plugin has the following configuration:
          > <Location /sample>
          > SetHandler weblogic-handler
          > WeblogicCluster 10.1.1.11:7010,10.1.1.12:7010
          > Idempotent ON
          > CookieName JSESSIONID
          > </Location>
          >
          > The server A and B use round-robin loadblancing, and we have a hardware
          loadblancer
          > infront of Apache to do loadblancing for our 6 web servers.
          >
          > In weblogic.xml we config our application to use replicated for session
          failover.
          >
          > Losing session is randomly happened.
          >
          > Anyone of you have any idea?
          >
          > Thanks in advance.
          >
          > Harry
          >
          

Similar Messages

  • Losing Session for Weblogic 7.0.2 in Cluster env

              PROBLEM: We are losing our session when running in our app in a clustered environment.
              The user can use the app for a while, but then weird stuff starts happening. In
              some cases, the login check that we do at the begining of each request fails,
              because it tries to check for a login token in the session, and the session has
              been wiped out. The user gets forwarded to the login page.
              Our configuration is: WLS 7.0.2 (OS = Windows 2000) Admin Server and a managed
              server A at APP1 (physical machine), another managed server B at APP2 (physical
              machine), A and B is in one cluster. We had 6 Apache Servers 2.0.45 (OS = Linux)
              and each works together with Weblogic Plugin. The weblogic plugin has the following
              configuration: <Location /sample> SetHandler weblogic-handler WeblogicCluster
              10.1.1.11:7010,10.1.1.12:7010 Idempotent ON CookieName JSESSIONID </Location>
              The server A and B use round-robin loadblancing, and we have a hardware loadblancer
              infront of Apache to do loadblancing for our 6 web servers.
              In weblogic.xml we config our application to use replicated for session failover.
              Losing session is randomly happened.
              Anyone of you have any idea?
              Thanks in advance.
              Harry
              

    The advice on version numbers given above is quite generic. While JDK 1.4 may work, if you want to run a supported configuration the answer to this question depends on what OS you're running. Further, BEA supports different JDK versions for running the server and for client applications. Here is the whole chart:
    http://e-docs.bea.com/platform/suppconfigs/configs70/70_over/overview.html
    Be sure to click on your operating system to get the specific information about what JDK is "fully-supported" and what is "client-only".
    Hope that helps,
    Justin

  • Deployig to a Cluster without losing session.

    Hi,
              We have a cluster setup with 4 servers. We use HttpSession and
              StatefulSessionBeans in the cluster with in-memory replication. Is it
              possible to redeploy the application to a cluster without losing
              session ?.
              Thanks,
              -Senthil.
              

    We have a cluster setup with 4 servers. We use HttpSession and          > StatefulSessionBeans in the cluster with in-memory replication. Is it
              > possible to redeploy the application to a cluster without losing
              > session ?.
              Not with WebLogic session replication. The session replication is "lazy"
              (only when something happens) so the best approach is to make sure there are
              no imcompatibilities and then cycle the cluster one server at a time, maybe
              one server every hour (or whatever your session timeout is).
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "Senthil" <[email protected]> wrote in message
              news:[email protected]..
              > Hi,
              >
              >
              > Thanks,
              > -Senthil.
              

  • 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

  • Java 1.5 client with WLS 8.1 MBeans...

    Hi,
              I maintain http://www.hermesjms.com and am investigating a problem with Hermes, which uses a 1.5 VM, interrogating WLS MBeans with WLS on 1.4.
              This thread describes what users have seen and what I have also replicated:
              http://www.hermesjms.com/forum/viewtopic.php?t=126
              As you can see, setting -Djmx.serial.form=1.0 fixes the serialisation problem but I now get the InstanceNotFoundException.
              I invoke getMBean() from the getStatistics() method here:
              http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/weblogic/WebLogicJMSAdmin.java?view=markup
              Any kind soul out there know what the problem may be? I'm kinda confused...
              Many thanks,
              Colin.

    Hi Tom,
              When I upgrade to 9.0 client against 8.1 server I get the exceptions at the end of this mail. The server I am talking to is a single server, not in a cluster, and is just the out-of-the-box WLS 8.1 with a JMS server and some queues and topics configured.
              I don't get the ClassNotFoundException for WebLogicObjectName as this exists in weblogic.jar. Is there anything I need to do to WLS 8.1 to allow a 9.0 client to interop?
              Cheers,
              Colin.
              2005-08-04 08:25:41,753 [Timer-7] DEBUG hermes.ext.weblogic.WebLogicJMSAdmin - Constructed JMSDestination MBean name: mydomain:JMSServerRuntime=MyJMS Server,Location=myserver,Name=MyDistributed Queue,ServerRuntime=myserver,Type=JMSDestinationRuntime
              2005-08-04 08:25:41,773 [Timer-7] ERROR hermes.HermesWatchManager - Unexpected Exception
              weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
                   at weblogic.management.internal.MBeanHomeImpl_814_WLStub.getMBean(Unknown Source)
                   at hermes.ext.weblogic.WebLogicJMSAdmin.getMBean(WebLogicJMSAdmin.java:329)
                   at hermes.ext.weblogic.WebLogicJMSAdmin.getStatistics(WebLogicJMSAdmin.java:155)
                   at hermes.ext.weblogic.WebLogicJMSAdmin.getDepth(WebLogicJMSAdmin.java:119)
                   at hermes.impl.HermesAdminAdapter.getDepth(HermesAdminAdapter.java:108)
                   at hermes.impl.DefaultHermesImpl.getDepth(DefaultHermesImpl.java:1187)
                   at hermes.HermesWatchManager.updateWatchStatistics(HermesWatchManager.java:202)
                   at hermes.HermesWatchManager.doUpdate(HermesWatchManager.java:170)
                   at hermes.HermesWatchManager.access$000(HermesWatchManager.java:38)
                   at hermes.HermesWatchManager$2.run(HermesWatchManager.java:84)
                   at java.util.TimerThread.mainLoop(Timer.java:512)
                   at java.util.TimerThread.run(Timer.java:462)
              Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
                   java.lang.ClassNotFoundException: weblogic.management.interop.WebLogicObjectName: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
                   at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
                   at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:155)
                   ... 12 more
              Caused by: java.lang.ClassNotFoundException: weblogic.management.interop.WebLogicObjectName: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
                   at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:344)
                   at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:258)
                   at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:253)
                   at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(MsgAbbrevInputStream.java:327)
                   at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectInputStream.java:316)
                   at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
                   at java.io.ObjectInputStream.readClassDesc(Unknown Source)
                   at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
                   at java.io.ObjectInputStream.readObject0(Unknown Source)
                   at java.io.ObjectInputStream.readObject(Unknown Source)
                   at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:120)
                   at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:120)
                   at weblogic.management.internal.MBeanHomeImpl_WLSkel.invoke(Unknown Source)
                   at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
                   at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
                   at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
                   at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
                   at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
                   at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
                   at java.lang.Thread.startThreadFromVM(Unknown Source)
              2005-08-04 08:25:41,773 [Timer-7] DEBUG hermes.HermesWatchManager - closing Hermes WebLogic
              2005-08-04 08:25:41,783 [Timer-7] DEBUG hermes.impl.jms.ThreadLocalSessionManager - all sessions closed, closing Connection

  • LIBOVD ERROR  - "validateContextToken: workflow session was not found for given context. Create a new workflow session with token"

    Hello everyone,
    I have the following scenario:
    We're using "Oracle SOA Suite 11g 11.1.1.7.0" (Patched w/ 17893896) mainly for a BPM/Human workflow composite. Former, we were having the error bellow:
    <Mar 16, 2015 1:13:03 PM BRT> <Error> <oracle.soa.services.workflow.query> <BEA-000000> <<.> Verification Service cannot resolve user identity. User weblogic cannot be found in the identity repository. Workflow Context token cannot be null in request.
    ORABPEL-30511
    When that error ocurred, no one was able to use the system (BPM/Human Workflow).
    I opened an SR, and after some analysis from the support, it recommended me to set up "virtualize=true" in EM, and restarting the domain. Then it started logging the following:
    connection to ldap://[10.200.10.57]:7001 as cn=Admin.
    javax.naming.NamingException: No LDAP connection available to process request for DN: cn=Admin.
    Looking up on support KB, I found this note Doc ID 1545680.1 and increased from Max size of Connection Pool 10 to 200. That did work successfully! Problem now is that the <SERVER>_diagnostic.log is being filled up with the following error:
    [2015-03-31T16:03:46.421-03:00] [soa_server2] [ERROR] [] [oracle.soa.services.workflow.verification] [tid: [ACTIVE].ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: e0194e38aa6c9a2f:39fc1ff9:14c5def5247:-8000-00000000000a5653,0] [APP: soa-infra] <.>    validateContextToken: workflow session was not found for given context. Create a new workflow session with token=51490173-e3d0-41dd-ae99-983915aa8454;;G;;Z+P7Oe9ABnoTUQD9ECryEW2l0/8yRcqPDyZsOWBCuzMmRgA3Qsj601TxmWQ87z2MjuwW5AH+KzgjIwkPmhJFdpc1FrE6Y/MrN1bxIDHJWu2/zP3iSNwKD07hRrh/U37Ea0TvaQyuaHJIog9y3Ptmzw==
    One important point is that we're using only the embedded WLS ldap. So I am not 100% sure if we should be using the virtualize flag=true, once all docs I read point out that this should be done when using multi-ldap providers.
    Also, I only got this error in the "diagnostic.log".
    Although, no user has complained about using the system, I really want to work it out. Anyone has any suggestions?
    Thanks in advance!

    I have moved your thread from Certification to SOA Suite to get proper assistance.
    Thanks,
    Lisa

  • Using Connection Pooling in a WLS 5.1.x - Cluster

    Hi,
              We have problems using connection pooling in a WLS 5.1.x - Cluster. Is it
              possible to use CP in such a cluster at all ? The problem is, connections
              will be opened and never been closed. How can I configure a cluster for CP?
              I have a WLS-Cluster with 2 instances and my webApp uses connection pooling.
              By the way I get a connection on Instance 1, Instance 2 gets a connection
              also, but never releases it.
              In my opinion, the reference to the connection in the partner-instance will
              be lost.
              How do I have to configure my cluster to work well with that stuff ?
              Thank a lot,
              Markus.
              

    Clustering with connection pools works fine in WLS 5.1. If connections are
              not being release, you have bugs in your code.
              When a connection is retrieved from a pool on one instance, a corresponding
              connection is NOT retrieved on another instance.
              Mike
              "M. Hammer" <[email protected]> wrote in message
              news:[email protected]..
              > Hi,
              >
              > We have problems using connection pooling in a WLS 5.1.x - Cluster. Is it
              > possible to use CP in such a cluster at all ? The problem is, connections
              > will be opened and never been closed. How can I configure a cluster for
              CP?
              >
              > I have a WLS-Cluster with 2 instances and my webApp uses connection
              pooling.
              > By the way I get a connection on Instance 1, Instance 2 gets a connection
              > also, but never releases it.
              > In my opinion, the reference to the connection in the partner-instance
              will
              > be lost.
              > How do I have to configure my cluster to work well with that stuff ?
              >
              > Thank a lot,
              >
              > Markus.
              >
              >
              >
              

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

  • General install and deployment problem with WLS clustering on two boxes

    Hi,
    I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
    The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
    So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
    Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
    One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
    Any help appriecated.
    Surfbum.

    Hi I think I've found the answer. You can build a managed server template using the pack command.
    http://e-docs.bea.com/common/docs90/pack/tasks.html

  • IE5 and Netscape with WLS 5.1

    Hi,
    I sent this out a couple of weeks ago. I have tried the solution but with no success could some one please help...
    We are using Weblogic 5.1 Service Pack 8 on Solaris 2.6, with Apache server acting as a bridge. Apache actually does not serve any content and just forwards ALL requests to WLS. We have a problem at the moment that if you use internet explorer with WLS then it is extremely slow serving up pages. Weblogic listens on port 7001. If we use Netscape to connect then it runs with no slow downs at all, about three second to serve a page but if we use IE it takes nearly a minute. This delay occurs when the request goes through apache. If we directly access WLS on port 7001 then there is no such delay.
    Any ideas on what could cause that delay? Is it an Apache bridge problem or a WLS one?
    Cheers,
    Barnaby
    [att1.html]

    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

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

  • Avoid http sessions with XML request

    Hello,
    We are sending quick complete messages (and other XMLs like resource status change,...) to SAP ME. We see on Wily that it always create sessions and as we are starting more and more machines we are always reaching the sessions limits --> we currently increased it to 3000. With MII webservices, we know that we can avoid to create a session with parameter "session=false" but we don't know if something like this can be done with ME xml message.
    Any idea ?
    Regards,
    Michaël.

    Hi Michaël,
    Session control is done by Netweawer and I'm not aware of a way/setting to make Netweaver not create http/security sessions for requests. What I think could work in your scenario is setting low timeout value for web application responsible for ME web services handling. I'm not sure if suggested re-configuration is valid from WAR archive consistency point of view, but I believe it could be tried in a test system:
    1. Find WAR archive in the following path - drive:\usr\sap\[SID]\[InstanceNo]\j2ee\cluster\apps\sap.com\me~ear\servlet_jsp\manufacturing-services\me.webservices.web-5.2.x.x-Base.war   OR ..\servlet_jsp\manufacturing-xml\me.integration.xml.web-5.2.x.x-Base.war
    2. Open it and edit WEB-INF\web.xml file. Change session-timeout property to 1.
    3. Save the file in the open archive.
    4. Restart engine.
    If such change is catched up by j2ee engine, all sessions for the web app should be invalidated and purged after 1 minute. Off course the same procedure has to be followed each time application is redeployed/upgraded to a newer version as this will deploy default WAR archive with default 60 min timeout config.
    Regards,
    Konstantin

  • How to use Muticast testing utilities with WLS ??

    Hello,
              Does anyone here know how we can use the muticast testing utilities that are
              avilable with WLS ??
              I have run it, but I don't understand how to use it...
              What will it show ??
              WIll it show that there is a conflict in the muticast address ??
              Will it show something else ??
              Whenever I run it.... it just writes a bunch of messages ot the screen.
              What does that mean ??
              Is there any documentation available on this utlity ??
              Please help.
              -Anu
              

    see below
              If your multicast is properly setup each server reports that a new
              neighbor is found and it's able to accept messages from the other server.
              java utils.MulticastTest -N S1 -A 224.0.0.1
              ***** WARNING ***** WARNING ***** WARNING *****
              Do NOT use the same multicast address as a running WLS cluster.
              Starting test. Hit any key to abort
              Using multicast address 224.0.0.1:7001
              Will send messages under the name S1 every 2 seconds
              Will print warning every 600 seconds if no messages are received
              New Neighbor s2 found on message number 2
              Duplicate message from s2: 2
              Duplicate message from s2: 2
              Duplicate message from s2: 2
              Duplicate message from s2: 2
              Duplicate message from S1: 1
              Duplicate message from S1: 1
              Duplicate message from S1: 1
              Duplicate message from S1: 1
              I (S1) sent message num 1
              Received message 3 from s2
              Duplicate message from s2: 3
              Duplicate message from s2: 3
              Duplicate message from s2: 3
              Duplicate message from s2: 3
              Received message 2 from S1
              java utils.MulticastTest -N S2 -A 224.0.0.1
              ***** WARNING ***** WARNING ***** WARNING *****
              Do NOT use the same multicast address as a running WLS cluster.
              Starting test. Hit any key to abort
              Using multicast address 224.0.0.1:7001
              Will send messages under the name s2 every 2 seconds
              Will print warning every 600 seconds if no messages are received
              Duplicate message from s2: 1
              Duplicate message from s2: 1
              Duplicate message from s2: 1
              Duplicate message from s2: 1
              I (s2) sent message num 1
              Received message 2 from s2
              Duplicate message from s2: 2
              Duplicate message from s2: 2
              Duplicate message from s2: 2
              Duplicate message from s2: 2
              I (s2) sent message num 2
              New Neighbor S1 found on message number 1
              Duplicate message from S1: 1
              Duplicate message from S1: 1
              Duplicate message from S1: 1
              Duplicate message from S1: 1
              Received message 3 from s2
              Duplicate message from s2: 3
              Duplicate message from s2: 3
              Duplicate message from s2: 3
              Duplicate message from s2: 3
              I (s2) sent message num 3
              Received message 2 from S1
              Duplicate message from S1: 2
              Duplicate message from S1: 2
              Duplicate message from S1: 2
              Duplicate message from S1: 2
              Received message 4 from s2
              Duplicate message from s2: 4
              Duplicate message from s2: 4
              Duplicate message from s2: 4
              Duplicate message from s2: 4
              I (s2) sent message num 4
              Anu Kulatunga wrote:
              > Hello,
              >
              > Does anyone here know how we can use the muticast testing utilities that are
              > avilable with WLS ??
              >
              > I have run it, but I don't understand how to use it...
              >
              > What will it show ??
              >
              > WIll it show that there is a conflict in the muticast address ??
              >
              > Will it show something else ??
              >
              > Whenever I run it.... it just writes a bunch of messages ot the screen.
              >
              > What does that mean ??
              >
              > Is there any documentation available on this utlity ??
              >
              > Please help.
              > -Anu
              >
              >
              >
              >
              >
              

  • Help  - SPENGO - Microsoft SSO with WLS 9.2

    Friends,
    I am trying to integrate Microsoft SSO with WLS with SPENGO. I followed the steps given in http://edocs.bea.com/wls/docs92/secmanage/sso.html and even in 8.x documentation where I had to create a LDAP authenticator etc.
    However, instead of SPENGO token, I get the NTLM token. It looks like when Kerberos fails, WLS tries to invoke NTLM. But I am not sure where I am doing wrong. It would be great if someone could look at the following logs and suggest some workaround.
    <<WLS Kernel>> <> <> <1183957002830> <000000> <NegotiateIdentityAsserterServletAuthenticationFilter.doFilter() called>
    <<WLS Kernel>> <> <> <1183957002830> <000000> <CERT auth type found for webapp>
    <<WLS Kernel>> <> <> <1183957002830> <000000> <All request headers:>
    <<WLS Kernel>> <> <> <1183957002830> <000000> < Header: Accept : image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*>
    <<WLS Kernel>> <> <> <1183957002830> <000000> < Header: Accept-Language : en-us>
    <<WLS Kernel>> <> <> <1183957002830> <000000> < Header: UA-CPU : x86>
    <<WLS Kernel>> <> <> <1183957002830> <000000> < Header: Accept-Encoding : gzip, deflate>
    <<WLS Kernel>> <> <> <1183957002830> <000000> < Header: User-Agent : Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322)>
    <<WLS Kernel>> <> <> <1183957002830> <000000> < Header: Host : 10.31.252.182:7001>
    <<WLS Kernel>> <> <> <1183957002830> <000000> < Header: Connection : Keep-Alive>
    <<WLS Kernel>> <> <> <1183957002862> <000000> <Negotiate filter: new session, no negotiation has started>
    <<WLS Kernel>> <> <> <1183957002862> <000000> <PrincipalAuthenticator.getChallengeToken will use common security service>
    <<WLS Kernel>> <> <> <1183957002862> <000000> <com.bea.common.security.internal.service.ChallengeIdentityAssertionServiceImpl.getChallengeToken(WWW-Authenticate.Negotiate)>
    <<WLS Kernel>> <> <> <1183957002862> <000000> <com.bea.common.security.internal.service.ChallengeIdentityAssertionTokenServiceImpl.getChallengeToken(WWW-Authenticate.Negotiate)>
    <<WLS Kernel>> <> <> <1183957002862> <000000> <com.bea.common.security.internal.legacy.service.ChallengeIdentityAssertionProviderImpl$ChallengeIdentityAsserterV2Adapter.getChallengeToken(WWW-Authenticate.Negotiate)>
    <<WLS Kernel>> <> <> <1183957002862> <000000> <Unauthorized, sending WWW-Authenticate: Negotiate>
    <<WLS Kernel>> <> <> <1183957003268> <000000> <NegotiateIdentityAsserterServletAuthenticationFilter.doFilter() called>
    <<WLS Kernel>> <> <> <1183957003268> <000000> <CERT auth type found for webapp>
    <<WLS Kernel>> <> <> <1183957003268> <000000> <All request headers:>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: Accept : image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: Accept-Language : en-us>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: UA-CPU : x86>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: Accept-Encoding : gzip, deflate>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: User-Agent : Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322)>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: Host : 10.31.252.182:7001>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: Connection : Keep-Alive>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: Cookie : JSESSIONID=0nRcGRQKvcpzV8wQPVX584Pxwly4GrpTdQGGGYGGb4Z62Rs1GLVv!542382297>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < Header: Authorization : Negotiate TlRMTVNTUAABAAAAB7IIogoACgAvAAAABwAHACgAAAAFAs4OAAAAD0RFU0tUT1BGRURFUkFUSU9O>
    <<WLS Kernel>> <> <> <1183957003268> <000000> < processing header: Negotiate TlRMTVNTUAABAAAAB7IIogoACgAvAAAABwAHACgAAAAFAs4OAAAAD0RFU0tUT1BGRURFUkFUSU9O>
    <<WLS Kernel>> <> <> <1183957003283> <000000> <SPNEGONegotiateToken.discriminate: not Application Constructed Object, not SPNEGO NegTokenInit token>
    <<WLS Kernel>> <> <> <1183957003283> <000000> <Token not supported by Negotiate Filter, ignoring: NTLM>

    Another question.
    When you configure Spnego and sso, do you also need to configure an active directory authenticator ??
    I think I have the SSO part working - it does kerberos authentication and gets the username, howerver after taht it fails because it tries to do an LDAP authentication with that username.
    <LDAP Atn Login username: kerbuser01>
    <[Security:090300]Identity Assertion Failed: User kerbuser01 does not exist
    Any pointers ?

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

Maybe you are looking for

  • An Internal Error Occured - Adobe Acrobat Professional 10.0.0.396

    Hi All, We are facing an issue in Acrobat 10.0.0.396 version, While working on the adobe file its suddenly get closed with the following error pop up " an internal error occured ", we dont get any event logs errors in the system and no error code in

  • Kindly help reg - LSMW using BAPI

    Hi All,   I am using LSMW using BAPI method to upload data to create an Purchase order. I m getting this error. " Identification specifications missing for source structure 'PSOURCE_HEAD' ". Here are the steps I have followed. 1. Created an IDOC Inbo

  • Batch input messages

    hi experts how can i find out what is the meaning of the message numbers in batch input operation, and what is the meaning of the message type. thanks amit

  • Grouping two sections in one report

    Hello, I am newbie to Crystal Reports.I have one doubt in designing a report. The proto for the report is: Date: XX:XX:XXXX                                 Sales Report - Value S No     Item         Increase    Decrease 1           XXX 2           YY

  • OSPF design

    Hi Guys, I'm currently researching the possibility of the implementation of OSPF in our core network. First, let me share a topology.  It basically concerns traffic from the subnets connected to firewall cluster 1 that is going to firewall cluster 2.