You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Dev Null 52 (JIRA)" <ji...@apache.org> on 2016/12/03 19:59:58 UTC

[jira] [Updated] (TOMEE-1977) MDB not listening to ActiveMQ messages

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

Dev Null 52 updated TOMEE-1977:
-------------------------------
    Description: 
I have been trying for couple of days to have a trivial MDB to listed on ActiveMQ Queue. I am using TomEE 7.0.2.

I tried first using an embedded Active MQ 5.2.0 broker, then moved it as a stand alone process using activemq-maven-plugin plugin.

I tried MDB with annotation using activation config, without annotation but no avail. Examples online vary and none of them appear to work. I am able to send to the Queue using a seperate Servlet and able to validate then but not able to read.

Also I am seeing very strange Auto-linking resource-ref logs whereby I see injections for Beans that do not have those instances/types defined -- so very confused.

Plain JMS and EJB worked like a charm on JEE. Please help if possible.

> MDB not listening to ActiveMQ messages
> --------------------------------------
>
>                 Key: TOMEE-1977
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1977
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 7.0.2
>         Environment: local
>            Reporter: Dev Null 52
>
> I have been trying for couple of days to have a trivial MDB to listed on ActiveMQ Queue. I am using TomEE 7.0.2.
> I tried first using an embedded Active MQ 5.2.0 broker, then moved it as a stand alone process using activemq-maven-plugin plugin.
> I tried MDB with annotation using activation config, without annotation but no avail. Examples online vary and none of them appear to work. I am able to send to the Queue using a seperate Servlet and able to validate then but not able to read.
> Also I am seeing very strange Auto-linking resource-ref logs whereby I see injections for Beans that do not have those instances/types defined -- so very confused.
> Plain JMS and EJB worked like a charm on JEE. Please help if possible.



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