Reply-to: Geoffrey Fox To: Sung-Hoon Ko cc: Ahmet Uyar Subject: Please make changes Date: Thu, 04 Oct 2001 08:03:51 -0400 From: Geoffrey Fox I am not certain what right paramaters are! Please set up reserve Sonic MQ on grids Please ask for 3.5 THanks Geoffrey Fox gcf@indiana.edu FAX 8128567972 Phones Cell 315-254-6387 Home 8123239196 Lab 8128567977 CS 8128553788 ------- Forwarded Message Date: Wed, 03 Oct 2001 22:22:06 -0700 From: "Hong Zhou" To: cc: "John Yin" Subject: Modify SonicMQ/JMS This is a multi-part message in MIME format. - ------=_NextPart_000_0032_01C14C59.D5E4DA70 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0033_01C14C59.D5E4DA70" - ------=_NextPart_001_0033_01C14C59.D5E4DA70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Dr. Fox: John asked me to show you how to modify some parameters in the SonicMQ = broker.ini file and setup file to improve the efficiency. Here are the = details: 1. in broker.ini file, add one line or modify the line to (if = existing already): GUAR_QUEUE_SIZE=3D10000000 This set the server's buffer size to 10MB. The default is 150KB 2. in broker.ini file, add one line or modify the line to (if = existing already): OUTPUT_QUEUE_SIZE=3D300000 This set every buffer to each client to 300KB, the default is = 150KB 3. in broker.ini file, add one line or modify the line to (if = existing already): QUEUE_DELIVERY_THREADS=3D15 The default is 10. I believe that to our current scale of = queue, 5 more threads could increase the efficiency. 4. in broker.ini file, add one line or modify the line to (if = existing already): WAIT_QUEUE_SIZE=3D150000 The default is 75KB. This parameter probably does not matter = much since it is used to queue those waiting messages. 5. in bin/setenv file, modify the second last line code to: JVM_PARAM=3D"-ms32m -mx256m -ss128k -oss128k" To this line of code, I have experience that setting the initial = memory size to 32M and the max memory to 256MB (in available) could = improve the efficiency and to make the sonicMQ more stable. However, = this is the first time that I increased the stack size. They are = originally 64K. But I guess the 128K may make difference. This is up = to you. We are testing. I already asked for SonicMQ3.5, it will arrive in a few of days. You = probably want to try that. Attached is out broker.ini file. Should you have more questions, please feel free to contact me. Hong Zhou =20 - ------=_NextPart_001_0033_01C14C59.D5E4DA70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi, Dr. Fox:

John asked me to show you how to modify = some=20 parameters in the SonicMQ broker.ini file and setup file to improve the=20 efficiency. Here are the details:

1. in broker.ini = file, add one=20 line or modify the line to (if existing already):

=20 =20 GUAR_QUEUE_SIZE=3D10000000

= This set the=20 server's buffer size to 10MB. The default is 150KB

2. in broker.ini = file, add one=20 line or modify the line to (if existing already):

=20 =20 OUTPUT_QUEUE_SIZE=3D300000

= This set=20 every buffer to each client to 300KB, the default is 150KB

3. in broker.ini = file, add one=20 line or modify the line to (if existing already):

=20 =20 QUEUE_DELIVERY_THREADS=3D15

= The default=20 is 10. I believe that to our current scale of queue, 5 more = threads could=20 increase the efficiency.

4. in=20 broker.ini file, add one line or modify the line to (if existing=20 already):

=20 =20 WAIT_QUEUE_SIZE=3D150000

= The default=20 is 75KB. This parameter probably does not matter much since it is = used to=20 queue those waiting messages.

5. in bin/setenv = file, modify the=20 second last line code to:

=20 = JVM_PARAM=3D"-ms32m=20 - -mx256m -ss128k -oss128k"

= To this line=20 of code, I have experience that setting the initial memory size to 32M = and the=20 max memory to 256MB (in available) could improve the efficiency and to = make the=20 sonicMQ more stable. However, this is the first time that I = increased the=20 stack size. They are originally 64K. But I guess the 128K = may make=20 difference. This is up to you. We are = testing.

I already asked for SonicMQ3.5, it will = arrive in a=20 few of days. You probably want to try that.

Attached is out broker.ini = file.

Should you have more questions, please = feel free to=20 contact me.

Hong Zhou

=20

- ------=_NextPart_001_0033_01C14C59.D5E4DA70-- - ------=_NextPart_000_0032_01C14C59.D5E4DA70 Content-Type: application/octet-stream; name="broker.ini" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="broker.ini" ;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ; File: broker.ini ; ; This file contains the various Message Broker configuration = parameters. ; ; NOTE: Some of the parameter values are provided as examples. ; Please set the value of each parameter as appropriate for your system. = ; There may be additional parameters that you can add and set. ; ; For more information, refer to the Progress SonicMQ documentation=20 ; (Installation and Administration Guide). ; ;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ; ; Installation created on Mon Jan 29 08:20:32 PST 2001 ; ; Serial number=3D123456789 ; Product number=3D35 ; Product name=3D ; ; Set the Control Code CONTROL_NUMBER=3Dtr3hh74929uv8ht ; ; Set the Broker's name: BROKER_NAME=3DDefault ; ; Set the Broker's port number PORT=3D%anabas.vcm.port% ; ; Set the location for the log files LOG_PATH=3D%anabas.installdir%/sonic/log ; ; Set the location of the message files. ERROR_MSG_FILES_DIR=3D%anabas.installdir%/sonic/messages ; ; Enable/Disable Security ENABLE_SECURITY=3DFALSE ; ; SSL default setting=20 ;SSL_CERTIFICATE_CHAIN=3Dcerts/server.p7c ;SSL_PRIVATE_KEY=3Dcerts/serverKey.pkcs8 ;SSL_PRIVATE_KEY_PASSWORD=3Dpassword ;SSL_CLIENT_AUTHENTICATION=3DFALSE ; ; SSL cipher suites (in priority order). ; If blank, all supported suites are enabled. ;SSL_CIPHER_SUITES=3D ; ; SSL default directory for trusted CA certificate(s) ;SSL_CA_CERTIFICATES_DIR=3Dcerts/CA ; ; Set protocol DEFAULT_SOCKET_TYPE=3Dtcp ;DEFAULT_SOCKET_TYPE=3Dhttp ;DEFAULT_SOCKET_TYPE=3Dssl ; ; Enable/Disable the Interbroker feature: ENABLE_INTERBROKER=3DTRUE ;increase the size of the server side buffer by Hong Zhou on 10-3-01 ;10MB GUAR_QUEUE_SIZE=3D10000000 ;IB_CONFIG_SERVER=3Dtcp://: ; ; Specify what acceptor should listen for connection requests from other ; brokers in a cluster. Use a value in the 1..NUM_ACCEPTORS range. ; INTERBROKER_ACCEPTOR=3D ; ; You must specify the Routing Node Name. ROUTING_NODE_NAME=3DDefault ;DEFAULT_ROUTING_ACCEPTOR=3D ; ;double this queue size on 10-3-01 by Hong ZHou OUTPUT_QUEUE_SIZE=3D300000 ; ; Setting Dynamic Queue clean up to true starts a thread that does=20 ; periodic checks of queues for expired messages: ENABLE_DYNAMIC_QUEUE_CLEANUP=3DTRUE QUEUE_CLEANUP_INTERVAL=3D600 ; ; Determines the number of dispatch threads that are created (and ; started) for dequeuing messages from queues: ; increase it to 15 from 10 by Hong Zhou on 10-3-01 QUEUE_DELIVERY_THREADS=3D15 ; ;double the size by Hong Zhou on 10-3-01 WAIT_QUEUE_SIZE=3D150000 ; ; Log file Management parameters MAX_LOG_FILE_SIZE=3D10000000 ;=20 ;BROKER_LOG=3D%anabas.installdir%/sonic/log/log ; ; Database Server Access Parameters. ; This connects with Microsoft SQL Server: ;DB_USER=3D ;DB_PASSWORD=3D ;JDBC_DRIVER=3Dcom.merant.sequelink.jdbc.SequeLinkDriver ;DB_CONNECT=3Djdbc:sequelink:;databaseName=3D ;DB_PROPERTIES=3Dmssqls.cfg ; ; Database Server Access Parameters. ; This connects with Oracle 8i database using the JDBC Thin Driver: ;DB_USER=3D ;DB_PASSWORD=3D ;JDBC_DRIVER=3Doracle.jdbc.driver.OracleDriver ;DB_CONNECT=3Djdbc:oracle:thin:@:: ;DB_PROPERTIES=3Dorasvr8_jdbc.cfg ; ; Database Server Access Parameters. ; This connects with Progress database via Progress JDBC Driver: ; ;DB_USER=3D ;DB_PASSWORD=3D ;JDBC_DRIVER=3Dcom.progress.sql.jdbc.JdbcProgressDriver ;DB_CONNECT=3Djdbc:jdbcprogress:T::: ;DB_PROPERTIES=3Dprogress_jdbc.cfg ; ; Database Server Access Parameters. ; This connects with Cloudscape JDBC Driver (Embedded): DB_USER=3D DB_PASSWORD=3D JDBC_DRIVER=3DCOM.cloudscape.core.JDBCDriver ;DB_CONNECT=3Djdbc:cloudscape: DB_CONNECT=3Djdbc:cloudscape:%anabas.installdir%/sonic/SonicMQDB DB_PROPERTIES=3D%anabas.installdir%/sonic/DefaultDB_jdbc.cfg ; - ------=_NextPart_000_0032_01C14C59.D5E4DA70-- ------- End of Forwarded Message