On an external alert management system (XAMS) that is configured to use Apache ActiveMQ for message queueing, SAS OnDemand Decision Engine encounters an exception after scoring each transaction. Any alerts that are generated are not added to the XAMS output queue. In addition, transactions are not inserted into the Transaction Data Repository (TDR) database. 

Here is an example of the full message that is written to the console log:

WARN  POST_SCORE_ACTION_FAILED cmx_tran_id=0032100692118450 smh_acct_type="CS" smh_activity_type="BF" smh_rtn_code="12" smh_reason_code="ERRR"  failure_reason="org.springframework.jms.UncategorizedJmsException: Uncategorized exception occurred during JMS processing; nested exception is javax.jms.JMSException: Could not connect to broker URL: tcp://<server>:ODE_XAMS. Reason: java.lang.IllegalArgumentException: hostname can't be null"

Workaround

You can work around this issue by updating the jms.xml configuration file located in the <CONFIGDIR>/Lev1/Applications/SASFraudManagement/6.2/<Auth-Domain>/engine/Server<n>/etc directory.

Change the following line as follows:

Original

tcp://${XAMS_QUEUE1_HOST}:${XAMS_QUEUE1_NAME}

Updated

tcp://${XAMS_QUEUE1_HOST}:${XAMS_QUEUE1_PORT}

Then, save the file and restart SAS OnDemand Decision Engine.

Note: You should complete this file update on all servers running SAS OnDemand Decision Engine.