Results 1 to 2 of 2

Thread: MDB, WMQ, and JmsGatewaySupport

  1. #1
    Join Date
    May 2006
    Posts
    15

    Default MDB, WMQ, and JmsGatewaySupport

    I'm trying to use Spring's JmsGatewaySupport with WMQ and JBoss to create a JMS Router. But I receive an WMQ error "MQJE001: Completion Code 2, Reason 2072". IBM states that this is due to caching of the session object. Has anyone been able to use this with the above configuration?

    Here's a link to IBM's description of the problem:

    http://www-1.ibm.com/support/docview...id=swg21202628

  2. #2
    Join Date
    Jul 2005
    Posts
    105

    Default

    Are you running under a global transaction when you're doing this? It could be related to the way the Session is retrieved from the TransactionSynchronizationManager... although I wouldn't think that this would be the case. Can you post the offending code?

    Also, are you using MDBs for this? JmsGatewaySupport is more for outwardly-initiated queue operations rather than inbound processing. If you were using message-driven POJOs, I can tell you that DefaultMessageListenerContainer by default shares Connection objects between concurrent consumer calls. With WMQ, you must set sharedConnectionEnabled to false.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •