I am installing appian 7.4 . Our architecture involves an webserver, appserver a

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

christianb0003 — Thu, 09 Jan 2020 15:50:08 GMT

Hi Tejas. I`ve seen in your comment that you suggested to add com.bofa.laws.appian.custom.security.auth.UserLoginEventProcessor to be logged. What I have been trying to do is to configure a logger to catch all log4j from a high level package name , like com.bofa, but it is not working. Do you think would be possible to achieve this behavior? I am using SL4J.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

Eduardo Fuentes — Tue, 16 Sep 2014 04:28:09 GMT

Did you check with the developer of this plug-in? As we mentioned earlier we don't know what this plug-in does for two reasons:

1. This is not part of the base product
2. This is not a plug-in that is shared on Appian Forum

You need to troubleshoot this with your team who develop the smart service.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

srikanthk — Mon, 15 Sep 2014 19:35:02 GMT

will comparing the DB's help in this event . Secondly, i was able to login into designer without any issue. Its only the temp page where i get this error.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

Tejas Kargutkar — Mon, 15 Sep 2014 19:34:01 GMT

It is probably because the custom code does not print information at debug level. You may need to enhance the custom code to catch such exceptions.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

srikanthk — Mon, 15 Sep 2014 19:27:09 GMT

Tejas, i did add the above log4j proeprty to appian log4j.properties but still do not receive anything in logs which is quite frustrating. I did open a case with support.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

Tejas Kargutkar — Mon, 15 Sep 2014 18:36:08 GMT

The log settings can be enhanced by adding the following property in place:
log4j.logger.com.bofa.laws.appian.custom.security.auth.UserLoginEventProcessor=DEBUG

in the appian_log4j.properties file present in the following location:
<Appian_home>\\ear\\suite.ear\\resources OR
<Appian_home>\\runtime_ear\\suite.ear\\resources depending on if you installed Appian using ACM.

Like Eduardo mentioned if your custom code doesn't print that information at ERROR level nor DEBUG then you may want to enhance it to do so.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

srikanthk — Mon, 15 Sep 2014 16:43:21 GMT

how do i enhance the logging ? I have tried re-installing the product agaon on both JBOSS and engine server.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

Eduardo Fuentes — Fri, 12 Sep 2014 07:59:14 GMT

This is a custom smart service created by your team (com.bofa.laws.appian.custom.security.auth.UserLoginEventProcessor), it's not part of the base product, therefore whether you can tell what table is missing or not, it depends on how the code handles this, if your custom code doesn't print that information at ERROR level nor DEBUG then you may want to enhance it to do so.

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

srikanthk — Thu, 11 Sep 2014 22:09:43 GMT

I did check the application server log and found the following

$ cat server.log | grep -i 'Caused by'
[09-08-14 00:38:37:498 GMT] INFO [stdout] (Thread-153) Caused by: HornetQException[errorType=INTERNAL_ERROR message=null]
[09-08-14 00:38:37:611 GMT] INFO [stdout] (ServerService Thread Pool -- 88) Caused by: HornetQException[errorType=INTERNAL_ERROR message=null]

application-server.log

RE: I am installing appian 7.4 . Our architecture involves an webserver, appserver a

Tejas Kargutkar — Thu, 11 Sep 2014 20:49:16 GMT

Take a look at the 'Caused by' exception in the application server log which should have more information about this error.