2 Replies Latest reply on Jul 12, 2006 4:22 AM by Adi Kalamaro

    No transaction manager provided

    Adi Kalamaro Newbie

      Hi
      it seems that for about 3 weeks I can't find solution to my problem
      I tried to deploy Jboss portal - jboss-portal-2.2.1-SP1 on jboss-4.0.4.GA and I get

      Reason: java.lang.IllegalArgumentException: No transaction manager provided
      I Depend On:
      portal:policy=JaccPortalPolicyConfigurator
      portal:service=TreeCacheProvider,type=transient
      portal:policy=PortalPolicyConfigService
      Depends On Me:
      portal:deploymentFactory=PortletApp

      I don't know what to do I tried to work with Hypersonic (in addition to Oracle 10) and it's not working too there are probably some files that I need to config and I don't know which axactly.

      I hope that you can help me because I was looking for solution since now and I couldn't find.

      Thanks

        • 1. Re: No transaction manager provided
          Mineto Kariya Newbie

          I was getting exactly same error when trying to run jboss-4.0.4.GA with portal-2.2 with MySql 5.0.22.

          Easy way I got around this issue is by simply downloading and deploying the bundled SP2 portal zip.

          However, I was really puzzled as to why the non-bundled deployment was not working. FYI, I am not an expert, so the steps I relate below to get the non-bundled release may not be 100% kosher.

          It seems that the TransationManager was somehow not being recognized. Comparing the *xml files betweens the non-bundled and the bundled jboss-4.0.4.GA releases, it appears that the TransactionManager is defined in different places. The nonbundled release has it defined in deploy/jta-service.xml, whereas the bundled release has it defined in conf/jboss-service.xml.

          Since it's the bundled release that works fine, this is what I did: I simply copied the definition for the XidFactory and TransactionManager services from the bundled release into the conf/jboss-service.xml for nonbundled release, and then removed the deploy/jta-service.xml for the nonbunlded release.

          That is, in addition to removing deploy/jta-service.xml, I simply added the following lines into the conf/jboss-service.xml:

           <!-- The configurable Xid factory. For use with Oracle, set pad to true -->
           <mbean code="org.jboss.tm.XidFactory"
           name="jboss:service=XidFactory">
           <!--attribute name="Pad">true</attribute-->
           </mbean>
          
           <!--
           | The fast in-memory transaction manager.
           -->
           <mbean code="org.jboss.tm.TransactionManagerService"
           name="jboss:service=TransactionManager"
           xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
           <attribute name="TransactionTimeout">300</attribute>
           <!-- set to false to disable transaction demarcation over IIOP -->
           <attribute name="GlobalIdsEnabled">true</attribute>
           <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
          
           <!-- Transaction Integrity Checking -->
           <!-- Force a rollback if another thread is associated with the transaction at commi
          t -->
           <!--depends optional-attribute-name="TransactionIntegrityFactory"
           proxy-type="org.jboss.tm.integrity.TransactionIntegrityFactory">
           <mbean code="org.jboss.tm.integrity.FailIncompleteTransaction"
           name="jboss:service=TransactionManager,plugin=TransactionIntegrity"/>
           </depends-->
           </mbean>
          


          • 2. Re: No transaction manager provided
            Adi Kalamaro Newbie

            araiguma thanks a lot!!

            I saw your answer just now, it's woking! till now I didn't find any solution

            I realy appriciate it!