Urgent : weblogic.jms.common.JMSException: Producer not found

Sudeep Kumar

unread,

Nov 26, 2003, 9:41:18 AM11/26/03

to

HI

Whenever we are doing the volume testing on our app the following exception comes
after 10K or 12K of message processing where we are receiving messages from one
queue and after processing publishing the message to another local queue: It shouts
for the local queue on which we r publishing.

weblogic.jms.common.JMSException: Producer not found.

It also says that sender object is not getting closed (although we have closed
it in the finally)

Can i get more info on this exception as why it is coming and what may be the
proposed solution.

Note: we are using Filestore as the persistant message store.

Regs'
Sudeep

Tom Barnes

unread,

Nov 26, 2003, 11:13:30 AM11/26/03

to Sudeep Kumar

Hi,

For urgent requests, ALWAYS contact
customer support immediately. The newsgroups
are informally maintained by volunteers (typically
development engineers), are
not maintained by customer support, and provide
no guarantee for response time or problem resolution.

A google search of this newsgroup (and likely of the support
web-site) would have aided you on this question.
The most common reason for getting "producer not found"
is a misconfiguration where two different resource
are named the same. For various reasons, makes sure that:

(1) all domains are named differently
(2) all wl servers are named differently
(3) all jms servers are named differently
(4) all jms stores are named differently

2,3,and 4 apply even if they are different domains

Tom, BES

Sudeep Kumar

unread,

Nov 27, 2003, 4:54:57 AM11/27/03

to

HI

Thanks for your response and the advice.

As mentioned by you, i checked all my configurations and they all are unique.

On top of it , we are facing the problem only after processing 10000 or 12000
messages.Then how come the configuration issues affects the runtime environment
so late.

Am i missing something here?

Sudeep

Tom Barnes

unread,

Nov 27, 2003, 5:23:05 PM11/27/03

to Sudeep Kumar

Sudeep Kumar wrote:
> HI
>
> Thanks for your response and the advice.
>
> As mentioned by you, i checked all my configurations and they all are unique.

Sorry. But when did you mention this, and where? I can't
find anything in the original post.

>
> On top of it , we are facing the problem only after processing 10000 or 12000
> messages.Then how come the configuration issues affects the runtime environment
> so late.

Random timing related race conditions that happen under load.

>
> Am i missing something here?

Post more info. Full stack traces and config files.
Contact customer support.

Tom Barnes

unread,

Nov 27, 2003, 10:49:00 PM11/27/03

to ple...@replyinnewsgroup.com, Sudeep Kumar

Tom Barnes wrote:

>
>
> Sudeep Kumar wrote:
>
>> HI
>>
>> Thanks for your response and the advice.
>>
>> As mentioned by you, i checked all my configurations and they all are
>> unique.
>
>
> Sorry. But when did you mention this, and where? I can't
> find anything in the original post.

Ignore this comment, I misread your post. But please go
ahead and post your config files, deployment files, and full
stack traces if you wish, and I'll take a quick look.

Regis Serrano

unread,

Dec 3, 2013, 5:24:10 AM12/3/13

to

Hi Sudeep,
We are currently facing the same issue.
And you r post is quite old.
Did you find any solution ?
regards,
Regis