Really long startup times

Question

Does anyone else experience very long startup times with imq? If so, do you know the cause and how to reduce it?
We're seeing startup times of up to an hour with the 3.6 Enterprise version. Stopping the broker doesn't take very long, but restarting is a different story. The log doesn't seem to show anything unusual, but there are long periods where it just sits there doing nothing. Here's an example:
================================================================================
Java Runtime: 1.5.0_01 Sun Microsystems Inc. /usr/jdk/instances/jdk1.5.0/jre
[10/Dec/2005:16:23:57 EST] License: Sun Java(tm) System Message Queue 3.6 Enterprise Edition
[10/Dec/2005:16:23:57 EST] IMQ_HOME=/
[10/Dec/2005:16:23:57 EST] IMQ_VARHOME=/var/imq
[10/Dec/2005:16:23:57 EST] SunOS 5.10 sparc jmsdev03 (1 cpu) emb
[10/Dec/2005:16:23:57 EST] Max file descriptors: 65536 (65536)
[10/Dec/2005:16:23:57 EST] Java Heap Size: max=194688k, current=32448k
[10/Dec/2005:16:23:57 EST] Arguments: -name JMSDEV -port 8001 -license unl
[10/Dec/2005:16:23:57 EST] [B1004]: Starting the portmapper service using tcp [ 8001, 50, * ] with min threads 1 and max threads of 1
[10/Dec/2005:16:23:57 EST] [B1060]: Loading persistent data...
[10/Dec/2005:16:23:57 EST] Using plugged in persistent store:
database connection url=jdbc:oracle:thin:@dbdev:1521:jmsdevdb
brokerid=JMSDEV
[10/Dec/2005:16:24:10 EST] [B1041]: Cluster initialization successful.
[10/Dec/2005:16:24:10 EST] [B1136]: Processing stored transactions
[10/Dec/2005:16:24:10 EST] [B1013]: Auto Creation of Queues is Enabled
[10/Dec/2005:17:05:19 EST] [B1151]: Loading destination mq.sys.dmq [Queue] with 0 messages
[10/Dec/2005:17:05:52 EST] [B1152]: Loading of destination mq.sys.dmq [Queue] complete
[10/Dec/2005:17:05:52 EST] [B3138]: Unable to parse property imq.protocol.tcp.inbufsz:
java.lang.NumberFormatException: For input string: "128k"
[10/Dec/2005:17:05:52 EST] [B3138]: Unable to parse property imq.protocol.tcp.outbufsz:
java.lang.NumberFormatException: For input string: "128k"
[10/Dec/2005:17:05:53 EST] [B3138]: Unable to parse property imq.protocol.tcp.inbufsz:
java.lang.NumberFormatException: For input string: "128k"
[10/Dec/2005:17:05:53 EST] [B3138]: Unable to parse property imq.protocol.tcp.outbufsz:
java.lang.NumberFormatException: For input string: "128k"
[10/Dec/2005:17:05:53 EST] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max thread
s of 10
[10/Dec/2005:17:05:53 EST] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads
of 1000
[10/Dec/2005:17:05:53 EST] [B1004]: Starting the cluster service using tcp [ 0 ] with min threads 1 and max threads of 1
[10/Dec/2005:17:05:53 EST] [B1039]: Broker "JMSDEV@jmsdev03:8001" ready.
========================
As you can see, startup takes roughly 35 mins and between the messages "Auto Creation of Queues is Enabled" and "Loading destination mq.sys.dmq" there's no indication of what's happening.
Any clues?

Answer 1

You may be running into Message Queue bug
6155089 JDBC: JDBCStore.getMessageCount() takes a long time with large messages and Oracle
I imagine this could also happen if you have a lot of messages or destinations.
A fix is being worked on . In the meantime you can work around this by adding
an index to MQ's message table. Details will be posted shortly...
Joe