Tracing a Declare Page crashes the node
Hi all,
trying to add Declare Page to the traced pages causes us to see a StackOverflowError in Tracer (after clicking the OK button). The node then becomes unresponsive and has to be restarted.
At one point this is in the log file and the block starting with the underlined line is repeated many times.
Caused by:
java.lang.StackOverflowError
[...]
at com.pega.pegarules.priv.factory.AbstractContainerFactory.acquireObjectAbstractContainerFactory.java:213
at com.pega.pegarules.priv.factory.IntArrayFactory.acquireIntArrayFactory.java:88
at com.pega.pegarules.pub.util.PRDateFormat.formatIDTPRDateFormat.java:591
at com.pega.pegarules.exec.internal.util.PRDateTimeUtilsImpl.getCurrentTimeStampPRDateTimeUtilsImpl.java:710
at com.pega.pegarules.monitor.internal.tracer.events.TraceEventBaseImpl.ctorCommonTraceEventBaseImpl.java:194
at com.pega.pegarules.monitor.internal.tracer.events.TraceEventBaseImpl.<init>TraceEventBaseImpl.java:190
at com.pega.pegarules.monitor.internal.tracer.TraceEvent.<init>TraceEvent.java:207
at com.pega.pegarules.monitor.internal.tracer.TracerSessionImpl.logTraceEventTracerSessionImpl.java:486
at com.pega.pegarules.session.internal.mgmt.Executable.logTraceEventExecutable.java:1253
at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.traceDeclarativePageDirectoryImpl.java:1115
at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.traceDeclarativePageDirectoryImpl.java:1108
at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.isDeclarePageFreshDeclarativePageDirectoryImpl.java:642
at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.findDeclarativePageDeclarativePageDirectoryImpl.java:471
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.findDeclarativePagePRRequestorImpl.java:2195
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.findDeclarativePageThreadPageDir.java:993
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.directPageExistsThreadPageDir.java:697
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.directPageExistsThreadPageDir.java:662
at com.pega.pegarules.session.internal.mgmt.base.ThreadPageDir.pageExistsThreadPageDir.java:658
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.pageExistsPRThreadImpl.java:713
at com.pega.pegarules.session.internal.mgmt.Executable.findPageExecutable.java:1715
at com.pega.pegarules.monitor.internal.tracer.events.TraceEventBaseImpl.collectAnyNamedPagesTraceEventBaseImpl.java:655
at com.pega.pegarules.monitor.internal.tracer.TraceEvent.<init>TraceEvent.java:271
at com.pega.pegarules.monitor.internal.tracer.TracerSessionImpl.logTraceEventTracerSessionImpl.java:486
at com.pega.pegarules.session.internal.mgmt.Executable.logTraceEventExecutable.java:1253
[...]
many more lines....
[...]
[4/29/15 18:10:21:631 CEST] 0000001d ThreadPool I WSVR0629I: The request buffer for thread pool "WorkManager.PRPCWorkManager" has reached its capacity.
[4/29/15 18:10:29:303 CEST] 00000084 SystemOut O 2015-04-29 18:10:29,302 [ WebContainer : 0] [ Developer] [ IAVFW:15.00] .timers.EnvironmentDiagnostics INFO [Node Name]|[IP Adress] [OperatorID here] - --- Thread Dump Starts ---
[...]
We are using PRPC Version 6.3 SP1. This can be reproduced reliably. We now know not to trace any Declare Pages anymore. Have we discovered a bug or can this behaviour be explained?
Thank you.
TATA CONSULTANCY SERVICES
IN
Hi John,
Till before seeing this Post, had never tried to add a Declare Page to the List of Pages to Trace.
But now when I tried to Trace a Declare Page, got the below error in end-user portal. Believe Tracer doesn't have any such capability either to Trace the DeclarePages or specifically to add them to the List of Pages that required to be Traced.
Let's wait for other Community Members to share their comments on this.
| Status | fail |
| Message | caught exception java.lang.StackOverflowError |
| Operator ID | ssssss |
| Requestor ID | H3299E1ED98A8XXXXX62DB4D01FAE3F |
| Timestamp | Thu Apr 30 13:36:28 MST 2015 |
| Engine Version | PegaRULES 6.3 SP1 (coreAssemblyCached_63SP1_38) |
Thanks
Hari
Pegasystems Inc.
IN
Hi John, Good Morning!
- would enabling the option Event Types to Trace --> Declare Pages be of help?
-
as the declare page executes declaratively...
-
assuming that...
-
it is referring to an arbitrary object created at run time &
-
failing to find the exact page name as they're case-sensitive..
- could be the cause for this error, not sure though.
-
failing to find the exact page name as they're case-sensitive..
-
it is referring to an arbitrary object created at run time &
-
assuming that...
- again, the option 'Pages to Trace' would read simple user pages, primary pages and step pages of a requestor.
Please share your thoughts, Thank you!
psahukaru
Pegasystems Inc.
IN
also - once the declare page exists on clipborad - example - node level, read-only, page type - it is not throwing any error when added under Pages to trace section.