Some variables won't write to the log file in Web Services Before Operation rule

IdentityIQ (IIQ) IIQ Discussion and Questions
, , ,
1

Which IIQ version are you inquiring about?

Version 8.4

Share all details related to your problem, including any error messages you may have received.

I have a strange one here. We have been noticing that when we try to log some variables in the Web Services Before Operation rule, the logger statement is simply ignored. We have seen this in numerous rules in various scenarios.

Take this code for example:

  Logger logger = Logger.getLogger("Rule.BeforeOp");
  logger.debug("**************************");  
  logger.debug("requestEndPoint: " + requestEndPoint.getBody());
  logger.debug("test");

The first and the third logger statement do print the listed values to the log file. However, the middle logger doesn’t print ANYTHING. The string value of “requestEndPoint” is not logged and neither is the method call of requestEndPoint.getBody().

We have seen this behavior when trying to log other methods such as .toXml().

What are we doing wrong here? It’s like strings will print if they are not included with a variable, but as soon as a variable is included, the logger just ignores the call to log the data.

We are not receiving any errors at all.

Thanks,
Vic

2

Hi @vic_rinkenberger,

Have you tried removing the requestEndpoint.getBody()?
Also, if removal of the above attributes works then try just printing requestEndpoint to isolate the cause.

Thanks

3

try to print only the requestEndPoint or the headers of this obj. If you havent a body in your configured operation, is normal that you cant see anything in before rule.

ps What operation are you using it for?

4

Hi @vic_rinkenberger remove the body.

Log the requestEndPoint only and see if it will work also let us know the result please.

5

Also apart from above suggestion, try clearing cache , reloading log4j config and restart the application service.

6

Thanks for the suggestions.

To be clear, I have cleared cache and also restarted tomcat numerous times, but the problem persists.

Here is a new block of code that is having the same issue:

  Logger logger = Logger.getLogger("Rule.asdf");
  logger.debug("REP - " + requestEndPoint);
  logger.debug("**************************");  
  Map requestMap = requestEndPoint.getBody();
  logger.debug("requestEndPoint: " + requestMap);
  logger.debug("test");

The only two lines that print AT ALL are the “test” and “***********” statements. The two lines that start with “REP” and “requestEndPoint” don’t print ANYTHING - not even the string values, let alone the variables in the statement.

Any other ideas? This should be pretty basic stuff; printing variables.

Thanks!

1 Like
7

@vic_rinkenberger this is wired and not supposed to happens but okay, let’s do another thing…
Could you please instead of using logger just use System.out.println and check the webserver logs for the same statments let us know if they are appearing or not.

Regards,
Muhammad

8

Hi Vic,

Could you try to force the Debug level by including this like after the logger declaration:

log.setLevel(Level.DEBUG);

You can also include the imports:

import org.apache.log4j.Logger;
import org.apache.log4j.Level;

Best regards

9

I do have the imports already included (I just didn’t include them in the code snippet I posted).

Also, the logging is working for some logging statements, but not others, so it wouldn’t be an issue with the logging level, right?

10

System.out.println does not print anything for any of the lines, not even the ones that are working with logger.debug(). Very strange.

I do see that tomcat logs its startup in the tomcat logs (which is where System.out.println would print to), but System.out.println doesn’t print anything for me.

Vic

1 Like
11

Super strange and weirdo, but lets do one more thing please, could you please creat new application (as a dummy test) and create a new rule with the same logs, and check then let us know…

12

OK, here is the odd part.

I am using the same “Before Operation” rule on my app for both the Create Operation and the Add Entitlement Operation. For the Create Operation, it prints things just fine. For the Add Entitlement Operation, it does the behavior that I have described, where it just simply ignores the logging statements that have the built-in variables mentioned in them.

We have seen this behavior on other apps, so I don’t think a new app will make a difference. I’m just finally reporting the behavior because it is slowing down development.

1 Like
13

yeah, you are correct, if it’s noticed on the other apps, then making a new app will not make any sense, because you will see the same result.

Perfect that you reported that and let us know how it ended up so we can have this knowlage :).

Regards,
Muhammad

14

I find that dump/logging the entire beanshell namespace for beanshell rules helps troubleshooting, by exposing all the available arguments/variables at rule execution time:

Dumping the BeanShell namespace in a rule

Compare the namespace argument/variable details between the create and add entitlement operations.

1 Like
15

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.