This post is more than 5 years old
9 Posts
0
4670
Scheduled Reports
I have just installed DPA 6 (Build 69322), using it to report on jobs on an Avamar grid.
Everything is working fine, I can create reports and run them interactively then email them to myself - all works fine.
Unfortunately when using the scheduling functionality noting appears to work.
I have used the inbuilt-schedules and created a few custom to no avail.
Looking at the server log in C:\Program Files\EMC\DPA\services\logs I see the report trying to execute at the defined time then failing.
A similar message is seen with all scheduled reports.
Any ideas?
"2013-06-10 11:10:00,015 INFO [com.emc.apollo.scheduler.QuartzJob] (DPAScheduler_Worker-3) Executing Job ...DPASchedReport_0b0f15e3-7100-449c-91bc-555782421875
2013-06-10 11:10:00,015 INFO [com.emc.apollo.scheduler.QuartzJob] (DPAScheduler_Worker-3) Found scheduler job. schedulerJob.getName()=dpaScheduledReport, jndiTarget=java:/queue/DPA/publisherWorkQueue
2013-06-10 11:10:00,016 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (DPAScheduler_Worker-3) IJ000612: Destroying connection that could not be successfully matched: org.jboss.jca.core.connectionmanager.listener.TxConnectionListener@1e8e1ee2[state=NORMAL managed connection=org.hornetq.ra.HornetQRAManagedConnection@2470d710 connection handles=0 lastUse=1370858710832 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@ab2d518 pool internal context=SemaphoreArrayListManagedConnectionPool@4051655d[pool=HornetQConnectionDefinition] xaResource=XAResourceWrapperImpl@6c376e20[xaResource=org.hornetq.ra.HornetQRAXAResource@2b1f2e61 pad=false overrideRmValue=false productName=HornetQ productVersion=2.0 jndiName=java:/JmsXA] txSync=null]
2013-06-10 11:10:00,063 INFO [com.emc.apollo.scheduler.QuartzJob] (DPAScheduler_Worker-4) Executing Job ...DPASchedReport_727ce4fb-3b5c-4319-9c84-b9eba83ed805
2013-06-10 11:10:00,064 INFO [com.emc.apollo.scheduler.QuartzJob] (DPAScheduler_Worker-4) Found scheduler job. schedulerJob.getName()=dpaScheduledReport, jndiTarget=java:/queue/DPA/publisherWorkQueue
2013-06-10 11:10:00,098 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,098 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,098 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,098 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,099 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,099 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,099 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,099 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,099 WARN [com.emc.apollo.datamodel.xml.node.NodeLinkXML] (Thread-404 (HornetQ-client-global-threads-1230121474)) Invalid uuid: null
2013-06-10 11:10:00,129 ERROR [org.jboss.as.ejb3.invocation] (Backup Client Summary:f0e03330-9c98-45c3-aa38-58fefa418810:Sched) JBAS014134: EJB Invocation failed on component QueuedAndRunningJobCacheSingleton for method public abstract void com.emc.dpa.services.reporter.QueuedAndRunningJobCache.informQueued(java.util.UUID,com.emc.dpa.datamodel.report.queue.ReportRunOrigin,com.emc.dpa.datamodel.entity.config.Report,java.util.List,com.emc.apollo.datamodel.security.User,long,java.util.UUID,java.lang.Long,java.util.UUID,java.util.UUID,java.util.UUID,java.lang.String): javax.ejb.EJBException: java.lang.NullPointerException
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:164) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:326) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextI"
Dusted
9 Posts
0
June 10th, 2013 03:00
Found the answer myself in article : esg136230
"Symptoms
After configuring a Scheduled Report, the user clicks the "Save and Test" button. The server indicates that the report was sent to the server for processing. However, the report is not published.
The following message is logged in the DPA server.log file on the DPA Application server:
[Date] [TIME] ERROR [com.emc.dpa.services.reporter.schedule.RunScheduledReportServiceBean] ( :2470998a-ac96-4536-a094-a32fb18b92a1:Sched) Unexpected error occurred when running scheduled report: java.lang.NullPointerException: javax.ejb.EJBTransactionRolledbackException: java.lang.NullPointerException
Cause
This is a known bug/defect in Data Protection Advisor 6.0. This is caused when a scheduled reprot is configured with a scope of children objects (i.e. a specific selection of clients from a backup server).
Resolution
To work around this issue, change the scope to a higher level object. For example, if the currently selected scope is a list of clients change the selection to the backup server that these clients are configured on. This is resolved in DPA 6.0.1 and later.
A Hot Fix may be available for this issue on some platforms and some DPA versions. Please contact EMC Technical Support for more details.
Note: Not all issues are available for a Hot Fix for all versions and platforms. These will be evaluated by L2 SME Engineers and DPA Engineering. If a Hot Fix is not available, upgrade will be required."
That's a fairly basic functionality snafu. I don't want to report on the whole Avamar grid - I want to report on a sub-set of the clients for a specific use case. I have over 1000 clients on this grid.
Pah. When is the next version released?
eagarg1
66 Posts
0
June 10th, 2013 13:00
I had a quick look into this and from what I can tell it seems that there is a patch for DPA 6.0 that will resolve this issue. To get the patch please log a support ticket and reference the ESG article.
Regards,
Gareth