activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Bausewein <ha...@comerwell.xs4all.nl>
Subject Re: JBoss Integration - recovering XAResource
Date Mon, 20 Oct 2008 18:47:05 GMT


rball wrote:
> 
> Question: Is the a way to clear the "persistent" Warning "Could not find
> new XAResource to use for recovering non-serializable XAResource" that
> keep comming up over and over, even after a server restart?
> 


I don't get these warnings with XA transactions on JBoss 4.0.5 and 4.2.3

The only warning in my log was:


2008-10-19 23:22:58,083 WARN 
[com.arjuna.ats.jbossatx.jta.TransactionManagerService]
XAExceptionFormatters are not supported by the JBossTS Transaction Service -
this warning can safely be ignored

You can download a small test EJB app, here:

  https://issues.apache.org/activemq/browse/AMQ-1983

It links to this "container-configuration":

    <container-configuration>
       <container-name>ActiveMQ Message Driven Bean</container-name>
       <call-logging>false</call-logging>
      
<invoker-proxy-binding-name>activemq-message-driven-bean</invoker-proxy-binding-name>
       <container-interceptors>
         
<interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
          <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
         
<interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor>
          <!-- CMT -->
          <interceptor
transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
          <interceptor
transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
          <interceptor transaction="Container"
metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
          <interceptor
transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
          <!-- BMT -->
          <interceptor
transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
          <interceptor
transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
          <interceptor
transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
          <interceptor transaction="Bean"
metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
         
<interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
       </container-interceptors>
      
<instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
       <instance-cache></instance-cache>
       <persistence-manager></persistence-manager>
       <container-pool-conf>
          <MaximumSize>100</MaximumSize>
       </container-pool-conf>
    </container-configuration>

which is linked to this "invoker-proxy-binding":

    <invoker-proxy-binding>
       <name>activemq-message-driven-bean</name>
       <invoker-mbean>default</invoker-mbean>
      
<proxy-factory>org.jboss.ejb.plugins.inflow.JBossMessageEndpointFactory</proxy-factory>
       <proxy-factory-config>
          <activation-config>
           <activation-config-property>
             
<activation-config-property-name>maxSessions</activation-config-property-name>
             
<activation-config-property-value>15</activation-config-property-value>
           </activation-config-property>
          </activation-config>
          <MDBConfig>
            <ReconnectIntervalSec>10</ReconnectIntervalSec>
            <DLQConfig>
              <DestinationQueue>activemq/queue/DLQ</DestinationQueue>
              <MaxTimesRedelivered>5</MaxTimesRedelivered>
              <TimeToLive>0</TimeToLive>
            </DLQConfig>
          </MDBConfig>
          <endpoint-interceptors>
            
<interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
            
<interceptor>org.jboss.ejb.plugins.inflow.MessageEndpointInterceptor</interceptor>
            
<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
            
<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
          </endpoint-interceptors>
       </proxy-factory-config>
    </invoker-proxy-binding>

( Both in conf/standardjboss.xml )

I've moved the "<activation-config>" from "ejb-jar.xml" to "jboss.xml",
because I think it belongs there.

If anyone finds an error, please reply. I'm also quite new to this.

I'm not sure whether JBoss has enough information to use the XA connection
factory for the MDB.

The "sun-ejb-jar.xml" (for GlassFish) has an "mdb-connection-factory" entry:

                <mdb-connection-factory>
                        <jndi-name>activemq/XAConnectionFactory</jndi-name>
                </mdb-connection-factory>

(BTW: in the tar it was set to "activemq/XAConnectionFactory")

Hans

-- 
View this message in context: http://www.nabble.com/JBoss-Integration---recovering-XAResource-tp20035573p20076233.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message