You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Gangadhar Rao <ga...@netcracker.com> on 2014/02/05 12:08:50 UTC

Queue Full exception not thrown on the client side

We are using the activemq cms cpp library 3.4.5 to send and receive messages
from a activemq broker.

Description: 
Queue full exception not thrown on the client side when the queue memory is
full on the activemq broker .


settings
-----------
producer flow control is disabled.

kahadb persistence is disabled.

Using the below configuration for system usage 

<systemUsage>
 <systemUsage sendFailIfNoSpace="true">
   <memoryUsage>
     <memoryUsage limit="20 mb"/>
   </memoryUsage>
 </systemUsage>
</systemUsage>

Using Queues for  the messages.

When the queue memory limit is reached, there is no exception thrown on the
client side.

Can anyone tell of what should be the configuration to get the queue full
exception on the client side.





--
View this message in context: http://activemq.2283324.n4.nabble.com/Queue-Full-exception-not-thrown-on-the-client-side-tp4677459.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Queue Full exception not thrown on the client side

Posted by Timothy Bish <ta...@gmail.com>.
On 02/05/2014 11:25 AM, Gangadhar Rao wrote:
> Yes on the broker side we are able to see the error message.
>
> But on the client side we are not getting the CMSException for queue FULL
> scenario.
>
> We can definitely upgrade to the latest client version. Just like to know if
> the problem what I am stating is fixed in the latter versions.
>
> Thanks,
> Gangadhar
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Queue-Full-exception-not-thrown-on-the-client-side-tp4677459p4677480.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
There was a point at which support for that was added into the client, 
but I don't remember what version it was.  You are welcome to troll the 
issues resolved for each version, that should lead you to the answer.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


Re: Queue Full exception not thrown on the client side

Posted by Gangadhar Rao <ga...@netcracker.com>.
Yes on the broker side we are able to see the error message.

But on the client side we are not getting the CMSException for queue FULL
scenario.

We can definitely upgrade to the latest client version. Just like to know if
the problem what I am stating is fixed in the latter versions.

Thanks,
Gangadhar



--
View this message in context: http://activemq.2283324.n4.nabble.com/Queue-Full-exception-not-thrown-on-the-client-side-tp4677459p4677480.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Queue Full exception not thrown on the client side

Posted by Timothy Bish <ta...@gmail.com>.
On 02/05/2014 06:08 AM, Gangadhar Rao wrote:
> We are using the activemq cms cpp library 3.4.5 to send and receive messages
> from a activemq broker.
>
> Description:
> Queue full exception not thrown on the client side when the queue memory is
> full on the activemq broker .
>
>
> settings
> -----------
> producer flow control is disabled.
>
> kahadb persistence is disabled.
>
> Using the below configuration for system usage
>
> <systemUsage>
>   <systemUsage sendFailIfNoSpace="true">
>     <memoryUsage>
>       <memoryUsage limit="20 mb"/>
>     </memoryUsage>
>   </systemUsage>
> </systemUsage>
>
> Using Queues for  the messages.
>
> When the queue memory limit is reached, there is no exception thrown on the
> client side.
>
> Can anyone tell of what should be the configuration to get the queue full
> exception on the client side.
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Queue-Full-exception-not-thrown-on-the-client-side-tp4677459.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
Check your broker logs to see if you are hitting the limit and the error 
is even being generated.  Upgrade to the latest CMS client.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/