g.glazewski

Sorry, I wasn't clear enough. Sometimes I can't get my thoughts together. I edited my question with better explanation what I expect and what tools do I use. The thing is that the conversion is not happening even though it should.

I want to display dates from mysql as Europe/London time in the jasperserver. On login page I set timezone to europe/london, in JDBC connector i changed timezone to europe/london but jasperserver is still showing dates "as is" form database. It is not converting dates to timezone europe/london. How can I solve it? - MySQL's timezone is set to UTC (data is saved as UTC too) - Jasperreport's server is set to Europe/London Right now the only way to get dates as London time is using SQL query ( like convert_tz() ) but this is not what I want. I want it to be dynamic. What is the use of changing timezones in jasper if it doesn't work? thx in advance, Greg EDIT: I am using JasperServer Professional 5.1.0 what I need to have is: 1. dates in database are saved in UTC (i.e. 2013-09-09 13:00:00) 2. Reports are generated in London where BST (GMT +1) exists 3. I want to read dates from database and show them as BST (i.e. 2013-09-09 14:00:00) 4. I want to read dates from database as Europe/Berlin when needed (i.e. 2013-09-09 15:00:00) 5. I don't want to change queries. I need it to be in the presentation layer It looks like it is possible but I need someone's help over here 'cause Jasper is ignoring timezones and is NOT converting anything.

Thank you for the exhausting answer!

Why is jasperserver creating dozens of postgres processes? I am using 5.1.0 and after new start i see this: jasper 5082 0.5 0.2 72372 22024 ? Ss 16:56 0:04 postgres: jasperdb jasperserver 127.0.0.1(55407) idle jasper 5257 2.0 0.3 77800 30044 ? Ss 16:56 0:14 postgres: jasperdb jasperserver 127.0.0.1(55440) idle jasper 5830 2.6 0.2 73696 22000 ? Ss 16:57 0:18 postgres: jasperdb jasperserver 127.0.0.1(55536) idle jasper 5831 4.1 0.2 71460 19728 ? Ss 16:57 0:29 postgres: jasperdb jasperserver 127.0.0.1(55537) idle jasper 5832 2.6 0.3 77928 28360 ? Ss 16:57 0:19 postgres: jasperdb jasperserver 127.0.0.1(55538) idle jasper 5833 0.6 0.2 71548 18396 ? Ss 16:57 0:05 postgres: jasperdb jasperserver 127.0.0.1(55539) idle jasper 7263 1.0 0.2 71948 17772 ? Ss 16:58 0:06 postgres: jasperdb jasperserver 127.0.0.1(55775) idle jasper 7270 1.5 0.3 78392 26000 ? Ss 16:58 0:09 postgres: jasperdb jasperserver 127.0.0.1(55778) idle jasper 8068 2.5 0.3 77684 26264 ? Ss 16:59 0:15 postgres: jasperdb jasperserver 127.0.0.1(55923) idle After few days the list is few times longer. Why is it happening and what impact can it have on overall performance? It seems very weird to have THAT much db connections just to generate a report (data for reports are in MySQL anyway). I think it might be related to the fact that I have to restart jasperserver even now and then 'cause it is getting terrible slow.

As far as I know it is not possible even tho' it sounds like it is basic functionality

Has anything changed? Is ther a way to put crosstab BEFORE detail band?

Same problem. It's really hard to develop anything useful with this stuff.

over a year later you still cannot delete an organization...

Unfortunately it is not possible. If you want to work with Jasper reporting server you must get use to lack of basic functionality and think of thousands workarounds and/or hacks in files.