• Post Reply Bookmark Topic Watch Topic
  • New Topic

message driven bean not bind to destination!  RSS feed

 
kevin chang
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i have correctly named Connection Factory and Destination name, but the message driven bean still not bind to JMS, the status of the bean is not alive. when i write a client to send message , it just got in JMS, but no consumer in JMS . Can anyone give me some suggestion? thanks
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, have you written a consumer for the destination?
 
kevin chang
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i think it should message driven bean to do as a consumer and show something here, else what's the role of message driven bean. A message send to appserver and a consumer got it, nothing happened to the bean. I got confused , some suggestion?
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, if you know you have an MDB configured to listen the destination and you know you sent a message into that destination, there's not much I can say. Have you set some kind of filtering properties for the MDB or some other, optional configurations? It might be a good idea to strip down anything that is not mandatory and see whether it works end-to-end then.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
By the way, do you have access to some kind of a management console where you could see some monitoring statistics for your JMS destination? From there you would see how many messages are pending or have been processed.
 
kevin chang
Ranch Hand
Posts: 64
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
yes, I could see the received messaged in monitoring status in destinations, but there is nothing happened to MDB. As a listener , i think it should consumer the message, but it didn't work well. By the way, should also config session pools? I just config Connection pools and JMS server and the destinations in JMS server , and name MDB with that connection pool and destination , is that right?
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The needed configuration items depend on your application server. You might want to browse the specific product's forum.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!