JMS messages stuck as Pending messages

Ghanshyam Sharma

unread,

Jun 23, 2004, 4:40:27 PM6/23/04

to

Hi.

I am trying to write an application to process huge amounts of data. I try to
process around 1,000, 000 messages [java objects] using a single queue and 8 MDB.
The strange thing is that in the end there are always 10 messages stuck in the
pending message category.

I can also observe that a weblogic thread is stuck. [can see it in the console]
The stuck thread current description is something like "Connectio27.Session28".

I have tried to use the QueueConnectionFactory from a EJB using resource reference
instead of fetching it directly. Even this has not helped. I guess the problem
is that while loading the messages onto the queues, one of the threads gets stuck
somewhere.

I am sing MDB's for processing. There doesnot seem to be any problems on the MDB
side.

If I reboot the server the 10 messages get processed successfully.

Any ideas will be highly appreciated.
-Sharma

Ghanshyam Sharma

unread,

Jun 24, 2004, 11:41:19 AM6/24/04

to

Infact The thread which is stuck is not the loader/message producer thread. It
is a thread handling message driven beans. My producers end up populating the
JMS correctly.

This is 81sp02.
-Sharma

Tom Barnes

unread,

Jun 24, 2004, 2:31:23 PM6/24/04

to Ghanshyam Sharma

Since you narrowed the problem down to the MDB side, can
post a thread dump of the server when it is stuck? That
might help diagnose the problem.

Sharma

unread,

Jun 24, 2004, 2:42:10 PM6/24/04

to

Surprisingly I could process all one million messages if I configure the MDB's
as folowing.

Default-transaction=required
Transaction-typr=container

When I was getting the problem, I had nothing for these settings. I do not know
what is the default, probably Not-supported ???

Let me try my testing a few times and than confirm to you guys.

Tom Barnes <pleasereplyinnewsgroup.webl...@newsgroups.bea.com>
wrote:

Tom Barnes

unread,

Jun 24, 2004, 2:51:03 PM6/24/04

to Sharma

The default is no transactions. I also find it curious
that this helps. I wonder if tx timeouts are helping here...

Sharma

unread,

Jun 24, 2004, 3:47:01 PM6/24/04

to

Hm, this is confirmed. I pumped in one million messages a few time with and without
file stores to differe the performance, but every time I get a clean slate :)

Looks like having required transaction attribute somehow removes this problem.

But still I do not understand why messages were getting stuck with not-supported
attribute. Tom is it possible to understand this. The phenomenon/Reason behind
this may show up somewhere else :)

-Sharma

Tom Barnes <pleasereplyinnewsgroup.webl...@newsgroups.bea.com>
wrote:

Tom Barnes

unread,

Jun 24, 2004, 3:58:45 PM6/24/04

to Sharma

As I wrote below, a thread-dump of the WL Server that hosts
the stuck MDB might help explain things.

Diptanshu Parui

unread,

Jun 25, 2004, 5:06:29 AM6/25/04

to

Shyam,

You are right. If the transaction attribute is not specified it is defaulted to
Not-Supported.

This message on startup of server proves it.

<25-Jun-2004 10:03:10 o'clock BST> <Warning> <EJB> <BEA-010212> <The EJB 'AQJMSMDBBean(Application:
AQMDB, EJBComponent: AQMDB)' contains at least one method without an explicit
transaction attribute setting. The default transaction attribute of NotSupported
will be used for the following methods: onMessage(javax.jms.Message)>

Dips

sree bodapati

unread,

Jun 30, 2004, 11:09:45 AM6/30/04

to

Threaddumps dont seem to show much except for it looks like both execute
thread 13 and 12 are stuck reading from oracle , you may want to see what
query is being sent to oracle by instrumenting you MDB code see that query
properly returns. The threads are runnable but they dont seem to move , what
was the duration between each thread dump ?

/
sree

"Ghanshyam Sharma" <ghanshya...@fanniemae.com> wrote in message
news:40e2ce39$1@mktnews1...
>
> Hi Tom.
>
> I am attaching a thread dump of the server on windows, when I have 20
messages
> stuck as pending with MDB's having not-supported transaction attribute.
>
> I hope this helps in debugging the problem. Please let me know if
something is
> needed.
>
> Thanks everyone.

Ghanshyam Sharma

unread,

Jun 30, 2004, 11:18:46 AM6/30/04

to

Hmm, I didnt wait too much between thread dumps. Probably a minute or two.

Let me check the oracle stuff.

Thanks a Lot.

-Sharma

sree bodapati

unread,

Jun 30, 2004, 11:35:13 AM6/30/04

to

if you waited for a minute or so between each threaddump, it definitly
sounds like an issue around the database query not returning or there is too
much data being returned.

/
sree

"Ghanshyam Sharma" <ghanshya...@fanniemae.com> wrote in message

news:40e2d9d6$1@mktnews1...