In CMC my server APS.core is green, but in my logging folder,i’ve a log aps_BOE.APS.Core_trace.000011.glf shows :
|6C05E2C0ECBD40D7AF2B878EC35E96BB7de|2014 04 18 10:15:06.378|+0200|Error| |==|E| |aps_BOE.APS.Core|13614| 123|Monitoring Service Thread: 18| ||||||||||||||||||||com.businessobjects.monitoring.subscription.SubscriptionManager||[com.businessobjects.monitoring.subscription.SubscriptionManager$SubscriptionsStateComputerTask:invoke] Exception in subscription computation task.
javax.management.RuntimeOperationsException: Exception occurred trying to invoke the getter on the MBean
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:644)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:648)
at com.businessobjects.monitoring.subscription.SubscriptionManager$SubscriptionsStateComputerTask.isThresholdMet(SubscriptionManager.java:386)
at com.businessobjects.monitoring.subscription.SubscriptionManager$SubscriptionsStateComputerTask.invoke(SubscriptionManager.java:275)
at com.businessobjects.monitoring.common.MonitoringTask.run(MonitoringTask.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:761)
Caused by: java.lang.IllegalArgumentException: Object name cannot be null
... 14 more
|6C05E2C0ECBD40D7AF2B878EC35E96BB7df|2014 04 18 10:15:09.679|+0200|Error| |==|E| |aps_BOE.APS.Core|13614| 123|Monitoring Service Thread: 18| ||||||||||||||||||||com.businessobjects.monitoring.trendingmanager.TrendingManager||[com.businessobjects.monitoring.trendingmanager.TrendingManager$MetricDataCommitTask:invoke] unable to access BOE.AdaptiveProcessingServer MBean.Continuing with next managed entity
java.lang.NullPointerException: while trying to load from a null object array loaded from local variable 'details'
at com.businessobjects.monitoring.trendingmanager.TrendingManager$MetricDataCommitTask.invoke(TrendingManager.java:432)
at com.businessobjects.monitoring.common.MonitoringTask.run(MonitoringTask.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:761)
I see the same errors on our new installed BO 4.1 system (not yet in production) in logfile like aps_.APS_trace.000043.glf
I am not sure if this is a problem but it fills up the trace file and making it difficult to see any other maybe more important messages.
The error is “Caused by: java.lang.IllegalArgumentException: Object name cannot be null”
It has to do with Monitoring because I see this for both
com.businessobjects.monitoring.subscription.SubscriptionManager
and
com.businessobjects.monitoring.trendingmanager.TrendingManager
Probably some Monitoring configuration issue where a property is not set to a required value?
So if someone has a clue, I am interested to hear it
Martin.
SAP BusinessObjects BI Platform 4.1 Support Pack 2 Patch 3 - Version: 14.1.2.1216
I’ve got the same error and we are running BI 4.1 SP 05. Actually, I’m getting this over and over in my log files. Any updates.
I’ll follow it up to say that I moved my Monitoring database from Apache Derby to Oracle. I can use a regular SQL Browser to see records in the tables. But I’m getting this error from BI. It’s basically saying it can’t read the JMX Mbean to get the value.
It’s throwing this error on multiple servers, multiple beans… Any insight would be appreciated. Did I forget to install something?
|E13C123CAD2745E39C9DF6DFCC013C9612dd1|2014 12 15 05:22:32.908|-0500|Error| |==|E| |aps_[b]<NODE>[/b].APS.Core| 2000| 407|Monitoring Service Thread: 23| ||||||||||||||||||||com.businessobjects.monitoring.trendingmanager.TrendingManager||[com.businessobjects.monitoring.trendingmanager.TrendingManager$MetricDataCommitTask:invoke] unable to access [b]<Node>[/b] MBean.Continuing with next managed entity
javax.management.InstanceNotFoundException: Topology:name=null,type=EnterpriseNodes
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1092)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:832)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:771)
at com.businessobjects.monitoring.trendingmanager.TrendingManager$MetricDataCommitTask.invoke(TrendingManager.java:437)
at com.businessobjects.monitoring.common.MonitoringTask.run(MonitoringTask.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:763)
I am seeing this as well in my log files with BOB41, SP5, Patch 03. I did a search on SAP Tech support and found a ticket (2153826) that SAYS it is fixed but does not list the patch which includes the fix.
I have been migrating from XI3.1 to BIP 4.1
Same problem before and after installing SP5 patch 6.
I tried updating to \SAP BusinessObjects Enterprise XI 4.0\conf\BO_trace.ini parm from trace_debug;
to
sap_trace_level = trace_error;
But still the same volume of messages, 10MB trace files are filling up every 6 hours. Yet everything in the front end is working as expected.
Would like to get this resolved before going to production.
Anything work for anybody?
OK, so I got the logs to stop filling up by disabling the monitoring application in the CMC, but it looks like I have got problems with the application monitoring configuration, below is from section 20.4 in the admin guide.
20.4 Configuration properties
This section describes the monitoring application properties and how you can edit them.
To see the configuration properties of the monitoring application:
1.
Go to the Applications tab of the CMC.
2.
Right-click Monitoring Application and select Properties. The Monitoring Application Properties window appears. The configurable properties are described in the following table:
Table 89:
Section
Field
DescriptionEnable Monitoring Application
Select this option to enable monitoring functionality. If you deselect this option, all monitoring functions except probes will be disabled. Probe trending will also be disabled.
I have noticed this error in logging directory after re-deployed the APS servers due to the planned BI server re-sizing activity. I haved split APS servers using CMC SAP BI system configuration Wizzard. Some of the APS were deleted and new APS have been created.
BI platform: SAP BO 4.2 SP 05
OS: Unix
I guess that has effected the Monitoring and therefore we are getting the monitoring error logs in logging directory. Please note that the titles of the APS have changed and therefore can no longer be found by monitoring watchlists and alerts. I believe it causes such error to appear. I would advise to go through the monitoring watchlist and check the caution and danger alert checks.
For e.g. APS server changes
The following servers will be created:
BIserver.APS.PromotionManagement
BIserver.APS.DF
BIserver.APS.WebI
BIserver.APS.Connectivity
BIserver.APS.Core
BIserver.APS.Analysis
BIserver.APS.Search
BIserver.APS.Auditing
BIserver.APS.WebIDSLBridge
The following servers will be deleted:
BIserver.APS.Data
BIserver.APS.Auditing
BIserver.APS.Analysis
BIserver.APS.Core
(BOB member since 2003-11-27)
(BOB member since 2002-08-29)