Topic messages disappearing

Question

I'm running a JMS Topic on weblogic, and I have noticed that as soon
          as a topic subscriber receives exactly 6 messages, it no longer has
          its onMessage method called when messages are produced. I get no
          errors of any sort that I notice, even with logging cranked up to
          Info. I have tried all sorts of combinations of acknowledgements and
          have seen no change. One oddity I have noticed, though, is when I look
          at the Weblogic server console JMS Destination view, I (sometimes, not
          always) see 1 count under "Messages Pending" for each message that the
          client never sees. This number is then set to 0 when the client
          disconnects.
          My set up consists of Weblogic 7.0 SP2, on windows XP. I have a ton
          of memory and processor power. Anybody have any ideas?
          Thanks!
          Jonathan Krebs
          

Answer 1

Hi Jonathan,
          Thanks for filling me in.
          FYI: You can get usually a much smaller jar using the "URLClassLoader"
          approach outlined in the "Small Footprint Client
          Options" white-paper on dev2dev.bea.com. The verbose2zip
          utility is too "greedy". See:
          http://dev2dev.bea.com/resourcelibrary/whitepapers/smallfootprintclient.jsp
          With a bit of extra code, the URLClassLoader approach can actually
          automatically download classes that the class loader
          can't find locally.
          But, if you can, I highly recommend moving to WebLogic 8.1. 8.1
          supplies a built-in thin-client jar. The total size is 700K:
          http://edocs.bea.com/wls/docs81/jms/thin_client.html
          This jar can only works with 8.1 (and future versions).
          Tom
          Jonathan Krebs wrote:
          > Tom, I found my problem. This is one for the notebooks.
          >
          > My client runs in an applet. As you know, Weblogic 7 is all bundled
          > in the gigantic weblogic.jar file. I noticed that the applet took a
          > really long time to load because of this (upwards of a minute) so I
          > used the weblogic verboseToZip utility to scale it down. I had it
          > down to 5 megs, pretty nice.
          >
          > Anyway, once I encountered this problem, I moved on to another part of
          > the project, which required more of weblogic.jar, so I included that,
          > insted of the scaled-down version I had loaded into my IDE.
          >
          > When you asked to see my source, I thought, better run this again to
          > make sure it does what I say, and suddenly it worked. After a few
          > hours of bashing my head against the monitor I realized that's what it
          > was.
          >
          > Now I'm afraid to try to pare down weblogic.jar again, because who
          > knows what weird problem won't show up until it's deployed at a
          > customer's site.
          >
          > Anyway, thanks for your help. I suppose this one could be chalked up
          > to "user error."
          >
          > [email protected] (Jonathan Krebs) wrote in message news:<[email protected]>...
          >
          >>Tom, thank you for your reply. I have narrowed my system down to one
          >>topic and one subscriber, to no avail. My messages are AUTO_ACK (I
          >>have tried all different modes, same thing), and I have also tried
          >>acknowledging them but no use. I should also mention that I'm using a
          >>messaging bridge. Do you think this would make a difference?
          >>
          >>I will contact tech support and see what they have to say.
          >>
          >>Thanks again,
          >>Jonathan
          >>
          >>Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
          >>
          >>>This is odd.
          >>>
          >>>Try with a single subscriber to see if that works, it
          >>>will help narrow down the problem.
          >>>
          >>>Are you subscribers failing to acknowledge
          >>>their messages (if they are not AUTO_ACK and
          >>>not running in an MDB, make sure to call session.acknowledge())?
          >>>
          >>>Do your the messages have an expiration time set on them?
          >>>
          >>>If the above doesn't help, I recommend contacting customer
          >>>support. There are known issues with acknowledgement
          >>>and non-durable subscribers in version 7, but I thought
          >>>that SP2 would cover them...
          >>>
          >>>Tom
          >>>
          >>>Jonathan Krebs wrote:
          >>>
          >>>>I'm running a JMS Topic on weblogic, and I have noticed that as soon
          >>>>as a topic subscriber receives exactly 6 messages, it no longer has
          >>>>its onMessage method called when messages are produced. I get no
          >>>>errors of any sort that I notice, even with logging cranked up to
          >>>>Info. I have tried all sorts of combinations of acknowledgements and
          >>>>have seen no change. One oddity I have noticed, though, is when I look
          >>>>at the Weblogic server console JMS Destination view, I (sometimes, not
          >>>>always) see 1 count under "Messages Pending" for each message that the
          >>>>client never sees. This number is then set to 0 when the client
          >>>>disconnects.
          >>>>
          >>>>My set up consists of Weblogic 7.0 SP2, on windows XP. I have a ton
          >>>>of memory and processor power. Anybody have any ideas?
          >>>>
          >>>>Thanks!
          >>>>Jonathan Krebs
          >>>