search

awslabs / amazon-sqs-java-messaging-lib

This Amazon SQS Java Messaging Library holds the Java Message Service compatible classes, that are used for communicating with Amazon Simple Queue Service.
http://aws.amazon.com/sqs
Apache License 2.0
167 stars 146 forks source link

Support MDB #2

Closed lowecg closed 1 year ago

lowecg commented 9 years ago

I've attempted to configure this library with Wildfly 8.2.0 using its generic JMS support. The generic JMS glue code makes some calls to the following methods which raise "method not supported" exceptions:

com.amazon.sqs.javamessaging.SQSSession#setMessageListener com.amazon.sqs.javamessaging.SQSConnection#createConnectionConsumer(javax.jms.Queue, java.lang.String, javax.jms.ServerSessionPool, int)

Without support for MDB, this library does not support enough of the JMS feature set to consider using this library over our regular JMS brokers.

aws-bilgin commented 9 years ago

Thanks for the feedback! It really helps us for our planning of how best to meet customer needs. I would like to ask some follow-up questions: 1-) What is your current JMS provider? 2-) Does your set-up requires JNDI support as well? 3-) Are you using message selectors or it is just a placeholder?

lowecg commented 9 years ago

Sorry for the delay in replying.

1) Our current provider is JBoss HornetQ 2) Yes it does, but this is managed by adding a JBoss module to Wildfly that contains an implementation of ObjectFactory to create connection factory and queue references. 3) We're not using message selectors at this time (but it would be nice to know they are there for future use)

mikesir87 commented 8 years ago

I, too, would be interested in this. Here's my answers too (in case it matters):

1) Also using HornetQ, but have also used ActiveMQ. 2) We are creating the queues in the container, placing them at global JNDI references. Then, in jboss-web.xml, creating local references that the app then binds to. So, app doesn't know global names, but the aliased names. 3) No. Not using message selectors.

beikov commented 8 years ago

1) Using ActiveMQ 2) Yes 3) No, but future support for selectors would be very nice

Is MDB support something you are considering already or do you need more people requesting that feature?

Mobe91 commented 6 years ago

I am also in need of proper MDB support:

  1. Just started to build JMS into our system so there is no current provider
  2. Yes
  3. No, but would be nice