-
1. Re: Unable to use MySQL for DefaultDS
beyarecords Nov 5, 2004 8:44 PM (in response to pyuill)You don't need to change it. If you are using jboss 4.0 just add your own for mysql. you can find the correct map for mysql in /docs/examples/jca. Alter that file to your own requirements and then dump it in the deploy directory.
regards
Andrew -
2. Re: Unable to use MySQL for DefaultDS
pyuill Nov 5, 2004 9:54 PM (in response to pyuill)I do need to change it because I am running an extremely memory constrained configuration and I need to save every byte I can. Hsqldb eats up a significant amount of memory that I was hoping to save.
-
3. Re: Unable to use MySQL for DefaultDS
raist_majere Nov 6, 2004 4:49 AM (in response to pyuill)On the FAQs there is an entry to this:
http://www.jboss.org/wiki/Wiki.jsp?page=ChangeTheDatabase -
4. Re: Unable to use MySQL for DefaultDS
pyuill Nov 10, 2004 1:37 AM (in response to pyuill)Thanks for the link. It is very useful, but as at 4.0.1 RC1 it is incorrect for MySQL 4.1. The problem turns out to be a change introduced in JBoss 4.0.1 that 'hard codes' the Timer table column names in the EJB Timer GerneralPurposeDatabasePersistencePlugin. I have raised a bug report on it, but in the meantime the options are use 4.0.0, use the noop policy, or patch the source and build your own.
Cheers,
Peter Yuill -
5. Re: Unable to use MySQL for DefaultDS
amenra Dec 15, 2004 10:28 AM (in response to pyuill)I also stumbled across this problem - Does somebody know whether it is fixed in 4.0.1rc2?
Thnx
Sebastian Rohde -
6. Re: Unable to use MySQL for DefaultDS
hazarinaveen Dec 16, 2004 5:19 AM (in response to pyuill)Remove jboss-media-entity-ejb.jar and start server