ERROR: Error in getting session data: Invalid or Expired Session

Hi,
We are using ssrs 2008 r2 and have a report which has links that allow the user to drill down.
When the link is clicked the same report is run but shows more detail. This works fine but we are now getting the error below for a user. 
I have increased the time out for the report to 600 seconds.
Error in getting session data: Invalid or Expired Session: fnxgxhjuveugvd552qfyv3fw
session!ReportServer_0-6!4b0!03/18/2015-10:51:29:: i INFO: LoadSnapshot: Item with session: fnxgxhjuveugvd552qfyv3fw, reportPath: , userName: doman/user not found in the database
Any ideas how this can be resolved?

Hi Nasa1999,
Based on your error message, If the all the users will sometimes got the same issue, it can be caused by the timeout issue. It happens a lot when rendering big report, and it exceeds the default Session Timeout. You can execute script
to increase the Session Timeout time. Please refer to following blog:
Session Timeout during execution. Also increase the value of <Query Timeout> in rsreportserver.config file. This file locate at XX:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
Please also check to set the <legacyImpersonationPolicy> back to true(https://support.microsoft.com/en-us/kb/972328).
Locate the Aspnet.config file in the following folder:
 %windir%\Microsoft.NET\Framework64\v2.0.50727
If Microsoft Visual Studio is installed on the computer that is running SQL Server 2005, double-click
Aspnet.config. If Visual Studio is not installed on the computer, follow these steps:
        a. Right-click Aspnet.config, point to
Open with, and then click Choose program.
        b. In the Programs list, click
Notepad, and then click OK.
Locate the following tag in the <runtime> section of the code.
        <legacyImpersonationPolicy enabled="false"/>
Change the tag to:
        <legacyImpersonationPolicy enabled="true"/>
Save the Aspnet.config file.
Reset IIS.
Try your report again.
Similar Thread for your reference:
Using SharePoint Report Viewer
Web Part: Error in getting session data: Invalid or Expired Session: xxxxxxxxxxx
If only the one user or several users will got the issue, the issue can be caused by the permission setting, please reference to below blog:
http://answers.flyppdevportal.com/categories/sqlserver/sqlreportingservices.aspx?ID=3506231b-9f4d-4f5a-884d-157137c56336
http://blog.goobol.com/the-permissions-granted-to-user-domainusername-are-insufficient-for-performing-this-operation/
If your problem still exists, please try to provide more details information as below:
Did you reporting service installed in native mode or sharepoint mode, If in native mode, please try to provide more error message from the log file:
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

Similar Messages

  • Error: Could not get markup. The cookie or session is invalid or ...

    When I run the portlet getting the below error:
    Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.
    I have gone through the log, it's processing the request.
    Any help on this ...

    first can you give us some idea about which product/component/platform/version are you working with. and how did you edit the 'portal prefs'.
    thanks!

  • LV 8.0.1 Bug, no error when unflattening mis-matched data type

    When unflattening a string and wiring a "type" that does not match the original format of the data, sometimes I don't get an error and I get no data. I've attached a VI written in 8.0.1 that illustrates 2 examples of this. In LV 7.1 these cases did return an error, but not in 8.0.1. Can anyone offer some insight or global solution?
    Thanks, Chip
    Attachments:
    LV 8 Bug, no error trapped on mismatched type when unflattening string.vi ‏23 KB

    Good afternoon,
    Well, this certainly is an interesting situation.  In the example “Unflatten string returns data
    from previous iterations”, the second iteration of the for loop unflattens a
    string as an array of strings type, this is obviously a type mismatch so if any
    data is returned I wouldn’t expect it to be valid.  What is even more interesting, is that if you
    don’t use the auto indexing, but rather explicitly index the array there is no
    error, but the data returned is like it was in 7.x.  I tried to use the flatten function’s
    “convert 7.x data function with no luck in either case.  I filed a bug report on this issue (number
    3X0CBC3A), but it seems to me the only workaround for now is going to be just
    making sure the types match.  I know this
    is going to be inconvenient for you, and for that I apologize.
    Incidentally, in many cases I wouldn’t necessarily expect an
    error to be generated if the types don’t match. 
    This is because the flatten to string function takes your data and
    converts it to a string which is nothing more than a byte[ ] of data with some
    size information.  When you “unflatten”
    the function takes the string it is given, and attempts to reconstruct the data
    in the format that is specified by the “type” input.  If it can reconstruct the data from type,
    regardless of the data returned I wouldn’t expect it to generate an error.  Sometimes, however, an error can be detected
    – if you flatten a double-precision number and unflatten to a single precision
    number LabVIEW can detect that the incoming data represents something much
    larger than a single precision number.  I
    suppose that LabVIEW 7 did a better job checking the size of the sting before
    deciding whether or not to generate an error.
    Again, I apologize for the problems this may cause.  Please let me know if there is anything else
    I can help with.
    Travis M
    LabVIEW R&D
    National Instruments

  • Property Data Invalid

    Having a problem when I try to export from Premiere Pro (CS4). The main files I am importing are .flv (Sorenson H.263 - btw anyone know why it won't find media data for H.264 .flv?), 29,970, 4:3, 640 x 480, etc. I have tried modifying these file specs and generating new .flvs - codec, frame rate, size, aspect ratio, audio codec & sample rate, etc. - to get a better match with the sequence setting presets but  nothing seems to be working. I always get "Property Data Invalid" and then it crashes.
    My computer specs:
    Custom Intel Core-Duo CPU
    6400 @ 2.13 GHz, 1.99 GB RAM
    Windows XP SP3
    Hard Drive - 1x 195GB NTFS w/ 106GB free
    ATI Radeon Graphics Processor
    RAID controllers: Intel(R) 82801 GR/GH SATA RAID Controller, and Silicon Image SiI 3114 SoftRaid 5 Controller
    HP DVD Writer 840y
    Virtual memory 2044 MB for all drives
    Let me know if I've missed any pertinent info. I am new to Adobe CS4 but so far it seems to be a whole lot of hassle. Can anyone offer any speculative insights as to what could be going on?
    Thanks

    In a 3x HDD setup, the first disc is used for the OS, programs, and possibly the Page File (Windows Virtual Memory). The other two HDD's are used, one for media and one for the Project and Scratch Disks.
    Video editing is highly I/O intensive. The ability of the computer to access multiple HDD's for multiple tasks is very important to freeing things up. If everything is on one physical HDD, then the computer keeps waiting on the reads/writes, that cannot come at the same time. Things get even worse, should one have any partitions, because the OS thinks that it's dealing with multiple physical HDD's, but is only dealing with logical HDD's, and it cannot understand why it's taking so long.
    This is heavily simplified, but it all about data access.
    Good luck,
    Hunt

  • Servlet Session data being shared

    I have a bunch of servlets tha basically generate reports. The problem I'm having is that when two users run the same servlet at about the same time, one of the reports will be over written by the data of the other report. It almost seems that the users are sharing the same context.
    Is there any way to fix this or do you have ny suggestions, tips as to how to prevent this.
    Thnaks in advance for any help you may provide.

    I ran into a similar problem not to long ago with sessions. I had an instance or global reference to the session object in my servlet. When two or more people used the servlet at just the right time I would get problems where data was getting used across sessions. For example:
    public class FooServlet extends HttpServlet
         HttpSession session;
         doGet(HttpServletRequest req, HttpServletResponse res)
              session = req.getSession(false);
              doStuffWithSessionData();
         doStuffWithSessionData()
              String temp = session.getValue("temp");
              //do some stuff
    }So, person A would connect to the servlet, and their session would be retreived, and the instance reference would get set to their session. Person B would connect at about the same time, their session would get retreived and the instance reference would get set to theirs... right before the getValue("temp") on person A's session is called. So, whatever I was doing for person A would end up using the data out of person B's session. I like to call this a race condition.
    It is important to keep in mind that servlets are accessed by multiple threads concurrently, so you need to make sure your servlets are thread safe. Instance variables that get modified with each request are a very bad, non-thread safe thing and will cause odd behaviour like what you are describing. I speak from experience.
    I fixed the above by removing the instance reference and doing the following:
    public class FooServlet extends HttpServlet
         doGet(HttpServletRequest req, HttpServletResponse res)
                   doStuffWithSessionData(req);
         doStuffWithSessionData(HttpServletRequest req)
              HttpSession session = req.getSession(false);
              String temp = session.getValue("temp");
              //do some stuff
              //NOTE: this works most of the time. However, if the client
              //connects with more than one browser window using the same
              //session, I could run into some trouble here too.
    }That was a quick fix. However, what I really need to do is create a separate class to encapsulate all user session data and access the session and all data through public static synchronized methods on that class, passing it the request object when I do it. That way all data is stored in one object, and that object is used to do all session access in a thread-safe, synchronized manner.
    I hope this information helps you and is understandable. If you have any questions I will try to clarify. Making things thread-safe can be a daunting task.

  • Why do I get "Error 1 occured at Config Data Registry.vi(get data) invalid object 0" while starting my application?

    Why do I get "Error 1 occured at Config Data Registry.vi(get data) invalid object 0" when starting my application created in LabVIEW 7.1?  I am starting the application in a PXI rack running Windows XP.  I have an executable written in LabVIEW 7.0 that runs without this error.  After clicking the Continue button in the error, the application seems to continue happily.
    Is there something I need to include when I make the executable?
    I would like to understand and eliminate this start up error.
    Thanks in advance.
    BobNorth

    Hi Bob,
    I looked through the program and I figured out where the error is coming from, and potentially what is causing it. In a lot of the cases of the program you are searching a 1-D array for the name of the case, and if you don't find it then it skips the function and gives "Error 1 occurred at Config Data Registry.vi(CASENAME) invalid object 0". I attached a screenshot that shows what I mean. The Search 1-D Array.vi is returning a -1 which means it didn't find the case. The reason I believe this is happening is because the shift register for that array is not initialized. While the other cases "reset" and "register" interact with the array shift registers and most likely create the array you need, if the program defaults to the "get data" case then it will try to run that before registering and won't have an array to search. This would also explain why it only has this problem at first and seems to run just fine after that. To fix this you should either make an initial array and wire it into the shift register or make the "reset" case the default as opposed to the "get data" case.
    Regards,
    Peter W.
    Attachments:
    Config Data Registry.png ‏55 KB

  • Why I get "Error in getting session data" error when running report?

    Hello,
    I have reporting services on one server, and SharePoint 2010 on other server. When I view report from browser, I got blank page. From Report Server Log file, I got below error:
    v VERBOSE: writting session cookie: ekkrjbubp00t5wzc3rzspvzb
    v VERBOSE: Saved report snapshot to session in a background thread <for same session id>
    e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database.  This may be due to a connection failure, timeout or low disk condition within the database.;
    e ERROR: Error in getting session data: Expired Session: ekkrjbubp00t5wzc3rzspvzb
    e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: The report execution ekkrjbubp00t5wzc3rzspvzb has expired or cannot be found
    Are there anyone getting the same issue as mine? I did not see any solutions for this issue when I searched.
    Thanks,
    Megan

    There are a number of timeouts in SSRS; session timeout, report execution timeouts, http request timeouts.  A session timeout in SSRS is not the same as a session timeout in ASP.NET.  Below are some articles that can help you understand the timeouts
    and hopefully lead you down the path of discovery.
    This articles is a good article as it discusses the session timeout and the keep alive that is sent from the report viewer.
    http://blogs.msdn.com/b/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
    This article is good as well in describing some of the timeouts.
    http://blogs.msdn.com/b/dynamicsaxbi/archive/2013/02/14/how-to-addressing-ssrs-session-timeouts.aspx

  • HT4157 When I click "view account" I get an error message that says "SIM is invalid; please use different SIM." What next?

    I am trying to activate a first gen iPad with WiFi and 3G. When I go to Settings, Cellular Data, and View Account to activate the iPad, I get an error message that says, "SIM is Invalid.  Pleae use a different SIM." 
    There is a SIM PIN option, and when I click that it asks for the PIN.  I don't have a PW for the SIM (the iPad was a slightly used gift, and none of the paperwork came with the iPad). 
    Any ideas on how to activate the iPAD?
    Thanks!

    Did you check your user name and password in Settings>Mail,Contacts,Calendars...tap your email account, tap SMTP, then tap the primary server name.  Make sure the settings there are correct.

  • I am getting "ORA-00900: invalid SQL statement"  error.?

    I did installed oracle 11gR2. and used "DBMS_METADATA_DIFF.COMPARE_ALTER('TABLE','TBL_A','TBL_A','USER1','USER2')"   to see the result like below,  but I am getting "ORA-00900: invalid SQL statement"  error.   Any idea?
    I am using:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE 11.2.0.1.0 Production
    TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production
    SQL> desc user1.tbl_a
    Name                                      Null?    Type
    FIELD_A1                                  NOT NULL NUMBER
    FIELD_A2                                           VARCHAR2(20)
    FIELD_A4                                  NOT NULL NUMBER(5,2)
    FIELD_A5                                           VARCHAR2(10)
    FIELD_A6                                  NOT NULL NUMBER(2)
    SQL> desc user2.tbl_a
    Name                                      Null?    Type
    FIELD_A1                                  NOT NULL NUMBER
    FIELD_A2                                           VARCHAR2(50)
    FIELD_A3                                           DATE
    FIELD_A4                                           NUMBER(5,2)
    FIELD_A5                                  NOT NULL VARCHAR2(10)
    SQL> select dbms_metadata_diff.compare_alter('TABLE','TBL_A','TBL_A','USER1','USER2') from dual
    expected result:
    DBMS_METADATA_DIFF.COMPARE_ALTER('TABLE','TBL_A','TBL_A','U1','U2')
    ALTER TABLE "U1"."TBL_A" ADD ("FIELD_A3" DATE)
      ALTER TABLE "U1"."TBL_A" DROP ("FIELD_A6")
      ALTER TABLE "U1"."TBL_A" MODIFY ("FIELD_A2" VARCHAR2(50))
      ALTER TABLE "U1"."TBL_A" MODIFY ("FIELD_A4" NUMBER(5,2) DEFAULT 0)
      ALTER TABLE "U1"."TBL_A" MODIFY ("FIELD_A4" NULL)
      ALTER TABLE "U1"."TBL_A" MODIFY ("FIELD_A5" NOT NULL ENABLE)

    Thanks for reply rp,
    I got result using "select dbms_metadata_diff.compare_alter('TABLE','TBL_A','TBL_A','USER1','USER2') from dual"

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

  • Error loading serialized session data

    Could anyone please suggest how to fix this issue. We run 2 Solaris servers
              running WL5.1 SP8:
              Thank you!
              Fri Jan 12 16:23:43 PST 2001:<E> <HttpSessionContext> Error loading
              serialized session data for session
              OlzPsQ2ZCGETxLZsvwig2hgGGyZEU4opBHfSaq1P02MlsbGKNK64QcKLS3JTa0QJZyZxdjVIY5k3
              |5212765075526534138/-1062730671/6/80/80/7002/7002/80/-1
              java.io.InvalidClassException:
              weblogic.servlet.internal.session.SessionData; Local class not compatible:
              stream classdesc serialVersionUID=2475912102520200080 local class
              serialVersionUID=8380332519449050139
              at java.lang.Throwable.fillInStackTrace(Native Method)
              at java.lang.Throwable.fillInStackTrace(Compiled Code)
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Exception.<init>(Compiled Code)
              at java.io.IOException.<init>(Compiled Code)
              at
              java.io.ObjectStreamException.<init>(ObjectStreamException.java:29)
              at
              java.io.InvalidClassException.<init>(InvalidClassException.java:47)
              at java.io.ObjectStreamClass.validateLocalClass(Compiled Code)
              at java.io.ObjectStreamClass.setClass(Compiled Code)
              at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.inputObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at
              weblogic.servlet.internal.session.FileSessionContext.loadSession(FileSession
              Context.java:467)
              at
              weblogic.servlet.internal.session.FileSessionContext.invalidateSession(FileS
              essionContext.java:391)
              at
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
              teSessions(Compiled Code)
              at
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
              SessionContext.java:479)
              at
              weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled Code)
              at weblogic.time.common.internal.ScheduledTrigger.execute(Compiled
              Code)
              at weblogic.time.server.ScheduledTrigger.execute(Compiled Code)
              at weblogic.kernel.ExecuteThread.run(Compiled Code)
              java.io.InvalidClassException:
              weblogic.servlet.internal.session.SessionData; Local class not compatible:
              stream classdesc serialVersionUID=2475912102520200080 local class
              serialVersionUID=8380332519449050139
              at java.lang.Throwable.fillInStackTrace(Native Method)
              at java.lang.Throwable.fillInStackTrace(Compiled Code)
              at java.lang.Throwable.<init>(Compiled Code)
              at java.lang.Exception.<init>(Compiled Code)
              at java.io.IOException.<init>(Compiled Code)
              at
              java.io.ObjectStreamException.<init>(ObjectStreamException.java:29)
              at
              java.io.InvalidClassException.<init>(InvalidClassException.java:47)
              at java.io.ObjectStreamClass.validateLocalClass(Compiled Code)
              at java.io.ObjectStreamClass.setClass(Compiled Code)
              at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.inputObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at java.io.ObjectInputStream.readObject(Compiled Code)
              at
              weblogic.servlet.internal.session.FileSessionContext.loadSession(FileSession
              Context.java:467)
              at
              weblogic.servlet.internal.session.FileSessionContext.invalidateSession(FileS
              essionContext.java:391)
              at
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
              teSessions(Compiled Code)
              at
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
              SessionContext.java:479)
              at
              weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled Code)
              at weblogic.time.common.internal.ScheduledTrigger.execute(Compiled
              Code)
              at weblogic.time.server.ScheduledTrigger.execute(Compiled Code)
              at weblogic.kernel.ExecuteThread.run(Compiled Code)
              

    It might cause by inconsistent service patch and/or versions among your
              servers in your cluster. Double check the installation, especially
              classpathes of all your servers. Make sure you apply SP8 correctly in all
              servers.
              Cheers - Wei
              "Andre Taube" <[email protected]> wrote in message
              news:[email protected]...
              > Could anyone please suggest how to fix this issue. We run 2 Solaris
              servers
              > running WL5.1 SP8:
              >
              > Thank you!
              >
              >
              > Fri Jan 12 16:23:43 PST 2001:<E> <HttpSessionContext> Error loading
              > serialized session data for session
              >
              OlzPsQ2ZCGETxLZsvwig2hgGGyZEU4opBHfSaq1P02MlsbGKNK64QcKLS3JTa0QJZyZxdjVIY5k3
              > |5212765075526534138/-1062730671/6/80/80/7002/7002/80/-1
              > java.io.InvalidClassException:
              > weblogic.servlet.internal.session.SessionData; Local class not compatible:
              > stream classdesc serialVersionUID=2475912102520200080 local class
              > serialVersionUID=8380332519449050139
              > at java.lang.Throwable.fillInStackTrace(Native Method)
              > at java.lang.Throwable.fillInStackTrace(Compiled Code)
              > at java.lang.Throwable.<init>(Compiled Code)
              > at java.lang.Exception.<init>(Compiled Code)
              > at java.io.IOException.<init>(Compiled Code)
              > at
              > java.io.ObjectStreamException.<init>(ObjectStreamException.java:29)
              > at
              > java.io.InvalidClassException.<init>(InvalidClassException.java:47)
              > at java.io.ObjectStreamClass.validateLocalClass(Compiled Code)
              > at java.io.ObjectStreamClass.setClass(Compiled Code)
              > at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.inputObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at
              >
              weblogic.servlet.internal.session.FileSessionContext.loadSession(FileSession
              > Context.java:467)
              > at
              >
              weblogic.servlet.internal.session.FileSessionContext.invalidateSession(FileS
              > essionContext.java:391)
              > at
              >
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
              > teSessions(Compiled Code)
              > at
              >
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
              > SessionContext.java:479)
              > at
              > weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled
              Code)
              > at weblogic.time.common.internal.ScheduledTrigger.execute(Compiled
              > Code)
              > at weblogic.time.server.ScheduledTrigger.execute(Compiled Code)
              > at weblogic.kernel.ExecuteThread.run(Compiled Code)
              >
              > java.io.InvalidClassException:
              > weblogic.servlet.internal.session.SessionData; Local class not compatible:
              > stream classdesc serialVersionUID=2475912102520200080 local class
              > serialVersionUID=8380332519449050139
              > at java.lang.Throwable.fillInStackTrace(Native Method)
              > at java.lang.Throwable.fillInStackTrace(Compiled Code)
              > at java.lang.Throwable.<init>(Compiled Code)
              > at java.lang.Exception.<init>(Compiled Code)
              > at java.io.IOException.<init>(Compiled Code)
              > at
              > java.io.ObjectStreamException.<init>(ObjectStreamException.java:29)
              > at
              > java.io.InvalidClassException.<init>(InvalidClassException.java:47)
              > at java.io.ObjectStreamClass.validateLocalClass(Compiled Code)
              > at java.io.ObjectStreamClass.setClass(Compiled Code)
              > at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.inputObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at java.io.ObjectInputStream.readObject(Compiled Code)
              > at
              >
              weblogic.servlet.internal.session.FileSessionContext.loadSession(FileSession
              > Context.java:467)
              > at
              >
              weblogic.servlet.internal.session.FileSessionContext.invalidateSession(FileS
              > essionContext.java:391)
              > at
              >
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
              > teSessions(Compiled Code)
              > at
              >
              weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
              > SessionContext.java:479)
              > at
              > weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled
              Code)
              > at weblogic.time.common.internal.ScheduledTrigger.execute(Compiled
              > Code)
              > at weblogic.time.server.ScheduledTrigger.execute(Compiled Code)
              > at weblogic.kernel.ExecuteThread.run(Compiled Code)
              >
              >
              

  • "Could not deserialize session data" error during sign out

    Hello,
    I have an application deployed on WLS 8.1, one instance, no clustering. The application EAR contains 1 web module and 2 ejb modules. When I try to sign out(I use Single Sign-On for Multiple Applications - a sign out application deployed separately) I receive the attached error.
    Notes: my session is serializable - I did a test that serialize and deserialize the session and I have no errors.
    Q: Why does WLS try to deserialize the session data during sign out? I don't use any session persistance/replication.
    The error ClassNotFoundException from my point of view is normal: UsersTableModel(from web modile) is not visible from the Application Classloader.
    Here is the error:
    <> <BEA-100028> <Could not deserialize session data.
    java.lang.ClassNotFoundException: xxx.controller.actions.UsersTableModel: 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(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;Z)Ljava.lang.Class;(ApplicationManager.java:344)
         at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.ClassLoader;)Ljava.lang.Class;(ApplicationManager.java:258)
         at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:253)
         at weblogic.j2ee.ApplicationManager.loadClass(Ljava.lang.String;Ljava.lang.String;)Ljava.lang.Class;(ApplicationManager.java:216)
         at weblogic.common.internal.WLObjectInputStream.resolveClass(Ljava.io.ObjectStreamClass;)Ljava.lang.Class;(WLObjectInputStream.java:48)
         at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
         at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
         at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
         at weblogic.servlet.internal.AttributeWrapper.convertBytesToObject([B)Ljava.lang.Object;(AttributeWrapper.java:173)
         at weblogic.servlet.internal.AttributeWrapper.getObject(Z)Ljava.lang.Object;(AttributeWrapper.java:114)
         at weblogic.servlet.internal.AttributeWrapper.getObject()Ljava.lang.Object;(AttributeWrapper.java:69)
         at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;Z)Ljava.lang.Object;(SessionData.java:614)
         at weblogic.servlet.internal.session.SessionData.removeAttribute(Ljava.lang.String;)V(SessionData.java:596)
         at weblogic.servlet.internal.session.SessionData.remove()V(SessionData.java:808)
         at weblogic.servlet.internal.session.MemorySessionContext.invalidateSession(Lweblogic.servlet.internal.session.SessionData;)Z(MemorySessionContext.java:69)
         at weblogic.servlet.internal.session.SessionData.invalidate()V(SessionData.java:750)
         at weblogic.servlet.security.ServletAuthentication.invalidateAll(Ljavax.servlet.http.HttpServletRequest;)Z(ServletAuthentication.java:184)
         at xxx.framework.authentication.WebAuthenticationHelper.invalidateSessions(Ljavax.servlet.http.HttpServletRequest;)V(WebAuthenticationHelper.java:574)
         at xxx.framework.authentication.WebAuthenticationHelper.closeSession(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:523)
         at xxx.framework.authentication.WebAuthenticationHelper.logout(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebAuthenticationHelper.java:250)
         at xxx.yyy.ViewDispatcher.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:75)
         at xxx.yyy.ViewDispatcher.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ViewDispatcher.java:42)
         at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:996)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:419)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
    Edited by: user11291053 on 22-Jun-2009 02:52
    Edited by: user11291053 on 22-Jun-2009 03:01
    Edited by: user11291053 on 23-Jun-2009 01:42

    When OptimisticSerialization is turned on, WebLogic server does not serialize-deserialize context and request attributes upon getAttribute(name) when a request gets dispatched across servlet contexts. This means you will need to make sure that the attributes common to Web applications are scoped to a common parent classloader (they are application-scoped) or placed in the system classpath if the two Web applications do not belong to the same application.
    When OptimisticSerialization is turned off (which is the default) WebLogic Server does serialize-deserialize context and request attributes upon getAttribute(name) to avoid the possibility of ClassCastExceptions. The value of OptimisticSerialization can also be overridden for specific Web applications by setting the optimistic-serialization value in weblogic.xml.
    [http://edocs.bea.com/wls/docs100/ConsoleHelp/pagehelp/Corecoredomaindomainconfigwebapptitle.html]
    [http://e-docs.bea.com/wls/docs90/webapp/weblogic_xml.html#1067857]
    I hope this helps :)

  • Getting error while uploading gl master data using LSMW batch input data

    Hi Experts,
    I am getting error while uploading the GL master data through lsmw using batch input recording.
    After completion of all steps at the time of running batch input session error i am getting is "maintain EN language discription"
    and Pls tell me is it possible to upload transactional data using lsmw? if yes pls explaing briefly.

    Hello,
    Kindly post in the FI forum to get a better response.
    Regarding the issue you might check whether the correct column is being picked up where you have maintained the description.
    Kind Regards // Shaubhik

  • "Could not deserialize session data" error during shutdown WLS 6.0SP2

              Hello all,
              I get this Error ("Could not deserialize session data") when shutting down WLS
              6.0 SP2.
              I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to use memory-based
              storage for session data. So WLS should not try to serialize the session and save
              it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
              methods and realized that WLS calls writeObject on all in the session saved objects
              and readObject directly afterwards. Here's the stackTrace:
              ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
              AttributeWrapper.getObject()
              SessionData.removeAttribute()
              SessionData.removeValue()
              SessionData.remove()
              MemorySessionContext.invalidateSession()
              MemorySessionContext.shutDown()
              WebAppServletContext.destroyServlets()
              HttpServer.destroyServlets()
              HttpServer.shutDown()
              WebService.shutDown()
              ServerServiceList.shutDown()
              T3srvr.die()
              T3srvr.waitForDeath()
              T3srvr.run()
              Server.main()
              I do save some objects which are not Serializable in the session. I understand
              that session data can be made persistent in a file/jdbc and then the objects must
              be Serializable but not when saving the session data in memory.
              Why is WLS trying to Serialize the Session Data and how can I switch it off ?
              The Documentation says that it is allowed to store any object in the sessio, as
              long as it is not persistet.
              Thanks for your help,
              Oliver
              [weblogic.xml]
              

              Hello Oliver & All-
              Did anyone ever make any progress with this question, or come up with an answer?
              I've found similar behavior when properly shuting down a WLS server with this command:
              java -classpath $CLASSPATH weblogic.Admin -url t3://localhost:7001 -username <user>
              -password <passwd> SHUTDOWN
              TIA.
              --oliver.
              "Oliver Seiler" <[email protected]> wrote:
              >
              >Hello all,
              >
              >I get this Error ("Could not deserialize session data") when shutting down
              >WLS
              >6.0 SP2.
              >I set the property 'PersistentStoreType' to 'memory' in weblogic.xml to
              >use memory-based
              >storage for session data. So WLS should not try to serialize the session
              >and save
              >it to disk (and I didn't find any files). I set a breakpoint in the writeObject()/readObject()
              >methods and realized that WLS calls writeObject on all in the session saved
              >objects
              >and readObject directly afterwards. Here's the stackTrace:
              >
              >ObjectOutputStream.writeObject()/ObjectOutputStream.readObject()
              >AttributeWrapper.getObject()
              >SessionData.removeAttribute()
              >SessionData.removeValue()
              >SessionData.remove()
              >MemorySessionContext.invalidateSession()
              >MemorySessionContext.shutDown()
              >WebAppServletContext.destroyServlets()
              >HttpServer.destroyServlets()
              >HttpServer.shutDown()
              >WebService.shutDown()
              >ServerServiceList.shutDown()
              >T3srvr.die()
              >T3srvr.waitForDeath()
              >T3srvr.run()
              >Server.main()
              >
              >I do save some objects which are not Serializable in the session. I understand
              >that session data can be made persistent in a file/jdbc and then the objects
              >must
              >be Serializable but not when saving the session data in memory.
              >Why is WLS trying to Serialize the Session Data and how can I switch it
              >off ?
              >The Documentation says that it is allowed to store any object in the sessio,
              >as
              >long as it is not persistet.
              >
              >Thanks for your help,
              > Oliver
              >
              

  • Error reading stored session data

    CF8/IIS6/Win2k3
    getting a ton of these messages:
    04/02 15:00:39 error Error reading stored session data
    (ID=70307b52029b2dd2dadc1f364fe3e4c3463e)
    java.io.StreamCorruptedException: unexpected end of block
    data
    at
    java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
    at
    java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
    at
    java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
    at
    java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at
    java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at
    java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at java.util.ArrayList.readObject(ArrayList.java:593)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
    at
    java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
    at
    java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at
    java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at
    java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
    at
    java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
    at
    java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at
    java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at
    java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at
    coldfusion.runtime.SessionScope.readObject(SessionScope.java:211)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
    at
    java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
    at
    java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at
    java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at
    java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
    at
    java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:480)
    at
    coldfusion.runtime.J2eeSessionScopeStub.readObject(J2eeSessionScopeStub.java:86)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
    at
    java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
    at
    java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at
    java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at
    java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at java.util.Hashtable.readObject(Hashtable.java:859)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at
    java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
    at
    java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
    at
    java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at
    java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at
    java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at
    jrun.servlet.session.SessionService.retrieve(SessionService.java:1357)
    at
    jrun.servlet.session.SessionService.retrieve(SessionService.java:1341)
    at
    jrun.servlet.session.SessionService.restoreSession(SessionService.java:1259)
    at
    jrun.servlet.session.SessionService.restoreSessionState(SessionService.java:876)
    at
    jrun.servlet.session.SessionService.setClassLoader(SessionService.java:504)
    at
    jrun.servlet.WebApplicationService.postStart(WebApplicationService.java:300)
    at
    jrun.ea.EnterpriseApplication.start(EnterpriseApplication.java:203)
    at
    jrun.deployment.DeployerService.initModules(DeployerService.java:708)
    at
    jrun.deployment.DeployerService.createWatchedDeployment(DeployerService.java:243)
    at
    jrun.deployment.DeployerService.deploy(DeployerService.java:428)
    at
    jrun.deployment.DeployerService.checkWatchedDirectories(DeployerService.java:179)
    at
    jrun.deployment.DeployerService.run(DeployerService.java:889)
    at
    jrunx.scheduler.SchedulerService.invokeRunnable(SchedulerService.java:230)
    at
    jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
    Here is the arguments line in my jvm:
    # Arguments to VM
    java.args=-server -Xmx512m -Xms512m -XX:MaxNewSize=24m
    -XX:NewSize=24m -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled
    -XX:+UseConcMarkSweepGC -Dsun.io.useCanonCaches=false -Xdebug
    -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=2702
    -Dcoldfusion.rootDir={application.home}/

    Beyond this I have not been able to identify or figure out
    what is causing the issue. I did a double check and some of the
    times are outside of our nightly back-up schedule. It looks like
    this issue hasn't happend for me since 27 Aug. I couldn't say why
    though. I'm hoping Adobe has an answer.
    Thx

Maybe you are looking for