java.util.concurrent.CancellationException when running stories

593 views
Skip to first unread message

Vikram Thaduri

unread,
Mar 16, 2015, 11:12:09 PM3/16/15
to John Smart, thucydid...@googlegroups.com
Hi John,

I am getting the below exception every time I run a bunch of scenarios. Do you have any Idea what going wrong here

Failed to run batch 
stories/Smoke_Tests/SmokeTests.story: java.util.concurrent.CancellationException
stories/Report/Report.story: java.util.concurrent.CancellationException
stories/Details/Details.story: java.util.concurrent.CancellationException
Generating reports view to 'C:\web-auto-tests\target\jbehave' using formats '[stats, console, html, xml, thucydidesreporter, junitscenarioreporter]' and view properties '{decorateNonHtml=true}'
Reports view generated with 7 stories (of which 7 pending) containing 44 scenarios (of which 44 pending)
Tests run: 139, Failures: 0, Errors: 8, Skipped: 45, Time elapsed: 304.694 sec <<< FAILURE!
2015-03-17 14:06:04.807 [36m[Thread-2] [0;39m [34mINFO [0;39m [32mo.s.o.j.LocalContainerEntityManagerFactoryBean [0;39m - Closing JPA EntityManagerFactory for persistence unit 'default' 

Thanks
Vikram
​| ​
Senior Software Engineer

m.dolinin

unread,
Mar 17, 2015, 5:54:04 AM3/17/15
to thucydid...@googlegroups.com, john....@wakaleo.com
Hi Vikram,

Those kind of exception occurs when your stories run more than 300 seconds.
Because Jbehave has property story.timeout.in.secs=3000
by default. Try to put higher value.

вторник, 17 марта 2015 г., 5:12:09 UTC+2 пользователь Viki Syd написал:

m.dolinin

unread,
Mar 17, 2015, 5:55:12 AM3/17/15
to thucydid...@googlegroups.com, john....@wakaleo.com
Sorry story.timeout.in.secs=300

Viki Syd

unread,
Mar 25, 2015, 8:12:05 PM3/25/15
to thucydid...@googlegroups.com, john....@wakaleo.com
Thanks dolinin it solved my problem :-)

I kept story.timeout.in.secs=3600 in thucydides.properties file under project folder and it overridden the jbehave property. Since I have more scenarios I have given 3600.

On Tuesday, March 17, 2015 at 8:55:12 PM UTC+11, m.dolinin wrote:
Sorry story.timeout.in.secs=300

Reply all
Reply to author
Forward
0 new messages