BCP-620 · Question #48
An administrator has his BlackBerry Administration Service server setup in a three node BlackBerry Administration Service cluster. He notices that each time he selects a link within the BlackBerry…
The correct answer is A. Log4j.xml. Log4j.xml is the correct file because BlackBerry Administration Service (BAS) is built on a Java EE stack that uses Apache Log4j as its logging framework - the log4j.xml configuration file controls log levels (DEBUG, INFO, WARN, ERROR, TRACE) for all BAS components, and setting…
Question
An administrator has his BlackBerry Administration Service server setup in a three node BlackBerry Administration Service cluster. He notices that each time he selects a link within the BlackBerry Administration Service it takes 2+ minutes before the BlackBerry Administration Service responds. He decides he needs to set the debug log level to "TRACE" to troubleshoot the issue and get a root causes analysis. Which XML file needs to be modified to increase the BlackBerry Administration Service debug log level to "TRACE"? (Choose one)
Options
- ALog4j.xml
- BCluster-service.xml
- CBAS-logger.xml
- DEjb3-entity-cache-service.xml
- EDebugLogLevel.xml
How the community answered
(32 responses)- A78% (25)
- B13% (4)
- D3% (1)
- E6% (2)
Explanation
Log4j.xml is the correct file because BlackBerry Administration Service (BAS) is built on a Java EE stack that uses Apache Log4j as its logging framework - the log4j.xml configuration file controls log levels (DEBUG, INFO, WARN, ERROR, TRACE) for all BAS components, and setting it to TRACE produces the most verbose output needed for root cause analysis.
The distractors are plausible-sounding but fictional or unrelated: cluster-service.xml is a JBoss/WildFly file related to clustering behavior, not logging; ejb3-entity-cache-service.xml controls EJB3 entity caching configuration, not log verbosity; BAS-logger.xml and DebugLogLevel.xml simply do not exist as real BAS configuration files and are invented distractors designed to sound authoritative.
Memory tip: Think "Log4j logs Java" - any Java-based enterprise application (including BAS) that needs log-level tuning almost universally uses log4j.xml (or log4j.properties). If you see a Java middleware product and a logging question, Log4j is the default answer unless the question specifies a different framework.
Topics
Community Discussion
No community discussion yet for this question.