[ https://issues.jboss.org/browse/DROOLS-1032?page=com.atlassian.jira.plugi... ] Karel Suta updated DROOLS-1032: ------------------------------- Description: When I run WebSphere JMS tests for Kie server then SystemOut log gets filled by exception listed in attachment. It doesn't cause any error in Kie server functionality as error is created by WebSphereSecurityAdapter while JMS use JMSSecurityAdapter to get needed info, it just spam log making it almost unusable for searching for any real issue logged there. Caused by https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv... Maybe would be good to reduce log level there to be able to filter out this error. Edit: After deeper analysis has been revealed that this error actually signals failure in authentication on WebSphere when using JMS. Tests passed because users and their roles has beech cached when running REST tests and for JMS there has been used values from cache. If user would use just JMS for Kie server then he wouldn't be able to use any functionality based on user authentication and its roles like claiming task. was: When I run WebSphere JMS tests for Kie server then SystemOut log gets filled by exception listed in attachment. It doesn't cause any error in Kie server functionality as error is created by WebSphereSecurityAdapter while JMS use JMSSecurityAdapter to get needed info, it just spam log making it almost unusable for searching for any real issue logged there. Caused by https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-serv... Maybe would be good to reduce log level there to be able to filter out this error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)