Return-Path: 
 <users-return-16531-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: (qmail 71680 invoked from network); 20 Oct 2008 18:47:38 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 20 Oct 2008 18:47:38 -0000
Received: (qmail 62188 invoked by uid 500); 20 Oct 2008 18:47:40 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 61865 invoked by uid 500); 20 Oct 2008 18:47:38 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 61854 invoked by uid 99); 20 Oct 2008 18:47:38 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2008 11:47:38 -0700
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2008 18:46:28 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1KrzmT-0006F1-P7
	for users@activemq.apache.org; Mon, 20 Oct 2008 11:47:05 -0700
Message-ID: <20076233.post@talk.nabble.com>
Date: Mon, 20 Oct 2008 11:47:05 -0700 (PDT)
From: Hans Bausewein <hansb@comerwell.xs4all.nl>
To: users@activemq.apache.org
Subject: Re: JBoss Integration - recovering XAResource
In-Reply-To: <20042333.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: hansb@comerwell.xs4all.nl
References: <20035573.post@talk.nabble.com> <20036449.post@talk.nabble.com>
 <20042333.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org



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.