Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 sreevani v (sreevani)
Coforge

Coforge
GB
sreevani Member since 2015 1 post
Coforge
Posted: Nov 17, 2017
Last activity: Nov 22, 2017
Posted: 17 Nov 2017 5:15 EST
Last activity: 22 Nov 2017 2:14 EST
Closed

BIX does not function correctly in Prod Environment
"2017-11-01 19:05:27,436 [ PegaRULES-Batch-5] [ STANDARD] [ ] [bilityLines:01.02.01] ( internal.pal.PALDurationImpl) ERROR - Attempting to stop timer pxOtherIOElapsed/pxOtherIOCPU .
Show More
"2017-11-01 19:05:27,436 [ PegaRULES-Batch-5] [ STANDARD] [ ] [bilityLines:01.02.01] ( internal.pal.PALDurationImpl) ERROR - Attempting to stop timer pxOtherIOElapsed/pxOtherIOCPU . Exception while peeking at timerStack;java.util.EmptyStackException; at java.util.Stack.peek(Unknown Source); at com.pega.pegarules.monitor.internal.pal.PALDurationImpl._meStopTiming(PALDurationImpl.java:322); at com.pega.pegarules.monitor.internal.pal.PALDurationImpl.stopTiming(PALDurationImpl.java:363); at com.pega.pegarules.data.internal.access.ExtractImpl.getColumnLength(ExtractImpl.java:5756); at com.pega.pegarules.data.internal.access.ExtractImpl.addDbRow(ExtractImpl.java:5424); at com.pega.pegarules.data.internal.access.ExtractImpl.writeRow(ExtractImpl.java:5249); at com.pega.pegarules.data.internal.access.ExtractImpl.writeRow(ExtractImpl.java:5211); at com.pega.pegarules.data.internal.access.ExtractImpl.writeRow(ExtractImpl.java:5240); at com.pega.pegarules.data.internal.access.ExtractImpl.WritetoOutput(ExtractImpl.java:5143); at com.pega.pegarules.data.internal.access.ExtractImpl.doExtract(ExtractImpl.java:3172); at com.pega.pegarules.data.internal.access.ExtractImpl.runExtract(ExtractImpl.java:1621); at com.pega.pegarules.data.internal.access.ExtractImpl.run(ExtractImpl.java:1463); at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1177); at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:926); at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:777); at com.pega.pegarules.data.internal.access.ExtractImpl.runEngineExtract(ExtractImpl.java:1447); at com.pega.pegarules.data.internal.access.DatabaseImpl.executeExtract(DatabaseImpl.java:7006); at com.pega.pegarules.session.internal.mgmt.Executable.executeExtract(Executable.java:8112); at com.pegarules.generated.activity.ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.step1_circum0(ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.java:169); at com.pegarules.generated.activity.ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.perform(ra_action_runextract_7eb17a5ada24845605c3d982093ca8a6.java:69); at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375); at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10450); at com.pegarules.generated.activity.ra_action_extractflendorsements_9e504818774419a59620edfa6e089519.step3_circum0(ra_action_extractflendorsements_9e504818774419a59620edfa6e089519.java:325); at com.pegarules.generated.activity.ra_action_extractflendorsements_9e504818774419a59620edfa6e089519.perform(ra_action_extractflendorsements_9e504818774419a59620edfa6e089519.java:106); at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375); at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:719); at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:600); at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:885); at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1177); at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:926); at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:825); at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:618); at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991); at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532); at java.lang.Thread.run(Unknown Source);"

Show Less
To see attachments, please log in.
Data Integration
Reporting
System Administration

Posted: 7 years ago
Posted: 17 Nov 2017 10:10 EST
Nick Loving (NickLoving_GCS)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

I've found just one previously reported issue with this error and it was related to a filter condition on the extract rule. The filter was set to "Contains" and changing it to "Is Equal" resolved the problem.

If that doesn't appear to be related to your situation...

What version of Pega is in use?

Does this issue occur every time the extract runs?

Did this ever work?

Is the extract running from command line or via an agent?

Can you provide the complete PegaBIX log?

To see attachments, please log in.
Posted: 7 years ago
Posted: 20 Nov 2017 4:58 EST
sreevani v (sreevani)
Coforge

Coforge
GB

What version of Pega is in use?

The Version which we are using is 7.1.7

Does this issue occur every time the extract runs?

Not Every Time

Did this ever work?

Previously we are not getting this type of Exceptions

Is the extract running from command line or via an agent?

Via an agent

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 20 Nov 2017 10:31 EST
Nick Loving (NickLoving_GCS)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Are you running multiple extracts at the same time?

Screen shots of all tabs in the extract rule may also be helpful.

You may want to also consider opening an SR, as this may require deeper investigation. If you do open one, let us know the number.

To see attachments, please log in.
Posted: 7 years ago
Posted: 22 Nov 2017 2:14 EST
sreevani v (sreevani)
Coforge

Coforge
GB

Are you running multiple extracts at the same time?

Yes we are running two extracts at the same time.

You may want to also consider opening an SR, as this may require deeper investigation

Yes I am opening an SR for the same issue i will provide the SR number after that

Thank You Nick

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice