Posted: Sat May 01, 2004 4:16 pm Post subject: session bean transaction attribute and sending messages
Newbie
Joined: 30 Jan 2004 Posts: 7
Hi,
My environment is Websphere 5.0 and mQ5.3. I am using a stateless session bean to send messages to mq. I can see in my logger messages that the msg id is generated but it is not in the queue. I didn't specify transaction attribute since I don't need it. What needs to be done to solve this problem.
Thanks
Shan
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
You can see your message id, but it isn't in the queue? Are you looking at what it is set to immediately after the send? How do you know it isn't in the queue? Are you using a browse or are you looking at the curdepth? My guess is that you've accidentally put it inside of a UOW. You should be able to use the 'display queue' command to see the curdepth which will include uncommitted messages. I believe the 'display qstatus' command will let you get the count of uncommitted messages.
Thanks for sending me a reply in mqseries.net. How do I see uncommitted message using mq explorer? How do I see uncommited messages.
Basically I put a listener for the sendq. The listener will display a System.out. message and it will send a reply message to a different q. Since I didn't see the System.out message I decided that the message didn't arrive in the queue that the listener was listening.
If I change the transaction type of the Stateless session bean to BEan it sends the message? I don't understand this thing.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum