...
Info | |||||
---|---|---|---|---|---|
| |||||
When:
What:
Why:
How to fix:
|
Info | |||||
---|---|---|---|---|---|
| |||||
When:
What:
Why:
How to fix:
|
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
When:
What:
Why:
How to fix:
|
...
Check from diagnostics logs if there are any warnings or errors, in particular the following ones. If you have followed the installation / upgrade process the broker URL host name should always be localhost and the port number should match with the one configured on the Accounting Service side.
Code Block language text 2019-05-03 16:48:18,707 init WARN Error in opening Accounting Service JMS connection in SSO startup. Accounting Service is a required component of SSO that needs to be functioning when running SSO. javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616?connectionTimeout=10. Reason: java.net.SocketTimeoutException: connect timed out 2019-05-03 17:00:08,112 tech WARN Error in opening Accounting Service JMS connection, event cannot be sent. Accounting Service is a required component of SSO that needs to be functioning when running SSO. javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616?connectionTimeout=10. Reason: java.net.SocketTimeoutException: connect timed out
Check from diagnostics logs if there is the following warning. It implies that you have not properly installed / upgraded SSO or the respective LDAP entry has been manually modified.
Code Block language text 2019-05-03 18:09:46,030 tech WARN MessageQueueSender missing Accounting Service broker URL. Accounting Service is a required component of SSO that needs to be functioning when running SSO.
If the connection is in tact and the Accounting Service is running SSO diagnostics log shows in the startup
Code Block language text 2019-05-03 13:00:03,998 init MessageQueueSender initialised with connection to Accounting Service broker URL: tcp://localhost:36161?connectionTimeout =10
If Accounting Service is not running start it.
If connection timeout is too short on your server change the respective Accounting Service setting in
file, follow instructions in here. Remember to update LDAP.win32.config
/unix.configIf the connection seems to be in tact change log level of
uas/tech
to DEBUG (see Management UI logging configuration) and check for the following messages in the diagnostics log. If the events are sent normally then the problem is on the Accounting Service receiving side.Code Block language text 2019-08-14 12:43:35,969 tech DEBUG Going to send JMS message to the queue: SSOEventQueue 2019-08-14 12:43:35,970 tech DEBUG Elapsed time in MessageQueueSender: 3377300 nanos (3 ms), enabled: true, message sent: true
In the end remember to set the SSO log level back to INFO
...