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

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956739#3956739

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956739


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to