Return-Path: 
 <dev-return-48164-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C562B17468
	for <apmail-activemq-dev-archive@www.apache.org>;
 Tue, 20 Jan 2015 01:45:32 +0000 (UTC)
Received: (qmail 13892 invoked by uid 500); 20 Jan 2015 01:45:34 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 13827 invoked by uid 500); 20 Jan 2015 01:45:34 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 13816 invoked by uid 99); 20 Jan 2015 01:45:34 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jan 2015 01:45:34 +0000
Date: Tue, 20 Jan 2015 01:45:34 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12768568.1421712887000.120486.1421718334705@Atlassian.JIRA>
In-Reply-To: <JIRA.12768568.1421712887000@Atlassian.JIRA>
References: <JIRA.12768568.1421712887000@Atlassian.JIRA>
 <JIRA.12768568.1421712887543@arcas>
Subject: [jira] [Closed] (AMQ-5528) Connection Factory Properties not
 effective for MDB
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/AMQ-5528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-5528.
-----------------------------
    Resolution: Invalid

Questions like these should go to the users mailing list, if a real problem is identified then an issue can be opened with reproducer tests and detailed problem descriptions. 

> Connection Factory Properties not effective for MDB
> ---------------------------------------------------
>
>                 Key: AMQ-5528
>                 URL: https://issues.apache.org/jira/browse/AMQ-5528
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JCA Container
>    Affects Versions: 5.10.0
>         Environment: glassfish >= 3.1
> activemq-5.10.0
> project jee >=5
> activemq-ra.5.10.0.rar
> ear + ejb + mdb +servlet
>            Reporter: hhfrancois
>
> In glassfish deploy activemq-ra
> create jms connectorFactory jms/testConnectionFactory
> with property serverUrl = activemqUrl
> create jms queue jms/testQueue
> create sessionBean producer with injecteds resources jms/testConnectionFactory and testQueue.
> create servlet for launch producer.
> This works.
> But now create MDB with  Activation Spec Properties
> *destination = "jms/testQueue"*
> *destinationType = "Queue"*
> in glassfish-ejb-jar.xml configure the mdb 
> {code:xml:title=glassfish-ejb-jar.xml|borderStyle=solid}
> <enterprise-beans>
>    <ejb>
>       <ejb-name>MDB-NAME<ejb-name>
>       <mdb-connection-factory>
>           <jndi-name>jms/testConnectionFactory</jndi-name>
>       </mdb-connection-factory>
>    </ejb>
> </enterprise-beans>
> {code}
> the MDB doesnt work, I can't use the connectionFactory for MDB why ?
> This technic works perfectly with openMQ but not with activeMQ
> If I place the conguration on resource-adapter with  Resource Adapter Properties and define in glassfish-ejb-jar.xml 
> {code:xml:title=glassfish-ejb-jar.xml|borderStyle=solid}
> <enterprise-beans>
>    <ejb>
>       <ejb-name>MDB-NAME<ejb-name>
>       <mdb-resource-adapter>
>          <resource-adapter-mid>activemq-ra.5.10.0</resource-adapter-mid>
>       </mdb-resource-adapter>
>    </ejb>
> </enterprise-beans>
> {code}
> this works, but If I want to use 2 differents business activemq for 1 application, how I do ? 
> The solution is deploy 2 or more resource-adapter, but this is unstable and ugly. The logic is I deploy 1 resource-adapter and configure separatly 2 connectionFactories/pools.
> When I look sources of ra, I feel that the MDB doesn't use ra connectionFactory config in glassfish. just adapter config and spec from MDB.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)