Home → Bug Reports →

An error occurred: possible nonthreadsafe access to session

• Edit

espanae

30 Oct, 2014 03:36 PM

A page, in our Cascade Server 7.8 production instance, is not allowing us to activate previous versions. Instead we get the following error message:
An error occurred: possible nonthreadsafe access to session

We're able to activate previous versions of other pages, templates and formats. Here's the published version of the page:
http://www.union.edu/offices/international/index.php

Where should I start troubleshooting this?

• possible_nonthreadsafe_access_to_session.gif 6.38 MB

1. Support Staff 1 Posted by Tim on 30 Oct, 2014 07:12 PM

   

   Hi,

   When you have the chance, can you please replicate that error and then immediately attach your most recent cascade.log file?

   Thanks!

   • Edit

2. 2 Posted by espanae on 31 Oct, 2014 01:33 PM

   

   Hi Tim,
   I got the error again this morning and immediately downloaded the cascade.log file.

   Thanks,
   Erik

   • cascade.log.zip 23.5 KB
   • Edit

3. Support Staff 3 Posted by Tim on 31 Oct, 2014 01:45 PM

   

   Thanks for attaching that log file, Erik. It looks like this message is coinciding with the following error:
   

   2014-10-31 09:23:08,312 ERROR [JDBCExceptionReporter] Cannot delete or update a parent row: a foreign key constraint fails (cascade.cxml_structureddata, CONSTRAINT FK_SDATA_NEXT FOREIGN KEY (structuredDataId) REFERENCES cxml_structureddata (id))
   

   This was a known issue that was fixed for 7.8.2. Do you have an upgrade of the software planned any time soon? Let me know.

   Thanks!

   • Edit

4. 4 Posted by espanae on 31 Oct, 2014 02:35 PM

   

   Hi Tim,
   Our next upgrade (to 7.12.2) is planned for December. In the meantime, is there a way to temporarily fix this through MySQL?

   • Edit

5. Support Staff 5 Posted by Tim on 31 Oct, 2014 03:10 PM

   

   Hmm, I looked around but I'm not seeing any explicit steps that will fix this. You could try the following:

   • Create a backup of your database (to be safe!)
   • Run the Optimize Database tool (System Menu -> Utilities -> Database Tools) with the following options selected:
     • Remove orphaned records
     • Repair Structured Data

   If that doesn't correct the issue, an upgrade will be the only way to resolve this problem. Perhaps you all could upgrade to the latest 7.8.x version now and then 7.12.x in December? Let me know how things go.

   Thanks

   • Edit

6. 6 Posted by espanae on 31 Oct, 2014 04:04 PM

   

   Okay, the problem may be manageable until our planned upgrade in December. I'll let you know how it goes.

   Thanks,
   Erik

   • Edit

7. espanae closed this discussion on 31 Oct, 2014 04:04 PM.