jason.whitehorn Posted August 26, 2014 Share Posted August 26, 2014 We're attempting to integrate Jasper Reports (via the Visualize.js SDK) into a single page web application (written with Ember).I've noticed that after a user has been interacting with the app for a while, eventually calls to Visualize.js fail with an "Authentication Error". From the developer guide, I read that this can either be because of invalid credentials or a session timeout. Refreshing the app gets past the error for a while, but eventually calls start failing again with the same error.From my limited experience with the product, it appears we're authenticating on every request to Visualize.js:visualize auth: name: "user" password: "password", (v) -> report = v.report resource: "/path/to/report" container: "#container" error: (err) -> alert err.message[/code]If we're passing in credentials on each call to visualize, could this possibly be a session timeout? If so, is there a way to prevent session timeouts (e.g. make it more stateless), so the web app can manage this directly? Link to comment Share on other sites More sharing options...
hozawa Posted August 27, 2014 Share Posted August 27, 2014 Seems to be a session timeout. I've experienced the same.If you're using Tomcat, edit confserver.xml file. Search for "<Connector port="8080"". There should be a "connectionTimeout" attribute. Try increasing it. Link to comment Share on other sites More sharing options...
jason.whitehorn Posted August 27, 2014 Author Share Posted August 27, 2014 Isn't that simply the connection timeout for HTTP requests? The current value is 20,000... which, I assume is 20 seconds. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now