<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Nested transactions and failure of services in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/nested-transactions-and-failure-of-services/m-p/236993#M190123</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Some pointers, since I've been struggling with this myself recently. :? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can't have "nested transactions" in the sense you are asking,&amp;nbsp; each thread only has a single active transaction context.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;However you can suspend one transaction and run another.&amp;nbsp;&amp;nbsp; You can "push" and "pop" transaction contexts.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any exception is best considered fatal to your transaction,&amp;nbsp; the decision is not yours to decide to catch and commit.&amp;nbsp;&amp;nbsp;&amp;nbsp; You are rolling back whether you like it or not.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So one easy improvement for your problem is to do a check for whether the space exists before creating it.&amp;nbsp;&amp;nbsp; Then you won't be attempting to handle the FileExistsException.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Jun 2009 23:02:38 GMT</pubDate>
    <dc:creator>mrogers</dc:creator>
    <dc:date>2009-06-19T23:02:38Z</dc:date>
    <item>
      <title>Nested transactions and failure of services</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/nested-transactions-and-failure-of-services/m-p/236992#M190122</link>
      <description>Hi all,I have been facing a problem with transactions at the worst moment: everything was fine but falls apart just days before the final delivery of a project based on Alfresco.Exact details would be too long so I'll just give a general picture. We are storing data into an Alfresco repository throu</description>
      <pubDate>Mon, 15 Jun 2009 14:25:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/nested-transactions-and-failure-of-services/m-p/236992#M190122</guid>
      <dc:creator>amenel</dc:creator>
      <dc:date>2009-06-15T14:25:18Z</dc:date>
    </item>
    <item>
      <title>Re: Nested transactions and failure of services</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/nested-transactions-and-failure-of-services/m-p/236993#M190123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Some pointers, since I've been struggling with this myself recently. :? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can't have "nested transactions" in the sense you are asking,&amp;nbsp; each thread only has a single active transaction context.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;However you can suspend one transaction and run another.&amp;nbsp;&amp;nbsp; You can "push" and "pop" transaction contexts.&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any exception is best considered fatal to your transaction,&amp;nbsp; the decision is not yours to decide to catch and commit.&amp;nbsp;&amp;nbsp;&amp;nbsp; You are rolling back whether you like it or not.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So one easy improvement for your problem is to do a check for whether the space exists before creating it.&amp;nbsp;&amp;nbsp; Then you won't be attempting to handle the FileExistsException.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2009 23:02:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/nested-transactions-and-failure-of-services/m-p/236993#M190123</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2009-06-19T23:02:38Z</dc:date>
    </item>
  </channel>
</rss>

