| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Listener servlet not notified |
« View previous topic :: View next topic » |
| Author |
Message
|
| ppietrus |
 Posted: Fri Feb 15, 2002 9:51 am Post subject: |
 |
|
Newbie
Joined: 14 Feb 2002
Posts: 3
|
Hi,
I am using MQSeries with WAS 3.5, we have a bunch of servlets
deployed which register as listeners with some MQSeries queues.
Most of the time this setup works ok. But once in a while
I see that I have a message waiting in my queue, yet my servlet
is not notified. Then the next day after the system is rebooted
- with no configuration changes is miraculously starts to work..
Now however we hit this problem again and refuses to go away
(even by miracle) ... - any thoughts on this?
Thanks!
Pawel
|
|
| Back to top |
|
 |
| bduncan |
| Posted: Tue Feb 19, 2002 11:42 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Some questions:
1) are you using triggering, or are these servlets always running?
2) are you doing a single MQGET with an unlimited wait time, or looping MQGETs with some arbitrary timeout period (and if so, what is the timeout period)?
3) Are the servlets running in a simple servlet-runner, or a full fledged application server?
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| ppietrus |
| Posted: Tue Feb 19, 2002 1:48 pm Post subject: |
|
|
Newbie
Joined: 14 Feb 2002
Posts: 3
|
Hey Brandon,
Thanks for your reply. Here are answers to your questions:
> 1) are you using triggering, or are these servlets always running?
They're always running - actually now, during development, they don't
load at startup, I hit the ones I need with a browser to cause
them to load, and start processing messages.
>2) are you doing a single MQGET with an unlimited wait time, or looping MQGETs
> with some arbitrary timeout period (and if so, what is the timeout period)?
I am using JMS message listeners and register to
be asynchronously notified by MQ
when a new message appears in queue.
I am not calling any polling or proprietary MQ APIs or setting any timeouts.
>3) Are the servlets running in a simple servlet-runner, or a full fledged >application server?
Servlets are deployed to WebSphere Advanced Edition 3.5.4 server
Thanks,
Pawel
|
|
| Back to top |
|
|
| ppietrus |
| Posted: Thu Feb 28, 2002 2:17 pm Post subject: |
|
|
Newbie
Joined: 14 Feb 2002
Posts: 3
|
Seems the problem is solved
The connection factory I was using was transactional (wsqcf) while
my listener servlet obviously did not have an associated
transactional context - and it was never notified. As soon
as I switched to non transactional factory (qcf) all started
to work just fine.
One would expect to get an error if such combination is not allowed
but...
Pawel
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
