171334125

Any update on this? was it resolved or still there in 6.1?

@lucianc, any update on this, was it supported in the later version or not yet now in 6.1?

EnvironmentJasperServer (6.0.1) and AWS Redshift database (the latest version) of UTC timezone. The local timezone for experiment is UTC+8. PurposeFully support local timezone to run report, i.e., the input and output date/time are based on the local timezone. For example, if an user queries data of the date 2015-11-05, i.e., [2015-11-05 00:00:00, 2015-11-06 00:00:00), then two conversions are desired, 1) convert the local time to UTC [2015-11-04 16:00:00, 2015-11-05 16:00:00) and then query against UTC-based database; 2) convert database resultset back to UTC+8 [2015-11-05 00:00:00, 2015-11-06 00:00:00) to be of local timezone. ReportInput: there exists two input parameters to indicate the period of data to query; Output: there exist one output filed of java.sql.Timestamp to indicate the timestamp of this record; QuestionsWhether is the scenario above supported or not? if yes, what is right way to achieve it? if not fully supported, then what extend can it be supported?The observation during fail and trial is: 1) if the inputs are set as the type 'java.sql.Timestamp' then the first conversion can happen automatically, but if the type is set as 'java.util.Date' then it will not happen. Is that expected? For the second conversion, it never happened, do we have to do it ourselves? BTW, I already managed to know how to pass the local timezone to JasperServer (userTimezone) and how to retrieve it in JasperServer wherever needed (TimeZoneContextHolder).

It was solved by decrease MTU from 9000 to 1300.

It is solved. The resolution is: enhance Visualize.js to support timezone parameter in the case of token-based authentication.

It is solved. The resolution is: enhance Visualize.js to support timezone parameter in the case of token-based authentication.

We embedded Jasper reports into our Web application via Visualize.js, and we would like to show reports in local time. what we are using is the token-based authentication, per the API doc, timezone is not the supported attribute in the request (it does in the way of username/password). So one way we plan is to take such info in the token and then pass to JasperServer, so far so good, the last step is at JasperServer side to parse it and then set one build-in session attibute with this value, the quesiton is: what is the session attribute and how to manage JasperServer sesson attribute? Thanks in advace, appreciate our help.

We have a lot details on environment setup and the whole story, but in order not to be distracting, I think the real issue can be reflected as: For one same report - Top N Application, in the case of N = 10 to show the top 10 records, it run properly, which proved Report and database connection were good; but in the case of N = 100, the report kept spinning there without return, from database perspective, it was confirmed that the database already returned the result dataset back. At same time, we saw the error exception in JS log - org.springframework.webflow.conversation.impl.LockTimeoutException: Unable to acquire conversation lock after 180 seconds Besides, the original found was: we had some reports running properly, but some can not; laterly, we found this factor - the size of resultset, the bigger resultset, the more likely Report is hanging there.