/imq/instances/imqbroker/fs370/txnack 2,8 GB ? how to deal with this?

Question

hi *,
we have mass deleted messages yesterday by an internal java program. now my some of my JMQ managers have a txnack file of remarkeable size. will this ever shrink to normal size again?
how do we get rid of this? what has the custom client done wrong when deleting/consuming messages?
regards chris

Answer 1

hi linda,
thanks for immediate response.
1) we are facing a file with 2,8 in workds twopointeight --> 2800 MB (not 8)
2) dump does not work :-( the version i use does not support that command
imqcmd -b localhost:39176 dump db -o file=XXXXX
Error [A3021]: Bad command specified: dump3) list txn gives the following
imqcmd -b localhost:39176 list txn
Username: admin
Password: XXXXXXXXXXXXXXXXXX
Listing all the transactions on the broker specified by:
Host         Primary Port
localhost    39176
There are no transactions to list.4) normally 1-10 messages / transaction in this case an incredible huge number like 10000 - 30000
--> as a result of this we (in production) should never face this problem in the wild. this originally was caused by our "cleanup script" that to a certain point of time (sunday endo of week) just consumes all unconsumed messages in outr devel environment
5) we are running a cluster BUT particular this case happened in a SJAS domain of CAPS V6 (embedded mode)
the client was an external java programm
6) VERSION i think we are using the same binaries for embedded and non embedded do you know how to detect embedded version?
================================================================================
Sun Java(tm) System Message Queue 4.1
Sun Microsystems, Inc.
Version:  4.1 Patch 2  (Build 2-a)
Compile:  Wed Apr  9 22:49:54 PDT 2008
Copyright (c) 2007 Sun Microsystems, Inc.  All rights reserved.  U.S.
Government Rights - Commercial software.  Government users are subject to the
Sun Microsystems, Inc. standard license agreement and applicable provisions of
the FAR and its supplements.  Use is subject to license terms.  This
distribution may include materials developed by third parties.  Sun, Sun
Microsystems, the Sun logo, Java, Solaris, SunTone, The Network is the Computer,
We're the dot in .com and  iForce are trademarks or registered trademarks of
Sun Microsystems, Inc. in the U.S. and other countries.  All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC
International, Inc. in the U.S. and other countries.  UNIX is a registered
trademark in the U.S. and other countries, exclusively licensed through
X/Open Company, Ltd.
Copyright (c) 2007 Sun Microsystems, Inc.  Tous droits réservés.
L'utilisation est soumise aux termes du contrat de licence.  Cette distribution
peut comprendre des composants développés par des tierces parties.  Sun,
Sun Microsystems, le logo Sun, Java, Solaris, SunTone, The Network is the
Computer, We're the dot in .com et iForce sont des marques de fabrique ou des
marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres
pays.  Toutes les marques SPARC sont utilisées sous licence et sont des
marques de fabrique ou des marques déposées de SPARC International, Inc.
aux Etats-Unis et dans d'autres pays.  UNIX est une marque déposée aux
Etats-Unis et dans d'autres pays et licenciée exlusivement par X/Open
Company, Ltd.
================================================================================
com.sun.messaging.jmq Version Information
        Product Compatibility Version:          4.1
        Protocol Version:                       4.1
        Target JMS API Version:                 1.1
Java Runtime Version: 1.6.0_07 Sun Microsystems Inc. /home/caps/tools/jdk/jre7) Queues only (no topics)
8) how many consumers --> in this case 1
9) in this case 30000 in other cases 1-10 average with an average size of 1-5k
10) in this case inside appserver
11) no HA
12) my estimation would be a couple of minutes but i do not really know ....
regards chris