activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Namrata Patel <namrata.pa...@synergytechservices.com>
Subject Re: Apollo MQ : when sending messages in transaction, producers count keeps increasing
Date Fri, 23 Aug 2013 05:50:09 GMT
Sorry but I don't think so, though I wish it was just that :)

On the admin console http://192.168.31.70:61780/console/index.html , I
cannot even open the queue (click on the name) now. It wont open to see
those Message, Producer and Consumers tabs.


But when i go to the old broker portal:
http://192.168.31.70:61780/broker/virtual-hosts/youtubeNotification/queues/videoQ.html
It shows (attached the full screenshot..) and open to see "Current
Producers", the list keeps going on... So was thinking, it definitely
cannot be just statistics count, as all are diff ports.

> Producers
>
> producers: 232,408
>
> total producers ever : 232,410
>
Also,

While doing some more tests, found that if I don't use transaction, ie
remove BEGIN & COMMIT and transaction-id in MESSAGE.. all works fine. The
producers count goes from 0 to 1 and back to 0 when the script stops..

Hope this info will be helpful to re-produce/test.

Thanks.


On Thu, Aug 22, 2013 at 8:11 PM, Hiram Chirino <hiram@hiramchirino.com>wrote:

> Your just talking about the statistics counters?
>
> On Thu, Aug 22, 2013 at 8:06 AM, Namrata Patel
> <namrata.patel@synergytechservices.com> wrote:
> > Hello,
> >
> > I am using Apollo MQ Version: 1.6 with STOMP 1.2 protocol. I was trying
> to
> > send couple of messages in an transactional manner using "BEGIN" and
> > "COMMIT" stomp commands. This works as expected and all messages get to
> the
> > queue correctly but the producers count keeps increasing. Attached
> > screenshot of the Apollo admin console. The count wont go away even if i
> > delete the queue. I have to stop the broker and restart for it to reset,
> but
> > that is a bad idea for production environment.
> >
> > These are the set of STOMP commands that get fired in background:
> >>
> >> CONNECT
> >> login:admin
> >> passcode:password
> >> accept-version:1.2
> >> host:mybroker
> >>
> >> BEGIN
> >> transaction:tx130822113902
> >>
> >> SEND
> >> transaction:tx130822113902
> >> persistent:true
> >> destination:/queue/videoQ
> >>
> >> {"mymessage":"hello"}
> >>
> >> SEND
> >> transaction:tx130822113902
> >> persistent:true
> >> destination:/queue/videoQ
> >>
> >> {"mymessage":"bwk2323"}
> >>
> >> SEND
> >> transaction:tx130822113902
> >> persistent:true
> >> destination:/queue/videoQ
> >>
> >> {"mymessage":"dummy"}
> >>
> >>
> >> COMMIT
> >> transaction:tx130822113902
> >> receipt:0125d425c2b845844c5532dfc4535b72
> >>
> >> DISCONNECT
> >
> >
> >
> >
> > Do you think there is some issue with the code, as it looks pretty
> straight
> > forward :-)
> >
> > Thanks.
> >
> > Namrata Patel
> >
> >
> >
> > Disclaimer: The information contained in this electronic message and any
> > attachments to this message are intended for the exclusive use of the
> > addressee(s) and may contain confidential or privileged information.  If
> you
> > are not the intended recipient or have received this email in error you
> are
> > notified that disclosing, copying, distributing or taking any action in
> > reliance on the contents of this information is strictly prohibited.
>
>
>
> --
> Hiram Chirino
>
> Engineering | Red Hat, Inc.
>
> hchirino@redhat.com | fusesource.com | redhat.com
>
> skype: hiramchirino | twitter: @hiramchirino
>
> blog: Hiram Chirino's Bit Mojo
>



-- 

*Namrata Patel** *| Software Engineer
Synergy Technology Services

t+91-22-407-51999 | f +91-22-2925-1003 | m +91-9967585155
*namrata.patel@synergytechservices.com*<namrata.patel@synergytechservices.com>|
www.synergytechservices.com <http://synergytechservices.com/>

701 Acropolis, Military Road, Marol, Andheri (East), Mumbai - 400 059

-- 
 

*Disclaimer: The information contained in this electronic message and any 
attachments to this message are intended for the exclusive use of the 
addressee(s) and may contain confidential or privileged information.  If 
you are not the intended recipient or have received this email in error you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.*

Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message