ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » MQSeries JMS publish/subscribe disk space problem

Post new topic  Reply to topic
 MQSeries JMS publish/subscribe disk space problem « View previous topic :: View next topic » 
Author Message
jennyng
PostPosted: Sun Oct 14, 2001 5:44 pm    Post subject: Reply with quote

Newbie

Joined: 13 Oct 2001
Posts: 2
Hi,

I'm having some serious disk space problems when doing MQSeries JMS publish/subscribe's. All the messages that I publish are appended to some file - C:Program FilesMQSeriesqmgrs[queue manager name]Queues[directory name]Q. Examples of "directory name"s are !!GHOST!56636A8D!0!D4FF0961!2 and !!GHOST!56636A8D!0!116C6875!2. Since my messages are fairly large, this behavior is causing my server to run out of space very quickly (within a day).

Since my messages do not need to be persisted (only subscribers that are running at the time of publish need to receive the messages), I was wondering if there is any way to turn this *feature* off??

Please note that since I'm using JMS, I do not specify the queues to use for publish/subscribe. Instead, the system queues created by running MQJMS_PSQ.mqsc are used.

If anyone can tell me how to avoid this problem, it'll be greatly appreciated. Thanks in advance for your help.

- jenny
Back to top
View user's profile Send private message
kolban
PostPosted: Sun Oct 14, 2001 7:19 pm    Post subject: Reply with quote

Grand Master

Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
It sounds like you have a durable subscriber still in existence. Remember, a durable subscriber is one which claimed that it would come back and desire its messages in the future. You should use the Pub/Sub admin tool to list subscriptions and identify any that are durable and remove them manually if you can't re-run the durable subscriber to collect its held messages.
Back to top
View user's profile Send private message
msvxxx
PostPosted: Wed Jul 24, 2002 2:16 am    Post subject: List durable suscribers Reply with quote

Newbie

Joined: 24 Jul 2002
Posts: 1
I tried to do this with this command:

amqspsd -m QM1 -r *

but the clientIDs don´t appears, this is what appears me:

MQSeries Message Broker Dumper
Start time: Wed Jul 24 11:54:35 2002

Broker Relations
----------------
QMgrName:
QM1
Parent:
None
Children:
None

Streams supported
-----------------
SYSTEM.BROKER.DEFAULT.STREAM
SYSTEM.BROKER.ADMIN.STREAM

Publishers
----------
StreamName: SYSTEM.BROKER.ADMIN.STREAM
None
StreamName: SYSTEM.BROKER.DEFAULT.STREAM
None

Subscribers
-----------
StreamName: SYSTEM.BROKER.ADMIN.STREAM
Topic: MQ/QM1 /StreamSupport
BrokerCount: 0
ApplCount: 1
AnonymousCount: 0
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.BROKER.INTER.BROKER.COMMUNICATIONS
RegistrationCorrellId: 414D51590101000000000000000000000000000000000000
RegistrationUserIdentifier: mqm
RegistrationOptions: 17 : MQREGO_CORREL_ID_AS_IDENTITY MQREGO_NEW_PUBLICAT
IONS_ONLY
RegistrationTime: 2002061710361992
Topic: MQ/S/QM1 /Subscribers/Iden
tities/*
BrokerCount: 0
ApplCount: 1
AnonymousCount: 1
StreamName: SYSTEM.BROKER.DEFAULT.STREAM
Topic: computers/Java
BrokerCount: 0
ApplCount: 10
AnonymousCount: 0
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D31202020202020202020AF5C3D3D12800400
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002072409391734
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D31202020202020202020AF5C3D3D12800300
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002072408410255
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202069822D3D12600400
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071211383449
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202069822D3D12900400
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071211414902
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202069822D3D12A00300
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071211121201
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202008C4333D12100100
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071810091420
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202069822D3D12000400
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071211363146
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202069822D3D12200200
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071209182395
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202069822D3D12500200
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071209212859
RegistrationQMgrName: QM1
RegistrationQName: SYSTEM.JMS.D.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D5120514D3120202020202020202069822D3D12300400
RegistrationUserIdentifier: MUSR_MQADMIN
RegistrationOptions: 1 : MQREGO_CORREL_ID_AS_IDENTITY
RegistrationTime: 2002071211371867
Topic: MQ/S/QM1 /Subscribers/Iden
tities/*
BrokerCount: 0
ApplCount: 1
AnonymousCount: 1

Retained messages
-----------------
StreamName: SYSTEM.BROKER.DEFAULT.STREAM
None


I have the ClientID called "eo" and it not appears.

Who can I list my durable subscribers?

or Who can delete the messages in my Computer?

Thx
Back to top
View user's profile Send private message
bower5932
PostPosted: Wed Jul 24, 2002 8:44 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
It looks like you have 10 durable subscribers hanging around. The client id is masked inside of the correlation id which is why you can't really find it. The only way to get rid of these things will be to write a program to delete them. If you run WMQI as your pub/sub broker, you can use the ControlCenter to do it.

I've also sent you a private message......
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » MQSeries JMS publish/subscribe disk space problem
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.