What causes javax.jms.JMSException: Can't publish message: Server running low on memory?

Question

I'm trying to debug a problem with an application running under
          Weblogic 5.11p11, Solaris 2.7. JMS has a JDBC backing store.
          The application runs fine unless we keep it under severe high load for
          a relatively long period of time (say a couple of hours) without
          giving it time to "breath". Then, we start getting these JMS
          exceptions: javax.jms.JMSException: Can't publish message: Server
          running low on memory
          I initially thought this was a GC problem: i thought the GC thread
          wasn't able to "catch up" because the server utilization was high.
          However, when i display Runtime.freeMemory() at the point where i get
          this JMSException, i can see that there is about 16MB (out of 64MB
          totalMemory) of allocatable memory. So it isn't really running out
          of memory!
          I'd appreciate any insights, pointers, etc., about this problem.
          Thank you in advance.
          glauber
          

Answer 1

JMS 5.1 prevents new messages if the server as at 75% utilization. I think (not sure)
          that this can be turned off if desired, but I would not recommend doing so, as this feature prevents
          JMS messages from "hogging" all of the memory.
          Tom
          glauber wrote:
          > Does the JMS server use a separate pool of memory, or does it share
          > the same Java heap? If it's a separate pool, how can it be set up?
          >
          > glauber
          >
          > [email protected] (glauber) wrote in message news:<[email protected]>...
          > > I'm trying to debug a problem with an application running under
          > > Weblogic 5.11p11, Solaris 2.7. JMS has a JDBC backing store.
          > >
          > > The application runs fine unless we keep it under severe high load for
          > > a relatively long period of time (say a couple of hours) without
          > > giving it time to "breath". Then, we start getting these JMS
          > > exceptions: javax.jms.JMSException: Can't publish message: Server
          > > running low on memory
          > >
          > > I initially thought this was a GC problem: i thought the GC thread
          > > wasn't able to "catch up" because the server utilization was high.
          > > However, when i display Runtime.freeMemory() at the point where i get
          > > this JMSException, i can see that there is about 16MB (out of 64MB
          > > totalMemory) of allocatable memory. So it isn't really running out
          > > of memory!
          > >
          > > I'd appreciate any insights, pointers, etc., about this problem.
          > >
          > > Thank you in advance.
          > >
          > > glauber