[#5008] - jasperserver unable to run on mysql 5.5

Posted by ahagopian on December 16, 2010 - 5:55pm
Category:
Bug report
 Priority:
Normal
 Status:
Assigned
Project:
JasperReports® Server
 Severity:
Block
 Resolution:
Open
Component: Reproducibility:
Always
 Assigned to:
swood
Subscribe

Due to the JIDataType table using a column name of maxValue, jasperserver is unable to run on MySQL 5.5 (which is now GA).

AttachmentSize
File jasperserver-repository-hibernate-aaron-3.7.1.jar30.37 KB
ahagopian's picture
ahagopian
78
Joined: Dec 16 2010 - 11:47am
Last seen: 12 years 5 months ago

10 Comments:

#1Posted by ahagopian on December 17, 2010 - 12:49pm

FYI- I edited
jasperserver-repository-hibernate/src/main/resources/com/jaspersoft/jasperserver/api/metadata/common/service/impl/hibernate/persistent/RepoDataType.hbm.xml

and added a column attribute:
<property name="maxValue" column="[maxValue]" type="serializable"/>

and rebuilt and deployed the jasperserver-repository-hibernate jar to my jasperserver and it worked fine on MySQL 5.5. Obvious the DDLs and the other programs would need a similar update but the [] notation should be cross platform according to hibernate's documentation

#2Posted by planetzone on December 23, 2010 - 5:05am

@ahagopian:
I seem to have a problem building the hibernate project. Could you please upload your rebuilt jasperserver-repository-hibernate jar? I need a quick fix for this problem until an official patch is released.

#3Posted by beren on February 23, 2011 - 9:06pm

Is there a fix in the works for this? Its hard to tell from the tracker (sorry I'm familiar with Jira) what is going on and where this bug fits into the overall set of work.

The bug is a few months old, but is still labeled as new; its a blocker bug, but its also just normal priority.

#4Posted by beren on February 24, 2011 - 12:33pm

I did make the changes to the ddl and hibernate mapping and that does seem to get the install to complete ok.

I foudn I also had to remove all the "type=InnoDB" stuff from the DDL to get that to work at all.

#5Posted by ahagopian on February 24, 2011 - 12:55pm

Instead of removing those lines, you can change it from:

type=InnoDB

to

engine=InnoDB

That did the trick for me.

#6Posted by nicolasdiogo on June 7, 2011 - 10:54am

quite a simple fix

but i have spent a while trying to explain to a possible client that JasperServer is not that bad after this problem stopped their testing..

thanks for the fix

#7Posted by PeterFlinn on June 22, 2011 - 11:42pm

Can anyone advise when this bug will be fixed? Still an issue in 4.0 ce.

#8Posted by ronhashjr on August 15, 2011 - 12:50pm

Any update on when this bug will be fixed? 4.1 ce still errors out. I would hate to modify anything that can cause issues with future upgrades.

#9Posted by julias on August 26, 2011 - 10:46am

jasperserver supports MySQL 5.5 as data warehouse, and doesn't support MySQL 5.5 as repository.
Thanks.

#10Posted by did1979 on February 14, 2012 - 12:57pm

Hello,
I find the same issue.
I just disable the last lines which cahnge the column name.
-- ALTER TABLE JIDataType
-- CHANGE maxValue max_value TINYBLOB;

/var/jasperreports-server-cp-4.5.0-bin/buildomatic/install_resources/sql/mysql/upgrade-mysql-4.2.1-4.5.0-ce.sql

I run the .sh
and after all is correctly upgraded,
I rename the column of the table jidatatype into mysql command line :
ALTER TABLE JIDataType
CHANGE max_value maxValue TINYBLOB;

Feedback
randomness