Print PDF and RQM Server Health/Performance - what is the relation
Srikanth Bhushan (169●4●27●34)
| asked Jan 25 '13, 2:34 a.m.
retagged Feb 25 '13, 3:13 p.m. by Laura Kuczarski (211●3●7) We started noticing lot of Out of memory errors and Print PDF errors in our RQM logs. Some of them are ERROR com.ibm.rqm.print.service.engine.PrintEngine - the command "----.pdf" reports that it has failed. javax.print.PrintException: The print command (----.pdf) completed successfully, but the PrintEngine was unable to save the results to the repository at com.ibm.rqm.print.service.engine.PrintEngine.executionSucceeded(PrintEngine.java:333) at com.ibm.rqm.print.service.engine.command.PrintCommand.notifyExeSucceeded(PrintCommand.java:330) at com.ibm.rqm.print.service.engine.command.PrintCommand.run(PrintCommand.java:249) at com.ibm.rqm.print.service.engine.command.PrintCommandTask.transactionSucceeded(PrintCommandTask.java:59) at sun.reflect.GeneratedMethodAccessor484.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy1635.transactionSucceeded(Unknown Source) at com.ibm.team.repository.service.internal.AsynchronousTaskSchedulerService$2.transactionSucceeded(AsynchronousTaskSchedulerService.java:825) at com.ibm.team.repository.service.internal.AsynchronousTaskSchedulerService$2.executeTask(AsynchronousTaskSchedulerService.java:834) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:136) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:99) at java.lang.Thread.run(Thread.java:736) Caused by: com.ibm.team.repository.common.ItemNotFoundException: CRJAZ0215I The following record was not found in the database: com.ibm.rqm.print.common.model.impl.PrintJobHandleImpl@3e563e56 (stateId: <unset>, ite mId: [UUID _M6t0EGDzEeKwXZQOK2LTtQ], origin: null, immutable: <unset>) ======================================
[jazz: AsynchronousTaskRunner-13] WARN org.apache.fop.apps.FOUserAgent - The following feature isn't implemented by Apache FOP, yet: table-layout="auto" (on f o:table) (No context info available)
=============================================
00032326 SystemErr R (Location of error unknown)java.lang.StringIndexOutOfBoundsException: String index out of range: 4
=========================
We Do see lot many instances of these errors. What might be causing these.
I also see From the RQM server statistics page, some of the “Print” services and tasks stays very high. All these parameters stay high.
Asynchronous TasksLongest Average Time (seconds)
Seconds
Name
PrintJobReaper
Asynchronous TasksTop Count (Count)
Count
Name
PrintEngineInitQueue
PrintEngineExeQueue
PrintCommandTask
Current CacheTop Hit Count (Top Hit Count)
Count
Name
PrintJob
Current CacheTop Miss Count (Top Miss Count)
Count
Name
PrintJob
Is there any baseline of these numbers to compare with? What is the relationship between Print PDF tasks and RQM server health and perfroamnce? Any suggestions to resolve these? |
|||||||||||||||||||||||||||||||||||
2 answers
what are you printing? Could you introduce how you reproduce this issue?
What do you mean by RQM server health and perfroamnce? Thanks |
In your mind what is a GPS jammer and what can it do to help you? Only when you are in the situation that the portable gps jammer is need you will understand how important and useful such kind of device is. Gaining more knowledge of the device? Just start and then you will have access to the best GPS jammer.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.