Hi.

I’m investigate the condition when CSQ count increase for JMS Connection Alias.

• For UM
• For Broker

Please sincerely provide with any technical information (about 9.10).

Best regards,
Shotat

Hi Shogo,

CSQ count will be increasing only when there is no connection established to the Broker/UM.

Once the connection is established, the documents from CSQ will be processed first and then later published one’s.

Firoz-san,

Thanks for the reply very much.

CSQ count will be increasing only when there is no connection established to the Broker/UM.

I had thought the same as you sincerely replied.
But it seem to be different in case of JMS connection.
Without connection to Broker/UM, it become the error when executing “pub.jms:send”
So I cannot finish the publish service (JMS) successfully and CSQ count (JMS) keeps “0”.

Please sincerely give any advice.

Best regards,
Shotat

Error?

use input parameter “useCSQ” as True for pub.jms:send service and set property Maximum CSQ Size >0 for “connectionAliasName” you are using in send service.

Dear Pradeep Sahu-san,

Thanks for the reply.

I just confirmed that in the case of JMS for UM & Broker CSQ count increases by
the settings you sincerely mentioned.

Best regards,
Shotat

Pradeep Sahu-san, all

I’m still investigating about CSQ.

1. Broker (UM) Server stops.
2. Publish JMS document using “pub.jms:send”
3. Confirm the CSQ count increase.
4. IS stops.
5. Broker (UM) Server starts.
6. IS starts.
7. I expected the message delivered by JMS document should appear on IS server.log
   by subscribing the JMS document in CSQ.
   But JMS document seem to disappear and no message is shown on IS server.log

Why Step 7?

*When Native Pub/Sub (not JMS Pub/Sub), documents are kept in CSQ and any message
is shown on IS server.log at Step 7.

Best regards,
Shotat