The following errors can be seen in the arerror.log: ...................................... Could not refresh JMS Connection for destination 'queue://ESCALATION_LOG_TO_FORM_SERVICE' - retrying using FixedBackOff{interval=30000, currentAttempts=0, maxAttempts=unlimited}. Cause: Wire format negotiation timeout: peer did not send his wire format.
Could not refresh JMS Connection for destination 'queue://LICENCE_SERVICE' - retrying using FixedBackOff{interval=30000, currentAttempts=0, maxAttempts=unlimited}. Cause: Wire format negotiation timeout: peer did not send his wire format. Could not refresh JMS Connection for destination 'topic://FLASHBOARD' - retrying using FixedBackOff{interval=30000, currentAttempts=0, maxAttempts=unlimited}. Cause: Wire format negotiation timeout: peer did not send his wire format. Could not refresh JMS Connection for destination 'topic://GENERIC_NO_LOCAL_BROADCAST' - retrying using FixedBackOff{interval=30000, currentAttempts=0, maxAttempts=unlimited}. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://<server_connect_name>:61617?wireFormat.maxInactivityDurationInitalDelay=120000&wireFormat.maxInactivityDuration=30000. Reason: java.net.ConnectException: Connection refused Could not refresh JMS Connection for destination 'queue://GENERIC_<server_connect_name>' - retrying using FixedBackOff{interval=30000, currentAttempts=0, maxAttempts=unlimited}. Cause: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://<server_connect_name>:61617?wireFormat.maxInactivityDurationInitalDelay=120000&wireFormat.maxInactivityDuration=30000. Reason: java.net.ConnectException: Connection refused ......................................
|
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. Defect SW00503417 added two new server parameters (these are valid for all versions after 9.01.001):
The default values are as above.
Use central configuration add/modify/view the above two parameters. Add this to the com.bmc.arsys.server component for each server in server group. Under heavy load if the JMS error messages are appearing in the arerror.log, the recommendation is to set:
Both changes require AR Server restart. |