Cluster enviornment i get session failover exception

Hi All,
In cluster enviornment i get session failover exception comes when one of my node is down .
How can i inform all manage server at the time of creation of session object in cluster enviornment.
Thanks in advance,
Sumit Bhasin

.

Similar Messages

  • AM without session failover set up?

    Generally I have at least 2 servers for redundancy and plan 2 servers to host AM behind a load balancer. Unfortunately I am unable to support message queue and berkeley sleepycat DB which is required for session failover. So I am curious what the session behavior is without the session failover set up. When one AM server goes down and the other is used does the user click on a link and is asked to login again? Wondering how graceful it is.

    Hi.
    I have been kind of struggling with session failover for sometime now (it worked perfectly with 2003Q4 though).
    Once you have a session queue / DB established, this is how things proceed:
    1. User hits load balancer, which directs him / her to one of the servers.
    2. User logs in. Load balancer maintains a sticky session. Future requests go to the same server.
    3. Say that server goes down. User clicks. Load balancer figures out that server is down, redirects user to another AM server.
    4. If you have session failover in place, user can continue to work without logging in (technically!).
    It was seamless with 2003Q4. We pulled the cable on one AM server (so resulting DS, DPS, AM and message broker all went offline), and still the user's session transitioned to the other server.
    If you do get session failover to work with 2005Q4, would be grateful if you could post something about it.

  • Session-failover-enabled not working in iWS6 with a FileStore

    I'm trying to use a FileStore to implement session persistence using IWSSessionManager. I have the following in my web-apps.xml:
    <web-app uri="/Banking" dir="c:/java/online">
    <session-manager class='com.iplanet.server.http.session.IWSSessionManager'>
    <init-param>
    <param-name>session-data-store</param-name>
    <param-value>com.iplanet.server.http.session.FileStore</param-value>
    </init-param>
    <init-param>
    <param-name>session-data-dir</param-name>
    <param-value>c:/iplanet/servers/SessionData</param-value>
    </init-param>
    <init-param>
    <param-name>session-failover-enabled</param-name>
    <param-value>false</param-value>
    </init-param>
    </session-manager>
    </web-app>
    I'm seeing the following exception in my log:
    [12/Jun/2002:10:10:56] info ( 320): java.io.NotSerializableException: com.iplanet.server.http.servlet.WebApplication
    at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
    at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
    at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
    at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
    at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827)
    at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
    at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
    at java.util.Hashtable.writeObject(Hashtable.java:764)
    at java.lang.reflect.Method.invoke(Native Method)
    at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
    at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
    at com.iplanet.server.http.session.IWSHttpSession.writeObject(IWSHttpSession.java:764)
    at java.lang.reflect.Method.invoke(Native Method)
    at java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864)
    at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
    at com.iplanet.server.http.session.FileStore.save(FileStore.java:167)
    at com.iplanet.server.http.session.IWSSessionManager.update(IWSSessionManager.java:499)
    at com.iplanet.server.http.servlet.NSHttpServletRequest.closeInputStream (NSHttpServletRequest.java:612)
    at com.iplanet.server.http.servlet.NSServletRunner.servicePostProcess(NSServletRunner.java:857)
    at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:942)
    at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1065)
    at com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:959)
    Any ideas what's wrong?
    I should note that I don't think it is because I am storing non-serializable things in the session attributes. I think this because originally I was getting an exception that said that a specific attribute wasn't serializable. I changed the class definition of the class I was storing in that attribute to include "implements java.io.Serializable" and that problem went away.

    Hi Sija,
    Can i have detailed scenario in your cluster configuration.
    Means you are saying that going to start cluster package manually, if it is right please make sure that you had the same copy of start, instance profiles of NodeA to Node B. Means you need to maintain two startup, two instance profiles for both nodes. In a normal situation it will picik the profile of node A to start databse from A node. But in a failover situation it will not pick node A profile to start, it should pick Node B s profiles.
    Just make a copy from node A and change the profile name accordingly to Node b. Then try to restart.
    Regards
    Nick Loy

  • Access Manager 7.1 Session Failover

    Hello,
    I am trying to do a session failover with access Manager 7.1.
    My Infrastructure:
    OS: Solaris 10
    2 Solaris Servers dedicated to 4 LDAP instances (2 each)
    2 Solaris Servers dedicated to 2 LDAP Proxy servers configured to access 4 LDAP instances.
    2 Solaris Servers dedicated to 2 Sun Application Server 8.2 running 2 instances of Access Manager sharing the 4 LDAP instances through Proxy.
    2 Solaris Servers dedicated to 2 instances of JMS servers (1 on each) with Access Manager Session DB configured. JMS is running on cluster mode.
    1 Solaris server for Webserver 7.0 configured for Load Balancing (loadbalancer.xml).
    Configuration:
    2 instances of Access Manager on separate solaris boxes use the same LDAP instance(s).
    Access Manager is configured for session failover using amsfoconfig as documented.
    The Session failover instances where started as documented
    1.     Start session DB using amsfo script
    2.     Start the Access Manager instances (by Starting DAS)
    3.     Start Webserver
    My Problem:
    Session Failover does not work. The Amsession log throws
    ERROR: JMQSessionRepository.save(): failed to save Session
    java.lang.NullPointerException
    at com.iplanet.dpro.session.jmqdb.PersistSession.setString(PersistSession.java:310)
    at com.iplanet.dpro.session.jmqdb.JMQSessionRepository.save(JMQSessionRepository.java:357)
    at com.iplanet.dpro.session.service.SessionService.saveForFailover(SessionService.java:2812)
    AmSessionMonitor file continuously throws below error and fills up the disk (20 GB ) space quickly:
    04/24/2007 04:28:13:450 PM EDT: Thread[amSessionMonitor,5,main]
    WARNING: SessionMonitor runtime exception
    java.lang.NullPointerException
    at com.iplanet.dpro.session.service.SessionService.locateCurrentHostServer(SessionService.java:1762)
    at com.iplanet.dpro.session.service.SessionService.getCurrentHostServer(SessionService.java:1731)
    at com.iplanet.dpro.session.service.SessionMonitor.run(SessionMonitor.java:94)
    JMS queue Log:
    Sun Java(tm) System Message Queue 3.7
    Sun Microsystems, Inc.
    Version: 3.7 UR1 (Build 9-b)
    Compile: Sun Jun 18 22:11:21 PDT 2006
    Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
    SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================
    Java Runtime: 1.5.0_09 Sun Microsystems Inc. /usr/jdk/instances/jdk1.5.0/jre
    [18/Apr/2007:09:14:28 EDT] License: Sun Java(tm) System Message Queue 3.7 UR1 Enterprise Edition
    [18/Apr/2007:09:14:29 EDT] IMQ_HOME=/
    "log.txt" 725 lines, 61600 characters
    Magic/Version: 469754818/301 Size: 116 Type: ACKNOWLEDGE(24)
    Expiration: 0 Timestamp: 1177446120954
    Source IP: 172.31.120.44(c0:ca:66:ec:a9:d5) Port: 60437 Sequence: 32
    Property Offset: 76 Property Size: 0
    Encryption: 0 Priority: 5
    Flags: consumerID: 0
    TransactionID: 0
    MessageID: 32-172.31.120.44(c0:ca:66:ec:a9:d5)-60437-1177446120954
    Properties: null
    Message Body: 40 bytes [3052053123717449216:16-172.31.120.44(b1:6a:3:39:7d:6)-60434-1177446116385]
    Internal Buffers (useDirect=false):
    Fixed Header Buffer:java.nio.HeapByteBuffer[pos=0 lim=72 cap=72]
    com.sun.messaging.jmq.jmsserver.util.BrokerException: Internal Error: Unable to complete processing acks: Unknown consumer [consumer:30520
    53123717449216, type=NONE]
    at com.sun.messaging.jmq.jmsserver.data.handlers.AckHandler.handleAcks(AckHandler.java:256)
    at com.sun.messaging.jmq.jmsserver.data.handlers.AckHandler.handle(AckHandler.java:166)
    at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:146)
    at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.readData(IMQConnection.java:1856)
    at com.sun.messaging.jmq.jmsserver.service.imq.IMQConnection.process(IMQConnection.java:816)
    at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:141)
    at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:459)
    at java.lang.Thread.run(Thread.java:595)
    [24/Apr/2007:16:22:05 EDT] [B1071]: Established cluster connection : testuidp02.dol.state.nj.us/172.31.120.45:7676 (aminstance)
    [24/Apr/2007:16:23:00 EDT] [B1066]: Closing: [email protected]:57590->jms:60425 because "[B0061]: Client exited without closing con
    nections". Count=1
    [24/Apr/2007:16:24:37 EDT] [B1065]: Accepting: [email protected]:42435->jms:60425. Count=2
    [24/Apr/2007:16:26:15 EDT] [B1066]: Closing: [email protected]:42435->jms:60425 because "[B0061]: Client exited without closing con
    nections". Count=1
    Access Manager via load balancer web server works fine with out session failover configuration.
    I noticed through forums that Accessmanager 2005Q4 had similar problem and was fixed with a patch.
    Will somebody please help who has done session failover with AM7.1?
    Thanks
    Kris

    Yep, that was me struggling with 2005Q4 before they released a patch (120954-03 if I am not mistaken).
    1. Have you configured your AM installation as a site?
    2. Have you added a secondary configuration in the session tab?
    A restart will be required after that. Try setting log levels to debug. When AM webserver comes up and brings the application live, you'll see information regarding the secondary configuration, and whether things are actually in place or not.
    Hope this helps.
    Ankush
    http://www.iamcg.net

  • Session Failover and Clustering

              Let's say that we have two WebServers (NES) with the weblogic plugin (say WS1 and WS2) and a cluster with two WebLogicCommerce AppServers (say AS1 and AS2). Let's assume that each WebServer and AppServer runs on its own machine (total: 4 machines). Now, let's assume that the WebServer "obj.conf" files (on both WS1 and WS2) are setup so that they point to the servers in the cluster (WebLogicCluster="AS1:7601,AS2:7601").
              When a new request comes in to one of the WebServers (say WS1), the plugin will route it to one of the AppServers using Round-Robin (say AS1). A session will now be initiated in AS1 and it sends a response back to the client.
              Question 1: How does the other proxy in WS2 know that all future requests for this client need to be forwarded to AS1?
              Question 2: For failover, does the cluster automatically replicate the session state existing in AS1 onto AS2 before sending the response (does AS2 automatically become the secondary)?
              Now let's assume that AS1 crashes/dies. When the next request from the client comes to WS1 or WS2, they will forward it to AS1 (assuming that WS2 knows about the client session in AS1) . Since AS1 has crashed, will the client eventually get a timeout error message?
              Question 3: To ensure that the session failover happens so that AS2 gets the request instead (becomes the primary), do we need to setup a WebLogic Proxy Server? If so, why can't the plugins for NES provide the failover themselves?
              Thank you very much for your help!
              Giri
              

              Thank you very much for your responses. It has been very helpful and I am clear on the session/clustering stuff. I have new questions on EJB and clustering which I will post as a separate thread.
              Giri
              "Jason Rosenberg" <[email protected]> wrote:
              >And also, if the browser has cookies disabled, it is important for
              >the app server to embed the WebLogicSession info via url rewriting,
              >otherwise the proxy or NES will not be able to route the session
              >properly.
              >
              >So, in all http responses, be sure to pass the url string through
              >response.encodeURL(). This will do the right thing depending
              >on whether cookies are enabled or not.
              >
              >I've just only recently figured this out. Haven't actually tried it
              >all out yet, so forgive me if it is not quite this simple, but this
              >seems to be the gist of it...
              >
              >Jason
              >
              >
              >"Justin James" <[email protected]> wrote in message news:[email protected]...
              >>
              >> Giri,
              >>
              >> I'm not a weblogic representative, but I tried to replicate this proxing service inside a load balancing switch(BigIP) and I
              >discovered a few things. The weblogic server sets a cookie (WebLogicSession)that the webserver plugin uses to manage the proxying.
              >The cookie (found in the HTTP header information) contains encoded information about the primary and secondary application servers
              >that the session is bound too. Any web server can read the cookie to determine how to dispatch the request to the primary server.
              >If the primary server does not respond, the request is forwarded to the secondary server by the plugin. Regardless of cluster size,
              >the session is replicated to only one other server.
              >>
              >> <[email protected]> wrote:
              >> >Giri Alwar wrote:
              >> >
              >> >> I need a couple of clarifications. First with regard to Question 1, I understand that plugins provide load balancing and
              >failover but what I really was asking is how the plugin in WS2 knows that a session for the client has been initiated in AS1 as a
              >result of WS1 sending the initial request to AS1. If WS2 gets a future request from the client, it needs to know this to send the
              >request to AS1. Does the plugin talk to the cluster to find out if there is a primary and who it is?
              >> >>
              >> >
              >> >> I should have clarified that my other questions pertain to in-memory replication. If I do not persist the session in a database
              >then does the client get an error message (timeout) when AS1 goes down (assuming we use NES with the WebLogic plugin)?
              >> >
              >> >Plugins' know how to route requests based on cookies. If it can't reach the primary server it will automatically try secondary.
              >In your case it doesn't matter if it reaches to proxy 1 or proxy 2, it is still the same.
              >> >
              >> >- Prasad
              >> >
              >> >> To prevent this error message and achieve failover, do I need to use WebLogic as the proxy server? If so, why isn't the NES
              >plugin doing this?
              >> >
              >> >> Thanks.
              >> >> Giri
              >> >>
              >> >> Prasad Peddada <[email protected]> wrote:
              >> >> >Giri Alwar wrote:
              >> >> >
              >> >> >> Let's say that we have two WebServers (NES) with the weblogic plugin (say WS1 and WS2) and a cluster with two
              >WebLogicCommerce AppServers (say AS1 and AS2). Let's assume that each WebServer and AppServer runs on its own machine (total: 4
              >machines). Now, let's assume that the WebServer "obj.conf" files (on both WS1 and WS2) are setup so that they point to the servers
              >in the cluster (WebLogicCluster="AS1:7601,AS2:7601").
              >> >> >>
              >> >> >> When a new request comes in to one of the WebServers (say WS1), the plugin will route it to one of the AppServers using
              >Round-Robin (say AS1). A session will now be initiated in AS1 and it sends a response back to the client.
              >> >> >>
              >> >> >> Question 1: How does the other proxy in WS2 know that all future requests for this client need to be forwarded to AS1?
              >> >> >
              >> >> > Plugin takes care of load balancing and failover, it is all transparent to the client.
              >> >> >
              >> >> >
              >> >> >> Question 2: For failover, does the cluster automatically replicate the session state existing in AS1 onto AS2 before sending
              >the response (does AS2 automatically become the secondary)?
              >> >> >
              >> >> > If you have only two yes it is automatically your secondary. Yes, replication is synchronous.
              >> >> >
              >> >> >>
              >> >> >> Now let's assume that AS1 crashes/dies. When the next request from the client comes to WS1 or WS2, they will forward it to
              >AS1 (assuming that WS2 knows about the client session in AS1) . Since AS1 has crashed, will the client eventually get a timeout
              >error message?
              >> >> >
              >> >> > If you are using some kind of persistence then you will be able to retrieve the session information and since the server
              >is not available the request will automatically failover.
              >> >> >
              >> >> >> Question 3: To ensure that the session failover happens so that AS2 gets the request instead (becomes the primary), do we
              >need to setup a WebLogic Proxy Server? If so, why can't the plugins for NES provide the failover themselves?
              >> >> >
              >> >> > No, you need only one. Either NES or weblogic proxy.
              >> >> >
              >> >> >
              >> >> >> Thank you very much for your help!
              >> >> >> Giri
              >> >> >
              >> >> >- Prasad
              >> >> >
              >> >
              >>
              >
              >
              

  • Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015. SQL 2012 SP1

    Hi,
    Please help. I was trying to remove a SQL 2012 SP1 two node clustered instance using setup (Mantenance -> Remove Node)
    I started by doing this on passive node (and was successful) but when I ran setup on active node just before finishing successfully I got this error:
    TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
    The following error has occurred:
    The resource 'BCK_SG1DB' could not be moved from cluster group 'SQL Server (SG1DB)' to cluster group 'Available Storage'. 
    Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015.
    Description: The operation failed because either the specified cluster node is not the owner of the resource, or the node
    is not a possible owner of the resource.
    For help, click:
    http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE8049925%25400x42B4DED7
    BUTTONS:
    OK
    I noticed that SG1DB instance was removed on both nodes but on Failover Cluster Manager -> Services and Applications the SQL server instance for SG1DB is still there. So I tried to delete it but got the error:
    Failed to delete SQL Server SG1DB. An error was encountered while deleting the cluster service or
    application SQL Server SG1DB. Could not move the resource to available storage. An error occured
    while moving the resource BCK_SG1DB to the clustered service or application Available Storage
    Any ideas why it failed or how could I delete the SQL server instance from Clauster?
    Thx

    Hello,
    Please read the following resource.
    https://support.microsoft.com/en-us/kb/kbview/313882?wa=wsignin1.0
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • How to get only current exception message from tables

    Hi
    In my sceanario , I want to have the list of Current MRP exception messages list from table
    I understand that MRP detailed lists, including all exception messages, are stored in transparent table MDKP and cluster table MDTC.
    I can tell ABAPer to write a report for me , to read the data from these tables , but I guess these tables contain old exception message also , which are not currently appearing in MRP list
    How to get only current exception message
    Rgds,
    sandeep

    Sandeep,
    MDTC contains only data from the most recent MRP run.  So, all messages you see are those which are currently valid.
    The messages might have first appeared during a previous run, but they still need to be addressed.
    Before you invest a lot of time and effort into writing and debugging a custom report, you should probably try to use the standard SAP functionality found in MD06.  On the Processing indicator tab, you can select "Only with new exceptions".  Here you can tag a material/plant as 'processed', and thereafter, the exceptions that existed there before you tagged the part will not be re-displayed.
    Best Regards,
    DB49

  • Getting class cast exception in Web application.

    I have a web application deployed using standard specs for deployment. I
              have and web-inf directory with a web.xml file set up. All the servlet
              classes are in the classes sub-directory of web-inf.
              If I deploy this application using the Tomcat application server,
              everything works as expected. When I deploy this application using the
              Weblogic software, I can get to the initial page, put once I select a
              link that calls the main servlet, I get a classcast exception. Both the
              Tomcat and Weblogic software point to the same directory for the
              application.
              I double checked and made sure that no other instances of my servlet
              classes exist anywhere else in the class path.
              Any one have any thoughts or suggestions. I am perplexed that this web
              app runs fine under the Tomcat software and yet...
              Thanks.
              Paul Garduno
              

    Thanks for your reply. I am not using any EJBs. From what I have
              gathered since writing my message, this may be the "dreaded" class cast
              exception (although I don't know why since it runs under Tomcat).
              Basically, the initial page is displayed. When you select the SEARCH
              button (for example), the request goes to a servlet which puts a vector
              of custom classes into a session parameter. The request is then
              forwarded to the JSP page which uses the information in the classes to
              help build some information on the page. The first line in the JSP is
              processed (a simple output line to the system console) and then the
              classcast exception occurs.
              According to the info that I have seen, this shouldn't happen since I am
              not changing either the servlet or JSP files which would mean that
              nothing should be re-compiled.
              I have a call into tech support. I will post their answer and copy you
              on the message.
              Thanks.
              Paul
              Cameron Purdy wrote:
              >
              > Are you using EJBs hosted on the same instance of WebLogic? If so, delete
              > the home/remote interfaces from your web deployment. Otherwise, post the
              > exception listing ....
              >
              > Cameron Purdy, LiveWater
              >
              > "Paul Garduno" <[email protected]> wrote in message
              > news:[email protected]...
              > > I have a web application deployed using standard specs for deployment. I
              > > have and web-inf directory with a web.xml file set up. All the servlet
              > > classes are in the classes sub-directory of web-inf.
              > >
              > > If I deploy this application using the Tomcat application server,
              > > everything works as expected. When I deploy this application using the
              > > Weblogic software, I can get to the initial page, put once I select a
              > > link that calls the main servlet, I get a classcast exception. Both the
              > > Tomcat and Weblogic software point to the same directory for the
              > > application.
              > >
              > > I double checked and made sure that no other instances of my servlet
              > > classes exist anywhere else in the class path.
              > >
              > > Any one have any thoughts or suggestions. I am perplexed that this web
              > > app runs fine under the Tomcat software and yet...
              > >
              > > Thanks.
              > >
              > > Paul Garduno
              

  • HADB session failover & realm problem

    I have a enterprise applicaiton server cluster configured for loadbalancing and session failover.
    I installed HADB.
    HADB works, I test with the webapp from the samples of the application server:
    I add some attribute in session, I see which node executed the request, I stop the node.
    The other requesto go to the other node and the session is reloaded as it was on the stopped node.
    The problem I have is with app with realms authentication.
    I can login without problem on the first node.
    I stop the server handling the request and when switched to the other server I have to login again if I request a realm protected URL again.
    Any suggestion?
    Thanks in advance.

    Solved
    on Cluster configuration (in the tree of admin apps of application server):
    my-clu-config -->
       Availability Service -->
            Web Container Availability -->
                      Single-Sign-On State: Enabled.

  • Use of error page resulting in could not deserialize session data exception

              We have recently converted classes that store objects in the HTTP Session to implement
              serializable.
              Our application uses an error page set up in our web.xml for 500 errors.
              It also uses filters.
              When our application throws an exception and allows the server to handle it
              via the error page setup, we end up with the exception we threw, plus a number
              of
              "Could not deserialize session data" exceptions in the stack trace.
              In general, the exceptions can be traced to lines in code that attempt to reference
              one of our "serializable" session objects to get user info for logging purposes.
              Problem is, other applications that do not use error pages to handle exceptions
              do not throw these types of exceptions in the wl-domain.log and they use the same
              classes.
              Does anyone know why this happens when using error pages and what we need to do
              to correct it?
              We are using Weblogic 8.1sp2.
              Thanks!!
              Example of the stack trace messages:
              ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
              <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
              <Could not deserialize session data.
              java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
                   at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
                   at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
                   at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
                   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
                   at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
                   at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
                   at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
                   at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
                   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
                   at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
                   at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
              <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
              <Could not deserialize session data.
              java.io.NotSerializableException: java.util.Vector$1
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
                   at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
                   at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
                   at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
                   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
                   at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
                   at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
                   at doh.stuff.OurHTML.<init>(OurHTML.java:57)
                   at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
                   at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
                   at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
                   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
                   at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
                   at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              

              We have recently converted classes that store objects in the HTTP Session to implement
              serializable.
              Our application uses an error page set up in our web.xml for 500 errors.
              It also uses filters.
              When our application throws an exception and allows the server to handle it
              via the error page setup, we end up with the exception we threw, plus a number
              of
              "Could not deserialize session data" exceptions in the stack trace.
              In general, the exceptions can be traced to lines in code that attempt to reference
              one of our "serializable" session objects to get user info for logging purposes.
              Problem is, other applications that do not use error pages to handle exceptions
              do not throw these types of exceptions in the wl-domain.log and they use the same
              classes.
              Does anyone know why this happens when using error pages and what we need to do
              to correct it?
              We are using Weblogic 8.1sp2.
              Thanks!!
              Example of the stack trace messages:
              ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
              <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
              <Could not deserialize session data.
              java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
                   at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
                   at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
                   at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
                   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
                   at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
                   at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
                   at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
                   at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
                   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
                   at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
                   at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
              <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
              <Could not deserialize session data.
              java.io.NotSerializableException: java.util.Vector$1
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
                   at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
                   at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
                   at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
                   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
                   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
                   at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
                   at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
                   at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
                   at doh.stuff.OurHTML.<init>(OurHTML.java:57)
                   at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
                   at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
                   at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
                   at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
                   at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
                   at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
              >
              

  • How can I get Firefox to except the home page that I want to use

    I have clicked and dragged the icon a hundred times, and still when I click on Firefox a previously set up home page appears.
    This is very annoying because I can get to my homepage; but I have to sign on to yahoo e-mail every time; then go to my homepage and my bookmarks. I can't seem to get it to except the homepage I want to use..

    If you want a customize Yahoo! page then make sure that you keep the Yahoo! cookies.
    Such details are stored in a cookie.
    * Create an allow cookie exception (Tools > Options > Privacy > Cookies: Exceptions) to keep such a cookie, especially for secure websites and if cookies expire when Firefox is closed.
    * In [[Private Browsing]] mode all cookies are session cookies that expire if that session is ended, so websites won't remember you.
    * In [[Private Browsing]] mode Firefox won't fill names and passwords automatically.
    * You enter Private Browsing mode if you select: Tools > Options > Privacy > History: Firefox will: "Never Remember History"
    * To see all History and Cookie settings, choose: Tools > Options > Privacy, choose the setting <b>Firefox will: Use custom settings for history</b>
    * Uncheck: [ ] "Permanent Private Browsing mode"
    * Do not use [[Clear Recent History]] to clear the "Cookies" and the "Site Preferences"
    Clearing "Site Preferences" clears all exceptions for cookies, images, pop-up windows, software installation, and passwords.
    * http://kb.mozillazine.org/Cookies

  • Clustered role 'Cluster Group' has exceeded its failover threshold.

    Hello.
    I’m hoping to get some help with a cluster issue I’m having using Windows Storage Server 2012.
    When the cluster is created my Cluster Core Resources are all happy and online.
    I can more the Cluster Name using “move Core Cluster Resources” between the two nodes without any problems.
    If I select ‘Simulate Failure’ on the IP Address resource, it works the first time
    If I do it again shortly after it fails and I get an Event ID 1254, 1205 and 1069.
    Event ID 1254
    Clustered role 'Cluster Group' has exceeded its failover threshold. 
    It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. 
    No additional attempts will be made to bring the role online or fail it over to another node in the cluster. 
    Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.
    Event ID 1205
    The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
    Event ID 1069
    Cluster resource 'Cluster IP Address' of type 'IP Address' in clustered role 'Cluster Group' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. 
    Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
    Basically I’m trying to simulate a network failure to make sure the failover kicks in.
    If I click on it and ‘Bring Online’ it comes up fine.
    Where do I find this Threshold Policy and set it to initiate failover if the IP Address resources fails?
    Thank you in advance for your help.

    Hi,
    The failover threshold is the number of times the group can fail over within the number of hours specified by the failover period. For example, if a group failover threshold is set to "5" and its failover period to "3," the clustering software stops attempting
    to bring the group online and leaves the resources within the group in their current state. For example, if the IP Address resource is brought online but the Network Name resource fails, the group is left offline, but the IP Address resource is left online.
    To configure thresholds for a resource:
    Right-click the cluster resource and then select 'Propereties'
    Click 'Advanced'
    Select 'Do not restart' if the cluster service should not attempt to restart. Restart is the default
    If 'Restart' is selected:
    Affect the Group: uncheck to prevent a failure of the selected resource from causing the Server group to failover
    Threshold: number of times the cluster service will attempt to restart the resource, and period is the amount of time in seconds between retries
    Do not modify the 'LooksAlive' and 'IsAlive' settings
    Unless necessary, do not alter the 'Pending Timeout'. This is the amount of time the resource is either in the online or pending or offline pending states before the the cluster service puts it in either offline or failed state
    For more information please refer to following MS articles:
    Windows Failover Clustering Overview
    http://blogs.technet.com/b/rob/archive/2008/05/07/failover-clustering.aspx
    Tuning Failover Cluster Network Thresholds
    http://blogs.msdn.com/b/clustering/archive/2012/11/21/10370765.aspx
    Failover cluster (group) maximum failures limit
    http://blogs.msdn.com/b/arvindsh/archive/2012/03/09/failover-cluster-group-maximum-failures-limit.aspx
    Lawrence
    TechNet Community Support

  • XA  jDriver for Oracle problem : Getting native code exception

    Hi,
    I'm getting a native code exception which causes the Weblogic server to crash when
    using XA drivers for transaction with two oracle databases. My application uses RMI
    and threads.
    I'm using BEA's jDriver for Oracle running under Weblogic server 6.1 sp1 talking
    to Oracle 8.1.6. The OS is Solaris 2.8.
    In middle of the program execution it's giving this problem. I'm using jdk131 in
    solaris platform.
    Any idea what's going on here ?
    Thanks,
    Nagoor Haja
    Exception in the Log file:
    ===========================
    An unexpected exception has been detected in native code outside the VM.
    Unexpected Signal : 11 occurred at PC=0xff2414d8
    Function name=madvise
    Library=/usr/lib/libc.so.1
    Current Java thread:
    at weblogic.jdbc.oci.xa.XA.native_commit(Native Method)
    at weblogic.jdbc.oci.xa.XA.commit(XA.java:136)
    at weblogic.jdbc.oci.xa.XADataSource.commit(XADataSource.java:696)
    at weblogic.jdbc.jta.DataSource.commit(DataSource.java:784)
    at weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.java:1180)
    at weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.java:419)
    at weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:233)
    at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1397)
    at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:1940)
    at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:1886)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:221)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
    at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
    at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    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)
    Dynamic libraries:
    0x10000 /opt/jdk131/jre/bin/../bin/sparc/native_threads/java
    0xff350000 /usr/lib/libthread.so.1
    0xff390000 /usr/lib/libdl.so.1
    0xff200000 /usr/lib/libc.so.1
    0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
    0xfe480000 /opt/jdk131/jre/lib/sparc/hotspot/libjvm.so
    0xff2e0000 /usr/lib/libCrun.so.1
    0xff1e0000 /usr/lib/libsocket.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff310000 /usr/lib/libw.so.1
    0xff0b0000 /usr/lib/libmp.so.2
    0xff080000 /opt/jdk131/jre/lib/sparc/native_threads/libhpi.so
    0xff050000 /opt/jdk131/jre/lib/sparc/libverify.so
    0xfe440000 /opt/jdk131/jre/lib/sparc/libjava.so
    0xff020000 /opt/jdk131/jre/lib/sparc/libzip.so
    0xfafb0000 /opt/jdk131/jre/lib/sparc/libnet.so
    0xfadd0000 /usr/lib/nss_files.so.1
    0xe1d00000 /opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoci37.so
    0xe1400000 /opt/oracle/lib/libclntsh.so.8.0
    0xfac90000 /usr/lib/libC.so.5
    0xfadb0000 /opt/oracle/lib/libwtc8.so
    0xfad90000 /usr/lib/libgen.so.1
    0xfac70000 /usr/lib/libsched.so.1
    0xfac40000 /usr/lib/libaio.so.1
    0xfac20000 /opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoxa37.so
    0xe8ad0000 /redis/tibco/rv6.6/lib/libtibrvj.so
    0xe8ab0000 /redis/tibco/rv6.6/lib/libtibrvcmq.so
    0xe89c0000 /redis/tibco/rv6.6/lib/libtibrvcm.so
    0xe8990000 /redis/tibco/rv6.6/lib/libtibrvft.so
    0xe8890000 /redis/tibco/rv6.6/lib/libtibrv.so
    0xe8870000 /usr/lib/libpthread.so.1
    0xe6fe0000 /opt/wlserver6.1/lib/solaris/libmuxer.so
    0xe6fc0000 /opt/wlserver6.1/lib/solaris/libweblogicunix1.so
    java Exception in the program due to the above reason:
    ======================================================
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
         at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
         at com.cme.clearing.jta.JThread.process(JThread.java:100)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
         at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
         at com.cme.clearing.jta.JThread.process(JThread.java:100)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException - with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
         at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
         at com.cme.clearing.jta.JThread.process(JThread.java:100)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction is not active.
    Xid=0:a1ccd55d7f28edb9(795840),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=0:a1ccd55d7f28edb9(795840),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=29,seconds left=30,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=68,seconds left=1,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
         at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
         at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy1.process(Unknown Source)
         at com.cme.clearing.jta.JThread.process(JThread.java:101)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction is not active.
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=29,seconds left=30,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=69,seconds left=0,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
         at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
         at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy1.process(Unknown Source)
         at com.cme.clearing.jta.JThread.process(JThread.java:101)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction is not active.
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Rolled back. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 33 seconds
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Active,numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=33,seconds left=30,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOwedOthers=0,seconds
    since begin=68,seconds left=5,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,CoordinatorURL=myserver+10.1.32.81:8001+mydomain+)
         at weblogic.transaction.internal.TransactionManagerImpl.sendRequest(TransactionManagerImpl.java:1155)
         at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:101)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy1.process(Unknown Source)
         at com.cme.clearing.jta.JThread.process(JThread.java:101)
         at com.cme.clearing.jta.JThread.run(JThread.java:85)
    javax.naming.CommunicationException. Root exception is java.rmi.ConnectException:
    Unable to get direct or routed connection to: '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain:myserver'
         at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:255)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:222)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy0.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
         at javax.naming.InitialContext.lookup(InitialContext.java:350)
         at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
         at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
         at com.cme.clearing.jta.JThread.run(JThread.java:81)
    Exception null
    javax.naming.CommunicationException. Root exception is java.rmi.ConnectException:
    Unable to get direct or routed connection to: '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain:myserver'
         at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:85)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:255)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:222)
         at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
         at $Proxy0.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
         at javax.naming.InitialContext.lookup(InitialContext.java:350) Exception null
         at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
         at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
         at com.cme.clearing.jta.JThread.run(JThread.java:81)

    I see. Do you mean this code runs outside of the server? :
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    Regards,
    Slava Imeshev
    "Tim" <[email protected]> wrote in message
    news:[email protected]...
    >
    Slava,
    In my case, I'm not spawning any threads.
    Regards,
    Tim
    "Slava Imeshev" <[email protected]> wrote:
    That could be a trace of some threading issue. Note that EJB spec
    prohibits
    using threads within a container.
    Regards,
    Slava Imeshev
    "Tim" <[email protected]> wrote in message
    news:[email protected]...
    Nagoor,
    Did anybody respond? I'm getting the same exception with the sameenvironment configuration
    but using WLS 6.1 SP2.
    Tim
    "Nagoor Haja" <[email protected]> wrote:
    Hi,
    I'm getting a native code exception which causes the Weblogic server
    to
    crash when
    using XA drivers for transaction with two oracle databases. Myapplication
    uses RMI
    and threads.
    I'm using BEA's jDriver for Oracle running under Weblogic server 6.1sp1
    talking
    to Oracle 8.1.6. The OS is Solaris 2.8.
    In middle of the program execution it's giving this problem. I'm
    using
    jdk131 in
    solaris platform.
    Any idea what's going on here ?
    Thanks,
    Nagoor Haja
    Exception in the Log file:
    ===========================
    An unexpected exception has been detected in native code outside theVM.
    Unexpected Signal : 11 occurred at PC=0xff2414d8
    Function name=madvise
    Library=/usr/lib/libc.so.1
    Current Java thread:
    at weblogic.jdbc.oci.xa.XA.native_commit(Native Method)
    at weblogic.jdbc.oci.xa.XA.commit(XA.java:136)
    atweblogic.jdbc.oci.xa.XADataSource.commit(XADataSource.java:696)
    at weblogic.jdbc.jta.DataSource.commit(DataSource.java:784)
    at
    weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
    ava:1180)
    at
    weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
    ava:419)
    at
    weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:233
    at
    weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
    ctionImpl.java:1397)
    at
    weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(Server
    TransactionImpl.java:1940)
    at
    weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTrans
    actionImpl.java:1886)
    at
    weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
    nsactionImpl.java:221)
    at
    weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
    Impl.java:190)
    at
    weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68
    atweblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown
    Source)
    atweblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:296)
    at
    weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:265)
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
    2)
    at
    weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Dynamic libraries:
    0x10000 /opt/jdk131/jre/bin/../bin/sparc/native_threads/java
    0xff350000 /usr/lib/libthread.so.1
    0xff390000 /usr/lib/libdl.so.1
    0xff200000 /usr/lib/libc.so.1
    0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
    0xfe480000 /opt/jdk131/jre/lib/sparc/hotspot/libjvm.so
    0xff2e0000 /usr/lib/libCrun.so.1
    0xff1e0000 /usr/lib/libsocket.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff100000 /usr/lib/libnsl.so.1
    0xff0d0000 /usr/lib/libm.so.1
    0xff310000 /usr/lib/libw.so.1
    0xff0b0000 /usr/lib/libmp.so.2
    0xff080000 /opt/jdk131/jre/lib/sparc/native_threads/libhpi.so
    0xff050000 /opt/jdk131/jre/lib/sparc/libverify.so
    0xfe440000 /opt/jdk131/jre/lib/sparc/libjava.so
    0xff020000 /opt/jdk131/jre/lib/sparc/libzip.so
    0xfafb0000 /opt/jdk131/jre/lib/sparc/libnet.so
    0xfadd0000 /usr/lib/nss_files.so.1
    0xe1d00000/opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoci37.so
    0xe1400000 /opt/oracle/lib/libclntsh.so.8.0
    0xfac90000 /usr/lib/libC.so.5
    0xfadb0000 /opt/oracle/lib/libwtc8.so
    0xfad90000 /usr/lib/libgen.so.1
    0xfac70000 /usr/lib/libsched.so.1
    0xfac40000 /usr/lib/libaio.so.1
    0xfac20000/opt/wlserver6.1/lib/solaris/oci816_8/libweblogicoxa37.so
    0xe8ad0000 /redis/tibco/rv6.6/lib/libtibrvj.so
    0xe8ab0000 /redis/tibco/rv6.6/lib/libtibrvcmq.so
    0xe89c0000 /redis/tibco/rv6.6/lib/libtibrvcm.so
    0xe8990000 /redis/tibco/rv6.6/lib/libtibrvft.so
    0xe8890000 /redis/tibco/rv6.6/lib/libtibrv.so
    0xe8870000 /usr/lib/libpthread.so.1
    0xe6fe0000 /opt/wlserver6.1/lib/solaris/libmuxer.so
    0xe6fc0000 /opt/wlserver6.1/lib/solaris/libweblogicunix1.so
    java Exception in the program due to the above reason:
    ======================================================
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
    with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException]
    at
    weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
    >>>>
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
    with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException]
    at
    weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
    >>>>
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.sql.SQLException: weblogic.rmi.extensions.RemoteRuntimeException-
    with nested
    exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException]
    at
    weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:310)
    >>>>
    at com.cme.clearing.jta.JThread.insertAgain(JThread.java:121)
    at com.cme.clearing.jta.JThread.process(JThread.java:100)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction isnot
    active.
    Xid=0:a1ccd55d7f28edb9(795840),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=0:a1ccd55d7f28edb9(795840),Status=Active,numRepliesOwedMe=1,numReplies
    O
    wedOthers=0,seconds
    since begin=29,seconds
    left=30,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myser
    >
    ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
    >
    atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
    edOthers=0,seconds
    since begin=68,seconds
    left=1,activeThread=Thread[Thread-1,5,main],spatidbxa,SCInfo[mydomain+myserv
    >
    er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
    torURL=myserver+10.1.32.81:8001+mydomain+)
    at
    weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
    ManagerImpl.java:1155)
    at
    weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
    101)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
    >>>>
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy1.process(Unknown Source)
    at com.cme.clearing.jta.JThread.process(JThread.java:101)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction isnot
    active.
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 29 seconds
    Xid=1:a1ccd55d7f28edb9(6051803),Status=Active,numRepliesOwedMe=1,numReplie
    s
    OwedOthers=0,seconds
    since begin=29,seconds
    left=30,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myser
    >
    ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
    >
    atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
    edOthers=0,seconds
    since begin=69,seconds
    left=0,activeThread=Thread[Thread-2,5,main],spatidbxa,SCInfo[mydomain+myserv
    >
    er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
    torURL=myserver+10.1.32.81:8001+mydomain+)
    at
    weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
    ManagerImpl.java:1155)
    at
    weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
    101)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
    >>>>
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy1.process(Unknown Source)
    at com.cme.clearing.jta.JThread.process(JThread.java:101)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    java.rmi.RemoteException: Message was not sent because transaction isnot
    active.
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Rolled back.[Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 33 seconds
    Xid=2:a1ccd55d7f28edb9(4244097),Status=Active,numRepliesOwedMe=1,numReplie
    s
    OwedOthers=0,seconds
    since begin=33,seconds
    left=30,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myser
    >
    ver]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordin
    >
    atorURL=myserver+10.1.32.81:8001+mydomain+)],numRepliesOwedMe=1,numRepliesOw
    edOthers=0,seconds
    since begin=68,seconds
    left=5,activeThread=Thread[Thread-3,5,main],spatidbxa,SCInfo[mydomain+myserv
    >
    er]=(state=active),properties=({}),OwnerTransactionManager=ClientTM,Coordina
    torURL=myserver+10.1.32.81:8001+mydomain+)
    at
    weblogic.transaction.internal.TransactionManagerImpl.sendRequest(Transaction
    ManagerImpl.java:1155)
    at
    weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:
    101)
    at
    weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:123)
    >>>>
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy1.process(Unknown Source)
    at com.cme.clearing.jta.JThread.process(JThread.java:101)
    at com.cme.clearing.jta.JThread.run(JThread.java:85)
    javax.naming.CommunicationException. Root exception isjava.rmi.ConnectException:
    Unable to get direct or routed connection to:
    '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain
    :myserver'
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy0.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    >>>>
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
    at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
    at com.cme.clearing.jta.JThread.run(JThread.java:81)
    Exception null
    javax.naming.CommunicationException. Root exception isjava.rmi.ConnectException:
    Unable to get direct or routed connection to:
    '-736127454917455663S:10.1.32.81:[8001,8001,8002,8002,8001,8002,-1]:mydomain
    :myserver'
    at
    weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
    java:85)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :255)
    at
    weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java
    :222)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy0.lookup(Unknown Source)
    at
    weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
    >>>>
    at javax.naming.InitialContext.lookup(InitialContext.java:350)Exception
    null
    at com.cme.clearing.jta.JContext.getTransaction(JContext.java:29)
    at com.cme.clearing.jta.JThread.startTransaction(JThread.java:67)
    at com.cme.clearing.jta.JThread.run(JThread.java:81)

  • Does the SCAN feature in 11gR2 provide session failover?

    I setup a two-node RAC environment (11.2.0.2), and I can successfully connect to it using Single Client Access Name (SCAN). My clients' tnsnames.ora is as simple as:
    RAC =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = cluster-scan)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = rac)
    I was told by the senior DBA that SCAN provides session failover. By that I mean: suppose there are two nodes, and I have a client establish a connection through sqlplus in another machine (client version 11.2.0.2 as well), eg:
    sqlplus system/password@rac
    I then use something like "SELECT host_name, instance_name FROM v$instance" to figure out which instance I am connected to and I shutdown that instance by running "shutdown abort" there. The expected behavior is for that client to automatically switch to the surviving node (*in the same session*).
    However, it doesn't work that way. Instead, the next SQL statement issued in that sqlplus session results in a "ORA-03113: end-of-file on communication channel." I managed to have it failover automatically, without adding anything (eg: FAILOVER_MODE) in the clients' tnsnames files by creating a service with TAF using srvctl:
    srvctl add service -d rac -s ractaf -P BASIC -m BASIC -e SELECT -z 5 -w 120
    But I have been told this step is not necessary with 11gR2, and session failover should occur automatically if I installed the grid infrastructure and set up SCAN correctly. But I haven't been able to find anything in the documentation indicating this is the case. So, does the SCAN feature in 11gR2 provide session failover?
    Edited by: 894946 on Nov 3, 2011 10:16 AM

    I think you are right because session failover is a service property linked to cluster database instances and not a scan listener feature that basically establish connection with right instance.

  • Getting stack overflow exception whilst reading from HashMap

    hi,
    We are getting stack oveflow exception exception whilst reading from the HashMap.
    Following are few details about the code
    We have a swing based client and Session beans and Entity beans deployed on Weblogic Server.
    When the server is started, a session bean method queries to data base and creates a java object for each row in the data base.This java object is then stored in HashMap. These java objects have all get/set methods . and it has attributes of primitive data type as well as other java objects.This Hahsmap is then returned to client.
    When client calls this method and the method processes succesfuly , but when tries to return the HashMap, it gives Stack overflow exception.
    Looking at the stack trace i think this exception is thrown when the HashMap.readObject() methods is being invoked.
    does any body have any idea about this ? a quick help is much appriciated.

    Stack overflow is often caused by infinity loops No, an infinite loop would be like while (true) {
        // stuff
    } That doesn't cause stack overflow.
    or
    recursive method calls.Bingo.

Maybe you are looking for

  • Lightroom - Lens Correction - Lens Manufactuer unknown

    I have a Canon Rebel XTi and shoot in Raw. I have 3 Tamron lenses - a 10-24, 17-50 and 18-270. I thought I'd try out the lens correction profile for my 10-24 for a few pics, but when invoking the option, it was unable to determine the len manufacture

  • Email in HTML - iPhone

    How can I retain the HTML format when sending email? In a similar way, I want my emails to go in HTML format from my iPhone. As of now, it goes as text type and I did not like the font. I wanted to go as Arial.

  • PSE 8 catalog issue with Lr3

    I installed PSE 8 and then installed Lightroom 3 and did the catalog upgrade conversion. but now my PSE 8 catalog has not updated in a few months and when I try to import or get PSE 8 to update the catalog - it stops due to errors. And additionally,

  • BW statistics for Process chains

    Hi All. We want to do some analysis on our process chains... like which process chains takes the longest to run, which InfoPackages (or other steps) in a process chain takes up most of the time etc... The BW statistics cubes like 0BWTC_C05 keeps nice

  • Installing Windows Media 9 - help??

    I'm trying to upgrade my windows media player to wmp 9 but i dont know which program to use to open the downloaded file from the apple website. The file is a .sitx and the computer doesent automatically open it, just gives you the option to choose an