Version 3

    How to configure MySQL for JBoss Mail Server 1.0M3


    versions: 1.0M3


    Easy way


    The easy way to configure MySQL for JBMS 1.0M3 is to use the graphical installer and select "generate datasource", put in your server/user information then download the MySQL Connector/J 3.1 driver and copy it into your $JBOSS_HOME/server/$CONFIG/lib directory.  Do a full restart and you're ready to start.  You may want to read the bottom section about how to configure MySQL for larger blob sizes.


    Hard way


    The harder way to configure MySQL for JBMS 1.0M3 is to copy the datasource descriptor example from $JBOSS_HOME/docs/examples/jca/mysql-ds.xml to the $JBOSS_HOME/server/$CONFIG/deploy directory.  Edit this replacing the user and server information with the information related to your database.  Following this you need to ensure that some additional information is in the JBMS jboss-service.xml descriptor.




    Adding MySQL specific parts to the descriptor


    In the jboss-service.xml you need to ensure that the following is defined.  (You may also want to remove

    any alternatively defined "Store" implementations.)


                    Hibernate based store that uses a Paging mechanism
                    to achieve partial I/O across a range of databases
            <mbean code=""
                    <attribute name="PageSize">65536</attribute>
                    <attribute name="Compress">true</attribute>
                    <attribute name="CompressBufferSize">65536</attribute>
                    <attribute name="StartIndex">0</attribute>
                    <attribute name="Hashed">false</attribute>
            <!-- Mail Body Manager -->
            <mbean code="org.jboss.mail.message.MailBodyManager"
                    <attribute name="UseStore">true</attribute>
                    <depends optional-attribute-name="Store"


    There is also an addition descriptor that you must change called $JBOSS_HOME/server/$CONFIG/deploy/mail.ear/mail.har/META-INF/hibernate-service.xml.  Ensure it reads as follows:


    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.0//EN"
            <mbean code="org.jboss.hibernate.jmx.Hibernate"
                            <attribute name="DatasourceName">java:/YOUR_DATASOURCE_NAME</attribute>
                            <attribute name="SessionFactoryName">java:/jbossmail.HibernateSessionFactory</attribute>
    <!-- IMPORTANT -->
                            <attribute name="Dialect">org.hibernate.dialect.MySQLDialect</attribute>
                            <attribute name="Hbm2ddlAuto">update</attribute>
                            <attribute name="ShowSqlEnabled">false</attribute>
                   <!--attribute name="CacheProviderClass">
                            <attribute name="CacheProviderClass">org.hibernate.cache.HashtableCacheProvider</attribute>


    That's basically it.  You will need to restart the underlying JBAS instance after making this change.


    MySQL blob page size


    JBMS messages are stored in the database as BLOBs. MySQL requires that the entire blob be sent at once or that "emulated SQL locators" be used.  The above chooses the latter option which move the inefficiency to the database side than over the whole stack.  The entire page size listed above must fit comfortably in mysql's transmit page.  You can define this in your my.cnf:


    set-variable    = max_allowed_packet=32M


    You'll then need to restart MySQL.


    It is strongly recommended that you use the innodb table option.  Consult the MySQL documentation for more information on that issue.




    MySQL does not handle blobs efficiently so we recommend you consider an alternative database for JBMS.