Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
4 subscribers
Views
1191 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Reports
131666 - no subject - Sometimes our (Task By Process) portal r
Mike James
Certified Lead Developer
over 9 years ago
Sometimes our (Task By Process) portal reports fail. It's not always the same process model we're reporting on, and sometimes they work and other times they do not. Each time we get a failure we receive the same error in the application server log:
2014-12-09 17:33:44,140 [ajp-/0.0.0.0:8009-5] ERROR com.appiancorp.process.analytics2.service.ProcessAnalyticsServiceFacade - com.appiancorp.kougar.driver.exceptions.Signal: index
and in the engine log we see something like...
2014-12-09 17:06:24 [PA00011] {pa131.kdb 29667} (Default) ERROR .a.p.ANLYZE.i "pricroge" "2" "id:51269" "index: exception (Report named 'CMDSFBM_processDashboard' (report document id 51269), maximum report time 2000ms) affected 0 rows"
Can anyone help us understand what might be happening?...
OriginalPostID-131666
Discussion posts and replies are publicly visible
0
Chris
over 9 years ago
Looks like you may be receiving timeouts from the analytics engine. You can try increasing this setting in your properties file, we have ours set to 10000.
server.conf.processcommon.MAXIMUM_REPORT_MS
Assuming that is set to 2000 in your environment?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mike James
Certified Lead Developer
over 9 years ago
Thanks! that was a good suggestion. However, we have increased the report time and still receive similar errors.
ERROR .a.p.ANLYZE.i "pricroge" "63" "id:51269" "index: exception (Report named 'CMDSFBM_processDashboard' (report document id 51269), maximum report time 10000ms) affected 0 rows"
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel